Page 1 of 2

Release Candidate (2022 02 23)

Posted: Tue Feb 22, 2022 10:32 pm
by VK3KYY
There is a new Release Candidate available

Firmware files downloads/ReleaseCandidate_20220223/firmware/

CPS downloads/ReleaseCandidate_20220223/Ope ... .23.01.exe

The firmware changes are:

* Fix to hotspot mode where occasionally the first LC frame is not sent to MMDVMHost, this can include signals which are 'late entry', i.e the GD77 did not hear the beginning of the transmission
* Fix per channel DMR ID override , which was not functioning on the VFO's

CPS change is to add the per channel DMR ID to the VFO screen


Thanks to Daniel F1RMB for all of these bug fixes.


I am hoping that perhaps this may be the final Release Candidate and will become the next "Stable" release if no serious problems are reported in the next 2 weeks.

The CPS has been tested under Windows 10 and Windows 11, in both cases on X86 machines the Com port driver installed OK and the CPS was then able to recognise the radio without the operator needing to select the radio

If the CPS can't find the radio, because a generic driver has been installed by Windows, the CPS will prompt the operator to select the com port of the radio.

Re: Release Candidate (2022 02 23)

Posted: Wed Feb 23, 2022 12:27 am
by W1CY
Thanks, as always.
I will load the code later tonight.
Cheers!

Re: Release Candidate (2022 02 23)

Posted: Wed Feb 23, 2022 2:08 am
by Ik0nwg
thank you
Ciao Roger

Re: Release Candidate (2022 02 23)

Posted: Wed Feb 23, 2022 8:52 am
by m1dyp
thank you

Re: Release Candidate (2022 02 23)

Posted: Wed Feb 23, 2022 9:30 am
by EA1MU
Muchas gracias.

Re: Release Candidate (2022 02 23)

Posted: Wed Feb 23, 2022 10:21 am
by SQ7PTE
Yes. I must say that there is a difference in the efficient, quick connection of the radio to the HotSpot. The response time is faster.
Now, when the correspondent finishes transmitting, you can press PTT and go in - it works.
Thanks to Daniel for the amendment.

P. S.
I have never had a problem with restarting the radio or HotSpot.

Re: Release Candidate (2022 02 23)

Posted: Thu Feb 24, 2022 6:21 pm
by PU2RMT
For now everything working fine, no reboots this time.

Just a doubt, when I'm scanning a certain frequency range in dmr mode and it finds a signal that I don't know what type of signal it is, if I press SK2 to activate the monitor mode it doesn't enable the function, while it's with the active scan, in this case I have to stop the scan at the frequency found and then press sk2 to find out what signal it is, my doubt is this, if this is how it is done? Or is there some other method I'm not aware of?

Thanks and congratulations to the developers for the excellent work!! 73

Re: Release Candidate (2022 02 23)

Posted: Thu Feb 24, 2022 7:03 pm
by F1RMB
Hi,

You have to keep the SK2 pressed as long as you want to use the monitor mode.
It will start detecting the DMR, and if it fails, it will switch to FM.


Cheers.
---
Daniel

Re: Release Candidate (2022 02 23)

Posted: Thu Feb 24, 2022 7:34 pm
by WRPI448
So, as soon as the DMR signal drops, it switches to FM. Hence the static

Re: Release Candidate (2022 02 23)

Posted: Thu Feb 24, 2022 7:43 pm
by F1RMB
No, if monitor mode correctly detected DMR, it will stick to that settings until you release SK2.