The CAN bus node is red or has a red exclamation mark. | See the general troubleshooting for the CAN bus. |
The CANopen Manager is red or has a red exclamation mark. | Check the status page and logger page of the CANopen Manager. You will find more information here. |
The CANopen Manager has an orange triangle. | The CANopen Manager is in the PREOPERATIONAL state. Possible causes: Not all mandatory slaves are in the OPERATIONAL state. Mark the unavailable devices in the Device Configurator as optional. The "Autostart CANopen Manager" option is not selected in the CANopen Manager configurator. You have to manually start the CANopen Manager in the application by means of the function block CiA405.NMT.
|
A slave has an orange triangle. | The slave is not in the OPERATIONAL state. The I/O communication has not started yet. You can view the current state on the status page. You can manually start the slave in the application by means of the function block CiA405.NMT. |
A slave has a red exclamation mark. | The slave has reported an emergency (for example, due to a broken cable) or configuration errors have occurred (SDO abort in the configuration phase). Check the status page and logger page of the CANopen Manager. You will find more information here. For more information about the emergency, see the manual for the slave. Possible causes of configuration errors: The EDS file does not match the device or it contains errors. Contact the manufacturer. For modular devices: The order or the type of the modules in the device tree do not match the physical construct. Perform a device scan on the CANopen Manager device and compare the configuration.
|
A slave has a gray exclamation mark. | An error occurred in the past which has been corrected in the meantime. You can check the logger page for which error this was. You can confirm the gray exclamation mark by clicking the Confirm button on the status page or the command in the context menu of the device. |
The inputs and outputs of the slave do not work. | Possible causes: The CANopen Manager might not be in the OPERATIONAL state yet (no green icon). The CANopen Manager may edit PDOs only in the OPERATIONAL state. The CANopen Manager reaches this state only when all required CANopen subscribers are in the OPERATIONAL state. Moreover, the Autostart CANopen Manager option has to be set in the CANopen Manager configurator or the CANopen Manager has to be started manually by means of the function block CiA405.NMT. The affected slave is not in the OPERATIONAL state yet (no green icon) or configuration errors have occurred (SDO abort during configuration phase). You can read possible configuration errors in the logger of the respective slave and on the status page. If the Start Slaves option in the CANopen Manager configurator is deactivated, then you have to start the slaves manually by means of the function block CiA405.NMT so that the I/O data traffic is included. If the Autostart CANopen Manager option is deactivated, then you also have to start the manager manually.
|
The analog inputs of a slave do not work. | Possible causes: For the input, no interrupt is generated in the slave. This can happen, for example, in the case of analog inputs when the associated PDO is set to transmission type "asynchronous" (254 or 255) and not Event time has been defined. Three solutions are provided for this purpose. Set the PDO to synchronous and activate Sync Producing in the CANopen Manager. Set the Event time of the PDO to values > 0 On the SDO page, insert the object 16#6423sub0 (analog input global interrupt enable) and set the value to 1
|
A slave quits sporadically (turns red and then green again). | Possible causes: There are cycle time outliers in the bus cycle task. In the task monitor, check the minimum and maximum time of the bus cycle task. In the application, search for application code which produces these cycle time outliers: Optimize the code or move it to another task.
A handle leak was caused by a faulty driver or incorrect usage of the CL2 layer. A physical error exists. See troubleshooting for CAN-based fieldbuses.
|