Problem acquiring GPS satellites (possible voxl2 board EMI?)

[nuallaino]

Hello,
We have a Starling 2 and a few Starling 2 Max's which have issues acquiring GPS. We tested on several occasions outside with clear skies. However, we never acquire any satellites no matter how long we wait.

The current version information is as follows, but we have tried earlier voxl-suite versions too:

system-image: 1.7.10-M0054-14.1a-perf
kernel:       #1 SMP PREEMPT Fri Sep 27 22:10:45 UTC 2024 4.19.125
--------------------------------------------------------------------------------
hw platform:  M0054
mach.var:     1.2.1
--------------------------------------------------------------------------------
voxl-suite:   1.3.5
--------------------------------------------------------------------------------
current IP:   wlan0: 192.168.8.1
--------------------------------------------------------------------------------

It appears that there is comms with the gps module, from the following log excerpt:

INFO  [muorb] SLPI: GPS UART baudrate set to 9600
INFO  [muorb] SLPI: GPS UART baudrate set to 38400
INFO  [muorb] SLPI: Got ack to initial CFG_VALSET!
INFO  [muorb] SLPI: u-blox firmware version: SPG 5.10
INFO  [muorb] SLPI: u-blox protocol version: 34.10
INFO  [muorb] SLPI: u-blox module: MAX-M10S
INFO  [uORB] Advertising remote topic sensor_gps

We used SignalHound to check of EMI from the drone in an RF isolation chamber. The 1st plot shows the chamber baseline with the Starling 2 powered off and the second shows the spike in EM from the Starling 2 once powered on. The EMI is right at the GPS L1 freq.

After modifying one of the Starling 2 Max drones to use a pixhawk gps module on a mast (as in the following picture) we were able to acquire gps satellites without issue. No software changes were made.

I'd appreciate any guidance on whether we have a hardware issue with the out of the box GPS units or any other steps to debug the issue.

Thanks!