@Martin__E wrote:
Hello,
What would be the best way to trap a VISA error where someone disconnects a USB to serial Converter.
At the moment I am looking at the error code and if it is -1073807194 The I break out and let the user reset the system.
Is -1073807194 the only code that will indicate the USB bus was disconnected? Or are there a other codes that apply.
Thanks
Martin
Don't worry about trapping the error where someone disconnects a USB to serial Converter
Trap the "Someone"!
Place a "TEST in Progress - Do not disturb" Sign on the station, Post an armed guard! (with orders to shoot!)
PROTECT your experiment's equipment set-up! The alternative is to state, without ambiguity, the the contitions of your test could not be verified and the data, and any conclusions dranw from the data, have NO merit. (Should be discarded without consideration)
Yes, that is very blunt. If you want to draw conclusions about something you "Test" the "Test enviornment" must be tracable and stable. You CANNOT recover from an undocumented procedural violation easilly. You can abort or fail a "Test" where procedures were not followed..... it is much harder to "Prove" that such a violation did not effect data integrity!
"Should be" isn't "Is" -Jay
