Bug #9353

RT98 chirp issue, two versions of radio?

Added by Ken Hansen 12 days ago. Updated 3 days ago.

Status:In Progress Start date:09/06/2021
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:RT98V

Description

I just built up a go-box with the Retevis RT98 2M mobile radio. I installed Chirp (chirp-daily-20210830-installer.exe) on a Win 11 laptop (a supposedly supported model), and using the Retevis supplied programming cable.

Steps taken:
Install chirp
Attach prog cable to laptop & radio
Start chirp
Select "download from radio"
Select correct com port, mfg (Retevis) and model (RT98)
It attempts to download from radio, and it halts, telling me:

"Radio version not in allowed list for Retevis RT98: 000: 49 41 54 2d 37 37 39 56 IAT-779V
008: 01 56 31 30 30 00 00 06 .V100..."

Retevis offers two versions of programming software for this radio, my radio, with serial number starting 1907* programmed fine with v1.01 of Retevis software.

retevis_rt98_at-779v.py (47.9 kB) Jim Unroe, 09/06/2021 02:34 pm

Download.png (42.9 kB) Jim Unroe, 09/07/2021 01:08 pm

CHIRP RT98 Error.png - Screen Grab RT98 N2VIP (227.3 kB) Ken Hansen, 09/07/2021 02:24 pm

debug.log - RT98 Debug file (30.9 kB) Ken Hansen, 09/07/2021 03:20 pm

retevis_rt98_at-779v.py - supports 7 character model names (47.9 kB) Jim Unroe, 09/07/2021 05:30 pm

debug.log (306.4 kB) Ken Hansen, 09/07/2021 07:24 pm

SaveAs.png (38.5 kB) Jim Unroe, 09/08/2021 04:40 am

debug.log - after read of radio, bandlimitfrequencies error (306.5 kB) Ken Hansen, 09/09/2021 01:07 pm

retevis_rt98_at-779v_blf_hack.py (48 kB) Jim Unroe, 09/09/2021 02:41 pm

debug.log - Debug file for successful load (314.1 kB) Ken Hansen, 09/09/2021 08:05 pm

Embedded Message.png - Embedded Message (54.5 kB) Ken Hansen, 09/09/2021 08:06 pm

Retevis_RT98_20210909.img - contents of successful read (15.7 kB) Ken Hansen, 09/09/2021 08:07 pm

RT98 V1.01 Embedded Message.png (12 kB) Jim Unroe, 09/10/2021 04:30 am

retevis_rt98_at-779v.py (48.7 kB) Jim Unroe, 09/10/2021 09:14 am

Retevis Embedded Message Screen.png - Retevis V1.01 Embedded Message (60.4 kB) Ken Hansen, 09/10/2021 09:25 am

Retevis_RT98_Scan_CO.img - Scan set CO (15.7 kB) Ken Hansen, 09/10/2021 09:39 am

Retevis_RT98_Scan_SE.img - Scan set at SE (15.7 kB) Ken Hansen, 09/10/2021 09:41 am

Retevis_RT98_Scan_TO.img - Scan set at TO (15.7 kB) Ken Hansen, 09/10/2021 09:41 am

Retevis_RT98_VFO.img - V/M set to VFO (15.7 kB) Ken Hansen, 09/10/2021 09:41 am

Retevis_RT98_MR.img - V/M set to MR (15.7 kB) Ken Hansen, 09/10/2021 09:41 am

Retevis_RT98_VFO.img - Radio in VFO mode (15.7 kB) Ken Hansen, 09/10/2021 02:01 pm

Retevis_RT98_MR.img - Radio in MR mode (15.7 kB) Ken Hansen, 09/10/2021 02:01 pm

Retevis_RT98_Scan_CO.img - Scan set to CO (15.7 kB) Ken Hansen, 09/10/2021 02:01 pm

Retevis_RT98_Scan_SE.img - Scan set to SE (15.7 kB) Ken Hansen, 09/10/2021 02:01 pm

