The IP Slave mode is used to connect one or more Over-the-Air and local Ethernet ports to the internal registers . The OTA and Ethernet ports use the Modbus via TCP protocol or the Modbus TCP protocol. The external devices connected to these ports are modbus masters and the terminal acts as a modbus slave.
A connection between an OTA port and internal registers is configured using a row in the form. The connection is enabled using the first check box.
| Protocol | Select the TCP choice for Modbus via TCP or the MTCP choice for Modbus TCP. |
| OTA Port | Over-the-air port number in the range 1 to 3. |
| RTU ID | Modbus address in the range 1..247. |
This is only available for the SAT130 since that type of terminal has ethernet, wifi, and direct cell. All of these are considered local ethernet here. Direct cell means the path from the SAT130 to the web that bypasses the SatSCADA server.
A connection between a local Ethernet port and internal registers is configured using a row in the form. The connection is enabled using the first check box.
| Protocol | Select the TCP choice for Modbus via TCP or the MTCP choice for Modbus TCP. |
| IP Port | IP port number in the range 501 to 503. |
| RTU ID | Modbus address in the range 1..247. |
| Delay | Time to wait until the next poll (.1 sec units). |
The example in this figure shows many OTA masters (either satellite or cell) accessing the internal registers. The RTU ID on the form is set to 1 and enabled using the check boxes.
The example in this figure has one local ethernet master (connected via LAN cable to SAT130) accessing the internal registers. The RTU ID on the form is set to 1 and enabled using the check boxes.
.