10.3 Unsupported
®
®
RTC
2/RTC
3/RTC
Commands
®
®
Some RTC
3/RTC
4 commands and a few RTC
commands emulated by the RTC
®
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
Replaced by
auto_change (see page 238)
Ctrl Command dsp_start
Support status
This RTC
®
®
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
List Command field_jump
Support status
This RTC
Replaced by
home_position (see page
Ctrl Command get_rtc2_mode
Support status
This RTC
®
Replaced by
The RTC
set_laser_mode (see page 443)
Ctrl Command get_rtc2_version
Support status
This RTC
Replaced by
get_rtc_version (see page 277)
Ctrl Command get_version
Support status
This RTC
Replaced by
get_hex_version (see page 267)
Ctrl Command get_xy_pos
Support status
This RTC
®
®
RTC
4 RTC
5 Replaced by
®
RTC
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
®
4
®
2
®
®
3/RTC
4 are not
®
2 command is not supported by the RTC
®
®
®
2/RTC
3/RTC
4 command is not supported by the RTC
®
2 command is not supported by the RTC
298), the "field jump" is automatically executed.
®
2 command is not supported by the RTC
5 has no need to query the mode, which is now be set via the software command
instead of hardware.
®
2 command is not supported by the RTC
®
2 command is not supported by the RTC
®
®
®
2/RTC
3/RTC
4 command is not supported by the RTC
get_value (see page 291)
®
5.
®
5.
load_program_file (page
340).
®
5.
®
5.
®
5.
®
5.
®
5.
561
Need help?
Do you have a question about the RTC 5 PC Interface Board and is the answer not in the manual?