Re: [chirp_users] chirp_users Digest, Vol 43, Issue 4
It was the 2008 version of the ARRL Travel Plus for repeaters 11.0.
On Tue, Jul 3, 2012 at 3:00 PM, chirp_users-request@intrepid.danplanet.comwrote:
Send chirp_users mailing list submissions to chirp_users@intrepid.danplanet.com
To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request@intrepid.danplanet.com
You can reach the person managing the list at chirp_users-owner@intrepid.danplanet.com
When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..."
Today's Topics:
- Re: TPL Files (Tom Hayward)
Message: 1 Date: Mon, 2 Jul 2012 15:02:05 -0600 From: Tom Hayward esarfl@gmail.com Subject: Re: [chirp_users] TPL Files To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Message-ID: < CAFXO5Z1K7UrN90Vf8pQu0O2dpHswKwiKoZMwREzgBZghc+4oqQ@mail.gmail.com> Content-Type: text/plain; charset=UTF-8
On Sun, Jul 1, 2012 at 6:53 PM, Franklin Sanor wa8whp@gmail.com wrote:
This is the file from the ARRL repeater software I use when traveling. It shows 100 repeaters within 35 miles of my home in Alliance, Ohio. I can
set
a trip route and get a list of all along the route.
What is the name of the software that generated this tpl file? What is the version number of that software?
Tom KD7LXL
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
End of chirp_users Digest, Vol 43, Issue 4
Greetings all- I ran into a problem setting up a VX-6R for a friend today (first time I have used CHIRP on this model radio). Since it was a "new" used radio, I first reset it to factory defaults, then did a read from the radio which worked fine. Next I opened my master CSV file with all my local programming, and copy and pasted various sections into the VX-6 tab (using about 65% of the memories). I then wrote the new file back to the radio, which also seemed to go fine. As I reviewed the programming on the radio, the first thing I noticed was that several of the memory names started with a P instead of what I had programmed. Then, even worse, when I scrolled up to around memory location 380 (I don't remember the exact number), the radio locked up and required removing the battery. When I reinstalled the battery, it immediately locked up again, and I had to hold down the reset sequence and install the battery (which required more hands than I have) to reset it back to factory defaults. I reviewed the CHIRP file, which looked OK, but writing back to the radio gave the same results. Next I wrote the file to the radio, and then turned around and read it back into VX-6 Commander and compared it with the CHIRP programming. The only difference I could see was that Commander showed the Clock.Set bit was on for all the memories I pasted from my master CSV file. This bit can be set on a per memory slot basis, and is not visible on CHIRP. When I reset it on all memories, and then rewrote the file from Commander, the radio performed as expected.
So, did I run into both a CHIRP bug and a Yaesu firmware bug, or is this known behavior?
-Scott
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...
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
See attached. There may be a few changes between the two, I think I changed the power settings and maybe a name or two.
Okay, thanks. Hopefully I'll be able to weed those bits out, but I might need some help cleaning them up. I'll let you know.
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.....
Heh, well, so far the Yaesus seem to be resistant to true bricking because they'll always take a reset and clean themselves up. So, I'm not sure what the right term is.
participants (4)
-
Dan Smith -
Franklin Sanor -
Scott Currie -
Scott Currie