QNX

Why is Connext Micro logging [Module: 4, Errcode: 215]?

By default, RTI Connext Micro will let the Network stack select the interface that will be used to receive multicast traffic. This is done by simply using INADDR_ANY (which translates to 0.0.0.0) when setting the socket option to join a multicast group (that is IP_ADD_MEMBERSHIP). While this works ...
aromero
Mon, 04/01/2024 - 01:13
591 reads — 0 comments

How to choose QNX target libraries

“Note: This article applies to Connext DDS Professional 4.x and above” The QNX operating system provides in its SDK a front-end that calls a GCC named “qcc”. In the end, qcc will call the compiler, set the correct flags and link libraries based on the parameters that you use. The SDK provides the C ...
pablov
Wed, 08/28/2019 - 09:04
5985 reads — 0 comments

Using Dynamic or Static Libraries with DDS Secure

When you link your application with the RTI Connext DDS libraries, you can choose whether to use dynamic or static linking. But what is the best approach if you want to use the DDS Secure plug-in? There are some situations that you need to be aware of and avoid. This article describes the possible ...
fabrizio
Wed, 03/27/2019 - 09:34
5175 reads — 0 comments

When do I need to send TypeCode or TypeObject?

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/ ...
grayson
Thu, 03/14/2019 - 11:48
5559 reads — 0 comments

What causes this error: "PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2"

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 ...
belen
Wed, 03/25/2015 - 10:05
56849 reads — 7 comments

What causes this error: "incompatible shared memory protocol detected."

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 ...
bobby
Wed, 02/06/2013 - 14:05
5741 reads — 0 comments

How can I resolve problems with QNX applications that use shared memory?

Note: Applies to RTI Connext 4.x and above If you have an RTI Connext application running on a QNX machine and it is unable to communicate with other applications running on the same machine started by another user, or if your application fails to start (with an error related to shared memory), ...
sara
Thu, 01/17/2013 - 07:15
6459 reads — 0 comments
Subscribe to RSS - QNX