Block

Mask

Description

This block is one part of a sampling process that will occur in the Bitstream/XSG/FPGA model. It must be used with an XSG Scope block from the RT-XSG library, which must be in the bitstream.
The XSG Scope will have to be placed in the RT-Lab CPU model. It configures sampling parameters, receives data sampled through DataOutport, and performs automatic rescaling.
Parameters for these 2 blocks must be set accordingly.

This is to give you an idea about how to set the parameters:

In this example, your FPGA model is set to sample 3 channels in 16 bits mode, and you used the LoadIn port 2, LoadOut port 3, and DataOut ports 4 and 5.

That is the reason why you will have to set your parameters for the XSG Scope in the RT-Lab model this way:

Parameters

General

Card	Choose your FPGA card: ML605 or OP5142 only.
FPGA Frequency	Choose your FPGA card frequency.
Oversampling factor	Choose the number of samples you want each for CPU step, from 1 to 250. This will set your sampling resolution.
Controller Name	Bind this block to an OpCtrlblock by entering the same 'Controller Name' as specified in the OpCtrl block. The OpCtrl block controls initialization of the settings for one specific card in the system. If your card is an ML605/OP5142, the OpCtrl must be from the RT-Lab ML605/OP5142EX1 Library.
Number of channels	The number of channels you want to sample, from 1 to 32. This parameter must be the same in your XSG Scope in the bitstream and depends on your needs.
Enable 16 bits mode	If enabled, performance may improve but precision may decrease if the channels you want to sample in the bitstream are more than 16 bits long. This parameter must be the same in your XSGScope in the bitstream model, and you should choose to enable/disable it depending on if you prefer high precision or abetter performance (meaning that you can have a smaller CPU time step.).
LoadIn port ID	Enter the loadIn port number to which your XSG Scope in your bitstream is connected. The block will not work if the LoadIn port is not specified.
LoadOut port ID	Enter the loadOut port number to which your XSG Scope in your bitstream is connected. The block will not work if the LoadOutport is not specified.
DataOut Recv port IDs	Enter the DataOut ports numbers to which your XSG Scope in your bitstream is connected. The block will not work if the port Ids are not specified. Make sure you enter a vector and that the numbers are in the right order otherwise, the automatic rescaling will be false.

Information

Model Time Step	The size of the RT-Lab CPU step time. Refreshed every model update.
Resolution	Since the XSG Scope blocks perform regular sampling, this is the sampling resolution you will obtain with this time step and this oversampling factor.
Time needed for data transmission	This is an indicator only. Data transmission time is not null, due to the PCI-e speed. If this time is smaller than the CPU step time, overruns will occur. If the CPU step time is slightly higher, there is a greater probability of overruns, and the number of overruns will increase with the complexity of your RT-Lab CPU model. An overrun occurs when your CPU model does not have the time to perform all processing and data transmission, meaning there will be incorrect data in your model, but you cannot determine where. Avoid overruns.

Inputs

None.

Outputs

Load Status	Status for the LoadIn (element 1 of the vector) and the LoadOut (element 2). Have a look to the LoadIn/Out help for the meaning.
DataOut Receive Status	Status for DataOut ports. If you entered K DataOuts in the DataOutPort ID mask parameter, then the status for the first one will be the first element of the vector, and the status of the K-th will be the K-th/last element of the vector. If the value is not 0, there is a problem. For the meaning of those statuses, have a look at the DataOut Receive help.
Channel N	Data from channel N sampled and automatically rescaled to the double format. The width of the vector is equal to the oversampling factor.

Characteristics and Limitations

This block is suitable for models that have a CPU time step lower than 5ms for ML605 at 200 Mhz, and lower than 10 ms for OP5142/ML605 cards at 100 MHz, and has to be used only withOP5142/ML605 cards.

Direct Feedthrough	No
Discrete sample time	Yes
XHP support	Yes
Work offline	No

RT-LAB Documentation

OP5142EX1 XSGScope