STOBER 12 | Diagnostics
05/2019 | ID 442790.01
135
12.2 Events
The drive controller has a self-monitoring system that uses test rules to protect the drive system from damage. Violating
the test rules triggers a corresponding event. There is no possible way for you as the user to intervene in some events, such
as the Short/ground event. In other cases, such as the Overspeed event, you can define the triggering threshold and the
response.
Possible responses include:
§ Message: Information that can be evaluated by the controller
§ Warning: Information that can be evaluated by the controller and becomes a fault after a defined time span has
elapsed without the cause being resolved
§ Fault: Immediate drive controller response; the drive either stops applying torque/force or is brought to a stop through
a quick stop or emergency braking
Events, their causes and suitable measures are listed below. If the cause of the error is corrected, you can usually
acknowledge the error immediately. If the drive controller has to be restarted instead, a corresponding note can be found
in the measures.
12.2.1 Overview
The following table shows the possible events at a glance.
Event
Event 31: Short/ground [}137]
Event 32: Short/ground internal [}137]
Event 33: Overcurrent [}138]
Event 34: Hardware fault [}139]
Event 35: Watchdog [}139]
Event 36: High voltage [}140]
Event 37: Motor encoder [}140]
Event 38: Temperature drive controller sensor [}143]
Event 39: Overtemperature drive controller i2t [}144]
Event 40: Invalid data [}145]
Event 41: Temp.MotorTMP [}146]
Event 42: TempBrakeRes [}147]
Event 44: External fault 1 [}148]
Event 45: Overtemp.motor i2t [}149]
Event 46: Low voltage [}150]
Event 47: Torque limit [}151]
Event 50: Safety module [}152]
Event 51: Virtual master limit switch [}153]
Event 52: Communication [}154]
Event 53: Limit switch [}155]
Event 54: Following error [}156]
Event 56: Overspeed [}157]
Event 57: Runtime usage [}158]
Event 59: Overtemperature drive controller i2t [}159]