TCP-IP connection ID doesn't work after being assigned to a global

[stephenb2]

I'm not sure the device makes a difference. It works as expected over a windows command line telnet session or in a Tera Term session (no repeating of history after each write and read). It is a radio that provides a wireless path for ethernet.

[stephenb2]

Writing to the TCP-IP socket VISA clears the read buffer. Running 'Clear VISA' does not. Wheh, that means the solution is workable.

[JÞB]

And that's why I asked for the device.

TCP/IP Socket and TCP/IP Instrument classes have slightly different properties.  It looks like you discovered correctly that you need a socket.

The details are not important and way more that I care to dive into ( I'd just get a bunch of TL;DR replies anyhow so dig into the help file and google your hearts out)

[stephenb2]

Here is a different solution that preserves the tcp-ip session between TestStand steps.

Under Configure->Adapters->LabVIEW:

I prefer using TCP-IP palette VIs for telnet because it is faster than TCP-IP over VISA (though it could just be my implementation).

[JÞB]

---

@stephenb2 wrote:

Here is a different solution that preserves the tcp-ip session between TestStand steps.

Under Configure->Adapters->LabVIEW:

I prefer using TCP-IP palette VIs for telnet because it is faster than TCP-IP over VISA (though it could just be my implementation).

---

Nice,  remember to call through the project context to avoid proxy caller namespace gotchas.