Scanlab RTC 5 PC Interface Board - 10.3 Unsupported RTC2;RTC3;RTC4 Commands

RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
561
innovators for industry
10.3 Unsupported
RTC
®
2/RTC
®
3/RTC
®
4
Commands
Some RTC
®
3/RTC
®
4 commands and a few RTC
®
2
commands emulated by the RTC
®
3/RTC
®
4 are not
supported by the RTC
®
5. But most of these can be
replaced by RTC
®
5 commands. The following table
lists all unsupported commands and appropriate
RTC
®
5 replacements.
Ctrl Command aut_change
Support status This RTC
®
2 command is not supported by the RTC
®
5.
Replaced by auto_change (see page 238)
Ctrl Command dsp_start
Support status This RTC
®
2/RTC
®
3/RTC
®
4 command is not supported by the RTC
®
5.
RTC
®
4  RTC
®
5 This command is not needed for normal operation. The DSP starts automatically after the
program file is loaded via the command load_program_file (page 340).
List Command field_jump
Support status This RTC
®
2 command is not supported by the RTC
®
5.
Replaced by home_position (see page 298), the “field jump” is automatically executed.
Ctrl Command get_rtc2_mode
Support status This RTC
®
2 command is not supported by the RTC
®
5.
Replaced by The RTC
®
5 has no need to query the mode, which is now be set via the software command
set_laser_mode (see page 443) instead of hardware.
Ctrl Command get_rtc2_version
Support status This RTC
®
2 command is not supported by the RTC
®
5.
Replaced by get_rtc_version (see page 277)
Ctrl Command get_version
Support status This RTC
®
2 command is not supported by the RTC
®
5.
Replaced by get_hex_version (see page 267)
Ctrl Command get_xy_pos
Support status This RTC
®
2/RTC
®
3/RTC
®
4 command is not supported by the RTC
®
5.
RTC
®
4  RTC
®
5Replaced by get_value (see page 291)