Changeset 1108 in ntrip
- Timestamp:
- Sep 9, 2008, 5:42:07 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/todo.txt
r571 r1108 1 Upgrade to NTRIP Version 2 1 BNS 2 ========================= 3 (*) Allow dummy clock values 999999.999999 coming from RTNet 4 Reason: DLR real-time engine (Oliver Montenbruck) uses dummies. 5 6 (*) How about clocks and orbits coming in sampling rates .ne. 1sec? 7 Does it make sense to support i.e. 3sec/5sec/10sec? 8 Reason: DRL provides clocks and orbits with 30sec sampling. 9 10 (*) Outlier in orbit corrections concerning only GLONASS. 11 Comment from Georg: I don't have an idea where to look for the problem. 12 Does anybody have an idea for a test scenario? 13 14 (*) BNS reconnect behavior with respect to caster is sometimes a problem. 15 I checked the situation with breaking/re-establishing the Internet 16 connection. BNS just stops operation. 17 18 (*) BNS reconnect behavior with respect to BNC is sometimes a problem. 19 Reason: Once BNC is stopped and restarted, BNS does not continue 20 its operation. 21 22 BNC 23 ========================= 24 (*) Georg: Keep an eye on www.igs-ip.net/PENC0. 25 Reason: Have seen 100% CPU. Dirk Stoecker says he has not seen 26 this over a period of several days. He also says the reason 27 could actually only be that the decoding function is called 28 although no new data available. 29 30 (*) Zdenek: Include GLONASS in RTCMv2 20/21 messages. 31 32 (*) Zdenek: Include Loss of Lock indicator in socket output for RTNet 33 Comment from Georg: Doesn't have this consequences for RTNet? 34 35 (*) Concerning the new RTCMv3 clock/orbit messages, it looks like 36 RTCM will now exchange input files between manufacturers. Each 37 Manufacturer will do the encoding and decoding and results will 38 be exchange to check them. 39 Leos: BNC can't read from files. Would it be possible to have an 40 additional function in BNC which allows that? (It may be, that 41 this is not easy to implement.) Input would be the full path 42 to the file plus a string describing the expected stream format. 43
Note:
See TracChangeset
for help on using the changeset viewer.