CHIRP

Sorry, forgot to mention.
I'am using the latest "Today's build".
CHIRP daily-20170222

Rick.

Sorry for the delay in udpating this thread.
I can confirm that although the log suggests I was trying to upload to an 897 I did most certainly use the 7100 option.
As a matter of interest, I do use Chirp with an 897 and that works perfectly well.
Unfortunately I can no longer produce the problem as I've now switched entirely over to Windows 10 and have found the old Yaesu tool works fine anyway, so I no longer need to try Chirp for this radio.
I will, however, try my Windows 10 install of the latest Daily Build to upload to the FT7100 as before.
Update to follow.
Rick.

Sorry for the time this response took.
The log says you were trying to upload your data selecting the FT-7100 as model?
Can you provide another log, please?

#6641 suggests a patch, which needs to be reviewed by a developer.

I can confirm that the problem is still present with the latest daily build, 20201125, when using Windows 10 64bit and my original Prolific usb to serial adaptor and original Yaesu cable.
I haven't bought another cable yet, as I'm not convinced that is the issue. Yet...
Rick.

Hi all, I've spent 4 hours typing frequencies, shifts, and all other settings for my FT7100M, only to find out the same thing as you all... So, on the latest version 20201128, when using WIN 10 64bit, upload to the radio still doesn't work... Download works fine.
Stevan

also having this same problem. latest version 01/10/2021 still not working. any solutions?
have downgraded driver on prolific chip as well as upgraded.

RadioError: Failed to communicate with radio: Failed to read ACK. No response from radio.

[2021-01-17 22:08:10,173] chirp.ui.common - ERROR: ----------------
[2021-01-17 22:08:10,173] chirp.ui.clone - ERROR: Clone failed: Failed to communicate with radio: Failed to read ACK. No response from radio.
[2021-01-17 22:08:10,194] chirp.ui.clone - DEBUG: Clone thread ended
[2021-01-17 22:08:10,197] chirp.ui.reporting - DEBUG: Reporting model usage: Yaesu_FT-7100M,upload,True
[2021-01-17 22:08:10,201] chirp.ui.reporting - DEBUG: Reporting exception
[2021-01-17 22:08:10,201] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Failed to communicate with radio: Failed to read ACK. No response from radio. ---
[2021-01-17 22:08:10,204] chirp.ui.inputdialog - ERROR: Traceback (most recent call last):
File "chirpw", line 68, in
AttributeError: 'NoneType' object has no attribute 'split'

[2021-01-17 22:08:10,204] chirp.ui.inputdialog - ERROR: ----------------------------

Does the radio need to be toggled to receive from Chirp?
To clone from one transceiver to another, use the following procedure:
...
3. On the “destination” radio, press the [REV] key. The “CLONE RX” indicator will appear on the display.

Yes it does need to be toggled and no, it doesn't make any difference.

Many thanks.
Rick.

have we found out how to fix Failed to communicate with radio: Failed to read ACK. No response from radio. yet? im having the same issue

I personally haven't found a work around.
Luckily I still have the original Yaesu software (and it runs on Windoz 10), so I can still program the radio.
Chirp would be a better solution though. It has far more flexibility than the Yaesu software.
Rick.

I purchased the radio used so it did not come with Yaesu software. I bought the cable from Mark Dunkle of bluemax just so I could use chirp. I could buy yaesu software and a cable for about the same price as this cable. do you have a resource that I could download Yaesu's software? I really wanted to use chirp. Use it on my other radios.

Also what does status feedback mean? shouldn't be a open issue?

