Recording service

Hi, 

I generated my xml files from my idl's and stored them in a folder called xml. This folder lives in the same directory as my MY_RECORDING_SERVICE.xml. It looks like this

main_folder/

|---xml/

|------image.xml

|------image_types.xml

|------coordinate_systems.xml

|---MY_RECORDING_SERVICE.xml

Inside my MY_RECORDING_SERVICE.xml I'm including these xml generated as follow: 

Hello, 

I'm sending images using a docker. I created a publisher and subscriber which sends a simple image. And I want to use the recording service to log info from this images. 

I created this xml, based on the example in the RTI_RecordingService_UsersManual.pdf page 27.

 

<?xml version="1.0" encoding="UTF-8"?>

 

 

 

Hi

I want to know whether it is possible to record other vendors' (e.g OpenSplice ...) data with recording service or not. I have tried to do that but got the following error :

"Failed to get valid typecode information for Publisher of Topic 'SampleStatus'. Recorder will NOT be able to record type 'DDSPackets::Main::IDL_Status::payload' in deserialized mode".

Thanks in advance for your help.

Bonjefir

We use the RTI Recording Service to record data, does anyone know of any good linux sqlite GUI tool to view the recorded data?    We use a tool called “sqlite-manager” but it doesn’t work well (failed to load/refresh) when the data file is constantly being added by the recording service.   

Hi all,

The recording service configuration file may contain the description of QoSs for its data readers. Is there a way to refer to the QoS profiles defined in a USER_QOS_PROFILES.xml file instead of recopying the entire description of the QoSs? In other words: how to describe in the configuration file the QoS profile that is expected to be used for each datareader?

Thanks in advance.

Hello,

While trying to use the RTI Recorder it crashed right after starting it. In the config file for the recorder we specified that it should use our QOS to create the recorder's participant, and removing this (thus making the recorder use the default RTI QOS) stopped it from crashing, however now it can't record our data which is using a different QOS. After some trial and error we reached the problemetic definition in our QOS which was causing the crash:

<participant_qos>

<property>