IB IL RS 485/422 ...
Inline terminal for serial data transmission
2 x
Firmware Version 1.20 or later
AUTOMATION
Data sheet
6878_en_04
1
© PHOENIX CONTACT - 03/2009
Description
The terminal is designed for use within an Inline station. It is
used to operate standard I/O devices with serial interfaces
on a bus system.
Features
–
–
–
–
–
–
–
A serial input and output channel (RS-485 or RS-422)
Various protocols supported
Transmission speed can be set up to 38,400 baud
Number of data bits, stop bits, and parity can be set
4 kbyte receive buffer and 1 kbyte transmit buffer
Parameterization and data exchange via the bus using
PCP services
Diagnostic and status indicators
This data sheet only is valid with the IL SYS INST UM E user manual (see "Ordering data" on page 4).
Make sure you always use the latest documentation.
It can be downloaded at www.phoenixcontact.net/download.
This data sheet is valid for all products listed on the following page:
6 1 9 9 A 0 0 2
IB IL RS 485/422 ...
Table of contents
1
Description.................................................................................................................................. 1
2
Ordering data ........................................................................................................................... 4
3
Technical data ............................................................................................................................ 4
4
Internal basic circuit diagram ...................................................................................................... 7
5
Diagnostic and status indicators and terminal point assignment................................................. 8
5.1
5.2
5.3
5.4
Local diagnostic and status indicators............................................................................................................ 8
Function identification..................................................................................................................................... 8
Terminal point assignment in half duplex mode (RS-485) .............................................................................. 8
Terminal point assignment in full duplex mode (RS-422) ............................................................................... 8
6
Installation instructions ............................................................................................................... 9
7
Serial interface............................................................................................................................ 9
7.1
7.2
8
Connection notes........................................................................................................................ 9
8.1
8.2
9
RS-485 ........................................................................................................................................................... 9
RS-422 ........................................................................................................................................................... 9
Capacitor between shield and FE................................................................................................................... 9
Shield connected directly to FE .................................................................................................................... 10
Connection examples ................................................................................................................10
9.1
9.2
9.3
9.4
9.5
9.6
Comparison of the wiring examples in Figure 5 to Figure 9 .......................................................................... 10
RS-485: IB IL RS 485/422 terminal as the end point of a network ................................................................ 11
RS-485: IB IL RS 485/422 terminal in the center of a network ...................................................................... 11
RS-485: IB IL RS 485/422 terminal as the end point of a network ................................................................ 12
RS-422: Shield connected using a capacitor to the IB IL RS 485/422 terminal............................................. 12
RS-422: Shield connected directly to the IB IL RS 485/422 terminal ............................................................ 13
10 Programming data/configuration data........................................................................................14
10.1
10.2
Local bus (INTERBUS)................................................................................................................................. 14
Other bus systems ....................................................................................................................................... 14
11 Data storage and
transmission .......................................................................................................................................................... 14
11.1
11.2
11.3
11.4
11.5
11.6
11.7
11.8
11.9
6878_en_04
Overview of supported protocols .................................................................................................................. 14
Transparent protocol .................................................................................................................................... 15
End-to-end protocol...................................................................................................................................... 15
Dual buffer protocol ...................................................................................................................................... 15
3964R protocol............................................................................................................................................. 15
XON/XOFF protocol ..................................................................................................................................... 16
Modbus RTU (Remote Terminal Unit) .......................................................................................................... 16
Modbus ASCII .............................................................................................................................................. 16
Time monitoring for Modbus......................................................................................................................... 16
PHOENIX CONTACT
2
IB IL RS 485/422 ...
12 PCP communication ..................................................................................................................17
12.1
12.2
12.3
Object dictionary .......................................................................................................................................... 17
Object description ........................................................................................................................................ 17
Error messages in PCP mode ...................................................................................................................... 24
13 Process data..............................................................................................................................25
13.1
13.2
13.3
13.4
6878_en_04
Assignment of the process data output word (~control word)....................................................................... 25
Format of the process data output word (~control word) .............................................................................. 25
Assignment of the process data input word (~status word) .......................................................................... 26
Format of the process data input word (~status word).................................................................................. 27
PHOENIX CONTACT
3
IB IL RS 485/422 ...
2
Ordering data
Products
Description
Type
Order No.
Pcs./Pkt.
Inline terminal for serial data transmission;
transmission speed of 500 kbps;
including connectors and labeling fields
IB IL RS 485/422-PAC
2861933
1
Inline terminal for serial data transmission;
transmission speed of 500 kbps;
without accessories
IB IL RS 485/422
2836793
1
Inline terminal for serial data transmission;
transmission speed of 2 Mbps;
including connectors and labeling fields
IB IL RS 485/422-2MBD-PAC
2862097
1
Inline terminal for serial data transmission;
transmission speed of 2 Mbps;
without accessories
IB IL RS 485/422-2MBD
2855839
1
The connector set listed below is needed for the complete fitting of the IB IL RS 485/422 and IB IL RS 485/422-2MBD terminals.
Accessories
Description
Type
Order No.
Pcs./Pkt.
Connector set with a standard connector and a shield connector
IB IL AO/CNT-PLSET
2732664
1
Documentation
Description
Type
Order No.
Pcs./Pkt.
"Automation terminals of the Inline product range"
user manual
IL SYS INST UM E
2698737
1
"INTERBUS addressing"
data sheet
DB GB IBS SYS ADDRESS
9000990
1
"Peripherals Communication Protocol (PCP)"
user manual
IBS SYS PCP G4 UM E
2745169
1
3
Technical data
General data
Housing dimensions (width x height x depth)
24.4 mm x 120 mm x 72 mm (with connectors)
Weight
90 g (without connectors), 135 g (with connectors)
Operating mode
Process data mode with 1 word
PCP mode with 2 words
Transmission speed
IB IL RS 485/422-PAC
500 kbps
IB IL RS 485/422
500 kbps
IB IL RS 485/422-2MBD-PAC
2 Mbps
IB IL RS 485/422-2MBD
2 Mbps
Permissible temperature (operation)
-25°C to +55°C
Permissible temperature (storage/transport)
-25°C to +85°C
Permissible humidity (operation/storage/transport)
75% to 85% according to DIN EN 61131-2
Permissible air pressure (operation)
80 kPa to 106 kPa (up to 2000 m above sea level)
Permissible air pressure (storage/transport)
70 kPa to 106 kPa (up to 3000 m above sea level)
Degree of protection
IP20 according to IEC 60529
Protection class
Class 3 according to EN 61131-2, IEC 61131-2
Connection data for Inline connectors
Connection method
Spring-cage terminals
Conductor cross-section
0.08 mm2 to 1.5 mm2 (solid or stranded), 28 - 16 AWG
6878_en_04
PHOENIX CONTACT
4
IB IL RS 485/422 ...
Interfaces
Bus
Local bus
Through data routing
Serial interfaces
Type
RS-485 half duplex or RS-422 full duplex
Cannot be operated simultaneously
Electrical data according to EIA (RS) 485, EIA (RS) 422, CCITT V.11
Cable termination resistance
120 Ω, typical
Permissible input differential voltage
±5.7 V, maximum
Owing to the 120 Ω termination resistor, the input differential voltage is limited to ±5.7 V.
Hysteresis
50 mV, typical
Input sensitivity
-0.2 V, minimum; +0.2 V, maximum
Output differential voltage (with 100 Ω load)
±2.0 V, minimum
Output differential voltage (with 54 Ω load)
±1.5 V, minimum
Short-circuit output current
±80 mA, typical
Power consumption
500 kbps
Communications power UL
7.5 V
7.5 V
Current consumption at UL
170 mA, typical; 260 mA, maximum*
185 mA, typical; 260 mA, maximum*
Total power consumption
Approximately 1.275 W, typical;
1.950 W, maximum*
Approximately 1.388 W, typical;
1.950 W, maximum*
2 Mbps
* All serial interface connections short circuited.
NOTE: Damage to the device
A continuous short circuit can damage the device.
This terminal takes no current from potential jumpers UM and US.
Supply of the module electronics through the bus coupler
Connection method
Potential routing
Power dissipation
500 kbps
Power dissipation of the electronics PTOT
PTOT = 1.2 W
PTOT = 1.4 W
Power dissipation of the housing PHOU
1.2 W, maximum*
1.4 W, maximum*
2 Mbps
* Within the permissible operating temperature
Limitation of simultaneity, derating
TA ≤ 50°C
TA > 50°C
500 kbps
2 Mbps
No limitation of simultaneity, no
derating
No limitation of simultaneity, no
derating
No limitation of simultaneity, no
derating
IQ = 4 A
IQ: Total diagonal
routing current IM/IS/GND
Safety equipment
None
6878_en_04
PHOENIX CONTACT
5
IB IL RS 485/422 ...
Electrical isolation/isolation of the voltage areas
The electrical isolation of the logic level from the serial interface is ensured by the DC/DC converter.
Common potentials
The serial interface control and data cables have the same potential. FE is a separate potential area.
Separate potentials in the system consisting of bus coupler/power terminal and I/O terminal
- Test distance
- Test voltage
5 V supply incoming remote bus/7.5 V supply (bus logic)
500 V AC, 50 Hz, 1 min.
5 V supply outgoing remote bus/7.5 V supply (bus logic)
500 V AC, 50 Hz, 1 min.
RS-485/422 interface/7.5 V supply (bus logic)
500 V AC, 50 Hz, 1 min.
RS-485/422 interface/24 V supply (I/O)
500 V AC, 50 Hz, 1 min.
RS-485/422 interface/functional earth ground
500 V AC, 50 Hz, 1 min.
7.5 V supply (bus logic)/24 V supply (I/O)
500 V AC, 50 Hz, 1 min.
7.5 V supply (bus logic)/functional earth ground
500 V AC, 50 Hz, 1 min.
24 V supply (I/O)/functional earth ground
500 V AC, 50 Hz, 1 min.
Error messages to the higher-level control or computer system
None
Approvals
For the latest approvals, please visit www.phoenixcontact.net/catalog.
6878_en_04
PHOENIX CONTACT
6
IB IL RS 485/422 ...
4
Internal basic circuit diagram
L o c a l b u s
U
U
U
O P C
D
L +
A N A
L -
2 4 V
R x D
5 V
T R
T x D
5 V
5 V
1
µ P
R S -4 8 5 /4 2 2
In te rfa c e
/
T x D +
+ 2 4 V (U S )
/
T x D -
1
R x D +
R x D -
R +
R -
+ 2 4 V (U M )
6 1 9 9 D 0 0 4
Figure 1
Internal wiring of the terminal points
Key:
Protocol chip (bus logic including voltage
conditioning)
Optocoupler
OPC
Diagnostic and status indicators with function
information
DC/DC converter with electrical isolation
x x x
X X X
R S -4 8 5 /4 2 2
In te rfa c e
Microprocessor
µ P
/
Capacitor
RS-485/422 interface
/
Resistor
Ground, electrically isolated from ground of the
communications power UL
1
Other symbols used are explained in the
IL SYS INST UM E user manual.
6878_en_04
PHOENIX CONTACT
7
IB IL RS 485/422 ...
5
Diagnostic and status indicators
and terminal point assignment
5.3
Terminal point assignment in half duplex mode
(RS-485)
Connector Terminal Signal
point
1
1.4, 2.4 FE
D
T R
R x D
T x D
R S 4 8 5 /4 2 2
2
2
1
1
2
1 .1
1
1
2 .1
1 .2
2
2
2 .2
1 .3
3
3
2 .3
1 .4
4
4
2 .4
6 1 9 9 0 0 0 3
Figure 2
5.1
Local diagnostic and status indicators
Des.
Color
D
Green
TR
Green
Serial interface:
RxD
Yellow
TxD
5.2
Yellow
2
Terminal is receiving data from the
connected device
Terminal is transmitting data to the
connected device
Orange
2 Mbps: White stripe in the vicinity of the D LED
Terminal point assignment in full duplex mode
(RS-422)
Connector Terminal Signal
point
1
1.4, 2.4 FE
Meaning
Diagnostics
PCP active
Function identification
6878_en_04
5.4
Diagnostic and status indicators and terminal
point assignment
Assignment Data
direction
Functional
earth ground
All other terminal points of this
connector are not used.
1.1
TxD+
Reserved
2.1
TxDReserved
1.2
RxD+
Receive/
Input/
transmit data output
(positive)
2.2
RxDReceive/
Input/
transmit data output
(negative)
1.3
R+
Termination
resistor
(positive)
2.3
RTermination
resistor
(negative)
1.4, 2.4 Shield Shield
connection
Assignment Data
direction
Functional
earth ground
All other terminal points of this
connector are not used.
1.1
TxD+
Transmit data Output
(positive)
2.1
TxDTransmit data Output
(negative)
1.2
RxD+
Receive data Input
(positive)
2.2
RxDReceive data Input
(negative)
1.3
R+
Termination
resistor
(positive)
2.3
RTermination
resistor
(negative)
1.4, 2.4 Shield Shield
connection
PHOENIX CONTACT
8
IB IL RS 485/422 ...
6
Installation instructions
8
Connection notes
Please observe the "Connection notes" on
page 9.
7
By assigning terminal points 1.4 and 2.4 of both
connectors, you can connect the cable shield
either using a capacitor (connector 2) or directly
(connector 1) to functional earth ground (FE).
Serial interface
With the two connection options, you can connect
one side of the cable shield directly and one side
using a capacitor to FE without any additional
effort. In this way, you can prevent ground loops,
which can occur if a shield is connected directly to
FE on both sides.
The IB IL RS 485/422 terminal has one RS-485 and one
RS-422 interface. The interfaces cannot be operated
simultaneously.
7.1
RS-485
In RS-485 mode, an RS-485 network with multiple devices
can be created.
Regardless of the side to which the shield is
connected, all wires must be wired to
connector 2.
Use a twisted pair, common shielded data cable to connect
the devices. Fit this data cable with a termination resistor at
the two furthest points of the RS-485 network. For connection
to the Inline terminal, use the termination resistor installed in
the device (see Figure 1).
Use at least one connector with shield connection
when connecting the I/O device.
8.1
Capacitor between shield and FE
Connection examples are shown in Figure 5 to Figure 7 on
page 11 to page 12.
This operating mode supports half duplex transmission.
Make sure that only one device is transmitting data at a time.
To ensure a defined idle cable state, data cable polarization
is included in the IB IL RS 485/422 terminal.
7.2
RS-422
In RS-422 mode, a point-to-point connection can be
established.
Use a twisted pair, common shielded data cable to connect
the devices. Fit this data cable with a termination resistor at
each device. For connection to the Inline terminal, use the
termination resistor installed in the device (see Figure 1).
Connection examples are shown in Figure 8 on page 12 and
Figure 9 on page 13.
This operating mode supports full duplex transmission.
6878_en_04
6 8 7 8 B 0 0 5
Figure 3
Position of the shield connector to connect the
shield to FE using a capacitor
PHOENIX CONTACT
9
IB IL RS 485/422 ...
8.2
Shield connected directly to FE
6 8 7 8 B 0 0 6
Figure 4
Position of the shield connector to connect the
shield directly to FE
9
Connection examples
9.1
Comparison of the wiring examples in Figure 5 to Figure 9
Operating
mode
Special feature
Shield
connection
Remark
RS-485
IB IL RS 485/422 as the
end point of a network
IB IL RS 485/422 in the
center of a network
IB IL RS 485/422 as the
end point of a network
Shield connected using a
capacitor
Shield connected directly
Capacitive
Termination resistor
required
–
RS-485
RS-485
RS-422
RS-422
Capacitive/
direct
Direct
Capacitive
Direct
Termination resistor
required
Termination resistor
required
Termination resistor
required
Connectors
required per
IB IL RS 485/422
Connector set
Example in
2 shield connectors
Figure 6
Connector set
Figure 7
Connector set
Figure 8
Connector set
Figure 9
Figure 5
The connector set consists of a shield connector
and a standard connector.
When wiring, please observe the following notes:
–
–
–
Always connect the shield between two devices on one
side using a capacitor and on the other side directly to
FE.
An RS-485 network must be equipped with a
termination resistor at both ends.
For an RS-422 point-to-point connection, the receive
signals on every device must have a termination
resistor.
6878_en_04
PHOENIX CONTACT
10
IB IL RS 485/422 ...
9.2
RS-485: IB IL RS 485/422 terminal as the end point of a network
Connect the shield to FE using a capacitor.
Connector
Transmit/receive data (positive)
Transmit/receive data (negative)
Connection of termination resistor via
R+ and RInline connector
(connector 2)
Figure 5
9.3
RS-485 interface wiring: IB IL RS 485/422 as the end point of a network,
capacitor between data cable shield and FE
RS-485: IB IL RS 485/422 terminal in the center of a network
Connector
Transmit/
receive data
(positive)
Transmit/
receive data
(negative)
Inline connector
(connector 2)
Figure 6
6878_en_04
RS-485 interface wiring: IB IL RS 485/422 in the center of a network, data cable shield connected directly and
using a capacitor to FE
PHOENIX CONTACT
11
IB IL RS 485/422 ...
9.4
RS-485: IB IL RS 485/422 terminal as the end point of a network
Connect the shield directly to FE.
Connector
Transmit/receive data (positive)
Transmit/receive data (negative)
Connection of termination resistor via
R+ and RInline connector
(connector 2)
Figure 7
9.5
RS-485 interface wiring: IB IL RS 485/422 as the end point of a network, data cable shield connected directly
to FE
RS-422: Shield connected using a capacitor to the IB IL RS 485/422 terminal
Connector
RS-422 device
Transmit data (positive)
Receive data (positive)
Transmit data (negative)
Receive data (negative)
Receive data (positive)
Transmit data (positive)
Receive data (negative)
Transmit data (negative)
Connection of termination
resistor via R+ and R-
Connection of
termination resistor
Inline connector
(connector 2)
Figure 8
6878_en_04
RS-422 interface wiring: Data cable shield connected using a capacitor to FE
PHOENIX CONTACT
12
IB IL RS 485/422 ...
9.6
RS-422: Shield connected directly to the IB IL RS 485/422 terminal
Connector
RS-422 device
Inline connector
(connector 2)
Figure 9
6878_en_04
Transmit data (positive)
Receive data (positive)
Transmit data (negative)
Receive data (negative)
Receive data (positive)
Transmit data (positive)
Receive data (negative)
Transmit data (negative)
Connection of
termination resistor via
R+ and R-
Connection of
termination resistor
RS-422 interface wiring: Data cable shield connected directly to FE
PHOENIX CONTACT
13
IB IL RS 485/422 ...
10
Programming data/configuration
data
11
10.1
Local bus (INTERBUS)
The terminal stores the received serial data in an
intermediate buffer until it is requested by the bus controller
board or the device at the serial interface. Serial data traffic
can be managed using various protocols. The protocol used
depends on the type of protocol supported by the peer.
ID code
Length code
Process data channel
Input address area
Output address area
Parameter channel (PCP)
Register length (bus)
10.2
DChex (220dec)
01hex
16 bits
2 bytes
2 bytes
4 bytes
6 bytes
11.1
Data storage and
transmission
Overview of supported protocols
Protocol
Receive
memory
Other bus systems
For the programming data of other bus systems,
please refer to the corresponding electronic
device data sheet, e.g., GSD, EDS.
6878_en_04
Transparent 4096 bytes
End-to-end 25 buffers
with 58 bytes
each
Dual buffer
2 buffers with
58 bytes
each
3964R
25 buffers
with 58 bytes
each
XON/XOFF
4096 bytes
Modbus
RTU
25 buffers
with 58 bytes
each
Modbus
ASCII
25 buffers
with 58 bytes
each
Transmit
memory
Special
features
when
receiving
1023 bytes
1023 bytes
Two end
(including end characters
characters)
are filtered
out
1023 bytes
Only stores
(including end the most
characters)
recently
received
data, end
characters
are filtered
out
15 buffers with Data
58 bytes each exchange
with software
handshake,
time
monitoring,
and
checksum
1023 bytes
Software
handshake
15 buffers with Time
58 bytes each monitoring
and
checksum
15 buffers with Time
58 bytes each monitoring
and
checksum
PHOENIX CONTACT
14
IB IL RS 485/422 ...
11.2
Transparent protocol
If the transparent protocol is used, serial data is forwarded
by the terminal in the same format it was received from the
serial interface or the bus side.
The transmit FIFO (First In, First Out memory) can store
1023 bytes (1 kbyte) and the receive FIFO can store
4096 bytes (4 kbytes). If the terminal receives another
character after the 4095th character, the error pattern is
stored in the receive FIFO. All subsequent characters are
ignored.
11.3
End-to-end protocol
The serial data is conditioned for the end-to-end protocol.
If serial data is sent from the bus side, two additional
characters, the first and second delimiters, are attached for
transmission to the serial interface. The first and second
delimiters are defined when the terminal is configured using
the INIT-TABLE object.
complete once both delimiters have been detected, one
after the other. It can then be read from the bus side.
If the buffer size of 58 bytes is exceeded without the two end
characters (delimiters) being detected, the buffer is
overwritten again. Depending on the INIT-TABLE object,
subindex 0Chex (rotation switch), there are two variants.
Variant 1 (0Chex = 0): Only the new data is available in the
overwritten buffer, i.e., any existing data from the previous
cycle is rejected (no rotation).
Variant 2 (0Chex = 1): The buffer is re-written character by
character. If the two delimiters are detected, the new
characters and the remaining characters from the previous
cycle are available in the overwritten buffer (rotation).
The same conditions as in the end-to-end protocol apply to
sending serial data. If serial data is sent from the bus side,
two additional characters, the first and second delimiters,
are attached for transmission to the serial interface.
11.5
Serial data sent from the serial interface can only be read by
the user if the terminal has received the first and second
delimiters. The two delimiters confirm that the serial data
has been received without error and the maximum data
length of 58 bytes has been observed. The delimiters are
filtered out when the data is read by the bus side.
Unlike in the transparent protocol, the receive memory is not
organized as a FIFO but as a buffer. 25 buffers of 58 bytes
each are available. If the buffer size of 58 bytes is exceeded
without the two delimiters being detected, the buffer is
overwritten again. Depending on the INIT-TABLE object,
subindex 0Chex (rotation switch), there are two variants.
Variant 1 (0Chex = 0; default setting):
Only the new data is available in the overwritten buffer, i.e.,
any existing data from the previous cycle is rejected
(no rotation).
3964R protocol
This protocol, developed by Siemens, is the most complex.
It uses start and end identifiers, a checksum, and time
monitoring.
15 buffers are available for transmitting and 25 buffers are
available for receiving.
Character delay time:
Acknowledgment delay time:
Block waiting time:
Number of attempts to establish a connection:
220
ms
2s
10 s
6
The optional 3964 priority defines which device may send
first (high priority) if there is an initialization conflict (several
devices attempting to send data simultaneously).
Variant 2 (0Chex = 1): The buffer is re-written character by
character. If the two delimiters are detected, the new
characters and the remaining characters from the previous
cycle are available in the overwritten buffer (rotation).
The transmit FIFO is 1023 bytes in size. The delimiters are
attached to, and stored with, the data to be sent.
11.4
Dual buffer protocol
With this protocol, the last received data block is stored.
A data block is defined as a sequence of characters with the
first and second delimiter, as in the end-to-end protocol.
As soon as a new data block is received, the previous one is
overwritten. This is achieved using two buffers, which are
written to alternately. This means that one buffer will always
be available to receive serial data, while the other stores the
last received data block. A data block is only regarded as
6878_en_04
PHOENIX CONTACT
15
IB IL RS 485/422 ...
11.6
XON/XOFF protocol
11.8
This protocol operates in the same way as the transparent
protocol, but uses a software handshake.
Data transmission with this protocol is controlled by the
XON and XOFF characters. XON is preset to 11hex and
XOFF to 13hex. These characters can also be defined when
the terminal is configured using the INIT-TABLE object.
If the terminal receives an XOFF, no more serial data will be
sent until an XON is received.
The terminal itself transmits an XOFF if the available space
in the receive memory is less than 5 bytes. As soon as more
memory becomes available again, the terminal transmits a
single XON.
Modbus ASCII
Telegram structure in ASCII mode:
Start
Address Function Data
CRC
End
check
1 ASCII 2 ASCII 2 ASCII 2 x (0 ... 56) 2 ASCII 2 ASCII
character characters characters ASCII
characters characters
(:)
characters
(CR, LF)
In Modbus ASCII mode, each hex value is converted into
two ASCII characters. In this way, the data throughput is
halved compared to RTU mode.
Example: The number 5Bhex is split into ASCII characters
5 and B. The corresponding ASCII codes are 35hex (5)
and 42hex (B).
Serial data is not filtered when it is transmitted. So any
characters that occur with the code defined for XON and
XOFF are sent and may trigger undesirable events at the
receiver. When serial data is received, the XON and XOFF
characters are filtered and are not available as data. Any
characters with the XON or XOFF code are lost. Ensure that
characters with these codes do not appear in the data
stream.
Both end characters can be modified using the first delimiter
and second delimiter entries in the INIT-TABLE object.
11.7
The broadcast telegram is an exception where no slave
responds and thus the response timeout is not maintained.
Instead, the turnaround delay of 200 ms is observed. The
next telegram may not be sent until this time has elapsed.
Modbus RTU (Remote Terminal Unit)
Telegram structure in RTU mode:
Address
Function
Data
1 byte
1 byte
0 ... 56
bytes
CRC
check
2 bytes
(EXOR)
11.9
Time monitoring for Modbus
Time monitoring is valid for Modbus RTU as well as for
Modbus ASCII. After a telegram is sent, a response is
expected within the response time of 2.5 s. After a timeout,
the transmit error bit is set in the process data.
A frame (telegram) is finished if there is a break in
transmission of at least 3.5 characters (referred to as t3.5).
If there is a break in frame transmission of more than
1.5 characters (referred to as t1.5), the message is
considered incomplete and is thus rejected.
In the Modbus environment, two timeouts are always
required: t1.5 and t3.5. For baud rates above 19,200 baud,
the timeouts are specified as t1.5 = 1.5 ms and
t3.5 = 3.0 ms.
6878_en_04
PHOENIX CONTACT
16
IB IL RS 485/422 ...
12
PCP communication
The IBS CMD (for standard controller boards)
and PC WorX (for Field Controllers (FC) and
Remote Field Controllers (RFC)) programs are
available for the configuration and
parameterization of your INTERBUS system.
For information about PCP communication, please
refer to the IBS SYS PCP G4 UM E user manual.
By default upon delivery, the terminal is configured for data
transmission according to the parameters on page 22. You
can configure the terminal to meet the requirements of your
application.
The terminal is configured in PCP mode using the INIT-TABLE
object.
12.1
Data type
Var of unsigned 8
String var of octet string
Array of unsigned 8
Number of elements
Length of an element in bytes
12.2
Parameter records or text strings are transmitted to or from
a connected I/O device in PCP mode using the SERIALDATA object.
Object dictionary
Index
5FC1hex
5FE0hex
5FFFhex
N:
L:
For additional information, please refer to the
"IBS CMD SWT G4 UM E" user manual and the
Quick Start Guide for your version of PC WorX.
rd:
wr:
N
1
1
20
L
1
58
1
Meaning
Module start indicator
Send/receive serial data
IB IL RS 485/422 terminal
configuration
Object name
START-IND
SERIAL-DATA
INIT-TABLE
Rights
rd/wr
rd/wr
rd/wr
Read access permitted
Write access permitted
Object description
Object description:
START-IND object
The object indicates whether or not the terminal was
restarted.
Following a power up, the byte will always have a value of
01hex. For a restart to be detected, the byte must be set
to 00hex by the application. If it is then set to 01hex again by
the terminal, this indicates that the terminal has been
restarted.
Object
Access
Data type
Index
Subindex
Length
(bytes)
Data
START-IND
Read, write
Var of unsigned 8
5FC1hex
00hex
01hex
1 byte
Module start indicator
The object is of no significance to the function of
the terminal.
Index
5FC1hex
5FE0hex
5FFFhex
6878_en_04
Data type
Var of unsigned 8
String var of octet string
Array of unsigned 8
N
1
1
20
L
1
58
1
Meaning
Module start indicator
Send/receive serial data
IB IL RS 485/422 terminal
configuration
Object name
START-IND
SERIAL-DATA
INIT-TABLE
Rights
rd/wr
rd/wr
rd/wr
PHOENIX CONTACT
17
IB IL RS 485/422 ...
Value range of the object:
Module start indicator
Code
Meaning
Representation in
CMD/PC WorX
00hex
Reset power up
Reset power up
message
message
01hex Power up was carried out Power up completed
Here, the parameters are:
Error_Class:
Error_Code:
Additional_Code:
Meaning:
8
0
0022hex
No character of the serial data will be
accepted from this service.
A write service without user data (length = 0) will be
answered with a negative confirmation.
If you set the object to 01hex, it has no effect on
the function of the terminal.
A power up cannot be triggered in this way.
However, it is then not possible to detect a
terminal restart.
Here, the parameters are:
Error_Class:
Error_Code:
Additional_Code:
Meaning:
8
0
0030hex
Value is out of range
SERIAL-DATA object
This object is used to send and receive serial data.
Object description:
Object
Access
Data type
Index
Subindex
Length
(bytes)
Data
SERIAL-DATA
Read, write
String var of octet string
1 x 58 bytes
5FE0hex
00hex (Only access to all data possible)
00hex
:
3Ahex
00hex Amount of data in the buffer
:
:
3Ahex Maximum length of the object
Send/receive serial data
If no serial data is available on a read access, a read
response (read service response) is generated with the
result (+) and length of 0.
With a protocol data unit (PDU) size of 64 bytes, a maximum
of 58 characters can be transmitted.
The length of the read or write service depends on the
number of characters to be transmitted. If, for example,
20 characters are to be read, the read response is 24 bytes
long (20 bytes of data + 4-byte PCP overhead).
Error messages for the SERIAL-DATA object:
If, during a write service, there is not enough transmit
memory available for serial data, the service will be
answered with a negative confirmation.
6878_en_04
PHOENIX CONTACT
18
IB IL RS 485/422 ...
Mapping a write request to the Modbus telegrams:
A
B
PCP Write Request
Para Count
0020
Invoke ID Comm.Ref
00 CR
Modbus RTU Telegram
Modbus ASCII Telegram
Address field (1 byte)
Address field (2 ASCII; 1 byte)
Function code (1 byte)
Function code (2 ASCII; 1 byte)
Data
(0...56 byte)
Data
(0...112 ASCII; 0...56 byte)
CRC (2 byte)
CRC (2 ASCII)
5FE0
Index
Length
D
0082
Command Code
Subindex
C
00 3A
Data
(0...58 byte)
Data
Start (3Ahex)
End (0D0Ahex)
Figure 10
6199A014
Write request
Key:
A General representation of a write request
B Mapped example call for 58 bytes of data
C Transmitted data for Modbus RTU
Data transmitted using the service is indicated by the
color background and bold outline.
CRC is only added to the Modbus device.
D Transmitted data for Modbus ASCII
Data transmitted using the service is indicated by the
color background and bold outline.
Start, CRC, and End are only added to the Modbus
device.
A read response service is mapped accordingly.
6878_en_04
PHOENIX CONTACT
19
IB IL RS 485/422 ...
INIT-TABLE object
The terminal is configured by writing the INIT-TABLE object using a write service.
Object description:
Object
Access
Data type
Index
Subindex
Length (bytes)
Data
6878_en_04
INIT-TABLE
Read, write
Array of unsigned 8
5FFFhex
00hex
Write all elements
01hex
Protocol
02hex
Baud rate
03hex
Data width
04hex
Reserved
05hex
Reserved
06hex
Error pattern
07hex
First delimiter
08hex
Second delimiter
09hex
3964R priority
0Ahex
Output type
0Bhex
Reserved
0Chex
Rotation switch
0Dhex
XON pattern
0Ehex
XOFF pattern
0Fhex
Baud rate direct
10hex
Basic baud rate direct
11hex
Reserved
:
:
14hex
Reserved
14hex subindex 00hex
01hex subindex 01hex to 14hex
IB IL RS 485/422 terminal configuration
20 x 1 byte
PHOENIX CONTACT
20
IB IL RS 485/422 ...
INIT-TABLE object elements:
Element
dec
hex
1
1
2
2
Meaning
Protocol
Baud rate
Code
00hex
07hex
3
3
Data width
02hex
4
5
6
7
8
9
10
11
12
13
14
15
16
17 - 20
4
5
6
7
8
9
A
B
C
D
E
F
10
11 - 14
Reserved
Reserved
Error pattern
First delimiter
Second delimiter
3964R priority
Output type
Reserved
Rotation switch
XON pattern
XOFF pattern
Baud rate direct
Basic baud rate direct
Reserved
00hex
00hex
24hex
0Dhex
0Ahex
00hex
01hex
00hex
00hex
11hex
13hex
00hex
00hex
00hex
Default setting
Meaning
Transparent
9600 baud
8 data bits, even parity,
1 stop bit
Data type
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
Unsigned 8
($)
Carriage return (CR)
Line feed (LF)
Low
RS-485
No rotation
Set all reserved elements to 00hex.
Element value range:
The options in bold are default settings.
Protocol
Representation in
CMD/PC WorX
Code
Meaning
00hex
01hex
02hex
03hex
04hex
05hex
06hex
Transparent
End-to-end
Dual buffer
3964R
XON/XOFF
Modbus RTU
Modbus ASCII
6878_en_04
Transparent
End-End
Dual buffer
3964R
XON/XOFF
Modbus RTU
Modbus ASCII
Code
00hex
01hex
02hex
03hex
04hex
05hex
06hex
07hex
08hex
09hex
FFhex
Baud rate
Value
110
300
600
1200
1800
2400
4800
9600
19200
38400
Direct
PHOENIX CONTACT
21
IB IL RS 485/422 ...
Data width
Code
00hex
01hex
02hex
03hex
04hex
05hex
06hex
07hex
08hex
09hex
0Ahex
0Bhex
Data bits
7
7
8
8
8
7
7
7
8
8
8
7
Meaning
Parity
Even
Odd
Even
Odd
None
None
Even
Odd
Even
Odd
None
None
Code
24hex
xxhex
Error pattern
Meaning
$
Any character
Code
0Dhex
xxhex
First delimiter
Meaning
Carriage return (CR)
Any character
Code
0Ahex
xxhex
Code
00hex
01hex
Code
00hex
01hex
02hex
Representation in CMD/PC WorX
Stop bits
1
1
1
1
1
1
2
2
2
2
2
2
Second delimiter
Meaning
Line feed (LF)
Any character
3964R priority
Meaning
Representation in
CMD/PC WorX
Low priority
Low priority
High priority
High priority
Output type
Meaning
Invalid
RS-485
RS-422
If the baud rate contains the value FFhex, direct baud rate
programming is selected. Thus the baud rate can be freely
6878_en_04
7 data bits, even parity, 1 stop bit
7 data bits, odd parity, 1 stop bit
8 data bits, even parity, 1 stop bit
8 data bits, odd parity, 1 stop bit
8 data bits, without parity, 1 stop bit
7 data bits, without parity, 1 stop bit
7 data bits, even parity, 2 stop bits
7 data bits, odd parity, 2 stop bits
8 data bits, even parity, 2 stop bits
8 data bits, odd parity, 2 stop bits
8 data bits, without parity, 2 stop bits
7 data bits, without parity, 2 stop bits
Code
00hex
01hex
Code
11hex
xxhex
Code
00hex
xxhex
Code
13hex
xxhex
Code
00hex
01hex
02hex
Rotation switch
Meaning
Representation in
CMD/PC WorX
No rotation
No rotation
Rotation
Rotation
XON pattern
Meaning
Any character
(not the same as XOFF pattern)
Baud rate direct
Meaning
Baud rate = Basic baud rate
n = (Basic baud rate/baud rate) - 1
XOFF pattern
Meaning
Any character
(not the same as XON pattern)
Basic baud rate direct
Meaning
500 kbaud
62.5 kbaud
15625 baud
assigned. Element 15 indicates the desired baud rate.
Element 16 indicates the basic baud rate.
PHOENIX CONTACT
22
IB IL RS 485/422 ...
Example:
The baud rate should be
Element 2 = FFhex
25,000 baud
500 kbaud is selected as the Element 16 = 00hex
basic baud rate
n = (500,000 baud/25,000
Element 15 = 13hex
baud) - 1 = 19 = 13hex
When element 16 is written, direct baud rate programming
takes effect.
In theory, direct baud rate programming supports a
maximum value of 500 kbaud. Correct operation of the
module is tested and ensured up to 38,400 baud. Operation
at a higher baud rate depends on the application.
The error pattern contains the character that is written to
the FIFO if a character was received with errors (this does
not apply to the 3964R protocol). This can, for example, be
the result of parity errors, exceeded value ranges or noise
interference. In the transparent and XON/XOFF protocols,
this pattern is also used if the receive FIFO is full and
additional characters are received.
The first delimiter and the second delimiter contain the
end characters for the dual buffer and the end-to-end
protocols.
The value in the 3964R priority element defines the priority
of a device if there is an initialization conflict (several
devices attempting to send data simultaneously). The
device with priority level 1 has priority over the device with
priority level 0.
The rotation switch determines how the buffer is re-written
when it is full and the two end characters (delimiters) have
not been detected.
No rotation:
Only the new data is available in the overwritten buffer,
i.e., any existing data from the previous cycle is rejected.
Rotation:
The buffer is re-written character by character. If the two
delimiters are detected, the new characters and the
remaining characters from the previous cycle are available
in the overwritten buffer.
channel are set to empty. This means that all transmit and
receive data that has not yet been processed will be lost.
Error messages for the INIT-TABLE object
– If an element with an invalid value is written during a
write service, the service will be acknowledged with a
negative confirmation.
Here, the parameters are:
Error_Class:
Error_Code:
Additional_Code:
Meaning:
8
0
xx30hex
Value is out of range
The high byte of the Additional_Code (xx) contains the
number of the affected element. If several elements are
affected, the highest number is given. If, for example, the
output type element is written with the value 0, an error
message with the Additional_Code 0A30hex will be
displayed, because the 10th element is faulty.
– For a write request with the subindex 0 (write entire
table) in which the XON/XOFF protocol is to be set and
the XON pattern is the same as the XOFF pattern, an
error message will be generated.
Here, the parameters are:
Error_Class:
Error_Code:
Additional_Code:
Meaning:
–
8
0
0E30hex
Parameterization error
If a reserved element is written, the value must equal 0,
otherwise an error message is generated.
Here, the parameters are:
Error_Class:
Error_Code:
Additional_Code:
Meaning:
8
0
xx30hex
Parameterization error
If at least one element of the INIT-TABLE object is
written, the pointers for the transmit and receive
FIFOs will be reset. This means that all transmit
and receive data that has not yet been processed
will be lost.
XON pattern and XOFF pattern contain the control
characters for the XON/XOFF protocol. The characters
must not be the same.
In the case of the INIT-TABLE object, if one of the elements
is written, the transmit and receive buffers of the affected
6878_en_04
PHOENIX CONTACT
23
IB IL RS 485/422 ...
12.3
Error messages in PCP mode
The terminal error messages have the parameters:
Error_Class = 8 (device-specific error) and Error_Code = 0
(no communication error).
The exact error cause is indicated by the Additional_Code.
The low byte of the Additional_Code indicates the error
cause. The high byte of the Additional_Code (xx) contains
the number of the affected element. If several elements are
affected, the highest number is given.
The following Additional_Codes can occur on this terminal:
0022hex No character of the serial data will be accepted
from this service.
xx30hex Value is out of range or parameterization error
0000hex Hardware fault
For additional information about error messages
in PCP mode, please refer to the
IBS SYS PCP G4 UM E PCP manual and the
user manual for your controller board.
6878_en_04
PHOENIX CONTACT
24
IB IL RS 485/422 ...
13
Process data
For the assignment of the (word.bit) or (byte.bit) view illustrated under 13.1 and 13.3 to your INTERBUS control or
computer system, please refer to the DB GB IBS SYS ADDRESS data sheet.
5
Assignment
9
Word 0
8
7
6
5
2
1
0
5
3
Byte 1
4
3
7
6
4
Reserved
2
1
0
2
1
0
Reserved
6
10
Reset receive error
7
12 11
Byte 0
4
3
Reset transmit error
13
Execute re-initialization
14
Reserved
15
Reserved
(Word.bit) view Word
Bit
(Byte.bit) view Byte
Bit
Reserved
Assignment of the process data output word (~control word)
Reserved
13.1
Set all reserved bits to 0.
13.2
Format of the process data output word (~control word)
PCP channel
PCP channel
Process data channel
Receive error
No action
Reset receive error
Transmit error
No action
Reset transmit error
Re-initialization
No action
Execute re-initialization
Figure 11
6878_en_04
Format of the process data output word
PHOENIX CONTACT
25
IB IL RS 485/422 ...
If the control word contains 3C00hex, then the status word returns the firmware version and the module ID.
Example:
Status word (hex)
1
2
Firmware Version 1.20
0
7
Module ID
Using the module ID, it is possible to clearly identify different terminals with the same ID code.
Terminal
IB IL RS 485/422
IB IL RS 232
Module ID
7
8
6878_en_04
5
9
2
1
0
6
5
7
6
5
4
3
Byte 1
4
3
Number of received characters
2
1
0
2
1
0
Receive buffer not empty
6
10
Receive error
7
12 11
Byte 0
4
3
Re-initialization executed
13
Receive buffer full
14
Transmit buffer full
Assignment
15
Word 0
8
7
Transmit buffer not empty
(Word.bit) view Word
Bit
(Byte.bit) view Byte
Bit
Transmit error
Assignment of the process data input word (~status word)
Reserved
13.3
ID code
DChex (220dec)
DChex (220dec)
PHOENIX CONTACT
26
IB IL RS 485/422 ...
13.4
Format of the process data input word (~status word)
PCP channel
PCP channel
Process data channel
Receive buffer
Only for transparent and
XON/XOFF protocol:
Number of characters received
Reserved
If value = FFhex, the number of characters is
>= 255
Transmit buffer
Empty
Not empty
Empty
Not empty
Transmit buffer
Not full
Full
Receive buffer
Not full
Full
Figure 12
6878_en_04
Receive error
No error
Error
Transmit error
No error
Error
Re-initialization
No re-initialization
Re-initialization executed
Format of the process data input word
PHOENIX CONTACT
27
IB IL RS 485/422 ...
Bit/status
Bit 0 = '1'
Bit 1 = '1'
Bit 2 = '1'
Bit 3 = '1'
Bit 4 = '1'
Effect
The receive buffer is not empty, characters to be read are available.
Receive error
In the case of the 3964R protocol, this bit indicates that a telegram could not be received
without error after six transmit attempts by the serial peer or after the block waiting time
had elapsed.
For Modbus RTU and Modbus ASCII, this bit indicates that the checksum comparison
was faulty.
Transmit error
In the case of the 3964R protocol, this bit indicates that a telegram could not be
transmitted by the terminal to the serial peer after six transmit attempts. The telegram was
rejected.
For Modbus RTU and Modbus ASCII, this bit indicates that the timeout of 2.5 s elapsed
without any response being received.
A re-initialization was executed; the transmit and receive buffers are now empty.
The receive buffer is full:
Residual capacity: < 15 characters
Residual capacity: None
Bit 5 = '1'
The transmit buffer is full:
Residual capacity: ≤ 30 characters
Residual capacity: None
Bit 6 = '1'
Bit 7 = '1'
The transmit buffer is not empty, characters to be sent are available.
Reserved
Protocol
All
3964R,
Modbus RTU,
Modbus ASCII
3964R,
Modbus RTU,
Modbus ASCII
All
Transparent,
XON/XOFF
End-to-end,
3964R,
Modbus RTU,
Modbus ASCII
Transparent,
XON/XOFF,
end-to-end,
dual buffer
3964R,
Modbus RTU,
Modbus ASCII
All
Both error bits (bit 1 and 2) are not automatically
reset. They can only be reset by the process data
output word.
6878_en_04
PHOENIX CONTACT GmbH & Co. KG • 32823 Blomberg • Germany • Phone: +49-(0) 5235-3-00
PHOENIX CONTACT • P.O.Box 4100 • Harrisburg • PA 17111-0100 • USA • Phone: +717-944-1300
www.phoenixcontact.com
28
工商网监
湘ICP备2023018690号
