06-19-2017 07:41 AM
They are both set to "switch when released". Anyway the crash happens even if I start the application with both the boolean true and I don't change their value while the VI is working.
06-19-2017 07:51 AM
That is what I would expect. If you send a command once the switch is set, it will continue to send that command every 200ms. If it takes the instrument longer than 200ms to configure for your request, it will eventually crash. Likewise, if you continually write information in this fashion and are sending a command with a "?" each time, you might also overrun the read buffer. However, I believe that it does handle this in the Read buffer like a FIFO and discards any earlier responses without crashing.
Try setting the mechanical actions of the READ and WRITE Booleans to Latch when released instead of Switch when released.
06-23-2017 07:02 AM
Minions ha scritto:
That is what I would expect. If you send a command once the switch is set, it will continue to send that command every 200ms. If it takes the instrument longer than 200ms to configure for your request, it will eventually crash. Likewise, if you continually write information in this fashion and are sending a command with a "?" each time, you might also overrun the read buffer. However, I believe that it does handle this in the Read buffer like a FIFO and discards any earlier responses without crashing.
Try setting the mechanical actions of the READ and WRITE Booleans to Latch when released instead of Switch when released.
I tried but nothing changed...
...Finally I solved when I threw my Prolific USB-Serial Adapter away and I replaced it with my new FTDI USB-Serial Adapter.
Thanks everybody for the hints.