Skip to content

GPS satellite count low and fix unstable compared to SoftRF #224

Description

@Oli-70

Hey everyone,

​I noticed a big difference in GPS performance when running GxAirCom vs. SoftRF on my LilyGO T-Beam-S3Core (equipped with the u-blox MAX-M10S chip). I tested both firmwares on the exact same board at the same location.

​What I'm seeing in GxAirCom:

  • ​Takes several minutes to get a GPS fix.
    ​Finds only about half the satellites that SoftRF sees.
  • ​Fix loss: It often drops satellites completely out of nowhere and loses the lock again.
  • ​Feels sluggish.

​Comparison with SoftRF:

  • ​Gets a fix within seconds.
  • ​Finds roughly twice as many satellites.
  • ​Holds the signal rock-solid and reacts much faster/more dynamically.

​Since this seems to be related to how the GNSS chip is initialized, this might not just affect the T-Beam-S3Core, but could potentially be a broader issue with GxAirCom's GPS config for M10 (or other) modules. SoftRF likely enables multiple constellations (like concurrent GPS + GLONASS + Galileo) or uses better UBX configuration messages during setup.

​My coding skills aren't deep enough to dive into the codebase and port the GPS init routines from SoftRF over to GxAirCom myself, so I wanted to share my findings here. Maybe someone with more experience can check how SoftRF configures the M10 chip and mirror that setup in GxAirCom.

​Thanks a lot for all your work on this project!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions