Is it possible that after removing the fourth solder blob, the radio can no longer be programmed by a PC?

Thanks

I haven't heard that in regard to the VX-6R specifically.  I have heard that about other radios.

Quoted: Is it possible that after removing the fourth solder blob, the radio can no longer be programmed by a PC?

yes.

tell me what SW you are using.

ar-jedi

ETA:

Sent: 41 48 30 32 31 00 E0 01 02 01
ERROR: No 06 response from VX-6!

Thats what I get when I try to write to the radio
I'm using VX-6 Commander, btw

Quoted: Sent: 41 48 30 32 31 00 E0 01 02 01

i see your problem, and i know how to fix it.  

unfortunately for you, my wife owns my ass for the next 4 hours so you'll have to wait until Jan 1st!

ar-jedi

Thanks, AR-Jedi, you are the man.  I understand the delay.  In CB slang, "happy happy" and I look forward to your reply.

O5a,

the problem is that by changing the diode arrangement, the "product typecode" of your radio has been changed.  the result of this is that when the VX6R Commander tries to read from the radio, the radio does not reply since the requested product typecode does not match the US-spec VX6R typecode that VX6R commander is using.

you can see the evidence of this issue above:

the initialization string sent to your VX6R by VX6R Commander:

Sent: 41 48 30 32 31 00 E0 01 02 01

the initialization string needed by a modified VX6R (case 1 of 2):

Sent: 41 48 30 32 31 00 F8 01 02 01

the initialization string needed by a modified VX6R (case 2 of 2):

Sent: 41 48 30 32 31 00 E8 01 02 01

some folks on the VX6R list have reported using F8, others have needed to use E8.  the general consensus is that it has to do with either manufacturing vintage (serial number range dependent?) or manufacturing location.  my radio requires product code F8.

btw, my configuration jumpers, post mod, are

(from left to right, antenna at top right) 1st group: 1 open 2 open 3 open 4 open (was closed, now open with mod in place) 5 open (already open from factory) 6 open 7 open 8 open 2nd group: 1 open 2 open 3 open 4 open 5 open my SN is 500211xx.

-------------------------------------------------

how to fix?

the problem is that the initialization string for sent by VX6R commander must be changed to be compatible with the mod'd radio's new product typecode.  the easiest way to do this is by modifying the .vx6 programming file, which includes the initialization string at the start of the file.  this is cumbersome only because you need a binary file editor to do it.

(1)
get and install "hexedit" from hexedit.com/download.htm

(2)
using hexedit, open up a *copy* of your current .vx6 file.  
change the E0 on the first row, 7th column, to F8.
and now save the file back.  
see losdos.dyndns.org:8080/public/ham/yaesu-vx6r/example-hexedit-session-updated.jpg

(3)
start VX6R Commander.  load the .vx6 file you just modified.  i'm assuming you previously have used VX6R Commander to write to the radio, and all your cables etc are known good.  so now attempt to program the radio.  ideally, it should "Just Work".  if not, try again using "E8" for the product config byte.

good luck.

ar-jedi

OK, it didn't work on F8, but on E8 it would write to 100 percent but when the progress window closed on the program the radio displayed ERROR and lost all its memory.

Any suggestions?  I hope its just another number that needs changed.

Thanks again!

Quoted: OK, it didn't work --- Any suggestions?

ok, you are definitely, absolutely, positively sure that you ONLY changed the one byte (E0->E8) in the programming file?  and that you changed the existing value, not added a new value (shifting everything else to the right by one spot)?

ar-jedi

ETA: version of VX6R Commander you are using?  (from within Commander, Help->About will show you)

Quoted: Quoted: OK, it didn't work --- Any suggestions? ok, you are definitely, absolutely, positively sure that you ONLY changed the one byte (E0->E8) in the programming file?  and that you changed the existing value, not added a new value (shifting everything else to the right by one spot)? ar-jedi ETA: version of VX6R Commander you are using?  (from within Commander, Help->About will show you)

V 0.2.0

Quoted: V 0.2.0

same here.  

try using the "blank" programming file i sent you.  
it has the E8 edit already, so it should be good to go.  
see if that runs to completion.

ar-jedi

Quoted: Quoted: V 0.2.0 same here.   try using the "blank" programming file i sent you.   it has the E8 edit already, so it should be good to go.   see if that runs to completion. ar-jedi

ok, the first time I tried it it showed a complete write on the laptop but I still got an error message.  On the second try it worked.  Weird.  I'm going to put all my data into the file you sent me and try it.  I'm cautiously optimistic.  Thanks so much!

73,
Mark

Quoted: On the second try it worked.

ok.  what i would do now is restart VX6R Commander, and do a virgin read from the radio.  make sure that works.  then, enter a couple of memory locations, and write the file back to the radio.

ar-jedi

Thanks a ton ar-jedi, this thing works great.  I still need to learn about the other memories, but I have about 15 channels saved on the home freq bank.  This little radio has impressive range, I can work the repeaters that are 10-20 miles from my house if I am standing by the window.

Thanks again, I thought I screwed everything up, but I guess not!

Happy New Year!

glad to hear it worked out.

73,
ar-jedi

Well it recorded once, but now it will load the whole file, but the radio doesn't change screens...just the RX screen till ERROR.  Is there a file fix for this?

mark,

regarding the above issue in the context of your prior post...

Quoted: ok, the first time I tried it it showed a complete write on the laptop but I still got an error message.  On the second try it worked.

this is unusual.  either the data is correct and the radio accepts it, or it doesn't.  it should not work one time but not the prior.  it should be more deterministic -- i.e., it should work EVERY time.  to me your current problem sounds like a data transfer issue, not a memory programming file issue.  

suggestions:
-- are you using a USB->serial converter?
-- what programming cable are you using?
-- have you tried this latest file a couple of times?
-- what is the product typecode in the file you are trying now (look at it with Hexedit).
-- try changing it to F8.

ar-jedi

Quoted: mark, regarding the above issue in the context of your prior post... Quoted: ok, the first time I tried it it showed a complete write on the laptop but I still got an error message.  On the second try it worked.   this is unusual.  either the data is correct and the radio accepts it, or it doesn't.  it should not work one time but not the prior.  it should be more deterministic -- i.e., it should work EVERY time.  to me your current problem sounds like a data transfer issue, not a memory programming file issue.   suggestions: -- are you using a USB->serial converter? no.  It came from Yaesu with a mic adapter.  Its serial. -- what programming cable are you using? -- have you tried this latest file a couple of times? yes -- what is the product typecode in the file you are trying now (look at it with Hexedit). -- try changing it to F8. E8 ar-jedi

Weird.   Changed it to F8, no work at all.  Back to E8, it worked.  Who knows?