Luc

Okay...here is a example where it worked when a packet was decoded.

19:35:41.197076 Hop: {ChannelIdx:18 ChannelFreq:911379847 FreqError:1775}
19:35:43.760963 ID:0 packet missed (50), missed per freq: [7 9 9 16 9 17 9 
9 16 9 10 9 9 16 9 9 17 9 9 16 9 10 16 9 9 16 10 17 9 17 9 9 16 9 9 9 16 9 
16 9 9 16 9 9 17 9 15 16 9 10 9]
19:35:43.761307 Hop: {ChannelIdx:0 ChannelFreq:902348338 FreqError:1775}
19:35:46.260077 8000B41D190057D9 18 0 0 0 12 msg.ID=0
19:35:46.260259 Hop: {ChannelIdx:19 ChannelFreq:911881597 FreqError:1653}
19:35:48.886651 ID:0 packet missed (1), missed per freq: [7 9 9 16 9 17 9 9 
16 9 10 9 9 16 9 9 17 9 9 17 9 10 16 9 9 16 10 17 9 17 9 9 16 9 9 9 16 9 16 
9 9 16 9 9 17 9 15 16 9 10 9]

Rich
On Sunday, March 24, 2019 at 7:32:45 PM UTC-4, ljm.h...@gmail.com wrote:
>
> Rich,
>
> This bug is harder than I thought. I need some time for debugging.
>
> Luc
>

Reply via email to