Commissioning
EL600x, EL602x
134
Version: 4.6
Process data
Contents
Ctrl.Output length
Number of user data bytes (n) + 2
Data Out 0
Protected ID field (PID = Protected identifier field)
Data Out 1
Data byte 1
Data Out n
Data byte n
Data Out n+1
Checksum
EL6001 LIN example
The following LIN communication example is intended to illustrate that participation of a PLC controller via
the EL6001 terminal in a LIN cluster is possible by activating the complementary LIN functionality via the
0xB000 CoE “command” object in combination with a physical conversion of RS-232 to the LIN bus.
Hardware connection based on a UART-LIN converter
The implementation of the physical layer as a basic prerequisite for LIN communication includes the
provision of one-wire bus with corresponding signal levels 0V / 12V. This is best done with an RS232-LIN
converter, which is connected to a sub-D connector and on the other side provides three poles for ground,
power supply and the electrical connection to the one-wire LIN-bus.
The use of an RS232-LIN converter requires a sub-D 9-pin connector to be connected to the EL6001
terminal, as shown in the diagram:
Fig. 151: RS232-LIN sub-D connector connected to the EL6001 terminal
Electrical connections between the EL6001 terminal and the sub-D 9-pin connector:
• RxD →pin 2
• TxD →pin 3
• GND → pin 5
Programming in ST
A LIN communication can be represented by a PLC “master task”, whereby a master sends an
“unconditional frame”, as usual with a LIN bus, and only outputs the PID (protocol identifier) of a known slave
node on the LIN bus, thereby generally requesting data from the respective slave. The chapter on
commissioning contains a relevant
