GPS configuration issue

ArduPlane Plane 4.6
1

After updating to 4.6.0-beta1 I had the problem today (Tritilt VTOL, BZGNSS BZ-251 GPS / u-blox M10 chip, Mateksys H743 white), that could not be armed due to problems with the GPS configuration:

Messages:
GPS 1: probing for u-blox at 230400 baud
u-blox 1 HW: 000A0000 SW: ROM SPG 5.10 (7b202e)
Arm: GPS 1 still configuring this GPS
GPS 1: u-blox solution rate configuration 0x80008

GPS has perfect reception, status 4, 14-16 sats, HDOP < 0.85
Here is the short prearm log file: MagentaCLOUD

At home, I switched back to 4.5.7. stable, which did not have the problem.
To cross-check, I reinstalled 4.6.0-beta1, and the problem was back. To be able to fly with the VTOL and 4.6.0-beta1 for the time being, I disabled GPS_AUTO_CONFIG so that it can be armed.

On 2 other airplanes with different GPS (M8N) the problem did not occur when switching to the beta.

Rolf

2

I’ll check the BZ-251 on my ARWingPro.

The Beitian BE-220 on my Drift did not have any issues with 4.6.0-beta1.

EDIT:
Confirmed, with the BZ-251 it keeps trying to write configuration and at some point the ESC starts to beep. Something seems to hang-up here. But it took a couple of reboots to reach this scenario.

[ARWingPro:1] u-blox 1 HW: 000A0000 SW: ROM SPG 5.10 (7b202e) 
[ARWingPro:1] ArduPlane V4.6.0-beta1 (8d4976cd) 
[ARWingPro:1] ChibiOS: 88b84600 
[ARWingPro:1] MatekF405-Wing-bdshot 00220036 32325010 2039384D 
[ARWingPro:1] RCOut: PWM:1-2 DS600:3-4 PWM:5-10 
[ARWingPro:1] PreArm: GPS 1 still configuring this GPS 
[ARWingPro:1] GPS 1: u-blox solution rate configuration 0x208
1 Like
3

I had the same problem with a matek f405 TE. It wouldnt arm. Wouldnt configure the gps. did you solve this?

4

Set GPS_AUTO_CONFIG to 0
(If it is adequately configured, it does not have to be reconfigured at every boot)

Rolf

5

Thanks. That did it!

6

How do I config the GPS(brand new) for the first time?

With disabled GPS_AUTO_CONFIG it won’t be configured.

I’m on the latest beta. Is there a fix for this somewhere?

Thanks

7

You may have to enable auto config once. From what I have observed, it does set “Airborne >4G” and the baudrate but leaves SATS / GNSS options untouched.
The annoying part is that it takes a couple of attempts because some conditional evaluation is not correct in AP4.6. I’ve seen a patch commit somewhere recently.