Kobuki,
A ppm calibration offset would be great! Unfortunately the program does not
provide one as of yet, I am well aware that my Freq list may be of little
use to anyone else. It's just a temporary terrible hack to get some
decoded output for now.
Luc,If I take your current US test Freq and add + 711 such as:
902419338,902921088,903422839,903924589,904426340,
904928090,905429841,905931591,906433342,906935092,
907436843,907938593,908440344,908942094,909443845,
909945595,910447346,910949096,911450847,911952597,
912454348,912956099,913457849,913959599,914461350,
914963100,915464850,915966601,916468351,916970102,
917471852,917973603,918475353,918977104,919478854,
919980605,920482355,920984106,921485856,921987607,
922489357,922991108,923492858,923994609,924496359,
924998110,925499860,926001611,926503361,927005112,
927506862,
Then it runs without the 5 missed and re-int
panders@laptop1:~/work/src/github.com/lheijst/rtldavis$
$GOPATH/bin/rtldavis -maxmissed 4 -tf US
19:10:26.883329 rtldavis.go VERSION=0.10
19:10:26.883441 tr=1 fc=0 ex=0 maxmissed=4 actChan=[0] maxChan=1
19:10:26.883751 BitRate: 19200
19:10:26.883769 SymbolLength: 14
19:10:26.883782 SampleRate: 268800
19:10:26.883791 Preamble: 1100101110001001
19:10:26.883799 PreambleSymbols: 16
19:10:26.883807 PreambleLength: 224
19:10:26.883817 PacketSymbols: 80
19:10:26.883828 PacketLength: 1120
19:10:26.883839 BlockSize: 512
19:10:26.883851 BufferLength: 2048
Detached kernel driver
Found Rafael Micro R820T tuner
19:10:27.360651 {ChannelIdx:0 ChannelFreq:902419338 FreqError:0}
Exact sample rate is: 268800.001367 Hz
Allocating 1 zero-copy buffers
19:10:27.555825 Init channels: wait max 133 seconds for a message of each
transmitter
19:10:50.528429 TRANSMITTER 0 SEEN
19:10:50.528584 Hop: {ChannelIdx:19 ChannelFreq:911952597 FreqError:-14}
19:10:53.090298 E000003D0500F339 2 0 0 0 0 msg.ID=0
19:10:53.090373 Hop: {ChannelIdx:41 ChannelFreq:922991108 FreqError:-45}
19:10:55.654347 500000FF7500485B 3 0 0 0 0 msg.ID=0
19:10:55.654413 Hop: {ChannelIdx:25 ChannelFreq:914963100 FreqError:-28}
19:10:58.216217 A00000AA85007F18 4 0 0 0 0 msg.ID=0
19:10:58.216293 Hop: {ChannelIdx:8 ChannelFreq:906433342 FreqError:-102}
19:11:00.777950 8000009305000ABC 5 0 0 0 0 msg.ID=0
19:11:00.778008 Hop: {ChannelIdx:47 ChannelFreq:926001611 FreqError:-20}
19:11:03.341700 E000003D0500F339 6 0 0 0 0 msg.ID=0
19:11:03.341755 Hop: {ChannelIdx:32 ChannelFreq:918475353 FreqError:-4}
19:11:05.903563 500000FF7500485B 7 0 0 0 0 msg.ID=0
19:11:05.903657 Hop: {ChannelIdx:13 ChannelFreq:908942094 FreqError:-10}
19:11:08.465485 600000FFC50079DA 8 0 0 0 0 msg.ID=0
19:11:08.465549 Hop: {ChannelIdx:36 ChannelFreq:920482355 FreqError:12}
19:11:11.029518 8000009305000ABC 9 0 0 0 0 msg.ID=0
19:11:11.029569 Hop: {ChannelIdx:22 ChannelFreq:913457849 FreqError:-64}
19:11:13.591415 E000003D0500F339 10 0 0 0 0 msg.ID=0
19:11:13.591476 Hop: {ChannelIdx:3 ChannelFreq:903924589 FreqError:12}
19:11:16.153252 500000FF7500485B 11 0 0 0 0 msg.ID=0
19:11:16.153304 Hop: {ChannelIdx:29 ChannelFreq:916970102 FreqError:-43}
19:11:18.716974 400000FFC5004CD2 12 0 0 0 0 msg.ID=0
19:11:18.717045 Hop: {ChannelIdx:44 ChannelFreq:924496359 FreqError:-73}
19:11:21.278841 8000009305000ABC 13 0 0 0 0 msg.ID=0
19:11:21.278908 Hop: {ChannelIdx:16 ChannelFreq:910447346 FreqError:-67}
19:11:23.840833 E000003D0500F339 14 0 0 0 0 msg.ID=0
19:11:23.840887 Hop: {ChannelIdx:5 ChannelFreq:904928090 FreqError:-12}
19:11:26.404319 500000FF7500485B 15 0 0 0 0 msg.ID=0
19:11:26.404373 Hop: {ChannelIdx:27 ChannelFreq:915966601 FreqError:-65}
19:11:28.966327 9000000005003151 16 0 0 0 0 msg.ID=0
19:11:28.966391 Hop: {ChannelIdx:38 ChannelFreq:921485856 FreqError:-47}
^CReattached kernel driver
On Monday, March 25, 2019 at 6:45:05 PM UTC-4, [email protected] wrote:
>
> Rich and Paul,
>
> I am puzzled by the fact that after the first received message on channel
> zero 5 messages in a row are missed AND after the next init NO SINGLE
> message is missed for a long period..
>
> I Don't think it has to to with warming up of the dongle, but it can have
> an influence.
>
> Another possibility is a to precise (time-out) timing. This is important
> when the program has to scan more than one transmitter but is less critical
> when only one transmitter is read.
>
> Could you both try to add the -ex parameter for extra loop timing?
>
> Try values such as '-ex 65' to '-ex 200' (ms). Maybe the percentage of
> missed signals will drop then.
>
> Luc
>
