Bosch 6000 User's Guide Page 251

  • Download
  • Add to my manuals
  • Print
  • Page
    / 268
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 250
236
6000 Series Programmer's Guide
Error Messages
Depending on the error level setting (set with the ERRLVL command), when a programming
error is created, the 6000 controller will respond with an error message and/or an error prompt.
A list of all possible error messages is provided in a table below. The default error prompt is
a question mark (?), but you can change it with the ERRBAD command if you wish.
At error level 4 (ERRLVL4—the factory default setting) the 6000 controller responds with
both the error message and the error prompt. At error level 3 (ERRLVL3), the 6000 controller
responds with only the error prompt.
Error Response Possible Cause
ACCESS DENIED Program security feature enabled, but program access input (INFNCi-Q) not activated
ALREADY DEFINED FOR THUMBWHEELS Attempting to assign an I/O function to an I/O that is already defined as a thumbwheel I/O
AXES NOT READY Compiled Profile (includes contouring) path compilation error
COMMAND NOT IMPLEMENTED Command is not applicable to the 6000 Series product
ERROR: MOTION ENDS IN NON-ZERO
VELOCITY - AXIS
n
Compiled Motion: The last GOBUF segment within a PLOOP/PLN loop does not end at zero
velocity, or there is no final GOBUF segment placed outside the loop.
EXCESSIVE PATH RADIUS DIFFERENCE Contouring path compilation error
FOLMAS NOT SPECIFIED No FOLMAS for the axis is currently specified. It will occur if FMCNEW, FSHFC, or FSHFD
commands are executed and no FOLMAS command was executed, or FOLMASØ was
executed.
INCORRECT AXIS Axis specified is incorrect
INCORRECT DATA Incorrect command syntax.
Following: Velocity (V), acceleration (A), or deceleration (AD) command is zero. (used by
FSHFC & FSHFD)
INSUFFICIENT MEMORY Not enough memory for the user program or compiled profile segments. See memory
allocation guidelines on page 12.
INVALID COMMAND Command is invalid because of existing conditions
INVALID CONDITIONS FOR COMMAND System not ready for command (e.g., LN command issued before the L command).
Following (these conditions can cause an error during Following):
FOLMD command value is too small to achieve the preset distance and still remain
within the FOLRN/FOLRD ratio.
A command phase shift cannot be performed:
FSHFD......... Error if already shifting or performing other time based move.
FSHFC......... Error if currently executing a FSHFD move, or if currently executing
another FSHFC move in the opposite direction.
The FOLEN1 command was given while a profile was suspended by a GOWHEN.
INVALID CONDITIONS FOR S_CURVE
ACCELERATION—FIELD
n
Average (A
avg
) acceleration or deceleration command (e.g., AA, ADA, HOMAA, HOMADA,
etc.) with a range that violates the equation 1/2A
max
A
avg
A
max
. (A
max
is the maximum
accel or decel command—e.g., A, AD, HOMA, HOMAD, etc.)
INVALID DATA Data for a command is out of range
Following (these conditions can cause an error during Following):
The parameter supplied with these commands is invalid:
FFILT......... Error if: smooth number is not 0-4
FMCLEN....... Error if: master steps > 999999999 or negative
FMCP............ Error if: master steps > 999999999 or <-999999999
FOLMD......... Error if: master steps > 999999999 or negative
FOLRD......... Error if: master steps > 999999999 or negative
FOLRN......... Error if: slave steps>999999999 or negative
FSHFC......... Error if: number is not 0-3
FSHFD......... Error if: slave steps>999999999 or <-999999999
GOWHEN....... Error if: position > 999999999 or <-999999999
WAIT............ Error if: position > 999999999 or <-999999999
Error if a GO command is given in the preset positioning mode (MCØ) and:
FOLRN = zero
FOLMD = zero, or too small (see
Preset Moves
on page 200)
Page view 250
1 2 ... 246 247 248 249 250 251 252 253 254 255 256 ... 267 268

Comments to this Manuals

No comments