Low mass is causing UAV to climb on arming about jmavsim HOT 12 CLOSED

Can you provide a log generated by sdlog2 or the new logger?
Do you see the same problems in SITL?

from jmavsim.

I was able to reproduce, it climbes with HITL, but not with SITL.
But I'm not sure if changing the mass is the right solution. @kd0aij can you reproduce?

from jmavsim.

Do you get no flight log with HIL? It would be less work for me to analyze a log than to set up a HIL run.

from jmavsim.

I thought you had this working. Here's a log: http://logs.uaventure.com/view/ZXXowDSpCugMJXjoLfHN4X

from jmavsim.

Wow, that log has no data on thrust, RC inputs or actuator outputs. As far as I can tell nothing should be happening at all.

from jmavsim.

@sytelus I don't know how you're commanding the thrust level in your HIL setup, but the mavlink log shows that the only non-zero actuator_control_target is 0.68. If that's the thrust level, then it's no wonder that the quad is taking off.

from jmavsim.

I'm not doing anything about commanding the thrust level. My setup is everything with its defaults. After launching jMavLink, I just go to qGroundControl and arm the vehicle. That's all I do. The problem is reproducible even if you don't connect RC to pixhawk board.

One thing that is different in HIL and SITL is airframe. For HIL, I set the Airframe to Simulation > HIL Quadcopter X. For SITL, I think the default airframe is something else.

from jmavsim.

Then neither one of us knows what thrust level has been commanded. Why do you expect it to stay on the ground then?

from jmavsim.

As I'd mentioned, I'm using qGroundControl to arm the vehicle by sliding the switch. There is nothing else I'm doing to send any thrust commands. My setup is simple HIL with everything default. The only additional thing is setting airframe to Simulation > HIL Quadrotor X as per the readme instructions. It is clear that problem is not occurring without your change and is occurring with your change. I would suggest to test your changes with HIL first and then push your changes.

from jmavsim.

The the difference here is that @sytelus and the others having issues don't have an RC unit or other input. @kd0aij has an RC connected.

@kd0aij could you check the behaviour without any RC input?

from jmavsim.

This is nothing about a wrong mass but the issue is that the actuator scaling is wrong (or at least different for SITL vs. HITL right now.

A fix is coming up: #45, PX4/PX4-Autopilot#5716.

from jmavsim.

Fixed.

from jmavsim.