[arm-allstar] Remote Base BCD Channel Steering

Ed Wilhelm vacuumtubesforever at gmail.com
Wed Jan 20 22:31:35 EST 2016


Just saw the Repeater Builder link. None of that stuff exists. Will be 
going from the rpi gpio to probably a ULN2803 and then to the 4 pins on 
the accessory connector.

If nothing is pulled low the radio will operate normally.

Ed


On 01/20/2016 10:09 PM, Doug Crompton wrote:
> OK, So am I to assume the external diode BCD steering does not exist 
> and the RPi2 just controls the 4 bits (or 5) bits straight into the 
> radio? If all are high the front panel works?
>
> *73 Doug
> WA3DSP
> http://www.crompton.com/hamradio*
>
>
> ------------------------------------------------------------------------
> Date: Wed, 20 Jan 2016 17:33:27 -0800
> From: kg6uyz at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Remote Base BCD Channel Steering
>
> For a GM300 you supply a GND trigger to one or more of the 4 channel 
> steering pins.  The pins have to stay grounded to stay on the channel 
> you selected, if you release the triggers the radio reverts back to 
> whatever channel you last manually selected with the channel up/down 
> button.
>
> Example in this link: 
> http://www.repeater-builder.com/motorola/maxtrac/remote-channel-select.html
>
>
> On Wed, Jan 20, 2016 at 2:04 PM, Doug Crompton <doug at crompton.com 
> <mailto:doug at crompton.com>> wrote:
>
>     Ed,
>
>      OK fine. I can supply an example if you want but I was wondering
>     what they wanted to see. Do you set the four lines BCD and then
>     strobe another pin to load it? That is often the way it is done or
>     maybe it just monitors the lines for them being stable and switches?
>
>     *73 Doug
>     WA3DSP
>     http://www.crompton.com/hamradio*
>
>
>     ------------------------------------------------------------------------
>     To: arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>     From: vacuumtubesforever at gmail.com
>     <mailto:vacuumtubesforever at gmail.com>
>     Date: Wed, 20 Jan 2016 16:44:27 -0500
>
>     Subject: Re: [arm-allstar] Remote Base BCD Channel Steering
>
>     Doug,
>
>     Nothing fancy, just 16 channel stuff. GM300, Maxtracs, Kenwood 90
>     series stuff. Just got to yank the lines low.
>
>     Ed
>
>     On 1/20/2016 11:14 AM, Doug Crompton wrote:
>
>         Ed,
>
>          What is the format of the BCD control you are wanting? 16
>         channels - 0001 - 1111 ?? Does the radio take TTL  levels? Is
>         there a strobe bit once the other bits are setup?
>
>         *73 Doug
>         WA3DSP
>         http://www.crompton.com/hamradio*
>
>
>         ------------------------------------------------------------------------
>         To: arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>         From: vacuumtubesforever at gmail.com
>         <mailto:vacuumtubesforever at gmail.com>
>         Date: Wed, 20 Jan 2016 06:31:55 -0500
>         Subject: Re: [arm-allstar] Remote Base BCD Channel Steering
>
>         Hi Doug,
>
>         Never did get a response. Was trying to avoid reinventing the
>         wheel.
>
>         Never thought of using the patch command to do DTMF stuff.
>         Will do some investigating.
>         That's the cool thing about Allstar/Asterisk, if you can think
>         of something, there's usually a way to do it.
>
>         All your efforts are really appreciated.
>
>         Ed W8VT
>
>         On 1/19/2016 9:21 PM, Doug Crompton wrote:
>
>             Ed,
>
>             In researching I saw you asked the same question years ago
>             and I did not see an answer then. Did you ever get one?
>
>             http://lists.allstarlink.org/pipermail/app_rpt-users/2013-February/005962.html
>
>             Using the GPIO on the Pi to BCD control a radio would not
>             be hard. In fact a user has already done that using
>             function codes and an external script I wrote to control
>             the bits. It is in use commercially.
>
>             The idea for the future code we are writing is to get
>             specific stuff out of the base code and put it where users
>             can create their own interfaces to whatever hardware they
>             want.
>
>             Here are the basics of how I would do it....
>
>             Use the patch command (with a different code) to pass DTMF
>             to a Linux script via an extensions.conf dial plan.
>             Then the script would take the number sent, convert it to
>             BCD or any other format the radio requires
>             and send it to the GPIO bits. Of course you would have to
>             interface those bits to the actual hardware.
>
>             If you needed to pass a code to a remote node you would
>             use the standard codes to pass the command to the remote
>             nodes dial plan.
>
>             *73 Doug
>             WA3DSP
>             http://www.crompton.com/hamradio*
>
>
>             > To: arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>             > From: vacuumtubesforever at gmail.com
>             <mailto:vacuumtubesforever at gmail.com>
>             > Date: Tue, 19 Jan 2016 20:04:16 -0500
>             > Subject: [arm-allstar] Remote Base BCD Channel Steering
>             >
>             > Is this supported with the current image? If so, anyone
>             know the
>             > details, what gpio pins, etc?
>             >
>             > Tnx
>             >
>             > Ed W8VT
>             > Beckley WV
>             > Nodes 27849, 29496, 29982
>             > _______________________________________________
>             >
>             > arm-allstar mailing list
>             > arm-allstar at hamvoip.org <mailto: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 <mailto: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
>         <mailto: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 <mailto: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
>     <mailto: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 <mailto: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
>
>
>
>
> -- 
> Jeff Ackerman
> kg6uyz at gmail.com <mailto:kg6uyz at gmail.com>
>
> _______________________________________________ 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160120/02034981/attachment-0001.html>


More information about the arm-allstar mailing list