EasyManua.ls Logo

Scanlab RTC6 PCIe Board - Page 912

Scanlab RTC6 PCIe Board
1004 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
RTC6 boards
Doc. Rev. 1.0.21 en-US
16 Appendix A: The RTC6 Ethernet Board
912
innovators for industry
16.7.5 Control Commands Allowed
for Automatic Booting
Only certain control commands are allowed in
each boot phase, see table 8 and Chapter 16.7.6
”Automatic Booting – Process in Detail”,
page 914:
Boot Phase 1
Boot Phase 2
They meet one or more of the following criteria:
Requires no communication with the PC
Does not send a response to the PC
There is no corresponding list command
Exceptions are, for example,
set_free_variable, see Comments there
set_auto_laser_control or
set_scanahead_params
They check the connected scan systems at
point in time of the call
They save exclusively the parameters to be
finally set only in case of success
set_jump_mode only sets the tuning numbers
VA1
JB2
during automatic booting and does
not check whether they match the scan system.
The table containing the Jump Delay values
[JumpTable<No>]
, see page 219 and
load_jump_table_offset, must have been
previously saved via create_dat_file.
Upon (later) automatic booting, the connected
scan systems are not checked anymore!
Boot Phase 2-control commands are control
commands which:
Necessarily need to be executed after a
Boot Phase 1-control command
Require functioning peripherals, for example,
an iDRIVE scan system
(1)
with “Automatic Laser
Control“. Important: users must make sure
themselves that the periphery is actually
working at runtime
(1) See Glossary entry on page 27.

Table of Contents