CHIRP

RT22S actually quite different from RT22.

RT22S has 22 channels instead of RT22's 16, plus has compander and scrambler options for each channel location.

I am curious on the RT22 model that works. At one point in time it worked now I get the dredded "The radio did not accept program mode after five tries.
Check you interface cable and power cycle your radio." Tried different ports, tried different (Windows 10) desktops, and iMAC. Awaiting on another cable to see if that works. Any replies helpful.

Kenny Madsen wrote:

I am curious on the RT22 model that works. At one point in time it worked now I get the dredded "The radio did not accept program mode after five tries.
Check you interface cable and power cycle your radio." Tried different ports, tried different (Windows 10) desktops, and iMAC. Awaiting on another cable to see if that works. Any replies helpful.

Kenny,
I am of the impression that this radio's hardware/firmware has been updated between RT22 production runs. I have noticed that the radio's casing was updated from the rounded style identical to the WLN and similar versions to a slightly more angular styling, so perhaps there were internal changes made at that time or at some other point in its lifecycle.

From reading various sources, including this site, the firmware change (affecting Chirp) might be as simple as having added an exclamation point to the radio ID string. It'd be good if someone could test that theory (or show that it's been tested). Unfortunately it might mean having two options to choose from (within Chirp) if you are programming an RT22 - "old" vs "new" versions.

Thank You Art - Right now we need these but are sending them back for a different model.

Any further updates Kenny or Art? I am running into the same issue with out RT22 models. We have bought 20 more and are trying to program them all the same from an original RT22 we bought about a year ago. The older model works perfectly (downloading and uploading) but none of the new ones will take an upload. It's pretty frustrating that the Dev's can't send out an update to fix this.

Thanks for writing Luke. No - No updates. I basically told them to tank these and buy Kenwoods (3230). They are much easier to program albeit more expensive. Truly you get what you pay for. And you don't need a cable. https://www.amazon.com/Kenwood-TK-3230DX-Compact-Durable-Business/dp/B0068U5OLG I burned out on a lot of time with these.

If you do get a resolution on this, I would be interested. I can program my RT22's but not the new RT22S's.

Thanks!

Here is a link to RT22S software and worked for me:

https://www.retevis.com//resources_center/software/RT22S-softwareV1.41.zip

I am beginning to examine the RT22S more closely, having just obtained a pair. It is sold worldwide with a variety of channels locked in memory, and I am thinking there might have to be programming software that would permit changes to the frequencies. Until then, in the USA users are stuck with FRS preset frequencies and power levels, and the software allows editing of only adjunct features like CTCSS and DCS tones and a few radio default settings.
Another thing - it appears that these units actually may have 32 channel capability. That number makes more sense than 22.
The RT22S programming software's data file is not as straightforward and readable as the RT22 data file. I will take a closer look at that soon as well.

The RT22S is constrained to 22 channels as delivered, but I now have mine loaded with 32 memory channels using Retevis software. Just make a couple changes to settings.ini. I am still working through the data file; bear with me I am new to this.