[chirp_users] Beginner's guide and a loaner radio
Bruce MacAlister, W4BRU
Thu Nov 28 08:09:05 PST 2013
Yes, that's what I did. Since I've seen lots of Ubuntu wiki and questions
about this, I think this symptom and solution should be a part of Chirp
documentation or a least links to Ubuntu wikis about it. It's complexity
is that USB is not a separate connection but a subset of serial which is
still called TTY (remember teletype?) in Linux. The "dialout" permission
solution is not what I'd call an obvious solution to a USB connection
problem.
The real solution is for Ubuntu to make "connected permission" the default.
We all have USB devices to connect so we'll all run into the problem.
Windows and OSX arrive with connection-on as a default.
--
73, Peace,سلام ,שָׁלוֹם, ειρήνη, Bruce ∞
On Thu, Nov 28, 2013 at 10:57 AM, Tom Balaban <mototom800 at gmail.com> wrote:
> You can solve this permanently by adding your user name to the "dialout"
> group. Then log out and log back in again.
>
>
> On Thu, Nov 28, 2013 at 10:10 AM, Bruce MacAlister, W4BRU <W4BRU at arrl.net>wrote:
>
>> Mike,
>>
>> I've not tried changing much using Chirp. I just got too busy.
>>
>> The issue for me was getting Chirp connected to my radio. I can provide
>> documentation when you are ready but the problem was a Ubuntu issue.
>> Basically the user (me) did not have permission for a serial connection.
>> Under Ubuntu USB appears to be a subset of the serial connection so if you
>> do not have permission for a serial connection your USB connection fails.
>> The symptom is clear and I have the screen snap for it. There is a simple
>> command (terminal session) to establish permission and solve the problem.
>>
>> --
>> 73, Peace,سلام ,שָׁלוֹם, ειρήνη, Bruce ∞
>>
>> On Tue, Nov 26, 2013 at 8:51 PM, Mike Agner <ka3jjz at comcast.net> wrote:
>>
>>> Today, Bruce MacAllister wrote:
>>> ===========================
>>> Yes, I will. I did technical writing for pay and will do it as a
>>> volunteer
>>> now-retired engineer. I have a Kenwood TM-D700 and TH-F6A and the the
>>> MPC
>>> FX and Chirp files for them. I am new to Chirp and so see it from a
>>> newbie
>>> perspective with all the confusion inherent in just starting.
>>> ===============================
>>>
>>> Thanks vy much for the offer, Bruce - however please hold off for now. I
>>> have to set up a mailbox to keep your radio from being stolen (around
>>> here that's not an uncommon occurrence). Once
>>> I have that done, I'll email you off-list.
>>>
>>> Since you mentioned that you are a newbie to Chirp (me too) I wonder if
>>> you would discuss what you found difficult in using the software for the
>>> first time. That way as the Guide
>>> gets built, we can at least try to address at least some of these so
>>> that others don't run into the same issues.
>>>
>>> Here's one that had me stumped - I know you can use the stored
>>> configuration files to load certain freq ranges into the radio (if it
>>> supports them). But here's a question I never found the
>>> answer for - How can you append that data at the end of data you've
>>> already loaded, or perhaps put the configuration file in first, then the
>>> unloaded contents of your radio? Does it simply overlay the data,
>>> or push it down further in the editor?
>>>
>>> Mike
>>>
>>> ---
>>> This email is free from viruses and malware because avast! Antivirus
>>> protection is active.
>>> http://www.avast.com
>>>
>>> _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>
>>
>>
>>
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20131128/3eca2ec5/attachment.html
More information about the chirp_users
mailing list