[Bug] Unable to get publish topic in companion computer RasPi #23842
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Describe the bug
I was successfull connect ROS2 and PX4 via serial by the guide [https://docs.px4.io/main/en/companion_computer/pixhawk_rpi.html](url)
Opened the agent,It seems normal connected ,but only created subscriber
And it is only have /fmu/in/** topic.In my opinion,It is should also has /fmu/out/**
when I am looking the mavlink Console
its
Payload tx:has 0 B/s .I think this is abnormal.And thetimesync convergedisfalseI wanna know that is the true reason that I don't have output topic /fmu/out/**.The picture Below is the Parameters
And when I try to change the parameter
UXRCE_DDS_SYNCTinto 'Disable'.So I am able to get the published topic /fmu/out...
It is seems normal,but when i try to run example...It shows
timeout while checking message compatibility,I don't known why.And in QGroudControl Daily don't have the new mode
Autonomous Executor.In mavlink...
Now the
Payload txis not 0.ALL of this is normal when i in sitl,but it is doesn't work in real hardware.
To Reproduce
No response
Expected behavior
No response
Screenshot / Media
No response
Flight Log
No response
Software Version
nsh> ver all
HW arch: PX4_FMU_V5
HW type: V5006000
HW version: 0x006
HW revision: 0x000
PX4 git-hash: 9ca0630
PX4 version: 1.15.0 80 (17760384)
PX4 git-branch: main
OS: NuttX
OS version: Release 11.0.0 (184549631)
OS git-hash: d140f96627bd55edd24060cb90fe4c55ed3b9efd
Build datetime: Oct 22 2024 13:05:44
Build uri: localhost
Build variant: default
Toolchain: GNU GCC, 9.3.1 20200408 (release)
PX4GUID: 0002000000003234333830395119002c0041
MCU: STM32F76xxx, rev. Z
Flight controller
CUAV V5 nano
Vehicle type
Multicopter
How are the different components wired up (including port information)
PX4 TELEM2 Pin RPi GPIO Pin
UART5_TX (2) RXD (GPIO 15 - pin 10)
UART5_RX (3) TXD (GPIO 14 - pin 8)
GND (6) Ground (pin 6)
Additional context
No response
The text was updated successfully, but these errors were encountered: