To learn more about triggers in general, see section Understanding Triggers.

The TCP/IP client trigger turns your Automation into a listening client that connects to TCP/IP servers. There are multiple devices and systems that take the role of a TCP/IP server: vision inspection systems, printers, PLCs, scanners, weighing scales, etc. Automation can connect to them and wait for the incoming data. After receiving a certain number of characters, a character sequence, or a timeout, the TCP/IP client trigger fires, and starts executing your actions. If the connection fails, the trigger allows you to automatically reconnect.

Typical use: You are automatically printing multiple types of packaging labels using a network printer. It is crucial for you to know when your printer is done printing one label type before you start printing the second label type. The TCP/IP client trigger allows you to set permanent automated checking of printer availability. While printing the first label type, the TCP/IP client trigger checks for the printing status, and when the printer is done, it sends a message to Automation to send the second label type for printing.