Type 8681 büS/CANopen
ChangesconcerningbüS/CANopendesign
LED
Red
Device status
Error
- it is critical if the LED is still lit 2 minutes after the last device restart possible errors
• Another device with the same
Node ID is in the same network
• No bus connection (Gateway
/ PLC) due to communication problems or gateway restart
Remedy
• Check baud rate
• Check the Node ID address (if required, correct it so that each address is only available once)
• Check the status of the gateway connected to the system
• If required, replace the device
*) Display/visualization only from firmware version B.02
5.6 Further help
5.6.1 Links to different operating instructions
If you need further help for the configuration of Type 8681 (büS) you can also use further documents.
On the Bürkert website www.burkert.com search for the type number or the device identification number and find the corresponding documents under “Downloads” / “User manuals” (use language filters if necessary):
Operating Instructions Type 8681 | Control Head
Operating Instructions Type ME43 | Fieldbus gateway büS to Industrial Ethernet
For configuration and parameterisation using the Bürkert Communicator, see also:
Software manual Type 8920 | Bürkert Communicator
Software manual | Central configuration management
(Search for type: ME43 / Downloads / User manual)
On the Bürkert website under “Downloads” / “Software” also can be found:
for Type 8681 büS/CANopen, the Object List for CANopen and the corresponding EDS file and
for the gateway, the Parameter List for the respective specific configuration.
To do this, enter the identification or article number of the respective device into the search field, search under
“Downloads” / “Software” the ZIP container with the “Initiation Files”, open it and download the corresponding files.
24
5.6.2 Firmware updates
Firmware updates of the control heads, gateways (and possibly other devices) can only be carried out using the
Bürkert Communicator with the aid of a büS stick. This requires the “installer level”.
The integration of the Bürkert Communicator into the network can be seen, for example, in “Fig. 2”.
The firmware is stored in the Bürkert Communicator and is kept up to date via updates.
english
