Topic type format shows as class not topic

[tank104]

Hi,
I have just setup a new environment (Ubuntu 22.04 + ROS2 Humble) and all the messages types are showing classes not topic structure.

i.e. px4_msgs::msg::CollisionConstraints instead of px4_msgs/msg/CollisionConstraints

I didn’t have this issue in Ubuntu 20.04 + ROS2 Galactic - but that might be a red herring - since its a new install now.

$ ros2 topic list -t
/fmu/collision_constraints/out [px4_msgs::msg::CollisionConstraints]
/fmu/debug_array/in [px4_msgs::msg::DebugArray]
/fmu/debug_key_value/in [px4_msgs::msg::DebugKeyValue]
/fmu/debug_value/in [px4_msgs::msg::DebugValue]
/fmu/debug_vect/in [px4_msgs::msg::DebugVect]
/fmu/offboard_control_mode/in [px4_msgs::msg::OffboardControlMode]
/fmu/onboard_computer_status/in [px4_msgs::msg::OnboardComputerStatus]
/fmu/position_setpoint/in [px4_msgs::msg::PositionSetpoint]
/fmu/position_setpoint_triplet/in [px4_msgs::msg::PositionSetpointTriplet]
/fmu/sensor_combined/out [px4_msgs::msg::SensorCombined]
/fmu/sensor_optical_flow/in [px4_msgs::msg::SensorOpticalFlow]
/fmu/telemetry_status/in [px4_msgs::msg::TelemetryStatus]
/fmu/timesync/in [px4_msgs::msg::Timesync]
/fmu/timesync/out [px4_msgs::msg::Timesync]
/fmu/trajectory_bezier/in [px4_msgs::msg::TrajectoryBezier]
/fmu/trajectory_setpoint/in [px4_msgs::msg::TrajectorySetpoint]
/fmu/trajectory_waypoint/out [px4_msgs::msg::TrajectoryWaypoint]
/fmu/vehicle_command/in [px4_msgs::msg::VehicleCommand]
/fmu/vehicle_control_mode/out [px4_msgs::msg::VehicleControlMode]
/fmu/vehicle_local_position_setpoint/in [px4_msgs::msg::VehicleLocalPositionSetpoint]
/fmu/vehicle_mocap_odometry/in [px4_msgs::msg::VehicleMocapOdometry]
/fmu/vehicle_odometry/out [px4_msgs::msg::VehicleOdometry]
/fmu/vehicle_status/out [px4_msgs::msg::VehicleStatus]
/fmu/vehicle_trajectory_bezier/in [px4_msgs::msg::VehicleTrajectoryBezier]
/fmu/vehicle_trajectory_waypoint/in [px4_msgs::msg::VehicleTrajectoryWaypoint]
/fmu/vehicle_trajectory_waypoint_desired/out [px4_msgs::msg::VehicleTrajectoryWaypointDesired]
/fmu/vehicle_visual_odometry/in [px4_msgs::msg::VehicleVisualOdometry]
/parameter_events [rcl_interfaces/msg/ParameterEvent]
/rosout [rcl_interfaces/msg/Log]
/timesync_status [px4_msgs::msg::TimesyncStatus]

[tank104]

I saw this issue: #52

But confirmed using fastrtpsgen v1.0.4. Also tried the latest, and always my messages are showing wrong.

[nigeltiany]

Could be resolved the same way 🤷‍♂️

#52 (comment)