(new) GZ Feature tracker

[Jaeyoung-Lim]

Describe problem solved by the proposed feature

This is a feature tracker to achieve feature parity with gazebo classic.

Feed free to modify the issue to append the list or mark it as completed. If there is an issue/PR, please reference it.

Describe your preferred solution

The list of features that are missing in the new GZ is as follows:

Models

• Fixedwing-advanced lift drag (Port of Advanced Plane from Gazebo Classic to Gazebo #22167)
• Tiltrotor VTOL
• Differential rover (Differential drive for Rover & Gazebo R1 Rover port  #22402)
• Ackermann Rover (Add SITL airframe for ackermann rover #23383)
• Quadtailsitter
• Omnicopter (add a gz-omnicopter model #21818)
• USVs (Boats)

Worlds

• Ocean
• Baylands

PX4 related Features

• Gimbal Control (Add gimbal device  #23382)
• Camera Manager / Video Streaming
• Camera triggering/geotagging
• Rotor failures
• Collision prevention
• Catapult launch
• Parachute/Flight termination
• Retractable landing gear
• Precision Landing ([gz] X500 mono_cam_down and aruco world #23450)

Sensors

• Airspeed sensors
• Optical Flow sensor
• GPS yaw heading simulation
• Multi airspeed sensor

Actuators

• Wind influence for motor thrust
• Wind influence for lift and drag plugin

Simulation Features

• Faster than real-time simulation
• Vehicle view tracking (Follow model in gz GUI #22808)
• MAVSDK SITL tests
• Multivehicle simulation
• Wind/Gust simulation

Describe possible alternatives

NA

Additional context

[dakejahl]

Add optical flow to the sensors list. I can help with creating the plugin architecture, I just need to find some time to do it.

[mrpollo]

Maybe add switching the MAVSD SITL tests to the new GZ as well. I can take care of it once we have faster than real-time.

[dirksavage88]

1. Collision prevention/obstacle distance already exists in PX4 gz with the x500 lidar model:

   PX4-Autopilot/src/modules/simulation/gz_bridge/GZBridge.cpp

   Line 808 in 1a0f97e

   obstacle_distance_s obs {};

2. Catapult is just a Wrench publisher in GZ and a model would purely be for visual purposes. Easy to implement outside of PX4:
   gz topic -t /world/default/wrench -m gz.msgs.EntityWrench -p 'entity:{name:"x_500",type:MODEL},wrench:{force: {x:32000,y:0,z:8500,}}' -n 100

3. Airspeed is in GZ garden, but not yet in a PX4 plugin: https://github.com/gazebosim/gz-sensors/blob/gz-sensors7/src/AirSpeedSensor.cc

Multivehicle simulation as in multiple PX4 capable vehicles or just one PX4 vehicle and another controlled externally?

[Jaeyoung-Lim]

@dirksavage88

Collision prevention/obstacle distance already exists in PX4 gz with the x500 lidar model:

I know, but does the test work?

Catapult is just a Wrench publisher in GZ and a model would purely be for visual purposes. Easy to implement outside of PX4:
gz topic -t /world/default/wrench -m gz.msgs.EntityWrench -p 'entity:{name:"x_500",type:MODEL},wrench:{force: {x:32000,y:0,z:8500,}}' -n 100

We need to write a plugin that does it automatically on arm to make testing more convenient. It doesn't make sense to type that everytime you test it.

Airspeed is in GZ garden, but not yet in a PX4 plugin: https://github.com/gazebosim/gz-sensors/blob/gz-sensors7/src/AirSpeedSensor.cc

That is just the sensor implementation. We need to incorporate it into gz bridge and handle the airframe configs for it.

[dirksavage88]

@dirksavage88

Collision prevention/obstacle distance already exists in PX4 gz with the x500 lidar model:

I know, but does the test work?

Catapult is just a Wrench publisher in GZ and a model would purely be for visual purposes. Easy to implement outside of PX4:
gz topic -t /world/default/wrench -m gz.msgs.EntityWrench -p 'entity:{name:"x_500",type:MODEL},wrench:{force: {x:32000,y:0,z:8500,}}' -n 100

We need to write a plugin that does it automatically on arm to make testing more convenient. It doesn't make sense to type that everytime you test it.

Airspeed is in GZ garden, but not yet in a PX4 plugin: https://github.com/gazebosim/gz-sensors/blob/gz-sensors7/src/AirSpeedSensor.cc

That is just the sensor implementation. We need to incorporate it into gz bridge and handle the airframe configs for it.

By test, this is in reference to a unit test of some sort? I am not sure how tests were carried out in gazebo classic.