6985

DATASHEET SEARCH SITE

Document overview

• Manufacturer or author: Provided By www.digicamel.com(FREE DATASHEET DOWNLOAD SITE)
• PDF pages: 20

Technical content

Features

– A serial I/O channel (RS-485 or RS-422) – Various protocols supported – Transmission speed can be set up to 38400 baud – Number of data bits, stop bits, and parity can be set – 4 kbyte receive buffer an d 1 kbyte transmit buffer – Parameterization and data exchange via the bus using process data Inline terminal for serial data transmission This data sheet is only valid in association with the IL SYS PRO INST UM E user manual. Make sure you always use the latest documentation. It can be downloaded at www.download.phoenixcontact.com. This data sheet is valid for the products listed on the following page: /G32 /G78

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 2 2O r d e r i n g d a t a

3 Technical data

Description Type Order No. Pcs./Pkt. Inline terminal for serial data transmission, complete with accessories (connector and labeling fields); transmission speed 500 kbaud IB IL RS 485/422-PRO-PAC 2863627 1 Inline terminal for serial data transmission, without accessories, transmission speed 500 kbaud IB IL RS 485/422-PRO 2863707 1 Inline terminal for serial data transmission, complete with accessories (connector and labeling fields); transmission speed 2 Mbaud IB IL RS 485/422-PRO-2MBD-PAC 2878887 1 The listed connector set is needed for the complete fitting of the IB IL RS 485/422-PRO terminal. When using the terminal according to the example "RS-485: Terminal in the network center" on page 9 two shield connectors are required for connecting the cables. Accessories Description Type Order No. Pcs./Pkt. Connector set with a standard connector and a shield connector IB IL AO/CNT-PLSET 2732664 1 set Shield connector IB IL SCN-6 SHIELD 2736353 5 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 General data Housing dimensions (width x height x depth) 24.4 mm x 136 mm x 72 mm (with connectors) Weight 90 g (without connectors), 135 g (with connectors) Operating mode Process data mode with 6 words Connection method for sensors 2 and 3-wire technology Permissible temperature (operation) -25°C to +55°C Permissible temperature (storage/transport) -25°C to +85°C Permissible humidity (operation/storage/transport) 10% to 95% according to DIN EN 61131-2 Permissible air pressure (operation/storage/transport) 70 kPa to 106 kPa (up to 3000 m above sea level) Degree of protection IP20 according to IEC 60529 Class of protection Class 3 according to EN 61131-2, IEC 61131-2 Connection data for connectors Connection type Spring-cage terminals Conductor cross-section 0.2 mm 2 to 1.5 mm2 (solid or stranded), 24 - 16 AWG

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 3 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 Line termination resistance 120 Ω typical Permissible input differential voltage ±5.7 V maximum Hysteresis 50 mV, typical Input sensitivity -0.2 V mi nimum, +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 Owing to the 120 Ω termination resistance the input differential voltage is limited to ±5.7 V. Transmission speed IB IL RS 485/422-PRO 500 kbaud IB IL RS 485/422-PRO-PAC 500 kbaud IB IL RS 485/422-PRO-2MBD-PAC 2 Mbaud Supply of the module electronics through the bus coupler Connection method Potential routing Power consumption 500 kbps 2 Mbps 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 Approx. 1.275 W, typical,

1.950 W, maximum*

Approx. 1.388 W, typical,

• All connections of the serial interface are short-circuited. ATTENTION: Defective module when continuously short-circuited A continuous short circuit can damage the device. Therefore rule out continuous short circuits. This terminal takes no current from the UM and US potential jumpers. Power dissipation Power dissipation in the module P EL = 1.4 W Power dissipation of the housing PHOU 1.4 W, maximum (within the permissible operating temperature) Limitation of simultaneity, derating TA ≤ 50°C No derating TA > 50°C IQ = 4 A IQ: Total diagonal routing current IM/IS/GND Safety equipment None

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 4

4 Diagnostic/status indicators and

Figure 1 Diagnostic/status indi cators and terminal point assignment

