ROS topic issues

asked 2017-12-01 19:00:48 -0500

Noidea gravatar image

updated 2017-12-01 21:52:34 -0500

jayess gravatar image

RPi3 with PXFmini Linux version 4.4.20-v7+ (lander@erle) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #2 SMP PREEMPT Thu Sep 15 14:06:54 CEST 2016 frambuesa 3 mavros 0.18.3

My remote GCS connects without issue. My topics are not connected and not sure why. Also not sure where it's pulling hardware_id: udp://:6001@ from. I assumed from a launch file but not sure.

pi@erle-brain-2 ~ $ rostopic echo -n1 /diagnostics
No handlers could be found for logger "rosout"
header:
seq: 118
stamp:
secs: 1512174254
nsecs: 905840778
frame_id: ''
status:
-
level: 1
name: mavros: FCU connection
message: not connected
hardware_id: udp://:6001@
values:
-
key: Received packets:
value: 0
-
key: Dropped packets:
value: 0
-
key: Buffer overruns:
value: 0
-
key: Parse errors:
value: 0
-
key: Rx sequence number:
value: 0
-
key: Tx sequence number:
value: 0
-
key: Rx total bytes:
value: 0
-
key: Tx total bytes:
value: 0
-
key: Rx speed:
value: 0.000000
-
key: Tx speed:
value: 0.000000
-
level: 2
name: mavros: GPS
message: No satellites
hardware_id: udp://:6001@
values:
-
key: Satellites visible
value: 0
-
key: Fix type
value: 0
-
key: EPH (m)
value: Unknown
-
key: EPV (m)
value: Unknown
-
level: 2
name: mavros: Heartbeat
message: No events recorded.
hardware_id: udp://:6001@
values:
-
key: Heartbeats since startup
value: 0
-
key: Frequency (Hz)
value: 0.000000
-
key: Vehicle type
value: Generic micro air vehicle
-
key: Autopilot type
value: Generic autopilot
-
key: Mode
value: ''
-
key: System status
value: Uninit
-
level: 0
name: mavros: System
message: Normal
hardware_id: udp://:6001@
values:
-
key: Sensor present
value: 0x00000000
-
key: Sensor enabled
value: 0x00000000
-
key: Sensor helth
value: 0x00000000
-
key: CPU Load (%)
value: 0.0
-
key: Drop rate (%)
value: 0.0
-
key: Errors comm
value: 0
-
key: Errors count #1
value: 0
-
key: Errors count #2
value: 0
-
key: Errors count #3
value: 0
-
key: Errors count #4
value: 0
-
level: 2
name: mavros: Battery
message: No data
hardware_id: udp://:6001@
values:
-
key: Voltage
value: -1.00
-
key: Current
value: 0.0
-
key: Remaining
value: 0.0

pi@erle-brain-2 ~ $ rostopic list
No handlers could be found for logger "rosout"
/diagnostics
/mavlink/from
/mavlink/to
/mavros/actuator_control
/mavros/altitude
/mavros/battery
/mavros/cam_imu_sync/cam_imu_stamp
/mavros/extended_state
/mavros/fake_gps/fix
/mavros/global_position/compass_hdg
/mavros/global_position/global
/mavros/global_position/local
/mavros/global_position/raw/fix
/mavros/global_position/raw/gps_vel
/mavros/global_position/rel_alt
/mavros/hil_actuator_controls
/mavros/hil_controls/hil_controls
/mavros/imu/atm_pressure
/mavros/imu/data
/mavros/imu/data_raw
/mavros/imu/mag
/mavros/imu/temperature
/mavros/local_position/odom
/mavros/local_position/pose
/mavros/local_position/velocity
/mavros/manual_control/control
/mavros/mission/waypoints
/mavros/mocap/pose
/mavros/px4flow/ground_distance
/mavros/px4flow/raw/optical_flow_rad
/mavros/px4flow/temperature
/mavros/radio_status
/mavros/rc/in
/mavros/rc/out
/mavros/rc/override
/mavros/safety_area/set
/mavros/setpoint_accel/accel
/mavros/setpoint_attitude/att_throttle
/mavros/setpoint_attitude/attitude
/mavros/setpoint_attitude/cmd_vel
/mavros/setpoint_position/local
/mavros/setpoint_raw/attitude
/mavros/setpoint_raw/global
/mavros/setpoint_raw/local
/mavros/setpoint_raw/target_attitude
/mavros/setpoint_raw/target_global
/mavros/setpoint_raw/target_local
/mavros/setpoint_velocity/cmd_vel
/mavros/state
/mavros/time_reference
/mavros/vfr_hud
/mavros ...
(more)
edit retag flag offensive close merge delete

Comments

1

The hardware id is indeed pulled from launch file. Your autopilot is not connected because invalid hardware_id. That's why your topics do nothing. Btw this is not ROS related issue but rather px4 issue. Next time ask on pixhawk's forums.

l4ncelot gravatar image l4ncelot  ( 2017-12-02 09:38:41 -0500 )edit