X20 System-ENG PDF
X20 System-ENG PDF
User's Manual
All information contained in this manual is current as of its creation/publication. B&R reserves the right to change
the contents of this manual without notice. The information contained herein is believed to be accurate as of
the date of publication; however, Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. makes no warranty, ex-
pressed or implied, with regard to the products or documentation contained within this manual. In addition,
Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. shall not be liable for any incidental or consequential damages
in connection with or arising from the furnishing, performance or use of the product(s) in this documentation. Soft-
ware names, hardware names and trademarks are registered by their respective companies.
Table of contents
1 General information................................................................................................ 50
1.1 Manual history...............................................................................................................................................50
1.2 Safety notices................................................................................................................................................52
1.2.1 Introduction.............................................................................................................................................. 52
1.2.2 Intended use............................................................................................................................................52
1.2.3 Protection against electrostatic discharge...............................................................................................53
1.2.3.1 Packaging...........................................................................................................................................53
1.2.3.2 Guidelines for proper ESD handling..................................................................................................53
1.2.4 Transport and storage............................................................................................................................. 54
1.2.5 Installation................................................................................................................................................54
1.2.5.1 Inserting and removing I/O modules while the controller is running..................................................54
1.2.6 Operation................................................................................................................................................. 55
1.2.6.1 Protection against touching electrical parts....................................................................................... 55
1.2.7 Environmentally friendly disposal............................................................................................................ 55
1.2.7.1 Separation of materials...................................................................................................................... 55
1.2.8 Organization of safety notices.................................................................................................................55
1.3 Terminology...................................................................................................................................................56
2 System features...................................................................................................... 57
2.1 Setting the standards in automation.............................................................................................................57
2.1.1 More than just I/O................................................................................................................................... 57
2.1.2 3 x 1 = 1..................................................................................................................................................58
2.2 Optimized design.......................................................................................................................................... 59
2.3 Remote backplane........................................................................................................................................ 60
2.4 X20 CPUs..................................................................................................................................................... 61
2.4.1 General information................................................................................................................................. 61
2.4.2 Remote backplane...................................................................................................................................61
2.4.3 B&R Automation Studio...........................................................................................................................62
2.4.4 PC-based technology.............................................................................................................................. 62
2.4.5 Suitable for industrial use........................................................................................................................62
2.5 X20 Compact CPUs......................................................................................................................................63
2.5.1 General information................................................................................................................................. 63
2.5.2 Product range.......................................................................................................................................... 63
2.6 X20 Fieldbus CPUs...................................................................................................................................... 64
2.6.1 General information................................................................................................................................. 64
2.6.2 Product range.......................................................................................................................................... 64
2.6.3 Programming........................................................................................................................................... 64
2.7 For all fieldbuses, integration through standardization................................................................................. 65
2.8 Complete system.......................................................................................................................................... 66
2.8.1 IP67 - then X67....................................................................................................................................... 66
2.8.2 Integrated valve terminal control............................................................................................................. 66
2.9 Easy wiring....................................................................................................................................................67
2.9.1 Install the wires, plug it in, and it's ready to go...................................................................................... 67
2.10 Sophisticated mechanics............................................................................................................................ 68
2.11 Diagnostics.................................................................................................................................................. 69
2.11.1 re LEDs.................................................................................................................................................. 70
2.12 Embedded parameter chip..........................................................................................................................71
2.13 Space for options........................................................................................................................................71
2.14 Flexibility for options................................................................................................................................... 71
2.15 Configurable X2X Link address.................................................................................................................. 72
2.16 Universal 1, 2, 3-wire connections............................................................................................................. 73
2.17 Coated X20 system.................................................................................................................................... 74
2.18 Redundancy................................................................................................................................................ 74
2.19 reACTION technology................................................................................................................................. 74
2.20 X20 system configuration........................................................................................................................... 75
2.20.1 Fieldbus connection...............................................................................................................................76
2.20.2 Connection to X2X Link backplane....................................................................................................... 77
4.19.2.11 SG4.............................................................................................................................................1712
4.19.3 X20BC8083........................................................................................................................................1713
4.19.3.1 General information......................................................................................................................1713
4.19.3.2 Order data.................................................................................................................................... 1713
4.19.3.3 Technical data..............................................................................................................................1714
4.19.3.4 LED status indicators................................................................................................................... 1715
4.19.3.5 Operating and connection elements............................................................................................ 1716
4.19.3.6 POWERLINK station number.......................................................................................................1716
4.19.3.7 Ethernet interface.........................................................................................................................1716
4.19.3.8 Slot for hub expansion modules.................................................................................................. 1716
4.19.3.9 SG3.............................................................................................................................................. 1717
4.19.3.10 SG4............................................................................................................................................ 1717
4.19.4 X20BC8084........................................................................................................................................1718
4.19.4.1 General information......................................................................................................................1718
4.19.4.2 Order data.................................................................................................................................... 1718
4.19.4.3 Technical data..............................................................................................................................1719
4.19.4.4 LED status indicators................................................................................................................... 1720
4.19.4.5 Operating and connection elements............................................................................................ 1721
4.19.4.6 POWERLINK station number.......................................................................................................1721
4.19.4.7 Ethernet interface.........................................................................................................................1721
4.19.4.8 SG3.............................................................................................................................................. 1721
4.19.4.9 SG4.............................................................................................................................................. 1722
4.19.4.10 POWERLINK cable redundancy system................................................................................... 1723
4.19.4.11 Redundant supply voltage..........................................................................................................1730
4.19.5 X20BC80G3.......................................................................................................................................1732
4.19.5.1 General information......................................................................................................................1732
4.19.5.2 Order data.................................................................................................................................... 1733
4.19.5.3 Technical data..............................................................................................................................1733
4.19.5.4 LED status indicators................................................................................................................... 1734
4.19.5.5 Operating and connection elements............................................................................................ 1735
4.19.5.6 RJ45 ports....................................................................................................................................1735
4.19.5.7 EtherCAT network address switch...............................................................................................1736
4.19.5.8 Slot............................................................................................................................................... 1736
4.20 Expandable bus controllers System modules.........................................................................................1737
4.20.1 Brief information.................................................................................................................................1737
4.20.2 X20BB81............................................................................................................................................1738
4.20.2.1 General information......................................................................................................................1738
4.20.2.2 Order data.................................................................................................................................... 1738
4.20.2.3 Technical data..............................................................................................................................1738
4.20.2.4 Voltage routing............................................................................................................................. 1739
4.20.3 X20BB82............................................................................................................................................1740
4.20.3.1 General information......................................................................................................................1740
4.20.3.2 Order data.................................................................................................................................... 1740
4.20.3.3 Technical data..............................................................................................................................1740
4.20.3.4 Voltage routing............................................................................................................................. 1741
4.20.4 X20IF1091-1...................................................................................................................................... 1742
4.20.4.1 General information......................................................................................................................1742
4.20.4.2 Order data.................................................................................................................................... 1742
4.20.4.3 Technical data..............................................................................................................................1743
4.20.4.4 Use with POWERLINK bus controllers........................................................................................1743
4.20.4.5 LED status indicators................................................................................................................... 1744
4.20.4.6 Operating and connection elements............................................................................................ 1744
4.20.4.7 X2X Link interface (IF1)...............................................................................................................1744
4.20.4.8 Firmware.......................................................................................................................................1744
4.21 Fieldbus CPUs........................................................................................................................................ 1745
4.21.1 Brief information.................................................................................................................................1746
4.21.2 X20XC0201, X20XC0202, X20XC0292............................................................................................ 1747
4.23.15.8 Firmware.....................................................................................................................................1823
4.23.16 X20IF1086-2.................................................................................................................................... 1824
4.23.16.1 General information....................................................................................................................1824
4.23.16.2 Order data.................................................................................................................................. 1824
4.23.16.3 Technical data............................................................................................................................1825
4.23.16.4 LED status indicators................................................................................................................. 1826
4.23.16.5 "S/E" LED...................................................................................................................................1826
4.23.16.6 Operating and connection elements.......................................................................................... 1828
4.23.16.7 POWERLINK station number.....................................................................................................1828
4.23.16.8 Duplex LC port...........................................................................................................................1829
4.23.16.9 Firmware.....................................................................................................................................1829
4.23.16.10 Wiring guidelines for X20 modules with fiber optic cable........................................................ 1829
4.23.17 X20IF1091....................................................................................................................................... 1830
4.23.17.1 General information....................................................................................................................1830
4.23.17.2 Order data.................................................................................................................................. 1830
4.23.17.3 Technical data............................................................................................................................1831
4.23.17.4 LED status indicators................................................................................................................. 1832
4.23.17.5 Operating and connection elements.......................................................................................... 1832
4.23.17.6 X2X Link interface (IF1).............................................................................................................1832
4.23.17.7 Firmware.....................................................................................................................................1832
4.23.18 X20IF10A1-1....................................................................................................................................1833
4.23.18.1 General information....................................................................................................................1833
4.23.18.2 Order data.................................................................................................................................. 1833
4.23.18.3 Technical data............................................................................................................................1834
4.23.18.4 LED status indicators................................................................................................................. 1835
4.23.18.5 Operating and connection elements.......................................................................................... 1835
4.23.18.6 AS-interface (IF1).......................................................................................................................1835
4.23.18.7 Use with POWERLINK bus controllers......................................................................................1836
4.23.18.8 Firmware.....................................................................................................................................1836
4.23.19 X20IF10D1-1....................................................................................................................................1837
4.23.19.1 General information....................................................................................................................1837
4.23.19.2 Order data.................................................................................................................................. 1837
4.23.19.3 Technical data............................................................................................................................1838
4.23.19.4 LED status indicators................................................................................................................. 1839
4.23.19.5 Operating and connection elements.......................................................................................... 1839
4.23.19.6 Ethernet interface.......................................................................................................................1840
4.23.19.7 Use with POWERLINK bus controllers......................................................................................1840
4.23.19.8 Firmware.....................................................................................................................................1840
4.23.20 X20IF10D3-1....................................................................................................................................1841
4.23.20.1 General information....................................................................................................................1841
4.23.20.2 Order data.................................................................................................................................. 1841
4.23.20.3 Technical data............................................................................................................................1842
4.23.20.4 LED status indicators................................................................................................................. 1843
4.23.20.5 Operating and connection elements.......................................................................................... 1843
4.23.20.6 Ethernet interface.......................................................................................................................1844
4.23.20.7 Use with POWERLINK bus controllers......................................................................................1844
4.23.20.8 Firmware.....................................................................................................................................1844
4.23.21 X20IF10E1-1....................................................................................................................................1845
4.23.21.1 General information....................................................................................................................1845
4.23.21.2 Order data.................................................................................................................................. 1845
4.23.21.3 Technical data............................................................................................................................1846
4.23.21.4 LED status indicators................................................................................................................. 1847
4.23.21.5 Operating and connection elements.......................................................................................... 1847
4.23.21.6 Ethernet interface.......................................................................................................................1848
4.23.21.7 Use with POWERLINK bus controllers......................................................................................1848
4.23.21.8 Firmware.....................................................................................................................................1848
4.23.22 X20IF10E3-1....................................................................................................................................1849
6 Accessories......................................................................................................... 2661
6.1 Additional equipment for X20 modules.....................................................................................................2661
6.1.1 Tag holders, terminal locking clips...................................................................................................... 2662
6.1.2 Plain text tags......................................................................................................................................2662
6.1.3 Accessory locking clips....................................................................................................................... 2662
6.2 Locking plates........................................................................................................................................... 2663
6.3 Cable shield clamp................................................................................................................................... 2663
6.4 Shielding bracket.......................................................................................................................................2663
6.5 Terminal labeling.......................................................................................................................................2664
6.6 Labeling tool..............................................................................................................................................2664
6.7 Screwdriver................................................................................................................................................2664
6.8 POWERLINK cables................................................................................................................................. 2665
6.8.1 RJ45 to RJ45...................................................................................................................................... 2665
6.8.2 RJ45 to M12........................................................................................................................................ 2665
6.9 X2X Link cables........................................................................................................................................ 2666
6.9.1 X2X Link connection cable..................................................................................................................2666
6.9.2 Field-assembled...................................................................................................................................2666
6.9.3 General specifications for X2X Link cables........................................................................................ 2666
1 General information
Programmable logic controllers, operating and monitoring devices (e.g. industrial PCs, Power Panels, Mobile Pan-
els etc.) as well as the uninterruptible power supplies have all been designed, developed, and produced by B&R for
conventional use in industry. They were not designed, developed and manufactured for any use involving serious
risks or hazards that could lead to death, injury, serious physical damage or loss of any kind without the implemen-
tation of exceptionally stringent safety precautions. In particular, such risks and hazards include the use of these
devices to monitor nuclear reactions in nuclear power plants, their use in flight control or flight safety systems as
well as in the control of mass transportation systems, medical life support systems or weapons systems.
When using programmable logic controllers or operating/monitoring devices as control systems together with a Soft
PLC (e.g. B&R Automation Runtime or comparable product) or Slot PLC (e.g. B&R LS251 or comparable product),
safety precautions relevant to industrial control systems (e.g. the provision of safety devices such as emergency
stop circuits, etc.) must be observed in accordance with applicable national and international regulations. The same
applies for all other devices connected to the system, e.g. drives.
All tasks such as the installation, commissioning and servicing of devices are only permitted to be carried out by
qualified personnel. Qualified personnel are those familiar with the transport, mounting, installation, commissioning
and operation of devices who also have the appropriate qualifications (e.g. IEC 60364). National accident preven-
tion regulations must be observed.
The safety notices, connection descriptions (type plate and documentation) and limit values listed in the technical
data are to be read carefully before installation and commissioning and must be observed.
Electronic devices are never completely failsafe. If the programmable control system, operating/monitoring device
or uninterruptible power supply fails, the user is responsible for ensuring that other connected devices, e.g. motors,
are brought to a secure state.
Electrical components that can be damaged by electrostatic discharge (ESD) must be handled accordingly.
1.2.3.1 Packaging
Individual components
• ESD protective measures for individual components are thoroughly integrated at B&R (conductive floors,
footwear, arm bands, etc.).
• These increased ESD protective measures for individual components are not necessary for customers
handling B&R products.
During transport and storage, devices must be protected against undue stress (mechanical loads, temperature,
moisture, corrosive atmospheres, etc.).
Devices contain components sensitive to electrostatic charges that can be damaged by inappropriate handling. It
is therefore necessary to provide the required protective measures against electrostatic discharge when installing
or removing these devices (see also section 1.2.3 "Protection against electrostatic discharge").
1.2.5 Installation
• Installation must be performed according to this documentation using suitable equipment and tools.
• Devices are only permitted to be installed by qualified personnel without voltage applied.
• General safety guidelines and national accident prevention regulations must be observed.
• Electrical installation must be carried out in accordance with applicable guidelines (e.g. line cross sections,
fuses, protective ground connections).
• Take the necessary steps to protect against electrostatic discharges (see section 1.2.3 "Protection against
electrostatic discharge").
1.2.5.1 Inserting and removing I/O modules while the controller is running
I/O modules may be connected and disconnected while the controller is running under the following conditions:
• Connectors are not allowed to carry voltages and must be removed.
• Replacing a module during operation must be supported by the software; otherwise, disconnecting a mod-
ule will cause an emergency stop of the controller.
1.2.6 Operation
To operate programmable logic controllers, operating and monitoring devices, and uninterruptible power supplies,
certain components must carry dangerous voltage levels. Touching one of these parts can result in a life-threatening
electric shock. This could lead to death, severe injury or damage to equipment.
Before turning on the programmable logic controller, operating/monitoring devices or uninterruptible power supply,
the housing must be properly grounded (PE rail). Ground connections must be established even when testing or
operating operating/monitoring devices or the uninterruptible power supply for a short time!
Before turning the device on, all parts that carry voltage must be securely covered. During operation, all covers
must remain closed.
All B&R control components are designed to inflict as little harm on the environment as possible.
It is necessary to separate different materials so the device can undergo an environmentally friendly recycling
process.
Component Disposal
X20 modules Electronic recycling
Cables
Cardboard/paper packaging Paper/Cardboard recycling
1.3 Terminology
Term Explanation
SG3 System Generation 3 (SG3) - CPUs with Motorola processors
Table 4: Terminology
2 System features
Figure 1: Each module is comprised of three basic elements: Terminal block – Electronic module – Bus module
With its well thought-out details and a sophisticated ergonomic design, the X20 system is more than a remote I/O
system – it's a complete control solution. The X20 system family makes it possible to combine the exact components
needed to meet any application requirements.
• The X20 system is the ideal addition to a standard fieldbus and expands the possibilities of conventional
control systems. Simply connect it, configure it and you're done.
• Teamed up with other B&R components, the X20 system achieves its full potential and allows the imple-
mentation of applications with unimagined performance and flexibility. This type of seamless integration
is a major advantage.
2.1.2 3 x 1 = 1
Three basic elements make up one module: Terminal block – Electronic module – Bus module
This modularity results in a system that combines the advantages of both rack and I/O slice systems:
• Prewiring without the module
• Hot pluggable electronics
• Extra bus slots for added options
Figure 2: X20 modules are divided into three parts to guarantee the simplest usability
The X20 system delivers 50% more component density, perfected connection technology and optimal gran-
ularity.
• Added value
12 channels with a width of 12.5 mm allow a component density never before achieved with optimal terminal
ergonomics. As a result, the X20 system offers 50% more channels than conventional slice systems. And
this without sacrificing terminal connections.
• Uniformity
Consistent implementation of 1-, 2- or 3-wire connections – no additional jumper terminals needed.
• Granularity
1-channel and 2-channel modules: Maximum flexibility so you only have to pay for what you really need.
Note:
A 100 m X2X Link cable is available from B&R for custom assembly (model number: X67CA0X99.1000).
X20 system
100 m 100 m
XV
X20 system X67 X67 X67
The optimally scaled X20 system CPU line satisfies a wide range of needs. It can be implemented anywhere, from
standard applications to the most demanding applications with the highest performance requirements. It can even
master cycle times of 100 µs.
At B&R, RS232, Ethernet and USB are already standard equipment. Network capability and connecting USB de-
vices are therefore possible at no additional cost. In addition, every CPU has a POWERLINK interface for real-time
communication. The possibility to directly connect axes is already integrated. Although the standard features of the
CPUs can handle the majority of applications, there are also up to three multipurpose slots for additional interface
modules.
Because the X20 CPU was designed for top-hat rail installation in a control cabinet, up to 250 X20 I/O modules
– 3000 channels – can be connected directly. This provides the highest performance as well as the advantages
of the remote backplane.
A power supply integrated in the CPU with I/O supply terminals provides power for the backplane and I/O sensors
and actuators, eliminating the need for additional system components. With a direct I/O connection to an X20 CPU,
you get all the advantages of the remote backplane, i.e. the ability to repeatedly place I/O line sections anywhere
within 100 m using a cable or to add modules with IP67 protection.
XV
X20 system X67 X67 X67 X20 system
Figure 5: X20 CPUs - Direct I/O connection to X20 CPU and advantages of remote backplanes
B&R Automation Studio is the only programming tool needed for all platforms. It can be used to create application
software in all relevant IEC 61131-3 languages as well as C. Integrated visualization, NC and soft CNC functions
and web server technologies complete the range of powerful features.
Based on the latest Intel ATOM™ processor technology, X20 CPUs can effectively utilize cycle times down to
100 µs.
An extensive amount of RAM provides the user with unlimited freedom when it comes to application development.
This is complemented by battery-backed nonvolatile SRAM for task-specific data and remanent variables. In the
case of a power failure, variables that have been declared as being remanent are automatically copied from the
fast RAM to the secure SRAM. Data contents are therefore retained after the controller is restarted so that the
process can simply be resumed. A slot for a CompactFlash card is also integrated into the system to hold program
memory or application data such as recipes.
Providing the highest performance, with many standard interfaces and interface modules for expansions, yet the
dimensions are unbelievably compact. The dimensions of the CPU match those of the X20 modules, which prevents
unnecessary waste of space in the control cabinet.
Fanless operation - a demand the X20 CPUs can satisfy. None of the processors require a fan, which makes them
virtually maintenance-free.
With a width of 37.5 mm the X20 Compact CPUs are extremely compact, yet surprisingly powerful. Less powerful
than the PC-based CPUs, there are several models of Compact CPUs available in 2 performance classes.
Compact CPUs are ideal for situations where cycle times in the millisecond range are sufficient and a cost-benefit
analysis plays a decisive role. A range of models with CAN bus and Ethernet can be perfectly adapted to all
requirements, resulting in extremely sleek automation solutions.
The Compact CPU's design and dimensions correspond to the X20 system. The X20 I/O modules are connected
directly to the CPU. These are attached seamlessly to the CPU, making the entire system an extreme space saver
in the control cabinet. Despite the sleek profile, the CPU supply, the X2X Link supply, and the I/O module supply
are integrated in the system. No additional power modules are necessary.
All CPUs have at least two things in common: multitasking capability and programming with B&R Automation Studio
using all relevant IEC61131-3 languages and C.
The many different variants start with the most space-saving solution, the X20 compact CPU. This module is
equipped with an RS232 online interface and an integrated X20 module connection. Selecting another bus module
also provides an additional onboard CAN bus interface. The upper end of the product range is characterized by
CPUs with a Fast Ethernet interface. The variant with Ethernet is also available with approx. 60% more processing
power.
Remote design of I/O systems is one of the standard topologies used in automation solutions for machines and
equipment. In addition, fieldbuses with bus controllers are normally used. Larger topologies or standard fieldbuses
like CANopen, PROFIBUS DP, or DeviceNet can cause relatively long response times.
An input must travel via the bus controller to the CPU before it is processed. The output data must then return on
the same path. This is sufficient for most I/O functions. However, this response time is too long for some functions.
The best solution is for the bus controller to process the data. This type of data preprocessing is usually associated
with limited CPU functionality in the programmable bus controller.
Fieldbus CPUs with integrated fieldbus connections overcome these limitations. Fieldbus CPUs are variations of
Compact CPUs. In addition to these features, there is also the option of connecting fieldbus modules to the left side.
The full CPU functionality of the Compact CPUs plus a plug-in fieldbus module create many more possibilities than
simply data preprocessing. There are enough reserves for relatively complex application processing. Intelligent
substations are another area of use. That means a part of the machine part must continue to function, even when
separated from the main controller.
Based on the Compact CPU platform with up to two plug-in interface modules for the respective fieldbus connection,
this results in a very compact (62.5 mm and 87.5 mm), powerful and intelligent fieldbus controller.
As with the Compact CPUs, the new CPUs with fieldbus connection are available in two performance classes.
Depending on the bus module being used, the CPU has an RS232 interface or an RS232 interface plus a CAN
bus interface. The CPU with higher processing power is available with or without an onboard Ethernet interface.
Various fieldbus modules are available.
2.6.3 Programming
All CPUs have several features in common, including integrated connection of X20 modules and system multitask-
ing capability. With B&R Automation Studio, programming can be done in all IEC 61131-3 languages and in C.
XV
X20 system
Compact I/O
Figure 8: Expansion of existing control systems using standard fieldbuses and the X20 system
The X67 is the robust version of the X20 for use outside the control cabinet. The same basic technology, with an ex-
tremely robust housing and 4 to 32 channel modules, guarantees economical solutions in the roughest conditions.
The development of the XV system allows for the first time direct and manufacturer-independent control of valve
terminals. A complete digital output module in a size and form comparable with a normal DSUB connector. XV
allows any valve terminal manufacturer to be selected because it is connected directly to the standardized multiple
pin connector on the valve terminal.
Fully integrated in the remote backplane, it rounds off the X20 and X67 for complete automation solutions. One
system, several variations - advantages that pay off. You select your automation components and distribute them
as needed inside and outside the control cabinet.
Simple, tool-free wiring for fast installation. The X20 system terminal blocks use a fully integrated and proven push-
in connector system. Each terminal can also handle double wire sleeves up to a diameter of 2x 0.75 mm². The
user saves time wiring the system multiple times and distributing the signals.
The wire connections can be removed with a screwdriver. Each terminal also has an access point for a measure-
ment probe. A great deal of thought was given to designing every aspect of the X20 system. Right down to the
wire connectors.
Information:
To avoid damaging the terminals, the X20AC0SD1 B&R screwdriver should be used.
Detached Tool-free
The terminals can be prewired apart from the actual I/O Simple, tool-free wiring for fast installation. The X20 sys-
module. This provides many advantages for control cab- tem terminals use a fully integrated and proven push-
inet construction. Separate manufacturing, just-in-time in connector system. Available with 6-pin and extremely
logistics and the installation of preassembled systems compact 12-pin terminals.
during start-up become reality.
Figure 10: Easy mounting on and removal from the top-hat rail
Unlocking mechanism with two positions Defined open position makes the difference
Closed for secure fit on the top-hat rail. Open to remove a module or the entire system.
Removing a single module from the system Mount the entire system as a whole
Remove or reconnect vertically. Or just as easily removing the entire system.
2.11 Diagnostics
Outstanding diagnostic options are needed for errors to be found quickly. The X20 system offers several levels
of diagnostics:
• Direct on the module using visual LED displays. Bus status, I/O status and channel states are displayed
in direct relationship to the channels or the function. The different states are displayed in different ways,
e.g. green for OK, red for error.
• Via software in the cyclic data image. With the X20 system, status data does not result in an additional
communication load, which would result in considerable differences between theoretically possible bus
speeds and real requirements during operation. All necessary status data is always transferred cyclically,
with no exceptions.
• Expanded diagnostic data in acyclic data traffic without loss in performance. If a problem occurs, detailed
diagnostic data can be requested from the application by the respective module using an asynchronous
channel. This does not result in additional communication load and cycle times remain unchanged.
Figure 11: Visual diagnostics directly on the module using LED indicators
2.11.1 re LEDs
Each X20 system module has a LEDs for diagnostics at the top.
The operating state of the module firmware is indicated by the two topmost LEDs r (green) and e (red).
Additional LEDs depend on the module and generally indicate the status of I/O channels. Green LEDs are usually
used for inputs, while yellow is used for outputs. These I/O LED status indicators are only operational in RUN
mode on some modules.
There is a difference between "blinking" and "single flash": when blinking, the LED is on 50% of the time and off
50% of the time; with single flash, the LED only flashes quickly. With "double flash", the LED blinks twice quickly
followed by a pause.
LED r (green) e (red) Description Note
Off Off No power to module Module does not have power.
Single flash On Firmware is not valid Invalid firmware. Occurs when a firmware update has been interrupted.
The firmware is reloaded as soon as the X2X Link master is active again,
but only if the module is also specified in the configuration.
Single flash Off RESET mode Module not yet detected by the X2X Link master
Double flash Off BOOT mode Usually a firmware transfer. Some modules remain in single flash mode
(RESET mode with communi- with a firmware transfer. Depending on the configuration, a firmware
cation) transfer can take several minutes.
Blinking Off PREOPERATIONAL mode Modules whose slot is configured for a different module (or none at all)
remain in PREOPERATIONAL mode. It could be that an incorrect mod-
ule is inserted. An incorrect slot number might be set for bus modules
with node number switches.
On Off RUN mode Everything is OK.
On Blinking RUN mode with an I/O channel An error or warning is present on one or more I/O channels.
error Which channel error on the module is being indicated depends on the
module and can be determined with the respective module description.
On On RUN mode with a module error The module has an error that affects all of its channels.
If no LEDs are lit, then the module is not supplied with power.
If the green r LED is constantly lit and the red e LED is off, then everything is OK.
If the modules remain in a green single flash mode, there is no connection to the X2X Link master, or the X2X Link
master is not yet running. Single flash is output for some modules during a firmware update.
If the module outputs a green double flash, the firmware is being updated. This can take several minutes depending
on the configuration. A firmware update usually only takes place once after the module has been replaced or if
new firmware has been loaded to the master CPU during a project update.
If the modules are blinking green, it means that there are different X2X Link modules in that slot (or none at all).
Machine variation B
Variation B shows the necessary electronic modules but the modules necessary for vari-
ation A are missing. The distribution of the free bus modules for the variations is also
clear: The variable I/O modules can be very easily connected to the required electrically
isolated groups and don't need to be attached in the back. The extensive process of
taking apart the configuration to expand existing electrically isolated groups is also elim-
inated. Simply insert the electronic module and attach the terminal block.
X20 system
X67 system
#10 #11 #12 #30 #31 #20 #21 #22 #50 #51 #52
X2X Link
Sensor 1
Sensor 2
+24 VDC +24 VDC
GND GND
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 7 Sensor 8
Sensor 9 Sensor 10
Sensor 11 Sensor 12
2.18 Redundancy
The X20 system provides the following forms of redundancy:
• Controller
• Network
• Power supply modules for X20 standalone devices and expandable POWERLINK bus controllers
• X2X Link supply
The first three areas are covered in the "Redundancy for control systems" user's manual. The user's manual is
available in the Downloads section of the B&R website www.br-automation.com.
For a description of the redundant X2X Link supply, see section 3.20 "X2X Link supply".
Open fieldbus
Several bus controllers for standard fieldbus technologies like POWERLINK, DeviceNet, PROFIBUS, CANopen,
ModbusTCP or EtherNet/IP are available to connect X20 modules to existing control systems. Fieldbus configura-
tors transparently integrate the X20 system into the 3rd-party development environment.
Variable
Supplies the bus controller, X2X Link, and internal I/O
Bus controller power supply module X20PS940x
Bus controller fieldbus interface X20BC00xx
I/O modules
I/O modules
Variable
Figure 15: X20 system configurator for connection to X2X Link backplane
X20BT9x00 bus transmitter
77
Mechanical and electrical configuration
3.1 Dimensions
3.1.1 X20 CPUs with one slot for interface modules
150 +0.2 85
99
200 +0.2 85
99
37.5 +0.2 75
99
62.5 +0.2 75
99
Figure 19: Dimensions of the fieldbus CPUs and expandable bus controller with one additional slot
87.5 +0.2 75
99
Figure 20: Dimensions of the fieldbus CPUs and expandable bus controller with two additional slots
12.5 +0.2 75
99
To ensure CAD support, the dimensions are included in the ECAD macros in 2D. STEP data is available to allow
3D viewing.
The STEP data can be found in the Downloads section of the B&R website at www.br-automation.com under the
respective module.
The electronics in a machine must be designed in a way that optimizes use of available space and materials.
Graphic ECAD systems have proven themselves as the right tool for this job.
Every module in the X20 system is delivered with pre-designed electronic descriptions of the mechanical dimen-
sions, electrical signals and module functions. These macros can be loaded directly to proven ECAD systems. The
wiring plans are automatically applied by the configuration and programming system, Automation Studio. Design
and changes are immediately reflected at all levels of development. This saves time for the more important tasks
and prevents errors right from the start. The accelerated development, programming, maintenance and documen-
tation involved with the X20 system mean lower costs, enhanced quality and increased sales by earlier entry into
the market.
System printers and standard identification labels are supported by the appropriate printer software. Printing can
be done manually from table calculations or directly from ECAD software (all methods are supported). The software
and printer systems correspond with the Weidmüller standard.
3.3 Installation
A top-hat rail conforming to the EN 60715 standard (TH35-7.5) is required to mount the PLC. The conductive top-
hat rail is fastened to the back wall of the control cabinet.
The complete system including all individual modules is hung in the desired location on the top-hat rail with the
unlocking mechanisms open and locked in place by closing the unlocking mechanisms. Finally, the modules are
equipped with the prewired terminal blocks.
Information:
Only horizontal or vertical mounting orientation is permitted.
10 b = n 1) · 12.5 +0.2 10
35
99
40.2
35
1)
n ... Number of modules
35 99 35
10
· 12.5 +0.2
h = n 1)
10
40.2
1)
n ... Number of modules
Information:
The controller must be secured against slipping. An end bracket or ground terminal can be used for
securing.
3.4 Wiring
In order to achieve a secure connection in the terminal blocks, wires must be stripped accordingly.
7 to 9 mm
Information:
The wire stripping length must not be more or less than 7 to 9 mm.
Figure 26: Slots through which the cable ties are fed
3.6 Shielding
In principle, the shield must be grounded in all shielded cables:
• Analog signals (inputs and outputs)
• Interface modules
• Counter modules
• X2X Link cables
• Fieldbus connections (PROFIBUS DP, CAN bus, etc. )
In general, the following guidelines apply for shielding:
• The X20 top-hat rail must always be mounted to a conductive backplane.
• Shielded cables must be grounded on both sides.
The shield is twisted and connected to the bus module's ground connection using a cable lug (2.8 x 0.5 mm). The
cable is additionally secured to the terminal block using a cable tie (stress relief).
Information:
The ground connection should be made as short and with as little resistance as possible.
The X20 cable shield clamp (model number X20AC0SG1) is latched to the terminal block and connected to the bus
module's ground connection using a cable lug. Cable ties are used to press the shield against the grounding plate.
The X20 shielding bracket (model number X20AC0SF9.0010) is installed below the X20 system. The shield is
pressed against the shielding bracket using ground terminals from another manufacturer (e.g. PHOENIX or WAGO)
or a cable tie.
Attaching the shield with a ground terminal Attaching the shield with a cable tie
① ①
To reduce the EMC emissions most effectively, the cable shield must be as long as possible after the cable tie
(see ① in the diagram above).
Content of delivery
• 10 X20 shielding brackets
• Installation template
Information:
Using POWERLINK cables offered by B&R (X20CA0E61.xxxx and X67CA0E41.xxxx) satisfies the EN
61131-2 product standard.
For any further requirements, the customer must take additional measures.
Wiring diagram
r ≥ rmin
r ≥ rmin
Figure 30: Wiring diagram for X20 modules with an Ethernet cable
Danger!
In order to guarantee a specific supply voltage, a SELV power supply that conforms to IEC 60204 must
be used to supply the bus and I/O.
X20BM11 X20BM01
Figure 31: The bus module replaces the rack in the X20 system
The bus module is the backbone of the X20 system regarding the bus supply and bus data as well as the I/O supply
for the electronics modules. Each bus module is an active bus station, even without an electronics module. There
are two variations of the bus module:
• Interconnected I/O supply
• I/O supply isolated to the left (for power supply modules)
Potential group "In" Potential group "Out 1" Potential group "Out 2"
3.15 Power supply module for internal I/O supply and bus supply
The X2X Link is fed by the X20BR9300 bus receiver. After approx. 30 modules (see section 3.23 "Calculating the
power requirements" for a calculation example), the supply must be "refreshed". The X20PS3300 power supply
module is used for this. This module is equipped with a feed for X2X Link as well as for the internal I/O supply.
Using the X20BM01 bus module and organizing the power supply bus modules accordingly allows various potential
groups to be implemented (e.g. for input groups or various power circuits for the outputs).
BR9300 + BM01
PS2100 + BM01
PS2100 + BM01
X2X
I/O I/O I/O
Link
1 A slow-blow 1)
U2/24 VDC
The bus transmitter has an integrated internal I/O supply feed. This saves a power supply module for the last
potential group.
Keep in mind: this potential group is separated from the rest of the potential groups by an I/O module with the
bus module.
I/O module + BM01
BR9300 + BM01
PS2100 + BM01
BT9x00 + BM11
X2X
I/O I/O I/O
Link
U2/24 VDC
The X2X Link remote backplane is supplied separately from the I/O points. This ensures that the remote backplane
doesn't fail if there is a power failure on the I/O side, for example with an emergency stop. After approx. 30 modules,
it is necessary to "refresh" with a power supply module for X2X Link.
To achieve increased supply security, it is possible to set up a redundant X2X Link supply. To do so, the necessary
X2X Link power must be determined and then covered by the corresponding quantity plus at least one additional
X2X Link power supply module. This guarantees the functionality of the remote backplane even if the X2X Link
supply fails.
Please note the following for the correct calculation:
• To determine the necessary X2X Link power, calculate using 75% of the power supply module's rated
power during parallel operation.
Information:
This must be done for all power supply modules at the same time for a non-redundant X2X Link supply
or when completely turning the X2X supply of an X20 module block on/off.
It is possible to set up potential groups through the use of different supplies for the power supply modules.
BR9300 + BM01
PS2100 + BM01
PS3300 + BM01
X2X X2X
I/O I/O I/O
Link Link
1 A slow-blow 1) 1 A slow-blow 1)
U2/24 VDC
The X20PS3300 power supply module supplies both the X2X Link and I/O; the X20PS2100 power supply module
only supplies the I/O.
Multiple X20PS3300 power supply modules can be set up in parallel. It is possible to set up potential groups through
the use of different supplies.
BR9300 + BM01
PS3300 + BM01
PS3300 + BM01
2)
U2/24 VDC
The X20PS3300 power supply module supplies both X2X Link and the I/O.
The operating principle "Safe cutoff of a potential group" allows the user to implement safety functions that satisfy
the requirements of ISO 13849 within a B&R system when using an external safety relay.
The safety function is limited to cutting off or interrupting the power to the connected actuators.
Functionality
An external safety relay is connected to the I/O supply for the potential group. When the functional safe state is
requested or a "Failsafe" state occurs, then this safety relay cuts off the I/O supply of the potential group. The
power is then also cut off for all actuators connected to this potential group.
The operating principle is confined to machine manufacturing applications, and therefore implicitly to the following
standards:
• ISO 13849-1:2007 and ISO 13849-2:2013
Requirements of other standards are not taken into consideration.
It is the user's responsibility to clarify guidelines for the use of safety-related B&R components with the respective
authorities and to ensure these guidelines are met.
B&R will not assume warranty or liability for damages that occur due to:
• Improper use
• Non-observance of standards and guidelines
• Unauthorized modifications to devices, connections and settings
• Operation of unauthorized or unsuitable devices or device groups
• Failure to follow the safety notices covered in this manual
• Malfunctions caused by the external safety relay
Safety functionality is only permitted to be implemented by personnel with appropriate training in safety technology
and knowledge of applicable regulatory and technical requirements.
Use of safety-related products is restricted to the following persons:
• Qualified personnel who are familiar with relevant safety concepts for automation technology as well as
applicable standards and regulations
• Qualified personnel who plan, develop, install and commission safety equipment in machines and systems
Qualified personnel in the context of this manual's safety guidelines are those who, because of their training,
experience and instruction combined with their knowledge of relevant standards, regulations, accident prevention
guidelines and operating conditions, are qualified to carry out essential tasks and recognize and avoid potentially
dangerous situations.
In this regard, sufficient language skills are also required in order to be able to properly understand this manual.
The operating principle applies to a potential group in the X20 system. For information about how to create a
potential group in the X20 system, see section 3.11 "Potential groups".
When implementing the operating principle, each X20 potential group must be supplied by a single power supply
module. Only X20BM01, X20BM23 and X20BM26 modules that guarantee the interruption of the internal I/O supply
to the left are permitted for use as bus modules for the power supply module. This ensures that each potential
group in the X20 system will receive power from exactly one power supply module and prevents the possibility
of multiple power sources.
The operating principle of the X20 system has been tested by TÜV Süd, with the results documented under report
number BE85906T.
Modules must be protected against impermissible dirt and contaminants. The maximum permissible level of dirt and
contaminants is Pollution Level II as specified in the IEC 60664 standard. This can be achieved through installation
in a control cabinet that provides IP54 protection.
When using the operating principle, uncoated X20 modules must not be operated in condensing relative humidity
or with ambient temperatures below 0°C.
3.21.6.2 Timing
A maximum cutoff time of 500 ms must be assumed for the potential group for worst case scenarios. This time is
needed to guarantee that energy stored within the module is discharged and the actuators are cut off in worst case
scenarios. The cutoff times needed for the upstream external safety relay and actuator must also be added.
Worst case conditions for "Output = Off"
• Digital output: <5 V
• Analog output: <100 mV
The actual duration of cutoff can be calculated with the following formula.
If the result is tspec = >500 ms, then the worst-case assumption from section 3.21.6.2.1 "Worst case scenario" applies.
Information:
• The calculated load-dependent cutoff time must be verified by a test measurement!
• At the time a safety function is requested, there is no guarantee that the outputs used to cal-
culate the load-dependent cutoff time are enabled. For example, if an output is disabled at the
time of a request, then the respective internal capacities in the module will not be discharged
in the calculated time (tspec). The worst-case time of 500 ms should be taken into account in this
situation. If the output is enabled from the functional application (shown in the sketch as the
interval tapplication) during the worst-case time (<500 ms), then the output subsequently remains
enabled for the calculated time.
Uin
Worst-case cutoff
Load-dependent cutoff
Uoff
Time
t application t spec
The potential group can be made up only of modules in accordance with the table in section 3.21.5.1 "Suitable
modules". Modules not listed in this table would compromise the "absence of feedback" of the external cutoff and
therefore put the safety function at risk.
To ensure clarity and that the external cutoff is triggered when a fault occurs, installing multiple power supply
sources in a potential group is not permitted.
SELV/PELV power supplies must be used for both the bus supply (X2X) and the module supply; otherwise, safe-
ty-related malfunctions can occur due to overvoltages.
For modules with isolated I/O potential for sensors and actuators, the upstream safety relay must shut off the supply
for both the sensors and actuators; otherwise, energy regeneration cannot be excluded.
Power supply
X20 module
for +24 VDC potential group
23 24 (inputs and outputs)
E-stop
Power supply
X20 module
for +24 VDC potential group
(inputs and outputs)
X2
E-stop Reference potential for
GND potential group, 0 VDC Outputs
(inputs and outputs)
Load
X20DO2322
X20SI4100 X20SP1130
Load
E-stop
+
+24 VDC
X20DO8332
X20SI4100 X20SP1130
Load
E-stop
+
+24 VDC
Figure 41: Circuit example 3: With X20SP1130 power supply module and X20DO8332
Provided that the external components used (E-stop button, load) satisfy the respective requirements, this example
can achieve PL e.
The operating principle "Safe cutoff of a potential group" only applies to the B&R modules used. All other parts
of the safety chain, such as the application, upstream sensors or downstream actuators are NOT included in this
principle.
For this reason, it is important to take the following points into consideration:
• Ensure proper wiring of the safety relay with the I/O supply. A short circuit between the output of the safety
relay and an external 24 V voltage source can cause an unintended supply of 24 V to the internal supply
voltage of the potential group. As a result, the safety function can no longer be guaranteed, which means
that ALL of the channels in the potential group can no longer be cut off by the upstream safety switching
device.
• Make sure that ALL of the potential group's input and output channels and the connected sensors and
actuators are wired properly. A short circuit between an input or output of the potential group and an external
24 V voltage source can cause the unintended feedback of 24 V to the internal supply voltage of the
potential group. As a result, the safety function can no longer be guaranteed, which means that ALL of the
output channels in the potential group can no longer be cut off by the upstream safety relay.
• In accordance with EN ISO 13849-2:2013, Appendix D.2, Table D.4, a short circuit between any two con-
ductors can be excluded, provided that:
° they are permanently connected and protected against external damage (e.g. using a cable duct
or armored conduit)
° OR they are in separate plastic-sheathed cables
° OR they are installed within an electrical enclosure (provided that both the conductors and the
enclosure meet the appropriate requirements [see EN 60204-1 (IEC 60204-1)])
° OR they are individually shielded with a ground connection
Danger!
Please observe the following safety notices. Failure to observe one of the following notices can lead
to loss of safety functionality and may result in serious injury.
• The safety relay determines which category (according to ISO 13849) is achieved.
• When using the operating principle, it is the user's responsibility to adhere to the relevant
standards and safety directives. The notices provided in sections 3.21.1 "General information"
through 3.21.4 "Qualified personnel" regarding functionality, applicable standards, proper use
and qualified personnel are also to be observed.
• The safety function is limited to cutting off or interrupting the power to connected devices.
Safety functions that require actively powering on an actuator in a safe state cannot be imple-
mented with this function.
• For all potentials supplying the modules, SELV/PELV power supplies must be used.
• The potential groups for which the operating principle is applied must only contain modules
listed in the table in section 3.21.5.1 "Suitable modules".
• When using the operating principle with uncoated X20 modules, the modules must not be op-
erated in condensing relative humidity or with ambient temperatures below 0°C.
• It is not permitted to mix modules from different systems (X20, X67) within a potential group.
• It is not permitted to install multiple power supply modules in a potential group (particularly
with regard to power supply modules that also supply the bus supply).
• Ensure that the upstream safety relay is wired properly.
• Ensure that ALL sensors and actuators connected to the potential group are wired properly.
• Be aware of the maximum safety-related response time of 500 ms when shutting down the
potential group. The cutoff times needed for the upstream external safety relay and actuator
must also be added. Using the formulas defined in section 3.21.6.2.2 "Load-dependent cutoff
time", it is possible to achieve cutoff times under 500 ms.
• The calculated load-dependent cutoff time must be verified by a test measurement!
• For modules with isolated I/O potential for sensors and actuators, the upstream safety relay
must shut off the supply for both the sensors and actuators.
• The ground connections should be used as functional ground and not as protective ground
and must not be connected to the 24 V supply voltage (GND is permitted). There must not be
any protective components between the ground and the 24 V supply voltage.
The X2X Link provides a complete remote backplane, which is used for communicating between bus modules and
over the X2X Link cable. Systems based on X2X Link can be combined with one another as needed.
The following connection overviews illustrate combinations of different systems that are based on X2X Link. The
model numbers indicate which standard cables available from B&R can be used to connect with one another.
X2X Link X2X Link X2X Link X2X Link X2X Link X2X Link
Attachment cable Connection cables Open cables Attachment cable Open cables Attachment cable
X67CA0X21.xxxx X67CA0X01.xxxx X67CA0X41.xxxx X67CA0X21.xxxx X67CA0X41.xxxx X67CA0X21.xxxx
X67CA0X31.xxxx X67CA0X11.xxxx X67CA0X51.xxxx X67CA0X31.xxxx X67CA0X51.xxxx X67CA0X31.xxxx
X67PS1300 X67 I/O X67 I/O X20 system X67PS1300 X67 I/O X67 I/O
Figure 42: Connection overview - Combining X20, X67 and compact I/O system
X2X Link X2X Link X2X Link X2X Link X2X Link
Attachment cable Connection cables Open cables Attachment cable Open cables
X67CA0X21.xxxx X67CA0X01.xxxx X67CA0X41.xxxx X67CA0X21.xxxx X67CA0X41.xxxx
X67CA0X31.xxxx X67CA0X11.xxxx X67CA0X51.xxxx X67CA0X31.xxxx X67CA0X51.xxxx
IP67 XV IP20 XV
X67PS1300 X67 I/O X20 system X67PS1300 X67 I/O
Figure 43: Connection overview - Combining X20, X67 and valve terminal connections
1)
X2X+ (optional)
1
1)
X2X+ (optional)
2
In: X2X White
3
In: X2X⊥ Black
4
In: X2X\ Blue
5
Shield
6
Out: X2X White
7
Out: X2X⊥ Black
8
Out: X2X\ Blue
9 10 11 12
+ Shield
+24 VDC supply
Supply ⊥
-
1) Used to forward the X2X Link supply when using IP67 modules.
Signal Cable type Model number
X2X Link In Open cables1) X67CA0X41.xxxx
X67CA0X51.xxxx
X2X Link Out Attachment cable1) X67CA0X21.xxxx
X67CA0X31.xxxx
X2X Link in/out Cable for custom assembly, 100 m X67CA0X99.1000
1
In: X2X⊥ Black
2
In: X2X\ Blue
3
Shield
4
Out: X2X White
5
Out: X2X⊥ Black
6
Out: X2X\ Blue
7
Shield
8
+24 VDC for X2X Link
9 10 11
+ Supply ⊥
+24 VDC for I/O
X2X Link and -
-
I/O supply
Shield
4
Shield
8
X2X+ Red
9 10 11
STATUS 2 STATUS 1
Bus transmitter
When calculating the power requirements for bus transmitters, it is important to know whether they are only being
used as such or are also being used as an I/O power supply module.
Model number I/O internal power Bus power
When operated as When operated as a
a bus transmitter bus transmitter and I/
O power supply module
X20BT9100 -0.1 W +240 W -0.5 W
X20BT9400 -0.1 W +240 W -0.5 W
Information:
For a calculation example, see 3.23.1 "Example 1" and 3.23.2 "Example 2".
Embedded parameter chip
On modules with 0.01 W power requirements, it is only possible to read the embedded parameter chip if the I/
O supply is also active. Information about the embedded parameter chip can be found in the 2.12 "Embedded
parameter chip" section.
3.23.1 Example 1
Calculating the power requirements for the bus and 24 VDC I/O supply with the following hardware configuration:
Module Bus power [W] I/O-internal power [W] I/O-external power [W] Sensor/Actuator supply [W]1)
X20DI4371 0.14 0.59 - 12.00
X20DI2371 0.12 0.29 - 12.00
X20DO4322 0.16 0.49 48.002) 12.00
X20DO4322 0.16 0.49 48.002) 12.00
X20BT9100 0.50 0.10 - -
Subtotal 1.96 96.00 48.00
Total 1.08 145.96
(=1.96 + 96.00 + 48.00)
The total power to be supplied by the 24 VDC I/O power supply is 145.86 W. One power supply module is already
integrated in the X20BR9300 bus receiver. The power comparison indicates that the power provided by the power
supply module is sufficient.
Bus power [W] Power 24 VDC I/O supply [W]
X20BR9300 +7.00 +240.001)
Power requirements of I/O modules -1.08 -145.96
Power requirements of all bus modules -0.78 -
Remaining power +5.14 +94.04
3.23.2 Example 2
The I/O modules are divided into 3 potential groups in this example:
Potential group 1 Potential group 2 Potential group 3
Digital input modules Digital output modules Analog input modules and temperature modules
Calculating the power requirements for the bus and 24 VDC I/O supply per potential group with the following
hardware configuration:
Potential group 1
Module Bus power [W] I/O-internal power [W] I/O-external power [W] Sensor/Actuator supply [W]1)
X20DI6371 0.15 0.88 - -
X20DI6371 0.15 0.88 - -
X20DI2377 0.15 0.82 - 12.00
Subtotal 2.58 - 12.00
Total 0.45 14.58
(= 2.58 + 12.00)
Potential group 3
Module Bus power [W] I/O-internal power [W] I/O-external power [W] Sensor/Actuator supply [W]
X20AI4622 0.01 1.10 - -
X20AI4622 0.01 1.10 - -
X20AT4222 0.01 1.10 - -
X20AT2402 0.01 0.72 - -
X20BT9100 0.50 0.10 - -
Subtotal 4.12 - -
Total 0.54 4.12
It is then necessary to perform a power comparison between the power needed by the I/O modules and the power
supplied by the power supply modules.
Potential group 1 is supplied by the supply module integrated in the X20BR9300 bus receiver. The total power
supplied by the bus, including all bus modules, is 3.04 W (= 1.22 W +1.82 W). The total amount of power that must
be provided for the potential group 1 via the 24 VDC I/O supply is 14.58 W.
The power comparison indicates that the power provided by the power supply module integrated in the X20BR9300
is sufficient.
Potential group 1 Bus power [W] Power 24 VDC I/O supply [W]
X20BR9300 +7.00 +240.001)
Power requirements of I/O modules -1.222) -14.583)
Power requirements of all bus modules -1.82 -
Remaining power +3.96 +225.42
In potential groups 2 and 3, the 24 VDC I/O supply is fed via the X20PS2100 power supply module. One power
supply module is needed for each potential group.
The power comparison indicates that the power provided by the X20PS2100 is sufficient.
Potential group 2 Power 24 VDC I/O supply [W]
X20PS2100 +240.001)
Power requirements of I/O modules -109.04
Remaining power +130.96
Power supply modules are used to provide power to an X20 system. The power supply modules are either a
separate module or part of a CPU or a bus controller.
The power consumed by the power supply modules is passed on to the X20 system, taking into consideration
its own power requirements and the effectiveness of the power supplies. The data sheets for the power supply
modules list their own power requirements and power loss (as maximum power consumption). With the formulas
in the following sections, the exact power consumption can also be calculated. This calculation is explained using
an example.
The following image shows where the power supply module uses power for its own requirements. It also shows
where the power supply module uses power to supply the system and where power loss occurs.
Figure 44: Power supply modules draw power at up to three supply points
Table 14: Power consumption of power supply modules without X2X Link supply
II/O ... I/O summation current of all I/O modules supplied by this power supply module
ΣX67 ... Sum of X67 modules (max. = 8)
X20BR9300
0.4 0.1 + IIO2 × 0.005
Table 15: Power consumption of power supply modules with X2X Link supply
ΣPX2X ... Sum of the bus power consumption of all modules in the X20 system (compact CPU, fieldbus CPU, BC, BR, I/O, BM, BT)
n ... Number of all power supply modules in the X20 system with X2X Link supply, including X20BR9300
II/O ... I/O summation current of all I/O modules supplied by this power supply module
Table 16: Power consumption of power supply module for X20 standalone devices
POut ... Sum of power consumption values of all modules (HB) supplied by the power supply module
3.24.6 Example
Calculating the total internal power consumption of a BR9300 bus receiver with the following hardware configura-
tion:
Module Bus power [W] I/O-internal power [W]
X20DI4371 0.14 0.59
X20DI2371 0.12 0.29
X20DO4322 0.16 0.49
X20DO4322 0.16 0.49
X20BT9100 0.50 0.10
Total 1.08 1.96
Two power values have to be calculated in order to determine the entire internal power consumption of the bus
receiver.
• Internal X2X Link power consumption of the X20BR9300
• Internal I/O power consumption of the X20BR9300
3.24.6.1 Calculating the internal X2X Link power consumption of the X20BR9300
The I/O summation current of all I/O modules supplied by the X20BR9300 is needed to calculate the internal I/O
power consumption. The I/O summation current is composed of three parts:
• Internal power consumption of the I/O modules
• Sum of the output currents
• Sum of the actuator currents
DO
0.35 A 0.4 A
Actuator 1
Actuator 2
0.1 A 0.08 A
0.5 A 0.3 A
Actuator 4
Actuator 3
0.15 A 0.09 A
DO
0.45 A 0.5 A
Actuator 1
Actuator 2
0.07 A 0.1 A
0.35 A
Actuator 3
0.09 A
The following 3 power values must be added together to calculate the total internal power of the X20BR9300:
• Power consumption - Bus
• Power consumption - I/O-internal
• Power consumption - X2X Link-internal
DO
0.45 A 0.5 A
Actuator 1
Actuator 2
0.07 A 0.1 A
0.35 A
Actuator 3
0.09 A
All modules
Product ID Short description on page
X20DO6325 X20 digital output module, 6 outputs, 24 VDC, 0.5 A, source, open line and overload detection, 2-wire connec- 1210
tions
Analog input modules
X20AI1744 X20 analog input module, 1 full-bridge strain gauge input, 24-bit converter resolution, 5 kHz input filter 129
X20AI1744-3 X20 analog input module, 1 full-bridge strain gauge input, 24-bit converter resolution, 5 Hz input filter 129
X20AI2222 X20 analog input module, 2 inputs, ±10 V, 13-bit resolution, configurable input filter 144
X20AI2237 X20 analog input module, 2 inputs, ±10 V, 16-bit resolution, each channel electrically isolated and with own 152
sensor supply
X20AI2322 X20 analog input module, 2 inputs, 0-20 mA / 4-20 mA, 12-bit converter resolution, configurable input filter 167
X20AI2437 X20 analog input module, 2 inputs, 4 to 20 mA, 16-bit resolution, each channel electrically isolated and with 176
own sensor supply
X20AI2438 X20 analog input module, 2 inputs, 4 to 20 mA, 16-bit resolution, each channel electrically isolated and with 193
own sensor supply, HART protocol supported
X20AI2622 X20 analog input module, 2 inputs, ±10 V or 0 to 20 mA / 4 to 20 mA, 13-bit resolution, configurable input filter 249
X20AI4222 X20 analog input module, 4 inputs, ±10 V, 13-bit resolution, configurable input filter 259
X20AI4322 X20 analog input module, 4 inputs, 0-20 mA / 4-20 mA, 12-bit converter resolution, configurable input filter 267
X20AI4622 X20 analog input module, 4 inputs, ±10 V or 0 to 20 mA / 4 to 20 mA, 13-bit resolution, configurable input filter 276
X20AI8221 X20 analog input module, 8 inputs, ±10 V, 13-bit converter resolution 286
X20AI8321 X20 analog input module, 8 inputs, 0-20 mA, 12-bit resolution 294
X20AP3111 X20 energy measurement module, 3 analog inputs 480 VAC, 50/60 Hz, 4 analog inputs 20 mA AC, calculates 304
effective, reactive and apparent power/energy, calculates root mean square values, 240 V keyed
X20AP3121 X20 energy measurement module, 3 analog inputs 480 VAC, 50/60 Hz, 4 analog inputs 1 A AC, calculates 304
effective, reactive and apparent power/energy, calculates root mean square values, 240 V keyed
X20AP3131 X20 energy measurement module, 3 analog inputs 480 VAC, 50/60 Hz, 4 analog inputs 5 A AC, calculates 304
effective, reactive and apparent power/energy, calculates root mean square values, 240 V keyed
X20AP3161 X20 energy measurement module, 3 analog inputs 480 VAC, 50/60 Hz, 4 analog inputs 333 mV AC, calculates 304
effective, reactive and apparent power/energy, calculates root mean square values, 240 V keyed
Analog output modules
X20AO2437 X20 analog output module, 2 outputs, 4 to 20 mA / 0 to 20 mA or 0 to 24 mA 16-bit resolution, single channel 390
electrically isolated
X20AO2438 X20 analog output module, 2 outputs, 4 to 20 mA / 0 to 20 mA or 0 to 24 mA 16-bit resolution single channel 401
electrically isolated, supports the HART protocol
X20AO2622 X20 analog output module, 2 outputs, ±10 V / 0 to 20 mA / 4 to 20 mA, 13-bit resolution 454
X20AO2632 X20 analog output module, 2 outputs, ±10 V / 0 to 20 mA, 16-bit resolution 460
X20AO2632-1 X20 analog output module, 2 outputs, ±11 V / 0 to 22 mA, 16-bit resolution 467
X20AO4622 X20 analog output module, 4 outputs, ±10 V / 0 to 20 mA / 4 to 20 mA, 13-bit resolution 474
X20AO4632 X20 analog output module, 4 outputs, ±10 V / 0 to 20 mA, 16-bit resolution 481
X20AO4632-1 X20 analog output module, 4 outputs, ±11 V / 0 to 22 mA, 16-bit resolution 489
X20AO4635 X20 analog output module, 4 outputs, ±10 V / 0 to 20 mA, 16-bit resolution low temperature drift 498
Bus controllers
X20BC0043 X20 bus controller, CANopen interface, order 1x TB2105 terminal block separately. Order bus base, power 507
supply module and terminal block separately.
X20BC0043-10 X20 bus controller, CANopen interface, configuration supported by the B&R FieldbusDESIGNER, order 1x 514
TB2105 terminal block separately. Order bus base, power supply module and terminal block separately.
X20BC0053 X20 bus controller, DeviceNet interface, order 1x TB2105 terminal block separately. Order bus base, power 521
supply module and terminal block separately.
X20BC0063 X20 bus controller, PROFIBUS DP interface, 9-pin DSUB connection, order bus base, power supply module 527
and terminal block separately.
X20BC0073 X20 bus controller, CAN I/O interface, order 1x TB2105 terminal block separately. Order bus base, power supply 532
module and terminal block separately.
X20BC0083 X20 bus controller, POWERLINK interface, integrated 2x hub, 2x RJ45 connection, order bus base, power 537
supply module and terminal block separately.
X20BC0087 X20 bus controller, Modbus/TCP or Modbus/UDP interface, integrated 2x switch, 2x RJ45 connection, order 542
bus base, power supply module and terminal block separately.
X20BC0088 X20 bus controller, EtherNet/IP interface, integrated switch, web interface 2x RJ45 connection, order bus base, 547
power supply module and terminal block separately.
X20BC00E3 X20 bus controller, PROFINET interface, integrated 2x switch, 2x RJ45 connection, order bus base, power 552
supply module and terminal block separately.
X20BC00G3 X20 bus controller, EtherCAT interface, 2x RJ45 connection, order bus base, power supply module and terminal 558
block separately.
X20BC0143-10 X20 bus controller, CANopen interface, 9-pin DSUB, configuration supported by the B&R FieldbusDESIGNER, 562
order 1x 7AC911.9 connector separately. Order bus base, power supply module and terminal block separately.
Bus modules
X20BM01 X20 supply bus module, internal I/O supply interrupted to the left 584
X20BM05 X20 supply bus module with node number switch, internal I/O supply is isolated to the left 586
X20BM11 X20 bus module, 24 V coded, internal I/O supply is interconnected 588
X20BM12 X20 bus module, 240 V coded, internal I/O supply is interconnected 590
X20BM15 X20 bus module with node number switches, internal I/O supply is interconnected 592
X20BM21 X20 bus module for double-width modules, internal I/O supply is isolated to the left 594
X20BM31 X20 bus module for double-width modules, internal I/O supply is interconnected 596
X20BM32 X20 bus module, 240 V coded, for double wide modules, internal I/O supply is interconnected 598
Bus receivers and transmitters
X20BR9300 X20 bus receiver, X2X Link, supply for X2X Link and internal I/O supply, X20 locking plates (left and right) 601
X20AC0SL1/X20AC0SR1 included
X20BT9100 X20 bus transmitter, X2X Link, supply for internal I/O supply 607
The X20AI1744 and X20AI1744-3 modules work with both 4-line and 6-line strain gauge cells. If a 6-line strain
gauge cell is connected, the line compensation no longer functions. This module concept requires compensation
in the measurement system. This compensation eliminates the absolute uncertainty in the measurement circuit,
suchas component tolerances, effective bridge voltage, or zero offset. The measurement precision refers to the
absolute (compensated) value, which will only change as a result of changes in the operating temperature.
The AI1744 analog input module is available in two versions:
Model number Description
X20AI1744 The module is equipped with a 5kHz input filter for fast signal sequences. It therefore also allows high frequency signals and
disturbances to pass through.
X20AI1744-3 This version is equipped with a slow 5Hz input filter. It is therefore suitable for slow signal sequences and provides good suppres-
sion of high frequency disturbance signals.
The status LEDs are identical on the X20AI1744 and X20AI1744- 3 modules.
Image LED Color Status Description
r Green Off No power to module
Single flash Reset mode
Double flash Boot mode (during firmware update)
Blinking Preoperational mode
On RUN mode
e Red Off Module supply not connected or everything OK
On Error or reset status
1 Green Off Possible causes:
• Open line
• Sensor is unplugged
• Converter is busy
On Analog/digital converter running, value OK
4.3.2.5 Pinout
r e
X20 AI 1744
Input + Input +
Input - Input -
AI
+U
- +
Figure 49: Connection example - Full-bridge strain gauge with 4-line connection
AI
+U +U Sense
- +
⊥ ⊥ Sense
Figure 50: Connection example - Full-bridge strain gauge with 6-line connection
AI
+U +U
- + + -
⊥ ⊥
Input -
Filters
60 db / dec. -
Strain gauge GND
AD converter
Strain gauge GND
Gain
0 4x 8x 12 x 16 x 20 x 24 x
1xf
DATA Frequency
The AD converter on the AI1744 provides a 24 bit measurement value. However, the actual attainable noise-free
resolution is always less than 24 bit. This "effective resolution" depends on the data rate and measurement range.
Example:
Because of the conversion methods, a data rate of 2.5 Hz and a specified measurement area of 2 mV/V result in
an effective resolution of 18.7 bits:
24-bit
23 21 20 16 15 12 11 8 7 4 3 0
18.7-bit
In a weighing application, the corresponding weight located on the connected load cell should be determined from
the value derived from the X20AI1744.
The characteristics of the strain gauge load cell are as follows:
• Rated load: 1000 kg
• Bridge factor: 4 mV/V
The value for the positive full-scale deflection at a specified rated load of 1000kg is derived from the bridge factor
of the strain gauge load cell (multiplication with the bridge supply voltage from the AI1744 module):
4 mV/V × 5.5 V = 22 mV
With a simple Rule of Three calculation, the corresponding value can be calculated (as seen in the table) from
weight to the converter value and vice versa. This simplified theoretical approach is only valid for an ideal mea-
surement system. Calibration of the entire measurement system is recommended because not only the X20AI1744
module, but particularly the strain gauge bridges feature tolerances (offset, gain). When taring, the gradient offset
is recalculated and the gain of the linear equation is determined when standardized. In addition to the calculation
displayed in the table, these calculations must also be carried out in the application.
24 bit value from the X20AI1744 Quantization Corresponding weight
0x007F FFFF 8,388,607 22.0 mV 1000 kg
0x0000 0001 1 2.62 nV 0.119 g
0x0000 20C3 8,387 22.0 μV 1 kg
0x0001 0000 65,536 171.9 μV 7.81 kg
The values for each LSB can be found in the technical data of the X20AI1744, under "Quantization" (1 LSB in
reference to 16 bit and 1 LSB in reference to 24 bit).
1) X20AI744: from firmware version 8 / upgrade 1.3.0.0; X20AI744-3: from firmware version 8 / upgrade 1.2.0.0
In this function model, the AD converter is operated in synchronization with X2X Link using a fixed ADC cycle time
(configurable as 50 or 100 µs).
The module returns between 3 and 10 measured values per X2X cycle depending on the configuration. With an
X2X cycle time of 400 µs and ADC cycle time of 50 µs, exactly 8 measurements are performed and the module
can return 8 values (strain gauge value 01 to strain gauge value 08).
If a longer cycle time is used, the values returned correspond to the last measurements. If using an X2X cycle time
that is not a whole number multiple of the ADC cycle time, then the conversion cannot be synchronized with X2X
Link. In this case, the module outputs the invalid value 0x8000.
Example 1
With an X2X cycle time of 800 µs, 16 measurements are performed per X2X cycle. The first 6 measured values
are discarded; the last 10 measured values are provided by the module.
With a shorter X2X cycle time, the number of measured values should not exceed the number of measurements
that can actually be made. All other measured values are invalid (0x8000). To minimize the load on X2X Link, it is
possible to disable unneeded registers (see "Number of measurement values").
Example 2
If using an X2X cycle time of 300 μs, it is possible to perform 6 measurements per X2X cycle if the ADC cycle
time equals 50 µs. For this reason, only the first 6 registers are valid. The registers for the 7th through 10th mea-
sured value (AnalogInput07 to AnalogInput08) should be disabled by setting "Number of measured values" to "6
measured values" in the I/O configuration.
Register Name Data type Read Write
Cyclic Acyclic Cyclic Acyclic
2 StatusInput01 USINT ●
1534 + N * 4 AnalogInput0N (N = 1 to 10) INT ●
1600 ConfigOutput01 (X20AI1744) USINT ●
ConfigGain01_MultiSample (X20AI1744-3)
1603 ConfigCycletime01_MultiSample USINT ●
In the bus controller function model, the module behaves as it does in the standard function model, with the ex-
ception that it is not synchronized to the X2X Link even if Synchronous mode is activated in the ADC configuration
register. Instead, the module behaves as if the set ADC cycle time is not a factor or multiple of the X2X cycle time
and attempts to maintain the set ADC cycle time as precisely as possible.
Register Name Data type Read Write
Cyclic Acyclic Cyclic Acyclic
2 StatusInput01 USINT ●
4 AnalogInput01 DINT ●
16 ConfigOutput01 USINT ●
18 ConfigCycletime01 UINT ●
32 AdcClkFreqShift011) USINT ●
1) X20AI744: from firmware version 8 / upgrade 1.3.0.0; X20AI744-3: from firmware version 8 / upgrade 1.2.0.0
Name:
StatusInput01
The current state of the module is indicated in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 AD converter values 0 ADC value is valid
1 ADC value is invalid
1 Line monitoring 0 OK
1 Open line
2 Only valid in synchronous mode 0 ADC runs synchronous to the X2X Link
1 ADC does not run synchronous to the X2X Link
3-7 Reserved -
Name:
AnalogInput01
This register contains the ADC's raw value for the full-bridge strain gauge with 24-bit resolution.
Data type Value Information
DINT 0x007FFFFF to 0xFF800001 Valid value range
0x007FFFFF Overrun
0xFF800001 Underflow
0xFF800000 Invalid value
Effective resolution
In principle, the effective resolution of the AD converter is dependent on the data rate and the measurement range
(see "Effective resolution of the AD converter").
The following table shows how the effective resolution (in bits), or the effective value range of the strain gauge
value depend on the module configuration (data rate, measurement area).
Measurement range
Data rate ±16mV/V ±8mV/V ±4mV/V ±2mV/V
fDATA [Hz] Bits Scope Bits Scope Bits Scope Bits Scope
2.5 21.3 ±1,290,000 20.8 ±912,000 19.7 ±425,000 18.7 ±212,000
5 20.7 ±851,000 20.3 ±645,000 19.3 ±322,000 18.3 ±161,000
10 20.4 ±691,000 19.9 ±490,000 18.9 ±244,000 17.9 ±122,000
15 20.1 ±562,000 19.3 ±320,000 18.7 ±212,000 17.7 ±106,000
25 19.7 ±425,000 19.2 ±301,000 18.5 ±185,000 17.5 ±92,000
30 19.6 ±397,000 19.0 ±262,000 18.1 ±140,000 17.1 ±72,000
50 19.4 ±346,000 18.8 ±230,000 17.9 ±122,000 16.9 ±61,000
60 19.3 ±320,000 18.8 ±230,000 17.8 ±114,000 16.8 ±57,000
100 19.1 ±280,000 18.5 ±185,000 17.4 ±86,000 16.4 ±43,000
500 18.0 ±130,000 17.3 ±80,000 16.3 ±40,000 15.3 ±20,000
1000 17.2 ±75,000 16.5 ±46,000 15.6 ±25,000 14.6 ±12.00
2000 16.6 ±49,600 16.1 ±35,000 15.3 ±20,000 14.3 ±10,000
3750 16.2 ±37,600 15.7 ±26,600 14.7 ±13,000 13.7 ±6,600
7500 15.8 ±28,500 15.3 ±20,200 14.4 ±10,800 13.4 ±5,400
Table 22: Effective resolution of the strain gauge value in bits for the measurement range 2 to 16 mV/V
Table 23: Effective resolution of the strain gauge value in bits for the measurement range 32 to 256 mV/V
Name:
ConfigOutput01
The sampling rate and measurement range for the AD converter can be configured in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Data rate fDATA (samples per second): 0000 2.5
0001 5
0010 10
0011 15
0100 25
0101 30
0110 50
0111 60
1000 100
1001 500
1010 1000
1011 2000
1100 3750
1101 7500
1110 Synchronous mode1)
1111 Reserved
4-5 Standard measurement range (bit 6 = 0) 00 16 mV/V
01 8 mV/V
10 4 mV/V
11 2 mV/V
Extended measurement range (bit 6 = 1)2) 00 256 mV/V
01 128 mV/V
10 64 mV/V
11 32 mV/V
6 0 Standard measurement range (2 to 16 mV/V)
1 Extended measurement range (32 to 256 mV/V)2)
7 Reserved 0 (must be 0)
1) ADC is operated synchronously with the X2X Link, if possible; beginning with firmware 2
2) Starting with Firmware Version 4
Synchronous mode
Beginning with firmware version 2, the analog/digital converter (ADC) on the X20AI1744 module can be operated
and read synchronously with the X2X Link. Synchronous mode is activated by selecting the respective operating
mode in the ADC configuration register. A time between 200 and 2,000 µs must also be set in the ADC cycle time
register. If this time is a whole number factor or multiple of the configured cycle time of the X2X Link, then the ADC
is synchronously read with the X2X Link.
Information:
The ADC cycle time must be ≥1/4 of the X2X cycle time.
The bit 2 in Module Status is set (i.e. ADC does not run synchronously), ...
• ... if the configured ADC cycle time cannot be synchronized with the X2X Link.
• ... if the module is still in the settling phase.
Jitter, dead time and settling time:
Jitter
ADC cycle times <1500 μs Max. ±1 μs
ADC cycle times >1500 μs Max. ±4 μs
Dead time on the X2X Link X2X cycle time
50 μs +
128
Settling time
Firmware Version ≤ Max. 150 x ADC cycle time
Firmware Version ≥5 150 x X2X cycle time
The settling time corresponds to the time needed until the AD converter can be operated after activating the syn-
chronous mode or following conversion of the ADC cycle time.
Name:
ConfigCycletime01
This register is only used in "Synchronous mode". If synchronous mode is enabled in the ADC configuration, then
the module attempts to operate the ADC synchronously to the X2X Link (based on the ADC cycle time specified
in this register). It is necessary for the X2X Link cycle time and the ADC cycle time to have a certain relationship.
The following conditions must be adhered to:
1 ADC cycle time ≥ 1/4 X2X cycle time
2 ADC cycle time corresponds to a whole number factor or multiple of the X2X cycle time
3 ADC cycle time must be in the range from 50 to 2000 µs
Data type Value
UINT 50 to 2000
Name:
AdcClkFreqShift01
In rare cases, X20AI1744 connected to neighboring slots can influence one another. This can result in tempo-
rary, minimal deviations in measurement values. This can only occur if the SigmaDelta ADCs on the neighboring
X20AI1744 modules are operated at exactly the same clock frequency.
In most cases, these clock frequencies vary slightly due to part variances. When they are the same however, this
register on the X20AI1744 provides a safe way for an application to prevent this type of mutual influence.
Data type Value
SINT -128 to 127
This register can be used to vary the clock frequency in increments of 200 ppm. Setting values from -50 to 50 cover
a range of -10000 ppm to 10000 ppm. This corresponds with -1% to 1%.
Values beyond this range will cause activation of a default mode. The frequency shift is derived from the from the
last 2 digits of the serial number by the X20AI1744 firmware. This saves time that would otherwise be needed for
programming, provided that the last two digits of the serial numbers on the neighboring modules are not the same
Register value Frequency shift in ppm Example of a sampling rate1)
127 ((SerialNo. modulo 100) - 50) * (-200) ppm Based on the serial number
... ... ...
51 ((SerialNo. modulo 100) - 50) * (-200) ppm Based on the serial number
50 10000 505
49 9800 504.9
... ... ...
2 400 500.2
1 200 500.1
0 0 500
-1 -200 499.9
-2 -400 499.8
... ... ...
-50 -10000 495
-51 ((SerialNo. modulo 100) - 50) * (-200) ppm Based on the serial number
... ... ...
-128 ((SerialNo. modulo 100) - 50) * (-200) ppm Based on the serial number
IMPORTANT:
As shown in the table above, shifting the ADC clock frequency will equally shift the ADC sampling rate. Shifting the
ADC clock frequency too much can cause problems with disturbance suppression particularly when a very specific
sampling rate has been defined to suppress existing disturbances (e.g: 50 Hz to suppress the 50 Hz hum). Also
see "Filter characteristics of the Sigma-Delta ADC".
It's situations like this where the option to manually shift the frequency in the I/O configuration or ASIOACC library
should be utilized rather than relying on the default frequency shift that is based on the serial number.
A frequency shift like the one shown below would be sufficient to prevent modules from influencing one another
and would not cause any noticeable difference to the filter characteristics.
Slot 1 2 3 4 5 6 ...
ADC clock frequency shift 0 2 -1 1 -2 0 ...
Information:
• This register has no effect in synchronous mode because the firmware regulates the ADC clock
frequency in such a way that the ADC conversion cycle is synchronous with the X2X cycle.
• When writing to this register using the ASIOACC library, only the lowest value byte of the written
value is accepted. For example, the value 256 (=0x100) is identical to the value 0 (=0x00).
Name:
StatusInput01
The current state of the module is indicated in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 AD converter values 0 ADC value is valid
1 ADC value is invalid
1 Line monitoring 0 OK
1 Open line
An open line was found during at least one measurement in this
X2X cycle. This bit is reset if all measurements are OK after
correcting this error, i.e. it does not have to be acknowledged.
2 Synchronous mode 0 ADC runs synchronous to the X2X Link
1 ADC does not run synchronous to the X2X Link
3-7 Reserved -
Name:
AnalogInput01 to AnalogInput10
This register contains the raw value determined by the ADC for the full-bridge strain gauge with 16-bit resolution.
The module returns between 3 and 10 measured values per X2X cycle depending on the configuration.
Effective resolution
In principle, the effective resolution of the AD converter is dependent on the data rate and the measurement range
(see "Effective resolution of the AD converter").
The following table shows how the effective resolution (in bits), or the effective value range of the strain gauge
value depend on the module configuration (data rate, measurement area).
Measurement range
±16mV/V ±8mV/V ±4mV/V ±2mV/V
Bits Scope Bits Scope Bits Scope Bits Scope
15.4 22,000 14.6 12,000 13.8 7,000 12.8 4,000
Table 26: Effective resolution of the strain gauge value in bits for the measurement range 2 to 16 mV/V
Measurement range
±256mV/V ±128mV/V ±64mV/V ±32mV/V
Bits Scope Bits Scope Bits Scope Bits Scope
17.1 70,000 16.7 53,000 16.4 43,000 15.9 31,000
Table 27: Effective resolution of the strain gauge value in bits for the measurement range 32 to 256 mV/V
Name:
ConfigOutput01 (X20AI1744)
ConfigGain01_MultiSample (X20AI1744-3)
The measurement range for the AD converter can be configured in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Standard measurement range (bit 2 = 0) 00 16 mV/V
01 8 mV/V
10 4 mV/V
11 2 mV/V
Extended measurement range (bit 2 = 1)1) 00 256 mV/V
01 128 mV/V
10 64 mV/V
11 32 mV/V
2 0 Standard measurement range (2 to 16 mV/V)
1 Extended measurement range (32 to 256 mV/V)1)
3-7 Reserved 0 (must be 0)
1) Starting with Firmware Version 4. In the standard measurement range (2 to 16 mV/V), open-circuit detection works reliably at all adjustable data rates. In
the extended measurement range (32 to 256 mV/V), open-circuit detection does not work reliably (because of the variable input impedance of the amplifier
in relation to the set data rate).
Name:
ConfigCycletime1_MultiSample
This register can be used to configured the ADC cycle time.
In order for multisampling to work, the X2X cycle time must be divisible by the ADC cycle time (i.e. results in a
whole number).
Data type Value Information
USINT 0 50 μs (default)
1 100 μs
2 - 255 Reserved
If the X2X cycle time is too short, then bot all 10 measurements can be performed. To reduce the load on X2X Link,
it makes sense to only transfer as many values as measurements that can be made. This is why it is possible to
configure the number of measured values to be transferred (see "Function model 1 - Multiple sampling").
Example: ADC cycle time 50 μs
X2X cycle time Number of measurement values to be transferred
250 μs 5
300 μs 6
350 μs 7
400 μs 8
450 μs 9
≥500 μs 10
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
250 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
There is no limitation and no simple dependency on the bus cycle time. In the "Standard" function model, the I/O
update time is defined by the register "ADC configuration" and "ADC cycle time".
In the "Multiple Sampling" function model, the update time is 50 µs.
4.3.3 X20AI2222
The module is equipped with 2 inputs with 13-bit (including sign) digital converter resolution. It can be used to
capture voltage signals in the range from ±10 V.
This module is designed for X20 6-pin terminal blocks. If needed (e.g. for logistical reasons), the 12-pin terminal
block can also be used.
• 2 analog inputs ±10 V
• 13-bit digital converter resolution
Product ID X20AI2222
Short description
I/O module 2 analog inputs ±10 V
General information
B&R ID code 0xCAB0
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 0.8 W 1)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
GOST-R Yes
Analog inputs
Input ±10 V
Input type Differential input
Digital converter resolution ±12-bit
Conversion time 300 µs for all inputs
Output format
Data type INT
Voltage 0x8001 - 0x7FFF / 1 LSB = 0x0008 = 2.441 mV
Input impedance in signal range 20 MΩ
Input protection Protection against wiring with supply voltage
Permitted input signal Max. ±30 V
4.3.3.5 Pinout
r e
X20 AI 2222
1 2
AI + 1 U AI + 2 U
AI - 1 U AI - 2 U
AI
+ +
AI + x U
LED (green)
1) The offset specifies the position of the register within the CAN object.
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Name:
AnalogInput01 to AnalogInput02
The analog input values are mapped to this register.
Data type Value Input signal:
INT -32,768 to 32,767 Voltage signal -10 to 10 VDC
This module is equipped with a configurable input filter. The minimum cycle time must be >500 μs. Filtering is
disabled for shorter cycle times.
If the input filter is active, then the scan rate for the channels is measured in ms. The time offset between the
channels is 200 μs. The conversion takes place asynchronously to the network cycle.
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
Adjustable filter levels:
Value Filter level
0 Filter switched off
1 Filter level 2
2 Filter level 4
3 Filter level 8
4 Filter level 16
5 Filter level 32
6 Filter level 64
7 Filter level 128
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
Example 2
A disturbance interferes with the input value. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 Reserved 0
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of -32768 corresponds to the minimum default value of -10 VDC.
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value at +10 VDC.
Keep in mind that this setting applies to all channels!
Name:
StatusInput01
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Channel 1 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
2-3 Channel 2 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
4-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Inputs without filtering 100 µs
Inputs with filtering 500 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Inputs without filtering 300 µs for all inputs
Inputs with filtering 1 ms
4.3.4 X20AI2237
The X20AI2237 module is equipped with two voltage inputs with 16-bit digital converter resolution.
Each voltage input has its own sensor supply. The two channels with their respective sensor supplies are electrically
isolated from each other.
• 2 analog voltage inputs
• Electrically isolated analog channels
• Electrically isolated sensor supplies
• 16-bit digital converter resolution
• Very high sampling rate
Product ID X20AI2237
Short description
I/O module 2 analog inputs ±10 V
General information
B&R ID code 0xC9C4
Status indicators I/O function per channel, operating state, module status, sensor supply per channel
Diagnostics
Module run/error Yes, using status LED and software status
Inputs Yes, using status LED and software status
Sensor supply Yes, using status LED and software status
Power consumption
Bus 0.05 W
I/O internal 2.65 W
I/O external 1.5 W 1)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
c-UL-us In preparation
GOST-R Yes
Analog inputs
Input ±10 V
Input type Differential input
Digital converter resolution ±15-bit
Data output rate 10,000 samples per second
Output format
Data type INT
Voltage INT 0x8001 - 0x7FFF / 1 LSB = 0x0001 = 305.176 µV
Input impedance in signal range 20 MΩ
4.3.4.5 Pinout
Shielded twisted pair cables should be used to minimize coupling disturbances. Use either one cable for each
channel or a multiple twisted pair cable for both channels.
r e
X20 AI 2237
V V
1 2
AI
2-wire
Transducer
(passive)
Voltage source
+24 VDC +24 VDC
GND GND
With external
AI power supply
4-wire
transducer
(active)
4-wire
transducer
(active)
With internal
power supply 1)
1)
The internal power supply can handle a load of max. 30 mA.
Electrical
Isolation
Sensor supply x + I/O
DC/DC
Supply
DC/DC 28 V
Input 18 - 30 V
Converter
protection GND x GND I/O
25 V DC/DC
5V
Sensor supply x - DC/DC
3.3 V
GND x
Channel x +
Channel x -
In the event of a short circuit, the output current for the sensor supply is limited according to the following diagram.
25
20
Voltage [V]
15
10
0
0 10 20 30 40 50
Current [mA]
Figure 60: Typical behavior of the sensor supply output current in the event of a short circuit
The X20AI2237 provides two electrically isolated channels. Each channel can read an electrical voltage signal in
the ±10 V range, and the supply the signal encoder with 24 VDC.
Each channel is configured and enabled separately First, the user must set the scaling of the input value and select
a replacement value strategy. Depending on the requirements of the application, the user can also set user-defined
limit values to limit the slew rate of the input value.
Scaling
The module's ADC works at a resolution of 16 bits (±15 bits). This allows the input value of ±10 V to be mapped
using ±32767 steps. To simplify implementation, the user can configure scaling to ±10000 steps. The conversion
value corresponds to the voltage in mV, and with a resolution of more than 14 bits (±13 bits) is still precise enough
for the many different application that use this technology.
Replacement value strategy
The detected voltage is evaluated in order to ensure the quality of the read value. For example, if a logically
impermissible voltage value or an open line is detected, the limit monitor triggers an appropriate response.
The response is determined by the replacement value strategy selected by the user. With the option "Replace with
static value", the user defines two values that replace the converted value when the upper and lower limits are
exceeded. The alternative "Retain last valid value" keeps the last validated value. However, the evaluation for this
option takes more time. Depending on the defined preparation interval, the currently read value may be delayed.
User limit check
In addition to the qualitative evaluation of the input, the module also provides the option of adapting the range
of permitted values to the requirements of the application. The "UpperLimit" and "LowerLimit" registers can be
used to place additional restrictions on the permitted upper and lower limit. When this feature is used, the selected
replacement value strategy is implemented according to the new limits.
Slew rate of the input value
Analog input signals can experience brief disturbances caused by external factors (EMC). The ADC's high sampling
rate allows you to filter out these types of signal peaks without hindering the application processes.
Two configuration points are available for interpolating the input signal:
• "Level of input filter" and
• "Input limitation"
The "Level of input filter" limits the permissible changes to the input value. The calculation is recursive, which
means the current value depends on the previously filtered input value. The curve of the filtered input value is
similar to a first order low pass filter.
Example 1: The diagram shows how the evaluated input value behaves during normal operation.
Configured filter level: 2 or 4
Jump in incoming raw value: From 8000 to 16000
16000
8000
0
0 1 2 3 4 5 6 7 8 t
Figure 61: Step response of input value with respect to configured filter level
Example 2: The diagram shows how the evaluated input value behaves when a disturbance occurs.
Configured filter level: 2 or 4
Spike in incoming raw value: From 8000 to 16000
16000
Disturbance (spike)
8000
Raw value
Evaluated value: Filter level 2
Evaluated value: Filter level 4
0
0 1 2 3 4 5 6 7 8 t
Figure 62: Pulse response of input value with respect to configured filter level
The higher the filter level is set, the lower the absolute amplitude of the evaluated input value. Due to the recursive
calculation, however, the spike has a considerable after-effect. It is therefore recommended to define an additional
input limit when using high filter levels. This provides an absolute limit to variation in the evaluated input value
in advance.
Example 1: The diagram shows how the evaluated input value behaves during normal operation.
Input limitation: 2047
Configured filter level: 2
Jump in incoming raw value: From 8000 to 17000
17000
8000
0
0 1 2 3 4 5 6 7 8 t
Figure 63: Step response of input value with configured filter level and input ramp limit
Example 2: The diagram shows how the evaluated input value behaves when a disturbance occurs.
Input limitation: 2047
Configured filter level: 2 or 4
Spike in incoming raw value: From 8000 to 16000
16000
Disturbance (spike)
8000
Raw value
Evaluated value
0
0 1 2 3 4 5 6 7 8 t
Figure 64: Pulse response of input value with configured filter level and input ramp limit
4.3.4.9.4.1 AnalogFilter
Name:
AnalogFilter01
AnalogFilter02
If required by the application, the "AnalogFilter" register can be used to limit the slew rate of the input value.
Data type Values
UINT See bit structure
Bit structure:
Bit Name Value Note
0-2 Level of input filter 000 Off (input limitation not processed)
001 2
010 4
011 8
100 16
101 32
110 64
111 128
3 Reserved 0
4-6 Input limitation 000 No additional limitation
001 16383
010 8191
011 4095
100 2047
101 1023
110 511
111 255
7 Reserved 0
4.3.4.9.4.2 AnalogMode
Name:
AnalogMode01
AnalogMode02
These registers are used to predefine the operating parameters that the module will be using for the respective
channel. Each channel must be enabled individually and can be configured and operated independently.
It is extremely important to not that different limit values need to be configured for any display normalizing that
needs to take place.
Data type Values
UINT See bit structure
Bit structure:
Bit Name Value Note
0 Channel (on/off) 0 Disabled
1 Enabled
1 Limit exceeded 0 Disabled
1 Enabled
2 Lower limit violation 0 Disabled
1 Enabled
3 Reserved 0
4 Replacement value strategy 0 Replace with static value
1 Retain last valid value
5 Measurement value scaling 0 ±32767 (resolution: 16-bit)
1 ±10000 (resolution: >14-bit)
6-15 Reserved 0
Name:
UpperLimit01
UpperLimit02
LowerLimit01
LowerLimit02
If the value range needs to be restricted further, the "UpperLimit" and "LowerLimit registers can be used to enter
new user-specific limit values.
Data type Values
INT -32767…32767
-10000…10000
Information:
The defined limit values must take the scaling into consideration.
4.3.4.9.4.4 Hysteresis
Name:
Hysteres01
Hysteres02
If the user-specific limit values are being used, then a hysteresis range should also be defined. The "Hysteresis"
registers configure how far a limit value can be exceeded before a response is triggered.
The error status is cleared when the scaled input value once again passes the limit by at least the hysteresis value
in the permitted direction.
Data type Values
INT -32767…32767
-10000…10000
Information:
The hysteresis value must take the scaling into consideration.
Name:
ReplacementUpper01
ReplacementUpper02
ReplacementLower01
ReplacementLower02
The "Replace" register is used to define the static values to be displayed instead of the current measurement value
when the limit is violated.
Data type Values
INT -32767…32767
4.3.4.9.4.6 PreparationInterval
Name:
PreparationInterval01
PreparationInterval02
If the last valid measurement value should be kept when violating the limit value, then PreparationInterval must be
defined. The measurement values continue to be acquired and converted according to the configured I/O update
time. They are then checked and discarded if they do not meet the specifications. When an error does not occur,
therefore, the measurement value acquired two preparation intervals ago is constantly output.
Data type Values [0.1 ms]
UINT 0…65535
"Application"
How it works: for the value being measured (analog)
Measured values are converted at the configured conversion rate and saved to measurement value memory. Condition:
The current contents of the measurement value memory are checked within the configured interval. If a permis- ↓
- Conversion interval (ADC) elapsed
sible value is present, then the contents of the buffer memory are passed to output memory and the contents of "Measurement value memory"
the measurement value memory are passed to the buffer. Measurement value (digital)
If the check turns up an impermissible value, then the contents of the measurement value memory are discard-
Condition:
ed. The copy direction between the output and buffer memory reverses and the last valid value continues to be
↓ - PreparationInterval elapsed
output.
- Measurement value permissible
"Buffer"
Information: Last valid value
Condition:
If configured to keep the last valid value, the delay time from measuring to outputting the value ↓ - PreparationInterval elapsed
will be at least twice the preparation interval. In the worst case scenario, this can also take twice - Measurement value permissible
the interval time plus the configured ADC conversion rate. "Output memory"
Next-to-last valid/
displayed value
4.3.4.9.4.7 ErrorDelay
Name:
ErrorDelay01
ErrorDelay02
This register specifies the number of consecutive conversion procedures where an error is pending until the cor-
responding individual error status bit is set. The delay applies to underflow, overflow and open circuit errors. This
delay can be used to hide temporary measurement value deviations, for example.
Data type Values
UINT 0…65535
4.3.4.9.4.8 SumErrorDelay
Name:
SumErrorDelay01
SumErrorDelay02
A "SumErrorDelay" register can be used to set the time that an error must remain pending before the composite
error bit is set.
Data type Values
UINT 0…65535
The measured voltage data can be obtained via two different registers: The unevaluated measurement value
("measurand") contains the scaled converter value. The evaluated measurement value ("Evaluated“) also takes
the limit values and the configured replacement value strategy into consideration.
Name:
AnalogInput01
AnalogInput02
The "Measurand" registers represent the actual input values after standardization. The settings for limit value
monitoring and replacement value strategy only affect the "Evaluated" registers.
Data type Values
INT -32767…32767
-10000…10000
Name:
Sampletime01
Sampletime02
The registers return the timestamp for when the module reads the current channel mapping. The values are pro-
vided as signed 2-byte or 4-byte values.
Data type Values [µs]
INT -32768...32767: Nettime timestamp of the current input value
DINT -2,147,483,648...2,147,483,647: Nettime timestamp of the current input value
4.3.4.9.5.3 AnalogStatus
Name:
AnalogStatus01
AnalogStatus02
The current error status of the module channels is displayed in this register, regardless of the configured replace-
ment value strategy. Some error information may be delayed according to the previously configured condition.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Value Note
0 UnderflowAnalogInput 0 Value equals lower limit
1 Lower limit value exceeded
1 OverflowAnalogInput 0 Value equals upper limit
1 Upper limit value exceeded
2 OpenLineAnalogInput 0 No open line detected
1 Open line detected
3 Reserved 0
4 SumErrorAnalogInput 0 No error detected
1 Composite error detected
5 Reserved 0
6 SensorErrorAnalogInput 0 Sensor voltage OK
1 Sensor load too high
7 IoSuppErrorAnalogInput 0 Module voltage OK
1 Energy supply not permitted
UnderflowAnalogInput:
The signal underflow error status is indicated here according to the configuration. This error information is activated
as a multiple of the conversion cycles only after the configurable delay time has passed ("ErrorDelay" registers).
OverflowAnalogInput:
The signal overflow error status is indicated here according to the configuration. This error information is activated
as a multiple of the conversion cycles only after the configurable delay time has passed ("ErrorDelay" registers).
SumErrorAnalogInput:
This error information derives from the status of individual errors and is only activated after the configurable delay
time has passed ([ms], "SumErrorDelay" registers). Linking this error information to an application makes it possible
to hide temporary temperature value overflows and underflows, for example.
SensorErrorAnalogInput:
In addition to the analog input, the module also provides the option of supplying the connected encoder with 24 VDC.
If the input impedance for the sensor is too high, however, the integrated supply voltage will fail.
IoSuppErrorAnalogInput:
This error is activated immediately as soon as the module detects that the necessary supply voltage is no longer
being provided (<20 VDC).
A function model specifies the registers on the module (storage model) that are available for the application. Only
these registers are processed on the module during each cycle and transferred cyclically via the bus. In this way,
it is possible to minimize the cycle time by selecting the correct function model.
Function model Number Automation Studio CANopen DeviceNet Modbus/TCP CAN I/O
Default 0 ●
Bus controllers 254 ● ● ● ●
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
1 ms
4.3.5 X20AI2322
The module is equipped with 2 inputs with 12-bit digital converter resolution. It is possible to select between the
two current ranges 0 to 20 mA and 4 to 20 mA.
This module is designed for X20 6-pin terminal blocks. If needed (e.g. for logistical reasons), the 12-pin terminal
block can also be used.
• 2 analog inputs, 0 to 20 mA or 4 to 20 mA
• 12-bit digital converter resolution
Product ID X20AI2322
Short description
I/O module 2 analog inputs 0 to 20 mA / 4 to 20 mA
General information
B&R ID code 0xCAB2
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 0.8 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
GOST-R Yes
Analog inputs
Input 0 to 20 mA/4 to 20 mA
Input type Differential input
Digital converter resolution 12-bit
Conversion time 300 µs for all inputs
Output format
Data type INT
Current 0x0000 - 0x7FFF / 1 LSB = 0x0008 = 4.883 µA
Load <400 Ω
Input protection Protection against wiring with supply voltage
Permitted input signal Max. ±50 mA
4.3.5.5 Pinout
r e
X20 AI 2322
1 2
AI +1 I AI +2 I
AI -1 I AI -2 I
AI
+ +
PTC
AI + x I
LED (green)
1) The offset specifies the position of the register within the CAN object.
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Name:
AnalogInput01 to AnalogInput02
The analog input values are mapped to this register.
Data type Value Input signal:
INT 0 to 32767 Current signal 0 to 20 mA or 4 to 20 mA
This module is equipped with a configurable input filter. The minimum cycle time must be >500 μs. Filtering is
disabled for shorter cycle times.
If the input filter is active, then the scan rate for the channels is measured in ms. The time offset between the
channels is 200 μs. The conversion takes place asynchronously to the network cycle.
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
Adjustable filter levels:
Value Filter level
0 Filter switched off
1 Filter level 2
2 Filter level 4
3 Filter level 8
4 Filter level 16
5 Filter level 32
6 Filter level 64
7 Filter level 128
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
Example 2
A disturbance interferes with the input value. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 Reserved 0
Name:
ConfigOutput02
This register can be used to set the range of the current signal. This is determined by how they are configured.
The following input signals can be set:
• 0 to 20 mA current signal
• 4 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Reserved 1
2-3 Reserved 0
4 Channel 1: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
5 Channel 2: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
6-7 Reserved 0
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
• When configured as 0 to 20 mA, this value should be set to 0.
• When configured as 4 to 20 mA, this value can be set to -8192 (corresponds to 0 mA) in order
to display values <4 mA.
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value at 20 mA.
Keep in mind that this setting applies to all channels!
Name:
StatusInput01
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Channel 1 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
2-3 Channel 2 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
4-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Inputs without filtering 100 µs
Inputs with filtering 500 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Inputs without filtering 300 µs for all inputs
Inputs with filtering 1 ms
4.3.6 X20AI2437
The X20AI2437 module is equipped with two inputs that have 16-bit digital converter resolution.
Each current measurement input has its own sensor supply. The two channels with their respective sensor supplies
are electrically isolated from each other. The user can select between the two measurement ranges 4 to 20 mA
and 0 to 25 mA.
• 2 analog current measurement inputs
• Electrically isolated analog channels
• Electrically isolated sensor supplies
• 16-bit digital converter resolution
Product ID X20AI2437
Short description
I/O module 2 analog inputs, 4 to 20 mA or 0 to 25 mA
General information
B&R ID code 0xB784
Status indicators I/O function per channel, operating state, module status, sensor supply per channel
Diagnostics
Module run/error Yes, using status LED and software status
Inputs Yes, using status LED and software status
Sensor supply Yes, using status LED and software status
Power consumption
Bus 0.05 W
I/O internal 1.15 W 1)
I/O external 1.5 W 2)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
GOST-R Yes
UL/CSA Yes
Analog inputs
Input 4 to 20 mA or 0 to 25 mA (can be configured via software)
Input type Differential input
Digital converter resolution 15-bit
Data output rate 4.7 to 960 scans per second, can be set using software
Output format INT
Output format
4 to 20 mA INT $0000 - $7FFF / 1 LSB = $0001 = 488.281 nA
0 to 25 mA INT $0000 - $7FFF / 1 LSB = $0001 = 762.939 nA
0 to 25000 µA INT $0000 - $61A8 / 1 LSB = $0001 = 1000 nA
Load <300 Ω
Input protection Up to 30 VDC, reverse polarity protection (max. 0.1 A)
Open line detection Yes, via software
Permitted input signal 0 to 25 mA
Output of the digital value during overload Configurable
Conversion procedure Sigma Delta
Max. error at 25°C
Gain
0 to 25 mA <0.046% 3)
4 to 20 mA <0.046% 3)
Offset
0 to 25 mA <0.004% 4)
4 to 20 mA <0.013% 4)
Common-mode rejection
DC 80 dB
50 Hz Depends on the sampling rate: e.g. >130 dB for 50 scans per second
Common-mode range 0 to 7 V
Non-linearity <0.003% 4)
Input filter
Hardware 1st-order low pass / cut-off frequency 2.5 kHz
Software Sinc4 filter
Maximum gain drift
0 to 25 mA 0.003 %/°C 3)
4 to 20 mA 0.003 %/°C 3)
Maximum offset drift
0 to 25 mA 0.0002 %/°C 4)
4 to 20 mA 0.0007 %/°C 4)
Test voltage between
Channel and channel 1500 VAC
Channel and bus 1500 VAC
To ground 1500 VAC
Sensor supply
Nominal voltage 25 V ±2 %
Nominal output current Max. 30 mA
Short circuit protection Yes, continuous
Electrical isolation
Sensor supply - Channel No
Sensor supply - Sensor supply Yes
Shielded twisted pair cables are generally used to minimize disturbance. Use either one cable for each channel
or a multiple twisted pair cable for both channels.
r e
X20 AI 2437
V V
1 2
Electrical
Isolation
Sensor supply x + I/O
DC/DC
Supply
DC/DC 28 V
Output 18 - 30 V
Converter
protection GND x GND I/O
25 V DC/DC
3.3 V
Sensor supply x -
GND x
Channel x +
Input
protection Protection
Shunt
A/D
and Processor
Converter
Channel x - Filter
GND x
In the event of a short circuit, the output current for the sensor supply is limited according to the following diagram.
25
20
Voltage [V]
15
10
0
0 10 20 30 40 50
Current [mA]
Figure 71: Typical behavior of the sensor supply output current in the event of a short circuit
The X20AI2437 module has two independent electrically isolated channels. Both channels can be used to read in an
analog signal. Two registers need to be configured for one analog signal. The two channels operate independently,
so two registers must be configured per channel to be used.
The current input signals (0 to 25 mA) can be displayed in different formats.
Specific features:
• Electrical isolation by channel
• Internal supply with short circuit protection <30 mA per channel
• Configurable filter (default 50 Hz)
• Selective line monitoring can be enabled for: open line (<2 mA), underflow (<3.6 mA) or overflow (>21 mA)
of a configurable threshold
• Selectable error strategy: Replacement value for each threshold (default) or last valid value
4.3.6.9.5.1 AnalogInputEvaluated
Names (pChannelName):
AnalogInputEvaluated01
AnalogInputEvaluated02
These registers take the values from the "AnalogInput" registers and use them to generate the evaluated input
values. The configured auxiliary functions are applied to form these values.
Data type Values
INT 0…25000: Normalizing option 0 to 25 mA
0…32767: Normalizing option 0 to 25 mA
0…32767: Normalizing option 4 to 20 mA
UINT 0…65535: Normalizing option 0 to 25 mA
4.3.6.9.5.2 AnalogInput
Names (pChannelName):
AnalogInput01
AnalogInput02
The normalized input values are transferred to these registers. Depending on the scaling selected, the value range
and the data type can be adapted to the requirements of the application. Generated limit values or value changes
from the configured limit value strategy have no effect on these registers.
Data type Values
INT 0…25000: Normalizing option 0 to 25 mA
0…32767: Normalizing option 0 to 25 mA
0…32767: Normalizing option 4 to 20 mA
UINT 0…65535: Normalizing option 0 to 25 mA
4.3.6.9.5.3 AnalogSampletime
Names (pChannelName):
AnalogSampletime01
AnalogSampletime01_16Bit
AnalogSampletime01_32Bit
AnalogSampletime02
AnalogSampletime02_16Bit
AnalogSampletime02_32Bit
The registers return the timestamp for when the module reads the current channel mapping. The values are pro-
vided as signed 2-byte or 4-byte values.
Data type Values [µs]
INT -32768...32767: Nettime timestamp of the current input value
DINT -2,147,483,648...2,147,483,647: Nettime timestamp of the current input value
4.3.6.9.5.4 AnalogStatus
Names (pChannelName):
AnalogStatus01
AnalogStatus02
The current error status of the module channels is displayed in this register, regardless of the configured replace-
ment value strategy. Some error information may be delayed according to the previously configured condition.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Information
0 Underflow 0 No error
1 Underflow on Channel 0x
1 Overflow 0 No error
1 Overflow on Channel 0x
2 Open line 0 No error
1 Open line on Channel 0x
3 Conversion error 0 No error
1 Conversion error on Channel 0x
4 Composite error 0 No error
1 Composite error on Channel 0x
5 Reserved -
6 Sensor error 0 No error
1 Sensor error on Channel 0x
7 I/O supply error 0 No error
1 I/O supply error on Channel 0x
Underflow:
The signal underflow error status is indicated here according to the configuration. This error information is activated
as a multiple of the conversion cycles only after the configurable delay time has passed ("ErrorDelay" registers).
Overflow:
The signal overflow error status is indicated here according to the configuration. This error information is activated
as a multiple of the conversion cycles only after the configurable delay time has passed ("ErrorDelay" registers).
Open line:
According to the configuration, measurement information is checked for values <2 mA ("OpenLoopLimit" register)
to detect a failure signal. Open line detection takes place using a configurable hysteresis value (default: 100 µA,
"Hysteresis" registers). It is possible to disable open line detection ("AnalogMode" registers) to suppress alarms
when hardware is not present. This error information is activated as a multiple of the conversion cycles only after
the configurable delay time has passed ("ErrorDelay" registers).
Conversion error:
This error status is triggered when the hardware exceeds the conversion time.
Composite error:
This error information derives from the status of individual errors and is only activated after the configurable delay
time has passed ([msec], "SumErrorDelay" registers). Linking this error information to an application makes it
possible to hide temporary temperature value overflows and underflows, for example.
Sensor error:
This error is activated immediately after a fault is detected in the internal sensor supply.
I/O supply error:
This error is activated immediately as soon as the module detects that the necessary supply voltage is no longer
being provided (<20 VDC).
How the analog signal is displayed can be adapted to the requirements of the application. Separate configuration
registers per channel are available to aid in this.
Designations (pChannelName):
AnMode_1
AnMode_2
These registers are used to predefine the operating parameters that the module will be using for the respective
channel. Each channel must be enabled individually and can be configured and operated independently.
It is extremely important to not that different limit values need to be configured for any display normalizing that
needs to take place.
Data type Values
UINT See bit structure
Bit structure:
Bit Description Note
0 Channel 0 Channel 0x turned off
1 Channel 0x enabled (bus controller default setting)
1 Open circuit detection 0 Open circuit monitoring turned off
1 Channel 0x monitoring enabled (bus controller default setting)
2 Underflow detection 0 Underflow detection turned off
1 Underflow detection enabled (bus controller default setting)
3 Replacement value strategy 0 Use replacement values when an error occurs (bus controller
default setting)
1 Keep the last valid converted value
4-5 Normalization 00 Displays 0...25 mA as 0...32767
01 Displays 0...25 mA as 0...25000 [µA] (bus controller default set-
ting)
10 Displays 4...20 mA as 0...32767
11 Displays 0...25 mA as 0...65535
6-15 Reserved -
Names (pChannelName):
Samplerate_1
Samplerate_2
A sample rate can be configured for both analog inputs independently of one another. The following formula for
this parameter is put together using the desired sampling frequency:
Sample rate for ADC = (4920000/1024)/sampling frequency
Data type Values
UINT 4 - 1023: Sample rate
960 ... 200 ms ... 5 Hz
480 ... 100 ms ... 10 Hz
320 ... 66.7 ms ... 15 Hz
192 ... 40 ms ... 25 Hz
160 ... 33.3 ms ... 30 Hz
96 ... 20 ms ... 50 Hz (bus controller default setting)
80 ... 16.7 ms ... 60 Hz
48 ... 10 ms ... 100 Hz
9 ... 2 ms ... 500 Hz
4 ... 1 ms ... 1000 Hz
Setting to 1000 Hz will result in jitter when acquiring measurement values. Jitter-free operation is possible up to
960 Hz (sample rate setting = 5).
4.3.6.9.6.3 OpenLoopLimit
Names (pChannelName):
OpenLoopLimit_1
OpenLoopLimit_2
The limit value for the respective analog input must be set when open circuit monitoring is enabled and if required
by the configured normalization. If limit value monitoring is active, the corresponding error status is output after a
configured delay when falling below this value. Using a default value of 2000 µA, the following values and formulas
apply to this parameter:
• Displaying 0..25 mA as 0..25000 : 2000
• Displaying 0..25 mA as 0..32767 : 2621, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : -4096, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 5243, limit value = ([µA]*65535)/25000
Data type Values
INT -32767...32767: Open circuit limit value
UINT 0...65535: Open circuit limit value
4.3.6.9.6.4 PreparationInterval
Names (pChannelName):
PreparationInterval_1
PreparationInterval_2
If the last valid measurement value should be kept when violating the limit value, then PreparationInterval must be
defined. The measurement values continue to be acquired and converted according to the configured I/O update
time. They are then checked and discarded if they do not meet the specifications. When an error does not occur,
therefore, the measurement value acquired two preparation intervals ago is constantly output.
Data type Values [0.1 ms]
UINT 0…65535
"Application"
How it works: for the value being measured (analog)
Measured values are converted at the configured conversion rate and saved to measurement value memory. Condition:
The current contents of the measurement value memory are checked within the configured interval. If a permis- ↓
- Conversion interval (ADC) elapsed
sible value is present, then the contents of the buffer memory are passed to output memory and the contents of "Measurement value memory"
the measurement value memory are passed to the buffer. Measurement value (digital)
If the check turns up an impermissible value, then the contents of the measurement value memory are discard-
Condition:
ed. The copy direction between the output and buffer memory reverses and the last valid value continues to be
↓ - PreparationInterval elapsed
output.
- Measurement value permissible
"Buffer"
Information: Last valid value
Condition:
If configured to keep the last valid value, the delay time from measuring to outputting the value ↓ - PreparationInterval elapsed
will be at least twice the preparation interval. In the worst case scenario, this can also take twice - Measurement value permissible
the interval time plus the configured ADC conversion rate. "Output memory"
Next-to-last valid/
displayed value
Names (pChannelName):
ReplacementUpper_1
ReplacementUpper_2
ReplacementLower_1
ReplacementLower_2
The "Replace" registers are used to predefine the static values that will be displayed instead of the current mea-
surement value when a limit value is violated.
Data type Values
INT -32767...32767
UINT 0...65535
If the replacement strategy "Use replacement values when an error occurs" is activated, the replacement value must
be set for the respective analog input taking the configured normalization into account as well. When an overflow
or underflow error status occurs, the "AnalogInputEvaluated0x" channel is replaced with the corresponding value.
Using a default value of 21000 µA and 3600 µA, the following values and formulas apply to this parameter:
Overflow:
• Displaying 0..25 mA as 0..25000 : 21000
• Displaying 0..25 mA as 0..32767 : 27524, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : 32767, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 55049, limit value = ([µA]*65535)/25000
Underflow:
• Displaying 0..25 mA as 0..25000 : 3600
• Displaying 0..25 mA as 0..32767 : 4718, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : -819, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 9437, limit value = ([µA]*65535)/25000
Names (pChannelName):
UpperLimit_1
UpperLimit_2
LowerLimit_1
LowerLimit_2
If the value range needs to be restricted further, the "UpperLimit" and "LowerLimit registers can be used to enter
new user-specific limit values.
Data type Values
INT -32767…32767
UINT 0...65535
The limit value must be set for the respective analog input depending on the configured normalization. After the
configured delay time has passed, the corresponding error status is given if the respective value is overrun or
underrun. When this error status occurs, the "AnalogInputEvaluated0x" channel is evaluated according to the
replacement value strategy. Using a default value of 21000 µA and 3600 µA, the following values and formulas
apply to this parameter:
UpperLimit
• Displaying 0..25 mA as 0..25000 : 21000
• Displaying 0..25 mA as 0..32767 : 27524, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : 32767, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 55049, limit value = ([µA]*65535)/25000
LowerLimit
• Displaying 0..25 mA as 0..25000 : 3600
• Displaying 0..25 mA as 0..32767 : 4718, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : -819, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 9437, limit value = ([µA]*65535)/25000
4.3.6.9.6.7 Hysteresis
Names (pChannelName):
Hysteres_1
Hysteres_2
If the user-specific limit values are being used, then a hysteresis range should also be defined. The "Hysteresis"
registers configure how far a limit value can be exceeded before a response is triggered.
Data type Values
INT -32767…32767
UINT 0...65535
Te hysteresis value must be set for the respective analog input dpending on the configured normalization. The
error status is cleared if the actual analog value changes by at least this hysteresis value from the limit value in the
allowed direction. Using a default value of 100 µA, the following values and formulas result for this parameter:
• Displaying 0..25 mA as 0..25000 : 100
• Displaying 0..25 mA as 0..32767 : 131, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : 156, limit value = [µA]*1.5625
• Displaying 0..25 mA as 0..65535 : 262, limit value = ([µA]*65535)/25000
4.3.6.9.6.8 ErrorDelay
Names (pChannelName):
ErrorDelay_1
ErrorDelay_2
This register specifies the number of consecutive conversion procedures where an error is pending until the cor-
responding individual error status bit is set. The delay applies to underflow, overflow and open circuit errors. This
delay can be used to hide temporary measurement value deviations, for example.
Data type Values
UINT 0...10: Error formation delay [conversion cycles]
2 conversion cycles [default]
4.3.6.9.6.9 SumErrorDelay
Names (pChannelName):
SumErrorDelay_1
SumErrorDelay_2
This register specifies the time in milliseconds that one of the individual error bits must be pending until the com-
posite error status bit is set.
Data type Values
UINT 0...65535: Composite error bit delay [msec]
4000 msec [default]
A function model specifies the registers on the module (storage model) that are available for the application. Only
these registers are processed on the module during each cycle and transferred cyclically via the bus. In this way,
it is possible to minimize the cycle time by selecting the correct function model.
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
200 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Analog inputs 1 ms
4.3.7 X20AI2438
The X20AI2438 module is equipped with two inputs with 16-bit digital converter resolution. It supports the HART
communication standard for data transfer, parameter configuration and diagnostics.
Each current measurement input has its own sensor supply. The two channels with their respective sensor supplies
are electrically isolated from each other. The user can select between the two measurement ranges 4 to 20 mA
and 0 to 25 mA.
• 2 analog current measurement inputs
• HART protocol integration
• Support for HART variables
• Electrically isolated analog channels
• Electrically isolated sensor supplies
• 16-bit digital converter resolution
Product ID X20AI2438
Short description
I/O module 2 analog inputs, 4 to 20 mA or 0 to 25 mA
General information
B&R ID code 0xB3A9
Status indicators I/O function per channel, operating state, module status, sensor supply per channel, HART
Diagnostics
Module run/error Yes, using status LED and software status
Inputs Yes, using status LED and software status
Sensor supply Yes, using status LED and software status
HART link Yes, using status LED and software status
HART error Yes, using status LED and software status
Power consumption
Bus 0.05 W
Internal I/O 1.15 W 1)
External I/O 1.5 W 2)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Analog inputs
Input 4 to 20 mA or 0 to 25 mA (can be configured via software)
Input type Differential input
Digital converter resolution 15-bit
Data output rate
With HART 4.7 to 10 scans per second, can be set using software
Analog 4.7 to 100 scans per second, can be set using software
Output format INT
Output format
4 to 20 mA INT 0x0000 - 0x7FFF / 1 LSB = 0x0001 = 488.281 nA
0 to 25 mA INT 0x0000 - 0x7FFF / 1 LSB = 0x0001 = 762.939 nA
0 to 25000 µA INT 0x0000 - 0x61A8 / 1 LSB = 0x0001 = 1000 nA
Load <300 Ω
Input protection Up to 30 VDC, reverse polarity protection (max. 0.1 A)
Open line detection Yes, via software
Permitted input signal 0 to 25 mA
Output of the digital value during overload Configurable
Conversion procedure Sigma Delta
Max. error at 25°C
Gain
0 to 25 mA <0.046% 3)
4 to 20 mA <0.046% 3)
Offset
0 to 25 mA <0.004% 4)
4 to 20 mA <0.013% 4)
Common-mode rejection
DC 80 dB
50 Hz Depends on the sampling rate: e.g. >130 dB for 50 scans per second
Common-mode range 0 to 7 V
Non-linearity <0.003% 4)
Input filter
Hardware 1st-order low pass / cut-off frequency 100 Hz
Software Sinc4 filter
Maximum gain drift
0 to 25 mA 0.003 %/°C 3)
4 to 20 mA 0.003 %/°C 3)
Maximum offset drift
0 to 25 mA 0.0002 %/°C 4)
4 to 20 mA 0.0007 %/°C 4)
Test voltage between
Channel and channel 1500 VAC
Channel and bus 1500 VAC
To ground 1500 VAC
Sensor supply
Nominal voltage 25 V ±2 %
Nominal output current Max. 30 mA
Shielded twisted pair cables should be used to minimize coupling disturbances. Use either one cable for each
channel or a multiple twisted pair cable for both channels.
r e
X20 AI 2438
V V
1 2
L L
e e
Electrical
Isolation
Sensor supply x + I/O
DC/DC
Supply
DC/DC 28 V
Output 18 - 30 V
Converter
protection GND x GND I/O
25 V DC/DC
3.3 V
Sensor supply x -
GND x
RTS (Request to Send)
Channel x + HART
Modem
Input Processor
protection Protection
Shunt
A/D
and
Converter
Channel x - Filter
GND x
In the event of a short circuit, the output current for the sensor supply is limited according to the following diagram.
25
20
Voltage [V]
15
10
0
0 10 20 30 40 50
Current [mA]
Figure 72: Typical behavior of the sensor supply output current in the event of a short circuit
1) REAL data types are not supported by the B&R CANIO Manager on SG3 CPUs. Therefore they can be accessed as UDINT data types in the corresponding
hardware description files.
The UDINT variable data content corresponds to REAL format (IEEE), so it is important to note that using a "Casting" command is not permitted!
The X20AI2438 module has two independent electrically isolated channels with integrated HART modems. Both
channels can be used to read in an analog signal and handle HART communication. Two registers need to be
configured for one analog signal. The two channels operate independently, so two registers must be configured
per channel to be used.
The current input signals (0 to 25 mA) can be displayed in various formats and used as conventional analog inputs.
The integrated HART modems retrieve digital information from the memory on the HART slave using the same
physical lines that modulate the HART signals.
When using the 0 to 25 mA current input variant, the module is conceived as a HART master for 2 channels (loops),
with FSK modulation of the HART protocol and sensor supply for max. 4 slaves per channel.
Each channel can use one of the following connection variants:
• Connection of one HART node (point-to-point) with evaluation of the analog signal and output of 4 HART
process variables OR
• Connection of up to 15 HART nodes in multidrop mode with output of the primary HART variable from
activated nodes
Specific features:
• Electrical isolation by channel
• Up to 4 or 15 HART input variables per channel
• Configurable sampling rate (input filter) to transfer HART and analog signal without interference (default:
50 Hz or 20 ms)
• Internal supply with short circuit protection <30 mA per channel
• Selective line monitoring can be enabled for: open line (<2 mA), underflow (<3.6 mA) or overflow (>21 mA)
of a configurable threshold
• Selectable error strategy (static replacement value or retention of the last permitted value)
• Cyclic "HART status" polling (HART command 0), the status information received is made available for
channel diagnostics
• Compatible with an additional secondary master in the HART network (module acts as the primary master)
• "HART communication error bit" (shows loss of HART connection if a connection had already been estab-
lished successfully)
• Optional: Burst mode for one node per channel
• Optional: Cyclic polling of "HART variables" (HART command 3 or 9)
• Optional: Sensor supply for max. 4 nodes per channel in the multidrop variant
• Optional: FlatStream functionality (module acts as bridge for HART packets)
4.3.7.9.6.1 AnalogInputEvaluated
Names (pChannelName):
AnalogInputEvaluated01
AnalogInputEvaluated02
These registers take the values from the "AnalogInput" registers and use them to generate the evaluated input
values. The configured auxiliary functions are applied to form these values.
Data type Values
INT 0…25000: Normalizing option 0 to 25 mA
0…32767: Normalizing option 0 to 25 mA
0…32767: Normalizing option 4 to 20 mA
UINT 0…65535: Normalizing option 0 to 25 mA
4.3.7.9.6.2 AnalogInput
Names (pChannelName):
AnalogInput01
AnalogInput02
The normalized input values are transferred to these registers. Depending on the scaling selected, the value range
and the data type can be adapted to the requirements of the application. Generated limit values or value changes
from the configured limit value strategy have no effect on these registers.
Data type Values
INT 0…25000: Normalizing option 0 to 25 mA
0…32767: Normalizing option 0 to 25 mA
0…32767: Normalizing option 4 to 20 mA
UINT 0…65535: Normalizing option 0 to 25 mA
4.3.7.9.6.3 AnalogStatus
Names (pChannelName):
AnalogStatus01
AnalogStatus02
The current error status of the module channels is displayed in this register, regardless of the configured replace-
ment value strategy. Some error information may be delayed according to the previously configured condition.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Information
0 Underflow 0 No error
1 Underflow on Channel 0x
1 Overflow 0 No error
1 Overflow on Channel 0x
2 Open line 0 No error
1 Open line on Channel 0x
3 Conversion error 0 No error
1 Conversion error on Channel 0x
4 Composite error 0 No error
1 Composite error on Channel 0x
5 Reserved -
6 Sensor error 0 No error
1 Sensor error on Channel 0x
7 I/O supply error 0 No error
1 I/O supply error on Channel 0x
Underflow:
The signal underflow error status is indicated here according to the configuration. This error information is activated
as a multiple of the conversion cycles only after the configurable delay time has passed ("ErrorDelay" registers).
Overflow:
The signal overflow error status is indicated here according to the configuration. This error information is activated
as a multiple of the conversion cycles only after the configurable delay time has passed ("ErrorDelay" registers).
Open line:
According to the configuration, measurement information is checked for values <2 mA ("OpenLoopLimit" register)
to detect a failure signal. Open line detection takes place using a configurable hysteresis value (default: 100 µA,
"Hysteresis" registers). It is possible to disable open line detection ("AnalogMode" registers) to suppress alarms
when hardware is not present. This error information is activated as a multiple of the conversion cycles only after
the configurable delay time has passed ("ErrorDelay" registers).
Conversion error:
This error status is triggered when the hardware exceeds the conversion time.
Composite error:
This error information derives from the status of individual errors and is only activated after the configurable delay
time has passed ([msec], "SumErrorDelay" registers). Linking this error information to an application makes it
possible to hide temporary temperature value overflows and underflows, for example.
Sensor error:
This error is activated immediately after a fault is detected in the internal sensor supply.
4.3.7.9.6.4 AnalogSampletime
Names (pChannelName):
AnalogSampletime01
AnalogSampletime01_16bit
AnalogSampletime01_32bit
AnalogSampletime02
AnalogSampletime02_16bit
AnalogSampletime02_32bit
The registers return the timestamp for when the module reads the current channel mapping. The values are pro-
vided as signed 2-byte or 4-byte values.
Data type Values [µs]
INT -32768 to 32767: Nettime timestamp of the current input value
DINT -2,147,483,648 to 2,147,483,647: Nettime timestamp of the current input value
How the analog signal is displayed can be adapted to the requirements of the application. Separate configuration
registers per channel are available to aid in this.
Names (pChannelName):
AnMode_1
AnMode_2
These registers are used to predefine the operating parameters that the module will be using for the respective
channel. Each channel must be enabled individually and can be configured and operated independently.
It is extremely important to not that different limit values need to be configured for any display normalizing that
needs to take place.
Data type Values
UINT See bit structure
Bit structure:
Bit Name Information
0 Channel 0 Channel 0x turned off
1 Channel 0x enabled (bus controller default setting)
1 Open line detection 0 Open line monitoring turned off
1 Open line monitoring enabled (bus controller default setting)
2 Underflow detection 0 Underflow detection turned off
1 Underflow detection enabled (bus controller default setting)
3 Replacement value strategy 0 Use replacement values when an error occurs (bus controller
default setting)
1 Keep the last valid converted value
4-5 Normalization 00 Displays 0...25 mA as 0...32767
01 Displays 0...25 mA as 0...25000 [µA] (bus controller default set-
ting)
10 Displays 4...20 mA as 0...32767
11 Displays 0...25 mA as 0...65535
6-15 Reserved
Names (pChannelName):
Samplerate_1
Samplerate_2
A sample rate can be configured for both analog inputs independently of one another. The following formula for
this parameter is derived using the desired sampling frequency:
Sample rate for ADC = (4920000/1024)/sampling frequency
Data type Values
UINT 48 - 1023: Sample rate
960 ... 200 ms ... 5 Hz
480 ... 100 ms ... 10 Hz
320 ... 66.7 ms ... 15 Hz
192 ... 40 ms ... 25 Hz
160 ... 33.3 ms ... 30 Hz
96 ... 20 ms ... 50 Hz (bus controller default setting)
80 ... 16.7 ms ... 60 Hz
48 ... 10 ms ... 100 Hz
The fastest sample rate of 10 ms for the analog inputs is predefined by the cut-off frequency of the hardware filter.
When using HART communication, however, a sample rate not faster than 100 ms is recommended.
4.3.7.9.7.3 OpenLoopLimit
Names (pChannelName):
OpenLoopLimit_1
OpenLoopLimit_2
The limit value for the respective analog input must be set when open circuit monitoring is enabled and if required
by the configured normalization. If limit value monitoring is active, the corresponding error status is output after a
configured delay when falling below this value. Using a default value of 2000 µA, the following values and formulas
apply to this parameter:
• Displaying 0..25 mA as 0..25000 : 2000
• Displaying 0..25 mA as 0..32767 : 2621, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : -4096, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 5243, limit value = ([µA]*65535)/25000
Data type Values
INT -32767...32767: Open circuit limit value
UINT 0...65535: Open circuit limit value
4.3.7.9.7.4 PreparationInterval
Names (pChannelName):
PreparationInterval_1
PreparationInterval_2
If the last valid measurement value should be kept when violating the limit value, then PreparationInterval must be
defined. The measurement values continue to be acquired and converted according to the configured I/O update
time. They are then checked and discarded if they do not meet the specifications. When an error does not occur,
therefore, the measurement value acquired two preparation intervals ago is constantly output.
Data type Values [0.1 ms]
UINT 0…65535
"Application"
How it works: for the value being measured (analog)
Measured values are converted at the configured conversion rate and saved to measurement value memory. Condition:
The current contents of the measurement value memory are checked within the configured interval. If a permis- ↓
- Conversion interval (ADC) elapsed
sible value is present, then the contents of the buffer memory are passed to output memory and the contents of "Measurement value memory"
the measurement value memory are passed to the buffer. Measurement value (digital)
If the check turns up an impermissible value, then the contents of the measurement value memory are discard-
Condition:
ed. The copy direction between the output and buffer memory reverses and the last valid value continues to be
↓ - PreparationInterval elapsed
output.
- Measurement value permissible
"Buffer"
Information: Last valid value
Condition:
If configured to keep the last valid value, the delay time from measuring to outputting the value ↓ - PreparationInterval elapsed
will be at least twice the preparation interval. In the worst case scenario, this can also take twice - Measurement value permissible
the interval time plus the configured ADC conversion rate. "Output memory"
Next-to-last valid/
displayed value
Names (pChannelName):
ReplacementUpper_1
ReplacementUpper_2
ReplacementLower_1
ReplacementLower_2
The "Replace" registers are used to predefine the static values that will be displayed instead of the current mea-
surement value when a limit value is violated.
Data type Values
INT -32767...32767
UINT 0...65535
If the replacement strategy "Use replacement values when an error occurs" is activated, the replacement value must
be set for the respective analog input taking the configured normalization into account as well. When an overflow
or underflow error status occurs, the "AnalogInputEvaluated0x" channel is replaced with the corresponding value.
Using a default value of 21000 µA and 3600 µA, the following values and formulas apply to this parameter:
Overflow:
• Displaying 0..25 mA as 0..25000 : 21000
• Displaying 0..25 mA as 0..32767 : 27524, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : 32767, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 55049, limit value = ([µA]*65535)/25000
Underflow:
• Displaying 0..25 mA as 0..25000 : 3600
• Displaying 0..25 mA as 0..32767 : 4718, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : -819, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 9437, limit value = ([µA]*65535)/25000
Names (pChannelName):
UpperLimit_1
UpperLimit_2
LowerLimit_1
LowerLimit_2
If the value range needs to be restricted further, the "UpperLimit" and "LowerLimit registers can be used to enter
new user-specific limit values.
Data type Values
INT -32767…32767
UINT 0...65535
The limit value must be set for the respective analog input depending on the configured normalization. After the
configured delay time has passed, the corresponding error status is given if the respective value is overrun or
underrun. When this error status occurs, the "AnalogInputEvaluated0x" channel is evaluated according to the
replacement value strategy. Using a default value of 21000 µA and 3600 µA, the following values and formulas
apply to this parameter:
UpperLimit
• Displaying 0..25 mA as 0..25000 : 21000
• Displaying 0..25 mA as 0..32767 : 27524, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : 32767, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 55049, limit value = ([µA]*65535)/25000
LowerLimit
• Displaying 0..25 mA as 0..25000 : 3600
• Displaying 0..25 mA as 0..32767 : 4718, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : -819, limit value = (([µA]*1.31068) - 5242.72)*1.5625
• Displaying 0..25 mA as 0..65535 : 9437, limit value = ([µA]*65535)/25000
4.3.7.9.7.7 Hysteresis
Names (pChannelName):
Hysteres_1
Hysteres_2
If the user-specific limit values are being used, then a hysteresis range should also be defined. The "Hysteresis"
registers configure how far a limit value can be exceeded before a response is triggered.
Data type Values
INT -32767…32767
UINT 0...65535
Te hysteresis value must be set for the respective analog input dpending on the configured normalization. The
error status is cleared if the actual analog value changes by at least this hysteresis value from the limit value in the
allowed direction. Using a default value of 100 µA, the following values and formulas result for this parameter:
• Displaying 0..25 mA as 0..25000 : 100
• Displaying 0..25 mA as 0..32767 : 131, limit value = ([µA]*32767)/25000
• Displaying 4..20 mA as 0..32767 : 156, limit value = [µA]*1.5625
• Displaying 0..25 mA as 0..65535 : 262, limit value = ([µA]*65535)/25000
4.3.7.9.7.8 ErrorDelay
Names (pChannelName):
ErrorDelay_1
ErrorDelay_2
This register specifies the number of consecutive conversion procedures where an error is pending until the cor-
responding individual error status bit is set. The delay applies to underflow, overflow and open circuit errors. This
delay can be used to hide temporary measurement value deviations, for example.
Data type Values
UINT 0...10: Error formation delay [conversion cycles]
2 conversion cycles [default]
4.3.7.9.7.9 SumErrorDelay
Names (pChannelName):
SumErrorDelay_1
SumErrorDelay_2
This register specifies the time in milliseconds that one of the individual error bits must be pending until the com-
posite error status bit is set.
Data type Values
UINT 0...65535: Composite error bit delay [msec]
4000 msec [default]
4.3.7.9.8 HART
HART (Highway Addressable Remote Transducer) is a protocol for communicating with intelligent field devices. It
was developed in order to more efficiently use the infrastructure for transferring analog signals. The digital HART
notifications are modulated to the analog signal using Frequency Shift Keying (FSK). HART can thus use the same
physical line as the analog signal without influencing the original function.
HART slaves are able to determine different process data independently and prepare HART concordantly. This
protocol supports polling of the value of a process variable as well as its unit and status. Field devices usually supply
their information after the master requests it. In newer revisions, it is also possible to transfer configuration data.
There are two different types of HART networks. In a point-to-point network, only one slave is connected to a HART
master. Here, the analog signal and the HART signal can be transferred over the same line. Managing several
slaves with HART requires what is known as a multidrop network. Here, each HART slave is assigned and identified
by a unique address. Classic analog signals cannot be clearly traced in bus systems. As a result, the HART protocol
does not support analog information transfers in multidrop networks up to and including HART Revision 5.
• HART configuration:
HartNodeCnt_1
HartNodeCnt_2
HartBurstNode_1
HartBurstNode_2
HartMode_1
HartMode_2
• HART communication:
PvInput01_[01...15]
PvInput02_[01...15]
PvUnit01_[01...15]
PvUnit02_[01...15]
PvSampleTime01_[01...15]
PvSampleTime01_[01...15]_16bit
PvSampleTime01_[01...15]_32bit
PvSampleTime02_[01...15]
PvSampleTime02_[01...15]_16bit
PvSampleTime02_[01...15]_32bit
PvNodeComStatus01_[01...15]
PvNodeComStatus02_[01...15]
PvCountHartRequest01
PvCountHartRequest02
PvCountHartTimeout01
PvCountHartTimeout02
PvCountHartRxError01
PvCountHartRxError02
PvCountHartFrameError01
PvCountHartFrameError02
PvNodeFound01
PvNodeFound02
PvNodeError01
PvNodeError02
• HART - Extended configuration:
HartNodeDisable_1
HartNodeDisable_2
HartProtTimeOut_1
HartProtTimeOut_2
HartProtRetry_1
HartProtRetry_2
HartPreamble_1
HartPreamble_2
HART modules are analog modules equipped with a HART modem. For each channel, a separate HART network
can be managed by the module, which acts as a primary master. Once configured successfully, the HART infor-
mation is stored in the module where it can then be used by the PLC.
The number of HART slaves must be specified in the configuration.
If only one slave is connected to the HART channel, then it is part of a point-to-point network. The module can then
prepare up to four process variables from the connected slave.
Multidrop mode allows up to 15 HART slaves to be connected. The primary process variable from each slave is
then retrieved.
HartNodeCnt
The "HartNodeCnt" registers tell the module how many HART slaves are connected to a channel.
Information:
If a slave is not connected to one of the HART channels, the value "0" should be defined in this register.
This shortens the I/O update time and avoids superfluous error messages.
Data type Values
USINT 0 HART communication disabled for this channel
1 Point-to-point Standard HART communication (bus controller default)
2 to 15 Multidrop Number of HART slave nodes
HartBurstNode
In addition to the type of network, the user can also choose from two different types of communication behavior.
Conventional HART communication relies on polling. The module requests the data from the individual HART
slaves and receives the corresponding information from each slave as a response. If a HART node should be
queried in short time intervals, the user can configure burst mode for channels on one node. In this case, the slave
transmits the node's information cyclically without constant prompting from the master.
The "HartBurstNode" registers are therefore used to enter the node numbers (short address) for the channels
whose information should be retrieved using burst mode. Burst mode itself is enabled with the "HartMode" register.
Data type Values
USINT 0 to 15
Point-to-point → 0 (bus controller default)
HartMode
The user can use the "HartMode" registers to configure the communication behavior of each of the HART channels.
Generally, the HART nodes are polled individually. This register can still be used to start or stop burst mode when
needed.
In burst mode, a node transmits its information cyclically instead of continuously. As a result, the HART standard
allows the simultaneous usage of both burst mode and polling.
Information:
To retrieve information with burst mode, the "HartBurstNode" register must be configured correctly.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Information
0 Slave polling mode 0 Polling mode enabled (bus controller default)
1 Polling mode disabled
1 Start slave burst mode 0 No response to burst (bus controller default)
1 Enables burst mode in the "HartBurstNode" node
2 Stop slave burst mode 0 No response to burst (bus controller default)
1 Disables burst mode if enabled
3-7 Reserved -
Once the configuration has been completed, the information is retrieved automatically and transferred to the
module's registers. A separate register in the module is implemented for each piece of information. HART modules
are designed to retrieve up to 15 pieces of information per channel. The module reads in the data, stores it in tem-
porary memory and prepares it for retrieval. When the X2X master accesses the module registers, it is irrelevant
whether the HART data originates from a point-to-point network or a multidrop network.
The HART specifications stipulates that information from a HART node be split into various pieces. The value of a
process variable is stored to the respective "PvInput" register and has a size of 4 bytes (REAL) in accordance with
the HART specification. Due to the length limitation of 30 bytes on the X2X bus, there are restrictions to the number
of cyclic variables possible. It is recommended to only transfer a maximum of two "PvInput" registers cyclically to
the X2X master. All other information should be transferred in a different way. To access HART information, the
user can choose from among the following methods:
• Data points that are configured to be transferred cyclically are read once per bus cycle. This method allows
information to be exchanged between the module and the X2X master in real time. Nevertheless, the length
limitation may prevent all data from being retrieved within one cycle.
• If the AsIOAcc library is used, information is retrieved acyclically only when it is needed, i.e. communication
can be adapted to the application running on the X2X master. In this way, all of the necessary module
registers on the X2X bus can be polled despite the length limitation.
This method of information exchange is not real-time capable.
• HART modules are equipped with a FlatStream interface. When using FlatStream communication, the
module acts a bridge between the X2X master and the HART slave, i.e. the X2X master communicates
directly with the HART slave (see section "FlatStream communication").
FlatStream communication is also not real-time capable. It allows unrestricted access to the HART slave.
The user must have sufficient knowledge of the HART protocol command set as well as the capabilities
of the HART slave device.
PvInput
The "Input" registers return the current value of the process variable that has been read.
Information:
These registers are of data type REAL, which means that the available bytes on the X2X bus are filled
more quickly when operated cyclically. If information from several slave nodes is needed, it must be
retrieved acyclically or using FlatStream.
Data type Values
REAL IEEE745 SPF: 32-bit data type with valid value
0x7FA00000: Not a number (NaN) with invalid value
PvUnit
The "PvUnit" registers return a HART-specific code that specifies the unit for the measured value. The coding for
this is established in the HART specification.
Data type Values
USINT See description of the HART slave
See HART specification
PvSampleTime
The registers return the timestamp for when the module reads the current channel mapping. The values are pro-
vided as signed 2-byte or 4-byte values.
Data type Values [µs]
INT -32768 to 32767: Nettime timestamp of the current input value
DINT -2,147,483,648 to 2,147,483,647: Nettime timestamp of the current input value
This refers to the point in time when the HART master receives the slave's response. This is a way to check whether
new HART information has been read since the last X2X cycle.
Information:
The cycle times of a HART network are relatively long so that it is not possible to reliably determine
when exactly the measured value is retrieved with just this information.
PvNodeComStatus
The "PvNodeComStatus" registers return information about whether a value that has been read is valid. According
to the HART specification, this type of status register consists of two parts. The high byte stores the "response
code" and the low byte the "field device status". This makes it possible to check the current status of a read process
variable.
The "PvNodeComStatus" register can be checked before further processing information in temporary storage. If
the current value is 0x0000, an error was not detected during the HART transfer and the information from the
checked node can be used. If a different value is present, the situation in the HART network should be checked.
This can be done using an extension register, for example.
Data type Values
UINT See bit structure
Bit structure:
Bit Name Information
0 Quality - Node information 2…n 0 Digital measured value okay
1 Measured value outside the permitted range
1 Quality - Node information 1 0 Digital measured value okay
1 Measured value outside the permitted range
2 Limit violation 0 Parameter okay
1 Invalid measured value(s) or encoder supply value
3 Static analog signal 0 Normal value change/fluctuation
1 Constant analog value of Node 1 slave
4 Additional status information 0 Not available
(only supported by a few slaves) 1 Available (only using FlatStream command #48)
5 Reboot 0 Normal operation
1 Field device restarts
6 Device ID 0 Unchanged
1 Changed
7 Device error 0 Measured value okay
1 Questionable measured value information
8-14 Response code, if relevant See coding (HART-specific)
15 Error - Communication 0 Error-free communication (response code irrelevant)
1 Faulty communication (response code relevant)
PvCountHartRequest
The "PvCountHartRequest" registers are increased once the module is ready to transmit a message to the corre-
sponding channel.
Data type Values
UINT 0 to 65535
PvCountHartTimeout
The "PvCountHartTimeout" registers are increased if the slave exceeds the maximum permitted time before re-
sponding to the module's request.
Data type Values
UINT 0 to 65535
PvCountHartRxError
The "PvCountHartRxError" registers are increased if communication errors occur on Layer 1 of the OSI model (e.g.
transmission error as per parity bit).
Data type Values
UINT 0 to 65535
PvCountHartFrameError
The "PvCountHartFrameError" registers are increased if communication errors occur on Layer 2 of the OSI model
(e.g. faulty telegram structure).
Data type Values
UINT 0 to 65535
PvNodeFound
The "PvNodeFound" registers provide information about which nodes were detected on which channel (slave
identified successfully).
Data type Values
UINT See bit structure
Bit structure:
Bit Name Information
0 Node 0 (default mode) 0 Not detected as valid
Node 1 (multidrop mode) 1 Detected as valid
1 Node 2 (multidrop mode) 0 Not detected as valid
1 Detected as valid
...
13 Node 14 (multidrop mode) 0 Not detected as valid
1 Detected as valid
14 Node 15 (multidrop mode) 0 Not detected as valid
1 Detected as valid
15 Reserved -
PvNodeError
The "PvNodeError" registers contain the HART communication error bits. These bits are set if the connection to
a node was established successfully but the node at some point no longer responds as it should (e.g. the HART
slave exceeds the configured timeout / number of retries).
Data type Values
UINT See bit structure
Bit structure:
Bit Name Information
0 Node 0 (default mode) 0 Detected as having no errors
Node 1 (multidrop mode) 1 Error
1 Node 2 (multidrop mode) 0 Detected as having no errors
1 Error
...
13 Node 14 (multidrop mode) 0 Detected as having no errors
1 Error
14 Node 15 (multidrop mode) 0 Detected as having no errors
1 Error
15 Reserved -
The additional configuration registers are specified values when the module is started. In most systems, the user
does not need to make any adjustments here. Register values should only be changed if HART network commu-
nication is not taking place satisfactorily.
HartNodeDisable
The "HartNodeDisable" registers are intended for things like maintenance. They make it possible to cut off config-
ured HART nodes to suppress error messages for a certain period of time. During normal operation, the configured
nodes must be switched active to guarantee that the procedure runs smoothly.
Data type Values
UINT See bit structure
Bit structure:
Bit Name Information
0 Node 0 (default mode) 0 Enabled (bus controller default)
Node 1 (multidrop mode) 1 Disabled
1 Node 2 (multidrop mode) 0 Enabled
1 Disabled (bus controller default)
...
13 Node 14 (multidrop mode) 0 Enabled
1 Disabled (bus controller default)
14 Node 15 (multidrop mode) 0 Enabled
1 Disabled (bus controller default)
15 Reserved -
HartProtTimeOut
The "HartProtTimeOut" registers specify the time span within which the slave must respond for the response to
be valid.
Data type Values [ms]
UINT 0 to 65535
Bus controller default: 256 [ms]
HartProtRetry
The "HartProtRetry" registers how many times the master retries a request if it receives an invalid response or
no response at all.
Data type Values
UINT 0 to 65535
Bus controller default: 3 attempts
HartPreamble
The length of the preamble can be set in the "HartPreamble" registers. The preamble is used to synchronize the
receiver to the transmitter. The longer the declared preamble, the less chance that a communication error will
occur. Nevertheless, a useful signal is not transmitted during synchronization so the preamble should be kept as
short as possible.
Data type Values
UINT 5 to 20
Bus controller default: 20
4.3.7.9.9.1 Introduction
B&R offers an additional communication method for some modules. "FlatStream" was designed for X2X and
POWERLINK networks and allows data transmission to be adapted to individual demands. Although this method
is not 100% real-time capable, it still allows data transmission to be handled more efficiently than with standard
cyclic polling.
Field device
X2X language
Cyclic call
via I/O mapping
B&R CPU
Cyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
bus controller
Acyclic call
via
library functions
B&R CPU
Acyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
bus controller
FlatStream
The physical properties of the bus system limit the amount of data that can be transmitted during one bus cycle.
With FlatStream communication, all messages are viewed as part of a continuous data stream. Long data streams
must be broken down into several fragments that are sent one after the other. To understand how the receiver puts
these fragments back together to get the original information, it is important to understand the difference between
a message, a segment, a sequence and an MTU.
Message:
A message refers to information exchanged between two partner stations. The length of a message is not restricted
by the FlatStream communication method. Nevertheless, module-specific limitations must be considered.
Segment (logical division of a message):
A segment has a finite size and can be understood as a section of a message. The number of segments per
message is arbitrary. So that the recipient can correctly reassemble the transmitted segments, each segment
is preceded by a byte with additional information. This control byte contains information such as the length of a
segment and whether the approaching segment completes the message. This makes it possible for the receiving
station to interpret the incoming data stream correctly.
Sequence (how a segment needs to be arranged physically):
The maximum size of a sequence corresponds to the number of enabled Rx or Tx bytes (later: "MTU"). The
transmitting station splits the transmit array into valid sequences. These sequences are then written successively
to the MTU and transmitted to the receiving station where they are put back together again. The receiver stores
the incoming sequences in a receive array, obtaining an image of the data stream in the process.
With FlatStream communication, the number of sequences sent are counted. Successfully transmitted sequences
must be acknowledged by the receiving station to ensure the integrity of the transmission.
MTU (Maximum Transmission Unit) – Physical transport:
MTU refers to the enabled USINT registers used with FlatStream. These registers can accept at least one se-
quence and pass it on to the receiving station. A separate MTU is defined for each direction of communication.
The OutputMTU defines the number of FlatStream Tx bytes, and the InputMTU specifies the number of FlatStream
Rx bytes. The MTUs are transported cyclically via the X2X Link, increasing the load with each additional enabled
USINT register.
Properties:
FlatStream messages are not transmitted cyclically or in 100% real time. Many bus cycles may be needed to trans-
mit a particular message. Although the Rx and Tx registers are exchanged between the transmitter and the receiv-
er cyclically, they are only processed further if explicitly accepted by the "InputSequence" or "OutputSequence"
register.
Behavior in the event of an error (brief summary):
The protocol for X2X and POWERLINK networks specifies that the last valid values should be retained when
disturbances occur. With conventional communication (cyclic/acyclic data queries), this type of error can generally
be ignored.
In order for communication to also take place without errors using FlatStream, all of the sequences issued by the
receiver must be acknowledged. If Forward functionality is not used, then subsequent communication is delayed
for the length of the disturbance.
If Forward functionality is being used, the receiving station receives a transmission counter that is incremented
twice. The receiver stops, i.e. it no longer returns any acknowledgments. The transmitting station uses the Se-
quenceAck to determine that the transmission was faulty and that all affected sequences will have to be repeated.
Requirements:
Before FlatStream can be used, the respective communication direction must be synchronized, i.e. both commu-
nication partners cyclically query the sequence counter on the opposite station. This checks to see if there is new
data that should be accepted.
Communication:
If a communication partner wants to transmit a message to its opposite station, it should first create a transmit
array that corresponds to FlatStream conventions. This allows the FlatStream data to be organized very efficiently
without having to block other important resources.
PLC / Bus controller Module
Module-internal Module-internal
Transmit array OutputMTU Receive buffer Receive array
Type: USINT Type: USINT Type: USINT Type: USINT
Module-internal Module-internal
Receive array InputMTU Send buffer Transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Five registers are available for configuring FlatStream. The default configuration can be used to transmit small
amounts of data relatively easily.
Information:
The CPU communicates directly with the field device via the OutputSequence/InputSequence registers
and the enabled Tx / Rx bytes. For this reason, the user needs to have sufficient knowledge of the
communication protocol being used on the field device.
FlatStream configuration
To use FlatStream, the program sequence must first be expanded. The cycle time of the FlatStream routines must
be set to a multiple of the bus cycle. Other program routines should be implemented in Cyclic #1 to ensure data
consistency.
At the absolute minimum, the "InputMTU" and "OutputMTU" registers need to be configured. All other registers are
filled in with default values at the beginning and can be used immediately. These registers are used for additional
options, e.g. to transmit data in a more compact way or to increase the efficiency of the general procedure.
The Forward registers extend the functionality of the FlatStream protocol. This functionality is useful for substan-
tially increasing the FlatStream data rate, but it also requires quite a bit of extra work when creating the program
sequence.
OutputMTU, InputMTU
These registers define the number of enabled Tx or Rx bytes, i.e. the maximum size of a sequence. The user must
consider that the more bytes made available also means a higher load on the bus system.
Information:
In the rest of this documentation, the names "OutputMTU" and "InputMTU" do not refer to the registers
explained here. Instead, they are used as synonyms for the currently enabled Tx or Rx bytes.
Data type Value
USINT See the module-specific register overview (theoretically: 3 - 27)
FlatStream operation
When using FlatStream, the communication direction is enormously important. For sending data to a module ("out-
put" direction), the Tx bytes are used. For receiving data from a module ("input" direction), the Rx bytes are used.
The "OutputSequence" and "InputSequence" registers are used to control and ensure that communication is taking
place properly, i.e. the transmitter issues the directive that the data should be accepted and the receiver acknowl-
edges that a sequence has been transmitted successfully.
Tx and Rx bytes:
The Tx and Rx bytes are cyclic registers used to transport the payload data and the necessary control bytes.
The number of active Tx/Rx bytes is taken from the configuration of the "OutputMTU" and "InputMTU" registers,
respectively.
In the user program, only the Tx/Rx bytes from the CPU can be used. The corresponding counterparts are located
in the module and are not accessible to the user. For this reason, names were chosen from the CPU point of view.
• "T" - "Transmit" → CPU transmits data to the module.
• "R" - "Receive" → CPU receives data from the module.
Data type Value
USINT 0...65535
Control bytes:
In addition to the payload data, the Tx and Rx bytes also transmit the necessary control bytes. These control bytes
contain additional information about the data stream so that the receiver can reconstruct the original message from
the transmitted segments.
Bit structure of a control byte:
Bit Name Information
0-5 SegmentLength 0-63 Size of the subsequent segment in bytes (default: Max. MTU size - 1)
6 nextCBPos 0 Next control byte at the beginning of the next MTU
1 Next control byte directly after the end of the current segment
7 MessageEndBit 0 Message continues after the subsequent segment
1 Message ended by the subsequent segment
SegmentLength:
The segment length lets the receiver know the length of the coming segment. If the configured segment length
is insufficient for a message, then the information must be distributed over several segments. In these cases, the
actual end of the message is detected using bit 7 of the control byte.
Information:
The control byte is not included in the calculation to determine the segment length. The segment length
is only derived from the bytes of payload data.
nextCBPos:
This bit indicates the position where the next control byte is to be expected. This information is especially important
when using the "MultiSegmentMTU" option.
When using FlatStream communication with multi-segment MTUs, the next control byte is no longer expected in
the first Rx byte of the subsequent MTU, but directly after the current segment.
MessageEndBit:
The "MessageEndBit" is set if the subsequent segment completes a message. The message has then been com-
pletely transmitted and is ready for further processing.
Information:
In the output direction, this bit must also be set if one individual segment is enough to hold the entire
message. The module will only process a message internally if this identifier is detected.
The size of the message being transmitted can be calculated by adding all of the message's segment
lengths together.
FlatStream formula for calculating message length:
Message [bytes] = SegmentLengths (all CBs without ME) + SegmentLength (of the first CB with CB Control byte
ME) ME MessageEndBit
OutputSequence
The "OutputSequence" register contains information about the communication status of the CPU. It is written by
the CPU and read by the module.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Information
0-2 OutputSequenceCounter 0-7 Counter for the sequences issued in the output direction
3 OutputSyncBit 0 Output direction disabled
1 Output direction enabled
4-6 InputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 InputSyncAck 0 Input direction not ready (disabled)
1 Input direction ready (enabled)
OutputSequenceCounter:
The OutputSequenceCounter is a continuous counter of sequences that have been issued by the CPU. The CPU
uses the OutputSequenceCounter to direct the module to accept a sequence (the output direction must be syn-
chronized when this happens).
OutputSyncBit:
The CPU uses the OutputSyncBit to attempt to synchronize the output channel.
InputSequenceAck:
InputSequenceAck is used for acknowledgment. The value of the InputSequenceCounter is mirrored if the CPU
has received a sequence successfully.
InputSyncAck:
The InputSyncAck bit acknowledges the synchronization of the input channel for the module. This indicates that
the CPU is ready to receive data.
InputSequence
The "InputSequence" register contains information about the communication status of the module. It is written by
the module and should only be read by the CPU.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Information
0-2 InputSequenceCounter 0-7 Counter for sequences issued in the input direction
3 InputSyncBit 0 Not ready (disabled)
1 Ready (enabled)
4-6 OutputSequenceAck 0-7 Mirrors the OutputSequenceCounter value
7 OutputSyncAck 0 Not ready (disabled)
1 Ready (enabled)
InputSequenceCounter:
The InputSequenceCounter is a continuous counter of sequences that have been issued by the module. The
module uses the InputSequenceCounter to direct the CPU to accept a sequence (the input direction must be
synchronized when this happens).
InputSyncBit:
The module uses the InputSyncBit to attempt to synchronize the input channel.
OutputSequenceAck:
OutputSequenceAck is used for acknowledgment. The value of the OutputSequenceCounter is mirrored if the
module has received a sequence successfully.
OutputSyncAck:
The OutputSyncAck bit acknowledges the synchronization of the output channel for the CPU. This indicates that
the module is ready to receive data.
7 InputSyncAck 7 OutputSyncAck
Information:
If communication is interrupted, segments from the unfinished message are discarded. All messages
that were transmitted completely are processed.
Synchronization
During synchronization, a communication channel is opened. It is important to make sure that a module is present
and that the current value of the SequenceCounter is stored on the station receiving the message.
FlatStream can handle full-duplex communication. This means that both channels / communication directions can
be handled separately. They have to be synchronized independently so that simplex communication can theoret-
ically be carried out as well.
If a channel is synchronized, then the opposite station is ready to receive messages from the transmitter. Before
the transmitter can send data, it needs to first create a transmit array in order to meet FlatStream requirements.
The transmitting station must also generate a control byte for each segment created. This control byte contains
information about how the subsequent part of the data being transmitted should be processed. The position of the
next control byte in the data stream can vary. For this reason, it must be clearly defined at all times when a new
control byte is being transmitted. The first control byte is always in the first byte of the first sequence. All subsequent
positions are determined recursively.
FlatStream formula for calculating the position of the next control byte:
Position (of the next control byte) = Current position + 1 + Segment length
Example:
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The rest of the configuration corresponds to the default settings.
Message 1: Transmit/Receive array
Default
Message 2:
Message 3:
C3 B1 B2 - - - - Sequence for bus cyc. 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C4 D1 D2 D3 D4 D5 D6 Sequence for bus cyc. 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C0 (control byte 0) C1 (control byte 1) C2 (control byte 2)
- SegmentLength (0) = 0 - SegmentLength (6) = 6 - SegmentLength (1) = 1
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (0) = 0 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 0 Control byte Σ 6 Control byte Σ 129
Table 44: FlatStream determination of the control bytes for the default configuration example (part 1)
C3 (control byte 3) C4 (control byte 4) C5 (control byte 5)
- SegmentLength (2) = 2 - SegmentLength (6) = 6 - SegmentLength (3) = 3
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 130 Control byte Σ 6 Control byte Σ 131
Table 45: FlatStream determination of the control bytes for the default configuration example (part 2)
When transmitting data, the transmit array must be generated in the application program. Sequences are then
transmitted one by one using FlatStream and received by the module.
Information:
Although all B&R modules with FlatStream communication always support the most compact trans-
missions in the output direction, it is recommended to use the same design for the transfer arrays in
both communication directions.
Start
► diff = (OutputSequenceCounter -
OutputSequenceAck) AND 7
► limit = (OutputSequenceCounter -
LastValidAck) AND 7
Yes Yes No
No LastValidAck =
diff = 0?
OutputSequenceAck
Yes
LastValidAck = No
OutputSequenceAck = 0?
OutputSequenceAck
Yes
No OutputSequenceCounter = 0
More sequences to be sent? OutputSequenceCounter = 1 OutputSyncBit = 1
LastValidAck = 0
Yes
When receiving data, the transmit array is generated by the module, transferred via FlatStream and must then
be reproduced in the receive array. The structure of the incoming data stream can be configured with the mode
register. The algorithm for receiving the data does not change in this regard.
PLC / Bus controller Module
Module-internal Module-internal
Receive array InputMTU Send buffer Transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Start
► InputSequenceAck = InputSequenceCounter
Synchronization
No
InputSyncBit = 1? ► RemainingSegmentSize = 0
► SegmentFlags = 0
Yes
No No
InputSyncAck = 1? InputSequenceAck > 0?
Yes Yes
MTU_Offset = 0 InputSyncAck = 1
(InputSequenceCounter – No
InputSequenceAck)
AND 0x07 = 1?
Yes
► RemainingSegmentSize =
Yes MTU_Data[MTU_Offset] AND 0b0011 1111
RemainingSegmentSize = 0? ► SegmentFlags =
MTU_Data[MTU_Offset] AND 0b1100 0000
No ► MTU_Offset = MTU_Offset + 1
No
No
Yes
► InputSequenceAck =
InputMTU_Size = MTU_Offset?
InputSequenceCounter
No
Details
Information:
When transmitting with MultiSegmentMTUs, it is possible for several small messages to be part of one
sequence. In the program, it's important to make sure that a sufficient number of receive arrays can
be managed. The entire sequence must be accepted before it is possible to change the Acknowledge
register.
If a SequenceCounter is incremented by more than one value, then an error has occurred (this situation is very
unlikely when operating without "Forward" functionality).
In this case, the receiver stops. All additional incoming sequences are ignored until the transmission with the correct
SequenceCounter is retried. This response prevents the transmitter from receiving any more acknowledgments for
transmitted sequences. The transmitter can identify the last successfully transmitted sequence from the opposite
station's SequenceAck and continue the transmission from this point.
Acknowledgments must be checked for validity.
If the receiver has successfully accepted a sequence, it must be acknowledged. The receiver takes on the Se-
quenceCounter value sent along with the transmission and matches the SequenceAck to it. The transmitter reads
the SequenceAck and registers the successful transmission. If the transmitter acknowledges a sequence that has
not yet been dispatched, then the transmission needs to be interrupted and the channel resynchronized. The syn-
chronization bits are reset and the current/incomplete message is discarded. It needs to be sent again once the
channel has been resynchronized.
In the input direction, the transmit array is generated automatically. This register offers two options to the user
that allow an incoming data stream to have a more compact arrangement. Once enabled, the program code for
evaluation must be adapted accordingly.
Information:
All B&R modules that offer FlatStream mode support the options "Large segments" and "MultiSeg-
mentMTUs" in the output direction. Compact transmission only needs to be explicitly allowed in the
input direction.
Bit structure:
Bit Name Information
0 MultiSegmentMTU 0 Not allowed (default)
1 Allowed
1 Large segments 0 Not allowed (default)
1 Allowed
2-7 Reserved
Default:
By default, both options relating to compact transmission in the input direction are disabled.
1. The module only forms segments that are at least one byte smaller than the enabled MTU. Each sequence
begins with a control byte so that the data stream is clearly structured and relatively easy to evaluate.
2. Since a FlatStream message can be of any length, the last segment of the message frequently doesn't fill up
all of the MTU's space. By default, the remaining bytes during this type of transfer cycle are not used.
C C C
- - -
ME0 ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
MultiSegmentMTUs allowed:
With this option, the InputMTU is completely filled (if enough data is pending). The previously unfilled Rx bytes
transmit the next control bytes and their segments. This allows the enabled Rx bytes to be used more efficiently.
C C C C
- -
ME0 ME1 ME0 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Information:
It is still possible to split up a message into several segments, however. If this option is used and
messages with more than 63 bytes occur, for example, then messages can still be split up among
several segments.
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Figure 84: Arrangement of messages in the MTU (large segments and MultiSegmentMTUs)
FlatStream adjustment
If the way messages are structured is changed, then the way data in the transmit/receive array is arranged is also
different. The following changes apply to the example given earlier on.
MultiSegmentMTU:
If MultiSegmentMTUs are allowed, then "open positions" in an MTU can be used. These "open positions" occur if
the last segment in a message doesn't fully use the entire MTU. MultiSegmentMTUs allow these bits to be used
to transmit the following control bytes and segments. In the program sequence, the "nextCBPos" bit in the control
byte is set so that the receiver can correctly identify the next control byte.
Example:
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows transmission of MultiSegmentMTUs.
Message 1: Transmit/Receive array
Message 2: MultiSegmentMTU
Message 3:
C5 D2 D3 D4 D5 D6 D7 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C6 D8 D9 C0 - - - Sequence for bus cycle 4
➯ First segment = Control byte + 2 data bytes (MTU still has 2 open bytes)
• Message 3 (9 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (6) = 6 - SegmentLength (1) = 1 - SegmentLength (2) = 2
- nextCBPos (1) = 64 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 70 Control byte Σ 193 Control byte Σ 194
Table 46: FlatStream determination of the control bytes for example with MultiSegmentMTU (part 1)
Warning!
The second sequence must have been completely processed before it can be acknowledged with Se-
quenceAck. In the example, there are three different segments within the second sequence, i.e. the
program must include enough receive arrays to handle this situation.
C4 (control byte 4) C5 (control byte 5) C6 (control byte 6)
- SegmentLength (1) = 1 - SegmentLength (6) = 6 - SegmentLength (2) = 2
- nextCBPos (6) = 6 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 0 - MessageEndBit (1) = 128
Control byte Σ 7 Control byte Σ 70 Control byte Σ 194
Table 47: FlatStream determination of the control bytes for example with MultiSegmentMTU (part 2)
Large segments:
Segments are limited to a maximum of 63 bytes. This means they can be larger than the active MTU. These large
segments are divided among several sequences when transmitted. It is possible for sequences to be completely
filled with payload data and not have a control byte.
Information:
It is still possible to subdivide a message into several segments so that the size of a data packet doesn't
also have to be limited to 63 bytes.
Example:
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows the transmission of large segments.
Message 1: Transmit/Receive array
Message 3:
C2 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C3 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 48: FlatStream determination of the control bytes for example with large segments.
Message 3:
D3 D4 D5 D6 D7 D8 D9 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C0 - - - - - - Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 49: FlatStream determination of the control bytes for large segments and MultiSegmentMTU example
Forward functionality is a method that can be used to substantially increase the FlatStream data rate. The basic
principle is also used in other technical areas such as "pipelining" for microprocessors.
Operating principle
X2X Link communication cycles through five different steps to transmit a FlatStream sequence. At least five bus
cycles are therefore required to successfully transfer the sequence.
Step I Step II Step III Step IV Step V
Actions Transfer sequence from Cyclic matching of MTU and Append sequence to re- Cyclic matching of Check SequenceAck
transmit array, module buffer ceive array MTU and module buffer
increase Sequence- Adjust SequenceAck
Counter
Resource Sender Bus system Recipient Bus system Sender
(task to transmit) (direction 1) (task to receive) (direction 2) (task for Ack checking)
Sequence 3 ...
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Configuration
The Forward function only has to be enabled for the input direction. Two additional configuration registers are
available for doing so. FlatStream modules have been optimized in such a way that they support this function. In
the output direction, the Forward function can be used as soon as the size of the OutputMTU is specified.
Forward:
With the "Forward" register, the user specifies how many unacknowledged sequences the module is allowed to
transmit.
Recommendation:
X2X Link: Max. 5
POWERLINK: Max. 7
Data type Value
USINT 1...7
Default: 1
ForwardDelay:
The "ForwardDelay" register is used to specify the delay time in µs. This is the amount of time the module has
to wait after sending a sequence until it is allowed to write new data to the MTU in the following bus cycle. The
program routine for receiving sequences from a module can therefore be run in a task class whose cycle time is
slower than the bus cycle.
Data type Values [µs]
UINT 0...65535
Default: 0
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Figure 89: Effect of ForwardDelay when using FlatStream communication with the Forward function
In the program, it is important to make sure that the CPU is processing all of the incoming InputSequences and In-
putMTUs. The ForwardDelay value causes delayed acknowledgment in the output direction and delayed reception
in the input direction. In this way, the CPU has more time to process the incoming InputSequence or InputMTU.
The basic algorithm for transmitting and receiving data remains the same. With the Forward function, up to seven
unacknowledged sequences can be transmitted. Sequences can be transmitted without having to wait for the
previous message to be acknowledged. Since the delay between writing and response is eliminated, a considerable
amount of additional data can be transferred in the same time window.
Algorithm for transmitting:
Cyclic status query:
- The Module monitors the OutputSequenceCounter.
0. Cyclic checks:
- The CPU must check OutputSyncAck.
→ If OutputSyncAck = 0: Reset the OutputSyncBit and resynchronize the channel.
- The CPU must check whether OutputMTU is enabled.
→ If OutputSequenceCounter > OutputSequenceAck + 7, then it is not enabled because the last sequence has not yet been acknowledged.
1. Preparation (create transmit array):
- The CPU must split up the message into valid segments and create the necessary control bytes.
- The CPU must add the segments and control bytes to the transmit array.
2. Transmitting:
- The CPU must transfer the current part of the transmit array to the OutputMTU.
- The CPU must increase the OutputSequenceCounter for the sequence to be accepted by the module.
- The CPU can then transmit in the next bus cycle if the MTU has been enabled.
The module responds since OutputSequenceCounter > OutputSequenceAck:
- The module accepts data from the internal receive buffer and appends it to the end of the internal receive array.
- The module is acknowledged and the currently received value of the OutputSequenceCounter is transferred to OutputSequenceAck.
- The module requests the status cyclically again.
3. Completion (acknowledgment):
- The CPU must check OutputSequenceAck cyclically.
→ A sequence is only considered to have been transmitted successfully if it has been acknowledged via OutputSequenceAck. In order to detect potential trans-
mission errors in the last sequence as well, it is important to make sure that the algorithm is run through long enough.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost (the relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individ-
ually).
Details/Background:
1. Illegal SequenceCounter size (counter offset)
Error situation: MTU not enabled
If the difference between SequenceCounter and SequenceAck is larger than allowed during transmission,
then a transmission error has occurred. In this case, all unacknowledged sequences must be repeated with
the old SequenceCounter value.
2. Checking an acknowledgment
After an acknowledgment has been received, a check must verify whether the acknowledged sequence has
been transmitted and had not yet been unacknowledged. If a sequence has been acknowledged more than
once, then a fatal error has occurred. The channel must be closed and resynchronized (same behavior as
when not using Forward).
Information:
In exceptional cases, the module can increment OutputSequenceAck by more than 1 when using
Forward.
This is not an error. The CPU is permitted to consider all sequences up to the one being acknowl-
edged as having been transmitted successfully.
In industrial environments, it is often the case that many different devices from various manufacturers are being
used side by side. The electrical and/or electromagnetic properties of these technical devices can sometimes cause
them to interfere with one another. These kinds of situations can be reproduced and protected against in laboratory
conditions only to a certain point.
Precautions have been taken for X2X Link transmissions if this type of interference occurs. For example, if an
invalid checksum occurs, the I/O system will ignore the data from this bus cycle and the receiver will receive the
last valid data once more. With conventional (cyclic) data points, this error can often be ignored. In the following
cycle, the same data point is again retrieved, adjusted and transmitted.
Using Forward functionality with FlatStream communication makes this situation more complex. The receiver re-
ceives the old data again in this situation as well, i.e. the previous values for SequenceAck/SequenceCounter and
the old MTU.
Loss of acknowledgment (SequenceAck):
If a SequenceAck value is lost, then the MTU was already transmitted properly. For this reason, the receiver is per-
mitted to continue processing with the next sequence. The SequenceAck is aligned with the associated Sequence-
Counter and sent back to the transmitter. Checking the incoming acknowledgments shows that all sequences up
to the last one acknowledged have been transmitted successfully (see sequences 1 and 2 in the image).
Loss of transmission (SequenceCounter, MTU):
If a bus cycle drops out and the SequenceCounter value and/or filled MTU are lost, then no data reaches the
receiver. At this point, the transmission routine is not yet affected by the error. The time-controlled MTU is released
again and can be rewritten to. The receiver receives SequenceCounter values that have been incremented several
times. For the receive array to be put together correctly, the receiver is only allowed to process transmissions
whose SequenceCounter has been increased by one. The incoming sequences must be ignored, i.e. the receiver
stops and no longer transmits back any acknowledgments. If the maximum number of unacknowledged sequences
has been sent and no acknowledgments are returned, the transmitter must repeat the affected SequenceCounter
and associated MTUs (see sequence 3 and 4 in the image).
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 EMC Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
When using FlatStream communication, the module acts as a bridge between the X2X master and an intelligent
field device connected to the module. FlatStream mode can be used for either point-to-point connections as well
as for multidrop systems. Specific algorithms such as timeout and checksum monitoring are usually managed
automatically. During normal operation, the user does not have access to these details.
HART is considered a master-slave network where half-duplex communication takes place asynchronously. Vari-
ous features have been included to ensure that signals are transmitted without errors.
For example, the user can increase the length of the preamble, thus making the transmission more secure. How-
ever, this also has an effect on the percentage of payload data and overhead.
Additional information about HART can be found at http://www.HARTcomm.org.
Operation
The module has two independent channels. When using FlatStream, the channel number must therefore be spec-
ified. The general structure of a FlatStream frame is extended as follows.
Input/Output sequence Tx/Rx bytes
(Unchanged) Control byte Channel number HART frame
(unchanged) (without preamble and checksum)
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
200 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Analog inputs 1 ms
4.3.8 X20AI2622
The module is equipped with 2 inputs with 13-bit (including sign) digital converter resolution. It is possible to select
between the current and voltage signal using different connection terminal points.
This module is designed for X20 6-pin terminal blocks. If needed (e.g. for logistical reasons), the 12-pin terminal
block can also be used.
• 2 analog inputs
• Either current or voltage signal possible
• 13-bit digital converter resolution
Product ID X20AI2622
Short description
I/O module 2 analog inputs ±10 V or 0 to 20 mA / 4 to 20 mA
General information
B&R ID code 0x1B9E
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 0.8 W 1)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Analog inputs
Input ±10 V or 0 to 20 mA / 4 to 20 mA, via different connection terminal points
Input type Differential input
Digital converter resolution
Voltage ±12-bit
Current 12-bit
Conversion time 300 µs for all inputs
Output format INT
Output format
Voltage INT 0x8001 - 0x7FFF / 1 LSB = 0x0008 = 2.441 mV
Current INT 0x0000 - 0x7FFF / 1 LSB = 0x0008 = 4.883 µA
Input impedance in signal range
Voltage 20 MΩ
Current -
Load
Voltage -
Current <400 Ω
Input protection Protection against wiring with supply voltage
Permitted input signal
Voltage Max. ±30 V
Current Max. ±50 mA
Output of the digital value during overload
Below lower limit
Voltage 0x8001
Current 0x0000
Above upper limit
Voltage 0x7FFF
Current 0x7FFF
Conversion procedure SAR
Input filter 3rd-order low pass / cutoff frequency 1 kHz
Max. error at 25°C
Voltage
Gain 0.08% 2)
Offset 0.015% 3)
Current
Gain 0 to 20 mA = 0.08% / 4 to 20 mA = 0.1% 2)
Offset 0 to 20 mA = 0.03% / 4 to 20 mA = 0.16% 4)
Max. gain drift
Voltage 0.006 %/°C 2)
Current 0 to 20 mA = 0.009 %/°C
4 to 20 mA = 0.0113 %/°C 2)
Max. offset drift
Voltage 0.002 %/°C 3)
Current 0 to 20 mA = 0.004 %/°C
4 to 20 mA = 0.005 %/°C 4)
Common-mode rejection
DC 70 dB
50 Hz 70 dB
Common-mode range ±12 V
4.3.8.5 Pinout
r e
X20 AI 2622
1 2
AI + 1 I AI + 2 I
AI + 1 U AI + 2 U
AI - 1 U/I AI - 2 U/I
Voltage Current
measurement measurement
Current/Voltage switching
PTC
AI + x I
Shunt
AI + x U Input value
A/D
converter
I/O status
AI - x U/I
LED (green)
1) The offset specifies the position of the register within the CAN object.
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Name:
AnalogInput01 to AnalogInput02
The analog input value are mapped to this register depending on the configured operating mode.
Data type Value Input signal:
INT -32768 to 32767 Voltage signal -10 to 10 VDC
0 to 32767 Current signal 0 to 20 mA
This module is equipped with a configurable input filter. The minimum cycle time must be >500 μs. Filtering is
disabled for shorter cycle times.
If the input filter is active, then the scan rate for the channels is measured in ms. The time offset between the
channels is 200 μs. The conversion takes place asynchronously to the network cycle.
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 Reserved 0
Name:
ConfigOutput02
This register can be used to define the type and range of signal measurement.
Each channel is capable of handling either current or voltage signals. This differentiation is made using multiple
connection terminal points and an integrated switch in the module. The switch is automatically activated by the
module depending on the specified configuration. The following input signals can be set:
• ±10 V voltage signal (default)
• 0 to 20 mA current signal
• 4 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Voltage signal
1 Current signal, measurement range corresponding to bit 4
1 Channel 2 0 Voltage signal
1 Current signal, measurement range corresponding to bit 5
2-3 0
4 Channel 1: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
5 Channel 2: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
6-7 0
The input signal is monitored at the upper and lower limit values. These must be defined according to the operating
mode:
Limit value (default) Voltage signal ±10 V Current signal 0 to 20 mA Current signal 4 to 20 mA
Upper maximum limit value +10 V +32767 (0x7FFF) 20 mA +32767 (0x7FFF) 20 mA +32767 (0x7FFF)
Lower minimum limit value -10 V -32767 (0x8001) 0 mA 01) 4 mA 02)
Other limit values can be defined if necessary. Limit values are valid for all channels and activated automatically
by writing to the limit value registers. From this point on, the analog values will be monitored and limited according
to the new limits. The results of monitoring are displayed in the status register.
Examples of limit value settings
Application case Limit value settings
Current signal: 4 to 20 mA A negative limit value must be configured in order to measure values <4 mA with a current signal of 4 to
20 mA: 0 mA is equal to a value of -8192 (0xE000).
Mixed voltage and current signal The configured limit values are valid for all channels. Mixed operation (voltage and current signal) there-
fore requires a compromise.
The following configuration has proven effective:
Upper limit = +32767, lower limit = -32767
This makes it possible to also measure negative voltage values. A lower limit value of 0 would limit the
voltage value to 0.
Current signal on all channels All channels are configured for measuring current. The limit value setting in Automation Studio is not
adjusted automatically. That means that +32767 is configured as the upper limit value and -32767 as the
lower limit value. The necessary changes must be made by the user, e.g. lower limit value = 0
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
• The default value of -32768 corresponds to the minimum default value of -10 VDC.
• When configured as 0 to 20 mA, this value should be set to 0.
• When configured as 4 to 20 mA, this value can be set to -8192 (corresponds to 0 mA) in order
to display values <4 mA.
Information:
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value of 20 mA or +10 VDC.
Information:
Keep in mind that this setting applies to all channels!
Name:
StatusInput01
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
The following states are monitored depending on the settings:
Value Voltage signal ±10 V Current signal 0 to 20 mA Current signal 4 to 20 mA
0 No error No error No error
1 Lower limit value exceeded Default setting Lower limit value exceeded
The input value has a lower limit of 0x0000. Un-
derflow monitoring is therefore not necessary.
After lower limit value change
The input value is limited to the configured val-
ue. The status bit is set when the lower limit val-
ue is passed.
2 Upper limit value exceeded Upper limit value exceeded Upper limit value exceeded
3 Open line - -
Bit structure:
Bit Description Value Information
0-1 Channel 1 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
2-3 Channel 2 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
4-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Inputs without filtering 100 µs
Inputs with filtering 500 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Inputs without filtering 300 µs for all inputs
Inputs with filtering 1 ms
4.3.9 X20AI4222
The module is equipped with 4 inputs with 13-bit (including sign) digital converter resolution. It can be used to
capture voltage signals in the range from ±10 V.
• 4 analog inputs ±10 V
• 13-bit digital converter resolution
Product ID X20AI4222
Short description
I/O module 4 analog inputs ±10 V
General information
B&R ID code 0xCAB1
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W 1)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
GOST-R Yes
Analog inputs
Input ±10 V
Input type Differential input
Digital converter resolution ±12-bit
Conversion time 400 µs for all inputs
Output format
Data type INT
Voltage 0x8001 - 0x7FFF / 1 LSB = 0x0008 = 2.441 mV
Input impedance in signal range 20 MΩ
Input protection Protection against wiring with supply voltage
Permitted input signal Max. ±30 V
Output of the digital value during overload
Below lower limit 0x8001
Above upper limit 0x7FFF
Conversion procedure SAR
Input filter 3rd-order low pass / cutoff frequency 1 kHz
4.3.9.5 Pinout
r e
1 2
3 4
AI + 1 U AI + 2 U
AI - 1 U AI - 2 U
AI + 3 U AI + 4 U
AI - 3 U AI - 4 U
AI
+ +
+ +
AI + x U
LED (green)
1) The offset specifies the position of the register within the CAN object.
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Name:
AnalogInput01 to AnalogInput04
The analog input values are mapped to this register.
Data type Value Input signal:
INT -32,768 to 32,767 Voltage signal -10 to 10 VDC
This module is equipped with a configurable input filter. The minimum cycle time must be >500 μs. Filtering is
disabled for shorter cycle times.
If the input filter is active, then the scan rate for the channels is measured in ms. The time offset between the
channels is 200 μs. The conversion takes place asynchronously to the network cycle.
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
Adjustable filter levels:
Value Filter level
0 Filter switched off
1 Filter level 2
2 Filter level 4
3 Filter level 8
4 Filter level 16
5 Filter level 32
6 Filter level 64
7 Filter level 128
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
Example 2
A disturbance interferes with the input value. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 Reserved 0
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of -32768 corresponds to the minimum default value of -10 VDC.
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value at +10 VDC.
Keep in mind that this setting applies to all channels!
Name:
StatusInput01
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Channel 1 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
... ...
6-7 Channel 4 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Inputs without filtering 100 µs
Inputs with filtering 500 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Inputs without filtering 400 µs for all inputs
Inputs with filtering 1 ms
4.3.10 X20AI4322
The module is equipped with 4 inputs with 12-bit digital converter resolution. It is possible to select between the
two current ranges 0 to 20 mA and 4 to 20 mA.
• 4 analog inputs, 0 to 20 mA or 4 to 20 mA
• 12-bit digital converter resolution
Product ID X20AI4322
Short description
I/O module 4 analog inputs 0 to 20 mA / 4 to 20 mA
General information
B&R ID code 0xCAB3
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
GOST-R Yes
Analog inputs
Input 0 to 20 mA/4 to 20 mA
Input type Differential input
Digital converter resolution 12-bit
Conversion time 400 µs for all inputs
Output format
Data type INT
Current 0x0000 - 0x7FFF / 1 LSB = 0x0008 = 4.883 µA
Load <400 Ω
Input protection Protection against wiring with supply voltage
Permitted input signal Max. ±50 mA
Output of the digital value during overload
Below lower limit 0x0000
Above upper limit 0x7FFF
Conversion procedure SAR
Input filter 3rd-order low pass / cutoff frequency 1 kHz
4.3.10.5 Pinout
r e
1 2
3 4
AI + 1 I AI + 2 I
AI - 1 I AI - 2 I
AI + 3 I AI + 4 I
AI - 3 I AI - 4 I
AI
+ +
+ +
PTC
AI + x I
LED (green)
1) The offset specifies the position of the register within the CAN object.
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Name:
AnalogInput01 to AnalogInput04
The analog input values are mapped to this register.
Data type Value Input signal:
INT 0 to 32767 Current signal 0 to 20 mA or 4 to 20 mA
This module is equipped with a configurable input filter. The minimum cycle time must be >500 μs. Filtering is
disabled for shorter cycle times.
If the input filter is active, then the scan rate for the channels is measured in ms. The time offset between the
channels is 200 μs. The conversion takes place asynchronously to the network cycle.
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
Adjustable filter levels:
Value Filter level
0 Filter switched off
1 Filter level 2
2 Filter level 4
3 Filter level 8
4 Filter level 16
5 Filter level 32
6 Filter level 64
7 Filter level 128
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
Example 2
A disturbance interferes with the input value. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 Reserved 0
Name:
ConfigOutput02
This register can be used to set the range of the current signal. This is determined by how they are configured.
The following input signals can be set:
• 0 to 20 mA current signal
• 4 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Reserved 1
4 Channel 1: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
... ...
7 Channel 4: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
• When configured as 0 to 20 mA, this value should be set to 0.
• When configured as 4 to 20 mA, this value can be set to -8192 (corresponds to 0 mA) in order
to display values <4 mA.
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value at 20 mA.
Keep in mind that this setting applies to all channels!
Name:
StatusInput01
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Channel 1 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
... ...
6-7 Channel 4 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Inputs without filtering 100 µs
Inputs with filtering 500 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Inputs without filtering 400 µs for all inputs
Inputs with filtering 1 ms
4.3.11 X20AI4622
The module is equipped with 4 inputs with 13-bit (including sign) digital converter resolution. It is possible to select
between the current and voltage signal using different connection terminal points.
• 4 analog inputs
• Either current or voltage signal possible
• 13-bit digital converter resolution
Product ID X20AI4622
Short description
I/O module 4 analog inputs ±10 V or 0 to 20 mA / 4 to 20 mA
General information
B&R ID code 0x1BAA
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W 1)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Analog inputs
Input ±10 V or 0 to 20 mA / 4 to 20 mA, via different connection terminal points
Input type Differential input
Digital converter resolution
Voltage ±12-bit
Current 12-bit
Conversion time 400 µs for all inputs
Output format INT
Output format
Voltage INT 0x8001 - 0x7FFF / 1 LSB = 0x0008 = 2.441 mV
Current INT 0x0000 - 0x7FFF / 1 LSB = 0x0008 = 4.883 µA
Input impedance in signal range
Voltage 20 MΩ
Current -
Load
Voltage -
Current <400 Ω
Input protection Protection against wiring with supply voltage
Permitted input signal
Voltage Max. ±30 V
Current Max. ±50 mA
Output of the digital value during overload
Below lower limit
Voltage 0x8001
Current 0x0000
Above upper limit
Voltage 0x7FFF
Current 0x7FFF
Conversion procedure SAR
Input filter 3rd-order low pass / cutoff frequency 1 kHz
Max. error at 25°C
Voltage
Gain 0.08% 2)
Offset 0.015% 3)
Current
Gain 0 to 20 mA = 0.08% / 4 to 20 mA = 0.1% 2)
Offset 0 to 20 mA = 0.03% / 4 to 20 mA = 0.16% 4)
Max. gain drift
Voltage 0.006 %/°C 2)
Current 0 to 20 mA = 0.009 %/°C
4 to 20 mA = 0.0113 %/°C 2)
Max. offset drift
Voltage 0.002 %/°C 3)
Current 0 to 20 mA = 0.004 %/°C
4 to 20 mA = 0.005 %/°C 4)
Common-mode rejection
DC 70 dB
50 Hz 70 dB
Common-mode range ±12 V
4.3.11.5 Pinout
r e
X20 AI 4622
1 2
3 4
AI + 1 I AI + 2 I
AI + 1 U AI + 2 U
AI - 1 U/I AI - 2 U/I
AI + 3 I AI + 4 I
AI + 3 U AI + 4 U
AI - 3 U/I AI - 4 U/I
Voltage AI Current
measurement measurement
Current/Voltage switching
PTC
AI + x I
Shunt
AI + x U Input value
A/D
converter
I/O status
AI - x U/I
LED (green)
1) The offset specifies the position of the register within the CAN object.
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Name:
AnalogInput01 to AnalogInput04
The analog input value are mapped to this register depending on the configured operating mode.
Data type Value Input signal:
INT -32768 to 32767 Voltage signal -10 to 10 VDC
0 to 32767 Current signal 0 to 20 mA
This module is equipped with a configurable input filter. The minimum cycle time must be >500 μs. Filtering is
disabled for shorter cycle times.
If the input filter is active, then the scan rate for the channels is measured in ms. The time offset between the
channels is 200 μs. The conversion takes place asynchronously to the network cycle.
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 Reserved 0
Name:
ConfigOutput02
This register can be used to define the type and range of signal measurement.
Each channel is capable of handling either current or voltage signals. This differentiation is made using multiple
connection terminal points and an integrated switch in the module. The switch is automatically activated by the
module depending on the specified configuration. The following input signals can be set:
• ±10 V voltage signal (default)
• 0 to 20 mA current signal
• 4 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Voltage signal
1 Current signal, measurement range corresponding to bit 4
... ...
3 Channel 4 0 Voltage signal
1 Current signal, measurement range corresponding to bit 7
4 Channel 1: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
... ...
7 Channel 4: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
The input signal is monitored at the upper and lower limit values. These must be defined according to the operating
mode:
Limit value (default) Voltage signal ±10 V Current signal 0 to 20 mA Current signal 4 to 20 mA
Upper maximum limit value +10 V +32767 (0x7FFF) 20 mA +32767 (0x7FFF) 20 mA +32767 (0x7FFF)
Lower minimum limit value -10 V -32767 (0x8001) 0 mA 01) 4 mA 02)
Other limit values can be defined if necessary. Limit values are valid for all channels and activated automatically
by writing to the limit value registers. From this point on, the analog values will be monitored and limited according
to the new limits. The results of monitoring are displayed in the status register.
Examples of limit value settings
Application case Limit value settings
Current signal: 4 to 20 mA A negative limit value must be configured in order to measure values <4 mA with a current signal of 4 to
20 mA: 0 mA is equal to a value of -8192 (0xE000).
Mixed voltage and current signal The configured limit values are valid for all channels. Mixed operation (voltage and current signal) there-
fore requires a compromise.
The following configuration has proven effective:
Upper limit = +32767, lower limit = -32767
This makes it possible to also measure negative voltage values. A lower limit value of 0 would limit the
voltage value to 0.
Current signal on all channels All channels are configured for measuring current. The limit value setting in Automation Studio is not
adjusted automatically. That means that +32767 is configured as the upper limit value and -32767 as the
lower limit value. The necessary changes must be made by the user, e.g. lower limit value = 0
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
• The default value of -32768 corresponds to the minimum default value of -10 VDC.
• When configured as 0 to 20 mA, this value should be set to 0.
• When configured as 4 to 20 mA, this value can be set to -8192 (corresponds to 0 mA) in order
to display values <4 mA.
Information:
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value of 20 mA or +10 VDC.
Information:
Keep in mind that this setting applies to all channels!
Name:
StatusInput01
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
The following states are monitored depending on the settings:
Value Voltage signal ±10 V Current signal 0 to 20 mA Current signal 4 to 20 mA
0 No error No error No error
1 Lower limit value exceeded Default setting Lower limit value exceeded
The input value has a lower limit of 0x0000. Un-
derflow monitoring is therefore not necessary.
After lower limit value change
The input value is limited to the configured val-
ue. The status bit is set when the lower limit val-
ue is passed.
2 Upper limit value exceeded Upper limit value exceeded Upper limit value exceeded
3 Open line - -
Bit structure:
Bit Description Value Information
0-1 Channel 1 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
... ...
6-7 Channel 4 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Inputs without filtering 100 µs
Inputs with filtering 500 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Inputs without filtering 300 µs for all inputs
Inputs with filtering 1 ms
4.3.12 X20AI8221
The module is equipped with 8 inputs with 13-bit (including sign) digital converter resolution. It can be used to
capture voltage signals in the range from ±10 V.
• 8 analog inputs ±10 V
• 13-bit digital converter resolution
Product ID X20AI8221
Short description
I/O module 8 analog inputs ±10 V
General information
B&R ID code 0xD82F
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.04 W 1)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
GOST-R Yes
Analog inputs
Input ±10 V
Input type Differential input
Digital converter resolution ±12-bit
Conversion time 1 ms for all inputs
Output format
Data type INT
Voltage 0x8001 - 0x7FFF / 1 LSB = 0x0008 = 2.441 mV
Input impedance in signal range 20 MΩ
Input protection Protection against wiring with supply voltage
Open line detection Yes, using software
Reverse polarity protection Yes
Permitted input signal Max. ±30 V
Output of the digital value during overload
Below lower limit 0x8001
Above upper limit 0x7FFF
4.3.12.5 Pinout
S 1
2
3
4
5
6
7
8
AI + 1 U AI− 1 U
AI + 2 U AI− 2 U
AI + 3 U AI− 3 U
AI + 4 U AI− 4 U
AI + 5 U AI− 5 U
AI + 6 U AI− 6 U
AI + 7 U AI− 7 U
AI + 8 U AI− 8 U
AI
U1
U2
U3
U4
U5
U6
U7
U8
AI + x U
LED (green)
1) The offset specifies the position of the register within the CAN object.
Name:
AnalogInput01 to AnalogInput08
The analog input values are mapped to this register.
Data type Value Input signal:
INT -32,768 to 32,767 Voltage signal -10 to 10 VDC
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
Adjustable filter levels:
Value Filter level
0 Filter switched off
1 Filter level 2
2 Filter level 4
3 Filter level 8
4 Filter level 16
5 Filter level 32
6 Filter level 64
7 Filter level 128
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
Example 2
A disturbance interferes with the input value. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 - 15 Reserved 0
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of -32768 corresponds to the minimum default value of -10 VDC.
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value at +10 VDC.
Keep in mind that this setting applies to all channels!
Name:
StatusInput01 to StatusInput02
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
Data type Value
USINT See bit structure.
Bit structure:
StatusInput01 monitors Channels 1 to 4
StatusInput02 monitors Channels 5 to 8
Bit Description Value Information
0-1 Channel 1 or 5 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
... ...
6-7 Channel 4 or 8 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
11 Open line
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
1 ms
4.3.13 X20AI8321
The module is equipped with 8 inputs with 12-bit digital converter resolution. It is possible to select between the
two current ranges 0 to 20 mA and 4 to 20 mA.
• 8 analog inputs, 0 to 20 mA or 4 to 20 mA
• 12-bit digital converter resolution
Product ID X20AI8321
Short description
I/O module 8 analog inputs 0 to 20 mA / 4 to 20 mA
General information
B&R ID code 0xD831
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Inputs Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.24 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
GOST-R Yes
Analog inputs
Input 0 to 20 mA/4 to 20 mA
Input type Differential input
Digital converter resolution 12-bit
Conversion time 1 ms for all inputs
Output format
Data type INT
Current 0x0000 - 0x7FFF / 1 LSB = 0x0008 = 4.883 µA
Load <300 Ω
Input protection Protection against wiring with supply voltage
Reverse polarity protection Yes
Permitted input signal Max. ±50 mA
Output of the digital value during overload
Below lower limit 0x0000
Above upper limit 0x7FFF
Conversion procedure SAR
4.3.13.5 Pinout
S 1
2
3
4
5
6
7
8
AI + 1 I AI− 1 I
AI + 2 I AI− 2 I
AI + 3 I AI− 3 I
AI + 4 I AI− 4 I
AI + 5 I AI− 5 I
AI + 6 I AI− 6 I
AI + 7 I AI− 7 I
AI + 8 I AI− 8 I
AI
I1 I
I I2
I3 I
I I4
I5 I
I I6
I7 I
I I8
PTC
AI + x I
LED (green)
1) The offset specifies the position of the register within the CAN object.
Name:
AnalogInput01 to AnalogInput08
The analog input values are mapped to this register.
Data type Value Input signal:
INT 0 to 32767 Current signal 0 to 20 mA or 4 to 20 mA
Input ramp limitation can only take place when a filter is used; the input ramp is limited before filtering takes place.
The amount the input value changes is checked to make sure that specified limits are not exceeded. If the values
are exceeded, the adjusted input value is equal to the old value ± the limit value.
Configurable limit values:
Value Limit value
0 The input value is used without limitation.
1 0x3FFF = 16383
2 0x1FFF = 8191
3 0x0FFF = 4095
4 0x07FF = 2047
5 0x03FF = 1023
6 0x01FF = 511
7 0x00FF = 255
Input ramp limitation is well suited for suppressing disturbances (spikes). The following examples show the function
of the input ramp limitation based on an input jump and a disturbance.
Example 1
The input value jumps from 8,000 to 17,000. The diagram shows the adjusted input value with the following settings:
Input ramp limitation = 4 = 0x07FF = 2047
Filter level = 2
Input value
Internally adjusted input value before filtering
17000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
A filter can be defined to prevent large input jumps. This filter is used to bring the input value closer to the actual
analog value over a period of several bus cycles.
Filtering takes place after input ramp limitation.
Formula for calculating the input value:
Value Old Input value
Value New = Value Old - +
Filter level Filter level
Adjustable filter levels:
Value Filter level
0 Filter switched off
1 Filter level 2
2 Filter level 4
3 Filter level 8
4 Filter level 16
5 Filter level 32
6 Filter level 64
7 Filter level 128
The following examples show how filtering works in the event of an input jump or disturbance.
Example 1
The input value jumps from 8,000 to 16,000. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
8000
0
1 2 3 4 5 6 7 8 t [ms]
Input jump
Example 2
A disturbance interferes with the input value. The diagram shows the calculated value with the following settings:
Input ramp limitation = 0
Filter level = 2 or 4
Input value
Calculated value: Filter level 2
Calculated value: Filter level 4
16000
Disturbance (spike)
8000
0
1 2 3 4 5 6 7 8 t [ms]
Name:
ConfigOutput01
This register is used to define the filter level and input ramp limitation of the input filter.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Defines the filter level 000 Filter switched off
001 Filter level 2
010 Filter level 4
011 Filter level 8
100 Filter level 16
101 Filter level 32
110 Filter level 64
111 Filter level 128
3 Reserved 0
4-6 Defines the input ramp limitation 000 The input value is used without limitation
001 Limit value = 0x3FFF (16383)
010 Limit value = 0x1FFF (8191)
011 Limit value = 0x0FFF (4095)
100 Limit value = 0x07FF (2047)
101 Limit value = 0x03FF (1023)
110 Limit value = 0x01FF (511)
111 Limit value = 0x00FF (255)
7 - 15 Reserved 0
Name:
ConfigOutput02
This register can be used to set the range of the current signal. This is determined by how they are configured.
The following input signals can be set:
• 0 to 20 mA current signal
• 4 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
... ...
7 Channel 8: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
Name:
ConfigOutput03
This register can be used to configure the lower limit for analog values. If the analog value goes below the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
• When configured as 0 to 20 mA, this value should be set to 0.
• When configured as 4 to 20 mA, this value can be set to -8192 (corresponds to 0 mA) in order
to display values <4 mA.
Keep in mind that this setting applies to all channels!
Name:
ConfigOutput04
This register can be used to configure the upper limit for analog values. If the analog value goes above the limit
value, it is frozen at this value and the corresponding error status bit is set.
Data type Value
INT -32,768 to 32,767
Information:
The default value of 32767 corresponds to the maximum default value at 20 mA.
Keep in mind that this setting applies to all channels!
Name:
StatusInput01 to StatusInput02
This register is used to monitor the module inputs. A change in the monitoring status generates an error message.
Data type Value
USINT See bit structure.
Bit structure:
StatusInput01 monitors Channels 1 to 4
StatusInput02 monitors Channels 5 to 8
Bit Description Value Information
0-1 Channel 1 or 5 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
... ...
6-7 Channel 4 or 8 00 No error
01 Lower limit value exceeded
10 Upper limit value exceeded
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
1 ms
4.3.14 X20AP31x1
Power monitoring
These modules measure active, reactive and apparent power individually for each of the three phases and for
all of them collectively. The power consumption of each phase and the total sum is also recorded. In addition,
the modules provide the RMS values for voltage and current on the three phases. When measuring the current,
the value of the current through the neutral line can also be detected and monitored. Measurement of the mains
frequency and the phase angle of the three phases (current and voltage) complete the power measurement data.
Energy management
The integrated functions on the modules map the immediate power requirements of the machine in detail and also
record its total power consumption. For the user, all relevant data is prepared and made available in the process
image.
The ability to measure currents and voltages up to the 31st harmonic enables higher precision recording of RMS
values. This allows the modules to easily cope with irregular sine curves, and makes them well-suited to renewable
energy applications. In these types of applications, being able to accurately measure the frequency at a resolution
of 0.01 Hz between 45-65 Hz is a great advantage. In general, the modules are suitable for use with 1-phase, 2-
phase or 3-phase power mains.
Features
• Calculate RMS values from currents and voltages
• Calculate active, reactive and apparent power
• Calculate active, reactive and apparent energy
• Phasing detection
• Measure individual phases and calculate cumulative values
• Optionally measure current through the neutral line
• Calculate frequency and harmonics with high precision
4.3.14.5 Pinout
r e
X20 AP 3111
U1 I1
U2 I2
U3 I3
IN
U L1 I L1a
U L2 I L1b
U L3 I L2a
I Na I L2b
I Nb I L3a
UN I L3b
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Potential-free measurement of the AC current requires a current transformer. The current transformer is a trans-
ducer that delivers a secondary signal proportional to the primary current. This secondary signal is measured by the
module. The maximum directly configurable primary current is 65 A. Values higher than 65 A can also be measured
by implementing a transformation in the software application (see explanation and example provided below).
The maximum secondary signal depends on the module:
Module Secondary current/voltage
X20AP3111 20 mA
X20AP3121 1A
X20AP3131 5A
X20AP3161 333 mV
A smaller transformation ratio should be defined for measuring higher primary currents. The values calculated
by the module must be converted in the application according to the real rated transformation ratio that must be
defined.
Example: Currents of up to 100 A are flowing on the primary side. A current transformer with a rated
transformation ratio of 100/1 A is used. A rated transformation ratio of 50/1 A is defined in the
module to match the current transformer. If the primary current calculated by the module is 40 A,
then the actual value will be calculated as follows:
Caution!
To prevent damaging the module, you must ensure the current inputs are electrically isolated. This is
done by connecting one transformer for each current input that is being used.
The current inputs on the module are not electrically isolated, so the secondary circuit between the
transformer and the module must not be grounded. Grounding would distort the measurement and
show current values that are too low!
Any other devices connected to this secondary circuit must also be electrically isolated (also see
Figure 129 "Input circuit diagram of current inputs")!
Voltage transformers are not provided in the configuration by default (e.g. by setting the transformation ratio).
They can, however, be used to measure higher voltages than the nominal voltages specified in the technical data.
Similar to current value correction (see 4.3.14.6 "Current transformer") the rated transformation ratio between
primary and secondary voltage should be calculated and applied.
Information:
The same factor must be used for all voltage values, power ratings and energy values when making
the transformation.
AC voltage inputs
Protective impedance Anti-aliasing filter
Filter
UN
AC current inputs
AP3111, AP3121, AP3131: (Current measurement)
External Measurement shunts Anti-aliasing filter
current transformer I xa
(current output)
A/D Input value
transformer
I xb
UN
UN
General information
There are many different mains configurations around the world. This section will present a few typical connection
examples.
U L1
U L2
U L3
UN
I L1a
I L1b
I L2a
I L2b
I L3a
I L3b
I Na
optional
I Nb
L1 L2 L3 N
U L1
U L2
U L3
UN
I L1a
I L1b
I L2a
I L2b
I L3a
I L3b
I Na
I Nb
L1 L2 L3
U L1
U L2
U L3
UN
I L1a
I L1b
I L2a
I L2b
I L3a
I L3b
I Na
optional
I Nb
L1 L2 L3
U L1
U L2
U L3
UN
I L1a
I L1b
I L2a
I L2b
I L3a
I L3b
I Na
optional
I Nb
L1 L2 L3 N
U L1
U L2
U L3
UN
I L1a
I L1b
I L2a
I L2b
I L3a
I L3b
I Na
optional
I Nb
L1 L3 N
U L1
U L2
U L3
UN
I L1a
I L1b
I L2a
I L2b
I L3a
I L3b
I Na
I Nb
L1 L2 L3
Information:
The maximum voltage value specified in the data sheet must not be exceeded!
U L1
U L2
U L3
UN
I L1a
I L1b
I L2a
I L2b
I L3a
I L3b
I Na
optional
I Nb
L1 L2 L3 N
1) The offset specifies the position of the register within the CAN object.
The modules are used for power monitoring and for a machine's energy management. Examples of where this
would be used:
• Multi-phase energy measurement for class 0.5S or class 1 for
The modules provide the following possibilities for measured value preparation:
• IEC62052-11, IEC62053-22 and IEC62053-23, ANSI C12.1 and ANSI C12.20: Can be used for class 0.5S
or class 1 multi-phase wattmeter or class 2 multi-phase varmeter
• Precision of ±0.1% for real energy and ±0.02% for reactive energy over a range of 6000:1
• Temperature coefficient of internal reference of 6 ppm/°C
• Each phase can be calibrated for the active power
• Calibration not required for reactive power and apparent power
• Error ≤±0.5% for voltage, current, active-, reactive-, apparent power, frequency active power factor and
phase angle
• Energy registers for active, reactive and apparent energy, separated for forward and backward, fundamen-
tal waves and harmonics
• Threshold register for status signal generation and activation of power and energy measurement
• Determining the THD harmonic component
• Discrete Fourier Transformation (DFT) up to 31st harmonic component per phase for voltage and current
• Status signals for voltage dip, loss of voltage, phase sequence, energy flow, neutral current monitor, har-
monic component monitor
The values measured for RMS, power, active power factor, phase angle and frequency are mean values over
16 full waves, the update rate is ~3 Hz.
The following represents the measurement time over 16 full waves at the corresponding frequency:
50 Hz ... 320 ms
60 Hz ... 267 ms
Energy measurement
The power measurement (energy measurement) is based on the integration of the measured values with a sampling
rate of 1 MHz.
The collected energy values are made available as energy pulses with an adjustable resolution of 0.1 CF or 0.01 CF
values in the energy registers and with a resolution of 1 CF on the CF status flags.
The conversion can be defined using the PL constant. The default value 0x4A817C80 = 1.250.000.000 is equal
to 360 CF/kWh or 0.1 CF/kWs. Increasing the value causes the CF amount to decrease per energy unit (e.g.
0x53D1AC10 = 1.406.250.000 is equal to 320 CF/kWh). When choosing to display the values as kWh, a resolution
of 0.08789 CF/kWs is set internally and the register values are converted with a factor of 1/4096.
The energy threshold register (e.g. PStartTh) can be used to set the amount of energy needed to start an accu-
mulation or to reset the "no load" signals in the status registers. The length of the CF pulse can vary according
to the resulting output rate.
Automatic reading of the energy meter from the transformer must be enabled because valid values are only avail-
able after the transformer has been configured. It is possible to clear the energy register or to set it with a block
of the register written in the software application.
Tp = 80 ms
CFx
T ≥ 160 ms
Tp = 0.5 T
CFx
10 ms ≤ T < 160 ms
Tp = 5 ms
CFx
if T < 10 ms,
then T is set to 10 ms
Figure 137: The length of the CF pulse can vary according to the resulting output rate
Power measurement
The phase power ratings are calculated by the module and stored in the corresponding registers.
The total power ratings are equal to the sum of the phase power ratings. To prevent the number range from being
exceeded, the value in the registers is equal to a fourth of the actual power. This value must be multiplied by 4
by the application.
The vector-based total apparent power (complex total apparent power) is calculated according to IEEE1459.
Power factor
The phase power factor is calculated by dividing the phase active power by the phase apparent power.
The total power factor is calculated by dividing the total active power by the total apparent power.
Neutral current
The neutral current can be measured or calculated. Both values are available.
The user can configure which one to use for displaying the status.
Phase angle
Frequency
Frequency measurement is based on Phase A. If A fails, then Phase C is used. If both A and C fail, then Phase
B is used.
Temperature
The Chip-Junction temperature is measured approximately every 100 ms using the sensor integrated in the trans-
former.
THD+N - Sum of interference power of the harmonic (THD) + interference power of the noise (N)
The THD+N measurement is used to monitor the percentage of harmonics in the network.
If this percentage falls below 10%, then an accuracy of 0.01% can no longer be guaranteed.
This is calculated as follows: (SQR (RMStotal^2 - RMSfundamental wave^2)) / RMSfundamental wave
Fourier analysis
The harmonic component from the 2nd to the 31st harmonic is calculated for voltage and current and the THD
(Total Harmonic Distortion) of each phase.
The DFT period is 0.5 s. This corresponds to a resolution of 2 Hz. The input samples are recorded at a sampling
rate of 8 kHz and can be optionally multiplied with a "Hann window" before being evaluated. This is initiated when
requested by the application.
Mains frequency Sampling frequency
Frequency Percentage-based
Input Scaling
Digital components for components of
samples Post-
X X Fourier fundamental wave fundamental wave
from the processing
Transformation and and
DSP processor
harmonics harmonics
Interface to the
oversampling
buffer
Zero-crossing detection
Zero-crossing detection can be configured for each phase for cu or voltage and edge and forms the basis for
frequency and angle measurements and subsequently also for active and reactive power calculations.
U
TZX
ZX
positive zero crossing
TD
ZX
negative zero crossing
ZX
all zero crossings
Voltage
+Threshold
Time
-Threshold
IRQ
(if enabled)
Figure 140: Time diagram for detecting a voltage dip or power failure
Neutral current monitoring of the measured and the calculated value is done with separate threshold value registers
and status flags.
The configuration and calibration registers are each composed of blocks and employ a checksum feature to high-
light undesired changes. In order to apply this register to the transformer, the respective transfer register must be
changed after the data is transferred to the module (incrementing, bit toggling, etc.). The start value of the transfer
register is 0 after startup.
Due to the amount of potential cyclic input data and the limitation to 30 byte cyclic X2X data, the extended Flat
Stream interface, DPS = Data Point Stream, has been defined as the mechanism for transferring the process
variables. DPS is based on the Flat Streaming Interface (FSI) for serial interface modules. The FSI was expanded
to include the block number as the first byte of the user data frame and implements the termination of a frame
(data image of the channel) with a zero segment.
The data blocks are re-transferred if a read request is triggered after a transfer has been completed. A block number
can be sent via the DPS to set a different block or transfer the entire image (default: block number 0).
It should be possible to adapt the DPS interface to the available buffer size. However, the higher-level fieldbus
must be taken into account when doing so (e.g.: CAN 8 byte object, InputMTU size 7). The block number is added
to the front of the actual payload data as a means to differentiate the blocks.
#define ADC_BLK_ALL 0 // struct ADC_REG
#define ADC_BLK_STATUS 1 // long NetTimeReg + struct ADC_REG_STATUS
#define ADC_BLK_RMS 2 // struct ADC_REG_RMS
#define ADC_BLK_POWER 3 // struct ADC_REG_POWER
#define ADC_BLK_THD_ANGLE 4 // struct THD_ANGLE
#define ADC_BLK_ENERGY 5 // long NetTimeEnergy + struct ADC_REG_ENERGY
#define ADC_BLK_DFT 6 // long NetTimeDft + struct ADC_REG_DFT
#define ADC_BLK_CFGACT 7 // struct ADC_REG_CFGACT
#define ADC_BLK_ENVREG 8 // struct ENV_STATUS
Information:
• Consistency of the data is only provided for the individual variables because the data is trans-
ferred from the AD converter asynchronously to the conversion.
• Make sure that the byte sequence of the register is in accordance with the Little Endian model
(Intel format).
The NetTime timestamps are always updated after the blocks are generated when preparing a new alternating
buffer.
ADC_REG
ADC_REG_STATUS
ADC_REG_RMS
ADC_REG_POWER
ADC_REG_THD_ANGLE
ADC_REG_ENERGY
ADC_REG_DFT
// Environment Variables
Name:
PmeanT
The value in the register equals a fourth of the actual power. The calculation can be performed in either absolute
or arithmetic mode (see register "MeteringMode" <Bit 3>). Each phase can be separately enabled for the power
calculation (see register "MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT -32,767 to 32,767 Resolution 4 W
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total active power = Register value * 4
Name:
QmeanT
The value in the register equals a fourth of the actual power. The calculation can be performed in either absolute
or arithmetic mode (see register "MeteringMode" <Bit 4>). Each phase can be separately enabled for the power
calculation (see register "MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT -32,767 to 32,767 Resolution 4 var
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total reactive power = Register value * 4
Name:
SmeanT
The value in the register equals a fourth of the actual power. The power is calculated in arithmetic mode. Each
phase can be separately enabled for the power calculation (see register "MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT 0 to 32767 Resolution 4 VA
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total apparent power = Register value * 4
Name:
AEnergyT
Total active energy in forward and backward direction.
Data type Value
DINT -2,147,483,647 to 2,147,483,647 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Name:
REnergyT
Total reactive energy in forward and backward direction.
Data type Value Information
DINT -2,147,483,647 to 2,147,483,647 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Name:
StatusInput
The signals are recorded in 200 µs intervals.
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 CF1 energy pulse 1, total active energy 0 Not yet calculated
1 Calculated
1 CF2 energy pulse 2, total apparent energy, configurable 0 Not yet calculated
Standard: 1 Calculated
Arithmetic sum of apparent energy, can be reconfigured via reg-
ister <MeteringMode>
2 CF3 energy pulse 3, total active energy, fundamental wave 0 Not yet calculated
1 Calculated
3 CF4 energy pulse 4, total active energy, harmonics 0 Not yet calculated
1 Calculated
4 ZX1 zero cross signal – Phase A 0 Zero cross-over not detected
1 Standard:
Pulse at positive edge of the zero cross signal of the voltage
input, can be reconfigured via register "ZXConfig"
5 ZX2 zero cross signal – Phase B 0 Zero cross-over not detected
1 Standard:
Pulse at positive edge of the zero cross signal of the voltage
input, can be reconfigured via register "ZXConfig"
6 ZX3 zero cross signal – Phase C 0 Zero cross-over not detected
1 Standard:
Pulse at positive edge of the zero cross signal of the voltage
input, can be reconfigured via register "ZXConfig"
7 Reserved 0
8 DFT response sent x If the state in the register "ControlOutput" corresponds with the
response, then the action is complete
9 Energy value update response sent 0 No update
1 Update complete
10 Energy value response deleted x If the state in the register "ControlOutput" corresponds with the
response, then the action is complete
11 Energy value response set x If the state in the register "ControlOutput" corresponds with the
response, then the action is complete
12 - 15 Reserved 0
Name:
ControlOutput
Control signals are evaluated in a ~5 ms interval.
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 DFT analysis 0 Don't start
1 Start1)
1 Automatically read energy values 0 Do not automatically read
1 Automatically read
2 Clear energy values 0 Don't delete
1 Delete1)
3 Set energy values 0 Don't start
1 Start1)
4 - 15 Reserved 0
1) If the state in the register "ControlOutput" corresponds with the response, then the action is complete.
Name:
SampleTime01_32bit
Network timestamp for the readout of the status, RMS, power register.
Data type Value Information
DINT -2,147,483,647 to 2,147,483,647 Network time
Name:
SysStatus1
The register is read by the converter in a ~5 ms interval.
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0-1 Reserved 0
2 SumStatusPhaseLoss, voltage of one or more phases < failure 0 Voltage within permitted range
threshold in the register 1 Voltage lower than the failure threshold
3 SumStatusPhaseWarning, voltage of one or more phases < 0 Voltage within permitted range
warning threshold in the register 1 Voltage lower than the warning threshold
4-5 Reserved 0
6 ErrOrderPhasecurrent, error in the order of phase currents 0 No error
1 Error
7 ErrOrderPhaseVoltage, error in the order of phase voltages 0 No error
1 Error
8 CS3Err, checksum error in configuration block 3 0 No error
1 Error
9 Reserved 0
10 CS2Err, checksum error in configuration block 2 0 No error
1 Error
11 Reserved 0
12 CS1Err, checksum error in configuration block 1 0 No error
1 Error
13 Reserved 0
14 CS0Err, checksum error in configuration block 0 0 No error
1 Error
15 Reserved 0
Name:
SysStatus2
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 RevPchgC, the direction of the active energy for phase C has 0 No change of direction
changed 1 Direction has changed
1 RevPchgB, the direction of the active energy for phase B has 0 No change of direction
changed 1 Direction has changed
2 RevPchgA, the direction of the active energy for phase A has 0 No change of direction
changed 1 Direction has changed
3 RevPchgT, the direction of the active energy for the total has 0 No change of direction
changed 1 Direction has changed
4 RevQchgC, the direction of the reactive energy for phase C has 0 No change of direction
changed 1 Direction has changed
5 RevQchgB, the direction of the reactive energy for phase B has 0 No change of direction
changed 1 Direction has changed
6 RevQchgA, the direction of the reactive energy for phase A has 0 No change of direction
changed 1 Direction has changed
7 RevQchgT, the direction of the reactive energy for the total has 0 No change of direction
changed 1 Direction has changed
8 Reserved 0
9 DFTDone, DFT analysis complete (temporary bit) 0 DFT analysis not complete
1 DFT analysis complete
10 SumStatusWarningTHDCurrent, the THDIx value of one or more 0 THDIx value within permitted range
phases > warning threshold in the register 1 THDIx value higher than warning threshold
11 SumStatusWarningTHDVoltage, the THDUx value of one or 0 THDUx value within permitted range
more phases > warning threshold in the register 1 THDUx value higher than warning threshold
12 - 13 Reserved 0
14 ErrIrmsNCalc, the calculated value of the neutral line > warning 0 Calculated value within permitted range
threshold in the Register 1 Calculated value higher than warning threshold
15 ErrIrmsNMeas, the measured value of the neutral line > warning 0 Measured value within permitted range
threshold in the Register 1 Measured value higher than warning threshold
Name:
SysStatus3
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 CF1RevFlag, direction of CF signal 0 Forward1)
1 Back2)
1 CF2RevFlag, direction of CF signal 0 Forward1)
1 Back2)
2 CF3RevFlag, direction of CF signal 0 Forward1)
1 Back2)
3 CF4RevFlag, direction of CF signal 0 Forward1)
1 Back2)
4 - 11 Reserved 0
12 TVSNoload, vector-based total apparent power of all phases in 0 Status with load
"No load" state 1 Status without load
13 TASNoload, total apparent power of all phases in "No load" state 0 Status with load
1 Status without load
14 TPNoload, total active power of all phases in "No load" state 0 Status with load
1 Status without load
15 TQNoload, total reactive power of all phases in "No load" state 0 Status with load
1 Status without load
Name:
SysStatus4
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 LossPhaseC, voltage lower than value in the register 0 Voltage is higher
"PhaseLoseTh" 1 Voltage is lower
1 LossPhaseB, voltage lower than value in the register 0 Voltage is higher
"PhaseLoseTh" 1 Voltage is lower
2 LossPhaseA, voltage lower than value in the register 0 Voltage is higher
"PhaseLoseTh" 1 Voltage is lower
3 Reserved 0
4 WarningPhaseC, voltage lower than value in the register 0 Voltage is higher
"SagTh" 1 Voltage is lower
5 WarningPhaseB, voltage lower than value in the register 0 Voltage is higher
"SagTh" 1 Voltage is lower
6 WarningPhaseA, voltage lower than value in the register 0 Voltage is higher
"SagTh" 1 Voltage is lower
7 - 15 Reserved 0
Name:
SystemStatusSel01
The most important bits of the "SysStatus1" register are stored in this register.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0-1 Reserved 0
2 SumStatusPhaseLoss, voltage of one or more phases < failure 0 Voltage within permitted range
threshold in the register 1 Voltage lower than the failure threshold
3 SumStatusPhaseWarning, voltage of one or more phases < 0 Voltage within permitted range
warning threshold in the register 1 Voltage lower than the warning threshold
4-5 Reserved 0
6 ErrOrderPhasecurrent, error in the order of phase currents 0 No error
1 Error
7 ErrOrderPhaseVoltage, error in the order of phase voltages 0 No error
1 Error
Name:
SystemStatusSel02
The most important bits of the "SysStatus2" register are stored in this register.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0-1 Reserved 0
2 SumStatusWarningTHDCurrent, the THDIx value of one or more 0 THDIx value within permitted range
phases > warning threshold in the register 1 THDIx value higher than warning threshold
3 SumStatusWarningTHDVoltage, the THDUx value of one or 0 THDUx value within permitted range
more phases > warning threshold in the register 1 THDUx value higher than warning threshold
4-5 Reserved 0
6 ErrIrmsNCalc, the calculated value of the neutral line > warning 0 Calculated value within permitted range
threshold in the Register 1 Calculated value higher than warning threshold
7 ErrIrmsNMeas, the measured value of the neutral line > warning 0 Measured value within permitted range
threshold in the Register 1 Measured value higher than warning threshold
Name:
PhaseStatus
This register corresponds to the SysStatus4 register. It contains the status of phases A, B und C.
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 LossPhaseC, voltage lower than value in the register 0 Voltage is higher
"PhaseLoseTh" 1 Voltage is lower
1 LossPhaseB, voltage lower than value in the register 0 Voltage is higher
"PhaseLoseTh" 1 Voltage is lower
2 LossPhaseA, voltage lower than value in the register 0 Voltage is higher
"PhaseLoseTh" 1 Voltage is lower
3 Reserved 0
4 WarningPhaseC, voltage lower than value in the register 0 Voltage is higher
"SagTh" 1 Voltage is lower
5 WarningPhaseB, voltage lower than value in the register 0 Voltage is higher
"SagTh" 1 Voltage is lower
6 WarningPhaseA, voltage lower than value in the register 0 Voltage is higher
"SagTh" 1 Voltage is lower
7 - 15 Reserved 0
Name:
IrmsN
Measured value of the neutral current between the P and N connections on the current terminal, multiplied with
the transfer factor of the transformer.
Data type Value Information
UINT 0 to 65,535 Measured value 0.001 Arms
Name:
UrmsA
UrmsB
UrmsC
Measured value for N-terminal or virtual zero point.
Data type Value Information
UINT 0 to 65,535 Measured value 0.01 Vrms
Name:
IrmsNcalc
Calculated value of neutral current derived from the other 3 phases.
Data type Value Information
UINT 0 to 65,535 Measured value 0.001 Arms
Name:
IrmsA
IrmsB
IrmsC
Measured value of the phase current between the P and N connections on the current terminal, multiplied with
the transfer factor of the transformer.
Data type Value Information
UINT 0 to 65,535 Measured value 0.001 Arms
Name:
THDNUA
THDNUB
THDNUC
Data type Value Information
UINT 0 to 10000 Resolution 0.01%
Name:
THDNIA
THDNIB
THDNIC
Data type Value Information
UINT 0 to 10000 Resolution 0.01%
Name:
Freq
Measured fundamental frequency of phases A, B and C.
Data type Value Information
UINT 0 to 10000 Resolution 0.01 Hz
Name:
PAngleA
PAngleB
PAngleC
Middle phase angle (power angle) of the current to the voltage based on the zero-crossing detection.
Data type Value Information
INT -1800 to 1800 Resolution 0.1°
Name:
Temperature
This register contains the internal temperature of the transformer component. The temperature is recorded in a
100 ms interval.
Data type Value Information
INT -200 to 200 Resolution 1°C
Name:
UAngleA
UAngleB
UAngleC
The value for phase A is always 0. On the other phases, the angle corresponds with the offset to A. This is based
on the zero-crossing detection.
Data type Value Information
INT -1800 to 1800 Resolution 0.1°
Name:
SVmeanTLSB
The value in the register equals a fourth of the actual power.
Data type Value Information
INT -32,767 to 32,767 Resolution of units/LSB equals 4/65536 VA
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual vector sum of the total apparent power LSW = register value * 4 (complex sum)
Name:
SVmeanT
The value in the register equals a fourth of the actual power. The calculation is made in accordance with IEEE 1459.
Data type Value Information
INT 0 to 32767 Resolution 4 VA
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual vector sum of the total apparent power MSW = register value * 4 (complex sum)
Name:
PmeanT
The value in the register equals a fourth of the actual power. The calculation can be performed in either absolute
or arithmetic mode (see register "MeteringMode" <Bit 3>). Each phase can be separately enabled for the power
calculation (see register "MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT -32,767 to 32,767 Resolution 4 W
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total active power = Register value * 4
Name:
PmeanA
PmeanB
PmeanC
Active power on the phase. Each phase can be separately enabled for the power calculation (see register "Meter-
ingMode" <Bits 0, 1 and 2>).
Data type Value Information
INT -32,767 to 32,767 Resolution 1 W
Name:
QmeanT
The value in the register equals a fourth of the actual power. The calculation can be performed in either absolute
or arithmetic mode (see register "MeteringMode" <Bit 4>). Each phase can be separately enabled for the power
calculation (see register "MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT -32,767 to 32,767 Resolution 4 var
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total reactive power = Register value * 4
Name:
QmeanA
QmeanB
QmeanC
Reactive power on the phase. Each phase can be separately enabled for the power calculation (see register
"MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT -32,767 to 32,767 Resolution 1 var
Name:
SmeanT
The value in the register equals a fourth of the actual power. The power is calculated in arithmetic mode. Each
phase can be separately enabled for the power calculation (see register "MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT 0 to 32767 Resolution 4 VA
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total apparent power = Register value * 4
Name:
SmeanA
SmeanB
SmeanC
Apparent power on the phase. Each phase can be separately enabled for the power calculation (see register
"MeteringMode" <Bits 0, 1 and 2>).
Data type Value Information
INT 0 to 32767 Resolution 1 VA
Name:
PFmeanT
Data type Value Information
INT -1000 to 1000 Resolution 0.001
Name:
PFmeanA
PFmeanB
PFmeanC
Data type Value Information
INT -1000 to 1000 Resolution 0.001
Name:
PmeanTF
The value in the register equals a fourth of the actual power.
Data type Value Information
INT -32,767 to 32,767 Resolution 4 W
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total active power of fundamental wave = Register value * 4
Name:
PmeanAF
PmeanBF
PmeanCF
Active power of fundamental wave on the phase.
Data type Value Information
INT -32,767 to 32,767 Resolution 1 W
Name:
PmeanTH
The value in the register equals a fourth of the actual power.
Data type Value Information
INT -32,767 to 32,767 Resolution 4 W
This value must be multiplied by 4 by the application. Calculation formula for actual power:
Actual total active power of harmonics = Register value * 4
Name:
PmeanAH
PmeanBH
PmeanCH
Active power of harmonics on the phase.
Data type Value Information
INT -32,767 to 32,767 Resolution 1 W
Name:
SampleTime02_32bit
Network timestamp for the readout of the energy register.
Data type Value Information
DINT -2,147,483,647 to 2,147,483,647 Network time
Name:
APenergyT
Total active energy in forward direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
APenergyA
APenergyB
APenergyC
Active energy in forward direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
ANenergyT
Total active energy in reverse direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
ANenergyA
ANenergyB
ANenergyC
Active energy in reverse direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
RPenergyT
Total reactive energy in forward direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
RPenergyA
RPenergyB
RPenergyC
Reactive energy in forward direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
RNenergyT
Total reactive energy in reverse direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
RNenergyA
RNenergyB
RNenergyC
Reactive energy in reverse direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
SAenergyT
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
SenergyA
SenergyB
SenergyC
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
SVenergyT
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
APenergyTF
Fundamental wave of total active energy in forward direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
APenergyAF
APenergyBF
APenergyCF
Fundamental wave of active energy in forward direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
ANenergyTF
Fundamental wave of total active energy in reverse direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
ANenergyAF
ANenergyBF
ANenergyCF
Fundamental wave of active energy in reverse direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
APenergyTH
Harmonics of total active energy in forward direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
APenergyAH
APenergyBH
APenergyCH
Harmonics of active energy in forward direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
ANenergyTH
Harmonics of total active energy in reverse direction.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
ANenergyAH
ANenergyBH
ANenergyCH
Harmonics of active energy in reverse direction of the phase.
Data type Value Information
UDINT 0 to 4,294,967,295 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Comments:
• The unit CF is derived from the Power Line factor (default: 3600 Imp/kWh), see register "MeteringMode"
• The resolution can be switched between 0.1 and 0.01, see register "MeteringMode"
• The register is updated automatically after being enabled, see register "ControlOutput" <Bit 1>
• The register is cleared upon request, see register "ControlOutput"
• The register is set upon request, see register "ControlOutput" <Bit 3>
Name:
AEnergyT
Total active energy in forward and backward direction.
Data type Value Information
DINT -2,147,483,647 to 2,147,483,647 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Name:
REnergyT
Total reactive energy in forward and backward direction.
Data type Value Information
DINT -2,147,483,647 to 2,147,483,647 Resolution 0.1 or 0.01 CF, depending on the Power Line factor (e.g. kWs)
Name:
SampleTime03_32bit
Network timestamp for the readout of the DFT register.
Data type Value Information
DINT -2,147,483,647 to 2,147,483,647 Network time
Name:
AI_HRN (2..32)
BI_HRN (2..32)
CI_HRN (2..32)
Ratio of harmonics.
Data type Value Information
UINT 0 to 32767 Ratio of frequency component
Name:
DFT_AI_THD
DFT_BI_THD
DFT_CI_THD
Ratio of total harmonic distortion.
Data type Value Information
UINT 0 to 32767 Total harmonic distortion on phase A current
Name:
DftAI_Fund
DftBI_Fund
DftCI_Fund
Data type Value Information
UINT 0 to 32767 Fundamental wave current
Name:
DftAV_Fund
DftBV_Fund
DftCV_Fund
Data type Value Information
UINT 0 to 32767 Fundamental value voltage
Name:
ChanControl
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 Channel status LED for phase A 0 Disabled
1 Enabled1)
1 Channel status LED for phase B 0 Disabled
1 Enabled1)
2 Channel status LED for phase C 0 Disabled
1 Enabled1)
3 Reserved 0
4 Neutral current monitor and status LED 0 Disabled
1 Enabled1)
5 Neutral current status derived from the calculated or measured 0 Derived from the calculated value1)
value 1 Derived from the calculated value
6 Conversion of energy register to kWh (internal register / 4096) 0 Disabled
1 Enabled
7 Display current values despite power failure2) 0 Disabled3), Current values = 0
1 Enabled
8 - 15 Oversampling with prescaler 0 Disabled1), Current values = 0
1 - 255 Enabled, Display current values despite power failure
Name:
IDispTh
Data type Value Information
UINT 100 to 65000 I RMS indicator threshold
The indicator threshold defines the RMS value of the current at which the status LED for the phase current is
illuminated. The default values vary from module to module and should be adjusted to the maximum primary
current. Suggestion: 1% of maximum value
Module Indicator threshold
X20AP3111 200 mA
X20AP3121 500 mA
X20AP3131 500 mA
X20AP3161 500 mA
Name:
I_RatioA
I_RatioB
I_RatioC
I_RatioN
Data type Value Information
UINT 10 to x Current transformer rating
In the modules AP311, 21 and 31, the rated current is multiplied by the rated transformation ratio. In the module
AP3161, the maximum primary current of the transformer is configured directly.
The permissible values differ from module to module (resolution 0.1):
Module Rating
X20AP3111 Transformer ratio: 10 to 32,500 (default: 25000)
X20AP3121 Transformer ratio: 10 to 650 (default: 500)
X20AP3131 Transformer ratio: 10 to 130 (default: 100)
X20AP3161 Measurement range: 50 to 650 (default: 500)
Information:
The maximum resulting current must not exceed the value of 65000 mA.
Name:
CfgUpdate
The registers in the group CfgReg are only updated after the CfgUpdate register is changed. Setting 0xFFFF only
causes this register to be reset without updating the CfgReg register.
Data type Value Information
UINT 0 to 65,535 Update request
Name:
Cs0Update
Cs1Update
Cs3Update
The registers in the group CsxReg are only updated after the CsxUpdate register is changed. Setting 0xFFFF only
causes this register to be reset without updating the CsxReg register.
Data type Value Information
UINT 0 to 65,535 Update request
Name:
Cs1UpdateFB
Cs3UpdateFB
The ADC configuration registers are only transferred to the feedback buffer after transfer to the ADC is complete.
Data type Value Information
UINT 0 to 65,535
Name:
ZXConfig
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 Zero cross signals 0 Enabled
1 Disabled
1-2 ZX20Con: Trigger zero cross-over 00 Positive zero cross-over1)
01 Negative zero cross-over
10 Both zero cross-overs
11 No zero cross-over
3-4 ZX1Con: Trigger zero cross-over 00 Positive zero cross-over1)
01 Negative zero cross-over
10 Both zero cross-overs
11 No zero cross-over
5-6 ZX2Con: Trigger zero cross-over 00 Positive zero cross-over1)
01 Negative zero cross-over
10 Both zero cross-overs
11 No zero cross-over
7-9 ZX0Src: Signal source for ZX0 hardware signal 000 A voltage1)
001 B voltage
010 C voltage
011 Fix 0
100 Current A
101 Current B
110 Current C
111 Fix 0
10 - 12 ZX1Src: Signal source for ZX1 hardware signal 000 A voltage
001 B voltage1)
010 C voltage
011 Fix 0
100 Current A
101 Current B
110 Current C
111 Fix 0
13 - 15 ZX2Src: Signal source for ZX2 hardware signal 000 A voltage
001 B voltage
010 C voltage1)
011 Fix 0
100 Current A
101 Current B
110 Current C
111 Fix 0
Name:
SagTh
Data type Value Information
UINT 5000 to 50000 Resolution 0.01 V
This register defines an RMS voltage value for monitoring the voltage warning signal.
Name:
PhaseLoseTh
Data type Value Information
UINT 1000 to 6000 Resolution 0.01 V
This register defines an RMS voltage value for monitoring the power failure signal.
Name:
INWarnTh0
Current value for monitoring the calculated neutral line current.
Data type Value Information
UINT 0 to 65000 Resolution 0.001 A
Name:
INWarnTh1
Current value for monitoring the measured neutral line current.
Data type Value Information
UINT 0 to 65000 Resolution 0.001 A
Name:
THDNUTh
Percentage value defining warning threshold for THD ratio.
Data type Value Information
UINT 0 to 10000 Resolution 0.01%
Name:
THDNITh
Percentage value defining warning threshold for THD ratio.
Data type Value Information
UINT 0 to 10000 Resolution 0.01%
Name:
PLconstH
Data type Value
UINT 0 to 65,535
Basis value of power line constant = 0x4A817C80 = 1,250,000,000 corresponding to 360 CF pulses per kWh
or 0.1 CF pulse per kWs. The result of setting the resolution in the energy registers to a decimal (see register
"MeteringMode" <Bit 9>) is 1 kWs per digit. Power line constant / 10 results in a 10x resolution.
Name:
PLconstL
Data type Value
UINT 0 to 65,535
Basis value of power line constant = 0x4A817C80 = 1,250,000,000 corresponding to 360 CF pulses per kWh
or 0.1 CF pulse per kWs. The result of setting the resolution in the energy registers to a decimal (see register
"MeteringMode" <Bit 9>) is 1 kWs per digit. Power line constant / 10 results in a 10x resolution.
Name:
MeteringMode
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0 Enables phase C for adding the power and energy values to- 0 Not enabled
gether 1 Approved1)
1 Enables phase B for adding the power and energy values to- 0 Not enabled
gether 1 Approved1)
2 Enables phase A for adding the power and energy values to- 0 Not enabled
gether 1 Approved1)
3 Calculation method for adding active power and active energy 0 Arithmetic sum1)
1 Absolute sum
4 Calculation method for adding reactive power and reactive en- 0 Arithmetic sum1)
ergy 1 Absolute sum
5 Reserved 0
6 Selects apparent energy for CF2 source 0 Arithmetic sum1)
1 Vector sum
7 CF2 source 0 Apparent energy
1 Reactive energy1)
8 Measuring configuration 0 3P4W1)
1 3P3W
9 Resolution of energy register 0 0.1 CF1)
1 0.01 CF
10 Integrator for didt current transformer 0 Disabled
1 Enabled
11 High-pass filter 0 Enabled
1 Disabled
12 Basis frequency 0 50 Hz1)
1 60 Hz
13 Phase assignment 0 I1 to Phase A and I3 to Phase C1)
1 I1 to Phase C and I3 to Phase A
14 - 15 Reserved 0
The values in the registers specified below must be read at the beginning of the calibration. This is the only way
to ensure that the gain and offset will be calculated correctly.
The values contained in the registers correspond to the valueold in the calculation formulas for gain and offset (see
4.3.14.10.17 "ADC RMS comparison checksum 3").
Name:
UGainA_R
UGainB_R
UGainC_R
Data type Value
UINT 0 to 65,535
Name:
IGainA_R
IGainB_R
IGainC_R
IGainN_R
Data type Value
UINT 0 to 65,535
Name:
UoffsetA_R
UoffsetB_R
UoffsetC_R
Data type Value
INT -32,767 to 32,767
Name:
IoffsetA_R
IoffsetB_R
IoffsetC_R
IoffsetN_R
Data type Value
INT -32,767 to 32,767
Name:
UGainA_W
UGainB_W
UGainC_W
Data type Value Information
UINT 0 to 65,535 Voltage RMS gain, phase-based
Name:
IGainA_W
IGainB_W
IGainC_W
IGainN_W
Data type Value Information
UINT 0 to 65,535 Current RMS gain, phase-based
Name:
UoffsetA_W
UoffsetB_W
UoffsetC_W
Corresponds to the negated value of the corresponding RMS register when U = 0.
Data type Value Information
INT -32,767 to 32,767 RMS voltage offset, phase-based
Name:
IoffsetA_W
IoffsetB_W
IoffsetC_W
IoffsetN_W
Corresponds to the negated value of the corresponding RMS register when I = 0.
Data type Value Information
INT -32,767 to 32,767 RMS current offset, phase-based
Use the following procedure to properly calculate the power angle correction:
1 Calculate the values
2 Write the value 0xFFFF to register Cs1Update
3 Read register Cs1UpdateFB until 0xFFFF is returned
4 Write the calculated values to the registers PhiA_W, PhiB_W, PhiC_W
5 Write the value 0x0001 to register Cs1Update
6 Read register Cs1UpdateFB until 0x0001 is returned
Information:
These registers are NOT nonvolatile, and the process needs to be repeated after every PowerOn and
every positive edge of the ModuleOK bit.
Name:
PhiA_R
PhiB_R
PhiC_R
These registers can be used to read out the configured values at runtime, but are not nonvolatile and have the
value 0 after the system is started.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0-9 Delay time for energy phase angle correction x The clock base is 2.048 MHz. Maximum 0.499 mSec.
10 - 14 Reserved 0
15 Delay times 0 Effect on current channel
1 Effect on voltage channel
Name:
PhiA_W
PhiB_W
PhiC_W
These registers can be used to correct phase shifts at runtime. This can be necessary if the transformers used
distort the phase shift.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0-9 Delay time for energy phase angle correction 0 to 1023 See descriptions for Bits 0 to 9
10 - 14 Reserved 0
15 Delay times 0 or 1 See description for Bit 15
Description - Bits 0 to 9
The maximum correction 0x3FF = 1023 dec. corresponds to 0.49951 ms.
At 50 Hz mains this corresponds to a change of 8.99 degrees
At 60 Hz mains this corresponds to a change of 10.79 degrees
Schematic representation of inductive load: Voltage ahead of current Schematic representation of capacitive load: Current ahead of voltage
Voltage Voltage
Current Current
Desription - Bit 15
0 Delay affects current channel
Effect with inductive load Reduced angle between I and U, and therefore an increased power factor
Effect with capacitive load Increased angle between U and I, and therefore an reduced power factor
1 Delay affects voltage channel
Effect with inductive load Reduced angle between U and I, and therefore an increased power factor
Effect with capacitive load Increased angle between I and U, and therefore an reduced power factor
4.3.14.10.19.1 Introduction
B&R offers an additional communication method for some modules. "FlatStream" was designed for X2X and
POWERLINK networks and allows data transmission to be adapted to individual demands. Although this method
is not 100% real-time capable, it still allows data transmission to be handled more efficiently than with standard
cyclic polling.
Field device
X2X language
Cyclic call
via I/O mapping
B&R CPU
Cyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
Acyclic call
via
library functions
B&R CPU
Acyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
FlatStream
The physical properties of the bus system limit the amount of data that can be transmitted during one bus cycle.
With FlatStream communication, all messages are viewed as part of a continuous data stream. Long data streams
must be broken down into several fragments that are sent one after the other. To understand how the receiver puts
these fragments back together to get the original information, it is important to understand the difference between
a message, a segment, a sequence and an MTU.
Message
A message refers to information exchanged between two partner stations. The length of a message is not restricted
by the FlatStream communication method. Nevertheless, module-specific limitations must be considered.
Segment (logical division of a message):
A segment has a finite size and can be understood as a section of a message. The number of segments per
message is arbitrary. So that the recipient can correctly reassemble the transmitted segments, each segment
is preceded by a byte with additional information. This control byte contains information such as the length of a
segment and whether the approaching segment completes the message. This makes it possible for the receiving
station to interpret the incoming data stream correctly.
Sequence (how a segment needs to be arranged physically):
The maximum size of a sequence corresponds to the number of enabled Rx or Tx bytes (later: "MTU"). The
transmitting station splits the transmit array into valid sequences. These sequences are then written successively
to the MTU and transmitted to the receiving station where they are put back together again. The receiver stores
the incoming sequences in a receive array, obtaining an image of the data stream in the process.
With FlatStream communication, the number of sequences sent are counted. Successfully transmitted sequences
must be acknowledged by the receiving station to ensure the integrity of the transmission.
MTU (Maximum Transmission Unit) – Physical transport:
MTU refers to the enabled USINT registers used with FlatStream. These registers can accept at least one se-
quence and pass it on to the receiving station. A separate MTU is defined for each direction of communication.
The OutputMTU defines the number of FlatStream Tx bytes, and the InputMTU specifies the number of FlatStream
Rx bytes. The MTUs are transported cyclically via the X2X Link, increasing the load with each additional enabled
USINT register.
Features
FlatStream messages are not transmitted cyclically or in 100% real time. Many bus cycles may be needed to trans-
mit a particular message. Although the Rx and Tx registers are exchanged between the transmitter and the receiv-
er cyclically, they are only processed further if explicitly accepted by the "InputSequence" or "OutputSequence"
register.
Behavior in the event of an error (brief summary)
The protocol for X2X and POWERLINK networks specifies that the last valid values should be retained when
disturbances occur. With conventional communication (cyclic/acyclic data queries), this type of error can generally
be ignored.
In order for communication to also take place without errors using FlatStream, all of the sequences issued by the
receiver must be acknowledged. If Forward functionality is not used, then subsequent communication is delayed
for the length of the disturbance.
If Forward functionality is being used, the receiving station receives a transmission counter that is incremented
twice. The receiver stops, i.e. it no longer returns any acknowledgments. The transmitting station uses the Se-
quenceAck to determine that the transmission was faulty and that all affected sequences will have to be repeated.
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Five registers are available for configuring FlatStream. The default configuration can be used to transmit small
amounts of data relatively easily.
Information:
The CPU communicates directly with the field device via the "OutputSequence" and "InputSequence"
as well as the enabled Tx and Rx bytes. For this reason, the user needs to have sufficient knowledge
of the communication protocol being used on the field device.
FlatStream configuration
To use FlatStream, the program sequence must first be expanded. The cycle time of the FlatStream routines must
be set to a multiple of the bus cycle. Other program routines should be implemented in Cyclic #1 to ensure data
consistency.
At the absolute minimum, the "InputMTU" and "OutputMTU" registers need to be configured. All other registers are
filled in with default values at the beginning and can be used immediately. These registers are used for additional
options, e.g. to transmit data in a more compact way or to increase the efficiency of the general procedure.
The Forward registers extend the functionality of the FlatStream protocol. This functionality is useful for substan-
tially increasing the FlatStream data rate, but it also requires quite a bit of extra work when creating the program
sequence.
Name:
OutputMTU
InputMTU
These registers define the number of enabled Tx or Rx bytes, i.e. the maximum size of a sequence. The user must
consider that the more bytes made available also means a higher load on the bus system.
Information:
In the rest of this documentation, the names "OutputMTU" and "InputMTU" do not refer to the registers
explained here. Instead, they are used as synonyms for the currently enabled Tx or Rx bytes.
Data type Value
USINT See the module-specific register overview (theoretically: 3 to 27)
FlatStream operation
When using FlatStream, the communication direction is enormously important. For sending data to a module ("out-
put" direction), the Tx bytes are used. For receiving data from a module ("input" direction), the Rx bytes are used.
The "OutputSequence" and "InputSequence" registers are used to control and ensure that communication is taking
place properly, i.e. the transmitter issues the directive that the data should be accepted and the receiver acknowl-
edges that a sequence has been transmitted successfully.
Name:
TxByte1 to TxByteN
RxByte1 to RxByteN
(The value the number N is different depending on the bus controller model used.)
The Tx and Rx bytes are cyclic registers used to transport the payload data and the necessary control bytes. The
number of active Tx and Rx bytes is taken from the configuration of the "OutputMTU" and "InputMTU" registers,
respectively.
In the user program, only the Tx and Rx bytes from the CPU can be used. The corresponding counterparts are
located in the module and are not accessible to the user. For this reason, names were chosen from the CPU point
of view.
• "T" - "Transmit" → CPU transmits data to the module.
• "R" - "Receive" → CPU receives data from the module.
Data type Value
USINT 0 to 65535
Control bytes
In addition to the payload data, the Tx and Rx bytes also transmit the necessary control bytes. These control bytes
contain additional information about the data stream so that the receiver can reconstruct the original message from
the transmitted segments.
Bit structure of a control byte
Bit Name Value Information
0-5 SegmentLength 0 - 63 Size of the subsequent segment in bytes (default: Max. MTU size - 1)
6 nextCBPos 0 Next control byte at the beginning of the next MTU
1 Next control byte directly after the end of the current segment
7 MessageEndBit 0 Message continues after the subsequent segment
1 Message ended by the subsequent segment
SegmentLength
The segment length lets the receiver know the length of the coming segment. If the configured segment length
is insufficient for a message, then the information must be distributed over several segments. In these cases, the
actual end of the message is detected using bit 7 of the control byte.
Information:
The control byte is not included in the calculation to determine the segment length. The segment length
is only derived from the bytes of payload data.
nextCBPos
This bit indicates the position where the next control byte is to be expected. This information is especially important
when using the "MultiSegmentMTU" option.
When using FlatStream communication with multi-segment MTUs, the next control byte is no longer expected in
the first Rx byte of the subsequent MTU, but directly after the current segment.
MessageEndBit
The "MessageEndBit" is set if the subsequent segment completes a message. The message has then been com-
pletely transmitted and is ready for further processing.
Information:
In the output direction, this bit must also be set if one individual segment is enough to hold the entire
message. The module will only process a message internally if this identifier is detected.
The size of the message being transmitted can be calculated by adding all of the message's segment
lengths together.
FlatStream formula for calculating message length:
Message [bytes] = SegmentLengths (all CBs without ME) + SegmentLength (of the first CB with CB Control byte
ME) ME MessageEndBit
Name:
OutputSequence
The "OutputSequence" register contains information about the communication status of the CPU. It is written by
the CPU and read by the module.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-2 OutputSequenceCounter 0-7 Counter for the sequences issued in the output direction
3 OutputSyncBit 0 Output direction disabled
1 Output direction enabled
4-6 InputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 InputSyncAck 0 Input direction not ready (disabled)
1 Input direction ready (enabled)
OutputSequenceCounter
The OutputSequenceCounter is a continuous counter of sequences that have been issued by the CPU. The CPU
uses the OutputSequenceCounter to direct the module to accept a sequence (the output direction must be syn-
chronized when this happens).
OutputSyncBit
The CPU uses the OutputSyncBit to attempt to synchronize the output channel.
InputSequenceAck
InputSequenceAck is used for acknowledgment. The value of the InputSequenceCounter is mirrored if the CPU
has received a sequence successfully.
InputSyncAck
The InputSyncAck bit acknowledges the synchronization of the input channel for the module. This indicates that
the CPU is ready to receive data.
Name:
InputSequence
The "InputSequence" register contains information about the communication status of the module. It is written by
the module and should only be read by the CPU.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-2 InputSequenceCounter 0-7 Counter for sequences issued in the input direction
3 InputSyncBit 0 Not ready (disabled)
1 Ready (enabled)
4-6 OutputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 OutputSyncAck 0 Not ready (disabled)
1 Ready (enabled)
InputSequenceCounter
The InputSequenceCounter is a continuous counter of sequences that have been issued by the module. The
module uses the InputSequenceCounter to direct the CPU to accept a sequence (the input direction must be
synchronized when this happens).
InputSyncBit
The module uses the InputSyncBit to attempt to synchronize the input channel.
OutputSequenceAck
OutputSequenceAck is used for acknowledgment. The value of the OutputSequenceCounter is mirrored if the
module has received a sequence successfully.
OutputSyncAck
The OutputSyncAck bit acknowledges the synchronization of the output channel for the CPU. This indicates that
the module is ready to receive data.
7 InputSyncAck 7 OutputSyncAck
Information:
If communication is interrupted, segments from the unfinished message are discarded. All messages
that were transmitted completely are processed.
Synchronization
During synchronization, a communication channel is opened. It is important to make sure that a module is present
and that the current value of the SequenceCounter is stored on the station receiving the message.
FlatStream can handle full-duplex communication. This means that both channels / communication directions can
be handled separately. They have to be synchronized independently so that simplex communication can theoret-
ically be carried out as well.
Note:
Theoretically, data can be transmitted from this point forward. However, it is still recommended to wait until the output direction is completely synchronized be-
fore transmitting data.
The module sets OutputSyncAck.
The output direction is synchronized, and the CPU can transmit data to the module.
Note:
Theoretically, data can already be transmitted in this cycle.
If the InputSyncBit is set and InputSequenceCounter has been increased by 1, the values in the enabled Rx bytes have to be accepted and acknowledged (see
also "Communication in the input direction").
The input direction is synchronized, and the module can transmit data to the CPU.
If a channel is synchronized, then the opposite station is ready to receive messages from the transmitter. Before
the transmitter can send data, it needs to first create a transmit array in order to meet FlatStream requirements.
The transmitting station must also generate a control byte for each segment created. This control byte contains
information about how the subsequent part of the data being transmitted should be processed. The position of the
next control byte in the data stream can vary. For this reason, it must be clearly defined at all times when a new
control byte is being transmitted. The first control byte is always in the first byte of the first sequence. All subsequent
positions are determined recursively.
FlatStream formula for calculating the position of the next control byte:
Position (of the next control byte) = Current position + 1 + Segment length
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The rest of the configuration corresponds to the default settings.
Default
Message 2:
Message 3:
C3 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C4 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
First, the messages must be split into segments. In the default configuration, it is important to ensure that each
sequence can hold an entire segment, including the associated control byte. The sequence is limited to the size of
the enable MTU. In other words, a segment must be at least 1 byte smaller than the MTU.
MTU = 7 bytes → Max. segment length = 6 bytes
• Message 1 (7 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C0 (control byte 0) C1 (control byte 1) C2 (control byte 2)
- SegmentLength (0) = 0 - SegmentLength (6) = 6 - SegmentLength (1) = 1
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (0) = 0 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 0 Control byte Σ 6 Control byte Σ 129
Table 73: FlatStream determination of the control bytes for the default configuration example (part 1)
C3 (control byte 3) C4 (control byte 4) C5 (control byte 5)
- SegmentLength (2) = 2 - SegmentLength (6) = 6 - SegmentLength (3) = 3
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 130 Control byte Σ 6 Control byte Σ 131
Table 74: FlatStream determination of the control bytes for the default configuration example (part 2)
When transmitting data, the transmit array must be generated in the application program. Sequences are then
transmitted one by one using FlatStream and received by the module.
Information:
Although all B&R modules with FlatStream communication always support the most compact trans-
missions in the output direction, it is recommended to use the same design for the transfer arrays in
both communication directions.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost.
(The relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individually.)
- Subsequent sequences can only be transmitted in the next bus cycle after the completion check has been carried out successfully.
Start
► diff = (OutputSequenceCounter -
OutputSequenceAck) AND 7
► limit = (OutputSequenceCounter -
LastValidAck) AND 7
(diff ≤ limit)
No OutputSequenceAck = No LastValidAck = Yes
AND (OutputSyncAck = 1)
AND (OutputSyncBit = 1) ? OutputSequenceCounter ? OutputSequenceCounter ?
Yes Yes No
No LastValidAck =
diff = 0 ?
OutputSequenceAck
Yes
LastValidAck = No
OutputSequenceAck = 0 ?
OutputSequenceAck
Yes
No OutputSequenceCounter = 0
More sequences to be sent ? OutputSequenceCounter = 1 OutputSyncBit = 1
LastValidAck = 0
Yes
When receiving data, the transmit array is generated by the module, transferred via FlatStream and must then
be reproduced in the receive array. The structure of the incoming data stream can be configured with the mode
register. The algorithm for receiving the data does not change in this regard.
PLC / Bus controller Module
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Start
► InputSequenceAck = InputSequenceCounter
Synchronisation
No
InputSyncBit = 1 ? ► RemainingSegmentSize = 0
► SegmentFlags = 0
Yes
No No
InputSyncAck = 1 ? InputSequenceAck > 0 ?
Yes Yes
MTU_Offset = 0 InputSyncAck = 1
(InputSequenceCounter – No
InputSequenceAck)
AND 0x07 = 1 ?
Yes
► RemainingSegmentSize =
Yes MTU_Data[MTU_Offset] AND 0b0011 1111
RemainingSegmentSize = 0 ? ► SegmentFlags =
MTU_Data[MTU_Offset] AND 0b1100 0000
No ► MTU_Offset = MTU_Offset + 1
No
No
Yes
► InputSequenceAck =
InputMTU_Size = MTU_Offset ?
InputSequenceCounter
No
Details
Information:
When transmitting with MultiSegmentMTUs, it is possible for several small messages to be part of one
sequence. In the program, it's important to make sure that a sufficient number of receive arrays can
be managed. The entire sequence must be accepted before it is possible to change the Acknowledge
register.
If a SequenceCounter is incremented by more than one value, then an error has occurred.
Note: This situation is very unlikely when operating without "Forward" functionality.
In this case, the receiver stops. All additional incoming sequences are ignored until the transmission with the correct
SequenceCounter is retried. This response prevents the transmitter from receiving any more acknowledgments for
transmitted sequences. The transmitter can identify the last successfully transmitted sequence from the opposite
station's SequenceAck and continue the transmission from this point.
Acknowledgments must be checked for validity.
If the receiver has successfully accepted a sequence, it must be acknowledged. The receiver takes on the Se-
quenceCounter value sent along with the transmission and matches the SequenceAck to it. The transmitter reads
the SequenceAck and registers the successful transmission. If the transmitter acknowledges a sequence that has
not yet been dispatched, then the transmission needs to be interrupted and the channel resynchronized. The syn-
chronization bits are reset and the current/incomplete message is discarded. It needs to be sent again once the
channel has been resynchronized.
FlatStream mode
Name:
FlatstreamMode
In the input direction, the transmit array is generated automatically. This register offers two options to the user
that allow an incoming data stream to have a more compact arrangement. Once enabled, the program code for
evaluation must be adapted accordingly.
Information:
All B&R modules that offer FlatStream mode support the options "Large segments" and "MultiSeg-
mentMTUs" in the output direction. Compact transmission only needs to be explicitly allowed in the
input direction.
Bit structure:
Bit Name Value Information
0 MultiSegmentMTU 0 Not allowed (default)
1 Allowed
1 Large segments 0 Not allowed (default)
1 Allowed
2-7 Reserved
Default
By default, both options relating to compact transmission in the input direction are disabled.
1. The module only forms segments that are at least one byte smaller than the enabled MTU. Each sequence
begins with a control byte so that the data stream is clearly structured and relatively easy to evaluate.
2. Since a FlatStream message can be of any length, the last segment of the message frequently doesn't fill up
all of the MTU's space. By default, the remaining bytes during this type of transfer cycle are not used.
C C C
- - -
ME0 ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
MultiSegmentMTUs allowed
With this option, the InputMTU is completely filled (if enough data is pending). The previously unfilled Rx bytes
transmit the next control bytes and their segments. This allows the enabled Rx bytes to be used more efficiently.
Bus cycle 1 Bus cycle 2 Bus cycle 3
C C C C
- -
ME0 ME1 ME0 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Information:
It is still possible to split up a message into several segments, however. If this option is used and
messages with more than 63 bytes occur, for example, then messages can still be split up among
several segments.
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Figure 152: Arrangement of messages in the MTU (large segments and MultiSegmentMTUs)
If the way messages are structured is changed, then the way data in the transmit/receive array is arranged is also
different. The following changes apply to the example given earlier.
MultiSegmentMTU
If MultiSegmentMTUs are allowed, then "open positions" in an MTU can be used. These "open positions" occur if
the last segment in a message does not fully use the entire MTU. MultiSegmentMTUs allow these bits to be used to
transmit the subsequent control bytes and segments. In the program sequence, the "nextCBPos" bit in the control
byte is set so that the receiver can correctly identify the next control byte.
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows transmission of MultiSegmentMTUs.
Message 1: Transmit/Receive array
Message 2: MultiSegmentMTU
Message 3:
C5 D2 D3 D4 D5 D6 D7 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C6 D8 D9 C0 - - - Sequence for bus cycle 4
First, the messages must be split into segments. As in the default configuration, it is important for each sequence
to begin with a control byte. The free bits in the MTU at the end of a message are filled with data from the following
message, however. With this option, the "nextCBPos" bit is always set if payload data is sent after the control byte.
MTU = 7 bytes → Max. segment length = 6 bytes
• Message 1 (7 bytes)
➯ First segment = Control byte + 2 bytes of data (MTU still has 2 open bytes)
• Message 3 (9 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (6) = 6 - SegmentLength (1) = 1 - SegmentLength (2) = 2
- nextCBPos (1) = 64 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 70 Control byte Σ 193 Control byte Σ 194
Table 75: FlatStream determination of the control bytes for the MultiSegmentMTU example (part 1)
Warning!
The second sequence must have been completely processed before it can be acknowledged with Se-
quenceAck. In this example, there are three different segments within the second sequence, i.e. the
program must include enough receive arrays to handle this situation.
C4 (control byte 4) C5 (control byte 5) C6 (control byte 6)
- SegmentLength (1) = 1 - SegmentLength (6) = 6 - SegmentLength (2) = 2
- nextCBPos (6) = 6 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 0 - MessageEndBit (1) = 128
Control byte Σ 7 Control byte Σ 70 Control byte Σ 194
Table 76: FlatStream determination of the control bytes for the MultiSegmentMTU example (part 2)
Large segments
Segments are limited to a maximum of 63 bytes. This means they can be larger than the active MTU. These large
segments are divided among several sequences when transmitted. It is possible for sequences to be completely
filled with payload data and not have a control byte.
Information:
It is still possible to subdivide a message into several segments so that the size of a data packet does
not also have to be limited to 63 bytes.
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows the transmission of large segments.
Message 3:
C2 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C3 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 77: FlatStream determination of the control bytes for the large segment example
Message 3:
D3 D4 D5 D6 D7 D8 D9 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C0 - - - - - - Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 78: FlatStream determination of the control bytes for the large segment and MultiSegmentMTU example
Forward functionality is a method that can be used to substantially increase the FlatStream data rate. The basic
principle is also used in other technical areas such as "pipelining" for microprocessors.
Operating principle
X2X Link communication cycles through five different steps to transmit a FlatStream sequence. At least five bus
cycles are therefore required to successfully transfer the sequence.
Step I Step II Step III Step IV Step V
Actions Transfer sequence from Cyclic matching of MTU and Append sequence to re- Cyclic matching of Check SequenceAck
transmit array, module buffer ceive array MTU and module buffer
increase Sequence- Adjust SequenceAck
Counter
Resource Transmitter Bus system Recipient Bus system Transmitter
(task to transmit) (direction 1) (task to receive) (direction 2) (task for Ack checking)
Sequence 3 ...
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Configuration
The Forward function only has to be enabled for the input direction. Two additional configuration registers are
available for doing so. FlatStream modules have been optimized in such a way that they support this function. In
the output direction, the Forward function can be used as soon as the size of the OutputMTU is specified.
Name:
Forward
With the "Forward" register, the user specifies how many unacknowledged sequences the module is allowed to
transmit.
Recommendation:
X2X Link: Max. 5
POWERLINK: Max. 7
Data type Value
USINT 1 to 7
Default: 1
Delay time
Name:
ForwardDelay
The "ForwardDelay" register is used to specify the delay time in µs. This is the amount of time the module has
to wait after sending a sequence until it is allowed to write new data to the MTU in the following bus cycle. The
program routine for receiving sequences from a module can therefore be run in a task class whose cycle time is
slower than the bus cycle.
Data type Value
UINT 0 to 65,535 [µs]
Default: 0
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Figure 157: Effect of ForwardDelay when using FlatStream communication with the Forward function
In the program, it is important to make sure that the CPU is processing all of the incoming InputSequences and In-
putMTUs. The ForwardDelay value causes delayed acknowledgment in the output direction and delayed reception
in the input direction. In this way, the CPU has more time to process the incoming InputSequence or InputMTU.
The basic algorithm for transmitting and receiving data remains the same. With the Forward function, up to seven
unacknowledged sequences can be transmitted. Sequences can be transmitted without having to wait for the
previous message to be acknowledged. Since the delay between writing and response is eliminated, a considerable
amount of additional data can be transferred in the same time window.
Algorithm for transmitting
Cyclic status query:
- The Module monitors the OutputSequenceCounter.
0) Cyclic checks:
- The CPU must check OutputSyncAck.
→ If OutputSyncAck = 0: Reset the OutputSyncBit and resynchronize the channel.
- The CPU must check whether OutputMTU is enabled.
→ If OutputSequenceCounter > OutputSequenceAck + 7, then it is not enabled because the last sequence has not yet been acknowledged.
1) Preparation (create transmit array):
- The CPU must split up the message into valid segments and create the necessary control bytes.
- The CPU must add the segments and control bytes to the transmit array.
2) Transmit:
- The CPU must transfer the current part of the transmit array to the OutputMTU.
- The CPU must increase the OutputSequenceCounter for the sequence to be accepted by the module.
- The CPU can then transmit in the next bus cycle if the MTU has been enabled.
The module responds since OutputSequenceCounter > OutputSequenceAck:
- The module accepts data from the internal receive buffer and appends it to the end of the internal receive array.
- The module is acknowledged and the currently received value of the OutputSequenceCounter is transferred to OutputSequenceAck.
- The module requests the status cyclically again.
3) Completion (acknowledgment):
- The CPU must check OutputSequenceAck cyclically.
→ A sequence is only considered to have been transmitted successfully if it has been acknowledged via OutputSequenceAck. In order to detect potential trans-
mission errors in the last sequence as well, it is important to make sure that the algorithm is run through long enough.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost (the relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individ-
ually).
Details/Background
1. Illegal SequenceCounter size (counter offset)
Error situation: MTU not enabled
If the difference between SequenceCounter and SequenceAck is larger than allowed during transmission,
then a transmission error has occurred. In this case, all unacknowledged sequences must be repeated with
the old SequenceCounter value.
2. Checking an acknowledgment
After an acknowledgment has been received, a check must verify whether the acknowledged sequence has
been transmitted and had not yet been unacknowledged. If a sequence has been acknowledged more than
once, then a fatal error has occurred. The channel must be closed and resynchronized (same behavior as
when not using Forward).
Information:
In exceptional cases, the module can increment OutputSequenceAck by more than 1 when using
Forward.
This is not an error. The CPU is permitted to consider all sequences up to the one being acknowl-
edged as having been transmitted successfully.
In industrial environments, it is often the case that many different devices from various manufacturers are being
used side by side. The electrical and/or electromagnetic properties of these technical devices can sometimes cause
them to interfere with one another. These kinds of situations can be reproduced and protected against in laboratory
conditions only to a certain point.
Precautions have been taken for X2X Link transmissions if this type of interference occurs. For example, if an
invalid checksum occurs, the I/O system will ignore the data from this bus cycle and the receiver receives the last
valid data once more. With conventional (cyclic) data points, this error can often be ignored. In the following cycle,
the same data point is again retrieved, adjusted and transmitted.
Using Forward functionality with FlatStream communication makes this situation more complex. The receiver re-
ceives the old data again in this situation as well, i.e. the previous values for SequenceAck/SequenceCounter and
the old MTU.
Loss of acknowledgment (SequenceAck)
If a SequenceAck value is lost, then the MTU was already transmitted properly. For this reason, the receiver is per-
mitted to continue processing with the next sequence. The SequenceAck is aligned with the associated Sequence-
Counter and sent back to the transmitter. Checking the incoming acknowledgments shows that all sequences up
to the last one acknowledged have been transmitted successfully (see sequences 1 and 2 in the image).
Loss of transmission (SequenceCounter, MTU):
If a bus cycle drops out and the SequenceCounter value and/or filled MTU are lost, then no data reaches the
receiver. At this point, the transmission routine is not yet affected by the error. The time-controlled MTU is released
again and can be rewritten to.
The receiver receives SequenceCounter values that have been incremented several times. For the receive array
to be put together correctly, the receiver is only allowed to process transmissions whose SequenceCounter has
been increased by one. The incoming sequences must be ignored, i.e. the receiver stops and no longer transmits
back any acknowledgments.
If the maximum number of unacknowledged sequences has been sent and no acknowledgments are returned, the
transmitter must repeat the affected SequenceCounter and associated MTUs (see sequence 3 and 4 in the image).
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 EMC Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Name:
The registers are described under 4.3.14.10.10 "Analog energy registers". Comparison:
Force registers Read registers
Frc_APenergyT "APenergyT"
Frc_APenergyTF
Frc_APenergyTH
Frc_APenergyA "APenergyA"
Frc_APenergyAF
Frc_APenergyAH
Frc_APenergyB "APenergyB"
Frc_APenergyBF
Frc_APenergyBH
Frc_APenergyC "APenergyC"
Frc_APenergyCF
Frc_APenergyCH
Frc_ANenergyT "ANenergyT"
Frc_ANenergyTF
Frc_ANenergyTH
Frc_ANenergyA "ANenergyA"
Frc_ANenergyAF
Frc_ANenergyAH
Frc_ANenergyB "ANenergyB"
Frc_ANenergyBF
Frc_ANenergyBH
Frc_ANenergyC "ANenergyC"
Frc_ANenergyCF
Frc_ANenergyCH
Frc_RPenergyT "RPenergyT"
Frc_RPenergyA "RPenergyA"
Frc_RPenergyB "RPenergyB"
Frc_RPenergyC "RPenergyC"
Frc_RNenergyT "RNenergyT"
Frc_RNenergyA "RNenergyA"
Frc_RNenergyB "RNenergyB"
Frc_RNenergyC "RNenergyC"
Frc_SAenergyT "SAenergyT"
Frc_SenergyA "SenergyA"
Frc_SenergyB "SenergyB"
Frc_SenergyC "SenergyC"
Frc_SVenergyT "SVenergyT"
These registers can be used to set the energy counter to a specific value after a module has been replaced.
Data type Value
UDINT 0 to 4,294,967,295
Name:
FrcAPenergyT
The registers are described under 4.3.14.10.10 "Analog energy registers".
These registers can be used to set the energy counter to a specific value after a module has been replaced. The
register is updated to the current values when triggered by ControlOutput, Bit 3.
Data type Value
UDINT 0 to 4,294,967,295
A Sample Line contains the present values for currents (4 channels) and voltages (3 channels), as well as a
consecutive number and the network time when transferred from the transformer. These values are recorded in
an interval of 125 µs * prescaler.
The user must then scale the values to respective physical values:
Voltage: Vrms = (INT32)Vs * 4 / Sqrt(2)
Current: Irms = (INT32)Is * 4 / Sqrt(2)
Name:
IactN_Sample1 to IactN_Sample16
Data type Value Information
INT -32,767 to 32,767 Present value of the neutral current, resolution 0,001 A
This value must be converted by the application: See section 4.3.14.10.21.1 "General information"
Name:
IactA_Sample1 to IactA_Sample16
Data type Value Information
INT -32,767 to 32,767 Present current value on phase A, resolution 0.001 A
This value must be converted by the application: See section 4.3.14.10.21.1 "General information"
Name:
UactA_Sample1 to UactA_Sample16
Data type Value Information
INT -32,767 to 32,767 Present voltage value on phase A, resolution 0.01 V
This value must be converted by the application: See section 4.3.14.10.21.1 "General information"
Name:
IactB_Sample1 to IactB_Sample16
Data type Value Information
INT -32,767 to 32,767 Present current value on phase B, resolution 0.001 A
This value must be converted by the application: See section 4.3.14.10.21.1 "General information"
Name:
UactB_Sample1 to UactB_Sample16
Data type Value Information
INT -32,767 to 32,767 Present voltage value on phase B, resolution 0.01 V
This value must be converted by the application: See section 4.3.14.10.21.1 "General information"
Name:
IactC_Sample1 to IactC_Sample16
Data type Value Information
INT -32,767 to 32,767 Present current value on phase C, resolution 0.001 A
This value must be converted by the application: See section 4.3.14.10.21.1 "General information"
Name:
UactC_Sample1 to UactC_Sample16
Data type Value Information
INT -32,767 to 32,767 Present voltage value on phase C, resolution 0.01 V
This value must be converted by the application: See section 4.3.14.10.21.1 "General information"
Name:
SampleCount1 to Samplecount16
Number of new Sample Lines since last readout.
Data type Value Information
SINT -127 to 127 Sample Line number, ascending, cyclic
INT -32,767 to 32,767
Name:
Timestamp
Older Sample Lines must each be back-calculated with 125 µs.
Data type Value Information
INT -32,767 to 32,767 Network timestamp of Sample Line 1
DINT -2,147,483,647 to 2,147,483,647
Name:
OnTime
The operating time since startup is saved in seconds in this register.
Data type Value
UDINT 0 to 4,294,967,295
Name:
UpCounter
The number of restarts since startup is saved in this register.
Data type Value
UDINT 0 to 4,294,967,295
Name:
MinTemp
The lowest transformer temperature [°C] since startup is saved in this register.
Data type Value Information
INT -200 to 200 Resolution 1°C
Name:
MaxTemp
The highest transformer temperature [°C] since startup is saved in this register.
Data type Value Information
INT -200 to 200 Resolution 1°C
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Voltage and current sampling rate for calculation of effective value, power and energy 1 MHz
Derived values: RMS, power, energy, power factor, phase angle, frequency (mean values over 16 full waves) Approx. 3 Hz
FFT on request (SR: 8 kHz) 2 Hz
4.4.2 X20AO2437
The X20AO2437 module is equipped with two current outputs with 16-bit digital converter resolution. The two
channels are electrically isolated from each other. The user can select between the three output ranges 4 to 20 mA,
0 to 20 mA and 0 to 24 mA.
• 2 analog current outputs
• Electrically isolated analog channels
• 16-bit digital converter resolution
Product ID X20AO2437
Short description
I/O module 2 analog outputs 4 to 20 mA, 0 to 20 mA or 0 to 24 mA
General information
B&R ID code 0xB785
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED and software
Power consumption
Bus 0.05 W
Internal I/O 1.6 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Analog outputs
Output 4 to 20 mA, 0 to 20 mA or 0 to 24 mA, configurable using software
Digital converter resolution 16-bit
Settling time for output changes over entire range 2 ms to 20 s, configurable using software
Data output rate 1 ms without ramp
4.4.2.5 Pinout
r e
X20 AO 2437
1 2
Channel 1 +
Channel 1 −
Channel 2 +
Channel 2 −
With external
AO Power supply
4-wire
Actuator
4-wire
Actuator
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
I/O status
Processor
Electrical
Isolation
LED (orange)
I/O
Power supplies
GND x Power supply
Channel x +
D/A
Converter GND x GND I/O
Channel x -
GND x
4.4.2.9 Derating
To ensure proper operation, the derating values listed below must be adhered to:
Horizontal installation
Horizontal installation
600
500
300
Prohibited
200
Range
100
50°C / 0 Ω
0
-20 -10 0 10 20 30 40 50 60
600
500
400
Prohibited
Range
Load [Ω]
300
100
45°C / 0 Ω
0
-20 -10 0 10 20 30 40 50 60
1) The offset specifies the position of the register within the CAN object.
The module has two electrically isolated channels. All registers have a dual design. Channels can be configured
and operated independently of one another.
Specific features
• Electrical isolation by channel
• Configurable output ramp DAC slew rate (Default: 210 ms full scale)
4.4.2.10.4.1 AnalogMode
Name:
AnalogMode01 to AnalogMode02
These registers are used to predefine the operating parameters that the module will be using for the respective
channel. Each channel must be activated and configured separately.
Information:
When you select the operating mode "Scaling 0 to 20 mA (Resolution 0 to 65535)", then the corre-
sponding "AnalogOutput" registers are interpreted internally as UINT instead of INT.
The entire program must be rebuilt for the data type change to take effect. The data type cannot be
changed during runtime (e.g. using a library).
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 0 Disabled
1 Enabled (bus controller default)
1 Check - DAC configuration/status 0 Enabled (bus controller default)
1 Disabled
2-3 Reserved -
4 Scaling 0 to 20 mA 0 Disabled
(Resolution 0 to 32767) 1 Enabled
5 Scaling 4 to 20 mA 0 Disabled
(Resolution 0 to 32767) 1 Enabled (bus controller default)
6 Scaling 0 to 24 mA 0 Disabled
(Resolution 0 to 24000) 1 Enabled
7 Scaling 0 to 20 mA 0 Disabled
(Resolution 0 to 65535) 1 Enabled
8 - 15 Reserved -
4.4.2.10.4.2 DACSlewrate
Name:
DACSlewrate01 to DACSlewrate02
These registers limit the rate at which the analog signal is modified. This makes it possible to define a sort of upper
limit frequency.
The following formula f(Analog) = f(Output rate) * Permitted change / max. ∆(standardized output value)
applies:
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0-2 Permitted change per rate 000 1-bit
001 2-bit
010 4 bit (bus controller default)
011 8-bit
100 16-bit
101 32-bit
110 64-bit
111 128-bit
3-7 Reserved -
8 - 11 Output rate 0000 257730 Hz
0001 198410 Hz
0010 152440 Hz (bus controller default)
0011 131580 Hz
0100 115740 Hz
0101 69440 Hz
0110 37590 Hz
0111 25770 Hz
1000 20160 Hz
1001 16030 Hz
1010 10290 Hz
1011 8280 Hz
1100 6900 Hz
1101 5530 Hz
1110 4240 Hz
1111 3300 Hz
12 - 14 Reserved -
15 Slewrate enable 0 Disabled (undefined jump behavior)
(ramp functionality) 1 Enabled (defined transitions)
In order to output the required current signal (default: 4 to 20 mA), the module must be provided with the standard-
ized output value (default: 0 to 32767).
4.4.2.10.5.1 AnalogOutput
Name:
AnalogOutput01 to AnalogOutput02
These registers provide the standardized output values. Depending on the scaling selected (see AnalogMode
register), the value range and the data type can be adapted to the requirements of the application. Once a permitted
value is determined, the module outputs the respective current.
Information:
The value "0" disables the channel status LED.
Data type Value Information
INT 0 to 32767 Bus controller default: 0
Optional: UINT 0 to 65535
4.4.2.10.5.2 AnalogStatus
Name:
AnalogStatus01 to AnalogStatus02
The status register gives the user feedback about whether the respective channel is functioning properly.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0-1 Reserved -
2 OpenLineAnalogOutput01, 02 0 Line OK
1 Open line
3 ConversionErrorAnalogOutput01, 02 0 Conversion temperature OK
1 Conversion temperature too high
4-6 Reserved -
7 IoSuppErrorAnalogOutput01, 02 0 Module supply OK
1 Module supply error
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 OSPValid 0 Request OSP operation (after initial start or module in Standby)
1 Request normal operation
1-7 Reserved 0
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the relevant
task in the master CPU. However, an output still occurs depending on the configuration of the OSP
replacement value.
Name:
CfgOSPMode01 to CfgOSPMode02
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue01 to CfgOSPValue02
This register contains the analog output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
Corresponds to Corresponds to AnalogOutput0x
AnalogOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
200 µs
4.4.3 X20AO2438
The X20AO2438 module is equipped with two current outputs with 16-bit digital converter resolution. It supports
the HART communication standard for data transfer, parameter configuration and diagnostics.
The two channels are electrically isolated from each other. The user can select between the three output ranges
4 to 20 mA, 0 to 20 mA and 0 to 24 mA.
• 2 analog current outputs
• HART protocol integration
• Support for HART variables
• Electrically isolated analog channels
• 16-bit digital converter resolution
Product ID X20AO2438
Short description
I/O module 2 analog outputs 4 to 20 mA, 0 to 20 mA or 0 to 24 mA
General information
B&R ID code 0xB3AA
Status indicators I/O function per channel, operating state, module status, HART
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED and software
HART link Yes, using status LED and software
HART error Yes, using status LED and software
Power consumption
Bus 0.05 W
I/O internal 1.65 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Analog outputs
Output 4 to 20 mA, 0 to 20 mA or 0 to 24 mA, configurable using software
Digital converter resolution 16-bit
Settling time for output changes over entire range 2 ms to 20 s, configurable using software
4.4.3.5 Pinout
r e
1 2
L L
e e
Channel 1 +
Channel 1 −
Channel 2 +
Channel 2 −
With external
AO Power supply
4-wire
Actuator
4-wire
Actuator
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
I/O status
LED (orange)
GND x
HART link
Processor
LED (green)
GND x
HART error
LED (red)
GND x Electrical
Isolation
Receiving HART Power I/O
Modem sections Power supply
D/A
converter
Channel x -
GND x
4.4.3.9 Operation
4.4.3.9.1 Derating
To ensure proper operation, the derating values listed below must be adhered to:
Horizontal installation
Horizontal installation
600
500
300
Prohibited
200
Range
100
50°C / 0 Ω
0
-20 -10 0 10 20 30 40 50 60
Vertical installation
Vertical installation
600
500
400
Prohibited
Range
Load [Ω]
300
100
45°C / 0 Ω
0
-20 -10 0 10 20 30 40 50 60
This module supports the HART communication standard for data transfer, parameter configuration and diagnos-
tics. The HART standard is used for the current range 4 to 20 mA. Be aware that the load is not permitted to fall
below 230 Ω .
600
500 Prohibited
Range
Specified
400 HART operational range
Load [Ω]
300
200
100
0
0 2 4 6 8 10 12 14 16 18 20 22 24
Current [mA]
1) These HART registers are defined multiple times. Hence, they can be activated acyclically, if they are not registered during the cyclical phase of the X2X
transmission.
1) These HART registers are defined multiple times. Hence, they can be activated acyclically, if they are not registered during the cyclical phase of the X2X
transmission.
1) The offset specifies the position of the register within the CAN object.
The X20AO2438 module has two independent electrically isolated channels with integrated HART modems. Both
channels can be used to output an analog signal and handle HART communication. Two registers need to be
configured for one analog signal. The two channels operate independently, so two registers must be configured
per channel to be used.
The current outputs (default: 4 to 20 mA) can be used as conventional analog signals. The integrated HART
modems retrieve digital information from the memory on the HART slave using the same physical lines that mod-
ulate the HART signals.
Each channel can use one of the following connection variants:
• Point-to-point (connection of one HART node on the channel):
→ Evaluation of the analog signal
and
→ Recording of up to 4 HART values
• Multidrop (connection of up to 15 HART nodes on the channel):
→ Recording of one HART value per connected node
Specific features
• Electrical isolation by channel
• Up to 4 or 15 HART input variables per channel
• Configurable output rate (DAC slew rate) to transfer HART and analog signal without interference (default:
210 ms full scale)
• Selectable error strategy (static replacement value or retention of the last permitted value)
• Cyclic "HART status" polling (HART command 0), the status information received is made available for
channel diagnostics
• Compatible with an additional secondary master in the HART network (module acts as the primary master)
• "HART communication error bit" (shows loss of HART connection if a connection had already been estab-
lished successfully)
• Optional: BURST mode for one node per channel
• Optional: Cyclic polling of "HART variables" (HART command 3 or 9)
• Optional: FlatStream functionality (module acts as bridge for HART packets)
4.4.3.10.4.1 AnalogMode
Name:
AnalogMode01 to AnalogMode02
These registers are used to predefine the operating parameters that the module will be using for the respective
channel. Each channel must be activated and configured separately.
Information:
When you select the operating mode "Scaling 0 to 20 mA (Resolution 0 to 65535)", then the corre-
sponding "AnalogOutput" registers are interpreted internally as UINT instead of INT.
The entire program must be rebuilt for the data type change to take effect. The data type cannot be
changed during runtime (e.g. using a library).
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 0 Disabled
1 Enabled (bus controller default)
1 Check - DAC configuration/status 0 Enabled (bus controller default)
1 Disabled
2-3 Reserved -
4 Scaling 0 to 20 mA 0 Disabled
(Resolution 0 to 32767) 1 Enabled
5 Scaling 4 to 20 mA 0 Disabled
(Resolution 0 to 32767) 1 Enabled (bus controller default)
6 Scaling 0 to 24 mA 0 Disabled
(Resolution 0 to 24000) 1 Enabled
7 Scaling 0 to 20 mA 0 Disabled
(Resolution 0 to 65535) 1 Enabled
8 - 15 Reserved -
Information:
The "AnalogMode" registers provide the option of avoiding the cyclic check of the DAC configuration.
To manage communication reliably, this option should only be used if no HART communication is
taking place on the channel.
4.4.3.10.4.2 DACSlewrate
Name:
DACSlewrate01 to DACSlewrate02
These registers limit the rate at which the analog signal is modified. This makes it possible to define a sort of upper
limit frequency.
The following formula f(Analog) = f(Output rate) * Permitted change / max. ∆(standardized output value)
applies:
Data type Value
UINT See bit structure
To ensure communication takes place without errors, it's important that the frequency range of the digital HART
signal is not influenced by the analog output. HART communication takes place in the frequency range 950 to
2500 Hz.
Example (default): f(Analog) = 152440 Hz * 4 / (32767 - 0)
Conclusion: f(Analog) = ~20 Hz << 950 Hz = f(HART)
Bit structure:
Bit Name Value Information
0-2 Permitted change per rate 000 1-bit
001 2-bit
010 4 bit (bus controller default)
011 8-bit
100 16-bit
101 32-bit
110 64-bit
111 128-bit
3-7 Reserved -
8 - 11 Output rate 0000 257730 Hz
0001 198410 Hz
0010 152440 Hz (bus controller default)
0011 131580 Hz
0100 115740 Hz
0101 69440 Hz
0110 37590 Hz
0111 25770 Hz
1000 20160 Hz
1001 16030 Hz
1010 10290 Hz
1011 8280 Hz
1100 6900 Hz
1101 5530 Hz
1110 4240 Hz
1111 3300 Hz
12 - 14 Reserved -
15 Slewrate enable 0 Disabled (undefined jump behavior)
(ramp functionality) 1 Enabled (defined transitions)
In order to output the required current signal (default: 4 bis 20 mA), the module must be assigned the default
output value (default: 0 to 32767). In this way, the X20AO2438 can be used as a conventional output module. The
integrated HART modem uses the same physical line. Using signals with a higher frequency allows the module to
communicate with and also retrieve information from the HART slave.
4.4.3.10.5.1 AnalogOutput
Name:
AnalogOutput01 to AnalogOutput02
These registers provide the standardized output values. Depending on the scaling selected (see AnalogMode
register), the value range and the data type can be adapted to the requirements of the application. Once a permitted
value is determined, the module outputs the respective current.
Information:
The value "0" disables the channel status LED.
Data type Value Information
INT 0 to 32767 Bus controller default: 0
Optional: UINT 0 to 65535
4.4.3.10.5.2 AnalogStatus
Name:
AnalogStatus01 to AnalogStatus02
The status register gives the user feedback about whether the respective channel is functioning properly.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0-1 Reserved -
2 OpenLineAnalogOutput01, 02 0 Line OK
1 Open line
3 ConversionErrorAnalogOutput01, 02 0 Conversion temperature OK
1 Conversion temperature too high
4-6 Reserved -
7 IoSuppErrorAnalogOutput01, 02 0 Module supply OK
1 Module supply error
4.4.3.10.6 HART
HART (Highway Addressable Remote Transducer) is a protocol for communicating with intelligent field devices. It
was developed in order to more efficiently use the infrastructure for transferring analog signals. The digital HART
notifications are modulated to the analog signal using Frequency Shift Keying (FSK). HART can thus use the same
physical line as the analog signal without influencing the original function.
HART slaves are able to determine different process data independently and prepare HART concordantly. This
protocol supports polling of the value of a process variable as well as its unit and status. Field devices usually supply
their information after the master requests it. In newer revisions, it is also possible to transfer configuration data.
There are two different types of HART networks. In a point-to-point network, only one slave is connected to a HART
master. Here, the analog signal and the HART signal can be transferred over the same line. Managing several
slaves with HART requires what is known as a multidrop network. Here, each HART slave is assigned and identified
by a unique address. Classic analog signals cannot be clearly traced in bus systems. As a result, the HART protocol
does not support analog information transfers in multidrop networks up to and including HART Revision 5.
Information:
Split range operation with HART AO modules
Beginning with HART revision 6, bus stations that use an analog signal according to the split range
method are written to separately. The HART protocol supports multidrop addressing as well as the use
of analog signals for these applications.
The module was designed based on HART-Revision 5. Only single-channel FSK scheme is available for transmit-
ting the signals.
Since all HART frames are generated and evaluated in the application when using the FlatStream interface, infor-
mation that isn't specified until later revisions can also be read.
HART modules are analog modules equipped with a HART modem. For each channel, a separate HART network
can be managed by the module, which acts as a primary master. Once configured successfully, the HART infor-
mation is stored in the module where it can then be used by the PLC.
The number of HART slaves must be specified in the configuration.
If only one slave is connected to the HART channel, then it is part of a point-to-point network. The module can then
prepare up to four process variables from the connected slave.
Multidrop mode allows up to 15 HART slaves to be connected. The primary process variable from each slave is
then retrieved.
HartNodeCnt
Name:
HartCodeCnt_1 to HartCodeCnt_2
These registers tell the module how many HART slaves are connected to a channel.
Information:
If a slave is not connected to one of the HART channels, the value "0" should be defined in this register.
This shortens the I/O update time and avoids superfluous error messages.
Data type Value Information
USINT 0 HART communication disabled for this channel
1 Point-to-point Standard HART communication (bus controller default)
2 to 15 Multidrop Number of HART slave nodes
HartBurstNode
Name:
HartBurstNode_1 to HartBurstNode_2
In addition to the type of network, the user can also choose from two different types of communication behavior.
Conventional HART communication relies on polling. The module requests the data from the individual HART
slaves and receives the corresponding information from each slave as a response. If a HART node should be
queried in short time intervals, the user can configure burst mode for channels on one node. In this case, the slave
transmits the node's information cyclically without constant prompting from the master.
The "HartBurstNode" registers are therefore used to enter the node numbers (short address) for the chan-
nels whose information should be retrieved using burst mode. Burst mode itself is enabled with the
"HartMode""HartMode" register.
Data type Value Information
USINT 0 to 15 Point-to-point 0 (bus controller default)
HartMode
Name:
HartMode_1 to HartMode_2
The user can use these registers to configure the communication behavior of each of the HART channels. Gener-
ally, the HART nodes are polled individually. This register can still be used to start or stop burst mode when needed.
In burst mode, a node transmits its information cyclically instead of continuously. As a result, the HART standard
allows the simultaneous usage of both burst mode and polling.
Information:
To retrieve information with burst mode, the "HartBurstNode"HartBurstNode register must be config-
ured correctly.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0 Slave polling mode 0 Polling mode enabled (Bus Controller Default)
1 Polling mode disabled
1 Start slave burst mode 0 No response to burst (bus controller default)
1 Enables burst mode in the "HartBurstNode" nodeHartBurstNode
2 Stop slave burst mode 0 No response to burst (bus controller default)
1 Disables burst mode, if enabled
3-7 Reserved -
Once the configuration has been completed, the information is retrieved automatically and transferred to the
module's registers. A separate register in the module is implemented for each piece of information. HART modules
are designed to retrieve up to 15 pieces of information per channel. The module reads in the data, stores it in tem-
porary memory and prepares it for retrieval. When the X2X master accesses the module registers, it is irrelevant
whether the HART data originates from a point-to-point network or a multidrop network.
Overview of internal module mapping
Point-to-point network (1 HART slave) Multidrop network (2 to 15 HART slaves)
(Pv)Input_01 Primary piece of information from HART node 1 Primary piece of information from HART node 1
(Pv)Input_02 Secondary piece of information from HART node 1 Primary piece of information from HART node 2
... ... ...
(Pv)Input_04 Quaternary piece of information from HART node 1 Primary piece of information from HART node 4
(Pv)Input_05 Reserved Primary piece of information from HART node 5
... ... ...
(Pv)Input_15 Reserved Primary piece of information from HART node 15
The HART specifications stipulates that information from a HART node be split into various pieces. The value of
a process variable is stored to the respective "PvInput" register and has a size of 4 bytes (REAL) in accordance
with the HART specification. Due to the length limitation of 30 bytes on the X2X link, there are restrictions to
the number of possible cyclic variables. It is recommended to only transfer a maximum of two "PvInput""PvInput"
registers cyclically to the X2X master. All other information should be transferred in a different way. To access
HART information, the user can choose from among the following methods:
• Data points that are configured to be transferred cyclically are read once per bus cycle. This method allows
information to be exchanged between the module and the X2X master in real time. Nevertheless, the length
limitation may prevent all data from being retrieved within one cycle.
• If the AsIOAcc library is used, information is retrieved acyclically only when it is needed, i.e. communication
can be adapted to the application running on the X2X master. In this way, all of the necessary module
registers on the X2X link can be polled despite the length limitation.
This method of information exchange is not real-time capable.
• HART modules are equipped with a FlatStream interface. When using FlatStream communication, the
module acts a bridge between the X2X master and the HART slave, i.e. the X2X master communicates
directly with the HART slave (see section "FlatStream communication""FlatStream communication").
FlatStream communication is also not real-time capable. It allows unrestricted access to the HART slave.
The user must have sufficient knowledge of the HART protocol command set as well as the capabilities
of the HART slave device.
PvInput
Name:
PvInput_01 to PvInput_15
These registers return the current value of the process variable that has been read.
Information:
These registers are of data type REAL, which means that the available bytes on the X2X link are filled
more quickly when operated cyclically. If information from several slave nodes is needed, it must be
retrieved acyclically or using FlatStream.
Data type Value Information
REAL IEEE745 SPF 32-bit data type with valid value
0x7FA00000 Not a number (NaN) with invalid value
PvUnit
Name:
PvUnit_01 to PvUnit_15
These registers return a HART-specific code that specifies the unit for the measured value. The coding for this is
established in the HART specification.
Data type Value
USINT See description of the HART slave
See HART specification
PvSampleTime
Name:
PvSampleTime01 to PvSampleTime02
PvSampleTime01_01 to PvSampleTime01_15
PvSampleTime02_01 to PvSampleTime02_15
These registers return the timestamp for when the module reads the current channel mapping. The values are
provided as signed 2-byte or 4-byte values.
Data type Values [µs] Information
INT -32768 to 32767 Nettime timestamp of the current input value
DINT -2,147,483,648 Nettime timestamp of the current input value
to 2,147,483,647
This refers to the point in time when the HART master receives the slave's response. This is a way to check whether
new HART information has been read since the last X2X cycle.
Information:
The cycle times of a HART network are relatively long so that it is not possible to reliably determine
when the measured value is retrieved with just this information.
PvNodeComStatus
Name:
PvNodeComStatus01 to PvNodeComStatus02
PvNodeComStatus01_01 to PvNodeComStatus01_15
PvNodeComStatus02_01 to PvNodeComStatus02_15
These registers return information about whether a value that has been read is valid. According to the HART
specification, this type of status register consists of two parts. The high byte stores the "response code" and the
low byte the "field device status". This makes it possible to check the current status of a read process variable.
These registers can be checked before further processing information in temporary storage. If the current value
is 0x0000, an error was not detected during the HART transfer and the information from the checked node can
be used. If a different value is present, the situation in the HART network should be checked. This can be done
using an extension register, for example.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Quality - Node information 2 to n 0 Digital measured value okay
1 Measured value outside the permitted range
1 Quality - Node information 1 0 Digital measured value okay
1 Measured value outside the permitted range
2 Limit violation 0 Parameter okay
1 Invalid measured value(s) or encoder supply value
3 Static analog signal 0 Normal value change/fluctuation
1 Constant analog value of Node 1 slave
4 Additional status information 0 Not available
(only supported by a few slaves) 1 Available (only using FlatStream command #48)
5 Reboot 0 Normal operation
1 Field device restarts
6 Device ID 0 Unchanged
1 Changed
7 Device error 0 Measured value okay
1 Questionable measured value information
8 - 14 Response code, if relevant x See HART-specific response code
15 Error - Communication 0 Error-free communication (response code irrelevant)
1 Faulty communication (response code relevant)
PvCountHartRequest
Name:
PvCountHartRequest01 to PvCountHartRequest02
These registers are increased once the module is ready to transmit a message to the corresponding channel.
Data type Value
UDINT 0 to 4,294,967,295
PvCountHartTimeout
Name:
PvCountHartTimeout01 to PvCountHartTimeout02
These registers are increased if the slave exceeds the maximum permitted time before responding to the module's
request.
Data type Value
UDINT 0 to 4,294,967,295
PvCountHartRxError
Name:
PvCountHartRxError01 to PvCountHartRxError02
These registers are increased if communication errors occur on Layer 1 of the OSI model (e.g. transmission error
as per parity bit).
Data type Value
UDINT 0 to 4,294,967,295
PvCountHartFrameError
Name:
PvCountHartFrameError01 to PvCountHartFrameError02
These registers are increased if communication errors occur on Layer 2 of the OSI model (e.g. faulty telegram
structure).
Data type Value
UDINT 0 to 4,294,967,295
PvNodeFound
Name:
PvNodeFound01 to PvNodeFound02
These registers provide information about which nodes were detected on which channel (slave identified success-
fully).
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0 Node 0 (default mode) 0 Not detected as valid
Node 1 (multidrop mode) 1 Detected as valid
1 Node 2 (multidrop mode) 0 Not detected as valid
1 Detected as valid
... ...
13 Node 14 (multidrop mode) 0 Not detected as valid
1 Detected as valid
14 Node 15 (multidrop mode) 0 Not detected as valid
1 Detected as valid
15 Reserved -
PvNodeError
Name:
PvNodeError01 to PvNodeError02
These registers contain the HART communications error bits. These bits are set if the connection to a node was
established successfully but the node at some point no longer responds as it should (e.g. the HART slave exceeds
the configured timeout / number of retries).
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0 Node 0 (default mode) 0 Detected as having no errors
Node 1 (multidrop mode) 1 Detected as having errors
1 Node 2 (multidrop mode) 0 Detected as having no errors
1 Detected as having errors
... ...
13 Node 14 (multidrop mode) 0 Detected as having no errors
1 Detected as having errors
14 Node 15 (multidrop mode) 0 Detected as having no errors
1 Detected as having errors
15 Reserved -
The additional configuration registers are specified values when the module is started. In most systems, the user
does not need to make any adjustments here. Register values should only be changed if HART network commu-
nication is not taking place satisfactorily.
HartNodeDisable
Name:
HartNodeDisable_1 to HartNodeDisable_2
These registers are intended for things like maintenance. They make it possible to cut off configured HART nodes
to suppress error messages for a certain period of time. During normal operation, the configured nodes must be
switched active to guarantee that the procedure runs smoothly.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0 Node 0 (default mode) 0 Enabled (bus controller default)
Node 1 (multidrop mode) 1 Disabled
1 Node 2 (multidrop mode) 0 Enabled
1 Disabled (bus controller default)
... ...
13 Node 14 (multidrop mode) 0 Enabled
1 Disabled (bus controller default)
14 Node 15 (multidrop mode) 0 Enabled
1 Disabled (bus controller default)
15 Reserved -
HartProtTimeOut
Name:
HartProtTimeOut_1 to HartProtTimeOut_2
These registers specify the time span within which the slave must respond for the response to be valid.
Data type Values [ms] Information
UINT 0 to 65535 Bus controller default: 256 [ms]
HartProtRetry
Name:
HartProtRetry_1 to HartProtRetry_2
These registers determine how many times the master retries a request if it receives an invalid response or no
response at all.
Data type Value Information
UINT 0 to 65535 Bus controller default: 3 attempts
HartPreamble
Name:
HartPreamble_1 to HartPreamble_2
The length of the preamble can be set in these registers. The preamble is used to synchronize the receiver to the
transmitter. The longer the declared preamble, the less chance that a communication error will occur. Nevertheless,
a useful signal is not transmitted during synchronization so the preamble should be kept as short as possible.
Data type Value Information
UINT 5 to 20 Bus controller default: 20
4.4.3.10.7.1 Introduction
B&R offers an additional communication method for some modules. "FlatStream" was designed for X2X and
POWERLINK networks and allows data transmission to be adapted to individual demands. Although this method
is not 100% real-time capable, it still allows data transmission to be handled more efficiently than with standard
cyclic polling.
Field device
X2X language
Cyclic call
via I/O mapping
B&R CPU
Cyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
Acyclic call
via
library functions
B&R CPU
Acyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
FlatStream
The physical properties of the bus system limit the amount of data that can be transmitted during one bus cycle.
With FlatStream communication, all messages are viewed as part of a continuous data stream. Long data streams
must be broken down into several fragments that are sent one after the other. To understand how the receiver puts
these fragments back together to get the original information, it is important to understand the difference between
a message, a segment, a sequence and an MTU.
Message
A message refers to information exchanged between two partner stations. The length of a message is not restricted
by the FlatStream communication method. Nevertheless, module-specific limitations must be considered.
Segment (logical division of a message)
A segment has a finite size and can be understood as a section of a message. The number of segments per
message is arbitrary. So that the recipient can correctly reassemble the transmitted segments, each segment
is preceded by a byte with additional information. This control byte contains information such as the length of a
segment and whether the approaching segment completes the message. This makes it possible for the receiving
station to interpret the incoming data stream correctly.
Sequence (how a segment needs to be arranged physically)
The maximum size of a sequence corresponds to the number of enabled Rx or Tx bytes (later: "MTU"). The
transmitting station splits the transmit array into valid sequences. These sequences are then written successively
to the MTU and transmitted to the receiving station where they are put back together again. The receiver stores
the incoming sequences in a receive array, obtaining an image of the data stream in the process.
With FlatStream communication, the number of sequences sent are counted. Successfully transmitted sequences
must be acknowledged by the receiving station to ensure the integrity of the transmission.
MTU (Maximum Transmission Unit) - Physical transport
MTU refers to the enabled USINT registers used with FlatStream. These registers can accept at least one se-
quence and pass it on to the receiving station. A separate MTU is defined for each direction of communication.
The OutputMTU defines the number of FlatStream Tx bytes, and the InputMTU specifies the number of FlatStream
Rx bytes. The MTUs are transported cyclically via the X2X Link, increasing the load with each additional enabled
USINT register.
Features
FlatStream messages are not transmitted cyclically or in 100% real time. Many bus cycles may be needed to trans-
mit a particular message. Although the Rx and Tx registers are exchanged between the transmitter and the receiv-
er cyclically, they are only processed further if explicitly accepted by the "InputSequence" or "OutputSequence"
register.
Behavior in the event of an error (brief summary)
The protocol for X2X and POWERLINK networks specifies that the last valid values should be retained when
disturbances occur. With conventional communication (cyclic/acyclic data queries), this type of error can generally
be ignored.
In order for communication to also take place without errors using FlatStream, all of the sequences issued by the
receiver must be acknowledged. If Forward functionality is not used, then subsequent communication is delayed
for the length of the disturbance.
If Forward functionality is being used, the receiving station receives a transmission counter that is incremented
twice. The receiver stops, i.e. it no longer returns any acknowledgments. The transmitting station uses the Se-
quenceAck to determine that the transmission was faulty and that all affected sequences will have to be repeated.
Requirements
Before FlatStream can be used, the respective communication direction must be synchronized, i.e. both commu-
nication partners cyclically query the sequence counter on the opposite station. This checks to see if there is new
data that should be accepted.
Communication
If a communication partner wants to transmit a message to its opposite station, it should first create a transmit
array that corresponds to FlatStream conventions. This allows the FlatStream data to be organized very efficiently
without having to block other important resources.
PLC / Bus controller Module
Module-internal Module-internal
Transmit array OutputMTU receive buffer receive array
Type: USINT Type: USINT Type: USINT Type: USINT
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Five registers are available for configuring FlatStream. The default configuration can be used to transmit small
amounts of data relatively easily.
Information:
The CPU communicates directly with the field device via the "OutputSequence" and "InputSequence"
as well as the enabled Tx and Rx bytes. For this reason, the user needs to have sufficient knowledge
of the communication protocol being used on the field device.
FlatStream configuration
To use FlatStream, the program sequence must first be expanded. The cycle time of the FlatStream routines must
be set to a multiple of the bus cycle. Other program routines should be implemented in Cyclic #1 to ensure data
consistency.
At the absolute minimum, the "InputMTU" and "OutputMTU" registers need to be configured. All other registers are
filled in with default values at the beginning and can be used immediately. These registers are used for additional
options, e.g. to transmit data in a more compact way or to increase the efficiency of the general procedure.
The Forward registers extend the functionality of the FlatStream protocol. This functionality is useful for substan-
tially increasing the FlatStream data rate, but it also requires quite a bit of extra work when creating the program
sequence.
Name:
OutputMTU
InputMTU
These registers define the number of enabled Tx or Rx bytes, i.e. the maximum size of a sequence. The user must
consider that the more bytes made available also means a higher load on the bus system.
Information:
In the rest of this documentation, the names "OutputMTU" and "InputMTU" do not refer to the registers
explained here. Instead, they are used as synonyms for the currently enabled Tx or Rx bytes.
Data type Value
USINT See the module-specific register overview (theoretically: 3 to 27)
FlatStream operation
When using FlatStream, the communication direction is enormously important. For sending data to a module ("out-
put" direction), the Tx bytes are used. For receiving data from a module ("input" direction), the Rx bytes are used.
The "OutputSequence" and "InputSequence" registers are used to control and ensure that communication is taking
place properly, i.e. the transmitter issues the directive that the data should be accepted and the receiver acknowl-
edges that a sequence has been transmitted successfully.
Name:
TxByte1 to TxByteN
RxByte1 to RxByteN
(The value the number N is different depending on the bus controller model used.)
The Tx and Rx bytes are cyclic registers used to transport the payload data and the necessary control bytes. The
number of active Tx and Rx bytes is taken from the configuration of the "OutputMTU" and "InputMTU" registers,
respectively.
In the user program, only the Tx and Rx bytes from the CPU can be used. The corresponding counterparts are
located in the module and are not accessible to the user. For this reason, names were chosen from the CPU point
of view.
• "T" - "Transmit" → CPU transmits data to the module.
• "R" - "Receive" → CPU receives data from the module.
Data type Value
USINT 0 to 65535
Control bytes
In addition to the payload data, the Tx and Rx bytes also transmit the necessary control bytes. These control bytes
contain additional information about the data stream so that the receiver can reconstruct the original message from
the transmitted segments.
Bit structure of a control byte
Bit Name Value Information
0-5 SegmentLength 0 - 63 Size of the subsequent segment in bytes (default: Max. MTU size - 1)
6 nextCBPos 0 Next control byte at the beginning of the next MTU
1 Next control byte directly after the end of the current segment
7 MessageEndBit 0 Message continues after the subsequent segment
1 Message ended by the subsequent segment
SegmentLength
The segment length lets the receiver know the length of the coming segment. If the configured segment length
is insufficient for a message, then the information must be distributed over several segments. In these cases, the
actual end of the message is detected using bit 7 of the control byte.
Information:
The control byte is not included in the calculation to determine the segment length. The segment length
is only derived from the bytes of payload data.
nextCBPos
This bit indicates the position where the next control byte is to be expected. This information is especially important
when using the "MultiSegmentMTU" option.
When using FlatStream communication with multi-segment MTUs, the next control byte is no longer expected in
the first Rx byte of the subsequent MTU, but directly after the current segment.
MessageEndBit
The "MessageEndBit" is set if the subsequent segment completes a message. The message has then been com-
pletely transmitted and is ready for further processing.
Information:
In the output direction, this bit must also be set if one individual segment is enough to hold the entire
message. The module will only process a message internally if this identifier is detected.
The size of the message being transmitted can be calculated by adding all of the message's segment
lengths together.
FlatStream formula for calculating message length:
Message [bytes] = SegmentLengths (all CBs without ME) + SegmentLength (of the first CB with CB Control byte
ME) ME MessageEndBit
Name:
OutputSequence
The "OutputSequence" register contains information about the communication status of the CPU. It is written by
the CPU and read by the module.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-2 OutputSequenceCounter 0-7 Counter for the sequences issued in the output direction
3 OutputSyncBit 0 Output direction disabled
1 Output direction enabled
4-6 InputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 InputSyncAck 0 Input direction not ready (disabled)
1 Input direction ready (enabled)
OutputSequenceCounter
The OutputSequenceCounter is a continuous counter of sequences that have been issued by the CPU. The CPU
uses the OutputSequenceCounter to direct the module to accept a sequence (the output direction must be syn-
chronized when this happens).
OutputSyncBit
The CPU uses the OutputSyncBit to attempt to synchronize the output channel.
InputSequenceAck
InputSequenceAck is used for acknowledgment. The value of the InputSequenceCounter is mirrored if the CPU
has received a sequence successfully.
InputSyncAck
The InputSyncAck bit acknowledges the synchronization of the input channel for the module. This indicates that
the CPU is ready to receive data.
Name:
InputSequence
The "InputSequence" register contains information about the communication status of the module. It is written by
the module and should only be read by the CPU.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-2 InputSequenceCounter 0-7 Counter for sequences issued in the input direction
3 InputSyncBit 0 Not ready (disabled)
1 Ready (enabled)
4-6 OutputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 OutputSyncAck 0 Not ready (disabled)
1 Ready (enabled)
InputSequenceCounter
The InputSequenceCounter is a continuous counter of sequences that have been issued by the module. The
module uses the InputSequenceCounter to direct the CPU to accept a sequence (the input direction must be
synchronized when this happens).
InputSyncBit
The module uses the InputSyncBit to attempt to synchronize the input channel.
OutputSequenceAck
OutputSequenceAck is used for acknowledgment. The value of the OutputSequenceCounter is mirrored if the
module has received a sequence successfully.
OutputSyncAck
The OutputSyncAck bit acknowledges the synchronization of the output channel for the CPU. This indicates that
the module is ready to receive data.
7 InputSyncAck 7 OutputSyncAck
Information:
If communication is interrupted, segments from the unfinished message are discarded. All messages
that were transmitted completely are processed.
Synchronization
During synchronization, a communication channel is opened. It is important to make sure that a module is present
and that the current value of the SequenceCounter is stored on the station receiving the message.
FlatStream can handle full-duplex communication. This means that both channels / communication directions can
be handled separately. They have to be synchronized independently so that simplex communication can theoret-
ically be carried out as well.
Note:
Theoretically, data can be transmitted from this point forward. However, it is still recommended to wait until the output direction is completely synchronized be-
fore transmitting data.
The module sets OutputSyncAck.
The output direction is synchronized, and the CPU can transmit data to the module.
Note:
Theoretically, data can already be transmitted in this cycle.
If the InputSyncBit is set and InputSequenceCounter has been increased by 1, the values in the enabled Rx bytes have to be accepted and acknowledged (see
also "Communication in the input direction").
The input direction is synchronized, and the module can transmit data to the CPU.
If a channel is synchronized, then the opposite station is ready to receive messages from the transmitter. Before
the transmitter can send data, it needs to first create a transmit array in order to meet FlatStream requirements.
The transmitting station must also generate a control byte for each segment created. This control byte contains
information about how the subsequent part of the data being transmitted should be processed. The position of the
next control byte in the data stream can vary. For this reason, it must be clearly defined at all times when a new
control byte is being transmitted. The first control byte is always in the first byte of the first sequence. All subsequent
positions are determined recursively.
FlatStream formula for calculating the position of the next control byte:
Position (of the next control byte) = Current position + 1 + Segment length
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The rest of the configuration corresponds to the default settings.
Default
Message 2:
Message 3:
C3 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C4 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
First, the messages must be split into segments. In the default configuration, it is important to ensure that each
sequence can hold an entire segment, including the associated control byte. The sequence is limited to the size of
the enable MTU. In other words, a segment must be at least 1 byte smaller than the MTU.
MTU = 7 bytes → Max. segment length = 6 bytes
• Message 1 (7 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C0 (control byte 0) C1 (control byte 1) C2 (control byte 2)
- SegmentLength (0) = 0 - SegmentLength (6) = 6 - SegmentLength (1) = 1
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (0) = 0 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 0 Control byte Σ 6 Control byte Σ 129
Table 85: FlatStream determination of the control bytes for the default configuration example (part 1)
C3 (control byte 3) C4 (control byte 4) C5 (control byte 5)
- SegmentLength (2) = 2 - SegmentLength (6) = 6 - SegmentLength (3) = 3
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 130 Control byte Σ 6 Control byte Σ 131
Table 86: FlatStream determination of the control bytes for the default configuration example (part 2)
When transmitting data, the transmit array must be generated in the application program. Sequences are then
transmitted one by one using FlatStream and received by the module.
Information:
Although all B&R modules with FlatStream communication always support the most compact trans-
missions in the output direction, it is recommended to use the same design for the transfer arrays in
both communication directions.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost.
(The relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individually.)
- Subsequent sequences can only be transmitted in the next bus cycle after the completion check has been carried out successfully.
Start
► diff = (OutputSequenceCounter -
OutputSequenceAck) AND 7
► limit = (OutputSequenceCounter -
LastValidAck) AND 7
(diff ≤ limit)
No OutputSequenceAck = No LastValidAck = Yes
AND (OutputSyncAck = 1)
AND (OutputSyncBit = 1) ? OutputSequenceCounter ? OutputSequenceCounter ?
Yes Yes No
No LastValidAck =
diff = 0 ?
OutputSequenceAck
Yes
LastValidAck = No
OutputSequenceAck = 0 ?
OutputSequenceAck
Yes
No OutputSequenceCounter = 0
More sequences to be sent ? OutputSequenceCounter = 1 OutputSyncBit = 1
LastValidAck = 0
Yes
When receiving data, the transmit array is generated by the module, transferred via FlatStream and must then
be reproduced in the receive array. The structure of the incoming data stream can be configured with the mode
register. The algorithm for receiving the data does not change in this regard.
PLC / Bus controller Module
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Start
► InputSequenceAck = InputSequenceCounter
Synchronisation
No
InputSyncBit = 1 ? ► RemainingSegmentSize = 0
► SegmentFlags = 0
Yes
No No
InputSyncAck = 1 ? InputSequenceAck > 0 ?
Yes Yes
MTU_Offset = 0 InputSyncAck = 1
(InputSequenceCounter – No
InputSequenceAck)
AND 0x07 = 1 ?
Yes
► RemainingSegmentSize =
Yes MTU_Data[MTU_Offset] AND 0b0011 1111
RemainingSegmentSize = 0 ? ► SegmentFlags =
MTU_Data[MTU_Offset] AND 0b1100 0000
No ► MTU_Offset = MTU_Offset + 1
No
No
Yes
► InputSequenceAck =
InputMTU_Size = MTU_Offset ?
InputSequenceCounter
No
Details
Information:
When transmitting with MultiSegmentMTUs, it is possible for several small messages to be part of one
sequence. In the program, it's important to make sure that a sufficient number of receive arrays can
be managed. The entire sequence must be accepted before it is possible to change the Acknowledge
register.
If a SequenceCounter is incremented by more than one value, then an error has occurred.
Note: This situation is very unlikely when operating without "Forward" functionality.
In this case, the receiver stops. All additional incoming sequences are ignored until the transmission with the correct
SequenceCounter is retried. This response prevents the transmitter from receiving any more acknowledgments for
transmitted sequences. The transmitter can identify the last successfully transmitted sequence from the opposite
station's SequenceAck and continue the transmission from this point.
Acknowledgments must be checked for validity.
If the receiver has successfully accepted a sequence, it must be acknowledged. The receiver takes on the Se-
quenceCounter value sent along with the transmission and matches the SequenceAck to it. The transmitter reads
the SequenceAck and registers the successful transmission. If the transmitter acknowledges a sequence that has
not yet been dispatched, then the transmission needs to be interrupted and the channel resynchronized. The syn-
chronization bits are reset and the current/incomplete message is discarded. It needs to be sent again once the
channel has been resynchronized.
FlatStream mode
Name:
FlatstreamMode
In the input direction, the transmit array is generated automatically. This register offers two options to the user
that allow an incoming data stream to have a more compact arrangement. Once enabled, the program code for
evaluation must be adapted accordingly.
Information:
All B&R modules that offer FlatStream mode support the options "Large segments" and "MultiSeg-
mentMTUs" in the output direction. Compact transmission only needs to be explicitly allowed in the
input direction.
Bit structure:
Bit Name Value Information
0 MultiSegmentMTU 0 Not allowed (default)
1 Allowed
1 Large segments 0 Not allowed (default)
1 Allowed
2-7 Reserved
Default
By default, both options relating to compact transmission in the input direction are disabled.
1. The module only forms segments that are at least one byte smaller than the enabled MTU. Each sequence
begins with a control byte so that the data stream is clearly structured and relatively easy to evaluate.
2. Since a FlatStream message can be of any length, the last segment of the message frequently doesn't fill up
all of the MTU's space. By default, the remaining bytes during this type of transfer cycle are not used.
C C C
- - -
ME0 ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
MultiSegmentMTUs allowed
With this option, the InputMTU is completely filled (if enough data is pending). The previously unfilled Rx bytes
transmit the next control bytes and their segments. This allows the enabled Rx bytes to be used more efficiently.
Bus cycle 1 Bus cycle 2 Bus cycle 3
C C C C
- -
ME0 ME1 ME0 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Information:
It is still possible to split up a message into several segments, however. If this option is used and
messages with more than 63 bytes occur, for example, then messages can still be split up among
several segments.
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Figure 181: Arrangement of messages in the MTU (large segments and MultiSegmentMTUs)
If the way messages are structured is changed, then the way data in the transmit/receive array is arranged is also
different. The following changes apply to the example given earlier.
MultiSegmentMTU
If MultiSegmentMTUs are allowed, then "open positions" in an MTU can be used. These "open positions" occur if
the last segment in a message does not fully use the entire MTU. MultiSegmentMTUs allow these bits to be used to
transmit the subsequent control bytes and segments. In the program sequence, the "nextCBPos" bit in the control
byte is set so that the receiver can correctly identify the next control byte.
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows transmission of MultiSegmentMTUs.
Message 1: Transmit/Receive array
Message 2: MultiSegmentMTU
Message 3:
C5 D2 D3 D4 D5 D6 D7 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C6 D8 D9 C0 - - - Sequence for bus cycle 4
First, the messages must be split into segments. As in the default configuration, it is important for each sequence
to begin with a control byte. The free bits in the MTU at the end of a message are filled with data from the following
message, however. With this option, the "nextCBPos" bit is always set if payload data is sent after the control byte.
MTU = 7 bytes → Max. segment length = 6 bytes
• Message 1 (7 bytes)
➯ First segment = Control byte + 2 bytes of data (MTU still has 2 open bytes)
• Message 3 (9 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (6) = 6 - SegmentLength (1) = 1 - SegmentLength (2) = 2
- nextCBPos (1) = 64 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 70 Control byte Σ 193 Control byte Σ 194
Table 87: FlatStream determination of the control bytes for the MultiSegmentMTU example (part 1)
Warning!
The second sequence must have been completely processed before it can be acknowledged with Se-
quenceAck. In this example, there are three different segments within the second sequence, i.e. the
program must include enough receive arrays to handle this situation.
C4 (control byte 4) C5 (control byte 5) C6 (control byte 6)
- SegmentLength (1) = 1 - SegmentLength (6) = 6 - SegmentLength (2) = 2
- nextCBPos (6) = 6 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 0 - MessageEndBit (1) = 128
Control byte Σ 7 Control byte Σ 70 Control byte Σ 194
Table 88: FlatStream determination of the control bytes for the MultiSegmentMTU example (part 2)
Large segments
Segments are limited to a maximum of 63 bytes. This means they can be larger than the active MTU. These large
segments are divided among several sequences when transmitted. It is possible for sequences to be completely
filled with payload data and not have a control byte.
Information:
It is still possible to subdivide a message into several segments so that the size of a data packet does
not also have to be limited to 63 bytes.
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows the transmission of large segments.
Message 3:
C2 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C3 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 89: FlatStream determination of the control bytes for the large segment example
Message 3:
D3 D4 D5 D6 D7 D8 D9 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C0 - - - - - - Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 90: FlatStream determination of the control bytes for the large segment and MultiSegmentMTU example
Forward functionality is a method that can be used to substantially increase the FlatStream data rate. The basic
principle is also used in other technical areas such as "pipelining" for microprocessors.
Operating principle
X2X Link communication cycles through five different steps to transmit a FlatStream sequence. At least five bus
cycles are therefore required to successfully transfer the sequence.
Step I Step II Step III Step IV Step V
Actions Transfer sequence from Cyclic matching of MTU and Append sequence to re- Cyclic matching of Check SequenceAck
transmit array, module buffer ceive array MTU and module buffer
increase Sequence- Adjust SequenceAck
Counter
Resource Transmitter Bus system Recipient Bus system Transmitter
(task to transmit) (direction 1) (task to receive) (direction 2) (task for Ack checking)
Sequence 3 ...
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Configuration
The Forward function only has to be enabled for the input direction. Two additional configuration registers are
available for doing so. FlatStream modules have been optimized in such a way that they support this function. In
the output direction, the Forward function can be used as soon as the size of the OutputMTU is specified.
Name:
Forward
With the "Forward" register, the user specifies how many unacknowledged sequences the module is allowed to
transmit.
Recommendation:
X2X Link: Max. 5
POWERLINK: Max. 7
Data type Value
USINT 1 to 7
Default: 1
Delay time
Name:
ForwardDelay
The "ForwardDelay" register is used to specify the delay time in µs. This is the amount of time the module has
to wait after sending a sequence until it is allowed to write new data to the MTU in the following bus cycle. The
program routine for receiving sequences from a module can therefore be run in a task class whose cycle time is
slower than the bus cycle.
Data type Value
UINT 0 to 65,535 [µs]
Default: 0
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Figure 186: Effect of ForwardDelay when using FlatStream communication with the Forward function
In the program, it is important to make sure that the CPU is processing all of the incoming InputSequences and In-
putMTUs. The ForwardDelay value causes delayed acknowledgment in the output direction and delayed reception
in the input direction. In this way, the CPU has more time to process the incoming InputSequence or InputMTU.
The basic algorithm for transmitting and receiving data remains the same. With the Forward function, up to seven
unacknowledged sequences can be transmitted. Sequences can be transmitted without having to wait for the
previous message to be acknowledged. Since the delay between writing and response is eliminated, a considerable
amount of additional data can be transferred in the same time window.
Algorithm for transmitting
Cyclic status query:
- The Module monitors the OutputSequenceCounter.
0) Cyclic checks:
- The CPU must check OutputSyncAck.
→ If OutputSyncAck = 0: Reset the OutputSyncBit and resynchronize the channel.
- The CPU must check whether OutputMTU is enabled.
→ If OutputSequenceCounter > OutputSequenceAck + 7, then it is not enabled because the last sequence has not yet been acknowledged.
1) Preparation (create transmit array):
- The CPU must split up the message into valid segments and create the necessary control bytes.
- The CPU must add the segments and control bytes to the transmit array.
2) Transmit:
- The CPU must transfer the current part of the transmit array to the OutputMTU.
- The CPU must increase the OutputSequenceCounter for the sequence to be accepted by the module.
- The CPU can then transmit in the next bus cycle if the MTU has been enabled.
The module responds since OutputSequenceCounter > OutputSequenceAck:
- The module accepts data from the internal receive buffer and appends it to the end of the internal receive array.
- The module is acknowledged and the currently received value of the OutputSequenceCounter is transferred to OutputSequenceAck.
- The module requests the status cyclically again.
3) Completion (acknowledgment):
- The CPU must check OutputSequenceAck cyclically.
→ A sequence is only considered to have been transmitted successfully if it has been acknowledged via OutputSequenceAck. In order to detect potential trans-
mission errors in the last sequence as well, it is important to make sure that the algorithm is run through long enough.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost (the relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individ-
ually).
Details/Background
1. Illegal SequenceCounter size (counter offset)
Error situation: MTU not enabled
If the difference between SequenceCounter and SequenceAck is larger than allowed during transmission,
then a transmission error has occurred. In this case, all unacknowledged sequences must be repeated with
the old SequenceCounter value.
2. Checking an acknowledgment
After an acknowledgment has been received, a check must verify whether the acknowledged sequence has
been transmitted and had not yet been unacknowledged. If a sequence has been acknowledged more than
once, then a fatal error has occurred. The channel must be closed and resynchronized (same behavior as
when not using Forward).
Information:
In exceptional cases, the module can increment OutputSequenceAck by more than 1 when using
Forward.
This is not an error. The CPU is permitted to consider all sequences up to the one being acknowl-
edged as having been transmitted successfully.
In industrial environments, it is often the case that many different devices from various manufacturers are being
used side by side. The electrical and/or electromagnetic properties of these technical devices can sometimes cause
them to interfere with one another. These kinds of situations can be reproduced and protected against in laboratory
conditions only to a certain point.
Precautions have been taken for X2X Link transmissions if this type of interference occurs. For example, if an
invalid checksum occurs, the I/O system will ignore the data from this bus cycle and the receiver receives the last
valid data once more. With conventional (cyclic) data points, this error can often be ignored. In the following cycle,
the same data point is again retrieved, adjusted and transmitted.
Using Forward functionality with FlatStream communication makes this situation more complex. The receiver re-
ceives the old data again in this situation as well, i.e. the previous values for SequenceAck/SequenceCounter and
the old MTU.
Loss of acknowledgment (SequenceAck)
If a SequenceAck value is lost, then the MTU was already transmitted properly. For this reason, the receiver is per-
mitted to continue processing with the next sequence. The SequenceAck is aligned with the associated Sequence-
Counter and sent back to the transmitter. Checking the incoming acknowledgments shows that all sequences up
to the last one acknowledged have been transmitted successfully (see sequences 1 and 2 in the image).
Loss of transmission (SequenceCounter, MTU)
If a bus cycle drops out and the SequenceCounter value and/or filled MTU are lost, then no data reaches the
receiver. At this point, the transmission routine is not yet affected by the error. The time-controlled MTU is released
again and can be rewritten to.
The receiver receives SequenceCounter values that have been incremented several times. For the receive array
to be put together correctly, the receiver is only allowed to process transmissions whose SequenceCounter has
been increased by one. The incoming sequences must be ignored, i.e. the receiver stops and no longer transmits
back any acknowledgments.
If the maximum number of unacknowledged sequences has been sent and no acknowledgments are returned, the
transmitter must repeat the affected SequenceCounter and associated MTUs (see sequence 3 and 4 in the image).
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 EMC Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
When using FlatStream communication, the module acts as a bridge between the X2X master and an intelligent
field device connected to the module. FlatStream mode can be used for either point-to-point connections as well
as for multidrop systems. Specific algorithms such as timeout and checksum monitoring are usually managed
automatically. During normal operation, the user does not have access to these details.
HART is considered a master-slave network where half-duplex communication takes place asynchronously. Vari-
ous features have been included to ensure that signals are transmitted without errors.
For example, the user can increase the length of the preamble, thus making the transmission more secure. How-
ever, this also has an effect on the percentage of payload data and overhead.
Additional information about HART can be found at www.HARTcomm.org.
Operation
The module has two independent channels. When using FlatStream, the channel number must therefore be spec-
ified. The general structure of a FlatStream frame is extended as follows.
Input/Output sequence Tx/Rx bytes
(unchanged) Control byte Channel number HART frame
(unchanged) (without preamble and checksum)
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 OSPValid 0 Request OSP operation (after initial start or module in Standby)
1 Request normal operation
1-7 Reserved 0
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the relevant
task in the master CPU. However, an output still occurs depending on the configuration of the OSP
replacement value.
Name:
CfgOSPMode01 to CfgOSPMode02
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue01 to CfgOSPValue02
This register contains the analog output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
Corresponds to Corresponds to AnalogOutput0x
AnalogOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Analog outputs 1 ms
4.4.4 X20AO2622
The module is equipped with two outputs with 13-bit (including sign) digital converter resolution. It is possible to
select between the current and voltage signal using different connection terminal points.
This module is designed for X20 6-pin terminal blocks. If needed (e.g. for logistical reasons), the 12-pin terminal
block can also be used.
• 2 analog outputs
• Either current or voltage signal possible
• 13-bit digital converter resolution
Product ID X20AO2622
Short description
I/O module 2 analog outputs ±10 V or 0 to 20 mA / 4 to 20 mA 1)
General information
B&R ID code 0x1BA2
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Analog outputs
Output ±10 V or 0 to 20 mA / 4 to 20 mA, via different terminal connections 1)
Max. output current 10 mA at voltages >5 V
15 mA at voltages <5 V
Digital converter resolution
Voltage ±12-bit
Current 12 Bit
Conversion time 200 µs for all outputs
Settling time for output changes over entire range 1 ms
Power on/off behavior Internal enable relay for booting
Max. error at 25°C
Voltage
Gain 0.150% 2)
Offset 0.050% 3)
Current
Gain 0.150% 2)
Offset 0.050% 3)
Output protection Short circuit protection
Output format
Voltage INT 0x8001 - 0x7FFF / 1 LSB = 0x0010 = 4.882 mV
Current INT 0x8001 - 0x7FFF / 1 LSB = 0x0010 = 9.766 µA
Load per channel
Voltage Max. ±10 mA, load ≥1 kΩ
Current Load max. 600 Ω (Rev. ≥ J0); 500 Ω (Rev. < J0)
Short circuit protection Current limiting ±40 mA
Output filter 1st-order low pass / cutoff frequency 10 kHz
Max. gain drift
Voltage 0.020 %/°C 2)
Current 0.020 %/°C 2)
Max. offset drift
Voltage 0.032 %/°C 3)
Current 0.032 %/°C 3)
Error caused by load change
Voltage Max. 0.11%, from 10 MΩ → 1 kΩ, resistive
Current Max. 0.50%, from 1 Ω → 600 Ω, resistive
Non-linearity <0.007% 4)
Isolation voltage between channel and bus 500 Veff
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
e+r Red on / Green single flash Invalid firmware
1-2 Orange Off Value = 0
On Value ≠ 0
4.4.4.5 Pinout
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
r e
X20 AO 2622
1 2
AO + 1 I AO + 2 I
AO + 1 U AO + 2 U
AO - 1 U/I AO - 2 U/I
AO
Voltage Current
Load
+
Load
+24 VDC +24 VDC
GND GND
AO + x I
Reset
I/O status
AO + x U
1) The offset specifies the position of the register within the CAN object.
X2X
I/O
0 1 2 3 4 5
Values output in the next cycle
Value transfer
0 1 2 3 4 5
X2X
I/O
0 1 2 3 4 5
Values output in the same cycle
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
Name:
AnalogOutput01 to AnalogOutput02
These registers provide the standardized output values. Once a permitted value is received the module outputs
the respective current or voltage.
Data type Value Information
INT -32768 to 32767 Voltage signal -10 to 10 VDC
0 to 32767 Current signal 0 to 20 mA
0 to 32767 Current signal 4 to 20 mA1)
Name:
ConfigOutput01
This register can be used to set the channel type of the outputs.
Each channel is capable of handling either current or voltage signals. The type of signal is determined by the
connection terminals used. Since current and voltage require different adjustment values, it is also necessary to
configure the desired type of output signal. The following output signals can be set:
• ±10 V voltage signal (default)
• 0 to 20 mA current signal
• 4 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 1 0 Voltage signal
1 Current signal, measurement range corresponding to bit 4
1 Channel 2 0 Voltage signal
1 Current signal, measurement range corresponding to bit 5
2-3 Reserved 0
4 Channel 1: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
5 Channel 2: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
6-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
250 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
300 μs
4.4.5 X20AO2632
The module is equipped with two outputs with 16-bit (including sign) digital converter resolution. It is possible to
select between the current and voltage signal using different connection terminal points.
This module is designed for X20 6-pin terminal blocks. If needed (e.g. for logistical reasons), the 12-pin terminal
block can also be used.
• 2 analog outputs
• Either current or voltage signal possible
• 16-bit digital converter resolution
Product ID X20AO2632
Short description
I/O module 2 analog outputs, ±10 V or 0 to 20 mA
General information
B&R ID code 0x1BA4
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Analog outputs
Output ±10 V or 0 to 20 mA, via different terminal connections
Digital converter resolution
Voltage ±15-bit
Current 15 Bit
Conversion time 50 µs for all outputs
Settling time for output changes over entire range 500 μs (Rev. <H0: 1 ms)
Power on/off behavior Internal enable relay for booting
4.4.5.5 Pinout
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
r e
X20 AO 2632
1 2
AO + 1 I AO + 2 I
AO + 1 U AO + 2 U
AO - 1 U/I AO - 2 U/I
AO
Voltage Current
Load Load
AO + x I
Reset
I/O status
AO + x U
1) The offset specifies the position of the register within the CAN object.
The module provides two analog outputs. Each channel can output a voltage range of ±10 V or a current range
of 0 to 20 mA.
The module also has a time-based watchdog monitor. The user can activate this feature channel-by-channel as
needed.
Each channel is configured independently. The user can also define an optional time-based monitor. To make this
possible, two watchdog timers were implemented, which can be assigned to the outputs.
Name:
ConfigOutput01
This register can be used to set the channel type of the outputs.
Each channel is capable of handling either current or voltage signals. The type of signal is determined by the
connection terminals used. Since current and voltage require different adjustment values, it is also necessary to
configure the desired type of output signal. The following output signals can be set:
• ±10 V voltage signal (default)
• 0 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-7 Reserved 0
8 Channel 1 0 Voltage signal
1 Current signal
9 Channel 2 0 Voltage signal
1 Current signal
10 - 15 Reserved 0
Name:
Cfo_Channel01TimeMode to Cfo_Channel02TimeMode
This register is used to activate or configure the time-based watchdog monitor for the analog output channels.
Possibilities per channel:
• Validation timer data type: General choice 16 or 32 bit
• Validation window: The maximum value can be further limited within the data type.
• Timer allocation: A separate timer is available for each channel. However, all channels can be configured
with the same validation timer, whereby the same settings must be made for the data type and window
in the TimeMode registers.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-4 Max. validation time 00000 Disabled
00001 2 µs
00010 4 µs
00011 8 µs
... ...
11111 2,147,483,648 µs (~35 min)
5-7 Reserved 0
8 Timer allocation 0 ValidationTimer01 (default for channel 1)
1 ValidationTimer02 (default for channel 2)
9 - 14 Reserved 0
15 Time format 0 16-bit
1 32-bit
In standard mode, the module's outputs are enabled. Based on the configuration and AnalogOutput value, they
output the corresponding current or voltage.
If the application requires time-based monitoring of the outputs, then a validation timer can be assigned to each
channel. The validation timer register assigns a validity duration to the current output value. When validation is
enabled, the module compares the validation time with the Nettime of the X2X Link. If the transferred validity
duration is exceeded, the module disables the channel and resets the output. The "safety shutdown" state will not
be reset until a new and valid validation time has been transferred. If enabled, the module reports which state it
is currently in via the channel's error status bit.
If the value of the validation timer is incremented in each task cycle, the valid validation time will be calculated
as follows:
Nettime of the X2X Link master (which the module is connected to)
+ Timespan for transferring data from the X2X Link master to the CPU (higher-level system)
+ Cycle time of task class (including tolerance)
+ Timespan for transferring the data from the CPU to the module
+ Timespan allowed by the application (e.g. for tolerating failure of an X2X Link cycle)
= Valid validation time
The AnalogOutputEnableByte is enabled during time-based monitoring. If the timer expires prematurely, the corre-
sponding bit in the AnalogOutputOkayByte is reset and the output drops out. This provides an easy way to achieve
a defined state.
Name:
AnalogOutput01 to AnalogOutput02
These registers provide the standardized output values. Once a permitted value is received, the module outputs
the respective current or voltage.
Information:
The value "0" disables the channel status LED.
Data type Value
INT -32767 to 32767 Voltage; Bus controller default setting: 0
0 to 32767 Current
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
ValidationTimer01 to ValidationTimer02
When an output is being monitored, these registers must provide the timestamp which, when reached, will cause
the output to shut down automatically. The values must be provided as signed 2-byte or 4-byte values.
Data type Values [µs]
INT -32768 to 32767 Nettime timestamp of the current output value
DINT -2,147,483,648 Nettime timestamp of the current output value
to 2,147,483,647
Name:
AnalogOutput01Enable to AnalogOutput02Enable
AnalogOutput01EnableReadback to AnalogOutput02EnableReadback
The "OutputEnable" byte is only needed for the channels with activated time-based monitoring. The individual bits
are used to enable/disable the respective channels. To receive reliable feedback about the current state of the
module, the byte was also implemented so that it can be read cyclically.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0 AnalogOutput01Enable 0 Output deactivated
AnalogOutput01EnableReadback 1 Output activated
1 AnalogOutput02Enable 0 Output deactivated
AnalogOutput02EnableReadback 1 Output activated
2-7 Reserved 0
Name:
AnalogOutput01OK to AnalogOutput02OK
These registers are only needed for channels with activated time-based monitoring. The individual bits report
whether the respective channel is actually generating the required voltage or current.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0 AnalogOutput01OK 0 Electrical signal deactivated
1 Electrical signal activated
1 AnalogOutput02OK 0 Electrical signal deactivated
1 Electrical signal activated
2-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
200 µs
4.4.6 X20AO2632-1
The module is equipped with two outputs with 16-bit (including sign) digital converter resolution. It is possible to
select between the current and voltage signal using different connection terminal points.
This module is designed for X20 6-pin terminal blocks. If needed (e.g. for logistical reasons), the 12-pin terminal
block can also be used.
• 2 analog outputs
• Either current or voltage signal possible
• Extended signal range
• 16-bit digital converter resolution
Product ID X20AO2632-1
Short description
I/O module 2 analog outputs, ±11 V or 0 to 22 mA
General information
B&R ID code 0xC36E
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 1.25 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Analog outputs
Output ±11 V or 0 to 22 mA, via different terminal connections
Digital converter resolution
Voltage ±15-bit
Current 15-bit
Conversion time 50 µs for all outputs
Settling time for output changes over entire range 500 µs
Power on/off behavior Internal enable relay for booting
4.4.6.5 Pinout
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
r e
X20 AO 2632-1
1 2
AO + 1 I AO + 2 I
AO + 1 U AO + 2 U
AO - 1 U/I AO - 2 U/I
AO
Voltage Current
Load Load
AO + x I
Reset
I/O status
AO + x U
1) The offset specifies the position of the register within the CAN object.
The module provides two analog outputs. Each channel can output a voltage range of ±11 V or a current range
of 0 to 22 mA.
The module also has a time-based watchdog monitor. The user can activate this feature channel-by-channel as
needed.
Each channel is configured independently. The user can also define an optional time-based monitor. To make this
possible, two watchdog timers were implemented, which can be assigned to the outputs.
Name:
ConfigOutput01
This register can be used to set the channel type of the outputs.
Each channel is capable of handling either current or voltage signals. The type of signal is determined by the
connection terminals used. Since current and voltage require different adjustment values, it is also necessary to
configure the desired type of output signal. The following output signals can be set:
• ±11 V voltage signal (default)
• 0 to 22 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-7 Reserved 0
8 Channel 1 0 Voltage signal
1 Current signal
9 Channel 2 0 Voltage signal
1 Current signal
10 - 15 Reserved 0
Name:
Cfo_Channel01TimeMode to Cfo_Channel02TimeMode
This register is used to activate or configure the time-based watchdog monitor for the analog output channels.
Possibilities per channel:
• Validation timer data type: General choice 16 or 32 bit
• Validation window: The maximum value can be further limited within the data type.
• Timer allocation: A separate timer is available for each channel. However, all channels can be configured
with the same validation timer, whereby the same settings must be made for the data type and window
in the TimeMode registers.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-4 Max. validation time 00000 Disabled
00001 2 µs
00010 4 µs
00011 8 µs
... ...
11111 2,147,483,648 µs (~35 min)
5-7 Reserved 0
8 Timer allocation 0 ValidationTimer01 (default for channel 1)
1 ValidationTimer02 (default for channel 2)
9 - 14 Reserved 0
15 Time format 0 16-bit
1 32-bit
In standard mode, the module's outputs are enabled. Based on the configuration and AnalogOutput value, they
output the corresponding current or voltage.
If the application requires time-based monitoring of the outputs, then a validation timer can be assigned to each
channel. The validation timer register assigns a validity duration to the current output value. When validation is
enabled, the module compares the validation time with the Nettime of the X2X Link. If the transferred validity
duration is exceeded, the module disables the channel and resets the output. The "safety shutdown" state will not
be reset until a new and valid validation time has been transferred. If enabled, the module reports which state it
is currently in via the channel's error status bit.
If the value of the validation timer is incremented in each task cycle, the valid validation time will be calculated
as follows:
Nettime of the X2X Link master (which the module is connected to)
+ Timespan for transferring data from the X2X Link master to the CPU (higher-level system)
+ Cycle time of task class (including tolerance)
+ Timespan for transferring the data from the CPU to the module
+ Timespan allowed by the application (e.g. for tolerating failure of an X2X Link cycle)
= Valid validation time
The AnalogOutputEnableByte is enabled during time-based monitoring. If the timer expires prematurely, the corre-
sponding bit in the AnalogOutputOkayByte is reset and the output drops out. This provides an easy way to achieve
a defined state.
Name:
AnalogOutput01 to AnalogOutput02
These registers provide the standardized output values. Once a permitted value is received, the module outputs
the respective current or voltage.
Information:
The value "0" disables the channel status LED.
Data type Value
INT -32767 to 32767 Voltage; Bus controller default setting: 0
0 to 32767 Current
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
ValidationTimer01 to ValidationTimer02
When an output is being monitored, these registers must provide the timestamp which, when reached, will cause
the output to shut down automatically. The values must be provided as signed 2-byte or 4-byte values.
Data type Values [µs]
INT -32768 to 32767 Nettime timestamp of the current output value
DINT -2,147,483,648 Nettime timestamp of the current output value
to 2,147,483,647
Name:
AnalogOutput01Enable to AnalogOutput02Enable
AnalogOutput01EnableReadback to AnalogOutput02EnableReadback
The "OutputEnable" byte is only needed for the channels with activated time-based monitoring. The individual bits
are used to enable/disable the respective channels. To receive reliable feedback about the current state of the
module, the byte was also implemented so that it can be read cyclically.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0 AnalogOutput01Enable 0 Output deactivated
AnalogOutput01EnableReadback 1 Output activated
1 AnalogOutput02Enable 0 Output deactivated
AnalogOutput02EnableReadback 1 Output activated
2-7 Reserved 0
Name:
AnalogOutput01OK to AnalogOutput02OK
These registers are only needed for channels with activated time-based monitoring. The individual bits report
whether the respective channel is actually generating the required voltage or current.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0 AnalogOutput01OK 0 Electrical signal deactivated
1 Electrical signal activated
1 AnalogOutput02OK 0 Electrical signal deactivated
1 Electrical signal activated
2-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
200 µs
4.4.7 X20AO4622
The module is equipped with four outputs with 13-bit (including sign) digital converter resolution. It is possible to
select between the current and voltage signal using different connection terminal points.
• 4 analog outputs
• Either current or voltage signal possible
• 13-bit digital converter resolution
Product ID X20AO4622
Short description
I/O module 4 analog outputs ±10 V or 0 to 20 mA / 4 to 20 mA 1)
General information
B&R ID code 0x1BA3
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 1.8 W (Rev. ≥ J0); 2.2 W (Rev. < J0)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Analog outputs
Output ±10 V or 0 to 20 mA / 4 to 20 mA, via different terminal connections 1)
Max. output current 10 mA at voltages >5 V
15 mA at voltages <5 V
Digital converter resolution
Voltage ±12-bit
Current 12 Bit
Conversion time 300 µs for all outputs
Settling time for output changes over entire range 500 µs
Power on/off behavior Internal enable relay for booting
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
e+r Red on / Green single flash Invalid firmware
1-4 Orange Off Value = 0
On Value ≠ 0
4.4.7.5 Pinout
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
r e
X20 AO 4622
1 2
3 4
AO + 1 I AO + 2 I
AO + 1 U AO + 2 U
AO - 1 U/I AO - 2 U/I
AO + 3 I AO + 4 I
AO + 3 U AO + 4 U
AO - 3 U/I AO - 4 U/I
AO
Voltage Current
Load
+
Load
Load
+
Load
AO + x I
Reset
I/O status
AO + x U
To ensure proper operation, the following items must be taken into consideration:
• The following derating listings must be taken into consideration
• For mixed operation with one current output, the average of both derating curves should be used
• For mixed operation with two or three current outputs, the derating for the current outputs should be used
Horizontal installation
From revision J0 Before revision J0
Voltage output Voltage output
10 10
8 8
Load [kΩ]
6 6
Load [kΩ]
Prohibited Prohibited
range range
4 4
2 2
1 1
-20 -10 20 30 40 50 60 0 10 20 30 40 50
600 500
500 400
Working resistance [Ω]
Working resistance [Ω]
400 300
Prohibited
Prohibited range
300 200
range
200 100
100 0
0 10 20 30 40 50
0 Ambient temperature [°C]
-20 -10 20 30 40 50 60
Vertical installation
From revision J0 Before revision J0
Voltage output Voltage output
10 10
8 8
Load [kΩ]
6 Prohibited 6 Prohibited
Load [kΩ]
range range
4 4
2 2
1 1
-20 -10 20 30 40 50 60 0 10 20 30 40 50
600 500
500 400
400 300
Prohibited
Prohibited range
300 200
range
200 100
100 0
0 10 20 30 40 50
0
Ambient temperature [°C]
-20 -10 20 30 40 50 60
1) The offset specifies the position of the register within the CAN object.
X2X
I/O
0 1 2 3 4 5
Values output in the next cycle
Value transfer
0 1 2 3 4 5
X2X
I/O
0 1 2 3 4 5
Values output in the same cycle
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
Name:
AnalogOutput01 to AnalogOutput04
These registers provide the standardized output values. Once a permitted value is received the module outputs
the respective current or voltage.
Data type Value Information
INT -32768 to 32767 Voltage signal -10 to 10 VDC
0 to 32767 Current signal 0 to 20 mA
0 to 32767 Current signal 4 to 20 mA1)
Name:
ConfigOutput01
This register can be used to set the channel type of the outputs.
Each channel is capable of handling either current or voltage signals. The type of signal is determined by the
connection terminals used. Since current and voltage require different adjustment values, it is also necessary to
configure the desired type of output signal. The following output signals can be set:
• ±10 V voltage signal (default)
• 0 to 20 mA current signal
• 4 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Voltage signal
1 Current signal, measurement range corresponding to bit 4
... ...
3 Channel 4 0 Voltage signal
1 Current signal, measurement range corresponding to bit 7
4 Channel 1: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
... ...
7 Channel 4: Current measurement range 0 0 to 20 mA current signal
1 4 to 20 mA current signal
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
250 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
400 μs
4.4.8 X20AO4632
The module is equipped with four outputs with 16-bit (including sign) digital converter resolution. It is possible to
select between the current and voltage signal using different connection terminal points.
• 4 analog outputs
• Either current or voltage signal possible
• 16-bit digital converter resolution
Product ID X20AO4632
Short description
I/O module 4 analog outputs, ±10 V or 0 to 20 mA
General information
B&R ID code 0x1BA5
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 1.8 W (Rev. ≥ J0); 2.2 W (Rev. < J0)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Analog outputs
Output ±10 V or 0 to 20 mA, via different terminal connections
Digital converter resolution
Voltage ±15-bit
Current 15 Bit
Conversion time 50 µs for all outputs
Settling time for output changes over entire range 500 µs
Power on/off behavior Internal enable relay for booting
4.4.8.5 Pinout
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
r e
X20 AO 4632
1 2
3 4
AO + 1 I AO+ 2 I
AO+ 1 U AO+ 2 U
AO + 3 I AO + 4 I
AO + 3 U AO + 4 U
AO - 3 U/I AO - 4 U/I
AO
Voltage Current
Load
+
Load
Load
+
Load
AO + x I
Reset
I/O status
AO + x U
To ensure proper operation, the following items must be taken into consideration:
• The following derating listings must be taken into consideration
• For mixed operation with one current output, the average of both derating curves should be used
• For mixed operation with two or three current outputs, the derating for the current outputs should be used
Horizontal installation
From revision J0 Before revision J0
Voltage output Voltage output
10 10
8 8
Load [kΩ]
6 6
Load [kΩ]
Prohibited Prohibited
range range
4 4
2 2
1 1
-20 -10 20 30 40 50 60 0 10 20 30 40 50
600 500
500 400
Working resistance [Ω]
Working resistance [Ω]
400 300
Prohibited
Prohibited range
300 200
range
200 100
100 0
0 10 20 30 40 50
0 Ambient temperature [°C]
-20 -10 20 30 40 50 60
Vertical installation
From revision J0 Before revision J0
Voltage output Voltage output
10 10
8 8
Load [kΩ]
6 Prohibited 6 Prohibited
Load [kΩ]
range range
4 4
2 2
1 1
-20 -10 20 30 40 50 60 0 10 20 30 40 50
600 500
500 400
400 300
Prohibited
Prohibited range
300 200
range
200 100
100 0
0 10 20 30 40 50
0
Ambient temperature [°C]
-20 -10 20 30 40 50 60
1) The offset specifies the position of the register within the CAN object.
Name:
ConfigOutput01
This register can be used to set the channel type of the outputs.
Each channel is capable of handling either current or voltage signals. The type of signal is determined by the
connection terminals used. Since current and voltage require different adjustment values, it is also necessary to
configure the desired type of output signal. The following output signals can be set:
• ±10 V voltage signal (default)
• 0 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-7 Reserved 0
8 Channel 1 0 Voltage signal
1 Current signal
... ...
11 Channel 4 0 Voltage signal
1 Current signal
12 - 15 Reserved 0
Name:
AnalogOutput01 to AnalogOutput04
These registers provide the standardized output values. Once a permitted value is received, the module outputs
the respective current or voltage.
Information:
The value "0" disables the channel status LED.
Data type Value
INT -32767 to 32767 Voltage; Bus controller default setting: 0
0 to 32767 Current
Name:
AnalogOutputDelayed00 to AnalogOutputDelayed03
These registers contain the values with which the analog outputs are overwritten after the delay configured with
OutputDelayConfig0x has expired.
Data type Value Output Signal
INT -32768 to 32767 Voltage signal -10 VDC to 10 VDC
0 to 32767 Current signal 0 mA to 20 mA
Name:
OutputDelayConfig00 to OutputDelayConfig01
Two configurations independent from each other can be created using these registers.
The delay time after which AnalogOutputDelay0x should overwrite the channel can be configured using bits 0 to
13. Using bits 14 and 15, the channel is determined for which the configuration is valid.
Each channel can only be overwritten once. No additional channel can be overwritten while the respective time
is running.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0 - 13 Delay time for the selected channel x Time in μs
14 - 15 Channel 00 Analog output 01
01 Analog output 02
10 Analog output 03
11 Analog output 04
Name:
AnalogOutputLatchTime00 to AnalogOutputLatchTime01
These registers can be used to read when the respective overwrite value was actually written on the output.
Data type Value
UINT Actual delay time
Name:
Error
There are some limitations because two timers are used. This register is available to the user for reporting these
potential errors.
The error bits are deleted as soon as a valid state is reset.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0 Analog output 01 0 OK
1 Has already been overwritten
... ...
3 Analog output 04 0 OK
1 Has already been overwritten
4 Timer 01 0 OK
1 Already in use
5 Timer 02 0 OK
1 Already in use
6 Timer 01 and 02 0 OK
1 Both timers refer to the same channel number
7 - 15 Reserved
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
200 µs
4.4.9 X20AO4632-1
The module is equipped with four outputs with 16-bit (including sign) digital converter resolution. It is possible to
select between the current and voltage signal using different connection terminal points.
• 4 analog outputs
• Either current or voltage signal possible
• Extended signal range
• 16-bit digital converter resolution
Product ID X20AO4632-1
Short description
I/O module 4 analog outputs, ±11 V or 0 to 22 mA
General information
B&R ID code 0xC36F
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
I/O internal 2.15 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
GOST-R Yes
Analog outputs
Output ±11 V or 0 to 22 mA, via different terminal connections
Digital converter resolution
Voltage ±15-bit
Flow 15-bit
Conversion time 50 µs for all outputs
Settling time for output changes over entire range 500 µs
Power on/off behavior Internal enable relay for booting
Max. error at 25°C
Voltage
Gain 0.050% 1)
Offset 0.015% 2)
Flow
Gain 0.080% 1)
Offset 0.050% 2)
Output protection Short circuit protection
4.4.9.5 Pinout
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
r e
X20 AO 4632-1
1 2
3 4
AO + 1 I AO + 2 I
AO + 1 U AO + 2 U
AO - 1 U/I AO - 2 U/I
AO + 3 I AO + 4 I
AO + 3 U AO + 4 U
AO - 3 U/I AO - 4 U/I
AO
Voltage Current
Load
+
Load
Load
+
Load
AO + x I
Reset
I/O status
AO + x U
To ensure proper operation, the following items must be taken into consideration:
• The following derating listings must be taken into consideration
• For mixed operation with one current output, the average of both derating curves should be used
• For mixed operation with two or three current outputs, the derating for the current outputs should be used
X20 system User's Manual 3.10 491
X20 system modules • Analog output modules • X20AO4632-1
Horizontal installation
Voltage output
Horizontal installation
10
Load [k Ω] 6 Prohibited
Range
4
2
1
-20 -10 0 10 20 30 40 50
Figure 192: Derating the load with a voltage output and horizontal mounting
Current output
Horizontal installation
600
500
Working resistance [ Ω]
400
Prohibited
300
Range
200
100
0
-20 -10 0 10 20 30 40 50
Figure 193: Derating the load with a current output and horizontal mounting
Vertical installation
Voltage output
Vertical installation
10
Load [k Ω ] 6 Prohibited
Range
4
2
1
-20 -10 0 10 20 30 40 50
Figure 194: Derating the load with a voltage output and vertical mounting
Current output
Vertical installation
600
500
Working resistance [Ω]
400
Prohibited
300
Range
200
100
0
-20 -10 0 10 20 30 40 50
Figure 195: Derating the load with a current output and vertical mounting
1) The offset specifies the position of the register within the CAN object.
The module provides four analog outputs. Each channel can output a voltage range of ±11 V or a current range
of 0 to 22 mA.
The module also has a time-based watchdog monitor. The user can activate this feature on a channel-by-channel
basis as needed.
Each channel is configured independently. The user can also define an optional time-based monitor. To make this
possible, four watchdog timers were implemented, which can be assigned to the outputs.
Name:
ConfigOutput01
This register can be used to set the channel type of the outputs.
Each channel is capable of handling either current or voltage signals. The type of signal is determined by the
connection terminals used. Since current and voltage require different adjustment values, it is also necessary to
configure the desired type of output signal. The following output signals can be set:
• ±11 V voltage signal (default)
• 0 to 22 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-7 Reserved 0
8 Channel 1 0 Voltage signal
1 Current signal
... ...
11 Channel 4 0 Voltage signal
1 Current signal
12 - 15 Reserved 0
Name:
Cfo_Channel01TimeMode to Cfo_Channel04TimeMode
This register is used to activate or configure the time-based watchdog monitor for the analog output channels.
Possibilities per channel:
• Validation timer data type: General choice 16 or 32 bit
• Validation window: The maximum value can be further limited within the data type.
• Timer allocation: A separate timer is available for each channel. However, all channels can be configured
with the same validation timer, whereby the same settings must be made for the data type and window
in the TimeMode registers.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-4 Max. validation time 00000 Disabled
00001 2 µs
00010 4 µs
00011 8 µs
... ...
11111 2,147,483,648 µs (~35 min)
5-7 Reserved 0
8-9 Timer allocation 00 ValidationTimer01 (default for channel 1)
01 ValidationTimer02 (default for channel 2)
10 ValidationTimer03 (default for channel 3)
11 ValidationTimer04 (default for channel 4)
10 - 14 Reserved 0
15 Time format 0 16-bit
1 32-bit
In standard mode, the module's outputs are enabled. Based on the configuration and AnalogOutput value, they
output the corresponding current or voltage.
If the application requires time-based monitoring of the outputs, then a validation timer can be assigned to each
channel. The validation timer register assigns a validity duration to the current output value. When validation is
enabled, the module compares the validation time with the Nettime of the X2X Link. If the transferred validity
duration is exceeded, the module disables the channel and resets the output. The "safety shutdown" state will not
be reset until a new and valid validation time has been transferred. If enabled, the module reports which state it
is currently in via the channel's error status bit.
If the value of the validation timer is incremented in each task cycle, the valid validation time will be calculated
as follows:
Nettime of the X2X Link master (which the module is connected to)
+ Timespan for transferring data from the X2X Link master to the CPU (higher-level system)
+ Cycle time of task class (including tolerance)
+ Timespan for transferring the data from the CPU to the module
+ Timespan allowed by the application (e.g. for tolerating failure of an X2X Link cycle)
= Valid validation time
The AnalogOutputEnableByte is enabled during time-based monitoring. If the timer expires prematurely, the corre-
sponding bit in the AnalogOutputOkayByte is reset and the output drops out. This provides an easy way to achieve
a defined state.
Name:
AnalogOutput01 to AnalogOutput04
These registers provide the standardized output values. Once a permitted value is received, the module outputs
the respective current or voltage.
Information:
The value "0" disables the channel status LED.
Data type Value
INT -32767 to 32767 Voltage; Bus controller default setting: 0
0 to 32767 Current
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
ValidationTimer01 to ValidationTimer04
When an output is being monitored, these registers must provide the timestamp which, when reached, will cause
the output to shut down automatically. The values must be provided as signed 2-byte or 4-byte values.
Data type Values [µs]
INT -32768 to 32767 Nettime timestamp of the current output value
DINT -2,147,483,648 Nettime timestamp of the current output value
to 2,147,483,647
Name:
AnalogOutput01Enable to AnalogOutput04Enable
AnalogOutput01EnableReadback to AnalogOutput04EnableReadback
The "OutputEnable" byte is only needed for the channels with activated time-based monitoring. The individual bits
are used to enable/disable the respective channels. To receive reliable feedback about the current state of the
module, the byte was also implemented so that it can be read cyclically.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0 AnalogOutput01Enable 0 Output deactivated
AnalogOutput01EnableReadback 1 Output activated
... ...
3 AnalogOutput04Enable 0 Output deactivated
AnalogOutput04EnableReadback 1 Output activated
4-7 Reserved 0
Name:
AnalogOutput01OK to AnalogOutput04OK
These registers are only needed for channels with activated time-based monitoring. The individual bits report
whether the respective channel is actually generating the required voltage or current.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Value Information
0 AnalogOutput01OK 0 Electrical signal deactivated
1 Electrical signal activated
... ...
3 AnalogOutput04OK 0 Electrical signal deactivated
1 Electrical signal activated
4-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
200 µs
4.4.10 X20AO4635
The module is equipped with four outputs with 16-bit (including sign) digital converter resolution. It is possible to
select between the current and voltage signal using different connection terminal points.
• 4 analog outputs
• Either current or voltage signal possible
• 16-bit digital converter resolution
• Low temperature drift
Product ID X20AO4635
Short description
I/O module 4 analog outputs, ±10 V or 0 to 20 mA, low temperature drift
General information
B&R ID code 0xA7FE
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Channel type Yes, using software
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Analog outputs
Output ±10 V or 0 to 20 mA, via different connection terminal points
Digital converter resolution
Voltage ±15-bit
Current 15-bit
Conversion time 50 µs for all outputs
Settling time for output changes over entire range 500 µs
Power on/off behavior Internal enable relay for booting
Max. error at 25°C
Gain 0.040% 1)
Offset 0.022% 2)
4.4.10.5 Pinout
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
r e
X20 AO 4635
1 2
3 4
AO + 1 I AO + 2 I
AO + 1 U AO + 2 U
AO - 1 U/I AO - 2 U/I
AO + 3 I AO + 4 I
AO + 3 U AO + 4 U
AO - 3 U/I AO - 4 U/I
AO
Voltage Current
Load
+
Load
Load
+
Load
AO + x I
Output value
D/A
Conversion Enable relay AO + x U
I/O status
AO - x U/I
LED (orange)
Reset
To ensure proper operation, the following items must be taken into consideration:
• The following derating listings must be taken into consideration
• For mixed operation with one current output, the average of both derating curves should be used
• For mixed operation with two or three current outputs, the derating for the current outputs should be used
Horizontal installation
Voltage output
Horizontal installation
10
8
Load [k Ω]
6 Prohibited
Range
4
2
1
-20 -10 0 10 20 30 40 50
Figure 198: Derating the load with a voltage output and horizontal mounting
Current output
Horizontal installation
500
400
Prohibited
300
Load [Ω]
Range
200
100
0
-20 -10 0 10 20 30 40 50
Vertical installation
Voltage output
Vertical installation
10
Load [k Ω ] 6 Prohibited
Range
4
2
1
-20 -10 0 10 20 30 40 50
Figure 199: Derating the load with a voltage output and vertical mounting
Current output
Vertical installation
500
400
Prohibited
300
Load [Ω]
Range
200
100
0
-20 -10 0 10 20 30 40 50
1) The offset specifies the position of the register within the CAN object.
Each channel can be configured for either current or voltage signals. The type of signal is also determined by the
connection terminals used.
Name:
AnalogOutput01 to AnalogOutput04
These registers provide the standardized output values. Once a permitted value is received, the module outputs
the respective current or voltage.
Information:
The value "0" disables the channel status LED.
Data type Value
INT -32767 to 32767 Voltage; Bus controller default setting: 0
0 to 32767 Current
Name:
ConfigOutput01
This register can be used to set the channel type of the outputs.
Each channel is capable of handling either current or voltage signals. The type of signal is determined by the
connection terminals used. Since current and voltage require different adjustment values, it is also necessary to
configure the desired type of output signal. The following output signals can be set:
• ±10 V voltage signal (default)
• 0 to 20 mA current signal
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-7 Reserved 0
8 Channel 1 0 Voltage signal
1 Current signal
... ...
11 Channel 4 0 Voltage signal
1 Current signal
12 - 15 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
200 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
200 µs
Terminal block
X20 TB 12
Figure 200: The four parts of a bus controller - fieldbus interface, base module, supply module, terminal block
The entire backplane can be preinstalled. With the removable terminals, the entire system can be wired separately
from the electronics module. The individual modules are put in place during commissioning. This is where the I/
O system is adapted to the fieldbus being used.
Unlike the Compact CPU with integrated fieldbus connection, the bus controller does not need to be programmed
in order to transfer or receive the I/O data on the fieldbus. It can be configured on the fieldbus master.
4.5.2 X20BC0043
CAN (Controller Area Network) systems are widespread in the field of automation technology. CAN topology is
based on a line structure and uses twisted pair wires for data transfer. CANopen is a higher-layer protocol based
on CAN. This standardized protocol offers highly flexible configuration possibilities.
The bus controller makes it possible to connect up to 253 X2X Link I/O nodes to CANopen. A transition between
IP20 and IP67 protection outside of the control cabinet is possible by aligning X20, X67 or XV modules one after
the other as needed at distances up to 100 m. All CANopen transmission types such as synchronous, event and
polling modes are supported together with PDO linking, life/node guarding, emergency objects, and much more.
• Fieldbus: CANopen
• I/O configuration via the fieldbus
• 20 receiver PDOs and 20 sender PDOs
• Select between entry of a fixed transfer rate or automatic transfer rate detection.
• Integrated terminating resistor
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
The B&R FieldbusDESIGNER can be used to create configuration files (e.g. DCF files) in six easy steps.
All other function models are also supported by transferring configuration data to the bus controller
(e.g. from the master environment with an SDO download or via the serial interface).
The B&R FieldbusDESIGNER is available free of charge in the download section of the B&R website
www.br-automation.com.
Product ID X20BC0043
Short description
Bus controller CANopen slave
General information
B&R ID code 0x1F1A
Status indicators Module status, bus function, data transfer, terminating resistor
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED
Data transfer Yes, with status LED
Terminating resistor Yes, with status LED
Power consumption
Bus 1.5 W
Long flash
400 800
Triple flash
200 200 200 200 200 1000
Single flash
200 1000
Blinking
200 200
3
Flashing
500
Green/red
Flickering
50
All times in ms
CANopen interface
The interface is a 5-pin multipoint plug. The 0TB2105 terminal block must be ordered separately.
Interface Pinout
Terminal Function
1
1 CAN⊥ CAN ground
2 CAN_L CAN low
3 SHLD Shield
5 4 CAN_H CAN high
5 NC
5-pin male multipoint connector
On Off
A terminating resistor is already integrated on the bus controller. It can be turned on and off with a switch on the
bottom of the housing. An active terminating resistor is indicated by the "TERM" LED.
Node numbers and transfer rates are configured using the two bus controller number switches.
The transfer rate can be specified in two ways:
• Automatic detection by bus controller (see 4.5.2.9 "Automatic transfer rate detection" on page 511)
• Fixed definition by user (see 4.5.2.10 "Setting the transfer rate" on page 511)
After booting, the bus controller goes into "Listen only" mode. This means the bus controller behaves passively
on the bus and only listens.
The bus controller attempts to receive valid objects. If receive errors occur, the controller switches to the next
transfer rate in the lookup table.
If no objects are received, all transfer rates are tested cyclically. This procedure is repeated until valid objects are
received.
Lookup table
The controller tests the transfer rate according to this table. Beginning with the starting transfer rate (1000 kbit/s),
the controller switches to the next lower transfer rate. At the end of the table, the bus controller restarts the search
from the beginning.
Transfer rate
1000 kbit/s
800 kbit/s
500 kbit/s
250 kbit/s
125 kbit/s
100 kbit/s
50 kbit/s
20 kbit/s
10 kbit/s
The bus controller will detect the transfer rate automatically by default. Switch positions 0x80 - 0x88 can be used
to set a fixed transfer rate, or 0x89 can be used to enable automatic transfer rate detection.
Switch position Transfer rate
0x80 1000 kbit/s
0x81 800 kbit/s
0x82 500 kbit/s
0x83 250 kbit/s
0x84 125 kbit/s
0x85 100 kbit/s
0x86 50 kbit/s
0x87 20 kbit/s
0x88 10 kbit/s
0x89 Automatic transfer rate detection
Additional documentation about bus controller functions as well as the necessary import files for the master engi-
neering tool are available in the Downloads section of the B&R website (www.br-automation.com).
4.5.3 X20BC0043-10
CAN (Controller Area Network) systems are widespread in the field of automation technology. CAN topology is
based on a line structure and uses twisted pair wires for data transfer. CANopen is a higher-layer protocol based
on CAN. This standardized protocol offers highly flexible configuration possibilities.
The bus controller makes it possible to connect up to 253 X2X Link I/O nodes to CANopen. A transition between
IP20 and IP67 protection outside of the control cabinet is possible by aligning X20, X67 or XV modules one after
the other as needed at distances up to 100 m. All CANopen transmission types such as synchronous, event and
polling modes are supported together with PDO linking, life/node guarding, emergency objects, and much more.
• Fieldbus: CANopen
• Auto-configuration of I/O modules
• I/O configuration via the fieldbus (also supported by the B&R FieldbusDESIGNER)
• Constant response times even with large amounts of data (max. 32 Rx and 32 Tx PDOs)
• Configurable I/O cycle (0.5 - 4 ms)
• Possible to configure the transfer rate or have it detected automatically
• Heartbeat consumer and producer
• Emergency producer
• 2x SDO server, NMT slave
• Simple bootup (autostart)
• Terminal access via the serial interface on the X20PS9400
• Integrated terminating resistor
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
The B&R FieldbusDESIGNER can be used to create configuration files (e.g. DCF files) in six easy steps.
All other function models are also supported by transferring configuration data to the bus controller
(e.g. from the master environment with an SDO download or via the serial interface).
The B&R FieldbusDESIGNER is available free of charge in the download section of the B&R website
www.br-automation.com.
Product ID X20BC0043-10
Short description
Bus controller CANopen slave
General information
B&R ID code 0xA8B8
Status indicators Module status, bus function, data transfer, terminating resistor
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED and software status
Data transfer Yes, with status LED
Terminating resistor Yes, with status LED
Power consumption
Bus 2W
Electrical isolation
Fieldbus - X2X Link No
Fieldbus - I/O Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
GOST-R Yes
Interfaces
Fieldbus CANopen slave
Design 5-pin male multipoint connector
Max. distance 1000 m
Transfer rate Max. 1 Mbit/s
Determination of transfer rate Automatic transfer rate detection or fixed rate setting
Terminating resistor Integrated in the module
Min. cycle time 1)
Fieldbus No limitations
X2X Link 500 μs
Synchronization between bus systems possible No
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
quad Flash
200 200 200 200 200 200 200 1000
triple Flash
200 200 200 200 200 1000
double Flash
200 200 200 1000
single Flash
200 1000
blinkend
200 200
3
blitzend
500
grün/rot
Flickering
50
All times in ms
CANopen interface
The interface is a 5-pin multipoint plug. The 0TB2105 terminal block must be ordered separately.
Interface Pinout
Terminal Function
1
1 CAN⊥ CAN ground
2 CAN_L CAN low
3 SHLD Shield
5 4 CAN_H CAN high
5 NC
5-pin male multipoint connector
On Off
A terminating resistor is already integrated on the bus controller. It can be turned on and off with a switch on the
bottom of the housing. An active terminating resistor is indicated by the "TERM" LED.
Node numbers and transfer rates are configured using the two bus controller number switches.
The transfer rate can be specified in two ways:
• Automatic detection by bus controller (see 4.5.3.9 "Automatic transfer rate detection" on page 517)
• Fixed definition by user (see 4.5.3.10 "Setting the transfer rate" on page 518)
After booting, the bus controller goes into "Listen only" mode. This means the bus controller behaves passively
on the bus and only listens.
The bus controller attempts to receive valid objects. If receive errors occur, the controller switches to the next
transfer rate in the lookup table.
If no objects are received, all transfer rates are tested cyclically. This procedure is repeated until valid objects are
received.
Lookup table
The controller tests the transfer rate according to this table. Beginning with the starting transfer rate (1000 kbit/s),
the controller switches to the next lower transfer rate. At the end of the table, the bus controller restarts the search
from the beginning.
Transfer rate
1000 kbit/s
800 kbit/s
500 kbit/s
250 kbit/s
125 kbit/s
100 kbit/s
50 kbit/s
20 kbit/s
10 kbit/s
The bus controller will detect the transfer rate automatically by default. Switch positions 0x80 - 0x88 can be used
to set a fixed transfer rate, or 0x89 can be used to enable automatic transfer rate detection.
Switch position Transfer rate
0x80 1000 kbit/s
0x81 800 kbit/s
0x82 500 kbit/s
0x83 250 kbit/s
0x84 125 kbit/s
0x85 100 kbit/s
0x86 50 kbit/s
0x87 20 kbit/s
0x88 10 kbit/s
0x89 Automatic transfer rate detection
The node number position 0x92 can be used to save automatically generated configurations. This makes it possible
to work with a standardized configuration without having to adapt the application to changes associated with service
work or different development stages for example.
1. Turn off the power supply to the bus controller.
2. Set the node number to 0x90.
3. Turn on the power supply to the bus controller.
4. Wait until the "MS" LED starts blinking green (100 ms on / 200 ms off).
5. The node number switch must be set to 0x00 and then back to 0x90 within this time window of 5 seconds
(rotate the top switch).
6. Wait until the "MS" LED blinks with a red double-flash (parameters have been cleared).
7. Turn off the power supply to the bus controller.
8. Set the node number to 0x92.
9. Turn on the power supply to the bus controller.
10.Wait until the "MS" LED starts blinking green (100 ms on / 200 ms off).
11. The node number switch must be set to 0x02 and then back to 0x092 within this time window of 5 seconds
(rotate the top switch).
12.Wait until the "MS" LED blinks with a red quad-flash (parameters have been saved).
13.Turn off the power supply to the bus controller.
14.Set the desired node number (0x01 - 0x7F).
15.Turn on the power supply to the bus controller.
16.The bus controller boots with the set node number and automatic transfer rate detection.
Information:
A mapping tool for decoding the saved PDO mapping is available in the Download section of the B&R
website (www.br-automation.com).
Information:
This function is available starting with Hardware version E0 or Firmware version V0001.0107.
Additional documentation about bus controller functions as well as the necessary import files for the master engi-
neering tool are available in the Downloads section of the B&R website (www.br-automation.com).
4.5.4 X20BC0053
DeviceNet was developed by Allen Bradley as a CAN bus based automation network. It is based on a produc-
er/consumer protocol. From the user's point of view, all data is handled separately from CAN bus transfer possi-
bilities (e.g. longer data packets are automatically fragmented by DeviceNet). Access occurs using I/O messages
with defined properties.
The X20BC0053 bus controller makes it possible to connect X2X Link I/O nodes to DeviceNet. It has automatic
transfer rate detection, auto scan, automatic mapping and automatic configuration of the I/O modules. Explicit mes-
saging, change of state, cyclic, polled and bit strobe are supported as transfer modes. In addition to the standard
communication objects, there are also manufacturer-specific objects used to represent the modular X20 System
in the best manner possible.
X20 and other modules that are based on X2X Link can be connected to the bus controller. The entire configuration
of this type of modular system is supported by the DeviceNet standard. Allen Bradley developed the modular I/O
configuration to simplify the necessary configuration steps. The DeviceNet bus controllers from B&R also support
this type of configuration.
• Fieldbus: DeviceNet
• I/O configuration via the fieldbus
• Support of both linear and modular (Allen Bradley) configuration systems
• Auto scan, automatic I/O mapping of the I/Os
• Automatic I/O configuration (starting with Rev. D0, firmware version 1.23)
• Integrated terminating resistor
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
Product ID X20BC0053
Short description
Bus controller DeviceNet adapter (slave)
General information
B&R ID code 0x1F1B
Status indicators Module status, bus function, 24V DeviceNet voltage, data transfer, terminating resistor.
Diagnostics
24 V DeviceNet voltage Yes, with status LEDs (MOD and NET)
Module status Yes, with status LED and software status
Bus function Yes, with status LED
Data transfer Yes, with status LED
Terminating resistor Yes, with status LED
No transfer rate:
If the PS9400's "RUN" LED is active (PREOPERATIONAL or RUN mode), the
automatic transfer rate detection is still running or no transfer rate could be de-
tected.
On RUN mode:
The 24 V DeviceNet voltage is OK and the module is operating under normal
conditions.
Blinking Standby mode:
Configuration is missing, incomplete, or incorrect.
Red Blinking Recoverable Fault mode:
Green/red Blinking Module is performing a self test.
DeviceNet interface
The interface is a 5-pin multipoint plug. The 0TB2105 terminal block must be ordered separately.
Interface Pinout
Terminal DeviceNet
1
1 CAN⊥ (V-) CAN ground
2 CAN_L CAN low
3 SHLD Shield
5 4 CAN_H CAN high
5 V+ Supply voltage1)
5-pin male multipoint connector
On Off
A terminating resistor is already integrated on the bus controller. It can be turned on and off with a switch on the
bottom of the housing. An active terminating resistor is indicated by the "TERM" LED.
The MAC ID is configured using the two address switches on the bus controller.
The configurable range lies between 0 and 63. This value range is required in the DeviceNet specifications for a
DeviceNet device.
After booting, the bus controller goes into "Listen only" mode. This means the bus controller behaves passively
on the bus and only listens.
The bus controller attempts to receive valid objects. If receive errors occur, the controller switches to the next
transfer rate in the lookup table.
If no objects are received, all transfer rates are tested cyclically. This procedure is repeated until valid objects
are received, indicating that the correct transfer rate has been determined. Only transfer rates permitted by the
DeviceNet specification are tested.
Lookup table
The controller tests the transfer rate according to this table. Beginning with the starting transfer rate (500 kbit/s),
the controller switches to the next lower transfer rate. At the end of the table, the bus controller restarts the search
from the beginning.
Transfer rate
500 kbit/s
250 kbit/s
125 kbit/s
Information:
While automatic transfer rate recognition is running, both DeviceNet LEDs are switched off (because
there is no LED status definition in the DeviceNet specifications for this status).
To ensure that the module has been supplied and booted, this manufacturer specific status definition
requires the X20PS9400 RUN LED to be active.
Multiple parameters can be stored in the bus controller flash memory. Deleting the parameters using the switch
position 90 returns the bus controller to its factory settings.
Deleting parameters
1. Turn off the power supply to the bus controller.
2. Set the node number to 90
3. Turn the power supply to the bus controller back on.
4. Wait until the "MOD" LED blinks green for 5 s (3 ms on / 500 ms off). The node number switch must be set
to 00 and then back to 90 within this time window.
5. Wait until the "MOD" LED blinks with a red double-flash (parameters have been cleared).
6. Turn off the power supply to the bus controller.
7. Set desired node number (00 - 63)
8. Turn the power supply to the bus controller back on.
9. The bus controller boots with the set node number and automatic transfer rate detection.
The automatic configuration of the connected I/O modules by the bus controller is supported starting with Rev.D0
(firmware ≥V 1.23) of the bus controller.
To prevent the configuration data from being accidentally overwritten on the bus controller, the procedure described
below must be followed when creating the configuration data. When doing this, it is important that all required I/
O modules are also started when booting the bus controller (i.e. supplied with power). This is especially important
when using potential groups (E-stop switches).
The automatic configuration sets the following attributes of class 0x65 on the individual I/O modules:
• Module type (0x01)
• Input length (0x03)
• Output length (0x05)
Additional parameters are not set. That means that the connected modules are configured with their standard
settings and standard I/O lengths. This can be changed by editing the parameters in the respective master engi-
neering tool.
Automatic configuration
1. Turn off the power supply to the bus controller.
2. Set node number switch to 95 (this is done by turning "x10" switch right to the position "P" and the "x1" switch
to 5).
3. Turn on the power supply to the bus controller.
4. Wait until the "MOD" LED starts blinking green (3 ms on / 500 ms off). This phase of green blinking lasts 5 s.
The node number "x10" switch must be set to 0 within this time frame and then set back to 9.
5. Wait until the "MOD" LED blinks (4 red flashes). The old configuration data is now deleted completely and
overwritten with the new values from the connected I/O modules.
6. Turn off the power supply to the bus controller.
7. Set the desired node number (00 - 63).
8. Turn on the power supply to the bus controller.
9. The bus controller boots using the set node number, automatic transfer rate recognition and standard settings
from the connected I/O modules.
Additional documentation about bus controller functions as well as the necessary import files for the master engi-
neering tool are available in the Downloads section of the B&R website (www.br-automation.com).
4.5.5 X20BC0063
PROFIBUS DP is based on the physics of the RS485 interface. Data transfer is controlled using a hybrid bus access
procedure. Active stations receive communication rights via a token passing procedure and can then access all
stations on the network according to the master-slave principle. The maximum time of circulation for a token can
be configured, which results in a defined cycle time.
Access represents various services for the user for both cyclic and for non-cyclic data transfer.
The X20BC0063 bus controller makes it possible to connect X2X Link I/O nodes to PROFIBUS DP. It supports
PROFIBUS DP with all of its options and other additional properties. In addition to the device, module, and channel
diagnostics provided in the PROFIBUS standard, it is also possible, for example, to switch to the slot diagnostics
option in S7 format. X20 or other modules that are based on X2X Link can be connected to the bus controller.
Modular system configurations are optimally supported by PROFIBUS DP.
• Fieldbus: PROFIBUS DP
• I/O configuration via the fieldbus
• Extensive device, module, and channel diagnosis according to PROFIBUS DP standard
• Communication with X2X Link I/O nodes even works when some nodes are missing or without power
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
Product ID X20BC0063
Short description
Bus controller PROFIBUS DP V0 slave
General information
B&R ID code 0x1F1C
Status indicators Module status, bus function, data transfer
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED
Data transfer Yes, with status LED
Power consumption
Bus 2.3 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Fieldbus - X2X Link No
Fieldbus - I/O Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Interfaces
Fieldbus PROFIBUS DP V0 slave
Design 9-pin DSUB socket
Max. distance 1200 m
Transfer rate Max. 12 Mbit/s
Determination of transfer rate Automatic transfer rate detection
Min. cycle time 1)
Fieldbus No limitations
X2X Link 400 μs
Synchronization between bus systems possible No
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20PS9400 or X20PS9402 power supply module separately
Order 1x X20BB80 bus base separately
Spacing 2) 37.5 +0.2 mm
The condition of the PROFIBUS DP bus controller is diagnosed using the LED status indicators "STATUS" and
"ERROR".
STATUS ERROR Function Solution
(green) (red)
Off Off HARDWARE FAULT / POWER FAIL • Check wiring of supply voltage.
On On BUS OFF • Check the PROFIBUS network
• Baud rate not detected • Check the PROFIBUS master
• No connection to the DP master
• DP master not active
On Blinking WAIT FOR CONFIG • Check the node number switch
• Transfer rate has been detected, but the PROFIBUS • Check the slave address in the master configuration
master has not yet configured the bus controller
Blinking Off DATA EXCHANGE - DIAGNOSTICS • Initialization can take a few seconds depending on the
• The bus controller is still initializing the I/O modules number of I/O modules connected
• The I/O modules configured by the master cannot be • Check the wiring and power supply for the I/O modules
found • Read diagnostic messages in the respective PROFIBUS
• An error has occurred on one or more I/O modules (short master's engineering tool
circuit, etc.)
On Off DATA EXCHANGE
• Cyclic data exchange with the PROFIBUS DP master
Blinking Blinking CONFIG ERROR • Check the wiring of the X2X Link and the order of I/O
• One or more I/O modules found do not match with the modules
configuration of the PROFIBUS DP master • Check configuration of the PROFIBUS master
• The configuration received from the PROFIBUS master • Read diagnostic messages in the respective PROFIBUS
is invalid master's engineering tool
• Check the configuration being used - it is possible that
the number of configured I/O modules is too high
Off Blinking SERVICE MODE - BOOT • Set a valid node number
• The bus controller's node number has been set to 255
(0xFF) - after 2 s the bus controller starts in service mode
Single flash Single flash HARDWARE FAULT
PROFIBUS DP interface
Interface Pinout
Pin RS485
1 Reserved
2 Reserved
9 5 3 RxD/TxD-P Data1)
4 CNTR-P Transmit enable
6 5 DGND Electrically isolated supply
1
6 CP Electrically isolated supply
7 Reserved
9-pin female DSUB connector
8 RxD/TxD-N Data\2)
9 CNTR-N Transmit enable\
CNTR ... Directional switch for external repeater
The PROFIBUS DP node number is configured using both number switches of the bus controller.
After booting or after a communication timeout, the bus controller goes into the status "Baud Search". This means
the bus controller behaves passively on the bus.
The bus controller always begins the search for the configured transfer rate with the highest transfer rate. If a
complete error-free telegram is not received during monitoring time, then the search is continued using the next
lowest transfer rate.
Transfer rate
12 Mbit/s
6 Mbit/s
3 Mbit/s
1.5 Mbit/s
500 kbit/s
187.5 kbit/s
93.75 kbit/s
45.45 kbit/s
19.2 kbit/s
9.6 kbit/s
Additional documentation about bus controller functions as well as the necessary import files for the master engi-
neering tool are available in the Downloads section of the B&R website (www.br-automation.com).
4.5.6 X20BC0073
The X20BC0073 bus controller makes it possible to connect X2X Link I/O nodes to CAN I/O. CAN I/O is a transfer
protocol based on standard CAN bus fully integrated in the B&R system. From the user's point of view, it doesn't
matter if I/O points are operated locally or remotely via CAN I/O.
Up to 43 I/O modules can be connected to the bus controller. Up to 16 of them can be analog modules.
• Fieldbus: CAN bus
• Automatic firmware update via the fieldbus
• Integrated I/O access in B&R Automation Studio
• Integrated terminating resistor
Information:
The bus controller is unable to detect modules after a gap in the X2X Link station numbers. This can
be caused by:
• X20 modules not being connected
• Modules with integrated node number switch, such as the X20BM05
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
Product ID X20BC0073
Short description
Bus controller CAN I/O slave
General information
B&R ID code 0x1F1D
Status indicators Module status, bus function, data transfer, terminating resistor
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED
Data transfer Yes, with status LED
Terminating resistor Yes, with status LED
Power consumption
Bus 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Fieldbus - X2X Link No
Fieldbus - I/O Yes
The interface is a 5-pin multipoint plug. The 0TB2105 terminal block must be ordered separately.
Interface Pinout
Terminal Function
1
1 CAN⊥ CAN ground
2 CAN_L CAN low
3 SHLD Shield
5 4 CAN_H CAN high
5 NC
5-pin male multipoint connector
On Off
A terminating resistor is already integrated on the bus controller. It can be turned on and off with a switch on the
bottom of the housing. An active terminating resistor is indicated by the "TERM" LED.
Node numbers and transfer rates are configured using the two bus controller number switches. The switch posi-
tions 0x00 to 0x40 and 0x60 enable automatic transfer rate detection (see section 4.5.6.9 "Automatic transfer rate
detection" on page 535). The rest of the switch positions have a fixed transfer rate (see table).
After booting, the bus controller goes into "Listen only" mode. This means the bus controller behaves passively
on the bus and only listens.
The bus controller attempts to receive valid objects. If receive errors occur, the controller switches to the next
transfer rate in the lookup table.
If no objects are received, all transfer rates are tested cyclically. This procedure is repeated until valid objects are
received.
Starting transfer rate
The bus controller begins the search with this transfer rate. The starting transfer rate can be defined in two different
ways:
• Read from EEPROM
• Using the last detected transfer rate after a software reset (Command Code 20)
Search table
The controller tests the transfer rate according to this table. Beginning with the starting transfer rate, the controller
switches to the next lower transfer rate. At the end of the table, the bus controller starts searching from the beginning
again.
Transfer rate
1000 kbit/s
500 kbit/s
250 kbit/s
125 kbit/s
50 kbit/s
20 kbit/s
10 kbit/s
4.5.6.10 SG4
The module comes with preinstalled firmware. The firmware is also part of the B&R Automation Runtime operating
system for the PLC. If the two versions are different, the Automation Runtime firmware is loaded to the module.
The latest firmware is available automatically when updating B&R Automation Runtime.
4.5.7 X20BC0083
The X20BC0083 bus controller makes it possible to connect X2X Link I/O nodes to POWERLINK. It is also possible
to operate the X2X Link cycle synchronously 1:1 or synchronous to POWERLINK using a prescaler.
POWERLINK is a standard protocol for Fast Ethernet with hard real-time properties. The Ethernet POWER-
LINK Standardization Group (EPSG) ensures that the standard remains open and is continually developed:
www.ethernet-powerlink.org
• POWERLINK
• I/O configuration and FW update via the fieldbus
• Integrated hub for efficient cabling
Product ID X20BC0083
Short description
Bus controller POWERLINK (V1/V2) controlled node
General information
B&R ID code 0x1F1E
Status indicators Module status, bus function
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED and software status
Power consumption
Bus 2.0 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Fieldbus - X2X Link Yes
Fieldbus - I/O Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Interfaces
Fieldbus POWERLINK (V1/V2) controlled node
Design 2x shielded RJ45 port (hub)
Cable length Max. 100 m between two stations (segment length)
Transfer rate 100 Mbit/s
Transmission
Physical interfaces 100 BASE-TX
Half-duplex Yes
Full-duplex No
Autonegotiation Yes
Auto-MDI / MDIX Yes
Min. cycle time 1)
Fieldbus 200 μs
X2X Link 200 μs
Synchronization between bus systems possible Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20PS9400 or X20PS9402 power supply module separately
Order 1x X20BB80 bus base separately
Spacing 2) 37.5 +0.2 mm
Triple flash
200 200 200 200 200 1000
Double flash
200 200 200 1000
Single flash
200 1000
Blinking
200 200
Flickering
All times in ms
The station number for the POWERLINK station is set using the two number switches. Station numbers are per-
mitted between 0x01 and 0xEF.
Switch position Description
0x00 Reserved, switch position not permitted.
0x01 - 0xEF Station number of the POWERLINK station. Operation as controlled node.
0xF0 - 0xFF Reserved, switch position not permitted.
Information about cabling X20 modules with an Ethernet interface can be found in the module's download section
on the B&R website (www.br-automation.com).
Interface Pinout
Pin Ethernet
1 RXD Receive data
2 RXD\ Receive data\
1
3 TXD Transmit data
4 Termination
5 Termination
6 TXD\ Transmit data\
Shielded RJ45 port 7 Termination
8 Termination
4.5.7.8 SG3
4.5.7.9 SG4
The module comes with preinstalled firmware. The firmware is also part of the B&R Automation Runtime operating
system for the PLC. If the two versions are different, the Automation Runtime firmware is loaded to the module.
The latest firmware is available automatically when updating B&R Automation Runtime.
4.5.8 X20BC0087
Established in 1979, the Modbus protocol has approved the use of Ethernet with both Modbus/TCP and Mod-
bus/UDP. Today, Modbus/TCP is an open Internet draft standard introduced by Schneider Automation to the In-
ternet Engineering Task Force (IETF), the organization responsible for Internet standardization. The Modbus ser-
vices and object model have been preserved since the original version and left unchanged for use with the TCP/
IP transmission medium.
Modbus/UDP differs from Modbus/TCP in that it uses connectionless communication via UDP/IP. The advantages
of faster and easier communication with UDP/IP also brings with it the disadvantage of requiring error detection
and correction in the application layer.
This bus controller makes it possible to connect X2X Link I/O nodes to Modbus via Ethernet. The bus controller can
be operated on B&R controllers through the use of Automation Studio or on third-party systems with Modbus/TCP
or -UDP master functionality.
• Fieldbus: Modbus/TCP, Modbus/UDP
• I/O configuration via the fieldbus
• DHCP-capable
• Bootp-capable
• Integrated double switch for efficient cabling
• Configurable I/O cycle (0.5 to 4 ms)
• Response time: <1 - 8 ms (depending on the load on the integrated switch)
• Validity check for command sequences before execution
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
All other function models are supported when configured accordingly. The B&R FieldbusDESIGNER
is available at no cost in the Downloads section of the B&R website www.br-automation.com.
Product ID X20BC0087
Short description
Bus controller Modbus TCP/UDP slave
General information
B&R ID code 0x227C
Status indicators Module status, bus function
Diagnostics
Module status Yes, with status LED and software
Bus function Yes, with status LED and software
Information about cabling X20 modules with an Ethernet interface can be found in the module's download section
on the B&R website (www.br-automation.com).
Interface Pinout
Pin Ethernet
1 RXD Receive data
2 RXD\ Receive data\
1
3 TXD Transmit data
4 Termination
5 Termination
6 TXD\ Transmit data\
Shielded RJ45 port 7 Termination
8 Termination
Changes to the network address switches are only applied after a restart. If the bus controller is restarted with
the address switch value 0xFF, it is initialized with the IP address 192.168.100.1. This address is also the factory
default setting. The port number is set to 502 (reserved for Modbus).
This IP address can be used to establish a connection to the bus controller. The internationally unique MAC address
is listed on the housing side of the bus controller. The combination of "br" and the MAC address results in a unique
name (primary NetBIOS name) that also makes it possible to access the bus controller.
Example of the primary NetBIOS name:
MAC address: 00-60-65-00-49-02
Resulting NetBIOS name: br006065004902
This means that, without additional parameter changes, either the default IP address 192.168.100.1 or the NetBIOS
name "br+MAC" can be used to communicate with the controller.
Since NetBIOS is being used, the bus controller can only be accessed via this name if there are no intermediary
routers or gateways in the way.
If a network address switch setting between 0x80 and 0xEF is configured, the bus controller will attempt to request
an IP address from the DHCP server. To query this IP address, simply run a "ping" command with the hostname.
The bus controller registers this hostname on the DHCP server, which should forward it to a DNS server.
Example The hostname (DNS name) is made up of three elements:
"br" + "mb" + address switch value (three decimal places).
This means, for example, that the following hostname is generated for address switch setting
0xD7 (dec. 215): "brmb215"
If the DNS service is not available on the network, the bus controller's two NetBIOS names can also be used for
access. The secondary NetBIOS name is identical to the hostname. If the address switches are set to 0x00, it is
identical to the primary NetBIOS name. The bus controller can only be reached via its NetBIOS name if no other
routers or gateways are in the way.
The address switches can be used to change the last byte in the IP address configured on the bus controller. The
IP address saved in flash memory is not changed. If the address switches are set to 0x00, the bus controller applies
the IP address last saved to flash memory. Switch positions between 0x01 and 0x7F cause the last position of the
IP address (the lowest byte) to be overwritten by the value of the address switch. This provides the user a quick
and easy way to address a large number of bus controllers. In short, an IP address between 192.168.100.1 and
192.168.100.127 can be selected for a bus controller using the address switches without requiring any additional
software configuration.
In addition to the hostname used to register on the DHCP server, the bus controller also has so-called NetBIOS
names. These are used to access the bus controller from a PC using its name (as opposed to its IP address). This
is only possible if no routers or gateways are in the way, however.
The primary NetBIOS name is always composed of the prefix "br" and the MAC address from the bus controller
(see 4.5.8.9 "Automatic IP assignment by a DHCP server" on page 546).
The secondary NetBIOS name corresponds to the primary NetBIOS name at address switch position 0x00. This
is necessary because there may be several bus controllers with the address switch 0x00 in a network segment.
In this case, the IP address from flash memory is used.
For all other address switch positions, the secondary NetBIOS name is generated from the network address switch
value (as in DHCP mode): "br" + "mb" + address switch value (3 decimal places).
A hostname defined explicitly by the user will be used for the secondary NetBIOS name regardless of the address
switch value.
This makes it possible to access the bus controller with the NetBIOS name configured using the address switches.
This is also possible if the controller was not configured for use with a DHCP server (address switch setting between
0x01 and 0x7F).
The IP parameters in flash memory can be changed via the Modbus protocol, the ModbusTCP Toolbox or the
Telnet interface. The ModbusTCP Toolbox can be downloaded from the B&R website.
The IP address, subnet and gateway are all defined in the address range 0x1003 to 0x100E. Each has a length
of 4 words. The data is applied by writing the constant 0xC1 to the address 0x1140 ("Write Single Register" fc6,
addr. 0x1140, data 0xC1). The new settings are applied after the bus controller is restarted.
4.5.9 X20BC0088
EtherNet/IP is a fieldbus based on EtherNet/IP that was developed by Allen-Bradley (Rockwell Automation) and
later handed off to the Open DeviceNet Vendor Association (ODVA) as an open standard. In 1998, a working group
at ControlNet International developed a procedure for setting the published Common Industrial Protocol to Ethernet.
EtherNet/IP was published in March 2000 as an open industrial automation standard based on this procedure.
The X20BC0088 bus controller makes it possible to connect X2X Link I/O nodes to EtherNet/IP. The bus controller
can be operated via the X20IF10D1-1 interface module or by 3rd-party systems with EtherNet/IP scanner func-
tionality.
• Fieldbus: EtherNet/IP
• Integrated 3-port switch for efficient cabling
• Auto-configuration of I/O modules
• Can be configured by the scanner (master) using configuration assembly
• Web interface
• DHCP-capable
• Configurable I/O cycle (0.5 to 4 ms)
• Minimum fieldbus cycle time (also requested packet interval or RPI): 1 ms
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
The B&R FieldbusDESIGNER can be used to create configuration files (e.g. EDS files) in six easy steps.
All other function models are also supported by transferring configuration data to the bus controller
(e.g. using its web interface or the scanner via a "Configuration Assembly").
The B&R FieldbusDESIGNER is available free of charge in the download section of the B&R website
www.br-automation.com.
Product ID X20BC0088
Short description
Bus controller EtherNet/IP adapter (slave)
General information
B&R ID code 0x26D8
Status indicators Module status, network status, bus function
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED and software status
Network status Yes, with status LED and software status
Information about cabling X20 modules with an Ethernet interface can be found in the module's download section
on the B&R website (www.br-automation.com).
Interface Pinout
Pin Ethernet
1 RXD Receive data
2 RXD\ Receive data\
1
3 TXD Transmit data
4 Termination
5 Termination
6 TXD\ Transmit data\
Shielded RJ45 port 7 Termination
8 Termination
Changes to the network address switch are only applied after a restart (power cycle). If the bus controller is restarted
with the address switch number 0xFF, it is initialized with the IP address 192.168.100.1. This address is also the
default address upon delivery.
This IP can be used to establish a connection to the bus controller. The internationally unique MAC address is
listed on the housing side of the bus controller. The combination of "br" and the MAC address results in a unique
name (primary NetBIOS name) that also makes it possible to access the bus controller.
Example for the primary NetBIOS names:
MAC address: 00-60-65-00-49-02
Resulting NetBIOS name: br006065004902
This means that, without additional parameter changes, either the default IP address 192.168.100.1 or the NetBIOS
name "br+MAC" can be used to communicate with the controller.
The bus controller can only be accessed via this name if there are no intermediary routers or gateways because
the NetBIOS method is used.
At an address switch position between 0x80 and 0xEF, the bus controller attempts to request an IP address from
the DHCP server. To query this IP address, simply run a "ping" command with the host name. The bus controller
registers this host name on the DHCP server, which should forward it to a DNS server.
Example: The host name (DNS name) is made up of three elements:
"br" + "eip" + address switch value (three decimal places)
This means that a address switch value of e.g. 0xD7 (dec. 215) would result in the following host name:
"breip215"
If DNS service is not available on the network, the bus controller's two NetBIOS names can also be used for
access. The secondary NetBIOS name is identical to the host name; at address switch value 0x00, it is identical
with the primary NetBIOS name. The bus controller can only be reached via its NetBIOS name if no other routers
or gateways are in the way.
The address switches can be used to change the last position (octet) in the IP address configured on the bus
controller. The IP address saved in flash memory is not changed. If the address switches are set to 0x00, the
bus controller applies the IP address last saved to flash memory. Switch positions between 0x01 and 0x7F cause
the last position of the IP address (the lowest byte) to be overwritten by the value of the address switch. This
provides the user a quick and easy way to address a large number of bus controllers. In short, an IP address
between 192.168.100.1 and 192.168.100.127 can be selected for a bus controller using the address switches
without requiring any additional software configuration.
The IP parameters in the flash memory can be changed via the EtherNet/IP protocol or using the Telnet interface
(see EtherNet/IP in User's Manual). If the IP address should be set via the TCP/IP object (class 0xF5), then the
new address is only saved in the flash if the instance attribute 3 (Configuration Control) of the TCP/IP object is
set at 0 (see CIP specification).
4.5.10 X20BC00E3
PROFINET (Process Field Network) is an Industrial Ethernet protocol. It uses TCP/IP and is real-time capable.
PROFINET IO was developed for real-time (RT) and synchronous communication (IRT = Isochronous Real Time).
The designations RT and IRT merely describe the real-time properties for communication taking place within
PROFINET IO. PROFINET IO defines how all data is exchanged between controllers (masters) and devices
(slaves) and how parameter settings and diagnostics are handled. The bus system is designed to exchange data
between Ethernet-based field devices using the producer/consumer model.
X20 modules or other modules that are based on X2X Link can be connected to the bus controller. Modular system
configurations are optimally supported by PROFINET. Using the device description file (GSDML format), it is very
easy to handle project configuration in the respective engineering tool from the manufacturer of the master device.
• Fieldbus: PROFINET RT
• I/O configuration via the fieldbus
• Conformance Class B
• Minimum cycle time 1 ms
• Integrated switch for cabling multiple slaves
• 100 Mbit/s full duplex mode
• Up to 1440 bytes of input data and up to 1440 bytes of output data are possible
• Web interface that has been implemented
• PROFINET diagnostics and module diagnostics during runtime from within the master environment
• Module and switch diagnostics during runtime using the Web interface or SNMP
Product ID X20BC00E3
Short description
Bus controller PROFINET RT slave
General information
B&R ID code 0xBB7D
Status indicators Module status, bus function
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED and software status
Power consumption
Bus 2.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Fieldbus - X2X Link Yes
Fieldbus - I/O Yes
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GOST-R Yes
Interfaces
Fieldbus PROFINET RT slave
Design 2x shielded RJ45 port (switch)
Cable length Max. 100 m between two stations (segment length)
Transfer rate 100 Mbit/s
Transmission
Physical interfaces 100 BASE-TX
Half-duplex Yes
Full-duplex Yes
Autonegotiation Yes
Auto-MDI / MDIX Yes
Min. cycle time 1)
Fieldbus 1 ms
X2X Link 250 μs
Synchronization between bus systems possible Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20PS9400 or X20PS9402 power supply module separately
Order 1x X20BB80 bus base separately
Spacing 2) 37.5 +0.2 mm
The following table lists the status LEDs available on the bus controller. Exact blink times are specified in the timing
diagram in the next section.
Figure LED Color Status Description
MS1) Green Off The PROFINET master is in "Stop" mode.
Quad flash The bus controller does not have a valid IP address (0.0.0.0). It will wait in this
state until it is assigned an IP address from the PROFINET master or from an
external source. This state can also occur if the bus controller is being operated
in DHCP mode.
Double flash An unacknowledged alarm is pending on the bus controller.
Blinking 1 The bus controller is in the initialization phase. This boot phase is where all con-
nected I/O modules are initialized.
Blinking 3 The bus controller is configuring the connected I/O modules. The configuration
is transferred to the bus controller via the PROFINET master.
On A connection to a PROFINET master has been established. The master and
slave are both in OPERATIONAL mode and data is being exchanged between
them.
This mode also indicates that the master itself is in RUN mode.
Red Blinking 4 The bus controller has detected an error. However, it can still be corrected in the
master environment during runtime.
Blinking 1 The bus controller has detected an error. This error cannot be corrected during
runtime; a restart is required.
BF1) Green Blinking 2 Device identification ("blink" function in step 7 when searching for existing Eth-
ernet stations).
On A connection to a PROFINET master has been established.
Red On Not connected to a PROFINET Master
L/A IFx Green Off No physical Ethernet connection exists.
Blinking The respective LED blinks when Ethernet activity is detected on the correspond-
ing RJ45 port (IF1, IF2).
On Connection (link) established, but no communication is taking place.
Blinking 1
150
Blinking 2
250
Blinking 3
500
Blinking 4
1000
Quad flash
300 300 300 300 300 300 300 1500
Double flash
300 300 300 1500
All times in ms
Information about cabling X20 modules with an Ethernet interface can be found in the module's download section
on the B&R website (www.br-automation.com).
Interface Pinout
Pin Ethernet
1 RXD Receive data
2 RXD\ Receive data\
1
3 TXD Transmit data
4 Termination
5 Termination
6 TXD\ Transmit data\
Shielded RJ45 port 7 Termination
8 Termination
The bus controller has 2 node number switches. The bus controller can be set to different operating modes using
certain, pre-defined switch positions. They can also be used to configure various additional parameters (PROFINET
device name, DHCP mode, etc.).
Switch position Description
0x00 All parameters are loaded from flash memory: Default PROFINET initialization via the DCP protocol (factory state)
0x01 - 0xEF These switch positions generate a valid PROFINET device name. This name is composed as follows: "brpnXXX".
XXX refers to the decimal value of the node number switch position. The system automatically adds any necessary
leading zeros.
0xF0 Clears flash (see 4.5.10.8 "Erasing flash memory" on page 556)
0xF1 - 0xFD Reserved, switch position not permitted
0xFE IP address via DHCP server
0xFF All parameters set to default: PME mode
Erasing flash memory using switch position 0xF0 returns the bus controller to its factory state.
Procedure
1. Turn off the power supply to the bus controller.
2. Set the node number to 0xF0.
3. Turn the power supply to the bus controller back on.
4. Wait until the "MS" LED flashes green for 5 s. The node number switch must be set to 0x00 and then back
to 0xF0 within this time window of 5 seconds (rotate the top switch).
5. Wait until the "MS" LED blinks with a red double-flash (flash has been cleared).
6. Turn off the power supply to the bus controller.
7. Set the desired node number (0x00 - 0xEF)
8. Turn the power supply to the bus controller back on.
9. The bus controller boots with the configured node number.
The integrated Web interface gives the user an overview of the bus controller's network parameters, the configured
I/O modules and the switch configuration. The starting page includes information regarding specific bus controller
settings such as IP address, host name and the PROFINET device name. In addition, the web page provides
556 X20 system User's Manual 3.10
X20 system modules • Bus controllers • X20BC00E3
information about the current firmware version. Information concerning module diagnostics is incorporated into a
tree structure. Expanding and collapsing the individual module nodes provides an overview of the configured I/O
modules. In addition, various package counters are read from the integrated switch. This makes diagnosing errors
on the network quick and easy.
Network parameters concerning the bus controller itself can be read, but they cannot be modified. The bus
controller's IP configuration is handled during booting or by the PROFINET master when a connection is estab-
lished.
Each page of the Web interface contains help information that describes the functions and parameters displayed
on that page. The link to this information can be found in the upper right corner of the page in the form of a question
mark.
A connection to the web interface is established by entering the current IP address or the unique host name in
a Web browser. Some functions require authentication.
The host name is composed of a predefined text and a unique MAC address. For example, if the bus controller
has the MAC address 00:60:65:11:22:33, this will result in the following host name: br006065112233.
Default parameters for the web interface
IP address: 192,168,100.1
User name: admin
Password: B&R
Information:
Take note of the node number switch position.
Be aware that the authentication parameters are case sensitive.
4.5.11 X20BC00G3
EtherCAT is an Ethernet-based fieldbus developed by Beckhoff. The protocol is suitable for hard and soft real-time
requirements in automation technology. In addition to a ring structure, which becomes logically necessary because
of the summation frame telegram used, the EtherCAT technology also physically supports topologies such as line,
tree, star (limited) and combinations of these topologies. B&R's X20BC80G3 (expandable bus controller module)
and X20HB88G0 (stand alone junction base module) are available for implementing these topologies.
EtherCAT slave devices take the data designated for them from a telegram as it is passing through the device.
Input data is also inserted in the telegram as it is passing through. The X20BC00G3 bus controller allows X2X
Link I/O modules to be coupled to EtherCAT and can be operated on any EtherCAT master system. A transition
between IP20 and IP67 protection outside of the control cabinet is possible by aligning X20, X67 or XV modules
one after the other as needed at distances up to 100 m.
Master systems without FoE (File Access over EtherCAT) support require an appropriate configuration tool to
transfer the configuration (optional).
• Fieldbus: EtherCAT
• Auto-configuration of I/O modules
• I/O configuration and firmware update via the fieldbus (FoE)
• Full support of the modular slice concept via CoE (CANopen over EtherCAT)
• Configurable I/O cycle (0.2 - 4 ms)
• Synchronization between the fieldbus and X2X Link
• X20BC80G3 module type with two additional output ports (X20HB28G0)
Information:
Only the default function model is supported (see respective module description) when the bus con-
troller automatically configures multi-function modules.
All other function models are supported when configured accordingly (see EtherCAT user's manual).
The easy-to-use B&R FieldbusDESIGNER can help in this regard and is available for free download
from www.br-automation.com/designer.
Product ID X20BC00G3
Short description
Bus controller EtherCAT slave
General information
B&R ID code 0xAC23
Status indicators Module status, bus function
Double flash
200 200 200 1000
Single flash
200 1000
Blinking
200 200
Flickering
All times in ms
Information about cabling X20 modules with an Ethernet interface can be found in the module's download section
on the B&R website (www.br-automation.com).
IN (IF1) IN
Interface Pinout
Pin Ethernet
1 TXD Transmit data
2 TXD\ Transmit data\
1
3 RXD Receive data
4 Termination
5 Termination
6 RXD\ Receive data\
Shielded RJ45 port 7 Termination
8 Termination
A slave alias address can be set using the two network address switches on the bus controller. During the initial-
ization phase (during start-up), the bus controller writes the value of the address switch to the ESC register 0x12
or 0x13. However, the value is only accepted in the register if the value of the switch value is between 0x00 and
0xFA (decimal 250).
Switch position Description
0x00 to 0xFA Writes the address switch value to the "Station Alias" register.
0xFB to 0xFE Address switch value not used. ESC Alias registers not changed.
0xFF Address switch value not used. ESC Alias registers not changed. The bus controller boots with the default values
if the address switch is set to the value "0xFF" before a restart. All set parameters remain unchanged in flash
memory.
The master determines whether the alias address is used for the slave addressing by setting the corresponding
bit in the ESC DL control register (bit 24).
4.5.12 X20BC0143-10
CAN (Controller Area Network) systems are widespread in the field of automation technology. CAN topology is
based on a line structure and uses twisted pair wires for data transfer. CANopen is a higher-layer protocol based
on CAN. This standardized protocol offers highly flexible configuration possibilities.
The bus controller makes it possible to connect up to 253 X2X Link I/O nodes to CANopen. A transition between
IP20 and IP67 protection outside of the control cabinet is possible by aligning X20, X67 or XV modules one after
the other as needed at distances up to 100 m. All CANopen transmission types such as synchronous, event and
polling modes are supported together with PDO linking, life/node guarding, emergency objects, and much more.
• Fieldbus: CANopen
• Auto-configuration of I/O modules
• I/O configuration via the fieldbus (also supported by the B&R FieldbusDESIGNER)
• Constant response times even with large amounts of data (max. 32 Rx and 32 Tx PDOs)
• Configurable I/O cycle (0.5 - 4 ms)
• Possible to configure the transfer rate or have it detected automatically
• Heartbeat consumer and producer
• Emergency producer
• 2x SDO server, NMT slave
• Simple bootup (autostart)
• Terminal access via the serial interface on the X20PS9400
Information:
Only the standard function model (see the respective module description) is supported when the bus
controller is used together with multi-function modules it has automatically configured itself.
The B&R FieldbusDESIGNER can be used to create configuration files (e.g. DCF files) in six easy steps.
All other function models are also supported by transferring configuration data to the bus controller
(e.g. from the master environment with an SDO download or via the serial interface).
The B&R FieldbusDESIGNER is available free of charge in the download section of the B&R website
www.br-automation.com.
Product ID X20BC0143-10
Short description
Bus controller CANopen slave
General information
B&R ID code 0xAD3E
Status indicators Module status, bus function, data transfer
Diagnostics
Module status Yes, with status LED and software status
Bus function Yes, with status LED and software status
Data transfer Yes, with status LED
Power consumption
Bus 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Fieldbus - X2X Link No
Fieldbus - I/O Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
GOST-R Yes
Interfaces
Fieldbus CANopen slave
Design 9-pin male DSUB connector
Max. distance 1000 m
Transfer rate Max. 1 Mbit/s
Determination of transfer rate Automatic transfer rate detection or fixed rate setting
Min. cycle time 1)
Fieldbus No limitations
X2X Link 500 μs
Synchronization between bus systems possible No
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation 0 to 55°C
Vertical installation 0 to 50°C
Derating -
Storage -25 to 70°C
Transport -25 to 70°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20PS9400 or X20PS9402 power supply module separately
Order 1x X20BB80 bus base separately
Spacing 2) 37.5 +0.2 mm
quad Flash
200 200 200 200 200 200 200 1000
triple Flash
200 200 200 200 200 1000
double Flash
200 200 200 1000
single Flash
200 1000
blinkend
200 200
3
blitzend
500
grün/rot
Flickering
50
All times in ms
CANopen interface
Node numbers and transfer rates are configured using the two bus controller number switches.
The transfer rate can be specified in two ways:
• Automatic detection by bus controller (see 4.5.12.8 "Automatic transfer rate detection" on page 566)
• Fixed definition by user (see 4.5.12.9 "Setting the transfer rate" on page 566)
After booting, the bus controller goes into "Listen only" mode. This means the bus controller behaves passively
on the bus and only listens.
The bus controller attempts to receive valid objects. If receive errors occur, the controller switches to the next
transfer rate in the lookup table.
If no objects are received, all transfer rates are tested cyclically. This procedure is repeated until valid objects are
received.
Lookup table
The controller tests the transfer rate according to this table. Beginning with the starting transfer rate (1000 kbit/s),
the controller switches to the next lower transfer rate. At the end of the table, the bus controller restarts the search
from the beginning.
Transfer rate
1000 kbit/s
800 kbit/s
500 kbit/s
250 kbit/s
125 kbit/s
100 kbit/s
50 kbit/s
20 kbit/s
10 kbit/s
The bus controller will detect the transfer rate automatically by default. Switch positions 0x80 - 0x88 can be used
to set a fixed transfer rate, or 0x89 can be used to enable automatic transfer rate detection.
Switch position Transfer rate
0x80 1000 kbit/s
0x81 800 kbit/s
0x82 500 kbit/s
0x83 250 kbit/s
0x84 125 kbit/s
0x85 100 kbit/s
0x86 50 kbit/s
0x87 20 kbit/s
0x88 10 kbit/s
0x89 Automatic transfer rate detection
The node number position 0x92 can be used to save automatically generated configurations. This makes it possible
to work with a standardized configuration without having to adapt the application to changes associated with service
work or different development stages for example.
1. Turn off the power supply to the bus controller.
2. Set the node number to 0x90.
3. Turn on the power supply to the bus controller.
4. Wait until the "MS" LED starts blinking green (100 ms on / 200 ms off).
5. The node number switch must be set to 0x00 and then back to 0x90 within this time window of 5 seconds
(rotate the top switch).
6. Wait until the "MS" LED blinks with a red double-flash (parameters have been cleared).
7. Turn off the power supply to the bus controller.
8. Set the node number to 0x92.
9. Turn on the power supply to the bus controller.
10.Wait until the "MS" LED starts blinking green (100 ms on / 200 ms off).
11. The node number switch must be set to 0x02 and then back to 0x092 within this time window of 5 seconds
(rotate the top switch).
12.Wait until the "MS" LED blinks with a red quad-flash (parameters have been saved).
13.Turn off the power supply to the bus controller.
14.Set the desired node number (0x01 - 0x7F).
15.Turn on the power supply to the bus controller.
16.The bus controller boots with the set node number and automatic transfer rate detection.
Information:
A mapping tool for decoding the saved PDO mapping is available in the Download section of the B&R
website (www.br-automation.com).
Additional documentation about bus controller functions as well as the necessary import files for the master engi-
neering tool are available in the Downloads section of the B&R website (www.br-automation.com).
4.6.2 X20BB80
Product ID X20BB80
Short description
Bus module Bus base - backplane for bus controller fieldbus interface and bus controller supply module
General information
Power consumption
Bus 0.35 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
+24 VDC
GND
4.6.3 X20PS9400
The supply module is used together with an X20 bus controller. It is equipped with a feed for the bus controller,
the X2X Link and the internal I/O supply.
• Supply for the bus controller, X2X Link and internal I/O supply
• Feed and bus controller / X2X Link supply electrically isolated
• Redundancy of bus controller / X2X Link supply possible by operating multiple supply modules simultane-
ously
• Service interface (RS232)
Product ID X20PS9400
Brief description
Power supply module 24 VDC supply module for bus controller, X2X Link supply and I/O
Interfaces 1x RS232 service interface
General information
B&R ID code 0x1F8C
Status indicators Overload, operating status, module status, RS232
Diagnostics
Module run/error Yes, using status LED and software
RS232 data transfer Yes, using status LED
Overload Yes, using status LED and software
Power consumption 1)
Bus 1.42 W
Internal I/O 0.6 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Bus - RS232 No
I/O feed - I/O supply No
BC/X2X Link feed - BC/X2X Link supply Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Bus controller / X2X Link supply input
Input voltage 24 VDC -15% / +20%
Input current Max. 0.7 A
Fuse Integrated, cannot be replaced
Reverse polarity protection Yes
4.6.3.5 Pinout
r e
X20 PS 9400
S I
Reserved Reserved
GND GND
The RS232 service interface is not for use in a machine or system application. It is only intended to be used to
update the firmware on various bus controllers and X2X modules as well as to save settings.
PS
10 A slow-blow
BC/X2X Link + + I/O
Power supply _ _ Power supply
+24 VDC
GND
PS
Jumper
10 A slow-blow
+ I/O-
_ Power supply
+24 VDC
GND
4.6.3.8 Derating
The rated output current for the supply is 7.0 W. Derating must be taken into consideration based on mounting
orientation.
Installation position
Horizontal
Vertical
7
Nominal output power
4
[W]
0
-25 40 45 50 55 60
1) The offset specifies the position of the register within the CAN object.
Name:
Module status
The following voltage and current states of the module are monitored in this register:
Bus supply current: A bus supply current of >2.3A is displayed as a warning.
Bus supply voltage: A bus supply voltage of <4.7V is displayed as a warning.
24 VDC I/O supply voltage: An I/O supply voltage of <20.4 V is displayed as a warning.
Function model Data type Value
0 - Standard USINT See bit structure.
254 - Bus controller UINT See bit structure.
Bit structure:
Bit Name Value Information
0 StatusInput01 0 No error
1 Warning - overcurrent (>2.3 A) or undervoltage (<4.7 V)
1 Reserved 0
2 StatusInput02 0 I/O supply above the warning level of 20.4 V
1 I/O supply below the warning level of 20.4 V
3-x Reserved 0
Name:
SupplyCurrent
This register displays the bus supply current measured at a resolution of 0.1 A.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
Name:
SupplyVoltage
This register displays the bus supply voltage measured at a resolution of 0.1 V.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
2 ms
4.6.4 X20PS9402
The supply module is used together with an X20 bus controller. It is equipped with a feed for the bus controller,
the X2X Link and the internal I/O supply.
The module is designed to supply power for smaller X20 systems. Potential groups are able to be formed. An
expansion or redundancy of the X2X Link with the X20PS3300 or X20PS3310 supply module is not possible.
Expansion of the X20 system with a bus transmitter is not permitted either.
• Supply for the bus controller, X2X Link and internal I/O supply
• Low-cost supply module for small X20 system
• Feed and bus controller / X2X Link supply not electrically isolated
• Expansion or redundancy of bus controller / X2X Link supply not possible by operating multiple supply
modules simultaneously
Product ID X20PS9402
Brief description
Power supply module 24 VDC supply module for bus controller, X2X Link supply and I/O
General information
B&R ID code 0xA389
Status indicators Operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Overload Yes, using status LED and software
Power consumption 1)
Bus 1.44 W
Internal I/O 0.6 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
I/O feed - I/O supply No
BC/X2X Link feed - BC/X2X Link supply No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Bus controller / X2X Link supply input
Input voltage 24 VDC -15% / +20%
Input current Max. 0.7 A
Fuse Integrated, cannot be replaced
4.6.4.5 Pinout
r e
X20 PS 9402
I
Reserved Reserved
Reserved Reserved
Reserved Reserved
GND GND
PS
10 A slow-blow
BC/X2X Link + + I/O
Power supply _ _ Power supply
+24 VDC
GND
PS
Jumper
10 A slow-blow
+ I/O-
_ Power supply
+24 VDC
GND
The rated output current for the bus controller / X2X Link supply is 7.0 W. Derating must be taken into consideration
based on mounting orientation.
Installation position
Horizontal
Vertical
4
[W]
0
-25 40 45 50 55 60
1) The offset specifies the position of the register within the CAN object.
Name:
Module status
The following module supply voltages are monitored in this register:
Bus supply voltage: A bus supply voltage of <4.7V is displayed as a warning.
24 VDC I/O supply voltage: An I/O supply voltage of <20.4 V is displayed as a warning.
Function model Data type Value
0 - Standard USINT See bit structure.
254 - Bus controller UINT See bit structure.
Bit structure:
Bit Name Value Information
0 StatusInput01 0 No error
1 Bus supply warning - Undervoltage (<4.7V)
1 Reserved 0
2 StatusInput02 0 I/O supply above the warning level of 20.4 V
1 I/O supply below the warning level of 20.4 V
3-x Reserved 0
Name:
SupplyVoltage
This register displays the bus supply voltage measured at a resolution of 0.1 V.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
2 ms
X20BM11 X20BM01
Figure 228: The bus module replaces the rack in the X20 system
The bus module is the backbone of the X20 system regarding the bus supply and bus data as well as the I/O supply
for the electronics modules. Each bus module is an active bus station, even without an electronics module. There
are two variations of the bus module:
• Interconnected I/O supply
• I/O supply isolated to the left (for power supply modules)
4.7.2 X20BM01
The X20BM01 bus module is the base for all X20 supply modules.
• Basis for all X20 supply modules
• For creating voltage groups
• The internal I/O supply is isolated to the left
Product ID X20BM01
Brief description
Bus module Power supply bus module, 24 VDC keyed, internal I/O supply interrupted to the left
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
+24 VDC
GND
4.7.3 X20BM05
The X20BMx5 safety bus modules have node number switches that can be used to set permanent addresses.
Placing one of these modules at the beginning of an X20 block ensures a unique address. The addresses of
subsequent modules are automatically set in ascending order starting at this address. This simple feature greatly
increases the flexibility of applications.
Another advantage: Addresses can be set independently of which specific I/O modules are used. All that is required
are the respective bus modules. This provides logistical advantages with respect to cost and the variety of parts.
• The X20BM05 is the base for all X20 supply modules
• For creating voltage groups
• The internal I/O supply is isolated to the left
• Manual node number assignment
• Independent of electronics module
• Manual and automatic addressing can be combined as desired
Product ID X20BM05
Short description
Bus module Supply bus module, internal I/O supply is isolated to the left, manual node number assignment
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
+24 VDC
GND
x16
x1
4.7.4 X20BM11
The bus module serves as the base for all 24 VDC X20 I/O modules. The internal I/O supply is interconnected.
• Bus module for 24 VDC I/O modules
• The internal I/O supply is interconnected
Product ID X20BM11
Short description
Bus module Bus module for 24 VDC I/O modules, the internal I/O supply is interconnected
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
4.7.5 X20BM12
The bus module serves as the base for all 240 VAC X20 I/O modules. The internal I/O supply is interconnected.
• Bus module for 240 VAC I/O modules
• The internal I/O supply is interconnected
• 240 V coding for bus module, electronic module and terminal block
Product ID X20BM12
Short description
Bus module Bus module for 240 VAC I/O modules, the internal I/O supply is interconnected
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
4.7.6 X20BM15
The X20BMx5 safety bus modules have node number switches that can be used to set permanent addresses.
Placing one of these modules at the beginning of an X20 block ensures a unique address. The addresses of
subsequent modules are automatically set in ascending order starting at this address. This simple feature greatly
increases the flexibility of applications.
Another advantage: Addresses can be set independently of which specific I/O modules are used. All that is required
are the respective bus modules. This provides logistical advantages with respect to cost and the variety of parts.
• The X20BM15 is the base for all X20 24 VDC I/O modules
• The internal I/O supply is interconnected
• Manual node number assignment
• Independent of electronics module
• Manual and automatic addressing can be combined as desired
Product ID X20BM15
Short description
Bus module Bus module for 24 VDC I/O modules, the internal I/O sup-
ply is interconnected, manual node number assignment
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
x16
x1
4.7.7 X20BM21
The X20BM21 bus module serves as a basis for all double-width X20 I/O modules. The internal I/O supply is
isolated to the left. This allows the X20BM21 bus module to be used to set up a separate voltage group if the
X20BT9100 bus transmitter is used for the supply.
• For creating voltage groups
• The internal I/O supply is isolated to the left
Product ID X20BM21
Short description
Bus module Double-width bus module, internal I/O supply is isolated to the left
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
+24 VDC
GND
4.7.8 X20BM31
The X20BM31 bus module serves as a basis for all double-width X20 I/O modules. The internal I/O supply is
interconnected.
• Bus module for double-width I/O modules
• The internal I/O supply is interconnected
Product ID X20BM31
Short description
Bus module Double-width bus module, the internal I/O supply is interconnected
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
4.7.9 X20BM32
The bus module serves as the base for all double-width 240 VAC X20 I/O modules. The internal I/O supply is
interconnected.
• Bus module for double-width 240 VAC I/O modules
• The internal I/O supply is interconnected
• 240 V coding for bus module, electronic module and terminal block
Product ID X20BM32
Short description
Bus module Double-width bus module for 240 VAC I/O modules, the internal I/O supply is interconnected
General information
Power consumption
Bus 0.13 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
4.8.2 X20BR9300
The bus receiver X20BR9300 is used to connect the X20 System to the X2X Link. The module is equipped with
a feed for the X2X Link as well as the internal I/O supply.
The left and right end plates are included in the delivery.
• X2X Link bus receiver
• Feed for X2X Link and internal I/O supply
• Electrical isolation of feed and X2X Link supply
• Redundancy of X2X Link supply possible by operating multiple supply modules simultaneously
• Operation only on the slot to the far left
Information:
This module is NOT PERMITTED to be used together with continuous power supply modules (e.g.
X20BM11 or X20BM15) since this can result in problems with X2X Link!
Product ID X20BR9300
Short description
Bus receiver X2X Link bus receiver with supply for I/O and bus
General information
B&R ID code 0x1BC1
Status indicators X2X bus function, overload, operating status, module status
Diagnostics
Module run/error Yes, with status LED and software status
Overload Yes, with status LED and software status
X2X bus function Yes, with status LED
Power consumption 1)
Bus 1.62 W
Internal I/O 0.6 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
I/O feed - I/O supply No
X2X Link feed - X2X Link supply Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
X2X Link supply input
Input voltage 24 VDC -15% / +20%
Input current Max. 0.7 A
Fuse Integrated, cannot be replaced
Reverse polarity protection Yes
X2X Link supply output
Nominal output power 7.0 W
Parallel operation Yes 2)
Redundant operation Yes
Overload behavior Short circuit / temporary overload protection
Input I/O supply
Input voltage 24 VDC -15% / +20%
Fuse Required line fuse: Max. 10 A, slow-blow
Reverse polarity protection No
Output I/O supply
Rated output voltage 24 VDC
Behavior if a short circuit occurs Required line fuse
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating For >55°C nominal output power for X2X Link supply is limited to max. 5 W
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM01 supply bus module separately
Left and right X20 locking plates included in delivery
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Double flash LED indicates one of the following states:
• X2X Link power supply is overloaded
• I/O supply too low
• Input voltage for X2X Link supply too low
e+r Red on / Green single flash Invalid firmware
X Orange Off No communication at the X2X Link
On X2X Link communication in progress
l Red Off X2X Link supply in the acceptable range
On X2X Link power supply is overloaded
Solution: Use an additional feed module X20PS3300
4.8.2.5 Pinout
r e
X20 BR 9300
X I
X2X X2X\
X2X⊥
GND GND
BR
X2X
X2X\
X2X⊥
10 A slow-blow
X2X Link + + I/O
Power supply _ _ Power supply
+24 VDC
GND
BR
X2X
X2X\
X2X⊥
Jumper
10 A slow-blow
+ I/O
_ Power supply
+24 VDC
GND
4.8.2.7 Derating
The rated output current for the supply is 7.0 W. Derating must be taken into consideration based on mounting
orientation.
Installation position
Horizontal
Vertical
7
Nominal output power
4
[W]
0
-25 40 45 50 55 60
1) The offset specifies the position of the register within the CAN object.
Name:
Module status
The following voltage and current states of the module are monitored in this register:
Bus supply current: A bus supply current of >2.3A is displayed as a warning.
Bus supply voltage: A bus supply voltage of <4.7V is displayed as a warning.
24 VDC I/O supply voltage: An I/O supply voltage of <20.4 V is displayed as a warning.
Function model Data type Value
0 - Standard USINT See bit structure.
254 - Bus controller UINT See bit structure.
Bit structure:
Bit Name Value Information
0 StatusInput01 0 No error
1 Warning - overcurrent (>2.3 A) or undervoltage (<4.7 V)
1 Reserved 0
2 StatusInput02 0 I/O supply above the warning level of 20.4 V
1 I/O supply below the warning level of 20.4 V
3-x Reserved 0
Name:
SupplyCurrent
This register displays the bus supply current measured at a resolution of 0.1 A.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
Name:
SupplyVoltage
This register displays the bus supply voltage measured at a resolution of 0.1 V.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
2 ms
4.8.3 X20BT9100
The bus transmitter provides for the seamless expansion of the X20 System. The stations can be up to 100 m
away from each other.
• X2X Link bus transmitter
• For seamless expansion of the system
• Up to 100 m segment lengths
• Feed for internal I/O supply
• Operation only on the slot to the far right
Information:
The bus transmitter modules may only be operated with a bus module where the internal I/O supply
is connected through (e.g. X20BM11).
If the incoming voltage is used for internal I/O supply, then this potential group must not be supplied by
any other module. An I/O module with bus module X20BM01 should be used to separate the potential
group.
Product ID X20BT9100
Short description
Bus transmitter X2X Link bus transmitter with supply for I/O
General information
B&R ID code 0x1BC2
Status indicators X2X bus function, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software
X2X bus function Yes, using status LED
Power consumption 1)
Bus 0.5 W
Internal I/O
As bus transmitter 0.1 W
Additionally as supply module 0.6 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Input I/O supply
Input voltage 24 VDC -15% / +20%
Fuse Required line fuse: Max. 10 A, slow-blow
Reverse polarity protection No
Output I/O supply
Rated output voltage 24 VDC
Behavior if a short circuit occurs Required line fuse
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB06 or X20TB12 terminal block separately
Order 1x X20BM11 or X20BM15 bus module separately
Spacing 12.5 +0.2 mm
4.8.3.5 Pinout
r e
X20 BT 9100
X
X2X X2X\
X2X⊥
+24 V I/O
GND
BT
X2X\
X2X
X2X⊥
+24 VDC
GND
BT
X2X\
X2X
X2X⊥
10 A slow-blow
+ I/O
_ Power supply
+24 VDC
GND
Figure 240: Connection example - With feed for internal I/O supply
The bus transmitter has an integrated internal I/O supply feed. This saves a power supply module for the last
potential group.
Keep in mind: this potential group is separated from the rest of the potential groups by an I/O module with the
X20BM01 bus module.
I/O module + BM01
BR9300 + BM01
PS2100 + BM01
BT9x00 + BM11
X2X
I/O I/O I/O
Link
U2/24 VDC
The bus transmitter establishes the connection to the next X2X Link based I/O node. It is important to be sure that
only the data lines are connected on. X2X Link supply is system dependant.
System X2X Link supply
X67 system System supply X67PS1300
Remote I/O with X2X Link (XX modules) 24 VDC external supply
Remote valve terminal connection (XV modules) 24 VDC external supply
XV
X20 system
Compact I/O
1) The offset specifies the position of the register within the CAN object.
Name:
Module status
The following module supply voltages are monitored in this register:
Bus supply voltage: A bus supply voltage of <4.7V is displayed as a warning.
24 VDC I/O supply voltage: An I/O supply voltage of <20.4 V is displayed as a warning.
Function model Data type Value
0 - Standard USINT See bit structure.
254 - Bus controller UINT See bit structure.
Bit structure:
Bit Name Value Information
0 StatusInput01 0 No error
1 Bus supply warning - Undervoltage (<4.7V)
1 Reserved 0
2 StatusInput02 0 I/O supply above the warning level of 20.4 V
1 I/O supply below the warning level of 20.4 V
3-x Reserved 0
Name:
SupplyVoltage
This register displays the bus supply voltage measured at a resolution of 0.1 V.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
2 ms
4.8.4 X20BT9400
To connect an X20 system to an X67 system, a bus transmitter is simple added to the end of the X20 block, so
that the X2X Link cable can be connected. The bus transmitter also provides the X2X supply voltage for the X67
system. There is no longer a need for an X67 system supply module.
• X2X Link bus transmitter
• For seamless expansion of the system
• Up to 100 m segment lengths
• Feed for internal I/O supply
• Integrated X2X Link supply for the X67 system
• Operation only on the slot to the far right
Information:
The bus transmitter modules may only be operated with a bus module where the internal I/O supply
is connected through (e.g. X20BM11).
If the incoming voltage is used for internal I/O supply, then this potential group must not be supplied by
any other module. An I/O module with bus module X20BM01 should be used to separate the potential
group.
Product ID X20BT9400
Short description
Bus transmitter X2X Link bus transmitter with supply for I/O and integrated supply for the X67 system
General information
B&R ID code 0xA238
Status indicators X2X bus function, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software
X2X bus function Yes, using status LED
Power consumption 1)
Bus 0.5 W
Internal X67 X2X Link 1.38 W
Internal I/O
As bus transmitter 0.1 W
Additionally as supply module 0.6 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
X67 X2X Link supply input
Input voltage 24 VDC -15% / +20%
Input current Max. 0.5 A
Fuse Integrated, cannot be replaced
Reverse polarity protection Yes
X67 X2X Link supply output
Parallel connection with X67PS1300 Yes 2)
Overload behavior Temporarily protected against short circuit, overload
Be aware of corresponding status message (LED "I") or evaluate software status
X67 modules supplied by BT9400
Horizontal installation Max. 8 (Nominal output power: 6 W)
Vertical installation Max. 6 (Nominal output power: 4.5 W)
Input I/O supply
Input voltage 24 VDC -15% / +20%
Fuse Required line fuse: Max. 10 A, slow-blow
Reverse polarity protection No
Output I/O supply
Rated output voltage 24 VDC
Behavior if a short circuit occurs Required line fuse
Permitted contact load 10 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM11 or 1x X20BM15 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Double flash LED indicates one of the following states:
• I/O supply too low
• X2X Link voltage too low
e+r Red on / Green single flash Invalid firmware
X Orange Off No X2X Link communication
On X2X Link communication active
l Red Off The X67 / X2X Link supply is within the valid limits
On The X67 / X2X Link supply for the power supply is overloaded
Remedy: Use additional X67PS1300 supply modules
4.8.4.5 Pinout
r e
X20 BT 9400
X I
X2X X2X\
X2X+ X2X⊥
GND GND
BT
X2X\
X2X
X2X⊥
X2X+
10 A slow-blow
X67 X2X Link + + I/O
Power supply _ _ Power supply
+24 VDC
GND
BT
X2X\
X2X
X2X⊥
X2X+
Jumper
10 A slow-blow
+ I/O
_ Power supply
+24 VDC
GND
BT
X2X\
X2X
X2X⊥
X2X+
Jumper
+24 VDC
GND
The bus transmitter has an integrated internal I/O supply feed. This saves a power supply module for the last
potential group.
Keep in mind: this potential group is separated from the rest of the potential groups by an I/O module with the
X20BM01 bus module.
PS2100 + BM01
BT9x00 + BM11
X2X
I/O I/O I/O
Link
U2/24 VDC
The bus transmitter establishes the link between the X20 system and the X67 system. In addition to the data lines,
the X2X Link supply is also fed through. The module can supply up to 8 X67 modules. An additional X67 supply
module is only needed if operating more than 8 X67 modules.
Information:
Only the X67PS1300 system supply module can be used for calculating the total number of X67 mod-
ules.
1) The offset specifies the position of the register within the CAN object.
Name:
Module status
The following module supply voltages are monitored in this register:
X67 bus supply current: An X67 bus supply current of >0.4 A is displayed as a warning.
X67 bus supply voltage: A bus supply voltage of <18 V is displayed as a warning.
24 VDC I/O supply voltage: An I/O supply voltage of <20.4 V is displayed as a warning.
Function model Data type Value
0 - Standard USINT See bit structure.
254 - Bus controller UINT See bit structure.
Bit structure:
Bit Name Value Information
0 No error
0 StatusInput01 X67 bus supply warning for undervoltage (18 V) or when over-
1
current (0.4 A)
1 Reserved 0
0 I/O supply above the warning level of 20.4 V
2 StatusInput02
1 I/O supply below the warning level of 20.4 V
3-x Reserved 0
Name:
SupplyCurrent
This register shows the X67 bus supply current with a resolution of 0.01 A.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
Name:
SupplyVoltage
This register shows the X67 bus supply voltage with a resolution of 0.1 V.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
2 ms
Compact CPU
X20 CP 02xx
Terminal block
X20 TB 12
Figure 247: The four parts of the Compact CPU - Compact CPU, bus module, supply module, terminal block
Adaptable to individual requirements
• Embedded µP 25 with Ethernet on-board
• Embedded μP 16 with or without Ethernet on-board
• Supply module for Compact CPU, X2X Link bus supply and I/O
• RS232 interface connection
• CAN bus connection
• Without or without electrical isolation of the CPU/X2X Link supply
• 12-pin terminal block
The battery-free CPU
To meet the high demands of the market, the Compact CPU was designed to run without a battery. This makes it
completely maintenance-free. The following features make operation without a buffer battery possible.
The real-time clock is buffered for approx. 1000 hours by a gold foil capacitor.
This FRAM stores its contents ferroelectrically. Unlike normal SRAM, this does not require a battery.
Compact design
Despite the sleek profile of only 37.5 mm, the CPU supply, the X2X Link bus supply, and the I/O module supply
are integrated in the CPU. No additional power modules are necessary.
Compact CPUs are ideal for situations where cycle times in the millisecond range are sufficient and a cost-benefit
analysis plays a decisive role. A range of models with CAN and Ethernet can adapt optimally to all demands. The
result: extremely sleek automation solutions.
• Embedded µP 16 / μP 25 with additional I/O processor
• 100/750 kB User SRAM
• 1 MB / 3 MB User FlashPROM
• X20CP0291 and X20CP0292: Onboard Ethernet
• Only 37.5 mm wide
• No battery
X20CP0201
IF2 - Ethernet
Terminal block for CPU
and I/O supply
RS232 connection
CAN bus connection (with BB27)
Figure 249: X20 compact CPUs - Operating elements for X20CP0291 and X20CP0292
X20CP0201
When used with the X20BB27 bus module, the X20CP0201 has access to a CAN bus interface. The INA2000
station number for CAN is set using the node number switches.
X20CP0291 and X20CP0292
Both of these CPUs are equipped with an onboard Ethernet interface. When used with the X20BB27 bus module,
they also have access to a CAN bus interface.
The number set using the two hex switches defines the INA2000 station number of both the CAN and the Ethernet
interface.
Figure 251: X20 compact CPUs - Ethernet interface for X20CP0291 and X20CP0292
The X20CP0291 and X20CP0292 are equipped with an Ethernet interface. The connection is made using a 100
BASE-T twisted pair RJ45 socket.
Pinout
Interface Pinout
Pin Ethernet
1 RXD Receive data
2 RXD\ Receive data\
1
3 TXD Transmit data
4 Termination
5 Termination
6 TXD\ Transmit data\
Shielded RJ45 port 7 Termination
8 Termination
Information about cabling X20 modules with an Ethernet interface can be found in the module's download section
on the B&R website (www.br-automation.com).
Information:
The Ethernet interface (IF2) is not suited for POWERLINK.
Starting with operating system version 1.07, CPUs have a default IP address.
IP address: 192.168.0.1
Subnet mask: 255.255.0.0
General information
CPUs are delivered with a runtime system. When delivered, the node number switch is set to switch position 0x00
(bootstrap loader mode).
A suitable switch position must be set (0x01 to 0xFE) in order to boot the PLC in RUN mode. Updating the runtime
system is only possible in RUN mode.
Runtime system update
The runtime system can be updated via the programming environment. When updating the runtime system via an
online connection, the following procedure must be carried out:
1. An online runtime system update is only possible if the processor is in RUN mode. For this to be true, the
node number must be set to a value in the range 0x01 to 0xFE.
2. Switch on the power.
3. The runtime system update is performed via the existing online connection. The online connection can be
established via the onboard serial RS232 interface, for example. If a CPU has an Ethernet interface, then it
too can be used to perform the update.
4. Start B&R Automation Studio.
5. Start the update procedure by selecting Online from the Project menu. Select Transfer Automation Run-
time from the pop-up menu. Now follow the instructions given by B&R Automation Studio.
6. A window opens up for setting the runtime system version. The runtime system version is already pre-selected
by the project settings made by the user. The drop-down menu can be used to select one of the runtime
system versions stored in the project. Clicking on the Browse button allows a runtime system version to be
loaded from the hard drive or CD.
Clicking on Next opens a pop-up window that allows the user to select whether modules with target memory
SYSTEM ROM should be transferred during the subsequent runtime system update. If not, these modules
can also be transferred later during an application download.
Clicking on Next opens a dialog box where the user can set the CAN transfer rate, CAN ID and CAN node
number (the CAN node number set here is only relevant if an interface module does not have a CAN node
number switch). The CAN node number must be between decimal 01 and 99. Assigning a unique node
number is especially important with online communication over a CAN network (INA2000 protocol).
7. The update procedure is started by clicking on Next. Update progress is shown in a message box.
Information:
User flash memory is deleted.
8. When the update procedure is complete, the online connection is reestablished automatically.
9. The PLC is now ready for use.
Updating the runtime system is possible not only via an online connection, but also via a CAN network, serial
network (INA2000 protocol) or Ethernet network, depending on the system configuration.
4.10.2 X20BB22
The X20BB22 bus module is the base for all X20 Compact CPUs.
The left and right end plates are included in the delivery.
• Base for all X20 Compact CPUs
• RS232 connection
Product ID X20BB22
Short description
Bus module X20 Compact CPU base - backplane for Compact CPU and Compact CPU supply module
Interfaces 1x RS232 connection
General information
Power consumption
Bus 0.32 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Bus - RS232 No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No derating
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
Protection in accordance with EN 60529 IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Storage -40 to 85°C
Transport -40 to 85°C
+24 VDC
GND
4.10.3 X20BB27
The X20BB27 bus module is the base for all X20 Compact CPUs.
The left and right end plates are included in the delivery.
• Base for all X20 Compact CPUs
• RS232 connection
• CAN bus connection
• Integrated terminating resistor for CAN bus
Product ID X20BB27
Short description
Bus module X20 Compact CPU base - backplane for Compact CPU and Compact CPU supply module
Interfaces 1x RS232 connection, 1x CAN bus connection
General information
Power consumption
Bus 0.53 W
Internal I/O -
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Bus - CAN bus No
Bus - RS232 No
RS232 - CAN bus No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
I/O supply
Nominal voltage 24 VDC
Permitted contact load 10.0 A
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at altitudes above sea level
0 to 2000 m No derating
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
Protection in accordance with EN 60529 IP20
+24 VDC
GND
On Off
The bus module has an integrated CAN bus terminating resistor. The terminating resistor is turned on and off with
a switch. An active terminating resistor is indicated on the supply module by the T LED.
4.10.4 X20PS9500
The X20PS9500 supply module is used together with an X20 compact or fieldbus CPU. It has a feed for the compact
or fieldbus CPU, the X2X Link and the internal I/O supply.
• Supply for the compact or fieldbus CPU, X2X Link, and internal I/O supply
• Electrical isolation of feed and CPU / X2X Link supply
• Redundancy of CPU / X2X Link supply possible by operating multiple supply modules simultaneously
• RS232 interface configurable as online interface
• CAN bus
Product ID X20PS9500
Brief description
Power supply module 24 VDC supply module for compact or fieldbus CPU, X2X Link supply and I/O
Interfaces 1x RS232, 1x CAN bus 1)
General information
B&R ID code 0x2018
Status indicators Overload, operating state, module status, RS232, CAN bus 1)
Diagnostics
Module run/error Yes, using status LED and software
CAN bus data transfer 1) Yes, using status LED
RS232 data transfer Yes, using status LED
Overload Yes, using status LED and software
Power consumption 2)
Bus 1.42 W
Internal I/O 0.6 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
CPU/X2X Link feed - CPU/X2X Link supply Yes
I/O feed - I/O supply No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
CPU / X2X Link supply input
Input voltage 24 VDC -15% / +20%
Input current Max. 0.7 A
Fuse Integrated, cannot be replaced
Reverse polarity protection Yes
CPU / X2X Link supply output
Nominal output power 7.0 W
Parallel operation Yes 3)
Redundant operation Yes
Overload behavior Short circuit / temporary overload protection
Input I/O supply
Input voltage 24 VDC -15% / +20%
Fuse Required line fuse: Max. 10 A, slow-blow
Reverse polarity protection No
Output I/O supply
Rated output voltage 24 VDC
Behavior if a short circuit occurs Required line fuse
Permitted contact load 10.0 A
Interfaces
IF1 interface
Signal RS232
Design Connection made using 12-pin X20TB12 terminal block
Transfer rate Max. 115.2 kbit/s
IF3 interface 1)
Signal CAN bus
Design Connection made using 12-pin X20TB12 terminal block
Transfer rate Max. 1 Mbit/s
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating See section "Derating"
Storage -40 to 85°C
Transport -40 to 85°C
4.10.4.5 Pinout
r e
X20 PS 9500
S I
C T
GND GND
PS
10 A slow-blow
CPU / X2X Link + + I/O
supply _ _ supply
+24 VDC
GND
PS
Jumper
10 A slow-blow
+ I/O-
_ Power supply
+24 VDC
GND
4.10.4.7 Derating
The rated output current for the supply is 7.0 W. Derating must be taken into consideration based on mounting
orientation.
Installation position
Horizontal
Vertical
7
Nominal output power
4
[W]
0
-25 40 45 50 55 60
Name:
Module status
The following module supply voltages are monitored in this register:
Bus supply current: A bus supply current of >2.3A is displayed as a warning.
Bus supply voltage: A bus supply voltage of <4.7V is displayed as a warning.
24 VDC I/O supply voltage: An I/O supply voltage of <20.4 V is displayed as a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 StatusInput01 0 No error
1 Warning - overcurrent (>2.3 A) or undervoltage (<4.7 V)
1 Reserved 0
2 StatusInput02 0 I/O supply above the warning level of 20.4 V
1 I/O supply below the warning level of 20.4 V
3-x Reserved 0
Name:
SupplyCurrent
This register displays the bus supply current measured at a resolution of 0.1 A.
Function model Data type
0 - Standard USINT
Name:
SupplyVoltage
This register displays the bus supply voltage measured at a resolution of 0.1 V.
Function model Data type
0 - Standard USINT
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
2 ms
4.10.5 X20PS9502
The X20PS9502 supply module is used together with an X20 Compact or Fieldbus CPU. It is equipped with a feed
for the Compact or Fieldbus CPU, the X2X Link and the internal I/O supply.
The module is intended as a low-cost supply module for small X20 Systems. Voltage groups are able to be formed.
An expansion or redundancy of the X2X Link with the X20PS3300 or X20PS3310 supply module is not possible.
Expansion of the X20 System with a bus transmitter is not permitted either.
• Supply for the Compact or Fieldbus CPU, X2X Link, and internal I/O supply
• Low-cost supply module for small X20 Systems
• No electrical isolation of feed and CPU / X2X Link supply
• Expansion or redundancy of CPU / X2X Link supply not possible by operating multiple supply modules
simultaneously
• RS232 can be configured as an online interface
• CAN bus
Product ID X20PS9502
Short description
Power supply module 24 VDC supply module for compact or fieldbus CPU, X2X Link bus supply and I/O
Interfaces 1x RS232, 1x CAN bus 1)
General information
B&R ID code 0xA38A
Status indicators Operating state, module status, RS232, CAN bus 1)
Diagnostics
Module run/error Yes, with status LED and software status
CAN bus data transfer 1) Yes, with status LED
RS232 data transfer Yes, with status LED
Overload Yes, with status LED and software status
4.10.5.5 Pinout
r e
X20 PS 9502
S
C T
GND GND
PS
10 A slow-blow
CPU / X2X Link + + I/O
supply _ _ supply
+24 VDC
GND
PS
Jumper
10 A slow-blow
+ I/O-
_ Power supply
+24 VDC
GND
The rated output power for the CPU / X2X Link supply is 7.0W. Derating may be necessary depending on the
mounting orientation.
Installation position
Horizontal
Vertical
4
[W]
0
-25 40 45 50 55 60
Name:
Module status
The following module supply voltages are monitored in this register:
Bus supply voltage: A bus supply voltage of <4.7V is displayed as a warning.
24 VDC I/O supply voltage: A supply voltage of <20.4V is displayed as a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 No error
0 StatusInput01
1 Bus supply warning - Undervoltage (<4.7V)
1 0 Reserved
0 I/O supply above the warning level of 20.4V
2 StatusInput02
1 I/O supply below the warning level of 20.4V
3-x 0 Reserved
Name:
SupplyVoltage
This register displays the bus supply voltage measured at a resolution of 0.1 V.
Function model Data type
0 - Standard USINT
254 - Bus controller UINT
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
2 ms
4.11.2 X20CM1941
The module is equipped with a resolver input and a configurable ABR output.
• Resolver input (differential), with angular position and cyclic counter
• 14-bit resolution for the angular position
• ABR output (configurable)
Product ID X20CM1941
Short description
I/O module 1 resolver input, 1 ABR output
General information
B&R ID code 0x1E85
Status indicators Input, output, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software
Resolver input (OK, open line) Yes, using status LED and software
Resolver input (counter direction) Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Input/Output - Bus Yes
Input/Output - Module supply No
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Resolver inputs
Resolver transformation ratio 0.5 (±10%)
Reference output
Output voltage 34 Veff
Output current Max. 50 mAeff
Frequency 10 kHz
Type Differential
Angular position resolution 14-bit
Short circuit protection (reference output) Yes
Input impedance 10.4 kΩ - j 11.1 kΩ
Resolver type BRX
BRT with limitations
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash Warning/Error on an I/O channel. Level monitoring for digital outputs has been
triggered.
e+r Red on / Green single flash Invalid firmware
1 Green On Resolver connected and OK
Off Open line or no resolver connected
U Orange UP: Counts up
D Orange DOWN: Counts down
4.11.2.5 Pinout
r e
X20 CM 1941
1
U
D
COS A
/COS /A
SIN B
/SIN /B
REF R
/REF /R
CM
Resolver
COS
/COS
SIN
/SIN
REF
/REF
COS
ADC
/COS
Band-pass
10 kHz
SIN
ADC
/SIN
Ref
FPGA
/Ref
Band-pass
10 kHz
/A
/B
/R
Up to firmware version 4
The module measures the resolver's current angular position every 100 µs. The value for A, B or R is generated
immediately from the highest value bits (depending on configuration bit 8 to 10).
Firmware version 5 or higher
The procedure shown above reaches its limits as soon as more than one LSB difference occurs from one position
measurement to the next since only one edge of A or B is possible every 100 µs.
To achieve higher clock rates on the ABR encoder (and therefore higher rotational speeds) while simultaneously
improving temporal jitter, the ABR signal is no longer derived directly from the most recent measurement value,
but rather generated through interpolation between consecutive position measurements determined every 100 µs.
Information:
In comparison to firmware versions ≤4, the ABR outputs have a constant time offset of 250 μs. See
also "Comparison of the timing of the ABR outputs between Firmware version 4 and 5".
Comparison of the timing of the ABR outputs between Firmware version 4 and 5
Angular position
0x0180
0x0100
0x0080
0x0000
0xFF80
0xFF00
0xFE80
100 µs
B
R
A
9-bit
B
R
A
10-bit
B
R
B
R
A
9-bit
B
R
A
10-bit
B
R
1) The offset specifies the position of the register within the CAN object.
Name:
ConfigOutput01
This register can be used to set or move the zero position for the resolver. The zero position/offset specification
refers to the current resolver position.
Data type Value
UINT 0 to 65,535
Name:
ConfigOutput02
This register can be used to configure the resolution of the ABR emulation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Number of bits 0 8-bit = 256 increments/rotation
1 9-bit = 512 increments/rotation
2 10-bit = 1024 increments/rotation
3 11-bit = 2048 increments/rotation
4 12-bit = 4096 increments/rotation
5-7 Not permitted
3-7 Reserved -
Name:
Position
The current angle position of the resolver is shown in this register. The value consists of:
• The two upper bytes, which correspond to the number of rotations counted from -32768 (0x8000xxxx) to
+32767 (0x7FFFxxxx)
• The two lower bytes, which correspond to the angle position within the current rotation 1 LSB = 360° / 65536
The position value can, however, be interpreted exactly as an individual 32-bit long angle with resolution 1 / 65536
* 360°.
Data type Value Information
DINT 0x0000xxxx to 0xFFFFxxxx Number of rotations (cyclic)
0xxxxx0000 to 0xxxxxFFFF Angle position within the current rotation
Example
0x7FFF0080 corresponds to 32767 rotations, and 128 / 65536 * 360 = 0.703°.
Name:
StatusInput
This register shows a potential open line between the module and the encoder.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Open line 0 No open line
1 Open line
1- 7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
200 µs
4.11.3 X20DC1176
The module is equipped with 1 input for an ABR incremental encoder with 5 V encoder signal. The encoder inputs
are monitored (A, B, R, A\, B\, R\).
• 1 ABR incremental encoder 5 V
• Encoder input monitoring
• 2 additional inputs, e.g. for latch input
• 5 VDC, 24 VDC and GND for encoder supply
Product ID X20DC1176
Brief description
I/O module 1 ABR incremental encoder 5 V
General information
B&R ID code 0xA706
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.0 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC (-15% / +20%)
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≤2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Additional functions Latch input
Input resistance 7.03 kΩ
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash The encoder monitor has detected a line fault on the encoder inputs. The status
bits must be evaluated in order to provide a more detailed definition of this error.
The following error states are detected:
• Open line
• Short-circuit or voltage level too low
On Error or reset status
A1 Green Input state of counter input A
B1 Green Input state of counter input B
R1 Green Input state of reference pulse R
1-2 Green Input state of the corresponding digital input
4.11.3.5 Pinout
r e
X20 DC 1176
A1
B1
R1
1 2
A A\
B B\
R R\
DI 1 DI 2
Encoder 24 V+ Encoder 5 V+
GND GND
DC
A
A\
Counter 1
B
B\
R
R\
Sensor 1
Counter inputs
ABR
LED (green)
24 V
PTC
Encoder 24 V
24 V
DC
Encoder 5 V
DC
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
1) The offset specifies the position of the register within the CAN object.
The following registers are used for setting functions and configuring the module.
Name:
CfO_BWCNTEnableMaskChannel7_0
This register requires individually enabling error monitoring for each of the signal channels. "Open line", "short
circuit" and "voltage level too low" are reported as error states. Any errors that occur are reported in the error status
registers BW_Channel_x.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Enable error monitoring for signal A lines 0 Error monitoring - Encoder Signal A disabled
1 Error monitoring - Encoder Signal A enabled - Only default in
bus controller function model
1 Enable error monitoring for signal B lines 0 Error monitoring - Encoder Signal B disabled
1 Error monitoring - Encoder Signal B enabled - Only default in
bus controller function model
2 Enable error monitoring for signal R lines 0 Error monitoring - Encoder Signal R disabled
1 Error monitoring - Encoder Signal R enabled - Only default in
bus controller function model
3-7 Reserved 0
Name:
CfO_BWQuitTime_0
This register can be used to enable an additional automatic acknowledgment of the error status through timing.
If a valid time is set, then the acknowledgment can still be made manually, the only difference is that automatic
acknowledgment will take place on the module after the defined amount of time has passed. If the error state has
not yet been corrected, then the error status remains and the time is reset. Make sure that the time is set long
enough for the higher-level system to reliably detect the status messages.
If the timing = 0, then acknowledgment is only possible using the cyclic acknowledgment registers.
Data type Value Information
UDINT 0 No automatic acknowledgment - Only default in bus controller function model
1 to 2.147.483.647 Time for automatic acknowledgment [μs]
Name:
CfO_LatchMode
This register is used to set the latch mode:
• Single shot latch mode:
The latch function must be enabled/set. After a successful latch procedure, the activation must be reset in
order for a new latch procedure to be activated.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired.
A changed counter state on Encoder01LatchCount indicates that the latch procedure has been performed. The
counter value is stored in the latch register Encoder01Latch.
Data type Value Information
USINT 0 Single shot latch procedure
1 Continuous latch procedure
Name:
CfO_LatchComparator
This register defines the signal channels and their level for triggering the latch procedure.
• This mainly configures which channels are linked to generate the latch event. All three signals from the
encoder and digital input 1 can be used for the "AND" operation.
• The "active voltage level" needed for the latch procedure can now be used according to the physical signals.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Defines signal level for encoder signal A 0 Low
1 High
1 Defines signal level for encoder signal B 0 Low
1 High
2 Defines signal level for encoder signal R 0 Low
1 High
3 Defines signal level for digital input 1 0 Low
1 High
4 Use encoder signal A to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal A
5 Use encoder signal B to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal B
6 Use encoder signal R to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal R
7 Use digital input 1 to trigger latch procedure 0 Disabled
1 Latch function linked to digital input 1
The following registers must be set to the specified constant value for correct physical configuration:
Name:
CfO_SIframeGenID
Data type Value Information
USINT 9 Only default in the bus controller module
Name:
CfO_SystemCycleTime
Data type Value Information
UINT 800 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh01
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh02
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh03
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh04
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh05
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_BWQuitTimeSelChannel7_0
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_CounterCycleSelect
Data type Value Information
USINT 2 Only default in the bus controller module
Name:
CfO_CounterMode
Data type Value Information
USINT 3 Only default in the bus controller module
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
Encoder01
The counter state of the incremental encoder is displayed as a 16 or 32-bit counter value. Only the 16-bit value
is available in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01TimeValid
The net time of the last valid counter value is the time of the last valid counter value recorded on the module. The
user is able to determine the validity of the counter value by evaluating its age in the program. This means that the
module and error status bits do not have to be checked additionally to determine the validity of the value.
The net time of the last valid counter value that was read is displayed as a 16 or 32-bit value. Only the 16-bit value
is available in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01TimeChanged
For slow X2X Link cycles, the net time of the last counter value change can be used to more accurately determine
the speed.
The net time of the last counter value change is displayed as 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01Latch
The counter value at the time of the last latch is displayed as a 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01LatchCount
The latch events are counted and stored in a cyclic 8-bit counter. This counter is incremented with each latch event,
thereby indicating a new occurrence. The new latched counter value is stored in the respective latch register.
Data type Value
SINT -128 to 127
Name:
Encoder01Command
This register can be used to
1 reset the counter value. The counter is kept at zero until this command is reset.
2 enable the latch procedure. If the latch configuration is valid and matches the hardware signals, then this
activation causes the counter value to be saved in the latch register.
The two different latch configurations that are possible (see section 4.11.3.8.3.3 "Setting the latch mode") must
be handled as follows:
• Single shot latch mode:
After successful latching, indicated by the latch event counter, activation must be reset before any more
latching is possible. The activation must be set again if additional latching is needed.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired. The latch event counter is
incremented with each event.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01Reset 0 Do not reset
1 Set encoder value to 0
1 Encoder01LatchEnable 0 Do not activate latch
1 Latching
2-7 Reserved 0
Name:
Encoder01_A
Encoder01_B
Encoder01_R
DigitalInput01 to DigitalInput02
This register displays the input status of the signal lines from the encoder and the digital inputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01_A 0/1 Input state of encoder signal A
1 Encoder01_B 0/1 Input state of encoder signal B
2 Encoder01_R 0/1 Input state of encoder signal R
3 Reserved 0
4 DigitalInput01 0/1 Input state - Digital input 1
5 DigitalInput02 0/1 Input state - Digital input 2
6-7 Reserved 0
The error states are latched when they occur and are maintained until acknowledged. The counter and time reg-
isters are not updated if there are pending or unacknowledged errors.
Bit structure:
Bit Name Value Information
0 BW_Channel_A 0 No error in encoder signal A
1 Open line, short circuit or voltage level too low
1 BW_Channel_B 0 No error in encoder signal B
1 Open line, short circuit or voltage level too low
2 BW_Channel_R 0 No error in encoder signal R
1 Open line, short circuit or voltage level too low
3-7 Reserved 0
Name:
BW_QuitChannel_A
BW_QuitChannel_B
BW_QuitChannel_R
This register can be used to acknowledge the latched error states of the signal lines from the encoder. However,
if there are still pending errors remaining, then the error status remains active. After acknowledging the errors, the
bits must also be reset or else any repetition of the error would be undetected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_QuitChannel_A 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal A
1 BW_QuitChannel_B 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal B
2 BW_QuitChannel_R 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal R
3-7 Reserved 0
The latched error states of the signal lines from the encoder can be acknowledged manually. However, if there
are still pending errors remaining, then the error status remains active. After successfully acknowledging the errors
(latched error status = 0), the acknowledge bits must still be reset by the user or else a re-occurrence of an error
could be overlooked by the user.
Example 1: Cause of error corrected before being acknowledged
An error has occurred on a signal line. The error state is detected and latched by the module.
The error is acknowledged by the user after the cause of error has been corrected. The latched
error status changes to zero.
The manual acknowledge must now be reset so that any new errors will be recognized by the
user.
Manual acknowledgment
Manual acknowledgment
Figure 262: Cause of error not yet corrected before being acknowledged
In addition to manual acknowledgment, automatic acknowledgment of the latched error states after a specified
amount of time can also be enabled. Make sure that the time is set long enough for the higher-level system to
reliably detect the status messages and for the validity of the counter value to be determined using its age.
If the time specification = 0, then only manual acknowledgment is possible.
Example 1: An error has occurred on a signal line. The error state is detected and latched by the module. The
time for automatic acknowledgment starts counting after the cause of error has been corrected.
The error is acknowledged as soon as the time expires. The latched error status changes to zero.
Automatic acknowledgment
Time Time
start expired
Automatic acknowledgment
Time Time
start expired here
Manual acknowledgment
Name:
PowerSupply01 to PowerSupply02
This register shows the status of the integrated encoder supplies. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1 PowerSupply02 0 5 VDC encoder power supply OK
1 5 VDC encoder power supply faulty
2-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
150 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
150 µs
4.11.4 X20DC1178
This module is equipped with one input for SSI absolute encoders with 5 V encoder signal. The data signal is
monitored (Data, Data\).
• 1 SSI absolute encoder 5 V
• Monitoring the data signal
• 2 additional inputs
• 5 VDC, 24 VDC and GND for encoder supply
Product ID X20DC1178
Brief description
I/O module 1 SSI absolute encoder 5 V
General information
B&R ID code 0xA708
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC (-15% / +20%)
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≥2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Input resistance 7.03 kΩ
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash Either the encoder monitor has detected a line fault on the encoder inputs or a
transfer error has occurred. The status bits must be evaluated in order to provide
a more detailed definition of this error.
The following error states are detected:
• Open line
• Short-circuit or voltage level too low
• SSI cycle time violation
• Parity error
On Error or reset status
D1 Green Input status - Data signal
1-2 Green Input state of the corresponding digital input
4.11.4.5 Pinout
r e
X20 DC 1178
D1
1 2
Data Data\
Clock Clock\
DI 1 DI 2
Encoder 24 V + Encoder 5 V +
GND GND
DC
Data
Counter 1
Data\
Clock
Clock\
Sensor 1
Counter input
Data
LED (green)
24 V
PTC
Encoder 24 V
24 V
DC
Encoder 5 V
DC
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
PTC
Clock
Output status
Transmitter
PTC
Clock
1) The offset specifies the position of the register within the CAN object.
The following registers are used for setting functions and configuring the module.
The following two registers define the cycle time for SSI sampling.
Name:
CfO_CycleSelect
This register assigns the principle interrupt setting:
• Timer configuration (time setting with CfO_SystemCyclePrescaler register): The SSI transfer can be
started independently of the X2X cycle. The timer is synchronized with X2X Link.
• AOAI: Configuration with X2X interrupt, one-time start of the SSI transfer in the X2X cycle. The SSI transfer
may require an entire X2X cycle.
• SOSI: Configuration with X2X interrupt, one-time start of the SSI transfer in the X2X cycle. The reaction
time can be optimized with this setting if the SSI transfer doesn't exceed half of an X2X cycle.
Data type Value Filter
USINT 3 Timer [μsec] ... Time setting with register CfO_SystemCyclePrescaler
10 AOAI
14 SOSI
Name:
CfO_SystemCyclePrescaler
The desired cycle time must be configured additionally for the timer setting using this register.
Data type Value Filter
USINT 1 50 μs
2 100 μs
4 200 μs
8 400 μs
16 800 μs
0 All other settings in the CfO_CycleSelect register
Name:
CfO_PhysicalMode
This register defines the operating parameters for the SSI encoder to correctly evaluate the data from the encoder.
• Parity: Data with or without parity; an error is reported if there is an even or uneven parity mismatch.
• Monoflop check: The encoder uses the monoflop to signal the readiness to accept a new clock cycle.
• Data coding: Binary or gray coding of the data bits
• Clock rate: Speed of data transfer
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-1 Parity bit 00 No parity bit (no clock bit output)
01 Even parity bit
10 Uneven parity bit
11 Ignore parity bit (clock bit is output, but the result is ignored)
2-3 Monostable multivibrator testing 00 No monostable multivibrator check (no clock bit output)
01 Check - Low level
10 Check - High level
11 Check - Ignore level (clock bit is output, but the result is ignored)
4 Data coding 0 Binary coding
1 Gray coding
5 Reserved 0
6-7 Clock rate 00 1 MHz
01 500 kHz
10 250 kHz
11 125 kHz
Clock
Name:
Cfo_DataBits
This register can be used to define the number of SSI encoder data bits.
Data type Value Filter
USINT 1 to 32 Number of SSI data bits
Name:
Cfo_NullBits
This register can be used to define the number of SSI encoder leading zeros.
Data type Value Filter
USINT 1 to 32 Number of leading zeros
Name:
CfO_BWQuitTime_0
This register can be used to enable an additional automatic acknowledgment of the error status through timing.
If a valid time is set, then the acknowledgment can still be made manually, the only difference is that automatic
acknowledgment will take place on the module after the defined amount of time has passed. If the error state has
not yet been corrected, then the error status remains and the time is reset. Make sure that the time is set long
enough for the higher-level system to reliably detect the status messages.
If the timing = 0, then acknowledgment is only possible using the cyclic acknowledgment registers.
Data type Value Information
UDINT 0 No automatic acknowledgment - Only default in bus controller function model
1 to 2.147.483.647 Time for automatic acknowledgment [μs]
In addition to manual acknowledgment, automatic acknowledgment of the latched error states after a specified
amount of time can also be enabled. Make sure that the time is set long enough for the higher-level system to
reliably detect the status messages and for the validity of the counter value to be determined using its age.
If the time specification = 0, then only manual acknowledgment is possible.
Example 1: An error has occurred on a signal line. The error state is detected and latched by the module. The
time for automatic acknowledgment starts counting after the cause of error has been corrected.
The error is acknowledged as soon as the time expires. The latched error status changes to zero.
Automatic acknowledgment
Time Time
start expired
Automatic acknowledgment
Time Time
start expired here
Manual acknowledgment
The latched error states of the signal lines from the encoder can be acknowledged manually. However, if there
are still pending errors remaining, then the error status remains active. After successfully acknowledging the errors
(latched error status = 0), the acknowledge bits must still be reset by the user or else a re-occurrence of an error
could be overlooked by the user.
Example 1: Cause of error corrected before being acknowledged
An error has occurred on a signal line. The error state is detected and latched by the module.
The error is acknowledged by the user after the cause of error has been corrected. The latched
error status changes to zero.
The manual acknowledge must now be reset so that any new errors will be recognized by the
user.
Manual acknowledgment
Manual acknowledgment
Figure 268: Cause of error not yet corrected before being acknowledged
Name:
CfO_BWSSIEnableMaskChannel7_0
This register allows error monitoring for each of the signal channels to be enabled individually. "Open line", "short
circuit" and "voltage level too low" are reported as error states. Any errors that occur are reported in the error
status registers.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder signal D 0 Error monitoring switched off
1 Error monitoring enabled
1-7 Reserved 0
The following registers must be set to the specified constant value for correct physical configuration:
Name:
CfO_BWQuitTimeSelChannel7_0
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
DigitalInput0 to DigitalInput02
This register displays the input states for the digital inputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-3 Reserved 0
4 DigitalInput01 0 or 1 Input state - Digital input 1
5 DigitalInput02 0 or 1 Input state - Digital input 2
6-7 Reserved 0
Name:
Encoder01
The counter state of the incremental encoder is displayed as a 16 or 32-bit counter value.
Data type Value
UDINT 0 to 4.294.967.295
DINT -2.147.483.648 to 2.147.483.647
UINT1) 0 to 65535
Name:
Encoder01TimeValid
The net time of the last valid counter value is the time of the last valid counter value recorded on the module. The
user is able to determine the validity of the counter value by evaluating its age in the program. This means that the
module and error status bits do not have to be checked additionally to determine the validity of the value.
The net time of the last valid counter value that was read is displayed as a 16 or 32-bit value. Only the 16-bit value
is available in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01TimeChanged
For slow X2X Link cycles, the net time of the last counter value change can be used to more accurately determine
the speed.
The net time of the last counter value change is displayed as 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
EncoderCycleTimeViolation
EncoderDataError
This register displays the error states that occurred while determining the position. The error states are latched
when they occur and are maintained until acknowledged.
A cycle time error is triggered if:
• Transfer is still active: This means that the defined cycle time is shorter than the time resulting from the
sum of the data bits and stop bits and the clock rate.
• The monoflop level does not match the defined start level
• There is an error pending on the signal line (open line, short circuit).
A data error is triggered if:
• The parity bit does not match.
• An error occurs on the signal line (open line, short circuit) during transfer.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 EncoderCycleTimeViolation 0 No error
1 Error status - Cycle time violation
1 EncoderDataError 0 No error
1 Error status - Data error
2-7 Reserved 0
Name:
EncoderQuitCycleTimeViolation
EncoderQuitDataError
This register can be used to acknowledge the latched data error states from the encoder. However, if there are still
pending errors remaining, then the error status remains active. After acknowledging the errors, the bits must also
be reset or else any repetition of the error would be undetected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 EncoderQuitCycleTimeViolation 0 No acknowledgment
1 Confirmation of error status - Cycle time violation
1 EncoderQuitDataError 0 No acknowledgment
1 Confirmation of error status - Data error
2-7 Reserved 0
Name:
BW_Channel_D
This register displays the error state of the signal line from the encoder. The error state is latched when it occurs
and is maintained until acknowledged. The counter and time registers are not updated if there are pending or
unacknowledged errors.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_Channel_D 0 No error - Encoder signal D
1 Error status - Open line or short circuit (voltage level too low)
1-7 Reserved 0
Name:
BW_QuitChannel_D
This register can be used to acknowledge the latched error states of the signal lines from the encoder. However,
if there are still pending errors remaining, then the error status remains active. After acknowledging the errors, the
bit must also be reset or else any repetition of the error will be undetected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_QuitChannel_D 0 No acknowledgment
1 Acknowledgment of error status
1-7 Reserved 0
Name:
PowerSupply01 to PowerSupply02
This register shows the status of the integrated encoder supplies. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1 PowerSupply02 0 5 VDC encoder power supply OK
1 5 VDC encoder power supply faulty
2-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
150 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
150 µs
4.11.5 X20DC1196
The module is equipped with 1 input for an ABR incremental encoder with 5 V encoder signal.
• 1 ABR incremental encoder 5 V
• 2 additional inputs e.g. for home enable switch
• 5 VDC, 24 VDC and GND for encoder supply
Product ID X20DC1196
Brief description
I/O module 1 ABR incremental encoder 5 V
General information
B&R ID code 0x1BAF
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Encoder - Bus Yes
Channel - Bus Yes
Channel - Encoder No
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≤2 μs
Software -
Connection type 3-wire connections
Input circuit Sink
Additional functions Home enable switch
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
A1 Green Input state of counter input A
B1 Green Input state of counter input B
R1 Green Input state of reference pulse R
1-2 Green Input state of the corresponding digital input
4.11.5.5 Pinout
r e
X20 DC 1196
A1
B1
R1
1 2
A A\
B B\
R R\
DI 1 DI 2
Encoder 24 V + Encoder 5 V +
GND GND
DC
A
A\
Counter 1
B
B\
R
R\
Sensor 1
Counter inputs
ABR
RS485
driver Input status
LED (green)
24 V
PTC
Encoder 24 V
24 V
DC
Encoder 5 V
DC
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
The difference between function model 0 and function model 1 is the size of the data type for some registers.
• Function model 0 uses data type INT
• Function model 1 uses data type DINT (specified in parentheses)
Register Name Data type Read Write
Cyclic Acyclic Cyclic Acyclic
Configuration
4104 CfO_EdgeDetectFalling USINT ●
4106 CfO_EdgeDetectRising USINT ●
2064 CfO_PresetABR01_1(_32Bit) (D)INT ●
2068 CfO_PresetABR01_2(_32Bit) (D)INT ●
512 ConfigOutput24 UINT ●
522 ConfigOutput26 USINT ●
520 ConfigOutput27 USINT ●
Communication
2116 ReferenceModeEncoder01 USINT ●
2080 Encoder01 (D)INT ●
264 Input state of digital inputs 1 to 2 USINT ●
DigitalInput01 Bit 4
DigitalInput02 Bit 5
2118 StatusInput01 USINT ●
40 Status of encoder supplies USINT ●
PowerSupply01 Bit 0
PowerSupply02 Bit 1
1) The offset specifies the position of the register within the CAN object.
The following registers must be configured by a single acyclic write with the listed values so that the homing
procedure is completed on the edge of the reference pulse.
The homing procedure can take place on:
• Rising edge
• Falling edge (default configuration)
Name:
CfO_EdgeDetectFalling
Data type Value Filter
USINT 0x00 Configuration value for rising edge
0x04 Configuration value for falling edge
Name:
CfO_EdgeDetectRising
Data type Value Filter
USINT 0x04 Configuration value for rising edge
0x00 Configuration value for falling edge
Name:
ConfigOutput24
This register contains the value for ABR encoder 1.
Data type Value Filter
UINT 0x1012 Configuration value for rising edge
0x1002 Configuration value for falling edge
Name:
Cfo_PresetABR01_1 to Cfo_PresetABR01_2
CfO_PresetABR01_1_32Bit to CfO_PresetABR01_2_32Bit (only in function model 1)
It is possible to specify two home positions with these registers through a one-off acyclic write, for example (default
= 0). The configured values are applied to the counter values after a completed homing procedure.
Data type Value
INT -32,768 to 32,767
DINT1) -2,147,483,648 to 2,147,483,647
Regardless of the referencing mode, it is possible using this register to prevent the home position from being
applied when the corresponding reference input voltage level occurs (see 4.11.5.8.4.2 "Input state of digital inputs
1 to 2": bit 4). The desired setting can be configured by a one-off acyclic write.
Name:
ConfigOutput26
The voltage level of the digital inputs to activate reference enable is configured with this register.
Data type Value Filter
USINT 0x00 Reference enable is active at 0 VDC
0x10 Reference enable for digital input 1 is active at 24 VDC
0x20 Reference enable for digital input 2 is active at 24 VDC
0x30 Reference enable for both digital inputs is active at 24 VDC
Name:
ConfigOutput27
This register can be used to define whether the reference enable is activated.
Data type Value Filter
USINT 0x00 Reference enable input OFF (default)
0x10 Reference enable input 1 enabled
0x20 Reference enable input 2 enabled
0x30 Reference enable input 1 and 2 enabled
Name:
Encoder01
The encoder values are represented as 16-bit or 32-bit counter values in this register.
Data type Value
INT -32,768 to 32,767
DINT1) -2,147,483,648 to 2,147,483,647
Name:
DigitalInput01 to DigitalInput02.
This register displays the input status of the encoders and the digital inputs.
Data type Value
USINT See bit structure.
Name:
ReferenceModeEncoder01
This register determines the referencing mode.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-1 00 Referencing OFF
01 Single shot referencing
11 Continuous referencing
2-5 0 Bits permanently set = 0
6-7 00 Referencing OFF
11 Bits permanently set = 1
Name:
StatusInput01
This register contains information regarding whether the referencing process is off, active or complete.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Reference pulse without homing1) 0 No reference impulse without homing has occurred yet
1 At least a reference impulse without homing has occurred
1 State change 0 or 1 Changes with each reference pulse without homing
2 Reference pulse with homing1) 0 No homing has occurred yet
1 At least one homing procedure has occurred
3 State change 0 or 1 Changes with each homing procedure that has taken place
4 Reference pulse 0 The last reference pulse didn't bring about a homing procedure
1 The last reference pulse brought about a homing procedure
5-7 Counter x Free-running counter, increased with each reference pulse
Name:
PowerSupply01 to PowerSupply02
This register shows the status of the integrated encoder supplies. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1 PowerSupply02 0 5 VDC encoder power supply OK
1 5 VDC encoder power supply faulty
2-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
4.11.6 X20DC1198
This module is equipped with one input for SSI absolute encoders with 5 V encoder signal.
• 1 SSI absolute encoder 5 V
• 2 additional inputs
• 5 VDC, 24 VDC and GND for encoder supply
Product ID X20DC1198
Brief description
I/O module 1 SSI absolute encoder 5 V
General information
B&R ID code 0x1BB0
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Encoder - Bus Yes
Channel - Bus Yes
Channel - Encoder No
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≥2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Input resistance 7.19 kΩ
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
D1 Green Input status - Data signal
1-2 Green Input state of the corresponding digital input
4.11.6.5 Pinout
r e
X20 DC 1198
D1
1 2
Data Data\
Clock Clock\
DI 1 DI 2
Encoder 24 V + Encoder 5 V +
GND GND
DC
Data
Counter 1
Data\
Clock
Clock\
Sensor 1
Counter input
Data
RS485
driver Input status
LED (green)
24 V
PTC
Encoder 24 V
24 V
DC
Encoder 5 V
DC
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
PTC
Clock
RS485
Output status driver
PTC
Transmitter
Clock
1) The offset specifies the position of the register within the CAN object.
Name:
ConfigOutput14
This configuration register is used to set the coding, the clock rate and the number of bits. Default = 0. This must
be set once using an acyclic write command.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 00 1 MHz
01 500 kHz
10 250 kHz
11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
Name:
ConfigAdvanced
This configuration register is used to set the coding, the clock rate, the number of bits and the monostable multivi-
brator settings. Default = 0. This must be set once using an acyclic write command.
It only differs from ConfigOutput14 by data length and additional monostable multivibrator testing.
Data type Value
UDINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 00 1 MHz
01 500 kHz
10 250 kHz
11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
16 - 17 Monostable multivibrator testing 00 Check OFF, no additional clock bit
01 Check set to High level
10 Check set to Low level
11 Level is clocked but ignored
18 - 31 Reserved 0 Reserved
Clock
Name:
Encoder01
The SSI encoder value is displayed as a 32-bit position value. The SSI position value is generated synchronously
with the X2X cycle.
Data type Value Filter
UDINT 0 to 4,294,967,295 SSI position
Name:
DigitalInput01 to DigitalInput02
This register is used to indicate the input state of digital inputs 1 to 2.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
4 DigitalInput01 0 or 1 Input state - Digital input 1
5 DigitalInput02 0 or 1 Input state - Digital input 2
Name:
PowerSupply01 to PowerSupply02
This register shows the status of the integrated encoder supplies. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1 PowerSupply02 0 5 VDC encoder power supply OK
1 5 VDC encoder power supply faulty
2-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
4.11.7 X20DC11A6
The module is equipped with 1 input for an ABR incremental encoder with 5 V encoder signal. The encoder inputs
are monitored (A, B, R, A\, B\, R\).
• 1 ABR incremental encoder 5 V
• Encoder input monitoring (up to 250 kHz input frequency)
• 2 additional inputs, e.g. for latch input
• 5 VDC, 24 VDC and GND for encoder supply
Product ID X20DC11A6
Brief description
I/O module 1 ABR incremental encoder 5 V
General information
B&R ID code 0xB76B
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.0 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≤30 ns
Software -
Connection type 3-wire connections
Input circuit Sink
Additional functions Latch input
Input resistance 7.03 kΩ
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash The encoder monitor has detected a line fault on the encoder inputs. The status
bits must be evaluated in order to provide a more detailed definition of this error.
The following error states are detected:
• Broken connection (up to 250 kHz input frequency)
• Short-circuit or voltage level too low
On Error or reset status
A1 Green Input state of counter input A
B1 Green Input state of counter input B
R1 Green Input state of reference pulse R
1-2 Green Input state of the corresponding digital input
4.11.7.5 Pinout
r e
X20 DC 11A6
A1
B1
R1
1 2
A A\
B B\
R R\
DI 1 DI 2
Encoder 24 V+ Encoder 5 V+
GND GND
DC
A
A\
Counter 1
B
B\
R
R\
Sensor 1
Counter inputs
ABR
LED (green)
24 V
PTC
Encoder 24 V
24 V
DC
Encoder 5 V
DC
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
1) The offset specifies the position of the register within the CAN object.
The following registers are used for setting functions and configuring the module.
Name:
CfO_BWCNTEnableMaskChannel7_0
This register requires individually enabling error monitoring for each of the signal channels. "Open line", "short
circuit" and "voltage level too low" are reported as error states. Any errors that occur are reported in the error status
registers BW_Channel_x.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Enable error monitoring for signal A lines 0 Error monitoring - Encoder Signal A disabled
1 Error monitoring - Encoder Signal A enabled - Only default in
bus controller function model
1 Enable error monitoring for signal B lines 0 Error monitoring - Encoder Signal B disabled
1 Error monitoring - Encoder Signal B enabled - Only default in
bus controller function model
2 Enable error monitoring for signal R lines 0 Error monitoring - Encoder Signal R disabled
1 Error monitoring - Encoder Signal R enabled - Only default in
bus controller function model
3-7 Reserved 0
Name:
CfO_BWQuitTime_0
This register can be used to enable an additional automatic acknowledgment of the error status through timing.
If a valid time is set, then the acknowledgment can still be made manually, the only difference is that automatic
acknowledgment will take place on the module after the defined amount of time has passed. If the error state has
not yet been corrected, then the error status remains and the time is reset. Make sure that the time is set long
enough for the higher-level system to reliably detect the status messages.
If the timing = 0, then acknowledgment is only possible using the cyclic acknowledgment registers.
Data type Value Information
UDINT 0 No automatic acknowledgment - Only default in bus controller function model
1 to 2.147.483.647 Time for automatic acknowledgment [μs]
Name:
CfO_LatchMode
This register is used to set the latch mode:
• Single shot latch mode:
The latch function must be enabled/set. After a successful latch procedure, the activation must be reset in
order for a new latch procedure to be activated.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired.
A changed counter state on Encoder01LatchCount indicates that the latch procedure has been performed. The
counter value is stored in the latch register Encoder01Latch.
Data type Value Information
USINT 0 Single shot latch procedure
1 Continuous latch procedure
Name:
CfO_LatchComparator
This register defines the signal channels and their level for triggering the latch procedure.
• This mainly configures which channels are linked to generate the latch event. All three signals from the
encoder and digital input 1 can be used for the "AND" operation.
• The "active voltage level" needed for the latch procedure can now be used according to the physical signals.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Defines signal level for encoder signal A 0 Low
1 High
1 Defines signal level for encoder signal B 0 Low
1 High
2 Defines signal level for encoder signal R 0 Low
1 High
3 Defines signal level for digital input 1 0 Low
1 High
4 Use encoder signal A to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal A
5 Use encoder signal B to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal B
6 Use encoder signal R to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal R
7 Use digital input 1 to trigger latch procedure 0 Disabled
1 Latch function linked to digital input 1
The following registers must be set to the specified constant value for correct physical configuration:
Name:
CfO_SIframeGenID
Data type Value Information
USINT 9 Only default in the bus controller module
Name:
CfO_SystemCycleTime
Data type Value Information
UINT 800 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh01
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh02
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh03
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh04
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh05
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_BWQuitTimeSelChannel7_0
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_CounterCycleSelect
Data type Value Information
USINT 2 Only default in the bus controller module
Name:
CfO_CounterMode
Data type Value Information
USINT 3 Only default in the bus controller module
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
Encoder01
The counter state of the incremental encoder is displayed as a 16 or 32-bit counter value. Only the 16-bit value
is available in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01TimeValid
The net time of the last valid counter value is the time of the last valid counter value recorded on the module. The
user is able to determine the validity of the counter value by evaluating its age in the program. This means that the
module and error status bits do not have to be checked additionally to determine the validity of the value.
The net time of the last valid counter value that was read is displayed as a 16 or 32-bit value. Only the 16-bit value
is available in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01TimeChanged
For slow X2X Link cycles, the net time of the last counter value change can be used to more accurately determine
the speed.
The net time of the last counter value change is displayed as 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01Latch
The counter value at the time of the last latch is displayed as a 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01LatchCount
The latch events are counted and stored in a cyclic 8-bit counter. This counter is incremented with each latch event,
thereby indicating a new occurrence. The new latched counter value is stored in the respective latch register.
Data type Value
SINT -128 to 127
Name:
Encoder01Command
This register can be used to
1 reset the counter value. The counter is kept at zero until this command is reset.
2 enable the latch procedure. If the latch configuration is valid and matches the hardware signals, then this
activation causes the counter value to be saved in the latch register.
The two different latch configurations that are possible (see section 4.11.7.8.3.3 "Setting the latch mode") must
be handled as follows:
• Single shot latch mode:
After successful latching, indicated by the latch event counter, activation must be reset before any more
latching is possible. The activation must be set again if additional latching is needed.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired. The latch event counter is
incremented with each event.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01Reset 0 Do not reset
1 Set encoder value to 0
1 Encoder01LatchEnable 0 Do not activate latch
1 Latching
2-7 Reserved 0
Name:
Encoder01_A
Encoder01_B
Encoder01_R
DigitalInput01 to DigitalInput02
This register displays the input status of the signal lines from the encoder and the digital inputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01_A 0/1 Input state of encoder signal A
1 Encoder01_B 0/1 Input state of encoder signal B
2 Encoder01_R 0/1 Input state of encoder signal R
3 Reserved 0
4 DigitalInput01 0/1 Input state - Digital input 1
5 DigitalInput02 0/1 Input state - Digital input 2
6-7 Reserved 0
The error states are latched when they occur and are maintained until acknowledged. The counter and time reg-
isters are not updated if there are pending or unacknowledged errors.
Bit structure:
Bit Name Value Information
0 BW_Channel_A 0 No error in encoder signal A
1 Open line, short circuit or voltage level too low
1 BW_Channel_B 0 No error in encoder signal B
1 Open line, short circuit or voltage level too low
2 BW_Channel_R 0 No error in encoder signal R
1 Open line, short circuit or voltage level too low
3-7 Reserved 0
Name:
BW_QuitChannel_A
BW_QuitChannel_B
BW_QuitChannel_R
This register can be used to acknowledge the latched error states of the signal lines from the encoder. However,
if there are still pending errors remaining, then the error status remains active. After acknowledging the errors, the
bits must also be reset or else any repetition of the error would be undetected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_QuitChannel_A 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal A
1 BW_QuitChannel_B 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal B
2 BW_QuitChannel_R 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal R
3-7 Reserved 0
The latched error states of the signal lines from the encoder can be acknowledged manually. However, if there
are still pending errors remaining, then the error status remains active. After successfully acknowledging the errors
(latched error status = 0), the acknowledge bits must still be reset by the user or else a re-occurrence of an error
could be overlooked by the user.
Example 1: Cause of error corrected before being acknowledged
An error has occurred on a signal line. The error state is detected and latched by the module.
The error is acknowledged by the user after the cause of error has been corrected. The latched
error status changes to zero.
The manual acknowledge must now be reset so that any new errors will be recognized by the
user.
Manual acknowledgment
Manual acknowledgment
Figure 270: Cause of error not yet corrected before being acknowledged
In addition to manual acknowledgment, automatic acknowledgment of the latched error states after a specified
amount of time can also be enabled. Make sure that the time is set long enough for the higher-level system to
reliably detect the status messages and for the validity of the counter value to be determined using its age.
If the time specification = 0, then only manual acknowledgment is possible.
Example 1: An error has occurred on a signal line. The error state is detected and latched by the module. The
time for automatic acknowledgment starts counting after the cause of error has been corrected.
The error is acknowledged as soon as the time expires. The latched error status changes to zero.
Automatic acknowledgment
Time Time
start expired
Automatic acknowledgment
Time Time
start expired here
Manual acknowledgment
Name:
PowerSupply01 to PowerSupply02
This register shows the status of the integrated encoder supplies. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1 PowerSupply02 0 5 VDC encoder power supply OK
1 5 VDC encoder power supply faulty
2-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
150 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
150 µs
4.11.8 X20DC1376
The module is equipped with 1 input for an ABR incremental encoder with 24 V encoder signal. The encoder inputs
are monitored (A, B, R).
• 1 ABR incremental encoder 24 V, asymmetric
• Encoder input monitoring
• 2 additional inputs, e.g. for latch input
• 24 VDC and GND for encoder supply
Product ID X20DC1376
Short description
I/O module 1 ABR incremental encoder 24 V
General information
Input voltage 24 VDC (-15% / +20%)
B&R ID code 0xA705
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.3 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC (-15% / +20%)
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≤2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Additional functions Latch input
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash The encoder monitor has detected a line fault on the encoder inputs. The status
bits must be evaluated in order to provide a more detailed definition of this error.
The following error states are detected:
• Open line
• Short-circuit or voltage level too low
On Error or reset status
A1 Green Input state of counter input A
B1 Green Input state of counter input B
R1 Green Input state of reference pulse R
1-2 Green Input status - digital input
4.11.8.5 Pinout
r e
X20 DC 1376
A1
B1
R1
1 2
DI 1 DI 2
Encoder 24 V+
GND GND
DC
A
Counter 1
Counter inputs
ABR
I/O status
LED (green)
24 V
PTC
Encoder 24 V
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
1) The offset specifies the position of the register within the CAN object.
The following registers are used for setting functions and configuring the module.
Name:
CfO_BWCNTEnableMaskChannel7_0
This register requires individually enabling error monitoring for each of the signal channels. "Open line", "short
circuit" and "voltage level too low" are reported as error states. Any errors that occur are reported in the error status
registers BW_Channel_x.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Enable error monitoring for signal A lines 0 Error monitoring - Encoder Signal A disabled
1 Error monitoring - Encoder Signal A enabled - Only default in
bus controller function model
1 Enable error monitoring for signal B lines 0 Error monitoring - Encoder Signal B disabled
1 Error monitoring - Encoder Signal B enabled - Only default in
bus controller function model
2 Enable error monitoring for signal R lines 0 Error monitoring - Encoder Signal R disabled
1 Error monitoring - Encoder Signal R enabled - Only default in
bus controller function model
3-7 Reserved 0
Name:
CfO_BWQuitTime_0
This register can be used to enable an additional automatic acknowledgment of the error status through timing.
If a valid time is set, then the acknowledgment can still be made manually, the only difference is that automatic
acknowledgment will take place on the module after the defined amount of time has passed. If the error state has
not yet been corrected, then the error status remains and the time is reset. Make sure that the time is set long
enough for the higher-level system to reliably detect the status messages.
If the timing = 0, then acknowledgment is only possible using the cyclic acknowledgment registers.
Data type Value Information
UDINT 0 No automatic acknowledgment - Only default in bus controller function model
1 to 2.147.483.647 Time for automatic acknowledgment [μs]
Name:
CfO_LatchMode
This register is used to set the latch mode:
• Single shot latch mode:
The latch function must be enabled/set. After a successful latch procedure, the activation must be reset in
order for a new latch procedure to be activated.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired.
A changed counter state on Encoder01LatchCount indicates that the latch procedure has been performed. The
counter value is stored in the latch register Encoder01Latch.
Data type Value Information
USINT 0 Single shot latch procedure
1 Continuous latch procedure
Name:
CfO_LatchComparator
This register defines the signal channels and their level for triggering the latch procedure.
• This mainly configures which channels are linked to generate the latch event. All three signals from the
encoder and digital input 1 can be used for the "AND" operation.
• The "active voltage level" needed for the latch procedure can now be used according to the physical signals.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Defines signal level for encoder signal A 0 Low
1 High
1 Defines signal level for encoder signal B 0 Low
1 High
2 Defines signal level for encoder signal R 0 Low
1 High
3 Defines signal level for digital input 1 0 Low
1 High
4 Use encoder signal A to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal A
5 Use encoder signal B to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal B
6 Use encoder signal R to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal R
7 Use digital input 1 to trigger latch procedure 0 Disabled
1 Latch function linked to digital input 1
The following registers must be set to the specified constant value for correct physical configuration:
Name:
CfO_SIframeGenID
Data type Value Information
USINT 9 Only default in the bus controller module
Name:
CfO_SystemCycleTime
Data type Value Information
UINT 800 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh01
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh02
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh03
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh04
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh05
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_BWQuitTimeSelChannel7_0
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_CounterCycleSelect
Data type Value Information
USINT 2 Only default in the bus controller module
Name:
CfO_CounterMode
Data type Value Information
USINT 3 Only default in the bus controller module
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
Encoder01
The counter state of the incremental encoder is displayed as a 16 or 32-bit counter value. Only the 16-bit value
is available in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01TimeValid
The net time of the last valid counter value is the time of the last valid counter value recorded on the module. The
user is able to determine the validity of the counter value by evaluating its age in the program. This means that the
module and error status bits do not have to be checked additionally to determine the validity of the value.
The net time of the last valid counter value that was read is displayed as a 16 or 32-bit value. Only the 16-bit value
is available in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01TimeChanged
For slow X2X Link cycles, the net time of the last counter value change can be used to more accurately determine
the speed.
The net time of the last counter value change is displayed as 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01Latch
The counter value at the time of the last latch is displayed as a 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01LatchCount
The latch events are counted and stored in a cyclic 8-bit counter. This counter is incremented with each latch event,
thereby indicating a new occurrence. The new latched counter value is stored in the respective latch register.
Data type Value
SINT -128 to 127
Name:
Encoder01Command
This register can be used to
1 reset the counter value. The counter is kept at zero until this command is reset.
2 enable the latch procedure. If the latch configuration is valid and matches the hardware signals, then this
activation causes the counter value to be saved in the latch register.
The two different latch configurations that are possible (see section 4.11.8.8.3.3 "Setting the latch mode") must
be handled as follows:
• Single shot latch mode:
After successful latching, indicated by the latch event counter, activation must be reset before any more
latching is possible. The activation must be set again if additional latching is needed.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired. The latch event counter is
incremented with each event.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01Reset 0 Do not reset
1 Set encoder value to 0
1 Encoder01LatchEnable 0 Do not activate latch
1 Latching
2-7 Reserved 0
Bit structure:
Bit Name Value Information
0 Encoder01_A 0/1 Input state of encoder signal A
1 Encoder01_B 0/1 Input state of encoder signal B
2 Encoder01_R 0/1 Input state of encoder signal R
3 Reserved 0
4 DigitalInput01 0/1 Input state - Digital input 1
5 DigitalInput02 0/1 Input state - Digital input 2
6-7 Reserved 0
The error states are latched when they occur and are maintained until acknowledged. The counter and time reg-
isters are not updated if there are pending or unacknowledged errors.
Name:
BW_Channel_A
BW_Channel_B
BW_Channel_R
This register displays the error states of the signal lines from the encoder. The error states are latched when they
occur and are maintained until acknowledged. The counter and time registers are not updated if there are pending
or unacknowledged errors.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_Channel_A 0 No error in encoder signal A
1 Open line, short circuit or voltage level too low
1 BW_Channel_B 0 No error in encoder signal B
1 Open line, short circuit or voltage level too low
2 BW_Channel_R 0 No error in encoder signal R
1 Open line, short circuit or voltage level too low
3-7 Reserved 0
Name:
BW_QuitChannel_A
BW_QuitChannel_B
BW_QuitChannel_R
This register can be used to acknowledge the latched error states of the signal lines from the encoder. However,
if there are still pending errors remaining, then the error status remains active. After acknowledging the errors, the
bits must also be reset or else any repetition of the error would be undetected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_QuitChannel_A 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal A
1 BW_QuitChannel_B 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal B
2 BW_QuitChannel_R 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal R
3-7 Reserved 0
The latched error states of the signal lines from the encoder can be acknowledged manually. However, if there
are still pending errors remaining, then the error status remains active. After successfully acknowledging the errors
(latched error status = 0), the acknowledge bits must still be reset by the user or else a re-occurrence of an error
could be overlooked by the user.
Example 1: Cause of error corrected before being acknowledged
An error has occurred on a signal line. The error state is detected and latched by the module.
The error is acknowledged by the user after the cause of error has been corrected. The latched
error status changes to zero.
The manual acknowledge must now be reset so that any new errors will be recognized by the
user.
Manual acknowledgment
Manual acknowledgment
Figure 274: Cause of error not yet corrected before being acknowledged
In addition to manual acknowledgment, automatic acknowledgment of the latched error states after a specified
amount of time can also be enabled. Make sure that the time is set long enough for the higher-level system to
reliably detect the status messages and for the validity of the counter value to be determined using its age.
If the time specification = 0, then only manual acknowledgment is possible.
Example 1: An error has occurred on a signal line. The error state is detected and latched by the module. The
time for automatic acknowledgment starts counting after the cause of error has been corrected.
The error is acknowledged as soon as the time expires. The latched error status changes to zero.
Automatic acknowledgment
Time Time
start expired
Automatic acknowledgment
Time Time
start expired here
Manual acknowledgment
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
150 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
150 µs
4.11.9 X20DC137A
The module is equipped with 1 input for an ABR incremental encoder with 24 V differential signals. The encoder
inputs are monitored (A, B, R, A\, B\, R\).
• 1 ABR incremental encoder 24 V, differential
• Encoder input monitoring
• 2 additional inputs, e.g. for latch input
• 24 VDC and GND for encoder supply
Product ID X20DC137A
Brief description
I/O module 1 ABR incremental encoder 24 V, differential
General information
B&R ID code 0xDD28
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.2 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC (-15% / +20%)
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≤2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Additional functions Latch input
Input resistance 7.03 kΩ
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash The encoder monitor has detected a line fault on the encoder inputs. The status
bits must be evaluated in order to provide a more detailed definition of this error.
The following error states are detected:
• Open line
• Short-circuit or voltage level too low
On Error or reset status
A1 Green Input state of counter input A
B1 Green Input state of counter input B
R1 Green Input state of reference pulse R
1-2 Green Input state of the corresponding digital input
4.11.9.5 Pinout
r e
X20 DC 137A
A1
B1
R1
1 2
A A\
B B\
R R\
DI 1 DI 2
Encoder 24 V+
GND GND
DC
A
A\
Counter 1
B
B\
R
R\
Sensor 1
Counter inputs
ABR
VDR
Recipient Input status
with monitoring
VDR
ABR\ I/O Status
LED (green)
24 V
PTC
Encoder 24 V
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
1) The offset specifies the position of the register within the CAN object.
The following registers are used for setting functions and configuring the module.
Name:
CfO_BWCNTEnableMaskChannel7_0
This register requires individually enabling error monitoring for each of the signal channels. "Open line", "short
circuit" and "voltage level too low" are reported as error states. Any errors that occur are reported in the error status
registers BW_Channel_x.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Enable error monitoring for signal A lines 0 Error monitoring - Encoder Signal A disabled
1 Error monitoring - Encoder Signal A enabled - Only default in
bus controller function model
1 Enable error monitoring for signal B lines 0 Error monitoring - Encoder Signal B disabled
1 Error monitoring - Encoder Signal B enabled - Only default in
bus controller function model
2 Enable error monitoring for signal R lines 0 Error monitoring - Encoder Signal R disabled
1 Error monitoring - Encoder Signal R enabled - Only default in
bus controller function model
3-7 Reserved 0
Name:
CfO_BWQuitTime_0
This register can be used to enable an additional automatic acknowledgment of the error status through timing.
If a valid time is set, then the acknowledgment can still be made manually, the only difference is that automatic
acknowledgment will take place on the module after the defined amount of time has passed. If the error state has
not yet been corrected, then the error status remains and the time is reset. Make sure that the time is set long
enough for the higher-level system to reliably detect the status messages.
If the timing = 0, then acknowledgment is only possible using the cyclic acknowledgment registers.
Data type Value Information
UDINT 0 No automatic acknowledgment - Only default in bus controller function model
1 to 2.147.483.647 Time for automatic acknowledgment [μs]
Name:
CfO_LatchMode
This register is used to set the latch mode:
• Single shot latch mode:
The latch function must be enabled/set. After a successful latch procedure, the activation must be reset in
order for a new latch procedure to be activated.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired.
A changed counter state on Encoder01LatchCount indicates that the latch procedure has been performed. The
counter value is stored in the latch register Encoder01Latch.
Data type Value Information
USINT 0 Single shot latch procedure
1 Continuous latch procedure
Name:
CfO_LatchComparator
This register defines the signal channels and their level for triggering the latch procedure.
• This mainly configures which channels are linked to generate the latch event. All three signals from the
encoder and digital input 1 can be used for the "AND" operation.
• The "active voltage level" needed for the latch procedure can now be used according to the physical signals.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Defines signal level for encoder signal A 0 Low
1 High
1 Defines signal level for encoder signal B 0 Low
1 High
2 Defines signal level for encoder signal R 0 Low
1 High
3 Defines signal level for digital input 1 0 Low
1 High
4 Use encoder signal A to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal A
5 Use encoder signal B to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal B
6 Use encoder signal R to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal R
7 Use digital input 1 to trigger latch procedure 0 Disabled
1 Latch function linked to digital input 1
The following registers must be set to the specified constant value for correct physical configuration:
Name:
CfO_SIframeGenID
Data type Value Information
USINT 9 Only default in the bus controller module
Name:
CfO_SystemCycleTime
Data type Value Information
UINT 800 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh01
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh02
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh03
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh04
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh05
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_BWQuitTimeSelChannel7_0
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_CounterCycleSelect
Data type Value Information
USINT 2 Only default in the bus controller module
Name:
CfO_CounterMode
Data type Value Information
USINT 3 Only default in the bus controller module
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
Encoder01
The counter state of the incremental encoder is displayed as a 16 or 32-bit counter value. Only the 16-bit value
is available in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01TimeValid
The net time of the last valid counter value is the time of the last valid counter value recorded on the module. The
user is able to determine the validity of the counter value by evaluating its age in the program. This means that the
module and error status bits do not have to be checked additionally to determine the validity of the value.
The net time of the last valid counter value that was read is displayed as a 16 or 32-bit value. Only the 16-bit value
is available in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01TimeChanged
For slow X2X Link cycles, the net time of the last counter value change can be used to more accurately determine
the speed.
The net time of the last counter value change is displayed as 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01Latch
The counter value at the time of the last latch is displayed as a 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01LatchCount
The latch events are counted and stored in a cyclic 8-bit counter. This counter is incremented with each latch event,
thereby indicating a new occurrence. The new latched counter value is stored in the respective latch register.
Data type Value
SINT -128 to 127
Name:
Encoder01Command
This register can be used to
1 reset the counter value. The counter is kept at zero until this command is reset.
2 enable the latch procedure. If the latch configuration is valid and matches the hardware signals, then this
activation causes the counter value to be saved in the latch register.
The two different latch configurations that are possible (see section 4.11.9.8.3.3 "Setting the latch mode") must
be handled as follows:
• Single shot latch mode:
After successful latching, indicated by the latch event counter, activation must be reset before any more
latching is possible. The activation must be set again if additional latching is needed.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired. The latch event counter is
incremented with each event.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01Reset 0 Do not reset
1 Set encoder value to 0
1 Encoder01LatchEnable 0 Do not activate latch
1 Latching
2-7 Reserved 0
Bit structure:
Bit Name Value Information
0 Encoder01_A 0/1 Input state of encoder signal A
1 Encoder01_B 0/1 Input state of encoder signal B
2 Encoder01_R 0/1 Input state of encoder signal R
3 Reserved 0
4 DigitalInput01 0/1 Input state - Digital input 1
5 DigitalInput02 0/1 Input state - Digital input 2
6-7 Reserved 0
The error states are latched when they occur and are maintained until acknowledged. The counter and time reg-
isters are not updated if there are pending or unacknowledged errors.
Name:
BW_Channel_A
BW_Channel_B
BW_Channel_R
This register displays the error states of the signal lines from the encoder. The error states are latched when they
occur and are maintained until acknowledged. The counter and time registers are not updated if there are pending
or unacknowledged errors.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_Channel_A 0 No error in encoder signal A
1 Open line, short circuit or voltage level too low
1 BW_Channel_B 0 No error in encoder signal B
1 Open line, short circuit or voltage level too low
2 BW_Channel_R 0 No error in encoder signal R
1 Open line, short circuit or voltage level too low
3-7 Reserved 0
Name:
BW_QuitChannel_A
BW_QuitChannel_B
BW_QuitChannel_R
This register can be used to acknowledge the latched error states of the signal lines from the encoder. However,
if there are still pending errors remaining, then the error status remains active. After acknowledging the errors, the
bits must also be reset or else any repetition of the error would be undetected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_QuitChannel_A 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal A
1 BW_QuitChannel_B 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal B
2 BW_QuitChannel_R 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal R
3-7 Reserved 0
The latched error states of the signal lines from the encoder can be acknowledged manually. However, if there
are still pending errors remaining, then the error status remains active. After successfully acknowledging the errors
(latched error status = 0), the acknowledge bits must still be reset by the user or else a re-occurrence of an error
could be overlooked by the user.
Example 1: Cause of error corrected before being acknowledged
An error has occurred on a signal line. The error state is detected and latched by the module.
The error is acknowledged by the user after the cause of error has been corrected. The latched
error status changes to zero.
The manual acknowledge must now be reset so that any new errors will be recognized by the
user.
Manual acknowledgment
Manual acknowledgment
Figure 278: Cause of error not yet corrected before being acknowledged
In addition to manual acknowledgment, automatic acknowledgment of the latched error states after a specified
amount of time can also be enabled. Make sure that the time is set long enough for the higher-level system to
reliably detect the status messages and for the validity of the counter value to be determined using its age.
If the time specification = 0, then only manual acknowledgment is possible.
Example 1: An error has occurred on a signal line. The error state is detected and latched by the module. The
time for automatic acknowledgment starts counting after the cause of error has been corrected.
The error is acknowledged as soon as the time expires. The latched error status changes to zero.
Automatic acknowledgment
Time Time
start expired
Automatic acknowledgment
Time Time
start expired here
Manual acknowledgment
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
150 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
150 µs
4.11.10 X20DC1396
The module is equipped with 1 input for an ABR incremental encoder with 24 V encoder signal.
• 1 ABR incremental encoder 24 V
• 1 additional input e.g. for home enable switch
• 24 VDC and GND for encoder supply
Product ID X20DC1396
Brief description
I/O module 1 ABR incremental encoder 24 V
General information
Input voltage 24 VDC -15% / +20%
B&R ID code 0x1BAC
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.4 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Encoder - Bus Yes
Reference enable switch - Bus Yes
Reference enable switch - Encoder No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Home enable switch
Quantity 1
Nominal voltage 24 VDC
Input filter
Hardware ≥2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Input current at 24 VDC Approx. 3.3 mA
Input resistance 7.19 kΩ
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
A1 Green Input state of counter input A
B1 Green Input state of counter input B
R1 Green Input state of reference pulse R
1 Green Input state - Digital input
4.11.10.5 Pinout
r e
X20 DC 1396
A1
B1
R1
1
DI 1
Encoder 24 V +
GND
DC
A
Counter 1
Counter inputs
ABR
VDR
Input status
I/O status
24 V
PTC
Encoder 24 V LED (green)
GND
GND
Standard input
Input x
VDR
Input status
I/O status
Led (green)
The difference between function model 0 and function model 1 is the size of the data type for some registers.
• Function model 0 uses data type INT
• Function model 1 uses data type DINT (specified in parentheses)
Register Name Data type Read Write
Cyclic Acyclic Cyclic Acyclic
Configuration
4104 CfO_EdgeDetectFalling USINT ●
4106 CfO_EdgeDetectRising USINT ●
2064 CfO_PresetABR01_1(_32Bit) (D)INT ●
2068 CfO_PresetABR01_2(_32Bit) (D)INT ●
512 ConfigOutput24 UINT ●
522 ConfigOutput26 USINT ●
520 ConfigOutput27 USINT ●
Communication
2116 ReferenceModeEncoder01 USINT ●
2080 Encoder01 (D)INT ●
264 Input state of the digital input USINT ●
DigitalInput01 Bit 3
2118 StatusInput01 USINT ●
40 Status of encoder supply USINT ●
PowerSupply01 Bit 0
1) The offset specifies the position of the register within the CAN object.
The following registers must be configured by a single acyclic write with the listed values so that the homing
procedure is completed on the edge of the reference pulse.
The homing procedure can take place on:
• Rising edge
• Falling edge (default configuration)
Name:
CfO_EdgeDetectFalling
Data type Value Filter
USINT 0x00 Configuration value for rising edge
0x04 Configuration value for falling edge
Name:
CfO_EdgeDetectRising
Data type Value Filter
USINT 0x04 Configuration value for rising edge
0x00 Configuration value for falling edge
Name:
ConfigOutput24
This register contains the value for ABR encoder 1.
Data type Value Filter
UINT 0x1012 Configuration value for rising edge
0x1002 Configuration value for falling edge
Name:
Cfo_PresetABR01_1 to Cfo_PresetABR01_2
CfO_PresetABR01_1_32Bit to CfO_PresetABR01_2_32Bit (only in function model 1)
It is possible to specify two home positions with these registers through a one-off acyclic write, for example (default
= 0). The configured values are applied to the counter values after a completed homing procedure.
Data type Value
INT -32,768 to 32,767
DINT1) -2,147,483,648 to 2,147,483,647
Regardless of the referencing mode, it is possible using this register to prevent the home position from being
applied when the corresponding reference input voltage level occurs (see 4.11.10.8.4.2 "Input state of the digital
input": bit 3). The desired setting can be configured by a one-off acyclic write.
Name:
ConfigOutput26
This register is used to configure the active voltage level of the digital input for the reference enable.
Data type Value Filter
USINT 0x00 Reference enable is active at 0 VDC
0x08 Reference enable is active at 24 VDC
Name:
ConfigOutput27
This register can be used to define whether the reference enable is activated.
Data type Value Filter
USINT 0x00 Reference enable input OFF (default)
0x08 Reference enable input activated
Name:
Encoder01
The encoder values are represented as 16-bit or 32-bit counter values in this register.
Data type Value
INT -32,768 to 32,767
DINT1) -2,147,483,648 to 2,147,483,647
Name:
DigitalInput01
This register displays the input status of the encoder and the digital input.
Data type Value
USINT See bit structure.
Name:
ReferenceModeEncoder01
This register determines the referencing mode.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-1 00 Referencing OFF
01 Single shot referencing
11 Continuous referencing
2-5 0 Bits permanently set = 0
6-7 00 Referencing OFF
11 Bits permanently set = 1
Name:
StatusInput01
This register contains information regarding whether the referencing process is off, active or complete.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Reference pulse without homing1) 0 No reference impulse without homing has occurred yet
1 At least a reference impulse without homing has occurred
1 State change 0 or 1 Changes with each reference pulse without homing
2 Reference pulse with homing1) 0 No homing has occurred yet
1 At least one homing procedure has occurred
3 State change 0 or 1 Changes with each homing procedure that has taken place
4 Reference pulse 0 The last reference pulse didn't bring about a homing procedure
1 The last reference pulse brought about a homing procedure
5-7 Counter x Free-running counter, increased with each reference pulse
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
4.11.11 X20DC1398
This module is equipped with one input for SSI absolute encoders with 24 V encoder signal.
• 1 SSI absolute encoder 24 V
• 1 additional input
• 24 VDC and GND for encoder supply
Product ID X20DC1398
Brief description
I/O module 1 SSI absolute encoder 24 V
General information
Input voltage 24 VDC -15% / +20%
B&R ID code 0x1BAE
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.3 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Encoder - Bus Yes
Channel - Bus Yes
Channel - Encoder No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 1
Nominal voltage 24 VDC
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≥2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Input resistance 7.19 kΩ
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
D1 Green Input status - Data signal
1 Green Input state - Digital input
4.11.11.5 Pinout
r e
X20 DC 1398
D1
1
Data
Clock
DI 1
Encoder 24 V +
GND
DC
Data
Counter 1
Clock
Counter input
Data
VDR
Input status
I/O status
24 V
PTC
Encoder 24 V LED (green)
GND
GND
Standard input
Input x
VDR
Input status
I/O status
Led (green)
24 V
PTC
Clock
VDR
Output status Pull
GND
1) The offset specifies the position of the register within the CAN object.
Name:
ConfigOutput14
This configuration register is used to set the coding, the clock rate and the number of bits. Default = 0. This must
be set once using an acyclic write command.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 11 125 kHz
8 - 13 SSI number of bits Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
Name:
ConfigAdvanced
This configuration register is used to set the coding, the clock rate, the number of bits and the monostable multivi-
brator settings. Default = 0. This must be set once using an acyclic write command.
It only differs from ConfigOutput14 by data length and additional monostable multivibrator testing.
Data type Value
UDINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
16 - 17 Monostable multivibrator check 00 Check OFF, no additional clock bit
01 Check set to High level
10 Check set to Low level
11 Level is clocked but ignored
18 - 31 Reserved 0
Clock
Name:
Encoder01
The SSI encoder value is displayed as a 32-bit position value. The SSI position value is generated synchronously
with the X2X cycle.
Data type Value Filter
UDINT 0 to 4,294,967,295 SSI position
Name:
DigitalInput01
This register displays the input state of the digital input.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
3 DigitalInput01 0 or 1 Input state - Digital input 1
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
4.11.12 X20DC1976
The module is equipped with 1 input for an ABR incremental encoder with 5 V encoder signal. The encoder inputs
are monitored (A, B, R).
• 1 ABR incremental encoder 5 V, asymmetric
• Encoder input monitoring
• 2 additional inputs, e.g. for latch input
• 5 VDC, 24 VDC and GND for encoder supply
Product ID X20DC1976
Brief description
I/O module 1 ABR incremental encoder 5 V
General information
B&R ID code 0xA707
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.2 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input voltage 24 VDC (-15% / +20%)
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware <2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
Additional functions Latch input
Input resistance 7.03 kΩ
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash The encoder monitor has detected a line fault on the encoder inputs. The status
bits must be evaluated in order to provide a more detailed definition of this error.
The following error states are detected:
• Open line
• Short-circuit or voltage level too low
On Error or reset status
A1 Green Input state of counter input A
B1 Green Input state of counter input B
R1 Green Input state of reference pulse R
1-2 Green Input state of the corresponding digital input
4.11.12.5 Pinout
r e
X20 DC 1976
A1
B1
R1
1 2
DI 1 DI 2
Encoder 24 V+ Encoder 5 V+
GND GND
DC
A
Counter 1
R
Sensor 1
Counter inputs
ABR
I/O status
LED (green)
24 V
PTC
Encoder 24 V
24 V
DC
Encoder 5 V
DC
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
1) The offset specifies the position of the register within the CAN object.
The following registers are used for setting functions and configuring the module.
Name:
CfO_BWCNTEnableMaskChannel7_0
This register requires individually enabling error monitoring for each of the signal channels. "Open line", "short
circuit" and "voltage level too low" are reported as error states. Any errors that occur are reported in the error status
registers BW_Channel_x.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Enable error monitoring for signal A lines 0 Error monitoring - Encoder Signal A disabled
1 Error monitoring - Encoder Signal A enabled - Only default in
bus controller function model
1 Enable error monitoring for signal B lines 0 Error monitoring - Encoder Signal B disabled
1 Error monitoring - Encoder Signal B enabled - Only default in
bus controller function model
2 Enable error monitoring for signal R lines 0 Error monitoring - Encoder Signal R disabled
1 Error monitoring - Encoder Signal R enabled - Only default in
bus controller function model
3-7 Reserved 0
Name:
CfO_BWQuitTime_0
This register can be used to enable an additional automatic acknowledgment of the error status through timing.
If a valid time is set, then the acknowledgment can still be made manually, the only difference is that automatic
acknowledgment will take place on the module after the defined amount of time has passed. If the error state has
not yet been corrected, then the error status remains and the time is reset. Make sure that the time is set long
enough for the higher-level system to reliably detect the status messages.
If the timing = 0, then acknowledgment is only possible using the cyclic acknowledgment registers.
Data type Value Information
UDINT 0 No automatic acknowledgment - Only default in bus controller function model
1 to 2.147.483.647 Time for automatic acknowledgment [μs]
Name:
CfO_LatchMode
This register is used to set the latch mode:
• Single shot latch mode:
The latch function must be enabled/set. After a successful latch procedure, the activation must be reset in
order for a new latch procedure to be activated.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired.
A changed counter state on Encoder01LatchCount indicates that the latch procedure has been performed. The
counter value is stored in the latch register Encoder01Latch.
Data type Value Information
USINT 0 Single shot latch procedure
1 Continuous latch procedure
Name:
CfO_LatchComparator
This register defines the signal channels and their level for triggering the latch procedure.
• This mainly configures which channels are linked to generate the latch event. All three signals from the
encoder and digital input 1 can be used for the "AND" operation.
• The "active voltage level" needed for the latch procedure can now be used according to the physical signals.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Defines signal level for encoder signal A 0 Low
1 High
1 Defines signal level for encoder signal B 0 Low
1 High
2 Defines signal level for encoder signal R 0 Low
1 High
3 Defines signal level for digital input 1 0 Low
1 High
4 Use encoder signal A to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal A
5 Use encoder signal B to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal B
6 Use encoder signal R to trigger latch procedure 0 Disabled
1 Latch function linked to encoder signal R
7 Use digital input 1 to trigger latch procedure 0 Disabled
1 Latch function linked to digital input 1
The following registers must be set to the specified constant value for correct physical configuration:
Name:
CfO_SIframeGenID
Data type Value Information
USINT 9 Only default in the bus controller module
Name:
CfO_SystemCycleTime
Data type Value Information
UINT 800 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh01
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh02
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh03
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh04
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_PhyIOConfigCh05
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_BWQuitTimeSelChannel7_0
Data type Value Information
USINT 0 Only default in the bus controller module
Name:
CfO_CounterCycleSelect
Data type Value Information
USINT 2 Only default in the bus controller module
Name:
CfO_CounterMode
Data type Value Information
USINT 3 Only default in the bus controller module
Name:
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Name:
Encoder01
The counter state of the incremental encoder is displayed as a 16 or 32-bit counter value. Only the 16-bit value
is available in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01TimeValid
The net time of the last valid counter value is the time of the last valid counter value recorded on the module. The
user is able to determine the validity of the counter value by evaluating its age in the program. This means that the
module and error status bits do not have to be checked additionally to determine the validity of the value.
The net time of the last valid counter value that was read is displayed as a 16 or 32-bit value. Only the 16-bit value
is available in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01TimeChanged
For slow X2X Link cycles, the net time of the last counter value change can be used to more accurately determine
the speed.
The net time of the last counter value change is displayed as 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value Information
INT -32768 to 32767 NetTime in µsec.
DINT1) -2.147.483.648
bis 2.147.483.647
Name:
Encoder01Latch
The counter value at the time of the last latch is displayed as a 16 or 32-bit value. Only the 16-bit value is available
in the bus controller function model.
Data type Value
INT -32768 to 32767
DINT1) -2.147.483.648 bis 2.147.483.647
Name:
Encoder01LatchCount
The latch events are counted and stored in a cyclic 8-bit counter. This counter is incremented with each latch event,
thereby indicating a new occurrence. The new latched counter value is stored in the respective latch register.
Data type Value
SINT -128 to 127
Name:
Encoder01Command
This register can be used to
1 reset the counter value. The counter is kept at zero until this command is reset.
2 enable the latch procedure. If the latch configuration is valid and matches the hardware signals, then this
activation causes the counter value to be saved in the latch register.
The two different latch configurations that are possible (see section 4.11.12.8.3.3 "Setting the latch mode") must
be handled as follows:
• Single shot latch mode:
After successful latching, indicated by the latch event counter, activation must be reset before any more
latching is possible. The activation must be set again if additional latching is needed.
• Continuous latch mode:
The latch function only has to be enabled/set as long as latching is desired. The latch event counter is
incremented with each event.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01Reset 0 Do not reset
1 Set encoder value to 0
1 Encoder01LatchEnable 0 Do not activate latch
1 Latching
2-7 Reserved 0
Name:
Encoder01_A
Encoder01_B
Encoder01_R
DigitalInput01 to DigitalInput02
This register displays the input status of the signal lines from the encoder and the digital inputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder01_A 0/1 Input state of encoder signal A
1 Encoder01_B 0/1 Input state of encoder signal B
2 Encoder01_R 0/1 Input state of encoder signal R
3 Reserved 0
4 DigitalInput01 0/1 Input state - Digital input 1
5 DigitalInput02 0/1 Input state - Digital input 2
6-7 Reserved 0
The error states are latched when they occur and are maintained until acknowledged. The counter and time reg-
isters are not updated if there are pending or unacknowledged errors.
Bit structure:
Bit Name Value Information
0 BW_Channel_A 0 No error in encoder signal A
1 Open line, short circuit or voltage level too low
1 BW_Channel_B 0 No error in encoder signal B
1 Open line, short circuit or voltage level too low
2 BW_Channel_R 0 No error in encoder signal R
1 Open line, short circuit or voltage level too low
3-7 Reserved 0
Name:
BW_QuitChannel_A
BW_QuitChannel_B
BW_QuitChannel_R
This register can be used to acknowledge the latched error states of the signal lines from the encoder. However,
if there are still pending errors remaining, then the error status remains active. After acknowledging the errors, the
bits must also be reset or else any repetition of the error would be undetected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 BW_QuitChannel_A 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal A
1 BW_QuitChannel_B 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal B
2 BW_QuitChannel_R 0 No acknowledgment
1 Acknowledgment of error status - Encoder signal R
3-7 Reserved 0
The latched error states of the signal lines from the encoder can be acknowledged manually. However, if there
are still pending errors remaining, then the error status remains active. After successfully acknowledging the errors
(latched error status = 0), the acknowledge bits must still be reset by the user or else a re-occurrence of an error
could be overlooked by the user.
Example 1: Cause of error corrected before being acknowledged
An error has occurred on a signal line. The error state is detected and latched by the module.
The error is acknowledged by the user after the cause of error has been corrected. The latched
error status changes to zero.
The manual acknowledge must now be reset so that any new errors will be recognized by the
user.
Manual acknowledgment
Manual acknowledgment
Figure 282: Cause of error not yet corrected before being acknowledged
In addition to manual acknowledgment, automatic acknowledgment of the latched error states after a specified
amount of time can also be enabled. Make sure that the time is set long enough for the higher-level system to
reliably detect the status messages and for the validity of the counter value to be determined using its age.
If the time specification = 0, then only manual acknowledgment is possible.
Example 1: An error has occurred on a signal line. The error state is detected and latched by the module. The
time for automatic acknowledgment starts counting after the cause of error has been corrected.
The error is acknowledged as soon as the time expires. The latched error status changes to zero.
Automatic acknowledgment
Time Time
start expired
Automatic acknowledgment
Time Time
start expired here
Manual acknowledgment
Name:
PowerSupply01 to PowerSupply02
This register shows the status of the integrated encoder supplies. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1 PowerSupply02 0 5 VDC encoder power supply OK
1 5 VDC encoder power supply faulty
2-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
150 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
150 µs
4.11.13 X20DC2190
This module can be used to determine paths and to calculate speeds at the same time. The ultrasonic transducer
rods are connected directly to the RS422 interface. Communication to the transducer rod takes place using start/
stop signals. With the DPI/IP protocol, it is also possible, for example, to read operational properties directly from
the transducer. During service (when a transducer is being exchanged) the machine can be started again quickly
without additional configuration work.
The module is designed for connecting two transducer rods with a total of up to four paths. That means, for example,
that two ultrasonic transducers with two magnets each or one with four magnets can be used. The combination
three/one is also possible. The module provides 24 VDC as an external supply for the sensor.
• Ultrasonic transducer module
• Path measurement (resolution 10 µm)
• Speed measurement (resolution 100 µm/s)
• 1, 2, 3 and 4 magnetic rod measurements possible
• DPI/IP protocol supported
Product ID X20DC2190
Short description
I/O module Ultrasonic transducer module, 2 transducer rods, 4 position detection, speed measurement
General information
B&R ID code 0x2188
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
KC Yes
GOST-R Yes
Channels for path and speed measurements
Quantity 2
Supported encoder types Start/Stop interface
EP start/stop interface
DPI/IP interface
4.11.13.5 Pinout
r e
X20 DC 2190
1 2
Channel 1 Channel 2
Start + Start +
Start - Start -
Stop + Stop +
Stop - Stop -
GND GND
DC
Ultrasonic
Transducer rod
Start +
Start -
Stop +
Stop -
+24 VDC
GND
1) The offset specifies the position of the register within the CAN object.
In the bus controller function model, the measurements made from the module are not synchronized with the X2X
Link. The time between two measurements is defined by the configured recovery time for the rod (see section
4.11.13.7.11 "Channel configuration" on page 789) unlike on the X2X where it is the smallest multiple of the X2X
cycle time that is larger than the configured recovery time.
Two registers need to be configured to initialize an ultrasonic transducer rod and receive valid measurements. The
first step is to enter the length of the rod (see section 4.11.13.7.12 "Rod length 1 and 2" on page 789). The wave
propagation speed for the rod must then be defined (see section 4.11.13.7.8 "Ultrasonic speed specification" on
page 787). This information can usually be found directly on the transducer rod itself or in its data sheet.
If the plausibility limits remain set to 0 (default value), one of the respective ErrorStatus registers will now indicate
faulty readings or plausibility errors. If this is the case, plausibility mode can be disabled using the "ConfigOutput01"
register (see section 4.11.13.7.10 "Module configuration" on page 788). This will cause the positions of the mag-
nets to be displayed on the rod.
Name:
Position01 - Position04
These registers contain the position of the individual magnets on the transducer rods.
Data type Value
DINT -2,147,483,648 to 2,147,483,647: Resolution 1 µm
Name:
Speed01 to Speed04
These registers contain the speed of the individual magnets on the transducer rods. A resolution of 0.1 mm/s is
achieved by calculating the speed from 2 position values within a 100 ms interval.
Data type Value
INT -32768 to 32767: Resolution 0.1 mm/s
Name:
ErrorStatus01 to ErrorStatus04
These registers can be used to indicate the error status for individual channels.
Data type Value
USINT See bit structure.
Bit structure
Bit Description
0-3 Counter for plausibility errors (cyclic)
4-7 Counter for mis-measurements (cyclic)
Information:
If the registers "USSpeed01" and "USSpeed02" are unequal to 0 after the module starts up, the respec-
tive error counters on slower fieldbus systems (e.g. CAN I/O) may continue to count until the module
configuration is completed. In some cases, this is due problems between the respective rod and the
default configuration.
Name:
StatusInput01
This register displays the status information for the transducer rods.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Supply voltage too low 0 Supply voltage OK
1 Supply voltage too low
1 Supply voltage too high 0 Supply voltage OK
1 Supply voltage too high
2 Transducer Rod 1 0 Ok
1 Deactivated or not initialized
3 Transducer Rod 2 0 Ok
1 Deactivated or not initialized
4 Transducer Rod 1 0 Protocol error (invalid data)
1 Protocol OK (valid data)
5 Transducer Rod 2 0 Protocol error (invalid data)
1 Protocol OK (valid data)
6-7 Reserved
Name:
USSpeed01 to USSpeed02
The module does not perform any measurements on the respective rod while these registers have the value 0.
Also disabled:
• Automatic check to determine whether a rod is connected
• Parameter upload via DPI/IP or EP protocol
If a value >0 but <1000cm/s is specified here, the module freezes all measurements and error counters of the
corresponding rod, regardless of whether plausibility mode is enabled or not. Based on the default ultrasonic speed
of 280,000 cm/s, however, periodic measurement start pulses continue to be generated according to the formula
in section 4.11.13.7.11 "Channel configuration" on page 789. In this case the rod check (inserted/not inserted
and parameter upload) continues to be active.
As soon as a valid value (≥1000) is specified, the module recalculates the measurement rate (see section
4.11.13.7.11 "Channel configuration" on page 789) and begins the position/speed measurement.
Data type Value
UDINT 0 to 4,294,967,296: Resolution 1 cm/s
Name:
StatusOutput01
This register makes it easier to more quickly determine new offsets (= zero positions) for the individual magnets.
This approach is an alternative or additional method to determining an offset via configuration registers (see section
4.11.13.7.13 "Offset position on the transducer" on page 790).
If the respective bit changes from 0 to 1 in "StatusOutput01" (see following table) then the current mechanical
position of the respective magnet becomes the calculated zero position (register "Position0x" = 0).
From that moment, the current mechanical position will be subtracted from all future measured positions. This is
essentially a type of referencing. The max. and min. magnet paths (see section 4.11.13.7.14 "Plausibility check
configuration" on page 790) are now based on the new zero position.
This process can be repeated at any time by setting the bit again.
Information:
An offset position determined in this manner CANNOT be read out. The registers
"ConfigOutput07Read", "ConfigOutput08Read", "ConfigOutput15Read" and "ConfigOutput16Read"
can only be used to read the current contents of "ConfigOutput07", "ConfigOutput08", "ConfigOut-
put15" and "ConfigOutput16".
Data type Value
USINT See bit structure.
Name:
ConfigOutput01
This register configures the module.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Plausibility mode 0 The plausibility error counter is incremented with each implau-
sible measurement and the last plausible measurement value is
"frozen" (default)
1 The plausibility error counter is incremented with each implau-
sible measurement and the implausible measurement value is
forwarded to the controller
1 Reserved
2-3 Tolerance for monitoring the supply voltage 00 25%
01 20%
10 15%
11 10%
4-7 Magnet number 0000 4 magnets on channel 1, channel 2 not available
0001 3 magnets on channel 1, 1 magnet on channel 2
0010 2 magnets on channel 1, 2 magnets on channel 2
0011 1 magnet on channel 1, 0 magnets on channel 2
0100 2 magnets on channel 1, 0 magnets on channel 2
0101 3 magnets on channel 1, 0 magnets on channel 2
0110 2 magnets on channel 1, 1 magnet on channel 2
0111 1 magnet on channel 1, 1 magnet on channel 2
1xxx Reserved
Name:
ConfigOutput02
This register can be used to configure the individual channels.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-2 Transducer Rod 1 000 User parameter
001 DPI/IP (Balluf)
010 EP Start/Stop (MTS)
011 Reserved
1xx Reserved
3-4 Rod 1: Start/Stop IF type 00 Start/Stop Signal: Rising edge - rising edge
01 Start/Stop Signal: Falling edge - falling edge
10 Start/Stop Signal: Rising edge - falling edge (gate time)
11 Only Stop Signal: Start when signal is triggered (initialization
pulses)
5 Rod 1: Recovery time factor, minimum time between two mea- 0 3 x USW runtime for rod (default)
surements 1 2 x USW runtime for rod
6-7 Reserved
8 - 10 Transducer Rod 2 000 User parameter
001 DPI/IP (Balluf)
010 EP Start/Stop (MTS)
011 Reserved
1xx Reserved
11 - 12 Rod 2: Start/Stop IF type 00 Start/Stop Signal: Rising edge - rising edge
01 Start/Stop Signal: Falling edge - falling edge
10 Start/Stop Signal: Rising edge - falling edge (gate time)
11 Only Stop Signal: Start when signal is triggered (initialization
pulses)
13 Rod 2: Recovery time factor, minimum time between two mea- 0 3 x USW runtime for rod (default)
surements 1 2 x USW runtime for rod
14 - 15 Reserved
Name:
ConfigOutput03 to ConfigOutput04
These registers are used to configure the length of the respective rod.
• Rod length 1: ConfigOutput03
• Rod length 2: ConfigOutput04
Data type Value
UDINT 0 to 4,294,967,296: Resolution 1 mm
Name:
ConfigOutput07 to ConfigOutput08
ConfigOutput15 to ConfigOutput16
These registers are used to assign the respective magnet an offset position (= zero position) on the transducer.
The max. and min. magnet paths refer to these specified offsets (see 4.11.13.7.14 "Plausibility check configuration"
on page 790). If the offset is changed using the StatusOutput01 register, this becomes the new zero position.
This does not affect the contents of the offset register.
• Offset magnet 1: ConfigOutput07
• Offset magnet 2: ConfigOutput08
• Offset magnet 3: ConfigOutput15
• Offset magnet 4: ConfigOutput16
Data type Value
DINT -2,147,483,648 to 2,147,483,647: Resolution 1 µm
These registers are used to configure the plausibility check (also see section 4.11.13.7.6 "Error status" on page
786).
Name:
ConfigOutput09 to ConfigOutput10
ConfigOutput17 to ConfigOutput18
These registers are used to assign the min. plausible magnet position based on the applicable offset.
• Min. path - magnet 1: ConfigOutput09
• Min. path - magnet 2: ConfigOutput10
• Min. path - magnet 3: ConfigOutput17
• Min. path - magnet 4: ConfigOutput18
Data type Value
DINT -2,147,483,648 to 2,147,483,647: Resolution 1 µm
Name:
ConfigOutput11 to ConfigOutput12
ConfigOutput19 to ConfigOutput20
These registers are used to assign the max. plausible magnet position based on the applicable offset.
• Max. path - magnet 1: ConfigOutput11
• Max. path - magnet 2: ConfigOutput12
• Max. path - magnet 3: ConfigOutput19
• Max. path - magnet 4: ConfigOutput20
Data type Value
DINT -2,147,483,648 to 2,147,483,647: Resolution 1 µm
Name:
ConfigOutput13 to ConfigOutput14
ConfigOutput21 to ConfigOutput22
These registers are used to assign the max. plausible magnet speed.
• Max. speed - magnet 1: ConfigOutput13
• Max. speed - magnet 2: ConfigOutput14
• Max. speed - magnet 3: ConfigOutput21
• Max. speed - magnet 4: ConfigOutput22
Data type Value
UDINT 0 to 4,294,967,296: Resolution 0.1 mm/s
Name:
ConfigOutput23 to ConfigOutput24
These registers are used to configure the dead time of the respective rod.
• Dead time for rod 1: ConfigOutput23
• Dead time for rod 2: ConfigOutput24
To prevent the multiple pulses that occur with some encoders from affecting the measurement, all pulses received
within a configurable timespan from the beginning of the measurement are not evaluated. The range for the dead
time lies between 0 and 255 µs. The following figure illustrates the effects of defining a dead time:
Init pulse Init pulse
to the encoder
Pulse t
ignored
Name:
ConfigOutput01Read to ConfigOutput04Read
ConfigOutput07Read to ConfigOutput24Read
These registers are used to read the states of the corresponding configuration registers.
Name:
StatusInput09 to StatusInput36
These registers are used to store the data read after a parameter upload from transducer rods with DPI/IP protocol
or EP protocol. The registers "StatusInput19" to "StatusInput36" remain empty (0x0000) on transducer rods with
EP protocol.
Requirements for a successful upload of the transducer rod parameters to the module:
1. Selection of the communication protocol (DPI/IP or EP). See section . 4.11.13.7.11 "Channel configuration"
on page 789
2. Transducer rod must support the respective protocol.
3. If the transducer rod does not support the selected protocol, the module will detect this after a timeout of
approx. 300 ms and will treat the rod as a "normal" transducer rod.
After the module is started or after a transducer rod is connected, the parameter upload should be complete within
200 to 400 ms.
A communication error causes the data upload to cancel. A new upload attempt can be initiated by the user by
deactivating and reactivating the communication protocol using asynchronous access.
All rod parameters can be read to the controller using asynchronous access. The read parameters "rod length"
and "ultrasonic speed" are NOT automatically uploaded to the module.
It is left up to the application whether the upload values for rod length 1 and rod length 2 or for ultrasonic speed 1
and ultrasonic speed 2 are uploaded.
Information:
Keep in mind that no position measurements can be performed on a rod while parameters are being
uploaded. The module freezes all existing position/speed data for all magnets on the rod while the
parameters are uploading. Parameters should therefore only be uploaded with the machine stopped,
and this should be ensured by the application.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
250 µs
4.11.14 X20DC2395
This module is a multifunctional counter module. It can be connected to one SSI encoder, one ABR encoder, two
AB encoders or four event counters. Two outputs are available for pulse width modulation. The functions can also
be mixed.
• 24 VDC encoder inputs
• SSI, ABR, AB or event counters for inputs
• Pulse width modulation for outputs
• 24 VDC and GND for encoder supply
Information:
This module is a multifunctional module. Some bus controllers only support the default function model.
Default function model:
• 2x event counter (24 V)
• 2x PWM output (24 V)
Product ID X20DC2395
Short description
I/O module 1 SSI absolute encoder, 24 V, 1 ABR incremental encoder, 24 V, 2 AB incremental encoders,
24 V, 4x event counters or 2x pulse width modulation, time measurement, relative timestamp
General information
Input voltage 24 VDC -15% / +20%
B&R ID code 0x1CD4
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using the status LED and software (output error status)
Power consumption
Bus 0.01 W
Internal I/O 1.4 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Output - Output No
Output - Bus Yes
Output - Encoder No
Encoder - Bus Yes
Encoder - Encoder No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Incremental encoder
Quantity 2
Encoder inputs 24 V, asymmetrical
Counter size 16/32-bit
Input frequency Max. 100 kHz
Evaluation 4x
Encoder supply Module-internal, max. 600 mA
Overload behavior of the encoder supply Short circuit protection, overload protection
SSI absolute encoder
Quantity 1
Encoder inputs 24 V, asymmetrical
Counter size 32-bit
Max. transfer rate 125 kbit/s
Encoder supply Module-internal, max. 600 mA
Keying Gray/Binary
CLK: Output current Max. 100 mA
Overload behavior of the encoder supply Short circuit protection, overload protection
Event counter
Quantity 4
Nominal voltage 24 VDC
Signal form Square wave pulse
Evaluation Each edge, cyclic counter
Input frequency Max. 100 kHz
Input current at 24 VDC Approx. 1.3 mA
Input resistance 18.4 kΩ
Isolation voltage between channel and bus 500 Veff
Counter frequency 200 kHz
Counter size 16/32-bit
Input filter
Hardware ≥2 µs
Software -
Switching threshold
Low <5 VDC
High >15 VDC
Time measurement
Possible measurements Gate time, period duration, edge offset for various channels
Measurements per module Up to 9
Measurements per channel Up to 2
Counter size 16-bit
Counter frequency
Internal 8 MHz, 4 MHz, 2 MHz, 1 MHz, 500 kHz, 250 kHz, 125 kHz, 62.5 kHz
Signal form Square wave pulse
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
1-4 Green Status of the corresponding digital signal
4.11.14.5 Pinout
r e
X20 DC 2395
1
2
3
4
Channel 1
Channel 2
Channel 3
Channel 4
Encoder 24 V +
GND
DC
Data
Cycle
Counter 1
A
B
R
PWM
The following functions can be configured on the module. They cannot all be used at the same time due to the
multiple use of the hardware channels and the limited cyclic data length.
• 4 digital channels, 2 of which can be configured as outputs
• 4 event counters with configurable counting direction and optional referencing via digital input
• 2 PWM outputs
• 2 up/down counters, each with optional latch inputs and comparator output
• 2 AB counters, each with optional latch inputs and comparator output
• 1 ABR encoder with configurable reference pulse edge and reference position, optional reference enable
input, latch input and comparator output
• 1 SSI counter with optional latch input and comparator output
• 2 edge-triggered time measurement functions with configurable start edge based on current configuration
settings
The functions listed here are directly assigned to the respective hardware channels and cannot be changed:
Channel Signal connections
1 • Digital input 1
• Event counter 1
• AB encoder 1 - signal line A
• Up/down counter 1 - frequency
• SSI encoder 1 - data line
• ABR encoder 1 - signal line A
2 • Digital input 2
• Digital output 2
• Event counter 2
• PWM output 2
• AB encoder 1 - signal line B
• Up/down counter 1 - direction
• SSI encoder 1 - clock line
• ABR encoder 1 - signal line B
3 • Digital input 3
• Event counter 3
• AB encoder 2 - signal line A
• Up/down counter 2 - frequency
• ABR encoder 1 - signal line R
4 • Digital input 4
• Digital output 4
• Event counter 4
• PWM output 4
• AB encoder 2 - signal line B
• Up/down counter 2 - direction
• ABR encoder 1 - reference enable input
Options available in addition to these basic functions, such as comparator outputs or latch inputs, can be configured
freely to unused input/output channels.
Input x
VDR
Input status
I/O status
24 V
PTC
Encoder 24 V LED (green)
GND
GND
24 V
PTC
Output x
VDR
Output status Pull
GND
Output
monitoring
100 H 10 H 1H
1000
0.1 H
Coil resistance
Coil inductance
[Ω]
0.01 H
240 Ω ≙ 100 mA
0.1 1 10 100 1000 10000
The outputs of the module can be operated as PWM outputs. The period duration is calculated using the following
formula:
n
Period duration = s
48000
A value of 2 to 65535 can be defined for n.
Example
n Period duration Frequency
2 416 μs 24 kHz
24000 500 ms 2 Hz
48000 1s 1 Hz
65535 1.36 s 0.73 Hz
Unlike the function models 0 and 1, this model only offers a selection of functions with a limited scope of config-
uration on the module.
The following functions are provided and can be run at the same time:
• 2 event counter with configurable counting direction
• 2 PWM outputs
Register Offset1) Name Data type Read Write
Cyclic Acyclic Cyclic Acyclic
Configuration
(N-1) * 2 - CfO_CFGchannel0N (Index N = 1 to 4) USINT ●
64 + N * 2 - CfO_LEDNsource (Index N = 0 to 3) USINT ●
2,056 - CfO_Counter1configReg0 USINT ●
2,312 - CfO_Counter2configReg0 USINT ●
Communication
2,080 0 EventCounter01 UINT ●
2,336 2 EventCounter03 UINT ●
6,146 0 PWMOutput02 UINT ●
6,162 2 PWMOutput04 UINT ●
40 4 Status of encoder supply USINT ●
PowerSupply01 Bit 0
1) The offset specifies the position of the register within the CAN object.
Name:
CfO_LED0source to CfO_LED3source
These registers can be used to define how the module's LED status indicators are used. Blinking patterns can be
generated from the application, and the status of the physical inputs and outputs can be indicated.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 MODE = 0 0 LED off
1 Blinking quickly
2 Blinking
3 Blinking slowly
4 Single flash
5 Double flash
6 to 15 Reserved
MODE = 1 (inverted) 0 LED on
1 Blinking quickly
2 Blinking
3 Blinking slowly
4 Single flash
5 Double flash
6 to 15 Reserved
MODE = 2 0 to 3 Number of the physical input channel
4 to 15 Reserved
MODE = 3 0 to 3 Number of the physical output channel
4 to 15 Reserved
4-7 Selection of the mode for the LED status indicator 0 LED blinking pattern
1 Inverted LED blinking pattern
2 Displays a channel's physical input status
3 Displays a channel's physical output status
4 to 15 Reserved
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
Name:
CfO_CFGchannel01 to CfO_CFGchannel04
This register can be used to configure physical I/O channels 1 to 4.
Information:
Except for bit 2 (inverted input), all other bits are only available for channels 2 and 4.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Push1) 0 Disabled
1 Enabled
1 Pull1) 0 Disabled
1 Enabled
2 Inverted input 0 Disabled
1 Enabled
3 Inverted output 0 Disabled
1 Enabled
4-7 Output type 0 Direct I/O
1 to 5 Reserved
6 PWM (channel-specific)
7 SSI clock (channel-specific)
Name:
CfO_OutClearMask
The settings in this register only affect the values written to registers 4.11.14.12.4.5 "DigitalOutput02 and 04".
• 0 allows manual reset of digital outputs using registers DigitalOutput02 and 04
• 1 prevents manual reset of digital outputs using registers DigitalOutput02 and 04
When "1" is used, the "output event function" can be used to reset the outputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 DigitalOutput02 0 Writing 0 to the DigitalOutput02 register resets the output
1 Writing 0 from the DigitalOutput02 register does not reset the
output
2 Reserved -
3 DigitalOutput04 0 Writing 0 to the DigitalOutput04 register resets the output
1 Writing 0 from the DigitalOutput04 register does not reset the
output
4-7 Reserved -
Name:
CfO_OutSetMask
The settings in this register only affect the values written to registers 4.11.14.12.4.5 "DigitalOutput02 and 04".
• 0 allows manual setting of digital outputs using registers DigitalOutput02 and 04
• 1 prevents manual setting of digital outputs using registers DigitalOutput02 and 04
When "1" is used, the "output event function" can be used to set the outputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 DigitalOutput02 0 Writing 1 to the DigitalOutput02 register sets the output
1 Writing 1 from the DigitalOutput02 register does not set the out-
put
2 Reserved -
3 DigitalOutput04 0 Writing 1 to the DigitalOutput04 register sets the output
1 Writing 1 from the DigitalOutput04 register does not set the out-
put
4-7 Reserved -
Name:
see "Name in the AS I/O configuration"
This register reads the input status of a physical channel. The polarity settings are accounted for in the value (bit
2 in 4.11.14.12.4.1 "CfO_CFGchannel[x]" register).
The bits in this register are shown in the AS I/O mapping table under different names based on the function used
in order to improve readability.
Data type Value
USINT See bit structure.
Bit structure:
Bit Physical input channel Value Name in the AS I/O configuration
0 Channel 1 0 or 1 DigitalInput01
1 Channel 2 0 or 1 DigitalInput02
StatusDigitalOutput02
2 Channel 3 0 or 1 DigitalInput03
3 Channel 4 0 or 1 DigitalInput04
StatusDigitalOutput04
ReferenceEnableSwitch01
ComparatorActualValue01
4-7 Reserved -
Name:
DigitalOutput02 and DigitalOutput04
The output status of a physical channel can be written using this register. In order to configure a channel as an
output:
1 Bit 0 "Push" and/or bit 1 "Pull" must be enabled in the 4.11.14.12.4.1 "CfO_CFGchannel[x]" register.
2 Bits 4 to 7 in the 4.11.14.12.4.1 "CfO_CFGchannel[x]" register must be set to Direct I/O.
3 0 must be set for the respective channel in the 4.11.14.12.4.2 "CfO_OutClearMask" and 4.11.14.12.4.3
"CfO_OutSetMask" registers.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 DigitalOutput02 0 or 1 Output status of channel 2
2 Reserved -
3 DigitalOutput04 0 or 1 Output status of channel 4
4-7 Reserved -
The module provides configurable event functions. An event function can be connected to physical I/O and the
values derived from them (e.g. counters) or be purely used for internal processing.
Every event function has event inputs and outputs. Event functions can also have only inputs or only outputs. Each
event output has a unique event ID. It is possible to configure when an event should be generated on an event
output. The effect of an event is determined by the respective event function.
Event functions can also be linked to one another. The link takes place using the event input. Every event input
has a 16-bit register to which the event number of the linked event output is written.
Information:
The module functions that can be configured in the AS I/O configuration are primarily based on these
event functions and their links. Changes in the AS I/O configuration have multiple effects on event
functions and their links.
Various hardware and software functions send event IDs or require event IDs in order to start. The following table
shows all of the IDs available to configure the module.
Event ID Description
Direct event inputs
512 Comparator condition FALSE
513 Comparator condition TRUE
Counter comparator function
2,112 Counter function 1 Event function 1; FALSE
2,113 Event function 1; TRUE
2,144 Event function 2; FALSE
2,145 Event function 2; TRUE
2,368 Counter function 2 Event function 1; FALSE
2,369 Event function 1; TRUE
2,400 Event function 2; FALSE
2,401 Event function 2; TRUE
Edge events
4,096 Falling edge on I/O channel Channel 1
... ...
4,099 Channel 4
4,112 Rising edge on I/O channel Channel 1
... ...
4,115 Channel 4
4,128 Rising or falling edge on I/O channel Channel 1
... ...
4,131 Channel 4
SSI counter events
7,168 SSI valid
7,169 SSI ready
SSI comparator events
7,232 SSI 1 comparator condition FALSE
7,233 TRUE
Timerevents
208 Timer1 50 μs
209 Timer2 100 μs
210 Timer3 200 μs
211 Timer4 400 μs
212 Timer5 800 μs
213 Timer6 1600 μs
214 Timer7 3200 μs
215 Timer8 3200 μs (time offset to timer 7)
Network functions
224 SOAISOP (synchronous out asynchronous in start of protocol)
225 AOSISOP (asynchronous out synchronous in start of protocol)
226 SOAIEOP (synchronous out asynchronous in end of protocol)
227 AOSIEOP (asynchronous out synchronous in end of protocol)
Idle event
192 No-load operation
Timer
There are 8 timer events that the module can generate.
Information:
The timers have the highest event priority. All other system functions are interrupted when a timer
event occurs, and jitter for the amount of time it takes to process the event.
Idle event
Idle time is the time that remains after the system has processed all higher priority events and operations. The
module performs the following functions during idle time:
• Handling of the asynchronous protocol
• Mechanism for (re-)linking events
• Operation of LEDs
• Execution of event event functions linked to the idle function
Information:
Edge detection can also be used for channels that are configured as outputs.
To stabilize the system, there is a mechanism that limits the number of events created through edge recognition.
At least one idle event must occur between two edge events for the same edge.
The "CfO_FallingDisProtection" and "CfO_RisingDisProtection" registers can be used to disable this limitation for
each edge, and then an event will be generated for every edge. However, this can cause a system overload, i.e.
I/O operation can fail for up to 100 ms before the module changes to the reset state.
Bit structure:
Bit Description Value Information
0 Channel 1 0 No event generated on falling edge.
1 Events 4096 and 4128 are generated on falling edge.
... ...
3 Channel 4 0 No event generated on falling edge.
1 Events 4099 and 4131 are generated on falling edge.
4-7 Reserved -
Name:
CfO_EdgeDetectRising
This register defines whether an event is generated on a rising edge.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 No event generated on rising edge.
1 Events 4112 and 4128 are generated on rising edge.
... ...
3 Channel 4 0 No event generated on rising edge.
1 Events 4115 and 4131 are generated on rising edge.
4-7 Reserved -
Name:
CfO_FallingDisProtection
This register can be used to enable/disable the event frequency limit for falling edges on the respective channel.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Event frequency limit enabled.
1 Event frequency limit disabled.
... ...
3 Channel 4 0 Event frequency limit enabled.
1 Event frequency limit disabled.
4-7 Reserved -
Name:
CfO_RisingDisProtection
This register can be used to enable/disable the event frequency limit for rising edges on the respective channel.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Event frequency limit enabled.
1 Event frequency limit disabled.
... ...
3 Channel 4 0 Event frequency limit enabled.
1 Event frequency limit disabled.
4-7 Reserved -
Name:
CfO_DIREKTIOevent0IDwr
This register holds the event ID generated by the direct input function. For a list of all possible event IDs, see
4.11.14.12.5.1 "List of event IDs"
Data type Value Information
INT 192 to 7,233 ID of event function
Name:
CfO_DIREKTIOevent0mode
The mode in which the direct input function operates can be set in this register.
Comparator functions can be operated in 4 different modes. For a description, see "Comparator modes".
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Comparator mode 0 Off
1 Single
2 State change
3 Continuous
2-7 Reserved -
Name:
CfO_DIREKTIOevent0compState
This register contains the status bits that are compared with the bits specified in the "CfO_Ev0CompMask" register,
which contain the I/O input status, when an event is received.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Comparator status of channel 1 0 or 1
... ...
3 Comparator status of channel 4 0 or 1
4-7 Reserved -
Name:
CfO_Ev0CompMask
If a bit is set, then the input status of the respective channel is compared with that bit in the
"CfO_DIREKTIOeventcompState" register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Do not compare bit
1 Compare bit in register
... ...
3 Channel 4 0 Do not compare bit
1 Compare bit in register
4-7 Reserved 0
Name:
CfO_DIREKTIOoutclearmask0 to CfO_DIREKTIOoutclearmask1
Writing "1" to the bit position that corresponds to a channel resets the output if the output event function is being
executed. This corresponds to writing "0" to the 4.11.14.12.4.5 "DigitalOutput 02 and 04" registers.
The bit that corresponds to channels that should be reset should be set to "1" in the 4.11.14.12.4.2
"CfO_OutClearMask" register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 Channel 2 0 Reset channel 2
1 Do not reset channel 2
2 Reserved -
3 Channel 4 0 Reset channel 4
1 Do not reset channel 4
4-7 Reserved -
Name:
CfO_DIREKTIOoutsetmask0 to CfO_DIREKTIOoutsetmask1
Writing "1" to the bit position that corresponds to a channel sets the output if the output event function is being
executed. This corresponds to writing "1" to the 4.11.14.12.4.5 "DigitalOutput 02 and 04" registers.
The bit that corresponds to channels that should be reset should be set to "1" in the 4.11.14.12.4.3
"CfO_OutSetMask" register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 Channel 2 0 Set channel 2
1 Do not set channel 2
2 Reserved -
3 Channel 4 0 Set channel 4
1 Do not set channel 4
4 Reserved -
The module has 2 internal counter functions, each with 2 event counter registers. Each of these 2 counters is
permanently assigned to 2 physical inputs. This assignment cannot be changed.
The counter registers perform different functions based on how the event functions are connected. The counter
registers can be configured in the following ways:
• ABR counter
• AB counter
• Up/down counters
• Event counters
Different names are used for them in Automation Studio and in the register description to improve clarity.
Channel Counter function Counter register Name in AS
1 1 1 ABEncoder01
ABREncoder01
Counter01
EventCounter01
2 2 EventCounter02
3 2 1 ABEncoder02
Counter02
EventCounter03
4 2 EventCounter04
There are 3 steps for calculating the state of any counter function
1. The counter value is based on the 2 absolute value counters "abs1" and "abs2". They are only used internally in
the module and cannot be read. Depending on the mode, these registers show the respective physical input signals.
Mode
Edge counters AB encoders Up/down counter
abs1 Edges of counter channel 1 Increments in positive direction Counter channel 2 = 0:
Edges of counter channel 1
in up direction
abs2 Edges of counter channel 2 Increments in negative direction Counter channel 2 = 1
Edges of counter channel 1
in down direction
2. From the absolute value registers "abs1" and "abs2", 2 more counters are formed: "counter 1" and "counter 2".
These are only used internally in the module and cannot be read. The following values are used for the calculation:
• Absolute value registers "abs1" and "abs2"
• SW_reference_counter 1 and 2: This reference value can be defined by the "CfO_CounterPresetValue"
register to allow referencing <> 0.
• HW_reference_counter 1 and 2: In the "CfO_CounterEventMode" register, you can configure whether
latched values should be copied to these registers when counter events occur.
counter1 = abs1 + SW_reference_counter1 - HW_reference_counter1
counter2 = abs2 + SW_reference_counter2 - HW_reference_counter2
3. The counter registers contain the sum of the two internal counters "counter 1" and "counter 2". The
"CfO_CounterConfigReg" register allows you to define a sign for each "counter" register and define whether or
not it should be used.
Counter register = counter1 + counter2
All of the settings available in Automation Studio for AB encoders, ABR encoders, up/down counters and event
counters are based on the two counter functions.
The following configuration examples show the values with which Automation Studio initializes the module registers
in order to implement these functions.
The following table shows how the module's various event functions can be linked in order to configure an AB
encoder.
[x] stands for the respective counter function, either 1 or 2
Register Value Comment
For the function
CfO_Counter[x]config 0x01 Mode = Up/down counter
CfO_Counter[x]configReg0 0x0D Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.14.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
For the latch
CfO_Counter[x]event0config 0x000D Configuration of the calculation of the first value used for the latch
CfO_Counter[x]event0mode 0x03 Mode of the first counter event function - Continuous
CfO_Counter[x]event0IDwr (any) Number of the event that should trigger Latch 1 ("Latch 01 - Channel" in the AS
I/O configuration).
CfO_Counter[x]event1config 0x0D Configuration of the calculation of the second value used for the latch
CfO_Counter[x]event1mode 0x03 Mode of the second counter event function - Continuous
CfO_Counter[x]event1IDwr (any) Number of the event that should trigger Latch 2
For the comparator
CfO_Counter1event1IDwr 0x00D0 Event number of Timer 1 (50 μs)
Information:
The latch and comparator must not have the same event number!
CfO_Counter1event1config 0x900D or 0xA00D Configuration of the comparator for the second counter event
CfO_Counter1event1mode 0x03 Mode of the second counter event function - Continuous
CfO_DIREKTIOoutevent0IDwr 0x0861 TRUE event output of the second counter to trigger the direct output function
(set outputs).
CfO_DIREKTIOoutsetmask0 0x08, 0x20, 0x80 Outputs that should be set when comparator condition = TRUE
CfO_DIREKTIOoutevent1IDwr 0x0860 FALSE event output of the second counter to trigger the direct output function
(reset outputs).
CfO_DIREKTIOoutclearmask1 0x08, 0x20, 0x80 Outputs that should be reset when comparator condition = FALSE
The following table shows how the module's various event functions can be linked in order to configure an ABR
encoder.
Register Value Comment
For the function
CfO_Counter1PresetValue1 (any) Desired offset value for referencing
CfO_Counter1event0IDwr 0x0201 Link between the first counter event and the "direct input" comparator condition
TRUE
CfO_Counter1config 0x01 Mode = AB encoder
CfO_Counter1configReg0 0x0D Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.14.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
CfO_DIREKTIOevent0IDwr 0x1002 or 0x1012 Selection of the desired input edge as trigger for the ABR encoder function
CfO_Counter1event0config 0x0000 Configuration of the first counter event (for referencing)
CfO_DIREKTIOevent0mode 0x03 Mode of the "direct input function" - Continuous
CfO_DIREKTIOevent0compState 0x00 or 0x08 Comparator status for the "direct input function"
CfO_Ev0CompMask 0x08 Comparator mask for the "direct input function"
For the latch
CfO_Counter1event0config 0x000D Configuration of the calculation of the value used for the latch
CfO_Counter1event0mode 0x03 Mode of the first counter event function - Continuous
CfO_Counter1event0IDwr (any) Number of the event that should trigger the latch
For the comparator
CfO_Counter1event1IDwr 0x00D0 Event number of Timer 1 (50 μs)
Information:
The latch and comparator must not have the same event number!
CfO_Counter1event1config 0x900D or 0xA00D Configuration of the comparator for the second counter event
CfO_Counter1event1mode 0x03 Mode of the second counter event function - Continuous
CfO_DIREKTIOoutevent0IDwr 0x0861 TRUE event output of the second counter to trigger the direct output function
(set outputs).
CfO_DIREKTIOoutsetmask0 0x08, 0x20, 0x80 Outputs that should be set when comparator condition = TRUE
CfO_DIREKTIOoutevent1IDwr 0x0860 FALSE event output of the second counter to trigger the direct output function
(reset outputs).
CfO_DIREKTIOoutclearmask1 0x08, 0x20, 0x80 Outputs that should be reset when comparator condition = FALSE
The following table shows how the module's various event functions can be linked in order to configure an up/
down counter.
[x] stands for the respective counter function, either 1 or 2
Register Value Comment
For the function
CfO_Counter[x]config 0x03 Counter mode = Up/down counter
CfO_Counter[x]configReg0 0x0D, 0x07 Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.14.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
For the latch
CfO_Counter[x]event0config 0x0D, 0x07 Configuration of the calculation of the first value used for the latch
CfO_Counter[x]event0mode 0x03 Mode of the first counter function - Continuous
CfO_Counter[x]event0IDwr (any) Number of the event that should trigger Latch 1
CfO_Counter[x]event1config 0x0D, 0x07 Configuration of the calculation of the second value used for the latch
CfO_Counter[x]event1mode 0x03 Mode of the second counter function - Continuous
CfO_Counter[x]event1IDwr (any) Number of the event that should trigger Latch 2
For the comparator
CfO_Counter1event1IDwr 0x00D0 Event number of Timer 1 (50 μs)
Information:
The latch and comparator must not have the same event number!
CfO_Counter1event1config 0x900D, 0xA00D or 0x9007, 0xA007 Configuration of the comparator for the second counter event
CfO_Counter1event1mode 0x03 Mode of the second counter event function - Continuous
CfO_DIREKTIOoutevent0IDwr 0x0861 TRUE event output of the second counter to trigger the direct output function
(set outputs).
CfO_DIREKTIOoutsetmask0 0x08, 0x20, 0x80 Outputs that should be set when comparator condition = TRUE
CfO_DIREKTIOoutevent1IDwr 0x0860 FALSE event output of the second counter to trigger the direct output function
(reset outputs).
CfO_DIREKTIOoutclearmask1 0x08, 0x20, 0x80 Outputs that should be reset when comparator condition = FALSE
The following table shows how the module's various event functions can be linked in order to configure an event
counter.
[x] stands for the respective counter function, either 1 or 2
Register Value Comment
For event counters on channels 1 and 3
CfO_Counter[x]configReg0 0x01 or 0x03 Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.14.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
CfO_Counter[x]event0mode 0x43 Mode of the first counter event function and referencing configuration
CfO_Counter[x]event0IDwr (any) Number of the event that should trigger referencing
For event counters on channels 2 and 4
CfO_Counter[x]configReg1 0x04 or 0x08 Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.14.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
CfO_Counter[x]event1mode 0x83 Mode of the second counter event function and referencing configuration
CfO_Counter[x]event1IDwr (any) Number of the event that should trigger referencing
Each of the 2 counter functions has 2 counter event functions. These consist of:
• Event ID that triggers the counter event function
• A window comparator
• Latch register for saving the counter value
When the counter event function is complete, a combined event ID in the range 2112 to 2401 (see 4.11.14.12.5.1
"List of event IDs") is sent.
Each counter event function also has the option to copy the current counter value to the "HW reference counter"
when an event occurs (see 4.11.14.12.6.1 "Counter value calculation").
Event input
E
Latch True
True True
Hardware reference Hardware reference
Counter 1 = abs 1 Counter 1 = abs 1
True True
Hardware reference Hardware reference
Counter 2 = abs 2 Counter 2 = abs 2
E E
Event output Event output
True False
Name:
Counter function 1: CfO_Counter1config
Counter function 2: CfO_Counter2config
These registers are used to configure the mode of the counter function. Each counter function can be operated
in 3 different modes.
Counter function mode
Edge counters AB encoder Up/down counter
Counter channel 11) Counting pulses, edge counter 1 A Metering pulses
Counter channel 21) Counting pulses, edge counter 2 B Counting direction (0 =
positive, 1 = negative)
Counter register 1 Counter value 1 Position Counter value
Counter register 2 Counter value 2
1) Corresponds to the physical channels of the counter functions. See 4.11.14.7.1 "Description of channel assignments".
Bit structure:
Bit Description Value Information
0-1 Counter mode 00 Edge counters
01 AB encoder
11 Up/down counter
2-7 Reserved -
Name:
Counter function 1: CfO_Counter1configReg0 to CfO_Counter2configReg0
Counter function 2: CfO_Counter1configReg1 to CfO_Counter2configReg1
The calculation of the internal "counter1" and "counter2" registers can be configured in these registers. For infor-
mation on using these internal registers, see 4.11.14.12.6.1 "Counter value calculation".
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 counter 1 - use 0 0 is added instead of "counter 1"
1 "counter 1" is used for addition
1 counter 1 - sign 0 The sign of the "counter 1" register is not changed for addition
1 The sign of the "counter 1" register is reversed for addition
2 counter 2 - use 0 0 is added instead of "counter 2"
1 "counter 2" is used for addition
3 counter 2 - sign 0 The sign of the "counter 2" register is not changed for addition
1 The sign of the "counter 2" register is reversed for addition
4-7 Reserved -
Name:
Counter function 1: CfO_Counter1PresetValue1 to CfO_Counter2PresetValue1
Counter function 1: CfO_Counter1PresetValue1_32Bit to CfO_Counter2PresetValue1_32Bit
Counter function 2: CfO_Counter1PresetValue2 to CfO_Counter1PresetValue2
Counter function 2: CfO_Counter1PresetValue2_32Bit to CfO_Counter1PresetValue2_32Bit
"Preset value" in the AS I/O configuration.
These registers can be used to define an offset value for referencing. This value is copied to the internal
SW_reference_counter register of the respective counter register.
Data type Value
INT -32,768 to 32,767
DINT -2,147,483,648 to 2,147,483,647
Counter register
Name:
Different names are used for these 4 registers depending on their function.
These 4 registers show the results of the counter value calculation for the respective register. Depending on the
function, this corresponds to either the encoder position or the counter value.
For information on the relationship between physical channels and counter registers, see 4.11.14.12.6 "Counters
and encoders" and 4.11.14.7.1 "Description of channel assignments"
Counter function 1
Counter register Function Name
1 AB encoders ABEncoder01
ABR encoders ABREncoder01
Up/down counters Counter01
Event counters EventCounter01
2 Event counters EventCounter02
Counter function 2
Counter register Function Name
1 AB encoders ABEncoder02
Up/down counters Counter02
Event counters EventCounter03
2 Event counters EventCounter04
Name:
StatusABR01
The referencing status of the ABR encoder is shown in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Reserved 0
2 Bit is always 1 after the first reference pulse. 0 No reference pulses have occurred since the start of referenc-
ing.
1 The first reference pulse has occurred.
3 State change when referencing is complete 0 or 1
4 Bit is always 1 after the first reference pulse. 0 No reference pulses have occurred since the start of referenc-
ing.
1 The first reference pulse has occurred.
5-7 Continuous counter xxx Increased with each reference pulse
Name:
ReferenceModeABR01
The bits in this register are used to configure the reaction to the configured reference pulse.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Sets the referencing mode 00 Referencing OFF
01 Single shot referencing
10 Reserved
11 Continuous referencing
2-5 Reserved -
6-7 Reserved 11 Must always be 11!
The ABR and AB encoders and the up/down counter have a comparator function. It always works the same and
is described here globally for all three.
The comparators are implemented in software form. They do not work actively but rather passively, i.e. the com-
parison is only carried out when an event is received. The event received is forwarded along the TRUE or FALSE
branch depending on the status of the comparator condition. An event function like this generally also offers a latch
for the TRUE and FALSE branch to save the value used for the comparator at the time of the event.
Comparator modes
Name:
Counter function 1: CfO_Counter1event0config to CfO_Counter1event1config
Counter function 2: CfO_Counter2event0config to CfO_Counter2event1config
These registers are used to configure the counter event function for the respective counter function.
Bits 0 to 3 configure the calculation of the comparison or to latch the value. This calculation is similar to the calcu-
lation of the counter register (see 4.11.14.12.6.1 "Counter value calculation")
Bits 8 to 13 can be used to limit the number of bits used for the comparison. A mask is calculated as 2n - 1 and
linked with an "AND" operation. This makes it possible to generate a comparator pulse every 2n increments.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0 counter 1 - use 0 0 is added instead of "counter 1"
1 "counter 1" is used for addition
1 counter 1 - sign 0 The sign of the "counter 1" register is not changed for addition
1 The sign of the "counter 1" register is reversed for addition
2 counter 2 - use 0 0 is added instead of "counter 2"
1 "counter 2" is used for addition
3 counter 1 - sign 0 The sign of the "counter 2" register is not changed for addition
1 The sign of the "counter 2" register is reversed for addition
4-7 Reserved -
8 - 13 Number of bits for comparator mask x The mask value is calculated as 2n-1, where n is value set in
these bits. Default: 0
14 Reserved -
15 Margin comparator mode 0 MarginComparator01 >= (Current position - OriginCompara-
tor01)
1 MarginComparator01 > (Current position - OriginComparator01)
Name:
Counter function 1: CfO_Counter1event0mode to CfO_Counter1event1mode
Counter function 2: CfO_Counter2event0mode to CfO_Counter2event1mode
In these registers you can set the mode for the comparator function and optional copying of the latched registers.
Comparator functions can be operated in 4 different modes. For a description, see "Comparator modes".
Bits 4 to 7 can be used to define hardware referencing actions.
Based on these bits, the values of the internal absolute value counters "abs1" and "abs2" can be copied to the re-
spective "HW_reference_counter" register at every counter event (see 4.11.14.12.6.1 "Counter value calculation").
This function can be used to reference the counter values directly in the hardware.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Comparator mode 0 Off
1 Single
2 State change
3 Continuous
2-3 Reserved -
4 Copy abs1 counter value 0 No action
1 When event is FALSE → hardware reference counter 1 = abs1
5 Copy abs2 counter value 0 No action
1 When event is FALSE → hardware reference counter 2 = abs2
6 Copy abs1 counter value 0 No action
1 When event is TRUE → hardware reference counter 1 = abs1
7 Copy abs2 counter value 0 No action
1 When event is TRUE → hardware reference counter 2 = abs2
Comparator origin
Name:
OriginComparator01
This register is available for the AB and ABR encoders and the up/down counters.
It defines the position value at which the respective configured comparator output channel is set.
Data type Value Information
INT -32,768 to 32,767 Comparator window origin, 16-bit
DINT -2,147,483,648 Comparator window origin, 32-bit
to 2,147,483,647
Name:
MarginComparator01
This register is available for the AB and ABR encoders and the up/down counters.
It defines the width of the comparator window in the positive direction.
Data type Value Information
INT -32,768 to 32,767 Width of comparator window, 16-bit
DINT -2,147,483,648 to 2,147,483,647 Width of comparator window, 32-bit
Name:
Different names are used for these 4 registers depending on their function.
If the comparator returns "TRUE", then the current counter value is latched and copied to these registers. The
calculation of the comparator value used for the latch can be configured in the "Configure calculation of comparator"
register.
Counter function 1
Event function Function Name
1 AB encoders Latch01AB01
Up/down counters Latch01Counter01
2 ABR encoders Latch01ABR01
AB encoders Latch02AB01
Up/down counters Latch02Counter01
Counter function 2
Event function Function Name
1 AB encoders Latch01AB02
Up/down counters Latch01Counter02
Event counters Latch02AB02
2 Event counters Latch02Counter02
The module has 1 SSI encoders available, supported directly in the hardware. Two 24 V output channels are set
for the SSI encoder and cannot be changed. (See also 4.11.14.7.1 "Description of channel assignments")
When using the SSI encoder, the corresponding clock channel can be configured in the 4.11.14.12.4.1
"CfO_CFGchannel" register as "Channel-specific" and "Push/Pull".
SSI encoders Channel number
Data channel 1
Clock channel 2
The SSI encoder consists of an event function and an event input. The SSI cycle is started when an event is
received on this input.
Information:
The SSI event function is not linked to an event by default, i.e. SSI functions are disabled.
Two events are sent from the SSI encoder interface..
• An "SSI valid" event is triggered immediately after the end of the SSI cycle if a new counter value is available.
• The "SSI ready" event then shows when the monoflop time has expired (tp in SSI encoder timing diagram).
This is the earliest that the next SSI cycle can be started.
SSI encoder - Timing diagram
SSI cycle
Clock 1 2 3 4 5 6 n
Data
SSI valid
SSI start event SSI ready
Name:
CfO_SSI1eventIDwr
This register holds the event ID that should start the SSI cycle. For a list of all possible event IDs, see 4.11.14.12.5.1
"List of event IDs"
Normally this register is set to network event 225 "AOSISOP"- This ensures that the new encoder position is
available at the next "I/O → Synchronous Frame" transfer. Check the SSI transfer time and the X2X cycle time,
because the SSI cycle must be completed within this time.
Data type Value Information
INT 192 to 7,233 ID of event function
Configure SSI
Name:
CfO_SSI1cfg
This configuration register is used to set the coding, the clock rate and the number of bits. Default = 0. This must
be set once using an acyclic write command.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 00 1 MHz
01 500 kHz
10 250 kHz
11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
Name:
ConfigAdvanced
This configuration register is used to set the coding, the clock rate, the number of bits and the monostable multivi-
brator settings. Default = 0. This must be set once using an acyclic write command.
It only differs from "CfO_SSI1cfg" by data length and additional monostable multivibrator testing.
Data type Value
UDINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 00 1 MHz
01 500 kHz
10 250 kHz
11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
16 - 17 Monostable multivibrator check 00 Check OFF, no additional clock bit
01 Check set to High level
10 Check set to Low level
11 Level is clocked but ignored
18 - 31 Reserved 0
Name:
CfO_SSI1control
The two SSI encoder events can be enabled/disabled using this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Event: SSI valid 0 Not sent
1 Sent
1 Event: SSI ready 0 Not sent
1 Sent
2-7 Reserved -
Name:
SSIEncoder01
The last transferred SSI position can be read out from this register. The SSI encoder value is displayed as a 32-
bit position value. This position value is generated synchronously with the X2X cycle.
Data type Value Information
UDINT 0 to 4,294,967,295 Last SSI position transferred
The module has an assigned comparator function for the SSI function. These consist of:
• Event ID that triggers the comparator function
• The window comparator
• Latch register for saving the counter value
When the comparator function is complete, event ID 7232 or 7233 (see 4.11.14.12.5.1 "List of event IDs") is sent.
Name:
CfO_SSI1event0IDwr
This register holds the event ID that should start the SSI comparator function. For a list of all possible event IDs,
see 4.11.14.12.5.1 "List of event IDs"
Data type Value Information
INT 192 to 7,233 ID of comparator function
Name:
CfO_SSI1event0mode
This register can be used to configure the mode of the comparator function.
Comparator functions can be operated in 4 different modes. For a description, see "Comparator modes".
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Comparator mode 0 Off
1 Single
2 State change
3 Continuous
2-7 Reserved -
Name:
CfO_SSI1event0config
The calculation of the position value used for the comparator can be configured in this register.
The window comparator condition is calculated as follows:
counter_window_value = ssi_counter & (2^ssi_data_bits - 1)
diff = counter_window_value – origin_comparator
if ((diff & (2^(comparator_mask)-1)) <= margin_comparator)
condition = True;
else
condition = False;
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-5 SSI data bits x Number of data bits used for masking
6-7 Reserved -
8 - 13 Comparator mask x The mask value is calculated from 2n-1, where n is the value
configured in SSI data bits. Default: 0
14 Comparator mode 0 MarginComparator >= SSI position - OriginComparator
1 MarginComparator > SSI position - OriginComparator
Name:
OriginComparator01_SSI
This register contains the origin of the window comparator.
Data type Value Information
UDINT 0 to 4,294,967,295 Origin of the window comparator.
Name:
MarginComparator01_SSI
This register provides the width of the window comparator.
Data type Value Information
UDINT 0 to 4,294,967,295 Width of the SSI window comparator
Name:
Latch01SSI01
If the SSI window comparator returns "True", then the current SSI position is latched and saved in this register.
Data type Value Information
UDINT 0 to 4,294,967,295 Latched SSI position
The module has 2 PWM functions available, supported directly by the hardware. A 24 V output channel is set for
each PWM encoder and cannot be changed. (See also 4.11.14.7.1 "Description of channel assignments")
When using the PWM function, the corresponding channel can be configured in the 4.11.14.12.4.1
"CfO_CFGchannel" register as "Channel-specific".
PWM function Channel
PWM1 2
PWM2 4
Name:
CfO_PWM0prescaler to CfO_PWM1prescaler
The length of the PWM cycle is configured using this register. The base is a 48 MHz clock, which can be changed
(divided) using the setting in this register. One PWM cycle consists of 1,000 of the resulting clocks after they have
been divided. The period length of the PWM cycle is calculated as follows:
prescale
PWM_cycle = 1000 [s]
48,000,000
Data type Value Information
UINT 2 to 65,535 Prescaler for PWM cycle
Name:
PWMOutput02 and PWMOutput04
In this register, a configuration is made for the percentage of the PWM cycle (in 1/10 % steps) that the PWM output
is logical 1, i.e. ON.
Data type Value Information
UINT 0 to 1,000 PWM output always off
2 to 999 Turn on time in 1/10% steps
1,000 PWM output always on
The module has a time measurement function for each I/O channel. It can be configured separately for rising and
falling edges on each channel.
A starting edge can be configured for each time measurement function. When a configured starting edge occurs,
the value of the internal timer is saved in a FIFO. This FIFO holds up to 16 elements. When the actual trigger edge
occurs, the difference in time between the starting edge and the triggered edge is copied to the respective register.
Bits 8 to 11 "Previous start edge" of the 4.11.14.12.9.2 "CfO_EdgeTimeFallingMode" and 4.11.14.12.9.3
"CfO_EdgeTimeRisingMode" registers can be used to define which detected starting edge from the FIFO should
be used to calculate the difference. Additionally, when the trigger edge occurs, the counter clocked internally us-
ing bits 12 to 15 "Time measurement resolution are copied to the 4.11.14.12.9.10 "TimeStampFallingCH" and
4.11.14.12.9.11 "TimeStampRisingCH" registers.
Information:
The time measurement function is an extension of edge detection, so all of the channels used must
be configured there.
Name:
CfO_EdgeTimeglobalenable
This register enables/disables the time measurement function for the entire module.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Time measurement function 0 Disabled for entire module
1 Enabled for entire module
1-7 Reserved -
Name:
CfO_EdgeTimeFallingMode01 to CfO_EdgeTimeFallingMode04
These registers can be used to configure the time measurement function for the falling edge of the respective
channel.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Selects the channel for the starting edge 0 Channel 1
...
3 Channel 4
4 Selects the edge for the starting edge 0 The falling edge of the channel configured in bits 0 to 3 serves
as the starting edge.
1 The rising edge of the channel configured in bits 0 to 3 serves
as the starting edge.
5-6 Reserved -
7 Trigger 0 Triggered1)
1 Continuous2)
8 - 11 Previous start edge 0 to 15 The value determines which entry in the starting edge FIFO
should be used to calculate the time difference.
12 - 15 Time measurement resolution 0 8 Mhz
1 4 Mhz
2 2 Mhz
3 1 Mhz
4 500 kHz
5 250 kHz
6 125 kHz
7 625 kHz
1) The time measurement is triggered by the corresponding bit in the 4.11.14.12.9.5 "TriggerRisingCH" register.
2) Time measurement runs continuously and is triggered at every edge.
Name:
CfO_EdgeTimeRisingMode01 to CfO_EdgeTimeRisingMode04
These registers can be used to configure the time measurement function for the rising edge of the respective
channel.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Selects the channel for the starting edge 0 Channel 1
...
3 Channel 4
4 Selects the edge for the starting edge 0 The falling edge of the channel configured in bits 0 to 3 serves
as the starting edge.
1 The rising edge of the channel configured in bits 0 to 3 serves
as the starting edge.
5-6 Reserved -
7 Trigger 0 Triggered1)
1 Continuous2)
8 - 11 Previous start edge 0 to 15 The value determines which entry in the starting edge FIFO
should be used to calculate the time difference.
12 - 15 Time measurement resolution 0 8 Mhz
1 4 Mhz
2 2 Mhz
3 1 Mhz
4 500 kHz
5 250 kHz
6 125 kHz
7 625 kHz
1) The time measurement is triggered by the corresponding bit in the 4.11.14.12.9.4 "TriggerRisingCH" register.
2) Time measurement runs continuously and is triggered at every edge.
Name:
TriggerFallingCH01 to TriggerFallingCH04
If bit 7 "Trigger" is cleared in the 4.11.14.12.9.2 "CfO_EdgeTimeFallingMode" register, then detection of a falling
edge on the respective input can be triggered using the respective bit in this register. After a bit has been set, the
next falling edge on the corresponding channel is detected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 TriggerFallingCH01 0 Falling edges on channel 1 are not detected
1 The next falling edge on channel 1 will be detected
... ...
3 TriggerFallingCH04 0 Falling edges on channel 4 are not detected
1 The next falling edge on channel 4 will be detected
4-7 Reserved -
Name:
TriggerRisingCH01 to TriggerRisingCH04
If bit 7 "Trigger" is cleared in the 4.11.14.12.9.3 "CfO_EdgeTimeRisingMode" register, then detection of a rising
edge on the respective input can be triggered using the respective bit in this register. After a bit has been set, the
next rising edge on the corresponding channel is detected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 TriggerRisingCH01 0 Rising edges on channel 1 are not detected
1 The next rising edge on channel 1 will be detected
... ...
3 TriggerRisingCH04 0 Rising edges on channel 4 are not detected
1 The next rising edge on channel 4 will be detected
4-7 Reserved -
Name:
BusyTriggerFallingCH01 to BusyTriggerFallingCH04
If edges are triggered via the bits in the 4.11.14.12.9.4 "TriggerFallingCH" register, then a set bit in this register
indicates that no falling edges have been detected on the respective channel since the corresponding bit was
set in the "TriggerFallingCH" register. If a falling edge occurs on the respective channel, then the corresponding
BusyTriggerFalling bit is cleared.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 BusyTriggerFallingCH01 0 Falling edge detected on channel 1
1 Module waiting for a falling edge on channel 1
... ...
3 BusyTriggerFallingCH04 0 Falling edge detected on channel 4
1 Module waiting for a falling edge on channel 4
4-7 Reserved -
Name:
BusyTriggerRisingCH01 to BusyTriggerRisingCH04
If edges are triggered via the bits in the 4.11.14.12.9.5 "TriggerRisingCH" register, then a set bit in this register
indicates that no rising edges have been detected on the respective channel since the corresponding bit was
set in the "TriggerRisingCH" register. If a rising edge occurs on the respective channel, then the corresponding
BusyTriggerRising bit is cleared.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 BusyTriggerRisingCH01 0 Rising edge detected on channel 1
1 Module waiting for a rising edge on channel 1
... ...
3 BusyTriggerRisingCH04 0 Rising edge detected on channel 4
1 Module waiting for a rising edge on channel 4
4-7 Reserved -
Name:
CountFallingCH01 to CountFallingCH04
These registers contain cyclic counters that are incremented with every detected falling edge on the respective
channel.
Data type Value Information
USINT 0 to 255 Counter for falling edges
Name:
CountRisingCH01 to CountRisingCH04
These registers contain cyclic counters that are incremented with every detected rising edge on the respective
channel.
Data type Value Information
USINT 0 to 255 Counter for rising edges
Name:
TimeStampFallingCH01 to TimeStampFallingCH04
When a falling edge occurs on the respective channel, the current counter value of the module timer is copied
to these registers.
Data type Value Information
UINT 0 to 65,535 Time stamp for rising edges
Name:
TimeStampRisingCH01 to TimeStampRisingCH04
When a rising edge occurs on the respective channel, the current counter value of the module timer is copied to
these registers.
Data type Value Information
UINT 0 to 65,535 Time stamp for rising edges
Name:
TimeDiffFallingCH01 to TimeDiffFallingCH04
When a falling edge occurs on the respective channel, the time difference compared to the starting edge configured
in bit 4 of the 4.11.14.12.9.2 "CfO_EdgeTimeFallingMode" register is copied to this register.
Data type Value Information
UINT 0 to 65,535 Time difference from starting edge
Name:
TimeDiffRisingCH01 to TimeDiffRisingCH04
When a rising edge occurs on the respective channel, the time difference compared to the starting edge configured
in bit 4 of the 4.11.14.12.9.3 "CfO_EdgeTimeRisingMode" register is copied to this register.
Data type Value Information
UINT 0 to 65,535 Time difference from starting edge
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
4.11.15 X20DC2396
The module is equipped with two inputs for an ABR incremental encoder with 24 V encoder signal.
• 2 ABR incremental encoder 24 V
• 2 additional inputs e.g. for home enable switch
• 24 VDC and GND for encoder supply
Product ID X20DC2396
Brief description
I/O module 2 ABR incremental encoder 24 V
General information
Input voltage 24 VDC -15% / +20%
B&R ID code 0x1BAB
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Encoder - Bus Yes
Encoder - Encoder No
Reference enable switch - Bus Yes
Reference enable switch - Encoder No
Reference switch - Reference switch No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Home enable switch
Quantity 2
Nominal voltage 24 VDC
Input filter
Hardware ≤2 μs
Software -
Connection type 3-wire connections
Input circuit Sink
Input current at 24 VDC Approx. 3.3 mA
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
A1, A2 Green Input state of counter input A1 or A2
B1, B2 Green Input state of counter input B1 or B2
R1, R2 Green Input state of reference pulse R1 or R2
1-2 Green Input state of the corresponding digital input
4.11.15.5 Pinout
r e
X20 DC 2396
A1 A2
B1 B2
R1 R2
1 2
A1 A2
B1 B2
R1 R2
DI 1 DI 2
Encoder 1 24 V+ Encoder 2 24 V+
GND GND
DC
A1 A2
Counter 1
Counter 2
B1 B2
R1 R2
Counter inputs
ABR x
VDR
Input status
I/O status
24 V
PTC
Encoder x 24 V LED (green)
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
The difference between function model 0 and function model 1 is the size of the data type for some registers.
• Function model 0 uses data type INT
• Function model 1 uses data type DINT (specified in parentheses)
Register Name Data type Read Write
Cyclic Acyclic Cyclic Acyclic
Configuration
4104 CfO_EdgeDetectFalling USINT ●
4106 CfO_EdgeDetectRising USINT ●
2064 CfO_PresetABR01_1(_32Bit) (D)INT ●
2068 CfO_PresetABR01_2(_32Bit) (D)INT ●
2576 CfO_PresetABR02_1(_32Bit) (D)INT ●
2580 CfO_PresetABR02_2(_32Bit) (D)INT ●
512 ConfigOutput24 UINT ●
522 ConfigOutput26 USINT ●
520 ConfigOutput27 USINT ●
544 ConfigOutput32 UINT ●
554 ConfigOutput34 USINT ●
552 ConfigOutput35 USINT ●
Communication
2116 ReferenceModeEncoder01 USINT ●
2628 ReferenceModeEncoder02 USINT ●
2080 Encoder01 (D)INT ●
2592 Encoder02 (D)INT ●
264 Input state of digital inputs 1 to 2 USINT ●
DigitalInput01 Bit 3
DigitalInput02 Bit 7
2118 StatusInput01 USINT ●
2630 StatusInput02 USINT ●
40 Status of encoder supply USINT ●
PowerSupply01 Bit 0
1) The offset specifies the position of the register within the CAN object.
The following registers must be configured by a single acyclic write with the listed values so that the homing
procedure is completed on the edge of the reference pulse.
The homing procedure can take place on:
• Rising edge
• Falling edge (default configuration)
Name:
CfO_EdgeDetectFalling
Data type Value Filter
USINT 0x00 Configuration value for rising edge
0x04 Encoder 1 - Configuration value for falling edge
0x40 Encoder 2 - Configuration value for falling edge
0x44 Encoders 1 and 2 - Configuration value for falling edge
Name:
CfO_EdgeDetectRising
Data type Value Filter
USINT 0x00 Configuration value for falling edge (default 0x00)
0x04 Encoder 1 - Configuration value for rising edge
0x40 Encoder 2 - Configuration value for rising edge
0x44 Encoders 1 and 2 - Configuration value for rising edge
Name:
ConfigOutput24
This register contains the value for ABR encoder 1.
Data type Value Filter
UINT 0x1012 Configuration value for rising edge
0x1002 Configuration value for falling edge
Name:
ConfigOutput32
This register contains the value for ABR encoder 2.
Data type Value Filter
UINT 0x1016 Configuration value for rising edge
0x1006 Configuration value for falling edge
Name:
CfO_PresetABR01_1 to CfO_PresetABR01_2
CfO_PresetABR02_1 to CfO_PresetABR02_2
CfO_PresetABR01_1_32Bit to CfO_PresetABR01_2_32Bit
CfO_PresetABR02_1_32Bit to CfO_PresetABR02_2_32Bit (only in function model 1)
It is possible to specify two home positions for each encoder with these registers through a one-off acyclic write, for
example (default = 0). The configured values are applied to the counter values after a completed homing procedure.
Data type Value
INT -32,768 to 32,767
DINT1) -2,147,483,648 to 2,147,483,647
Regardless of the referencing mode, it is possible using this register to prevent the home position from being
applied when the corresponding reference input voltage level occurs (see 4.11.15.8.4.2 "Input state of digital inputs
1 to 2": bit 7). The desired setting can be configured by a one-off acyclic write.
Name:
ConfigOutput26
The voltage level of the digital input 1 to activate reference enable is configured with this register.
Data type Value Filter
USINT 0x00 Reference enable is active at 0 VDC
0x08 Reference enable is active at 24 VDC
Name:
ConfigOutput27
This register can be used to define whether the reference enable is activated.
Data type Value Filter
USINT 0x00 Reference enable input OFF (default)
0x08 Reference enable input activated
Name:
ConfigOutput34
The voltage level of the digital input 2 to activate reference enable is configured with this register.
Data type Value Filter
USINT 0x00 Reference enable is active at 0 VDC
0x80 Reference enable is active at 24 VDC
Name:
ConfigOutput35
This register can be used to define whether the reference enable is activated.
Data type Value Filter
USINT 0x00 Reference enable input OFF (default)
0x80 Reference enable input activated
Name:
Encoder01 to Encoder02
The encoder values are displayed in this register.
Data type Value
INT -32,768 to 32,767
DINT1) -2,147,483,648 to 2,147,483,647
Name:
DigitalInput01 to DigitalInput02.
This register displays the input status of the encoders and the digital inputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Encoder 1 0 or 1 Input state - Signal A
1 0 or 1 Input state - Signal B
2 0 or 1 Input state of reference pulse
3 DigitalInput01 0 or 1 Input state - Digital input 1
4 Encoder 2 0 or 1 Input state - Signal A
5 0 or 1 Input state - Signal B
6 0 or 1 Input state of reference pulse
7 DigitalInput02 0 or 1 Input state - Digital input 2
Name:
ReferenceModeEncoder01 to ReferenceModeEncoder02
This register determines the referencing mode.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-1 00 Referencing OFF
01 Single shot referencing
11 Continuous referencing
2-5 0 Bits permanently set = 0
6-7 00 Referencing OFF
11 Bits permanently set = 1
Name:
StatusInput01 (for encoder 1) to StatusInput02 (for encoder 2)
This register contains information regarding whether the referencing process is off, active or complete.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Reference pulse without homing1) 0 No reference impulse without homing has occurred yet
1 At least a reference impulse without homing has occurred
1 State change 0 or 1 Changes with each reference pulse without homing
2 Reference pulse with homing1) 0 No homing has occurred yet
1 At least one homing procedure has occurred
3 State change 0 or 1 Changes with each homing procedure that has taken place
4 Reference pulse 0 The last reference pulse didn't bring about a homing procedure
1 The last reference pulse brought about a homing procedure
5-7 Counter x Free-running counter, increased with each reference pulse
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
4.11.16 X20DC2398
This module is equipped with two inputs for SSI absolute encoders with 24 V encoder signal.
• 2 SSI absolute encoder 24 V
• 2 additional inputs
• 24 VDC and GND for encoder supply
Product ID X20DC2398
Brief description
I/O module 2 SSI absolute encoder 24 V
General information
Input voltage 24 VDC -15% / +20%
B&R ID code 0x1BAD
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.4 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Encoder - Bus Yes
Encoder - Encoder No
Channel - Bus Yes
Channel - Encoder No
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Quantity 2
Nominal voltage 24 VDC
Input current at 24 VDC Approx. 3.3 mA
Input filter
Hardware ≥2 µs
Software -
Connection type 3-wire connections
Input circuit Sink
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
D1, D2 Green Input state of data signal 1 or 2
1-2 Green Input state of the corresponding digital input
4.11.16.5 Pinout
r e
X20 DC 2398
D1 D2
1 2
Data 1 Data 2
Clock 1 Clock 2
DI 1 DI 2
Encoder 1 24 V+ Encoder 2 24 V+
GND GND
DC
Data 1 Data 2
Counter 1
Counter 2
Clock 1 Clock 2
Counter inputs
Data x
VDR
Input status
I/O status
24 V
PTC
Encoder x 24 V LED (green)
GND
GND
Standard inputs
Input x
VDR
Input status
I/O status
Led (green)
24 V
PTC
Clock x
VDR
Output status Pull
GND
1) The offset specifies the position of the register within the CAN object.
Name:
ConfigOutput15 to ConfigOutput 16
This configuration register is used to set the coding, the clock rate and the number of bits. Default = 0. This must
be set once using an acyclic write command.
"ConfigOutput15": Configuration register for SSI encoder01 and
"ConfigOutput16": Configuration register for SSI encoder02
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits
6-7 Clock rate 11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
Name:
ConfigAdvanced01 to ConfigAdvanced02
This configuration register is used to set the coding, the clock rate, the number of bits and the monostable multivi-
brator settings. Default = 0. This must be set once using an acyclic write command.
It only differs from register ConfigOutput15 + 16 by data length and additional monostable multivibrator testing.
"ConfigAdvanced01": Configuration register for SSI encoder01 and
"ConfigAdvanced02": Configuration register for SSI encoder02
Data type Value
UDINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
16 - 17 Monostable multivibrator 00 Check OFF, no additional clock bit
01 Check set to High level
10 Check set to Low level
11 Level is clocked but ignored
18 - 31 Reserved 0
Clock
Name:
Encoder01 to Encoder02
The two SSI encoder values are displayed as 32-bit position values. The SSI position values are generated syn-
chronously with the X2X cycle.
Data type Value Filter
UDINT 0 to 4,294,967,729 SSI position
Name:
DigitalInput01 to DigitalInput02
This register is used to indicate the input state of digital inputs 1 to 2.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
3 DigitalInput01 0 or 1 Input state - Digital input 1
7 DigitalInput02 0 or 1 Input state - Digital input 2
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
4.11.17 X20DC4395
This module is a multifunctional counter module. It can be connected to two SSI encoders, two ABR encoders,
four AB encoders or eight event counters. Four outputs are available for pulse width modulation. The functions
can also be mixed.
• 24 VDC encoder inputs
• SSI, ABR, AB or event counters for inputs
• Pulse width modulation for outputs
• 24 VDC and GND for encoder supply
Information:
This module is a multifunctional module. Some bus controllers only support the default function model.
Default function model:
• 1x ABR incremental encoder (24 V)
• 1x SSI absolute encoder (24 V)
• 1x event counter (24 V)
• 2x PWM output (24 V)
Product ID X20DC4395
Short description
I/O module 2 SSI absolute encoder, 24 V, 2 ABR incremental encoder, 24 V, 4 AB incremental encoders,
24 V, 8x event counters or 4x pulse width modulation, time measurement, relative timestamp
General information
Input voltage 24 VDC -15% / +20%
B&R ID code 0x1CC5
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using the status LED and software (output error status)
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Output - Output No
Output - Bus Yes
Output - Encoder No
Encoder - Bus Yes
Encoder - Encoder No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Incremental encoder
Quantity 4
Encoder inputs 24 V, asymmetrical
Counter size 16/32-bit
Input frequency Max. 100 kHz
Evaluation 4x
Encoder supply Module-internal, max. 600 mA
Overload behavior of the encoder supply Short circuit protection, overload protection
SSI absolute encoder
Quantity 2
Encoder inputs 24 V, asymmetrical
Counter size 32-bit
Max. transfer rate 125 kbit/s
Encoder supply Module-internal, max. 600 mA
Keying Gray/Binary
CLK: Output current Max. 100 mA
Overload behavior of the encoder supply Short circuit protection, overload protection
Event counter
Quantity 8
Nominal voltage 24 VDC
Signal form Square wave pulse
Evaluation Each edge, cyclic counter
Input frequency Max. 100 kHz
Input current at 24 VDC Approx. 1.3 mA
Input resistance 18.4 kΩ
Isolation voltage between channel and bus 500 Veff
Counter frequency 200 kHz
Counter size 16/32-bit
Input filter
Hardware ≥2 µs
Software -
Switching threshold
Low <5 VDC
High >15 VDC
Time measurement
Possible measurements Gate time, period duration, edge offset for various channels
Measurements per module Up to 9
Measurements per channel Up to 2
Counter size 16-bit
Counter frequency
Internal 8 MHz, 4 MHz, 2 MHz, 1 MHz, 500 kHz, 250 kHz, 125 kHz, 62.5 kHz
Signal form Square wave pulse
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
1-8 Green Status of the corresponding digital signal
4.11.17.5 Pinout
r e
X20 DC 4395
1 5
2 6
3 7
4 8
Channel 1 Channel 5
Channel 2 Channel 6
Channel 3 Channel 7
Channel 4 Channel 8
Encoder 1 24 V+ Encoder 2 24 V+
GND GND
DC
Data Data
Cycle Cycle
Counter 1
Counter 2
A A
B B
R R
PWM PWM
The following functions can be configured on the module. They cannot all be used at the same time due to the
multiple use of the hardware channels and the limited cyclic data length.
• 8 digital channels, 4 of which can be configured as outputs
• 8 event counters with configurable counting direction and optional referencing via digital input
• 4 PWM outputs
• 4 up/down counters, each with optional latch inputs and comparator output
• 4 AB counters, each with optional latch inputs and comparator output
• 2 ABR encoder with configurable reference pulse edge and reference position, optional reference enable
input, latch input and comparator output
• 2 SSI counter with optional latch input and comparator output
• 2 edge-triggered time measurement functions with configurable start edge based on current configuration
settings
The functions listed here are directly assigned to the respective hardware channels and cannot be changed:
Channel Signal connections
1 • Digital input 1
• Event counter 1
• AB encoder 1 - signal line A
• Up/down counter 1 - frequency
• SSI encoder 1 - data line
• ABR encoder 1 - signal line A
2 • Digital input 2
• Digital output 2
• Event counter 2
• PWM output 2
• AB encoder 1 - signal line B
• Up/down counter 1 - direction
• SSI encoder 1 - clock line
• ABR encoder 1 - signal line B
3 • Digital input 3
• Event counter 3
• AB encoder 2 - signal line A
• Up/down counter 2 - frequency
• ABR encoder 1 - signal line R
4 • Digital input 4
• Digital output 4
• Event counter 4
• PWM output 4
• AB encoder 2 - signal line B
• Up/down counter 2 - direction
• ABR encoder 1 - reference enable input
5 • Digital input 5
• Event counter 5
• AB encoder 3 - signal line A
• Up/down counter 3 - frequency
• SSI encoder 2 - data line
• ABR encoder 2 - signal line A
6 • Digital input 6
• Digital output 6
• Event counter 6
• PWM output 6
• AB encoder 3 - signal line B
• Up/down counter 3 - direction
• SSI encoder 2 - clock line
• ABR encoder 2 - signal line B
7 • Digital input 7
• Event counter 7
• AB encoder 4 - signal line A
• Up/down counter 4 - frequency
• ABR encoder 2 - signal line R
8 • Digital input 8
• Digital output 8
• Event counter 8
• PWM output 8
• AB encoder 4 - signal line B
• Up/down counter 4 - direction
• ABR encoder 2 - reference enable input
Options available in addition to these basic functions, such as comparator outputs or latch inputs, can be configured
freely to unused input/output channels.
Input x
VDR
Input status
I/O status
24 V
PTC
Encoder 24 V LED (green)
GND
GND
24 V
PTC
Output x
VDR
Output status Pull
GND
Output
monitoring
100 H 10 H 1H
1000
0.1 H
Coil resistance
Coil inductance
[Ω]
0.01 H
240 Ω ≙ 100 mA
0.1 1 10 100 1000 10000
The outputs of the module can be operated as PWM outputs. The period duration is calculated using the following
formula:
n
Period duration = s
48000
A value of 2 to 65535 can be defined for n.
Example
n Period duration Frequency
2 416 μs 24 kHz
24000 500 ms 2 Hz
48000 1s 1 Hz
65535 1.36 s 0.73 Hz
Unlike the function models 0 and 1, this model only offers a selection of functions with a limited scope of config-
uration on the module.
The following functions are provided and can be run at the same time:
• SSI encoders
• ABR encoder with configurable reference pulse edge and reference position
• 1 event counter with configurable counting direction
• 2 PWM outputs
Register Offset1) Name Data type Read Write
Cyclic Acyclic Cyclic Acyclic
Module configuration - General
N*2-2 - CfO_CFGchannel0N (Index N = 1 to 8) USINT ●
N * 2 + 64 - CfO_LEDNsource (Index N = 0 to 7) USINT ●
Configuration - ABR encoder
512 - CfO_DIREKTIOevent0IDwr UINT ●
544 - CfO_DIREKTIOevent1IDwr UINT ●
2,560 - CfO_Counter3config USINT ●
2,568 - CfO_Counter3configReg0 USINT ●
2,570 - CfO_Counter3configReg1 USINT ●
2,576 - CfO_Counter3PresetValue1 UINT ●
2,580 CfO_Counter3PresetValue2 UINT ●
2,624 - CfO_Counter3event0IDwr UINT ●
2,632 - CfO_Counter3event0config UINT ●
2,628 - CfO_Counter3event0mode USINT ●
2,656 - CfO_Counter3event1IDwr UINT ●
2,664 - CfO_Counter3event1config UINT ●
2,660 - CfO_Counter3event1mode USINT ●
4,104 - CfO_EdgeDetectFalling USINT ●
4,106 - CfO_EdgeDetectRising USINT ●
Configuration - Event counter
2,304 - CfO_Counter2config USINT ●
2,312 - CfO_Counter2configReg0 USINT ●
2,314 - CfO_Counter2configReg1 USINT ●
2,368 - CfO_Counter2event0IDwr UINT ●
2,376 - CfO_Counter2event0config UINT ●
2,372 - CfO_Counter2event0mode USINT ●
2,400 - CfO_Counter2event1IDwr UINT ●
2,408 - CfO_Counter2event1config UINT ●
2,404 - CfO_Counter2event1mode USINT ●
Configuration - SSI encoder
7,176 - CfO_SSI1cfg UINT ●
7,180 - CfO_SSI1control USINT ●
7,168 - CfO_SSI1eventIDwr UINT ●
7,232 - CfO_SSI1event0IDwr UINT ●
7,240 - CfO_SSI1event0config UINT ●
7,236 - CfO_SSI1event0mode USINT ●
7,172 - ConfigAdvanced01 UDINT ●
Configuration - PWM (pulse width modulation)
6,160 - CfO_PWM1prescaler UINT ●
6,192 - CfO_PWM3prescaler UINT ●
Module communication - General
40 6 Status of encoder supply USINT ●
PowerSupply01 Bit 0
Communication - Counters and encoders
2,336 4 EventCounter03 UINT ●
2,592 8 ABREncoder02 INT ●
2,628 10 ReferenceModeABR02 USINT ●
2,630 10 StatusABR02 USINT ●
7,184 0 SSIEncoder01 UDINT ●
Communication - PWM (pulse width modulation)
6,162 0 PWMOutput04 UINT ●
6,194 8 PWMOutput08 UINT ●
1) The offset specifies the position of the register within the CAN object.
Name:
CfO_LED0source to CfO_LED7source
These registers can be used to define how the module's LED status indicators are used. Blinking patterns can be
generated from the application, and the status of the physical inputs and outputs can be indicated.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 MODE = 0 0 LED off
1 Blinking quickly
2 Blinking
3 Blinking slowly
4 Single flash
5 Double flash
6 to 15 Reserved
MODE = 1 (inverted) 0 LED on
1 Blinking quickly
2 Blinking
3 Blinking slowly
4 Single flash
5 Double flash
6 to 15 Reserved
MODE = 2 0 to 7 Number of the physical input channel
8 to 15 Reserved
MODE = 3 0 to 7 Number of the physical output channel
8 to 15 Reserved
4-7 Selection of the mode for the LED status indicator 0 LED blinking pattern
1 Inverted LED blinking pattern
2 Displays a channel's physical input status
3 Displays a channel's physical output status
4 to 15 Reserved
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
Name:
CfO_CFGchannel01 to CfO_CFGchannel08
This register can be used to configure physical I/O channels 1 to 8.
Information:
Except for bit 2 (inverted input), all other bits are only available for channels 2, 4, 6 and 8.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Push1) 0 Disabled
1 Enabled
1 Pull1) 0 Disabled
1 Enabled
2 Inverted input 0 Disabled
1 Enabled
3 Inverted output 0 Disabled
1 Enabled
4-7 Output type 0 Direct I/O
1 to 5 Reserved
6 PWM (channel-specific)
7 SSI clock (channel-specific)
Name:
CfO_OutClearMask
The settings in this register only affect the values written to registers 4.11.17.12.4.5 "DigitalOutput02 to 08".
• 0 allows manual reset of digital outputs using registers DigitalOutput02 to 08
• 1 prevents manual reset of digital outputs using registers DigitalOutput02 to 08
When "1" is used, the "output event function" can be used to reset the outputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 DigitalOutput02 0 Writing 0 to the DigitalOutput02 register resets the output
1 Writing 0 from the DigitalOutput02 register does not reset the
output
2 Reserved -
3 DigitalOutput04 0 Writing 0 to the DigitalOutput04 register resets the output
1 Writing 0 from the DigitalOutput04 register does not reset the
output
4 Reserved -
5 DigitalOutput06 0 Writing 0 to the DigitalOutput06 register resets the output
1 Writing 0 from the DigitalOutput06 register does not reset the
output
6 Reserved -
7 DigitalOutput08 0 Writing 0 to the DigitalOutput08 register resets the output
1 Writing 0 from the DigitalOutput08 register does not reset the
output
Name:
CfO_OutSetMask
The settings in this register only affect the values written to registers 4.11.17.12.4.5 "DigitalOutput02 to 08".
• 0 allows manual setting of digital outputs using registers DigitalOutput02 to 04
• 1 prevents manual setting of digital outputs using registers DigitalOutput02 to 04
When "1" is used, the "output event function" can be used to reset the outputs.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 DigitalOutput02 0 Writing 1 to the DigitalOutput02 register sets the output
1 Writing 1 from the DigitalOutput02 register does not set the out-
put
2 Reserved -
3 DigitalOutput04 0 Writing 1 to the DigitalOutput04 register sets the output
1 Writing 1 from the DigitalOutput04 register does not set the out-
put
4 Reserved -
5 DigitalOutput06 0 Writing 1 to the DigitalOutput06 register sets the output
1 Writing 1 from the DigitalOutput06 register does not set the out-
put
6 Reserved -
7 DigitalOutput08 0 Writing 1 to the DigitalOutput08 register sets the output
1 Writing 1 from the DigitalOutput08 register does not set the out-
put
Name:
see "Name in the AS I/O configuration"
This register reads the input status of a physical channel. The polarity settings are accounted for in the value (bit
2 in 4.11.17.12.4.1 "CfO_CFGchannel[x]" register).
The bits in this register are shown in the AS I/O mapping table under different names based on the function used
in order to improve readability.
Data type Value
USINT See bit structure.
Bit structure:
Bit Physical input channel Value Name in the AS I/O configuration
0 Channel 1 0 or 1 DigitalInput01
1 Channel 2 0 or 1 DigitalInput02
StatusDigitalOutput02
ComparatorActualValue02
ComparatorActualValue03
2 Channel 3 0 or 1 DigitalInput03
3 Channel 4 0 or 1 DigitalInput04
StatusDigitalOutput04
ReferenceEnableSwitch01
ComparatorActualValue01
ComparatorActualValue02
ComparatorActualValue03
4 Channel 5 0 or 1 DigitalInput05
5 Channel 6 0 or 1 DigitalInput06
StatusDigitalOutput06
ComparatorActualValue01
6 Channel 7 0 or 1 DigitalInput07
7 Channel 8 0 or 1 DigitalInput08
StatusDigitalOutput08
ReferenceEnableSwitch02
ComparatorActualValue01
ComparatorActualValue02
ComparatorActualValue03
Name:
DigitalOutput02 to DigitalOutput08
The output status of a physical channel can be written using this register. In order to configure a channel as an
output:
1 Bit 0 "Push" and/or bit 1 "Pull" must be enabled in the 4.11.17.12.4.1 "CfO_CFGchannel[x]" register.
2 Bits 4 to 7 in the 4.11.17.12.4.1 "CfO_CFGchannel[x]" register must be set to Direct I/O.
3 0 must be set for the respective channel in the 4.11.17.12.4.2 "CfO_OutClearMask" and 4.11.17.12.4.3
"CfO_OutSetMask" registers.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 DigitalOutput02 0 or 1 Output status of channel 2
2 Reserved -
3 DigitalOutput04 0 or 1 Output status of channel 4
4 Reserved -
5 DigitalOutput06 0 or 1 Output status of channel 6
6 Reserved -
7 DigitalOutput08 0 or 1 Output status of channel 8
The module provides configurable event functions. An event function can be connected to physical I/O and the
values derived from them (e.g. counters) or be purely used for internal processing.
Every event function has event inputs and outputs. Event functions can also have only inputs or only outputs. Each
event output has a unique event ID. It is possible to configure when an event should be generated on an event
output. The effect of an event is determined by the respective event function.
Event functions can also be linked to one another. The link takes place using the event input. Every event input
has a 16-bit register to which the event number of the linked event output is written.
Information:
The module functions that can be configured in the AS I/O configuration are primarily based on these
event functions and their links. Changes in the AS I/O configuration have multiple effects on event
functions and their links.
Various hardware and software functions send event IDs or require event IDs in order to start. The following table
shows all of the IDs available to configure the module.
Event ID Description
Direct event inputs
512 Comparator condition 1 FALSE
513 TRUE
544 Comparator condition 2 FALSE
545 TRUE
576 Comparator condition 3 FALSE
577 TRUE
608 Comparator condition 4 FALSE
609 TRUE
Counter comparator function
2,112 Counter function 1 Event function 1; FALSE
2,113 Event function 1; TRUE
2,144 Event function 2; FALSE
2,145 Event function 2; TRUE
2,368 Counter function 2 Event function 1; FALSE
2,369 Event function 1; TRUE
2,400 Event function 2; FALSE
2,401 Event function 2; TRUE
2,624 Counter function 3 Event function 1; FALSE
2,625 Event function 1; TRUE
2,656 Event function 2; FALSE
2,657 Event function 2; TRUE
2,880 Counter function 4 Event function 1; FALSE
2,881 Event function 1; TRUE
2,912 Event function 2; FALSE
2,913 Event function 2; TRUE
Edge events
4,096 Falling edge on I/O channel Channel 1
... ...
4,103 Channel 8
4,112 Rising edge on I/O channel Channel 1
... ...
4,119 Channel 8
4,128 Rising or falling edge on I/O channel Channel 1
... ...
4,135 Channel 8
SSI counter events
7,168 SSI 1 SSI valid
7,169 SSI ready
7,424 SSI 2 SSI valid
7,425 SSI ready
SSI comparator events
7,232 SSI 1 comparator condition FALSE
7,233 TRUE
7,488 SSI 2 comparator condition FALSE
7,489 TRUE
Timerevents
208 Timer1 50 μs
209 Timer2 100 μs
210 Timer3 200 μs
211 Timer4 400 μs
212 Timer5 800 μs
213 Timer6 1600 μs
214 Timer7 3200 μs
215 Timer8 3200 μs (time offset to timer 7)
Network functions
224 SOAISOP (synchronous out asynchronous in start of protocol)
225 AOSISOP (asynchronous out synchronous in start of protocol)
226 SOAIEOP (synchronous out asynchronous in end of protocol)
227 AOSIEOP (asynchronous out synchronous in end of protocol)
Idle event
192 No-load operation
Timer
There are 8 timer events that the module can generate.
Information:
The timers have the highest event priority. All other system functions are interrupted when a timer
event occurs, and jitter for the amount of time it takes to process the event.
Idle event
Idle time is the time that remains after the system has processed all higher priority events and operations. The
module performs the following functions during idle time:
• Handling of the asynchronous protocol
• Mechanism for (re-)linking events
• Operation of LEDs
• Execution of event event functions linked to the idle function
Information:
Edge detection can also be used for channels that are configured as outputs.
To stabilize the system, there is a mechanism that limits the number of events created through edge recognition.
At least one idle event must occur between two edge events for the same edge.
The "CfO_FallingDisProtection" and "CfO_RisingDisProtection" registers can be used to disable this limitation for
each edge, and then an event will be generated for every edge. However, this can cause a system overload, i.e.
I/O operation can fail for up to 100 ms before the module changes to the reset state.
Name:
CfO_EdgeDetectFalling
This register defines whether an event is generated on a falling edge.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 No event generated on falling edge.
1 Events 4096 and 4128 are generated on falling edge.
... ...
7 Channel 8 0 No event generated on falling edge.
1 Events 4103 and 4135 are generated on falling edge.
Name:
CfO_EdgeDetectRising
This register defines whether an event is generated on a rising edge.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 No event generated on rising edge.
1 Events 4112 and 4128 are generated on rising edge.
... ...
7 Channel 8 0 No event generated on rising edge.
1 Events 4119 and 4135 are generated on rising edge.
Name:
CfO_FallingDisProtection
This register can be used to enable/disable the event frequency limit for falling edges on the respective channel.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Event frequency limit enabled.
1 Event frequency limit disabled.
... ...
7 Channel 7 0 Event frequency limit enabled.
1 Event frequency limit disabled.
Name:
CfO_RisingDisProtection
This register can be used to enable/disable the event frequency limit for rising edges on the respective channel.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Event frequency limit enabled.
1 Event frequency limit disabled.
... ...
7 Channel 8 0 Event frequency limit enabled.
1 Event frequency limit disabled.
Name:
CfO_DIREKTIOevent0IDwr to CfO_DIREKTIOevent1IDwr
This register holds the event ID generated by the direct input function. For a list of all possible event IDs, see
4.11.17.12.5.1 "List of event IDs"
Data type Value Information
INT 192 to 7,289 ID of event function
Name:
CfO_DIREKTIOevent0mode to CfO_DIREKTIOevent1mode
The mode in which the direct input function operates can be set in this register.
Comparator functions can be operated in 4 different modes. For a description, see "Comparator modes".
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Comparator mode 0 Off
1 Single
2 State change
3 Continuous
2-7 Reserved -
Name:
CfO_DIREKTIOevent0compState to CfO_DIREKTIOevent1compState
This register contains the status bits that are compared with the bits specified in the "CfO_Ev0CompMask" register,
which contain the I/O input status, when an event is received.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Comparator status of channel 1 0 or 1
... ...
7 Comparator status of channel 8 0 or 1
Name:
CfO_Ev0CompMask to CfO_Ev1CompMask
If a bit is set, then the input status of the respective channel is compared with that bit in the
"CfO_DIREKTIOeventcompState" register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Channel 1 0 Do not compare bit
1 Compare bit in register
... ...
7 Channel 8 0 Do not compare bit
1 Compare bit in register
Name:
CfO_DIREKTIOevent0IDwr to CfO_DIREKTIOevent3IDwr
These registers hold the event IDs that trigger the direct output function. For a list of all possible event IDs, see
4.11.17.12.5.1 "List of event IDs"
Data type Value Information
INT 192 to 7,489 ID of event function
Name:
CfO_DIREKTIOoutclearmask0 to CfO_DIREKTIOoutclearmask3
Writing "1" to the bit position that corresponds to a channel resets the output if the output event function is being
executed. This corresponds to writing "0" to the 4.11.17.12.4.5 "DigitalOutput 02 to 08" registers.
The bit that corresponds to channels that should be reset should be set to "1" in the 4.11.17.12.4.2
"CfO_OutClearMask" register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 Channel 2 0 Reset channel 2
1 Do not reset channel 2
2 Reserved -
3 Channel 4 0 Reset channel 4
1 Do not reset channel 4
4 Reserved -
5 Channel 6 0 Reset channel 6
1 Do not reset channel 6
6 Reserved -
7 Channel 8 0 Reset channel 8
1 Do not reset channel 8
Name:
CfO_DIREKTIOoutsetmask0 to CfO_DIREKTIOoutsetmask3
Writing "1" to the bit position that corresponds to a channel sets the output if the output event function is being
executed. This corresponds to writing "1" to the 4.11.17.12.4.5 "DigitalOutput 02 to 08" registers.
The bit that corresponds to channels that should be reset should be set to "1" in the 4.11.17.12.4.3
"CfO_OutSetMask" register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Reserved -
1 Channel 2 0 Set channel 2
1 Do not set channel 2
2 Reserved -
3 Channel 4 0 Set channel 4
1 Do not set channel 4
4 Reserved -
5 Channel 6 0 Set channel 6
1 Do not set channel 6
6 Reserved -
7 Channel 8 0 Set channel 8
1 Do not set channel 8
The module has 4 internal counter functions, each with 2 event counter registers. Each of these 4 counters is
permanently assigned to 2 physical inputs. This assignment cannot be changed.
The counter registers perform different functions based on how the event functions are connected. The counter
registers can be configured in the following ways:
• ABR counter
• AB counter
• Up/down counters
• Event counters
Different names are used for them in Automation Studio and in the register description to improve clarity.
Channel Counter function Counter register Name in AS
1 1 1 ABEncoder01
ABREncoder01
Counter01
EventCounter01
2 2 EventCounter02
3 2 1 ABEncoder02
Counter02
EventCounter03
4 2 EventCounter04
5 3 1 ABEncoder03
ABREncoder02
Counter03
EventCounter05
6 2 EventCounter06
7 4 1 ABEncoder04
Counter04
EventCounter07
8 2 EventCounter08
There are 3 steps for calculating the state of any counter function
1. The counter value is based on the 2 absolute value counters "abs1" and "abs2". These are only used internally in
the module and cannot be read. Depending on the mode, these registers show the respective physical input signals.
Mode
Edge counters AB encoders Up/down counter
abs1 Edges of counter channel 1 Increments in positive direction Counter channel 2 = 0:
Edges of counter channel 1
in up direction
abs2 Edges of counter channel 2 Increments in negative direction Counter channel 2 = 1
Edges of counter channel 1
in down direction
2. From the absolute value registers "abs1" and "abs2", 2 more counters are formed: "counter 1" and "counter 2".
They are only used internally in the module and cannot be read. The following values are used for the calculation:
• Absolute value registers "abs1" and "abs2"
• SW_reference_counter 1 and 2: This reference value can be defined by the "CfO_CounterPresetValue"
register to allow referencing <> 0.
• HW_reference_counter 1 and 2: In the "CfO_CounterEventMode" register, you can configure whether
latched values should be copied to these registers when counter events occur.
counter1 = abs1 + SW_reference_counter1 - HW_reference_counter1
counter2 = abs2 + SW_reference_counter2 - HW_reference_counter2
3. The counter registers contain the sum of the two internal counters "counter 1" and "counter 2". The
"CfO_CounterConfigReg" register allows you to define a sign for each "counter" register and define whether or
not it should be used.
Counter register = counter1 + counter2
All of the settings available in Automation Studio for AB encoders, ABR encoders, up/down counters and event
counters are based on the two counter functions.
The following configuration examples show the values with which Automation Studio initializes the module registers
in order to implement these functions.
The following table shows how the module's various event functions can be linked in order to configure an AB
encoder.
[x] stands for the respective counter function, from 1 to 4
Register Value Comment
For the function
CfO_Counter[x]config 0x01 Mode = Up/down counter
CfO_Counter[x]configReg0 0x0D Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.17.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
For the latch
CfO_Counter[x]event0config 0x000D Configuration of the calculation of the first value used for the latch
CfO_Counter[x]event0mode 0x03 Mode of the first counter event function - Continuous
CfO_Counter[x]event0IDwr (any) Number of the event that should trigger Latch 1 ("Latch 01 - Channel" in the AS
I/O configuration).
CfO_Counter[x]event1config 0x0D Configuration of the calculation of the second value used for the latch
CfO_Counter[x]event1mode 0x03 Mode of the second counter event function - Continuous
CfO_Counter[x]event1IDwr (any) Number of the event that should trigger Latch 2
For the comparator
CfO_Counter1event1IDwr 0x00D0 Event number of Timer 1 (50 μs)
CfO_Counter3event1IDwr
Information:
The latch and comparator must not have the same event number!
CfO_Counter1event1config 0x900D or 0xA00D Configuration of the comparator for the second counter event
CfO_Counter3event1config
CfO_Counter1event1mode 0x03 Mode of the second counter event function - Continuous
CfO_Counter3event1mode
CfO_DIREKTIOoutevent0IDwr 0x0861 TRUE event output of the second counter to trigger the direct output function
CfO_DIREKTIOoutevent2IDwr 0x0A61 (set outputs).
CfO_DIREKTIOoutsetmask0 0x08, 0x20, 0x80 Outputs that should be set when comparator condition = TRUE
CfO_DIREKTIOoutsetmask2 0x02, 0x08, 0x80
CfO_DIREKTIOoutevent1IDwr 0x0860 FALSE event output of the second counter to trigger the direct output function
CfO_DIREKTIOoutevent3IDwr 0x0A60 (reset outputs).
CfO_DIREKTIOoutclearmask1 0x08, 0x20, 0x80 Outputs that should be reset when comparator condition = FALSE
CfO_DIREKTIOoutclearmask3 0x02, 0x08, 0x80
The following table shows how the module's various event functions can be linked in order to configure an ABR
encoder.
Register Value Comment
For the function
CfO_Counter1PresetValue1 (any) Desired offset value for referencing
CfO_Counter3PresetValue1
CfO_Counter1event0IDwr 0x0201 Link between the first counter event and the "direct input" comparator condition
CfO_Counter3event0IDwr TRUE
CfO_Counter1config 0x01 Mode = AB encoder
CfO_Counter3config
CfO_Counter1configReg0 0x0D Configure the calculation of the internal "counter1" and "counter2" registers
CfO_Counter3configReg0 (see 4.11.17.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
CfO_DIREKTIOevent0IDwr 0x1002 or 0x1012 Selection of the desired input edge as trigger for the ABR encoder function
CfO_DIREKTIOevent1IDwr
CfO_Counter1event0config 0x0000 Configuration of the first counter event (for referencing)
CfO_Counter3event0config
CfO_DIREKTIOevent0mode 0x03 Mode of the "direct input function" - Continuous
CfO_DIREKTIOevent1mode
CfO_DIREKTIOevent0compState 0x00 or 0x08 Comparator status for the "direct input function"
CfO_DIREKTIOevent1compState
CfO_Ev0CompMask 0x08 Comparator mask for the "direct input function"
CfO_Ev1CompMask
For the latch
CfO_Counter1event0config 0x000D Configuration of the calculation of the value used for the latch
CfO_Counter3event1config
CfO_Counter1event0mode 0x03 Mode of the first counter event function - Continuous
CfO_Counter3event1mode
CfO_Counter1event0IDwr (any) Number of the event that should trigger the latch
CfO_Counter3event1IDwr
For the comparator
CfO_Counter1event1IDwr 0x00D0 Event number of Timer 1 (50 μs)
CfO_Counter3event1IDwr
Information:
The latch and comparator must not have the same event number!
CfO_Counter1event1config 0x900D or 0xA00D Configuration of the comparator for the second counter event
CfO_Counter3event1config
CfO_DIREKTIOoutevent0IDwr 0x0861 TRUE event output of the second counter to trigger the direct output function
CfO_DIREKTIOoutevent2IDwr 0x0A61 (set outputs).
CfO_DIREKTIOoutsetmask0 0x08, 0x20, 0x80 Outputs that should be set when comparator condition = TRUE
CfO_DIREKTIOoutsetmask2 0x02, 0x08, 0x80
CfO_DIREKTIOoutevent1IDwr 0x0860 FALSE event output of the second counter to trigger the direct output function
CfO_DIREKTIOoutevent3IDwr 0x0A60 (reset outputs).
CfO_DIREKTIOoutclearmask1 0x08, 0x20, 0x80 Outputs that should be reset when comparator condition = FALSE
CfO_DIREKTIOoutclearmask3 0x02, 0x08, 0x80
The following table shows how the module's various event functions can be linked in order to configure an up/
down counter.
[x] stands for the respective counter function, from 1 to 4
Register Value Comment
For the function
CfO_Counter[x]config 0x03 Counter mode = Up/down counter
CfO_Counter[x]configReg0 0x0D, 0x07 Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.17.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
For the latch
CfO_Counter[x]event0config 0x0D, 0x07 Configuration of the calculation of the first value used for the latch
CfO_Counter[x]event0mode 0x03 Mode of the first counter function - Continuous
CfO_Counter[x]event0IDwr (any) Number of the event that should trigger Latch 1
CfO_Counter[x]event1config 0x0D, 0x07 Configuration of the calculation of the second value used for the latch
CfO_Counter[x]event1mode 0x03 Mode of the second counter function - Continuous
CfO_Counter[x]event1IDwr (any) Number of the event that should trigger Latch 2
For the comparator
CfO_Counter1event1IDwr 0x00D0 Event number of Timer 1 (50 μs)
CfO_Counter3event1lDwr
Information:
The latch and comparator must not have the same event number!
CfO_Counter1event1config 0x900D, 0xA00d or 0x9007, 0xA007 Configuration of the comparator for the second counter event
CfO_Counter3event1config
CfO_Counter1event1mode 0x03 Mode of the second counter event function - Continuous
CfO_Counter3event1lmode
CfO_DIREKTIOoutevent0IDwr 0x0861 TRUE event output of the second counter to trigger the direct output function
CfO_DIREKTIOoutevent2lDwr (set outputs).
CfO_DIREKTIOoutsetmask0 0x08, 0x20, 0x80 Outputs that should be set when comparator condition = TRUE
CfO_DIREKTIOoutsetmask2 0x02, 0x08, 0x80
CfO_DIREKTIOoutevent1IDwr 0x0860 FALSE event output of the second counter to trigger the direct output function
CfO_DIREKTIOoutevent3lDwr 0x0A60 (reset outputs).
CfO_DIREKTIOoutclearmask1 0x08, 0x20, 0x80 Outputs that should be reset when comparator condition = FALSE
CfO_DIREKTIOoutclearmask3 0x02, 0x08, 0x80
The following table shows how the module's various event functions can be linked in order to configure an event
counter.
[x] stands for the respective counter function, from 1 to 4
Register Value Comment
For event counters on channels 1, 3, 5 and 7
CfO_Counter[x]configReg0 0x01 or 0x03 Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.17.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
CfO_Counter[x]event0mode 0x43 Mode of the first counter event function and referencing configuration
CfO_Counter[x]event0IDwr (any) Number of the event that should trigger referencing
For event counters on channels 2, 4, 6 and 8
CfO_Counter[x]configReg1 0x04 or 0x08 Configure the calculation of the internal "counter1" and "counter2" registers
(see 4.11.17.12.6.1 "Counter value calculation" and "Examples of calculation
configurations")
CfO_Counter[x]event1mode 0x83 Mode of the second counter event function and referencing configuration
CfO_Counter[x]event1IDwr (any) Number of the event that should trigger referencing
Each of the 4 counter functions has 2 counter event functions. These consist of:
• Event ID that triggers the counter event function
• A window comparator
• Latch register for saving the counter value
When the counter event function is complete, a combined event ID in the range 2112 to 2913 (see 4.11.17.12.5.1
"List of event IDs") is sent.
Each counter event function also has the option to copy the current counter value to the "HW reference counter"
when an event occurs (see 4.11.17.12.6.1 "Counter value calculation").
Event input
E
Latch True
True True
Hardware reference Hardware reference
Counter 1 = abs 1 Counter 1 = abs 1
True True
Hardware reference Hardware reference
Counter 2 = abs 2 Counter 2 = abs 2
E E
Event output Event output
True False
Name:
CfO_Counter1config to CfO_Counter4config
These registers are used to configure the mode of the counter function. Each counter function can be operated
in 3 different modes.
Counter function mode
Edge counters AB encoder Up/down counter
Counter channel 11) Counting pulses, edge counter 1 A Metering pulses
Counter channel 21) Counting pulses, edge counter 2 B Counting direction (0 =
positive, 1 = negative)
Counter register 1 Counter value 1 Position Counter value
Counter register 2 Counter value 2
1) Corresponds to the physical channels of the counter functions. See 4.11.17.7.1 "Description of channel assignments".
Bit structure:
Bit Description Value Information
0-1 Counter mode 00 Edge counters
01 AB encoder
11 Up/down counter
2-7 Reserved -
Name:
CfO_Counter1configReg0 to CfO_Counter4configReg0 ("counter 1")
CfO_Counter1configReg1 to CfO_Counter4configReg1 ("counter 2")
The calculation of the internal "counter1" and "counter2" registers can be configured in these registers. For infor-
mation on using these internal registers, see 4.11.17.12.6.1 "Counter value calculation".
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 counter 1 - use 0 0 is added instead of "counter 1"
1 "counter 1" is used for addition
1 counter 1 - sign 0 The sign of the "counter 1" register is not changed for addition
1 The sign of the "counter 1" register is reversed for addition
2 counter 2 - use 0 0 is added instead of "counter 2"
1 "counter 2" is used for addition
3 counter 2 - sign 0 The sign of the "counter 2" register is not changed for addition
1 The sign of the "counter 2" register is reversed for addition
4-7 Reserved -
Name:
CfO_Counter1PresetValue1 to CfO_Counter4PresetValue1
CfO_Counter1PresetValue1_32Bit to CfO_Counter4PresetValue1_32Bit (SW_reference_counter1)
CfO_Counter1PresetValue2 to CfO_Counter4PresetValue2
CfO_Counter1PresetValue2_32Bit to CfO_Counter4PresetValue2_32Bit (SW_reference_counter2)
These registers can be used to define an offset value for referencing. This value is copied to the internal
SW_reference_counter register of the respective counter register.
Data type Value
INT -32,768 to 32,767
DINT -2,147,483,648 to 2,147,483,647
Counter register
Name:
Different names are used for these 8 registers depending on their function.
These 8 registers show the results of the counter value calculation for the respective register. Depending on the
function, this corresponds to either the encoder position or the counter value.
For information on the relationship between physical channels and counter registers, see 4.11.17.12.6 "Counters
and encoders" and 4.11.17.7.1 "Description of channel assignments"
Counter 1 - Counter channel 1
Counter register Function Name
1 AB encoders ABEncoder01
ABR encoders ABREncoder01
Up/down counters Counter01
Event counters EventCounter01
2 Event counters EventCounter02
Name:
StatusABR01 to StatusABR02
The referencing status of the ABR encoder is shown in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Reserved 0
2 Bit is always 1 after the first reference pulse. 0 No reference pulses have occurred since the start of referenc-
ing.
1 The first reference pulse has occurred.
3 State change when referencing is complete 0 or 1 State change when referencing is complete
4 Bit is always 1 after the first reference pulse. 0 No reference pulses have occurred since the start of referenc-
ing.
1 The first reference pulse has occurred.
5-7 Continuous counter xxx Increased with each reference pulse
Name:
ReferenceModeABR01 to ReferenceModeABR02
The bits in this register are used to configure the reaction to the configured reference pulse.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Sets the referencing mode 00 Referencing OFF
01 Single shot referencing
10 Reserved
11 Continuous referencing
2-5 Reserved -
6-7 Reserved 11 Must always be 11!
The ABR and AB encoders and the up/down counter have a comparator function. It always works the same and
is described here globally for all three.
The comparators are implemented in software form. They do not work actively but rather passively, i.e. the com-
parison is only carried out when an event is received. The event received is forwarded along the TRUE or FALSE
branch depending on the status of the comparator condition. An event function like this generally also offers a latch
for the TRUE and FALSE branch to save the value used for the comparator at the time of the event.
Comparator modes
Name:
CfO_Counter1event0IDwr to CfO_Counter4event0IDwr (event function 1)
CfO_Counter1event1IDwr to CfO_Counter4event1IDwr (event function 2)
This register holds the event ID that should trigger the counter event function. For a list of all possible event IDs,
see 4.11.17.12.5.1 "List of event IDs"
Data type Value Information
INT 192 to 7,489 ID of counter event function
Name:
CfO_Counter1event0config to CfO_Counter4event0config (event function 1)
CfO_Counter1event1config to CfO_Counter4event1config (event function 2)
These registers are used to configure the counter event function for the respective counter function.
Bits 0 to 3 configure the calculation of the comparison or to latch the value. This calculation is similar to the calcu-
lation of the counter register (see 4.11.17.12.6.1 "Counter value calculation")
Bits 8 to 13 can be used to limit the number of bits used for the comparison. A mask is calculated as 2n - 1 and
linked with an "AND" operation. This makes it possible to generate a comparator pulse every 2n increments.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0 counter 1 - use 0 0 is added instead of "counter 1"
1 "counter 1" is used for addition
1 counter 1 - sign 0 The sign of the "counter 1" register is not changed for addition
1 The sign of the "counter 1" register is reversed for addition
2 counter 2 - use 0 0 is added instead of "counter 2"
1 "counter 2" is used for addition
3 counter 1 - sign 0 The sign of the "counter 2" register is not changed for addition
1 The sign of the "counter 2" register is reversed for addition
4-7 Reserved -
8 - 13 Number of bits for comparator mask x The mask value is calculated as 2n-1, where n is value set in
these bits. Default: 0
14 Reserved -
15 Margin comparator mode 0 MarginComparator >= (Current position - OriginComparator)
1 MarginComparator > (Current position - OriginComparator)
Name:
CfO_Counter1event0mode to CfO_Counter4event0mode (event function 1)
CfO_Counter1event1mode to CfO_Counter4event1mode (event function 2)
In these registers you can set the mode for the comparator function and optional copying of the latched registers.
Comparator functions can be operated in 4 different modes. For a description, see "Comparator modes".
Bits 4 to 7 can be used to define hardware referencing actions.
Based on these bits, the values of the internal absolute value counters "abs1" and "abs2" can be copied to the re-
spective "HW_reference_counter" register at every counter event (see 4.11.17.12.6.1 "Counter value calculation").
This function can be used to reference the counter values directly in the hardware.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Comparator mode 0 Off
1 Single
2 State change
3 Continuous
2-3 Reserved -
4 Copy abs1 counter value 0 No action
1 When event is FALSE → hardware reference counter 1 = abs1
5 Copy abs2 counter value 0 No action
1 When event is FALSE → hardware reference counter 2 = abs2
6 Copy abs1 counter value 0 No action
1 When event is TRUE → hardware reference counter 1 = abs1
7 Copy abs2 counter value 0 No action
1 When event is TRUE → hardware reference counter 2 = abs2
Comparator origin
Name:
OriginComparator01 to OriginComparator02 (ABR encoder)
OriginComparator01 and OriginComparator03 (AB encoder and up/down counter)
This register is available for the AB and ABR encoders and the up/down counters.
It defines the position value at which the respective configured comparator output channel is set.
Data type Value Information
INT -32,768 to 32,767 Comparator window origin, 16-bit
DINT -2,147,483,648 Comparator window origin, 32-bit
to 2,147,483,647
Name:
MarginComparator01 to MarginComparator02 (ABR encoder)
MarginComparator01 and MarginComparator03 (AB encoder and up/down counter)
This register is available for the AB and ABR encoders and the up/down counters.
It defines the width of the comparator window in the positive direction.
Data type Value Information
INT -32,768 to 32,767 Width of comparator window, 16-bit
DINT -2,147,483,648 to 2,147,483,647 Width of comparator window, 32-bit
Counter 1 - Latch 2
Event function Function Name
1 AB encoders Latch01AB02
Up/down counters Latch01Counter02
2 AB encoders Latch02AB02
Up/down counters Latch02Counter02
Counter 2 - Latch 1
Event function Function Name
1 AB encoders Latch01AB03
Up/down counters Latch01Counter03
2 AB encoders Latch02AB03
ABR encoders Latch01ABR02
Up/down counters Latch02Counter03
Counter 2 - Latch 2
Event function Function Name
1 AB encoders Latch01AB04
Up/down counters Latch01Counter04
2 AB encoders Latch02AB04
Up/down counters Latch02Counter04
The module has 2 SSI encoders available, supported directly in the hardware. Two 24 V output channels are set
for each SSI encoder and cannot be changed. (See also 4.11.17.7.1 "Description of channel assignments")
When using the SSI encoder, the corresponding clock channel can be configured in the 4.11.17.12.4.1
"CfO_CFGchannel" register as "Channel-specific" and "Push/Pull".
Encoder Data channel Clock channel
SSI1 1 2
SSI2 5 6
Each of the two SSI encoders consists of an event function and an event input. The SSI cycle is started when an
event is received on this input.
Information:
The SSI event function is not linked to an event by default, i.e. SSI functions are disabled.
Two events are sent from the SSI encoder interface..
• An "SSI valid" event is triggered immediately after the end of the SSI cycle if a new counter value is available.
• The "SSI ready" event then shows when the monoflop time has expired (tp in SSI encoder timing diagram).
This is the earliest that the next SSI cycle can be started.
SSI encoder - Timing diagram
SSI cycle
Clock 1 2 3 4 5 6 n
Data
SSI valid
SSI start event SSI ready
Name:
CfO_SSI1event0IDwr to CfO_SSI2event0IDwr
This register holds the event ID that should start the SSI cycle. For a list of all possible event IDs, see 4.11.17.12.5.1
"List of event IDs"
Normally this register is set to network event 225 "AOSISOP"- This ensures that the new encoder position is
available at the next "I/O → Synchronous Frame" transfer. Check the SSI transfer time and the X2X cycle time,
because the SSI cycle must be completed within this time.
Data type Value Information
INT 192 to 7,233 ID of event function
Configure SSI
Name:
CfO_SSI1cfg to CfO_SSI2cfg
This configuration register is used to set the coding, the clock rate and the number of bits. Default = 0. This must
be set once using an acyclic write command.
Data type Value
UINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 00 1 MHz
01 500 kHz
10 250 kHz
11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
Name:
ConfigAdvanced01 to ConfigAdvanced02
This configuration register is used to set the coding, the clock rate, the number of bits and the monostable multivi-
brator settings. Default = 0. This must be set once using an acyclic write command.
It only differs from "CfO_SSI1cfg" by data length and additional monostable multivibrator testing.
Data type Value
UDINT See bit structure.
Bit structure:
Bit Name Value Information
0-5 SSI value valid bits x
6-7 Clock rate 00 1 MHz
01 500 kHz
10 250 kHz
11 125 kHz
8 - 13 SSI number of bits x Number of bits including leading zeros
14 Reserved 0
15 Keying 0 Binary coding
1 Gray coding
16 - 17 Monostable multivibrator check 00 Check OFF, no additional clock bit
01 Check set to High level
10 Check set to Low level
11 Level is clocked but ignored
18 - 31 Reserved 0
Name:
CfO_SSI1control to CfO_SSI2control
The two SSI encoder events can be enabled/disabled using this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Event: SSI valid 0 Not sent
1 Sent
1 Event: SSI ready 0 Not sent
1 Sent
2-7 Reserved -
Name:
SSIEncoder01 to SSIEncoder02
The last transferred SSI position can be read out from this register. The SSI encoder value is displayed as a 32-
bit position value. This position value is generated synchronously with the X2X cycle.
Data type Value Information
UDINT 0 to 4,294,967,295 Last SSI position transferred
The module has an assigned comparator function for the SSI function. These consist of:
• Event ID that triggers the comparator function
• The window comparator
• Latch register for saving the counter value
When the comparator function is complete, event ID 7232 to7489 (see 4.11.17.12.5.1 "List of event IDs") is sent.
Name:
CfO_SSI1eventIDwr to CfO_SSI2eventIDwr
This register holds the event ID that should start the SSI comparator function. For a list of all possible event IDs,
see 4.11.17.12.5.1 "List of event IDs"
Data type Value Information
INT 192 to 7,233 ID of comparator function
Name:
CfO_SSI1event0mode to CfO_SSI2event0mode
This register can be used to configure the mode of the comparator function.
Comparator functions can be operated in 4 different modes. For a description, see "Comparator modes".
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Comparator mode 0 Off
1 Single
2 State change
3 Continuous
2-7 Reserved -
Name:
CfO_SSI1event0config and CfO_SSI2event0config
The calculation of the position value used for the comparator can be configured in this register.
The window comparator condition is calculated as follows:
counter_window_value = ssi_counter & (2^ssi_data_bits - 1)
diff = counter_window_value – origin_comparator
if ((diff & (2^(comparator_mask)-1)) <= margin_comparator)
condition = True;
else
condition = False;
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-5 SSI data bits x Number of data bits used for masking
6-7 Reserved -
8 - 13 Comparator mask x The mask value is calculated from 2n-1, where n is the value
configured in SSI data bits. Default: 0
14 Comparator mode 0 MarginComparator >= SSI position - OriginComparator
1 MarginComparator > SSI position - OriginComparator
Name:
OriginComparator01_SSI to OriginComparator02_SSI
This register contains the origin of the window comparator.
Data type Value Information
UDINT 0 to 4,294,967,295 Origin of the window comparator.
Name:
MarginComparator01_SSI to MarginComparator02_SSI
This register provides the width of the window comparator.
Data type Value Information
UDINT 0 to 4,294,967,295 Width of the SSI window comparator
Name:
Latch01SSI01 to Latch01SSI02
If the SSI window comparator returns "True", then the current SSI position is latched and saved in this register.
Data type Value Information
UDINT 0 to 4,294,967,295 Latched SSI position
The module has 4 PWM functions available, supported directly by the hardware. A 24 V output channel is set for
each PWM encoder and cannot be changed. (See also 4.11.17.7.1 "Description of channel assignments")
When using the PWM function, the corresponding channel can be configured in the 4.11.17.12.4.1
"CfO_CFGchannel" register as "Channel-specific".
PWM function Channel
PWM1 2
PWM2 4
PWM3 6
PWM4 8
Name:
CfO_PWM0prescaler to CfO_PWM3prescaler
The length of the PWM cycle is configured using this register. The base is a 48 MHz clock, which can be changed
(divided) using the setting in this register. One PWM cycle consists of 1,000 of the resulting clocks after they have
been divided. The period length of the PWM cycle is calculated as follows:
prescale
PWM_cycle = 1000 [s]
48,000,000
Data type Value Information
UINT 2 to 65,535 Prescaler for PWM cycle
Name:
PWMOutput02, PWMOutput04, PWMOutput06, PWMOutput08
In this register, a configuration is made for the percentage of the PWM cycle (in 1/10 % steps) that the PWM output
is logical 1, i.e. ON.
Data type Value Information
UINT 0 to 1,000 PWM output always off
2 to 999 Turn on time in 1/10% steps
1,000 PWM output always on
The module has a time measurement function for each I/O channel. It can be configured separately for rising and
falling edges on each channel.
A starting edge can be configured for each time measurement function. When a configured starting edge occurs,
the value of the internal timer is saved in a FIFO. This FIFO holds up to 16 elements. When the actual trigger edge
occurs, the difference in time between the starting edge and the triggered edge is copied to the respective register.
Bits 8 to 11 "Previous start edge" of the 4.11.17.12.9.2 "CfO_EdgeTimeFallingMode" and 4.11.17.12.9.3
"CfO_EdgeTimeRisingMode" registers can be used to define which detected starting edge from the FIFO should
be used to calculate the difference. Additionally, when the trigger edge occurs, the counter clocked internally us-
ing bits 12 to 15 "Time measurement resolution are copied to the 4.11.17.12.9.10 "TimeStampFallingCH" and
4.11.17.12.9.11 "TimeStampRisingCH" registers.
Information:
The time measurement function is an extension of edge detection, so all of the channels used must
be configured there.
Name:
CfO_EdgeTimeglobalenable
This register enables/disables the time measurement function for the entire module.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Time measurement function 0 Disabled for entire module
1 Enabled for entire module
1-7 Reserved -
Name:
CfO_EdgeTimeFallingMode01 to CfO_EdgeTimeFallingMode08
These registers can be used to configure the time measurement function for the falling edge of the respective
channel.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Selects the channel for the starting edge 0 Channel 1
...
7 Channel 8
4 Selects the edge for the starting edge 0 The falling edge of the channel configured in bits 0 to 3 serves
as the starting edge.
1 The rising edge of the channel configured in bits 0 to 3 serves
as the starting edge.
5-6 Reserved -
7 Trigger 0 Triggered1)
1 Continuous2)
8 - 11 Previous start edge 0 to 15 The value determines which entry in the starting edge FIFO
should be used to calculate the time difference.
12 - 15 Time measurement resolution 0 8 Mhz
1 4 Mhz
2 2 Mhz
3 1 Mhz
4 500 kHz
5 250 kHz
6 125 kHz
7 625 kHz
1) The time measurement is triggered by the corresponding bit in the 4.11.17.12.9.5 "TriggerRisingCH" register.
2) Time measurement runs continuously and is triggered at every edge.
Name:
CfO_EdgeTimeRisingMode01 to CfO_EdgeTimeRisingMode08
These registers can be used to configure the time measurement function for the rising edge of the respective
channel.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Selects the channel for the starting edge 0 Channel 1
...
7 Channel 8
4 Selects the edge for the starting edge 0 The falling edge of the channel configured in bits 0 to 3 serves
as the starting edge.
1 The rising edge of the channel configured in bits 0 to 3 serves
as the starting edge.
5-6 Reserved -
7 Trigger 0 Triggered1)
1 Continuous2)
8 - 11 Previous start edge 0 to 15 The value determines which entry in the starting edge FIFO
should be used to calculate the time difference.
12 - 15 Time measurement resolution 0 8 Mhz
1 4 Mhz
2 2 Mhz
3 1 Mhz
4 500 kHz
5 250 kHz
6 125 kHz
7 625 kHz
1) The time measurement is triggered by the corresponding bit in the 4.11.17.12.9.5 "TriggerRisingCH" register.
2) Time measurement runs continuously and is triggered at every edge.
Name:
TriggerFallingCH01 to TriggerFallingCH08
If bit 7 "Trigger" is cleared in the 4.11.17.12.9.2 "CfO_EdgeTimeFallingMode" register, then detection of a falling
edge on the respective input can be triggered using the respective bit in this register. After a bit has been set, the
next falling edge on the corresponding channel is detected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 TriggerFallingCH01 0 Falling edges on channel 1 are not detected
1 The next falling edge on channel 1 will be detected
... ...
7 TriggerFallingCH08 0 Falling edges on channel 8 are not detected
1 The next falling edge on channel 8 will be detected
Name:
TriggerRisingCH01 to TriggerRisingCH08
If the "Continued/triggered" bit is cleared in the 4.11.17.12.9.3 "CfO_EdgeTimeRisingMode" register, then detection
of a rising edge on the respective input can be triggered using the respective bit in this register. After a bit has been
set, the next rising edge on the corresponding channel is detected.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 Trigger rising edge - Channel 1 0 Rising edges on channel 1 are not detected
1 The next rising edge on channel 1 will be detected
... -
7 Trigger rising edge - Channel 8 0 Rising edges on channel 8 are not detected
1 The next rising edge on channel 8 will be detected
Name:
BusyTriggerFallingCH01 to BusyTriggerFallingCH08
If edges are triggered via the bits in the 4.11.17.12.9.4 "TriggerFallingCH" register, then a set bit in this register
indicates that no falling edges have been detected on the respective channel since the corresponding bit was
set in the "TriggerFallingCH" register. If a falling edge occurs on the respective channel, then the corresponding
BusyTriggerFalling bit is cleared.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 BusyTriggerFallingCH01 0 Falling edge detected on channel 1
1 Module waiting for a falling edge on channel 1
... ...
7 BusyTriggerFallingCH08 0 Falling edge detected on channel 8
1 Module waiting for a falling edge on channel 8
Name:
BusyTriggerRisingCH01 to BusyTriggerRisingCH08
If edges are triggered via the bits in the 4.11.17.12.9.5 "TriggerRisingCH" register, then a set bit in this register
indicates that no rising edges have been detected on the respective channel since the corresponding bit was
set in the "TriggerRisingCH" register. If a rising edge occurs on the respective channel, then the corresponding
BusyTriggerRising bit is cleared.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 BusyTriggerRisingCH01 0 Rising edge detected on channel 1
1 Module waiting for a rising edge on channel 1
... ...
7 BusyTriggerRisingCH08 0 Rising edge detected on channel 8
1 Module waiting for a rising edge on channel 8
Name:
CountFallingCH01 to CountFallingCH08
These registers contain cyclic counters that are incremented with every detected falling edge on the respective
channel.
Data type Value Information
USINT 0 to 255 Counter for falling edges
Name:
CountRisingCH01 to CountRisingCH08
These registers contain cyclic counters that are incremented with every detected rising edge on the respective
channel.
Data type Value Information
USINT 0 to 255 Counter for rising edges
Name:
TimeStampFallingCH01 to TimeStampFallingCH08
When a falling edge occurs on the respective channel, the current counter value of the module timer is copied
to these registers.
Data type Value Information
UINT 0 to 65,535 Time stamp for rising edges
Name:
TimeStampRisingCH01 to TimeStampRisingCH08
When a rising edge occurs on the respective channel, the current counter value of the module timer is copied to
these registers.
Data type Value Information
UINT 0 to 65,535 Time stamp for rising edges
Name:
TimeDiffFallingCH01 to TimeDiffFallingCH08
When a falling edge occurs on the respective channel, the time difference compared to the starting edge configured
in bit 4 of the 4.11.17.12.9.2 "CfO_EdgeTimeFallingMode" register is copied to this register.
Data type Value Information
UINT 0 to 65,535 Time difference from starting edge
Name:
TimeD-iffRisingCH01 to TimeDiffRisingCH08
When a rising edge occurs on the respective channel, the time difference compared to the starting edge configured
in bit 4 of the 4.11.17.12.9.3 "CfO_EdgeTimeRisingMode" register is copied to this register.
Data type Value Information
UINT 0 to 65,535 Time difference from starting edge
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
128 μs
The maximum cycle time defines how far the bus cycle can be increased without internal counter overflows causing
module malfunctions.
Minimum cycle time
16 ms
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
128 μs
The x86 100 MHz-compatible X20CP1483 is the entry-level X20 CPU. With an optimal price/performance ratio, it
has the same basic features as the larger CPUs and offers sufficient performance for most standard applications.
USB and Ethernet are included in every CPU. In addition, every CPU has a POWERLINK connection for real-time
communication.
In addition, a multi-purpose slot is provided for an additional interface module.
• Intel x86 100 MHz-compatible with additional I/O processor
• Ethernet, POWERLINK V1/V2 and USB onboard
• Modular expansion of interfaces
• CompactFlash as removable application memory
• Fanless
• Extremely compact
Included in delivery
Model number Short description
4A0006.00-000 Backup battery (see also section 4.12.2.18 "Exchanging the lithium battery")
- Interface module slot covers
X20AC0SR1 X20 locking plate, right
X20TB12 X20 terminal block, 12-pin, 24 V keyed
The Status/Error LED is a green/red dual LED. The LED status can have different meanings depending on the
operating mode.
4.12.2.4.1.2 POWERLINK V1
Status LED Status of the POWERLINK node
Green Red
On Off The POWERLINK node is running with no errors.
Off On A system error has occurred. The error type can be read using the PLC logbook. An irreparable problem has occurred. The system
cannot properly carry out its tasks. This state can only be changed by resetting the module.
Blinking alternately The POWERLINK managing node has failed. This error code can only occur when operated as a controlled node. This means
that the configured node number lies within the range 0x01 - 0xFD.
Off Blinking System failure. The red blinking LED signals an error code (see section 4.12.2.4.2 "System failure error codes").
Off Off Module is:
• Off
• Starting up
• Not configured correctly in Automation Studio
• Defective
4.12.2.4.1.3 POWERLINK V2
Red - Error Description
On The module is in an error mode (failed Ethernet frames, increased number of collisions on the network, etc.).
If an error occurs in the following states, then the green LED blinks over the red LED:
• PRE_OPERATIONAL_1
• PRE_OPERATIONAL_2
• READY_TO_OPERATE
Status
Green
t
Error
Red
t
"S/E" LED
t
Note:
The LED blinks red several times immediately after startup. This is not an error.
Triple flash
200 200 200 200 200 1000
Double flash
200 200 200 1000
Single flash
200 1000
Blinking
200 200
Flickering
All times in ms
Incorrect configuration or defective hardware can cause a system failure error code.
The error code is indicated by the red Error LED using four switch-on phases. The switch-on phases have a duration
of either 150 ms or 600 ms. The error code is output cyclically every 2 seconds.
Error description Error code indicated by red status LED
RAM error: ● ● ● - Pause ● ● ● - Pause
The module is defective and must be replaced.
Hardware error: - ● ● - Pause - ● ● - Pause
The module or a system component is defective and must be replaced.
Table 267: X20 CPUs - LED status indicators for the integrated power supply
IF1 - RS232
Figure 289: X20 CPUs - Operating elements for X20CP1483 and X20CP1483-1
These CPUs require application memory in order to operate. The application memory is provided in the form of a
CompactFlash card. It is not included with the CPUs, but must be ordered separately as an accessory.
Information:
The CompactFlash card must not be removed during operation.
Reset button
A power supply is integrated in the X20 CPUs. It has a feed for the CPU, the X2X Link and the internal I/O supply.
Supply for the CPU and X2X Link is electrically isolated.
Pinout
r e
SI
Reserved
Reserved Reserved
GND GND
Connection examples
PS
10 A slow-blow
CPU / X2X Link + + I/O
supply _ _ supply
+24 VDC
GND
PS
Jumper
10 A slow-blow
+ I/O
_ supply
+24 VDC
GND
The non-electrically isolated RS232 interface is primarily intended to serve as an online interface for communication
with the programming device.
r e
SI
TX RX
GND
Information:
The Ethernet interface (IF2) is not suited for POWERLINK (see 4.12.2.13 "POWERLINK interface (IF3)").
Pinout
Interface Pinout
Pin Ethernet
1 TXD Transmit data
2 TXD\ Transmit data\
1
3 RXD Receive data
4 Termination
5 Termination
6 RXD\ Receive data\
Shielded RJ45 7 Termination
8 Termination
POWERLINK V1
Switch position Description
0x00 Operation as managing node.
0x01 - 0xFD Node number of the POWERLINK node. Operation as controlled node.
0xFE - 0xFF Reserved, switch position not permitted
POWERLINK V2
Switch position Description
0x00 Reserved, switch position not permitted
0x01 - 0xEF Node number of the POWERLINK node. Operation as a controlled node.
0xF0 Operation as a managing node.
0xF1 - 0xFF Reserved, switch position not permitted
Ethernet mode
Starting with Automation Studio Version V2.5.3 and with Automation Runtime V2.90, the interface can be operated
as an Ethernet interface.
The INA2000 station number can be set using the B&R Automation Studio software.
Pinout
Information:
USB interfaces cannot be used for online communication with a programming device.
To prevent damage, a shut-off/reset is triggered on the CPU when the processor reaches 100°C.
The following errors are entered in the logbook:
Error number Error description
9204 WARNING: System halted because of temperature check
9210 WARNING: Boot by watchdog or manual reset
The CPUs are buffered by a backup battery. The following areas are buffered:
• Remanent variables
• User RAM
• System RAM
• Real-time clock
Battery monitoring
The battery voltage is checked cyclically. The cyclic load test of the battery does not considerably shorten the
battery life, instead it gives an early warning of weakened buffer capacity.
The status information "Battery OK" is available from the system library function "BatteryInfo" and the CPU's I/
O mapping.
The CPUs have a lithium battery. The lithium battery is found in a separate compartment on the bottom of the
module and protected by a cover.
Backup battery data
Model number
4A0006.00-000 1 pcs.
0AC201.91 4 pcs.
Short description Lithium battery, 3 V / 950 mAh, button cell
Storage temperature -20 to 60°C
Storage time Max. 3 years at 30°C
Relative humidity 0 to 95%, non-condensing
Warning!
The battery must be replaced by a Typ CR2477N Renata battery only. The use of another battery may
present a risk of fire or explosion.
The battery may explode if handled improperly. Do not recharge, disassemble or dispose of in fire.
3. Remove the battery from the holder (do not use pliers or uninsulated tweezers -> risk of short circuiting). The
battery should not be held by its edges. Insulated tweezers may also be used to remove the battery.
Correct: Incorrect:
4. Insert the new battery with the correct polarity. To do this, lay the battery with the "+" side up on the right part
of the battery holder under the USB interface IF4. Then secure the battery in the holder by pressing above
the left part of the battery holder.
5. Replace the cover.
Information:
Lithium batteries are considered hazardous waste. Used batteries should be disposed of in accordance
with applicable local regulations.
General information
In order for the application project to be executed on the CPU, the Automation Runtime operating system, the
system components and the application project must be installed on the CompactFlash card.
For details about commissioning: See help system under "Automation Software / Getting Started"
Based on state-of-the-art Intel® ATOM™ processor technology, X20 CPUs cover a wide spectrum of requirements.
They can be implemented in solutions ranging from standard applications to those requiring the highest levels of
performance.
The series starts with Intel® ATOM™ processor 333 MHz compatible models – X20CP1583 and X20CP3583. With
an optimum price/performance ratio, it has the same basic features as all of the larger CPUs.
The basic model includes USB, Ethernet, POWERLINK V1/V2 and replaceable CompactFlash card. The standard
Ethernet interface is capable of handling communication in the gigabit range. For improved real-time network
performance, the onboard POWERLINK interface supports poll response chaining mode (PRC).
In addition, there are up to three multi-purpose slots for additional interface modules.
• Intel® ATOM™ 1600/1000/600 Performance with integrated I/O processor
• Entry-level CPU is Intel® ATOM™ 333 MHz-compatible with integrated I/O processor
• Ethernet, POWERLINK V1/V2 with poll response chaining and onboard USB
• 1 or 3 slots for modular interface expansion
• CompactFlash as removable application memory
• Up to 512 MB DDR2-SRAM according to performance requirements
• CPU redundancy possible
• Fanless
• Extremely compact
Included in delivery
Model number Short description
4A0006.00-000 Backup battery (see also section 4.12.3.20 "Exchanging the lithium battery")
- Interface module slot covers
X20AC0SR1 X20 locking plate, right
X20TB12 X20 terminal block, 12-pin, 24 V keyed
Included in delivery
Model number Short description
4A0006.00-000 Backup battery (see also section 4.12.3.20 "Exchanging the lithium battery")
- Interface module slot covers
X20AC0SR1 X20 locking plate, right
X20TB12 X20 terminal block, 12-pin, 24 V keyed
The Status/Error LED is a green/red dual LED. The LED status can have different meanings depending on the
operating mode.
4.12.3.6.1.2 POWERLINK V1
Status LED Status of the POWERLINK node
Green Red
On Off The POWERLINK node is running with no errors.
Off On A system error has occurred. The error type can be read using the PLC logbook. An irreparable problem has occurred. The system
cannot properly carry out its tasks. This state can only be changed by resetting the module.
Blinking alternately The POWERLINK managing node has failed. This error code can only occur when operated as a controlled node. This means
that the configured node number lies within the range 0x01 - 0xFD.
Off Blinking System failure. The red blinking LED signals an error code (see section 4.12.3.6.2 "System failure error codes").
Off Off Module is:
• Off
• Starting up
• Not configured correctly in Automation Studio
• Defective
4.12.3.6.1.3 POWERLINK V2
Red - Error Description
On The module is in an error mode (failed Ethernet frames, increased number of collisions on the network, etc.).
If an error occurs in the following states, then the green LED blinks over the red LED:
• PRE_OPERATIONAL_1
• PRE_OPERATIONAL_2
• READY_TO_OPERATE
Status
Green
t
Error
Red
t
"S/E" LED
t
Note:
The LED blinks red several times immediately after startup. This is not an error.
Triple flash
200 200 200 200 200 1000
Double flash
200 200 200 1000
Single flash
200 1000
Blinking
200 200
Flickering
All times in ms
Incorrect configuration or defective hardware can cause a system failure error code.
The error code is indicated by the red Error LED using four switch-on phases. The switch-on phases have a duration
of either 150 ms or 600 ms. The error code is output cyclically every 2 seconds.
Error description Error code indicated by red status LED
RAM error: ● ● ● - Pause ● ● ● - Pause
The module is defective and must be replaced.
Hardware error: - ● ● - Pause - ● ● - Pause
The module or a system component is defective and must be replaced.
Table 287: X20 CPUs - LED status indicators for the integrated power supply
X20CP158x
Mounting rail Operating mode-
lock switch CompactFlash LED status indicators
IF1 - RS232
X20CP358x
Mounting rail Operating mode-
lock switch CompactFlash LED status indicators
IF1 - RS232
Ethernet IF2 - Ethernet Battery IF4 - USB Slots for Terminal block for CPU
Station address IF5 - USB interface and I/O supply,
IF3 - POWERLINK modules RS232 interface
Reset button
These CPUs require application memory in order to operate. The application memory is provided in the form of a
CompactFlash card. It is not included with the CPUs, but must be ordered separately as an accessory.
Information:
The CompactFlash card must not be removed during operation.
Reset button
A power supply is integrated in the X20 CPUs. It has a feed for the CPU, the X2X Link and the internal I/O supply.
Supply for the CPU and X2X Link is electrically isolated.
Pinout
r e
SI
Reserved
Reserved Reserved
GND GND
Connection examples
PS
10 A slow-blow
CPU / X2X Link + + I/O
supply _ _ supply
+24 VDC
GND
PS
Jumper
10 A slow-blow
+ I/O
_ supply
+24 VDC
GND
The non-electrically isolated RS232 interface is primarily intended to serve as an online interface for communication
with the programming device.
r e
SI
TX RX
GND
Information:
The Ethernet interface (IF2) is not suitable for POWERLINK (see 4.12.3.15 "POWERLINK interface
(IF3)").
Pinout
Interface Pinout
Pin Ethernet
1 D1+ Data 1+
2 D1- Data 1-
1
3 D2+ Data 2+
4 D3+ Data 3+
5 D3- Data 3-
6 D2- Data 2-
Shielded RJ45 port 7 D4+ Data 4+
8 D4- Data 4-
POWERLINK V1
Switch position Description
0x00 Operation as managing node.
0x01 - 0xFD Node number of the POWERLINK node. Operation as controlled node.
0xFE - 0xFF Reserved, switch position not permitted
POWERLINK V2
Switch position Description
0x00 Reserved, switch position not permitted
0x01 - 0xEF Node number of the POWERLINK node. Operation as a controlled node.
0xF0 Operation as a managing node.
0xF1 - 0xFF Reserved, switch position not permitted
Ethernet mode
In this mode, the interface is operated as an Ethernet interface. The INA2000 station number can be set using the
B&R Automation Studio software.
Pinout
Information about cabling X20 modules with an Ethernet interface can be found on the B&R website in the module's
download section at www.br-automation.com.
Pin Assignment
1 RxD Receive data
2 RxD\ Receive data\
3 TxD Transmit data
4 Termination
5 Termination
6 TxD\ Transmit data\
7 Termination
8 Termination
Information:
USB interfaces cannot be used for online communication with a programming device.
To prevent damage, the CPU is cut off and reset when the processor reaches 110°C or the circuit board reaches
95°C.
The following errors are entered in the logbook:
Error number Error description
9204 WARNING: System halted because of temperature check
9210 WARNING: Boot by watchdog or manual reset
The CPUs are buffered by a backup battery. The following areas are buffered:
• Remanent variables
• User RAM
• System RAM
• Real-time clock
Battery monitoring
The battery voltage is checked cyclically. The cyclic load test of the battery does not considerably shorten the
battery life, instead it gives an early warning of weakened buffer capacity.
The status information "Battery OK" is available from the system library function "BatteryInfo" and the CPU's I/
O mapping.
The CPUs have a lithium battery. The lithium battery is found in a separate compartment on the bottom of the
module and protected by a cover.
Backup battery data
Model number
4A0006.00-000 1 pcs.
0AC201.91 4 pcs.
Short description Lithium battery, 3 V / 950 mAh, button cell
Storage temperature -20 to 60°C
Storage time Max. 3 years at 30°C
Relative humidity 0 to 95%, non-condensing
Warning!
The battery must be replaced by a Typ CR2477N Renata battery only. The use of another battery may
present a risk of fire or explosion.
The battery may explode if handled improperly. Do not recharge, disassemble or dispose of in fire.
3. Remove the battery from the holder (do not use pliers or uninsulated tweezers -> risk of short circuiting). The
battery should not be held by its edges. Insulated tweezers may also be used to remove the battery.
Correct: Incorrect:
4. Insert the new battery with the correct polarity. To do this, lay the battery with the "+" side up on the right part
of the battery holder under the USB interface IF4. Then secure the battery in the holder by pressing above
the left part of the battery holder.
5. Replace the cover.
Information:
Lithium batteries are considered hazardous waste. Used batteries should be disposed of in accordance
with applicable local regulations.
General information
In order for the application project to be executed on the CPU, the Automation Runtime operating system, the
system components and the application project must be installed on the CompactFlash card.
For details about commissioning: See help system under "Automation Software / Getting Started"
• A hardware upgrade is required for some X20 IFxxxx interface modules. This can be installed from Au-
tomation Studio by selecting Tools/Upgrades from the menu.
In addition, some modules specify a specific hardware revision. The following table provides an overview:
Model number Minimum upgrade version Minimum hardware revision
X20IF1020 1.1.5.1 H0
X20IF1030 1.1.5.1 I0
X20IF1041-1 - -
X20IF1043-1 - -
X20IF1051-1 - -
X20IF1053-1 - -
X20IF1061 - E0
X20IF1061-1 - -
X20IF1063 1.1.5.0 -
X20IF1063-1 - -
X20IF1065 - -
X20IF1072 1.0.5.1 -
X20IF1082 1.2.2.0 -
X20IF1082-2 1.2.1.0 -
X20IF1086-2 1.1.1.0 -
X20IF1091 1.0.5.1 -
X20IF10A1-1 - -
X20IF10D1-1 - -
X20IF10D3-1 - -
X20IF10E1-1 - -
X20IF10E3-1 - -
X20IF10G3-1 - -
X20IF10H3-1 - -
X20IF2772 1.0.6.1 -
X20IF2792 1.0.5.1 -
Table 295: X20 CPUs - Minimum upgrade version and minimum hardware revision for X20 IFxxxx interface modules
• The X20CPx58x CPUs are supported by B&R Automation Studio V3.0.90.20 and higher.
• If an X20CPx48x is to be replaced by an X20CPx58x in an existing Automation Studio configuration, the
X20CPx58x may not be listed as one of the available options even though the upgrade for the CPU has
already been installed. If this is the case, it is necessary to upgrade the X20CPx48x.
• Starting with Automation Runtime 4.x, USB devices are integrated in Automation Runtime dynamically so
that they no longer need to be configured in Automation Studio. In order to use a USB device, its internal
device name needs to be obtained at runtime. For an example, see the Automation Studio help system
for the library "AsUSB / Examples".
4.13.2 X20DI2371
Product ID X20DI2371
Short description
I/O module 2 digital inputs 24 VDC for 3-wire connections
General information
B&R ID code 0x1B8D
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.12 W
Internal I/O 0.29 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 3-wire connections
Input circuit Sink
Input resistance Typ. 6.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Sensor supply
Power consumption Max. 12.0 W 1)
Voltage Module supply minus voltage drop for short circuit protection
Voltage drop for short circuit protection at 500 mA Max. 2 VDC
Summation current 0.5 A
Short circuit protection Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB06 or X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-2 Green Input status of the corresponding digital input
4.13.2.5 Pinout
r e
X20 DI 2371
1 2
DI 1 DI 2
GND GND
DI
Sensor 1
Sensor 2
Input x
VDR
GND
I/O status
LED (green)
Input status
24 V
PTC
24 V
GND
GND
An input filter is available for each input. The input delay can be set using register 4.13.2.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput02
The input status of digital inputs 1 to 2 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput02") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 3 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
1 DigitalInput02 0 or 1 Input status - Digital input 2
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.3 X20DI2372
Product ID X20DI2372
Short description
I/O module 2 digital inputs 24 VDC for 3-wire connections
General information
B&R ID code 0x22A7
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.12 W
Internal I/O 0.29 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 3-wire connections
Input circuit Source
Input resistance Typ. 6.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Sensor supply
Power consumption Max. 12.0 W 1)
Voltage Module supply minus voltage drop for short circuit protection
Voltage drop for short circuit protection at 500 mA Max. 2 VDC
Summation current 0.5 A
Short circuit protection Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB06 or X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-2 Green Input status of the corresponding digital input
4.13.3.5 Pinout
r e
X20 DI 2372
1 2
DI 1 DI 2
GND GND
DI
Sensor 1
Sensor 2
Input x
VDR
GND
I/O status
LED (green)
Input status
24 V
24 V
PTC
GND
GND
An input filter is available for each input. The input delay can be set using register 4.13.3.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput02
The input status of digital inputs 1 to 2 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput02") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 3 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
1 DigitalInput02 0 or 1 Input status - Digital input 2
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.4 X20DI2377
The module is equipped with two inputs for 3-wire connections. Both inputs can be configured as event counters.
Gate measurement is only ever possible on one channel.
This module is designed for X20 6-pin terminal blocks. If needed (e.g. for logistical reasons), the 12-pin terminal
block can also be used.
• 2 digital inputs
• Sink connection
• 3-wire connections
• 2 counter inputs with 50 kHz counter frequency
• Gate measurement
• 24 VDC and GND for sensor supply
• Software input filter can be configured for entire module
Product ID X20DI2377
Short description
I/O module 2 digital inputs 24 VDC for 3-wire connections, special functions
General information
B&R ID code 0x1B8E
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.15 W
Internal I/O 0.82 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 10.5 mA
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-2 Green Input status of the corresponding digital input
4.13.4.5 Pinout
r e
X20 DI 2377
1 2
DI 1 DI 2
GND GND
DI
Counter/sensor
Counter/sensor
Input x
VDR
GND
24 V
PTC
24 V
Input status
I/O status
LED (green)
GND
GND
An input filter is available for each input. The input delay can be set using register 4.13.4.9.4.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Information:
The input filter is applied to digital inputs in event counter mode with software
The input filter is NOT applied in event counter mode without software.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput02
The input status of digital inputs 1 to 2 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput02") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 3 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
1 DigitalInput02 0 or 1 Input status - Digital input 2
Name:
DigitalInputLatch01 to DigitalInputLatch02
The input status of digital inputs 1 to 2 after expiration of the input filter time is mapped in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 DigitalInputLatch01 0 or 1 Input status of digital input 1 after expiration of the delay time
1 DigitalInputLatch02 0 or 1 Input status of digital input 2 after expiration of the delay time
Information:
Only one of the counter channels at a time can be used for gate measurement.
Name:
Counter01 to Counter02
This register displays the results of the individual counters.
Event counter or gate measurement (16-bit counter value) depending on operating mode.
Data type Value
USINT Counter value
Name:
ConfigOutput02 to ConfigOutput03
The individual counters can be configured in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-3 Counter frequency 0 48MHz (only with gate measurement)
1 3MHz (only with gate measurement)
1 Event counter mode with software (only with event counter
measurement)
2 187.5kHz (only with gate measurement)
3 24MHz (only with gate measurement)
4 12MHz (only with gate measurement)
5 6MHz (only with gate measurement)
6 1.5MHz (only with gate measurement)
7 750kHz (only with gate measurement)
8 375kHz (only with gate measurement)
4 Reserved 0
5 ResetCounter01 or ResetCounter02 0 No influence on the counter
1 Clear counter (at positive edge)
6-7 0 Event counter measurement
1 Gate measurement
Using this function, the positive edges of the input signal can be latched with a resolution of 200 µs. With the
"Acknowledge - input latch" function, the input latch is either reset or prevented from latching.
It works in the same way as a dominant reset RS flip-flop.
Reset x
R
R S Q Status
0 0 x Do not change
S Q Latch x 0 1 1 Set
Input x
1 0 0 Reset
Pos. edge 1 1 0 Reset
Name:
DigitalInput01LatchQuitt to DigitalInput02LatchQuitt
This register is used to reset the input latches channel by channel.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 DigitalInput01LatchQuitt 0 No influence on the latch status
1 Resets the latch status
1 DigitalInput02LatchQuitt 0 No influence on the latch status
1 Resets the latch status
2-7 Reserved -
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.5 X20DI2653
The module is equipped with 2 inputs for 3-wire connections. It is designed for an input voltage of 100 to 240 VAC.
• 2 digital inputs
• 100 to 240 VAC inputs
• 50 Hz or 60 Hz
• 3-wire connections
• 240 V coded
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DI2653
Short description
I/O module 2 digital inputs 100 to 240 VAC for 3-wire connections
General information
B&R ID code 0x2544
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
External I/O supply Yes, using software (typical threshold 85 VAC)
Power consumption
Bus 0.14 W
Internal I/O -
External I/O 0.55 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital inputs
Nominal voltage 100 to 240 VAC
Input filter
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Hardware
1 -> 0 ≤30 ms
0 -> 1 ≤40 ms
Connection type 3-wire connections
Rated frequency 47 to 63 Hz
Switching threshold
Low <40 VAC
High >79 VAC
Isolation voltage between channel and bus 1 minute 2500 VAC
Input voltage
Maximum 264 VAC
Input current
100 VAC / 60 Hz 5.0 mA
240 VAC / 50 Hz 11 mA
Sensor supply
Voltage Equal to the module supply
Summation current 2 Aeff
Short circuit protection No
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB32 terminal block separately
Order 1x X20BM12 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
Double flash External supply is too low or not connected
e+r Red on / Green single flash Invalid firmware
1-2 Green Input status of the corresponding digital input
4.13.5.5 Pinout
r e
X20 DI 2653
1 2
DI 1 DI 2
L L
N N
L L
N N
DI
Sensor 1
Sensor 2
L L
N N
L L
N N
Input status
Input x
Diagnostics status
L U ok
Voltage
monitoring
An input filter is available for each input. The input delay can be set using register 4.13.5.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput02
PowerSupply
The input status of digital inputs 1 to 2 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01", "DigitalInput02" and "PowerSupply")
or whether this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 255 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
1 DigitalInput02 0 or 1 Input status - Digital input 2
2-6 Reserved 0
7 PowerSupply 0 Supply voltage too low
1 Supply voltage >80 VAC
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.6 X20DI4371
Product ID X20DI4371
Short description
I/O module 4 digital inputs 24 VDC for 3-wire connections
General information
B&R ID code 0x1B92
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.14 W
Internal I/O 0.59 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 3-wire connections
Input circuit Sink
Input resistance Typ. 6.4 kΩ
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-4 Green Input status of the corresponding digital input
4.13.6.5 Pinout
r e
X20 DI 4371
1 2
3 4
DI 1 DI 2
GND GND
DI 3 DI 4
GND GND
DI
Sensor 1
Sensor 2
Sensor 3
Sensor 4
Input x
VDR
GND
I/O status
LED (green)
Input status
24 V
PTC
24 V
GND
GND
An input filter is available for each input. The input delay can be set using register 4.13.6.9.4.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput04
The input status of digital inputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput04") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
3 DigitalInput04 0 or 1 Input status - Digital input 4
Starting with hardware variant F0 and firmware version 801, the module has four software counters for signal
edges. Each counter register can be configured individually for falling, rising or both edges.
Name:
ResetCounter01 to ResetCounter04
Using these data points, the corresponding counter registers can be reset to 0.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 ResetCounter01 0 No change
1 Counter register 1 is reset
... ...
3 ResetCounter04 0 No change
1 Counter register 4 is reset
Information:
A counter is only reset if a positive edge is detected on the reset bit.
A continually set reset bit does not prevent counting in the counter register.
Name:
ConfigOutput02
This register is used to configure which event will be assessed on the channel input for the respective counter.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Rising edge on input 1 0 Event is not counted
1 Event increments Counter01
... ...
3 Rising edge on input 4 0 Event is not counted
1 Event increments Counter04
4 Falling edge on input 1 0 Event is not counted
1 Event increments Counter01
... ...
7 Falling edge on input 4 0 Event is not counted
1 Event increments Counter04
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.7 X20DI4372
Product ID X20DI4372
Short description
I/O module 4 digital inputs 24 VDC for 3-wire connections
General information
B&R ID code 0x22A8
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.14 W
Internal I/O 0.59 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 3-wire connections
Input circuit Source
Input resistance Typ. 6.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Sensor supply
Power consumption Max. 12.0 W 1)
Voltage Module supply minus voltage drop for short circuit protection
Voltage drop for short circuit protection at 500 mA Max. 2 VDC
Summation current 0.5 A
Short circuit protection Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-4 Green Input status of the corresponding digital input
4.13.7.5 Pinout
r e
X20 DI 4372
1 2
3 4
DI 1 DI 2
GND GND
DI 3 DI 4
GND GND
DI
Sensor 1
Sensor 2
Sensor 3
Sensor 4
Input x
VDR
GND
I/O status
LED (green)
Input status
24 V
24 V
PTC
GND
GND
An input filter is available for each input. The input delay can be set using register 4.13.7.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput04
The input status of digital inputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput04") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
3 DigitalInput04 0 or 1 Input status - Digital input 4
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.8 X20DI4375
The module is equipped with four inputs for 3-wire connections. It has open circuit and short circuit detection. This
detection can be switched off individually for each channel.
• 4 digital inputs
• Sink connection
• 3-wire connections
• 24 VDC and GND for sensor supply
• Open circuit and short circuit detection, can be switched off individually for each channel
• Software input filter can be configured for entire module
Product ID X20DI4375
Short description
I/O module 4 digital inputs 24 VDC for 3-line connections, open line and short cir-
cuit detection, detection can be switched off individually for each channel
General information
B&R ID code 0xA911
Status indicators I/O function per channel, operating state, module status, sensor line, sensor supply
Diagnostics
Module run/error Yes, using status LED and software
Open line Yes, using status LED and software
Short circuit Yes, using status LED and software
Sensor supply Yes, using status LED and software
Other channel errors Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.1 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input filter
Hardware 0.8 ms
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 3-wire connections
Input circuit Sink
Sensor supply 4 x 50mA
Open circuit and short circuit detection Yes, can be switched off individually for each channel
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during update)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
Single flash Summary status for channel error → Check the red channel LEDs 1 - 4
Double flash Module supply below lower limit
Triple flash Converter error (or transition between single and double flash)
1-4 Green Input status of the corresponding digital input
1-4 Red Off No error detected
Single flash Short circuit of respective digital input with +24 VDC
Blinking Open circuit or the measured value is below the lower switch off threshold
Single flash, Other channel error
inverse
S1 - S4 Red Off Sensor supply OK
On Sensor supply monitor has detected something
4.13.8.5 Pinout
r e
X20 DI 4375
1 2
3 4
1 2
3 4
S1 S2
S3 S4
DI 1 DI 2
GND GND
DI 3 DI 4
GND GND
DI
Sensor 1
Sensor 2
Sensor 3
Sensor 4
VDR Ri
I/O status
GND GND GND
24 V LED (green)
PTC
24 V GND
GND GND
An input filter is available for each input. The input delay can be set using register 4.13.8.13.3.1 "ConfigOutput02"
on page 981. Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
General Information
The X20DI4375 digital input module is equipped with open line and short circuit detection. To do this the sensor
needs to be connected to the necessary resistances.
Sensor connections
The resistances are connected to the sensor parallel or in series. The following values are defined for the resis-
tances:
Resistance Range
Serial 1 - 2 kΩ (10%)
Parallel 10 - 20 kΩ (10%)
Connection options
To guarantee error-free functionality of the open circuit and short circuit detection, the +24 VDC sensor supply from
the module must absolutely be used.
Sensor connections Description Detection Setting in configuration register
+24 V
Standard connection - 0
Input x
Sensor
RS
+24 V
Input x
Sensor
RS
+24 V
Input x
Sensor
+24 V
RP
Parallel resistance Open line 3
Input x
Sensor
RS
+24 V
Input x
The following errors are detected by the module and can be evaluated separately for each channel:
• Sensor line short circuit
• Sensor line open circuit
• Sensor supply
• Other channel error
4.13.8.11 Timestamp
Each converted value is given a timestamp. The time of the last conversion can be read.
4.13.8.12 Configuration
The sensor connections and therefore the sensor monitoring are set in the configuration register. Sensor monitor-
ing and the settings in the configuration register are described in section 4.13.8.9 "Open circuit and short circuit
detection" on page 978.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput02
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput04
StateDigitalInput01 to StateDigitalInput04
The input status and status of digital inputs 1 to 4 are mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits
should be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput04" and
"StateDigitalInput01" through "StateDigitalInput04") or whether this register should be displayed as an individual
USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 255 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
3 DigitalInput04 0 or 1 Input status - Digital input 4
0 No error
4 StateDigitalInput01 Short-circuit, open line, sensor monitoring error or other channel
1
error
... ...
0 No error
7 StateDigitalInput04 Short-circuit, open line, sensor monitoring error or other channel
1
error
Name:
StatusInput01 or
SC_DigitalInput01 to SC_DigitalInput04
This register indicates whether a short circuit has occurred on the individual channels.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("SC_DigitalInput01" through "SC_DigitalInput04") or
whether this register should be displayed as an individual USINT data point ("StatusInput01").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 SC_DigitalInput01 0 No error
1 Short circuit on channel 1
... ...
3 SC_DigitalInput04 0 No error
1 Short circuit on channel 4
4-7 Reserved
Name:
StatusInput02 or
WB_DigitalInput01 to WB_DigitalInput04
This register indicates whether an open line has occurred on the individual channels.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("WB_DigitalInput01" through "WB_DigitalInput04") or
whether this register should be displayed as an individual USINT data point ("StatusInput02").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 WB_DigitalInput01 0 No error
1 Open line on channel 1
... ...
3 WB_DigitalInput04 0 No error
1 Open line on channel 4
4-7 Reserved -
Name:
StatusInput03 or
SM_DigitalInput01 to SM_DigitalInput04
This register monitors the voltage supply on the individual channels.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("SM_DigitalInput01" through "SM_DigitalInput04") or
whether this register should be displayed as an individual USINT data point ("StatusInput03").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 SM_DigitalInput01 0 No error
1 Sensor supply error on channel 1
... ...
3 SM_DigitalInput04 0 No error
1 Sensor supply error on channel 4
4-7 Reserved -
Name:
StatusInput04 or
IE_DigitalInput01 to IE_DigitalInput04
This register indicates whether any other errors have occurred on the individual channels.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("IE_DigitalInput01" through "IE_DigitalInput04") or
whether this register should be displayed as an individual USINT data point ("StatusInput04").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 IE_DigitalInput01 0 No error
1 Other error on channel 1
... ...
3 IE_DigitalInput04 0 No error
1 Other error on channel 4
4-7 Reserved -
Name:
SampleTimeStamp
This register shows the timestamp of the last conversion in μs.
Data type Value
UDINT Timestamp of the last conversion in μs
Name:
ConfigOutput01
This register is used to configure short circuit monitoring and line status monitoring on the inputs.
Data type Value
UINT See bit structure
Bit structure:
Bit Name Value Information
0-3 Channel configuration - Channel 1 0 Standard
1 Serial/Parallel: R-1k in series with (R-10k parallel to the switch)
2 Parallel/Serial: R-10k parallel to (R-1k in series with switch)
3 Parallel: R-10k parallel to switch
4 Serial: R-1k in series with switch
5 to 15 Inactive
4-7 Channel configuration - Channel 2 0 to 15 See Channel configuration - Channel 1
8 - 11 Channel configuration - Channel 3 0 to 15 See Channel configuration - Channel 1
12 - 15 Channel configuration - Channel 4 0 to 15 See Channel configuration - Channel 1
The name R-1k indicates a resistance in the permitted range of 1000 Ohm to 2000 Ohm with an accuracy of 10%.
The name R-10k indicates a resistance in the permitted range of 10000 Ohm to 20000 Ohm with an accuracy
of 10%.
Information:
Inputs that are not being used should be set to the type "Standard" or "Serial" to prevent mistakes.
Configuration Possibilities:
Value Configuration Diagram Information
0 Standard +24 V Short-circuit detection and line break monitoring is not possible when using this
configuration.
Input x
1 Serial/parallel Sensor Short-circuit detection and line break monitoring is possible with this configura-
tion.
RS
+24 V
RP
Input x
2 Parallel/serial Sensor Short-circuit detection and line break monitoring is possible with this configura-
tion.
RS
+24 V
RP
Input x
3 Parallel Sensor This configuration allows line break monitoring. Short-circuit detection is not pos-
sible when using this configuration.
+24 V
RP
Input x
4 Serial Sensor This configuration allows short circuit detection. Line break monitoring is not pos-
sible when using this configuration.
RS
+24 V
Input x
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
All channels 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
All channels 150 μs
4.13.9 X20DI4653
The module is equipped with 4 inputs for 2-wire connections. It is designed for an input voltage of 100 to 240 VAC.
• 4 digital inputs
• 100 to 240 VAC inputs
• 50 Hz or 60 Hz
• 2-wire connections
• 240 V coded
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DI4653
Short description
I/O module 4 digital inputs 100 to 240 VAC for 2-wire connections
General information
B&R ID code 0x2545
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
External I/O supply Yes, using software (typical threshold 85 VAC)
Power consumption
Bus 0.17 W
Internal I/O -
External I/O 0.91 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital inputs
Nominal voltage 100 to 240 VAC
Input filter
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Hardware
1 -> 0 ≤30 ms
0 -> 1 ≤40 ms
Connection type 2-wire connections
Rated frequency 47 to 63 Hz
Switching threshold
Low <40 VAC
High >79 VAC
Isolation voltage between channel and bus 1 minute 2500 VAC
Input voltage
Maximum 264 VAC
Input current
100 VAC / 60 Hz 5.0 mA
240 VAC / 50 Hz 11 mA
Sensor supply
Voltage Equal to the module supply
Short circuit protection No
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB32 terminal block separately
Order 1x X20BM12 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
Double flash External supply is too low or not connected
e+r Red on / Green single flash Invalid firmware
1-4 Green Input status of the corresponding digital input
4.13.9.5 Pinout
r e
X20 DI 4653
1 2
3 4
DI 1 DI 2
DI 3 DI 4
L L
L L
L L
N N
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
L L
N N
Input status
Input x
Diagnostics status
L U ok
Voltage
monitoring
An input filter is available for each input. The input delay can be set using register 4.13.9.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput04
PowerSupply
The input status of digital inputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits
should be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput02" and
"PowerSupply") or whether this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
3 DigitalInput04 0 or 1 Input status - Digital input 4
4-6 Reserved 0
7 PowerSupply 0 Supply voltage too low
1 Supply voltage >80 VAC
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.10 X20DI4760
The module is used to transfer digital signals from NAMUR encoders according to EN 60947-5-6. In addition to
NAMUR encoders, normal switches can also be used.
• 4 digital inputs
• Input module for NAMUR encoders
• Open line and short circuit detection
• Each input can be used as a counter input
Product ID X20DI4760
Short description
I/O module 4 NAMUR inputs, special function
General information
B&R ID code 0x2105
Status indicators I/O function by channel, open line and short circuit detection by channel, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software
Short circuit Yes, using status LED and software
Open line Yes, using status LED and software
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Event counter
Quantity 4
Signal form Symmetric square wave pulse or corresponding minimum pulse duration 1)
Evaluation Every positive edge, cyclic counter
Counter size 8-bit
Input frequency
1 input active Max. 1600 Hz
2 inputs active Max. 1100 Hz
3 inputs active Max. 870 Hz
4 inputs active Max. 680 Hz
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
On Error or reset status
Single flash Error on at least one channel
e+r Red on / Green single flash Invalid firmware
1-4 Green Off Open line or input status log. 0
On Short circuit or input status log. 1
1-4 Red Off The sensor is ready for operation
Blinking 1Hz Open line on corresponding channel
On Short circuit on corresponding channel
4.13.10.5 Pinout
r e
X20 DI 4760
1 2
3 4
1 2
3 4
K1 + K2 +
K1 - K2 -
K3 + K4 +
K3 - K4 -
DI
NAMUR NAMUR
Sensor Sensor
Signal-
evaluation
PTC
Kx +
An input filter is available for each input. The input delay can be set using register 4.13.10.10.3.1 "ConfigOutput03"
on page 998. Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Proximity switch
+ input x
+ input x
+ input x
- input x
+ input x
6 - Counter02 USINT ●
8 - Counter03 USINT ●
10 - Counter04 USINT ●
30 - Status of channels 1 to 4 USINT ●
ShortCircuit01 Bit 0
... ...
ShortCircuit04 Bit 3
OpenLine01 Bit 4
... ...
OpenLine04 Bit 7
16 - ConfigOutput01 USINT ●
18 - ConfigOutput02 USINT ●
20 - ConfigOutput03 USINT ●
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput03
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput04
PowerSupply
The input status of digital inputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits
should be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput02" and
"PowerSupply") or whether this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 15 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
3 DigitalInput04 0 or 1 Input status - Digital input 4
4-6 Reserved 0
7 PowerSupply 0 Supply voltage too low
1 Supply voltage >80 VAC
Name:
Counter01 to Counter04
These registers cyclically count the positive edges on the individual channels.
Data type Value
USINT Positive edge counter on channel, cyclic
Name:
StatusInput01 or
ShortCircuit01 to ShortCircuit04
OpenLine01 to OpenLine04
This register indicates whether an open line or overflow has occurred on the individual channels.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits
should be set up individually as data points in the AS I/O mapping ("ShortCircuit01" through "ShortCircuit02" and
"OpenLine01" through "OpenLine02") or whether this register should be displayed as an individual USINT data
point ("DigitalInput").
Data type Value Information
USINT 0 to 3 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 ShortCircuit01 0 No error
1 Overload on channel 1
... ...
3 ShortCircuit04 0 No error
1 Overload on channel 4
4 OpenLine01 0 No error
1 Open line on channel 1
... ...
7 OpenLine04 0 No error
1 Open line on channel 4
Firmware version 802 is offered for hardware variant 7 or higher of the module. This and subsequent firmware
versions provide the user with new configuration possibilities.
Name:
OutputConfig01
This register can be used to (de)activate individual channels or just their status responses.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 1 0 Channel enabled
1 Channel disabled
... ...
3 Channel 4 0 Channel enabled
1 Channel disabled
4 Status message - Channel 1 0 Status message activated
1 Status message deactivated
... ...
7 Status message - Channel 4 0 Status message activated
1 Status message deactivated
Name:
OutputConfig02
This register can be used to specify defined replacement values for the individual channels according to the error
situation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Overload - Channel 1 0 Replacement value when overload is FALSE
1 Replacement value when overload is TRUE
... ...
3 Overload - Channel 4 0 Replacement value when overload is FALSE
1 Replacement value when overload is TRUE
4 Open line - Channel 1 0 Replacement value when open line is FALSE
1 Replacement value when open line is TRUE
... ...
7 Open line - Channel 4 0 Replacement value when open line is FALSE
1 Replacement value when open line is TRUE
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.11 X20DI6371
The module is equipped with six inputs for 1 or 2-wire connections. The X20 6-pin terminal block can be used
for universal 1-line wiring. Two-line wiring can be implemented using the 12-pin terminal block. The inputs on the
module are designed for sink connections.
• 6 digital inputs
• Sink connection
• 2-wire connections
• 24 VDC for sensor supply
• Software input filter can be configured for entire module
• 1-wire connection type with 6-pin terminal block
Product ID X20DI6371
Short description
I/O module 6 digital inputs 24 VDC for 1- or 2-wire connections
General information
B&R ID code 0x1B93
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.15 W
Internal I/O 0.88 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, can be configured between 0 and 25 ms in 0.2 ms intervals
Connection type 1- or 2-wire connections
Input circuit Sink
Input resistance Typ. 6.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Sensor supply
Voltage Module supply minus voltage drop for short circuit protection
Voltage drop for short circuit protection at 500 mA Max. 2 VDC
Summation current 0.5 A
Short circuit protection Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB06 or X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-6 Green Input status of the corresponding digital input
4.13.11.5 Pinout
r e
X20 DI 6371
1 2
3 4
5 6
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Input x
VDR
GND
I/O status
LED (green)
Input status
24 V
PTC GND
24 V
An input filter is available for each input. The input delay can be set using register 4.13.11.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput06
The input status of digital inputs 1 to 6 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput06") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 63 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
5 DigitalInput06 0 or 1 Input status - Digital input 6
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.12 X20DI6372
The module is equipped with six inputs for 1 or 2-wire connections. The X20 6-pin terminal block can be used
for universal 1-line wiring. Two-line wiring can be implemented using the 12-pin terminal block. The inputs on the
module are designed for source connections.
• 6 digital inputs
• Source connection
• 2-wire connections
• 24 VDC for sensor supply
• Software input filter can be configured for entire module
• 1-wire connection type with 6-pin terminal block
Product ID X20DI6372
Short description
I/O module 6 digital inputs 24 VDC for 1- or 2-wire connections
General information
B&R ID code 0x1B94
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.15 W
Internal I/O 0.88 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 1- or 2-wire connections
Input circuit Source
Input resistance Typ. 6.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB06 or X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-6 Green Input status of the corresponding digital input
4.13.12.5 Pinout
r e
X20 DI 6372
1 2
3 4
5 6
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
GND GND
GND GND
GND GND
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
24 V
I/O status
LED (green)
Input status
Input x
VDR
GND
GND
GND
An input filter is available for each input. The input delay can be set using register 4.13.12.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput06
The input status of digital inputs 1 to 6 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput06") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 63 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
5 DigitalInput06 0 or 1 Input status - Digital input 6
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.13 X20DI6373
The module has 6 inputs. The input circuit can be sink or source thanks to the potential-free design of the inputs.
• 6 digital inputs
• Sink/Source connection
• Software input filter can be configured for entire module
Product ID X20DI6373
Short description
I/O module 6 digital floating inputs 24 VDC
General information
B&R ID code 0xA7A2
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.15 W
Internal I/O 0.88 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input filter
Hardware ≤100 μs
Software Default 1 ms, can be configured between 0 and 25 ms in 0.2 ms intervals
Input circuit Sink or source
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-6 Green Input status of the corresponding digital input
4.13.13.5 Pinout
r e
X20 DI 6373
1 2
3 4
5 6
DI 1+ DI 1-
DI 2+ DI 2-
DI 3+ DI 3-
DI 4+ DI 4-
DI 5+ DI 5-
DI 6+ DI 6-
DI
Sensor 1
Sensor 2
Sensor 3
Sensor 4
Input x+
I/O status
LED (green)
VDR
Input status
Input x-
An input filter is available for each input. The input delay can be set using register 4.13.13.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput06
The input status of digital inputs 1 to 6 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput06") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 63 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
5 DigitalInput06 0 or 1 Input status - Digital input 6
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.14 X20DI6553
The module is equipped with 6 inputs for 1-wire connections. It is designed for an input voltage of 100 to 120 VAC.
• 6 digital inputs
• 100 to 120 VAC inputs
• 50 Hz or 60 Hz
• 1-wire connections
• 240 V coded
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DI6553
Short description
I/O module 6 digital inputs 100 to 120 VAC for 1-wire connections
General information
B&R ID code 0x256F
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
External I/O supply Yes, using software (typical threshold 85 VAC)
Power consumption
Bus 0.21 W
Internal I/O -
External I/O 0.68 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital inputs
Nominal voltage 100 to 120 VAC
Input filter
Software Default 1 ms, can be configured between 0 and 25 ms in 0.2 ms intervals
Hardware
1 -> 0 ≤30 ms
0 -> 1 ≤15 ms
Connection type 1-wire connection
Rated frequency 47 to 63 Hz
Switching threshold
Low <20 VAC
High >79 VAC
Isolation voltage between channel and bus 1 minute 1500 VAC
Input voltage
Maximum 132 VAC
Input current
120 VAC / 50 Hz 8.5 mA
120 VAC / 60 Hz 10 mA
Sensor supply
Voltage Equal to the module supply
Short circuit protection No
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB32 terminal block separately
Order 1x X20BM12 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
Double flash External supply is too low or not connected
e+r Red on / Green single flash Invalid firmware
1-6 Green Input status of the corresponding digital input
4.13.14.5 Pinout
r e
X20 DI 6553
1 2
3 4
5 6
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
L L
L L
N N
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
L L
N N
Input status
Input x
Diagnostics status
L U ok
Voltage
monitoring
An input filter is available for each input. The input delay can be set using register 4.13.14.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput06
PowerSupply
The input status of digital inputs 1 to 6 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits
should be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput02" and
"PowerSupply") or whether this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 63 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
5 DigitalInput04 0 or 1 Input status - Digital input 6
6 Reserved 0
7 PowerSupply 0 Supply voltage too low
1 Supply voltage >80 VAC
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.15 X20DI8371
The module is equipped with eight inputs for 1-wire connections. The module is designed for sink input wiring.
• 8 digital inputs
• Sink connection
• 1-wire connections
• Software input filter can be configured for entire module
Product ID X20DI8371
Short description
I/O module 8 digital inputs 24 VDC for 1-wire connections
General information
B&R ID code 0xA4AB
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.18 W
Internal I/O -
External I/O 1.2 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 1-wire connections
Input circuit Sink
Input resistance Typ. 6.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1-8 Green Input status of the corresponding digital input
4.13.15.5 Pinout
r e
X20 DI 8371
1 2
3 4
5 6
7 8
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
DI 7 DI 8
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 7 Sensor 8
Input x
VDR
GND
I/O status
LED (green)
Input status
GND
An input filter is available for each input. The input delay can be set using register 4.13.15.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput08
This register is used to indicate the input state of digital inputs 1 to 8.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput08") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 255 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input state - Digital input 1
... ...
7 DigitalInput08 0 or 1 Input state - Digital input 8
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.16 X20DI9371
The module is equipped with 12 inputs for 1-wire connections. The module is designed for sink input wiring.
• 12 digital inputs
• Sink connection
• 1-wire connections
• Software input filter can be configured for entire module
Product ID X20DI9371
Short description
I/O module 12 digital inputs 24 VDC for 1-wire connections
General information
B&R ID code 0x1B95
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.18 W
Internal I/O -
External I/O 1.75 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 1-wire connections
Input circuit Sink
Input resistance Typ. 6.4 kΩ
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1 - 12 Green Input status of the corresponding digital input
4.13.16.5 Pinout
r e
X20 DI 9371
1 2
3 4
5 6
7 8
9 10
11 12
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
DI 7 DI 8
DI 9 DI 10
DI 11 DI 12
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 7 Sensor 8
Sensor 9 Sensor 10
Sensor 11 Sensor 12
Input x
VDR
GND
I/O status
LED (green)
Input status
GND
An input filter is available for each input. The input delay can be set using register 4.13.16.10.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
100
80
Simultaneity factor [%]
0
-25 50 55 60
Ambient temperature [°C]
100
75
Simultaneity factor [%]
60
0
-25 35 40 50 60
Ambient temperature [°C]
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput12
The input status of digital inputs 1 to 12 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput12") or whether
this register should be displayed as an individual UINT data point ("DigitalInput").
Data type Value Information
UINT 0 to 4095 Packed inputs = on
USINT See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Register 0:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
7 DigitalInput08 0 or 1 Input status - Digital input 8
Register 1:
Bit Name Value Information
0 DigitalOutput09 0 or 1 Input status - Digital input 9
... ...
3 DigitalOutput12 0 or 1 Input status - Digital input 12
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.17 X20DI9372
The module is equipped with 12 inputs for 1-wire connections. The module is designed for source input wiring.
• 12 digital inputs
• Source connection
• 1-wire connections
• Software input filter can be configured for entire module
Product ID X20DI9372
Short description
I/O module 12 digital inputs 24 VDC for 1-wire connections
General information
B&R ID code 0x1D28
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.18 W
Internal I/O 1.75 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 1-wire connections
Input circuit Source
Input resistance Typ. 6.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off Module supply not connected or everything OK
e+r Red on / Green single flash Invalid firmware
1 - 12 Green Input status of the corresponding digital input
4.13.17.5 Pinout
r e
X20 DI 9372
1 2
3 4
5 6
7 8
9 10
11 12
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
DI 7 DI 8
DI 9 DI 10
DI 11 DI 12
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 7 Sensor 8
Sensor 9 Sensor 10
Sensor 11 Sensor 12
GND GND
24 V
I/O status
LED (green)
Input status
Input x
VDR
GND
An input filter is available for each input. The input delay can be set using register 4.13.17.10.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
100
80
Simultaneity factor [%]
0
-25 50 55 60
Ambient temperature [°C]
100
75
Simultaneity factor [%]
60
0
-25 35 40 50 60
Ambient temperature [°C]
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput12
The input status of digital inputs 1 to 12 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput12") or whether
this register should be displayed as an individual UINT data point ("DigitalInput").
Data type Value Information
UINT 0 to 4095 Packed inputs = on
USINT See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Register 0:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
7 DigitalInput08 0 or 1 Input status - Digital input 8
Register 1:
Bit Name Value Information
0 DigitalOutput09 0 or 1 Input status - Digital input 9
... ...
3 DigitalOutput12 0 or 1 Input status - Digital input 12
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.18 X20DID371
The module is equipped with 8 inputs for 1-wire or 2-wire connections. The module is designed for sink input wiring.
• 8 digital inputs
• Sink connection
• 2-wire connections
• 24 VDC for sensor supply
• Software input filter can be configured for entire module
Product ID X20DID371
Short description
I/O module 8 digital inputs 24 VDC for 1- or 2-wire connections
General information
B&R ID code 0xC0E7
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.13 W
Internal I/O 1.2 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, can be configured between 0 and 25 ms in 0.2 ms intervals
Connection type 1- or 2-wire connections
Input circuit Sink
Input resistance Typ. 6.4 kΩ
Sensor supply 0.5 A total current
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB1F terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
S Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
Red Off Module supply not connected or everything OK
Red on / Green single flash Invalid firmware
1-8 Green Input status of the corresponding digital input
4.13.18.5 Pinout
S 1 2
3 4
X20 DI D371
5 6
7 8
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
DI 7 DI 8
+24 VDC +24 VDC
+24 VDC +24 VDC
+24 VDC +24 VDC
+24 VDC +24 VDC
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 7 Sensor 8
Input x
I/O status
LED (green)
Input status
GND
24 V
PTC
24 V
An input filter is available for each input. The input delay can be set using register 4.13.18.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput08
This register is used to indicate the input state of digital inputs 1 to 8.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput08") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 255 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input state - Digital input 1
... ...
7 DigitalInput08 0 or 1 Input state - Digital input 8
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.13.19 X20DIF371
The module is equipped with 16 inputs for 1-wire connections. The module is designed for sink input wiring.
• 16 digital inputs
• Sink connection
• 1-wire connections
• Software input filter can be configured for entire module
Product ID X20DIF371
Short description
I/O module 16 digital inputs 24 VDC for 1-wire connections
General information
B&R ID code 0xC0E8
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Power consumption
Bus 0.18 W
Internal I/O -
External I/O 1.47 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital inputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 2.68 mA
Input filter
Hardware ≤100 μs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 1-wire connections
Input circuit Sink
Input resistance Typ. 8.9 kΩ
Simultaneousness
With 24 V I/O supply 100% 1)
With 28.8 V I/O supply 75% 1)
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating See section "Derating"
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB1F terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
For a description of the various operating modes, see section 2.11.1 "re LEDs".
Image LED Color Status Description
S Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
Red Off Module supply not connected or everything OK
Red on / Green single flash Invalid firmware
1 - 16 Green Input status of the corresponding digital input
4.13.19.5 Pinout
S 1 2
3 4
X20 DI F371
5 6
7 8
9 10
11 12
13 14
15 16
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
DI 7 DI 8
DI 9 DI 10
DI 11 DI 12
DI 13 DI 14
DI 15 DI 16
DI
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 7 Sensor 8
Sensor 9 Sensor 10
Sensor 11 Sensor 12
Sensor 13 Sensor 14
Sensor 15 Sensor 16
Input x
GND
Input status
I/O status
LED (green)
GND GND
An input filter is available for each input. The input delay can be set using register 4.13.19.9.3.1 "ConfigOutput01".
Disturbance pulses which are shorter than the input delay are suppressed by the input filter.
Input
signal
Time
Time
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
Name:
DigitalInput or
DigitalInput01 to DigitalInput16
The input status of digital inputs 9 to 16 is mapped in this register.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput16") or whether
this register should be displayed as an individual UINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 65535 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Register 0:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
7 DigitalInput08 0 or 1 Input status - Digital input 8
Register 1:
Bit Name Value Information
0 DigitalInput09 0 or 1 Input status - Digital input 9
... ...
7 DigitalInput16 0 or 1 Input status - Digital input 16
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
4.14.2 X20DM9324
This module is equipped with 8 inputs and 4 outputs for 1-wire connections. The inputs are designed for sink
connections, the outputs for source connections.
• 8 digital inputs, sink connections
• 4 digital outputs, source connections
• 1-wire connections
• Configurable software input filter for entire module
• Integrated output protection
Product ID X20DM9324
Short description
I/O module 8 digital inputs 24 VDC for 1-wire connections, 4 digital outputs 24 VDC for 1-wire connections
General information
Nominal voltage 24 VDC
B&R ID code 0x20B9
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED and software (output error status)
Power consumption
Bus 0.21 W
Internal I/O 0.5 W
External I/O 1.17 W
Additional power dissipation caused by the actua- +0.21
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital inputs
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Typ. 3.75 mA
Input filter
Hardware ≤100 µs
Software Default 1 ms, configurable between 0 and 25 ms in 0.2 ms intervals
Connection type 1-wire connections
Input circuit Sink
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
Single flash Warning/Error on an I/O channel. Level monitoring for digital outputs has been
triggered.
e+r Red on / Green single flash Invalid firmware
1-8 Green Input status of the corresponding digital input
1-4 Orange Output status of the corresponding digital output
4.14.2.5 Pinout
r e
X20 DM 9324
1 2
3 4
5 6
7 8
1 2
3 4
DI 1 DI 2
DI 3 DI 4
DI 5 DI 6
DI 7 DI 8
DO 1 DO 2
DO 3 DO 4
DM
Sensor 1 Sensor 2
Sensor 3 Sensor 4
Sensor 5 Sensor 6
Sensor 7 Sensor 8
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Input x
VDR
GND
I/O status
LED (green)
Input status
GND
24 V
High-side
Output status
Logic
Output x
VDR
GND
I/O status
Output LED (orange)
monitoring
GND
100 H 10 H
1000
1H
Coil resistance
Coil inductance
[Ω] 100 mH
100
10 mH
50
0.1 1 10 100
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
Unfiltered
The input state is collected with a fixed offset to the network cycle and transferred in the same cycle.
Filtered
The filtered status is collected with a fixed offset to the network cycle and transferred in the same cycle. Filtering
takes place asynchronously to the network in multiples of 200 µs with a network-related jitter of up to 50 µs.
Name:
DigitalInput or
DigitalInput01 to DigitalInput08
This register is used to indicate the input state of digital inputs 1 to 8.
Function model 0 - Standard only:
The "packed inputs" setting in the AS I/O configuration is used to determine whether all of this register's bits should
be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput08") or whether
this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 255 Packed inputs = on
See bit structure Packed inputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input state - Digital input 1
... ...
7 DigitalInput08 0 or 1 Input state - Digital input 8
Name:
ConfigOutput01
This register can be used to specify the filter value for all digital inputs.
The filter value can be configured in steps of 100 μs. It makes sense to enter values in steps of 2, however, since
the input signals are sampled every 200 μs.
Data type Value Filters
USINT 0 No software filter
2 0.2 ms
... ...
250 25 ms - Higher values are limited to this value
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput04
The status of digital outputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
3 StatusDigitalOutput04 0 Channel 04: No error
1 Channel 04: Short circuit or overload
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Without filtering 100 μs
With filtering 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Without filtering 100 μs
With filtering 200 μs
DO
1A 0.6 A
Actuator 2
Actuator 1
1.2 A 1A
Actuator 4
Actuator 3
DO
0.5 A 0.2 A
0.3 A 0.4 A
Actuator 1
Actuator 2
Actuator 4
Actuator 3
L L
N N
Figure 315: Power dissipation calculation when specifying the residual voltage
Theoretically highest power dissipation resulting from actuators:
Number of outputs * residual voltage * nominal output current = power dissipation
4 * 1.6 V * 0.5 A = 3.2 W
Power dissipation resulting from actuators in this example:
1.6 V * (0.5 A + 0.2 A + 0.3 A + 0.4 A) = 2.24 W
DO
3A
3A
230 VAC
Figure 316: Power dissipation calculation when specifying the contact resistance
Theoretically highest power dissipation resulting from actuators:
Number of outputs * contact resistance * nominal output current2 = power dissipation
4 * 15 mΩ * 5 A2 = 1.5 W
Power dissipation resulting from actuators in this example:
15 mΩ * (3 A2 + 3 A2 ) = 0.27 W
4.15.3 X20DO2321
The module is equipped with 2 outputs for 3-wire connections. It is designed for X20 6-pin terminal blocks. If needed
(e.g. for logistical reasons), the 12-pin terminal block can also be used.
• 2 digital outputs
• Sink connection
• 3-wire connections
• 24 VDC and GND for actuator supply
• Integrated output protection
• OSP mode
Product ID X20DO2321
Short description
I/O module 2 digital outputs 24 VDC for 3-wire connections
General information
B&R ID code 0x22B3
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.13 W
Internal I/O 0.3 W
Additional power dissipation caused by the actua- +0.06
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design FET negative switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 1.0 A
Connection type 3-wire connections
Output circuit Sink
4.15.3.5 Pinout
r e
X20 DO 2321
1 2
DO 1 DO 2
GND GND
DO
Actuator 1
Actuator 2
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
I/O status
LED (orange)
Low-side
Output status Output x
Logic
VDR
GND
Output
monitoring GND
24 V
GND 24 V
PTC
GND
GND
28.8 V
1H
24.0 V
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput02
This register is used to store the switching state of digital outputs 1 to 2.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 3 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
1 DigitalOutput02 0 Digital output 02 reset
1 Digital output 02 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput02
The status of digital outputs 1 to 2 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 3 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
1 StatusDigitalOutput02 0 Channel 02: No error
1 Channel 02: Short circuit or overload
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.4 X20DO2322
The module is equipped with 2 outputs for 3-wire connections. It is designed for X20 6-pin terminal blocks. If needed
(e.g. for logistical reasons), the 12-pin terminal block can also be used.
• 2 digital outputs
• Source connection
• 3-wire connections
• 24 VDC and GND for actuator supply
• Integrated output protection
• OSP mode
Product ID X20DO2322
Brief description
I/O module 2 digital outputs 24 VDC for 3-wire connections
General information
B&R ID code 0x1B96
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.13 W
Internal I/O 0.33 W
Additional power dissipation caused by the actua- +0.1
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 1.0 A
Connection type 3-wire connections
Output circuit Source
4.15.4.5 Pinout
r e
X20 DO 2322
1 2
DO 1 DO 2
GND GND
DO
Actuator 1
Actuator 2
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
High-side
Output status
Logic
Output x
GND
I/O status
Output LED (orange) 24 V
PTC
monitoring
24 V
GND
GND
100 mH
Coil resistance Coil inductance
[Ω]
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput02
This register is used to store the switching state of digital outputs 1 to 2.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 3 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
1 DigitalOutput02 0 Digital output 02 reset
1 Digital output 02 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput02
The status of digital outputs 1 to 2 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 3 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
1 StatusDigitalOutput02 0 Channel 02: No error
1 Channel 02: Short circuit or overload
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.5 X20DO2623
The module is a digital output module that is equipped with 2 SSR outputs with zero cross-over switches and uses
3-line connections. The module is also equipped with integrated full-wave control. The supply (L and N) is fed
directly to the module.
• 2 digital outputs
• Outputs with integrated snubber circuit
• Outputs with 100 to 240 VAC
• L switching
• 50 Hz or 60 Hz
• 3-wire connections
• Integrated full-wave control
• 240 V coding
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO2623
Brief description
I/O module 2 digital SSR outputs 100 - 240 VAC, 3-wire connections
General information
B&R ID code 0x267B
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software status
Outputs Yes, with status LED
Power consumption
Bus 0.35 W
Internal I/O -
External I/O 0.38 W
Additional power dissipation caused by the actua- +3.0
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design SSR
Wiring L switching
Nominal voltage 100 to 240 VAC
Rated frequency 47 to 63 Hz
Nominal output current 1.0 A
Total nominal current 1.0 A
Surge current 40 A (20 ms), 10 A (1 s)
Connection type 3-wire connections
Zero crossover switches Yes
Leakage current Max. 10 mA at 240 V
Residual voltage (on-state voltage) 1.5 V
Switching delay
At 50 Hz
0 -> 1 ≤ 11 ms
1 -> 0 ≤ 11 ms
At 60 Hz
0 -> 1 ≤ 9.3 ms
1 -> 0 ≤ 9.3 ms
Isolation voltage between channel and bus Tested at 2500 VAC
Voltage monitoring L - N No
Overvoltage protection between L and N Yes
Output voltage
Minimum 80 VAC
Maximum 264 VAC
Protective circuit
External Generally a varistor or fuse
Internal Snubber circuit (RC element)
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating See section "Derating"
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
4.15.5.5 Pinout
r e
X20 DO 2623
1 2
DO 1 DO 2
L L
N N
L L
N N
DO
L L
N N
Actuator Actuator
L L
N N
SSR
Output x
Output status
zc
I/O status
(LED orange) electrical
separation
L
Zero External
power supply
N
Full-wave control is used to control power for electrical power consumers that are operated with AC voltage. Tem-
perature control is a typical application
Unlike phase-angle control, the sine wave oscillation form of the mains voltage is not changed during full-wave
control. This significantly reduces system perturbation.
The output voltage (channel) is switched on and off at a certain ratio. This switches the multi-cycle packets. A
multi-cycle packet consists of a number of complete sine waves throughout a cycle. The relationship between
the power-on duration and the cycle duration results in the desired effect of reduced power consumption by the
connected power consumer.
With the full-wave control that is integrated in the module, a maximum of 24 full waves can be provided on the
outputs per cycle. Control takes place in 4% steps.
Settings Full waves
SW% % 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
0 0
4 ●
8 ● ●
12 ● ● ●
16 ● ● ● ●
20 ● ● ● ● ●
24 25 ● ● ● ● ● ●
28 ● ● ● ● ● ● ●
32 ● ● ● ● ● ● ● ●
36 ● ● ● ● ● ● ● ● ●
40 ● ● ● ● ● ● ● ● ● ●
44 ● ● ● ● ● ● ● ● ● ● ●
48 50 ● ● ● ● ● ● ● ● ● ● ● ●
52 ● ● ● ● ● ● ● ● ● ● ● ● ●
56 ● ● ● ● ● ● ● ● ● ● ● ● ● ●
60 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
64 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
68 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
72 75 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
76 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
80 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
84 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
88 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
92 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
96 100 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
1 cycle
(24 full waves)
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
2) Firmware version 816 and up.
The output status is transferred to the control switch asynchronously to the connected network. The outputs switch
on when the voltage crosses zero and switch off when the current crosses zero.
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput02
This register is used to store the switching state of digital outputs 1 to 2.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 3 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
1 DigitalOutput02 0 Digital output 02 reset
1 Digital output 02 set
Information:
The states in this register are only applied when the channels are set to DIGITAL in "Setting the output
configuration ".
When using the setting "packed outputs" ALL channels must be set to DIGITAL. Mixed operation is
not possible.
The output value is transferred to the control circuit in sync with the connected power mains according to the
firing pattern table (see "Integrated full-wave control"). The analog value is output with a resolution of ~4% over a
duration of 24 complete waves. Values > 96% result in full control. Changes to the output value within an interval
are applied after the next zero crossover.
4.15.5.9.4.1 Setting the output value from the firing pattern table
Name:
AnalogOutput01 to AnalogOutput02
These registers are used to set the output value from the firing pattern table.
Values between 0 and 100 correspond to the output value for the respective channel in percent. Values above
100 correspond to 100%.
Data type Value
USINT 0 to 100
Information:
The states in these registers are only applied when the channels are set to ANALOG in Setting the
output configuration .
Name:
Output configuration 1 - 2 ConfigOutput01
Each channel can be configured for either "digital" or "analog" operation in this register. The corresponding
DigitalOutput or AnalogOutput registers must be written depending on the setting.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital register is used
0 Channel 1
1 Analog register is used
0 Digital register is used
1 Channel 2
1 Analog register is used
2-7 0
Name:
ShiftOutput01 to ShiftOutput02
To prevent load peaks due to simultaneous switching of outputs, this register can be used to shift the switching
pattern by a number of full waves. Due to the hardware used, it is not possible to shift by less than a full wave.
Values higher than 23 are limited to 23.
Data type Value Information
USINT 0 No shift
1 to 23 Size of the shift in number of full waves
Example
Set 0 on Channel 1 and 1 on Channel 2. With the same control value (see "Integrated full-wave control") this delays
the switching pattern of Channel 2 by one full wave.
Name:
ZeroCrossingInput
ZeroCrossingStatus
StatusInput01
Zero crossing detection uses a fixed filter time of 1 ms and a scanning frequency of 10 kHz. When a missing or too
short period is detected, control is switched off until at least 2 periods are detected correctly, and the status flag
is set accordingly. Control is offset by 2 ms from the negative half-wave until the next zero crossover is detected
correctly or another error occurs. This is normally at least one complete wave.
Monitoring is activated at the first zero crossover after being switched on.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("ZeroCrossingInput" through "ZeroCrossingStatus") or
whether this register should be displayed as an individual USINT data point ("StatusInput01").
Data type Value Information
USINT 0 to 17 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 ZeroCrossingInput1) 0 Signal during the negative half-wave
1 Signal during the positive half-wave
1-3 0
4 ZeroCrossingStatus 0 No error
1 Zero crossover failed
5-7 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Digital mode 100 μs
Digital and analog mode 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Digital mode 100 μs
Digital and analog mode 150 μs
4.15.6 X20DO2633
The module is a digital output module with phase-angle control that is equipped with 2 Triac outputs using 3-line
connections. The supply (L and N) is fed directly to the module.
• 2 digital outputs
• Outputs with integrated snubber circuit
• Outputs with 12 to 240 VAC
• L switching
• Zero-crossing detection
• Phase-angle control
• Open-circuit detection for each channel
• Negative half-waves can be switched off
• 50 Hz or 60 Hz
• 3-wire connections
• 240 V coding
• OSP mode
• Frequency mode
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO2633
Brief description
I/O module 2 digital outputs 12-240 VAC for 3-wire connections
General information
B&R ID code 0xAC39
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED and software
Power consumption
Bus 0.6 W
Internal I/O -
External I/O -
Additional power dissipation caused by the actua- +6 W
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design Triac
Wiring L switching
Nominal voltage 12 to 240 VAC
Rated frequency 47 to 63 Hz
Nominal output current 2.0 A
Total nominal current 4.0 A
Maximum current
Output current 2.5 A
Summation current 5.0 A
Connection type 3-wire connections
Zero-crossing detection Yes
Minimum holding current IH 15 mA
Leakage current 50 Hz: Max. 2.0 mA at 240 V
60 Hz: Max. 2.4 mA at 240 V
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off Module supply not connected
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
Flickering (ap- Module is in OSP state
prox. 10 Hz)
e Red Off Module supply not connected or everything OK
On Error or reset status
Single flash Zero cross-over signal has dropped out
e+r Red on / Green single flash Invalid firmware
1-2 Orange Control status of the corresponding digital output
4.15.6.5 Pinout
The following points must be taken into consideration when wiring the module:
• For thermal reasons, wires with a cross-section ≥1.5 mm² must be used to wire the module.
• The neutral return lines for the outputs must be wired to the terminal block separately for each channel
and must not be bypassed in the field.
• A line filter must be used for the 240 V supply that provides ≥40 dB attenuation at 150 kHz and works
up to 5 MHz.
r e
X20 DO 2633
1 2
DO 1 DO 2
L L
N N
L L
N N
2-wire connections
DO
Actuator Actuator
T 10 A
L L
N N
3-wire connections
DO
L L
N N
Actuator Actuator
T 10 A
L L
N N
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
DO 1
Output status 1
VDR
N
I/O status
(LED orange)
DO 2
Output status 2
VDR
N
I/O status
(LED orange)
1) See also section 4.15.6.13 "Operation with inductive loads" on page 1096
2) Meeting the limit values specified in the standards EN 61131, EN 55011 and EN 55022 (each Class A) requires installation of a line filter in the 240 V supply
line. Line filters such as the Schaffner FN 2412‐8‐44 can be used.
If periodic ground transients occur on the supply lines (as can occur with upstream inverters), it is necessary to use an asymmetric filter that keeps these
types of changes in potential below a few volts (e.g. "Sinus Plus" from Schaffner) in addition to the symmetric filter.
4.15.6.10 Derating
2.5
1.875
Output current [A]
0
-25 25 35 50 60
Ambient temperature [°C]
The digital output module was designed for phase control of resistive and and inductive loads. The triac outputs
do not have short circuit protection. The integrated open-circuit detection makes it possible to recognize defects
on the load or the cabling (see 4.15.6.12 "Open line detection" on page 1095).
The module is equipped with internal zero-crossing detection. Zero-crossing detection is the basis for a software
PLL that generates 200 times the zero-crossing frequency. The output signal of the PLL is the base timer for the
PWM outputs in both digital and analog mode.
Upon detection of lost periods or periods that are too short, control to the outputs is cut until the PLL is tuned
correctly. The tuning procedure can take several seconds. In addition, the "ZeroCrossingStatus" bit is set and the
error LED enabled (valid frequency range for the supply is 45 to 65 Hz).
Information:
The jitter of the output signals generated by the PLL and communication can reach 0.5%.
The module is equipped with open-circuit detection. Note that open-circuit detection only works when the output
is enabled. An open-circuit will not be detected if the output is turned off.
In addition, open-circuit detection is restricted or doesn't work at all for inductive loads. This depends on the induc-
tance of the load and should be determined beforehand, if necessary.
As inherent to its functional principal, the triac output is cleared when the current crosses zero. Because zero
crossing for current is delayed with inductive loads, it is possible that the triac will be fired again even though it is
not completely cleared at higher output values (between 50 and 100% depending on the inductance of the load).
In this case, a full-wave is output. This causes the available control range (0 to 95%) to be changed.
For open line detection (LowCurrentStatus), a pause in control is required where the triac is not permitted to be
fired. The full wave that is created with inductive loads causes open line detection to be triggered even though
the load on the output is sufficient.
This behavior can be used to detect the full wave and properly adjust the control range (Example: If open line
detection is triggered at a control value of 70%, that means that 0-70% corresponds to 0-100% output).
Input voltage
Output voltage
Output current
Internal firing signal for the triac
CfO_SwitchOffValue in %
With inductive loads, a suitable varistor must be provided between the output DO x and the phase L (e.g. a varistor
with 275 VRMS at 240 VAC).
DO
Actuator
VDR
L L
N N
The only difference between function model 2 and function model 0 is the possibility of generating half-wave pat-
terns in various frequencies. Register 18 "CfO_Frequency" is an additional register for this.
Register Name Data type Read Write
Cyclic Non-cyclic Cyclic Non-cyclic
Configuration - General
4 AnalogOutput01 USINT ●
6 AnalogOutput02 USINT ●
18 CfO-Frequency UINT ●
20 CfO_SwitchOffValue1 USINT ●
22 CfO_SwitchOffValue2 USINT ●
28 CfO_OutputConfig USINT ●
29 CfO_OutputTolerance USINT ●
Communication
2 DigitalOutput USINT ●
DigitalOutput01 Bit 0
DigitalOutput02 Bit 2
30 StatusInput01 USINT ●
LowCurrentStatus1 Bit 0
LowCurrentStatus2 Bit 1
ZeroCrossingInput Bit 4
ZeroCrossingStatus Bit 7
1) The offset specifies the position of the register within the CAN object.
The digital output module was designed for phase control of resistive and inductive loads. The triac outputs do
not have short circuit protection, but have open line detection that can be used to find defects in the consumer
or the wiring.
The module is equipped with internal zero-crossing detection. Zero crossing detection is the basis for a software
PLL that generates 200 times the zero crossing frequency. The output signal of the PLL is the base timer for the
2 PWM outputs in both digital and analog mode.
Upon detection of lost periods or periods that are too short, control of the outputs is cut until the PLL is tuned
correctly (can take several seconds). In addition, the "ZeroCrossingStatus" bit is set and the Error LED is enabled
(valid frequency range for the supply is 45 to 65 Hz).
Information:
The jitter of the output signals generated by the PLL and communication can reach 0.5%.
The output state of the outputs defined as digital is transferred to the output ports of the control switch in sync with
the connected power mains. The switch-on state is applied when the voltage crosses zero on the positive half-
wave and the switch-off state at the zero crossing for current in each half wave.
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput02
This register is used to store the switching state of digital outputs 1 to 2.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 3 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
1 DigitalOutput02 0 Digital output 02 reset
1 Digital output 02 set
Information:
The states in these registers are only applied when the channels are set to DIGITAL in "Configuration
of the output channels".
When using the setting "packed outputs" ALL channels must be set to DIGITAL. Mixed operation is
not possible.
The output value of the outputs defined as analog outputs (unit percent) is switched through to the control ports in
sync with power mains. The analog value is output to the TRIAC control port in the range between (output value
> SwitchOffValue) and (output value <= 95%) with a resolution of 1%.
A short triac switch-on delay is required for open line detection. Therefore even with output values >= 96%, there
is a a small pause in control.
Changes to the output value are applied at the next positive half-wave
Triac switch-on delay
for open line detection
U
1/f
Name:
AnalogOutput01 to AnalogOutput02
These registers are used to set the commutation angle for phase angle control.
Values between 0 and 100 correspond to the output value for the respective channel in percent. Values above
100 correspond to 100%.
Data type Value
USINT 0 to 100
Information:
The commutation angle for phase angle control set in these registers are only applied when the chan-
nels are set to ANALOG in "Configuration of the output channels".
Name:
CfO_Frequency
This register can only be used in function model 2 - Frequency mode and makes it possible to configure the output
of half-wave patterns in various frequencies. The commutation angle of the outputs is not affected by this. The
following frequency patterns can be configured:
• 100 half-waves
100 half-waves
• 50 half-waves
50 half-waves
• 33 half-waves
33 half-waves
• 25 half-waves
25 half-waves
With multichannel operation, the second channels should be operated with delayed half-waves in order to ensure
that the load is placed evenly on the module.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Channel 1 0000 100 half-waves/second
0001 50 half-waves/second
0010 25 half-waves/second
0011 33 half-waves/second
0101 50 half-waves/second delayed by 1 half-wave
0110 25 half-waves/second delayed by 2 half-waves
0111 33 half-waves/second delayed by 1 half-wave
4-7 Channel 2 0000 to 0111 See channel 1
8 - 15 Reserved -
Information:
This function is available beginning with firmware version 940. This can be included beginning with
hardware variant 8.
Name:
Cfo_SwitchOffValue1 and Cfo_SwitchOffValue2
This register defines how far in front of the zero cross-over the internal control signal for the TRIAC is switched off.
Increasing this value may be necessary in order to prevent unwanted firing of the TRIAC in the event of a slight
disturbance in the mains frequency.
With smaller loads, it is important to ensure that this switch off value is not set to large (too early) to prevent
switching off prematurely.
The triac can of course only be fired before the set switch-off time.
"SwitchOffValue" in the AS I/O configuration.
1/f
Triac
Control signal
Switch-off value
5 to 50%
Name:
Cfo_OutputConfig
The configuration of the output channels are stored in this register.
"Output type digital/analog" and "Output type full/half wave" in the AS I/O configuration
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 1: Digital / Analog output 0 Output channel 1 is defined as a digital output. The output status
is defined using bit 0 in the DigitalOutput 1 - 2 register.
1 Output channel 1 is defined as an analog output. The output
status is defined using the AnalogOutput01 register.
1 Channel 2: Digital / Analog output 0 Output channel 2 is defined as a digital output. The output status
is defined using bit 0 in the DigitalOutput 1 - 2 register.
1 Output channel 2 is defined as an analog output. The output
status is defined using the AnalogOutput02 register.
2-3 Reserved -
4 Channel 1: Full-wave / half-wave control1) 0 Full-wave control on output channel 1
1 Negative half-wave on output channel 1 is suppressed.
5 Channel 2: Full-wave / half-wave control1) 0 Full-wave control on output channel 2
1 Negative half-wave on output channel 2 is suppressed.
6-7 Reserved -
Name:
CfO_OutputTolerance
This register can be used to set the switching behavior of the trigger. After the number of zero-crossing errors
configured in Bit 0 to 4, the output is switched off for at least 3 periods. This is followed by synchronization with
the zero signal according to Bit 7.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-4 Trigger for Resync 0 to 30 Number of zero-crossover errors
5-6 Reserved -
7 Fast settling 0 Fast synchronization
1 PLL synchronization
Fast synchronization
With this option, the trigger point is closed-loop controlled after each individual zero-crossover and input jitter.
• Advantage: Increased tolerance and faster response to deviations in mains frequency
• Disadvantage: Increased switch-on jitter for firing signal by zero cross signal ±100 µSec
PLL synchronization
With this option the intervals between zero cross-overs are measured and the PLL frequency is updated accord-
ingly.
• Advantage: Jitter-free firing signal
• Disadvantage: When the output is switched off, additional measurement phases are required before it can
be switched back on.
Information:
This function is available starting with Firmware version 928. This can be installed with hardware ver-
sion 8 and hardware revision B4 or higher.
Name:
LowCurrentStatus1 through LowCurrentStatus2
ZeroCrossingInput
ZeroCrossingStatus
StatusInput01
The operating status of the outputs is mapped in this register.
In order to do determine the "LowCurrentStatus", the system checks if there is a neutral connection from the output
via the consumer shortly before each triac firing.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("LowCurrentStatus1" through "ZeroCrossingStatus")
or whether this register should be displayed as an individual USINT data point ("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 LowCurrentStatus1 0 Current flow on activated output 1
1 No current flow on activated output 1
1 LowCurrentStatus2 0 Current flow on activated output 2
1 No current flow on activated output 2
2-3 Reserved -
4 ZeroCrossingInput 0 Zero cross signal during the negative half-wave
1 Zero cross signal during the positive half-wave
5-6 Reserved -
7 ZeroCrossingStatus 0 Zero cross signal OK
1 Zero cross signal has dropped out
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 OSPValid 0 Request OSP operation (after initial start or module in Standby)
1 Request normal operation
1-7 Reserved 0
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
Name:
CfgOSPValue01 to CfgOSPValue02
This register contains the analog output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT 0 to 100
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
All channels 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
All channels 150 μs
4.15.7 X20DO2649
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO2649
Brief description
I/O module 2 digital outputs 30 VDC / 230 VAC, outputs are single-channel isolated
General information
B&R ID code 0x20DA
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED
Power consumption
Bus 0.45 W
Internal I/O -
Additional power dissipation caused by the actua- +2.5
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design Relay / Changeover contact
Channels are single-channel isolated
4.15.7.5 Pinout
r e
X20 DO 2649
1
2
NC 1 NC 1
COM 1 COM 1
NO 1 NO 1
NC 2 NC 2
COM 2 COM 2
NO 2 NO 2
DO
230 VAC
NC x
COM x
NO x
Output status
I/O status
LED (orange)
100
50
250 VAC / 30 VDC resistive (cos ɸ = 1)
Switching operations (x10⁴)
20
250 VAC cos ɸ = 0.7
10
30 VDC τ = 7 ms
1
0 2 4 6 8 10 12 14
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput02
This register is used to store the switching state of digital outputs 1 to 2.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 3 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
1 DigitalOutput02 0 Digital output 02 reset
1 Digital output 02 set
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.8 X20DO4321
Product ID X20DO4321
Brief description
I/O module 4 digital outputs 24 VDC for 3-wire connections
General information
B&R ID code 0x22B4
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.16 W
Internal I/O 0.49 W
Additional power dissipation caused by the actua- +0.12
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design FET negative switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 2.0 A
Connection type 3-wire connections
Output circuit Sink
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
4.15.8.5 Pinout
r e
X20 DO 4321
1 2
3 4
DO 1 DO 2
GND GND
DO 3 DO 4
GND GND
DO
Actuator 1
Actuator 2
Actuator 4
Actuator 3
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
I/O status
LED (orange)
Low-side
Output status Output x
Logic
VDR
GND
Output
monitoring GND
24 V
GND 24 V
PTC
GND
GND
28.8 V
1H
24.0 V
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput04
The status of digital outputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
3 StatusDigitalOutput04 0 Channel 04: No error
1 Channel 04: Short circuit or overload
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.9 X20DO4322
Product ID X20DO4322
Brief description
I/O module 4 digital outputs 24 VDC for 3-wire connections
General information
B&R ID code 0x1B97
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.16 W
Internal I/O 0.49 W
Additional power dissipation caused by the actua- +0.21
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 2.0 A
Connection type 3-wire connections
Output circuit Source
4.15.9.5 Pinout
r e
X20 DO 4322
1 2
3 4
DO 1 DO 2
GND GND
DO 3 DO 4
GND GND
DO
Actuator 1
Actuator 2
Actuator 4
Actuator 3
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
High-side
Output status
Logic
Output x
GND
I/O status
Output LED (orange) 24 V
PTC
monitoring
24 V
GND
GND
100 mH
Coil resistance Coil inductance
[Ω]
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput04
The status of digital outputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
3 StatusDigitalOutput04 0 Channel 04: No error
1 Channel 04: Short circuit or overload
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.10 X20DO4331
The module is equipped with 4 outputs for 3-wire connections. The rated output current is 2 A.
• 4 digital outputs with 2 A
• Sink connection
• 3-wire connections
• 24 VDC and GND for actuator supply
• Integrated output protection
• OSP mode
Product ID X20DO4331
Brief description
I/O module 4 digital outputs 24 VDC for 3-wire connections
General information
B&R ID code 0x22B5
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.16 W
Internal I/O 0.49 W
Additional power dissipation caused by the actua- +0.56
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design FET negative switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 2.0 A
Total nominal current 8.0 A
Connection type 3-wire connections
Output circuit Sink
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
4.15.10.5 Pinout
r e
X20 DO 4331
1 2
3 4
DO 1 DO 2
GND GND
DO 3 DO 4
GND GND
DO
Actuator 1
Actuator 2
Actuator 4
Actuator 3
+24 VDC +24 VDC
GND GND
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
I/O status
LED (orange)
Low-side
Output status Output x
Logic
VDR
GND
Output
monitoring GND
24 V
GND 24 V
PTC
GND
GND
100 100 mH
10 mH
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
28.8 V
24.0 V
100 mH
100
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
The outputs of the X20DO4331 can handle up to 2A. To ensure optimal use of the module, it is important to assign
the channels properly, and to keep in mind a potential derating.
The following table provides an overview of the number of fully used channels, the resulting best distribution, and
a potential derating.
Number of channels using 2A Division Derating
1 Any No
2 Possible divisions: No
1, 3
2, 4
3 Possible divisions: No
1, 2, 4
1, 3, 4
4 1-4 All channels
1.34
Output current [A]
0
-25 35 60
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput04
The status of digital outputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
3 StatusDigitalOutput04 0 Channel 04: No error
1 Channel 04: Short circuit or overload
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.11 X20DO4332
The module is equipped with 4 outputs for 3-wire connections. The rated output current is 2 A.
• 4 digital outputs with 2 A
• Source connection
• 3-wire connections
• 24 VDC and GND for actuator supply
• Integrated output protection
• OSP mode
Product ID X20DO4332
Brief description
I/O module 4 digital outputs 24 VDC for 3-wire connections
General information
B&R ID code 0x1B9C
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.16 W
Internal I/O 0.49 W
Additional power dissipation caused by the actua- +1.60 (Rev. <H0: +2.24)
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 2.0 A
Total nominal current 8.0 A (Rev. <H0: 4.0 A)
Connection type 3-wire connections
Output circuit Source
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
4.15.11.5 Pinout
r e
X20 DO 4332
1 2
3 4
DO 1 DO 2
GND GND
DO 3 DO 4
GND GND
DO
Actuator 1
Actuator 2
Actuator 4
Actuator 3
+24 VDC +24 VDC
GND GND
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
High-side
Output status
Logic
Output x
GND
I/O status
Output LED (orange) 24 V
PTC
monitoring
24 V
GND
GND
28.8 V
24.0 V
100 mH
100
Coil resistance Coil inductance
[Ω]
10 mH
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
28.8 V
24.0 V
100 mH
100
Coil resistance Coil inductance
[Ω]
10 mH
10
0.1 1 10 100
max. Schaltspiele / Sekunde
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
The outputs of the module can handle up to 2 A. With a total current of 4 A, no more than 2 channels are operable
at full load. Correct channel assignments are important for achieving optimal use of the module.
The following table provides an overview of the number of fully used channels and the resulting best distribution.
Number of channels using 2A Division
1 Any
2 The following channel numbers can be assigned:
1, 3
1, 4
2, 4
Information:
This section is only valid up to Rev. H0.
4.15.11.11 Derating
When operated at temperatures above 55°C, the power consumption of the modules to the left and right of this
module must not exceed 1.15 W.
8
6
Total current [A]
0
-25 50 60
Information:
This section is only valid for Rev. H0 and higher.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput04
The status of digital outputs 1 to 4 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
3 StatusDigitalOutput04 0 Channel 04: No error
1 Channel 04: Short circuit or overload
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.12 X20DO4529
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO4529
Brief description
I/O module 4 digital outputs 30 VDC / 115 VAC, outputs are single-channel isolated
General information
B&R ID code 0x20D9
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED
Power consumption
Bus 0.8 W
Internal I/O -
Additional power dissipation caused by the actua- +0.3
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design Relay / Changeover contact
Channels are single-channel isolated
4.15.12.5 Pinout
r e
X20 DO 4529
1 2
34
NC 1 NC 2
COM 1 COM 2
NO 1 NO 2
NC 3 NC 4
COM 3 COM 4
NO 3 NO4
DO
NC x
COM x
NO x
Output status
I/O status
LED (orange)
0.5
DC resistive
0.3
0.2
0.1
1 2 5 10 20 30 50 100 200
70
50
40
30
30 VD
C
re
si s
20
12
t iv
e
5V
DC
re
10
si s
t iv
e
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.13 X20DO4613
The module is a digital output module that is equipped with 4 opto-triac outputs using phase-angle control. L and
N are fed to the module for zero-crossing detection.
The 4 outputs are electrically isolated from one another and are used for controlling external power triacs or non-
parallel thyristors.
• 4 digital outputs
• Controls external power triacs or non-parallel thyristors
• Outputs with 48 - 240 VAC
• 50 Hz or 60 Hz
• Outputs electrically isolated from one another
• Phase-angle control
• Zero-crossing detection
• Negative half-waves can be switched off
• 2-wire connections
• 240 V coding
• OSP mode
• Frequency mode
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO4613
Short description
I/O module 4 digital outputs for controlling external power triacs or non-parallel thyristors
General information
B&R ID code 0xAD05
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED
Power consumption
Bus 0.8 W
Internal I/O -
External I/O -
Additional power dissipation caused by the actua- +1 W
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design Opto-triac
Wiring N.O. contact
Nominal voltage 48 to 240 VAC
Rated frequency 47 to 63 Hz
Rated current at 25°C
Nominal output current 80 mA
Total nominal current 320 mA
Current over entire temperature range
Output current 50 mA
Summation current 200 mA
Connection type 2-wire connections
Zero-crossing detection Yes
Holding current Max. 3.5mA
Leakage current Max. 1.5 mA (per channel)
Residual voltage (on-state voltage) Max. 3V
Phase-angle control
Range 5 to 95%
Resolution 1%
Accuracy (60 to 240 VAC) <100 μs
Voltage monitoring L - N No
Recommended cabling Twisted pair cabling to the terminal pairs
Cable length Max. 10 m
Overvoltage protection between L and N Yes
Isolation voltage
Channel - Bus Tested at 2300 VAC
Channel - Channel Tested at 2300 VAC
Protective circuit
External General protection
Internal Snubber circuit (RC element) and varistor
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off Module supply not connected
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
Flickering (ap- Module is in OSP state
prox. 10 Hz)
e Red Off Module supply not connected or everything OK
On Error or reset status
Single flash Loss of zero-crossing signal (input voltage absent or too low)
e+r Red on / Green single flash Invalid firmware
1-4 Orange Control status of the corresponding digital output
4.15.13.5 Pinout
r e
X20 DO 4613
1 2
3 4
DO 11 DO 12
DO 21 DO 22
DO 31 DO 32
DO 41 DO 42
L L
N N
48 - 240 VAC
L
Line filter
Load
N DO
N N
Triac Coupler
Output status 1
DO 11
VDR
DO 12
I/O status
(LED orange)
Triac Coupler
Output status 2
DO 21
VDR
DO 22
I/O status
(LED orange)
Triac Coupler
Output status 3
DO 31
VDR
DO 32
I/O status
(LED orange)
Triac Coupler
Output status 4
DO 41
VDR
DO 42
I/O status
(LED orange)
N
Zero-crossing detection
VDR
The digital output module DO4613 was designed to control external triacs and thyristors.
The module is equipped with internal zero-crossing detection. Zero-crossing detection is the basis for a software
PLL that generates 200 times the zero-crossing frequency. The output signal of the PLL is the base timer for the
4 PWM outputs in both digital and analog mode.
Upon detection of lost periods or periods that are too short, control to the outputs is cut until the PLL is tuned
correctly. The tuning procedure can take several seconds. In addition, the "ZeroCrossingStatus" bit is set and the
error LED enabled (valid frequency range for the supply is 47 to 63 Hz).
Information:
The jitter of the output signals generated by the PLL and communication can reach 0.5%.
As inherent to its functional principal, the triac output is cleared when the current crosses zero. Because zero
crossing for current is delayed with inductive loads, it is possible that the triac will be fired again even though it is
not completely cleared at higher output values (between 50 and 100% depending on the inductance of the load).
In this case, a full-wave is output. This causes the available control range to be reduced (0 to 100%).
For control beyond the point of full-wave control (up to 100%), the value that is physically output no longer changes.
However, this does not cause damage to the module.
Input voltage
Output voltage
Output current
Internal firing signal for the triac
CfO_SwitchOffValue in %
The only difference between function model 2 and function model 0 is the possibility of generating half-wave pat-
terns in various frequencies. Register 18 "CfO_Frequency" is an additional register for this.
Register Name Data type Read Write
Cyclic Non-cyclic Cyclic Non-cyclic
Configuration - General
2+N*2 AnalogOutput0N (Index N = 1 to 4) USINT ●
18 CfO_Frequency UINT ●
18 + N * 2 ConfigOutput0N (Index N = 1 to 4) USINT ●
28 ConfigOutput05 USINT ●
29 CfO_OutputTolerance USINT ●
Communication
2 DigitalOutput USINT ●
DigitalOutput01 Bit 0
... ...
DigitalOutput04 Bit 3
30 StatusInput01 USINT ●
ZeroCrossingInput Bit 4
ZeroCrossingStatus Bit 7
1) The offset specifies the position of the register within the CAN object.
The digital output module was designed for phase control of resistive and inductive loads.
The module is equipped with internal zero-crossing detection. Zero crossing detection is the basis for a software
PLL that generates 200 times the zero crossing frequency. The output signal of the PLL is the base timer for the
2 PWM outputs in both digital and analog mode.
Upon detection of lost periods or periods that are too short, control of the outputs is cut until the PLL is tuned
correctly (can take several seconds). In addition, the "ZeroCrossingStatus" bit is set and the Error LED is enabled
(valid frequency range for the supply is 45 to 65 Hz).
Information:
The jitter of the output signals generated by the PLL and communication can reach 0.5%.
The output state of the outputs defined as digital is transferred to the output ports of the control switch in sync with
the connected power mains. The switch-on state is applied when the voltage crosses zero on the positive half-
wave and the switch-off state at the zero crossing for current in each half wave.
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
Information:
The states in these registers are only applied when the channels are set to DIGITAL in register
4.15.13.10.7.3 "ConfigOutput05".
When using the setting "packed outputs" ALL channels must be set to DIGITAL. Mixed operation is
not possible.
The output value of the outputs defined as analog outputs (unit percent) is switched through to the control ports in
sync with power mains. The analog value is output to the TRIAC control port in the range between (output value
> SwitchOffValue) and (output value <= 95%) with a resolution of 1%.
Changes to the output value are applied at the next positive half-wave.
Name:
AnalogOutput01 to AnalogOutput04
These registers are used to set the commutation angle for phase angle control.
Values between 0 and 100 correspond to the output value for the respective channel in percent. Values above
100 correspond to 100%.
Data type Value
USINT 0 to 100
Information:
The commutation angle for phase angle control set in these registers are only applied when the chan-
nels are set to ANALOG in register 4.15.13.10.7.3 "ConfigOutput05".
Name:
CfO_Frequency
This register can only be used in function model 2 - Frequency mode and makes it possible to configure the output
of half-wave patterns in various frequencies. The commutation angle of the outputs is not affected by this. The
following frequency patterns can be configured:
• 100 half-waves
100 half-waves
• 50 half-waves
50 half-waves
• 33 half-waves
33 half-waves
• 25 half-waves
25 half-waves
With multichannel operation, the different channels should be operated with delayed half-waves in order to ensure
that the load is placed evenly on the module.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Channel 1 0000 100 half-waves/second
0001 50 half-waves/second
0010 25 half-waves/second
0011 33 half-waves/second
0101 50 half-waves/second delayed by 1 half-wave
0110 25 half-waves/second delayed by 2 half-waves
0111 33 half-waves/second delayed by 1 half-wave
4-7 Channel 2 0000 to 0111 See channel 1
8 - 11 Channel 3 0000 to 0111 See channel 1
12 - 15 Channel 4 0000 to 0111 See channel 1
Information:
This function is available beginning with firmware version 940. This can be included beginning with
hardware variant 8.
Name:
ConfigOutput01 to ConfigOutput04
This register defines how far in front of the zero cross-over the internal control signal for the TRIAC is switched off.
Increasing this value may be necessary in order to prevent unwanted firing of the TRIAC in the event of a slight
disturbance in the mains frequency.
With smaller loads, it is important to ensure that this switch off value is not set to large (too early) to prevent
switching off prematurely.
The triac can of course only be fired before the set switch-off time.
"SwitchOffValue" in the AS I/O configuration.
1/f
Triac
Control signal
Switch-off value
5 to 50%
Name:
ConfigOutput05
The configuration of the output channels are stored in this register.
"Output type digital/analog" and "Output type full/half wave" in the AS I/O configuration
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 1: Digital / Analog output 0 Output channel 1 is defined as a digital output. The output sta-
tus is defined using bit 0 in the register DigitalOutput 1 - 4
1 Output channel 1 is defined as an analog output. The output
status is defined in the register AnalogOutput01
... ...
3 Channel 4: Digital / Analog output 0 Output channel 4 is defined as a digital output. The output sta-
tus is defined using bit 1 in the register DigitalOutput 1 - 4
1 Output channel 2 is defined as an analog output. The output
status is defined in the register AnalogOutput04
4 Channel 1: Full-wave / half-wave control1) 0 Full-wave control on output channel 1
1 Negative half-wave on output channel 1 is suppressed.
... ...
7 Channel 4: Full-wave / half-wave control1) 0 Full-wave control on output channel 4
1 Negative half-wave on output channel 4 is suppressed.
Name:
CfO_OutputTolerance
This register can be used to set the switching behavior of the trigger. After the number of zero-crossing errors
configured in Bit 0 to 4, the output is switched off for at least 3 periods. This is followed by synchronization with
the zero signal according to Bit 7.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-4 Trigger for Resync 0 to 30 Number of zero-crossover errors
5-6 Reserved -
7 Fast settling 0 Fast synchronization
1 PLL synchronization
Fast synchronization
With this option, the trigger point is closed-loop controlled after each individual zero-crossover and input jitter.
• Advantage: Increased tolerance and faster response to deviations in mains frequency
• Disadvantage: Increased switch-on jitter for firing signal by zero cross signal ±100 µSec
PLL synchronization
With this option the intervals between zero cross-overs are measured and the PLL frequency is updated accord-
ingly.
• Advantage: Jitter-free firing signal
• Disadvantage: When the output is switched off, additional measurement phases are required before it can
be switched back on.
Information:
This function is available starting with Firmware version 928. This can be installed with hardware ver-
sion 7 and hardware revision B4 or higher.
Name:
ZeroCrossingInput
ZeroCrossingStatus
StatusInput01
The operating status of the outputs is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("ZeroCrossingInput" through "ZeroCrossingStatus") or
whether this register should be displayed as an individual USINT data point ("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0-3 Reserved -
4 ZeroCrossingInput 0 Zero cross signal during the negative half-wave
1 Zero cross signal during the positive half-wave
5-6 Reserved -
7 ZeroCrossingStatus 0 Zero cross signal OK
1 Zero cross signal has dropped out
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 OSPValid 0 Request OSP operation (after initial start or module in Standby)
1 Request normal operation
1-7 Reserved 0
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
Name:
CfgOSPValue01 to CfgOSPValue04
This register contains the analog output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT 0 to 100
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
All channels 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
All channels 150 μs
4.15.14 X20DO4623
The module is a digital output module that is equipped with 4 SSR outputs with zero cross-over switches and uses
2-line connections. The module is also equipped with integrated full-wave control. The supply (L and N) is fed
directly to the module.
• 4 digital outputs
• Outputs with integrated snubber circuit
• Outputs with 100 to 240 VAC
• L switching
• 50 Hz or 60 Hz
• 2-wire connections
• Integrated full-wave control
• 240 V coding
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO4623
Brief description
I/O module 4 digital SSR outputs 100 - 240 VAC, 2-wire connections
General information
B&R ID code 0x267C
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software status
Outputs Yes, with status LED
Power consumption
Bus 0.52 W
Internal I/O -
External I/O 0.38 W
Additional power dissipation caused by the actua- +3.2
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design SSR
Wiring L switching
Nominal voltage 100 to 240 VAC
Rated frequency 47 to 63 Hz
Nominal output current 0.5 A
Total nominal current 1.0 A
Surge current 7 A (20 ms), 2 A (1 s)
Connection type 2-wire connections
Zero crossover switches Yes
Leakage current Max. 1.5 mA at 240 V
Residual voltage (on-state voltage) 1.6 V
Switching delay
At 50 Hz
0 -> 1 ≤ 11 ms
1 -> 0 ≤ 11 ms
At 60 Hz
0 -> 1 ≤ 9.3 ms
1 -> 0 ≤ 9.3 ms
Isolation voltage between channel and bus Tested at 2500 VAC
Voltage monitoring L - N No
Overvoltage protection between L and N Yes
Output voltage
Minimum 75 VAC
Maximum 264 VAC
Protective circuit
External Generally a varistor or fuse
Internal Snubber circuit (RC element)
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0,5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating See section "Derating"
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
4.15.14.5 Pinout
r e
X20 DO 4623
1 2
3 4
DO 1 DO 2
DO 3 DO 4
N N
N N
L L
N N
DO
Actuator
Actuator
T 10 A
L L
N N
SSR
Output x
Output status
zc
I/O status
(LED orange) electrical
separation
L
Zero External
power supply
N
Full-wave control is used to control power for electrical power consumers that are operated with AC voltage. Tem-
perature control is a typical application
Unlike phase-angle control, the sine wave oscillation form of the mains voltage is not changed during full-wave
control. This significantly reduces system perturbation.
The output voltage (channel) is switched on and off at a certain ratio. This switches the multi-cycle packets. A
multi-cycle packet consists of a number of complete sine waves throughout a cycle. The relationship between
the power-on duration and the cycle duration results in the desired effect of reduced power consumption by the
connected power consumer.
With the full-wave control that is integrated in the module, a maximum of 24 full waves can be provided on the
outputs per cycle. Control takes place in 4% steps.
Settings Full waves
SW% % 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
0 0
4 ●
8 ● ●
12 ● ● ●
16 ● ● ● ●
20 ● ● ● ● ●
24 25 ● ● ● ● ● ●
28 ● ● ● ● ● ● ●
32 ● ● ● ● ● ● ● ●
36 ● ● ● ● ● ● ● ● ●
40 ● ● ● ● ● ● ● ● ● ●
44 ● ● ● ● ● ● ● ● ● ● ●
48 50 ● ● ● ● ● ● ● ● ● ● ● ●
52 ● ● ● ● ● ● ● ● ● ● ● ● ●
56 ● ● ● ● ● ● ● ● ● ● ● ● ● ●
60 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
64 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
68 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
72 75 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
76 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
80 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
84 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
88 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
92 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
96 100 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ●
1 cycle
(24 full waves)
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the control switch asynchronously to the connected network. The outputs switch
on when the voltage crosses zero and switch off when the current crosses zero.
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
Information:
The states are only applied when the channels are set to DIGITAL in Setting the output configuration.
When using the setting "packed outputs" ALL channels must be set to DIGITAL. Mixed operation is
not possible.
The output value is transferred to the control circuit in sync with the connected power mains according to the
firing pattern table (see "Integrated full-wave control"). The analog value is output with a resolution of ~4% over a
duration of 24 complete waves. Values > 96% result in full control. Changes to the output value within an interval
are applied after the next zero crossover.
4.15.14.9.4.1 Setting the output value from the firing pattern table
Name:
AnalogOutput01 to AnalogOutput04
These registers are used to set the output value from the firing pattern table.
Values between 0 and 100 correspond to the output value for the respective channel in percent. Values above
100 correspond to 100%.
Data type Value
USINT 0 to 100
Information:
The states in these registers are only applied when the channels are set to ANALOG in Setting the
output configuration.
Name:
Output configuration 1 - 4
ConfigOutput01
Each channel can be configured for either "digital" or "analog" operation in this register. Depending on the setting,
the corresponding DigitalOutput or AnalogOutput registers must be written.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Description
0 Channel 1 0 Digital register is used
1 1 Analog register is used
... ...
3 Channel 4 0 Digital register is used
1 Analog register is used
4-7 0
Name:
ZeroCrossingInput
ZeroCrossingStatus
StatusInput01
Zero crossing detection uses a fixed filter time of 1 ms and a scanning frequency of 10 kHz. When a missing or too
short period is detected, control is switched off until at least 2 periods are detected correctly, and the status flag
is set accordingly. Control is offset by 2 ms from the negative half-wave until the next zero crossover is detected
correctly or another error occurs. This is normally at least one complete wave.
Monitoring is activated at the first zero crossover after being switched on.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("ZeroCrossingInput" through "ZeroCrossingStatus") or
whether this register should be displayed as an individual USINT data point ("StatusInput01").
Data type Value Information
USINT 0 to 17 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 ZeroCrossingInput1) 0 Signal during the negative half-wave
1 Signal during the positive half-wave
1-3 0
4 ZeroCrossingStatus 0 No error
1 Zero crossover failed
5-7 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Standard function model 100 μs
Bus controller function model 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Function model 0 Equal to the minimum cycle time
Function model 1 Equal to the minimum cycle time
4.15.15 X20DO4633
The module is a digital output module with phase-angle control that is equipped with 4 Triac outputs using 2-line
connections. The supply (L and N) is fed directly to the module.
• 4 digital outputs
• Outputs with integrated snubber circuit
• Outputs with 12 to 240 VAC
• L switching
• Zero-crossing detection
• Phase-angle control
• Open-circuit detection for each channel
• Negative half-waves can be switched off
• 50 Hz or 60 Hz
• 2-wire connections
• 240 V coding
• OSP mode
• Frequency mode
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO4633
Short description
I/O module 4 digital outputs 12 to 240 VAC for 2-wire connections
General information
B&R ID code 0xAC3A
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED
Power consumption
Bus 0.6 W
Internal I/O -
External I/O -
Additional power dissipation caused by the actua- +6.4 W
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design Triac
Wiring L switching
Nominal voltage 12 to 240 VAC
Rated frequency 47 to 63 Hz
Nominal output current 1A
Total nominal current 4A
Maximum current
Output current 1.25 A
Summation current 5A
Connection type 2-wire connections
Zero-crossing detection Yes
Minimum holding current IH 15 mA
Leakage current Max. 2 mA at 240 V and 50 Hz
Max. 2.4 mA at 240 V and 60 Hz
Residual voltage (on-state voltage) 1.6 V
Phase-angle control
Range 5 to 95%
Resolution 1%
Accuracy (60 to 240 VAC) <100 μs
Voltage monitoring L - N No
Additional functions Open line detection
Overvoltage protection between L and N Yes
Isolation voltage
Terminal block - Bus Tested at 2300 VAC (Rev. <E0 1500 VAC)
Terminal block - 24 V Tested at 2300 VAC (Rev. <E0 2000 VAC)
Terminal block - PE Tested at 2300 VAC (Rev. <E0 1500 VAC)
Protective circuit
External See section "External fuses"
Internal Snubber circuit (RC element) and varistor
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating See section "Derating"
Storage -40 to 85°C
Transport -40 to 85°C
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off Module supply not connected
Single flash RESET mode
Blinking PREOPERATIONAL mode
On RUN mode
Flickering (ap- Module is in OSP state
prox. 10 Hz)
e Red Off Module supply not connected or everything OK
On Error or reset status
Single flash Loss of zero-crossing signal (I/O supply voltage not applied or too low)
e+r Red on / Green single flash Invalid firmware
1-4 Orange Control status of the corresponding digital output
4.15.15.5 Pinout
The following points must be taken into consideration when wiring the module:
• For thermal reasons, wires with a cross-section ≥1.5 mm² must be used to wire the module.
• The neutral return lines for the outputs must be wired to the terminal block separately for each channel
and must not be bypassed in the field.
• A line filter must be used for the 240 V supply that provides ≥40 dB attenuation at 150 kHz and works
up to 5 MHz.
r e
X20 DO 4633
1 2
3 4
DO 1 DO 2
DO 3 DO 4
N N
N N
L L
N N
DO
Actuator
Actuator
T 10 A
L L
N N
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
DO 1
Output status 1
VDR
N
I/O status
(LED orange)
DO 4
Output status 4
VDR
N
I/O status
(LED orange)
1) See also section 4.15.15.13 "Operation with inductive loads" on page 1180
2) Meeting the limit values specified in the standards EN 61131, EN 55011 and EN 55022 (each Class A) requires installation of a line filter in the 240 V supply
line. Line filters such as the Schaffner FN 2412‐8‐44 can be used.
If periodic ground transients occur on the supply lines (as can occur with upstream inverters), it is necessary to use an asymmetric filter that keeps these
types of changes in potential below a few volts (e.g. "Sinus Plus" from Schaffner) in addition to the symmetric filter.
4.15.15.10 Derating
1.25
0.938
0
-25 25 35 50 60
Ambient temperature [°C]
The digital output module was designed for phase control of resistive and and inductive loads. The triac outputs
do not have short circuit protection. The integrated open-circuit detection makes it possible to recognize defects
on the load or the cabling (see 4.15.15.12 "Open line detection" on page 1179).
The module is equipped with internal zero-crossing detection. Zero-crossing detection is the basis for a software
PLL that generates 200 times the zero-crossing frequency. The output signal of the PLL is the base timer for the
PWM outputs in both digital and analog mode.
Upon detection of lost periods or periods that are too short, control to the outputs is cut until the PLL is tuned
correctly. The tuning procedure can take several seconds. In addition, the "ZeroCrossingStatus" bit is set and the
error LED enabled (valid frequency range for the supply is 45 to 65 Hz).
Information:
The jitter of the output signals generated by the PLL and communication can reach 0.5%.
The module is equipped with open-circuit detection. Note that open-circuit detection only works when the output
is enabled. An open-circuit will not be detected if the output is turned off.
In addition, open-circuit detection is restricted or doesn't work at all for inductive loads. This depends on the induc-
tance of the load and should be determined beforehand, if necessary.
As inherent to its functional principal, the triac output is cleared when the current crosses zero. Because zero
crossing for current is delayed with inductive loads, it is possible that the triac will be fired again even though it is
not completely cleared at higher output values (between 50 and 100% depending on the inductance of the load).
In this case, a full-wave is output. This causes the available control range (0 to 95%) to be changed.
For open line detection (LowCurrentStatus), a pause in control is required where the triac is not permitted to be
fired. The full wave that is created with inductive loads causes open line detection to be triggered even though
the load on the output is sufficient.
This behavior can be used to detect the full wave and properly adjust the control range (Example: If open line
detection is triggered at a control value of 70%, that means that 0-70% corresponds to 0-100% output).
Input voltage
Output voltage
Output current
Internal firing signal for the triac
CfO_SwitchOffValue in %
With inductive loads, a suitable varistor must be provided between the output DO x and the phase L (e.g. a varistor
with 275 VRMS at 240 VAC).
DO
Actuator
VDR
L L
N N
The only difference between function model 2 and function model 0 is the possibility of generating half-wave pat-
terns in various frequencies. Register 18 "CfO_Frequency" is an additional register for this.
Register Name Data type Read Write
Cyclic Non-cyclic Cyclic Non-cyclic
Configuration - General
2+N*2 AnalogOutput0N (Index N = 1 to 4) USINT ●
18 CfO_Frequency UINT ●
18 + N * 2 CfO_SwitchOffValueN (Index N = 1 to 4) USINT ●
28 CfO_OutputConfig USINT ●
29 CfO_OutputTolerance USINT ●
Communication
2 DigitalOutput USINT ●
DigitalOutput01 Bit 0
... ...
DigitalOutput04 Bit 3
30 StatusInput01 USINT ●
LowCurrentStatus1 Bit 0
... ...
LowCurrentStatus4 Bit 3
ZeroCrossingInput Bit 4
ZeroCrossingStatus Bit 7
1) The offset specifies the position of the register within the CAN object.
The digital output module was designed for phase control of resistive and inductive loads. The triac outputs do
not have short circuit protection, but have open line detection that can be used to find defects in the consumer
or the wiring.
The module is equipped with internal zero-crossing detection. Zero crossing detection is the basis for a software
PLL that generates 200 times the zero crossing frequency. The output signal of the PLL is the base timer for the
2 PWM outputs in both digital and analog mode.
Upon detection of lost periods or periods that are too short, control of the outputs is cut until the PLL is tuned
correctly (can take several seconds). In addition, the "ZeroCrossingStatus" bit is set and the Error LED is enabled
(valid frequency range for the supply is 45 to 65 Hz).
Information:
The jitter of the output signals generated by the PLL and communication can reach 0.5%.
The output state of the outputs defined as digital is transferred to the output ports of the control switch in sync with
the connected power mains. The switch-on state is applied when the voltage crosses zero on the positive half-
wave and the switch-off state at the zero crossing for current in each half wave.
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
Information:
The states in these registers are only applied when the channels are set to DIGITAL in "Configuration
of the output channels".
When using the setting "packed outputs" ALL channels must be set to DIGITAL. Mixed operation is
not possible.
The output value of the outputs defined as analog outputs (unit percent) is switched through to the control ports in
sync with power mains. The analog value is output to the TRIAC control port in the range between (output value
> SwitchOffValue) and (output value <= 95%) with a resolution of 1%.
A short triac switch-on delay is required for open line detection. Therefore even with output values >= 96%, there
is a a small pause in control.
Changes to the output value are applied at the next positive half-wave
Triac switch-on delay
for open line detection
U
1/f
Name:
AnalogOutput01 and AnalogOutput04
These registers are used to set the commutation angle for phase angle control.
Values between 0 and 100 correspond to the output value for the respective channel in percent. Values above
100 correspond to 100%.
Data type Value
USINT 0 to 100
Information:
The commutation angle for phase angle control set in these registers are only applied when the chan-
nels are set to ANALOG in Configuration of the output channels.
Name:
CfO_Frequency
This register can only be used in function model 2 - Frequency mode and makes it possible to configure the output
of half-wave patterns in various frequencies. The commutation angle of the outputs is not affected by this. The
following frequency patterns can be configured:
• 100 half-waves
100 half-waves
• 50 half-waves
50 half-waves
• 33 half-waves
33 half-waves
• 25 half-waves
25 half-waves
With multichannel operation, the different channels should be operated with delayed half-waves in order to ensure
that the load is placed evenly on the module.
Data type Value
UINT See bit structure.
Bit structure:
Bit Description Value Information
0-3 Channel 1 0000 100 half-waves/second
0001 50 half-waves/second
0010 25 half-waves/second
0011 33 half-waves/second
0101 50 half-waves/second delayed by 1 half-wave
0110 25 half-waves/second delayed by 2 half-waves
0111 33 half-waves/second delayed by 1 half-wave
4-7 Channel 2 0000 to 0111 See channel 1
8 - 11 Channel 3 0000 to 0111 See channel 1
12 - 15 Channel 4 0000 to 0111 See channel 1
Information:
This function is available beginning with firmware version 940. This can be included beginning with
hardware variant 8.
Name:
CfO_SwitchOffValue1 to CfO_SwitchOffValue4
This register defines how far in front of the zero cross-over the internal control signal for the TRIAC is switched off.
Increasing this value may be necessary in order to prevent unwanted firing of the TRIAC in the event of a slight
disturbance in the mains frequency.
With smaller loads, it is important to ensure that this switch off value is not set to large (too early) to prevent
switching off prematurely.
The triac can of course only be fired before the set switch-off time.
"SwitchOffValue" in the AS I/O configuration.
1/f
Triac
Control signal
Switch-off value
5 to 50%
Name:
Cfo_OutputConfig
The configuration of the output channels are stored in this register.
"Output type digital/analog" and "Output type full/half wave" in the AS I/O configuration
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 1: Digital / Analog output 0 Output channel 1 is defined as a digital output. The output sta-
tus is defined using bit 0 in the register DigitalOutput 1 - 4
1 Output channel 1 is defined as an analog output. The output
status is defined in the register AnalogOutput01
... ...
3 Channel 4: Digital / Analog output 0 Output channel 4 is defined as a digital output. The output sta-
tus is defined using bit 1 in the register DigitalOutput 1 - 4
1 Output channel 2 is defined as an analog output. The output
status is defined in the register AnalogOutput04
4 Channel 1: Full-wave / half-wave control1) 0 Full-wave control on output channel 1
1 Negative half-wave on output channel 1 is suppressed.
... ...
7 Channel 4: Full-wave / half-wave control1) 0 Full-wave control on output channel 4
1 Negative half-wave on output channel 4 is suppressed.
Name:
CfO_OutputTolerance
This register can be used to set the switching behavior of the trigger. After the number of zero-crossing errors
configured in Bit 0 to 4, the output is switched off for at least 3 periods. This is followed by synchronization with
the zero signal according to Bit 7.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-4 Trigger for Resync 0 to 30 Number of zero-crossover errors
5-6 Reserved -
7 Fast settling 0 Fast synchronization
1 PLL synchronization
Fast synchronization
With this option, the trigger point is closed-loop controlled after each individual zero-crossover and input jitter.
• Advantage: Increased tolerance and faster response to deviations in mains frequency
• Disadvantage: Increased switch-on jitter for firing signal by zero cross signal ±100 µSec
PLL synchronization
With this option the intervals between zero cross-overs are measured and the PLL frequency is updated accord-
ingly.
• Advantage: Jitter-free firing signal
• Disadvantage: When the output is switched off, additional measurement phases are required before it can
be switched back on.
Information:
This function is available starting with Firmware version 928. This can be installed with hardware ver-
sion 8 and hardware revision B2 or higher.
Name:
LowCurrentStatus1 through LowCurrentStatus4
ZeroCrossingInput
ZeroCrossingStatus
StatusInput01
The operating status of the outputs is mapped in this register.
In order to do determine the "LowCurrentStatus", the system checks if there is a neutral connection from the output
via the consumer shortly before each triac firing.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("LowCurrentStatus1" through "ZeroCrossingStatus")
or whether this register should be displayed as an individual USINT data point ("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 LowCurrentStatus1 0 0 = No current flow on activated output 1
1 No current flow on activated output 1
... ...
3 LowCurrentStatus4 0 Current flow on activated output 4
1 No current flow on activated output 4
4 ZeroCrossingInput 0 Zero cross signal during the negative half-wave
1 Zero cross signal during the positive half-wave
5-6 Reserved -
7 ZeroCrossingStatus 0 Zero cross signal OK
1 Zero cross signal has dropped out
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 OSPValid 0 Request OSP operation (after initial start or module in Standby)
1 Request normal operation
1-7 Reserved 0
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
Name:
CfgOSPValue01 to CfgOSPValue04
This register contains the analog output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT 0 to 100
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
All channels 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
All channels 150 μs
4.15.16 X20DO4649
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO4649
Brief description
I/O module 4 digital outputs 30 VDC / 240 VAC, outputs are single-channel isolated
General information
B&R ID code 0xA704
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED
Power consumption
Bus 0.8 W
Internal I/O -
Additional power dissipation caused by the actua- +1.5
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design Relay / Normally open contact
Channels are single-channel isolated
Nominal voltage 30 VDC / 240 VAC
4.15.16.5 Pinout
For easy wiring, 4 auxiliary contacts are available on the module starting with revision E0. They are connected
together internally and can be loaded with a total of 10 A (see also section "Connection example").
r e
X20 DO 4649
1
2
3
4
NO 1 COM 1
NO 2 COM 2
NO 3 COM 3
NO 4 COM 4
AUX AUX
AUX AUX
DO
240 VAC
COM x
NO x
Output status
AUX
AUX
AUX
I/O status
AUX
LED (orange)
DC 30 V / AC 250 V resistive
1000
DC 30 V τ = 7 ms
500
300
200
100
50
AC 250 V cosφ = 0.4
30
20
10
0.1 0.2 0.3 0.5 1 2 3 5 10
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput04
The switching state of digital outputs 1 to 4 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 15 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
3 DigitalOutput04 0 Digital output 04 reset
1 Digital output 04 set
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.17 X20DO6321
The module is equipped with 6 outputs for 1 or 2-wire connections. The X20 6-pin terminal block can be used
for universal 1-line wiring. 2-line wiring can be implemented using the 12-pin terminal block. The X20DO6321 is
designed for sink output wiring.
• 6 digital outputs
• Sink connection
• 2-wire connections
• 24 VDC for signal supply
• Integrated output protection
• 1-wire connection type with 6-pin terminal block
Product ID X20DO6321
Brief description
I/O module 6 digital outputs 24 VDC for 1- or 2-wire connections
General information
B&R ID code 0x1B99
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.2 W
Internal I/O 0.59 W
Additional power dissipation caused by the actua- +0.18
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design FET negative switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 3.0 A
Connection type 1- or 2-wire connections
4.15.17.5 Pinout
r e
X20 DO 6321
1 2
3 4
5 6
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
24 V
I/O status
LED (orange)
Low-side
Output status Output x
Logic
VDR
GND
Output
monitoring GND
24 V
GND
24 V
28.8 V
1H
24.0 V
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput06
The switching state of digital outputs 1 to 6 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
5 DigitalOutput06 0 Digital output 06 reset
1 Digital output 06 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput06
The status of digital outputs 1 to 6 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
5 StatusDigitalOutput06 0 Channel 06: No error
1 Channel 06: Short circuit or overload
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.18 X20DO6322
The module is equipped with 6 outputs for 1 or 2-wire connections. The X20 6-pin terminal block can be used for
universal 1-line wiring. 2-line wiring can be implemented using the 12-pin terminal block. The module is designed
for source output wiring.
• 6 digital outputs
• Source connection
• 2-wire connections
• GND for signal supply
• Integrated output protection
• 1-wire connection type with 6-pin terminal block
• OSP mode
Product ID X20DO6322
Brief description
I/O module 6 digital outputs 24 VDC for 1- or 2-wire connections
General information
B&R ID code 0x1B98
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.18 W
Internal I/O 0.71 W
Additional power dissipation caused by the actua- +0.31
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
4.15.18.5 Pinout
r e
X20 DO 6322
1 2
3 4
5 6
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
GND GND
GND GND
GND GND
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
High-side
Output status
Logic
Output x
GND
I/O status
Output LED (orange)
monitoring
GND
GND
100 mH
Coil resistance Coil inductance
[Ω]
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput06
The switching state of digital outputs 1 to 6 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
5 DigitalOutput06 0 Digital output 06 reset
1 Digital output 06 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput06
The status of digital outputs 1 to 6 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
5 StatusDigitalOutput06 0 Channel 06: No error
1 Channel 06: Short circuit or overload
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.19 X20DO6325
The module is equipped with six outputs for 1 or 2-wire connections with diagnostic functions. The X20 6-pin
terminal block can be used for universal 1-line wiring. Two-line wiring can be implemented using the 12-pin terminal
block. The outputs on the module are designed for source connections.
• 6 digital outputs
• Source connection
• 2-wire connections
• GND for signal supply
• Integrated output protection
• 1-wire connection type with 6-pin terminal block
• Diagnostic functions (open line, short circuit and overload/overtemperature)
• OSP mode
Product ID X20DO6325
Brief description
I/O module 6 digital outputs 24 VDC for 1- or 2-wire connections with a diagnostics function
General information
B&R ID code 0xE284
Status indicators I/O function by channel, diagnostics by channel, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software
Status - Outputs Yes, using status LED and software
Diagnostics - Outputs Yes, using status LED and software
Power consumption
Bus 0.15 W
Internal I/O 0.4 W
Additional power dissipation caused by the actua- Max. 0.225 W
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
GOST-R In preparation
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 3.0 A
Connection type 1- or 2-wire connections
Output circuit Source
4.15.19.5 Pinout
r e
X20 DO 6325
1 2
3 4
5 6
1 2
3 4
5 6
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
GND GND
GND GND
GND GND
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
In order to best use OSP mode, make sure when creating the application that the output module and CPU have
separate power supplies.
24 V
GND
I/O status
Output LED (orange)
monitoring
GND
Each output is equipped with an internal 200 kOhm resistor to 24 V for open line detection.
If the charging resistance at the terminal is greater than 25 to 100 kOhm (tolerance range) an open line is therefore
detected at 24 V. When switched on, this corresponds to a current of 0.2 to 1 mA with all tolerances taken into
consideration.
Supply voltage Min. load Max. load Corresponds to load current when ON
24 V 100 kOhm 25 kOhm 0.2 to 1 mA
100
Switching voltage:
28.8 V
24.0 V
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
1) The offset specifies the position of the register within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput06
The switching state of digital outputs 1 to 6 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
5 DigitalOutput06 0 Digital output 06 reset
1 Digital output 06 set
The status of the outputs is checked every 4 ms. To suppress disturbances on the feedback inputs, two readings
are compared.
The hardware diagnostics recognize the following states:
• Short circuit to ground GND (when output is ON)
• Short circuit to 24 VDC (when output is OFF)
• Open line (when output is OFF)
• Overtemperature / overload
The error is logged in the corresponding status registers and in the cumulative status register.
An open line error is also indicated by the corresponding LED. The LED indicator can be disabled so that an open
(unused) channel does not constantly indicate an error.
Name:
CfgBwStatus
For each output there is a corresponding enable bit. In this register, the bit can be set to define whether or not the
status LED should be used to indicate an open line error. This allows the LED to be disabled for unused channels.
In the bus controller function model the default value is 0xBF.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 01 0 Open line indicator 01 disabled
1 Open line indicator 01 enabled
... ...
5 Channel 06 0 Open line indicator 06 disabled
1 Open line indicator 06 enabled
6 Reserved 0
7 PowerSupply01 0 No error status indicators
1 Monitor supply voltage
Name:
StatusInput01
DigitalStatusGnd01 to DigitalStatusGnd06
In this register, a short circuit or overtemperature error can be indicated by setting the corresponding channel bit.
It is not possible to differentiate between short circuit to GND and overload/overtemperature.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("DigitalStatusGnd01" through "DigitalStatusGnd06")
or whether this register should be displayed as an individual USINT data point ("StatusInput01").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalStatusGnd01 0 No error
1 Channel 1: Short circuit or overload
... ...
5 DigitalStatusGnd06 0 No error
1 Channel 6: Short circuit or overload
6-7 Reserved 0
Name:
StatusInput02
DigitalStatusVcc01 to DigitalStatusVcc06
In this register, a short circuit can be indicated by setting the corresponding channel bit.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("DigitalStatusVcc01" through "DigitalStatusVcc06") or
whether this register should be displayed as an individual USINT data point ("StatusInput02").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalStatusVcc01 0 No error
1 Channel 1: Short circuit to voltage
... ...
5 DigitalStatusVcc06 0 No error
1 Channel 6: Short circuit to voltage
6-7 Reserved 0
Name:
StatusInput03
DigitalStatusBw01 to DigitalStatusBw06
In this register, an open line can be indicated by setting the corresponding channel bit.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("DigitalStatusBw01" through "DigitalStatusBw06") or
whether this register should be displayed as an individual USINT data point ("StatusInput03").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalStatusBw01 0 No error
1 Channel 1: Open line
... ...
5 DigitalStatusBw06 0 No error
1 Channel 6: Open line
6-7 Reserved 0
Name:
StatusInput04
DigitalStatusSum01 to DigitalStatusSum06
PowerSupply01
Every error found in the other status registers is also shown in this register. This provides an easy way to check
whether any errors have occurred.
If the I/O supply fails, Bit 7 is set and all status bits in the other status registers are reset to 0.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points ("DigitalStatusSum01 through DigitalStatusSum06","PowerSupply01") in the
AS I/O mapping or whether this register should be displayed as an individual USINT data point ("StatusInput04").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalStatusSum01 0 No error
1 Channel 1: Error occurred
... ...
5 DigitalStatusSum06 0 No error
1 Channel 6: Error occurred
6 Reserved 0
7 PowerSupply01 0 No error
1 Pending supply voltage error
In the "OSP" function model (Operator Set Predefined), the user defines an analog value or digital pattern. This
OSP value is output as soon as communication between the module and master is interrupted.
Functionality
The user can choose between two OSP modes:
• Retain last valid value
• Replace with static value
In the first case, the module retains the last value as validly recognized output state.
When selecting the mode, "Replace with static value" a plausible output value must be entered in the corresponding
value register. If an OSP event occurs, this value will be output instead of the value currently requested by the task.
Name:
OSPValid
This data point offers the possibility to start module output and request OSP operation during running operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Request OSP operation (after initial start or module in Standby)
0 OSPValid
1 Request normal operation
1-7 0 Reserved
There is one OSPValid bit on the module, which is managed by the user task. It must be set when the enabled
channels are started. As long as the OSPValid bit remains set in the module, the module behaves the same as
the "Standard" function model.
If an OSP event occurs (e.g. communication between the module and master CPU interrupted) then the OSPValid
bit will be reset on the module. The module enters OSP mode and the output occurs in the "OSPMode" register
according to the configuration.
The following applies:
The OSP replacement value remains even after the communication channel has recovered. OSP mode
is only exited when a set OSPValid bit is transferred.
When the master CPU is restarted, the OSPValid bit is re-initialized on the master CPU. It must once
more be set by the application and transferred via the bus.
When temporary communication errors occur between the module and master CPU (e.g. due to EMC),
a few bus cycles will pass without refreshing the cyclic registers. The OSPValid bit is reset internally in
the module - the bit in the CPU however remains set. Upon the next successful transfer, the OSPValid
bit in the module is set again and the module returns to normal operation.
The ModulOK bit can be evaluated if the task in the master CPU needs to know which output mode the module
is currently in.
Warning!
If the OSPValid bit is reset to "0" on the module, then the output state no longer depends on the
responsible task in the master CPU. However, output still occurs according to the configuration of the
OSP replacement value.
Name:
CfgOSPMode
This register essentially controls a channel's behavior when OSP is being used.
Data type Value Description
USINT 0 Replace with static value
1 Retain last valid value
Name:
CfgOSPValue
This register contains the digital output value, which is output in "Replace with static value" mode during OSP
operation.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 0 or 1 OSP output value for channel DigitalOutput00
... ...
x 0 or 1 OSP output value for channel DigitalOutput0x
Warning!
The "OSPValue" is not accepted by the module until the "OSPValid" bit has been set in the module.
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.20 X20DO6529
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO6529
Brief description
I/O module 6 digital outputs 30 VDC / 115 VAC, outputs are single-channel isolated
General information
B&R ID code 0x2019
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using status LED
Power consumption
Bus 1.1 W
Internal I/O -
Additional power dissipation caused by the actua- +0.45
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel Yes
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design Relay / Normally open contact
Channels are single-channel isolated
4.15.20.5 Pinout
r e
X20 DO 6529
1 2
3 4
5 6
NO 1 NO 2
COM 1 COM 2
NO 3 NO 4
COM 3 COM 4
NO 5 NO 6
COM 5 COM 6
DO
NO x
COM x
Output status
I/O status
LED (orange)
0.5
DC resistive
0.3
0.2
0.1
1 2 5 10 20 30 50 100 200
70
50
40
30
30 VD
C
re
si s
20
12
t iv
e
5V
DC
re
10
si s
t iv
e
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput06
The switching state of digital outputs 1 to 6 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
5 DigitalOutput06 0 Digital output 06 reset
1 Digital output 06 set
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.21 X20DO6639
Danger!
Risk of electric shock!
The terminal block must only be allowed to conduct voltage when it is inserted. It must not under any
circumstances be removed or inserted when voltage is applied or have voltage applied to it when it
is removed.
Product ID X20DO6639
Short description
I/O module 6 digital outputs 30 VDC / 240 VAC, outputs are single-channel isolated
General information
B&R ID code 0xDF50
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED
Outputs Yes, using status LED
Power consumption
Bus 1W
Internal I/O -
Additional power dissipation caused by the actua- +0.36
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel -
Certification
CE Yes
ATEX Zone 2 Yes
GOST-R Yes
Digital outputs
Nominal voltage 30 VDC / 240 VAC
Switching voltage max. 110 VDC / 250 VAC
Rated frequency DC / 45 to 63 Hz
Nominal output current 2 A at 30 VDC / 2 A at 240 VAC
Total nominal current 10 A at 30 VDC / 10 A at 240 VAC
4.15.21.5 Pinout
r e
X20 DO 6639
1
2
3
4
5
6
NO 1 COM 1
NO 2 COM 2
NO 3 COM 3
NO 4 COM 4
NO 5 COM 5
NO 6 COM 6
DO
240 VAC
COM x
NO x
Output status
I/O status
LED (orange)
1000
DC 30 V τ = 7 ms
500
300
200
100
50
AC 250 V cosφ = 0.4
30
20
10
0.1 0.2 0.3 0.5 1 2 3 5
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput06
The switching state of digital outputs 1 to 6 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 63 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
5 DigitalOutput06 0 Digital output 06 reset
1 Digital output 06 set
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.22 X20DO8232
The module is equipped with 8 outputs for 1-wire connections. The nominal output current is 2 A and the nominal
voltage is 12 VDC.
The output supply is fed directly to the module. An additional supply module is not needed. There is no connection
between the module and the I/O supply potential on the bus module.
• 8 digital outputs with 2 A
• Rated voltage 12 VDC
• Source connection
• 1-wire connection
• Power feed integrated in the module
• Integrated output protection
Product ID X20DO8232
Brief description
I/O module Eight 12 VDC digital outputs for 1-wire connections
General information
B&R ID code 0xA4AD
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software status
Outputs Yes, with status LED and software status (output error status)
Supply voltage monitoring Yes, with software status
Power consumption
Bus 0.22 W
Internal I/O -
External I/O 0.82 W
Additional power dissipation caused by the actua- +4.48
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Nominal voltage 12 VDC
4.15.22.5 Pinout
r e
X20 DO 8232
1 2
3 4
5 6
7 8
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO
DI 17 DO 8
GND GND
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
_
+
+12 V ext. GND
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
External Supply
12 V GND
12 V
External Supply Reverse polarity
protection
High-side
Output status 1 GND
Logic
Output x
12 V
External
Power supply
GND
1 12 V
External Supply
12 V monitoring
Environmental temperature: 35°C, 4 outputs (1,3,5,7 or 2,4,6,8) with the same load.
100 H
500 10 H
Switching voltage:
14.4 V
12.0 V
1H
100
100 mH
Coil resistance Coil inductance
[Ω]
10 mH
10
5
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Environmental temperature: 60°C, 4 outputs (1,3,5,7 or 2,4,6,8) with the same load.
100 H 10 H
500
Switching voltage:
14.4 V
1H 12.0 V
100
100 mH
Coil resistance Coil inductance
[Ω]
10 mH
10
5
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
100 100 mH
10
5
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
The outputs of the module can handle up to 2 A. With a total current of 8 A, no more than 4 channels are operable
at full load. To ensure optimal use of the module, it is important to assign the channels properly, and to keep in
mind a potential derating.
Correct channel assignment is important, since the eight outputs are divided between two output drivers. The
channels operated with 2A must therefore be evenly divided between both output drivers.
Output driver 1: Channels 1 - 4
Output driver 2: Channels 5 - 8
The following table provides an overview of the number of fully used channels, the resulting best distribution, and
a potential derating.
Number of channels using 2A Division Derating
1 Any No
2 1st channel with 2 A ... channel no. 1 - 4 No
2nd channel with 2 A ... channel no. 5 - 8
3 Assign all even or all odd channel numbers. Exam-
ples:
1, 3, 5 Channels 1 and 3
2, 4, 6 Channels 2 and 4
3, 5, 7 Channels 5 and 7
4, 6, 8 Channels 6 and 8
4 Assign all even or all odd channel numbers. Possible
distributions:
1, 3, 5, 7 All channels
2, 4, 6, 8 All channels
1.375
Output current [A]
0
-25 35 60
Information:
Modules next to this module can have a maximum power consumption of 1.0 W.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput08
The switching state of digital outputs 1 to 8 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
7 DigitalOutput08 0 Digital output 08 reset
1 Digital output 08 set
Name:
asy_ModulID
This register offers another possibility for reading the module ID.
Data type Value
UINT Module ID
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput08
This register is used to indicate the status of digital outputs 1 to 8.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
8 StatusDigitalOutput08 0 Channel 08: No error
1 Channel 08: Short circuit or overload
The module's output supply is monitored. An I/O supply voltage of <10.2 V is displayed as a warning.
Name:
asy_SupplyStatus
The status of the I/O supply voltage is mapped in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-1 0 0
2 PowerSupply01 0 I/O supply above the warning level of 10.2 V
1 I/O supply below the warning level of 10.2 V
3-7 0 0
4.15.22.10.8 Additional function - switch digital outputs w/ delay using switching mask
In function model 1 - Output switching, it is possible to control the digital outputs with a delay.
The OutputDelay mask can be used to activate the delay for each channel individually. The module is controlled
here using a 100 μs-based timer and the Output or OutputDelayed register.
Behavior of function model 1 - Output switching
With a timer delay of 0:
Output: DigitalOutput0x bits
When the delay is changed:
The bit string for DigitalOutput0x bits is output. The timer restarts.
Output: DigitalOutput0x bits
After delay time has expired:
The channels with bits set in the OutputDelay mask are adapted to the respective OutputDelayed bits.
Output: DigitalOutput0x bits (if Enable bit = FALSE)
OutputDelayed bits (if Enable bit = TRUE)
Information:
Adjusting the output and restarting the timer take place immediately after transferring the new delay,
even if the previous time has not yet passed.
Name:
DigitalOutput01Delayed to Digital08Delayed
According to the corresponding bit in the OutputDelay mask, the switching state of all digital outputs 1 to 8 are
stored in the OutputDelayed bits after the delay time has expired.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital output 01 reset
0 DigitalOutput01Delayed
1 Digital output 01 set
... ...
0 Digital output 08 reset
7 DigitalOutput08Delayed
1 Digital output 08 set
Information:
After the delay time has expired, only the channels with a bit set in the OutputDelay mask are adjusted
to the OutputDelayed bits.
Name:
DigitalOutput01DelayEnable to DigitalOutput08DelayEnable
These registers create the mask for OutputDelay. They define which outputs are switched to the bit string for the
OutputDelayed register after the delay time has expired.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital output 01 remains unchanged
0 DigitalOutput01DelayEnable
1 Digital output 01 is toggled
... ...
0 Digital output 08 remains unchanged
7 DigitalOutput08DelayEnable
1 Digital output 08 is toggled
Name:
OutputDelayTime
This register can be used to set the delay in 100 μs steps.
After the delay time has expired, the digital outputs are adjusted according to the switching mask (register 6) and
the delayed output pattern (register 4).
Data type Value
USINT 0 to 255 (in 100 μs steps)1)
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Standard function model 100 μs
Bus controller function model 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Function model 0 Equal to the minimum cycle time
Function model 1 Equal to the minimum cycle time
4.15.23 X20DO8322
The module is equipped with 8 outputs for 1-wire connections and designed for source output wiring.
• 8 digital outputs
• Source connection
• 1-wire connections
• Integrated output protection
Product ID X20DO8322
Brief description
I/O module 8 digital outputs 24 VDC for 1-wire connections
General information
B&R ID code 0xA4AC
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.26 W
Internal I/O 0.8 W
Additional power dissipation caused by the actua- +0.42
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 4.0 A
Connection type 1-wire connections
Output circuit Source
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
Diagnostic status Output monitoring with 10 ms delay
Leakage current when switched off 5 µA
4.15.23.5 Pinout
r e
X20 DO 8322
1 2
3 4
5 6
7 8
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO 7 DO 8
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
GND GND
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
External Supply
24 V GND
Reverse polarity
protection
24 V
High-side 1 GND
Output status
Logic
Output x
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
28.8 V
24.0 V
100 mH
100
10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput08
The switching state of digital outputs 1 to 8 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
7 DigitalOutput08 0 Digital output 08 reset
1 Digital output 08 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput08
This register is used to indicate the status of digital outputs 1 to 8.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
8 StatusDigitalOutput08 0 Channel 08: No error
1 Channel 08: Short circuit or overload
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.24 X20DO8323
The module is an electrically isolated 8-channel digital output module. It can be configured as high-side or low-side
or as a push/pull output for controlling 12 to 24 VDC DC motors.
• 8 digital outputs
• High-side or low-side connection
• Push/pull outputs
• 1-wire connections
• Integrated output protection
Product ID X20DO8323
General information
Module type B&R X20 digital output module
B&R ID code 0xDF4E
Status indicators Operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using software
Power consumption
Bus 160 mW
Internal I/O 200 mW (without load)
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
Digital outputs
Design FET push/pull (high resistance)
Nominal voltage 11.5 to 30 V
Nominal output current 0.5 A
Total nominal current 4.0 A
Connection type Sink / source
Output circuit 1-wire connections
Diagnostic status
Voltage monitoring 1) 11.5 V < supply voltage < 30 V
Output monitoring Output OK
Leakage current when switched off 5 μA per channel
RDS(on) 120 mΩ (low-side), 140 mΩ (high-side)
Switching delay
0 -> 1 Max. 450 μs
1 -> 0 Max. 450 μs
Switching frequency
Resistive load Max. 100 Hz
Isolation voltage between channel and bus 500 V
Reverse polarity protection Yes
Switching voltage
Minimum 11.5 VDC
Nominal 12 – 24 VDC
Maximum 30 VDC
Protective circuit
External 24 VDC supply voltage – Maximum current 5A (blow-out fuse)
Internal Thermal cutoff, integrated protection for switching inductances
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5 +0.2 mm
4.15.24.5 Pinout
r e
X20 DO 8323
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO
DI 17 DO 8
GND GND
+ +
M1 DO M2
+ +
M7 M8
+
+12 VDC
+
+12 VDC
+24 VDC +24 VDC
GND GND
DO
+ +
M1 M2
+ +
M3 M4
+24 VDC
+
+24 VDC +24 VDC
GND GND
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
+
+24 VDC
24 V
AH x
Output x
Output status AL x
GND
GND
FB x
GND
GND GND
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output state is sent to the output ports acyclically to the network in the system timer (100 μsec). (max. switch
off jitter: 50 µsec, max. switch on jitter: 150 µsec)
The output state must be switched with at least a 300 µsec delay in order to prevent the high-side and low-side
drivers from switching together.
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput08
The switching state of digital outputs 1 to 8 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
7 DigitalOutput08 0 Digital output 08 reset
1 Digital output 08 set
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput08
This register is used to indicate the status of digital outputs 1 to 8.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
8 StatusDigitalOutput08 0 Channel 08: No error
1 Channel 08: Short circuit or overload
Name:
EnableDigitalOutput
EnabDigitalOutput01 through EnabDigitalOutput08
In this register, all channels can be connected as inputs or outputs. For each output there is a corresponding
switching bit. Clearing this bit switches to tristate mode.
In function model 254 the initial value is 255.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits should
be set up individually as data points in the AS I/O mapping ("EnabDigitalOutput01" through "EnabDigitalOutput08")
or whether this register should be displayed as an individual USINT data point ("EnableDigitalOutput").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 EnabDigitalOutput01 0 Channel 1 used as input
1 Channel 1 used as output
... ...
7 EnabDigitalOutput08 0 Channel 8 used as input
1 Channel 8 used as output
Name:
DigitalInput
DigitalInput01 through DigitalInput08
The status of digital inputs 1 to 8 is mapped in this register.
The status of the digital inputs is read with a minimum update rate of 5 to 8 msec. according to the digital output
status sample rate.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalInput01" through "DigitalInput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalInput").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalInput01 0 or 1 Input status - Digital input 1
... ...
7 DigitalInput08 0 or 1 Input status - Digital input 8
Name:
StatusDigitalOutputs
StatusSupplyLO
StatusSupplyHI
The state of output monitoring and the supply voltage for all outputs are collected and mapped to this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 StatusDigitalOutputs 0 No output monitoring
1 Output monitoring active for at least one channel
1-3 Reserved 0
4 StatusSupplyLO 0 No error
1 Supply voltage too low (<= 11.5 VDC)
5 StatusSupplyHI 0 No error
1 Supply voltage too high (> 30 VDC)
6-7 Reserved 0
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
All channels 400 μs
4.15.25 X20DO8331
The module is equipped with 8 outputs for 1-wire connections. The rated output current is 2 A.
The output supply is fed directly to the module. An additional supply module is not needed. There is no connection
between the module and the I/O supply potential on the bus module.
• 8 digital outputs with 2 A
• Sink connection
• 1-wire connections
• Power feed integrated in the module
• Integrated output protection
Product ID X20DO8331
Brief description
I/O module 8 digital outputs 24 VDC for 1-wire connections
General information
B&R ID code 0x22EB
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Supply voltage monitoring Yes, using software
Power consumption
Bus 0.22 W
Internal I/O -
External I/O 0.9 W
Additional power dissipation caused by the actua- +0.56
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design FET negative switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 2.0 A
Total nominal current 8.0 A
Connection type 1-wire connections
4.15.25.5 Pinout
r e
X20 DO 8331
1 2
3 4
5 6
7 8
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO 7 DO 8
GND GND
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
T 10 A _
+
+24 V ext.
External Supply
24 V 24 V GND
Reverse polarity
protection
I/O status
LED (orange) GND 24 VInternal
Low-side
Output status Output x
Logic
VDR
GND
Output
monitoring GND
24 V
GND 24 V
External
Power supply
24 VInternal GND
GND
24 V monitoring
GND
Environmental temperature: 35°C, 4 outputs (1,3,5,7 or 2,4,6,8) with the same load.
100 H 10 H
500
1H
100 100 mH
10 mH
Switching voltage:
28.8 V
24.0 V
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Environmental temperature: 60°C, 4 outputs (1,3,5,7 or 2,4,6,8) with the same load.
100 H 10 H
500
1H
100 mH
100
Switching voltage:
28.8 V
24.0 V
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
100 mH
100
10 mH
Coil resistance Coil inductance
[Ω]
Switching voltage:
28.8 V
24.0 V
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
The outputs of the module can handle up to 2 A. With a total current of 8 A, no more than 4 channels are operable
at full load. To ensure optimal use of the module, it is important to assign the channels properly, and to keep in
mind a potential derating.
Correct channel assignment is important, since the eight outputs are divided between two output drivers. The
channels operated with 2A must therefore be evenly divided between both output drivers.
Output driver 1: Channels 1 - 4
Output driver 2: Channels 5 - 8
The following table provides an overview of the number of fully used channels, the resulting best distribution, and
a potential derating.
Number of channels using 2A Division Derating
1 Any No
2 1st channel with 2 A ... channel no. 1 - 4 No
2nd channel with 2 A ... channel no. 5 - 8
3 Assign all even or all odd channel numbers. Exam-
ples:
1, 3, 5 Channels 1 and 3
2, 4, 6 Channels 2 and 4
3, 5, 7 Channels 5 and 7
4, 6, 8 Channels 6 and 8
4 Assign all even or all odd channel numbers. Possible
distributions:
1, 3, 5, 7 All channels
2, 4, 6, 8 All channels
1.375
Output current [A]
0
-25 35 60
Information:
Modules next to this module can have a maximum power consumption of 1.5 W.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput08
The switching state of digital outputs 1 to 8 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
7 DigitalOutput08 0 Digital output 08 reset
1 Digital output 08 set
Name:
asy_ModulID
This register offers another possibility for reading the module ID.
Data type Value
UINT Module ID
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput08
This register is used to indicate the status of digital outputs 1 to 8.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
8 StatusDigitalOutput08 0 Channel 08: No error
1 Channel 08: Short circuit or overload
The module's output supply is monitored. An I/O supply voltage of <20.4 V is displayed as a warning.
Name:
asy_SupplyStatus
The status of the I/O supply voltage is mapped in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-1 0
2 PowerSupply01 0 I/O supply above the warning level of 20.4V
1 I/O supply below the warning level of 20.4V
3-7 0
4.15.25.10.8 Additional function - switch digital outputs w/ delay using switching mask
In function model 1 - Output switching, it is possible to control the digital outputs with a delay.
The OutputDelay mask can be used to activate the delay for each channel individually. The module is controlled
here using a 100 μs-based timer and the Output or OutputDelayed register.
Behavior of function model 1 - Output switching
With a timer delay of 0:
Output: DigitalOutput0x bits
When the delay is changed:
The bit string for DigitalOutput0x bits is output. The timer restarts.
Output: DigitalOutput0x bits
After delay time has expired:
The channels with bits set in the OutputDelay mask are adapted to the respective OutputDelayed bits.
Output: DigitalOutput0x bits (if Enable bit = FALSE)
OutputDelayed bits (if Enable bit = TRUE)
Information:
Adjusting the output and restarting the timer take place immediately after transferring the new delay,
even if the previous time has not yet passed.
Name:
DigitalOutput01Delayed to Digital08Delayed
According to the corresponding bit in the OutputDelay mask, the switching state of all digital outputs 1 to 8 are
stored in the OutputDelayed bits after the delay time has expired.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital output 01 reset
0 DigitalOutput01Delayed
1 Digital output 01 set
... ...
0 Digital output 08 reset
7 DigitalOutput08Delayed
1 Digital output 08 set
Information:
After the delay time has expired, only the channels with a bit set in the OutputDelay mask are adjusted
to the OutputDelayed bits.
Name:
DigitalOutput01DelayEnable to DigitalOutput08DelayEnable
These registers create the mask for OutputDelay. They define which outputs are switched to the bit string for the
OutputDelayed register after the delay time has expired.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital output 01 remains unchanged
0 DigitalOutput01DelayEnable
1 Digital output 01 is toggled
... ...
0 Digital output 08 remains unchanged
7 DigitalOutput08DelayEnable
1 Digital output 08 is toggled
Name:
OutputDelayTime
This register can be used to set the delay in 100 μs steps.
After the delay time has expired, the digital outputs are adjusted according to the switching mask (register 6) and
the delayed output pattern (register 4).
Data type Value
USINT 0 to 255 (in 100 μs steps)1)
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Standard function model 100 μs
Bus controller function model 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Function model 0 Equal to the minimum cycle time
Function model 1 Equal to the minimum cycle time
4.15.26 X20DO8332
The module is equipped with 8 outputs for 1-wire connections. The rated output current is 2 A.
The output supply is fed directly to the module. An additional supply module is not needed. There is no connection
between the module and the I/O supply potential on the bus module.
• 8 digital outputs with 2 A
• Source connection
• 1-wire connections
• Power feed integrated in the module
• Integrated output protection
Product ID X20DO8332
Brief description
I/O module 8 digital outputs 24 VDC for 1-wire connections
General information
B&R ID code 0x1B9D
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Supply voltage monitoring Yes, using software
Power consumption
Bus 0.22 W
Internal I/O -
External I/O 0.92 W
Additional power dissipation caused by the actua- +2.24
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Number of output groups 2
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 2.0 A
4.15.26.5 Pinout
r e
X20 DO 8332
1 2
3 4
5 6
7 8
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO 7 DO 8
GND GND
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
T 10 A _
+
+24 V ext.
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
External Supply
24 V GND
Reverse polarity
24 V
protection
External Supply
High-side 1 GND
Output status
Logic
Output x
24 V
External
Power supply
GND
1 24 V
External Supply
24 V monitoring
Environmental temperature: 35°C, 4 outputs (1,3,5,7 or 2,4,6,8) with the same load.
100 H 10 H
500
1H
100 100 mH
Switching voltage:
28.8 V
24.0 V
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Environmental temperature: 60°C, 4 outputs (1,3,5,7 or 2,4,6,8) with the same load.
100 H 10 H
500
1H
100 mH
100
Switching voltage:
28.8 V
24.0 V
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
100 mH
100
10 mH
Coil resistance Coil inductance
[Ω]
Switching voltage:
28.8 V
24.0 V
10
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
The outputs of the module can handle up to 2 A. With a total current of 8 A, no more than 4 channels are operable
at full load. To ensure optimal use of the module, it is important to assign the channels properly, and to keep in
mind a potential derating.
Correct channel assignment is important, since the eight outputs are divided between two output drivers. The
channels operated with 2A must therefore be evenly divided between both output drivers.
Output driver 1: Channels 1 - 4
Output driver 2: Channels 5 - 8
The following table provides an overview of the number of fully used channels, the resulting best distribution, and
a potential derating.
Number of channels using 2A Division Derating
1 Any No
2 1st channel with 2 A ... channel no. 1 - 4 No
2nd channel with 2 A ... channel no. 5 - 8
3 Assign all even or all odd channel numbers. Exam-
ples:
1, 3, 5 Channels 1 and 3
2, 4, 6 Channels 2 and 4
3, 5, 7 Channels 5 and 7
4, 6, 8 Channels 6 and 8
4 Assign all even or all odd channel numbers. Possible
distributions:
1, 3, 5, 7 All channels
2, 4, 6, 8 All channels
1.375
Output current [A]
0
-25 35 60
Information:
Modules next to this module can have a maximum power consumption of 1.5 W.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput08
The switching state of digital outputs 1 to 8 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput0x") or
whether this register should be displayed as an individual USINT data point ("DigitalOutput").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
7 DigitalOutput08 0 Digital output 08 reset
1 Digital output 08 set
Name:
asy_ModulID
This register offers another possibility for reading the module ID.
Data type Value
UINT Module ID
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput08
This register is used to indicate the status of digital outputs 1 to 8.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of this registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through
"StatusDigitalOutput0x") or whether this register should be displayed as an individual USINT data point
("StatusInput01").
Data type Value Information
USINT 0 to 255 Packed outputs = on
See bit structure Packed outputs = off or function model <> 0 - Standard
Bit structure:
Bit Name Value Information
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
8 StatusDigitalOutput08 0 Channel 08: No error
1 Channel 08: Short circuit or overload
The module's output supply is monitored. An I/O supply voltage of <20.4 V is displayed as a warning.
Name:
asy_SupplyStatus
The status of the I/O supply voltage is mapped in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-1 0
2 PowerSupply01 0 I/O supply above the warning level of 20.4V
1 I/O supply below the warning level of 20.4V
3-7 0
4.15.26.10.8 Additional function - switch digital outputs w/ delay using switching mask
In function model 1 - Output switching, it is possible to control the digital outputs with a delay.
The OutputDelay mask can be used to activate the delay for each channel individually. The module is controlled
here using a 100 μs-based timer and the Output or OutputDelayed register.
Behavior of function model 1 - Output switching
With a timer delay of 0:
Output: DigitalOutput0x bits
When the delay is changed:
The bit string for DigitalOutput0x bits is output. The timer restarts.
Output: DigitalOutput0x bits
After delay time has expired:
The channels with bits set in the OutputDelay mask are adapted to the respective OutputDelayed bits.
Output: DigitalOutput0x bits (if Enable bit = FALSE)
OutputDelayed bits (if Enable bit = TRUE)
Information:
Adjusting the output and restarting the timer take place immediately after transferring the new delay,
even if the previous time has not yet passed.
Name:
DigitalOutput01Delayed to Digital08Delayed
According to the corresponding bit in the OutputDelay mask, the switching state of all digital outputs 1 to 8 are
stored in the OutputDelayed bits after the delay time has expired.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital output 01 reset
0 DigitalOutput01Delayed
1 Digital output 01 set
... ...
0 Digital output 08 reset
7 DigitalOutput08Delayed
1 Digital output 08 set
Information:
After the delay time has expired, only the channels with a bit set in the OutputDelay mask are adjusted
to the OutputDelayed bits.
Name:
DigitalOutput01DelayEnable to DigitalOutput08DelayEnable
These registers create the mask for OutputDelay. They define which outputs are switched to the bit string for the
OutputDelayed register after the delay time has expired.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital output 01 remains unchanged
0 DigitalOutput01DelayEnable
1 Digital output 01 is toggled
... ...
0 Digital output 08 remains unchanged
7 DigitalOutput08DelayEnable
1 Digital output 08 is toggled
Name:
OutputDelayTime
This register can be used to set the delay in 100 μs steps.
After the delay time has expired, the digital outputs are adjusted according to the switching mask (register 6) and
the delayed output pattern (register 4).
Data type Value
USINT 0 to 255 (in 100 μs steps)1)
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
Standard function model 100 μs
Bus controller function model 150 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Function model 0 Equal to the minimum cycle time
Function model 1 Equal to the minimum cycle time
4.15.27 X20DO9321
The module is equipped with 12 outputs for 1-wire connections. The module is designed for sink output wiring.
• 12 digital outputs
• Sink connection
• 1-wire connections
• Integrated output protection
Product ID X20DO9321
Short description
I/O module 12 digital outputs 24 VDC for 1-wire connections
General information
B&R ID code 0x1B9B
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.26 W
Internal I/O 0.99 W
Additional power dissipation caused by the actua- +0.36
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital outputs
Design FET negative switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 6.0 A
Connection type 1-wire connections
Output circuit Sink
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
Diagnostic status Output monitoring with 10 ms delay
Leakage current when switched off 75 µA
RDS(on) 120 mΩ
4.15.27.5 Pinout
r e
X20 DO 9321
1 2
3 4
5 6
7 8
9 10
11 12
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO 7 DO 8
DO 9 DO 10
DO 11 DO 12
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
Actuator 9 Actuator 10
Actuator 11 Actuator 12
24 V
I/O status
LED (orange)
Low-side
Output status Output x
Logic
VDR
GND
Output
monitoring GND
GND
28.8 V
24.0 V
100 mH
Coil resistance Coil inductance
[Ω]
100 10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
28.8 V
24.0 V
100 mH
10 mH
100
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput12
The switching state of digital outputs 1 to 12 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput12") or
whether these registers should be displayed as an individual UINT data point ("DigitalOutput").
Data type Value
UINT Packed "DigitalOutput" values
USINT See bit structure
Bit structure:
Register 2, Offset 0:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
7 DigitalOutput08 0 Digital output 08 reset
1 Digital output 08 set
Register 3, Offset 1:
Bit Name Value Information
0 DigitalOutput09 0 Digital output 09 reset
1 Digital output 09 set
... ...
3 DigitalOutput12 0 Digital output 12 reset
1 Digital output 12 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput12
The status of digital outputs 1 to 12 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through "Status-
DigitalOutput12") or whether these registers should be displayed as an individual UINT data point ("StatusDigi-
talOutput").
Data type Value
UINT Packed "StatusDigitalOutput" values
USINT See bit structure
Bit structure:
Register 30, (Offset 1):
Bit Name Value Description
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
7 StatusDigitalOutput08 0 Channel 08: No error
1 Channel 08: Short circuit or overload
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.28 X20DO9322
The module is equipped with 12 outputs for 1-wire connections. The module is designed for source output wiring.
• 12 digital outputs
• Source connection
• 1-wire connections
• Integrated output protection
Product ID X20DO9322
Short description
I/O module 12 digital outputs 24 VDC for 1-wire connections
General information
B&R ID code 0x1B9A
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.26 W
Internal I/O 1.15 W
Additional power dissipation caused by the actua- +0.63
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GL Yes
GOST-R Yes
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 6.0 A
Connection type 1-wire connections
Output circuit Source
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
Diagnostic status Output monitoring with 10 ms delay
Leakage current when switched off 5 µA
4.15.28.5 Pinout
r e
X20 DO 9322
1 2
3 4
5 6
7 8
9 10
11 12
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO 7 DO 8
DO 9 DO 10
DO 11 DO 12
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
Actuator 9 Actuator 10
Actuator 11 Actuator 12
GND GND
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
24 V GND
Reverse polarity
protection
24 V
High-side 1 GND
Output status
Logic
Output x
28.8 V
24.0 V
100 mH
100 10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
100
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput
DigitalOutput01 to DigitalOutput12
The switching state of digital outputs 1 to 12 are stored in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput12") or
whether these registers should be displayed as an individual UINT data point ("DigitalOutput").
Data type Value
UINT Packed "DigitalOutput" values
USINT See bit structure
Bit structure:
Register 2, Offset 0:
Bit Name Value Information
0 DigitalOutput01 0 Digital output 01 reset
1 Digital output 01 set
... ...
7 DigitalOutput08 0 Digital output 08 reset
1 Digital output 08 set
Register 3, Offset 1:
Bit Name Value Information
0 DigitalOutput09 0 Digital output 09 reset
1 Digital output 09 set
... ...
3 DigitalOutput12 0 Digital output 12 reset
1 Digital output 12 set
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusInput01
StatusDigitalOutput01 to StatusDigitalOutput12
The status of digital outputs 1 to 12 is mapped in this register.
Function model 0 - Standard only:
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers'
bits should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through "Status-
DigitalOutput12") or whether these registers should be displayed as an individual UINT data point ("StatusDigi-
talOutput").
Data type Value
UINT Packed "StatusDigitalOutput" values
USINT See bit structure
Bit structure:
Register 30, (Offset 1):
Bit Name Value Description
0 StatusDigitalOutput01 0 Channel 01: No error
1 Channel 01: Short circuit or overload
... ...
7 StatusDigitalOutput08 0 Channel 08: No error
1 Channel 08: Short circuit or overload
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.29 X20DOD322
The X20DOD322 module is equipped with eight outputs for 1-wire or 2-wire connections. The X20DOD322 is
designed for source output wiring.
• 8 digital outputs
• Source connection
• 2-wire connections
• GND for signal supply
• Integrated output protection
Product ID X20DOD322
Short description
I/O module 8 digital outputs 24 VDC for 1- or 2-wire connections
General information
B&R ID code 0xC0E9
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.19 W
Internal I/O 0.8 W
Additional power dissipation caused by the actua- 0.28 W
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R In preparation
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 4.0 A
Connection type 1- or 2-wire connections
Output circuit Source
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
Diagnostic status Output monitoring with 10 ms delay
4.15.29.5 Pinout
S 1 2
3 4
X20 DO D322
5 6
7 8
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO 7 DO 8
GND GND
GND GND
GND GND
GND GND
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
24 V
High-side
Output status
Logic
Output x
GND
I/O status
LED (orange)
Output
monitoring
GND
GND
28.8 V
24.0 V
100 mH
100 10 mH
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput or
DigitalOutput01 to DigitalOutput08
The switching state of digital outputs 1 to 8 are stored in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Digital output 01 reset
0 DigitalOutput01
1 Digital output 01 set
... ...
0 Digital output 08 reset
7 DigitalOutput08
1 Digital output 08 set
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput16") or
whether these registers should be displayed as an individual UINT data point ("DigitalOutput").
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusDigitalOutput or
StatusDigitalOutput01 to StatusDigitalOutput08
The status of digital outputs 1 to 8 is mapped in this register.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 Channel 01: No error
0 StatusDigitalOutput01
1 Channel 01: Short circuit or overload
... ...
0 Channel 08: No error
8 StatusDigitalOutput08
1 Channel 08: Short circuit or overload
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers' bits
should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through "StatusDigi-
talOutput16") or whether these registers should be displayed as an individual UINT data point ("StatusDigitalOut-
put").
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.15.30 X20DOF322
The X20DOF322 module is equipped with 16 outputs for 1-wire connections. The X20DOF322 is designed for
source output wiring.
• 16 digital outputs
• Source connection
• 1-wire connections
• Integrated output protection
Product ID X20DOF322
Short description
I/O module 16 digital outputs 24 VDC for 1-wire connections
General information
B&R ID code 0xC0EA
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, with status LED and software status (output error status)
Power consumption
Bus 0.28 W
Internal I/O 0.95 W
Additional power dissipation caused by the actua- 0.56 W
tors (resistive) [W] 1)
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R In preparation
Digital outputs
Design FET positive switching
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.5 A
Total nominal current 8.0 A
Connection type 1-wire connections
Output circuit Source
Output protection Thermal cutoff for overcurrent or short circuit (see value "Peak short circuit current")
Internal inverse diode for switching ind. loads (see section "Switching inductive loads")
Diagnostic status Output monitoring with 10 ms delay
Leakage current when switched off 5 µA
RDS(on) 140 mΩ
4.15.30.5 Pinout
S 1 2
3 4
X20 DO F322
5 6
7 8
9 10
11 12
13 14
15 16
DO 1 DO 2
DO 3 DO 4
DO 5 DO 6
DO 7 DO 8
DO 9 DO 10
DO 11 DO 12
DO 13 DO 14
DO 15 DO 16
DO
Actuator 1 Actuator 2
Actuator 3 Actuator 4
Actuator 5 Actuator 6
Actuator 7 Actuator 8
Actuator 9 Actuator 10
Actuator 11 Actuator 12
Actuator 13 Actuator 14
Actuator 15 Actuator 16
GND GND
Caution!
If the module is operated outside of specifications, the output current can increase above the maximum
permissible nominal current. This applies to individual channels and also to the summation current
for the module.
Therefore sufficient cable cross sections or external safety measures must be used.
24 V GND
Reverse polarity
protection
24 V
High-side 1 GND
Output status
Logic
Output x
GND
28.8 V
24.0 V
100 mH
10 mH
100
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
28.8 V
24.0 V
100 mH
100
50
0.1 1 10 100
Max. switching cycles / second
(with 90% duty cycle)
Information:
If the maximum number of operating cycles per second is exceeded, an external inverse diode must
be used.
Operating conditions outside of the area in the diagram are not permitted!
Fixed modules require their data points to be in a specific order in the X2X frame. Cyclic access occurs according
to a predefined offset, not based on the register address.
Acyclic access is continues to be based on the register numbers.
1) The offset specifies where the register is within the CAN object.
The output status is transferred to the output channels with a fixed offset (<60 µs) in relation to the network cycle
(SyncOut).
Name:
DigitalOutput or
DigitalOutput01 to DigitalOutput16
The switching state of digital outputs 1 to 16 are stored in this register.
Data type Value
UINT Packed "DigitalOutput" values
USINT See bit structure
Bit structure:
Register 2, Offset 0:
Bit Name Value Information
0 Digital output 01 reset
0 DigitalOutput01
1 Digital output 01 set
... ...
0 Digital output 08 reset
7 DigitalOutput08
1 Digital output 08 set
Register 3, Offset 1:
Bit Name Value Information
0 Digital output 09 reset
0 DigitalOutput09
1 Digital output 09 set
... ...
0 Digital output 16 reset
7 DigitalOutput16
1 Digital output 16 set
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers' bits
should be set up individually as data points in the AS I/O mapping ("DigitalOutput01" through "DigitalOutput16") or
whether these registers should be displayed as an individual UINT data point ("DigitalOutput").
On the module, the output states of the outputs are compared to the setpoint states. The control of the output
driver is used for the setpoint states.
A change in the output state resets monitoring for that output. The status of each individual channel can be read.
A change in the monitoring status generates an error message.
Name:
StatusDigitalOutput or
StatusDigitalOutput01 to StatusDigitalOutput16
The status of digital outputs 1 to 16 is mapped in this register.
Data type Value
UINT Packed "StatusDigitalOutput" values
USINT See bit structure
Bit structure:
Register 30, Offset 1:
Bit Name Value Description
0 Channel 01: No error
0 StatusDigitalOutput01
1 Channel 01: Short circuit or overload
... ...
0 Channel 08: No error
7 StatusDigitalOutput08
1 Channel 08: Short circuit or overload
The "packed outputs" setting in the AS I/O configuration is used to determine whether all of these registers' bits
should be set up individually as data points in the AS I/O mapping ("StatusDigitalOutput01" through "StatusDigi-
talOutput16") or whether these registers should be displayed as an individual UINT data point ("StatusDigitalOut-
put").
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
Equal to the minimum cycle time
4.16.2 X20CM1201
The module can be used to configure and carry out simple movements. For this purpose, the module has one AB
encoder input and a total of 8 digital channels. Four of them are inputs, and the other 4 can be set as either an
input or an output. Various output bit patterns are stored directly in the module.
The module is perfectly suited for easy to create drive control tasks for program and event controlled motor move-
ments. Feed movements using drives with 2 speeds and forward/reverse movement are created easily and effi-
ciently.
• Command-dependent digital pattern output
• Counter-dependent output circuit
• Event-controlled abort criteria
• 4 digital inputs
• 4 digital channels, configurable as inputs or outputs
Product ID X20CM1201
Short description
I/O module 1 AB incremental encoder, 24 V, 4 digital inputs, 4 channels configurable as inputs or outputs
General information
Input voltage 24 VDC -15% / +20%
B&R ID code 0x21EF
Status indicators I/O function per channel, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
Outputs Yes, using the status LED and software (output error status)
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines.
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Digital inputs
Quantity 4 + 4 additional channels, configurable as inputs or outputs
Nominal voltage 24 VDC
Input voltage 24 VDC -15% / +20%
Input current at 24 VDC Approx. 1.3 mA
Input filter
Hardware ≤2 μs
Software -
Connection type 1-wire connections
Input circuit Sink
Input resistance 18.4 kΩ
Switching threshold
Low <5 VDC
High >15 VDC
Isolation voltage between channel and bus 500 Veff
AB incremental encoder
Quantity 1
Encoder inputs 24 V, asymmetrical
Counter size 32-bit
Input frequency Max. 100 kHz
Evaluation 4x
Encoder supply Module-internal, max. 600 mA
Overload behavior of the encoder supply Short circuit protection, overload protection
Digital outputs
Design Push / Pull / Push-Pull
Quantity Up to 4, configurable as inputs or outputs using software
Nominal voltage 24 VDC
Switching voltage 24 VDC -15% / +20%
Nominal output current 0.1 A
Total nominal current 0.4 A
Connection type 1-wire connections
Output circuit Sink or source
Output protection Thermal cutoff if overcurrent or short circuit occurs, integrated protection for switching inductances
Actuator supply Module-internal, max. 600 mA
Diagnostic status Output monitoring
Leakage current when switched off Max. 25 µA
Residual voltage <0.9 V at 0.1 A rated current
Peak short circuit current <10 A
Switching on after overload or short circuit cutoff Approx. 10 ms (depends on the module temperature)
Switching delay
0 -> 1 <2 µs
1 -> 0 <2 µs
Switching frequency
Resistive load Max. 24 kHz
Inductive load See section "Switching inductive loads" (at 90% duty cycle).
Braking voltage when switching off inductive loads Switching voltage + 0.6 VDC
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset status
1-8 Green Status of the corresponding digital signal
4.16.2.5 Pinout
r e
X20 CM 1201
1 5
2 6
3 7
4 8
Channel 1 Channel 5
Channel 2 Channel 6
Channel 3 Channel 7
Channel 4 Channel 8
Encoder 24 V + Encoder 24 V +
GND GND
CM
End neg
A +24 VDC
Motion neg
B GND
End pos
R +24 VDC
Fast/Slow Motion pos
GND
GND
Input x
VDR
Input status
I/O status
24 V
PTC
Encoder 24 V LED (green)
GND
GND
24 V
PTC
Output x
VDR
Output status Pull
GND
Output
monitoring
100 H 10 H 1H
1000
0.1 H
Coil resistance
Coil inductance
[Ω]
0.01 H
240 Ω ≙ 100 mA
0.1 1 10 100 1000 10000
1) The offset specifies the position of the register within the CAN object.
4.16.2.10.3 General
This is a low-end positioning module that supports 2 speed movements in positive and negative directions. No
active position check is performed. The movements are started using a command interface and stopped by the
position comparator (target position) or user-defined trigger conditions (input edge/ comparison). Every movement
step is time-monitored. Up to 8 movement steps can be linked to form one continuous movement.
Position, input states and timeout periods are checked during each system cycle.
Information:
No directional stop state is defined. To allow error handling, the directional stop state must be the
same as STOP. Speed changes in the same direction of movement are not evaluated as changes in the
operating mode of the movement.
The module supports 4 movement blocks: Each movement block contains up to 8 movement steps. Each step is
comprised of the following parameters:
• Target position - relative or absolute
• Timeout or delay
• Trigger condition - edge or comparator value (signal level)
A block's movement steps can be executed as one continuous movement. The following parameters must be
configured before the movement start command is issued:
• Step activation
• Step target position interpolation - relative or absolute
• Step speed - slow or fast
• Trigger mode - off or "Comparator value = true" or "Comparator value = false"
When a movement start command is issued, the mode of the active movement step is calculated based on the
preceding target position. Step parameters may also be changed after the start as long as the step direction is
not changed. Otherwise a movement error occurs. To ensure correct directional interpretation, the movement step
position/range is limited to ±1073741824.
The target position of a step configured with a trigger is evaluated as the end position (error position). This means
the position at the time of the trigger condition becomes the effective target position. Because this position is
unknown when the calculation is made by the movement generator, the set end position is used for calculating the
next absolute movement step. As a result, it is recommended to proceed with a relative movement step following a
triggered step. A successive absolute movement step must be outside the positioning range of the triggered step.
If a movement step is configured as a standstill, i.e. relative position = 0, or the new absolute position = previous
target position, a delay has occurred. If no trigger is configured, the parameter step timeout is evaluated as a simple
delay time and not as an error state.
The module constantly monitors the position tolerance, even when no movements are active. Jitter and overshoot
tolerances must be configured for both directions. Depending on the previous movement direction, a tolerance
window is calculated based on the current target position. Because the movement generator uses the last target
position, movements within the tolerance window must be avoided to prevent errors from occurring.
4.16.2.10.3.5 Homing
Homing is not implemented in this module as a movement function. The target position of a completed movement
can be applied as the home position via command.
A safe input status (masks and comparator values) for positive and negative movements must be configured.
Software end positions – minimum and maximum positions – can also be configured for both directions.
The module monitors these two positions from the time the parameter 0x93 or 0x95 "Positive directional setup
state" is set. Monitoring is ended when the parameter 0x94 "Stop state" is set.
Because a trigger condition aborts the movement step before a safety check, a hardware limit switch can also be
used as a trigger condition without generating an error.
4.16.2.10.4.1 No action
This command can be used as a placeholder during development or to separate 2 identical commands.
Code 0x00
Parameter 0
Data 0 to 3 0
This command can be used to configure how the values in the 4.16.2.10.5.6 "Read parameter number" and
4.16.2.10.5.7 "Read parameter data" registers are displayed. Up to 4 display values can be displayed simultane-
ously. Possible selections include the command parameters 0xC0 = current position, to 0xC3 = I/O states.
Code 0x01
Parameter Display control:
0 Scheduler off; Data 0 used for display
1 Scheduler cycle = X2X cycle; The next display cycle starts with each X2X cycle
2 Scheduler cycle = Command cycle; The next display cycle starts with each completed command
Data 0 Parameter number of display cycle 1 (Default: 0xC0 = current position)
... ...
Data 3 Parameter number of display cycle 4 (Default: 0xC0 = current position)
This command activates the movement interface. The status of the interface is displayed in the 4.16.2.10.5.5
"Read status" register (bit 5). The interface is disabled following a reset. This is necessary to ensure a consistent
parameter field.
Code 0x02
Parameter 0
Data 0 to 3 0
Parameter list
Parameter Description Parameter format
Movement blocks
Calculating the address: Addr = (BlockN - 1) * 32 + (StepN - 1) * 8
BlockN = 1 to 4
StepN = 1 to 8
Addr Movement BlockN StepN: Position (relative or absolute) DINT value
Addr + 1 Movement BlockN StepN: Timeout or delay Time format
Addr + 2 Movement BlockN StepN: Trigger condition (edge or comparator value) Trigger condition
Addr + 3 Movement BlockN StepN: Debug information (read only) 0
Configuration
0x80 Jitter tolerance negative (must be a negative value) Time format
0x81 Jitter tolerance positive (must be a positive value) Time format
0x82 Overshoot tolerance negative (must be a negative value) Time format
0x83 Overshoot tolerance positive (must be a positive value) Time format
0x84 - 0x87 Reserved
0x88 Setup time - negative direction Time format
0x89 Setup time - positive direction Time format
0x8a Stop time - negative direction Time format
0x8b Stop time - positive direction Time format
0x8C - 0x8F Reserved
0x90 Output configuration (push/pull) Output configuration
0x91 Output state - negative direction, high speed Output states
0x92 Output state - negative direction, low speed Output states
0x93 Output state, negative direction - setup Output states
0x94 Output state - stop Output states
0x95 Output state, positive direction - setup Output states
0x96 Output state - positive direction, low speed Output states
0x97 Output state - positive direction, high speed Output states
0x98 Safe input state - negative direction Safe input states
0x99 Safe input state - positive direction Safe input states
0x9A - 0x9B Reserved
0x9C Safe minimum position - negative direction DINT value
0x9D Safe maximum position - negative direction DINT value
0x9E Safe minimum position - positive direction DINT value
0x9F Safe maximum position - positive direction DINT value
0xA0 - 0xBF Reserved
Status indicators
0xC0 Current position 0
0xC1 Target position 0
0xC2 Error information 0; Error information
0xC3 I/O states 0; I/O states
0xC4 - 0xFF Reserved
DINT value
The possible values depend on the respective command.
Data type Value
DINT -2,147,483,648 to 2,147,483,647
Time format
Time in microseconds. System resolution is a result of the system cycle time (default: 50 μs).
Trigger condition
Depending on bits 2 and 3 in the data structure of each movement block, either the "edge" or "comparator value"
structure is selected as the trigger condition.
Edge
Bit Description Value Information
0 Falling edge - channel 01 0 Disabled
1 Enabled
... ...
7 Falling edge - channel 08 0 Disabled
1 Enabled
8 - 15 Reserved 0
16 Rising edge - channel 01 0 Disabled
1 Enabled
.. ...
23 Rising edge - channel 08 0 Disabled
1 Enabled
24 - 31 Reserved 0
Comparator value
Bit Description Value Information
0 Activation mask - channel 01 0 Disabled
1 Enabled
... ...
7 Activation mask - channel 08 0 Disabled
1 Enabled
8 - 15 Reserved 0
15 Comparative state - channel 01 0 or 1
...
23 Comparative state - channel 08 0 or 1
24 - 31 Reserved 0
Output configuration
Bit Description Value Information
0-1 Reserved 0
2 Push driver - channel 02 0 Disabled
1 Enabled
3 Push driver - channel 02 0 Disabled
1 Enabled
4-5 Reserved 0
6 Push driver - channel 04 0 Disabled
1 Enabled
7 Pull driver - channel 04 0 Disabled
1 Enabled
8-9 Reserved 0
10 Push driver - channel 06 0 Disabled
1 Enabled
11 Pull driver - channel 06 0 Disabled
1 Enabled
12 - 13 Reserved 0
14 Push driver - channel 08 0 Disabled
1 Enabled
15 Pull driver - channel 08 0 Disabled
1 Enabled
16 - 31 Reserved 0
Output states
Bit Description Value Information
0 Reserved 0
1 Channel 02 0 No action
1 Clear channel
2 Reserved 0
3 Channel 04 0 No action
1 Clear channel
4 Reserved 0
5 Channel 06 0 No action
1 Clear channel
6 Reserved 0
7 Channel 08 0 No action
1 Clear channel
8 - 16 Reserved 0
17 Channel 02 0 No action
1 Set channel
18 Reserved 0
19 Channel 04 0 No action
1 Set channel
20 Reserved 0
21 Channel 06 0 No action
1 Set channel
22 Reserved 0
23 Channel 08 0 No action
1 Set channel
24 - 31 Reserved 0
Error information
This table shows the read display value. The parameter for the display command is 0.
Bit Description Value Information
0 Tolerance error - negative 0 No error
1 Error occurred
1 Tolerance error - positive 0 No error
1 Error occurred
2 Timeout 0 No timeout
1 Timeout
3-7 Reserved 0
8 Safety monitoring error Inputs (hardwire limit switch) 0 No error
1 Error occurred
9 Safety monitoring error Position (software end position) 0 No error
1 Error occurred
10 - 15 Reserved 0
16 - 18 Error status information 000 Reserved
001 Negative directional stop state
010 Negative movement
011 Negative directional setup state
100 Stop state
101 Positive directional setup state
110 Positive movement
111 Positive directional stop state
19 Reserved 0
20 - 24 Invalid step number 000 to 111 Number of the step that does not contain any movement infor-
mation.
1000 Inactive movement step (tolerance check)
25 - 31 Reserved 0
I/O states
This table shows the read display value. The parameter for the display command is 0.
Bit Description Value Information
0 Input state - channel 01 0 or 1
... ...
7 Input state - channel 08 0 or 1
8 - 16 Reserved 0
17 Output state - channel 02 0 or 1
18 Reserved 0
19 Output state - channel 04 0 or 1
20 Reserved 0
21 Output state - channel 06 0 or 1
22 Reserved 0
23 Output state - channel 08 0 or 1
24 - 31 Reserved 0
This command can be used to assign the hardware channels to the AB counter. With an ABR counter, the R input
can be connected to any hardware channel as the trigger signal.
Code 0x04
Parameter See parameter structure
Data 0 See data structure
Data 1 to 3 0
Parameter structure:
Bit Description Value Information
0-1 Counter connection pair 00 Pair 1 (A: channel 01, B: channel 02)
01 Pair 2 (A: channel 03, B: channel 04)
10 Pair 3 (A: channel 05, B: channel 06)
11 Pair 4 (A: channel 07, B: channel 08)
2-7 Reserved 0
Data structure:
Bit Description Value Information
0-1 Counter mode 00 AB encoder: Up/down counter (A: timing, B: up/down signal)
01 Edge counter - channel A
10 Reserved
11 Edge counter - channel B
2 Counting direction 0 Positive
1 Negative
3-7 Reserved 0
4.16.2.10.4.6 Homing
Assumes the target position of the last successful movement step as a reference position.
Code 0x05
Parameter 0
Data 0 to 3 Home position
The movement step in progress is stopped. This command always results in a movement error.
Code 0x06
Parameter 0
Data 0 to 3 0
The movement error is is cleared. If this command is executed when the error is still present, the current position
is assumed as the target position. The basis of the relative position becomes unclear.
Code 0x07
Parameter 0
Data 0 to 3 0
Parameter structure:
Bit Description Value Information
0 Step 1 0 No movement.
1 Perform movement step.
... ...
7 Step 8 0 No movement.
1 Perform movement step.
Data structure:
Bit Description Value Information
0 Step 1 position setting: 0 Relative
1 Absolute
1 Step 1 speed: 0 Slow
1 Fast
2-3 Step 1 trigger mode: 00 No trigger
01 Edge trigger
10 Comparator value "true"
11 Comparator value "false"
4-7 Step 2 x Like step 1 / Bits 0 to 2
...
28 - 31 Step 8 x Like step 1 / Bits 0 to 2
At the end of each movement step, the command parameter "Addr + 3" (see 4.16.2.10.4.4 "Movement blocks -
Calculating the address" can be used to read the debug information selected in this register. This debug information
is shown in the 4.16.2.10.5.6 "Read parameter number" and 4.16.2.10.5.7 "Read parameter data" registers.
Code 0x00
Parameter 0 Error information (default)
1 Timestamp
2 Current position
3 Target position
Data 0 to 3 0
Commands must be sent by the application using the command interface. Due to the simple structure of the
command interface, it is also possible to send them via CAN.
All commands are executed as follows:
1 Write command parameters and command data to the respective register.
2 Write command with changed toggle bit.
When bit 7 in the command register is toggled, the module executes the comand with the command para-
meters and command data.
3 Wait until bit 7 in the response register (System Status) matches bit 7 in the command register.
4 Read additional status information from the response register if necessary.
5 If additional commands should be sent, proceed with step 1.
Name:
SendCommand
The commands described under 4.16.2.10.4 "Command description" can be sent from this register. Bit 7 must be
toggled to apply the commands.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-6 Command code x
7 Toggle bit for applying a new command x
Name:
SendCommandParam
Specific parameters for the command to be sent must be entered in this register. The required parameters are
listed under 4.16.2.10.4 "Command description" for the respective commands.
Data type Value Information
USINT x Command parameter
Name:
SendData
Specific parameters for the command to be sent must be entered in this register. The required data is listed under
4.16.2.10.4 "Command description" for the respective commands.
Data 0 to 3 are sent as a single DINT value. The following structure is used:
Name:
ReadStatus
The commands and the current status can be checked in this register. Bit 7 can be used to check whether an
issued command has been applied.
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0-1 Reserved 0
2 Position 0 Not yet reached
1 Reached
3 Motion 0 In motion
1 completed
4 Numerator 0 Not yet configured
1 Configured
5 Interface 0 Not enabled
1 Enabled
6 Command 0 No error
1 Error occurred
7 Command toggle bit x Value that was read
Name:
ReadIndex
The parameter number returned for a display command is shown in this register. See 4.16.2.10.4.2 "Configure
display mode" and 4.16.2.10.4.10 "Selecting the debug information"
Data type Value Information
USINT x Parameter numbers
Name:
ReadData
The parameter data returned for a display command is shown in this register. See 4.16.2.10.4.2 "Configure display
mode" and 4.16.2.10.4.10 "Selecting the debug information"
Data type Value Information
DINT x Parameter data
The following 4 registers correspond to display parameters 0xC0 to 0xC3 in the command description 4.16.2.10.4.4
"Configure parameters". This frees up the 4.16.2.10.5.7 "ReadData" register for other data.
Name:
ABRPosition
This register shows the current position in the current step. It corresponds with the parameter 0xC0 in section
4.16.2.10.4.4 "Configure parameters".
Data type Value
DINT -2,147,483,648 to 2,147,483,647
Name:
TargetABRposition
This register shows the target position of the current step. It corresponds with the parameter 0xC1 in section
4.16.2.10.4.4 "Configure parameters".
Data type Value
DINT -2,147,483,648 to 2,147,483,647
Name:
ErrorInfo
The error information is shown in this register. It corresponds with the parameter 0xC2 in section 4.16.2.10.4.4
"Configure parameters".
Data type Value
UDINT See bit structure.
Bit structure:
Bit Description Value Information
0 Tolerance error - negative 0 No error
1 Error occurred
1 Tolerance error - positive 0 No error
1 Error occurred
2 Timeout 0 No timeout
1 Timeout
3-7 Reserved 0
8 Safety monitoring error Inputs (hardwire limit switch) 0 No error
1 Error occurred
9 Safety monitoring error Position (software end position) 0 No error
1 Error occurred
10 - 15 Reserved 0
16 - 18 Error status information 000 Reserved
001 Negative directional stop state
010 Negative movement
011 Negative directional setup state
100 Stop state
101 Positive directional setup state
110 Positive movement
111 Positive directional stop state
19 Reserved 0
20 - 24 Invalid step number 000 to 111 Number of the step that does not contain any movement infor-
mation.
1000 Inactive movement step (tolerance check)
25 - 31 Reserved 0
Name:
DigitalInput01 to DigitalInput08
The status of the digital inputs or read outputs are shown in this register. It corresponds with the parameter 0xC3
in section 4.16.2.10.4.4 "Configure parameters".
Data type Value
USINT See bit structure.
Bit structure:
Bit Description Value Information
0 DigitalInput01 0 or 1 Input status - channel 1
... ...
7 DigitalInput08 0 or 1 Input status - channel 8
Enable interface
Value Description
Code 0x02
Parameter 0
Data 0 to 3 0
Configure parameters
Value
Code 0x03
Parameter Parameter numbers
Data 0 to 3 Parameter data
0x90 0x0000CCC0 Output configuration: Channel 04, channel 06, channel 08 as push/pull outputs
0x91 0x00280080 Output states - fast negative movement: Set channels 04 and 06, clear channel 08
0x92 0x00200088 Output states - slow negative movement: Set channel 06, clear channels 04 and 08
0x93 0x000000A8 Output states - negative setup: Clear channels 04, 06 and 08
0x94 0x000000A8 Output states - stop: Clear channels 04, 06 and 08
0x95 0x000000A8 Output states - positive setup: Clear channels 04, 06 and 08
0x96 0x00800028 Output states - slow positive movement: Set channel 08, clear channels 04 and 06
0x97 0x00880020 Output states - fast positive movement: Set channels 04 and 08, clear channel 06
0x98 0x00100010 Safe input state - negative: Channel 05 active, status of channel 05 (level) = 1
0x99 0x00400040 Safe input state - positive: Channel 07 active, status of channel 05 (level) = 1 Code 0x04
Configure counters
Value Description
Code 0x04
Parameter 0x03 Counter pair 1
Data 0 0 AB encoder, positive direction
Data 1 to 3 0
Configure parameters
Value
Code 0x03
Parameter Parameter numbers
Data 0 to 3 Parameter data
Start movement
Value Description
Code 0x08 Block 1
Parameter 0x07 Activate steps 1 to 3
Data 0 to 3 0x00000411 Step 1: absolute, slow, trigger off
Step 2: absolute, slow, trigger off
Step 3: relative, slow, trigger on edge
Configure parameters
Value
Code 0x03
Parameter Parameter numbers
Data 0 to 3 Parameter data
Start movement
Value Description
Code 0x08 Block 1
Parameter 0x03 Activate steps 1 and 2
Data 0 to 3 0x00000011 Step 1: absolute, slow, trigger off
Step 2: absolute, slow, trigger off
Configure parameters
Value
Code 0x03
Parameter Parameter numbers
Data 0 to 3 Parameter data
Start movement
Value Description
Code 0x08 Block 1
Parameter 0x07 Activate steps 1 to 3
Data 0 to 3 0x00000011 Step 1: absolute, slow, trigger off
Step 2: absolute, slow, trigger off
Step 3: relative, trigger off
Name:
CycleTimeCff
This register configures the module's system cycle time.
Data type Value Information
UINT 25 to 255 System cycle time in µs (default = 50 µs)
Name:
PowerSupply01
This register shows the status of the integrated encoder supply. A faulty encoder power supply is displayed as
a warning.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0 PowerSupply01 0 24 VDC encoder power supply OK
1 24 VDC encoder power supply faulty
1-7 Reserved -
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
100 µs
The minimum cycle time defines how far the bus cycle can be reduced without communication errors occurring.
It should be noted that very fast cycles decrease the idle time available for handling monitoring, diagnostics and
acyclic commands.
Minimum cycle time
100 μs
4.16.3 X20DC1073
The module is equipped with a SinCos encoder interface. The input signals are monitored. This makes it possible
to detect open or shorted lines as well as encoder supply failures.
• SinCos encoder interface
• Encoder input monitoring
• 5 VDC and GND for encoder supply
• NetTime function: Timestamp for position
SinCos encoders
SinCos encoders with 1 Vss are mostly used in linear drives and systems with high-resolution optical or magnetic
position measurement systems. The module can process input signals with a frequency of up to 400 kHz.
NetTime position timestamp
Highly dynamic positioning tasks require not only the position value, but also the exact time at which the position
was determined. The module has a NetTime function for this, which adds a timestamp to the recorded position
with microsecond accuracy.
The module provides the PLC with the position value and timestamp as absolute time value. The NetTime mech-
anisms ensure that the PLC NetTime clock and the local NetTime clock on the module have exactly the same
absolute time at all times.
Product ID X20DC1073
Short description
I/O module 1x SinCos input
General information
B&R ID code 0xAEC6
Status indicators Counting direction, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software
Counting direction Yes, using status LED
Power consumption
Bus 0.01 W
Internal I/O 1.3 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
Channel - Bus Yes
Channel - Channel No
Type of signal lines Shielded cables must be used for all signal lines
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Encoder inputs
Type SinCos
Angular position resolution 13-bit, with a 1 VSS signal
Encoder monitoring Yes
Max. encoder cable length Max. 20 m, see "Calculation of the maximum encoder cable length"
Sine/Cosine inputs
Signal transmission Differential signals, symmetrical
Signal frequency DC up to 400 kHz
Differential voltage 1 VSS
Common-mode voltage Max. ±10 V
Terminating resistors 120 Ω
Encoder supply
Output voltage 5V
Min. output voltage at 300 mA 4.86 V
Load capability 300 mA
Protective measures
Overload protection Yes
Short circuit protection Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating See section "Derating"
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB12 terminal block separately
Order 1x X20BM11 bus module separately
Spacing 12.5+0.2 mm
For a description of the various operating modes, see the 2.11.1 "re LEDs" section.
Figure LED Color Status Description
r Green Off No power to module
Single flash RESET mode
Double flash BOOT mode (during firmware update)1)
Blinking PREOPERATIONAL mode
On RUN mode
e Red Off No power to module or everything OK
On Error or reset state. Possible cause:
• Encoder supply error
Single flash I/O error. Possible cause:
• Sine/Cosine relative position error (open line)
Single flash, inverted Error or reset state and I/O error
UP Green On The "UP/DN" LEDs are lit depending on the rotational direction and the
speed of the connected encoder.
The "UP" LED indicates when the encoder position changes in the pos-
itive direction.
DN Green On The "DN" LED indicates when the encoder position changes in the neg-
ative direction.
4.16.3.5 Pinout
r e
X20 DC 1073
UP
DN
A A\
B B\
R R\
Encoder 5V + GND
DC SinCos encoders
A
A\
Sine-Cosine
B
B\
R
Reference track
R\
A\
B\
Input status
Evaluation
R\
24 V UP
DC
Encoder 5 V
DC
LED (green)
GND
GND
DN
LED (green)
Figure 415: Circuit diagram for the encoder supply and LEDs
4.16.4 X20DS1828
The X20DS1828 module is equipped with a HIPERFACE encoder interface. This module can be used to evaluate
encoders installed in motors from other manufacturers as well as encoders for external axes (encoders that scan
any machine movement). The input signals are monitored, making it possible to detect open or shorted lines as
well as encoder supply failures.
• HIPERFACE encoder interface
• Encoder input monitoring
• 11 VDC and GND for encoder supply
• NetTime function: Time stamp for position
HIPERFACE
HIPERFACE is a standard developed by Max Stegmann GmbH (www.stegmann.de), which like EnDat incorporates
the advantages of absolute and incremental position measurement while also offering a read/write parameter
memory in the encoder. With absolute position measurement (the absolute position is sampled serially), a homing
procedure is usually not required. Where necessary, a multi-turn encoder should be installed. To save costs, a
single-turn encoder and a reference switch can also be used. In this case, a homing procedure must be carried out.
The incremental process allows the short delay times necessary for position measurement on drives with excep-
tional dynamic properties. With the sinusoidal incremental signal and the fine resolution in the HIPERFACE mod-
ule, a very high positioning resolution is achieved in spite of the moderate signal frequencies used.
NetTime position timestamp
Highly dynamic positioning tasks require not only the position value, but also the exact time at which the position
was determined. The module has a NetTime function for this, which adds a timestamp to the recorded position
with microsecond accuracy.
The module provides the PLC with the position value and timestamp as absolute time value. The NetTime mech-
anisms ensure that the PLC NetTime clock and the local NetTime clock on the module have exactly the same
absolute time at all times.
Product ID X20DS1828
Short description
I/O module 1x HIPERFACE interface
General information
B&R ID code 0xAEC7
Status indicators Counting direction, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software status
Counting direction Yes, using status LED
4.16.4.5 Pinout
r e
X20 DS 1828
UP
DN
D\ D
DS HIPERFACE encoder
SIN
REF SIN
Process data channel
COS
REF COS
D\
Parameter channel
D
4.16.4.7 Input diagram for the process data channel (sine-cosine track)
SIN
REF SIN
COS
REF COS
D DIN
RS485
drivers DOUT
D\
24 V UP
DC
Encoder 11 V
DC
LED (green)
GND
GND
DN
LED (green)
The following configuration registers can be used to define various module settings. They can be used, for example,
to modify the module's behavior on an X2X Link network. The X20DS1828 also provides one optional register.
Names (pChannelName):
CfO_SIframeGenID
This register can be used to define when the synchronous/cyclic input data is generated. "X2X cycle optimized"
should be set for jitter-free data acquisition. "Minimal latency" can be set for the best performance.
Data type Value
USINT 09 ... Minimal latency
14 ... X2X cycle optimized (bus controller default setting)
This module can read a position when used together with a HIPERFACE encoder. The received position data is
prepared in two different formats and given a timestamp. Six registers are available for further processing. This
allows the user to select the format that best fits the application at hand.
4.16.4.10.6.1 SDCLifeCount
Names (pChannelName):
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Value
SINT -128 to 127
Names (pChannelName):
PositionHW
PositionHW_64 / PositionHW_64_CANIO
PositionLW
PositionLW_64 / PositionLW_64_CANIO
The absolute position of the encoder is defined using 64-bit resolution. The position value is stored in the Position-
HW and PositionLW registers. The upper 32 bits are stored the PositionHW register, while the lower 32 bits are
stored in the PositionLW register.
Data type Value
2x UDINT 0 to 4,294,967,295
Names (pChannelName):
Position
Position_32
The SDC library requires a signed 32-bit position value. The position's low word can be accessed separately for
this. The value can also be used as default position value, however.
Data type Value
DINT -2,147,483,648 to 2,147,483,647
Names (pChannelName):
PosTime
PosTime_32
In this register, the current NetTime value is assigned to each position value read. The NetTime is recorded with
µs accuracy.
Data type Value
DINT -2.147.483.648 to 2.147.483.647 ... Nettime [µs]
Names (pChannelName):
PosTime
PosTime_16
The SDC library requires a 16-bit value. The NetTime value is therefore also generated in this format.
Data type Value
INT -32.768 to 32.767 ... Nettime [µs]
4.16.4.10.6.6 PosCycle
Names (pChannelName):
PosCycle
PosCycle_8 / PosCycle_8_CANIO
PosCycle is an integer counter that is incremented as soon as the module has saved a new valid position value.
Data type Value
SINT -128 to 127
This module can be used to diagnose error states. There are two ways the X20DS1828 performs error diagnostics:
• Module-based diagnostics
• HIPERFACE-based diagnostics
Like most B&R modules, the X20DS1828 is able to detect errors on its own. It diagnoses five different errors or
warnings. The error bits can be retrieved individually or grouped together.
Error registers
Names (pChannelName):
ErrorEnableID_0F08
ErrorInfo / ErrorInfo_CANIO
AckErrorInfo / AckErrorInfo_CANIO
Names of individual bits (pChannelName):
EncoderSupplyError
VssCheckError
PositionError
HfComError
HfRefWarning
AckEncoderSupplyError
AckVssCheckError
AckPositionError
AckHfComError
AckHfRefWarning
B&R's approach to error management uses three independent registers.
Data type Value
USINT See bit structure
The implemented diagnostics algorithms can be enabled or disabled using the Enable byte.
"ErrorEnableID_0F08" structure:
Bit Name Information
0 Encoder supply 0 Error detection disabled
1 Error detection enabled (bus controller default)
1 Reserved -
2 Vss Sin/Cos 0 Error detection disabled
1 Error detection enabled (bus controller default)
3 Position error 0 Error detection disabled
1 Error detection enabled (bus controller default)
4 HIPERFACE communication 0 Error detection disabled
1 Error detection enabled (bus controller default)
5 HIPERFACE reference warning 0 Warning disabled
1 Warning enabled (bus controller default)
6-7 Reserved -
The State byte indicates any errors or warnings that have not yet been acknowledged.
"ErrorInfo" structure:
Bit Name Information
0 EncoderSupplyError 0 No error
1 Encoder supply error
1 Reserved -
2 VssCheckError 0 No error
1 Vss error on the Sin/Cos track
3 PositionError 0 No error
1 Position error
4 HfComError 0 No error
1 HIPERFACE communication error
5 HfRefWarning 0 No warning
1 HIPERFACE reference warning
6-7 Reserved -
Encoder supply
The encoder supply voltage is below the permitted limit.
Vss Sin/Cos
The voltage value for the Sin/Cos track violates the configured limit values.
→ See registers SinCosVssMin and SinCosVssMax.
Position error
The position value determined violates internal requirements.
HIPERFACE communication
Communication error on the HIPERFACE interface (RS485)
→ See register HfErrorCode.
Memory areas are provided in the HIPERFACE standard for error diagnostics. Error management has been ad-
justed in order to use error detection in accordance with the HIPERFACE standard. An additional register has
been implemented in the module to provide this area in the encoder's memory. This error memory is mirrored in
the module's registers and can be interpreted by the user. Detailed information regarding the errors that can be
detected in this way can be found in the encoder's manual.
HfErrorCode
Names (pChannelName):
HfErrorCode
This register stores the error code that identifies the current problem with the HIPERFACE interface.
Data type Value
UDINT See bit structure
In addition to the digital HIPERFACE interface, this module is also equipped with an analog interface for sampling
a differential sine-cosine signal. To increase the resolution, the EnDat standard supports cooperation between
the analog and digital data. This enables a highly dynamic representation of the position while maintaining high
resolution.
4.16.4.10.8.1 SinCosEnable
Names (pChannelName):
SinCosEnable
This register must always have the value 1 for configuration reasons.
Data type Value
USINT 1!
Bus controller default: 1
4.16.4.10.8.2 SinCosRefSource
Names (pChannelName):
SinCosRefSource
This register must always have the value 3 for configuration reasons.
Data type Value
USINT 3!
Bus controller default: 3
4.16.4.10.8.3 SinCosVssMin
Names (pChannelName):
SinCosVssMin
The SinCosVssMin register specifies the lower limit value for the peak-to-peak voltage of the sine/cosine track.
The incoming signal is monitored in this way. If the incoming value falls below this specified limit, then the module
reports the corresponding error.
Data type Value
UINT 0 to 1500 [mV]
Bus controller default: 800
4.16.4.10.8.4 SinCosVssMax
Names (pChannelName):
SinCosVssMax
The SinCosVssMax register specifies the upper limit value for the peak-to-peak voltage of the sine/cosine track.
The incoming signal is monitored in this way. If the incoming value exceeds this specified limit, then the module
reports the corresponding error.
Data type Value
UINT 0 to 1500 [mV]
Bus controller default: 1200
4.16.4.10.8.5 SinCosQuitTime
Names (pChannelName):
SinCosQuitTime
If an error is detected on the analog interface, the last correctly read values remain valid. An interval can be defined
here at which the module begins receiving correct values again after the error state without processing them further
internally. Only then will newly sampled correct analog values be recognized as valid.
Data type Value
UDINT 0 to 20,000,000 [µs]
Bus controller default: 100000
4.16.4.10.9 HIPERFACE
HIPERFACE builds upon the RS-485 (EIA-485) specification and permits communication with multiple HIPER-
FACE slaves.
There are two methods available to use the slave data in a PLC program. One is to store the necessary slave
values temporarily in the module, where they can then be provided to the CPU. The other is to use the module's
FlatStream mode, which supports the full range of commands defined in the HIPERFACE specification.
Additional information regarding the HIPERFACE specification is provided in the "Description of HIPERFACE"
document.
HfMode
Names (pChannelName):
HfMode
This register is used to enable the HIPERFACE interface and must always be set to the value 1 for configuration
reasons.
Data type Value
USINT 1!
Bus controller default: 1
HfParity
Names (pChannelName):
HfParity
This register configures the parity bit for the interface.
Data type Value
USINT 69 ... E → Even parity
78 ... N → No parity
79 ... O → Odd parity
Bus controller default: 69
HfCharTimeout
Names (pChannelName):
HfCharTimeout
This register configures the time that the module waits after receiving the last data block to add additional data to
the current data packet (frame). When this time expires, the data received thus far is saved in a frame. The transfer
is complete and the data can be evaluated.
Information:
Time is specified as a char value in order to ensure identical behavior regardless of the baud rate
setting.
Data type Value
USINT 1 to 255 [char]
Bus controller default: 55
HfBaud
Names (pChannelName):
HfBaud
This register configures the baud rate (transfer rate) of the interface.
The module does not allow a transfer rate of 600 baud.
Data type Value
UDINT 1200, 2400, 4800, 9600, 19200, 38400 ... [Baud]
Bus controller default: 9600
HfRepressErrTime
Names (pChannelName):
HfRepressErrTime
This register configures the minimum time that an error code remains in the "HfErrorCode" register. This makes it
possible to ensure that the CPU registers every error that occurs.
Data type Value
UDINT 1 to 20,000,000 [µs]
Bus controller default: 100000
HfRefAdr
Names (pChannelName):
HfRefAdr
This module can manage up to 32 HIPERFACE slaves via its the digital interface. High-resolution position sampling,
however, requires information from both the digital and analog interfaces. The HIPERFACE address of the station
whose sine/cosine track is being read by the module is entered in this register. If there is only one slave on the
network, the broadcast address (255) can also be used.
Data type Value
USINT 0 ... Operation without sine/cosine track
64 to 95 ... Open address range for max. 32 HIPERFACE slaves
255 ... Broadcast address
Bus controller default: 255
HfRefWidth
Names (pChannelName):
HfRefWidth
This register sets the absolute width for the sampled position. The number of bits must be taken from the data
provided by the encoder manufacturer and usually consists of three values:
• 5 bits: Resolution of the digital absolute position
• x bits: HIPERFACE data format, number of bits per revolution
• 2y bits: Number of sine/cosine periods per revolution
The sum of the sampled values results in the HfRefWidth (HfRefWidth = 5+x+y).
Data type Value
USINT 8 to 32
Bus controller default: 32
The digital interface provides the option of assigning a HIPERFACE slave a specific ID. Its parameter data can
be queried when booting the PLC, for example. Any deviations from the previous hardware constellation can then
be handled accordingly in the program.
Configuration
The parameter to be read is specified by two registers. One of the registers contains the address of the desired
HIPERFACE slave; the other contains a code for the value to be read.
HfAdrIdent
Names (pChannelName):
HfAdrIdent
This register specifies the address of the HIPERFACE slave whose parameter should be read by the module.
Data type Value
USINT 0 ... Identification disabled
64 to 95 ... Open address range for max. 32 HIPERFACE slaves
255 ... Broadcast address (when operating with one slave)
Bus controller default: 0
HfSelectionIdent
Names (pChannelName):
HfSelectionIdent
This register defines the parameters that should be provided in the slave response and buffered in the module's
HfExtByte register.
Data type Value
USINT Selection codes
0 ... Serial number
1 ... Firmware date
2 ... High part of firmware version
3 ... Low part of firmware version
Bus controller default: 0
Call
After being configured correctly, the selected parameter is transmitted cyclically to the module. There are eight
registers that serve as temporary storage. The module confirms successful receipt by setting the HfIdentOkByte.
HfIdentOkByte
Names (pChannelName):
HfIdentOkByte
This register's bits provide information about the validity of the latest ID values in temporary storage.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Information
0 HfIdentOk01 0 Parameter 01 invalid
1 Parameter 01 valid
1-7 Reserved -
HfRs485Settings
Names (pChannelName):
HfRs485Settings
This register temporarily stores the current network configuration expected by the slave. The register value is
specifically structured for HIPERFACE.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Information
0-2 Speed code 0-6 Baud rate:
1 (001 b) ... 1200 baud
2 (010 b) ... 2400 baud
3 (011 b) ... 4800 baud
4 (100 b) ... 9600 baud
5 (101 b) ... 19200 baud
6 (110 b) ... 38400 baud
Bus controller default: 4
3 Reserved -
4 Number of parity bits 0 No parity bit
1 One parity bit (default)
5 Type of parity bit 0 Even (default)
1 Odd
6 Timeout behavior 0 Timeout 11/baud rate
1 Timeout 4*11/baud rate (default)
7 Network behavior 0 Bus
1 Direct connection (default)
HfEncoderType
Names (pChannelName):
HfEncoderType
This register temporarily stores the ID of the current encoder. The register value is structured specifically for each
slave and must be looked up in the encoder's data sheet.
Data type Value
USINT 0 to 255
HfEepromSize
Names (pChannelName):
HfEepromSize
This register stores the size of the EEPROM being used. The number of 16-byte blocks is specified.
Data type Value
USINT 0 to 255 [16-byte blocks]
HfOptionFlags
Names (pChannelName):
HfOptionFlags
This register stores slave-specific hardware and software settings.
Data type Value
USINT 0 to 255
HfFreeMemory
Names (pChannelName):
HfFreeMemory
This register shows the number of free 16-byte blocks remaining on the HIPERFACE slave.
Data type Value
USINT 0 to 255 [16-byte blocks]
HfDataFields
Names (pChannelName):
HfDataFields
This register indicates the number of data fields that have been written thus far.
Data type Value
USINT 0 to 255
HfExtByte
Names (pChannelName):
HfExtByte01
HfExtByte[02...10]
These registers provide the respective parameters according to how "HfSelectionIdent" is configured.
Data type Value
USINT 0 to 255
This module can read up to two additional position values via the HIPERFACE interface and provide them to the
PLC. Each position value is accompanied by a timestamp.
Configuration
The address must be specified in order to read the position value from the respective HIPERFACE interface. One
address register is provided for each position value.
AddPosAdr
Names (pChannelName):
AddPosAdr01
AddPosAdr02
These registers specify the addresses of the HIPERFACE slaves whose position values should be processed in
the module.
Data type Value
USINT 0 ... Additional encoder position disabled
64 to 95 ... Open address range for max. 32 HIPERFACE slaves
255 ... Broadcast address (when operating with one slave)
Bus controller default: 0
Call
After being configured correctly, the position value is transmitted cyclically to the module. Each slave has five reg-
isters that serve as temporary storage. The module automatically generates the timestamp and confirms success-
ful transmission by setting the corresponding AddPosOK0x bit. The HIPERFACE specification does not specify in
which format the parameters must be received. The module therefore provides the position value and time in two
formats. Which of the position registers should be used for further processing depends on the HIPERFACE slave.
The user is free to define the format of the timestamp.
AddPosOkByte
Names (pChannelName):
AddPosOk01
AddPosOk02
This register's bits provide information about the validity of the last position values in temporary storage.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Information
0 AddPosOk01 0 Position value 01 invalid
1 Position value 01 valid
1 AddPosOk02 0 Position value 02 invalid
1 Position value 02 valid
2-7 Reserved -
AddPosition (32-bit)
Names (pChannelName):
AddPosition01
AddPosition02
AddPosition01_32
AddPosition02_32
These registers provide the corresponding position values as signed 4-byte values.
Data type Value
DINT -2,147,483,648 to 2,147,483,647
AddPosition (16-bit)
Names (pChannelName):
AddPosition01
AddPosition02
AddPosition01_16
AddPosition02_16
These registers provide the corresponding position values as signed 2-byte values.
Data type Value
INT -32,768 to 32,767
AddPosTime (32-bit)
Names (pChannelName):
AddPosTime01
AddPosTime02
AddPosTime01_32
AddPosTime02_32
These registers provide the timestamps of the most recently received position values as signed 4-byte values.
Data type Value
DINT -2.147.483.648 to 2.147.483.647 ... Nettime [µs]
AddPosTime (16-bit)
Names (pChannelName):
AddPosTime01
AddPosTime02
AddPosTime01_16
AddPosTime02_16
These registers provide the timestamps of the most recently received position values as signed 2-byte values.
Data type Value
INT -32.768 to 32.767 ... Nettime [µs]
This module can read up to four analog values (16-bit) via the HIPERFACE interface and provide them to the PLC.
Each analog value is accompanied by a timestamp.
Configuration
The analog value to be read is specified by two registers. One of them contains the address of the desired station,
and the other the channel of the parameter to be read. An overview of analog values that can be read is provided
in the data sheet for the respective slave.
AnalogAdrCh
Names (pChannelName):
AnalogAdrCh01
AnalogAdrCh02
AnalogAdrCh03
AnalogAdrCh04
These registers specify the addresses of the HIPERFACE slaves whose analog values should be processed in
the module. To query multiple values from one HIPERFACE slave, it may make sense to write the same address
to different AnalogAdrCh registers.
Data type Value
USINT 0 ... Additional analog values disabled
64 to 95 ... Open address range for max. 32 HIPERFACE slaves
255 ... Broadcast address (when operating with one slave)
Bus controller default: 0
AnalogCh
Names (pChannelName):
AnalogCh01
AnalogCh02
AnalogCh03
AnalogCh04
These registers define the channel to be read that is written by the bus station to the module's temporary storage.
Data type Value
USINT See encoder data sheet
Bus controller default: 0
Call
After being configured correctly, the analog value is transmitted cyclically to the module. There are five registers
that serve as temporary storage. The module automatically generates the timestamp and confirms successful
transmission by setting the corresponding AnalogChOk0x bit. The HIPERFACE specification does not specify in
which format the parameters must be received. The module therefore provides the value and time in two formats.
Which of the value registers should be used for further processing depends on the peripheral equipment. The user
is free to define the format of the timestamp.
AnalogChOkByte
Names (pChannelName):
AnalogChOk01
AnalogChOk02
AnalogChOk03
AnalogChOk04
This register's bits provide information about the validity of the values in temporary storage.
Data type Value
USINT See bit structure
Bit structure:
Bit Name Information
0 AnalogChOk01 0 Analog value 01 invalid
1 Analog value 01 valid
1 AnalogChOk02 0 Analog value 02 invalid
1 Analog value 02 valid
2 AnalogChOk03 0 Analog value 03 invalid
1 Analog value 03 valid
3 AnalogChOk04 0 Analog value 04 invalid
1 Analog value 04 valid
4-7 Reserved -
AnalogChValue (unsigned)
Names (pChannelName):
AnalogChValue01_u
AnalogChValue02_u
AnalogChValue03_u
AnalogChValue04_u
These registers provide the current analog values as signed 2-byte values.
Data type Value
UINT 0 to 65,535
AnalogChValue (signed)
Names (pChannelName):
AnalogChValue01_s
AnalogChValue02_s
AnalogChValue03_s
AnalogChValue04_s
These registers provide the corresponding analog values as signed 2-byte values.
Data type Value
INT -32,768 to 32,767
AnalogChTime (32-bit)
Names (pChannelName):
AnalogChTime01_32
AnalogChTime02_32
AnalogChTime03_32
AnalogChTime04_32
These registers provide the timestamps of the most recently received analog values as signed 4-byte values.
Data type Value
DINT -2,147,483,648 to 2,147,483,647 [µs]
AnalogChTime (16-bit)
Names (pChannelName):
AnalogChTime01_16
AnalogChTime02_16
AnalogChTime03_16
AnalogChTime04_16
These registers provide the timestamps of the most recently received analog values as signed 2-byte values.
Data type Value
INT -32768 to 32,767 [µs]
4.16.4.10.10.1 Introduction
B&R offers an additional communication method for some modules. "FlatStream" was designed for X2X and
POWERLINK networks and allows data transmission to be adapted to individual demands. Although this method
is not 100% real-time capable, it still allows data transmission to be handled more efficiently than with standard
cyclic polling.
Field device
X2X language
Cyclic call
via I/O mapping
B&R CPU
Cyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
Acyclic call
via
library functions
B&R CPU
Acyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
FlatStream
The physical properties of the bus system limit the amount of data that can be transmitted during one bus cycle.
With FlatStream communication, all messages are viewed as part of a continuous data stream. Long data streams
must be broken down into several fragments that are sent one after the other. To understand how the receiver puts
these fragments back together to get the original information, it is important to understand the difference between
a message, a segment, a sequence and an MTU.
Message
A message refers to information exchanged between two partner stations. The length of a message is not restricted
by the FlatStream communication method. Nevertheless, module-specific limitations must be considered.
Segment (logical division of a message):
A segment has a finite size and can be understood as a section of a message. The number of segments per
message is arbitrary. So that the recipient can correctly reassemble the transmitted segments, each segment
is preceded by a byte with additional information. This control byte contains information such as the length of a
segment and whether the approaching segment completes the message. This makes it possible for the receiving
station to interpret the incoming data stream correctly.
Sequence (how a segment needs to be arranged physically):
The maximum size of a sequence corresponds to the number of enabled Rx or Tx bytes (later: "MTU"). The
transmitting station splits the transmit array into valid sequences. These sequences are then written successively
to the MTU and transmitted to the receiving station where they are put back together again. The receiver stores
the incoming sequences in a receive array, obtaining an image of the data stream in the process.
With FlatStream communication, the number of sequences sent are counted. Successfully transmitted sequences
must be acknowledged by the receiving station to ensure the integrity of the transmission.
MTU (Maximum Transmission Unit) – Physical transport:
MTU refers to the enabled USINT registers used with FlatStream. These registers can accept at least one se-
quence and pass it on to the receiving station. A separate MTU is defined for each direction of communication.
The OutputMTU defines the number of FlatStream Tx bytes, and the InputMTU specifies the number of FlatStream
Rx bytes. The MTUs are transported cyclically via the X2X Link, increasing the load with each additional enabled
USINT register.
Features
FlatStream messages are not transmitted cyclically or in 100% real time. Many bus cycles may be needed to trans-
mit a particular message. Although the Rx and Tx registers are exchanged between the transmitter and the receiv-
er cyclically, they are only processed further if explicitly accepted by the "InputSequence" or "OutputSequence"
register.
Behavior in the event of an error (brief summary)
The protocol for X2X and POWERLINK networks specifies that the last valid values should be retained when
disturbances occur. With conventional communication (cyclic/acyclic data queries), this type of error can generally
be ignored.
In order for communication to also take place without errors using FlatStream, all of the sequences issued by the
receiver must be acknowledged. If Forward functionality is not used, then subsequent communication is delayed
for the length of the disturbance.
If Forward functionality is being used, the receiving station receives a transmission counter that is incremented
twice. The receiver stops, i.e. it no longer returns any acknowledgments. The transmitting station uses the Se-
quenceAck to determine that the transmission was faulty and that all affected sequences will have to be repeated.
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Five registers are available for configuring FlatStream. The default configuration can be used to transmit small
amounts of data relatively easily.
Information:
The CPU communicates directly with the field device via the "OutputSequence" and "InputSequence"
as well as the enabled Tx and Rx bytes. For this reason, the user needs to have sufficient knowledge
of the communication protocol being used on the field device.
FlatStream configuration
To use FlatStream, the program sequence must first be expanded. The cycle time of the FlatStream routines must
be set to a multiple of the bus cycle. Other program routines should be implemented in Cyclic #1 to ensure data
consistency.
At the absolute minimum, the "InputMTU" and "OutputMTU" registers need to be configured. All other registers are
filled in with default values at the beginning and can be used immediately. These registers are used for additional
options, e.g. to transmit data in a more compact way or to increase the efficiency of the general procedure.
The Forward registers extend the functionality of the FlatStream protocol. This functionality is useful for substan-
tially increasing the FlatStream data rate, but it also requires quite a bit of extra work when creating the program
sequence.
Name:
OutputMTU
InputMTU
These registers define the number of enabled Tx or Rx bytes, i.e. the maximum size of a sequence. The user must
consider that the more bytes made available also means a higher load on the bus system.
Information:
In the rest of this documentation, the names "OutputMTU" and "InputMTU" do not refer to the registers
explained here. Instead, they are used as synonyms for the currently enabled Tx or Rx bytes.
Data type Value
USINT See the module-specific register overview (theoretically: 3 to 27)
FlatStream operation
When using FlatStream, the communication direction is enormously important. For sending data to a module ("out-
put" direction), the Tx bytes are used. For receiving data from a module ("input" direction), the Rx bytes are used.
The "OutputSequence" and "InputSequence" registers are used to control and ensure that communication is taking
place properly, i.e. the transmitter issues the directive that the data should be accepted and the receiver acknowl-
edges that a sequence has been transmitted successfully.
Name:
TxByte1 to TxByteN
RxByte1 to RxByteN
(The value the number N is different depending on the bus controller model used.)
The Tx and Rx bytes are cyclic registers used to transport the payload data and the necessary control bytes. The
number of active Tx and Rx bytes is taken from the configuration of the "OutputMTU" and "InputMTU" registers,
respectively.
In the user program, only the Tx and Rx bytes from the CPU can be used. The corresponding counterparts are
located in the module and are not accessible to the user. For this reason, names were chosen from the CPU point
of view.
• "T" - "Transmit" → CPU transmits data to the module.
• "R" - "Receive" → CPU receives data from the module.
Data type Value
USINT 0 to 65535
Control bytes
In addition to the payload data, the Tx and Rx bytes also transmit the necessary control bytes. These control bytes
contain additional information about the data stream so that the receiver can reconstruct the original message from
the transmitted segments.
Bit structure of a control byte
Bit Name Value Information
0-5 SegmentLength 0 - 63 Size of the subsequent segment in bytes (default: Max. MTU size - 1)
6 nextCBPos 0 Next control byte at the beginning of the next MTU
1 Next control byte directly after the end of the current segment
7 MessageEndBit 0 Message continues after the subsequent segment
1 Message ended by the subsequent segment
SegmentLength
The segment length lets the receiver know the length of the coming segment. If the configured segment length
is insufficient for a message, then the information must be distributed over several segments. In these cases, the
actual end of the message is detected using bit 7 of the control byte.
Information:
The control byte is not included in the calculation to determine the segment length. The segment length
is only derived from the bytes of payload data.
nextCBPos
This bit indicates the position where the next control byte is to be expected. This information is especially important
when using the "MultiSegmentMTU" option.
When using FlatStream communication with multi-segment MTUs, the next control byte is no longer expected in
the first Rx byte of the subsequent MTU, but directly after the current segment.
MessageEndBit
The "MessageEndBit" is set if the subsequent segment completes a message. The message has then been com-
pletely transmitted and is ready for further processing.
Information:
In the output direction, this bit must also be set if one individual segment is enough to hold the entire
message. The module will only process a message internally if this identifier is detected.
The size of the message being transmitted can be calculated by adding all of the message's segment
lengths together.
FlatStream formula for calculating message length:
Message [bytes] = SegmentLengths (all CBs without ME) + SegmentLength (of the first CB with CB Control byte
ME) ME MessageEndBit
Name:
OutputSequence
The "OutputSequence" register contains information about the communication status of the CPU. It is written by
the CPU and read by the module.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-2 OutputSequenceCounter 0-7 Counter for the sequences issued in the output direction
3 OutputSyncBit 0 Output direction disabled
1 Output direction enabled
4-6 InputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 InputSyncAck 0 Input direction not ready (disabled)
1 Input direction ready (enabled)
OutputSequenceCounter
The OutputSequenceCounter is a continuous counter of sequences that have been issued by the CPU. The CPU
uses the OutputSequenceCounter to direct the module to accept a sequence (the output direction must be syn-
chronized when this happens).
OutputSyncBit
The CPU uses the OutputSyncBit to attempt to synchronize the output channel.
InputSequenceAck
InputSequenceAck is used for acknowledgment. The value of the InputSequenceCounter is mirrored if the CPU
has received a sequence successfully.
InputSyncAck
The InputSyncAck bit acknowledges the synchronization of the input channel for the module. This indicates that
the CPU is ready to receive data.
Name:
InputSequence
The "InputSequence" register contains information about the communication status of the module. It is written by
the module and should only be read by the CPU.
Data type Value
USINT See bit structure.
Bit structure:
Bit Name Value Information
0-2 InputSequenceCounter 0-7 Counter for sequences issued in the input direction
3 InputSyncBit 0 Not ready (disabled)
1 Ready (enabled)
4-6 OutputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 OutputSyncAck 0 Not ready (disabled)
1 Ready (enabled)
InputSequenceCounter
The InputSequenceCounter is a continuous counter of sequences that have been issued by the module. The
module uses the InputSequenceCounter to direct the CPU to accept a sequence (the input direction must be
synchronized when this happens).
InputSyncBit
The module uses the InputSyncBit to attempt to synchronize the input channel.
OutputSequenceAck
OutputSequenceAck is used for acknowledgment. The value of the OutputSequenceCounter is mirrored if the
module has received a sequence successfully.
OutputSyncAck
The OutputSyncAck bit acknowledges the synchronization of the output channel for the CPU. This indicates that
the module is ready to receive data.
7 InputSyncAck 7 OutputSyncAck
Information:
If communication is interrupted, segments from the unfinished message are discarded. All messages
that were transmitted completely are processed.
Synchronization
During synchronization, a communication channel is opened. It is important to make sure that a module is present
and that the current value of the SequenceCounter is stored on the station receiving the message.
FlatStream can handle full-duplex communication. This means that both channels / communication directions can
be handled separately. They have to be synchronized independently so that simplex communication can theoret-
ically be carried out as well.
Note:
Theoretically, data can be transmitted from this point forward. However, it is still recommended to wait until the output direction is completely synchronized be-
fore transmitting data.
The module sets OutputSyncAck.
The output direction is synchronized, and the CPU can transmit data to the module.
Note:
Theoretically, data can already be transmitted in this cycle.
If the InputSyncBit is set and InputSequenceCounter has been increased by 1, the values in the enabled Rx bytes have to be accepted and acknowledged (see
also "Communication in the input direction").
The input direction is synchronized, and the module can transmit data to the CPU.
If a channel is synchronized, then the opposite station is ready to receive messages from the transmitter. Before
the transmitter can send data, it needs to first create a transmit array in order to meet FlatStream requirements.
The transmitting station must also generate a control byte for each segment created. This control byte contains
information about how the subsequent part of the data being transmitted should be processed. The position of the
next control byte in the data stream can vary. For this reason, it must be clearly defined at all times when a new
control byte is being transmitted. The first control byte is always in the first byte of the first sequence. All subsequent
positions are determined recursively.
FlatStream formula for calculating the position of the next control byte:
Position (of the next control byte) = Current position + 1 + Segment length
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The rest of the configuration corresponds to the default settings.
Default
Message 2:
Message 3:
C3 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C4 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
First, the messages must be split into segments. In the default configuration, it is important to ensure that each
sequence can hold an entire segment, including the associated control byte. The sequence is limited to the size of
the enable MTU. In other words, a segment must be at least 1 byte smaller than the MTU.
MTU = 7 bytes → Max. segment length = 6 bytes
• Message 1 (7 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C0 (control byte 0) C1 (control byte 1) C2 (control byte 2)
- SegmentLength (0) = 0 - SegmentLength (6) = 6 - SegmentLength (1) = 1
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (0) = 0 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 0 Control byte Σ 6 Control byte Σ 129
Table 430: FlatStream determination of the control bytes for the default configuration example (part 1)
C3 (control byte 3) C4 (control byte 4) C5 (control byte 5)
- SegmentLength (2) = 2 - SegmentLength (6) = 6 - SegmentLength (3) = 3
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 130 Control byte Σ 6 Control byte Σ 131
Table 431: FlatStream determination of the control bytes for the default configuration example (part 2)
When transmitting data, the transmit array must be generated in the application program. Sequences are then
transmitted one by one using FlatStream and received by the module.
Information:
Although all B&R modules with FlatStream communication always support the most compact trans-
missions in the output direction, it is recommended to use the same design for the transfer arrays in
both communication directions.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost.
(The relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individually.)
- Subsequent sequences can only be transmitted in the next bus cycle after the completion check has been carried out successfully.
Start
► diff = (OutputSequenceCounter -
OutputSequenceAck) AND 7
► limit = (OutputSequenceCounter -
LastValidAck) AND 7
(diff ≤ limit)
No OutputSequenceAck = No LastValidAck = Yes
AND (OutputSyncAck = 1)
AND (OutputSyncBit = 1) ? OutputSequenceCounter ? OutputSequenceCounter ?
Yes Yes No
No LastValidAck =
diff = 0 ?
OutputSequenceAck
Yes
LastValidAck = No
OutputSequenceAck = 0 ?
OutputSequenceAck
Yes
No OutputSequenceCounter = 0
More sequences to be sent ? OutputSequenceCounter = 1 OutputSyncBit = 1
LastValidAck = 0
Yes
When receiving data, the transmit array is generated by the module, transferred via FlatStream and must then
be reproduced in the receive array. The structure of the incoming data stream can be configured with the mode
register. The algorithm for receiving the data does not change in this regard.
PLC / Bus controller Module
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Start
► InputSequenceAck = InputSequenceCounter
Synchronisation
No
InputSyncBit = 1 ? ► RemainingSegmentSize = 0
► SegmentFlags = 0
Yes
No No
InputSyncAck = 1 ? InputSequenceAck > 0 ?
Yes Yes
MTU_Offset = 0 InputSyncAck = 1
(InputSequenceCounter – No
InputSequenceAck)
AND 0x07 = 1 ?
Yes
► RemainingSegmentSize =
Yes MTU_Data[MTU_Offset] AND 0b0011 1111
RemainingSegmentSize = 0 ? ► SegmentFlags =
MTU_Data[MTU_Offset] AND 0b1100 0000
No ► MTU_Offset = MTU_Offset + 1
No
No
Yes
► InputSequenceAck =
InputMTU_Size = MTU_Offset ?
InputSequenceCounter
No
Details
Information:
When transmitting with MultiSegmentMTUs, it is possible for several small messages to be part of one
sequence. In the program, it's important to make sure that a sufficient number of receive arrays can
be managed. The entire sequence must be accepted before it is possible to change the Acknowledge
register.
If a SequenceCounter is incremented by more than one value, then an error has occurred.
Note: This situation is very unlikely when operating without "Forward" functionality.
In this case, the receiver stops. All additional incoming sequences are ignored until the transmission with the correct
SequenceCounter is retried. This response prevents the transmitter from receiving any more acknowledgments for
transmitted sequences. The transmitter can identify the last successfully transmitted sequence from the opposite
station's SequenceAck and continue the transmission from this point.
Acknowledgments must be checked for validity.
If the receiver has successfully accepted a sequence, it must be acknowledged. The receiver takes on the Se-
quenceCounter value sent along with the transmission and matches the SequenceAck to it. The transmitter reads
the SequenceAck and registers the successful transmission. If the transmitter acknowledges a sequence that has
not yet been dispatched, then the transmission needs to be interrupted and the channel resynchronized. The syn-
chronization bits are reset and the current/incomplete message is discarded. It needs to be sent again once the
channel has been resynchronized.
FlatStream mode
Name:
FlatstreamMode
In the input direction, the transmit array is generated automatically. This register offers two options to the user
that allow an incoming data stream to have a more compact arrangement. Once enabled, the program code for
evaluation must be adapted accordingly.
Information:
All B&R modules that offer FlatStream mode support the options "Large segments" and "MultiSeg-
mentMTUs" in the output direction. Compact transmission only needs to be explicitly allowed in the
input direction.
Bit structure:
Bit Name Value Information
0 MultiSegmentMTU 0 Not allowed (default)
1 Allowed
1 Large segments 0 Not allowed (default)
1 Allowed
2-7 Reserved
Default
By default, both options relating to compact transmission in the input direction are disabled.
1. The module only forms segments that are at least one byte smaller than the enabled MTU. Each sequence
begins with a control byte so that the data stream is clearly structured and relatively easy to evaluate.
2. Since a FlatStream message can be of any length, the last segment of the message frequently doesn't fill up
all of the MTU's space. By default, the remaining bytes during this type of transfer cycle are not used.
C C C
- - -
ME0 ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
MultiSegmentMTUs allowed
With this option, the InputMTU is completely filled (if enough data is pending). The previously unfilled Rx bytes
transmit the next control bytes and their segments. This allows the enabled Rx bytes to be used more efficiently.
Bus cycle 1 Bus cycle 2 Bus cycle 3
C C C C
- -
ME0 ME1 ME0 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Information:
It is still possible to split up a message into several segments, however. If this option is used and
messages with more than 63 bytes occur, for example, then messages can still be split up among
several segments.
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Figure 427: Arrangement of messages in the MTU (large segments and MultiSegmentMTUs)
If the way messages are structured is changed, then the way data in the transmit/receive array is arranged is also
different. The following changes apply to the example given earlier.
MultiSegmentMTU
If MultiSegmentMTUs are allowed, then "open positions" in an MTU can be used. These "open positions" occur if
the last segment in a message does not fully use the entire MTU. MultiSegmentMTUs allow these bits to be used to
transmit the subsequent control bytes and segments. In the program sequence, the "nextCBPos" bit in the control
byte is set so that the receiver can correctly identify the next control byte.
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows transmission of MultiSegmentMTUs.
Message 1: Transmit/Receive array
Message 2: MultiSegmentMTU
Message 3:
C5 D2 D3 D4 D5 D6 D7 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C6 D8 D9 C0 - - - Sequence for bus cycle 4
First, the messages must be split into segments. As in the default configuration, it is important for each sequence
to begin with a control byte. The free bits in the MTU at the end of a message are filled with data from the following
message, however. With this option, the "nextCBPos" bit is always set if payload data is sent after the control byte.
MTU = 7 bytes → Max. segment length = 6 bytes
• Message 1 (7 bytes)
➯ First segment = Control byte + 2 bytes of data (MTU still has 2 open bytes)
• Message 3 (9 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (6) = 6 - SegmentLength (1) = 1 - SegmentLength (2) = 2
- nextCBPos (1) = 64 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 70 Control byte Σ 193 Control byte Σ 194
Table 432: FlatStream determination of the control bytes for the MultiSegmentMTU example (part 1)
Warning!
The second sequence must have been completely processed before it can be acknowledged with Se-
quenceAck. In this example, there are three different segments within the second sequence, i.e. the
program must include enough receive arrays to handle this situation.
C4 (control byte 4) C5 (control byte 5) C6 (control byte 6)
- SegmentLength (1) = 1 - SegmentLength (6) = 6 - SegmentLength (2) = 2
- nextCBPos (6) = 6 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 0 - MessageEndBit (1) = 128
Control byte Σ 7 Control byte Σ 70 Control byte Σ 194
Table 433: FlatStream determination of the control bytes for the MultiSegmentMTU example (part 2)
Large segments
Segments are limited to a maximum of 63 bytes. This means they can be larger than the active MTU. These large
segments are divided among several sequences when transmitted. It is possible for sequences to be completely
filled with payload data and not have a control byte.
Information:
It is still possible to subdivide a message into several segments so that the size of a data packet does
not also have to be limited to 63 bytes.
Example
Three autonomous messages (7 bytes, 2 bytes and 9 bytes) are being transmitted using an MTU with a width of
7 bytes. The configuration allows the transmission of large segments.
Message 3:
C2 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C3 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 434: FlatStream determination of the control bytes for the large segment example
Message 3:
D3 D4 D5 D6 D7 D8 D9 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C0 - - - - - - Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 435: FlatStream determination of the control bytes for the large segment and MultiSegmentMTU example
Forward functionality is a method that can be used to substantially increase the FlatStream data rate. The basic
principle is also used in other technical areas such as "pipelining" for microprocessors.
Operating principle
X2X Link communication cycles through five different steps to transmit a FlatStream sequence. At least five bus
cycles are therefore required to successfully transfer the sequence.
Step I Step II Step III Step IV Step V
Actions Transfer sequence from Cyclic matching of MTU and Append sequence to re- Cyclic matching of Check SequenceAck
transmit array, module buffer ceive array MTU and module buffer
increase Sequence- Adjust SequenceAck
Counter
Resource Transmitter Bus system Recipient Bus system Transmitter
(task to transmit) (direction 1) (task to receive) (direction 2) (task for Ack checking)
Sequence 3 ...
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Configuration
The Forward function only has to be enabled for the input direction. Two additional configuration registers are
available for doing so. FlatStream modules have been optimized in such a way that they support this function. In
the output direction, the Forward function can be used as soon as the size of the OutputMTU is specified.
Name:
Forward
With the "Forward" register, the user specifies how many unacknowledged sequences the module is allowed to
transmit.
Recommendation:
X2X Link: Max. 5
POWERLINK: Max. 7
Data type Value
USINT 1 to 7
Default: 1
Delay time
Name:
ForwardDelay
The "ForwardDelay" register is used to specify the delay time in µs. This is the amount of time the module has
to wait after sending a sequence until it is allowed to write new data to the MTU in the following bus cycle. The
program routine for receiving sequences from a module can therefore be run in a task class whose cycle time is
slower than the bus cycle.
Data type Value
UINT 0 to 65,535 [µs]
Default: 0
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Figure 432: Effect of ForwardDelay when using FlatStream communication with the Forward function
In the program, it is important to make sure that the CPU is processing all of the incoming InputSequences and In-
putMTUs. The ForwardDelay value causes delayed acknowledgment in the output direction and delayed reception
in the input direction. In this way, the CPU has more time to process the incoming InputSequence or InputMTU.
The basic algorithm for transmitting and receiving data remains the same. With the Forward function, up to seven
unacknowledged sequences can be transmitted. Sequences can be transmitted without having to wait for the
previous message to be acknowledged. Since the delay between writing and response is eliminated, a considerable
amount of additional data can be transferred in the same time window.
Algorithm for transmitting
Cyclic status query:
- The Module monitors the OutputSequenceCounter.
0) Cyclic checks:
- The CPU must check OutputSyncAck.
→ If OutputSyncAck = 0: Reset the OutputSyncBit and resynchronize the channel.
- The CPU must check whether OutputMTU is enabled.
→ If OutputSequenceCounter > OutputSequenceAck + 7, then it is not enabled because the last sequence has not yet been acknowledged.
1) Preparation (create transmit array):
- The CPU must split up the message into valid segments and create the necessary control bytes.
- The CPU must add the segments and control bytes to the transmit array.
2) Transmit:
- The CPU must transfer the current part of the transmit array to the OutputMTU.
- The CPU must increase the OutputSequenceCounter for the sequence to be accepted by the module.
- The CPU can then transmit in the next bus cycle if the MTU has been enabled.
The module responds since OutputSequenceCounter > OutputSequenceAck:
- The module accepts data from the internal receive buffer and appends it to the end of the internal receive array.
- The module is acknowledged and the currently received value of the OutputSequenceCounter is transferred to OutputSequenceAck.
- The module requests the status cyclically again.
3) Completion (acknowledgment):
- The CPU must check OutputSequenceAck cyclically.
→ A sequence is only considered to have been transmitted successfully if it has been acknowledged via OutputSequenceAck. In order to detect potential trans-
mission errors in the last sequence as well, it is important to make sure that the algorithm is run through long enough.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost (the relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individ-
ually).
Details/Background
1. Illegal SequenceCounter size (counter offset)
Error situation: MTU not enabled
If the difference between SequenceCounter and SequenceAck is larger than allowed during transmission,
then a transmission error has occurred. In this case, all unacknowledged sequences must be repeated with
the old SequenceCounter value.
2. Checking an acknowledgment
After an acknowledgment has been received, a check must verify whether the acknowledged sequence has
been transmitted and had not yet been unacknowledged. If a sequence has been acknowledged more than
once, then a fatal error has occurred. The channel must be closed and resynchronized (same behavior as
when not using Forward).
Information:
In exceptional cases, the module can increment OutputSequenceAck by more than 1 when using
Forward.
This is not an error. The CPU is permitted to consider all sequences up to the one being acknowl-
edged as having been transmitted successfully.
In industrial environments, it is often the case that many different devices from various manufacturers are being
used side by side. The electrical and/or electromagnetic properties of these technical devices can sometimes cause
them to interfere with one another. These kinds of situations can be reproduced and protected against in laboratory
conditions only to a certain point.
Precautions have been taken for X2X Link transmissions if this type of interference occurs. For example, if an
invalid checksum occurs, the I/O system will ignore the data from this bus cycle and the receiver receives the last
valid data once more. With conventional (cyclic) data points, this error can often be ignored. In the following cycle,
the same data point is again retrieved, adjusted and transmitted.
Using Forward functionality with FlatStream communication makes this situation more complex. The receiver re-
ceives the old data again in this situation as well, i.e. the previous values for SequenceAck/SequenceCounter and
the old MTU.
Loss of acknowledgment (SequenceAck)
If a SequenceAck value is lost, then the MTU was already transmitted properly. For this reason, the receiver is per-
mitted to continue processing with the next sequence. The SequenceAck is aligned with the associated Sequence-
Counter and sent back to the transmitter. Checking the incoming acknowledgments shows that all sequences up
to the last one acknowledged have been transmitted successfully (see sequences 1 and 2 in the image).
Loss of transmission (SequenceCounter, MTU):
If a bus cycle drops out and the SequenceCounter value and/or filled MTU are lost, then no data reaches the
receiver. At this point, the transmission routine is not yet affected by the error. The time-controlled MTU is released
again and can be rewritten to.
The receiver receives SequenceCounter values that have been incremented several times. For the receive array
to be put together correctly, the receiver is only allowed to process transmissions whose SequenceCounter has
been increased by one. The incoming sequences must be ignored, i.e. the receiver stops and no longer transmits
back any acknowledgments.
If the maximum number of unacknowledged sequences has been sent and no acknowledgments are returned, the
transmitter must repeat the affected SequenceCounter and associated MTUs (see sequence 3 and 4 in the image).
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 EMC Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
HIPERFACE is an asynchronous interface capable of half-duplex communication. Various features have been
included to ensure that signals are transmitted without errors.
• The user can choose to have a parity bit added when transmitting a data block.
• A checksum is sent together with a signal and evaluated by the receiver.
• The command to which the encoder is responding is repeated at the start of a response.
In FlatStream mode, the module acts as a bridge between the CPU and the HIPERFACE slave. HIPERFACE-spe-
cific algorithms have been implemented to monitor timeouts and handle checksums. During normal operation, the
user does not have access to these details.
Additional information is provided in the "Description of HIPERFACE" document.
Code0 is a byte that was added to the transfer protocol for safety reasons. It protects important system parameters
from being overwritten by mistake (default: Code0 = 0x55).
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x42 Command byte (read position)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x42
3 Pos_HH Response (data bytes)
4 Pos_HL
5 Pos_LH
6 Pos_LL
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x43 Command byte (set position)
3 Pos_HH New position (data bytes)
4 Pos_HL
5 Pos_LH
6 Pos_LL
7 Code0 Safety byte in accordance with the HIPERFACE specification
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x43
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x44 Command byte (read analog value)
3 Channel Channel byte (selects desired analog value)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address, command byte and channel byte (safety)
2 0x44
3 Channel
4 Value_H Value read
5 Value_L
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x46 Command byte (read counter)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x46
3 Ctr_H Counter value
4 Ctr_M
5 Ctr_L
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x47 Command byte (increment counter)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x47
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x49 Command byte (clear counter)
3 Code0 Safety byte in accordance with the HIPERFACE specification
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x49
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x4A Command byte (read data)
3 Data field ID of data to be read:
4 Byte address Number of the data field, start byte within the data field and number of bytes to be read
5 Count
6 Access code Access code in accordance with the HIPERFACE specification
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address, command byte and ID of data to be read (safety)
2 0x4A
3 Data field
4 Byte address
5 Count
6...n Data1...n Data to be read
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x4B Command byte (save data)
3 Data field ID of data to be saved:
4 Byte address Number of the data field, start byte within the data field and number of bytes to be read
5 Count
6 Access code Access code in accordance with the HIPERFACE specification
7...x Data1...n Data to be saved
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address, command byte and ID of data to be saved (safety)
2 0x4B
3 Data field
4 Byte address
5 Count
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x4C Command byte (determine status of a data field)
3 Data field Number of the data field
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address, command byte and number of the data field (safety)
2 0x4C
3 Data field
4 Status Access mode for queried data field
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x4D Command byte (create data field)
3 Data field Number of the data field
4 Status Access mode for the data field
5 Access code Access code in accordance with the HIPERFACE specification
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address, command byte, number of the data field and access mode of the data field (safety)
2 0x4D
3 Data field
4 Status
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x4E Command byte (read available memory area)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x4E
3 Free memory Number of available 16-byte blocks
4 Number of Number of data fields
data fields
Master
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address, command byte and code number (safety)
2 0x4F
3 Code number
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x50 Command byte (read encoder status)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x50
3 Encoder Status byte as specified by the slave manufacturer
status
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x52 Command byte (read nameplate)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x52
3 RS485 Nameplate in accordance with HIPERFACE specification:
settings HIPERFACE configuration, type of encoder, size of memory and other options
4 Encoder type
5 Size of
EEPROM
6 Options
Master
Slave response
Protocol bytes Information
No. Name
Slave
- - No response
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x55 Command byte (allocate encoder address)
3 New address New HIPERFACE address
4 Code0 Safety byte in accordance with the HIPERFACE specification
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x55
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x56 Command byte (read serial number and program version)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address and command byte (safety)
2 0x56
3...11 Serial number 9 characters
12...n Firmware Max. 20 characters
version
...n+8 Firmware date 8 characters (format: DD.MM.YY)
Master
Master command
Protocol bytes Information
No. Name
Master
1 Address Address of the HIPERFACE slave
2 0x57 Command byte (configure serial interface)
3 RS485 New baud rate in accordance with the HIPERFACE specification
settings
4 Code0 Safety byte in accordance with the HIPERFACE specification
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 Address Repeated address, command byte and new baud rate (safety)
2 0x57
3 RS485
settings
Master
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
100 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
100 µs
4.16.5 X20DS1928
The X20DS1928 module is equipped with an EnDat encoder interface. The X20DS1928 automatically detects
whether an encoder is connected with EnDat 2.1 or EnDat 2.2. This module can be used to evaluate encoders
installed in B&R servo motors as well as encoders for external axes (encoders that scan any machine movement).
The input signals are monitored. This makes it possible to detect open or shorted lines as well as encoder supply
failures.
• EnDat 2.1 and EnDat 2.2 encoder interface
• Encoder input monitoring
• 5 VDC and GND for encoder supply
• NetTime function: Time stamp for position
EnDat encoders
EnDat is a standard developed by Johannes Heidenhain GmbH (www.heidenhain.de) that incorporates the advan-
tages of absolute and incremental position measurement and also offers a read/write parameter memory in the
encoder. With absolute position measurement, the homing procedure is generally not required. Where necessary
a multi-turn encoder should be installed. To save costs, a single-turn encoder and a reference switch can also be
used. In this case, a homing procedure must be carried out.
NetTime position timestamp
Highly dynamic positioning tasks require not only the position value, but also the exact time at which the position
was determined. The module has a NetTime function for this, which adds a timestamp to the recorded position
with microsecond accuracy.
The module provides the PLC with the position value and timestamp as absolute time value. The NetTime mech-
anisms ensure that the PLC NetTime clock and the local NetTime clock on the module have exactly the same
absolute time at all times.
Product ID X20DS1928
Short description
I/O module 1x EnDat interface
General information
B&R ID code 0xA912
Status indicators Counting direction, operating status, module status
Diagnostics
Module run/error Yes, using status LED and software status
Counting direction Yes, with status LED
Power consumption
Bus 0.01 W
I/O internal 1.3 W
4.16.5.5 Pinout
X20 DS 1928 r e
UP
DN
B\ B
A\ A
D\ D
T\ T
Encoder 5V + GND
DS EnDat Encoder
B\
B Incremental signals
A\ (sine-cosine track)
A
D\
D Serial EnDat
T\ Interface
T
A\
B\
D DIN
RS485
Drivers DOUT
D\
T
RS485
Drivers DOUT
Transmitter
T\
24 V UP
DC
Encoder 5 V
DC
LED (green)
GND
GND
DN
LED (green)
The following configuration register can be used to configure different module settings. For example, the behavior
on the X2X bus can be modified this way. The user can choose between two option registers.
Names (pChannelName):
CfO_SIframeGenID
This register can be used to define when the synchronous/cyclic input data will be generated. X2X cycle optimized
should be set for jitter-free data acquisition or minimal latency for the best performance.
Data type Values
USINT 09 ... Minimal latency
14 ... X2X cycle optimized
4.16.5.10.5.2 Prescaler
Names (pChannelName):
CfO_SystemCyclePrescaler
In order for the module to communicate with the CPU as well as the EnDat encoder, the EnDat cycle time must be
at least twice the module cycle time. The actual EnDat cycle time is a result of multiplying the module cycle time
by the value in the register "CfO_SystemCyclePrescaler".
Data type Values
UINT 2 ... EnDat cycle: 200 to 400 μs
4 ... EnDat cycle: 400 to 800 μs
8 ... EnDat cycle: 800 to 1600
Bus controller default: 2
This module can import a position when used together with an EnDat encoder. The received data is prepared in
two different formats and given a time stamp. Six registers are available for post-processing. This allows the user
to select the format that best fits the application at hand.
4.16.5.10.6.1 SDCLifeCount
Names (pChannelName):
SDCLifeCount
The 8-bit counter register is needed for the SDC software package. It is incremented with the system clock to allow
the SDC to check the validity of the data frame.
Data type Values
SINT -128...127
Names (pChannelName):
PositionHW
PositionHW_64 / PositionHW_64_CANIO
PositionLW
PositionLW_64 / PositionLW_64_CANIO
The absolute position of the encoder is defined in 64 bit resolution. The position value is placed in the registers
PositionHW and PositionLW. The upper 32 bits are in the PositionHW register and the lower 32 bits in the Posi-
tionLW register.
Data type Values
2x UDINT 0...4294967295
Names (pChannelName):
Position
Position_32
The SDC library requires a signed 32-bit position value. The position's Low Word can be addressed separately for
this. However, the value can also be used as default position value.
Data type Values
DINT -2147483648...2147483647
Names (pChannelName):
PosTime
PosTime_32
In this register, each position determined is assigned to the current NetTime value. The NetTime is recorded with
µs precision.
Data type Values [NetTime]
DINT -2147483648...2147483647
Names (pChannelName):
PosTime
PosTime_16
The SDC library requires a 16 bit value. This is why the NetTime value is prepared in 16 bit format.
Data type Values [NetTime]
INT -32768...32767
4.16.5.10.6.6 PosCycle
Names (pChannelName):
PosCycle
PosCycle_8 / PosCycle_8_CANIO
PosCycle is an integer counter that is incremented as soon as the module has saved a new valid position value.
Data type Values
SINT -128...127
The module can also provide diagnostics about error states. There are two ways in which this is done:
• Module-based diagnostics
• EnDat-based diagnostics
The module diagnoses seven different errors or warnings. Depending on the settings, the error bits can be called
either individually or packed together.
Error registers
Names (pChannelName):
ErrorEnableID_1710
ErrorInfo / ErrorInfo_CANIO
AckErrorInfo / AckErrorInfo_CANIO
Names of the individual bits (pChannelName):
EncoderSupplyError
VssCheckError
PositionError
EnDatComError
EnDatPosError
EnDatParSetError
EnDatRefWarning
AckEncoderSupplyError
AckVssCheckError
AckPositionError
AckEnDatComError
AckEnDatPosError
AckEnDatParSetError
AckEnDatRefWarning
Three independent registers are provided in accordance with B&R's approach to error management.
Data type Values
3x USINT See bit structure
The implemented diagnostics algorithms can be activated or deactivated in the Enable byte.
Bit structure of "ErrorEnableID_1710":
Bit Name Information
0 Encoder supply 0 Error detection disabled
1 Error detection enabled (Bus Controller default setting)
1 Reserved -
2 Vss Sin/Cos 0 Error detection disabled
1 Error detection enabled (Bus Controller default setting)
3 Position Error 0 Error detection disabled
1 Error detection enabled (Bus Controller default setting)
4 EnDat - Communication 0 Error detection disabled
1 Error detection enabled (Bus Controller default setting)
5 EnDat - Position 0 Error detection disabled
1 Error detection enabled (Bus Controller default setting)
6 EnDat - Parameter 0 Error detection disabled
1 Error detection enabled (Bus Controller default setting)
7 EnDat - Reference warning 0 Warning disabled
1 Warning enabled (Bus Controller default setting)
Encoder supply:
Encoder supply voltage below permitted limit
Vss Sin/Cos:
Voltage value for Sin/Cos-Spur violates configured limit values
→ see the register SinCosVssMin or SinCosVssMax
Position error:
The determined position value violates requirements of the application
EnDat – Communication:
Communication error on the EnDat interface (e.g. incorrect checksum)
EnDat – Position:
Encoder evaluates determined position value as invalid
EnDat – Parameter:
Inconsistent register values for encoder identification
→ Counter-measures: Check wiring or rescan (see EnDatAck)
Memory areas are provided in the EnDat standard for error handling. Error management was tailored to utilize
error detection according to the EnDat standard. Three additional registers were implemented in the module which
prepare these areas in the encoder memory.
The module allows access to all previously defined memory areas for error handling. The memory areas are mir-
rored in the module registers and can be interpreted by the user.
Please refer to the encoder's manual for detailed information regarding the errors that can be detected this way.
EnDatError
Names (pChannelName):
EnDatError
This register is used to indicate critical conditions on the EnDat encoder. The system has generally ceased to work
and requires service.
Data type Values
UINT See bit structure
The bit structure described below is designed according to the general recommendations of the EnDat standard.
The specification does not limit which trigger algorithms to use or which of the listed messages must be supported.
Please refer to the encoder's manual for further details.
Bit structure:
Bit Name Information
0 Lighting 0 ok
1 Failed
1 Signal amplitude 0 ok
1 Error
2 Position value 0 ok
1 Error
3 Overvoltage 0 No
1 Yes
4 Undervoltage 0 No
1 Yes
5 Overcurrent 0 No
1 Yes
6 Battery 0 ok
1 Must be changed
7-15 Reserved -
EnDatWarning
Names (pChannelName):
EnDatWarning
This register is used to indicate critical conditions on the EnDat encoder. Encoder still functional, but must be
checked immediately. This generally means that defined tolerances have been exceeded.
Data type Values
UINT See bit structure
The bit structure described below is designed according to the general recommendations of the EnDat standard.
The specification does not limit which trigger algorithms to use or which of the listed messages must be supported.
Please refer to the encoder's manual for further details.
Bit structure:
Bit Name Information
0 Frequency collision 0 No
1 Yes
1 Temperature exceeded 0 No
1 Yes
2 Control reserve - Lighting 0 Not required
1 Mandatory
3 Charge - Battery 0 ok
1 Low
4 Reference point 0 Reached
1 Not reached
5-15 Reserved -
EnDatAck
Names (pChannelName):
EnDatAck
The "EnDatAck" acknowledges all errors and warnings from the registers "EnDatError" and "EnDatWarning". It can
also instruct the module to re-import the parameters for identification.
Data type Values
USINT See bit structure
If one of the bits in this register is set, the system automatically resets it and the respective algorithm is run.
Bit structure:
Bit Name Information
0 EnDatError/EnDatWarning 0 No acknowledgment
1 Acknowledged
1 Rescan - Identification register 0 Imported parameters retained
1 Re-import parameters
2-7 Reserved -
In addition to the digital EnDat, the module is also equipped with an analog interface for recording a differential
sine-cosine signal. To increase the resolution, the EnDat standard specifies a cooperation between the analog and
digital information. This enables highly dynamic display of the position while maintaining high resolution.
4.16.5.10.8.1 SinCosEnable
Names (pChannelName):
SinCosEnable
This register must always have the value 1 for configuration reasons.
Data type Values
USINT 1!
Bus controller default setting: 1
4.16.5.10.8.2 SinCosRefSource
Names (pChannelName):
SinCosRefSource
This register must always have the value 1 for configuration reasons.
Data type Values
USINT 1!
Bus controller default setting: 1
4.16.5.10.8.3 SinCosVssMin
Names (pChannelName):
SinCosVssMin
The SinCosVssMin register specifies the lower limit value for the peak-peak voltage of the sine/cosine track. This
ensures that the pending signal is monitored. If the incoming value falls below this specified limit, then the module
reports the corresponding error.
Data type Values [mV]
UINT 0...1500
Bus controller default setting: 800
4.16.5.10.8.4 SinCosVssMax
Names (pChannelName):
SinCosVssMax
The SinCosVssMax register specifies the upper limit value for the peak-peak voltage of the sine/cosine track. This
ensures that the pending signal is monitored. If the incoming value exceeds this specified limit, then the module
reports the corresponding error.
Data type Values [mV]
UINT 0...1500
Bus controller default setting: 1200
4.16.5.10.8.5 SinCosQuitTime
Names (pChannelName):
SinCosQuitTime
If an error is detected on the analog interface, the latest correctly determined values remain valid. A time span
can be defined here in which the module begins receiving correct values again after the error state without post-
processing them internally. Only then will newly imported correct analog values be recognized as valid.
Data type Values [µs]
UDINT 0...20000000
Bus controller default setting: 100000
4.16.5.10.9 EnDat
The EnDat interface allows you to establish a point-to-point connection with exactly one EnDat encoder.
There are two ways to use the encoder data in the PLC program. The important encoder values can be buffered in
the module before being made available on the CPU or the module's Flatstream mode can be used, which supports
the full command range in accordance with the EnDat specification.
Detailed information about the EnDat specification can be found in the document, "Technical Information – EnDat
2.2".
EnDatMode
Names (pChannelName):
EnDatMode
A variety of module properties are pre-defined in the "EnDatMode" register.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Information
0 EnDat interface 0 Disabled
1 Enabled (bus controller default setting)
1 Format of imported position data 0 Unsigned (bus controller default setting)
1 Signed
2 Fast EnDat cycle (6 MHz) 0 Enabled if encoder compatible (bus controller default setting)
1 Disabled
3 Sin/Cos track 0 Enabled (bus controller default setting)
1 Disabled
4-7 Reserved -
The EnDat interface does more than just help the user specify axis positions. It can also be used to readout certain
data stored in the encoder memory.
The EnDat specification divides the encoder memory into logical groups. These include memory areas for the op-
erating parameters, operating status, manufacturer parameters, and manufacturer parameters according to EnDat
2.2.
The four most important memory areas are mirrored in the module registers. The information can be accessed in
the application and used to identify a particular encoder.
Information:
There are different types of EnDat. Please keep this in mind. EnDat has been continuously expanded to
include new technical possibilities while maintaining backward compatibility. Several advancements
have been made to the standard, which has resulted in a non-uniform structure.
In general, data is queried from memory for identification purposes when the module is started. Additionally, the
data can be re-imported using the "EnDatAck" register (see Error management section). The module reads the
data from the encoder, which is then mapped for the PLC.
Operating Parameters
Names (pChannelName):
OperatingParam_00
OperatingParam_[01…15]
These registers can be used to read out the current operating parameters. The data in these registers correspond
exactly to the values on the encoder. More detailed information can be found in the encoder's manual or by referring
to the latest EnDat specification.
Data type Values
16x UINT See encoder manual
Operating status
Names (pChannelName):
OperatingStatus_00
OperatingStatus_[01…03]
This register can be used to read the encoder's current operating state. The first two registers from this group
are identical to the registers "EnDatError" and "EnDatWarning". A special setting is provided because they are
update cyclically.
Information about write protection and other configuration settings is managed in registers 02 and 03. The data in
these registers correspond exactly to the values on the encoder.
More detailed information can be found in the encoder's manual or by referring to the latest EnDat specification.
Data type Values
4x UINT See encoder manual
Manufacturer parameters
Names (pChannelName):
ParamManuf_04
ParamManuf_[05…47]
These registers are used to prepare the manufacturer parameters according to the EnDat standard 2.1. The exact
arrangement of information can be found in the documentation "Technical Information - EnDat 2.2".
Data type Values
44x UINT see "Technical Information - EnDat 2.2" or encoder manufacturer data
Names (pChannelName):
ParamManufEnDat22_00
ParamManufEnDat22_[01…63]
These registers are used to prepare the manufacturer parameters according to the EnDat standard 2.2. The exact
arrangement of information can be found in the documentation "Technical Information - EnDat 2.2".
Data type Values
64x UINT see "Technical Information - EnDat 2.2" or encoder manufacturer data
In addition to the identification data, other information can also be accessed from the encoder. However, the fol-
lowing algorithm requires exact knowledge of the encoder's memory structure and the EnDat specification.
Configuration
There are four different channels that can be operated during a cycle. One register per channel each is used for
configuration, (i.e. determines which data is read from the encoder and mirrored on the respective Info byte).
EnDatInfoCmd
Names (pChannelName):
EnDatInfoCmd01
EnDatInfoCmd[02…04]
The "EnDatInfoCmd" register controls which data is processed on the corresponding Info byte for each channel.
The register consists of up to four separate 8-bit values.
Data type Values
4x UDINT see bit structure
Bus controller default setting: 0
Bit structure:
Bit Name Information
00-07 Command Selects the response section
08-15 Memory area code MRS code
Parameters not in blocks Parameters arranged in blocks
16-23 Memory ID Parameter number Block number
24-31 Memory ID - Parameter number
There is a difference when querying data from an encoder using an EnDat 2.1 command or an EnDat 2.2 command.
When querying encoder data with an EnDat 2.1 command (0x04 and 0x06) the parameter number and (optionally)
the block number must be specified in addition to the MRS code.
When querying the memory with an EnDat 2.2 command, the parameter number and block number are not required.
The module consecutively sends all four words of the memory area, which was selected using the MRS code. The
right command must be selected depending on which of the four response bytes is needed.
Parameter number:
EnDat 2.1 requires the corresponding parameter number to be entered in order to specifically address the desired
parameter in the encoder memory. Older EnDat versions did not divide the encoder memory into blocks. This is
why there are memory areas that can be selected without specifying a block number. In this case, the parameter
number must be entered on the third byte.
More detailed information can be found in the encoder's manual or by referring to the latest EnDat specification.
Block number:
To expand the address range of the encoder memory, additional block numbers were added starting at the second
section. If the desired parameter is located in this blocked area, then the block number must be specified on the
third byte. In this case, the parameter number is indicated on the fourth byte.
More detailed information can be found in the encoder's manual or the latest EnDat specification.
Call
After proper configuration, the position value is transferred cyclically to the module. Two registers are available per
channel as a buffer. The module confirms successful receipt by setting an OK bit. The EnDat specification does not
specify in which format the parameters must be received. Therefore, the module provides the information in two
ways. Which of the two registers should be used for further processing depends on the parameters being read.
EnDatInfoOKByte
Names (pChannelName):
EnDatInfoOK01
EnDatInfoOK[02…04]
This register's bits provide information about the validity of the latest Info data in the buffer.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Information
0 EnDatInfoOK01 0 Value 01 invalid
1 Value 01 valid
1 EnDatInfoOK02 0 Value 02 invalid
1 Value 02 valid
2 EnDatInfoOK03 0 Value 03 invalid
1 Value 03 valid
3 EnDatInfoOK04 0 Value 04 invalid
1 Value 04 valid
4-7 Reserved -
EnDatInfo (unsigned)
Names (pChannelName):
EnDatInfo01_u16
EnDatInfo[02…04]_u16
The registers provide the corresponding requested information as an unsigned 2 byte value.
Data type Values
UINT 0...65535
EnDatInfo (signed)
Names (pChannelName):
EnDatInfo01_s16
EnDatInfo[02…04]_s16
The registers provide the corresponding requested information as a signed 2 byte value.
Data type Values
INT -32768...32767
4.16.5.10.10.1 Introduction
B&R offers an additional communication method for some modules. "FlatStream" was designed for X2X and
POWERLINK networks and allows data transfer adapted to individual demands. Although this method is not 100%
real-time capable, it still allows data transfer to be handled more efficiently than with standard cyclic polling.
Field device
X2X language
Cyclic call
via I/O mapping
B&R CPU
Cyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
Acyclic call
via
library functions
B&R CPU
Acyclic call B&R module Cyclic
PLC or B&R field device
of cached values cached value communication
Bus controller
FlatStream
The physical properties of the bus system limit the amount of data that can be transferred during one bus cycle.
With FlatStream communication, all messages are viewed as part of a continuous data stream. Long data streams
must be broken down into several fragments that are sent one after the other. To understand how the receiver puts
these fragments back together to get the original information, it is important to understand the difference between
a message, a segment, a sequence and the MTU.
Message:
A message refers to information exchanged between two partner stations. The length of a message is not restricted
by the FlatStream communication method. Nevertheless, module-specific limitations must be considered.
Segment (logical division of a message):
A segment has a finite size and can be understood as a section of a message. The number of segments per
message is arbitrary. So that the recipient can correctly reassemble the transferred segments, each segment
is preceded by a byte with additional information. This control byte contains information such as the length of
a segment and whether the approaching segment completes message. This makes it possible for the receiving
station to interpret the incoming data stream correctly.
Sequence (how a segment needs to be arranged physically):
The size of a sequence corresponds exactly to the number of activated Rx or Tx bytes (later: "MTU"). The trans-
mitting station splits the transmit array into valid sequences. These sequences are then written successively to
the MTU and transferred to the receiving station where they are put back together again. The receiver stores the
incoming sequences in a receive array, obtaining an image of the data stream in the process.
With FlatStream communication, the number of sequences sent are counted. Sequences transferred successfully
must be acknowledged by the receiving station to ensure the integrity of the transmission.
MTU (Maximum Transmission Unit) - Physical transport:
MTU refers to the activated USINT registers used with FlatStream. These registers can accept a sequence and
pass it on to the receiving station. A separate MTU is defined for each direction of communication. The OutputMTU
defines the number of FlatStream Tx bytes, and the InputMTU specifies the number of FlatStream Rx bytes. The
MTUs are transported cyclically via the X2X bus, increasing the load with each additional activated USINT register.
Properties:
FlatStream messages are not transferred cyclically or in 100% real time. Many bus cycles may be needed to trans-
fer a certain message. Although the Rx and Tx registers are exchanged between the transmitter and the receiv-
er cyclically, they are only processed further if explicitly accepted by the "InputSequence" or "OutputSequence"
register.
Behavior in the event of an error (brief summary):
The protocol for X2X and POWERLINK networks specifies that the last valid values should be retained when
disturbances occur. With conventional communication (cyclic/acyclic data queries), this type of error can generally
be ignored.
In order for communication to also take place without errors using FlatStream, all of the sequences issued by the
receiver must be acknowledged. If "Forward" functionality is not used, then subsequent communication is delayed
for the length of the disturbance.
If "Forward" functionality is being used, the receiving station receives a transmission counter that is incremented
twice. The receiver stops, i.e. it no longer returns any acknowledgments. The transmitting station uses the Se-
quenceAck to determine that the transmission was faulty and all affected sequences will have to be repeated.
Requirement:
Before FlatStream can be used, the respective communication direction must be synchronized, i.e. both commu-
nication partners cyclically query the sequence counter on the opposite station. This checks to see if there is new
data that should be accepted.
Communication:
If a communication partner wants to transmit a message to its opposite station, it should first create a transmit
array that corresponds to FlatStream conventions. This allows the FlatStream data to be organized very efficiently
without having to block other important resources.
PLC / Bus controller Module
Module-internal Module-internal
Transmit array OutputMTU receive buffer receive array
Type: USINT Type: USINT Type: USINT Type: USINT
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Five registers are available for configuring FlatStream. The default configuration can be used to transmit small
amounts of data relatively easily.
Information:
The CPU communicates directly with the field device via the OutputSequence/InputSequence registers
and the enabled Tx / Rx bytes. For this reason, the user needs to have sufficient knowledge of the
communication protocol being used on the field device.
FlatStream configuration
To use FlatStream, the program sequence must first be expanded. The cycle time of the FlatStream routines must
be set to a multiple of the bus cycle. Other program routines should be implemented in Cyclic #1 to ensure data
consistency.
At the absolute minimum, the "InputMTU" and "OutputMTU" registers need to be configured. All other registers are
filled in with default values at the beginning and can be used immediately. These registers are used for additional
options, e.g. to transmit data in a more compact way or to increase the efficiency of the general procedure.
The Forward registers extend the functionality of the FlatStream protocol. This functionality is useful for substan-
tially increasing the FlatStream data rate, but it also requires quite a bit of extra work when creating the program
sequence.
OutputMTU, InputMTU
These registers define the number of enabled Tx or Rx bytes, i.e. the maximum size of a sequence. The user must
consider that the more bytes made available also means a higher load on the bus system.
Information:
In the rest of this documentation, the names "OutputMTU" and "InputMTU" do not refer to the registers
explained here. Instead, they are used as synonyms for the currently enabled Tx or Rx bytes.
Data type Value
USINT See the module-specific register overview (theoretically: 3 - 27)
FlatStream operation
When using FlatStream, the communication direction is enormously important. For sending data to a module ("out-
put" direction), the Tx bytes are used. For receiving data from a module ("input" direction"), the Rx bytes are used.
The "OutputSequence" and "InputSequence" registers are used to control and ensure that communication is taking
place properly, i.e. the transmitter issues the directive that the data should be accepted and the receiver acknowl-
edges that a sequence has been transferred successfully.
Tx-/Rx-Bytes:
The Tx and Rx bytes are cyclic registers used to transport the payload data and the necessary control bytes.
The number of active Tx/Rx bytes is taken from the configuration of the "OutputMTU" and "InputMTU" registers,
respectively.
In the user's program, only the Tx/Rx bytes from the CPU can be used. The corresponding counterparts are located
in the module and are not accessible to the user. For this reason, names were chosen from the CPU point of view.
• "T" - "Transmit" → CPU transmits data to the module
• "R" - "Receive" → CPU receives data from the module
Data type Values
USINT 0...65535
Control bytes:
In addition to the payload data, the Tx and Rx bytes also transfer the necessary control bytes. These control bytes
contain additional information about the data stream so that the receiver can reconstruct the original message from
the transferred segments.
Bit structure of a control byte:
Bit Name Information
0-5 SegmentLength 0-63 Size in bytes of the following segment (default: max. MTUSize
- 1)
6 nextCBPos 0 Next control byte at the beginning of the next MTU
1 Next control byte directly at the end of this segment
7 MessageEndBit 0 Message continues after the subsequent segment
1 Message ends after the subsequent segment
Segment length:
The segment length lets the receiver know the length of the coming segment. If the configured segment length
is insufficient for a message, then the information must be distributed over several segments. In these cases, the
actual end of the message is detected using bit 7 of the control byte.
Information:
The control byte is not included in the calculation to determine the segment length. The segment length
is only derived from the bytes of payload data.
nextCBPos:
This bit indicates the position where the next control byte is to be expected. This information is especially important
when using the "MultiSegmentMTU" option.
When using FlatStream communication with multi-segment MTUs, the next control byte is no longer expected in
the first Rx byte of the subsequent MTU, but directly after the current segment.
MessageEndBit:
The "MessageEndBit" is set if the subsequent segment completes a message. The message is then completely
transferred and can be processed further.
Information:
In the output direction, this bit must also be set if one individual segment is enough to take on the
entire message. The module will only process a message internally if this identifying mark is detected.
The size of the message being transferred can be calculated by adding all of the message's segment
lengths together.
FlatStream formula for calculating message length:
Message [bytes] = SegmentLengths (all CBs without ME) + SegmentLength (of the first CB with CB Control byte
ME) ME MessageEndBit
OutputSequence
The "OutputSequence" register contains information about the communication status of the CPU. It is written by
the CPU and read by the module.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Information
0-2 OutputSequenceCounter 0-7 Counter for the sequences issued in the output direction
3 OutputSyncBit 0 Output direction disabled
1 Output direction enabled
4-6 InputSequenceAck 0-7 Mirrors the InputSequenceCounter value
7 InputSyncAck 0 Input direction not ready (disabled)
1 Input direction ready (enabled)
OutputSequenceCounter:
The OutputSequenceCounter is a continuous counter of sequences that have been issued by the CPU. The CPU
uses the OutputSequenceCounter to direct the module to accept a sequence (the output direction must be syn-
chronized when this happens).
OutputSyncBit:
The CPU uses the OutputSyncBit to try and synchronize the output channel.
InputSequenceAck:
InputSequenceAck is used for acknowledgment. The value of the InputSequenceCounter is mirrored if the CPU
has received a sequence successfully.
InputSyncAck:
The InputSyncAck bit acknowledges the synchronization of the input channel for the module. This indicates that
the CPU is ready to receive data.
InputSequence
The "InputSequence" register contains information about the communication status of the module. It is written by
the module and should only be read by the CPU.
Data type Values
USINT See bit structure
Bit structure:
Bit Name Information
0-2 InputSequenceCounter 0-7 Counter for the sequences issued in the input direction
3 InputSyncBit 0 Not ready (disabled)
1 Ready (enabled)
4-6 OutputSequenceAck 0-7 Mirrors the OutputSequenceCounter value
7 OutputSyncAck 0 Not ready (disabled)
1 Ready (enabled)
InputSequenceCounter:
The InputSequenceCounter is a continuous counter of sequences that have been issued by the module. The
module uses the InputSequenceCounter to direct the CPU to accept a sequence (the input direction must be
synchronized when this happens).
InputSyncBit:
The module uses the InputSyncBit to try and synchronize the input channel.
OutputSequenceAck:
OutputSequenceAck is used for acknowledgment. The value of the OutputSequenceCounter is mirrored if the
module has received a sequence successfully.
OutputSyncAck:
The OutputSyncAck bit acknowledges the synchronization of the output channel for the CPU. This indicates that
the module is ready to receive data.
7 InputSyncAck 7 OutputSyncAck
Information:
If communication is interrupted, segments from the unfinished message transfer are discarded. All
messages that were transferred completely are processed.
Synchronization
During synchronization, a communication channel is opened. It is important to make sure that a module is present
and that the current value of the SequenceCounter is stored on the station receiving the message.
FlatStream can handle full-duplex communication. This means that both channels / communication directions can
be handled separately. They have to be synchronized independently so that simplex communication can theoret-
ically be carried out as well.
If a channel is synchronized, then the opposite station is ready to receive messages from the transmitter. Before
the transmitter can send data, it needs to first create a transmit array in order to meet FlatStream requirements.
The transmitting station must also generate a control byte for each segment created. This control byte contains
information about how the subsequent part of the data being transferred should be processed. The position of the
next control byte in the data stream can vary. For this reason, it must be absolutely clear at all time when a new
control byte is being transferred. The first control byte is always in the first byte of the first sequence. All subsequent
positions are conveyed recursively.
FlatStream formula for calculating the position of the next control byte:
Position (of the next control byte) = Current position + 1 + Segment length
Example:
Three autonomous messages (7 bytes, 2 bytes, 9 bytes) are being transferred using an MTU with a width of 7
bytes. The rest of the configuration corresponds to the default settings.
Default
Message 2:
Message 3:
C3 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C4 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C0 (control byte 0) C1 (control byte 1) C2 (control byte 2)
- SegmentLength (0) = 0 - SegmentLength (6) = 6 - SegmentLength (1) = 1
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (0) = 0 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 0 Control byte Σ 6 Control byte Σ 129
Table 439: FlatStream determination of the control bytes for default configuration example (part 1)
C3 (control byte 3) C4 (control byte 4) C5 (control byte 5)
- SegmentLength (2) = 2 - SegmentLength (6) = 6 - SegmentLength (3) = 3
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (0) = 0 - MessageEndBit (1) = 128
Control byte Σ 130 Control byte Σ 6 Control byte Σ 131
Table 440: FlatStream determination of the control bytes for default configuration example (part 2)
When transmitting data, the transmit array must be generated in the application program. Sequences are then
transferred one by one using FlatStream and received by the module.
Information:
Although all B&R modules with FlatStream communication always support the most compact trans-
missions in the output direction, it is recommended to use the same design for the transfer arrays in
both communication directions.
Start
► diff = (OutputSequenceCounter -
OutputSequenceAck) AND 7
► limit = (OutputSequenceCounter -
LastValidAck) AND 7
(diff ≤ limit)
No OutputSequenceAck = No LastValidAck = Yes
AND (OutputSyncAck = 1)
AND (OutputSyncBit = 1) ? OutputSequenceCounter ? OutputSequenceCounter ?
Yes Yes No
No LastValidAck =
diff = 0 ?
OutputSequenceAck
Yes
LastValidAck = No
OutputSequenceAck = 0 ?
OutputSequenceAck
Yes
No OutputSequenceCounter = 0
More sequences to be sent ? OutputSequenceCounter = 1 OutputSyncBit = 1
LastValidAck = 0
Yes
When receiving data, the transmit array is generated by the module, transferred via FlatStream and must then
be reproduced in the receive array. The structure of the incoming data stream can be configured with the mode
register. The algorithm for receiving the data does not change in this regard.
PLC / Bus controller Module
Module-internal Module-internal
Receive array InputMTU transmit buffer transmit array
Type: USINT Type: USINT Type: USINT Type: USINT
Start
► InputSequenceAck = InputSequenceCounter
Synchronisation
No
InputSyncBit = 1 ? ► RemainingSegmentSize = 0
► SegmentFlags = 0
Yes
No No
InputSyncAck = 1 ? InputSequenceAck > 0 ?
Yes Yes
MTU_Offset = 0 InputSyncAck = 1
(InputSequenceCounter – No
InputSequenceAck)
AND 0x07 = 1 ?
Yes
► RemainingSegmentSize =
Yes MTU_Data[MTU_Offset] AND 0b0011 1111
RemainingSegmentSize = 0 ? ► SegmentFlags =
MTU_Data[MTU_Offset] AND 0b1100 0000
No ► MTU_Offset = MTU_Offset + 1
No
No
Yes
► InputSequenceAck =
InputMTU_Size = MTU_Offset ?
InputSequenceCounter
No
Details
Information:
When transmitting with MultiSegmentMTUs, it is possible for several small messages to be part of one
sequence. In the program, it's important to make sure that a sufficient number of receive arrays can
be managed. The entire sequence must be accepted before it is possible to change the Acknowledge
register.
If a SequenceCounter is incremented by more than one value, then an error has occurred (this situation is very
unlikely when operating without "Forward" functionality).
In this case, the receiver stops. All additional incoming sequences are ignored until the transmission with the correct
SequenceCounter is retried. This response prevents the transmitter from receiving any more acknowledgments for
transmitted sequences. The transmitter can identify the last successfully transmitted sequence from the opposite
station's SequenceAck and continue the transmission from this point.
Acknowledgments must be checked for validity.
If the receiver has successfully accepted a sequence, it must be acknowledged. The receiver takes on the Se-
quenceCounter value sent along with the transmission and matches the SequenceAck to it. The transmitter reads
the SequenceAck and registers the successful transmission. If the transmitter acknowledges a sequence that has
not yet been dispatched, then the transmission needs to be interrupted and the channel resynchronized. The syn-
chronization bits are reset and the current/incomplete message is discarded. It needs to be sent again once the
channel has been resynchronized.
In the input direction, the transmit array is generated automatically. This register offers two options to the user
that allow an incoming data stream to have a more compact arrangement. Once enabled, the program code for
evaluation must be adapted accordingly.
Information:
All B&R modules that offer FlatStream mode support the options "Large segments" and "Multi-segment
MTU" in the output direction. Compact transmission only needs to be explicitly allowed in the input
direction.
Bit structure:
Bit Name Information
0 MultiSegmentMTU 0 Not allowed (default)
1 Allowed
1 Large segments 0 Not allowed (default)
1 Allowed
2-7 Reserved
Default:
By default, both options relating to compact transfers in the input direction are disabled.
1. The module only forms segments that are at least one byte smaller than the activated MTU. Each sequence
begins with a control byte so that the data stream is clearly structured and relatively easy to evaluate.
2. Since a FlatStream message can be of any length, the last segment of the message frequently doesn't fill up
all of the MTU's space. By default, the remaining bytes during this type of transfer cycle are not used.
C C C
- - -
ME0 ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
MultiSegmentMTU allowed:
With this option, the InputMTU is completely filled (if enough data is pending). The previously unfilled Rx bytes
transfer the next control bytes and their segments. This allows the activated Rx bytes to be used more efficiently.
Bus cycle 1 Bus cycle 2 Bus cycle 3
C C C C
- -
ME0 ME1 ME0 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Information:
It is still possible to split up a message into several segments, however. If this option is used and
messages with more than 63 bytes occur, for example, the messages can still be split up among several
segments.
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
C C
- - - -
ME1 ME1
Message 1 Message 2
C
Control byte with MessageEndBit = 0
ME0
C
Control byte with MessageEndBit = 1
ME1
Figure 445: Message arrangement in the MTU (large segments and MultiSegmentMTU)
FlatStream adjustment
If the way messages are structured is changed, then the way data in the transmit/receive array is arranged is also
different. The following changes apply to the example given earlier on.
MultiSegmentMTU:
If MultiSegmentMTUs are allowed, then "open positions" in an MTU can be used. These "open positions" occur if
the last segment in a message doesn't fully use the entire MTU. MultiSegmentMTUs allow these bits to be used
to transfer the following control bytes and segments. In the program sequence, the "nextCBPos" bit in the control
byte is set so that the receiver can correctly identify the next control byte.
Example:
Three autonomous messages (7 bytes, 2 bytes, 9 bytes) are being transferred using an MTU with a width of 7 bytes.
The configuration allows the transfer of MultiSegmentMTUs.
Message 1: Transmit/Receive array
Message 2: MultiSegmentMTU
Message 3:
C5 D2 D3 D4 D5 D6 D7 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C6 D8 D9 C0 - - - Sequence for bus cycle 4
➯ First segment = Control byte + 2 data bytes (MTU still has 2 open bytes)
• Message 3 (9 bytes)
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (6) = 6 - SegmentLength (1) = 1 - SegmentLength (2) = 2
- nextCBPos (1) = 64 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 70 Control byte Σ 193 Control byte Σ 194
Table 441: FlatStream determination of the control bytes for default configuration example (part 1)
Warning!
The second sequence must have been completely processed before it can be acknowledged with Se-
quenceAck. In the example, there are three different segments within the second sequence, i.e. the
program must include enough receive arrays to handle this situation.
C4 (control byte 4) C5 (control byte 5) C6 (control byte 6)
- SegmentLength (1) = 1 - SegmentLength (6) = 6 - SegmentLength (2) = 2
- nextCBPos (6) = 6 - nextCBPos (1) = 64 - nextCBPos (1) = 64
- MessageEndBit (0) = 0 - MessageEndBit (1) = 0 - MessageEndBit (1) = 128
Control byte Σ 7 Control byte Σ 70 Control byte Σ 194
Table 442: FlatStream determination of the control bytes for default configuration example (part 2)
Large segments:
Segments are limited to a maximum of 63 bytes. This means they can be larger than the active MTU. These large
segments are divided among several sequences when transferred. It is possible for sequences to be completely
filled with payload data and not have a control byte.
Information:
It is still possible to subdivide a message into several segments so that the size of a data packet doesn't
also have to be limited to 63 bytes.
Example:
Three autonomous messages (7 bytes, 2 bytes, 9 bytes) are being transferred using an MTU with a width of 7 bytes.
The configuration allows the transfer of large segments.
Message 3:
C2 B1 B2 - - - - Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C3 D1 D2 D3 D4 D5 D6 Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 443: FlatStream determination of the control bytes for large segments example
Message 3:
D3 D4 D5 D6 D7 D8 D9 Sequence for bus cycle 3
D1 D2 D3 D4 D5 D6 D7 D8 D9
C0 - - - - - - Sequence for bus cycle 4
➯ C0 control byte
A unique control byte must be generated for each segment. In addition, the C0 control byte is generated to keep
communication on standby.
C1 (control byte 1) C2 (control byte 2) C3 (control byte 3)
- SegmentLength (7) = 7 - SegmentLength (2) = 2 - SegmentLength (9) = 9
- nextCBPos (0) = 0 - nextCBPos (0) = 0 - nextCBPos (0) = 0
- MessageEndBit (1) = 128 - MessageEndBit (1) = 128 - MessageEndBit (1) = 128
Control byte Σ 135 Control byte Σ 130 Control byte Σ 137
Table 444: FlatStream determination of the control bytes for large segments and MultiSegmentMTU example
The "Forward" function is a method that can be used to substantially increase the FlatStream data rate. The basic
principle is also used in other technical areas such as "pipelining" for microprocessors.
How it works
Communication on the X2X bus cycles through five different steps to transfer a FlatStream sequence. A successful
sequence transfer therefore requires at least five bus cycles.
Step I Step II Step III Step IV Step V
Actions Transfer sequence from Cyclic matching of MTU and Append sequence Cyclic matching Check SequenceAck
transmit array, module buffer toreceive array, of MTU and module buffer
increase Sequence- adjust SequenceAck
Counter
Resource Transmitter Bus system Receiver Bus system Transmitter
(task for sending) (direction 1) (task for receiving) (direction 2) (task for Ack checking)
Sequence 3 ...
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Configuration
The Forward function only has to be enabled for the input direction. Two additional configuration registers are
available for doing so. FlatStream modules have been optimized in such a way that they support this function. In
the output direction, the Forward function can be used as soon as the size of the OutputMTU is specified.
Forward:
With the "Forward" register, the user specifies how many unacknowledged sequences the module is allowed to
send.
Recommendation:
X2X bus: Max. 5
POWERLINK: Max. 7
Data type Values
USINT 1...7
Default: 1
ForwardDelay:
The "ForwardDelay" register is used to specify the delay time in µs. This is the amount of time the module has
to wait after sending a sequence until it is allowed to write new data to the MTU in the following bus cycle. The
program routine for receiving sequences from a module can therefore be run in a task class whose cycle time is
slower than the bus cycle.
Data type Values [µs]
UINT 0...65535
Default: 0
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Zeit
Figure 450: Effect of ForwardDelay when using FlatStream communication with the Forward function
In the program, it is important to make sure that the CPU is processing all of the incoming InputSequences and In-
putMTUs. The ForwardDelay value causes delayed acknowledgment in the output direction and a delayed recep-
tion in the input direction. In this way, the CPU has more time to process the incoming InputSequence or InputMTU.
The basic algorithm for transmitting and receiving data remains the same. With the Forward function, up to seven
unacknowledged sequences can be transmitted. Sequences can be transmitted without having to wait for the
previous message to be acknowledged. Since the delay between writing and response is eliminated, a considerable
amount of additional data can be transferred in the same time window.
Algorithm for transmitting:
Cyclic status query:
- The Module monitors the OutputSequenceCounter.
0. Cyclic checks:
- The CPU must check OutputSyncAck.
→ If OutputSyncAck = 0: Reset the OutputSyncBit and resynchronize the channel.
- The CPU must check whether OutputMTU is enabled.
→ If OutputSequenceCounter > OutputSequenceAck + 7, then it is not enabled because the last sequence has not yet been acknowledged.
1. Preparation (create transmit array):
- The CPU must split up the message into valid segments and create the necessary control bytes.
- The CPU must add the segments and control bytes to the transmit array.
2. Transmitting:
- The CPU must transfer the current part of the transmit array to the OutputMTU.
- The CPU must increase the OutputSequenceCounter for the sequence to be accepted by the module.
- The CPU can then transmit in the next bus cycle if the MTU has been enabled.
The module responds since OutputSequenceCounter > OutputSequenceAck:
- The module accepts data from the internal receive buffer and appends it to the end of the internal receive array.
- The module is acknowledged and the currently received value of the OutputSequenceCounter is transferred to OutputSequenceAck.
- The module requests the status cyclically again.
3. Completion (acknowledgment):
- The CPU must check OutputSequenceAck cyclically.
→ A sequence is only considered to have been transmitted successfully if it has been acknowledged via OutputSequenceAck. In order to detect potential trans-
mission errors in the last sequence as well, it is important to make sure that the algorithm is run through long enough.
Note:
To monitor communication times exactly, the task cycles that have passed since the last increase of the OutputSequenceCounter should be counted. In this
way, the number of previous bus cycles necessary for the transmission can be measured. If the monitoring counter exceeds a predefined threshold, then the
sequence can be considered lost (the relationship of bus to task cycle can be influenced by the user so that the threshold value needs to be determined individ-
ually).
Details/Background:
1. Illegal SequenceCounter size (counter offset)
Error situation: MTU not enabled
If the difference between SequenceCounter and SequenceAck is larger than allowed during transmission,
then a transmission error has occurred. In this case, all unacknowledged sequences must be repeated with
the old SequenceCounter value.
2. Checking an acknowledgment
After an acknowledgment has been received, a check must verify whether the acknowledged sequence has
been transmitted and had not yet been unacknowledged. If a sequence has been acknowledged more than
once, then a fatal error has occurred. The channel must be closed and resynchronized (same behavior as
when not using Forward).
Information:
In exceptional cases, the module can increment OutputSequenceAck by more than 1 when using
Forward.
This is not an error. The CPU is permitted to consider all sequences up to the one being acknowl-
edged as having been transmitted successfully.
In industrial environments, it's often the case that many different devices from various manufacturers are being
used side by side. The electrical and/or electromagnetic properties of these technical devices can sometimes cause
them to interfere with one another. These kinds of situations can be reproduced and protected against in laboratory
conditions only to a certain point.
Precautions have been taken for X2X bus transfers if this type of interference occurs. For example, if an invalid
checksum occurs, the I/O system will ignore the data from this bus cycle and the receiver receives the last valid
data once more. With conventional (cyclic) data points, this error can often just be ignored. In the following cycle,
the same data point is again retrieved, adjusted and transferred.
Using the "Forward" function with FlatStream communication makes this situation more complex. The receiver
receives the old data again in this situation as well, i.e. the previous values for SequenceAck/SequenceCounter
and the old MTU.
Loss of acknowledgment (SequenceAck):
If a SequenceAck value is lost, then the MTU was already transferred properly. For this reason, the receiver is per-
mitted to continue processing with the next sequence. The SequenceAck is aligned with the associated Sequence-
Counter and sent back to the transmitter. The check of incoming acknowledgments shows that all sequences up
to the last one acknowledged have been transferred successfully (see image: Sequence 1, 2).
Loss of transmission (SequenceCounter, MTU):
If a bus cycle drops out and the SequenceCounter value and/or filled MTU are lost, then no data reaches the
receiver. At this point, the transfer routine is not yet affected by the error. The time-controlled MTU is released
again and can be rewritten to. The receiver receives SequenceCounter values that have been incremented several
times. For the receive array to be put together correctly, the receiver is only allowed to process transmissions
whose SequenceCounter has been increased by one. The incoming sequences must be ignored, i.e. the receiver
stops and doesn't send back any more acknowledgments. If the maximum number of unacknowledged sequences
has been sent and no acknowledgments are returned, the transmitter must repeat the affected SequenceCounter
and associated MTUs (see image: Sequence 3, 4).
Bus cycle 1 Bus cycle 2 Bus cycle 3 Bus cycle 4 Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
Bus cycle 1 Bus cycle 2 Bus cycle 3 EMC Bus cycle 5 Bus cycle 6 Bus cycle 7 Bus cycle 8 Bus cycle 9 Bus cycle 10
Time
EnDat is a synchronous interface capable of half-duplex communication. A variety of safety measures are taken
to ensure error-free signal transfer.
• An automatically generated checksum is sent together with a signal and evaluated by the recipient.
• The command which the encoder is responding to is repeated at the start of a response.
In Flatstream mode, the module acts as a bridge between the CPU and the EnDat slave. EnDat-specific algorithms
were implemented to monitor timeouts and handle checksums. During normal operation, the user does not have
access to these details.
More detailed information can be found in the documentation "Technical Information - EnDat 2.2" and the encoder's
manufacturer data.
Master command
Protocol bytes Information
No. Name
Master
1 0x00 Command (Reset)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x00 Repetition (safety)
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x01 Command (acknowledge error)
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x01 Repetition (safety)
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x04 Command (read parameter)
2 MRS code
Memory area to read
3 Parameter no.
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x04
2 MRS code Repetition (safety)
3 Parameter no.
4 Value_L
Value read
5 Value_H
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x05 Command (write parameter)
2 MRS code
Memory area to write to
3 Parameter no.
4 Value_L
Value to be written
5 Value_H
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x05
2 MRS code Repetition (safety)
3 Parameter no.
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x06 Command (read parameter from memory block)
2 MRS code
3 Block no. Memory area to read
4 Parameter no.
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x06
2 MRS code
Repetition (safety)
3 Block no.
4 Parameter no.
5 Value_L
Value read
6 Value_H
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x07 Command (write parameter in memory block)
2 MRS code
3 Block no. Memory area to write to
4 Parameter no.
5 Value_L
Value to be written
6 Value_H
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x07
2 MRS code
Repetition (safety)
3 Block no.
4 Parameter no.
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x08 Command (read word 1 from additional information)
2 MRS code Memory area to read
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x08
Repetition (safety)
2 MRS code
3 Value_L
Word 1 from additional information
4 Value_H
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x09 Command (read word 2 from additional information)
2 MRS code Memory area to read
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x09
Repetition (safety)
2 MRS code
3 Value_L
Read word 1 from additional information (overhead)
4 Value_H
5 Value_L
Word 2 from additional information
6 Value_H
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x0A Command (read word 3 from additional information)
2 MRS code Memory area to read
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x0A
Repetition (safety)
2 MRS code
3 Value_L
Read word 1 from additional information (overhead)
4 Value_H
5 Value_L
Read word 2 from additional information (overhead)
6 Value_H
7 Value_L
Word 3 from additional information
8 Value_H
Master
Master command
Protocol bytes Information
No. Name
Master
1 0x0B Command (read word 4 from additional information)
2 MRS code Memory area to read
Slave
Slave response
Protocol bytes Information
No. Name
Slave
1 0x0B
Repetition (safety)
2 MRS code
3 Value_L
Read word 1 from additional information (overhead)
4 Value_H
5 Value_L
Read word 2 from additional information (overhead)
6 Value_H
7 Value_L
Read word 3 from additional information (overhead)
8 Value_H
9 Value_L
Word 4 from additional information
10 Value_H
Master
A function model specifies the registers on the module (storage model) that are available for the application. Only
these registers are processed on the module during each cycle and transferred cyclically via the bus. In this way,
it is possible to minimize the cycle time by selecting the correct function model.
The minimum cycle time defines how far the bus cycle can be reduced without causing a communication error
or impaired functionality. It should be noted that very fast cycles decrease the idle time available for handling
monitoring, diagnostics and acyclic commands.
Minimum cycle time
100 µs
The minimum I/O update time defines how far the bus cycle can be reduced while still allowing an I/O update to
take place in each cycle.
Minimum I/O update time
100 µs
4.17.2 X20IF0000
Covers for unused interface module slots are included with X20 CPUs. If an X20 system is used in a maritime
environment, then the system will be subjected to increased vibration fatigue. In order to achieve the stability
necessary for operation, the X20IF0000 dummy interface module from the X20 series is used instead of the covers.
• Cover for unused interface module slots
• IF dummy modules required if the X20 system is subjected to increased vibration fatigue
• Module with no electrical function
Product ID X20IF0000
Short description
Accessories Non-functional dummy module
General information
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
4.17.3 X20ZF0000
The X20ZF0000 module is used as a place holder for later system expansion.
• Place holder for later system expansion
• Used as a terminal holder
• Module with no electrical function
Product ID X20ZF0000
Short description
Accessories Non-functional dummy module
General information
Certification
CE Yes
cULus Yes
ATEX Zone 2 Yes
GL Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB06 or X20TB12 terminal block separately
Order 1x X20BM11 bus module or 1x X20BM01 supply bus module separately
Spacing 12.5 +0.2 mm
4.17.3.4 Pinout
X20 ZF 0000
4.17.3.5 Connection example
4.17.4 X20ZF000F
Product ID X20ZF000F
Short description
Accessories Non-functional dummy module
General information
Certification
CE Yes
ATEX Zone 2 Yes
Operating conditions
Mounting orientation
Horizontal Yes
Vertical Yes
Installation at elevations above sea level
0 to 2000 m No limitations
>2000 m Reduction of ambient temperature by 0.5°C per 100 m
EN 60529 protection IP20
Environmental conditions
Temperature
Operation
Horizontal installation -25 to 60°C
Vertical installation -25 to 50°C
Derating -
Storage -40 to 85°C
Transport -40 to 85°C
Relative humidity
Operation 5 to 95%, non-condensing
Storage 5 to 95%, non-condensing
Transport 5 to 95%, non-condensing
Mechanical characteristics
Note Order 1x X20TB1E or 1x X20TB1F terminal block separately
Order 1x X20BM11 bus module or 1x X20BM01 supply bus module separately
Spacing 12.5 +0.2 mm
4.17.4.4 Pinout
4.18.2 X20CS1011
SmartWire from the company Moeller makes it possible to very easily integrate switching devices such as contac-
tors or motor protection switches in the X20 system without extensive wiring. It replaces the control circuit wiring
between the controller and switching devices with pluggable, pre-assembled connection cables.
Although SmartWire is an intelligent connection, this changes almost nothing for the machine programmer. Inte-
gration in the X20 system via the interface module cuts down on overall communication. The individual switching
devices can simply be viewed as digital inputs and outputs.
Practical applications
SmartWire allows up to 16 switching devices to be connected using pre-assembled cables and attached to the X20
SmartWire interface module. The system can configure itself completely at the push of a button without additional
intervention or effort. This replaces the wiring test that was previously necessary.
At the same time, the device configuration is known to the system. If a device is no longer available due to an error
or intervention, it will be detected immediately. Once corrected, the system continues to run.
The interface module is designed as a normal electronic module, which means it can be placed anywhere on the
remote backplane.
• X2X SmartWire master for controlling up to 16 SmartWire slaves
• Simple connection using pre-assembled connection cables
• Moeller SmartWire modules for Moeller standard switching devices
• Replaces control circuit wiring
• Contactor activation
• Contactor switching status
• Motor circuit breaker status
• 24 VDC control voltage via SmartWire connection cable
Product ID X20CS1011
Short description
Communication module 1 SmartWire master for controlling up to 16 slaves
General information
B&R ID code 0xA38D
Status indicators SmartWire bus function, external supply voltage, operating state, module status
Diagnostics
Module run/error Yes, using status LED and software
SmartWire operating state Yes, using status LED and software
U Aux Yes, using status LED
Power output
Internal I/O 6.8 W for supplying external slaves (equal to 16 slaves each with 0.425 W)
Power consumption
Bus 0.01 W
Internal I/O 1.5 W
Additional power dissipation caused by the actua- -
tors (resistive) [W]
Electrical isolation
SmartWire bus - X2X Link Yes
SmartWire supply (17 VDC) - I/O supply No
Certification
CE Yes
cULus Yes
cCSAus HazLoc Class 1 Division 2 Yes
ATEX Zone 2 Yes
KC Yes
GOST-R Yes
Interfaces
Interface
Type SmartWire (LIN bus)
Design Connection made using 12-pin X20TB12 terminal block
Transfer rate 19200 bit/s
SmartWire
Data format 1 start bit, 8 data bits, no parity bit, 1 stop bit
Max. distance 4m
Configuration button
Internal Integrated in the module on the bottom of the housing.
External Connection via 12-pin terminal block
N.O. contact, not electrically isolated (use potential-free contact)
SWIRE terminal 1 (24 VDC)
Voltage drop for reverse polarity protection at Max. 0.1 VDC
3A
Voltage range Voltage and supply
Current load Max. 3 A
Short circuit protection No, only with external fuse
Monitoring 20 VDC < 24 VDC Aux < 29.4 VDC (via firmware)
SWIRE terminal 2
Daisy chain signal 5 VDC, CMOS level
SWIRE terminal 5 (bus level)
Dominant <2 VDC
Recessive >14.85 VDC
SWIRE terminal 6 (17 VDC)
Voltage range Typ. 16.6 VDC (16.3 VDC to 16.8 VDC)
Summation current Max. 400 mA for 16 SmartWire slaves
Short circuit protection Yes
Monitoring 14.2 VDC < 17 VDC Aux < 17.9 VDC (via firmware)
U-Aux (24 VDC aux supply)
Connection Externally via 12-pin terminal block 1)
Input voltage 24 VDC -15% / +20%
Fuse Recommended line fuse: 3 A, slow-blow
Summation current Max. 3 A fo