RemoteLog RTUs support a flexible suite of communications options in support of your open systems. Connect RemoteLogs as low cost Internet clients and avoid the expense of monitoring your own communications network. Alternatively, RemoteLog can be a slave in a traditional SCADA system or "report on exception" as a communications master.

Ethernet Port

The Ethernet port on a RemoteLog RTU will auto detect and respond to both SIXNET "I/O for Windows" and Open Modbus (Modbus/TCP) protocols. Messages from multiple computers can be received simultaneously in a mix of these two protocols.

RemoteLog supports DHCP. Consult SIXNET about advanced features such as proxy server functions.

Industrial Telephone Modem

The modem in a RemoteLog RTU is a fully featured equivalent of the SIXNET VT-MODEM-1WW. This industrial modem is certified for worldwide use and is PC and Windows compatible.

RS232 Port

The RS232 port on a RemoteLog RTU can be connected to cell phones, radios, and just about any modem required by your applications. The RS232 port can serve as either a slave (receive I/O commands) or master (send I/O commands). In slave mode, the RS232 port can be configured for either SIXNET "I/O for Windows", Modbus RTU, or Modbus ASCII protocol. In master mode, the RS232 port can be configured for SIXNET "I/O for Windows" protocol. (Please note that RS232 communications requires a single choice of mode and protocol. This choice is made in configuration software supplied with your RemoteLog RTU.)

RS485 Expansion Port

Use this port in a master mode to read/write one RS485 expansion module or Modbus device. If no expansion device is connected, then the port will operate in a slave mode, responding to SIXNET "I/O for Windows" or Modbus slave communications from an external device such as a computer. This port is not available for client transfer functions.

Selecting "I/O for Windows" or Modbus Protocol

Generally, "I/O for Windows" is the preferred protocol for SIXNET systems. In most cases it results in higher system performance and gives you the many benefits designed into SIXNET products, such as addressing I/O directly by tag name. Systems using "I/O for Windows" communications can be configured on-line (while live) and can be addressed by multiple masters simultaneously.

Modbus is a single master protocol (although Ethernet can extend this capability in some situations). Modbus is recommended when the SIXNET I/O will share a communications channel with existing Modbus devices or when the software in your master station can only talk Modbus protocol. This is generally the case with non-Windows legacy systems and Windows software with limited suites of supported I/O drivers.