TCP custom step closes connection after Write operation

[HieuHuynh]

I'm working on a project which requires me to send the command 0x02+"TIME"+0x06+"BASIC"+0x03+0x0D+0x0A  (hex values correspond to unprintable ascii) to a server. The server is expected to respond with the date and time. I am using the custom TCP steptype found here:http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B6A6CBB49F7F2CB1E034080020E74861&p_node=DZ52236&p_source=external


I organized the steps like so: TCPConnect->TCPWrite->TCPRead->TCPDisconnect. The problem is that there is an error after TCPWrite and the process stops, so I am unable to read any data. The error message I get is "Error (No connection established)". The network guys say that it might be an issue with Teststand not setting the socket linger parameter, so the server closes the connection after the write command.

I greatly appreciate any effort to fixing this problem, or providing an alternate solution to sending and receiving information through tcp with Teststand.

-Hieu Huynh

[DWeiland]

Hi HIeu,

Were you able to get the example that is inlcuded in that zip file working at all? I would say try that with some sort of standard tcp connection that doesn't require any special inputs and see if you can get that to function on your workstation.

Let me know, thanks Hieu.