Wrong satellite data with EOS receiver
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- mobile, networking
Research direction
Start by examining the network-connection handling for EOS receivers and compare the two attached example logs with the satellite data displayed by EOS Tools PRO. Done means Mergin Maps reports stable satellites in view and in use, with values matching the receiver’s proprietary app.
Written by the indexing model from the issue text.
Description
Description
When using network connection with EOS devices the satellite data is worng and doesn't match the data shown in EOS tools PRO. Mergin Maps shows only satellites in use and no satellites in view. But even this number jumps quite a lot and loops back to 0 after few values. Example logs below:
Environment
Production
Application (+ app version, build, operating system)
2026.3.0+
Steps to reproduce
- connect EOS receiver via network connection
- observe wrong data
Actual results
Wrong satellite info, doesn't match receivers proprietary app info
Expected results
Both satellites in view and in use are filled and matching receivers proprietary app info
- Dominant language
- C++
- Stars
- 389
- Forks
- 88
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MerginMaps/mobile
-
bug iOS 🍎 ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4744 ·
Maintainers usually reply within 2 days
-
bluetooth bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MerginMaps/mobile#4741 ·
Maintainers usually reply within 2 days
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MerginMaps/mobile#4669 ·
Maintainers usually reply within 2 days
-
bug Good first issue ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MerginMaps/mobile#4665 ·
Maintainers usually reply within 2 days
-
bug ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MerginMaps/mobile#4647 · 1 comment ·
Maintainers usually reply within 2 days
All issues in MerginMaps/mobile
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
c++ good first issue M2: audio plumbing no hardware needed tests
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
GageLawton/noise-cancellation#23 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nullmoth/nvidia-macos-driver#126 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/eo-graphs#85 ·