RTC
®
5 PC Interface Board
Rev. 1.9 e
2 Product Overview
33
Increased Parameter Resolution
When switching from the RTC
®
4 to the RTC
®
5 – even
for some commands not mentioned above – take
note that the resolution has been increased for
several parameters. Examples:
• For commands such as mark_abs or jump_rel,
the real-image-field x and y coordinate values are
specified with 20-bit resolution for the RTC
®
5
(whereas with 16-bit resolution for the RTC
®
4).
Therefore, 16 times larger parameter values must
be specified for a certain position (in mm) – also
see chapter 7.3.2, page 119. Moreover, an
extended, virtual value range – altogether a
virtual 24-bit image field – is available with the
RTC
®
5 (particularly for Processing-on-the-fly
applications) – also see chapter 7.3.3, page 120).
• For commands such as write_da_x, analog
output values are specified with 12-bit resolution
for the RTC
®
5 (whereas with 10-bit resolution for
the RTC
®
4). Therefore, a 4 times larger parameter
value must be specified for a certain output value
(in V).
• For the command set_laser_timing, output
period and pulse length are specified with 1/64 µs
resolution for the RTC
®
5 (whereas with 1/8 µs or
1 µs resolution for the RTC
®
4). Therefore,
an 8 times or 64 times larger parameter value
must be specified for a certain timing value (in
µs). For the clock frequency refer to the command
description.
• For the command set_laser_delays, the laser
delays are specified with 0.5 µs resolution for the
RTC
®
5 (whereas with 1 µs resolution for the
RTC
®
4). Therefore, a 2 times larger parameter
value must be specified for a certain delay value
(in µs).
Here, though, it generally suffices to set the
RTC
®
5DLL to RTC
®
4 compatibility mode via
set_rtc4_mode. Then the RTC
®
5 DLL automatically
converts parameter values so that many RTC
®
4
command sequences (e.g. for defining marking
patterns) can run unchanged on the RTC
®
5.
RTC
®
4 compatibility mode affects the following
RTC
®
4 commands (descriptions of the respective
commands might include relevant information under
the heading “RTC
®
4 RTC
®
5”):
• arc_abs
• arc_rel
• fly_return
• get_z_distance
• goto_xy (changed)
• goto_xyz (changed)
• home_position
• jump_abs
• jump_abs_3d
• jump_rel
• jump_rel_3d
• mark_abs
• mark_abs_3d
• mark_rel
• mark_rel_3d
• set_delay_mode
• set_ext_start_delay
• set_ext_start_delay_list
• set_firstpulse_killer
• set_firstpulse_killer_list
• set_fly_x
• set_fly_y
• set_jump_speed
• set_laser_delays
• set_mark_speed
• set_pixel (changed)
• set_pixel_line (changed)
• set_rot_center
• set_softstart_level
• set_standby
• set_standby_list
• simulate_ext_start
• timed_jump_abs (changed)
• timed_jump_rel (changed)
• timed_mark_abs (changed)
• timed_mark_rel (changed)
• write_da_1
• write_da_1_list
• write_da_2
• write_da_2_list
• write_da_x
• write_da_x_list
Nevertheless, the previously mentioned revision of
initialization and checking of unsupported or
changed RTC
®
4 commands needs to be carried out
regardless of whether the program is to execute in
RTC
®
5 mode or RTC
®
4 compatibility mode.
• timed_jump_abs changed
• timed_jump_rel changed
• timed_mark_abs changed
• timed_mark_rel changed
• z_out not supported
• z_out_list not supported
To Next Page
