CHIRP

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

Attach the debug.log please.

Jim

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 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

I will give it a try tonight, thanks!

Ken, N2VIP

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

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.

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

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

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

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

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

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

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

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

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

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

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