VisualMotion 9 Troubleshooting Guide Monitoring and Diagnostics 3-25
DOK-VISMOT-VM*-09VRS**-WA02-EN-P
450 Event %d: invalid event type
Cause:
The event type selected in the event table %d (where %d = event
number) is not valid or does not match the type of motion or event. This
error is also issued if an event/trigger (event arm) is executed for a
motion-based event.
Remedy:
Make sure that the event type selected under Data ⇒
⇒⇒
⇒ Events is
consistent with the type of motion specified for the axis. Modify the
numbered event and correct the event type. Save, compile and download
the program.
451 Invalid event number ‘%d’
Cause:
The event number %d (where %d = event number) is not within the
bounds selected with the data/size command for this task.
Remedy:
1. Verify that the sizing icon contains the correct amount of events for
the program.
2. Verify that the correct event number is selected and configured from
within Data ⇒
⇒⇒
⇒ Events.
452 More than %d event timers armed
Cause:
Only %d repeating timer events (where %d = number of events) can be
armed at one time.
Remedy:
Check the program flow to make sure that triggered events are being
disabled.
453 Homing param. transfer error: %d
Cause:
A SERCOS communication error occurred during a drive-controlled
homing command. The %d indicates the communication error code
returned by the drive.
Remedy:
Try homing the axis again. If this error still occurs, call Bosch Rexroth
Service for assistance.
454 Axis %d homing not complete
Cause:
The drive did not successfully complete the homing procedures instructed
by axis %d (where %d = axis number).
Remedy:
See the drive diagnostics for a status or error message. This can be
viewed under Commission ⇒
⇒⇒
⇒ Drive Overview.
To Next Page
Loading...
