Main Question:
How do I explicitly fill out a union? The other examples given on the forum rely on it automatically figuring out what type to use, but the rtirecord struct (ab)uses the discriminator to mean different things!
Main Question:
How do I explicitly fill out a union? The other examples given on the forum rely on it automatically figuring out what type to use, but the rtirecord struct (ab)uses the discriminator to mean different things!
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 am trying to follow the best practice: https://community.rti.com/best-practices/dont-force-topic-names-be-same-type-names.
So I defined topic name "camera" and multiple types like Frame, Diagnostic etc. to be sent under topic. Sounds logical and looks clean and fits into DDS topic concept that is name + type.
I have some older dat files created through the rtirecorder. I believe they were recorded with version 4.5c.
When trying to play them back with a newer version, like 5.1.0 or 5.3.0, it terminates saying there is no column: SampleInfo_reception_timestamp
Is there a way to work around this? Exporting from sqlite and re-creating would take some time.
Any help would be appreaciated.
Thanks,
scott