Scanlab RTC6 PCIe Board - Page 691

RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
691
innovators for industry
Comments
(cont’d)
• For deactivating Processing-on-the-fly correction, see Chapter 8.6.5 ”Deactivating
Processing-on-the-fly Correction”, page 251.
• 15 bits per axis (with sign) are effectively available for 2D correction ( Mode = 3),
whereby the x value is in the lower 16 bits of the “Bit #31 = 0”-coded McBSP input
value and the y value in the upper 16 bits.
• The McBSP interface cannot be simultaneously used for both Processing-on-the-fly
applications and Online Positioning.
See also Section ”Notes”, page 230.
• The McBSP interface ignores the first FrameSync signal after a load_program_file or
mcbsp_init. That is, data provided is not transmitted, see page 86.
• If Mode > 5, set_mcbsp_in is not executed (get_last_error return code
RTC6_PARAM_ERROR ).
• If an unallowed Scale parameter value is supplied (for example, Scale = 0),
set_mcbsp_in behaves as with Mode = 0.
• Processing-on-the-fly corrections are compatible with the settings from Chapter 8.6.12
”“Fly Extension” Commands”, page 259 as of RTC6 Software Package V1.6.1. They can
also be subsequently overwritten, for example, with encoder-based
Processing-on-the-fly corrections. The McBSP values are then not used for
Processing-on-the-fly corrections. However, the McBSP memory transfer described
above cannot be changed. If McBSP-based Processing-on-the-fly corrections other
than those set according to the Mode are set, the user is responsible for transferring the
McBSP data in the appropriate format. An encoder-based Processing-on-the-fly
correction activated for the z axis is retained.
RTC4RTC6 New command.
RTC5RTC6 Unchanged functionality.
Version info Last change DLL 617, OUT 617: compatibility with “Fly Extension” Commands.
References set_mcbsp_in_list
Ctrl Command set_mcbsp_in