12-13-2013 02:20 PM
I am currently using a USB 9213 to measure temperatures and I upgraded a computer and went from LabVIEW 2010 to LabVIEW 2013.
The vi I had used for years does not work and get the message "Error 200088 occurred at DAQ assistant. Task specified is invalid or does not exist" when quitting the vi a sign appears saying "Resetting vi"
If i try to generate a new vi ussing the DAQ assistant, when I select the temperature mode the message "reading System configuration, Please wait"
and then the computer freezes with no further action.
Is this a problem with the labVIEW 2013 installation? everything worked well with the LabVIEW 2010 version.
12-13-2013 02:23 PM
Hello Pablo,
What was involved in the upgrade? Is this the same PC, or a new one? Did you reformat or remove software as part of the upgrade? Have you also upgraded the DAQmx driver? Are you able to create a task in Measurement & Automation Explorer? Does the same code still work in LabVIEW 2010?
Regards,
12-13-2013 02:23 PM - edited 12-13-2013 02:24 PM
Edit: duplicate post.
12-13-2013 06:00 PM
This is a new PC running Windows 7 and with a new load of LabVIEW 2013, so everithing in the computer part is new. The vi I am trying to run was created with LabVIEW 2010 in an older computer and had no problems.
I installed NI DAQmx 9.7.5 as part of the LabVIEW 2013 installation, and all other vi that I have been running with third party hardware (MCC) in the LabVIEW 2010 run just fine in the new computer with LabVIEW 2013. So far the only vi that does nor run is the one that has the NI USB temperature module. The vi code runs just fine in an older computer with LabVIEW 2010
12-13-2013 06:22 PM
Hi Pablo,
This sounds like you may be using a preconfigured task (from MAX) that hasn't been recreated on the new computer. Try copying your MAX configuration to the new computer as per this KnowledgeBase:
KnowledgeBase 2GJJ9SY1: Export/Import (Save) the System Configuration in Measurement & Automation Explorer (MAX)
http://digital.ni.com/public.nsf/allkb/0E0D3D7C4AA8903886256B29000C9D5A
It would also help if you could share your code (or at least a screen capture) where you attempt to read from the DAQ device- without seeing how you're configuring the task, it's very difficult to discern what might be happening.
Regards,