...
| Use an RT core for asynchronous computation | If set to "true", the driver will reserve a real-time CPU core for its communication system and will be able to handle a bigger amount of data. If set to "false", the communication system will default to core 0. |
| Verbose | If enabled, additional information will be displayed during the load of the model. |
| Data frame adjustments | This drop-down offers options for automatic adjustments to the data frame as it is being built. bits (including type changes) is modified. The options are: None: no actions are taken Ensure no overlap: overlaps will be automatically corrected; this option permits having gaps in the frame Ensure contiguous: overlaps will be automatically corrected and any possible gaps will be automatically erased The correction is done by displacing all signals affected by the changes mentioned above by the correct amountcorrect amount of bits. appropriate location possible. |
| Enable virtual mode | In virtual mode, the model can be executed even if this I/O interface is not compatible with the hardware configuration of the system. The connections between the model and the I/O interface will be done during the initialization, but the I/O interface will not do anything. The virtual mode can be used to troubleshoot problems on a system without having the required hardware, or to prepare a model with different |
Stream Configuration
General Stream Configuration
By default, the driver is configured with two streams with a TCP client and a TCP server, both using the internal loopback network on port 23000.
Each TCP-UDP stream device has multiple parameters:
| Protocol |
|---|
...
Two choices are available:
|
...
|
...
|
| TCP |
|---|
...
| mode | Two choices are available:
Note: Only visible when TCP is selected as protocol. |
|---|---|
| TCP port |
...
Select the TCP port on which the stream |
...
communicates. The default port is 23000. |
...
Note: Only visible when TCP is selected as protocol. |
| UDP local port |
|---|
...
Select the local UDP port on which the endpoint |
...
receives data. The default port is 23001. Note: Only visible when UDP is selected as protocol. |
| UDP remote port |
|---|
...
Select the remote UDP port on which the endpoint |
...
sends data. The default port is 23002. Note: Only visible when UDP is selected as protocol. |
| NIC name |
|---|
...
The desired network interface name. The proper interface name should be selected based on the information given by the Linux command "ifconfig". The name of the Ethernet network is returned. If the driver is running |
...
Windows this field is ignored. |
| Local IP |
|---|
...
| Address | IP address of the local TCP/UDP endpoint
|
|---|
...
|
| NIC speed |
|---|
...
The desired network interface speed. If the driver is running on Windows this field is ignored. Several choices are available:
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
| Remote IP address |
|---|
...
IP address of the remote TCP/UDP endpoint |
...
. Note: Only visible when TCP Server or UDP is selected. |
| Decimation factor |
|---|
...
| Number of timesteps between transmission triggers. A value of one triggers transmission at each timestep. | |
| Enable transmission control |
...
| Adds a data point that controls whether or not the I/O interface |
...
| sends data. If disabled, |
...
| transmission is always enabled. |
| Enable reception control |
|---|
...
| Adds a data point that controls whether or not the I/O interface |
...
| receives data. If disabled, reception is always enabled. |
| Swap byte order |
|---|
...
| Swaps the native byte order when transmitting data. | |
| Enable custom byte swap | If Swap byte order is enabled, this field becomes visible. If enabled, byte swap option for custom data type is available. |
| Use sequential bit ordering for custom data | When enabled, each custom data frame on the stream will have its bits reordered from Most Significant Bit (MSB) to Least Significant Bit (LSB), which in turn reorders the messages in the stream, regardless of the endianness of the machine. Byte within messages are in MSB and messages with the smallest bit offset are serialized first. For instance, given that Message 0 and Message 1 have the following characteristics in a stream:
The MSB serialization will package the messages in the memory block the following way:
Which will result 0x1A BC DE F0, as opposed of serializing traditionally in little endianness, read in a U32 register: 0xF0 DE BC 1A |
| Use VLAN | When enabled, this creates a VLAN interface based on the NIC name defined previously and the following parameters become visible:
|
Frame Format
A TCP-UDP stream frame builder example is shown below:
...