RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
702
Ctrl Command set_multi_mcbsp_in
Function Activates a Processing-on-the-fly application and McBSP interface multi transmission with
up to 8 different data types.
Restriction If the Option Processing-on-the-fly is not enabled, then set_multi_mcbsp_in switches off
the Processing-on-the-fly process (even if it has been never switched on).
Call
set_multi_mcbsp_in( Ctrl, P, Mode )
Parameters
Ctrl
Control parameter for initializing or deactivating laser power variation.
As an unsigned 32-bit value.
= 1…6: defines which signal parameter to vary: for a description, see
set_auto_laser_control.
= 0 or > 6: deactivates laser power variation
(for
Ctrl
> 6: get_last_error return code
RTC6_PARAM_ERROR
).
P
Initialization value for laser power. As an unsigned 32-bit value.
Allowed value range: see set_auto_laser_control.
Mode
As an unsigned 32-bit value.
= 0: The transmitted value is used directly.
= 1: The transmitted value is multiplied by
P
/16384 and then put out.
Ctrl
,
P
and
Mode
are only relevant for Type 3 (= laser power) of the transmitted data word,
see read_multi_mcbsp.
Comments • Up to V1.6.0, the following applies:
Any other already activated McBSP transmission for Online Positioning and any other
activated Processing-on-the-fly application with encoder signals or positional values is
terminated first.
As of V1.6.1, the following applies:
Processing-on-the-fly corrections are compatible with the “Fly Extension” Commands.
The Processing-on-the-fly corrections of the 3 axes are correspondingly overwritten.
They can also be overwritten later by other corrections, for example, encoder-based
Processing-on-the-fly corrections. Data types 0…2 are then not used for
Processing-on-the-fly corrections. Hence, transmission of extra parameters can be
combined even with encoder-based Processing-on-the-fly corrections. However, the
McBSP memory transfer cannot be changed.
• set_multi_mcbsp_in enables inputting by the McBSP interface of up to 8 different
types for asynchronous transmission every 10 µs. Each 10 µs, the data is copied in
accordance with its type code to separate memory, from where it can also be queried
by read_multi_mcbsp.
• To avoid faulty sorting, no active McBSP transmission should be occurring when you
call set_multi_mcbsp_in.
• 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.
To Next Page
Loading...