2688666

AXL F RS UNI 1H Axioline F communication module for serial data transmission, 1 interface can be parameterized as RS-485/422 or RS-232 Data sheet 8533_en_04 1 © PHOENIX CONTACT 2018-03-26 Description The module is designed for use within an Axioline F station. The module 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 250,000 baud Parameterization via the PDI channel Device rating plate stored This data sheet is only valid in association with the UM EN AXL F SYS INST user manual. Make sure you always use the latest documentation. It can be downloaded from the product at phoenixcontact.net/products. AXL F RS UNI 1H 2 Table of contents 1 Description .............................................................................................................................. 1 2 Table of contents ..................................................................................................................... 2 3 Ordering data .......................................................................................................................... 3 4 Technical data ......................................................................................................................... 4 5 Internal circuit diagram ............................................................................................................ 6 6 Terminal point assignment....................................................................................................... 7 7 Connection notes .................................................................................................................... 8 8 Connection examples .............................................................................................................. 8 9 Local diagnostic and status indicators ................................................................................... 10 10 Serial interfaces..................................................................................................................... 12 11 Mass storage and transmission ............................................................................................. 13 12 Process data.......................................................................................................................... 15 13 Process data word 0 .............................................................................................................. 16 14 Commands ............................................................................................................................ 18 15 Parameter, diagnostics and information (PDI) ....................................................................... 21 16 Standard objects ................................................................................................................... 22 17 Application objects ................................................................................................................ 26 18 Device descriptions ............................................................................................................... 30 8533_en_04 PHOENIX CONTACT 2 / 30 AXL F RS UNI 1H 3 Ordering data Description Type Axioline F communication module for serial data AXL F RS UNI 1H transmission, 1 interface can be parameterized as RS-485/422 or RS-232 (including bus base module and connectors) Order No. Pcs./Pkt. 2688666 1 Accessories Type Order No. Pcs./Pkt. Axioline F bus base module for housing type H (Replacement item) AXL F BS H 2700992 5 Axioline F connector set (for e.g., AXL F DI16/1 1H) (Replacement item) AXL CNS 2L-O/D/UI/E1/E2 2700985 1 0829579 25 Zack marker strip, flat, in 10 mm pitch, unprinted, 10ZBF 10/5,8 AXL UNPRINTED 0829580 section, for individual labeling with M-PEN 0,8, X-PEN, or CMS-P1-PLOTTER (Marking) 50 Axioline shield connection set (contains 2 busbar holders AXL SHIELD SET and 2 SK 5 shield connection clamps) 2700518 1 Insert label, Roll, white, unlabeled, can be labeled with: EMT (35X28)R THERMOMARK ROLL, THERMOMARK ROLL X1, THERMOMARK ROLLMASTER 300/600, THERMOMARK X1.2, THERMOMARK S1.1, mounting type: snapped into marker carrier, lettering field size: 35 x 28 mm (Marking) 0801602 1 Zack marker strip for Axioline F (device labeling), in 2 x ZB 20,3 AXL UNPRINTED 20.3 mm pitch, unprinted, 25-section, for individual labeling with B-STIFT 0.8, X-PEN, or CMS-P1-PLOTTER (Marking) Order No. Pcs./Pkt. User manual, English, Axioline F: System and installation UM EN AXL F SYS INST Documentation - - User manual, English, Axioline F: Diagnostic registers, and error messages - - 8533_en_04 Type UM EN AXL F SYS DIAG PHOENIX CONTACT 3 / 30 AXL F RS UNI 1H 4 Technical data Dimensions (nominal sizes in mm) 122,4 54 126,1 35 Width 35 mm Height 126.1 mm Depth 54 mm Note on dimensions The depth is valid when a TH 35-7,5 DIN rail is used (according to EN 60715). General data Color traffic grey A RAL 7042 Weight 135 g (with connectors and bus base module) Mounting type DIN rail Ambient temperature (operation) -25 °C ... 60 °C Ambient temperature (storage/transport) -40 °C ... 85 °C Permissible humidity (operation) 5 % ... 95 % (non-condensing) Permissible humidity (storage/transport) 5 % ... 95 % (non-condensing) 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 Mounting position any (no temperature derating) Connection data: Axioline F connector Connection method Push-in connection Conductor cross section solid / stranded 0.2 mm² ... 1.5 mm² / 0.2 mm² ... 1.5 mm² Conductor cross section [AWG] 24 ... 16 Stripping length 8 mm Interface: Axioline F local bus Number 2 Connection method Bus base module Transmission speed 100 Mbps 8533_en_04 PHOENIX CONTACT 4 / 30 AXL F RS UNI 1H Interface: RS-232, RS-485, RS-422 Number of interfaces 1 Connection method Push-in connection Transmission speed 110 bps ... 250 kbps (can be parameterized) Transmission physics Copper Protocols supported Transparent, end-to-end, XON/XOFF, Modbus/RTU (master support) Input buffer 4 kByte Output buffer 1 kByte Data bits 5 ... 8 Stop bits 1 or 2 Termination resistor active, integrated Supply of the Axioline F local bus UBus The I/O is also supplied from the communications power UBus. The I/O supply is electrically isolated from the local bus. Supply voltage 5 V DC (via bus base module) Current draw typ. 200 mA max. 240 mA Configuration and parameter data in a PROFIBUS system Required parameter data 14 Byte Required configuration data 7 Byte Electrical isolation/isolation of the voltage areas Test section Test voltage 5 V supply (logic)/5 V supply (I/O) 500 V AC, 50 Hz, 1 min. 5 V supply (logic)/functional earth ground 500 V AC, 50 Hz, 1 min. 5 V supply (I/O)/functional earth ground 500 V AC, 50 Hz, 1 min. Error messages to the higher level control or computer system I/O supply failure Yes Mechanical tests Vibration resistance in acc. with EN 60068-2-6/ IEC 60068-2-6 5g Shock in acc. with EN 60068-2-27/IEC 60068-2-27 30g Continuous shock according to EN 60068-2-27/ IEC 60068-2-27 10g 8533_en_04 PHOENIX CONTACT 5 / 30 AXL F RS UNI 1H Conformance with EMC Directive 2014/30/EU Noise immunity test in accordance with EN 61000-6-2 Electrostatic discharge (ESD) EN 61000-4-2/ IEC 61000-4-2 Criterion B, 6 kV contact discharge, 8 kV air discharge Electromagnetic fields EN 61000-4-3/IEC 61000-4-3 Criterion A, Field intensity: 10 V/m Fast transients (burst) EN 61000-4-4/IEC 61000-4-4 Criterion B, 2 kV Transient overvoltage (surge) EN 61000-4-5/ IEC 61000-4-5 Criterion B, DC supply lines: ±0.5 kV/±0.5 kV (symmetrical/ asymmetrical) Conducted interference EN 61000-4-6/IEC 61000-4-6 Criterion A; Test voltage 10 V Noise emission test according to EN 61000-6-3 Radio interference properties EN 55022 Class B Approvals For the latest approvals, please visit phoenixcontact.net/products. 5 Internal circuit diagram Key: Local bus UBus µC Local bus µC 12x 5V D UI E1 E2 Axioline F local bus (hereinafter referred to as local bus) Microcontroller Optocoupler 5V FE RS-485 Diagnostic and status indicators RS-232 RS-485/422/232 interface RS-485 RS-232 5V DC/DC converter with electrical isolation Figure 1 Internal wiring of the terminal points Coupling network Electrically isolated areas 8533_en_04 PHOENIX CONTACT 6 / 30 AXL F RS UNI 1H 6 Terminal point assignment a1 a2 b1 b2 Figure 2 a1 a2 b1 b2 00 10 20 30 00 01 02 03 10 11 12 13 20 21 22 23 30 31 32 33 Connector 1 Terminal point a1, a2 b1, b2 03 13 23 33 Terminal point assignment Color Assignment Red Blue Not used (internally jumpered) Not used (internally jumpered) You can use connector 1 for potential routing of the 24 V supply voltage, however the voltage is not used by the module. Connector 2 Terminal point 00 10 20 Color Orange Orange Orange Signal TxD+ RxD+ RxD+ RS-485 Description Not used Transmit/receive data Transmit/receive data RS-422 Description Transmit data Receive data Receive data 30 Orange R+ Termination resistor Termination resistor 01 11 21 Orange Orange Orange TxDRxDRxD- Not used Transmit/receive data Transmit/receive data Transmit data Receive data Receive data 31 Orange R- Termination resistor Termination resistor Connector 3: RS-232 Terminal point Color 02 Orange 12 Orange 22 Orange Signal RxD RTS DTR Description Serial data input Request to send Data terminal ready 32 Orange DCD Data carrier detect 03 13 Orange Orange TxD CTS Serial data output Clear to send 23 Orange DSR 33 Orange GND 8533_en_04 Notes positive positive Positive; for external bridge to 30 Positive pole; for external bridge to 20 negative negative Negative; for external bridge to 31 Negative pole; for external bridge to 21 Request to send; handshake signal; output Startup request to the connected device; handshake signal; output Connected device ready to operate; handshake signal; input Permission to send; connected device ready to receive; handshake signal; input Data set ready Connected device ready to operate; handshake signal; input Ground for the serial interface PHOENIX CONTACT 7 / 30 AXL F RS UNI 1H 7 – – – 8 Connection notes Connect the shield to a busbar before the module Fit the receive signals of the RS-485 or RS-422 network with a termination resistor at the relevant end point. If you use the integrated termination resistor, the polarization of the data cable will also be active. Connection examples Operating mode RS-485 RS-485 RS-422 RS-232 RS-232 Special feature Module as the network end point Module in the network center Module is last receiver Four-wire handshake Without handshake Notes Termination resistor required   Termination resistor required     8.2 8.1 Image Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 RS-485: module in the network center RS-485: module as the network end point AXL F RS UNI ... AXL F RS UNI ... 1 00 10 TxD+ 00 2 01 11 02 12 1 TxD03 13 20 21 22 23 30 31 32 33 01 RxD+ 10 RxD- 11 RxD+ 20 RxD- 21 R+ 30 R- 31 RS-485 RS-485 RS-485 8533_en_04 TxD- 00 01 02 03 10 11 12 13 20 21 22 23 30 31 32 33 01 RxD+ 10 RxD- 11 RxD+ 20 RxD- 21 R+ 30 R- 31 RS-485 RS-485 RS-485 RS-485 Figure 4 Figure 3 RS-485 TxD+ 00 2 RS-485 interface wiring: Module as the network end point RS-485 interface wiring: Module in the network center PHOENIX CONTACT 8 / 30 AXL F RS UNI 1H RS-422 8.4 RS-232: with 4-wire handshake AXL F RS UNI ... TxD+ 00 TxD- 00 01 02 03 10 11 12 13 20 21 22 23 30 31 32 33 01 RxD+ 10 RxD- 11 03 10 11 12 13 20 21 22 23 30 31 32 33 RxD+ 20 RxD- 21 R+ 30 R- 31 Figure 6 RS-422 8.5 RS-232 interface wiring: four-wire handshake RS-232: without handshake RS-422 interface wiring, full duplex 00 01 02 03 10 11 12 13 20 21 22 23 30 31 32 33 TxD Figure 5 02 Figure 7 RxD 2 01 DTR 1 00 CTS TxD RxD 8.3 RS-232 interface wiring: without handshake For wiring without handshake, insert a bridge between terminal points 22 (DTR) and 13 (CTS). 8533_en_04 PHOENIX CONTACT 9 / 30 AXL F RS UNI 1H 9 Local diagnostic and status indicators D UI E1 E2 Figure 8 01 11 21 31 02 12 22 32 03 13 23 33 Local diagnostic and status indicators Connector 1 Designation Color D Red/ yellow/ green UI Green E1 Red E2 Red 8533_en_04 00 10 20 30 Channel errors are errors that can be associated with a channel. Periphery errors are errors that affect the entire module. Meaning State Description Diagnostics of local bus communication Run Green ON The device is ready for operation, communication within the station is OK. All data is valid. An error has not occurred. Active Green The device is ready for operation, communication within the station flashing is OK. The data is not valid. No valid data provided by the controller/ higher-level network. There is no error on the module. Device Flashing The device is ready for operation, communication within the station application not green/ is OK. active yellow Output data cannot be outputted and/or input data cannot be read. There is a fault on the periphery side of the module.. Ready Yellow ON The device is ready for operation but did not detect a valid cycle after power-up. Connected Yellow The device is not (yet) part of the active configuration. flashing Reset Red ON The device is ready for operation but has lost the connection to the bus head. Not connected Flashing The device is ready for operation but there is no connection to the red previously existing device. Power down OFF Device is in (power) reset. I/O voltage ON I/O supply voltage is present (generated from UBus). OFF I/O supply voltage is not present. Peripheral fault ON I/O error present. OFF No I/O error. Channel error ON Channel error present. OFF Channel error not present. PHOENIX CONTACT 10 / 30 AXL F RS UNI 1H Connector 2: RS-485/422 Designation 00 TxD Color Yellow 10 20 30 RS-485 Yellow 01 RxD Yellow 11 21 31 RS-422 Yellow Connector 3: RS-232 Designation 02 RxD Color Yellow 12 RTS Yellow 22 DTR Yellow 32 DCD Yellow 03 TxD Yellow 13 CTS Yellow 23 DSR Yellow 33 RS-232 Yellow 8533_en_04 State ON OFF ON OFF ON OFF ON OFF Description Module is transmitting data to the connected device Module is not transmitting data Not used Not used Module is parameterized for RS-485 Module is not parameterized for RS-485 Module is receiving data from the connected device Module is not receiving data Not used Not used Module is parameterized for RS-422 Module is not parameterized for RS-422 State ON OFF   ON OFF   ON OFF   ON OFF ON OFF   ON OFF ON ON OFF ON OFF Description Module is receiving data from the connected device Module is not receiving data Request to send Handshake signal is set by the module Handshake signal is not set Data terminal ready Handshake signal is set by the module Handshake signal is not set Data carrier detect Handshake signal is set by partner Handshake signal is not set Module is transmitting data to the connected device Module is not transmitting data Clear to send Handshake signal is set by partner Handshake signal is not set Data set ready Handshake signal is set by partner Handshake signal is not set Module is parameterized for RS-232 Module is not parameterized for RS-232 PHOENIX CONTACT 11 / 30 AXL F RS UNI 1H 10 Serial interfaces 10.1 RS-232 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. According to the standard, some form of DCE (data communication equipment) should be connected to the RS232 interface as a peer. DTE can also be connected. 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. Example: when using a 25-pos. standard connector the voltage between pin 2 (TxD) and pin 7 (GND) must be measured. In order to obtain the correct results, perform the measurement on the open cable end, i.e., if the modules are not connected together. RS-232 module handshake signals Any device with an RS-232 interface can be connected to the RS-232 interface on the module. Both the module and the device connected to the RS-232 interface can act as a transmitter and a receiver for data exchange. To avoid errors during data exchange, e.g., a buffer overrun, the handshake is used as a procedure for the mutual signaling of clear to receive and clear to send. 10.2 RS-485 (2-wire) In RS-485 mode, you can create a network with several devices using an existing network consisting of two signal cables. Use a twisted pair, common shielded data cable to connect the devices. Fit a termination resistor to the data cable at both end points of the RS-485 network. For this, you can use the integrated termination resistor in the module via connections R+ and R-. If you use the integrated termination resistor, the data cable will also be polarized in order to generate a defined cable idle level. This operating mode only supports half duplex transmission. Make sure that data is not sent simultaneously by several devices. 10.3 RS-422 In RS-422 mode, you can create a network with several devices using an existing network consisting of four signal cables. The cable pairs create a data forward path and a data return path. Specify a master for a structure with more than two devices. This master can send telegrams to all the other devices (slaves) and receive from them. The slaves can send telegrams between each other. Use a twisted pair, common shielded data cable to connect the devices. Fit the receive signals of the network with termination resistors at the relevant end point. Use the integrated termination resistor when connecting to the module. This operating mode supports full duplex transmission. The module supports the RTS, CTS, DTR, 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 module, i.e., from the point of view of the DTE. 8533_en_04 PHOENIX CONTACT 12 / 30 AXL F RS UNI 1H 11 Mass storage and transmission The module 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. 11.1 Supported protocols Protocol Receive memory Transparent End-to-end XON/XOFF 4096 bytes 3 buffers each with 340 bytes (PD) or 245 bytes (PDI) 4096 bytes Modbus/RTU 3 buffers each with 340 bytes (PD) or 245 bytes (PDI) PD PDI 11.2 Transmit memory 1023 bytes 1023 bytes (including end characters) 1023 bytes 3 buffers each with 340 bytes (PD) or 245 bytes (PDI) Special features when receiving 11.3 End-to-end protocol The serial data is conditioned for the end-to-end protocol. If serial data is sent from the bus side, two additional characters, the first and second delimiters, are attached for transmission to the serial interface. A block of serial data sent from the serial interface is only valid if the module has received the first and second delimiters. It is only then that the data can be read via the bus side. The delimiters are not forwarded to the higher-level bus with the user data, they are filtered out. Unlike in the transparent protocol, the receive memory is not organized as a FIFO but as a buffer. Three buffers are available. Two end characters are filtered out The size of the buffer depends on the parameterized data way: Software handshake   If the maximum buffer size is exceeded without the two delimiters being detected, the previous characters will be ignored and the buffer will be written again. Data exchange via process data Data exchange via PDI 340 bytes per buffer 245 bytes per buffer The transmit FIFO can store 1023 bytes (1 kbyte). The delimiters are attached to, and stored with, the data to be sent. Data exchange via process data Data exchange via PDI 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. 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 module 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. 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. 8533_en_04 PHOENIX CONTACT 13 / 30 AXL F RS UNI 1H 11.4 XON/XOFF protocol This protocol operates in the same way as the transparent protocol, but uses a software handshake. Data transmission with this protocol is controlled by the XON and XOFF characters. XON is preset to 11hex and XOFF to 13hex. If the module receives an XOFF, no more serial data will be sent until an XON is received. The module itself will transmit an XOFF if the available space in the receive memory is less than 15 bytes. As soon as more memory becomes available, the module will transmit a single XON. Transmission does not depend on the CTS input. Serial data is not filtered when it is transmitted. Any characters with the code defined for XON or XOFF are therefore 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 to the higher-lever system as data. Any characters with the XON or XOFF code are lost. Ensure that characters with these codes do not appear in the regular data stream. 11.5 Modbus/RTU (master support) Telegram structure Address 1 byte Function 1 byte Data 0 ... 244 bytes Data CRC 2 bytes Automatic generation and check In the Modbus environment, two time values play an important role: 1.5 characters, also referred to as t1.5 and 3.5 characters, also referred to as t3.5. The times for baud rates above 19,200 baud are set to t1.5 = 1.0 ms and t3.5 = 2.0 ms. If a break between two characters is greater than t1.5 and less than t3.5, this is identified as a transmission error. The message is considered incomplete and is indicated with a receive error. If the break after a character is greater than t3.5, this is identified as the telegram end. Three transmit and three receive buffers are available. The size of the buffer depends on the parameterized data way: Data exchange via process data Data exchange via PDI 340 bytes per buffer 245 bytes per buffer Modbus/RTU mode offers Modbus/RTU master support. However, the module does not have programmable logic. Modbus/RTU slave support is not implemented. Data transfer sequence The two checksum bytes are automatically generated and sent for the user data supplied via the bus (via process data or PDI). Once sent this has been sent, a response is expected. If the response is not received within 2.5 seconds, a transmit error is generated by setting error bit Tx in the status word. If the response is received in time, the checksum is checked. If the checksum is invalid, time t1.5 has elapsed on receipt or a parity error has occurred, a receive error is then generated by setting error bit Rx in the status word. On error-free receipt, the “Rx buffer not empty” bit is set in the status word. The checksum bytes are not included when reading the receive data. 8533_en_04 PHOENIX CONTACT 14 / 30 AXL F RS UNI 1H 12 Process data The module is parameterized via the PDI channel, data exchange with the higher-level controller depends on the parameter data way and is either via process data or via PDI. The module has ten words of process data. These are made up of 3 bytes of control data and a maximum of 17 bytes of user data. Assignment of the ten process data words Word Byte in the Motorola format Byte in the Intel format OUT IN 0 0 1 K/P K/P 1 1 0 S S 2 3 L L 2 3 2 D D 4 5 D D 5 4 D D ... ... ... ... ... 9 18 19 D D 19 18 D D K/P Command/parameter S Control bits (OUT) or status bits (IN) L Length: Number of characters to be written (OUT) or to be read (IN) D 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. 8533_en_04 PHOENIX CONTACT 15 / 30 AXL F RS UNI 1H 13 Process data word 0 13.1 Control word 15 0 14 13 12 Command 11 10 9 OUT parameter 8 7 6 5 4 3 Control bits 2 1 0 Control bits 7 DTR 6 0 Code (bin) 0 1 5 0 4 0 DTR (if DTR control enabled) Meaning Protocol DTR = logic 0 All DTR = logic 1 The DTR signal can only be controlled via the bit if you have parameterized interface type RS-232 and DTR control via process data in the parameter table. 3 0 2 1 Reset Reset receive transmit error error 0 0 Code (bin) 0 1 Reset transmit error Meaning No action Reset transmit error Protocol Modbus/RTU Code (bin) 0 1 Reset receive error Meaning No action Reset receive error Protocol Modbus/RTU Commands Command toggling Code (bin) 000 001 010 011 Code (hex) 0 1 2 3 100 101 4 5 110 6 111 7 8533_en_04 Command Read number of characters received (in the transparent and XON/XOFF protocol) and fill level of the receive buffer Transmit characters Store characters temporarily OUT parameter = 0hex: Read characters OUT parameter = Chex: Read firmware version OUT parameter = Ehex: Read counters Reserved Toggling command 1: Transmit characters Toggling command 2: Store characters temporarily Toggling command 3: Read characters 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 001bin for the first transmission and then use 101bin and 001bin alternately. PHOENIX CONTACT 16 / 30 AXL F RS UNI 1H 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 Error bit Reasons for an error bit set: – Invalid parameter for the specified command – Failure of the I/O voltage Status bits 7 DSR Code (bin) 0 1 6 Transmit buffer not empty 5 Transmit buffer full DSR Meaning DSR = logic 0 DSR = logic 1 4 Receive buffer full Protocol All 3 DCD Protocol Transparent XON/XOFF Modbus/RTU End-to-end 2 Transmit error 1 Receive error 0 Receive buffer not empty Meaning: receive buffer full Space remaining ≤ 15 characters Space remaining ≤ 15 characters No more buffer space No more buffer space The DSR signal state is displayed, if you have parameterized interface type RS-232. Code (bin) 0 1 Code (bin) 0 1 Protocol Modbus/RTU Other Code (bin) 0 1 Transmit buffer not empty Meaning Protocol Empty All Not empty, transmission in progress Transmit buffer full Meaning Not full Full Protocol All Meaning: transmit buffer full No more buffer space Space remaining in the transmit buffer ≤ 30 characters Receive buffer full Meaning Not full Full Code (bin) 0 1 Protocol All The DCD signal state is displayed, if you have parameterized interface type RS-232. Code (bin) 0 1 Code (bin) 0 1 Protocol All Code (bin) 0 1 8533_en_04 DCD Meaning DCD = logic 0 DCD = logic 1 Transmit error Meaning No error Transmit error; 2.5 s timeout has elapsed with no response received Receive error Meaning No error Receive error; telegram received with invalid checksum Receive buffer not empty Meaning Empty Not empty, characters to be read are available Protocol Modbus/RTU Protocol Modbus/RTU Protocol All PHOENIX CONTACT 17 / 30 AXL F RS UNI 1H 14 Commands 14.1 “Read number of characters received and fill level of the receive buffer” command For the transparent and XON/XOFF protocol, the command result is the number of characters that have been received but not yet read. The number is a 16-bit value and is mapped to word 1. This command can be used to first reach a minimum number of characters before transmitting the "Read characters" command. For all protocols, the fill level of the receive buffer is specified in byte 4 as the command result. Process data assignment for the “Read number of characters received and fill level of the receive buffer” command Word Byte OUT IN Fill level Byte 4 00hex 01hex 02hex 03hex 8533_en_04 0 0 00hex 00hex 1 1 2 3 xx xx xx Status bits Number of characters received Protocol Transparent, XON/XOFF Number of kbytes free 4