It looks like there are a few ways to do this, but I'm looking for the simplest, and I'm unfamiliar with some of the terms used in some of the explanations.
I have a subscriber that runs long-term. At times, a publisher comes up and publishes a message quickly and exits.
The problem is that unless it waits for discovery to complete, it publishes and exits before discovery is complete, and the subscriber does not receive the message.
I'm running rtirecorder on a dedicated linux node while sending DDS traffic from another dedicated linux node. I'm monitoring traffic with a PC running wireshark.
Later, I analyze the sql recording on the recording system, and compare it to the wireshark trace, and I have determined that the recorder is not recording everything. The data rate is about 50 MB/s, with a 50K packet travelling over DDS every millisecond.
What can I do to make the recorder not drop packets?
Background:
I'm crosscompiling my application with the libraries from rti_connext_dds-5.3.0.3-pro-target-armv8Linux4.4gcc5.4.0.rtipkg. Cmake is building my application under the petalinux toolset (which is a wrapper around the bitbake/yocto toolset).
In starting up my DDS application at the command line, I get a ton of unexpected RTI messages, as shown below. As the prorgram runs, the "RTIOsapiUtility_getTimeAdv:now " messages come up about three times a second (PTP is also running, but I believe it is not changing time because there is no PTP master on my net).
We are running a DDS micro 2.4.10 as a writer and a DDS (5.3.0) node as a reader, and we would like the data to be sent only over multicast, not unicast.
However, we see the data being sent via unicast AND multicast to the same single reader. Sending each data packet twice is not good.
I'm running a DDS micro application (v 2.4.10) on a linux ARM system (compiled from source).
As participants, I also have an RTI Admin Console running on windows, and a custom application that is consuming the data that this application produces.
My DDS topic has a variable length sequence in it, as such:
module MyModule {
const long MAX_DATA_SIZE = 20000;
struct DataMessage {
sequence<long, MAX_DATA_SIZE> data;
};
};
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.
