Stober PS6 Series, Руководство пользователя

Страница: 181 / 264

STOBER 13 | Diagnostics
02/2019 | ID 442728.05
181
13.3 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 event Short/ground. In other cases,
such as event Overspeed, 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.
13.3.1 Overview
The following table shows the possible events at a glance.
Event
Event 31: Short/ground [ } 183]
Event 32: Short/ground internal [
}
183]
Event 33: Overcurrent [
}
184]
Event 34: Hardware fault [ } 185]
Event 35: Watchdog [
}
185]
Event 36: High voltage [ } 186]
Event 37: Motor encoder [
}
186]
Event 38: Temperature drive controller sensor [
}
189]
Event 39: Overtemperature drive controller i2t [ } 190]
Event 40: Invalid data [
}
191]
Event 41: Temp.MotorTMP [ } 192]
Event 44: External fault 1 [
}
193]
Event 45: Overtemp.motor i2t [
}
194]
Event 46: Low voltage [ } 195]
Event 47: Torque limit [
}
196]
Event 50: Safety module [ } 197]
Event 51: Virtual master limit switch [
}
198]
Event 52: Communication [ } 199]
Event 53: Limit switch [
}
200]
Event 54: Following error [
}
201]
Event 56: Overspeed [ } 202]
Event 57: Runtime usage [
}
203]