06-06-2013 03:28 PM
Simple VI, writes *IDN?\n, reads the response, using visa write/read.
Works fine on local system with GPIB::nn::INSTR.
Fails on remote system with:
Error -1073807265 occurred at VISA Write in test.vi
Possible reason(s):
VISA: (Hex 0xBFFF005F) No listeners condition is detected (both NRFD and NDAC are deasserted).
Only change to the VI is that the resource (selected from the pull down menu choices) is preceded with visa://host/.
On that same remote system, it works from MAX.
Looking at the trace, the write call shows up and gets an error.
What is wrong?
06-07-2013 08:08 AM
Actually the error above is reported, for each LabVIEW session, on the second and sucessive runs.
The first time I run it the error is different:
Error -1073807346 occurred at VISA Write in test.vi
Possible reason(s):
VISA: (Hex 0xBFFF000E) The given session or object reference is invalid.
Here's a snapshot of the VI, running locally:
Remotely the resource would start with visa://remote/
06-07-2013 11:43 AM
Hi instrumento,
I have been able to find some KnowledgeBase articles regarding the errors you listed. I hope that this helps clear things up!
Error -1073807265: http://digital.ni.com/public.nsf/allkb/49817A4A58B78843862574730051962F?OpenDocument
Error -1073807346: http://digital.ni.com/public.nsf/allkb/A2561CDE98B66DD4862566510078264F?OpenDocument
Regards,
Jason D
Applications Engineer
National Instruments
06-07-2013 02:12 PM
Error -1073807265: http://digital.ni.com/public.nsf/allkb/49817A4A58B78843862574730051962F?OpenDocument
Error -1073807346: http://digital.ni.com/public.nsf/allkb/A2561CDE98B66DD4862566510078264F?OpenDocument
The first document tells me to check for the correct gpib address, which does not apply here. I have a VISA resource constant on the block diagram, which is filled by LabVIEW by querying available addresses, and I'm just selecting one. Either way, on the local system, where the code works, the address is gpib::5::instr, on the remote system the resource is visa://hostname_where_gpib_is/gpib::5::instr, so it ought to work. No need to check GPIB cables for remote visa operations either.
The second document talks about Automatic Closing VISA sessions. This is not set in the remote system.
01-19-2022 09:18 AM
I had exactly the same issue. I was also using a VISA resource Alias as identifier. I noticed that the GPIB address of the instrument did not match what NIMax showed; GPIB0::29::INSTR. The actual address of the instrument was 30. Once I changed it to 29, all worked well. The Alias is just a define for the actual VISA Resource Name.