@N_J,
Can you just use FastDDS? There’s been some significant refactoring around micrortps client. The name RTPS is making way for DDS. In my setup I noticed the name change to microdds_client. Mine is configured on TELEM3 as follows:
microdds_client start -t serial -d /dev/ttyS1 -b p:SER_TEL3_BAUD
Today the refactoring appears to be complete, So let me try from scratch:
$ git clone GitHub - PX4/PX4-Autopilot: PX4 Autopilot Software --recursive
$ cd PX4-Autopilot
$ git submodule update --init --recursive
$ make px4_fmu-v6c_default
$ ls build/px4_fmu-v6c_default/src/modules/microdds_client/. # See client already here
Flash firmware: build/px4_fmu-v6c_default/px4_fmu-v6c_default.px4
I can now see microdds_client running:
microdds_client start -t serial -d /dev/ttyS1 -b p:SER_TEL3_BAUD
Now for the agent:
Oops: src/modules/microdds_agent is no longer in the src tree! WTF?
In my test I subscribed to combined_sensor. I assume bandwidth depends on your link speed. The PX4 6C has no ethernet (UDP), but I was able to run my TELEM3 baud rate up to 2Mbps no MCU bog down. I suspect you could move a large fraction of the orb at that rate.
BTW, have you found any documentation for setting up a serial agent on the recent branch?
I see a lot of agent references but no microdds_agent, no MicroXRCEAgent:
Run an agent in a certain port, for example, 2018: MicroXRCEAgent udp4 -p 2018.