This option allows to format data unpacking for compatibility with other devices. 2 notions are implied.

The first specifies if the unpacking of the signal should be started from the start or end of the packet. If Signal 1 to N is selected, the packing will start from the less significant bits of the first transmitted byte. If Signal N to 1 is selected, unpacking will start from the most significant bits of the last transmitted byte and progress backward into the packet.

The second specifies if groups of 8, 16 or 32 bits must be permuted within the packet with respect to its middle boundary. Swapping is performed before extracting signals.

Number of entries that the application can log into memory before placing data into the file. Since an RT-LABmodel is executed real-time, writing into a file has to be done by a lower priority thread to avoid overruns. This thread writes data when time is available and in case of time be missing, it is important to have a memory buffer large enough to keep messages in memory until the time is available to write to the file. This value should never be less than twice the Number of samples between writes or twice the sum of Packets Before and after Trigger when using trigger model. It should be much larger than those limits to prevent data loss.

The mat file contains 1 variable in which each column represents one message and rows contain the following values:

1. The timestamp of the message (derived from the timestamp provided by the board)
2. Message identifier
3. DLC
4. Data byte 1
5. Data byte 2
6. Data byte 3
7. Data byte 4
8. Data byte 5
9. Data byte 6
10. Data byte 7
11. Data byte 8
12. Error.
13. Rx/Tx: 0=>message was received, 1=>message was transmitted)
14. Model time when the message was processed by the model
15. Identifier type: 0=>standard identifier, 1=>extended identifier

This option allows the user to dynamically change the mat file log during model execution. Selecting this option makes a new inport appear. The user must use it to input an ID that will be used to create the name of the mat file log. The name of the mat file log follows the pattern:

<Log file name parameter value without extension>_<ID input by the user>.mat

A change in the ID input triggers the closing of the current log file and the opening of a new log file. The name of the new log file is based on the new ID. At the end of the simulation, after model reset, all log files will be transferred to the host. The user may individually transfer one or more log files to the host for further analysis, before the end of the simulation. By default, this feature is not available.

Specifies if an error occurred.

Possible values are:

• 0: no error
• -1: CanAc2 reception FIFO overrun. Data has been lost at the hardware level.
• -3: Internal buffer FIFO overrun. This should never occur unless Number of packets is much too small or model overruns occurred.