Post by Lake Shore Jeff M on Nov 26, 2018 15:29:57 GMT -5
It seems that we may have a bug in our model 372 driver. Your trace capture shows no response to *IDN?
If you look at the ‘initialize.vi’ in the 372 driver, it appears it’s sending *RST before it updates the COM port settings (parity, baud, stop/start bits). This causes an error state and the COM port to be messed up. We were able to see a similar problem when I ran the driver at my desk.
We have an updated VI that I would like to send you so please send me an email at email@example.com so I can forward the updated VI to you for verification that it resolves the issue.
Post by Lake Shore Jeff M on Nov 29, 2018 12:01:47 GMT -5
Thanks For the post Francois.
So that everyone knows the full story, we also provided an updated initialize.vi for your 2016 Labview application which resolved what we saw happening in the initial issue you reported. We will provide the new .vi to National Instruments and they will post an updated version of the Model 372 Driver within the next two weeks