3-30 Monitoring and Diagnostics VisualMotion 9 Troubleshooting Guide
DOK-VISMOT-VM*-09VRS**-WA02-EN-P
486 SERCOS Device %d is not a drive
Cause:
The SERCOS device %d (where %d = SERCOS address) was enabled in
the user program or parameterized as an axis, but an I/O slave or other
type of slave was detected.
Remedy:
Check the VisualMotion program for any instances where the device (not
a drive, but maybe an I/O station) number is being configured as a drive
and modify the program accordingly. Once corrected, Save, Compile and
Download the modified program.
487 Cam %d is invalid or not stored
Cause:
In the CAM/activate command, the selected CAM %d (where %d = CAM
number) is not stored on the control’s memory or does not contain valid
data.
Remedy:
Check the variable or constant that selects the CAM. Check that there is
a valid CAM with index %d stored on the control.
488 Cam Error: See Task %c diag.
Cause:
An error was issued during a CAM command in task %c (where %c =
task letter).
Remedy:
Refer to the task diagnostic message (T-0-0122) for a description. See
also the extended message under Diagnostics ⇒
⇒⇒
⇒ Tasks for additional
information.
489 More than %d cam axes selected
Cause:
The control limits the number of axes configured as control Cam Axes.
The maximum number of control CAMs allowed on the control’s memory
is 40. The maximum number of control CAMs running in the program is
4.
Remedy:
Check the program and modify it so that the number of control CAMs
running is less than the number specified in this diagnostic message.