CHIRP

So the radio is completely dead and you have thrown it in the trash, is that right?

Dan Smith wrote:

So the radio is completely dead and you have thrown it in the trash, is that right?

Morning Dan

No, but I had thought about doing that ;),

I went back to stable 09-07-2012 version and loaded my original file and restored radio to working condition.

Well I tried this on 2 different Windows boxes w/2 different OS ( XP/Win7).
Same result, so it is not the radio or the PC, or even the operator of said software.
And the term bricked means just that, the radio was inoperable with the uploaded code plug till I uploaded a known good back up with the Icom CS-V82 RSS. Yes the Icoms are almost bullet proof, as I have several of them.

I also was able to use the 07-09-12 stable version to upload a known good back up and it too restored proper operation. So your stable version with the Icom support is good up to that point.

Now just to humor you, I will go and get every daily file you have made and see where it goes south at.
I will update you as to what I find.

You have very nice software here and to say there is nothing wrong is kind of stretching it a bit, so don't make me out to be an idiot, I am trying to help you here.

This might be a small thing, but your software worked fine till you added the new Baofang UV-5Rc support, a radio my wife just bought.

We have used the Icom part of your software for some time and was elated that you got the UV-5Rc added so we could move channel data between radios. The breakage (bug) is small one indeed and you should not stop the presses just for this.

I will research more and get back to you. I guarantee this will be one of those "Homer Simpson" moments and you will fix it and there will be no questions asked later, and we all will be grateful.

Anyhow off to test your stuff and I will get back to you.

TIA Bob

bob brown - w0nqx wrote:

I also was able to use the 07-09-12 stable version to upload a known good back up and it too restored proper operation. So your stable version with the Icom support is good up to that point.

Now just to humor you, I will go and get every daily file you have made and see where it goes south at.
I will update you as to what I find.

No really, the code for that radio hasn't been touched since May. Take a look at the change-log for yourself: http://chirp.danplanet.com/projects/chirp/repository/changes/chirp/icx8x.py

But like Dan said, no developers own this radio, so we won't be able to troubleshoot anything until someone loans one of us a radio.

"But like Dan said, no developers own this radio, so we won't be able to troubleshoot anything until someone loans one of us a radio."

So for me to find out where it breaks will not be of any value to you, since I own said radio and now have problems where I previously had none?

B

bob brown - w0nqx wrote:

"But like Dan said, no developers own this radio, so we won't be able to troubleshoot anything until someone loans one of us a radio."

So for me to find out where it breaks will not be of any value to you, since I own said radio and now have problems where I previously had none?

When I said "we" I was referring to Dan, Marco, myself, or anyone else who has previously acted as a Chirp developer. By all means, you are welcome to troubleshoot this yourself, and even contribute a patch once you have solved the problem. That is the beauty of open source.