Solutions

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 ...
58991 reads — 7 comments
For high-rate data, the usage of a WaitSet may lead to a very high CPU usage if the WaitSet wakes up too often. By default, a WaitSet is created without any properties specified. In this case, the WaitSet wakes up immediately every time a trigger event occurs. However, "waking up" involves a ...
5673 reads — 0 comments
Packets starting by RTPX are default domain discovery announcements. This is a new non-standard packet introduced in Connext 5.1.0 to help the tools discover applications running in other domains (for instance, RTI Admin Console). This packet is sent to the default multicast address and port for ...
4108 reads — 0 comments
The following error during shutdown: COMMENDBeReaderService_onSubmessage:!get ber remoteWriter indicates that a DataReader has received a sample but the corresponding remote DataWriter has already been deleted. If you are shutting down your entire system, you can probably ignore this message. ...
2823 reads — 0 comments
This solution is only a workaround until the Request/Reply API is available in LabVIEW. This will only work for one Requester and one Replier. The Request/Reply communication pattern is pretty useful for industrial applications. It is quite normal to have an application requesting an action to ...
17037 reads — 10 comments
If you create a large number of instances or entities and there is insufficient thread stack space, you can get the following error: REDAFastBufferPool_getBuffer:!precondition: pool==((void *)0) REDASkiplistNode_new:!create node REDASkiplist_assertNodeEA:!create node ...
3965 reads — 0 comments
A normal scenario in RTI Connext DDS is to have a Publisher that generates samples and several Subscribers that receive the generated data. In other words, the expected out-of-the-box behavior is for all Subscribers to get all the data. This is so because each Subscriber has its own DataReader for ...
4853 reads — 0 comments

Pages