4.1 Local diagnostic and status indicators

4.2 Function identification

2 Mbps: white stripe in the vicinity of the D LED

Electrical isolation/isolation of the voltage areas 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 lines 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 /G36 /G31 /G39 /G39 /G41 /G30 /G30 /G33 /G44 /G52 /G53 /G34 /G38 /G35 /G2F /G34 /G32 /G32 /G54 /G52 /G52 /G78 /G44 /G54 /G78 /G44 /G31 /G32 /G31 /G32 /G33 /G34 /G31 /G32 /G33 /G34 /G31 /G2E /G31 /G31 /G2E /G32 /G31 /G2E /G33 /G31 /G2E /G34 /G32 /G2E /G31 /G32 /G2E /G32 /G32 /G2E /G33 /G32 /G2E /G34 /G32 /G31 Des. Color Meaning D Green Diagnostics TR –– Serial interface: RxD Yellow Terminal is receiving data from the connected device TxD Yellow Terminal is transmitting data to the connected device

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 5

4.3 Terminal point assignment in the half-duplex

operating mode (RS-485)

4.4 Terminal point assignment in the full-duplex

operating mode (RS-422) Connec- tor Terminal point Signal Assignment Data direction 1 1.4, 2.4 FE Functional earth ground

2.3 GND GND*

All other terminal points of this connector are not used. 21 . 1 T x D + Reserved

2.1 TxD- Reserved

1.2 RxD+ Receive/transmit

data (positive) Input/ output

2.2 RxD- Receive/transmit

data (negative) Input/ output

1.3 R+ Termination

resistor (positive)

2.3 R- Termination

resistor (negative) 1.4, 2.4 Shield Shield connection * For the IB IL RS 485/422-PRO (-PAC) terminal, hardware version 01 or later. In all previous versions terminal point 2.3 is not used. For the IB IL RS 485/422-PRO-2MBD-PAC terminal, hardware version 00 or later. Connec- tor Terminal point Signal Assignment Data direction 11 . 4 , 2 . 4 F E Functional earth ground All other terminal points of this connector are not used. 21 . 1 T x D + Transmit data (positive) Output

2.1 TxD- Transmit data

(negative) Output

1.2 RxD+ Receive data

(positive) Input

2.2 RxD- Receive data

(negative) Input resistor (positive) resistor (negative) 1.4, 2.4 Shield Shield connection * For the IB IL RS 485/422-PRO (-PAC) terminal, hardware version 01 or later. In all previous versions terminal point 2.3 is not used. For the IB IL RS 485/422-PRO-2MBD-PAC terminal, hardware version 00 or later. Observe the connection notes on page 7.

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 6

5 Internal circuit diagram

Figure 2 Internal wiring of the terminal points Key: Protocol chip (bus logic including voltage conditioning) RS-485/422 interface Diagnostic and status indicators with function information Capacitor Optocoupler Resistor DC/DC converter with electrical isolation Ground, electrically isolated from ground of the communications power UL Microprocessor /G36 /G31 /G39 /G39 /G43 /G30 /G30 /G34 /G2B /G32 /G34 /G20 /G56 /G20 /G28 /G55 /G4D /G29 /G2B /G32 /G34 /G20 /G56 /G20 /G28 /G55 /G53 /G29 /G4C /G6F /G63 /G61 /G6C /G20 /G62 /G75 /G73 /G55 /G4C /G2B /G55 /G41 /G4E /G41 /G55 /G4C /G2D /G4F /G50 /G43 /G44 /GB5 /G50 /G54 /G78 /G44 /G2D /G35 /G20 /G56 /G35 /G20 /G56 /G35 /G20 /G56 /G32 /G34 /G20 /G56 /G54 /G52 /G31 /G54 /G78 /G44 /G52 /G78 /G44 /G52 /G53 /G2D /G34 /G38 /G35 /G2F /G34 /G32 /G32 /G20 /G49 /G6E /G74 /G65 /G72 /G66 /G61 /G63 /G65 /G2F /G2F /G54 /G78 /G44 /G2B /G52 /G78 /G44 /G2B /G52 /G2B /G52 /G2D /G31 /G52 /G78 /G44 /G2D /G47 /G4E /G44 OPC /G52 /G53 /G2D /G34 /G38 /G35 /G2F /G34 /G32 /G32 /G20 /G49 /G6E /G74 /G65 /G72 /G66 /G61 /G63 /G65 /G2F /G2F /G78 /G78 /G78 /G58 /G58 /G58 /G31 /GB5 /G50 Hardware version 01 or later: GND is assigned to terminal point 2.3 of the IB IL RS 485/ 422-PRO (-PAC) terminal. In all previous versions, this terminal point is not used. For the IB IL RS 485/422-PRO-2MBD-PAC terminal with hardware version 00 or later, the terminal point 2.3 is assigned to GND. Other symbols used are explained in the IL SYS INST UM E user manual or in the Inline system manual for your bus system.

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 7

6 Serial interface

The terminal has an RS-485 and an RS-422 interface. The interfaces can only be operated alternatively.

6.1 RS-485

In RS-485 operating mode, an RS-485 network with several devices can be created. Use a data cable with commonly shielded twisted pairs to connect the devices. Equip this data cable with a termination resistor at both most remote points of the RS- 485 network. To connect them to the Inline terminal, use the termination resistor installed in the device (see Figure 2). Connection examples are shown in Figures 5 to 7 on pages 9 to 10. This operating mode supports the half-duplex transmission. Make sure that only one device is transmitting data at a time. In order to be able to guarantee a defined cable idle state, the data cable polarization is contained in the terminal.

6.2 RS-422

In RS-422 operating mode, it is possible to establish a point- to-point connection. Use a data cable with commonly shielded twisted pairs to connect the devices. Equip this data cable with a termination resistor at each device. To connect them to the Inline terminal, use the termination resistor installed in the device (see Figure 2). Connection examples are shown in Figures 8 to 9 on pages 10 to 11. This operating mode supports full-duplex transmission.

7 Connection notes

7.1 Shield connected capacitively to FE

Figure 3 Position of the shield connector to connect the shield capacitively to FE

7.2 Shield connected directly to FE

Figure 4 Position of the shield connector to connect the shield directly to FE 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). The two connection options allow to connect one cable shield side to FE directly and the other capacitively - without additional effort. In this way, you can prevent ground loops occurring if a shield is connected directly to FE on both sides. No matter at what side you connect the shield, you must connect all wires to connector 2. Use at least one connector with shield connection when connecting the I/O device. /G36 /G38 /G37 /G38 /G42 /G30 /G30 /G35 /G36 /G38 /G37 /G38 /G42 /G30 /G30 /G36

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 8

8 Connection examples

8.1 Comparison of the connection examples in Figure 5 to Figure 9

For connection, 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 termination resistors at both ends. – For an RS-422 point-to-point connection, the receive signals on every device must be fitted with termination resistors. Operating mode Special remark Shield connection Comment Required connectors per IB IL RS 485/422-PRO Example in RS-485 IB IL RS 485/422-PRO terminal as network end point Capacitive Termination resistor required Connector set Figure 5 RS-485 IB IL RS 485/422-PRO in the network center Capacitive/ direct – 2 shield connectors Figure 6 RS-485 IB IL RS 485/422-PRO terminal as network end point Direct Termination resistor required Connector set Figure 7 RS-422 Shield connected capacitively to FE Capacitive Termination resistor required Connector set Figure 8 RS-422 Shield connected directly Direct Termination resistor required Connector set Figure 9 The connector set consists of a shield connector and a standard connector.

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 9

8.2 RS-485: Terminal as network end point

Figure 5 RS-485 interface wiring: IB IL RS 485/ 422-PRO ... as the end point of a network, data line shield connected to FE using a capacitor

8.3 RS-485: Terminal in the network center

Figure 6 RS-485 interface wiring: IB IL RS 4 85/422-PRO ... in the center of a network, data line shield directly and connected capacitively to FE Connect the shield to FE using a capacitor. D RS485/422 TR RxD TxD 6199B008 Connector 12 RS 485 RS 485 RS 485 TxD+ TxD- RxD- 1.1 2.1 1.2 2.2 R+ 1.3 2.3 RxD+ Inline connector (connector 2) IB IL RS 485/422-PRO ... Transmit/receive data (positive) Transmit/receive data (negative) Termination resistor connection via R+ and R- D RS485/422 TR RxD TxD 6199B009 Connector 12 RS 485 RS 485 RS 485 TxD+ TxD- RxD- 1.1 2.1 1.2 2.2 R+ 1.3 2.3 RxD+ Inline connector (connector 2) IB IL RS 485/422-PRO ... Transmit/ receive data (positive) Transmit/ receive data (negative) RS 485RS 485

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 10

8.4 RS-485: Terminal as network end point

Figure 7 RS-485 interface wiring: IB IL RS 485/ 422-PRO ... as the end point of a network, data line shield connected directly to FE

8.5 RS-422: Shield connected capacitively to the terminal

Figure 8 RS-422 interface wiring: Data lin e shield connected capacitively to FE Connect the shield directly to FE. D RS485/422 TR RxD TxD 6199B010 Connector 12 RS 485RS 485 Inline connector (connector 2) IB IL RS 485/422-PRO ... Transmit/receive data (positive) Tranmit/receive data (negative) Termination resistor connection via R+ and R- TxD+ TxD- RxD- 1.1 2.1 1.2 2.2 R+ 1.3 2.3 RxD+ D RS485/422 TR RxD TxD 6199C011 Connector RS 422 TxD+ TxD- RxD- 1.1 2.1 1.2 2.2 R+ 1.3 2.3 RxD+ Inline connector (connector 2) IB IL RS 485/422-PRO ... Receive data (positive) Receive data (negative) Termination resistor connection via R+ and R- Transmit data (positive) Transmit data (negative) Receive data (positive) Receive data (negative) Transmit data (positive) Transmit data (negative) Termination resistor connection RS-422 device

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 11

8.6 RS-422: Shield directly connected to the terminal

Figure 9 RS-422 interface wiring: Data line shield directly connected to FE

9 Programming data/configuration

9.1 Local bus (INTERBUS)

9.2 Other bus systems

D RS485/422 TR RxD TxD 6199C012 Connector RS 422 TxD+ TxD- RxD- 1.1 2.1 1.2 2.2 R+ 1.3 2.3 RxD+ Inline connector (connector 2) IB IL RS 485/422-PRO ... Receive data (positive) Receive data (negative) Termination resistor connection via R+ and R- Transmit data (positive) Transmit data (negative) Receive data (positive) Receive data (negative) Transmit data (positive) Transmit data (negative) Termination resistor connection RS-422 device ID code BF hex (191dec) Length code 06 hex Process data channel 96 bits Input address area 12 bytes Output address area 12 bytes Parameter channel (PCP) 0 bytes Register length (bus) 12 bytes For the programming data/configuration data of other bus systems, please refer to the corresponding electronic device data sheet (e.g., GSD, EDS).

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 12

10 Data storage and transmission

The terminal stores the received serial data in an intermediate buffer until it is fetched 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 peers.

10.1 Overview of supported protocols

10.2 Transparent protocol

If the transparent protocol is used, serial data is transmitted through 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 further characters are ignored.

10.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 upon terminal configuration. Serial data sent from the serial interface can only be read by the user if the terminal has received the first and second delimiters. Both delimiters confirm that the serial data has been received without error and the maximum data length of 11 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 with 11 bytes each are available. If the buffer size of 11 bytes is exceeded, without the two delimiters being detected, the buffer is overwritten again. The transmit FIFO consists of 1023 bytes. The delimiters are attached to, and stored with, the data to be sent.

10.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 end characters, as in the end-to- end protocol. As soon as a new data block is received, the previous one is overwritten. This is achieved by means of two buffers, which are written alternately. In this way, there is always one buffer ready to receive serial data while the second buffer stores the most recently received data block. A data block is only regarded as 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 11 bytes is exceeded, without the two delimiters being detected, the buffer is overwritten again. When transmitting serial data, the same is valid as 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. Protocol Receive buffer Transmit memory Special features when receiving Transpar- ent 4096 bytes 1023 bytes End-to- end 25 buffers with 11 bytes each 1023 bytes (including end characters) Two end characters are filtered out Dual buffer 2 buffers with 11 bytes each 1023 bytes (including end characters) Only stores the most recently received data, end characters are filtered out 3964R 25 buffers with 11 bytes each 5 buffers with 330 bytes each Data exchange with software handshake, time monitoring, and checksum XON/ XOFF 4096 bytes 1023 bytes Software handshake Movilink 11 bytes 11 bytes Data exchange with time monitoring and check sum The Movilink protocol is available for firmware Version 1.10 or later.

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 13 10.5 3964R protocol This protocol, developed by Siemens, is the most complex. It uses start and end identification, checksum and time monitoring. 5 buffers are available for transmitting, 25 buffers are available for receiving. 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).

10.6 XON/XOFF protocol

This protocol operates like the transparent protocol, however, using a software handshake. Data transmission with this protocol is controlled by the XON and XOFF characters. XON is set to 11 hex 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 5 bytes. As soon as more memory becomes available again, the module will transmit a single XON. Transmission of serial data is not filtered. Any characters, which occur with the code defined for XON and XOFF, are thus 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. With the XON/XOFF protocol this function is only completely available for the RS-422 interface. It can be discussed if using the protocol for the RS-485 interface is useful as the latter is a half duplex connection, which enables either to transmit or to receive data. However, with the XON/XOFF protocol the receiver can respond with a XOFF at any time when transmitting characters. Reception of this control character by the transmitter is thus not ensured.

10.7 Movilink protocol

The terminal is the Movilink master in the Movilink protocol. After transmission of a telegram the terminal waits for a maximum of 500 ms for the response. After the response was received, the response data is available in the input data. Only then can the next telegram be sent. A delimiter is placed ahead of the process data when a Movilink telegram is being sent. The calculated checksum is added behind the process data. When the data is received, the delimiter and the checksum are filtered out before the data is transmitted over the bus. Transmit or receive errors are reported when a transmission timeout or a negative checksum comparison occurs. Transmit and receive buffer have a size of 11 bytes each. Character delay time: 220 ms Acknowledgment delay time: 2 s Block waiting time: 10 s Number of attempts to establish a connection: 6 As the RS-485 interface is a half duplex interface a waiting time (slave response time) is kept between data transmission and reception. It is 11 bits and depends on the baud rate.

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 14

11 Process data

The terminal process image comprises six data words each in input and output direction. The terminal has six process data words. The command is used to determine the function. The actually transmitted data depends on the command.

11.1 Word 0 general

