1 | BNS
|
---|
2 | =========================
|
---|
3 | (*) BNS reconnect behavior with respect to caster is sometimes a problem.
|
---|
4 | I checked the situation with breaking/re-establishing the Internet
|
---|
5 | connection. BNS just stops operation.
|
---|
6 |
|
---|
7 | LM: it should be better now. At least it works fine on my notebook.
|
---|
8 |
|
---|
9 | (*) BNS reconnect behavior with respect to BNC is sometimes a problem.
|
---|
10 | Reason: Once BNC is stopped and restarted, BNS does not continue
|
---|
11 | its operation.
|
---|
12 |
|
---|
13 | LM: it should be better now. At least it works fine on my notebook.
|
---|
14 |
|
---|
15 | (*) Outlier in orbit corrections, concerning only GLONASS.
|
---|
16 | Comment from Georg: I don't have an idea where to look for the problem.
|
---|
17 | Does anybody have an idea for a test scenario?
|
---|
18 |
|
---|
19 | LM: I do not see the problem right now (on my notebook). Maybe is is already
|
---|
20 | O.K. due to other changes. Georg, could you test it?
|
---|
21 |
|
---|
22 | (*) DLR started (and unfortunately meanwhile stopped) sending 30sec
|
---|
23 | SP3 in realtime to euref-ip.bkg.bund.de:7777. Andre Hauschild promised
|
---|
24 | to restart sending SP3 again after the upcoming ION once he is back in Germany.
|
---|
25 |
|
---|
26 | (*) Allow dummy clock values 999999.999999 as input?
|
---|
27 | Reason: DLR real-time engine (Oliver Montenbruck) uses dummies.
|
---|
28 | The general question behind this is: Could it be done that the
|
---|
29 | input for BNS(from RTNet) is more closely coming in SP3 format?
|
---|
30 | The differences to SP3 we have today are just the 999999.999999
|
---|
31 | and the 2i/3i integers for orbit and clock corrections.
|
---|
32 | However, this touches RTNet's output.
|
---|
33 |
|
---|
34 | (*) How about clocks and orbits coming in sampling rates .ne. 1sec?
|
---|
35 | Does it make sense to support i.e. 3sec/5sec/10sec?
|
---|
36 | Reason: DRL provides clocks and orbits with 30sec sampling.
|
---|
37 |
|
---|
38 | (*) I found line "TODO: handle old ephemeris" in bns.cpp
|
---|
39 |
|
---|
40 |
|
---|
41 | BNC
|
---|
42 | =========================
|
---|
43 | (*) Georg: Keep an eye on www.igs-ip.net/PENC0.
|
---|
44 | Reason: Have seen 100% CPU. Dirk Stoecker says he has not seen
|
---|
45 | this over a period of several days. He also says the reason
|
---|
46 | could actually only be that the decoding function is called
|
---|
47 | although no new data available.
|
---|
48 | Georg, observation from 080915: BNC again shows 100% CPU because of PENC0.
|
---|
49 | Could it really be that the decoder is called although no new
|
---|
50 | data available? I deleted PENC0 from the configuration.
|
---|
51 |
|
---|
52 | (*) Die BNC-Routine füllt den rtcm3torinex-Puffer byteweise. Das ist unnötig
|
---|
53 | langsam. Der Puffer kann bis zum Rand gefüllt werden.
|
---|
54 |
|
---|
55 | LM: Das ist doch nicht wahr! Wo? In RTCM3/RTCM3Decoder.cpp fuellt man das
|
---|
56 | "_Parser.Message" mit "_Parser.NeedBytes" und erst dann startet das
|
---|
57 | dekodierung. Oder sprechen wir ueber einer anderen Stelle?
|
---|
58 |
|
---|
59 | (*) Zdenek: Include GLONASS in RTCMv2 20/21 messages.
|
---|
60 |
|
---|
61 | (*) Zdenek: Include Loss of Lock indicator in socket output for RTNet
|
---|
62 | Comment from Georg: Doesn't have this consequences for RTNet?
|
---|
63 |
|
---|
64 | (*) Concerning the new RTCMv3 clock/orbit messages, it looks like
|
---|
65 | RTCM will now exchange input files between manufacturers. Each
|
---|
66 | Manufacturer will do the encoding and decoding and results will
|
---|
67 | be exchange to check them.
|
---|
68 | Leos: BNC can't read from files. Would it be possible to have an
|
---|
69 | additional function in BNC which allows that? (It may be, that
|
---|
70 | this is not easy to implement.) Input would be the full path
|
---|
71 | to the file plus a string describing the expected stream format.
|
---|
72 |
|
---|