| 1 | BNS
|
|---|
| 2 | =========================
|
|---|
| 3 | (*) DLR started (and unfortunately meanwhile stopped) sending 30sec
|
|---|
| 4 | SP3 in realtime to euref-ip.bkg.bund.de:7777. Andre Hauschild promised
|
|---|
| 5 | to restart sending SP3 again after the upcoming ION once he is back in Germany.
|
|---|
| 6 |
|
|---|
| 7 | (*) Allow dummy clock values 999999.999999 as input?
|
|---|
| 8 | Reason: DLR real-time engine (Oliver Montenbruck) uses dummies.
|
|---|
| 9 | The general question behind this is: Could it be done that the
|
|---|
| 10 | input for BNS(from RTNet) is more closely coming in SP3 format?
|
|---|
| 11 | The differences to SP3 we have today are just the 999999.999999
|
|---|
| 12 | and the 2i/3i integers for orbit and clock corrections.
|
|---|
| 13 | However, this touches RTNet's output.
|
|---|
| 14 |
|
|---|
| 15 | (*) How about clocks and orbits coming in sampling rates .ne. 1sec?
|
|---|
| 16 | Does it make sense to support i.e. 3sec/5sec/10sec?
|
|---|
| 17 | Reason: DRL provides clocks and orbits with 30sec sampling.
|
|---|
| 18 |
|
|---|
| 19 | (*) Outlier in orbit corrections, concerning only GLONASS.
|
|---|
| 20 | Comment from Georg: I don't have an idea where to look for the problem.
|
|---|
| 21 | Does anybody have an idea for a test scenario?
|
|---|
| 22 |
|
|---|
| 23 | (*) BNS reconnect behavior with respect to caster is sometimes a problem.
|
|---|
| 24 | I checked the situation with breaking/re-establishing the Internet
|
|---|
| 25 | connection. BNS just stops operation.
|
|---|
| 26 |
|
|---|
| 27 | (*) BNS reconnect behavior with respect to BNC is sometimes a problem.
|
|---|
| 28 | Reason: Once BNC is stopped and restarted, BNS does not continue
|
|---|
| 29 | its operation.
|
|---|
| 30 |
|
|---|
| 31 | (*) I found line "TODO: handle old ephemeris" in bns.cpp
|
|---|
| 32 |
|
|---|
| 33 |
|
|---|
| 34 | BNC
|
|---|
| 35 | =========================
|
|---|
| 36 | (*) Georg: Keep an eye on www.igs-ip.net/PENC0.
|
|---|
| 37 | Reason: Have seen 100% CPU. Dirk Stoecker says he has not seen
|
|---|
| 38 | this over a period of several days. He also says the reason
|
|---|
| 39 | could actually only be that the decoding function is called
|
|---|
| 40 | although no new data available.
|
|---|
| 41 |
|
|---|
| 42 | (*) Zdenek: Include GLONASS in RTCMv2 20/21 messages.
|
|---|
| 43 |
|
|---|
| 44 | (*) Zdenek: Include Loss of Lock indicator in socket output for RTNet
|
|---|
| 45 | Comment from Georg: Doesn't have this consequences for RTNet?
|
|---|
| 46 |
|
|---|
| 47 | (*) Concerning the new RTCMv3 clock/orbit messages, it looks like
|
|---|
| 48 | RTCM will now exchange input files between manufacturers. Each
|
|---|
| 49 | Manufacturer will do the encoding and decoding and results will
|
|---|
| 50 | be exchange to check them.
|
|---|
| 51 | Leos: BNC can't read from files. Would it be possible to have an
|
|---|
| 52 | additional function in BNC which allows that? (It may be, that
|
|---|
| 53 | this is not easy to implement.) Input would be the full path
|
|---|
| 54 | to the file plus a string describing the expected stream format.
|
|---|
| 55 |
|
|---|
