01-19-2011 12:58 AM
Hi Rambaldi!
I am having same problem as you were having.
Can you post your vis which are working?
01-19-2011 03:27 AM
here is the code im using.
01-22-2011 01:17 PM - edited 01-22-2011 01:22 PM
@Rambaldi wrote:
here is the code im using.
06-03-2011 03:11 PM
I have to talk to some legacy CVI (7.1) code that resides on the Unit Under Test and is running in the form of an exe. That code is currently a TCP Client. It was being called by some CVI tests that were bundled into a DLL, and each test was called from TestStand (3.1). The tests within CVI are considered the slave, as there is a setup routine that calls RegisterTCPServer.
if ((status = RegisterTCPServer (ATS_TCP_PORT, ATS_TCP_Callback, NULL)) < 0)
To work within our existing architecture, however, I need to re-do (what is currently) the Server code in LabVIEW (8.5) and each of the tests will be called from TestStand (4.01). In the CVI Server, the TCP_Handle was a static Unsigned, so the handle seemed to be valid for all the tests that wanted to use it from TestStand.
static unsigned TCPhandle = 0;
In my mind, it would make most sense if the UUT code (what is now the client) were modified so as to be the server. Then, each labview test (called from teststand) would open a TCP connection, send the message, close connection. However, some would like to re-use the client-side C code if at all possible. If I did that, the labview tests would somehow need to be a server, or I need to create ONE somehow that all the tests use, correct? I thought I ran into this long ago, where the type for a TCP handle created down in a labVIEW VI didn't translate well into a TestStand type, so I couldn't keep the TCP Handle valid.
Any thoughts or clarification would be appreciated.
06-12-2020 05:58 AM - edited 06-12-2020 06:00 AM
Thanks