You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On Windows 10 using the regular v2.6.0 build, the integrated Yoctopuce driver does not load and thus data from Yoctopuce modules cannot be received and instead the message "YAPI shared library is missing" is displayed.
To Reproduce
Steps to reproduce the behavior:
Install the regular Artisan v2.6.0 on Windows 10
Configure for a Yoctopuce module
Press ON
See error: YAPI shared library is missing
Expected behavior
Proper connection to the connected module and proper data displayed in the Artisan LCDs.
Setup (please complete the following information):
Artisan Version [e.g. v2.4.4]: v2.6.0
Artisan Build (number in brackets shown in the about box) [e.g. 97e6dec]: 7088095
Version [e.g. 22]:
Platform (Mac/Windows/Linux + OS version) [e.g. macOS 10.15.3]: Windows 10
Connected devices or roasting machine [e.g. Probatone 5]: Yoctopuce module
Additional context
Seems to be a build problem as the Yoctopuce driver is correctly displayed in the About dialog. Further the macOS builds, Windows legacy and Linux builds work flawless with Yoctopuce modules.
The text was updated successfully, but these errors were encountered:
Describe the bug
On Windows 10 using the regular v2.6.0 build, the integrated Yoctopuce driver does not load and thus data from Yoctopuce modules cannot be received and instead the message "YAPI shared library is missing" is displayed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Proper connection to the connected module and proper data displayed in the Artisan LCDs.
Setup (please complete the following information):
Additional context
Seems to be a build problem as the Yoctopuce driver is correctly displayed in the About dialog. Further the macOS builds, Windows legacy and Linux builds work flawless with Yoctopuce modules.
The text was updated successfully, but these errors were encountered: