The actuator_output values were -1 throughout the log when viewed in pyFlightAnalysis. I adjusted PWM_MIN and PWM_MAX to the values that are known to work in fmu-v5 on a similar airframe and the motors spun for half a second after arming, but then they stopped, and the copter disarmed. The log still contains -1 for relevant actuator values, I’ll chalk that up to an instrumentation error.
Only PWM_DISARMED, PWM_MAX and PWM_MIN are set and present in the firmware after build. I suspect some other necessary PWM_ param values are needed for pwm_out and the copter to work reliably @bkueng ? What else is required?
Also, why the duplication
boards/emlid/navio2? I understand the desire to match you’ve done with boards/holybro/pix32v5 and boards/holybro/durandal-v1, but those holybros are manufacturer supported boards, and emlid continues to oppose and divert from PX4, so I think you should pick and flaunt
Or perhaps utilize some form of “contains” hierarchy to reduce duplication if you want two entry points to what essentially looks like an identical build.
I tried v1.11, both boards/emlid/navio2 and boards/px4/raspberrypi (with mods). With the same hardware setup and underlying Ubuntu 20, v1.11 is more unstable than v1.10.1. Here’s a list of issues that I saw:
- Preflight keeps failing with
Fail: Gyros inconsistent - Check Cal. Re-calibrating doesn’t solve it, the issue comes back again later. There were a bunch of timeouts for sensors throughout - nothing like that happens with 1.10.1. That’s a clear blocker.
- The battery indicator incorrectly shows 100%
- The RC indicator in QGC does not light up
- Same exact issue with pwm_out and motors as 1.10.1 above, they spin immediately after arming and stop after 1/2 second. Perhaps that means it’s a config issue and not a code issue.
- A lot of small (debug) crud in the log and QGC warning flashes
I’ll stick with trying 1.10.1 for now.