Micro

We are excited to announce the immediate availability of updates to Connext Drive 3.1.

Highlights of Connext Drive 3.1 updates include:

I'm running a DDS micro client (v 2.4.10) on a linux ARM system (compiled from source).  It produces topic data on one second intervals, and I have a windows 7 system with the Connext Pro version 5.3.0 running the Admin Console that should be able to watch the data.

The documentation explains that Connext Micro supports only BY_RECEPTION_TIMESTAMP for the DESTINATION_ORDER QoS. Thus, a Micro application will be able to receive data from a full-DDS application with BY_SOURCE_TIMESTAMP, but not send data to this application.

Hi,

I'm asking about which real time QoSs are supported in DDS Micro edition. I found this list of supported QoS on Data Distribution Service for Real-time Systems document:

DURABILITY
DURABILITY_SERVICE
PRESENTATION
DEADLINE
LATENCY_BUDGET
OWNERSHIP
OWNERSHIP_STRENGTH
LIVELINESS
TIME_BASED_FILTER
PARTITION
RELIABILITY
TRANSPORT_PRIORITY
LIFESPAN
DESTINATION_ORDER
HISTORY
RESOURCE_LIMITS

Hello RTI Community,

I'm having trouble getting multicast communications working between a connext micro and connext pro application. 

I am evaluating microDDS and am looking for a description of some of the micro DDS unique API's used in some of the examples provided with micro DDS.  These APIs are not described in the "RTI Connext Micro API and QoS Guide".  Specifically, in the HelloWorld_dpde example:

1. Configuration of the registry via RT_Registry_register()  for strings "wh", "rh",  "_udp" and  "dpde" strings.  What is the purpose of this function call and what is the signficance of the strings?

Hi,

What is the minimum amount of memory needed to run Micro ?

What is the minimum size of the library ?

Thanks,

Raz