This right here fixed it for me. MACOS 12.6.3 Show Package Contents>Contents>Resources>Chirp>Drivers save your old FT-7100.py and .pyc and delete them replace it with the FT-7100.py you download from this post re download from radio and then reupload that download. Open your saved file (because you saved one before you figured out it wasn't going to upload like me......) then upload to the FT-7100. Works.

https://chirp.danplanet.com/issues/6641

Tagging @Bob Sumien in case he didn't see the above.

@Daniel Fiechter Smith yes legacy. I had to install python 2.7 to get back up and running. Hadn't used CHIRP in a few months at least. I'd be happy to test for you. I see the instructions for loading test modules but Idon't see an attachment. Feel free to email me if that makes things easier.

Bob Sumien wrote in #note-24:

@Daniel Fiechter Smith yes legacy. I had to install python 2.7 to get back up and running. Hadn't used CHIRP in a few months at least. I'd be happy to test for you. I see the instructions for loading test modules but Idon't see an attachment. Feel free to email me if that makes things easier.

@Dan Smith not sure what happened I guess I tagged the wrong person in my previous comment. Hopefully this tags you.

@Dan Smith I am so sorry it has been a bad week around here. I see the attachment now. I was looking for it at the bottom and not the top. I'll try to test it tomorrow or Saturday at the latest! Thank you.

Bob, neither of your logs show that you've loaded the module I attached. Please follow the instructions in LoadingTestModules.

Okay, that last one has what looks like a timing bug that isn't relevant to the conversion nor the fix from the other bug we're trying to integrate. It probably just makes the driver flaky in general (I didn't write this driver by the way, so I'm building context as we go). Now that I realize what you're doing, I think that explains some of the confusion in the earlier one. We can look at that issue separately, but if you could just try a download again with the same driver that'd be good. Since you seem to be looking at the logs, when you see this:

[2023-04-07 18:11:03,356] chirp.loaded.loaded-8932-bk1eyznc - DEBUG: Header:
000: 56 61 72 74 65 78 20 53   Vartex.S
008: 74 61 6e 64 61 72 64 20   tandard.
016: 41 48 30 30 33 4d 20 4d   AH003M.M
024: 2d 4d                     -M......
[2023-04-07 18:11:03,356] chirp.loaded.loaded-8932-bk1eyznc - DEBUG: len(header) = 26
[2023-04-07 18:11:03,607] chirp.loaded.loaded-8932-bk1eyznc - DEBUG: Header:
000: 61 70 20 56 30 34         ap.V04..

That's the additional bug I'm describing, where it reads the header in two chunks and since neither looks complete, it throws it away as garbage and keeps waiting. So in that case, you just need to try again. The driver needs to be, well, smarter than that, but it's not currently.

Also, no need to try an upload unless the download succeeds and looks good.

Okay, well, that attempt got nothing at all from the radio. However, that could be that there was some junk queued on the serial line that the radio read as soon as it started up. They're also quite sensitive to that, since there isn't any negotiation back and forth between the computer and the radio, a single unexpected byte will stop it.

Okay, the first attempt still got nothing at all from the radio. You're not doing any uploads between successive successful downloads right? If not, nothing is being written to the radio so I can't explain why it would need a reset in between. When you start chirp waiting, it's literally just waiting for the radio to send something, never hears anything, and times out. So it's hard to imagine how chirp could be doing anything to cause the radio to error out.

So, if you haven't tried an upload, please do that and let me know if that's working.

If we can't explain the issue with the download and the resets, I'm hesitant to proceed further. If the radio fails to transmit the image and chirp is still waiting and you push the TONE button again, what happens? Are you doing anything with the cable (unplugging, etc) in between tests?

Ok. The one before the last I d/l, u/l and then tried to d/l again. The first d/l and u/l after the factory reset worked then the next d/l failed. When I push the Tone button it failed and presented ERROR on the screen of the radio immediately. Those are the times when CHIRP is getting nothing from the radio. As far as the cable the only thing I do is unplug it from my MBP and then plug it back into the same USB port. The cable remains attached to the 7100. I'll test more tomorrow. Would having logs from legacy vs next help? I'm not sure how to get the legacy log.

There's nothing being logged during this part so there's nothing to compare it to in legacy. I want to know if you can do multiple downloads in a row without the factory reset, without any uploads in between. It's also useful to know if that doesn't work in -next but does in -legacy (although there's really nothing useful that will tell me).

Why are you unplugging it from your computer in between successive download attempts? If the radio is in clone mode when you do that it can definitely confuse the radio and it should definitely not be necessary.

Testing and making notes as I test.
CHIRP Legacy
Seems like you can do multiple downloads but then when you try to upload after several it fails.
Looks like you have to download before you can upload even if the image was successfully uploaded previously.
Once you upload you have to shutdown and power back up in clone before you can download or upload again.

CHIRP Next
Also seems you can do multiple downloads.
You have to make a change to the download or switch images to be able to upload to the radio.
Same in that you have to shut down and reboot into clone before you can do another d/l or u/l.
Shut down CHIRP and brought it back up, loaded the module and was able to u/l without d/l first.

I was not unplugging it from the computer between u/l or d/l attempts. I was unplugging between testing sessions. Moving between the couch and the radio. :D The other thing I noticed was that with next I was having to push Tone or Rev twice to get it to either TX or RX the image. When d/ling the 2nd attempt I was only having to push Tone once. Not sure that makes any sense or difference but with Legacy I always only had to push Tone or Rev once for it to get into mode. For some reason today I was not having to do a factory reset to get it to work.

I put hands on my FT-1802M and it does not have a computer programming port so I won't be able to help with that one.

June 2023
I as well am still having an issues with this bug. I have tried old and new software, both windows 10 and MAC. The DL works perfect. UL will fail moments after the ok button is pressed and "ERROR" is shows on the radio screen. Reading through this page and the other associated tickets I believe I am performing all of the steps in the correct order. I am using a factory USB-29B cable

Is there any information or support I can provide or is there a known resolution I have not been able to find yet

Thank you
Keith