-
Bug
-
Resolution: Unresolved
-
Undefined
-
4.20.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The GNSS-Sync-State(gpsfix state) state is currently reported in metrics and cloud events do not accurately reflect the actual GNSS fix or sync condition.
Impact: Users and downstream systems receive incorrect cloud events indicating antenna disconnection when it may not have occurred. Expected Behavior: Map the cloud event and metric directly to the correct GNSS Sync State as defined in the spec, reflecting the true state: SYNCHRONIZED – GNSS functionality is synchronize ACQUIRING-SYNC – GNSS functionality is acquiring syn ANTENNA-DISCONNECTED – Only when physically disconnected BOOTING, ANTENNA-SHORT-CIRCUIT, FAILURE-* – according to actual GNSS status
Proposed fix
Update the mapping logic so that each GNSS Sync State reported in the cloud accurately represents the Ublox GPS fix state according to spec Ensure QA tests validate the mapping for all GNSS states.
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: