Hi Dan, See attached. There may be a few changes between the two, I think I changed the power settings and maybe a name or two.
I hear what you say about turning the radio into a brick. I used to have this argument with the PE's at my former employer. It went something like, "you were outside the maintenance package, you shouldn't have done that" to which I replied "don't let me do things that are bad." You can't win that argument.....
-Scott
On 7/3/2012 7:44 PM, Dan Smith wrote:
So, did I run into both a CHIRP bug and a Yaesu firmware bug, or is this known behavior?
Sounds like an honest-to-goodness bug to me.
Can you send me the original CHIRP image, and then an image captured after "fixing" it with commander? There's probably just some stray bit that isn't getting cleared. I should be able to find it from the diff of the two images.
I'll go on to say, once again, that Yaesu radios are really bad about this. They let you program basically anything into the memory you want, regardless of whether it will crash the radio's microcontroller or not. It's really rather unfortunate that they didn't design the radio a little better than that...
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users