I am writing Labview code for a Picoscope 4227. Inevitably some changes result in failures which means the code stops before the 4227 gets a close command. I find that getting the 4227 to a state when the next time the program runs the open command works is really problematic. Sometimes just unplugging the USB cable is sufficient. Sometimes I have to restart the computer before the 4227 comes back and sometimes not even that will do. How do I reset the 4227 in a consistent way so I don't waste so much time just getting the thing to respond?