Project

General

Profile

Actions

Bug #10936

closed

Chirp can't write to Yaesu VX-6 after MARS Mod

Added by Rodger Zeisler about 1 year ago. Updated about 1 year ago.

Status:
Not a bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/06/2023
Due date:
% Done:

0%

Estimated time:
Chirp Version:
next
Model affected:
Yaesu VX-6
Platform:
Windows
Debug Log:
I read the instructions above:
Yes

Description

I have been using Chirp (legacy and now next) to read/write to my Yaesu VX-6. It works great. I did a MARS Mod on my radio which worked fine. Part of the MARS Mod requires you to do a reset on your radio, which erases all your stored memory channels. I opened my saved settings in Chirp, connected the programming cable (same one I have always used), powered it on while holding the F/W key, CLONE was displayed, and then pressed V/M and WAIT was displayed. All was normal. I then clicked OK, waited a bit, and received the message "Failed to communicate with the radio: Radio did not ack block 1". The word "Error" was displayed on the radio. I tried this a couple of different times with the same unsatisfactory results. I verified via the Device Manager that I was using the correct com port.

As an additional test, I used VX-6 Commander at http://www.kc8unj.com/vx6.html. I was abled to successfully read/write to my radio, so this told me that the radio was not broken.


Files

yaesu-vx-6-fail.JPG (25.8 KB) yaesu-vx-6-fail.JPG Screen shot of failed message when attempting a write to the radio Rodger Zeisler, 11/06/2023 02:02 PM
chirp_debug-cui9h3c1.txt (17.9 KB) chirp_debug-cui9h3c1.txt Debug log Rodger Zeisler, 11/06/2023 02:13 PM
Actions #1

Updated by Rodger Zeisler about 1 year ago

I forgot to add the debug log. I tried to write and then read to/from the radio.

Actions #2

Updated by Dan Smith about 1 year ago

Can you download a fresh image from it and upload that?

Yaesu radios of that vintage change their identity when you mod them to prevent you from cloning between modified and unmodified radios. Since the Yaesu protocol is (so very) braindead and does no negotiation with the PC, we can't tell the difference between the radio actively refusing the ID and the radio not even being connected or responding. So what happens when you try to upload your unmodified image is we send the first block of the image which contains the ID, the radio sees it doesn't match its now-modified ID and refuses it by just never answering the PC.

So your only option is to download a fresh image from the modified radio and copy/paste all the memories from your original one into the new one and upload it back. I think you'll find that works if you try, but let me know.

Actions #3

Updated by Dan Smith about 1 year ago

Any update?

Actions #4

Updated by Rodger Zeisler about 1 year ago

I was having trouble downloading a fresh image until I actually ready the instructions that you provided in the popup. :-)

After clicking OK and then pressing the BAND button, a downloaded a fresh image from the radio. I then cut-and-pasted the contents of my old img file to the new img file. I then uploaded the new img file to the radio. All worked great. Thanks for your help.

Actions #5

Updated by Dan Smith about 1 year ago

  • Status changed from New to Not a bug

Cool, glad to hear it, thanks.

Actions

Also available in: Atom PDF