Why viWrite works and VISA Write does not (insufficient location information)?

[BarnaCsenteri]

I have issues with a VISA device which works from NI-MAX test panel but it doesn't with Labview VISA write.

I did checked NI I/O Trace to see the difference and the buffer for "*IDN?\n" is the same, the difference is that NI-MAX Visa test panel uses viWrite while the Labview visa write uses "Visa write". In theory it should not be any difference between the two but it seems it does.

Here it is the trace, the upper one when I try from NI-MAX, the two errors are when trying from Labview. I did tried with shortened VISA reference and also direct TCPIP link (both returns the same error). The VISA Open works however (added a probe after visa open and the result is at the end of the screenshot so it seems it finds it ok, the issue appears with first VISA write which is a IDN query.

 

I am aware of this two issues:
https://forums.ni.com/t5/LabVIEW/IDN-works-in-VISA-test-panel-but-VI-does-not/td-p/3575540/page/2

https://forums.ni.com/t5/LabVIEW/VISA-Hex-0xBFFF0011-Insufficient-location-information-or-the/td-p/6...

however I do not have any additional driver, nor package I can install (except different versions of NI-VISA).

My labview version is 2019sp2 and NI-VISA is 21.5 (installed with NI-DAQmx).

[RTSLVU]

What is the instrument you are trying to communicate with?

[JÞB]

---

@BarnaCsenteri wrote:

I have issues with a VISA device which works from NI-MAX test panel but it doesn't with Labview VISA write.

I did checked NI I/O Trace to see the difference and the buffer for "*IDN?\n" is the same, the difference is that NI-MAX Visa test panel uses viWrite while the Labview visa write uses "Visa write". In theory it should not be any difference between the two but it seems it does.

Here it is the trace, the upper one when I try from NI-MAX, the two errors are when trying from Labview. I did tried with shortened VISA reference and also direct TCPIP link (both returns the same error). The VISA Open works however (added a probe after visa open and the result is at the end of the screenshot so it seems it finds it ok, the issue appears with first VISA write which is a IDN query.

 

I am aware of this two issues:
https://forums.ni.com/t5/LabVIEW/IDN-works-in-VISA-test-panel-but-VI-does-not/td-p/3575540/page/2

https://forums.ni.com/t5/LabVIEW/VISA-Hex-0xBFFF0011-Insufficient-location-information-or-the/td-p/6...

however I do not have any additional driver, nor package I can install (except different versions of NI-VISA).

My labview version is 2019sp2 and NI-VISA is 21.5 (installed with NI-DAQmx).

---

You have not released the resources the the VISA test panel is reserving.  No other application can get a session handle while the resources are reserved so you get an error that essentially means; "VISA cannot open a session to that resource from this application." 

Close the VISA interactive test panel and try again.

[BarnaCsenteri]

---

@JÞB wrote:
You have not released the resources the the VISA test panel is reserving.  No other application can get a session handle while the resources are reserved so you get an error that essentially means; "VISA cannot open a session to that resource from this application." 

Close the VISA interactive test panel and try again.

---

It is closed. I did also retried with restarted system (without even opening that panel). Does not works.

[BarnaCsenteri]

---

@RTSLVU wrote:

What is the instrument you are trying to communicate with?

---

I tried with a few ITECH PSU's (2xM3223 and 1xM3812), neither works. Neither of them has special drivers, it's simple over the ethernet VISA. The only thing they provide is a VISA based factory API which 1st thing after open does a *IDN? (for identification).

I tried with a local simple "COM1" and that works.

Tried the same instruments from a different PC, same network, same labview, visa a bit older - it does not works either (however since the second system is a development PC there were 20-30 devices already started with this one without issues).

So I am not sure if this is something instruments related or some VISA issue - it it would not work from NI-MAX test panel I would say instrument issue but with that working I just don't know 😞

Tried raw socket too - it connects but no answer to *IDN?\n (both VXI-11 and raw socket are mentioned in the instrument manual).

I will contact the instrument maker too just to be sure there is not a bug on their side.

[dkfire]

You haven't shown any code yet, so it is hard to say what you are doing in your LabVIEW setup. 

I know that the ITECH vi's that I have found has a ton of errors and bad LabVIEW implementations. 

[crossrulz]

---

@BarnaCsenteri wrote:

Tried raw socket too - it connects but no answer to *IDN?\n (both VXI-11 and raw socket are mentioned in the instrument manual).

---

Are you using a normal display mode or '\ Codes' display mode for your command string?  If using normal, your command is not correct.

[BarnaCsenteri]

---

@dkfire wrote:

You haven't shown any code yet, so it is hard to say what you are doing in your LabVIEW setup. 

I know that the ITECH vi's that I have found has a ton of errors and bad LabVIEW implementations. 

---

That's exactly the reason I did made a simple test code (attached) which produces the same error.

I did tried with, without termination character etc. but the buffer in IO trace looks the same for VISA test panel and this dummy code:

[BarnaCsenteri]

---

@crossrulz wrote:

---

@BarnaCsenteri wrote:

Tried raw socket too - it connects but no answer to *IDN?\n (both VXI-11 and raw socket are mentioned in the instrument manual).

---

Are you using a normal display mode or '\ Codes' display mode for your command string?  If using normal, your command is not correct.

---

C codes. Anyway the buffer seems to be the same for the VISA and viWrite content in IO trace (so it should be ok in theory).

[crossrulz]

---

@BarnaCsenteri wrote:

---

@crossrulz wrote:

---

@BarnaCsenteri wrote:

Tried raw socket too - it connects but no answer to *IDN?\n (both VXI-11 and raw socket are mentioned in the instrument manual).

---

Are you using a normal display mode or '\ Codes' display mode for your command string?  If using normal, your command is not correct.

---

C codes. Anyway the buffer seems to be the same for the VISA and viWrite content in IO trace (so it should be ok in theory).

---

Your example VI is using \ Codes.  But a word of advice.  If you are using a display mode other than normal, turn on the display style (right-click, Visible Items->Display Mode).

Back to your actual issue, you might be having issues with a firewall.