Custom Query (104 matches)
Results (52 - 54 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #96 | fixed | Incorrect bit-allocation for Galileo NDF | ||
| Description |
Regarding the description of the NDF format here: https://software.rtcm-ntrip.org/wiki/NDF There seems to be a mistake in the `Frame Data' section. It reports: Galileo I/NAV 244 bits F/NAV 2*120 bits But should be: Galileo I/NAV 2*120 bits F/NAV 244 bits |
|||
| #95 | invalid | Any plans to implement ntripclient for RTCM 3? | ||
| #94 | fixed | Data loss at beginning of the day | ||
| Description |
We're using bnc 2.12.2 to retrieve data from different casters (about ~250 different mountpoints) at a sample rate of 10 seconds. Every day at midnight we loss all the mountpoints data. It looks like there is some kind of problem with the time reference used by bnc in this case and therefore it discards all date with "Old epoch" messages (find attached full log). In case it is useful for your, there seem to be two things also happening at the day change: configuration read (which is always done, even if the onTheFlyInterval is not set) and rinex files creation. Perhaps some of this tasks is blocking the others, which adds a delay bigger than the sample rate? Thanks in advance, David Roma |
|||
