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

Ctrl Command auto_cal
the following values are only returned after Command = 4:
100
200
19
29
91
92
99
255
Comments • For information on using the command, see
• At the end of this command's execution, the RTC
scanners back to the position held prior to the call, possibly with corrections attribut-
able to changed gain and offset values.
• During determination of the current Home-In positions with auto_cal(Command = 0, 1
or 3), the current gain and offset corrections of the galvanometer scanners are not
taken into account; neither are any head corrections or the current positions of the
scanners.
• After first-time or renewed connecting a scan system, a reference value determination
should be performed via auto_cal(Command = 0). Otherwise, the RTC
stored reference values of a previously operated (possibly different) scan system when
later performing an automatic self-calibration.
• After initialization of the RTC
= 1.0, offset = 0). However, previously determined reference values are still available.
• If no appropriate Home-In reference values were stored or the scan system is not
equipped with Home-In sensors, then the measurement routine for auto_cal(Command
= 1) (axis-specific) will automatically abort and restore the prior state.
• If the values for HeadNo or Command are invalid, then auto_cal will not be executed
(return value 6,
HeadNo = 2 if the "second scan head control" option has not been enabled (return value
6).
• The auto_cal command will likewise not be executed (return value 3,
return code: RTC5_BUSY) if the board's BUSY status is currently set (list is being proc-
essed or has been halted via pause_list) or the board's INTERNAL-BUSY status is
currently set. In contrast, the command is executed when a list has been paused via
set_wait
therefore return codes RTC5_BUSY and RTC5_PARAM_ERROR will not arrive simulta-
neously.
• For Command = 0, 1 or 2, a valid correction table must be loaded and assigned. Other-
wise, unexpected jumps can occur when gain/offset values are updated.
• Gain and offset correction can also be directly set via
Home-In sensors).
• Reference values determined and stored via auto_cal(Command = 0, 1 or 3) can be
queried via get_hi_pos.
®
RTC 5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
for both axes: a sensor system of type1 is included and is functioning
for both axes: a sensor system of type2 is included and is functioning
X axis (galvanometer scanner 2): a sensor system of type1 is included and is functioning
Y axis (galvanometer scanner 1): sensor system is defective
X axis (galvanometer scanner 2): a sensor system of type2 is included and is functioning
Y axis (galvanometer scanner 1): sensor system is defective
X axis (galvanometer scanner 2): sensor system is defective
Y axis (galvanometer scanner 1): a sensor system of type1 is included and is functioning
X axis (galvanometer scanner 2): sensor system is defective
Y axis (galvanometer scanner 1): a sensor system of type2 is included and is functioning
for both axes: sensor system is defective
for both axes: there is no sensor system included in the scan system
®
5, or after a reset, drift compensation is turned off (gain
get_last_error return code: RTC5_PARAM_ERROR). This also applies for
(PAUSED status set). For RTC5_PARAM_ERROR, the BUSY status is not checked;
"Automatic Self-Calibration", page
®
5 always moves the galvanometer
®
5 will use the
get_last_error
set_hi (even for systems without
199.
237