innovators for industry

Optimizing the Delays

The following figures show the various effects of
non-optimized delays on the letters “RTC“.

LaserOn Delay too short Mark Mark Mark M

k ark
ar

Ma
At the beginning of a mark vector M Jump

rk Mark
the laser is switched on, even

k
M ar
Mark
though the mirrors have not yet

Mark
Mark
reached the necessary angular

M ar
p
Ma

Jum
Jum
velocity.

rk

k
p
Burn-in effects at the start points M
ar Jump
k ark
of the respective vectors result. Mark M
p
Jum

LaserOn Delay too long Mark Mark Mark M

k ark
ar
The laser is turned on too late at Ma
M Jump
rk Mark
the beginning of a mark vector.

k
M ar
Mark

Mark
The first part of the vector is not
Mark

marked.

M ar
p
Ma

Jum
Jum
rk

k
p

M
ar Jump
k ark
Mark M
p
Jum

LaserOff Delay too short Mark Mark Mark M

k ark
ar
Ma

The laser is turned off after the M Jump

rk Mark

last mark command of a line or

k
M ar

Mark
polyline, although the mirrors
Mark
Mark

have not yet reached the end

M ar
p
Ma

Jum
Jum

position of the vectors.

rk

k
p

The respective vectors are not M

ar Jump
k ark
marked completely. Mark M
p
Jum

LaserOff Delay too long Mark Mark Mark M

k ark
ar
Ma

The laser is turned off too late M Jump

rk Mark

after the last mark command of a

k
M ar

Mark
line or polyline. The laser is still
Mark
Mark

on, even though the mirrors have

M ar
p
Ma

Jum
Jum

already stopped or move only

rk

k
p

very slowly. M Jump

ar
k ark
The results are burn-in effects at Mark M
p
the end points of the respective Jum
vectors.

RTC®5 PC Interface Board 110

Rev. 1.9 e
7 Basic Functions for Scan Head and Laser Control
 innovators for industry

Jump Delay too short Mark Mark Mark M

k ark
ar

Ma
After a jump, the first mark vector M Jump

rk Mark
has already started although the

k
M ar
Mark
scanners have not yet settled.

Mark
Mark
A running-in oscillation

M ar
p
Ma

Jum
Jum
(overshoot) will be visible.

rk

k
p
M
ar Jump
k ark
Mark M
p
Jum

Jump Delay too long

There are no visible effects if the
jump delay is too long. However,
the scanning time will be
extended.

Mark Delay too short Mark Mark Mark M

k ark
ar
Ma

Though the mirrors have not yet M Jump

rk Mark

reached the end position of the

k
M ar
Mark
last vector of a line or polyline,
Mark
Mark

the command for the succeeding M ar

p
Ma

Ju m
Jum

jump vector is already executing.

rk

k
p

The end of the mark vector is M

ar Jump
k ark
turned towards the direction of Mark M
p
the jump vector. Jum

Mark Delay too long

There are no visible effects if the
mark delay is too long, but the
scanning time will be increased.

RTC®5 PC Interface Board 111

Rev. 1.9 e
7 Basic Functions for Scan Head and Laser Control
 innovators for industry

Polygon Delay too short Mark Mark Mark M

k ark
ar

Ma
The subsequent mark command M Jump

rk Mark
in a polyline is already executing,

k
M ar
Mark
although the mirrors have not yet

Mark
Mark
reached the end position of the

M ar
p
Ma

Jum
Jum
preceding mark vector.

rk

k
p
The corners of the polyline are M
ar Jump
k ark
rounded off. Mark M
p
Jum

Polygon Delay too long Mark Mark Mark M

k ark
ar

Ma
If the polygon delay is too M Jump

rk Mark
long, the mirrors are moving

k
M ar
Mark
too slowly or are even

Mark
Mark

stopping between subse-

M ar
p
Ma

Jum
Jum
quent mark commands.
rk

k
p
Since the laser is not turned M
ar Jump
k ark
off between these vectors, Mark M
p
burn-in effects occur. Jum

In the variable polygon delay

mode, a maximum length
(“edgelevel“) can be defined.
See page 104 for details.

RTC®5 PC Interface Board 112

Rev. 1.9 e
7 Basic Functions for Scan Head and Laser Control