RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
275
Ctrl Command get_master_slave
Function returns the master/slave status of the addressed RTC
®
5 board.
Call
MasterSlaveStatus = get_master_slave()
Result Master/slave status as an unsigned 32-bit value, i.e.
information, whether a further RTC
®
5 board is connected to the MASTER or SLAVE
connector of the addressed RTC
®
5 board:
Bit #0 (LSB) = 1: A board is connected to the SLAVE connector.
Bit #1 = 1: A board is connected to the MASTER connector.
Bit #2-31 = 0
and information, whether the addressed board is operated as a master, slave or single
board:
= 0 The board is operated as single board.
= 1 The board is operated as slave (without any further downstream slave board).
= 2 The board is operated as master.
= 3 The board is operated as slave (together with a downstream slave board).
Comments • For usage of this command, see page 84.
• This command only returns the status if the addressed RTC
®
5 board was previously
initialized via load_program_file. Otherwise, 0 is returned.
RTC
®
4
RTC
®
5 new command
Version info Available beginning with version DLL 515, OUT 514, RBF 512
References sync_slaves
Ctrl Command get_mcbsp
Function returns the most recent input value that was fully transferred via the McBSP interface to
the memory location for Processing-on-the-fly applications.
Call
mcbsp_value = get_mcbsp()
Result Input value as a signed 32-bit value
Comments • get_mcbsp is equivalent to read_mcbsp(0) (see notes there).
RTC
®
4
RTC
®
5 new command
Version info • As of OUT 526, data transfer stagnation can no longer occur at the McBSP interface.
Therefore, get_mcbsp no longer needs to be called to resolve such stagnation.
Up to OUT 525, no more than two complete transmissions will be processed per 10 µs
cycle (also at 16 MHz). Each third data word might be overwritten with further data
words (the transfer stagnates). Up to OUT 525, any data transfer stagnation needs to
first be resolved via an additional get_mcbsp command before the actual current
values can be read via a further call of get_mcbsp. get_mcbsp_list can also achieve this
within execution of a list, so that a subsequent Processing-on-the-fly-application
(controlled by McBSP signals) will be supplied right from the beginning with current
data.
• As of OUT 526, data available at the McBSP after a load_program_file will be directly
and permanently acquired (also see page 53), whereas up to OUT 525 this only applies
if a Processing-on-the-fly-application that uses the McBSP interface has been activated
and a list is currently running.
References read_mcbsp
To Next Page
Loading...
