Hi All, We have only a few issues left to resolve for 1.4.1. While the core team will do the flight testing for these fixes, we would benefit from some general flight testing on these aspects: Multirotor altitude hold / position hold vs. 1.3 stable using the default estimators Multirotor altitude…

600 class quad with AUAV-X2 (and baro static port) running INAV on 1.4.1rc4: http://logs.uaventure.com/view/AmKfSBm8WYM9PVQYH7GugN ALTCTL was solid, no glitches observed POSCTL and RTL worked well also [image]

I’ve just pushed another update to the beta branch which improves the LPE performance. More flight testing with LPE would be appreciated. The last open issue we have are better defaults for position control gains.

Hello, Today when I try to load beta firmware in QGC 3.0 to my Pixhawk the upload goes well but after reboot I have the red led blink and QGC said “Your vehicle is not responding.[…]”. “Master” firmware do the same. “nuttx-px4fmu-v2-default.px4” from the 1.4.1rc4 zip has same problem. But when I…

No issue here at all with upgrading an existing system. What sort of peripherals do you have connected? The official release is now available: [image] PX4/Firmware PX4 Autopilot Software. Contribute to PX4/Firmware development by creating an account on GitHub. …

Congratulation for 1.4.1 release ! I have leaved only GPS + power module + Telemetry + buzzer + safety switch. I2C and telem2 disconnected. Upload of 1.4.1 bring to rapid flashing red and no connection with QGC 3.0. Upload of 1.3.4, via GQC, work, after px4 reboot QGC ask for calibrating sensor.

OK, I have connected the serial console and here is what is happening: sercon: Registering CDC/ACM serial driver sercon: Successfully registered the CDC/ACM serial driver WARN [param] selected parameter default file /fs/mtd_params rgbled on I2C bus 2 at 0x55 (bus: 100 KHz, max: 100 KHz) WARN …

I assume you use a FMUv2 Type FC. I had the very same Issue with an AUAV-X2 on 1.3.x Firmware when you choose EKF you need a Build that includes EKF. Connect to the Console and set the Parameter SYS_MC_EST_GROUP back to 0. This should let your FC startup completely.

@Andreas_Hoffmann Good thinking, in this case its the EKF1 which is missing. Today all three options (INAV, LPE, EKF2) are present in the same binary. [image] Benoit_C: ekf_att_pos_estimator Are you using the rover config? That was the only location where that filter was still present anywhe…

Yes I have once selected Rover to be sure to clean parameters, like we do with Arducopter. Not a good idea for PX4 :frowning: How to be sure to clean the Pixhawk ? Loading Arducopter then PX4 ?

@Benoit_C if you really want to reset all parameters to defaults then in QGC go to parameters and under tools you’ll see an option to reset all to default. Then select your airframe/rover and restart.

V1.4.1 Release testing

Flight Testing & Log Analysis

agribov August 9, 2016, 6:41pm 33

Sorry @LorenzMeier, I didn’t see this thread. I found a problem while testing the firmware, and turned it into a seperate thread: Huge Accelerometer errors with new firmware

Topic		Replies	Views
Position Control - Flight Mode PX4 Autopilot	39	8362	August 31, 2016
Various Issues with 1.5.2 Stable Flight Testing & Log Analysis	6	1262	December 27, 2016
Huge Accelerometer errors with new firmware	15	3115	August 20, 2016
Level horizon not staying calibrated PX4 Autopilot	21	3409	December 5, 2016
Full E-flite Convergence support PX4 Autopilot	81	18758	November 17, 2020

V1.4.1 Release testing

Related topics