LabVIEW
Labview com port communication error/driver failure
Hello everyone, I am a student doing summer research at Temple University. We are using labview to collect data from Lock In Amplifiers, and I am currently working on integrating a Thorlabs TSP01 temperature probe into a VI that was made before I was here. I got a VI from Thorlabs which I have integrated into the VI we have for the lock ins, however it appears that the temperature probe crashes about 1 hour into collecting data.
I have made sure of the following according to the specs and advice from Thorlabs:
We only sample data from the probe about once every second.
We reinitialize and stop the driver session each time we collect data.
I have wrapped the temperature probe data collection in a sequence structure which I believe makes sure all those nodes occur in a sequence before the rest of the VI happens
Once the temperature probe crashes, we only read zeroes from the probe, and the rest of the VI slows down dramatically, lags and becomes unresponsive, collecting data every 5-6 seconds instead of once every second. I have time elapsed counter that usually updates once every 1/100 seconds but after the probe crashes it only updates at that once every 5-6 second rate.
There is a Thorlabs GUI that came with the software of the temperature probe, the GUI when run alone does not cause this crash, however if I run the VI and it crashes, the GUI cannot interface with the probe until it is unplugged and reconnected to the computer.
This is a screenshot of the sequence structure, which first starts with a node to get the device resource string. This device resource string is then fed into a node that initializes the device. The instrument handle from that is then passed onto two nodes that get the temperature and humidity data, and after that there is a node to stop the driver session. This sequence executes about once every second. I do not know what is causing this issue and thus any advice or fixes would be helpful as we try to take around 100hr runs, and that cannot be done if the temperature probe crashes.
Please find the VI I am using attached below (you need to download the Thorlabs device drivers found at Thorlabs - Your Source for Fiber Optics, Laser Diodes, Optical Instrumentation and Polarization Meas...) to have the Labview VI elements.
Thank you,
Dipto Provas
@DiptoP wrote:
We only sample data from the probe about once every second.
We reinitialize and stop the driver session each time we collect data.
I have wrapped the temperature probe data collection in a sequence structure which I believe makes sure all those nodes occur in a sequence before the rest of the VI happens
I cannot look at your VI, do not have the latest version on this computer. If you want more people to help, save it it in version 2020.
Typically you do not reinitialize and stop the driver in the loop. This is bad advice. Initialize the driver outside your loop, close it when your loop finishes. If you have an error in the loop, then you can always close it and reinitialize it.
Your sequence structure does nothing; it isolates the Thorlabs code but does not do anything else. Think data flow. One potential issue I see your code is that you are trying to do things in parallel; typically this can be problematic. Connect your VIs by their error out error in so they operate in a sequence.
- Initialize (Outside Loop)
- Measure Temp
- Measure Humidity
- Close (Outside Loop)
Steps 2-4 should be in sequence, do not try to measure in parallel, do not think your sensor can support that.
