LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error in NIScope read

The program works fine until yesterday, but today it seems not stable, sometimes gave error as the attached screen.

 

I tried the NIscope front panel, it(5133) works fine.

 

Any suggestion?

0 Kudos
Message 1 of 11
(3,579 Views)
Have you searched the forum with the error code? Start here
Message 2 of 11
(3,575 Views)

Thanks, but I am only having one device and just simple data polling as attahced.

 

It may caused by not close the session properly. As attached, there are many sessions, some cannot close even I tried to make another simple program.

 

But I tried to start the system still not work. Unable to open the sample there since the version is too old.

 

May you give any suggestion, thanks.

Download All
0 Kudos
Message 3 of 11
(3,570 Views)

turbot wrote:

It may caused by not close the session properly. As attached, there are many sessions, some cannot close even I tried to make another simple program.


You are right at this point. Try closing the session. If not possible try closing LabVIEW and re-launch LabVIEW. Quick try and post back

Message 4 of 11
(3,566 Views)

I restart the PC, unplug and plug the 5133, but still get seem error.

 

This time even use niscope or Max test cannot run any more.

0 Kudos
Message 5 of 11
(3,554 Views)

After self test 2 times, it now works with NIscope front panel only.

 

Does I missing something, such as NIscope initiate acqusition.

0 Kudos
Message 6 of 11
(3,551 Views)
Are you opening up multiple session and not closing it properly?
Message 7 of 11
(3,543 Views)
I just open one session and close it in the end in the attached DAQ2.vi
0 Kudos
Message 8 of 11
(3,540 Views)

Now seems know the error, when I open the signal generator and when there is signal coming in, the program works ok and no errrors occur.

 

But I am still not sure how does it happen and how to change my program.

 

Any suggestion? 

 

0 Kudos
Message 9 of 11
(3,532 Views)
Are you saying that the program now works and that when it wasn't working, you did not have a signal applied? If that's the case, then the error message is normal. Without a trigger event, there is no waveform captured so you are supposed to get a timeout.
Message 10 of 11
(3,512 Views)