A well-trained workforce is critical to the success of your operation. Knowing how to correctly install, configure,
program, calibrate, and trouble-shoot your Emerson equipment provides your engineers and technicians with the
skills and confidence to optimize your investment. Remote Automation Solutions offers a variety of ways for your
personnel to acquire essential system expertise. Our full-time professional instructors can conduct classroom
training at several of our corporate offices, at your site, or even at your regional Emerson office. You can also receive
the same quality training via our live, interactive Emerson Virtual Classroom and save on travel costs. For our
complete schedule and further information, contact the Remote Automation Solutions Training Department at
800-338-8158 or email us at education@emerson.com.
2.3 Serial ..................................................................................................................................................... 1
2.4 Types and Capabilities of Serial Ports ..................................................................................................... 2
8.6 Register: INT ....................................................................................................................................... 13
This document describes the Modbus communications protocol on the FloBoss S600+ flow
computer. The flow computer has 20 user definable communication tasks. Each of the links may be
individually configured.
2. Physical Transport of Data
2.1 TCP Socket
The TCP/IP stream socket supports both master and slave links.
If the unit is the slave on the link it creates a server socket and listens for clients to connect. The
TCP/IP address of the slave link is the TCP/IP address of the flow computer.
If the unit is the master on the link it acts as a client and attempts to connect to a remote server
machine. When you configure the data link, you specify the TCP/IP address of the slave with which
the master must communicate.
D301904X012
January 2021
The S600+ supports communication between networks using a gateway.
Other communication parameters are independent of the mode of data transfer. ASCII and RTU are
supported over stream sockets and the Modbus map is independent of the transport mechanism.
2.2 Modbus TCP
This protocol is based on the Modbus/TCP Specification. The connection mechanism is TCP/IP
which secures data transfer between any machines connected on a network. The Modbus protocol
is encapsulated into the TCP/IP frame.
The data transfer within the Modbus part of the protocol is standard Modbus. The only significant
difference is that the Modbus CRC is not use; . Instead the CRC used with the TCP/IP protocol is
used.
2.3 Serial
In serial mode the data links communicate over standard serial lines with these specifications:
Baud rates: 2400, 4800, 9600, 19200, 38400, and 57600
Data bits: 7 (ASCII, required for Modbus ASCII) and 8 (RTU, required for Modbus RTU).
Com. Port 1: Reserved for the front panel display and keypad.
Com. Port 2: Reserved for the Config600 interface (actually a Modbus slave link)
Com. Ports 3 and Port 4: Dedicated RS-232 with RTS-CST handshaking capabilities
Com. Ports 5, 6, and 7: RS-485/RS-232 capability. RTS line is controlled automatically by the
P152 module’s UART and rapid turnaround is possible on the 485 links.
Com. Port 8: Reserved for I/O board communications.
Com. Ports 9, 10, 11, and 12: Dedicated RS-485.
3. Network Interface
The S600+ includes two 10 or 100 MB/s, full-duplex Ethernet interfaces. The system firmware
provides a full TCP/IP stack implementation on this interface.
Standard supported features include:
Telnet
FTP
Socket-based Modbus communications
The S600+ supports two gateways, which are configured on NWTK1. The IP addresses of the two
network ports
Supported: 193.195.232.1 / 193.195.230.1
Not supported: 193.195.232.1 / 193.195.232.2
must differ in the third octet:
2
4. Modbus
Modbus is the standard interface to the S600+. The protocol is based on Gould/Modicon Modbus.
The Config600 configuration software interfaces to the S600+ using Modbus. The link uses the
special function code 65, with specially defined S600+ sub-functions to provide file transfer,
system edit commands, and other specialized functionality. The S600+ is the slave on this link.
4.1 Configuration
The system firmware supports up to 20 communications links. Links can have individual
configurations or can share common parameters or configuration.
Configuration has two parts:
Link Configuration
This step defines the data link’s port or socket, its master or slave status, and whether it uses
RTU or ASCII. You enter this information using Config600 when the link is initially assigned,
but the link configuration can be modified later if required.
Map Configuration
This step assigns database points and fields to Modbus coils, inputs, and registers using a
text file created using Config600’s map builder utilities. You can modify this map later if
required.
4.2 Master
In master mode, the device communicates with up to 10 slaves on a single-drop link. You can
configure several masters if necessary.
4.3 Slave
In slave mode, the device waits for polls from an external master and responds to polls are
requested. You can define several slaves if necessary. The slave address is configurable per link, so a
single S600+ can have several slave addresses if required.
The S600+ fully supports both RTU Modbus and ACSII Modbus. A single configuration switch
enables you to select one or the other. Other communication parameters exist independently of
the ASCII/RTU switch.
RTU Mode
In RTU mode, you must configure the link for 8 data bits. No message header or trailers are
included. The checksum is the 16-bit CRC specified in the -Modbus specification.
ASCII Mode
In ASCII mode, you would normally configure the link for 7 data bits, although the S600+ also
supports 8 data bits. The message starts with the ASCII Modbus start character (the colon, or
“:”). The checksum is the 8-bit LRC defined in the Modbus specification. The message
terminates with the ASCII Modbus trailer characters CR followed by LF.
Each of these functions is described in this section.
Note
These message formats exclude the message header (ASCII only), the CRC/LRC, and message trailer
(ASCII only), since these are specific to the data transfer mode.
6.1 Function 1: Read Output Status
Function Code 01 reads the output coils (00001–09999), reading up to 2040 coils per poll in nonextended mode.