Custom Query (104 matches)
Results (10 - 12 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13 | fixed | Error storing RINEX ephemerids | ||
| Description |
Since BNC 2.6 the GLONASS ephemerids are stored in the GPS navigation file. The GLONASS navigation file only contains the header. |
|||
| #20 | fixed | Leap second bug in BNC | ||
| Description |
We are running v2.6 of BNC. The latency calculations produced by this software have been incorrect since the leap second of July 1 2012. The bug is in the module rtcm3torinex.c which does not feature the latest leap second. The result is that latency messages are being logged every second instead of at the proscribed interval (perfIntr), and of course the calculations are wrong (negative latencies!). |
|||
| #21 | fixed | Bug: SSR Update Intervall Indikator immer '0' | ||
| Description |
Der Indikator für das SSR-Update-Intervall (2te Spalte) ist sowohl in einer CLK-Datei als auch in der IP-Port-Ausgabe immer '0'; unabhängig von Message Type: Bsp: CLK10 .. 1057 0 1708 227100.0 G29 100 0.884 0.493 -0.100 -0.00002 -0.00029 0.00004 ! Orbits/Clocks: 31 GPS 0 Glonass 1058 0 1708 227100.0 G01 0 -2.677 0.00000 0.00000 .. Laut SSR-Dokumentation müsste entsprechend nachfolgender Liste für die Orbit-Korrekturen von CLK10 '6' für 60 Sekunden Update-Intervall und für die Uhr-Korrekturen von CLK10 '2' für 5 Sekunden Update-Intervall gesendet werden: SSR message update interval indicator 0 = 1 sec 1 = 2 sec 2 = 5 sec 3 = 10 sec 4 = 15 sec 5 = 30 sec 6 = 60 sec 7 = 120 sec 8 = 240 sec 9 = 300 sec 10 = 600 sec 11 = 900 sec 12 = 1800 sec 13 = 3600 sec 14 = 7200 sec 15 = 10800 sec |
|||
