Release Candidate (2022 02 15)

[VK3KYY]

There is a new "Release Candidate" version available

downloads/ReleaseCandidate_20220215/firmware/

To use this version you must also use the latest CPS

downloads/ReleaseCandidate_20220215/Ope ... .12.01.exe

and upload your DMR ID database

If you don't update your database it will not work with this new version.
This change to DMR ID database was required to fix some crash bugs.

Other changes since the last version

* Hotspot battery level is updated to show the correct value
* Hotspot battery level can be displayed as % of V using the same setting for battery display on the Channel and VFO screens.
* Bug fix entering dates in the month of February.


Thanks to Daniel F1RMB for all these changes.




My hope is that this version will be stable for 99.99% of users and it can become a full release, at which point the source code will also be released.
The firmware will never be 100% stable because we push the boundaries of whats possible using this radio hardware, including far more features than the official firmware and far bettery battery life etc.

[m1dyp]

thank you

[OE2WHP]

Hi,

did some long term testing withthe prior beta release and can now confirm that the reboots only occur when CC filter is off (in other words when CC scan is on). Small detail, whenever a reboot occured, the TS/CC settings both changed automatically from "TS on / CC off" to "TS off / CC on".

I will now update to this release and repeat the tests.

73 de OE2WHP

[py2kk]

Thanks.

[W1CY]

Thanks for the new release candidate.
I really appreciate your work on enhancing this firmware.

[BG5GNN]

谢谢！

[VK3KYY]

Hi,

did some long term testing withthe prior beta release and can now confirm that the reboots only occur when CC filter is off (in other words when CC scan is on). Small detail, whenever a reboot occured, the TS/CC settings both changed automatically from "TS on / CC off" to "TS off / CC on".

I will now update to this release and repeat the tests.

73 de OE2WHP

This release did not make any changes in relation to CC Filter/Scan

If the problem is definitely caused by disabling CC filter, we'll need to fix this problem and produce another release candidate


What signal were you listening to when this problem occurred, was it an amateur radio repeater or something commercial, was there traffic on both timeslots ?

I've not been able to reproduce this crash when listening to my local amateur radio repeater.

BTW.
The reason the settings get turned off when the radio is rebooted, is becasue they don't immediatly get saved. In general settings are only saved when you turn the radio off. For technical reasons the settings can't be saved immediatly because it causes the memory chips to literally wear out.

On the RD5R the settings are saved immediatly becuase it lacks the power management hardware in the other radios, and the EEPROM will eventually wear out in that radio with sustained use and multiple changes to settings or channel or frequency

[oh1fss]

The reason the settings get turned off when the radio is rebooted, is becasue they don't immediatly get saved. In general settings are only saved when you turn the radio off. For technical reasons the settings can't be saved immediatly because it causes the memory chips to literally wear out.

On the RD5R the settings are saved immediatly becuase it lacks the power management hardware in the other radios, and the EEPROM will eventually wear out in that radio with sustained use and multiple changes to settings or channel or frequency

I would prefer that on RD5R the saving would happen only on a command, not automatically. I don't want to destroy my memory chips.

Or perhaps on RD5R there could be a separate power off option in the menu, which would save the settings - it would allow the suspend feature on RD5R as well.

[VK3KYY]

The reason the settings get turned off when the radio is rebooted, is becasue they don't immediatly get saved. In general settings are only saved when you turn the radio off. For technical reasons the settings can't be saved immediatly because it causes the memory chips to literally wear out.

On the RD5R the settings are saved immediatly becuase it lacks the power management hardware in the other radios, and the EEPROM will eventually wear out in that radio with sustained use and multiple changes to settings or channel or frequency

I would prefer that on RD5R the saving would happen only on a command, not automatically. I don't want to destroy my memory chips.

Or perhaps on RD5R there could be a separate power off option in the menu, which would save the settings - it would allow the suspend feature on RD5R as well.

It would probably take several years of continuous use 2 wear out the chips.

Settings are only updated when there is a change and also there is a delay time to prevent constantly updating.

[OE2WHP]

What signal were you listening to when this problem occurred, was it an amateur radio repeater or something commercial, was there traffic on both timeslots ? I've not been able to reproduce this crash when listening to my local amateur radio repeater.

I did all tests with the same settings. RX, TG9 on our local DMR repeater (OE2XZR). Promiscuous mode on. CC off. Occasionally pushing PTT (@250mW) for 2-3 seconds to open the repeater. Reboot always occured within 48 hours.

73 de OE2WHP