-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Home: Scopy exits or hangs after connect in calibration #1531
Comments
Hi, Before trying to connect to the M2K - could you check in the Preferences page for a setting related to OpenGL and if checked, uncheck it. Then try to connect to the M2K and see if this still happens? Thank you! |
Hi Alexandra, no, unfortunatly unchecking "use hardware accelerated plotting - OpenGL (EXPERIMENTAL)" did not work. With session logging enabled I do not get a crashdump, only the log file. Nothing spectecular there. It ends with:
Any other suggestions what I could test? Kind regards |
Hi! The initial release candidate for the new Scopy v2.0.0 is now available in the official releases page: https://github.com/analogdevicesinc/scopy/releases/tag/v2.0.0-beta-rc1. This candidate includes a lot of new features in Scopy while bringing multiple bug fixes for the ADALM2000 plugin and underlying libm2k library. Could you give this version a try and reopen the issue if the bug still appears? We tested this new version of Scopy in 2 other similar cases and the problem didn't reappear. Thank you! |
Environment:
Describe the bug
After clicking connect, "Connecting" and then "Calibrating" is displayed. After a few seconds the Scopy window closes, or it hangs forever. This only happens on my work laptop (Lenovo ThinkPad P15 Gen 1). No problems on another laptop under both, Windows 10 and Linux (LMDE 6).
To Reproduce
Steps to reproduce the behavior:
As described above
Expected behavior
Finish calibration after a few seconds and resume normal operation
Additional context
I tried the usual:
Other observations:
Unfortunately, I cannot recall if this ever worked on this machine. Scopy had worked on a previous machine. It might be related to a Windows update or the way how priviledges are managed (EPM?).
The text was updated successfully, but these errors were encountered: