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
On last snapshot in next branch in serial port mode for Sump device implementation, requesting more than one time in a row "Show device metadata" from "OLS Capture settings" fails with
"Detection failed!"
"No such port!"
Context: Windows, usb-to-serial adapter
Running acquisition also fails after requesting device metadata.
Running acquisition without requesting device metadata succeeds, repeatedly.
Seems that the problem is in SumpDetectionTask, but I couldn't find the root cause: the streams seem to be properly closed, maybe is something about releasing the comm port...?
The text was updated successfully, but these errors were encountered:
Around commit 72ee061, after I applied some fixes regarding blocking reads I did not encounter the problem, but this was in August last year. I just tested it again (the patched, compiled version that I kept) and still works fine. Now it is difficult to say for sure what patches I embedded in that version, but I'm pretty sure I didn't run in the same thing.
Win8.1 x64: the usb-serial-adapter is based on PL2303TA chip and with recent drivers provided by windows update (works pretty well from my point of view).
The device is similar to Arduino Generic Logic Analyzer, but developed for Microchip PIC16 platforms with support for RLE, but nothing special for triggers. The device triggers on first detected change in input. I didn't get the time to publish the project code yet but I hope to do this soon also.
On last snapshot in next branch in serial port mode for Sump device implementation, requesting more than one time in a row "Show device metadata" from "OLS Capture settings" fails with
"Detection failed!"
"No such port!"
Context: Windows, usb-to-serial adapter
Running acquisition also fails after requesting device metadata.
Running acquisition without requesting device metadata succeeds, repeatedly.
Seems that the problem is in SumpDetectionTask, but I couldn't find the root cause: the streams seem to be properly closed, maybe is something about releasing the comm port...?
The text was updated successfully, but these errors were encountered: