Data Sheet DB EN IB IL RS 485/422-PRO - Digi-Key
Contents
1. Code Command Motorola gt hex format with bit 15 0 Read status bits Input word 1 contains the number of characters received Transmit characters 010 2 Buffer characters not in the Movilink protocol 011 3 Read characters Parameter Chex Read FW version Parameter Dhex Read configuration The byte representation in the Motorola format also called Big Endian high order byte at starting address corresponds to the INTERBUS transmit characters standard representation All byte representations 110 Toggle command 2 in the data sheet have this format Buffer characters The byte representation in the Intel format is also not in the Movilink protocol called Little Endian low order byte at starting 111 7 Toggle command 3 address Read characters not in the Movilink protocol The command is used to determine the function The actually transmitted data depends on the command Command toggling the Intel format Command parameter parameter Command toggling is used to execute a command ona 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 6985 _en_05 PHOENIX CONTACT 14 IB IL RS 485 422 PRO 11 2 Read Status Bits command Control word2. Dual buffer 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 PHOENIX CONTACT 12 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 Character delay time 220 ms Acknowledgment delay time 2s Block waiting time 10s Number of attempts to establish aconnection 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 As the RS 485 interface is a half duplex interface a waiting time slave response t
3. Interface O O 130 O G RD TxD 24 V Us 24 V Um oo GND R 1 L TN D l Oo XZ V7 A 6199C004 Figure 2 Internal wiring of the terminal points Key Protocol chip bus logic including RS 485 422 RS 485 422 interface voltage conditioning Diagnostic and status indicators with iL Capacitor function information T yq Optocoupler O Resistor DC DC converter with electrical m Ground electrically isolated from ground of the ES isolation communications power UL Microprocessor Hardware version 01 or later GND is assigned to Other symbols used are explained in the terminal point 2 3 of the IB IL RS 485 IL SYS INST UM E user manual or in the Inline 422 PRO PAC terminal In all previous system manual for your bus system 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 6985_en_05 PHOENIX CONTACT 6 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 witha termination resistor at both most remote points of the RS 485 network To connect them to the Inline terminal use the te
4. 7 2 Figure 4 Use at least one connector with shield connection when connecting the I O device Shield connected capacitively to FE 6878B005 Position of the shield connector to connect the shield capacitively to FE Shield connected directly to FE 6878B006 Position of the shield connector to connect the shield directly to FE PHOENIX CONTACT 7 IB IL RS 485 422 PRO 8 Connection examples 8 1 Comparison of the connection examples in Figure 5 to Figure 9 Operating Special remark Shield Comment Required connectors connection per IB IL RS 485 422 PRO RS 485 IB IL RS 485 422 PRO terminal Capacitive Termination resistor Connector set Figure 5 as network end point required RS 485 IB IL RS 485 422 PRO in the Capacitive 2 shield connectors Figure 6 network center direct as network end point required FE required required The connector set consists of a shield connector and a standard connector 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 AnRS 485 network must be equipped with termination resistors at both ends Foran RS 422 point to point connection the receive signals on every device must be fitted with termination resistors 6985_en_05 PHOENIX CONTACT 8 8 2 RS 485 Terminal as network end point a Connect the shield to FE using a capacitor C
5. IB IL RS 485 422 PRO 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 RS485 422 Termination resistor Termination resistor connection via connection R and R Inline connector connector 2 6199C011 Figure 8 RS 422 interface wiring Data line shield connected capacitively to FE 6985_en_05 IB IL RS 485 422 PRO PHOENIX CONTACT 10 IB IL RS 485 422 PRO 8 6 RS 422 Shield directly connected to the terminal Connector 2 IB IL RS 485 422 PRO 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 Termination resistor Termination resistor connection via connection R and R Inline connector connector 2 61990012 Figure 9 RS 422 interface wiring Data line shield directly connected to FE 9 Programming data configuration data 9 1 Local bus INTERBUS BF no Ot Output address area 12 bytes Parameter channel PCP Register length bus 12 bytes 9 2 Other bus systems For the programming data configuration data of other bus systems please refer to the corresponding electronic
6. MSB LSB jajil ujojojs z s s 4jsjeli o ofofo Receive error 0 No action 1 Reset receive error Transmit error 0 No action 1 Reset transmit error Status word MSB LSB japs fof olsl 7fels s sieiijo Number of Reserved Reserved received Transmit buffer Receive buffer data 0 Empty 0 Empty 1 Not empty 1 Not empty Transmit butter Receive error 0 Not full 0 No error 1 Full 1 Error Receive buffer Transmit error O Not full 0 No error 1 Full 1 Error 6985D001 Figure 10 Format of the process data word 0 In the Movilink protocol bits 8 to 11 in the status word have no meaning Bitstatus Efect OOOO O o Bit 0 1 The receive buffer is not empty there are characters to be read All excluding Movilink The receive error indicates that a 3964R telegram could not be received without error after six 3964R transmit attempts by the serial peer or after the block waiting time had elapsed Movilink 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 unequal to the number of transmitted characters to the serial peer without error after six transmit attempts The telegram was rejected The transmit error indicates that the set timeout of 500 ms elapsed and a response has not yet been received es 1 Reeva OOOO S The receive buffer is full Transparent
7. Transparent and XON XOFF protocol Residual capacity lt 15 end to end characters 3964R XON XOFF 3964R and end to end protocol Residual capacity none 6985_en_05 PHOENIX CONTACT 15 IB IL RS 485 422 PRO Bivstatus ete OOOO O Protocol The transmit buffer is full All excluding 3964R protocol Residual capacity none Movilink Dual buffer transparent end to end and XON XOFF protocol Residual capacity lt 30 characters Movilink The transmit buffer is not empty there are characters to be transmitted This bit is set during the entire data transmission pt7 T Reeves OOOO U O Number of characters received If the code Fhex more than 14 characters have been received Movilink With the Read Status Bits command the content of the input data is continuously updated Unlike with other commands toggling is not required 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 6985_en_05 PHOENIX CONTACT 16 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
8. rate 9600 baud Data width 8 data bits with odd parity and one stop bit Configuration in hex 4000 0672 0000 0000 6985_en_05 IB IL RS 485 422 PRO 11 7 Read Configuration command Process data assignment for the Read Configuration command Error pattern 1st delimiter 2 nd delimiter 11 8 Read Firmware Version command With a control word of 3C00 the second input word supplies the firmware version and the type code 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Firmware version e g 100ne Type code Thex Type code 7hex is identical with the type code of IB IL RS 485 422 PHOENIX CONTACT GmbH amp Co KG 32823 Blomberg Germany Phone 49 0 5235 3 00 20 PHOENIX CONTACT P O Box 4100 Harrisburg PA 17111 0100 USA Phone 717 944 1300 www phoenixcontact com
9. the command has been executed successfully the intermediate buffer is cleared Process data assignment for the Transmit Characters command with eleven characters C1 C11 wea 0 e 0 42 3 4 5 6 7 8 9 10 7 correla 54 5 6 7 8 9 0 Or OUT 1Bhex it bie eee eal Reasons for an error bit set OUT parameter 0 and intermediate buffer empty OUT parameter gt 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 1pex 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 Apex 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 Output data OUT 1A C1 C2 c3 C4 c5 C6 C7 C8 C9C10 Movilink telegram data 6985A003 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
10. IB IL RS 485 422 PRO Inline terminal for serial data transmission AUTOMATION Data Sheet 6985 en 05 PHOENIX CONTACT 03 2008 1 Description Features ae l E l l A serial I O channel RS 485 or RS 422 The terminal is designed for use within an Inline station It is l used to operate standard I O devices with serial interfaces Various protocols supported on a bus system Transmission speed can be set up to 38400 baud Number of data bits stop bits and parity can be set Difference between IB IL RS 485 422 and 4kbyte receive buffer and 1 kbyte transmit buffer BIERS AAAA ER Parameterization and data exchange via the bus using IB IL RS 485 422 process data Parameterization and data exchange are carried out via the bus using PCP services IB IL RS 485 422 PRO Parameterization and data exchange are carried out via the bus using process data This allows faster communication times than with the IB IL RS 485 422 a 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 A conversion table is available on the Internet at www download phoenixcontact com general 7000_en_00 pdf a This data sheet is valid for the products listed on the following page DOG0OCI M000 Weonnca ODE INSPIRING INNOVATIONS 2 Ordering data Products D
11. _en_05 Type Order No Pcs Pkt IB IL AO CNT PLSET 2732664 1 set IB IL SCN 6 SHIELD 2736353 5 Type Order No Pcs PKt ILSYS INST UME 2698737 1 DB GB IBS SYS ADDRESS 9000990 1 24 4 mm x 136 mm x 72 mm with connectors 90 g without connectors 135 g with connectors Process data mode with 6 words 2 and 3 wire technology 25 C to 55 C 25 C to 85 C 10 to 95 according to DIN EN 61131 2 70 kPa to 106 kPa up to 3000 m above sea level IP20 according to IEC 60529 Class 3 according to EN 61131 2 IEC 61131 2 Spring cage terminals 0 2 mm to 1 5 mm solid or stranded 24 16 AWG PHOENIX CONTACT Pcs Pkt i 2 IB IL RS 485 422 PRO 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 Q typical Permissible input differential voltage 5 7 V maximum a Owing to the 120 Q termination resistance 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 Q load 2 0 V minimum Output differential voltage with 54 Q load 1 5 V minimum Short circuit output current 80 mA typical 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 t
12. device data sheet e g GSD EDS 6985_en_05 PHOENIX CONTACT 11 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 Transmit memory 10 1 Overview of supported protocols Special features when Protocol Receive buffer receiving ent End to 25 buffers 1023 bytes Two end end with 11 bytes including end characters are each characters filtered out Dual 2 buffers with 1023 bytes Only stores the buffer 11 bytes including end most recently each characters received data end characters are filtered out 3964R 25 buffers 5 buffers with Data exchange with 11 bytes 330 bytes with software each handshake time monitoring and checksum XON 4096 bytes 1023 bytes Software XOFF 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 10 2 lf 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 Transparent protocol The transmit FIFO First In First Out memory can store 1023 bytes 1 kbyte and the receive FIFO can stor
13. e 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 6985_en_05 IB IL RS 485 422 PRO 10 3 The serial data is conditioned for the end to end protocol 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 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
14. ect programming of the baud rate in the output word 1 by means of the ODhex OEne and Fre baud rate codes You can select a basic clock for the baud rate The actual baud rate is calculated according to the following formula Baud rate basic clock DBC 1 Specify DBC in the output byte 6 To determine DBC change the equation to read DBC basic clock baud rate 1 Example The baud rate is 15625 baud A basic baud rate of 500 kbaud code ODpe is chosen Determine the direct baud rate DBC 500000 baud 15625 baud 1 3149 1 Fhex An example for the first four output words is 40 00 00 D2 00 00 1F hex i 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 PHOENIX CONTACT 19 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 ae ia E NO Error pattern Baud rate data width 1st delimiter 2nd delimiter Direct baud rate Reserved Reserved Reserved x lt E lt OUT 40 00 00 83 00 00 00 DD ES ice iad es E Example for a configuration with Movilink protocol Default Movilink protocol Baud
15. 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 The specified baud rates of 110 baud to 38400 baud are adequate for most applications However you can freely choose the baud rate by m means of direct programming For this use the ODhex OE hex and OF pe baud rate codes in the output word 1 see Direct Baud Rate DBC on page 19 6985 _en_05 PHOENIX CONTACT 18 a OZ hex even PB ee p 8 Nme o 7 od n 8 om C e e First delimiter Carriage Return CR Line Feed LF Any character The first delimiter and the second delimiter contain the end characters for the dual buffer and the end to end protocols 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 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 6985_en_05 even 1 1 IB IL RS 485 422 PRO Data width Meaning Representation in CMDIPC WORX 7 data bits even parity 1 stop bit 7 data bits odd parity 1 stop bit 7 data bits without parity 2 stop bits Direct Baud Rate DBC Choose dir
16. escription Inline terminal for serial data transmission complete with accessories connector and labeling fields transmission speed 500 kbaud Inline terminal for serial data transmission without accessories transmission speed 500 kbaud Inline terminal for serial data transmission complete with accessories connector and labeling fields transmission speed 2 Mbaud IB IL RS 485 422 PRO Type Order No IB IL RS 485 422 PRO PAC 2863627 IB IL RS 485 422 PRO 2863707 IB IL RS 485 422 PRO 2MBD PAC 2878887 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 Connector set with a standard connector and a shield connector Shield connector Documentation Description Automation Terminals of the Inline Product Range user manual INTERBUS Addressing data sheet 3 Technical data General data Housing dimensions width x height x depth Weight Operating mode Connection method for sensors Permissible temperature operation Permissible temperature storage transport Permissible humidity operation storage transport Permissible air pressure operation storage transport Degree of protection Class of protection Connection data for connectors Connection type Conductor cross section 6985
17. filtered out from the response 6985_en_05 pt 2 at 4 5 IB IL RS 485 422 PRO The start delimiter of the request telegram SD1 and the response telegram SD2 are defined as follows SD1 02hex 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 O 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 willbe 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 characte
18. going remote bus 7 5 V supply bus logic RS 485 422 interface 7 5 V supply bus logic RS 485 422 interface 24 V supply I O RS 485 422 interface functional earth ground 7 5 V supply bus logic 24 V supply I O 7 5 V supply bus logic functional earth ground 24 V supply I O functional earth ground IB IL RS 485 422 PRO Test voltage 500 V AC 50 Hz 1 min 500 V AC 50 Hz 1 min 500 V AC 50 Hz 1 min 500 V AC 50 Hz 1 min 500 V AC 50 Hz 1 min 500 V AC 50 Hz 1 min 500 V AC 50 Hz 1 min 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 download phoenixcontact com or www eshop phoenixcontact com 4 Figure 1 Diagnostic status indicators and terminal point assignment 6199A003 Diagnostic status indicators and terminal point assignment 6985_en_05 4 1 Local diagnostic and status indicators Des Color Meaning PD Green Diagnostics Cm Yellow Terminal is receiving data from the connected device TxD Yellow Terminal is transmitting data to the connected device 4 2 Function identification Orange 2 Mbps white stripe in the vicinity of the D LED PHOENIX CONTACT 4 4 3 Terminal point assignment in the half duplex operating mode RS 485 Connec Terminal Data tor point direction Func
19. haracters 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 PHOENIX CONTACT 13 IB IL RS 485 422 PRO 11 Process data 11 1 Word 0 general l Control word The terminal process image comprises six data words each in input and output direction 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Command OUT x x x x x x x x a For the assignment of the illustrated word bit or parameter byte bit view to your INTERBUS control system or computer system please refer to the Status word DB GB IBS SYS ADDRESS data sheet 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 The terminal has six process data words Err error x 0 or 1 the assignment depends on the command
20. he module electronics through the bus coupler Connection method Potential routing Power consumption 500 kbps 2 Mbps Communications power UL 7 5V 7 5V Current consumption at UL 170 mA typical 260 mA maximum 185 mA typical 260 mA maximum Total power consumption Approx 1 275 W typical Approx 1 388 W typical 1 950 W maximum 1 950 W maximum All connections of the serial interface are short circuited A continuous short circuit can damage the device Therefore rule out continuous short circuits This terminal takes no current from the Uy and Us potential jumpers Q ATTENTION Defective module when continuously short circuited Power dissipation Power dissipation in the module PeL 1 4W Power dissipation of the housing PHou 1 4 W maximum within the permissible operating temperature Limitation of simultaneity derating Ta lt 50 C No derating Ta gt 50 C Ig 4A lo Total diagonal routing current I j Is GND Safety equipment None 6985_en_05 PHOENIX CONTACT 3 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 5 V supply incoming remote bus 7 5 V supply bus logic 5 V supply out
21. ime is kept between data transmission and reception It is 11 bits and depends on the baud rate 6985_en_05 IB IL RS 485 422 PRO 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 11hex and XOFF to 1 3hex 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 c
22. onnector 1 2 Transmit receive data positive Transmit receive data negative Termination resistor connection via R and R Inline connector connector 2 6199B008 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 Connector 1 2 IB IL RS 485 422 PRO a a Transmit D receive data aiil positive Transmit receive data negative RS485 422 Inline connector connector 2 RS 485 RS 485 RS 485 RS 485 RS 485 6199B009 Figure 6 RS 485 interface wiring IB IL RS 485 422 PRO in the center of a network data line shield directly and connected capacitively to FE 6985_en_05 IB IL RS 485 422 PRO PHOENIX CONTACT 9 8 4 RS 485 Terminal as network end point Connect the shield directly to FE Connector 1 2 IB IL RS 485 422 PRO Transmit receive data positive Tranmit receive data negative Termination resistor connection via R and R Inline connector connector 2 6199B010 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 Connector
23. rmination 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 witha 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 6985_en_05 IB IL RS 485 422 PRO 7 Connection notes 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 a 7 1 Figure 3
24. rs can be transmitted They are divided over 20 telegrams with 11 characters each Reasons for an error bit set OUT parameter 0 or gt 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 PHOENIX CONTACT 17 IB IL RS 485 422 PRO 11 6 Write Configuration command Process data assignment for the Write Configuration SUIRUUIVRE Output words 0 to 5 RS 485 RS 422 ooo o roa C Oe Dualo C Oke 89647 with high prioriy The Movilink protocol is available for firmware Version 1 10 or later Protocol Baud rate Datawidth Baudrate _ _ _ 0 RS 485 00 110 baud 1 RS 422 6985B002 a nex a00 au Figure 11 Output word 1 in the Write Configuration ues command O2hex 600 baud O3nex 1200 baud Element value range 1800 baud The options in bold are default settings OShex 2400 baud 4800 baud e e gt ol a Reserved OR ai O E h 1st delimiter 2nd delimiter Direct baud rate Reserved Reserved 07 hex O8hex O9hex ODhex OEhex OF nay Directly basis 15625 baud Error pattern Any character The error pattern contains the character that is written into the FIFO if a character was received with an
25. tional earth ground Ce a All other terminal fener coral of this connector are not fener coral TxD Reserved 2i TxD a aaa li data positive output Receive transmit data negative output ae alll Termination resistor positive or Termination resistor negative 1 4 2 4 Shield Shield connection Shield connection 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 6985_en_05 4 4 IB IL RS 485 422 PRO Terminal point assignment in the full duplex operating mode RS 422 Connec Terminal Data tor point direction Functional earth ground GND GND connector are not used ica positive a he fega o negative ree te positive Pee recat negative re esor posve resistor positive Termination resistor oa 14 24 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 a Observe the connection notes on page 7 PHOENIX CONTACT 5 IB IL RS 485 422 PRO 5 Internal circuit diagram V Local bus SS ove U D Uana L y7 y i VA tL A S Se uP tt 1 BN RS 485 422
Download Pdf Manuals
Related Search