Page 1 of 1

Re: Dual Watch in latest version openDM1801 2021.04.03

Posted: Mon May 10, 2021 11:16 pm
by VK3KYY
OK

I'll need to investigate why its not working.

One change since January is that Dual Watch now operates in Eco mode.

You could try disabling Eco mode and see if the bug still exists.

Re: Dual Watch in latest version openDM1801 2021.04.03

Posted: Tue May 11, 2021 7:19 am
by VK3KYY
trengking wrote:
Tue May 11, 2021 7:10 am
Very well,

I'll try disabling the eco mode. I'll come back to give you feedback.
Thanks mate, cheers.
OK.

Re: Dual Watch in latest version openDM1801 2021.04.03

Posted: Tue May 11, 2021 7:48 am
by VK3KYY
trengking wrote:
Tue May 11, 2021 7:26 am
Oops..unfortunately after trying to set eco mode to zero (0), analog transmissions still not detected in Dual Watch in April's release.
It's not a big deal though, I personally prefer the eco Mode in April's release, it is super nice :D

But if there is chance to fix this in the future, it will be super nice even more :D no insist though, thankyou for such incredible efforts to keep this project so great.

Cheers.

OK.

Well, at least I know it's not the Eco levels causing the problem ;-)

Re: Dual Watch in latest version openDM1801 2021.04.03

Posted: Tue May 11, 2021 9:38 am
by G4EML
Another change was the addition of adjustable scan dwell time. It might be worth increasing the dwell setting to see if that has an effect.

Re: Dual Watch in latest version openDM1801 2021.04.03

Posted: Tue May 11, 2021 4:19 pm
by G4EML
I have confirmed the problem with Dual Watch is due to the introduction of adjustable Scan Dwell times.

The Dual Watch code sets a fixed dwell time of 135 ms for the first pass but on subsequent passes it tries to use the adjustable Dwell time, however this doesn't appear to be initialised correctly when Dual Watch is selected. (I suspect it probably defaults to zero which would not allow time to receive anything).

The Dwell time is not really relevant for Dual watch, so using a fixed Dwell time of 135ms probably makes sense.

If you are building your own code from source you need to change line 2352 in uiVFOMode.c
from:-

uiDataGlobal.Scan.timerReload = uiDataGlobal.Scan.stepTimeMilliseconds;

to:-

uiDataGlobal.Scan.timerReload = 135; //use a fixed value of Dwell for Dual watch


I have not confirmed it but there may be a work around for those of you that cannot rebuild from source.

Set the Scan Dwell in the Options Menu to 150ms.
Start and stop a frequency scan in VFO Mode. This should initialise the variable correctly.
Start the Dual Watch.


Colin G4EML