Altus Positioning Systems Pinpoints Cause for GLONASS Default

April 4, 2014  - By 1 Comments

Regarding the April 1–2 11-hour downtime for the full GLONASS constellation, president and CEO Neil Vancans of Altus Positioning Systems provides this additional information:

“From the reports on GLONASS problems, we have an explanation that may be used in our technical support replies:

“Our analysis reveals the GLONASS integration algorithms skipped an interval of around 1.5 minutes at the control centre software.

“At 21:00 UTC April 1, all GLONASS satellites received an orbit state (ephemeris) which was clearly several minutes ahead of the current orbit shape without actually changing the applicable reference time stamp. In other words, future orbit-position, velocity and accelerations were assigned to a current reference timestamp.

“This led to incorrect orbit positions for all GLONASS satellites and subsequent problems with receiver using GLONASS measurements.

“In our receivers, RAIM rejected the solutions because of the large GLONASS errors, and could only work with GPS only and the recently revised RAIM settings for a Base (SRL,ON,-6,-4,-4).

“The issue is now rectified, and the GLONASS constellation is back to normal.”

Alan Cameron

About the Author:

Alan Cameron is editor-in-chief and publisher of GPS World magazine, where he has worked since 2000. He also writes the monthly GNSS System Design e-mail newsletter and the Wide Awake blog.

1 Comment on "Altus Positioning Systems Pinpoints Cause for GLONASS Default"

Trackback | Comments RSS Feed

Inbound Links

  1. GLONASS Outage | GNSS Corner | April 8, 2014

Post a Comment