Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

-1192 error code??

Using Labview 6.0.  Getting the following error - "Error in 1433 Get Scan   Error # -1192".   It doesn't happen all the time.  When the error starts happening, it seems to continue.  But restarting Labview will stop it.  What is causing it and how do I stop it?
 
One time I also got Error # -121.  Are these two related?  Will fixing one fix the other?
 
Thanks,
John.......
0 Kudos
Message 1 of 6
(3,943 Views)
Hi John,

Could you give some additional information about your VI? What is the program doing? Are you using DAQ? Where do the errors occur?
Nick R
NI
0 Kudos
Message 2 of 6
(3,927 Views)

I am using a system that someone else wrote.  It is on a Dell PC running XP.  There is a Hewlett Packard VXI system scanning instruments in our lab and Labview gets the info from that and displays.  So I probably can't answer your questions completely.  I have only been here about 3 months and haven't been using the system for very long.  They (people who have been here longer than me) tell me that the previous PC didn't have any problem.  This was at least 3 years ago.  I am thinking that the problem was in the upgrade from whatever the previous system was to the new Dell PC with XP.  I am not sure that Labview 6.0 is fully compatible.  Sorry I can't give you a lot of information.  I'll keep asking the people here to see what I can find out.  Would you recommend going under the program compatibility screen (right click the desktop icon, properties, compatibility) and checking it to run under an earlier Windows?  Thanks for any help you can give.

 

John........

0 Kudos
Message 3 of 6
(3,924 Views)
I do know that 6.0 is not officially supported for Windows XP. LabVIEW 6.1 is supported. That could be responsible for the problems you are seeing.
Nick R
NI
0 Kudos
Message 4 of 6
(3,894 Views)

Thanks for the reply. 

 

john........

0 Kudos
Message 5 of 6
(3,883 Views)

After talking with some of the other personnel, it seems this error is being passed from an Agilent driver.  There is no update to the driver and the only solution is to shutdown and restart if it gets too bad.

John.......

0 Kudos
Message 6 of 6
(3,877 Views)