RTC
®
5 PC Interface Board
Rev. 1.9 e
2 Product Overview
33
innovators for industry
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
or
,
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
. 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
, 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
, 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
, 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
®
5 DLL to RTC
®
4 compatibility mode via
. 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”):
•
•
•
•
•
(changed)
•
(changed)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
(changed)
•
(changed)
•
•
•
•
•
•
(changed)
•
(changed)
•
(changed)
•
(changed)
•
•
•
•
•
•
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.
•
changed
•
changed
•
changed
•
changed
•
not supported
•
not supported