Each network interface must have its own Real-time Network Device (RTND) Driver.
The RT-TCP/IP stack, when running, uses multiple threads to accomplish its tasks. The priority and ideal processor of each thread can be set independently. The main portion of the RT-TCP/IP Stack uses a timer thread , to handle all TCP/IP time-related functions. Each network card uses two threads, an interrupt service thread that handles all interrupt-related processing, and a receiving thread that handles all receive-related processing. The priority settings needed for these threads depend greatly on how time-critical the TCP/IP processing is, related to any other processing activities running on the system. If you are not sure what values to enter, leave these fields blank.
Parameters
You can check the status of and change these configurable parameters using the RTX64 control panel.
NOTE: Configurable parameters that have N/A for a default value in the table do not have a default value. If used, values for these parameters must be specified.
RTX64 Control Panel
| Property | Description | Default |
|---|---|---|
| Device name |
The device associated with the interface. NOTE: The length of this friendly name cannot be more than 14 characters. |
|
|
Driver name |
The name of the Real-time network device (Rtnd) driver for this interface, which is either the file name of the RTDLL implementing the driver or the full pathname to the RTDLL implementing the driver. | |
|
IPv4 address |
The IPv4 address of the interface in dotted-quad notation. | |
| Netmask | The IPv4 network mask of the interface in dotted-quad notation. | |
| Gateway | The gateway for this interface. This parameter is optional. If this parameter is not specified, the interface has no gateway. In order to connect the local LAN to another LAN, the Gateway address must be specified. The Gateway address is specified as an IPv4 address in dot notation. | 0.0.0.0 |
| Location | The PCI bus location of the network interface card for the interface in the form of three semicolon-separated integers. This property is optional. | 0;0;0 |
| Interrupt thread priority | The interrupt priority for the interface. This must be a valid RTX64 priority, an integer in the range 0 to 127. This property is optional. | 64 |
| Interrupt processor |
The ideal processor for the thread servicing the interface interrupts. The specified value must be a valid RTSS processor. NOTE: Processor numbers are zero-based. By default, the first RTSS processor is the ideal processor. |
0 |
| MTU | The Maximum Transmission Unit (MTU) size in bytes for the interface. This property is optional. | The Stack-wide MTU, which defaults to 1500 |
| IPv6 address |
The IPv6 address. When the property is set to Auto, the network interface auto configures one link-local IP address. If the property is set to an IPv6 address, the network interface auto-configures a link-local address and the specified address. Link-local and site-local IPv6 addresses have scope IDs. Global IPv6 addresses do not have scope IDs. The RT TCP/IP stack chooses a scope ID when it configures the IPv6 address. The scope ID of a configured IPv6 address is displayed after the %. It can be obtained with the socket call getnameinfo. The RTSS application must set the scope ID of a local IPv6 address in the sockaddr_in6 structure for a connect and sendto socket call, if the outgoing connection is made using a link-local or site-local IPv6 address. The RtssClient.rtss application uses the –o option to specify scope ID. |
Auto |
| IPv6 prefix | The IPv6 network prefix. This property is optional. | 64 |
| Receive thread priority | The RT-TCP/IP stack’s receive thread priority. This must be a valid RTX64 priority in the range 0 to 127. This property is optional. | 63 |
| Receive thread ideal processor |
The ideal processor for the interface’s receive thread. The specified value must be a valid RTSS processor. NOTE: Processor numbers are zero based. By default, the first RTSS processor is the ideal processor |
0 |
| Number of receive buffers | The number of receive buffers used by the interface. This property is optional. | 256 |
| Number of transmit buffers | The number of transmit buffers used by the interface. This property is optional. | 256 |
| Interrupt type | Specify what type of interrupt will be used (MSI-X, MSI or Line-based). This is optional. If it is not set, the best available will be used. | MSI-X |
| Filter name | The name of the filter associated with the interface. | |
| Filter status | The enabled/disabled status of the filter. | Disable |
| Link status |
Enable/disable monitoring the link status for a given interface. NOTE: The driver for the network device must support acknowledging generated interrupts on link status changes in order for stack link status monitoring to function. |
Enable |
| Link status priority | The RT-TCP/IP stack’s link status thread priority. This must be a valid RTX64 priority in the range 0 to 127. This property is optional. | 0 |
| Link status thread ideal processor |
The ideal processor for the interface's link status thread. The specified value must be a valid RTSS processor. This property is optional. NOTE: Processor numbers are zero based. By default, the first RTSS processor is the ideal processor. |
0 |
