I'm remotely controlling rtirecord using a java application. It works fine recording pings until I increase the sample rate to 100 samples per second. At different points in my application, the rtirecord process stops sending heart beat and stalls. Attached is the java code and rtirecord xml file I use.
Attachment | Size |
---|---|
rtirecord.xml | 4.25 KB |
rtirecordcontrolsample.java | 9.64 KB |
Hi Paul,
Does the Recorder application crash or just stops sending status messages through administration?
Did you check the integrity of the recorded data? Is Recorder losing samples? Are any sample-lost messages printed out?
Thanks,
Juanlu
The process doesn't die, but the data file doesn't seem to grow once it stalls. I'm not watching stdout from the rtirecord process, but I could do that.
UPDATE: It gets more interesting ... It seems to be environment / network related. The problem was pretty reliable in occurance, although sometimes would happen when I send resume, and other times when i send stop. However, this only happens on my home network. The same VM running on the same laptop connected at my office LAN does NOT have this problem at all!!!
That's indeed strange, so this could be related to the DDS layer.
Are you just publishing the PingTopic? Is Recorder's memory growing?