TCPIP Cryouts

Configuration Notes

TCP/IP Connection

A TCPIP port in ACM can maintain the socket connection between the device and server or it can be set to release it when done. If using Report by Exception (RBE) with a TCPIP port in ACM, the port must be configured to Maintain Control. There must be a single TCPIP port for each device. The devices must be configured to call out to the host on the existing socket connection. This connection allows for the device to send RBX messages to the server. For the ACM server to recognize and allow the messages being sent from the device, Enable Unsolicited Support needs to be selected on the Connection tab of the device in ACM.

Important

Ensure that lazy connection is not selected. If it is selected and the connection is dropped, ACM will not try to re-establish the connection until the next poll. This is an issue as with cryouts it is the device that is sending the RBX messages. If the device has lost its connection it can’t send its message*

TCP Listen Connection

To use the TCP-Listen port for cry outs, multiple devices can use the same listen port. Within the TCP Listen configuration the listen ports must be set to an open listen port on the server, and the device must be setup to send the message to that listen port. Within the device configuration, on the Connection tab, the option to 'Enable Unsolicited Support' must also be selected to allow the RBX messages to be accepted by the device object in ACM.

Important

When the TCP Listen object accepts an incoming socket connection, it will monitor the socket for a maximum of 5 seconds waiting for unsolicited data to be received. If there is no data received within 5 seconds, the socket will be closed. If the field device has a transmit delay setting, verify that it is set to a value less than 5 seconds.