Service manual

Appendix I Using MODBUS Protocol in CAS Profile 180
Cyclades-TS Installation & Service Manual
In this example, the Automation Application running in the Workstation (local or remote) controls the PLCs
connected to the serial port (RS-485) of the Cyclades-TS100 using MODBUS/TCP protocol. The connection is
opened using Cyclades-TS100 Ethernet IP address and TCP port = 502. Cyclades-TS100 accepts the incoming
connection and converts MODBUS/TCP ADUs (packets) to plain MODBUS frames and sends them over the
serial port. On the other hand, the MODBUS frames received from the serial port are converted to MODBUS/
TCP ADUs and sent through the TCP connection to the Automation Application.
The configuration described earlier for Console Access Servers (see Chapter 6) should be followed with the
following exceptions for this example:
Parameter Description Value for
This Example
all.authtype There are several authentication type options: local (authentication is
performed using the /etc/passwd file), radius (authentication is performed
using a Radius authentication server), TacacsPlus (authentication is
performed using a TacacsPlus authentication server), none, local/radius
(authentication is performed locally first, switching to Radius if
unsuccessful), radius/local (the opposite of the previous option),
RadiusDownLocal (local authentication is tried only when the Radius server
is down), local/TacacsPlus (authentication is performed locally first,
switching to TacacsPlus if unsuccessful), TacacsPlus/local (the opposite of
the previous option), TacacsPlusDownLocal (local authentication is tried
only when the TacacsPlus server is down). Note that this parameter
controls the authentication required by the Cyclades-TS. The authentication
required by the device to which the user is connecting is controlled
separately.
none
FIGURE I.2 - MODBUS PSLAVE.CONF PORT SPECIFIC PARAMETERS
(ONLY WHERE IT DIFFERS FROM THE STANDARD CAS PROFILE)