EasyManua.ls Logo

REXROTH VisualMotion 9 - 547 Task %C Coordinated Articulation Error, See Ext. Diag; 548 Invalid Kinematic Number: %D; 549 Fieldbus Initialization Error; 550 User Initialization Task Timeout

REXROTH VisualMotion 9
96 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
3-46 Monitoring and Diagnostics VisualMotion 9 Troubleshooting Guide
DOK-VISMOT-VM*-09VRS**-WA02-EN-P
547 Task %c Coordinated Articulation Error, see ext. diag.
Cause:
This error is issued by runtime code during firmware initialization for task
%c (where %c = task letter). Refer to the extended diagnostics in Table
3-16 for details. Extended diagnostics can be viewed by selecting
Diagnostics
System in VisualMotion Toolkit.
Remedy:
Refer to the extended diagnostics for details. Extended diagnostics can
be viewed by selecting Diagnostics
System in VisualMotion Toolkit.
Extended Diagnostic C-0-0124 Description
Invalid % Axis
Minimum/Maximum Limits
The Max limit is not greater than the Min limit
% Axis Target Position Exceeds
Minimum/Maximum Limit
The commanded synchronized move or the manual
mode commanded move is outside the defined axis
limits
Invalid ELS Group ID Number:
%d
The selected ELS group ID is not in the range 1 to 8
Invalid CAM ID Number: %d The CAM ID is either not in range 1 to 40 or the
CAM has not been defined
Invalid Axis Number: %d The axis is not found in the SERCOS ring
Table 3-16: Coordinated Articulation Error Extended Diagnostics
548 Invalid Kinematic Number: %d
Cause:
The selected kinematic ID number (%d) is not within the existing
kinematic table size.
549 Fieldbus Initialization Error
Cause:
A problem has occurred during Fieldbus initialization.
Remedy:
If this error occurs, contact Bosch Rexroth Service for assistance.
Reference the three-digit diagnostic message in the error code displayed
under menu selection Diagnostic
System.
550 User Initialization Task Timeout
Cause:
Task could not be completed before the 300 seconds (5 mins.) timeout.
Remedy:
Return to parameter mode and review your program to determine why the
task requires longer than 300 seconds to run.

Table of Contents

Related product manuals