EasyManua.ls Logo

Scanlab RTC6 PCIe Board - Page 575

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
10 RTC6 Commands
575
innovators for industry
Undelayed
Short List
Command
range_checking
Function Defines an emergency action, if a galvanometer scanner exceeds its position limit.
Call
range_checking( HeadNo, Mode, Data )
Parameters
HeadNo
The scan system to be monitored.
As an unsigned 32-bit value.
0: No monitoring
(default after load_program_file).
1: First scan head is monitored.
2: Second scan head is monitored.
3: Both scan heads are monitored.
Only the 2 least significant bits are evaluated.
Mode
Action to take.
As an unsigned 32-bit value.
0: The Signals for “Laser Active” Operation are suppressed
immediately. List execution continues.
1: The Signals for “Laser Active” Operation are switched-off
immediately. List execution is stopped immediately
(as with stop_execution or
/STOP
).
2: A simulate_ext_stop is passed on to all slave boards.
Data
Data type chosen to be monitored.
As an unsigned 32-bit value.
0: Sample values.
Like set_trigger signal types 7…9.
1: Transformed control values.
Like set_trigger signal types 25…30.
2: Corrected control values.
Like set_trigger signal types 10…15.
3: Actual output values.
Like set_trigger signal types 20…23.
4: Actual galvanometer scanner position (only with iDRIVE
systems, varioSCAN is internally connected to an x axis).
Like set_trigger signal types [1, 2 and 4] or [4, 5 and 1].
5: Actual galvanometer scanner position (only with iDRIVE
systems, varioSCAN is internally connected to a y axis).
Like set_trigger signal types [1, 2 and 5] or [4, 5 and 2].
Comments No monitoring takes place if the specified scan head does not have a correction table
assigned (see select_cor_table).

Table of Contents