CHIRP

Any luck? Were you able to use my IMG and get a similar error. Maybe its something I am doing wrong with how I send the the data back to the radio?
Thanks
Dave

Sorry, not yet, but I haven't forgotten!

I don't think it's anything you're doing, FWIW. One other thing I should know, is this image from an 8R, 8DR or 8GR?

Thanks, it is the original VX-8r, don't have the GPS installed if that matters or not.
Dave

Hi Dave,

Sorry it took me so long to get to this. I had to tweak the model bits of your 8R image so that I could blow it into my 8DR radio. The good news is that I see the behavior you're seeing when I push your image into my radio. However, the bad news is, I can't figure out how in the world that could have happened as the buffer space that holds the VFO isn't touched by CHIRP at all.

So, if you'll humor me, I'd like to break this down a little to isolate what might have caused it.

I only see 154.830 in the TX frequency of the first channel, is that right? After you reset your radio, if you program in the same thing to channel 1, does it happen again? If it were something like CHIRP writing into the wrong spot, then that behavior should be reproducible. I'm not able to cause the VFO split frequency to change by editing the TX frequency of your image's channel 1.

Maybe you can tell me more about what you did with CHIRP and your radio? Importing from other lists? All manual programming?

Also, if you need it, I should be able to manually edit your image and send it back to you "unlocked". You have a lot of stuff in there, so if that would help, let me know. If I tweak the image, you can push it into your radio without chirp making any changes, so whatever happened before wouldn't have a chance to happen again.

You are correct the TX freq is only associated with channel 1 and that is the freq that gets stuck in VFO B as the duplex TX Freq no matter what RX freq I input. I will try to reset the radio and manually program ch 1 and see what happens. I also tried changing CH 1 info in Chirp and it was the same, that same freq would be locked in as the VFO B TX Duplex, It almost seems to me that particular frequency is in the programming somewhere?

I am new to radio programming as there is no other sollution for the Mac and I dont have or want to run Windows on my mac at this time. What I did was download Chirp and the associated Python that was listed. I then got a cable from ebay and had to search high and low for a driver so the Chirp would see the cable. Once I found the driver, Chirp then saw the USB device where it had not before.

I had to use the Yaesu programming function, powering on while holding a button (dont have my radio and instructions in front of me) and then pressing another to get it to RX in the program mode. I typed in all of the frequencies and information manually in Chirp, I didn't copy them from a spreadsheet. I tried but it didnt work so I started over and typed them.

If you could be so kind to make an IMG for me that I could use that would amazing. I have been putting off programming my radio since the reset as you said, I have alot of public safety, HAM, and commercial frequencies. Would that mean I could use your IMG to program my radio with all my info and have VFO B working? If so yes!

If you could also help with how you program your VX8. If you could give me the details of when you plug in what and what buttons you push when I would really appreciate that.

Again, thanks so much for making a programming sollution for the Mac and your help in this issue!
Dave

Just a quick update. I programmed a few memories manually and all of the VFO modes worked properly, no stuck TX frequencies.
Any help with an IMG would be greatly appreciated.

Thanks, Dave

I haven't yet had a chance to hand-edit your image, but I can still do that.

However, I had an idea over the weekend. I wonder if you somehow did a Memory->VFO transfer after you programmed the radio. That would explain the situation you're in. It might be good to try the same thing to get out of the current pickle you're in. My manual shows this procedure on page 55 under "Moving Memory Data to the VFO". Select a memory channel that does not have an odd split and then perform that procedure and see if it frees up the VFO. If so, then this is an interesting bug in the radio firmware!

Thanks!

The memory to VFO worked, it cleared up VFO B so it works normal. If thats what I have to do to be able to program on the mac I'm ok with that. Would be nice if the issue could be solved but you have no idea how happy I am just to be able to program a radio and not have to find a windows machine.

Thanks
Dave

Well, my point was: I don't know how chirp could have caused this behavior. You said in your post above that after clearing the radio and trying again, you didn't experience the problem, right? I've not been able to reproduce the issue either. So, my guess was that perhaps you inadvertently performed the memory->vfo operation on the radio on one of the channels that you had programmed with a split. Have you been able to reproduce the behavior since? If not, I think this is not actually a bug in chirp....

When I posted about the memories manually that was using the radio itself. In that time, I reset the radio, programmed memories on the radio and everything worked fine.

When I rest the radio, used CHIRP, same thing VFO B stuck. However when I did the memory to VFO function it cleared up VFO B. So to be clear the only time VFO b gets stuck is when I use CHIRP. Thus far, every time I use CHIRP it locks up VFO B until I do the memory to VFO function.
Thanks, Dave

If you keep uploading the same image into the radio, it will continue to push the brokenness back in.

On the radio, do the memory->vfo fix, then download a new image after doing that and trash the old one. I think that you will find that after doing this, further updates from chirp will not hose the radio.

Will do, thanks again for the help. In a side note, have you had any luck doing a Kenwood D700 with a Mac. Wondering about anUSB to serial cable or any help. I can start a different topic if you would like.

Thanks again,
Dave

Have this exact same problem. Was being told I was off frequency. Figured out, before reading this thread, that VFO entered memory entries were fine, Chirp ones (only the [-]) were 'off'. Running Chirp on Windows 10 Home v1607 and latest Chirp daily [chirp-daily-20170115-installer.exe] on a Yaesu VX-8DR. Thx for an otherwise great piece of software!!

Jim Alyanak wrote:
deleted Posted in wrong bug. Sorry.