This description is only intended for the use of trained specialists in control
and automation engineering who are familiar with the applicable national
standards.
The responsible staff must ensure that the application or use of the products described satisfy all the requirements for safety, including all the relevant laws, regulations, guidelines and standards.
The documentation has been prepared with care. The products described are,
however, constantly under development. For that reason the documentation is not
in every case checked for consistency with performance data, standards or other
characteristics, and does not represent an assurance of characteristics in the sense
of § 459, Para. 2 of the German Civil Code. In the event that it contains technical or
editorial errors, we retain the right to make alterations at any time and without warning. No claims for the modification of products that have already been supplied may
be made on the basis of the data, diagrams and descriptions in this documentation.
This manual is copyrighted. Any reproduction or third party use of this protected
The purpose of this document is to provide DeviceNet Specific Information needed to set up a DeviceNet
Network with Beckhoff FC520x / CX1500-x520 DeviceNet Interface units. From DeviceNet point of view
both units have the same functionalities. Therefore, this documentation serves for both.
Beside the Product Overview it shows the DeviceNet Configuration and Diagnostic Data of Beckhoff’s
TwinCAT System Manager using a Beckhoff DeviceNet Interface FC520x or CX1500-x520. It is intended
for the usage of Master and Slave Interfaces and describes the meaning of the diagnostic inputs and
explains the troubleshooting for the specific errors.
The responsible staff must ensure that the application or use of the products described satisfy all the requirements for safety
State at Delivery
All the components are supplied in particular hardware and software configurations appropriate for the
application. Modifications to hardware or software configurations other than those described in the documentation are not permitted, and nullify the liability of Elektro BECKHOFF GmbH.
Personal Qualification
This description is only intended for the use of trained specialists in control and automation engineering
who are familiar with the applicable national standards.
, including all the relevant laws, regulations, guidelines and standards.
The FC5201 and FC5202 PC plug-in cards link the PC to a DeviceNet network. They can act as master
or as slave modules. The PCI bus interface ensures both high transmission rates to the PC and fully
automatic configuration of the cards in the PC hardware. The DeviceNet cards provide a powerful implementation of the protocol, offering many desirable features:
•
One (FC5201) or two (FC5202) DeviceNet channels, each with its own processor, memory, etc.
•
All DeviceNet I/O modes are supported: polling, change of state, cyclic, strobed
•
Optionally two DeviceNet channels in parallel on one card are possible
•
Powerful parameter and diagnostics interface
•
The error management for each bus user is freely configurable
•
It is possible to read the bus configuration and automatically assign the "eds" files
125, 250, 500 kbaud
plug-and-play PCI interface 32 bit with 4 kbytes DPRAM
per channel
open style connector 5-pin according to DeviceNet specification, galvanically isolated. Card comes with connector.
Bus nodes
Process image
Communication
Termination Resistor
Hardware diagnostics
Dimensions
Operating temperature
per channel: max. 63 slaves
total max. 3 kbyte input and output data
master and slave functionality
Switchable
2 LEDs per channel
approx. 106 x 175 mm
0 °C ... 55 °C
The CX1500-x520 links the CPU to a DeviceNet network. The CX1500-M520 can act as master, the
CX1500-B520 as slave module. The DeviceNet interface provides a powerful implementation of the protocol, offering many desirable features:
•
All DeviceNet I/O modes are supported: polling, change of state, cyclic, strobed
•
Powerful parameter and diagnostics interface
•
The error management for each bus user is freely configurable
•
It is possible to read the bus configuration and automatically assign the "eds" files
DeviceNet is an open system based on CAN, developed by Bosch a few years ago. CAN was primarily
intended for the transfer of data within automobiles, and millions on CAN Chips have since been installed.
The disadvantage of using CAN in automation technology is that it does not define an application layer. It
specifies only the physical layer and data security layer.
DeviceNet specifies a uniform application layer and this makes it possible to use the CAN protocol for
industrial applications. ODVA (the open DeviceNet Vendor Association) is an independent association
which supports Manufactures and users of the DeviceNet system. ODVA ensures that all of the devices
which conform to the specification can operate together in one system, regardless of their manufacturer.
Example of DeviceNet in use:
For more details see the DeviceNet Specification or look at www.odva.org, the official Internet address of
the Open DeviceNet Vendor Association (ODVA).
On the FC520x card there are DeviceNet / CAN termination resistors (120 Ohms). They can be activated
with a DIP-Switch close to the DeviceNet Connector.
Channel B
B
A
Channel A
DIP-Switch for terminating resistor (120 Ohm) for
each channel
With the CX1500-M520, the MAC-Id / Address is set within the TwinCAT System Manger
With the CX1500-B20, the MAC-Id / Address is set with the Address selector
Fieldbus PCI cards may only be fitted by qualified personnel in accordance and the following points
must be observed
•
In order to protect the card from electrostatic discharge the user must be discharged before han-
dling the card or the PC.
•
Before opening the PC housing it must be switched off, and the mains plug must be removed.
Channel B
14
B
A
It may be necessary before fitting to set the Dip-Switch in order to activate the internal CAN / DeviceNet
bus terminating resistors. The card can be fitted into any free PCI slot. Ensure that the PCI bus connector
is making good contact, and that the module is seated firmly. Fasten the module to the PC slot housing
with the fixing screw.
Channel A
DIP-Switch for terminating resistor (120 Ohm) for
each channel
CAN / DeviceNet is a 2-wire bus system, to which all participating devices are connected in parallel (i.e.
using short drop lines). The bus must be terminated at each end with a 120 (or 121) Ohm terminating
resistor to prevent reflections. This is also necessary even if the cable lengths are very short!
Since the CAN signals are represented on the bus as the difference between the two levels, the CAN
leads are not very sensitive to incoming interference (EMI): Both leads are affected, so the interference
has very little effect on the difference.
The maximum length of a CAN bus is primarily limited by the signal transit time. The multi-master bus
access procedure (arbitration) requires signals to reach all the nodes at effectively the same time (before
the sampling within a bit period). Since the signal transit times in the CAN connecting equipment (transceivers, opto-couplers, CAN controllers) are almost constant, the line length must be chosen in accordance with the baud rate:
For the DeviceNet use of the CAN Bus following Baud Rates and Bus Lengths are specified:
BaudRate
500 kbit/s
250 kbit/s
125 kbit/s
Bus Length
< 100 m
< 250 m
< 500 m
3.2.3 Drop-Lines
Drop lines must always be avoided as far as possible, since they inevitably cause reflections. The reflections caused by drop lines are not however usually critical, provided they have decayed fully before the
sampling time. In the case of the bit timing settings selected in the bus couplers it can be assumed that
this is the case, provided the following drop line lengths are not exceeded (according to DeviceNet Specification):
BaudRate Drop line length Total length of all drop lines
500 kbit/s
250 kbit/s
125 kbit/s
< 6 m
< 6 m
< 6 m
< 39 m
< 78 m
< 156 m
Drop lines must not have terminating resistors.
Star Hub (Multiport Tap)
Shorter drop line lengths must be maintained with passive distributors ("multiport taps"), such as the
Beckhoff ZS5052-4500 Distributor Box. The following table indicates the maximum drop line lengths and
the maximum length of the trunk line (without the drop lines):
The ZB5200 cable material corresponds to the DeviceNet specification. The ready-made ZK1052-xxxxxxxx bus cables for the Fieldbus Box modules are made from this cable material. It has the following
specification:
•
2 x 2 x 0.34 mm² (AWG 22) twisted pairs
•
double screened braided screen with filler strand
•
characteristic impedance (1 MHz): 126 Ohm
•
conductor resistance 54 Ohm/km
•
sheath: grey PVC, external diameter 7.3 mm
•
printed with "InterlinkBT DeviceNet Type 572" as well as UL and CSA ratings
•
stranded wire colours correspond to the DeviceNet specification
•
UL recognised AWM Type 2476 rating
•
CSA AWM I/II A/B 80°C 300V FT1
•
corresponds to the DeviceNet "Thin Cable" specification
The TwinCAT System Manager Tool is used to configure the FC520x DeviceNet PCI card and the
CX1500-x520 Fieldbus Modules. The System Manager provides a representation of the number of programs of the TwinCat PLC systems, the configuration of the axis control and of the connected I/O channels as a structure, and organises the mapping of the data traffic.
For applications without TwinCAT PLC or NC, the TwinCAT System Manager Tool configures the programming interfaces for a wide range of application programs:
•
ActiveX control (ADS-OCX) for e.g. Visual Basic, Visual C++, Delphi, etc.
•
DLL interface (ADS-DLL) for e.g. Visual C++ projects
•
Script interface (ADS script DLL) for e.g. VBScript, JScript, etc.
4.1.1 System Manager – Features
•
- Bit-wise association of server process images and I/O channels
•
- Standard data formats such as arrays and structures
•
- User defined data formats
•
- Continuous variable linking
•
- Drag and Drop
•
- Import and export at all levels
4.1.2 Configuration by means of the TwinCAT System Manager
The procedure, and the configuration facilities in the System Manager are described within the next chapters.
Appending a Device can either be executed by running the “Scan-Devices” routine of the TwinCAT System Manager or by selecting manually the Device out of the list of possible DeviceNet Devices.
Appending the Device manually is done by e.g. selecting the “IO-Devices” and apply the right MouseButton:
If the FC520x-Device is appended manually, all settings for the DeviceNet Slave are configured automatically.
If the FC520x-Device is appended with the “Scan-Devices” routine, TwinCAT should not search for new
Boxes. The scan has to be stopped after detecting the FC520x and the following steps have to be done:
: Shows in which logical PCI slot the card was detected and which IRQ is assigned to it. The
IRQ is unused.
Search
: Searches for all connected FC520x channels. Select those required. In the case of an FC5202
both channels A and B appear. These behave in logical terms like two FC5201 cards.
Upload Configuration:
Scans the DeviceNet network and adds all found devices (boxes cannot be
added). In the case of Beckhoff boxes, reads the configuration precisely. Searches external devices to
find the corresponding EDS file.
Firmware
Firmware Update
MAC-ID
: Shows the current firmware version of the FC520x.
: Update the FC520x card firmware version here.
: Each DeviceNet device requires a unique station number – MAC-ID (Medium Access Identifier)-
including the master.
Baudrate
: Set the DeviceNet Baudrate here. Select one of the following: 125kBaud, 250 kBaud and 500
kBaud
Cycle Time
IO-Cycle Time
: Displays the cycle time of the corresponding highest priority task.
: Sets the cycle time for the I0 connections. This value is used as the default value for
: Searches for all connected CX1500-x520 channels.
: Scans the DeviceNet network and adds all found devices (boxes cannot be
added). In the case of Beckhoff boxes, reads the configuration precisely. Searches external devices to
find the corresponding EDS file.
Firmware
Firmware Update
MAC-ID
: Shows the current firmware version of the CX1500-x520.
: Update the CX1500-x520 card firmware version here.
: Each DeviceNet device requires a unique station number – MAC-ID (Medium Access Identifier)-
including the master
Note:
With the CX1500-M520, the MAC-Id / Address is set within the TwinCAT System Manger
With the CX1500-B20, the MAC-Id / Address is set with the Address selector on the module
Baudrate
: Set the DeviceNet Baudrate here. Select one of the following: 125kBaud, 250 kBaud and 500
kBaud
Cycle Time
IO-Cycle Time
: Displays the cycle time of the corresponding highest priority task.
: Sets the cycle time for the I0 connections. This value is used as the default value for
: This counter increments each time when at the beginning of theTwinCAT-Cycle
the last Bus-Cycle was not finished. If the Cycle-Time of the DeviceNet-FW exceeds the CycleTime of the
corresponding highest priority task this counter is incremented.
If the Failed Cycle Counter is incremented permanently after the Network-Start, the following has to be
checked:
- Cycle-time of the corresponding highest priority task should may adapted to the max. Cycle-Time
of the DeviceNet-FW
- Network-Load for the DeviceNet-Master has to be checked. There are may too much DeviceNet
Boxes connected to the DeviceNet Master, which could cause a heavy CycleTime for the DeviceNet Master FW.
- Check IO-Cycle Times of attached DeviceNet-Boxes. Some of the IO-Cyle Times of the DeviceNet Boxes are may to fast, which could cause a heavy CycleTime for the DeviceNet Master
FW.
The BoxState section shows the actual state of the connected Boxes for the DeviceNet-Master unit. The
BoxState is corresponding to the MAC-State of each DeviceNet-Box:
The DeviceNet Slave Functionality is the same for FC520x and CX1500-B520.
Diagnostic Data is corresponding to the explanations of the Diagnostic Inputs for DeviceNet Devices and
DeviceNet Boxes.
The DeviceNet Slave Port is Pre-Initialized using the IO-Mode Polling. Other IO-Modes can be selected
referring the DeviceNet rules by disabling/enabling of the IO-Modes. The Inputs and Outputs Data-Length
is set to 8 Bytes per Default. The Data-Lengths can be adjusted as used by the application.
The DeviceNet Slave Port is Pre-Initialized using the IO-Mode Polling. Other IO-Modes can be selected
referring the DeviceNet rules by disabling/enabling of the IO-Modes:
If there are still Inputs/Outputs disabled after selecting other IO-Modes, the referring DeviceNet rules for
the IO-Modes are not valid:
The Inputs and Outputs can be configured by inserting Variables. This can be done according to the need
of the application.
Within DeviceNet, data-lengths are seen as Byte-Steams. The total Number of Bytes have to be configured in the DeviceNet Masters Input and Output Size for its DeviceNet Slaves:
Note: The Data-Length for Inputs and Outputs should not exceed 255 Bytes
Appending a DeviceNet Box can either be executed by running the “Scan-Boxes” routine of the TwinCAT
System Manager or by selecting manually the Device out of the list of possible DeviceNet Devices.
Appending the DeviceNet-Box manually is done by e.g. selecting the “DeviceNet-Devices” and apply the
right Mouse-Button:
The “Insert-Box” Menu shows the list of available Devices:
The list is generated with the Information of the EDS-Files stored in:
: Sets the MAC-ID of the DeviceNet participant (between 0 and 63). This value must comply with
the value set at the Bus Coupler.
Cycle Time
: Sets the cycle time for the I0 connection (Polled and Bit-Strobe). This value is added to the
Expected Packet Rate (EPR) attributes of the DeviceNet slave and acts as a timeout monitor for IO connections.
Electronic Key
: Serves to check the devices within the network at the system StartUp. The electronic
key is read from the devices at every system StartUp and compared with the saved configuration.
Polled
: Produced/Consumed: Activation of the ”Polling” operating mode, cyclical writing and reading of IO
data. Setting of the data content of the data transmitted via the polled IO connections. You can choose
from digital data, analogue data or both. The selection depends upon the BK52xx terminal arrangement.
Bit-Strobed
: Produced/Consumed: Activation of the ”Bit Strobe” Operating Mode. With a broadcast message all nodes are requested to send their bit strobe message (up to 7 bytes input or status data). Setting
of the data content of the data transmitted via the bit-strobed IO connections. You can choose between
digital data or diagnostic data.
- Produced/Consumed: Setting of the data content of the data transmitted via the change of state/cyclical
IO connections. You can choose from digital data, analogue data or both. The selection depends upon
the BK52xx terminal arrangement.
- Change of State / Cyclic: Selecting the Corresponding Operating Mode
- Heartbeat Rate / Scan Rate: In the "Change of State" mode the heartbeat rate gives the cycle time of
the cyclical send of the lower-level (i.e. in addition to the event driven) IO data. In the ”Cyclic” operating
mode the scan rate gives the cycle time of the IO data send.
Inhibit time: Delay period in the ”Change of State” operating mode inserts this pre-set delay period after a
change of state before the IO data send.
Acknowledge Timeout: Time before the re-send in the event of faulty acknowledgement of a change of
state / cyclical message.
Acknowledge Retry Limit: Maximum number of re-sends until IO connection goes into error mode.
K-Bus Update
: Calculates the anticipated duration of a complete update of the terminal bus (according to
the number of connected terminals). This is not to be seen as the response time of the DeviceNet Node
to DeviceNet IO-Requests.
: Sets the MAC-ID of the DeviceNet participant (between 0 and 63). This value must comply with
the value set at the Bus Coupler.
Cycle Time
: Sets the cycle time for the I0 connection(Polled and Bit-Strobe). This value is added to the
Expected Packet Rate (EPR) attributes of the DeviceNet slave and acts as a timeout monitor for IO connections.
Electronic Key
: Serves to check the devices within the network at the system StartUp. The electronic
key is read from the devices at every system StartUp and compared with the saved configuration.
Polled
: Produced/Consumed: Activation of the ”Polling” operating mode, cyclical writing and reading of IO
data. Setting of the data content of the data transmitted via the polled IO connections. You can choose
from digital data, analogue data or both. The selection depends upon the BK52xx terminal arrangement.
Bit-Strobed
: Produced/Consumed: Activation of the ”Bit Strobe” Operating Mode. With a broadcast message all nodes are requested to send their bit strobe message (up to 7 bytes input or status data). Setting
of the data content of the data transmitted via the bit-strobed IO connections. You can choose between
digital data or diagnostic data.
- Produced/Consumed: Setting of the data content of the data transmitted via the change of state/cyclical
IO connections. You can choose from digital data, analogue data or both. The selection depends upon
the BK52xx terminal arrangement.
- Change of State / Cyclic: Selecting the Corresponding Operating Mode
- Heartbeat Rate / Scan Rate: In the "Change of State" mode the heartbeat rate gives the cycle time of
the cyclical send of the lower-level (i.e. in addition to the event driven) IO data. In the ”Cyclic” operating
mode the scan rate gives the cycle time of the IO data send.
Inhibit time: Delay period in the ”Change of State” operating mode inserts this pre-set delay period after a
change of state before the IO data send.
Acknowledge Timeout: Time before the re-send in the event of faulty acknowledgement of a change of
state / cyclical message.
Acknowledge Retry Limit: Maximum number of re-sends until IO connection goes into error mode.
K-Bus Update
: Calculates the anticipated duration of a complete update of the terminal bus (according to
the number of connected terminals). This is not to be seen as the response time of the DeviceNet Node
to IO-Requests.
Attributes/Parameters sent to the Box at StartUp of the Network are displayed/managed on this page.
Other entries can be managed using ”New”, ”Delete” and ”Edit”:
Start-Up Attributes are loaded into the DeviceNet Box at the Beginning of each Network-Startup.. The
values are loaded before the IO-Connections are started.
In order to be able to read and write attributes during the running time (e.g. from the PLC), the Box (e.g.
Bus Coupler) can be allocated via an ADS port. The ADS Port can be used to read / write attributes via
ADS read requests / ADS write requests:
The ADS IndexGroup contains the ClassId and the ADS IndexOffset contains InstanceId and AttributeId
(InstanceId * 256 + AttributeId).
The following ADS-Commands are used to exchange DeviceNet Explicit-Messages:
The parameters are read from the EDS-File when appending the box. If the system has not started up,
the EDS default value is always displayed under the value input:
When configuring a DeviceNet node, an electronic data sheet (EDS) is usually provided by the manufacture of that device to assist in this task. An EDS file is a text file that describes properties of a particular
DeviceNet node. It includes the number of bytes that are transmitted to the node (output information) and
the number of bytes that are received from the node (input and status information). Furthermore it includes a Parameter sections, which is analyzed by the SystemManger and displayed within this section.
The LEDs on the FC5201 / CX1500-x520 are implemented as DeviceNet Module-Network-Status LEDs.
For each channel there is a green and a red colour LED next to the channels DeviceNet connector.
The LEDs are displaying a different behaviour in Master and Slave Mode :
Voltage Error, Master failed Duplicate MacId Check
Inspect the devices, verify connections,
check cabling
Check Baudrate and cabling, Master is
may not able to set up his Duplicate Mac Id
messages, Check DeviceNet Voltage (24
Volt) at DeviceNet Connector
5.1.4 Slave-Functionality
LED Description Troubleshooting
Green Flashing Slave port has finished the Duplicate
MacId Check (Network OK), Slave
Port is not communicating with its
Master
Green on Slave port is online and communi-
cates with its Master
Red Flashing Slave port has lost communication
with its Master, Timeout of SlavePort
Red on DeviceNet Bus OFF, DeviceNet
Voltage Error, Slave port failed Duplicate MacId Check
None
None
Inspect the Master device, verify connections, check cabling
Check Baudrate and cabling, Slave Port is
may not able to set up his Duplicate Mac Id
messages, Check DeviceNet Voltage (24
Volt) at DeviceNet Connector
5.2 Device Diagnostics
Note: It is mandatory and recommended to take all the diag-
nostic Inputs of the DeviceNet Device into account.
5.2.1 Common Inputs
cycleCounter
error
: indicates the number of boxes with a BoxState unequal zero
actualCycleTime
DiagFlag
using ADS Read. For that purpose, specify the net ID of the FC520x / CX1500-x520, the port number 200
and the IndexGroup 0xF100. The IndexOffset and the length then relate to the diagnostic data.
CycleFailedCounter
the last Bus-Cycle was not finished
: DeviceNet-FW increments this counter once after each cycle
: reserved for future use
: Shows whether the diagnostics information on the card has changed. This can be read off
: This counter increments each time when at the beginning of theTwinCAT-Cycle
0 No error None
1 Node is deactivated by the scanner, node
is no longer in the masters scan-list
For Slave Devices it means that there is
no Data-Exchange between the Master
and the Slave. The Master has released
the DeviceNet Slave
2 No data exchange between node and
DeviceNet Master, node access timeout
18 Node is configured, ready for data ex-
change
42 Electronic Key Error: Vendor Id Make sure that the nodes key parameters
43 Electronic Key Error: Device Type Make sure that the nodes key parameters
44 Electronic Key Error: Product Code Make sure that the nodes key parameters
45 Electronic Key Error: Revision Make sure that the nodes key parameters
46 Error writing start-up attributes Make sure that the nodes start-up parame-
47 Wrong produced IO-Data length Check number of Bytes to be produced by
48 Wrong consumed IO-Data length Check number of Bytes to be consumed by
BECKHOFF and their partners around the world offer comprehensive support and service, making available fast and competent assistance with all questions related to BECKHOFF products and system solutions.
6.1 Support and Service
Beckhoff Support
Support offers you comprehensive technical assistance, helping you not only with the application of individual BECKHOFF products, but also with other, wide-ranging services:
•
world-wide support
•
design, programming and commissioning of complex automation systems
•
and extensive training program for BECKHOFF system components