Retevis_RT98_Scan_TO.img - Scan set to TO (15.7 kB) Ken Hansen, 09/10/2021 02:01 pm

retevis_rt98_at-779v.py (49.2 kB) Jim Unroe, 09/10/2021 05:06 pm

RT98 Freq Out Of Range.png - Error message (6.3 kB) Ken Hansen, 09/14/2021 04:29 pm

debug.log - Log file when adding 146.700 to "frequency" on new channel (469 kB) Ken Hansen, 09/14/2021 04:29 pm

retevis_rt98_at-779v.py (49.2 kB) Jim Unroe, 09/14/2021 06:53 pm

History

Updated by Jim Unroe 12 days ago

  • Status changed from New to In Progress
  • Assignee set to Jim Unroe
  • Target version set to chirp-daily
  • Model affected changed from S/N 1907* to RT98V
  • Platform changed from Windows to All

Hi Ken,

Thank you for opening this issue. I have sent a message to Retevis to see if they can offer any insight as to why your radio is identifying itself as an AnyTone AT-779V. But I think you have discovered what the difference is between the earlier S/N:1907*********** radios and the newer S/N:20************* radios. Let me work up something for you to test. Hopefully the "identification" returned is the only thing that has been changed between the 2 serial numbers.

Jim KC9HI

Updated by Jim Unroe 12 days ago

Important Note: The current CHIRP support for the Retevis RT98 is based on the v1.02 programming software. We do not know what else besides the identification string was changed in the change from v1.01 to v1.02 so do not make any edits to the first successful download. Immediately save it, unedited, to a CHIRP Radio Images (*.img) file as a backup. Attach this unedited CHIRP Radio Images (*.img) file to this issue so I can compare this v1.01 image to my v1.02 images.

Read and understand the above before going any further

I have created a test driver module to test support the Retevis RT98V S/N:1907***********. Since I do not have access to a radio here, you must test it and let me know if it works properly with your radio.

The following explains how to load the test driver module for testing.

1 save the attached "retevis_rt98_at-779v.py" test driver module to a convenient location

Important: left click the file name and then click the "download" link on the following page that loads.

2 open CHIRP
3 click "Help" in the menu bar and enable "Enable Developer Functions"
4 click "File" in the menu bar and select "Load Module" in the list of selections
5 locate and load the file that was saved in step 1

The CHIRP background should now be red. Attempt to download from your radio. If it works (it should), attach the downloaded CHIRP Radio Images (*.img) file to this issue so I can compare it to a S/N:20************* image.

Note: This test driver module does not permanently change your CHIRP installation. If you close CHIRP and later on need to access your radio, you will have to load this test driver first.

Jim KC9HI

Updated by Ken Hansen 11 days ago

Jim,

I am struggling to download the linked file - if I click on it, i get taken to a webpage showing the 1375 lines of python code. If I "Save link as" I get a file with HTML all around the python code.

other options? Select all grabs the 1375 line numbers in front of every line of code.

Thanks,

Ken

Updated by Jim Unroe 11 days ago

Ken Hansen wrote:

Jim,

I am struggling to download the linked file - if I click on it, i get taken to a webpage showing the 1375 lines of python code. If I "Save link as" I get a file with HTML all around the python code.

other options? Select all grabs the 1375 line numbers in front of every line of code.

Thanks,

Ken

Like I stated above in the "Important" note between step 1 and step 2, "click the "download" link on the following page". The "Download" link is located at the top left, directly under my name.

Jim KC9HI

Updated by Ken Hansen 11 days ago

Jim,

Downloaded the .py file (thanks!), but I ran into the exact same problem - no change.

Start CHIRP, enable Dev mode, load module, background turns red, click radio, download from radio, correct com port, mfg and model, get beta warning, then after i click OK, same error message - see attached screen grab

Thanks,

Ken, N2VIP

Updated by Jim Unroe 11 days ago

