LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

200478 no channels in task after Windows 7 auto updates

MS pushed a Win7 update this morning while I had Labview open, but was not actually running any VI's. After that, several VI's that had been working yesterday, and have not been changed in any way hung when accessing my USB-6251 at the acquisition timing setup step, and after some time bombed. I also could not start the test interface in MAX but it did recognize the hardware. I noticed 2 listings for this hardware and on starting MAX and would first get an error message claiming the data base was corrupt (this box could be closed). I used the max reset feature to reset the data base. Now MAX features work ok and data transfer can be tested there and seems to work fine (in MAX). When I run my LV programs however, now they immediately bomb after the timing setup step when I attempt to  simply read the sample clock rate using a property node (also has always worked before)  with error 200478 claiming there are no channels in the task. Clearly there are; the program has not changed since yesterday when it worked fine. Obviously, the windows push corrupted something in the DAQmx arena. How do I clean this up?  Thanks.

0 Kudos
Message 1 of 7
(3,483 Views)

First thing I would try is a forced recompile (Ctrl-Shift Run Button).

 

Have you tried building up the same logic in a new VI?

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 7
(3,464 Views)

Thanks Mike. At the moment something I haven't tried yet. At the moment I'm in the many hours long process of reinstalling DAQmx. If that doesn't work, I'll try your suggestion. This is the second time in a month I've had something similar to this happen. Last time (I believe there was a MS Windows push some time before this happened, but the machine was idle for 2 weeks) it took me 3 days to recover. After trying various repairs etc, I eventually cleaned everything NI off my machine and reinstalled everything including LV 2013 from scratch. That worked. I'm hoping to avoid that this time.

Chris

0 Kudos
Message 3 of 7
(3,436 Views)

Mike,

The reinstall of DAQmx had no effect on the (channel) error,  forcing a recompile had no effect on the errors, and creating a new Vi with the same program had no effect. My next step will be to wipe everything NI off my hachine (1/2 day) and reinstall /update everything again (1 day) unless you have some other suggestion for me to try (I hope!).

Thanks,

Chris 

0 Kudos
Message 4 of 7
(3,428 Views)

Sorry no. I am freah out of ideas.

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 5 of 7
(3,425 Views)

Problems resolved!

For some reason, when MS did the Windows update push, the device assignments changed. What was always dev1 was now dev2. Maybe this happened because the 6251 is a USB device and the update changed something in the USB port asssignments (???).

Thanks for your help!

Chris

0 Kudos
Message 6 of 7
(3,415 Views)
Whew! That was a close one. But in a way it makes sense.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 7 of 7
(3,405 Views)