09-05-2024 02:23 PM
I am trying to run my VI and after about 10 seconds after pressing Run the system pops up with the error and doesn't accurately display any of my signals. The main VI we run is titled "The_boss" in the zip folder and has the other sub vi's in it. This file has already run before (not testing new code here). None of the other sub VI's have been touched in the last several years and don't appear to be the issue at all. This only recent change in the_boss VI was changing which module two of the thermocouple signals came from because the DAQ wasn't recognizing the module. (Module 3 moved to module 7)
09-05-2024 05:02 PM
Haven't seen that error before. This whitepaper, if you haven't seen already, explains the error.
Your VI is difficult to debug due to its screen size. Consider making more subVIs and the diagram more compact. Lot's of things could be improved, use of sequence structures, local variable, could be eliminated.
PS I like the dog.
09-06-2024 01:44 AM
Hi badger,
@thermalbadger wrote:
I am trying to run my VI and after about 10 seconds after pressing Run the system pops up with the error and doesn't accurately display any of my signals. … because the DAQ wasn't recognizing the module. (Module 3 moved to module 7)
09-09-2024 09:53 AM
Hey mcduff,
Thanks for shooting over the whitepaper, unfortunately still have the issues after doing the steps. Been in contact with NI supp staff. I am pretty new with LabVIEW myself and this code for our test setup is legacy from the last several grad students here, but definitely agree.
09-09-2024 09:55 AM
Hey Gerd,
MAX does recognize all my hardware and passes each of the self tests. I also can see live signals coming from each input when I do a test panel. If I understand your "where" question correctly, it happens at a DAQmx Start Task after running the_boss.vi