voxl-px4 vs mainline px4 SITL questions
-
Background: I'm trying to set up a multi-vehicle sim environment using gazebo and px4 sitl. I've got 4 quads on SDK v1.3.5. I wanted to pull the voxl-px4/modalai px4-firmware version from that release to build px4_sitl on my local machine so I can test in sim against a version that's going to most representative of firmware on the quads.
I'm building inside a ubuntu 22 docker container after running ./px4-firmware/Tools/setup/ubuntu.sh. The px4_sitl build failed because of the bug mentioned here: https://forum.modalai.com/topic/3510/px4-build-broken-for-sitl-targets
I implemented the poster's fix (https://github.com/modalai/px4-firmware/pull/61) and was able to build px4-sitl but when I run it I get the following errors:
ERROR [gz_bridge] timed out waiting for clock message
ERROR [gz_bridge] Task start failed (-1)
ERROR [init] gz_bridge failed to start
ERROR [px4] Startup script returned with return value: 256Are there extra steps I missed that are required to build px4_sitl from modalai's px4-firmware fork vs the mainline px4? Is it just not going to work if I try to build it on my laptop?
If I have to pull a mainline px4 branch to build sitl on my laptop, is there a specific release (e.g. 1.14.0-1.14.4) that would be most analogous to the past/current branches of modalai's px4-firmware? The voxl-px4 version I have installed on the quads is using the 1.14.0-2.0.85 firmware.
I'm doing multi-vehicle offboard control via ros2 w/ ext vision for state estimation, mostly testing code that publishes trajectory setpoints. I'd like to make sure at least the controller and estimator code is as close as possible to what's running on the quads.
-
J jmltt referenced this topic on
-
Background: I'm trying to set up a multi-vehicle sim environment using gazebo and px4 sitl. I've got 4 quads on SDK v1.3.5. I wanted to pull the voxl-px4/modalai px4-firmware version from that release to build px4_sitl on my local machine so I can test in sim against a version that's going to most representative of firmware on the quads.
I'm building inside a ubuntu 22 docker container after running ./px4-firmware/Tools/setup/ubuntu.sh. The px4_sitl build failed because of the bug mentioned here: https://forum.modalai.com/topic/3510/px4-build-broken-for-sitl-targets
I implemented the poster's fix (https://github.com/modalai/px4-firmware/pull/61) and was able to build px4-sitl but when I run it I get the following errors:
ERROR [gz_bridge] timed out waiting for clock message
ERROR [gz_bridge] Task start failed (-1)
ERROR [init] gz_bridge failed to start
ERROR [px4] Startup script returned with return value: 256Are there extra steps I missed that are required to build px4_sitl from modalai's px4-firmware fork vs the mainline px4? Is it just not going to work if I try to build it on my laptop?
If I have to pull a mainline px4 branch to build sitl on my laptop, is there a specific release (e.g. 1.14.0-1.14.4) that would be most analogous to the past/current branches of modalai's px4-firmware? The voxl-px4 version I have installed on the quads is using the 1.14.0-2.0.85 firmware.
I'm doing multi-vehicle offboard control via ros2 w/ ext vision for state estimation, mostly testing code that publishes trajectory setpoints. I'd like to make sure at least the controller and estimator code is as close as possible to what's running on the quads.
Looks the same bug as here: https://github.com/PX4/PX4-Autopilot/issues/22148
Added the change from this commit and it looks like it works now: https://github.com/PX4/PX4-Autopilot/pull/22194/commits/38f3c711084b349cb9ed82cf44ff181c6a40738a
Reading along? Create a free ModalAI Forum account to join in.
With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.
Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.
Register Login