Kollmorgen BDS5, Инструкция по установке и настройке

Страница: 123 / 150

BDS5 A
PPENDIX
C - E
RROR
C
ODES
C-7
You attempted to make an absolute move (either MA or MCA) beyond PROTARY. For example, if PROTARY is
1000 and you typed:
MA 2000
Use incremental moves (MI and MCI) if you want to move beyond the rotary limit. This error breaks execution if
the instruction was issued from the program.
ERROR 61 "NORMALIZE FIRST" SEVERITY 2
You attempted to turn on the Rotary mode when PFB was less than zero or greater than PROTARY. Use the NORM
command to normalize the position to between 0 and PROTARY. This error breaks execution if the instruction was
issued from the program.
ERROR 62 "RD ALREADY IN USE" SEVERITY 2
You attempted to execute RD when RD was in use from some other task. This error occurs when two task levels
attempt to simultaneously use the RD command. This error breaks program execution.
ERROR 63 "NOT AT THIS LEVEL" SEVERITY 2
You attempted to execute a command that is not allowed at the present task level. For example, GOSUB and GOTO
are not allowed from within an alarm. This error breaks program execution.
ERROR 64 "BACKWARD REGULATION" SEVERITY 3
The external input counted backwards more than 30,000 counts when REG was on. This error breaks program
execution and disables the BDS5.
ERROR 65 "RECORD NOT READY" SEVERITY 3
You entered a PLAY command when nothing had been recorded since the last time the BDS5 powered up.
C.4.2 Improper Use of Labels
ERROR 70 "LABEL NOT FOUND" SEVERITY 2
You attempted to branch to a label (either from RUN, GOSUB, or GOTO) that does not exist. This error breaks
program execution.
ERROR 71 "LABEL USED TWICE" SEVERITY 2
The user program has a label that is used more than once. This error breaks program execution.
ERROR 74 "ERROR$ MUST BE LAST" SEVERITY 2
The user's error (ERROR$) must be the last label in the program buffer. You cannot have labels after ERROR$, nor
can you use the GOTO or GOSUB commands when the BDS5 is executing the error handler. The error handler is
intended to provide a graceful exit during error conditions and cannot be used to restart the program. You can use
the IF, TIL, and ? commands to execute conditional commands in the error handler. This error breaks program
execution.