Err: error x = 0 or 1; the assignment depends on the command. 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 – Buffer characters (not in the Movilink protocol) – Read characters (not in the Movilink protocol) Here, bit 14 is used for toggling. For the assignment of the illustrated (word.bit) or (byte.bit) view to your INTERBUS control system or computer system, please refer to the DB GB IBS SYS ADDRESS data sheet. W o r d 0 1234 5 Byte in the Motorola format 0 123456789 1 0 1 1 Byte in the Intel format 1 032547698 1 1 1 0 OUT Command/ parameter Data Data Data Data Data Data Data Data Data Data Data IN Status parameter Data Data Data Data Data Data Data Data Data Data 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). 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0 Command OUT

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Err Command I N p a r a m e t e rxxxxxxxx Code (Bin) Code (hex) (with bit 15 = 0) Command 000 0 Read status bits. Input word 1 contains the number of characters received. 001 1 Transmit characters 010 2 Buffer characters (not in the Movilink protocol) 011 3 Read characters. Parameter = C hex: Read FW version, Parameter = Dhex: Read configuration 100 4 Write configuration 101 5 Toggle command 1: transmit characters 110 6 Toggle command 2: Buffer characters (not in the Movilink protocol) 111 7 Toggle command 3: Read characters (not in the Movilink protocol)

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 15 11.2 "Read Status Bits" command Figure 10 Format of the process data word 0 07654321 6985D001 Receive error Transmit error Number of received data 0 00 Control word 0: No action 1: Reset receive error 0: No action 1: Reset transmit error 0: Empty 1: Not empty Receive buffer Receive error 0: No error 1: Error Transmit error 0: No error 1: Error Receive buffer 0: Empty 1: Not empty Transmit buffer 0: Not full 1: Full Transmit butter 0: Not full 1: Full Reserved Reserved0 00 815 14 13 12 11 10 9 Status word MSB LSB 07654321815 14 13 12 11 10 9 MSB LSB In the Movilink protocol bits 8 to 11 in the status word have no meaning. Bit/status Effect Protocol Bit 0 = '1' The receive buffer is not empty, there are characters to be read. All excluding Movilink Bit 1 = '1' The receive error indicates that a 3964R te legram could not be received without error after six transmit attempts by the serial peer or after the block waiting time had elapsed. 3964R The receive error indicates that – a parity error occurred while the response was received, – the first character received is not SD2, – the checksum test was negative, – the number of received characters is uneq ual to the number of transmitted characters. Movilink Bit 2 = '1' The transmit error indicates that a 3964R telegram could not be transmitted from the module to the serial peer without error after six transmit attempts. The telegram was rejected. 3964R The transmit error indicates, that the set timeout of 500 ms elapsed and a response has not yet been received. Movilink Bit 3 = '1' Reserved Bit 4 = '1' The receive buffer is full: Transparent, end-to-end, 3964R, XON/ XOFF Transparent and XON/XOFF protocol: Residual capacity: <15 characters 3964R and end-to-end protocol: Residual capacity: none

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 16 With the "Read Status Bits" command the content of the input data is continuously updated. Unlike with other commands toggling is not required. Bit 5 = '1' The transmit buffer is full: All excluding Movilink3964R protocol: Residual capacity: none Dual buffer, transparent, end-to-end, and XON/XOFF protocol: Residual capacity: ≤30 characters Bit 6 = '1' The transmit buffer is not empty, ther e are characters to be transmitted. All excluding Movilink The transmit buffer is not empty, there are characters to be transmitted. This bit is set during the entire data transmission. Movilink Bit 7 = '1' Reserved Bits 8 to 11 Number of characters received. If the code = F hex, more than 14 characters have been received. All excluding Movilink Bit/status Effect Protocol Both error bits (bits 1 and 2) are not automatically reset. They can only be reset by the process data output word. In the transparent and XON/XOFF protocols, the input word 1 contains the total number of characters received.

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 17 11.3 "Transmit Characters" command Process data is stored in the transmit memory and then directly transmitted via RS-485 or RS-422. A maximum of eleven characters can be transmitted. The OUT parameter determines the number of characters to be transmitted. Characters stored in the intermediate buffer are transmitted first. After the command has been executed successfully the intermediate buffer is cleared. Process data assignment for the "Transmit Characters" command with eleven characters (C1 - C11) Reasons for an error bit set: – OUT parameter = 0 and intermediate buffer empty – OUT parameter >11 – Not enough space in the transmit memory – Not enough space in the intermediate buffer "Transmit Characters" command for the Movilink protocol After the command 1 hex or 5hex was received over the bus, the terminal generates a Movilink telegram. The process data length is specified in the first byte (in the example Ahex = 10 bytes). The SD1 start delimiter is placed ahead of the process data in the telegram. The calculated checksum is added behind the process data. The checksum is calculated over the complete telegram. Process data assignment for the "Transmit Characters" command with 10 characters (C1 - C10) The command is only acknowledged over the bus, when either the response of the Movilink peer was received or the timeout period of 500 ms elapsed. When there is a positive acknowledgment (error bit = 0) the process input data contains the response data. Start delimiter and checksum have been filtered out from the response. The start delimiter of the request telegram (SD1) and the response telegram (SD2) are defined as follows: SD1 = 02 hex, SD2 = 1Dhex. The error bit (bit 15 in the status word, i.e. in the first word received (Wort 0)) indicates the acknowledgment: Error bit = 0: Data transmission is okay, the data behind byte 1 is response data of the Movilink peer. Error bit = 1: An error has occurred. It may have several causes: – The length information in the output data is equal to 0 or larger than 11. – The Movilink response is invalid; The options are as follows: – The first character is unequal SD2. – The checksum comparison is negative. – The number of received characters is unequal to the number of transmitted characters. – Parity errors occurred while the response was received. – The timeout period elapsed, which means that no response was received within 500 ms. Set the toggle bit for the next transfer in the command. If command 1 was used before, command 5 will be sent. Then command 1 again. 11.4 "Store Characters Temporarily" command The transmit data is stored in an intermediate buffer, which can store 330 characters. No characters are transmitted. The OUT parameter determines the number of characters. The "Transmit Characters" command is used for trans- mitting the data stored temporarily. In this way character blocks of up to 330 characters can be transmitted. They are divided over 20 telegrams with 11 characters each. Reasons for an error bit set: – OUT parameter = 0 or >11 – Not enough space in the intermediate buffer 11.5 "Read Characters" command This command is used to read a maximum of eleven characters. The IN parameter contains the number of valid characters available in the input data. Process data assignment for the "Read Characters" command with eleven characters (C1 - C11) Word 0 1234 5 Byte 0 1234567891 01 1 OUT 1Bhex C C C C C C C C C Word Byte 0 1 2 3 4 5 6 7 8 9 10 11 OUT 1Ahex C1 C2 C3 C4 C5 C6 C7 C8 C9C10 _ Delimiter Address Type User data Check- sum Movilink telegram 6985A003 0 12 3 4 5 Output data Word 0 1234 5 Byte 0 1234567891 01 1 IN 3Bhex C C C C C C C C C

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 18 11.6 "Write Configuration" command Process data assignment for the "Write Configuration" command Output words 0 to 5 Output word 1 Figure 11 Output word 1 in the "Write Configuration" command Element value range The error pattern contains the character that is written into the FIFO, if a character was received with an error (not valid for the 3964R protocol). Reasons are e.g. parity errors, exceeded value range, superimposed noise. In the transparent and XON/XOFF protocols, the pattern is also used if the receive FIFO is full and further characters are received. Word 0 1 2 3 4 5 Byte 0 1 2 3 4 5 6 7 8 9 10 11 OUT 40hex Error pattern Output type/protocol Baud rate/data width 1st delimiter 2nd delimiter Direct baud rate Reserved Reserved Reserved IN The options in bold are default settings. Error pattern Code Meaning 24hex $ xxhex Any character 6985B002 Output type: 0: RS 485 1: RS 422 Baud rate Data width 6 5 4 3 21 07 Byte 3 Protocol 6 5 4 3 21 07 Byte 2 Output type Code Meaning 0hex RS-485 1hex RS-422 Protocol Code Meaning 00hex Transparent 01hex End-to-end 02hex Dual buffer 03hex 3964R with low priority 04hex 3964R with high priority 05hex XON/XOFF 06hex Movilink The Movilink protocol is available for firmware Version 1.10 or later. Baud rate Code Value 00hex 110 baud 01hex 300 baud 02hex 600 baud 03hex 1200 baud 04hex 1800 baud 05hex 2400 baud 06hex 4800 baud 07hex 9600 baud 08hex 19200 baud 09hex 38400 baud 0Dhex Directly, basis 500 kbaud 0Ehex Directly, basis 62.5 kbaud 0Fhex Directly, basis 15625 baud The specified baud rates of 110 baud to 38400 baud are adequate for most applications. However, you can freely choose the baud rate by means of direct programming. For this, use the hex, 0E hex and 0Fhex baud rate codes in the output word 1, see "Direct Baud Rate (DBC)" on page 19.

