+ Model name
And I ran a make px4_sitl gazebo_(model name) but the terminal’s message doesn’t proceed after it.
dogcontrol99@dogcontrol99-TUF-Gaming-FX505DT-FX505DT:~/PX4-Autopilot$ make px4_sitl gazebo_cnu_vtol
[0/4] Performing build step for 'sitl_gazebo'
ninja: no work to do.
[3/4] cd /home/dogcontrol99/PX4-Autopi...9/PX4-Autopilot/build/px4_sitl_default
empty world, default world cnu_vtol.world for model found
Is there any missing things? Or Is there any solutions of it? The version of PX4 is v1.13.3
I didn’t try it at PX4-Autopilot main branch because model file is my senior’s old work so it has mixer file that doesn’t works on main branch. Is it necessary to check model at PX4-Autopilot main branch?
No, if you have your own branch it shall be ok. I am asking because I dont know the mixer file, just wanted to be sure you know about those airframes, since you did not mentioned it directly in the issue description.
When the mixer configuration is finished, the version of PX4-Autopilot was v1.9.1 . However, some troubles happened when launching Autopilot v.1.9.1 in Ubuntu 20.04, so i was trying to launch model files with v1.13.3 .
Hi @dogcontrol , did you succeeded ? I have managed to convert the x500 model for gazebo garden into gazebo classic model, but it is dead. Once I start simulation, the drone is spawned, but it does not communicate. And I have no mixer files… I use latest commits from PX4-Autopilot.
Still no answer, but for your question, you need to check PX4_Autopilot toolchian installation because gazebo garden is Gazebo ignition which is different to gazebo classic. Once simulation tool is different, Mavlink system will be different too.