LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1074135039

Hello all,
 
i encountered this error indicating 'Error - 1074135039 occured at Instrument -specific error.' ... please see attached.
 
I wired the right connections to error in, error out and the vi doesn't have any broken wires when i run the vi.
 
What should i do next?
0 Kudos
Message 1 of 6
(3,603 Views)
Hi microes,
    have you already took a look at this? and this?

    remember that there're other resources than forum to get infos Smiley Happy
  
    ...even if it's true that sometimes it's difficult to find the right document into the almost infinite NI library.... Smiley Very Happy

    Have a nice day!

graziano

  
0 Kudos
Message 2 of 6
(3,593 Views)

Greetings Graziano,

i'm not using calibration executive. The thing is my .vi consists of several sub vis indicating different test modes. I did four in total and only the last one gave me a problem. When error out left the 'Run.vi', it displays 'error 1074135039' which leaves me at my wit's end.

Thanks for any insight!

 

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

Ooh, i managed to use highlight execution and found out after the command *ESR? being written using Visa Write, the Visa Read still manages to capture a value '16', my previous vi showed the value is zero which is why i don't have this error.

what should i do to recitify this?

Thanks a lot!

0 Kudos
Message 4 of 6
(3,579 Views)
An instrument specific error usually means that a command was sent that is illegal for the current instrument settings. The author of the driver has trapped that condition and generated the error code. You did not provide the VI that is generating the error or even the name of the VI so it's impossible to provide an exact answer for your problem. You could open the VI and look at the code for it and see under what conditions that error code gets generated. You have a text search option in LabVIEW so you could do a search for that error code.
Message 5 of 6
(3,558 Views)
OOh kay, i realised a fault at my part for sending wrong command to the device. Now it works fine, thank you all!
0 Kudos
Message 6 of 6
(3,537 Views)