Environment:
Describe the bug
When Scopy 2.0.0 is started on a win10 machine, it recognizes the connected M2K.
But there is already a small orange x symbol as warning.
Then clicking correct starts calibration of Osci, Spectrum Analyzer, Network Analyzer and Signal generator, whereas the rest is already ready to use (square sign as stop button). Few seconds later, Scopy windows suddenly shuts down, before finishing the calibrations.
To Reproduce
Steps to reproduce the behavior:
- Click on 'Connect'
- Observe the analyzers, osci etc will be calibrated....
- See the crash and shut down of the compete Scopy window.
See pictures at
https://ez.analog.com/sw-interface-tools/f/q-a/597450/scopy---adalm2000-recognized-tried-to-lick-on-connect-few-secs-later-scopy-crashes-and-shuts-down
Environment:
Describe the bug
When Scopy 2.0.0 is started on a win10 machine, it recognizes the connected M2K.
But there is already a small orange x symbol as warning.
Then clicking correct starts calibration of Osci, Spectrum Analyzer, Network Analyzer and Signal generator, whereas the rest is already ready to use (square sign as stop button). Few seconds later, Scopy windows suddenly shuts down, before finishing the calibrations.
To Reproduce
Steps to reproduce the behavior:
See pictures at
https://ez.analog.com/sw-interface-tools/f/q-a/597450/scopy---adalm2000-recognized-tried-to-lick-on-connect-few-secs-later-scopy-crashes-and-shuts-down