Modify ↓
Opened 8 years ago
Closed 6 years ago
#90 closed task (fixed)
Apparently wrong update rates for RTCM message type scanning of BNC
| Reported by: | stuerze | Owned by: | stoecker |
|---|---|---|---|
| Priority: | normal | Component: | Professional Caster |
| Version: | Keywords: | ||
| Cc: | stuerze |
Description
The message type scanning in BNC delivers sometimes one message type twice per epoch (for example: 1064 every 10 seconds). But the real update rate is 5 seconds. Hence, it looks like the epoch before and / or behind it is missing.
But the two data sets have different epochs (difference is 5 secons)
Please note, the stream content is correct but the issue is related to the buffering in the BKG Ntrip Caster. Hence, it has to be solved there. BNC delivers correct values in connection with other Casters.
Attachments (0)
Change History (3)
comment:1 by , 8 years ago
| Type: | defect → task |
|---|
comment:2 by , 8 years ago
| Cc: | added |
|---|---|
| Component: | BNC → Professional Caster |
| Owner: | changed from to |
| Status: | new → assigned |
| Summary: | Apparently wrong update rates for RTCM mesage type scanning of BNC → Apparently wrong update rates for RTCM message type scanning of BNC |
comment:3 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
The buffer problem is soved within the BKG Ntrip Caster