IB IL RS 485/422-PRO ... 6985_en_05 PHOENIX CONTACT 19 The first delimiter and the second delimiter contain the end characters for the dual buffer and the end-to-end protocols. Reasons for an error bit set: – Using a reserved code – Setting a reserved bit – Baud rate 110 baud or 300 baud in the 3964 protocol Direct Baud Rate (DBC) Choose direct programming of the baud rate in the output word 1 by means of the 0D hex, 0Ehex and Fhex baud rate codes. You can select a basic clock for the baud rate. The actual baud rate is calculated according to the following formula: Specify DBC in the output byte 6. To determine DBC change the equation to read: Example: The baud rate is 15625 baud. A basic baud rate of 500 kbaud (code 0Dhex) is chosen. Determine the direct baud rate: An example for the first four output words is: 40 00 00 D2 00 00 1F hex. Data width Code Meaning Representation in CMD/PC WORX Data bits Parity Stop bits 00hex 7e v e n1 7 data bits, even parity, 1 stop bit 01hex 7o d d1 7 data bits, odd parity, 1 stop bit 02hex 8e v e n1 8 data bits, even parity, 1 stop bit 03hex 8o d d1 8 data bits, odd parity, 1 stop bit 04hex 8N o n e1 8 data bits, without parity, 1 stop bit 05hex 7N o n e1 7 data bits, without parity, 1 stop bit 06hex 7e v e n2 7 data bits, even parity, 2 stop bits 07hex 7o d d2 7 data bits, odd parity, 2 stop bits 08hex 8e v e n2 8 data bits, even parity, 2 stop bits 09hex 8o d d2 8 data bits, odd parity, 2 stop bits 0Ahex 8N o n e2 8 data bits, without parity, 2 stop bits 0Bhex 7N o n e2 7 data bits, without parity, 2 stop bits First delimiter Code Meaning 0Dhex Carriage Return (CR) xxhex Any character Second delimiter Code Meaning 0Ahex Line Feed (LF) xxhex Any character After successful configuration the characters for the receive and transmit FIFO are reset. In this way, all transmit and receive data that have not yet been processed will be deleted. Baud rate = basic clock / (DBC + 1) DBC = basic clock / baud rate - 1 DBC = (500000 baud / 15625 baud) - 1 = 31dec = 1Fhex Programming of the direct baud rate theoretically enables a maximum value of 500 kbaud. Proper operation of the terminal is tested and guaranteed for up to 38400 baud. Operation with higher baud rates depends on the application.

