Open MikeFallon opened 11 months ago
Hello Mike,
this and similar scan problems are known, but hard for me to reproduce, as I have rather poor receiving conditions. However I am wondering as the scanning did not change between 4.1.2 and 4.1.3.
Nevertheless: What you could do is to relax the timing conditions, i.e. increase the "Delay Time Before Ident" value.
What would also be helpful: Enable the "Debug" logging in the "Settings". Debug files will be created and put into the following directory:
C:\Users\
Thanks! Clem
Thanks Clem, will do a debug log as soon as I can.
I have increased the "Delay Time Before Ident" value and it has cured the problem. Thanks for the tip Clem
Hi Mike,
thanks for info! I would be interested in the following information:
Hi Clem, I'm using delay time.=5. The symbol rate is around 0.07
Thanks, Mike!
Hi guys, I switched scanning delay times from 1 (before Ident) and 10 (after Ident) to 5 and 20. I haven't seen any double entries after a few hours of scanning.SymbolTime varies from 0.04 to 0.06.
73 Kind regards
Herman Wijnants My logblog Belgium editor fmlist.org
Op donderdag 14 december 2023 om 13:33:44 CET schreef MikeFallon ***@***.***>:
Hi Clem, I'm using delay time.=5. The symbol rate is around 0.07
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Hi Clem, I've been running v4.1.3 for a few days and I have noticed that I get a lot of double entries when scanning where a mux appears in an adjacent block.as well as where it should be I am using all the same settings as I was with v4.1.2 where I didn't have this problem. I have tried selecting the filter and reducing gain but that hasn't helped. I am using a RSPDX.
Many thanks
Mike