Scanlab RTC 5 PC Interface Board Installation And Operation Manual page 437

Control set_jump_mode
Command
> 1
Notes • For information on using this command, see
• A check (also see
prior to the call and/or if the supplied tuning numbers don't match those stored on the
board. Otherwise, only the flag will be switched. For the check, the board must not be
BUSY or INTERNAL BUSY, because meanwhile the to-be-returned data type will change
and automatic laser control will be deactivated (both will get restored at the end of the
command). Depending on results of the check, different error codes will be returned
(see above). In case of error, Flag will get set to –1 (jump mode deactivated and
disabled). If the check is successful, then you can afterward (even via
set_jump_mode_list
Flag = 1 (jump mode activated, vector mode deactivated) and Flag = 0 (jump mode
deactivated, vector mode activated) without another check having to be performed.
• Use –1 as the tuning number if certain tunings shouldn't be checked (e.g. because no
intelliSCAN
for example, isn't needed in pure drilling applications) or if, after switching to jump
tuning, it isn't desirable to return to vector tuning. As a result, such tunings are neither
checked nor switched on. If the "second scan head control" option hasn't been
enabled, then the tuning numbers for the secondary scan head connector (B) will auto-
matically be set to –1 (even if others were supplied). If all tuning numbers are –1, then
Flag will be set to –1 (return value –1).
• Even after successful activation of jump mode (Flag = 1), the first servo switching only
occurs after the first subsequent 2D jump (see
then doesn't match the jump or vector tuning specified via set_jump_mode, then the
first switching can take somewhat longer (approx. 250 ms), depending on the currently
set tuning. You can determine ahead of time whether this is so by calling
set_jump_mode using the currently set tuning as a parameter. If true (return value >
1, Error code = 2), then you can achieve the desired operational sequence by calling
control_command
via set_jump_mode.
® ®
RTC 4 RTC 5 new command
Version info • Available beginning with version DLL 525
• Changed with version DLL 530, OUT 531, RBF 522: changed error code for return values
>1 (byte#1 and byte#2)
References set_jump_mode_list, load_jump_table_offset,
®
RTC 5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
Didn't pass the check (also see notes);
the following is returned:
Byte #0 = 255
Byte #1 = Error code for primary scan head connector
Byte #2 = Error code for secondary scan head connector
Byte #3 = 0
whereby Error code:
=1: X axis (galvanometer scanner 2) not responding or no intelliSCAN
®
intelliWELD or intelliDRILL
attached
=2: Y axis (galvanometer scanner 1) not responding or no intelliSCAN
®
intelliWELD or intelliDRILL
attached
=4: no correction table assigned
=8: incorrect tuning number(s): incorrect type or unsuitable for rapid switching
page 157) will only be performed if Flag = –1 (the initialization state)
during processing of a list) switch freely between the states
®
scan system is attached or specific tunings aren't available – vector tuning,
before the first 2D jump to set the tuning to one that was supplied
Flag
will be set to –1 (jump mode deactivated and disabled);
®
scan system (with software version 2078 or higher)
®
scan system (with software version 2078 or higher)
"Jump Mode", page 156.
page 156). If the currently set tuning
set_jump_table
® ®
, intellicube ,
® ®
, intellicube ,
437