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

without correction
LOff Delay1
LOn LOn
Delay1 Delay2
Mark
Delay1
Mark
Mark
Command2
Command1
Other Command
(jump_rel, list_nop, ...)
with automatic correction
LOff Delay1
Laser
LOn
Delay1
Mark
Delay1
Mark Mark
Command2
Command1
scanner delay is
Other Command
automatically inserted
(jump_rel, list_nop, ...)
Automatic adjustment of the scanner delays for large LaserOn
delays
Similarly, overlaps would occur for very large
LaserOff delays set for the beginning of a non-
mark command and extending across the next
mark command up to yet another non-mark
command. Here, the laser wouldn't switch off
between the two mark commands and instead
only switch off after the second non-mark
command and only after expiration of the
LaserOn delay (see figure
ation, a check is performed at the start of a mark
command to determine if the laser would have
already switched off prior to the end of the
command. If not, then the mark command will
get postponed by an appropriate scanner delay.
On the other hand, laser switch-off during polyg-
onal traversal with sharp corners (edgelevel
parameter) will only occur if the laser was already
on during this polygonal traversal (i.e. when all
previously initiated LaserOn delays have already
expired and no LaserOff delays remains active).
®
RTC 5 PC Interface Board
Rev. 1.9 e
7 Basic Functions for Scan Head and Laser Control
Laser
laser does not
switch on
for marking 1
Laser
LOn
Delay2
39
40). To prevent this situ-
without correction
LOff Delay1
Laser
LOn LOn
Delay1 Delay2
Mark
Delay1
Mark
Mark
Command2
Command1
Other Command
(jump_rel, list_nop, ...)
with automatic correction
LOff Delay1
Laser
LOn LOn
Delay1 Delay2
Mark
Delay1
Mark
Mark
Command2
Command1
Other Command
(jump_rel, list_nop, ...)
Automatic adjustment of the scanner delays for large LaserOff
delays
Notes
• The above description applies to firmware files
(RTC5RBF.rbf) where version > 509 (see
get_rtc_version). Discontinue using earlier
firmware versions, because in the above example
the laser would get switched off for the first mark
command, but not for the second one. Likewise,
the laser would get switched off for the first - but
not the second - non-mark command and
sometimes not for set_end_of_list.
• Thanks to these previously described automatic
®
adjustments, the RTC 5 always fulfills the
scanner delay conditions (markD>LOffD – LOnD,
edgelevel>LOffD – LOnD,
polygonD+LOnD>LOffD) at run-time that had to
be explicitly observed with the RTC
• Automatic adjustment of the scanner delays
might result in a total marking time longer than
that expected from just adding-up the predefined
vector lengths and delays.
LOff Delay2
Mark
Delay2
laser does not
switch off after
marking 1
LOff Delay2
Laser
Mark
Delay2
Other Command
scanner delay is
automatically inserted
40
®
4.
109