2.4KL6023 - Technical Data .................................................................................................................11
2.5Basic Function Principles ................................................................................................................12
3 Mounting and wiring................................................................................................................................14
3.1Installation on mounting rails ...........................................................................................................14
3.2Connection of the wireless adapter .................................................................................................17
7.1Support and Service ........................................................................................................................33
KL6021-0023 and KL60233Version: 2.0.0
Page 4
Table of contents
KL6021-0023 and KL60234Version: 2.0.0
Page 5
Foreword
1Foreword
1.1Notes on the documentation
Intended audience
This description is only intended for the use of trained specialists in control and automation engineering who
are familiar with the applicable national standards.
It is essential that the documentation and the following notes and explanations are followed when installing
and commissioning these components.
It is the duty of the technical personnel to use the documentation published at the respective time of each
installation and commissioning.
The responsible staff must ensure that the application or use of the products described satisfy all the
requirements for safety, including all the relevant laws, regulations, guidelines and standards.
Disclaimer
The documentation has been prepared with care. The products described are, however, constantly under
development.
We reserve the right to revise and change the documentation at any time and without prior announcement.
No claims for the modification of products that have already been supplied may be made on the basis of the
data, diagrams and descriptions in this documentation.
Trademarks
Beckhoff®, TwinCAT®, EtherCAT®, EtherCATG®, EtherCATG10®, EtherCATP®, SafetyoverEtherCAT®,
TwinSAFE®, XFC®, XTS® and XPlanar® are registered trademarks of and licensed by Beckhoff Automation
GmbH. Other designations used in this publication may be trademarks whose use by third parties for their
own purposes could violate the rights of the owners.
Patent Pending
The EtherCAT Technology is covered, including but not limited to the following patent applications and
patents: EP1590927, EP1789857, EP1456722, EP2137893, DE102015105702 with corresponding
applications or registrations in various other countries.
EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH,
Germany.
Please note the following safety instructions and explanations!
Product-specific safety instructions can be found on following pages or in the areas mounting, wiring,
commissioning etc.
Exclusion of liability
All the components are supplied in particular hardware and software configurations appropriate for the
application. Modifications to hardware or software configurations other than those described in the
documentation are not permitted, and nullify the liability of Beckhoff Automation GmbH & Co. KG.
Personnel qualification
This description is only intended for trained specialists in control, automation and drive engineering who are
familiar with the applicable national standards.
Description of instructions
In this documentation the following instructions are used.
These instructions must be read carefully and followed without fail!
DANGER
Serious risk of injury!
Failure to follow this safety instruction directly endangers the life and health of persons.
WARNING
Risk of injury!
Failure to follow this safety instruction endangers the life and health of persons.
CAUTION
Personal injuries!
Failure to follow this safety instruction can lead to injuries to persons.
NOTE
Damage to environment/equipment or data loss
Failure to follow this instruction can lead to environmental damage, equipment damage or data loss.
Tip or pointer
This symbol indicates information that contributes to better understanding.
KL6021-0023 and KL60236Version: 2.0.0
Page 7
1.3Documentation issue status
VersionComment
2.0• Migration
1.1• Mounting description expanded
• Information on basic function principles expanded
• Introduction to the KL6023 added
1.0• Description of the KL6023 (wireless adapter for EnOcean radio technology) added
• Wiring instructions added
• Description of the KS2000 configuration software added
• Technical data added
0.1First preliminary version
Firmware and hardware versions
Foreword
Documentation
Version
2.05D031A02
1.15D011A01
1.05A001A00
0.15A00--
The firmware and hardware versions (delivery state) of the terminal can be found in the serial number printed
on the side.
Syntax of the serial number
Structure of the serial number: WWYYFFHH
WW - week of production (calendar week)
YY – year of production
FF - firmware version
HH - hardware version
Example with ser. no.: 12 06 3A 02:
12 - week of production 12
06 - year of production 2006
3A - firmware version 3A
02 - hardware version 02
KL6021-0023KL6023
FirmwareHardwareFirmwareHardware
KL6021-0023 and KL60237Version: 2.0.0
Page 8
Product overview
2Product overview
2.1KL6021-0023 - Introduction
Fig.1: KL6021-0023 – serial interface terminal for the connection of the KL6023 wireless adapter
The KL6021-0023 serial interface connects the wireless adapter via an RS485 signal. The KL6023 wireless
adapter operates as an EnOcean radio receiver and receives the radio signals from EnOcean sensors.
LEDs
LEDColor Meaning
RUNgreen This LED indicates the terminal's operating state:
onnormal operation
offA watchdog timer overflow has occurred. The RUN LED goes out if no process
data is transmitted to the terminal from the Bus Coupler for 100ms.
TxDgreen State of the transmit signal line
RxDgreen State of the receive signal line
Connection
Terminal
point
1TxD+Signal line (Transmit Data)
5TxD-Signal line (Transmit Data)
2RxD+ Signal line (Receive Data)
6RxD-Signal line (Receive Data)
3GNDGround for the KL6023 (bridged internally with terminal point 7)
7GNDGround for the KL6023 (bridged internally with terminal point 3)
4+5 VSupply voltage for the KL6023 (bridged internally with terminal point 8)
8+5 VSupply voltage for the KL6023 (bridged internally with terminal point 4)
Name Signal
KL6021-0023 and KL60238Version: 2.0.0
Page 9
Product overview
2.2KL6021-0023 - Technical Data
Technical dataKL6021-0023
Number of inputs1, for wireless adapter (EnOcean radio technology)
Cable impedanceapprox. 120Ω
Connecting cable to KL6023 wireless adapter 2 twisted pairs
Length of connection to KL6023 wireless
adapter
Bit width in process image11 x 8bit user data, 1 x 8bit control/status
Power supply for the electronicsvia the K-bus
Current consumption via K-bustypically 65mA
Weightapprox.60g
Dimensions (WxHxD)approx. 15mmx100mmx70mm
Mountingon 35mm mounting rail according to EN60715
Permissible ambient temperature range
during operation
Permissible ambient temperature range
during storage
Permissible relative air humidity95%, no condensation
Vibration/shock resistanceconforms to EN60068-2-6/ EN60068-2-27, see also
Installation instructions for enhanced mechanical load
capacity
KL6021-0023 and KL60239Version: 2.0.0
Page 10
Product overview
2.3KL6023 - Introduction
Fig.2: KL6023 - Wireless Adapter for EnOcean radio technology
The KL6023 Wireless Adapter receives signals from battery-less sensors with EnOcean technology. These
signals are converted by the Wireless Adapter to a RS485 signal and directly processed further by the
KL6021-0023 serial Bus Terminal. With a radio signal range of at least 30m, the wiring of buildings can be
simplified significantly.
Fig.3: Application
KL6021-0023 and KL602310Version: 2.0.0
Page 11
Product overview
The status LEDs of the Wireless Adapter are helpful during commissioning. The LEDs indicate all telegrams
they receive as faulty or faultless. With a maximum distance of 300m between the receiver and the Bus
Terminal station, it is possible to place the receivers at any radio-technically favorable location within a
building. The system does not stipulate a maximum number of transmitters per receiver unit. In practice,
between 25 and 100transmitters per receiver are used.
2.4KL6023 - Technical Data
Technical dataKL6023
(Wireless Adapter for EnOcean radio technology)
Connection2 twisted pairs, direct to Bus Terminal KL6021-0023
Power supplyvia KL6021-0023 Bus Terminal (with electrical isolation)
Length of connecting cable to the KL6021-0023 max. 300m
Configurationnot required
Frequency band868.35MHz
Transfer rangeIn open spaces: approx. 300m
Inside buildings: approx. 30m
Radio telegramdepending on sensor type:
- 32bit sensor identification number
- number of user bytes is not limited
Receiving aerialintegrated in the housing
HousingBox: Polystyrene (grey) with M16 PG threaded fitting for
fitting)
Permissible ambient temperature range during
operation
Permissible ambient temperature range during
storage
Vibration/shock resistanceconforms to EN60068-2-6/ EN60068-2-27
EMC immunity/emissionconforms to EN61000-6-2/ EN61000-6-4
Protection classIP66
Mounting positionvariable
ApprovalCE
0°C ... + 55°C
-25°C ... + 85°C
KL6021-0023 and KL602311Version: 2.0.0
Page 12
Product overview
2.5Basic Function Principles
The KL6021-0023 [}8] serial communication terminal connects the KL6023 [}10] EnOcean receiver module
with the Beckhoff Bus Terminal system. EnOcean (http://www.enocean.de) permits radio transmission
without either batteries or an external power supply to the transmitter.
Fig.4: KL6021-0023 and KL6023
Approval of EnOcean radio technology
NOTE
Nature and source of the danger
The KL6032 EnOcean receiver module can be operated in the following countries without registration and
fees.
Permission for use in other countries must be clarified explicitly!
• European union
• Switzerland
Reading received telegrams
When the KL6021-0023 has received new telegrams it indicates this by setting the bit SB.2 [}26] in the
status byte to 1. Reading out received telegrams is initiated through bit CB.0 [}26] in the control byte being
inverted by the higher-level controller. The change from 0 to 1 or from 1 to 0 always causes the next
telegram in the memory to be displayed in the process data. The value of the bit CB.0 [}26] is adopted by
SB.0 [}26] as acknowledgement.
KL6021-0023 and KL602312Version: 2.0.0
Page 13
Product overview
The leading synchronization byte and the closing checksum are part of the EnOcean standard, and the
KL6021-0023 filters them out of the telegram, so that the displayed data starts with the telegram header[}13] and ends with the status field [}13].
Longer telegrams
If the telegram from an EnOcean transmitter consists of more than 4data bytes, it cannot be transferred in a
single K-bus cycle. In that case, the KL6021-0023 sets bit SB.1 [}26] in the status byte in the next read
cycle, placing the next data block from the telegram into the process data.
Faulty telegrams
The KL6021-0023 calculates the checksum for every EnOcean telegram that is received. If this does not
agree with the checksum that has been transmitted the terminal sets bit SB.6 [}26] in the status byte. A
telegram is not then placed into the data memory, and is lost.
Data memory overflow
If the telegrams received by the KL6021-0023 are not read by the higher-level controller, the terminal's
receive memory will overflow, and it will set bit SB.3 [}26] in the status byte. It is also possible for a
telegram only to be partially written into the memory. This will automatically cause an error in the checksum,
and it will be displayed and handled accordingly.
Protocol
The following table illustrates the general structure of an EnOcean telegram:
Bit7Bit0Description
Sync_Byte1 (0xA5)Synchronization byte
Sync_Byte0 (0x5A)
H_SeqLengthHeader
identification
ORGTelegram type
Data Byte3Data byte
Data Byte2
Data Byte1
Data Byte0
ID Byte332bit transmitter ID
ID Byte2
ID Byte1
ID Byte0
StatusStatus field
Check SumChecksum (LSB resulting from the addition of all bytes, not
including the synchronization byte or the checksum itself)
H_Seq (3bit)
• 0 unknown transmitter ID received
• 1 known transmitter ID received
• 2 new transmitter learnt
Length (5bit)
• Number of byte following the header
(here: 11)
KL6021-0023 and KL602313Version: 2.0.0
Page 14
Mounting and wiring
3Mounting and wiring
3.1Installation on mounting rails
WARNING
Risk of electric shock and damage of device!
Bring the bus terminal system into a safe, powered down state before starting installation, disassembly or
wiring of the bus terminals!
Assembly
Fig.5: Attaching on mounting rail
The bus coupler and bus terminals are attached to commercially available 35mm mounting rails (DIN rails
according to EN60715) by applying slight pressure:
1. First attach the fieldbus coupler to the mounting rail.
2. The bus terminals are now attached on the right-hand side of the fieldbus coupler. Join the components with tongue and groove and push the terminals against the mounting rail, until the lock clicks
onto the mounting rail.
If the terminals are clipped onto the mounting rail first and then pushed together without tongue and
groove, the connection will not be operational! When correctly assembled, no significant gap should
be visible between the housings.
Fixing of mounting rails
The locking mechanism of the terminals and couplers extends to the profile of the mounting rail. At
the installation, the locking mechanism of the components must not come into conflict with the fixing
bolts of the mounting rail. To mount the mounting rails with a height of 7.5mm under the terminals
and couplers, you should use flat mounting connections (e.g. countersunk screws or blind rivets).
KL6021-0023 and KL602314Version: 2.0.0
Page 15
Mounting and wiring
Disassembly
Fig.6: Disassembling of terminal
Each terminal is secured by a lock on the mounting rail, which must be released for disassembly:
1. Pull the terminal by its orange-colored lugs approximately 1cm away from the mounting rail. In doing
so for this terminal the mounting rail lock is released automatically and you can pull the terminal out of
the bus terminal block easily without excessive force.
2. Grasp the released terminal with thumb and index finger simultaneous at the upper and lower grooved
housing surfaces and pull the terminal out of the bus terminal block.
Connections within a bus terminal block
The electric connections between the Bus Coupler and the Bus Terminals are automatically realized by
joining the components:
• The six spring contacts of the K-Bus/E-Bus deal with the transfer of the data and the supply of the Bus
Terminal electronics.
• The power contacts deal with the supply for the field electronics and thus represent a supply rail within
the bus terminal block. The power contacts are supplied via terminals on the Bus Coupler (up to 24V)
or for higher voltages via power feed terminals.
Power Contacts
During the design of a bus terminal block, the pin assignment of the individual Bus Terminals must
be taken account of, since some types (e.g. analog Bus Terminals or digital 4-channel Bus Terminals) do not or not fully loop through the power contacts. Power Feed Terminals (KL91xx, KL92xx
or EL91xx, EL92xx) interrupt the power contacts and thus represent the start of a new supply rail.
PE power contact
The power contact labeled PE can be used as a protective earth. For safety reasons this contact mates first
when plugging together, and can ground short-circuit currents of up to 125A.
KL6021-0023 and KL602315Version: 2.0.0
Page 16
Mounting and wiring
Fig.7: Power contact on left side
NOTE
Possible damage of the device
Note that, for reasons of electromagnetic compatibility, the PE contacts are capacitatively coupled to the
mounting rail. This may lead to incorrect results during insulation testing or to damage on the terminal (e.g.
disruptive discharge to the PE line during insulation testing of a consumer with a nominal voltage of 230V).
For insulation testing, disconnect the PE supply line at the Bus Coupler or the Power Feed Terminal! In order to decouple further feed points for testing, these Power Feed Terminals can be released and pulled at
least 10mm from the group of terminals.
WARNING
Risk of electric shock!
The PE power contact must not be used for other potentials!
KL6021-0023 and KL602316Version: 2.0.0
Page 17
Mounting and wiring
3.2Connection of the wireless adapter
WARNING
Risk of electric shock and damage of device!
Bring the bus terminal system into a safe, powered down state before starting installation, disassembly or
wiring of the bus terminals!
Fig.8: Connection of the wireless adapter
KL6021-0023KL6023 – Wireless adapter
SignalTerminal point no.SignalTerminal point no.
RxD+2RxD+1
RxD-6RxD-2
GND3 or 7GND3
5V4 or 85V4
KL6021-0023 and KL602317Version: 2.0.0
Page 18
KS2000 Configuration Software
4KS2000 Configuration Software
4.1KS2000 - Introduction
The KS2000 configuration software permits configuration, commissioning and parameterization of bus
couplers, of the affiliated bus terminals and of Fieldbus Box Modules. The connection between bus coupler/
Fieldbus Box Module and the PC is established by means of the serial configuration cable or the fieldbus.
Fig.9: KS2000 configuration software
Configuration
You can configure the Fieldbus stations with the Configuration Software KS2000 offline. That means, setting
up a terminal station with all settings on the couplers and terminals resp. the Fieldbus Box Modules can be
prepared before the commissioning phase. Later on, this configuration can be transferred to the terminal
station in the commissioning phase by means of a download. For documentation purposes, you are provided
with the breakdown of the terminal station, a parts list of modules used and a list of the parameters you have
modified. After an upload, existing fieldbus stations are at your disposal for further editing.
Parameterization
KS2000 offers simple access to the parameters of a fieldbus station: specific high-level dialogs are available
for all bus couplers, all intelligent bus terminals and Fieldbus Box modules with the aid of which settings can
be modified easily. Alternatively, you have full access to all internal registers of the bus couplers and
intelligent terminals. Refer to the register description for the meanings of the registers.
KL6021-0023 and KL602318Version: 2.0.0
Page 19
KS2000 Configuration Software
Commissioning
The KS2000 software facilitates commissioning of machine components or their fieldbus stations: Configured
settings can be transferred to the fieldbus modules by means of a download. After a login to the terminal
station, it is possible to define settings in couplers, terminals and Fieldbus Box modules directly online. The
same high-level dialogs and register access are available for this purpose as in the configuration phase.
The KS2000 offers access to the process images of the bus couplers and Fieldbus Box modules.
• Thus, the coupler's input and output images can be observed by monitoring.
• Process values can be specified in the output image for commissioning of the output modules.
All possibilities in the online mode can be used in parallel with the actual fieldbus mode of the terminal
station. The fieldbus protocol always has the higher priority in this case.
4.2Parameterization with KS2000
Connect the configuration interface of your Fieldbus Coupler with the serial interface of your PC via the
configuration cable and start the KS2000 Configuration Software.
Click on the Login button. The configuration software will now load the information for the
connected fieldbus station.
In the example shown, this is
• a BK2020 Lightbus Coupler
• a KL1xx2 Digital Input Terminal
• a KL6021-0023 serial interface terminal (RS485 for EnOcean receiver KL6023)
• a KL9010 Bus End Terminal
KL6021-0023 and KL602319Version: 2.0.0
Page 20
KS2000 Configuration Software
Fig.10: Display of the fieldbus station in KS2000
The left-hand KS2000 window displays the terminals of the fieldbus station in a tree structure.
The right-hand KS2000window contains a graphic display of the fieldbus station terminals.
In the tree structure of the left-hand window, click on the plus-sign next to the terminal whose parameters
you wish to change (item 2 in the example).
Fig.11: KS2000 branch for channel 1 of the KL6021-0023
For the KL6021-0023, the branches Register, Settings and ProcData are displayed:
KL6021-0023 and KL602320Version: 2.0.0
Page 21
KS2000 Configuration Software
• Register [}21] permits direct access to the registers of the KL6021-0023.
• There are no dialog masks to be found for parameterizing the KL6021-0023 under Settings, since no
terminal-specific settings are required.
• ProcData [}22] displays the KL6021-0023 process data.
4.3Register
Under Register you can directly access the registers of the KL6021-0023. The meaning of the register is
explained in the Register Overview [}27].
Fig.12: Register view in KS2000
4.4Settings
No terminal-specific settings are necessary for the KL6021-0023 and the KL6023.
KL6021-0023 and KL602321Version: 2.0.0
Page 22
KS2000 Configuration Software
4.5Process data
The Status byte (Status), the Control byte (Ctrl) and the process data (Data) are displayed in a tree structure
under ProcData.
Fig.13: ProcData
The spectacles mark the data that are currently graphically displayed in the History field.
Fig.14: History field
The current input value is displayed numerically in the Value field.
Fig.15: Value field
Output values can be modified through direct input or by means of the fader control.
KL6021-0023 and KL602322Version: 2.0.0
Page 23
KS2000 Configuration Software
Fig.16: Value field
WARNING
Changing output values (forcing)
Note that changing output values (forcing) can have a direct effect on your automation application.
Only change these output values if you are certain that the state of your system permits it, and that there
will be no risk to people or to the machine!
After pressing the Settings button you can set the format of the numerical display to hexadecimal, decimal or
binary.
Fig.17: Settings
KL6021-0023 and KL602323Version: 2.0.0
Page 24
Programming
5Programming
5.1TwinCAT libraries
Software documentation in the Beckhoff Information System:
TwinCAT 2: TwinCAT 2 PLC Lib: EnOcean
TwinCAT 3: TwinCAT 3 PLC Lib: Tc2_EnOcean
KL6021-0023 and KL602324Version: 2.0.0
Page 25
Access from the user program
6Access from the user program
6.1Process image
The KL6021-0023 is represented in the process image with 12bytes of input data and 12bytes of output
data. These are organized as follows:
The registers are used to parameterize the terminal. They can be read or written by means of the register
communication.
R6: Diagnostic register
Status byte SB [}25] is placed into register R6.
R7: Command register
No commands are implemented in this terminal.
R8: Terminal description
The name of the terminal is contained in register R8. KL6021: 0x1785 (6021
dec
)
R9: Firmware version
Register R9 contains the ASCII coding of the terminal's firmware version, e.g. 0x3541 = '5A'. The '0x35'
corresponds here to the ASCII character '5', while the '0x41' represents the ASCII character 'A'.
This value cannot be changed.
R16: Hardware version number
Register R16 contains the hardware version of the terminal; this value cannot be changed.
R29: Terminal type - special identification
The name of the special type of the terminal is contained in register R29. KL6021-0023: 0x0017 (0023
dec
R31: Code word register
• If you write values into the user registers without first entering the user code word (0x1235) into the
code word register, the terminal will not accept the supplied data.
• If you write values into the user registers and have previously entered the user code word (0x1235) in
the code word register, these values are stored in the RAM registers and in the SEEPROM registers
and are therefore retained when the terminal is restarted.
The code word is reset when the terminal is restarted.
)
R32: Feature register
The feature register specifies the terminal's configuration. There are no configurations that can be made for
this terminal.
R35: Number of data bytes sent to the Bus Coupler
Register R35 indicates the number of data bytes that transmitted to the Bus Coupler. This value cannot be
changed.
KL6021-0023 and KL602328Version: 2.0.0
Page 29
Access from the user program
6.5Examples of Register Communication
The numbering of the bytes in the examples corresponds to the display without word alignment.
6.5.1Example 1: reading the firmware version from Register 9
Output Data
Byte 0: Control byteByte 1: DataOUT1, high byteByte 2: DataOUT1, low byte
0x89 (1000 1001
Explanation:
• Bit 0.7 set means: Register communication switched on.
• Bit 0.6 not set means: reading the register.
• Bits 0.5 to 0.0 specify the register number 9 with 00 1001
• The output data word (byte 1 and byte 2) has no meaning during read access. To change a register,
write the required value into the output word.
)0xXX0xXX
bin
.
bin
Input Data (answer of the bus terminal)
Byte 0: Status byteByte 1: DataIN1, high byteByte 2: DataIN1, low byte
0x890x330x41
Explanation:
• The terminal returns the value of the control byte as a receipt in the status byte.
• The terminal returns the firmware version 0x3341 in the input data word (byte 1 and byte 2). This is to
be interpreted as an ASCII code:
◦ ASCII code 0x33 represents the digit 3
◦ ASCII code 0x41 represents the letter A
The firmware version is thus 3A.
6.5.2Example 2: Writing to an user register
Code word
In normal mode all user registers are read-only with the exception of Register 31. In order to deactivate this write protection you must write the code word (0x1235) into Register 31. If a value other
than 0x1235 is written into Register 31, write protection is reactivated. Please note that changes to
a register only become effective after restarting the terminal (power-off/power-on).
I. Write the code word (0x1235) into Register 31.
Output Data
Byte 0: Control byteByte 1: DataOUT1, high byteByte 2: DataOUT1, low byte
0xDF (1101 1111
)0x120x35
bin
Explanation:
• Bit 0.7 set means: Register communication switched on.
• Bit 0.6 set means: writing to the register.
• Bits 0.5 to 0.0 specify the register number 31 with 01 1111
.
bin
• The output data word (byte 1 and byte 2) contains the code word (0x1235) for deactivating write
protection.
KL6021-0023 and KL602329Version: 2.0.0
Page 30
Access from the user program
Input Data (answer of the bus terminal)
Byte 0: Status byteByte 1: DataIN1, high byteByte 2: DataIN1, low byte
0x9F (1001 1111
)0xXX0xXX
bin
Explanation:
• The terminal returns a value as a receipt in the status byte that differs only in bit 0.6 from the value of
the control byte.
• The input data word (byte 1 and byte 2) is of no importance after the write access. Any values still
displayed are invalid!
II. Read Register 31 (check the set code word)
Output Data
Byte 0: Control byteByte 1: DataOUT1, high byteByte 2: DataOUT1, low byte
0x9F (1001 1111
)0xXX0xXX
bin
Explanation:
• Bit 0.7 set means: Register communication switched on.
• Bit 0.6 not set means: reading the register.
• Bits 0.5 to 0.0 specify the register number 31 with 01 1111
.
bin
• The output data word (byte 1 and byte 2) has no meaning during read access.
Input Data (answer of the bus terminal)
Byte 0: Status byteByte 1: DataIN1, high byteByte 2: DataIN1, low byte
0x9F (1001 1111
)0x120x35
bin
Explanation:
• The terminal returns the value of the control byte as a receipt in the status byte.
• The terminal returns the current value of the code word register in the input data word (byte 1 and byte
2).
III. Write to Register 32 (change contents of the feature register)
Output data
Byte 0: Control byteByte 1: DataIN1, high byteByte 2: DataIN1, low byte
0xE0 (1110 0000
)0x000x02
bin
Explanation:
• Bit 0.7 set means: Register communication switched on.
• Bit 0.6 set means: writing to the register.
• Bits 0.5 to 0.0 indicate register number 32 with 10 0000
.
bin
• The output data word (byte 1 and byte 2) contains the new value for the feature register.
CAUTION
Observe the register description!
The value of 0x0002 given here is just an example!
The bits of the feature register change the properties of the terminal and have a different meaning, depending on the type of terminal. Refer to the description of the feature register of your terminal (chapter Registerdescription) regarding the meaning of the individual bits before changing the values.
KL6021-0023 and KL602330Version: 2.0.0
Page 31
Access from the user program
Input data (response from the Bus Terminal)
Byte 0: Status byteByte 1: DataIN1, high byteByte 2: DataIN1, low byte
0xA0 (1010 0000
)0xXX0xXX
bin
Explanation:
• The terminal returns a value as a receipt in the status byte that differs only in bit 0.6 from the value of
the control byte.
• The input data word (byte 1 and byte 2) is of no importance after the write access. Any values still
displayed are invalid!
IV. Read Register 32 (check changed feature register)
Output Data
Byte 0: Control byteByte 1: DataOUT1, high byteByte 2: DataOUT1, low byte
0xA0 (1010 0000
)0xXX0xXX
bin
Explanation:
• Bit 0.7 set means: Register communication switched on.
• Bit 0.6 not set means: reading the register.
• Bits 0.5 to 0.0 indicate register number 32 with 10 0000
.
bin
• The output data word (byte 1 and byte 2) has no meaning during read access.
Input Data (answer of the bus terminal)
Byte 0: Status byteByte 1: DataIN1, high byteByte 2: DataIN1, low byte
0xA0 (1010 0000
)0x000x02
bin
Explanation:
• The terminal returns the value of the control byte as a receipt in the status byte.
• The terminal returns the current value of the feature register in the input data word (byte 1 and byte 2).
V. Write Register 31 (reset code word)
Output Data
Byte 0: Control byteByte 1: DataOUT1, high byteByte 2: DataOUT1, low byte
0xDF (1101 1111
)0x000x00
bin
Explanation:
• Bit 0.7 set means: Register communication switched on.
• Bit 0.6 set means: writing to the register.
• Bits 0.5 to 0.0 specify the register number 31 with 01 1111
.
bin
• The output data word (byte 1 and byte 2) contains 0x0000 for reactivating write protection.
Input Data (answer of the bus terminal)
Byte 0: Status byteByte 1: DataIN1, high byteByte 2: DataIN1, low byte
0x9F (1001 1111
)0xXX0xXX
bin
Explanation:
• The terminal returns a value as a receipt in the status byte that differs only in bit 0.6 from the value of
the control byte.
KL6021-0023 and KL602331Version: 2.0.0
Page 32
Access from the user program
• The input data word (byte 1 and byte 2) is of no importance after the write access. Any values still
displayed are invalid!
KL6021-0023 and KL602332Version: 2.0.0
Page 33
Appendix
7Appendix
7.1Support and Service
Beckhoff and their partners around the world offer comprehensive support and service, making available fast
and competent assistance with all questions related to Beckhoff products and system solutions.
Beckhoff's branch offices and representatives
Please contact your Beckhoff branch office or representative for local support and service on Beckhoff
products!
The addresses of Beckhoff's branch offices and representatives round the world can be found on her internet
pages:
http://www.beckhoff.com
You will also find further documentation for Beckhoff components there.
Support offers you comprehensive technical assistance, helping you not only with the application of
individual Beckhoff products, but also with other, wide-ranging services:
• support
• design, programming and commissioning of complex automation systems
• and extensive training program for Beckhoff system components
Fig. 14History field ..................................................................................................................................22
Fig. 15Value field ....................................................................................................................................22
Fig. 16Value field ....................................................................................................................................23