Stable config #2
Replies: 1 comment 3 replies
-
|
Good to hear. Unfortunately, I learned the hard way too. My first DM-32 was the HR Vocoder version back in January '25 with 0.29 firmware 😄 No surprise that 1.28 CPS mixed up things in such a way it was difficult to tell if CPS or the radio was to blame. Mostly it is CPS but the firmware is not polished so errors are being sent to CPS too I believe. The guys at RT Systems know more than I do how messed up the firmware/CPS is. Using CPS to bulk configure helps but amending (within the radio menu) after upload is the only way to ensure it will actually do what you want. Shame really, but at least Baofeng are improving CPS albeit very slowly 😉 Some issues remain from day 1. As it stands (for me) any changes are performed within the radio and only occasional back ups made with CPS. Seemingly a configured working radio will back up ok but it's still worth checking that scans lists work, no talkaround on repeaters or no TX has somehow got checked! Despite this I really enjoy using the DM-32 got quite a few for testing 😉 73 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Thank you so much for this collection. My new DM-32UV had issues from the factory and wouldn't reliably read/write info. The latest firmware (49) and CPS (50) solved most of the issues for me, and I now seem to have a functional radio. Reads are still not working consistently which is strange...
Beta Was this translation helpful? Give feedback.
All reactions