User Tools

Site Tools


gui2:ipmux

IP Mux

The IP Mux mode is used to connect one or more Over-the-Air and local Ethernet source ports to a COM destination port and tags. The source ports use the Modbus via TCP protocol or the Modbus TCP protocol.

More than one destination port can be selected. Each selected destination port can be connected to one or more source ports.

The OTA and ethernet source ports are modbus masters and each selected COM destination port is a modbus slave. The modbus slave can also be connected to one or more modbus master serial ports using the Serial Mux mode.

If the source port and destination port use a different protocol then an automatic conversion will occur.

Over-the-Air

A connection between an OTA port and a COM port and internal registers is configured using a row in the form. The connection is enabled using the first check box. Access to the internal registers is enabled using the second check box.

Protocol Select the TCP choice for Modbus via TCP or the MTCP choice for Modbus TCP.
OTA Port Over-the-air source port number in the range 1 to 3.
COM Port COM destination port number in the range 0 to 4.
RTU ID Modbus address in the range 0 to 247. If 0 the message is broadcast.

Ethernet

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 or COM port is configured using a row in the form. The connection is enabled using the first check box. Access to tags is enabled using the second 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.
COM Port COM port number in the range 0 to 4.
RTU ID Modbus address in the range 0 to 247. If 0 the message is broadcast.
Delay Time to wait until the next poll (.1 sec units).

Example #1: Modbus OTA Masters

The example in this figure shows many OTA masters (either satellite or cell) connected to a serial slave. Configuration only requires use of the IP Mux form.

Example #2: Modbus OTA Masters and a Serial Master

The example in this figure shows many OTA masters and a serial master connected to a serial slave. Both the IP Mux form and the Serial Mux form are required for this configuration.

Example #3: Modbus OTA Masters with Modbus RTU

The example in this figure shows many OTA masters connected to a serial slave and accessing internal registers. Configuration only requires use of the IP Mux form. The RTU ID on the form is set to 2 and is enabled using the check boxes. Modbus request messages received by the terminal with an RTU ID that is not 2 are sent to the serial slave. If the RTU ID is 1 then the serial slave returns a response. Modbus request messages received by the terminal with an RTU ID that is 2 are used to access tags.

Example #4: Modbus OTA Masters and Ethernet Master

The example in this figure shows many OTA masters and one ethernet master connected to an RS-485 serial slave. Only the IP Mux form is required for this configuration.

.

gui2/ipmux.txt · Last modified: 2020/04/13 09:06 by dmeier