09-25-2012 02:23 PM
Hello one and all... I have a pair of laptops in my lab used to collect data. They both have LabVIEW2009 installed. All of my hardware is USB driven (cDAQ-9174's). The one I use most is a newer Win7 machine and the other is a older WinXP machine... I've used the XP machine for several years without issue, but now when I hook it up to one of my cDAQ-9174's it gives me an error in MAX (little exclamation point in a yellow triangle) and if I try and run an older VI that I know should run without issue, it locks up LabVIEW and I have to go to the Task Manager to stop the application.
Max is telling me that I need to go to here (http://digital.ni.com/public.nsf/allkb/EDA23D2970BD16C6862577D70006E3CA) and see about possible data corruption issues... which I've never had. ...and that I need to go to Microsoft's website and download a patch. Ok, I did that and am still getting the little warning exclamation points in MAX that I'm assuming is telling me that there is a problem with the unit. The modules all show up and test out fine, the chassis tests out fine, but the warning symbol still is there. Anyone have any thoughts on this? I searched, but came up dry. A helping hand would be much appreciated!
Thanks!
Chad
09-26-2012 10:30 PM
Are there any error messages that display when you try to run any tasks on the devices that have the warning label? What version of the DAQmx driver are you using? Check the Device Manager in Windows to see if the device is loaded under Data Acquisition Devices. Also go to your services window: Start>>Control Panel>>Administrative Tools>>Services and Check if NI Device Loader is started. You can also reset the chassis in MAX by right clicking and selecting reset chassis.
-Travis E
Applications Engineer
National Instruments
10-01-2012 04:31 PM
@Travis-E wrote:
Are there any error messages that display when you try to run any tasks on the devices that have the warning label? What version of the DAQmx driver are you using? Check the Device Manager in Windows to see if the device is loaded under Data Acquisition Devices. Also go to your services window: Start>>Control Panel>>Administrative Tools>>Services and Check if NI Device Loader is started. You can also reset the chassis in MAX by right clicking and selecting reset chassis.
-Travis E
Applications Engineer
National Instruments
Travis,
I'll take these one at a time...
Are there any error messages... negative, just locks it down so if I try and select anything (and I do mean anything!) it just beeps.
Version of DAQmx... not sure, where would I check that?
Loading in DAQ devices.. yep, they all show up without issue.
Device Loader is started and ready to go.
I've reset the chassis, run self tests on all the modules with no change.
Now there is one thing that I thought of that might be causing this... I did make the last few modifications to the VI on my Win7-64 bit machine. ...and this started when I tried to pull the VI back to my XP 32-bit machine. I'm not thinking this has anything to do with my VI's, but rather the hardware since it happens in MAX. (already checked for updates and everything is up to date) VI's work fine when hooked up to the Win7 machine, but lockup at the first hint of trying to talk to the cDAQ.
Thoughts?
Chad
10-01-2012 04:44 PM
10-01-2012 04:52 PM
Yep, as I mentioned in my first post, I've already applied the "hot fix" and it did nada.
Thanks though!
C
10-01-2012 05:06 PM
Tried wiping the MAX database yet? Wouldn't be the first time that's gotten corrupted...
10-02-2012 08:33 AM
...didn't know that was possible. How is it done?
THX
C
10-02-2012 01:24 PM
the easy way: http://digital.ni.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9
or the hard way: http://digital.ni.com/public.nsf/allkb/86256F0E001DA9FF86256FFD005B827C
or just uninstall/reinstall MAX.
10-02-2012 03:52 PM
Thanks! I'll give it a shot and see what happens.
C
10-10-2012 04:45 AM
I was also facing the same problem few days back.It is sorted now.
Open MAX window>>Tools>>Reset configuration data.
After that installed the "hotfix" zip file as mentioned. It worked fine for me.
Hope this help.