Closed hanzheteng closed 3 years ago
From diagnostics i see that something coming in at relatively high speed, but only 2 messages ok. From checkid i see that it is having some complete garbage messages (checkid do not verify framing status, which likely indicating CRC errors).
From that facts i can suspect that you're having problem with hardware link. Please verify that you properly connected Rx-Tx and Grounds, and that you do not have ground loops, which can cause a lot of noise. If you could, i suggest to use some simple oscilloscope to check signal conditions. Most of the pins on STM32 are 5V tolerant, so probably you hadn't damaged it. Anyway you can try to use TELEM1.
Thank you for the constructive feedback. It ends up with the case that both cables I used are problematic.
The mRo USB FTDI Serial to JST-GH adapter is not a ready-to-go product (though recommended by PX4 docs in this section). I have to swap the TX and RX cables (cut them off and solder again). As for the second adapter I used, the chip is not a proper one and the noise level is too high (soldering was bad).
After fixing the hardware link, I made it work on the TELEM2 port. Out of curiosity, I also tested it with the FTDI chip in 5V mode, and it worked as well (the red power pin is not connected anyway). As you pointed out that most pins are 5V tolerant, I didn't really damage the port. Also found it in this section in PX4 docs,
All Pixhawk serial ports operate at 3.3V and are 5V level compatible.
Thanks again for the help. I am closing this issue.
Issue details
The mavros launch file got stuck at the line of
MAVROS started. MY ID 1.240, TARGET ID 1.1
. In the diagnostic message, it says that FCU is not connected.Efforts so far:
cat /dev/ttyPixhawk
and RX indicator is flickering. The Python serial toolminiterm.py
can also output symbols/streaming.TELEM2
; other parameters such as mode and baudrate are also set properly. (If MAV_1_CONFIG is disabled, the RX indicator will not flash any more.)fcu_url
is set to/dev/ttyPixhawk:921600
, andtgt_system
andtgt_component
do match theMAV_SYS_ID
andMAV_COMP_ID
parameters in PX4 firmware.Potential influence:
At this point I am still not entirely sure if this is a hardware issue (e.g., damaged FCU), or a software issue (e.g., incompatible/mismatched version). It seems to me that the computer and FCU are indeed exchanging data, bi-directionally, but somehow they don't recognize each other. (The baud rate is also matched, BTW). Went through existing issues but didn't get any more inspiration. Any hints or testing suggestions are appreciated.
MAVROS version and platform
Mavros: 1.8.0 (May 2021) ROS: Melodic Ubuntu: 18.04 Onboard computer: Jetson Xavier NX Autopilot: Pixhawk 4 Connection: Onboard computer and Pixhawk is directly connected via a FTDI chip (USB-JST)
Autopilot type and version
[X] PX4
Version: 1.11.3 (Jan 2021)
Node logs
Diagnostics
Check ID
launch file:
px4.launch