New Model #6425
closedRetevis RT95
0%
Description
Request that the Retevis RT95 is supported.
Files
| Retevis_RT95_Capture.zip (158 KB) Retevis_RT95_Capture.zip | Capture of radio read/write | ||
| Data_sent&received_using_RT95_software.dat (44.7 KB) Data_sent&received_using_RT95_software.dat | Data read/write saved in the RetevisRT95 software format | ||
| 20200522_anytone778uv.py (30.1 KB) 20200522_anytone778uv.py | |||
| retevis.jpg (36 KB) retevis.jpg | Error message screenshot. | ||
| retevis1.jpg (20.4 KB) retevis1.jpg | |||
| error message RT95.jpg (84.9 KB) error message RT95.jpg |
Updated by Marco 1891 almost 6 years ago
- File RT95-programming-software.zip added
- File Retevis_RT95_Capture.zip Retevis_RT95_Capture.zip added
- File Data_sent&received_using_RT95_software.dat Data_sent&received_using_RT95_software.dat added
Good morning, I have this radio (Retevis RT95 aka Anytone AT-778UV aka CRT Micron) and I would like it to be supported in Chirp as soon as possible. I'm not a programmer, and I would never know how to develop. But I was able to capture the data transited between the radio and the original software. Attached is the capture file, the read capture file, the RetevisRT95 program I used and the relative test file .dat related to the capture made.
For the capture I used USBPcap 1.2.0.4
I hope someone more learned than I can analyze the data collected and start the radio support process. I also hope to have done my little part well as far as possible. Thank you.
Updated by Steve Krzysiak over 5 years ago
I'm curious how the dev process works in regards to whether someone is actively working on something. If someone is working on this please update this ticket or tell me where I can reference who is working on what. I am thinking about getting an rt95 and if no one else is working on this I'd like to take a stab at it.
Updated by Dan Smith over 5 years ago
- File deleted (
RT95-programming-software.zip)
Updated by Dan Smith over 5 years ago
- Chirp Version changed from 0.4.0 to daily
I have deleted the stock software upload from Marco. It's not appropriate to post licensed software (even if it is freely available here). It exposes the CHIRP website and community to potential action by the owners.
Steve, I do not know of anyone working on this (although you might check with Jim Unroe first). In general, you should join the dev mailing list and ask if someone is working on it if you want to know.
Updated by Derek Haden over 5 years ago
Dan Smith wrote:
I have deleted the stock software upload from Marco. It's not appropriate to post licensed software (even if it is freely available here). It exposes the CHIRP website and community to potential action by the owners.
Steve, I do not know of anyone working on this (although you might check with Jim Unroe first). In general, you should join the dev mailing list and ask if someone is working on it if you want to know.
I too would be interested in offering help here.
I have to say upfront I'm no programming genius.
However can offer enthusiasm if nothing else.
The RT95 is a nice user friendly rig.
Updated by Bernhard Hailer over 4 years ago
- Status changed from New to Feedback
- Target version set to chirp-legacy
If you wish to contribute to Chirp, please review the Wiki: Developers. Thanks!
Updated by Joe Milbourn over 4 years ago
- File 20200522_anytone778uv.py 20200522_anytone778uv.py added
I think the new AnyTone 778UV driver will support his radio, but the current version won't automatically detect it. However, I don't have this model to hand to try it out.
If you, or anyone else, would be willing to have a go a very experimental driver is attached - 20200522_anytone778uv.py. To load it into your chirp:
Download 20200522_anytone778uv.py and put it somewhere convienent, doesn't matter where.¶
Start Chirp and select 'Enable Developer Functions' from the 'Help' menu¶
From the 'File' menu select 'Load Module' and browse to wherever you saved 20200522_anytone778uv.py and select it.¶
The chirp window will go red - that's OK.¶
With your radio connected, choose 'Download from radio' from the 'Radio' menu, and specify your serial port. Choose 'Retevus' as the manufacturer, and 'RT95' as the model, then hit OK.¶
Chirp will warn you that this is an experimental driver, say yes if you want to continue.¶
Hopefully, you'll see the 'Cloning from radio...' progress bar, and after a while you'll see all your memories in chirp. If you see an error, please attach a screenshot here.¶
Either way, please post your results.
Thank you!
Updated by Derek Haden over 4 years ago
- File retevis.jpg retevis.jpg added
Joe,
many thanks for taking the time to do this.
I tried the driver using the latest version of chirp 20200521.
Error message
"Unable to load modlue:invalid syntax(2020522_anytone778uv.py, line 1).
Screenshot attached.
Hope that helps.
Updated by Derek Haden over 4 years ago
- File retevis1.jpg retevis1.jpg added
Here is a screenshot of the about screen.
Updated by Michele IZ2EAS over 4 years ago
- File error message RT95.jpg error message RT95.jpg added
Hello,
tried it and managed to load the driver, but the radio is still not responding.
I am attaching the screenshot of the error message received.
73,
Michele
Updated by Joe Milbourn over 4 years ago
Derek Haden wrote:
I tried the driver using the latest version of chirp 20200521.
Error message
"Unable to load modlue:invalid syntax(2020522_anytone778uv.py, line 1).
Thanks Derek - don't suppose you accidentally saved the HTML version of that python file? I think you need to click the link, then select download from the new page.
Updated by Derek Haden over 4 years ago
Joe
Definitely saved the .py file.
I opened the file with bluefish editor to look at what the error might be (no genius at programming).
Here's what the line reads
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Hope that helps.
Updated by Michele IZ2EAS over 4 years ago
Michele IZ2EAS wrote:
Hello,
tried it and managed to load the driver, but the radio is still not responding.
I am attaching the screenshot of the error message received.
73,Michele
I tried again and I should have done some mistake, since now it is working correctly (apparently).
Thanks !
73, Michele
Updated by Derek Haden over 4 years ago
Joe
I have a simple mind, and realised that the py file name contains the version number 20200522, but the latest version of chirp is 20200521.
So out of curiosity I changed the .py file name to match the chirp version.
Now the py file loads.
However downloading from the radio fails, it appears to start and the rig displays PC Mode, but after a few seconds gives up.
So close
Thanks again.
Updated by Joe Milbourn over 4 years ago
I tried again and I should have done some mistake, since now it is working correctly (apparently).
That's awesome, thanks Michele.
Updated by Joe Milbourn over 4 years ago
I have a simple mind, and realised that the py file name contains the version number 20200522, but the latest version of chirp is 20200521.
So out of curiosity I changed the .py file name to match the chirp version.
Now the py file loads.
However downloading from the radio fails, it appears to start and the rig displays PC Mode, but after a few seconds gives up.
Thanks Derek, looks like you've somehow got the HTML version of the python file, which chirp can't understand.
Try downloading from https://chirp.danplanet.com/attachments/download/5613/20200522_anytone778uv.py and loading that into chirp. Shouldn't be any need to change the filename.
Updated by Derek Haden over 4 years ago
Update to my last comment.
I think the filename change was a fluke, I think it just fooled chirp into not showing the error message.
Is there a way of deleting the module and trying from fresh?
Updated by Derek Haden over 4 years ago
Joe Milbourn wrote:
I have a simple mind, and realised that the py file name contains the version number 20200522, but the latest version of chirp is 20200521.
So out of curiosity I changed the .py file name to match the chirp version.
Now the py file loads.
However downloading from the radio fails, it appears to start and the rig displays PC Mode, but after a few seconds gives up.Thanks Derek, looks like you've somehow got the HTML version of the python file, which chirp can't understand.
Try downloading from https://chirp.danplanet.com/attachments/download/5613/20200522_anytone778uv.py and loading that into chirp. Shouldn't be any need to change the filename.
OK I now have what looks like the right file. it loads without error.
However when I try to download from radio, the rig goes into PC Mode for a second or 2, then goes back to it's normal operation, and nothing is downloaded.
I have tried removing Chirp and reloading, to no avail.
Can the module be removed? and start again?
Updated by Derek Haden over 4 years ago
BTW I am using the Linux based version.
Updated by Derek Haden over 4 years ago
And FINALLY!
Bit of a saga, but here goes.
The py file appeared to load correctly, however I could not find Retevis RT95 listed, and assumed that I had to use the Anytone 778UV option, which didn't work.
I then noticed that the CRT Micron wasn't showing either, so to my simple mind the file was loading but not installing the driver.
I was right
After looking at the py file, I noticed the check for Python-Future around line 38, so I checked the log file, and it had a warning that Python-Future was not available.
So I manually installed python-future
sudo apt-get install python-future.
It now works beautifully.
I guess the next move is to get the driver installed into Chirp by default?
Updated by Joe Milbourn over 4 years ago
Derek Haden wrote:
It now works beautifully.
I guess the next move is to get the driver installed into Chirp by default?
Awesome, thanks for persisting Derek. Yes, next step is get a patch included.
Updated by Derek Haden over 4 years ago
Joe, your efforts will be very much appreciated by the many RT95, 778UV and Micron owners.
The stock software is truly horrid, you cannot even copy and paste, or move memories up and down.
Thanks for your efforts.
Updated by Bernhard Hailer over 4 years ago
- Status changed from Feedback to Resolved
Patch submission in progress.
Updated by Bernhard Hailer over 4 years ago
- Status changed from Resolved to Closed
Implementation appears to be complete.