Ctrl Command get_marking_info
Comments
• For usage of this command and of the error bits#0...7, see
• The boundary limits Xmin, Xmax, Ymin, Ymax for the customer-defined monitoring area
(bits#4...7) can be specified via the command set_fly_limits.
• Encoder-signal spacing could be too short if interfering signals are present, a rapid
directional change occurs or the frequency is essentially too high.
• An improper encoder signal sequence occurs if both signals 1 and 2 change simulta-
neously, thus hindering determination of the counting direction.
• If no external encoder is used, the corresponding inputs on the MARKING ON THE FLY
connector have undefined signal levels. Therefore signal errors may be permanently
detected for these inputs (upper 16 bit of the return value), even if simulated encoders
are used. If this will disturb the application, then this pins should be set to a defined
signal level via pull-up resistors.
• The error bits#10...15 and 26...31 are only set in case of an error if laser-signal auto-
suppression has been activated (see
Auto-Suppression" on page
to an error-indicating status signal are (cumulatively) set. If applicable, even error bits
are set, which have not been selected to be used for laser-signal auto-suppression via
set_laser_control. All error bits will be reset via get_marking_info.
• The boundary limits Zmin, Zmax for the customer-defined monitoring area
(bits#24...25) can be specified via the command set_fly_limits_z.
• All Error bits are reset during initialization (via load_program_file).
• Error bits #22...23 are also reset by get_marking_info. Error bits #24...25 are not
reset by get_marking_info. If applicable, error bits #24...25 get implicitly reset by the
conditional commands. They can also be explicitly reset via the command
clear_fly_overflow.
®
®
RTC
4 RTC
5 unchanged functionality for info bits that are also used on the RTC
Version info
Last changes:
• with version DLL 525, OUT 527 (Bit #4...7)
• with version DLL 527, OUT 529, RBF 519 (Bit #10...15 and 26...31)
• with version DLL 531, OUT 532 (Bit #22...25)
• with version DLL 536, OUT 536 (Bit #9)
References
set_fly_x, set_fly_y, set_fly_rot, set_fly_x_pos, set_fly_y_pos, set_fly_rot_pos,
set_fly_limits, set_fly_limits_z, clear_fly_overflow,
®
RTC
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
section "Scan-System-Error-Induced Laser-Signal
130). Any time an error occurs, all error bits corresponding
if_not_activated
page
190.
®
4
274
Need help?
Do you have a question about the RTC 5 PC Interface Board and is the answer not in the manual?