[chirp_users] Can't program or read Retevis RT-22

[Jaye Mathisen]

OK, eventual 100% success.

We started up chirp, loaded the module, and when we hit upload it would give
us a communication error.  Hit upload again wihout changing anything, and it
would upload the second time.  Unfortunately, I forgot to save that debug
log, and when we closed and reopened chirp again and loaded the module, it
seemed to work.  I include the debug.log file that was in the folder, but
I'm thinking I remember reading that chirp wipes the file on each startup,
so this may not have relevant info.

I did not have any "older" radios from last year to test with to make sure
it's still compatible.  I will try to find one.

So I think we're good for now.

Thanks for the quick response and the help, it is much appreciated.

J.



-----Original Message-----
From: chirp_users-bounces at intrepid.danplanet.com
[mailto:chirp_users-bounces at intrepid.danplanet.com] On Behalf Of Jim Unroe
Sent: Thursday, September 27, 2018 4:53 AM
To: Discussion of CHIRP <chirp_users at intrepid.danplanet.com>
Subject: Re: [chirp_users] Can't program or read Retevis RT-22

On Wed, Sep 26, 2018 at 11:35 PM, Jaye Mathisen <mrcpu at lilpantry.com> wrote:
>
> Read through the last couple months of archives, didn’t see anything
> directly related.
>
>
>
> Using the latest chirp, I cannot program or read from a retevis RT-22.
> Used to clone them all the time, then we didn’t need any for a while, got
> a new batch, and all I get when I try to read is an “unknown
> identification string”, and if I try to download programming from the img
> file we were using before, I get an error about 5 tries, but haven’t been
> able to get that to come up again.
>
>
>
> If I load the RT22 software downloaded from retevis, it fires right up,
> and can at least read the radio config, I haven’t tried writing it again.
>
>
>
> I programmed some RT22’s about 2 months ago, and didn’t have any of these
> issues, so I’m not sure if it’s a retevis firmware change, or what.

This RT22's response to the clone request is not what CHIRP expects.

Save the attached file to where you keep you CHIRP Radio Images
(*.img) files. Enable "Developer Functions" in CHIRP and then use File
-> Load Module to load the attached test driver module. Then test and
report back if it works.

Jim KC9HI

-- 



This electronic message may contain information that is
privileged, 
confidential or otherwise protected from disclosure to anyone other
than 
its intended recipient(s). Any dissemination or use of this electronic

message or its contents by persons other than the intended recipient(s) is

strictly prohibited, and may be unlawful. If you have received this 
electronic
transmission in error, please reply immediately to the sender so 
that we may
correct our internal records, and then delete the original 
message.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debug.log
Type: application/octet-stream
Size: 128252 bytes
Desc: not available
Url : http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180927/4c4b08c4/attachment.obj