Re: [chirp_users] CHIRP 0.1.7b8
Yep, the native .chirp driver isn't DV-aware yet, so that's expected
at the moment.
I guess I should fix that up before 0.1.7 official.
Only if you don't want a gaggle of amateurs (or whatever the collective noun is for a group of radio amateurs) wondering where all of their DV settings have gone :)
Mind you, it would give them hours of joy if they didn't hadn't taken your earlier advice and had their config backed up.
Cheers,
Davidt
PS: Maybe it could be a hamfest of amateurs... :D
Dan,
I was just thinking recently that I had sent out my .icf files so that others could adopt the work I did in programming just about every repeater pair from the ARRL Repeater Directory for all of Colorado. This included numerous different scan banks from a generic repeater list arranged in frequency order divided into areas like "Denver" "Colorado Springs" "Grand Junction" "EchoLink" "IRLP".
I did have one user call me telling me their radio was turning on by itself. Well that made since because my radio was set to Auto Turnoff after 2 hours and Auto Turnon after 8 hours. I just merely told him how to change the setting.
But that brought up the point that if I wasn't the one doing the programming using my .icf file that others may be just dumping it into their radios and could possibly be changing their MYCALL to my call sign. I don't have multiple radios to play with so I seldom get to program other radios using your software to cross program between various radio types. So if the software isn't loading or changing the MYCALL and URCALL RPT1 RPT2 fields that might not be a bad thing... otherwise there could be numerous operators running around with someone else's call in their radios. The alternative is to remove data from these fields prior to providing your own .icf to others.
We still have an RG8U here in Denver... someone just testing on a radio!
73.
Barry KA0BBQ
list chirp_users@lists.danplanet.com http://lists.danplanet.com/mailman/listinfo/chirp_users
Barry A. Wilson wrote:
We still have an RG8U here in Denver... someone just testing on a radio!
That's Doug, K2AD - He put it in as a joke during early testing, and I think it's stuck in his programming somewhere on his HT. LOL!
I told him I was going to be LMR400 instead. :-)
Nate
But that brought up the point that if I wasn't the one doing the programming using my .icf file that others may be just dumping it into their radios and could possibly be changing their MYCALL to my call sign. I don't have multiple radios to play with so I seldom get to program other radios using your software to cross program between various radio types. So if the software isn't loading or changing the MYCALL and URCALL RPT1 RPT2 fields that might not be a bad thing... otherwise there could be numerous operators running around with someone else's call in their radios. The alternative is to remove data from these fields prior to providing your own .icf to others.
Currently, the native chirp format doesn't store the MYCALL settings for a radio, which means it shouldn't suffer this problem.
Definitely a good idea to offer a "strip the mycalls from this radio" idea or some such :)
participants (4)
-
Barry A. Wilson -
Dan Smith -
David Tilson -
Nate Duehr