Material number:

X20CS1012

Description:

• Power supply for up to 64 slaves on the M-Bus

• Decentralized use of the communication interface

The M-Bus master is designed as a single-width module and

can be connected anywhere within the X20 I/O system.

It can therefore be used decentrally for distributed topologies.

The M-Bus master supports transfer rates of 300. 2400 and 9600

bit/s; up to 64 slaves supplied via M-Bus can be connected.

M-Bus (Meter-Bus) is a relatively simple fieldbus for recording

consumption data, such as from electricity or heat meters. 

It is based on a reverse polarity protected two-wire line and works

according to the master-slave principle.

Material number:

X20BC00G3

Description:

• 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 to 4 ms)

• Synchronization between the fieldbus and X2X Link

EtherCAT is an Ethernet-based fieldbus developed by Beckhoff. This protocol is suitable

for both 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 (standalone 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 added to the telegram as it is passing through.

The bus controller allows X2X Link I/O modules to be coupled to EtherCAT and operated on

any EtherCAT master system. A transition between IP20 and IP67 protection outside of the

control cabinet is possible by arranging 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).

Material number:

X20CP0411

Description:

• ARM Cortex-A9 processor with 240 MHz and integrated I/O processor

• Onboard Ethernet

• 2x onboard USB

• 128 MB DDR3 SDRAM

• 512 MB onboard flash drive

• Fanless

• No battery

• Extremely compact

The controllers in the X20 Compact-S family are both powerful and compact.

The fanless, battery-free design of these controllers means they are completely

maintenance-free.

The X20CP0411 is equipped with an ARM Cortex-A9-240 processor, 128 MB RAM

and 512 MB built-in flash drive. The FRAM for storing remanent variables has

16 kB available.

With Ethernet, USB and RS232. the controller offers plenty of communication options.

An optional RS485 or CAN interface is available.

Material number:

X20CP3585

Description:

• Intel Atom 1.0 GHz processor with an additional I/O processor

• Onboard Ethernet, POWERLINK with poll response chaining and USB

• 3 slots for modular interface expansion

• CompactFlash as removable application memory

• 256 MB DDR2-SDRAM

• Controller redundancy possible

• Fanless

The X20CP3585 controller is based on an Atom processor clocked at

1 GHz and equipped with 256 MB DDR2 SDRAM.

USB, Ethernet, POWERLINK and removable CompactFlash are all included

as standard features. A Gigabit Ethernet interface is a standard feature.

For even more real-time network performance, the onboard POWERLINK

interface supports poll response chaining mode (PRC).

The controller is equipped with 3 slots available for X20 communication

modules. Various bus and network systems can easily be integrated into

the X20 system through the use of communication modules.

The EtherCAT interface

From an Ethernet standpoint, the EtherCAT bus is simply a single large Ethernet station. This “station” re

ceives and transmits Ethernet telegrams. The station does not include an Ethernet controller with down

stream microprocessor, however, but rather a large number of EtherCAT slaves. These slaves process the

incoming telegrams during the cycle and extract the relevant payload data or add it and then forward the

telegram to the next EtherCAT slave. The last EtherCAT slave then returns the now fully processed telegram

so that it will be sent back to the master by the first slave as a kind of response telegram. This procedure

utilizes the fact that Ethernet deals separately with transfers in separate directions (Tx and Rx lines) and

operates in full-duplex mode.

The telegrams are processed in a continuous process. While the telegrams are already being sent on, de

layed by just a few bits, the slave recognizes certain commands for itself and executes them accordingly.

Processing takes place in the hardware and is therefore independent of the response times of the slave.

Each station has an addressable memory area of 64 kB, within which it is possible to read, write or write

and read simultaneously. Several EtherCAT commands can be embedded within an Ethernet telegram, each

of which addresses individual stations and/or memory areas.