CAN bus interruption is not detected (eliminated from V3.3.2)
Corrected from:
Controller 3200 C V3.3.2
Controller p500 V3.3.2
Behaviour of the new version?
The node of the CAN slave in the device tree turns red and the bCommunication flag in the AxisRef structure turns FALSE.
What happens?
The node of the CAN slave in the device tree does not turn red and the bCommunication flag in the AxisRef structure remains TRUE.
When does the problem occur?
The responses described above occur when the CAN connection to a SoftMotion drive is interrupted. Depending on the parameterisation of the drive, uncontrolled movements may occur when the CAN connection is restored. The drive does not respond to setpoints of the control.
Which products are affected?
Controller 3200 C from V3.3
Controller p500 from V3.3
Diagnostics options?
None
Short-term measures/recommendations?
Parameterise the drive so that quick stop is initiated in the case of a telegram failure (9400 HighLine: C5902/2). In order to avoid the tripping of quick stop if a telegram failure occurs once, the 'Maximum value telegram error' (C3010/0) should be set to a value > 1 for 9400 HighLine.
Evaluation:
An interruption of the CAN communication is not detected. After the CAN communication has been restored, uncontrolled movements may occur, depending on the parameterisation of the drive.
Taxonomy:
Controller 3221 C
,
Controller 3231 C
,
Controller 3241 C
,
Controller 3251 C
,
Controller 3200 C
,
Controller p500
AKB-ID:
201208890
Last update:
2023/09/09
Category:
Versions-Informationen
Lenze reserves the right to change information on this page at any time. Any liability for the accuracy of the information is excluded.
