EasyManua.ls Logo

Scanlab RTC 5 PC Interface Board - wait_for_encoder_mode

Scanlab RTC 5 PC Interface Board
622 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...
RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
555
innovators for industry
Normal
List Command
wait_for_encoder_mode
Function waits until the selected encoder counter has overstepped or understepped the specified
count for the first time.
Call
wait_for_encoder_mode( Value, EncoderNo, Mode )
Parameters
Value
Count as a signed 32-bit value; allowed range: [–2
31
…+(2
31
–1)]
EncoderNo
Number of the to-be-used encoder counter as an unsigned 32-bit value,
allowed values:
= 0: Encoder counter Encoder0
= 1: Encoder counter Encoder1
Mode
signed 32-bit value:
= 0: waits for understepping/overstepping (position dependent)
> 0: waits for overstepping (position independent)
< 0: waits for understepping (position independent)
Comments For usage of this command, see "Synchronization via Encoder Signals", page 215.
•For
Mode
= 0, ensure that the size and sign of the parameter
Value
is appropriate for
the counting direction of the selected encoder (for external triggering, this corresponds
to the workpiece’s direction of motion). If
Value
> 0, the command waits for overstep-
ping, otherwise for understepping. If
Value
is positive and already less than the current
encoder count, then the command waits for a complete traversal of the counter (like-
wise if
Value
is negative and larger than the current encoder count). At a 1 MHz counter
rate, this can take up to approx. 36 minutes!
•If
Mode
<> 0, then the command waits for overstepping/understepping of the
Value
parameter independently of the current position and direction of motion.
•If
EncoderNo
> 1, then wait_for_encoder_mode will be replaced with a list_nop
(get_last_error return code
RTC5_PARAM_ERROR
).
If no encoder-based Processing-on-the-fly correction is active, then the command
merely creates a waiting period (without galvanometer scanner motion) that allows
implementation of an externally triggered synchronization (as an alternative to external
starts, set_wait or if_cond, etc.).
The command is available even if the Processing-on-the-fly option is not enabled.
•For
Mode
= 0, the command is synonymous with wait_for_encoder.
The command doesn’t alter the laser control signals. If you want the laser off during
the wait, then this command must be preceded by some other command that switches
off the “laser active” laser control signals (e.g. a list_nop).
The active Processing-on-the-fly mode determines whether the galvanometer scanners
remain stationary during the wait or move in accordance with encoder changes (see
page 188): They move with set_fly_2d, but otherwise remain stationary.
RTC
®
4
RTC
®
5 new command
References get_encoder, store_encoder, read_encoder, simulate_encoder, wait_for_encoder,
wait_for_encoder_in_range, park_position, park_return

Table of Contents

Related product manuals