Attach the debug.log please.

Jim

Updated by Ken Hansen 11 days ago

Here is the debug.log file, I hope this helps.

Thanks,

Ken, N2VIP

Updated by Ken Hansen 11 days ago

It looks like the RT-98 code is looking for a 5 character string (like RT98V), and your change added a seven character string(AT-779V)...

I bet "AT-77" would work (sorry, I just got curious and looked at the file, that's what it looks like to me):

[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: ver_response =
[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: 000: 49 41 54 2d 37 37 39 56 IAT-779V
008: 01 56 31 30 30 00 00 06 .V100...

[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: radio model: 'AT-77' version: 'V100'
[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: allowed_types = {'AT-779V': ['V100'], 'AT-779U': ['V100'], 'RT98V': ['V100'], 'RT98U': ['V100']}
[2021-09-07 16:20:27,459] chirp.ui.reporting - DEBUG: Reporting exception

Thanks,

Ken, N2VIP

Updated by Jim Unroe 10 days ago

Ken Hansen wrote:

It looks like the RT-98 code is looking for a 5 character string (like RT98V), and your change added a seven character string(AT-779V)...

I bet "AT-77" would work (sorry, I just got curious and looked at the file, that's what it looks like to me):

[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: ver_response =
[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: 000: 49 41 54 2d 37 37 39 56 IAT-779V
008: 01 56 31 30 30 00 00 06 .V100...

[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: radio model: 'AT-77' version: 'V100'
[2021-09-07 16:20:27,459] chirp.ui.mainapp - DEBUG: allowed_types = {'AT-779V': ['V100'], 'AT-779U': ['V100'], 'RT98V': ['V100'], 'RT98U': ['V100']}
[2021-09-07 16:20:27,459] chirp.ui.reporting - DEBUG: Reporting exception

Thanks,

Ken, N2VIP

Ken,

You can give that a try to get a download while I "fix" the issue with the length.

Jim

Updated by Jim Unroe 10 days ago

Here is a revised test driver which accommodates the longer model name length.

Jim

Updated by Ken Hansen 10 days ago

I will give it a try tonight, thanks!

Ken, N2VIP

Updated by Ken Hansen 10 days ago

Jim,

It worked fine - I realize you probably don't need it, but I included debug.log for review.

Happy to test further if needed, just let me know if more help needed to fully resolve this issue.

Thanks,

Ken, N2VIP

Updated by Jim Unroe 10 days ago

Ken Hansen wrote:

Jim,

It worked fine - I realize you probably don't need it, but I included debug.log for review.

Happy to test further if needed, just let me know if more help needed to fully resolve this issue.

Thanks,

Ken, N2VIP

Great. Don't forget to attach an unedited image from your radio. I will need it for testing.

Also, what I/we need to do is to compare the settings of the v1.01 factory software to the v1.02 factory software to see if there are any differences (something on one version but not on the other or different selection choices. Retevis tells me the difference is the v1.01 doesn't support the PMR and FreeNet versions like the v1.02 does. Hopefully that is the only thing.

Don't forget, I need an image from your radio before you mess around and try to edit anything.

Jim

Updated by Ken Hansen 10 days ago

Jim,

I want to help, but to read the radio, I need to enter developer mode, load the .py file you sent me, and when I read the radio successfully, I don't have the ability to save whatever was loaded (the save options are greyed out)

Right now I can only read the radio in the developer mode.

Updated by Jim Unroe 10 days ago

Ken Hansen wrote:

Jim,

I want to help, but to read the radio, I need to enter developer mode, load the .py file you sent me, and when I read the radio successfully, I don't have the ability to save whatever was loaded (the save options are greyed out)

Right now I can only read the radio in the developer mode.

That's not the case here. With the test driver loaded and after downloading from the radio I can either File -> Save or File -> Save As. Neither are greyed out. What happens if you use the CTRL-S keyboard shortcut?

Jim

Updated by Jim Unroe 10 days ago

I see 2 settings that are in the OEM v1.01 software that are not in the OEM v1.02 software.

The first is a "VFO/MR" setting which allows you to choose which mode that you want the radio in when the cloning process is done. Switching to VFO mode was disabled on the S/N:20************* radios. The radio operated in MR mode only. So the [V/M] button on the front panel of the radio is used switch between the display of the channel data by Frequency or Name. Does this work for switching between VFO and MR modes on the S/N:1907*********** radios?

The second is a "Frequency Scan" setting which allows the user to choose between the TimeOut (TO), Carrier Operated (CO) and SEarch (SE) scan types. The User Manual claims that the setting is covered by menu 17 in the radio. This is not the case for a S/N:20************* radio. My guess that this is only true on a S/N:1907*********** radio, right?

Jim KC9HI

Updated by Ken Hansen 9 days ago

Jim Unroe wrote:

Ken Hansen wrote:

Jim,

I want to help, but to read the radio, I need to enter developer mode, load the .py file you sent me, and when I read the radio successfully, I don't have the ability to save whatever was loaded (the save options are greyed out)

Right now I can only read the radio in the developer mode.

That's not the case here. With the test driver loaded and after downloading from the radio I can either File -> Save or File -> Save As. Neither are greyed out. What happens if you use the CTRL-S keyboard shortcut?

Jim

Jim,

Save and Save as are greyed out, Ctrl-S does nothing.

The attached debug.log file complains about "bandlimitfrequencies" at the very end of the file

Ken

Updated by Ken Hansen 9 days ago

Jim Unroe wrote:

I see 2 settings that are in the OEM v1.01 software that are not in the OEM v1.02 software.

The first is a "VFO/MR" setting which allows you to choose which mode that you want the radio in when the cloning process is done. Switching to VFO mode was disabled on the S/N:20************* radios. The radio operated in MR mode only. So the [V/M] button on the front panel of the radio is used switch between the display of the channel data by Frequency or Name. Does this work for switching between VFO and MR modes on the S/N:1907*********** radios?

Yes, by quickly pressing the "V/M" button my radio switches between MR and VFO

The second is a "Frequency Scan" setting which allows the user to choose between the TimeOut (TO), Carrier Operated (CO) and SEarch (SE) scan types. The User Manual claims that the setting is covered by menu 17 in the radio. This is not the case for a S/N:20************* radio. My guess that this is only true on a S/N:1907*********** radio, right?

Menu 17 on the radio offers the three choices you mention (TO, CO, SE)

Jim KC9HI

Ken, N2VIP

Updated by Jim Unroe 9 days ago

Ken Hansen wrote:

Jim Unroe wrote:

Ken Hansen wrote:

Jim,

I want to help, but to read the radio, I need to enter developer mode, load the .py file you sent me, and when I read the radio successfully, I don't have the ability to save whatever was loaded (the save options are greyed out)

Right now I can only read the radio in the developer mode.

That's not the case here. With the test driver loaded and after downloading from the radio I can either File -> Save or File -> Save As. Neither are greyed out. What happens if you use the CTRL-S keyboard shortcut?

Jim

Jim,

Save and Save as are greyed out, Ctrl-S does nothing.

The attached debug.log file complains about "bandlimitfrequencies" at the very end of the file

Ken

This is useful. The radio doesn't appear to have any "Embedded Message" data, or more likely, it has been moved to a different place.

I can probably build an "image" from the debug.log file but it would take a l-o-n-g time. Instead I think I will hack the driver to bypass the "bandlimitfrequencies" check just so we can have an "image" to work with. Hopefully I can hack something up and get it attached to this issue soon.

In the mean time, would you get a screen capture of the Embedded Message panel from your radio? It should help me find the data if it has been moved.

Thanks,
Jim

Updated by Jim Unroe 9 days ago

Ken,

I think this might work. If it doesn't, include a debug.log file and we will try something else.

Jim

Updated by Ken Hansen 8 days ago

Jim,

Looks good - attached a few files, hope this helps!

Ken, N2VIP

Updated by Ken Hansen 8 days ago

Embedded Message file

Updated by Ken Hansen 8 days ago

Sorry, didn't know how to load multiple files in one update

Updated by Jim Unroe 8 days ago

Ken Hansen wrote:

Embedded Message file

I am looking for the screen capture from the Embedded Message area of the Retevis v1.01 software, not CHIRP. So when it is convenient, would you still get one for me? It reads from the radio to collect the data so the radio will have to be hooked up to the computer before you click the selection or a "Please check the link." error will be seen.

Thanks,
Jim

Updated by Jim Unroe 8 days ago

Ken Hansen wrote:

Sorry, didn't know how to load multiple files in one update

No problem. If you have multiple files in the future all you need to do is click the Add another file link below the [Browse...] button to ass as many additional [Browse...] buttons as you need.

Thank you very much for the CHIRP Radio Images (*.img) from your radio. I will get to studying it today in order to hopefully reverse engineer a permanent fix for the "Failed to get band limits for RT98: local variable 'bandlimitfrequencies' referenced before assignment" error.

Jim

Updated by Jim Unroe 8 days ago

Ken,

I think I have everything resolved for downloading and uploading from a S/N:1907*********** radio. It took a little longer than I thought it would take because there were quite a bit more places to change than what I was expecting. Give the attached test driver module a try.

In order to finish this project up so it can be formally submitted to be added to CHIRP, you will need to provide 5 separate CHIRP Radio Images (*.img) files. What I need is listed below.

- 3 images with the only difference being that menu 17 is set to each of the SCAN settings: SE, TO and CO.
- 2 images with the only difference being that the [V/M] button is toggled between both modes: VFO and Memory.

Please name the files in a way that I can tell which is which.

Thanks,
Jim

Updated by Ken Hansen 8 days ago

Jim,

Attached is the Embedded Message Screen grab from the Retevis 1.01 software, as requested.

Thanks,

Ken, N2VIP

Updated by Jim Unroe 8 days ago

Ken Hansen wrote:

Jim,

Attached is the Embedded Message Screen grab from the Retevis 1.01 software, as requested.

Thanks,

Ken, N2VIP

Hi Ken,

Thanks! I left you some additional "homework" to do. ;-)

Jim KC9HI

Updated by Ken Hansen 8 days ago

Jim,

Here are the five requested files - the three scan files are named in an obvious way, all were downloaded/read in MR mode. The VFO and MR specific downloads are also named in an obvious way.

Thank you for all your work on this Jim - I appreciate your persistence in pushing this issue to completion.

Thanks,

Ken, N2VIP

Updated by Ken Hansen 8 days ago

Sorry - the rest of the files ;^)

Updated by Jim Unroe 8 days ago

Ken Hansen wrote:

Jim,

Here are the five requested files - the three scan files are named in an obvious way, all were downloaded/read in MR mode. The VFO and MR specific downloads are also named in an obvious way.

Thank you for all your work on this Jim - I appreciate your persistence in pushing this issue to completion.

Thanks,

Ken, N2VIP

Hmmm... all 5 files are identical. It is as if making the selections at the radio was not stored in the radio's memory. Weird.

I wonder what would happen if you made the change(s) using the OEM software? Make the change, upload the change to the radio and then download into CHIRP? Then repeat 4 more times for the remaining settings.

If you want, just try it with the VFO/MR setting of the OEM software to see if that does work. Then if that works, the remaining 3 settings could be tried.

Jim

Updated by Ken Hansen 8 days ago

Jim,

That's odd. I'll revisit this later today, perhaps the issue is that I didn't shutdown/restart application between reads if the radio (when I went to close the app I had several 'untitled' "grids" in the app, maybe I kept saving the first one?

Also, to be 100% clear, you want me to create the 5 images using CHIRP or the Retevis software?

I'll check the settings page on the Retevis software to see if scan and VFO/MR button value are exposed in their application.

Ken

Jim Unroe wrote:

Ken Hansen wrote:

Jim,

Here are the five requested files - the three scan files are named in an obvious way, all were downloaded/read in MR mode. The VFO and MR specific downloads are also named in an obvious way.

Thank you for all your work on this Jim - I appreciate your persistence in pushing this issue to completion.

Thanks,

Ken, N2VIP

Hmmm... all 5 files are identical. It is as if making the selections at the radio was not stored in the radio's memory. Weird.

I wonder what would happen if you made the change(s) using the OEM software? Make the change, upload the change to the radio and then download into CHIRP? Then repeat 4 more times for the remaining settings.

If you want, just try it with the VFO/MR setting of the OEM software to see if that does work. Then if that works, the remaining 3 settings could be tried.

Jim

Updated by Jim Unroe 8 days ago

Ken Hansen wrote:

when I went to close the app I had several 'untitled' "grids" in the app, maybe I kept saving the first one?

I'll bet that is the case. That has bit me more than once. I've always expected CHIRP to automatically select any newly created tab. But in reality the previously selected tab remains selected so you have to remember to manually select the tab that you are interested in.

Take your time. I think the mystery has been solved. So just repeat what you did before from the radio's menus and buttons. Just remember to switch between the tabs before saving to a CHIRP "image".

Jim

Updated by Ken Hansen 8 days ago

Jim,
Here are the new files - I closed out of the "grid" between each one after saving it, this should be correct.

I didn't see "scan" or VFO/MR in the current CHIRP interface, I'm guessing you are going to add them for the early version of the radio?

Thanks,

Ken, N2VIP

Updated by Jim Unroe 8 days ago

Ken Hansen wrote:

I didn't see "scan" or VFO/MR in the current CHIRP interface, I'm guessing you are going to add them for the early version of the radio?

I couldn't add them because I didn't know where in memory the settings were store. This last exercise was to provide me with the data that I needed to reverse engineer those locations and add them to the driver module.

I think I have is all situated, but I just got the call to supper. When I return, I will do some final testing and then attach the result to this issue for your testing and feedback.

Jim

Updated by Jim Unroe 7 days ago

Ken,

I've added the VFO/MR and Scan Revive Method settings for the S/N:1907*********** radios. They won't show for S/N:20************* radios since the newer radios do not support those features (that's too bad because I wish my S/N:20************* radios would switch into VFO mode).

I've tested as much as I can test here with the radios that I have. Test downloads and uploads with your radio. If you run across any problems, let me know what they are and include a debug.log file if applicable. If all seems OK, let me know and I will begin working up an official patch to submit for inclusion into CHIRP.

Jim KC9HI

Updated by Jim Unroe 4 days ago

Ken,

Have you had a chance to test this latest driver module? I am holding off on submitting a patch until I have favorable feedback from you.

Jim KC9HI

Updated by Ken Hansen 3 days ago

Jim,

Bad news - I can read/write from/to the radio fine, but in the grid if I try and add another channel I get an error message (see attached picture).

I was attempting to add a channel with a frequency of 146.700, I never got to specify offset, Tone, name, etc...

I attached a debug.log file

Ken, N2VIP

Updated by Jim Unroe 3 days ago

Ken Hansen wrote:

Jim,

Bad news - I can read/write from/to the radio fine, but in the grid if I try and add another channel I get an error message (see attached picture).

I was attempting to add a channel with a frequency of 146.700, I never got to specify offset, Tone, name, etc...

I attached a debug.log file

Ken, N2VIP

That's why I needed testing done. Without the older radio, I can't test to see if the correct band limits were being picked up. Apparently they aren't.

I'll try to see what I can figure out.

Jim

Updated by Jim Unroe 3 days ago

Ken, Give this a try when it is convenient.

Thanks,
Jim

Also available in: Atom PDF