| 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 | (*) I found line "TODO: handle old ephemeris" in bns.cpp
|
|---|
| 23 |
|
|---|
| 24 | (*) Just a recommendation: The input format for clocks and orbits
|
|---|
| 25 | (from RTNet) very much follows the SP3 format. Would it be
|
|---|
| 26 | difficult to switch to from [m] to [km] as we have it in SP3?
|
|---|
| 27 | It would make it easier to argue for the usage of BNS within IGS
|
|---|
| 28 | if we can say: input is SP3. This would of course be something which
|
|---|
| 29 | would need to be adjusted also in RTNet - and I know that you prefer
|
|---|
| 30 | not to change RTNet.
|
|---|
| 31 |
|
|---|
| 32 |
|
|---|
| 33 | BNC
|
|---|
| 34 | =========================
|
|---|
| 35 | (*) Georg: Keep an eye on www.igs-ip.net/PENC0.
|
|---|
| 36 | Reason: Have seen 100% CPU. Dirk Stoecker says he has not seen
|
|---|
| 37 | this over a period of several days. He also says the reason
|
|---|
| 38 | could actually only be that the decoding function is called
|
|---|
| 39 | although no new data available.
|
|---|
| 40 |
|
|---|
| 41 | (*) Zdenek: Include GLONASS in RTCMv2 20/21 messages.
|
|---|
| 42 |
|
|---|
| 43 | (*) Zdenek: Include Loss of Lock indicator in socket output for RTNet
|
|---|
| 44 | Comment from Georg: Doesn't have this consequences for RTNet?
|
|---|
| 45 |
|
|---|
| 46 | (*) Concerning the new RTCMv3 clock/orbit messages, it looks like
|
|---|
| 47 | RTCM will now exchange input files between manufacturers. Each
|
|---|
| 48 | Manufacturer will do the encoding and decoding and results will
|
|---|
| 49 | be exchange to check them.
|
|---|
| 50 | Leos: BNC can't read from files. Would it be possible to have an
|
|---|
| 51 | additional function in BNC which allows that? (It may be, that
|
|---|
| 52 | this is not easy to implement.) Input would be the full path
|
|---|
| 53 | to the file plus a string describing the expected stream format.
|
|---|
| 54 |
|
|---|
