RTI Core Libraries and Utilities

Note: Applies to RTI Connext 4.x and above RTI Connext does not support the IDL interface data type because it corresponds to remote procedure calls, a concept that does not apply to the data-centric, publish-subscribe (DCPS) communications model of the DDS standard. The valuetype data type is ...
5456 reads — 0 comments
Note: Applies to RTI Connext 4.x and above and Red Hat Enterprise Linux 5. If DDS_DomainParticipantFactory_set_qos() crashes, the stack trace begins with free () from /lib/libc.so.6 and if you're making any calls to mlockall() , explicitly or implicitly, you may be running into a known bug in glibc ...
3290 reads — 0 comments
Errno 0x2738 or 10040 is WSAEMSGSIZE . It indicates that a datagram failed to be sent or received because an OS or hardware buffer was smaller than the datagram. Check for consistency between the publishing and subscribing Participant’s Transport property: transport.parent.message_size_max . ...
5861 reads — 0 comments
Note: Applies to RTI Connext 4.x and above. When using Visual Studio to build the project files generated by rtiddsgen, you may see the following error message: [source file name]:fatal error C1083: Cannot open compiler generated file:[object file name] is generated. The error is due to the fact ...
42232 reads — 0 comments
The following methods (provided in the FooSeq class) will help you manage RTI Connext sequences: FooSeq::loan_contiguous() for C++ FooSeq::loan_discontiguous() for C++ FooSeq_loan_contiguous() for C FooSeq_loan_discontiguous() for C FooSeq::unloan() for C++ FooSeq_unloan() for C Sequence.loan() for ...
5509 reads — 0 comments
RTI Connext uses clocks to measure time and generate timestamps. The middleware uses two clocks: an internal clock and an external clock. The internal clock measures time and handles all timing in the middleware. The external clock is used solely to generate timestamps (such as the source timestamp ...
4794 reads — 0 comments
Note: Applies to RTI Connext 4.x through 5.1. ETA: As of 5.2, RTI Connext supports truly unbounded sequences and strings in the C, C++, and .NET APIs. Unbounded sequences are actually not unbounded at all. They are bounded sequences whose bound is initialized by RTI Connext instead of by the user. ...
7652 reads — 0 comments
RTI Connext's static and dynamic libraries have the same tradeoffs as any other static and dynamic libraries. The main advantage of using dynamic libraries is less system-wide memory usage when there is more than one application using the same libraries on the machine. Starting a dynamically linked ...
4025 reads — 0 comments
NOTE: Applies to NDDS 3.x and RTI Connext 4.x and above. If you see errors similar to the following when using the Visual Studio 6.0 development environment: nddscorezd.lib(heap.obj) : error LNK2001: unresolved external symbol __aligned_malloc nddscorezd.lib(heap.obj) : error LNK2001: unresolved ...
4007 reads — 0 comments
Note: Applies to RTI Connext 4.x and above The narrow method is a class-scope method that implements a safe down-cast for a pointer to an RTI Connext entity. It is a type-safe way to cast a pointer. The Java API does not require this method because Java casts are always type-safe. This method takes ...
6651 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities