Copter-3.5.0-rc7 is now available for beta testing

Hi,

I got it on 2 vehicles, quad and octo.

What is happening - it only detects GPS units (i use witespy ones) if i set types to AUTO (1) and use autoconfigure setting (1). then it detects both GPS on board as ublox 115kbit.
If i set type to 2 - preset ublox, and remove autoconfigure option - i never get GPSes coming online at all! If i set autoconfigure to 0 and type to ‘auto’ - then i get something weird - i get one GPS discovered as NMEA at 38kbit, other one as NMEA at 9600. This way it works fine.

So, the issue i have exists on the quad - octo works fine.
On the quad i have consistent issue with both rc6 and rc7 - did not try previous releases - if i set all 3 options to (1) - autoconfig, auto, auto for types - it discovers second GPS fine, prints discovery string and a hardware string. First GPS unit is this one:

So, what happens with it - it repeatedly prints ‘discovered gps ublox 115000’ message and i believe it resets GPS feed automatically, like it fails something. If i look at statistics window i can see how GPS actually tries to get sats, but then statistic drops to 0. 99 hdop, 0 sat, then blinks back to 11 sats, then drops to 0 again.

if i remove autoconfiguration option i then get this GPS unit recognized as NMEA 38kbit and it comes up online fine every restart and shows sats fine as well. So it is quite confusing why it fails.
both vehicles use same auav controller, and all gps units are from witespy, but different types. so i am quite puzzled with that, why it acts like that with the autoconfig option set and why it is unable to autodiscover correctly as ublox if autoconfig is not set?

Here is how output looks, in messages window. ‘GPS 1: detected’ keeps showing up forever.

GPS 1: detected as u-blox at 115200 baud
GPS 1: detected as u-blox at 115200 baud
GPS 1: detected as u-blox at 115200 baud
PreArm: Throttle below Failsafe
u-blox 2 HW: 00080000 SW: 2.01 (75350)
GPS 1: detected as u-blox at 115200 baud
EKF2 IMU0 tilt alignment complete
EKF2 IMU1 tilt alignment complete
GPS 2: detected as u-blox at 115200 baud
GPS 1: detected as u-blox at 115200 baud
EKF2 IMU1 initial yaw alignment complete
EKF2 IMU0 initial yaw alignment complete
Barometer calibration complete
Calibrating barometer
Initialising APM

If i set GPS_AUTO_Config to 0 - here is what i get now:
PreArm: Throttle below Failsafe
GPS 1: detected as NMEA at 38400 baud
EKF2 IMU1 tilt alignment complete
GPS 2: detected as u-blox at 115200 baud
EKF2 IMU0 tilt alignment complete
EKF2 IMU1 initial yaw alignment complete
EKF2 IMU0 initial yaw alignment complete
Barometer calibration complete
Calibrating barometer
Initialising APM

i swear before it was giving GPS2 as NMEA 9600, no clue why now it shows up as proper ublox. all this it is very odd.