n Error handling
– The block has error outputs to show errors during job processing. ERROR indi-
cates the error, ERROR_ID shows an additional error number and
DATASET_INDEX informs at which object the error occurred.
– The output DONE designates a successful job execution and is not set when
ERROR becomes TRUE.
n Behavior of the DONE output
– The DONE output is set, when a command was successfully executed.
n Behavior of the BUSY output
– The BUSY output indicates that the function block is active.
– BUSY is immediately set with edge 0-1 of REQUEST and will not be reset until
the job was completed successfully or failed.
– As long as BUSY is TRUE, the function block must be called cyclically to execute
the command.
n Behavior of the DATASET_INDEX output
– The DATASET_INDEX output indicates, which object of the object list is currently
being processed.
– If there is no job active, DATASET_INDEX = 0 is returned.
– If there is an error during the object processing, DATASET_INDEX shows the
faulting object.
If there is again an edge 0-1 at REQUEST during the job processing, an
error is reported (ERROR_ID = 0x8075), no new command is activated
and the answer rejected by the current command!
(1) The job is started with edge 0-1 at REQUEST and BUSY becomes TRUE.
(2) At the time (2) the job is completed. BUSY has the value FALSE and DONE den
value TRUE.
(3) At the time (3) the job is completed and REQUEST becomes FALSE and thus each
output parameter FALSE respectively 0.
(4) At the time (4) with an edge 0-1 at REQUEST the job is started again and BUSY
becomes TRUE.
(5) At the time (5) an error occurs during the job. BUSY has the value FALSE and
ERROR den value TRUE.
ERROR_ID Description
0x0000 There is no Error
0x8070 Faulty parameter MODE
Status diagram
ERROR_ID
VIPA SPEED7
Device Specific
Motion Modules > FB 321 - ACYC_DS - Acyclic parametrization System SLIO motion module
HB00 | OPL_SP7 | Operation list | en | 18-30 278
To Next Page
Loading...
