Bug #10439: Yaesu FT90 problem UK - CHIRP

Actions

Copy link

Bug #10439

closed

Yaesu FT90 problem UK

Added by Mike Brogan almost 2 years ago. Updated almost 2 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Dan Smith

Category:

Target version:

chirp-py3

Start date:

03/12/2023

Due date:

% Done:

100%

Estimated time:

Chirp Version:

Model affected:

Yaesu FT90

Platform:

Windows

Debug Log:

chirp_debug-iov41jxh.txt chirp_debug-iov41jxh.txt

I read the instructions above:

Description

When trying to enter a 25KHz channel (eg 145.325) get the error Invalid edit: Tuning step 5.00 not supported; Frequency requires 5.00KHz step.
If I try to change step setting it tells me that the Channel Frequency (NOT STEP FREQUENCT) is invalid because it is 0.00000.

Have had no problems with original Chirp - trying to migrate to Chirp_Next but cannot make it work..........

Have tried changing region setting and doing things in different orders but nothing works. Version being used is today's release, have not tried any earlier ones.

Actions

Copy link

Updated by Dan Smith almost 2 years ago

There's apparently a bug in the FT-90 that prevents 5.0kHz from working in some situations, and the way chirp-next's editor works, it seemed easier to mark it as just not supporting 5.0kHz at all. But I guess this is an unintended consequence. Can you tell me the exact frequency you're trying to enter so I can experiment?

Actions

Copy link

Updated by Dan Smith almost 2 years ago

Dan Smith wrote in #note-1:

There's apparently a bug in the FT-90 firmware that prevents 5.0kHz from working in some situations, and the way chirp-next's editor works, it seemed easier to mark it as just not supporting 5.0kHz at all. But I guess this is an unintended consequence. Can you tell me the exact frequency you're trying to enter so I can experiment?

Actions

Copy link

Updated by Mike Brogan almost 2 years ago

Dan Smith wrote in #note-1:

There's apparently a bug in the FT-90 that prevents 5.0kHz from working in some situations, and the way chirp-next's editor works, it seemed easier to mark it as just not supporting 5.0kHz at all. But I guess this is an unintended consequence. Can you tell me the exact frequency you're trying to enter so I can experiment?

I tried 145.325 and 145.375 with the same result. Just to verify I went back to old chirp , programmed 145.325, back to chirp next and read it ok - still could not program 145.375 using next. Have now programmed all channels using old chirp without any problems - so definitely a problem when using next. Europe and UK use 12.5KHz channels these days so this is going to be a problem here.

Thanks for getting back to me.........

Actions

Copy link

Updated by Dan Smith almost 2 years ago

Assignee set to Dan Smith
Target version set to chirp-py3

Yeah, I know it's a next thing. It's not really even a problem with the FT-90 driver, it's the interaction between the new GUI and the driver trying to avoid programming a 5kHz step.

I'm not sure what the reference to 12.5kHz means - the radio does support that just fine and your sample frequencies align to 12.5kHz. The problem is just the workflow of getting a channel added without going through 5kHz first.

Are you aware of the 5kHz issue? I didn't write this driver, but the code avoids setting 5kHz tuning step for any channel with a comment about a known bug in the radio. It would be a lot easier if the driver didn't do that, but I assume it's the best plan, if selecting 5kHz will always be a problem for people...

Actions

Copy link