VxWorks

Note: Applies to Connext DDS 5.x and above Sending TypeCode/TypeObject on the wire provides convenience over specifying the type via XML configuration, but has the disadvantage that more data must be sent during endpoint discovery. This can cause network congestion problems when the TypeCode/ ...
5425 reads — 0 comments
Note: Applies to RTI Connext 5.2.0 and above. The following error: PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2. This class ID does not match the class ID 16777216 of the same transport in the local participant ...
54394 reads — 7 comments
When running two applications on the same WindRiver VxWorks target, one in kernel mode and the other in RTP mode, the two applications will not discover each other when using out of box settings in RTI Connext. The reason this occurs has to do with how RTI Connext internally marks the individual ...
5263 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. The following error: [D0004|CREATE Participant|D0004|ENABLE] NDDS_Transport_Shmem_is_segment_compatible:incompatible shared memory protocol detected. Current version 1.0 not compatible with 2.0. is caused when two applications, one using RTI Connext DDS 4 ...
5661 reads — 0 comments
Note: Applies to NDDS 3.0 and VxWorks 5.4. Introduction The VxWorks TCP/IP stack uses a fixed amount of buffers. The buffers and their sizes are configured in the kernel. This is different from non real-time OSs, where the buffers can be taken as needed from main memory. In many NDDS applications ...
24461 reads — 0 comments
SENS/TORNADO 2.0 NETWORK STACK CONFIGURATION/PERFORMANCE ISSUES -------------------------------- 1. INTRODUCTION 1.1 NETWORK STACK VERSIONS 1.2 NET POOLS 1.2.1 CLUSTERS 1.2.2 CLUSTER BLOCKS 1.2.3 MBLOCKS 1.3 RECEIVING: DATA FLOW FROM DRIVER TO APPLICATION LEVEL 1.4 SENDING: DATA FLOW FROM ...
10666 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. RTI Connext calls fopen() to load the default XML and NDDS_DISCOVERY_PEERS files if they exist. On some VxWorks targets that either have no file system or use NFS, FTP, or some other network-based file system, and the file system is not mounted, RTI ...
4842 reads — 0 comments
As described in TCP/IP Illustrated, Volume 1, by W. Richard Stevens, Section 11.9 , ARP entries that expire may introduce high latencies on the next send. Entry expiration details are system-dependent; for instance, a packet sent to a particular address may refresh the timeout. On a VxWorks target ...
4991 reads — 0 comments
Note: Applies to NDDS 3.x and earlier, RTI Data Distribution Service 4.0 and 4.1 To monitor the state of the data buffer usage inside the stack, you can use the netStackDataPoolShow or mbufShow functions. Both commands give the same information. If the stack has been running out of clusters, these ...
7428 reads — 0 comments
Note : Applies to RTI NDDS 2.x and earlier, and NDDS 3.x. This Solution describes errors you may see when running an NDDS application on VxWorks 5.4.x or 5.5.x. These error messages most likely mean that the amount and/or sizing of your stack buffers are incorrect. NDDS is unable to send "NDDS ...
4741 reads — 0 comments

Pages

Subscribe to RSS - VxWorks