RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
280
At any time, the curve can be restarted at the address
defined by set_extstartpos or set_extstartpos_list
(typically but not necessarily
FirstPos
) by an external
/START (independently of the current index, possibly
hard-jumped to the first marking position).
Notes
• An external /START during list execution is:
– Suppressed during normal operation
– Not suppressed during a Camming process
with indefinite repeating
If
Ctrl = 2
, then the Camming process waits at the
end of the point list for a new start. If
Ctrl = 3
, then
processing automatically starts again from the
beginning (the point list is processed as a ring buffer).
Furthermore, the Camming process can be combined
with Processing-on-the-fly (which can apply its own
scaling if different from camming parameter
Scale
).
The laser control can be combined with the
automatic ““vector-controlled laser control””
(set_vector_control). This requires to use
para_mark_abs[*] commands instead of
mark_abs[*] commands. The value defined there is
outputted immediately, thus allowing systematic
variation of laser power along the curve. If automatic
vector-defined laser control is not enabled, then no
laser power is outputted by the para_mark_abs[*]
commands.
In addition, a combination with Encoder-speed-
dependent laser control is possible, see Section
”Encoder-Speed-Dependent Laser Control”,
page 204.
Alternatively, mark_abs_3d or para_mark_abs_3d
as well as timed_mark_abs_3d can be used.
However, the z coordinate and
T
parameter is ignored
during outputting. Other commands within point
lists are likewise ignored.
Point output then remains unchanged for one clock
cycle.
Notes for Testing
• If a curve point list is finished by set_end_of_list
and does not cross the boundary between List 1
and List 2 (see Chapter 6.4 ”List Handling”,
page 105), then the curve shape can be tested
using a normal execution start, for example, by
execute_at_pointer( Pos )
(to some extend as a Polyline, but with a
predefined mark speed and using the currently
defined “Variable Polygon Delay”).
• The point list should be closed with list_return, if
it is part of a subroutine and a sub_call call is
used for testing.
• If the test should include the “Hard Jump”, then
timed_mark_abs_3d (with
Time
= 10 µs) can be
used as well, but not timed_para_mark_abs_3d.
To Next Page
Loading...