RTI Core Libraries and Utilities

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 ...
41275 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 ...
5150 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 ...
4506 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. ...
7060 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 ...
3697 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 ...
3709 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 ...
6169 reads — 0 comments
Note: Applies to RTI Data Distribution Service 4.2 and 4.3 RTI Data Distribution Service 4.2 and 4.3 applications and tools are interoperable, with the following caveats. To monitor a 4.2 application with 4.3 tools: If your 4.2 application's data types do not contain any 8-byte or larger primitive ...
2636 reads — 0 comments
Note: Applies to RTI DDS 4.0x. The following applies to RTI DDS 4.0g (or earlier). This problem has been corrected in RTI DDS 4.0h and later. You may see a deadlock problem during application shutdown, with or without an error message. This deadlock is typically seen when the value for the ...
5596 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 ...
7598 reads — 0 comments

Pages

Subscribe to RSS - RTI Core Libraries and Utilities