Project

General

Profile

Actions

Bug #10386

closed

Yaesu FT-90 error

Added by Dean Koger almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
02/22/2023
Due date:
% Done:

100%

Estimated time:
Chirp Version:
next
Model affected:
Yaesu FT-90
Platform:
MacOS
Debug Log:
I read the instructions above:

Description

CHIRP-next generates an error when attempting to download from Yaesu FT-90, while CHIRP-legacy works OK. CHIRP-next works OK with a Baofeng radio


Files

chirp_debug-vd97t5bl.txt (4.76 KB) chirp_debug-vd97t5bl.txt Dean Koger, 02/22/2023 10:46 PM
ft90.py (22.4 KB) ft90.py 37bed886 Dan Smith, 02/22/2023 11:34 PM
chirp_debug-sdsnwrmr.txt (7.92 KB) chirp_debug-sdsnwrmr.txt Dean Koger, 02/23/2023 12:38 AM
chirp_debug-zlrjsw82.txt (3.59 KB) chirp_debug-zlrjsw82.txt Dean Koger, 02/23/2023 12:38 AM
ft90.py (22.4 KB) ft90.py b0cd02bd Dan Smith, 02/23/2023 01:03 AM
chirp_debug-tbl9u16z.txt (7.02 KB) chirp_debug-tbl9u16z.txt Dean Koger, 02/23/2023 01:15 AM
chirp_debug-7lgdk8hr.txt (7.89 KB) chirp_debug-7lgdk8hr.txt Dean Koger, 02/23/2023 01:30 AM
ft90.py (22.5 KB) ft90.py 6f287d5c Dan Smith, 02/23/2023 02:26 AM
chirp_debug-ypsea3a8.txt (57.6 KB) chirp_debug-ypsea3a8.txt Dean Koger, 02/23/2023 03:01 AM
Yaesu_FT-90_20230222.img (4.14 KB) Yaesu_FT-90_20230222.img Dean Koger, 02/23/2023 03:08 AM
Actions #1

Updated by Dan Smith almost 2 years ago

Hi Dean, this radio hasn't been converted for -next per the front page, but only because we didn't have anyone to test. Can you try the attached module and let me know if it works for upload and download? Please be sure to have a backup of your radio with legacy in case it partially works and causes your radio to reset.

Enable developer mode in the help menu. After restarting chirp, File->Load Module and choose this file, then try to interact with the radio. Please capture a debug log afterwards, whether it works or not.

Thanks!

Updated by Dean Koger almost 2 years ago

Download from radio works ok, upload to radio generates an error. I am enclosing both logs.

Dean

Actions #3

Updated by Dan Smith almost 2 years ago

Thanks for the update Dean. Can you try this?

Actions #4

Updated by Dean Koger almost 2 years ago

Same result, download from radio ok, upload to radio generates error. Enclosed is log for upload error.

Dean

Actions #5

Updated by Dan Smith almost 2 years ago

Can you try downloading the radio, save to an image, then close and re-open chirp (and re-load the driver of course), load that image and try an upload? I see one strange error in that last log that relates to potentially not re-opening the serial port properly after the initial download.

Actions #6

Updated by Dan Smith almost 2 years ago

Er, actually, it looks like maybe you hit cancel, I assume because it seemed like it wasn't progressing? That's probably the error I'm seeing.

Actions #7

Updated by Dean Koger almost 2 years ago

Same result, log file attached.

Dean

Actions #8

Updated by Dan Smith almost 2 years ago

Hmm, yeah, the radio is just not responding to that block at all. Does the radio report an error on the display?

And just to be clear, you can upload with chirp-legacy?

Actions #9

Updated by Dean Koger almost 2 years ago

No, I didn't hit cancel. I tried it twice, once before hitting OK and once after hitting OK. It isn't clear like it is on the download where you hit OK first. I don't remember which so I'll try it on legacy which does work.

Dean

Actions #10

Updated by Dan Smith almost 2 years ago

Okay, you definitely have to put the radio into clone receive mode first, then click okay in chirp. Yaesus are annoying like that.

Actions #11

Updated by Dean Koger almost 2 years ago

Sorry for the delay (supper). Worked fine with legacy. But with next I get an error on the radio as soon as I push DISP/SS.

Dean

Actions #12

Updated by Dan Smith almost 2 years ago

Hmm, okay, I was surveying the history on this driver and I see something about needing to open the serial port before going into clone mode, but I'm not sure how that can really matter (I didn't write this driver).

Can you describe the cable you're using? I assume it's a DE9 to RJ45 or something like that? If so, can you tell how many wires are actually present inside the body of the clear plastic RJ connector?

If I have to make the change being described in the history, I'll have to do quite a bit more work.

Thanks for your patience with this. It's of course quite frustrating for me to not have one locally to iterate with, and for you having to keep trying things ;)

Actions #13

Updated by Dan Smith almost 2 years ago

I'm thinking maybe your cable relies on the DTR signal going high to give the radio the +5V it needs, and so when chirp is showing you the instructions, the port is not yet open. I can make that behave like legacy did, but let's try something if you don't mind.

Attached is another version of the module, where it waits five seconds before starting the clone once you click the okay button on the instruction prompt. So if you would, get the radio to the point right before you push DISP/SS, then click OK on the chirp instruction prompt, and then press DISP/SS on the radio and see if you can time it to work.

If that works, then I can make the change to chirp itself to open the port before the instruction prompt for the FT-90 like legacy did.

Actions #14

Updated by Dean Koger almost 2 years ago

I will try that. The cable is DB9 to RJ45 with 3 wires.

Actions #15

Updated by Dean Koger almost 2 years ago

That didn't work. Using legacy, when I push DISP/DD I get the R in the lower left, with next it just gives an error.

Actions #16

Updated by Dan Smith almost 2 years ago

Right, this is going to require you to do something different with next for a test. Please read what I wrote:

Attached is another version of the module, where it waits five seconds before starting the clone once you click the okay button on the instruction >prompt. So if you would, get the radio to the point right before you push DISP/SS, then click OK on the chirp instruction prompt, and then press >DISP/SS on the radio and see if you can time it to work.

For this one test, click okay on the chirp instruction box BEFORE you push DISP/SS on the radio, but within five seconds. This is just a special module to adjust the timing to prove that this is the problem, and then I'll have to do another full build of chirp for the real fix. And please include the debug log.

Actions #17

Updated by Dean Koger almost 2 years ago

Radio is an Apple silicon mac, then an Apple USBC to USBA adaptor, then a Prolific USB to serial converter, then the DB9 to RJ45 cable.

Actions #18

Updated by Dean Koger almost 2 years ago

That did work, guess I waited to long to push DISP?SS before.

Actions #19

Updated by Dan Smith almost 2 years ago

  • Status changed from Feedback to In Progress
  • Assignee set to Dan Smith
  • Target version set to chirp-py3

Fantastic, thanks Dean! I'll push this for a build tomorrow. Please let me know if it doesn't work "as it should" in tomorrow's build. You can just come back and comment on this and we'll go from there, but I think we should be good.

Thanks for your help!

Actions #20

Updated by Dean Koger almost 2 years ago

Thanks for your help. I never expected to get such a quick response.

Dean

Actions #21

Updated by Dan Smith almost 2 years ago

Oh, one more thing, we don't have a test image (.img file) for this radio in the tree. Can you attach one for me to add?

Actions #22

Updated by Dean Koger almost 2 years ago

Here's the image I've been using:

Actions #23

Updated by Dan Smith almost 2 years ago

Excellent, thanks again!

Actions #24

Updated by Dan Smith almost 2 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF