Passing telnet session between LabVIEW calls from TestStand

[JoshSat]

From TestStand I am calling VI's from telnet.llb.

In one TestStand step  am opening a telnet session to an IP address and collecting the telnet connection (U32). In the next TestStand step I pass the telnet connection  to a telnet write VI but get this error.

 "Dequeue Element in Acquire Semaphore.vi:1->Telnet Write.vi:1->Telnet Write.vi.ProxyCaller"

The telnet open, write, read, and close work great if I pass the telnet session number within the same VI. But I need to keep the session open between calls from TestStand because one huge VI is not feasible.

thank you

josh

[asbo]

I've sort of done what you're talking about in a previous project. In a VI, I opened the telnet connection, sent/received some data, and then passed the reference back out (the idea was to keep the shell session open). I did maybe 10-15 seconds of other testing, then called another VI to close the connection. I had to verify the session was staying open, so I telnet'd again manually during that 10-15 window and the shell session was definitely still connected. I didn't use a read or write between the two VIs, but if the connection had gone stale by the time I tried to close it, an error would have been passed out and it wasn't. Maybe you should post your attempt?

[dowNow · Accepted solution]

Check that your LabVIEW adapter is set for Reserved Execution. If it is already, I don't know, you might need to create a parallel thread that keeps the session alive.

cc

[RayFarmer]

Hi,

Maybe the following link can help

http://forums.ni.com/t5/NI-TestStand/Can-a-Telnet-session-be-passed-from-1-vi-to-the-next-in-test/m-...

[JoshSat]

That cleared the problem.

My LabVIEW Adapter Configuration needed to be set to allow "Reserve Loaded VIs for Execution" in order to pass the telnet connection (U32) variable.

THANK YOU,

josh