IB IL RS 485/422-PRO ... 6985_en_05 20PHOENIX 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 Example for a configuration with transparent protocol – Default: Transparent protocol – Baud rate: 19200 baud – Data width: 8 data bits with odd parity and one stop bit – Configuration (in hex): 4000 0083 0000 0000 Example for a configuration with Movilink protocol – Default: Movilink protocol – Baud rate: 9600 baud – Data width: 8 data bits with odd parity and one stop bit – Configuration (in hex): 4000 0672 0000 0000 11.7 "Read Configuration" command Process data assignment for the "Read Configuration" command 11.8 "Read Firmware Version" command With a control word of 3C00 hex, the second input word supplies the firmware version and the type code. Type code 7hex is identical with the type code of IB IL RS 485/422 .... W o r d 012345 B y t e0123456789 1 0 1 1 Meaning 40hex Error pattern Output type/protocol Baud rate/data width 1st delimiter 2nd delimiter Direct baud rate Reserved Reserved Reserved OUT 40 00 00 83 00 00 00 – – – – – Word 0 1 2 3 4 5 B y t e0123456789 1 0 1 1 OUT 3Dhex x x x x x x x x x x x IN 3Dhex Error pattern Output type/protocol Baud rate/data width 1st delimiter 2 nd delimiter Direct baud rate 1 5 1 4 1 3 1 2 1 1 1 0 9876543210 Firmware version, e.g.,100hex Type code: 7hex