DCS Codes

[K3SAD]

There haven't been any recent threads that I've noticed, pardon if that's untrue.

Previous versions of the CPS had a very convenient glitch that allowed tabbing into the Rx and Tx tones and entering non-standard DCS codes for non-standard repeaters, which made the firmware absolutely ubiquitous. I recently upgraded to the latest and it appears that glitch was fixed; and although somehow it hasn't yet screwed up my previously entered DCS codes, it displays random wrong things in previously stored channels threatening to change them the next time I write to the radio, which is a source of heartburn. Is there a way for someone to restore the supremely handy glitch that allowed tabbing into the dropdown box and entering whatever you want, and probably by way of side effect display the actual DCS codes stored under those channels?

[VK3KYY]

There haven't been any recent threads that I've noticed, pardon if that's untrue.

Previous versions of the CPS had a very convenient glitch that allowed tabbing into the Rx and Tx tones and entering non-standard DCS codes for non-standard repeaters, which made the firmware absolutely ubiquitous. I recently upgraded to the latest and it appears that glitch was fixed; and although somehow it hasn't yet screwed up my previously entered DCS codes, it displays random wrong things in previously stored channels threatening to change them the next time I write to the radio, which is a source of heartburn. Is there a way for someone to restore the supremely handy glitch that allowed tabbing into the dropdown box and entering whatever you want, and probably by way of side effect display the actual DCS codes stored under those channels?

There were no code changes in the latest CPS, the only changes were to the languages XML data files, which contain the UI text.

It's more likely that if you are seeing a change, it's something to do with a Microsoft update to either your PC or to the PC we compiled the CPS on.

Did you try reinstalling the previous CPS version. English users have no absolute need to use this very latest version

[K3SAD]

It's more likely that if you are seeing a change, it's something to do with a Microsoft update to either your PC or to the PC we compiled the CPS on.

Did you try reinstalling the previous CPS version. English users have no absolute need to use this very latest version

Thanks for the reply! No, I didn't try that - my previous mission was to chase down the APRS rabbithole and enjoy the improvements y'all have made in that regard since I'd originally installed it. Funny thing is, I was trying to load it onto a 2nd radio and I had some hardware changes (actually using a remote work Windows server via my personal Mac at home) so I decided to start from scratch. My original radio worked great but had a weird glitch (no doubt of my own doing) that caused it to take a few minutes to start up. When I finally overcame all my local issues and got it loaded onto the second radio, it started up immediately and the codeplug from the first went right on with no problem. I instantly swapped in the first radio and dumped in the new firmware, and it too fired right up the way it should. I was so stoked!

So that led me into my rabbithole playing with APRS, which I managed to get working whenever I had the APRS frequency up, and that was enough on that project. That's when I noticed the DCS code issue and worried that I was going to undo the best aspect of this radio and this software. I'm not sure what version I used first, I'll go looking and find the archive and see if I can load them both. I like the APRS improvements but the highest concern is actually talking with the radio.

[F1RMB]

Hi,

BTW, it wasn't possible to use anything else than the 83 "standard" DCS codes, see, the code can't permit that, from the beginning (even if the CPS had a bug that permitted to enter it, which I can't remember).
In the CPS, the unsupported DCS codes were removed from the drop-down lists on May 2021.


Cheers.
---
Daniel

[K3SAD]

Not sure about timing. I downloaded a firmware and a CPS in late summer of last year, and fought to get it installed because reading directions has generally been a blind spot for me. Using whatever that was, I loaded the firmware onto the machine at work and got it mostly functional, aside from the startup lag. Sometime late fall or early winter I was counting my woes about not being able to connect to local GMRS repeaters, when I stumbled upon the bug that allowed me to tab into the field, type whatever I wanted and save it, and it worked. The TYT moved up three slots in my preferred radio selection that day.