RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
307
Comments • Also observe "Board Acquisition by an Application", page 86.
•The init_rtc5_dll command is also available without explicit access rights to any partic-
ular RTC
®
5 board.
• init_rtc5_dll is not available as a multi-board command.
• After initialization of the DLL with init_rtc5_dll, you can additionally select between
two DLL operational modes (see set_rtc4_mode, page 473 and set_rtc5_mode,
page 473). The default is the RTC
®
5 mode.
•The init_rtc5_dll command does not cause a reset of the RTC
®
5 board. Board resets
can only be initiated via the command load_program_file, page 340.
RTC
®
4
RTC
®
5 new command
Normal
List Command
jump_abs
Function moves the output point (of the laser focus) along a 2D vector at jump speed from the
current position to the specified position (absolute coordinate values) within a two-
dimensional image field.
Call
jump_abs( X, Y )
Parameters
X, Y
absolute coordinates of the jump vector end point in bits as signed 32-bit
values; allowed range: [–8388608 … 8388607] (out-of-range values will be
edge-clipped). The complete value range [–8388608 … 8388607] is only
usable as a virtual image field e.g. for (enabled) Processing-on-the-fly
applications. The current coordinates will be clipped to [–524288 … 524287]
(real image field size) during runtime directly prior to use of the correction
table.
Comments • If the jump speed has not been previously explicitly set via set_jump_speed or
set_jump_speed_ctrl, then the jump will be executed at a predefined jump speed of
10000 bits per ms.
• The “laser active” laser control signals are off during the jump (if necessary, they will be
switched off before the jump).
• After a jump command, a (variable) jump delay is inserted. Exception: a zero-length
jump vector’s subsequent (variable) jump delay will not be executed. However, the
command itself still requires a 10 µs clock cycle for execution.
• During the conversion of specified coordinate values into scan system output values,
any previously defined coordinate transformations, assigned correction tables etc. are
taken into account after successful microvectorization (see page 126). As of version
DLL 520, OUT 519, coordinate transformation settings that were only collected until
then will possibly take effect via jump_abs (see page 163,
at_once
= 2).
RTC
®
4
RTC
®
5 unchanged functionality (except for the extended range of values).
In RTC
®
4 compatibility mode, the RTC
®
5 multiplies the specified coordinate values by 16
(the permissible range of values is correspondingly reduced).
Version info Last change with version DLL 520, OUT 519: behavior for coordinate transformations with
at_once
= 2 (see page 612)
References set_jump_speed, set_scanner_delays, jump_rel, timed_jump_abs, goto_xy
Ctrl Command init_rtc5_dll
To Next Page
Loading...
