[arm-allstar] GPIO for PTT and COS?

David Lang david at lang.hm
Tue Jun 7 18:50:30 EST 2016


This is part of a discussion on why we are needing to hook up to the tiny pins 
on the USB sound card, and how in the 'near' future we may not need to do that 
any more and be able to hook to some of the other pins on the Pi (the GPIO, 
General Purpose Input Output, pins)

David Lang

  On Tue, 7 Jun 
2016, David McGough via arm-allstar wrote:

> Date: Tue, 7 Jun 2016 15:23:17 -0400 (EDT)
> From: David McGough via arm-allstar <arm-allstar at hamvoip.org>
> To: Greg Thornwall via arm-allstar <arm-allstar at hamvoip.org>
> Cc: David McGough <kb4fxc at inttek.net>
> Subject: Re: [arm-allstar] GPIO for PTT and COS?
> 
>
> Hi Greg,
>
> The issue isn't C--you have to remember that python, java, the Linux
> Kernel, etc., are all written in C.
>
> My major concern is that we've got varying support for several different
> hardware platforms, including RPi2/3, BBB, various Odroids and I've got
> this code running on PC hardware, too.  Managing GPIO between each of
> these different platforms is subtly to significantly different, leading to
> many potential headaches....For example: if software monitoring a rain
> gauge misses an interrupt, nothing disastrous happens.  If repeater
> controller software misses an interrupt, the transmitter might not unkey,
> or COS might act flaky now and then, not activating when someone tries to
> key the repeater. With the AllStar code, if any inconsistency happens even
> occasionally, it's a huge deal.
>
> The advantage obtained by sticking with USB hardware (like a CM1xy sound
> FOB) is that the software API is the same across all the various
> computers. And, that software is very well tested.
>
> Now that modifiable sound FOBs are getting harder to obtain, I'm looking
> hard at getting more I/O solutions available, in a modular way.
>
> 73, David KB4FXC
>
>
>
> On Tue, 7 Jun 2016, Greg Thornwall via arm-allstar wrote:
>
>>
>> Hi David & Doug,
>> Is that because of the lack of interrupts in C on the Pi?  I built a wx
>> station and implemented  an interrupt in Python that listens to my rain
>> gauge, a reed switch that closes for a fraction of a second.
>>
>> I guess there's nothing like that in C on the Pi? Or is there more to it
>> than that? Can one integrate Python code into C? In Java you can use JNI
>> for native C calls.
>>
>> 73 Greg KD3SU
>>
>>
>>
>> On 06/07/2016 01:29 PM, David McGough via arm-allstar wrote:
>>> Hi Greg,
>>>
>>> Currently there isn't a way to efficiently utilize the RPi2/3 on-board
>>> GPIO for PTT or COS.  However, more I/O methods are currently in
>>> development.  This new code will start showing up in upcoming Alpha/Beta
>>> releases.
>>>
>>> 73, David KB4FXC
>>>
>>>
>>>
>>>
>>>
>>> On Tue, 7 Jun 2016, Greg Thornwall via arm-allstar wrote:
>>>
>>>> I was wondering is there a way (in the code) to setup using 2 GIPOs for
>>>> COS and PTT? Do you know where that's implemented in the code? Is it in
>>>> the channel C files? I would guess there are some C GIPO libraries for
>>>> the Raspberry Pis.
>>>>
>>>> Tnx 73 Greg KD3SU
>>>>
>>>>
>>>>
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>>
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
>


More information about the arm-allstar mailing list