Antcas TCP
The Antcas TCP interface is completely documented here. The protocol is based on TCP/IP. Antcas Control automatically establishes the connection to the client. Only one port from the server to the client is required.
Function Description
The PLC provides a TCP server and the gateway of Antcas Control establishes a connection. After the handshake, a translation table and all values are transferred to Antcas Control. A database of available variables is automatically created during installation. After initializing the client, visible by the START command, Antcas Control now sends back all data. Values with external initialization are set.
Every variable of the PLC is described bidirectionally. This means that the value is always synchronized between Antcas Control and the client.
Monitor
The values in the monitor are highlighted with colors. These have the following meaning.
| Color | Description |
|---|---|
| Yellow | System message |
| Gray | Internal translation |
| Blue | Read request from Antcas Control |
| Green | START command |
| Orange | Telegram was sent without translation |
| Red | Telegram could not be processed |
Notes
- The number of characters at the input of the name is limited to 50. Longer strings cannot be correctly displayed in the monitor and explorer.
- The string of the same data type must not appear in multiple function blocks simultaneously. The interface cannot send telegrams without unique identification.
- Note the maximum number of data per second. Since the server records all data, this can lead to damage to the file system.
Library
There is a library for CoDeSys 2.3 and for e!COCKPIT for all Ethernet controllers from WAGO. The library is not protected and may be modified after consultation with Antcas.
antcas-tcp-codesys-wago.zip (Version 1.3)