IB IL RS UNI(-2MBD)-PAC
Inline communication terminal
for serial data transmission
Data sheet
8235_en_01
1
© PHOENIX CONTACT 2012-03-14
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 in RS-232, RS-422 and
RS-485 format
Various protocols supported
Transmission speed can be set up to 250000 baud
Number of data bits, stop bits and parity can be set
Parameterization via process data or PCP
Process data width can be set via DIP switches: 7, 15 or
31 words
Diagnostic and status indicators
This data sheet is only valid in association with the IL SYS INST UM E user manual.
Make sure you always use the latest documentation.
It can be downloaded from the product at www.phoenixcontact.net/catalog.
IB IL RS UNI(-2MBD)-PAC
2
Table of contents
1
Description .............................................................................................................................. 1
2
Table of contents ..................................................................................................................... 2
3
Ordering data .......................................................................................................................... 3
4
Technical data ......................................................................................................................... 3
5
Internal circuit diagram ............................................................................................................ 5
6
Terminal point assignment....................................................................................................... 6
7
Local status and diagnostic indicators ..................................................................................... 7
8
Serial interfaces....................................................................................................................... 8
9
Connection examples .............................................................................................................. 9
10
Data storage and transmission .............................................................................................. 11
11
Programming data/configuration data.................................................................................... 12
12
Process data.......................................................................................................................... 13
13
Process data word 0 .............................................................................................................. 14
14
Commands ............................................................................................................................ 16
15
PCP communication .............................................................................................................. 21
8235_en_01
PHOENIX CONTACT
2
IB IL RS UNI(-2MBD)-PAC
3
Ordering data
Description
Type
Order No.
Pcs. / Pkt.
Inline communication terminal, for serial data transmission, complete with
accessories (plug connector and labeling field), 1 serial input and output
channel in RS-485/422 or RS-232 design
IB IL RS UNI-PAC
2700893
1
Inline communication terminal, for serial data transmission, complete with
accessories (plug connector and labeling field), 1 serial input and output
channel in RS-485/422 or RS-232 design, transmission speed 2 Mbaud
IB IL RS UNI-2MBD-PAC
2701025
1
Accessories
Type
Order No.
Pcs. / Pkt.
Connector set ( Plug/Adapter )
IB IL AO/CNT-PLSET
2732664
1
Inline shield connector ( Plug/Adapter )
IB IL SCN-6 SHIELD
2726353
5
Labeling field, width: 12.2 mm ( Marking )
IB IL FIELD 2
2727501
10
Insert strip, Sheet, white, Unlabeled, Can be labeled with: Office-Drucksys- ESL 62X10
teme, Plotter: Laser printer, Mounting type: Insert, Lettering field: 62 x 10
mm ( Marking )
0809492
1
Documentation
Type
Order No.
Pcs. / Pkt.
User manual, English, Automation terminals of the Inline product range
IL SYS INST UM E
-
-
Data sheet, English,
INTERBUS addressing
DB GB IBS SYS ADDRESS
-
-
4
Technical data
Dimensions (nominal sizes in mm)
135
71,5
119,8
Width
24.4 mm
Height
136.8 mm
Depth
71.5 mm
General data
Color
green
Weight
135 g
Mounting type
DIN rail
Ambient temperature (operation)
-25 °C ... 55 °C
Ambient temperature (storage/transport)
-25 °C ... 85 °C
Permissible humidity (operation)
10 % ... 95 % (DIN EN 61131-2)
Permissible humidity (storage/transport)
10 % ... 95 % (DIN EN 61131-2)
8235_en_01
PHOENIX CONTACT
3
IB IL RS UNI(-2MBD)-PAC
General data
Air pressure (operation)
70 kPa ... 106 kPa (up to 3000 m above sea level)
Air pressure (storage/transport)
70 kPa ... 106 kPa (up to 3000 m above sea level)
Degree of protection
IP20
Protection class
III, IEC 61140, EN 61140, VDE 0140-1
Connection data
Name
Inline connectors
Connection method
Spring-cage connection
Conductor cross section solid / stranded
0.08 mm² ... 1.5 mm²
Conductor cross section [AWG]
28 ... 16
Interface Inline local bus
Connection method
Inline data jumper
Interface RS-232, RS-485, RS-422
Connection method
Spring-cage connection
Transmission physics
Copper
Transmission speed Inline local bus
IB IL RS UNI-PAC
500 kBit/s
IB IL RS UNI-2MBD-PAC
2 MBit/s
Power consumption
Main circuit supply UM
24 V DC
I/O voltage range
19.2 V DC ... 30 V DC (including all tolerances, including ripple)
Current consumption from UM
Typ. 15 mA
Current consumption from UM
max. 25 mA
Communications power UL
7.5 V (via voltage jumper)
Current consumption from UL
Typ. 78 mA
Current consumption from UL
max. 90 mA
Power loss
max. 1.2 W (Within the permissible operating temperature)
This terminal takes no current from the UANA und US potential jumpers.
Electrical isolation/isolation of the voltage areas
Serial interface/7.5 V supply (bus logic)
500 V AC , 50 Hz , 1 min
Serial interface/24 V supply UM
500 V AC , 50 Hz , 1 min
Serial interface/functional earth ground
500 V AC , 50 Hz , 1 min
7.5 V supply (bus logics) / functional earth ground
500 V AC , 50 Hz , 1 min
24 V supply (UM)/functional earth ground
500 V AC , 50 Hz , 1 min
Electrical isolation of the logic level from the serial interface is ensured by the DC/DC converter.
The serial interface control and data lines galvanically have the same potential. FE is a separate potential area.
Error messages to the higher level control or computer system
None
Approvals
For the latest approvals, please visit www.phoenixcontact.net/catalog.
8235_en_01
PHOENIX CONTACT
4
IB IL RS UNI(-2MBD)-PAC
5
Internal circuit diagram
Local bus
SUPI 4
UL+
UAna
UL-
µP
5x
Current limit
short cut
protection
5V
±5 V
24 V
1
GND
±5 V
RS-485
±5 V
RS-232
DSR
RTS
Switch
RS-232
±5 V
RxD_232
/TxD_485
+24 V (US)
+24 V (UM)
Figure 1
±5 V
DCD
TxD_485
TxD_232
RxD_485
DSR_232
/RxD_485
RTS_232
R+_485
DCD_232
R-_485
+5 V
DTR_232
CTS_232
1
Internal wiring of the terminal points
Key:
Electrically isolated area
Protocol chip
SUPI 4
Capacitor
µC
Microprocessor
1
RS-485/422/232 interface
Diagnostic and status indicators
Ground, electrically isolated from ground
of the communications power UL
Explanation for other used symbols has been
provided in the IL SYS INST UM E user manual.
Optocoupler
DC/DC converter with electrical isolation
8235_en_01
There is a combination of resistors between
R+_485 and R-_485 which serve as a termination resistor when being used as RS-485 or RS422 interface.
PHOENIX CONTACT
5
IB IL RS UNI(-2MBD)-PAC
6
Terminal point assignment
1.1
1.1 2.1
2.1 1.1
1.1 2.1
2.1
1.2
1.2 2.2
2.2 1.2
1.2 2.2
2.2
1.3
1.3 2.3
2.3 1.3
1.3 2.3
2.3
1.4
1.4 2.4
2.4
1.4 2.4
1
Figure 2
6.1
6.2
RS-232 communication
Terminal Signal
point
Connector 1
1.1 / 2.1
1.2
DSR
2.2
RTS
1.3
DCD
2
Terminal point assignment
RS-485/422 communication
Terminal Signal
point
Connector 1
1.1
TxD+
2.1
TxD1.2
RxD+
2.2
RxD1.3
R+
2.3
R-
1.4 / 2.4
Shield
Description
Transmit data
Transmit data
Receive data
Receive data
Termination resistor
positive
negative
positive
negative
Positive
pole
Termination resistor
Negative
pole
Shield connection, same potential
as FE
Connector 2
The terminal points of this connector are not used.
2.3
1.4 / 2.4
Connector 2
1.1
RxD
2.1
TxD
1.2
+5 V DC
Description
Data set
ready
Not used
Connected device
ready to operate;
handshake signal;
input
Request to Request to send;
send
handshake signal; output
Data car- Connected device
rier detect ready to operate;
handshake signal;
input
Not used
Not used
2.2
CTS
Clear to
send
1.3
DTR
Data terminal
ready
2.3
GND
1.4 / 2.4
Shield
Serial data input
Serial data output
Control output; internally wired to +5 V
Permission to send;
connected device
ready to receive; handshake signal; input
Startup request to the
connected device;
handshake signal; output
Ground for the serial
interface
Shield connection, capacitive to FE
Ensure that on connector 2, terminal point 1.2
(+5 V DC) is exclusively used to provide the 5 V
signal for the CTS input (terminal point 2.2), in
the event of communication without a handshake. In this case, insert a jumper between the
terminal points.
8235_en_01
PHOENIX CONTACT
6
IB IL RS UNI(-2MBD)-PAC
7
Local status and diagnostic indicators
D
TR
DCD
RxD
TxD
RS UNI
Figure 3
CTS
RTS
DSR
DTR
Local status and diagnostic indicators
Designation
D
TR
DCD
RxD
Color
Meaning
green
Green
Yellow
Yellow
TxD
Yellow
CTS
RTS
DSR
DTR
Yellow
Yellow
Yellow
Yellow
Diagnostics (bus and logic voltage)
PCP communication
Data carrier detect
Terminal receives data from the
connected device
Terminal transmits data to the connected device
Clear to send
Request to send
Data set ready
Data terminal ready
For detailed information on diagnostics, please
refer to the IL SYS INST UM E user manual.
Function identification
Orange
2 Mbps: White stripe in the vicinity of the D LED
8235_en_01
PHOENIX CONTACT
7
IB IL RS UNI(-2MBD)-PAC
8
Serial interfaces
8.1
RS-232
8.2
RS-485
The RS-232 interface on the terminal represents some form of
DTE (data termination equipment).
This means that connector 2 terminal point 2.1 (TxD) is always used to transmit and connector 2 terminal point 1.1
(RxD) is always used to receive.
In RS-485 operating mode, an RS-485 network with several
devices can be created.
Measuring the voltage between the connection points for the
TxD and GND signals in idle state will determine whether the
device to be connected to the RS-232 interface is a form of
DTE or DCE. If the voltage measures approximately -5 V, the
device is a form of DTE. If the voltage is approximately 0 V,
the device is a form of DCE.
Make sure that only one device is transmitting data at a time.
Use a twisted-pair, shared and shielded data line to connect
the devices. Fit this data line with termination resistors at the
two most remote points of the RS-485 network. Use the termiAccording to the standard, some form of DCE (data commu- nation resistor integrated in the device when connecting the
nication equipment) should be connected to the RS-232 inter- Inline terminal.
face as a peer. DTE can also be connected.
This operating mode supports half-duplex transmission.
To ensure a defined idle cable state, the terminal contains
data line polarization.
8.3
RS-422
In RS-422 operating mode, a point-to-point connection can
Example: When using a 25-pos. standard connector the volt- be established.
age between pin 2 (TxD) and pin 7 (GND) must be measured.
Use a twisted-pair, shared and shielded data line to connect
the devices. Fit this data line with termination resistors at
RS-232 module handshake signals
every device. Use the termination resistor integrated in the
Any device with a RS-232 interface can be connected to the device when connecting the Inline terminal.
RS-232 interface on the terminal. Both the terminal and the
This operating mode supports full duplex transmission.
device connected to the RS-232 interface can act as a transmitter and a receiver for data exchange. As errors can occur
during data exchange if both devices transmit or receive simultaneously, the handshake is used as a procedure for the
mutual signaling of clear to receive and clear to transmit.
The terminal supports the RTS, CTS, CTR, DSR and DCD
handshake signals. Each uses one wire of the connecting cable.
The connecting signals are described from the point of view
of the terminal, i.e., from the point of view of the DTE.
8235_en_01
PHOENIX CONTACT
8
IB IL RS UNI(-2MBD)-PAC
9
Connection examples
Operating mode
RS-485
RS-485
RS-485
RS-422
Special feature
Inline terminal as network end point
Inline terminal as network end point
Terminal in the network
center
Shield connected using
a capacitor
Shield connection
Directly
Notes
Termination resistor required
Termination resistor required
-
With a capacitor
With a capacitor/directly
With a capacitor
Required connectors
Supplied connectors
(connector set)
Supplied connectors
(connector set)
2 shield connectors
Termination resistor re- Supplied connectors
quired
(connector set)
9.1
RS-485: Terminal as the network end point
The connector set consists of a shield connector and a standard connector. It is supplied as
standard.
Connect the shield directly to FE.
Please observe the following when wiring:
–
–
–
Always connect the shield between two devices on one
side using a capacitor and on the other side directly to FE. Connector
1 2
Fit a termination resistor to the RS-485 network beginning and end.
For an RS-422 point-to-point connection, the receive signals on every device must be fitted with termination resistors.
IB IL RS UNI ...
TxD+ 1.1
TxD-
D
TR
DCD
RxD
CTS
RTS
DSR
TxD
DTR
1
2
1
2
1
11
1
2
22
2
3
33
3
4
44
4
2.1
RxD+ 1.2
RxD-
2.2
R+
1.3
R-
2.3
8235_en_01
Transmit/receive data (negative)
Connecting the termination
resistor via R+ and R-
Inline connector
(Connector 1)
RS 485
Figure 4
Transmit/receive data (positive)
RS 485
RS 485
RS-485 interface wiring:
Terminal as end point of a network, shield or
data cable directly connected to FE
PHOENIX CONTACT
9
IB IL RS UNI(-2MBD)-PAC
9.2
RS-485: Terminal as the network end point
9.3
RS-485: Terminal in the network center
Connect the shield to FE using a capacitor.
Connector 1
2
IB IL RS UNI ...
TxD+ 1.1
Connector 1
2
TxDD
IB IL RS UNI ...
TxD+ 1.1
TxD- 2.1
Transmit/receive data (positive)
RxD+ 1.2
Transmit/receive data (negative)
RxD- 2.2
Connecting the termination
resistor via R+ and R-
R+
1.3
R-
2.3
Inline connector
(Connector 1)
RS 485
9.4
CTS
RTS
DSR
TxD
DTR
D
TR
DCD
RxD
CTS
RTS
DSR
TxD
DTR
1
2
1
1
2
1
11
1
2
22
2
3
33
3
4
44
4
RS 485
RS 485
2
1
2
1
11
1
2
22
2
3
33
3
4
44
4
Transmit/
receive data
(positive)
Transmit/
receive data
(negative)
2.1
RxD+ 1.2
RxD- 2.2
R+
1.3
R-
2.3
Inline connector
(Connector 1)
RS 485
RS 485
RS 485
RS 485
Figure 6
Figure 5
TR
DCD
RxD
RS-485 interface wiring:
Terminal in the center of a network, data line
shield connected directly capacitively to FE
RS-485 interface wiring:
Terminal as end point of a network, shield or
data cable connected capacitively to FE
RS-422: Shield connected to the terminal using a capacitor
Connector
1 2
IB IL RS UNI ...
D
TR
DCD
RxD
CTS
RTS
DSR
TxD
DTR
Receive data (positive)
TxD- 2.1
Transmit data (negative)
Receive data (negative)
RxD+ 1.2
Receive data (positive)
Transmit data (positive)
RxD- 2.2
Receive data (negative)
Transmit data (negative)
Connecting the
termination resistor
via R+ and R-
Connecting the
termination resistor
R+
1
2
1
2
1
11
1
2
22
2
3
33
3
4
44
4
RS-422 device
Transmit data (positive)
TxD+ 1.1
1.3
2.3
RInline connector
(Connector 1)
RS 422
Figure 7
8235_en_01
RS-422 interface wiring: Data line shield connected capacitively to FE
PHOENIX CONTACT
10
IB IL RS UNI(-2MBD)-PAC
9.5
RS-232: With 4-wire handshake
1.1
2.1
1.1
2.1
1.2
2.2
1.2
2.2
1.3
2.3
1.3
2.3
1.4
2.4
1.4
2.4
10
Data storage and transmission
The terminal stores the received serial data in an intermediate
buffer until it is requested from the serial interface by the bus
controller board or the device. Serial data traffic can be managed using various protocols. The protocol used depends on
the type of protocol supported by the peer.
10.1
Supported protocols
Receive
memory
Transmit
memory
Transparent
End-to-end
4096 bytes
3 buffers with
330 bytes
each
XON/XOFF
4096 bytes
1023 bytes
1023 bytes
(including
end characters)
1023 bytes
DTR
CTS
TxD
RxD
Protocol
Figure 8
9.6
RS-232 interface wiring: data cable shield connected capacitively to FE
RS-232: Without handshake
1.1
2.1
1.1
2.1
1.2
2.2
1.2
2.2
10.2
2.3
1.3
2.3
1.4
2.4
1.4
2.4
Two end
characters
are filtered
out
Software
handshake
Transparent protocol
If the transparent protocol is used, serial data is transmitted in
the same format it is received from the serial interface or from
the bus side.
TxD
RxD
1.3
Special features when
receiving
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 other subsequent characters are ignored.
This protocol supports a CTS hardware handshake.
Figure 9
RS-232 interface wiring: data cable shield connected directly to FE
If the available space in the receive memory is less than
15 bytes, DTR is set to logic 0. As soon as more memory
space becomes available again, DTR is set to logic 1.
For wiring without handshake, insert a bridge between terminal points 1.2 (+5 V) and 2.2 (CTS).
8235_en_01
PHOENIX CONTACT
11
IB IL RS UNI(-2MBD)-PAC
10.3
End-to-end protocol
11
The serial data is conditioned for the end-to-end protocol.
Programming data/configuration
data
If serial data is sent from the bus side, two additional characters, the first and second delimiters, are attached for transmis- 11.1 Local bus (INTERBUS)
sion to the serial interface.
DF
A block of serial data sent from the serial interface is only valid ID code [hex] DF
ID code (dec) 223
223
if the terminal has received the first and second delimiters.
Only then the data can be read via the bus side. The delimit- Length code 07
0F
ers are filtered out.
[hex]
240 bits
Unlike in the transparent protocol, the receive memory is not Process data 112 bits
organized as a FIFO but as a buffer. There are 3 buffers avail- channel
able, each with 330 bytes. If the buffer size of 330 bytes is ex- Input address 7 words
15 words
ceeded without the two delimiters being detected, the previ- space
ous characters will be ignored and the buffer will be written
Output ad7 words
15 words
again.
dress space
The transmit FIFO can store 1023 bytes (1 kbyte). The delim- Parameter
1 word
1 word
iters are attached to, and stored with, the data to be sent.
channel
(PCP)
10.4 XON/XOFF protocol
Register
8 words
16 words
This protocol operates in the same way as the transparent
length (bus)
protocol, but uses a software handshake.
Data transmission with this protocol is controlled by the XON 11.2
and XOFF characters. XON is preset to 11hex and XOFF to
13hex.
If the terminal receives an XOFF, no more serial data will be
sent until an XON is received.
The terminal itself will transmit an XOFF if the available space
in the receive memory is less than 15 bytes. As soon as more
memory space becomes available again, the terminal will
transmit a single XON.
DF
223
1F
496 bits
31 words
31 words
1 word
32 words
Other bus systems or networks
For the programming data/configuration data
of other bus systems, please refer to the corresponding electronic device data sheet (e.g.,
GSD, EDS).
Transmission does not depend on the CTS input.
Transmission of serial data is not filtered. So any characters
occurring with the code defined for XON and XOFF are transmitted 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.
8235_en_01
PHOENIX CONTACT
12
IB IL RS UNI(-2MBD)-PAC
12
Process data
The process image width of the terminal depends on the DIP
switch positions and comprises 7, 15 or 31 data words in input
and output direction respectively.
Switch 2
Switch 1
OFF
OFF
ON
ON
OFF
ON
OFF
ON
Data width User data when
transmitting and
reading
7 words
11 bytes
15 words
27 bytes
31 words
59 bytes
Reserved
Reserved
For the assignment of the illustrated (byte.bit)
view to your INTERBUS control or computer
system, please refer to the
DB GB IBS SYS ADDRESS data sheet.
ON
21
Data length
Figure 10
DIP switches
Example for the assignment of seven words of process data
Word
Byte in the Motorola format
Byte in the Intel
format
OUT
IN
K/P
S
L
D
0
1
2
3
4
5
6
0
1
2
3
4
5
6
7
8
9
10
11
12
13
1
0
3
2
5
4
7
6
9
8
11
10
13
12
K/P
K/P
S
S
L
L
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
D
Command/parameter
Control bits (OUT) or status bits (IN)
Length: Number of characters to be written
(OUT) or to be read (IN)
Data
The byte representation in the Motorola format,
also called Big Endian (high order byte at starting address) corresponds to the INTERBUS
standard representation. All byte representations in the data sheet have this format.
The byte representation in the Intel format is
also called Little Endian (low order byte at starting address).
The command is used to determine the function. The actually
transmitted data depends on the command.
8235_en_01
PHOENIX CONTACT
13
IB IL RS UNI(-2MBD)-PAC
13
Process data word 0
13.1
Control word
15
0
14
13
12
Command
7
DTR
6
0
11
10
9
OUT parameter
5
0
8
7
4
0
6
3
0
5
4
3
Control bits
2
2
1
Reset trans- Reset receive
mit error
error
1
0
0
0
Commands
DTR (if DTR control enabled)
Code [bin]
Meaning
0
DTR = logic 0
1
DTR = logic 1
The DTR signal can only be controlled when
DTR control is enabled via process data, that is
when the DTR control bit has been enabled in
the configuration (see "Write configuration"
command).
Code [bin]
0
1
Code [bin]
0
1
Meaning
Reset transmit error
No action
Reset transmit error
Reset receive error
Meaning
No action
Reset receive error
The listed protocols do not support transmit
and receive errors.
Code
[bin]
000
001
010
011
011
Code
[hex]
0
1
2
3
3
011
3
011
100
101
3
4
5
110
6
111
7
Command
Read number of characters received
Transmit characters
Store characters temporarily
OUT parameter = 0hex: Read characters
OUT parameter = Chex: Read firmware
version
OUT parameter = Dhex: Read configuration
OUT parameter = Ehex: Read counters
Write configuration
Toggling command 1: Transmit characters
Toggling command 2: Store characters
temporarily
Toggling command 3: Read characters
Command toggling
Command toggling is used to execute a command on a terminal again. In this way, a second command code is available
for the same function.
This applies for the following commands:
– Transmit characters
– Store characters temporarily
– Read characters
– Read counters
Here, bit 14 is used for toggling. If, for example, you wish to
transmit character strings in sequence, use command code
001hex for the first transmission and then use 101hex and
001hex alternately.
8235_en_01
PHOENIX CONTACT
14
IB IL RS UNI(-2MBD)-PAC
13.2
Status word
15
St
14
St
13
12
Command
11
10
9
IN parameter
8
7
6
5
4
3
Status bits
2
1
0
Reasons for an error bit set:
– Invalid parameter for the specified command
– Failure of the I/O voltage
Error bit
Status bits
7
DSR
6
5
Transmit buf- Transmit buffer not empty
fer full
4
Receive buffer full
3
DCD
2
Transmit
error
DSR
Code [bin]
0
1
Meaning
DSR = logic 0
DSR = logic 1
Transmit buffer not empty
Code [bin]
Meaning
0
Empty
1
Not empty
Code [bin]
0
1
Transmit buffer full
Meaning
Not full
Full
Code [bin]
0
1
Receive buffer full
Meaning
Not full
Full
Code [bin]
0
1
Code [bin]
0
1
1
0
Receive error Receive buffer not empty
Receive error
Meaning
No error
Receive error
Meaning
Receive buffer not empty
Empty
Not empty
The listed protocols do not support transmit
and receive errors.
DCD
Code [bin]
0
1
Meaning
DCD = logic 0
DCD = logic 1
Code [bin]
0
1
Transmit error
Meaning
No error
Transmit error
8235_en_01
PHOENIX CONTACT
15
IB IL RS UNI(-2MBD)-PAC
14
Commands
14.1
"Read number of characters received" command
The command result is the number of characters that have
been received but not yet read.
This command can be used to first reach a minimum number
of characters before transmitting the "Read characters" command.
Process data assignment for the "Read number of characters received" command (process data width: 7 words)
Word
Byte
OUT
IN
14.2
0
0
00hex
00hex
1
2
1
2
3
xx
xx
xx
Status bits Read number of characters received
4
xx
xx
3
5
xx
xx
6
xx
xx
4
7
xx
xx
8
xx
xx
5
9
xx
xx
10
xx
xx
6
11
xx
xx
12
xx
xx
13
xx
xx
"Transmit characters" command
The transmit data located in the process data is stored in the
transmit memory. From there the data is transmitted directly
via the interface. Depending on the process data width a maximum of 11, 27 or 59 characters can be transmitted. Enter the
number of characters to be transmitted in the third byte. If
there are characters in the intermediate buffer, these are
transmitted first. After the command has been executed successfully, the intermediate buffer is cleared.
Process data assignment for the "Transmit characters" command with 11 characters (Z1 - Z11; process data width: 7 words)
Word
Byte
OUT
IN
0
0
10hex
10hex
1
1
2
xx
0Bhex
Status
xx
bits
2
3
C1
xx
4
C2
xx
3
5
C3
xx
6
C4
xx
4
7
C5
xx
8
C6
xx
5
9
C7
xx
10
C8
xx
6
11
C9
xx
12
C10
xx
13
C11
xx
Reasons for an error bit set:
– Byte 2 (number of characters to be transmitted)
= 0 or > maximum user data length (11, 27 or 59 characters)
– "Neutral" interface type
14.3
"Store characters temporarily" command
The transmit data located in the process data is stored in an
intermediate buffer, which can store up to 330 characters. No
characters are transmitted. The "Transmit characters" command is used to transmit temporarily stored data. In this way,
blocks of up to 330 characters can be transmitted. They are,
for example, divided into 30 telegrams, each with 11 characters.
Reasons for an error bit set:
– Byte 2 (number of characters to be transmitted)
= 0 or > maximum user data length (11, 27 or 59 characters)
– Not enough space in the intermediate buffer
8235_en_01
PHOENIX CONTACT
16
IB IL RS UNI(-2MBD)-PAC
14.4
"Read characters" command
Depending on the process data width set a maximum of 11, tains the number of valid characters available in the input
27 or 59 characters can be read. The third byte (byte 2) con- data.
Process data assignment for the "Read characters" command with eleven characters (C1 - C11)
Word
Byte
OUT
IN
0
0
30hex
30hex
1
1
xx
Status
bits
2
xx
0Bhex
2
3
xx
C1
4
xx
C2
3
5
xx
C3
6
xx
C4
4
7
xx
C5
8
xx
C6
5
9
xx
C7
10
xx
C8
6
11
xx
C9
12
xx
C10
13
xx
C11
Bit 7 in the third input byte (byte 2)
Byte 2, bit 7 Effect
0
The characters read are the
last ones in the block received.
1
There are still more characters to be read from the block
received.
14.5
Protocol
E.g., end-toend
E.g., end-toend
"Read counters" command
This command can be used to read several counters. The
counters are used for interface diagnostics.
Process data assignment for the "Read counters" command
Word
Byte
OUT
IN
8235_en_01
0
0
3Ehex
3Ehex
1
00hex
Status bits
1
2
3
xx
xx
Number of valid characters received
2
4
5
xx
xx
Number of invalid characters received (parity,
overrun or framing errors)
3
6
7
xx
xx
Number of characters
transmitted
PHOENIX CONTACT
17
IB IL RS UNI(-2MBD)-PAC
14.6
"Write configuration" command
Output words 0 to 6
Process data assignment for the "Write configuration" command
Word
Byte
OUT
0
40hex
0
1
xx
2
T/P
1
IN
40hex
Status
bits
-
2
3
4
B/DB 1st del
-
-
3
5
2nd
del
-
4
5
6
6
ErrP
7
Uni1
8
Uni2
9
Uni3
10
res.
11
res.
12
Tv
13
Tn
-
-
-
-
-
-
-
-
Element value range
The options in bold are default settings.
Byte 2 (T/P: interface type/protocol)
7
res.
6
5
4
DTR Interface type
Code [bin]
0
1
Code [bin]
00
01
10
11
3
2
1
Protocol
0
DTR: DTR control
Meaning
Automatic
Can be controlled via process data
Interface type
Meaning
RS-232
RS-485
RS-422
Neutral
Select an RS-xxx interface type. With the "neutral" default setting, no data is transmitted or received. When using the default setting, an error
message is generated and the error bit is set.
Code [hex]
0
1
2
Other
8235_en_01
Protocol
Meaning
Transparent
End-to-end
XON/XOFF
Reserved
PHOENIX CONTACT
18
IB IL RS UNI(-2MBD)-PAC
Byte 3 (D/DB: baud rate/data width)
Baud rate
Code [hex]
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
The specified combinations of data width, parity and stop bits are adequate for most applications. However, you can freely choose the
combination by direct programming. For this,
use the 0Fhex data width code.
Wert [baud]
110
300
600
1200
1800
2400
4800
9600
15625
19200
38400
57600
115200
230400
250000
Direct (Uni1 ... 3)
Byte 4 and 5 (1st del, 2nd del: 1st and 2nd delimiters)
The 1st delimiter and 2nd delimiter contain the end characters
for the end-to-end and dual buffer protocols.
When selecting the end-to-end protocol, the two delimiters
can be adjusted.
Default settings:
Delimiter
1st del
2nd del
8235_en_01
Data width
Meaning
Data bits
Parity
7
Even
7
Odd
8
Even
8
Odd
8
Without
7
Without
7
Even
7
Odd
8
Even
8
Odd
8
Without
7
Without
8
Constantly at 0
8
Constantly at 1
6
Without
Directly
(Uni1)
ASCII character
CR = carriage return
LF = line feed
Byte 6 (ErrP: error pattern)
The specified baud rates of 110 baud to
250000 baud are adequate for most applications. However, you can freely choose the
baud rate by direct programming. For this, use
the 0Fhex baud rate code.
Code [hex]
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
Default
value
0Dhex
0Ahex
Stop bits
1
1
1
1
1
1
2
2
2
2
2
2
1
1
1
The error pattern contains the character that is written to the
FIFO if a character was received with errors (e.g., in the event
of a parity error).
The error pattern is used for the following protocols:
– Transparent
– End-to-end
– XON/XOFF
Code [hex]
24
xx
00
FF
Error pattern
Meaning
$
Any character
If a character is received with an error, no
error pattern is stored.
The invalid character is stored instead of
the error pattern.
PHOENIX CONTACT
19
IB IL RS UNI(-2MBD)-PAC
Byte 7 ... 9 (Uni1 ... Uni3: universal byte 1 ... 3)
Direct specification of the data width
These bytes can be used as universal bytes for direct specifi- If the provided combinations of data width, parity and stop bits
cation of the baud rate or the data width.
are inadequate, they can be directly specified. Use the Uni1
byte. Bit 1 and bit 0 are reserved.
Byte 7
Byte 8
Byte 9
7
6
5
4
3
2
1
0
7 6 5 4 3 2 1 0 7
...
0 7
...
0
Parity
Enable parity Stop
Data bits res. res.
Data width
Baud rate
bits
Direct specification of baud rate
Parity
If the provided baud rates do not correspond to the desired
baud rate, the baud rate can be directly specified. For this,
write the desired baud rate on the Uni1 to Uni3 fields in the
form of a numeric value. Transfer is right-aligned. However,
only the 2 lower bits of Uni1 are permitted.
The maximum value is 18 bits. The maximum value =
3FFFFhex which corresponds to 262143 baud.
Code [bin]
00
01
10
11
Meaning
Odd
Even
Constantly at 1
Constantly at 0
Code [bin]
0
1
Enable parity
Meaning
Disable
Enable
Code [bin]
0
1
Stop bits
Meaning
1 stop bit
2 stop bits
Code [bin]
00
01
10
11
Data bits
Meaning
5 bits
6 bits
7 bits
8 bits
Example for direct specification of the baud rate:
– Baud rate: 100000 baud
– 100000dec = 01 86 A0hex
Word
Byte
OUT
OUT
0
1
40hex
40hex
8235_en_01
1
1
xxhex
xxhex
2
T/P
xx
2
3
B/DB
Fxhex
4
res.
00
3
5
res.
00
6
ErrP
xx
4
7
Uni1
01
8
Uni2
86
5
9
Uni3
A0
10
res.
00
6
11
res.
00
12
Tv
xx
13
Tn
xx
PHOENIX CONTACT
20
IB IL RS UNI(-2MBD)-PAC
Byte 12 und 13 (Tv, Tn: lead time, lag time)
15
PCP communication
15.1
General information
These two times are used for the RS-232 protocol
Tv
Tn
Lead time
Lag time
The times are specified with a resolution of 1 ms. This allows
for waiting times of 1 ms ... 255 ms.
When transmitting data via RS-232 the RTS signal is set. If Tv
does not equal 0, transmission only starts after this time has
elapsed. After all the data is sent and Tn does not equal 0, the
RTS signal is only set to LOW after this time has elapsed.
For information on PCP communication,
please refer to the PCP user manuals (see Ordering data).
By default upon delivery, the terminal is configured according
to the default settings (under configuration). The terminal can
be configured using process data or PCP to suit your application.
In PCP mode, the terminal is configured with the "Config Table" object.
The programs IBS CMD (for standard controller boards) and PC WorX (for Controllers (ILC),
Field Controllers (FC) and Remote Field Controllers (RFC)) are available for the configuration and parameterization of your INTERBUS
system.
For additional information, please refer to the
documentation of the software used.
8235_en_01
PHOENIX CONTACT
21
IB IL RS UNI(-2MBD)-PAC
15.2
Object dictionary for PCP communication
Index
0080hex
A
L
15.3
Data type
Record
A
1
L
16
Meaning
Terminal configuration
Number of elements
Length of an element in bytes
rd
wr
Object name
Config Table
Read access permitted
Write access permitted
Rights
rd/wr
"Config Table" object
Configure the terminal using this object.
Access this object via subindex 0, i.e., read or write the entire
project.
The first twelve bytes correspond to byte 2 through byte 13 of
the "Write configuration" command. The other four bytes are
reserved.
Byte
0
1
2
3
4
5 ... 7
8, 9
10
11
12 ... 15
Meaning
Type, protocol
Baud rate, data width
1st delimiter
2nd delimiter
Error pattern
Uni1 ... Uni3
Reserved
Tv
Tn
Reserved
Default value
00hex
72hex
0Dhex
0Ahex
24hex
00 00 00hex
00 00hex
00hex
00hex
00 00 00 00hex
If an invalid configuration is specified, a negative confirmation
is generated with error message 08hex, 00hex or xx30hex. The
low byte of the Additional_Error_Code is 30hex (value is out of
range), the high byte contains the number of the affected
byte.
8235_en_01
PHOENIX CONTACT GmbH & Co. KG • 32823 Blomberg • Germany
www.phoenixcontact.com
22
工商网监
湘ICP备2023018690号
