Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Constant force on spacecraft after make #22

Closed
joris997 opened this issue Jul 16, 2024 · 2 comments
Closed

[Bug] Constant force on spacecraft after make #22

joris997 opened this issue Jul 16, 2024 · 2 comments
Assignees

Comments

@joris997
Copy link

joris997 commented Jul 16, 2024

Describe the bug

During initial operation, the /fmu/out/actuator_motors should publish actuation signals of all actuators of value 0.0 and the robot should remain static. This is not what happens. Instead, a constant force is being exerted on the platform.

This bug seems to be unique to Gazebo Garden.
I haven't tested this, but @Pedro-Roque told me this does not happen in the old Gazebo (see readme install instructions of this repo)

To Reproduce

  1. source ros and microros
  2. start the microros service ros2 run micro_ros_agent micro_ros_agent udp4 --port 8888
  3. make PX4-Space-Systems with the 2D space platform make px4_sitl gz_spacecraft_2d
  4. observe the movement

Other than that, you can additionally use QGroundControl and arm the robot. In position-mode, the robot behaves as expected and moves to the origin. In acro-mode, the robot is also subjected to this constant force.

Expected behavior

The robot remains static

Screenshot / Media

image
Arming the robot, enabling position mode, these are the /fmu/out/actuator_motors output

image
Armin the robot, acro-mode, these are the /fmu/out/actuator_motors output

Software Version

PX4-Space-Systems with Gazebo Garden with the DISCOWER px4_msgs and the DISCOWER gz-sim

Vehicle type

spacecraft_2d which grabs kth_freeflyer

Additional context (what I tried)

I created a custom kth_freeflyer model which has its maximum actuation set to 0.0. In this scenario, after startup, the robot does not move at all, indicating that there is something wrong on our end, not necessarily on Gazebo or the world file.

@Pedro-Roque
Copy link
Member

I could not reproduce your problem @joris997 . I do observe the force but the vehicle motion seems decoupled from actuator_outputs. In my case these are constantly zero. I'll check further on gazebo.

@Pedro-Roque
Copy link
Member

This issue is now fixed: there was a problem when targetDutyCycle was zero, that it would equal the beginning of the duty cycle, and therefore it would fire all thrusters.

This was fixed on the last commit to gazebosim/gz-sim#2431

andre-rebelo-teixeira pushed a commit to SpaceBotsISR/PX4-Space-Systems that referenced this issue Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants