I am working on a project that uses the Analog Discovery 2 to measure the response of a DUT over a long period (hours or days). I am working in LabVIEW and have been building this project using the foundation provided in the LabVIEW project shared here. It uses both the Waveform Generator functionality to apply a signal and the Scope functionality to measure the response.
Currently, I am running into a problem where my code stops working after 250 minutes. It seems to be very consistent. I and another have replicated the issue using multiple AD2 devices, multiple PCs, and both the LabVIEW source code as well as compiled into an executable. I have used LabVIEW to do profiling on the memory usage and such of the application and I do not believe I have a memory leak eating away at the PC. Also, the timeout is very repeatable to 250 minutes. The log files always end after that amount of time has passed.
Is it possible that the AD2 session has a timeout built into it somehow? If so, how do I reset the AD2 before the timeout occurs? I looked through the SDK and did not find a function call that appeared to be the obvious one to use.
Question
Chris Pouzou
Hello,
I am working on a project that uses the Analog Discovery 2 to measure the response of a DUT over a long period (hours or days). I am working in LabVIEW and have been building this project using the foundation provided in the LabVIEW project shared here. It uses both the Waveform Generator functionality to apply a signal and the Scope functionality to measure the response.
Currently, I am running into a problem where my code stops working after 250 minutes. It seems to be very consistent. I and another have replicated the issue using multiple AD2 devices, multiple PCs, and both the LabVIEW source code as well as compiled into an executable. I have used LabVIEW to do profiling on the memory usage and such of the application and I do not believe I have a memory leak eating away at the PC. Also, the timeout is very repeatable to 250 minutes. The log files always end after that amount of time has passed.
Is it possible that the AD2 session has a timeout built into it somehow? If so, how do I reset the AD2 before the timeout occurs? I looked through the SDK and did not find a function call that appeared to be the obvious one to use.
Any help would be appreciated! Thank you.
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.