I am operating on an octorotor (custom build from a local company) only from teleoperation since now. The octorotor has a Pixhawk Orange Cube mounted on the Kore multi-rotor carrier board (https://www.spektreworks.com/products/multi-rotor-pixhawk21-carrier-board) and communicates for the basic telemetry with the raspberry Pi 4.
I purchased an NVIDIA Jetson AGX Xavier in order to integrate automation flight algorithms based on NN detection for feature tracking with a ZED 2 stereocamera.
The NVIDIA Jetson AGX Xavier is set up (JetPack 4.4, CUDA 10.2 etc.), it has the basic ROS installation and the zed-ros-wrapper works well.
I now want to connect the Jetson with the Pixhawk. The guys that built the multi-rotor have given me cables coming from the SERIAL5 port of the carrier board in order to connect a TX, RX and GROUND cable for the communication.
I purchased a cheap USB to TTL cable like this one https://www.adafruit.com/product/954, i connected the cables and tried to run mavros apm.launch
The serial5 port on the carrier board is set up to speak with the cables and has a baudrate 921000 (everything from mission planner).
I also checked with an oscillator that the TX and RX cables give me pulse so they give information.
I also tried that cross connection of the cables (TX-RX and RX-TX, TX-TX and RX-RX)
All of the times when i run the mavros launch file for apm.launch with the right baudrate the rostopics where not published. It’s like there is dead communication.
I don’t know what else to try. Is there any more HW debugging you can recommend?
Is there the possibility the cable is not appropriate? How can i check this?
If everything is good HW-wise. what else can i check SW-wise?