From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Simple Messaging (STM) error on cRIO

Hi all,

 

We are trying to get our STM server-client implementation working, with server deployed on a cRIO 9038, and client on a Win 7 PC.

In the past this system has worked fine on PCs, but when deploying on the cRIO we get a comms issue (and PC also loses connection to the hardware).

 

We tried stripping back to basics, and deployed the very basic server-basic example as per the tutorial: http://www.ni.com/tutorial/53683/en/

When attempting toestablish connection via the client, we still get errors here: error 66 on the server (cRIO) and error 56 on the client (image attached).

 

Error 56: The network operation exceeded the user-specified or system time limit.

Error 66: The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools»Options»VI Server on the server side.

 

Other that the last suggestion of checking machine access, is there anything else to give us a further clue as to why the connection is not working?

 

0 Kudos
Message 1 of 2
(2,209 Views)

Error 56 in TCP read means that the read timed out before data was available - what do you have the read timeout set to, and are you sure there should be data at the port when you are reading? 

 

Without seeing code, I would guess the TCP read error is occurring first, closing the client side connection, and then the write occurs but the connection was closed so you see the error 66 coming from the write. 

0 Kudos
Message 2 of 2
(2,189 Views)