Helmholz CAN 300 PRO, Руководство для стартапов

Страница: 31 / 33

8 Troubleshooting
8.1 Looking for errors
To facilitate start-up of a CANopen
®
network, the following tips
must be taken into account.

If the LED BF (“CAN bus error”) is still lit or blinking, check
the physical structure of the CAN bus (terminating resistor,
baud rate, etc.). Use the layer 2 debug display.

If the SF “system errors” LED lights up, there is a defective
MMC in the module, or the imported CAN project has an
internal error.

Check which “device monitoring” method (heartbeat or
nodeguarding) is supported by the slave in question. Do not
use “Consumer Heartbeat” until everything else has been
started up.

On all devices, do not yet activate the option “Mandatory
device” so that the master will definitely start up and show all
the stations found in the slave list of the CANopen
®
debug
display. These stations can be defined as a mandatory device if
necessary.

Initially set “Wait after reset” to a long time (e.g. 30 seconds)
if the master displays all slaves as “operational” for a shorter
time, this time can be reduced.

If the slave device fulfills all requirements from Section 7.4 ?

If a slave is displayed as operational after the master has
started up, but no data is being received, check the PDO
mapping and the assignment of the PDOs in the PLC I/O
buffer of the PLC

Check whether emergency messages are present after start-up:
CANopen
®
Debug

Emergency

Check whether an error has occurred during SDO
initialization of the slaves: CANopen
®
Debug

SDO
Abortcode
If these tips do not help, contact our support Either by phone on
+49 9135 7380-0 or by e-mail to
support@helmholz.de .
If information about their slave device is also at hand (manual),
please also send this information.
Start-up Guide CAN 300 PRO 31