CHIRP

I now switched to the next version, the error still occurs. I'm not sure if this is relevant but there might be multiple version of FT-25, I've seen 2 of the official software version, EXP and US_EU. And the chirp's debugs also raised the ID suspect warning in this case. Maybe it'd be a good idea to have another radio tested after the fixes, my radio was bought in Thailand(afaik it's locally advertised and sold as FT-25R/E), I'm not sure if the USA EU or Exported version would be affected.

Thanks for the fast response!

I forgot to specify. On the latest img it's on memory 4. It showed -0.600 on the radio's settings but -1.200 on Chirp

Can you try the attached module? Enable developer mode with Help->Enable Developer Mode, then restart, File->Load Module and choose this file.

Please check with your FT-25 and FT-65 by selecting the E variant when you download. Old images will still open as the R variant, so you should download fresh.

Please test VHF and UHF frequencies in as many permutations as you can think of, and also attach a debug log here of the download from each please.

Sorry for the confusion, actually, I only have one which I just noticed that it's stated on the back plate as FT-25R (monoband VHF version since UHF is kinda not allowed in Thailand). The FT-65(R) I've mentioned are from the other issue (#9713) which is not mine. I'll upload the results soon.

Here are the results. I've saved the memory directly on the radio itself on memory 3, 145.6750 with -0.6000 offset. On the CHIRP (latest next with ft4.py module loaded), selecting FT-25E reads the offset correctly as -0.6000 but using FT-25R Model still reads it wrong as -1.2000.

I'll have a look, but please allow some time.
Indeed, there are some multipliers at work, and they differ from model to model (FT-25 vs. FT-65), and apparently from regions to regions (R vs. E), too. I developed using an R model, so I'm a bit surprised that this fails.

Thanks for the helpful files!

Started to work on this. Sorry, be patient, I need to get up to speed with Chirp-next.
I have an FT.25R for testing.

Got Chirp-next running after installing Linux Mint from scratch and cloning repository. Getting there.

Ok, so I tested this with my FT-25R, which I bought in the US. It looks exactly like yours. "FT-25" on the front, "FT-25R" under the battery.
When I program it with an offset of +0.6 MHz, it works correctly...

The interesting thing is that there is a multiplier in the code. The multipliers for FT-25/65 and FT-4 are different, with the one for the FT-25/65 being twice the value of the one for the FT-4 (50 vs. 25 kHz). Looking into this ticket, and also #9713, I'm beginning to suspect that the multipliers are applied using some mechanism we haven't caught on yet.

I did some digging, and based on some of your input, I came to this conclusion:

I now switched to the next version, the error still occurs. I'm not sure if this is relevant but there might be multiple version of FT-25, I've seen 2 of the official software version, EXP and US_EU. And the chirp's debugs also raised the ID suspect warning in this case. Maybe it'd be a good idea to have another radio tested after the fixes, my radio was bought in Thailand(afaik it's locally advertised and sold as FT-25R/E), I'm not sure if the USA EU or Exported version would be affected.

I think this might be the key, actually. Can you try the US_EU OEM software version? If that one fails as well, then we have the solution: Export versions come with a modified multiplier, and I need to add a sub driver.

I'm somewhat confused, because you added two images: one for an FT-25R, the other for an FT-25E. I assume it's your FT-25R radio, but the OEM software has two selections? The images are practically identical.

Attached is a modified driver. You can test as follows:

1. Open Chirp software.
2. In Help, checkmark "Developer mode".
3. End and restart Chirp.
4. In File menu, select "Load module" and load the attached file.
5. Test.

Please check:

• whether the offsets are coming out correctly,
• and whether there's no ID warning anymore in the debug log. Please share your observations and the debug log. Thanks!

Here's another driver to test. I'm fixing one thing for Bernhard but I don't have a radio to test with so if I could get a confirmation from one of the other people here, I'd appreciate it.

See LoadingTestModules for procedure to load this into your CHIRP.

Applied in changeset github|ab0d759426ede5209b436bc24967fb3579960abe.