RTC6 boards
Doc. Rev. 1.0.21 en-US
7 Basic Functions for Scan Head Control and Laser Control
182
Clock Overruns
The 10 µs clock cycle might not always suffice for
calculating all data required by the computation-
intensive Jump Commands, Mark Commands and
Arc Commands if several of the available command
options are utilized simultaneously – for example,
simultaneous control of two scan systems, wobbel
motion, coordinate transformation in the virtual
Image Field, Processing-on-the-fly for two axes
(correction by McBSP interface), “Automatic Laser
Control“, para vectors, data recording, “Variable
Polygon Delay”, short list commands (for example, in
a Polyline), control commands during list execution.
This overrun situation can be internally detected and
counted. You can appropriately test your
user program by using get_overrun to count the
number of overruns. Such overruns result in one or
several peripheral ports not being accessible during
the current 10 µs clock cycle, possibly including
output to the scan head. The galvanometer scanner
motion might also could pause for 10 µs.