Bug #291
closedFM-Narrow not supported on Yaesu FT-8800
100%
Description
Chirp does not allow a channel to be set to NFM (narrow deviation) when programming the radio, and ignores the NFM setting on a radio dump.
The unknown1 parameter is set to 0x00 for FM Wide and 0x01 for FM Narrow in a dump. I guess that 'unknown1' is actually the FM wide/narrow flag.
Files
Updated by Tom Hayward about 12 years ago
- Status changed from New to In Progress
- Assignee set to Tom Hayward
This has got to be one of the best bug reports I've ever read, thanks.
Can you post a .img file? It should contain FM, AM, and NFM channels, and tell me which are which. This should be very easy to fix, but I can't test it without an img.
Updated by Dave Ingram about 12 years ago
- File FT8800 NFM Sample.img FT8800 NFM Sample.img added
Here's the IMG file.
Channel 2 is FM (Wide), channel 3 is FM (narrow) and channel 1 is AM.
I can see the raw data with a right click on CHIRP 0.2.2, but the option has gone in CHIRP daily-20120906. Editing the file (copy or move) destroys the flag too.
BTW, the same thing happens with my FT7900, but I don't have a way of programming NFM for this radio (I have FTB8800, but not FTB7900). The struct also has an Unknown1 in it, so might be the same thing.
Updated by Tom Hayward about 12 years ago
Oh, great. The FT-7900 is mostly shared code with the 8800, so if I can fix them both at the same time it will be easiest. unknown1 is just a coincidence. I'd need to examine an image to determine the best way to fix both of these radios with shared code. You should be able to program memories from the front panel of the radio. In the FT-7900, can you program 3 identical channels, but with different modes?
By the way, the "show raw memeory" option probably disappeared because you don't have developer mode turned on.
Updated by Tom Hayward about 12 years ago
- File ft7800.py ft7800.py added
- Target version set to 0.3.0
- % Done changed from 0 to 100
- Chirp Version changed from 0.2.2 to 0.2.3
Will you test this with your FT-7900 and FT-8800? It should allow programming FMN to the 7900 and 8800. If it doesn't work, it'll probably program it to AM instead of FMN (I guessed the location of the FMN bit on 7900).
You can load this file by choosing File > Load Module in Chirp.
Updated by Dave Ingram about 12 years ago
- File Chirp File Menu.png Chirp File Menu.png added
I do not have the 'Load Module' option in my version of Chirp. I have installed CHIRP 0.2.3 and enabled the Developer functions. The extra functions appear in View, so that is working.
Any other tips?
Updated by Tom Hayward about 12 years ago
I think you'll need a daily build for that feature.
Updated by Tom Hayward about 12 years ago
- Status changed from In Progress to Feedback
Have you had a chance to test this? Any daily build since 2012-10-09 has the change.
Updated by Dave Ingram about 12 years ago
Tom Hayward wrote:
Have you had a chance to test this? Any daily build since 2012-10-09 has the change.
I tried the .py file earlier but couldn't find anyway to load it in Windows.
I've tried Daily281012 and it is working well on the FT-8800. I haven't tried the FT-7900 yet because that is out in the car.
One thing that is a nuisance for changing mode is that when the mode box is clicked twice (once to select, once to edit), the drop down doesn't drop automatically, so a third click is needed. Is it possible to have the 'combo-drop down with fixed contents' (that's the VB term for it) auto drop when selected?
I'll test out the FT-7900 when I get a chance. The irony is that since I lodged the bug, the repeater in question has been upgraded to normal FM, so there isn't a need for NFM on it. Oh well! NFM is still good for monitoring public service channels though.
Updated by Tom Hayward about 12 years ago
- Status changed from Feedback to Blocked
Waiting for test on FT-7900.