Could not receive uXRCE_DDS topics with companion computer thorough TELEM2

PX4 Autopilot
5

Some Other Things

Check with serial connection

I ran cutecom to see the incoming data of /dev/ttyTHS0, then I got:

cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=1772996199802487634&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper
cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=1772996199802487634&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper1920×1133 101 KB

It seems like there are incoming data frames (starts with 7e 01 and ends cf 12) coming in with ~1hz. So I guess the wire connection was right.

Trials with Other Baud Rates

I read this and tried to set Baud rates with TELEM2 to either 57600, 115200 and 1000000. All of them cause same result. The change of baud rate including these steps(115200 for example):

  • Change SER_TEL2_BAUD to 115200.
  • In MAVLink Console run uxrce_dds_client stop then uxrce_dds_client start -t serial -d /dev/ttyS1 -b 115200.
  • Reboot vehicle in QGroundControl.
  • On companion computer run sudo MicroXRCEAgent serial --dev /dev/ttyTHS0 -b 115200.
  • Try with cutecom to see the data coming to /dev/ttyTHS0.

Basic Configuration

cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=9093922615068163450&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg
cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=9093922615068163450&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg2560×1511 130 KB

Parameters

cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=1137740806548867092&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg
cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=1137740806548867092&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg2560×1511 81.1 KB

cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=3245563171198595963&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg
cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=3245563171198595963&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg2560×1511 67.3 KB

cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=5379680580016524165&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg
cgi-bin_mmwebwx-bin_webwxgetmsgimg_&MsgID=5379680580016524165&skey=@crypt_e0af6e40_f7b0b8092479f642c5524c20a6687427&mmweb_appid=wx_webfilehelper.jpeg2560×1511 88.2 KB

In case other parameters need to be examined, I saved a .params file here.

The Most Weird Thing

I have used the SAME companion computer to receive the ROS2 topic data with another vehicle. Here is the brief information about it:

  • Model: AmovLab P450 Quadrotor.
  • Controller: Pixhawk6C
  • Firmware Version: 1.15.4
  • Link: here
  • PX4 Params: here
  • Wire Connections: TELEM2 on Pixhawk6C <—> UART1 on Amov NX

So I guess my companion computer was set right.

Summary

Basically, I’ve encounter problems with receiving uXRCE messages from a VTOL with CubePilot Cube Orange+ using a companion computer that has already succeeded with another quadrotor with Pixhawk6C. I have ruled out (in my mind) problems with wire connections and companion computer. I guess it has something to do with settings with CubePilot Cube Orange+.

I hope someone can help. I am pretty desperate about this. If someone is reading documents with AmovLab devices, they are in Mandarin and I recommend to translate it by web browser.

Wish all the best