Moving Forward
Added 2025-06-09 17:37:06 +0000 UTCHi everyone,
I wanted to take a moment to share some thoughts on the current direction of development and what's coming next. There are several exciting possibilities on the horizon, and I’m carefully evaluating how best to move forward.
At the forefront is the Radtel 880, which is currently in my sights for nicFW treatment. However, progress is being slowed by a lack of publicly available technical documentation, specifically around the internals, GPIO mappings, and other key hardware details. While all of this can be reverse-engineered, it represents a significant investment of time and effort.
Interestingly, Radtel has indicated that they may release official documentation in the future. Their track record gives this some credibility, as they’ve already published substantial technical info for other models. If they do follow through, any prior reverse engineering efforts might ultimately be redundant. It's a bit of a dilemma.
In the meantime, I’m considering revisiting the H3 and 890 models. With the 900 receiving several updates and new features, it could be highly beneficial to backport or integrate some of those improvements into the earlier radios. This could bring meaningful enhancements without waiting on uncertain timelines.
Additionally, I’ve been exploring Avalonia, a cross-platform development framework with modern UI capabilities, similar in style to WPF. Its ability to deploy across Windows, Linux, and macOS is a compelling feature. I’m considering a complete rewrite of the programmer app using Avalonia, consolidating all radio support into a single, unified application. One app, one consistent UI; across all platforms and devices.
So as you can see, there’s plenty to keep me busy! I’m hopeful that Radtel will release the data we need, but I’m prepared to take on the heavy lifting if they don’t.
Thanks as always for your continued support, your enthusiasm and encouragement make all the difference.
Comments
Yes I had it already, but thank you for thinking of me.
Marcus Dudley
2025-06-26 12:49:11 +0000 UTChttps://t.me/RadtelRadio/31917?single (dont know if you have this)
Ramon Martinez Palomares
2025-06-26 12:29:25 +0000 UTCCan you please have some patience, I'm not Superman? Thank you.
Marcus Dudley
2025-06-18 21:11:04 +0000 UTCHi Marcus, when you will update also the RT-890 with the last features and improvements? Thanks.
Salvatore Todaro
2025-06-18 20:00:13 +0000 UTCInteresting, from my perspective this would be a lot of work for a feature hardly anyone would use, but, I can compromise on the PTT-ID side of things. It wouldn't be too hard to introduce an "escape code" for PTT-ID that would change the nature of the tone, from DTMF to single tone, and numbers in the sequence determine the amount of "bips" and the frequency, thus allowing you to create your own "chirp" as you said. I think I can pull that off.
Marcus Dudley
2025-06-17 21:26:18 +0000 UTCREQUEST: H3: Ability to select from a variety of friendly "chirp" sounds (or even create your own) for BOT/EOT. And ability to set independently (so, the tones could be different on BOT vs EOT). REASON: motorcycle/ATV riding. When riding, you cannot always tell you've hit PTT, so a BOT chirp is _critical_. PTT ID dial tones are boring and harsh, though that is what I use for now. But it would be ideal if we can customize this a bit! In larger groups with distinct little sounds for each person, it also helps as a hint for who is talking. Honestly, I don't even need to Tx/broadcast the tone, I just need to hear it on my own end for a split second so I know I have hit PTT _before_ BOT. But that might be different functionality/feature altogether. Ultimately, that is what I am after! A better BOT experience.
roachslayer
2025-06-17 16:56:12 +0000 UTC