[arm-allstar] Connections

[David]

It seems that user that have  upgraded to the new build that I connect to can not disconnect  from me I have to issue the disconnect command from my end even though I am not issuing a permanent connection any advice would be nice
Thank you all for your hard  work
David kb6rhd


On January 28, 2017 10:50:55 AM PST, arm-allstar-request at hamvoip.org wrote:
>Send arm-allstar mailing list submissions to
>	arm-allstar at hamvoip.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>or, via email, send a message with subject or body 'help' to
>	arm-allstar-request at hamvoip.org
>
>You can reach the person managing the list at
>	arm-allstar-owner at hamvoip.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of arm-allstar digest..."
>
>
>Today's Topics:
>
>   1.  I'm having problems with the 1.5 build. (Irvin Fontanes)
>   2. Great news on the version 1.5 build!! (John Baxter)
>   3. Before I dive down this rabbithole... (Buddy Brannan)
>   4. Re: Before I dive down this rabbithole... (gregory)
>   5. Re: The hamvoip Allstar V1.5 release is nowavailable! (txlawman)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Sat, 28 Jan 2017 11:33:35 -0600
>From: Irvin Fontanes <irvinpr at gmail.com>
>To: arm-allstar at hamvoip.org
>Subject: [arm-allstar]  I'm having problems with the 1.5 build.
>Message-ID: <588CD5EF.2040903 at gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>James,
>
>The process to connect to your RPI3 in 1.5 is the same as the previous 
>version. You do not need a monitor or a keyboard.
>1. Boot the new image
>2. Go to your router and find out the ip address assigned to 'alarmpi'.
>
>Setup port forwarding to that ip address using port 222.
>3. connect to your RPI3 via putty with the ip address obtained in #2 
>using port 222.
>4. connect and setup as usual.
>
>I hope this helps.
>
>---
>This email has been checked for viruses by Avast antivirus software.
>https://www.avast.com/antivirus
>
>
>
>------------------------------
>
>Message: 2
>Date: Sat, 28 Jan 2017 13:24:12 -0500
>From: John Baxter <jwilliambaxter at me.com>
>To: John Baxter via arm-allstar <arm-allstar at hamvoip.org>
>Subject: [arm-allstar] Great news on the version 1.5 build!!
>Message-ID: <0F177052-6C38-4A1B-B83E-602058AF1143 at me.com>
>Content-Type: text/plain;	charset=utf-8
>
>Hello,
>
>Really psyched about the version 1.5 build!   Time to load up the Pi
>and get things ready for when I get my rig back together.  Yaesu is
>fixing the front panel for my FT-7900.  This may take a couple weeks
>but I am swamped right now so no worries? Have the URI and cable all
>set, so it should be plug and pray?  :)
>
>Looking forward to the adventure.   Need to monitor a while to pick a
>nice quiet frequency for the node.
>
>Looking forward to Fun and Learning.   Many thanks to everybody who
>contributed to building the new version!!!!!!
>
>best 73,
>-john n3fpz
>
>John William Baxter	
>jwilliambaxter at me.com <mailto:jwilliambaxter at me.com>
>215-460-9128			iPhone/text/FaceTime
>215-572-0471			landline
>lydiasaudioguy			Skype
>N3FPZ					amateur radio callsign
>LydiaFerrell.com <http://lydiaferrell.com/>		Lydia Ferrell?s music
>
>  Psalms 19:1 ?the heavens declare the glory of God?	
>
>
>
>------------------------------
>
>Message: 3
>Date: Sat, 28 Jan 2017 13:39:03 -0500
>From: Buddy Brannan <buddy at brannan.name>
>To: ARM Allstar <arm-allstar at hamvoip.org>
>Subject: [arm-allstar] Before I dive down this rabbithole...
>Message-ID: <57C8738F-CB0A-4B7E-96A3-3B41B19F21E3 at brannan.name>
>Content-Type: text/plain; charset=us-ascii
>
>Hi,
>
>OK, just got a microSD card burned with the new 1.5 image.
>
>Before I jump down this rabbithole, can I ssh into the Pi to do the
>setup (I have an ethernet connection available) 
>
>No mentionwas made of a login password or anything like that. 
>
>Thanks,
>
>--
>Buddy Brannan, KB5ELV - Erie, PA
>Phone: 814-860-3194 
>Mobile: 814-431-0962
>Email: buddy at brannan.name
>
>
>
>
>
>
>------------------------------
>
>Message: 4
>Date: Sat, 28 Jan 2017 10:50:02 -0800
>From: gregory <dropbox at digitalattack.org>
>To: arm-allstar at hamvoip.org
>Subject: Re: [arm-allstar] Before I dive down this rabbithole...
>Message-ID: <fc4396eb-f4ca-a818-f0b6-e204854d2b5b at digitalattack.org>
>Content-Type: text/plain; charset=UTF-8
>
>i just did mine, didn't need to hook up monitor or keyboard. port 222
>and root root.
>
>
>On 01/28/2017 10:39 AM, "Buddy Brannan via arm-allstar" wrote:
>> Hi,
>>
>> OK, just got a microSD card burned with the new 1.5 image.
>>
>> Before I jump down this rabbithole, can I ssh into the Pi to do the
>setup (I have an ethernet connection available) 
>>
>> No mentionwas made of a login password or anything like that. 
>>
>> Thanks,
>>
>> --
>> Buddy Brannan, KB5ELV - Erie, PA
>> Phone: 814-860-3194 
>> Mobile: 814-431-0962
>> Email: buddy at brannan.name
>>
>>
>>
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>-- 
>( ?? ?? ??)
>digitalattack.org
>
>
>
>------------------------------
>
>Message: 5
>Date: Sat, 28 Jan 2017 12:50:59 -0600
>From: txlawman <txlawman at aol.com>
>To: arm-allstar at hamvoip.org
>Subject: Re: [arm-allstar] The hamvoip Allstar V1.5 release is
>	nowavailable!
>Message-ID: <72bjlud9ne9iye946nro3k0g.1485629459256 at email.android.com>
>Content-Type: text/plain; charset=utf-8
>
>
>    
>I saw in the archives that there would be "packages" for other things
>availabe wit the v1.5 release. I'm specially interested in the RMS
>node. Is that out yet? Do you have to set up the full AllStar node to
>accomplish this? If there is someone who has done this, I'd love to get
>input. Feel free to contact me off list, unless there are others
>interested.
>BrianKC5YSM
>
>
>Sent from my Samsung Galaxy Tab?4
>
>-------- Original message --------
>From: arm-allstar-request at hamvoip.org 
>Date: 01/28/2017  11:00 AM  (GMT-06:00) 
>To: arm-allstar at hamvoip.org 
>Subject: arm-allstar Digest, Vol 32, Issue 28 
>
>Send arm-allstar mailing list submissions to
>	arm-allstar at hamvoip.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>or, via email, send a message with subject or body 'help' to
>	arm-allstar-request at hamvoip.org
>
>You can reach the person managing the list at
>	arm-allstar-owner at hamvoip.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of arm-allstar digest..."
>
>
>Today's Topics:
>
>?? 1. Re: UCA222 info --was:RPi GPIO COS/PTT (David McGough)
>?? 2. Re: The hamvoip Allstar V1.5 release is now available!
>????? (Doug Crompton)
>?? 3. Re: UCA222 info --was:RPi GPIO COS/PTT (Josh W4ZZK)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Sat, 28 Jan 2017 01:48:26 -0500 (EST)
>From: David McGough <kb4fxc at inttek.net>
>To: "\"Josh W4ZZK via arm-allstar\"" <arm-allstar at hamvoip.org>
>Subject: Re: [arm-allstar] UCA222 info --was:RPi GPIO COS/PTT
>Message-ID:
>	<Pine.LNX.4.44.1701280057110.13197-100000 at goliath.inttek.net>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
>Hi Josh,
>
>I've used UCA222 devices at Field Day for HF digital modes a couple of
>years now and around the shack.? They have worked well for me, with far
>superior audio quality to the bargain basement CM1xy fobs.
>
>I've got one hooked to some JBL LSR305 monitors with a JBL PSW-1200,
>via a
>10 foot USB extension cable. No problem. (And shockingly good audio!)
>
>I've got medium-power (110W class) VHF and UHF gear nearby, high-power
>HF
>in the other room.
>
>The caveat I've found is to make sure to break-up USB ground loops,
>they
>will cause major grief. I've found these isolators work very well. At
>Field day, this isolator made the difference between being completely
>functional and totally useless:
>
>http://us.hifimediy.com/index.php?route=product/product&product_id=69
>
>
>73, David KB4FXC
>
>
>
>
>On Wed, 25 Jan 2017, "Josh W4ZZK via arm-allstar" wrote:
>
>> Just a note about the Behringer UCA222
>> I'm an Audio Engineer and Production Manager in AL/MS/TN market, and
>> have "played" with these little boxes for several years.? The newer
>> 222's are quite better in manufacturing than the older ones.? Hard to
>> believe, but since Behringer had been bought up by Music Group, their
>> QC has went up some in this device's pro-sumer market... even by
>leaps
>> and bounds in the commercial/professional sector.
>> 
>> Do note that these 222 boxes are VERY susceptible to RFI. For
>example,
>> I attempted to use it as a "receiving" sound card for a few Online
>> Streams at a local EMA office.... typical install scenario....
>> computer, radios, and this box all were in a rather active RF
>> environment. (HF VHF and UHF).? I don't know if I simply had a unique
>> scenario on my hands, but there would be some times where it would
>> "lose sync" with the computer, like I had disconnected the USB cable.
>> That meant restarting the streaming app to regain sync.? Remoting in
>> to the PC again and again to resync the device got old pretty
>quickly.
>> Perhaps there were more RFI choking and eliminating I could have
>done,
>> but I exhausted all feasible, and "affordable" options before going
>> with individual $3 CM108 Cards, which work GREAT.? Maybe some way to
>> bleed off transient voltage from active RF environments would work...
>> I don't know.? But, in their normal operation, the little 222 boxes
>> are halfway decent. Very simple audio interface. Would love to see a
>> schematic of it, and know how we could go in the future with using
>> that box.
>> 
>> Josh Hatton W4ZZK
>> Muscle Shoals, AL
>> w4zzkjosh at gmail.com
>> 
>> 
>> On Mon, Jan 23, 2017 at 11:16 AM, "Doug Crompton via arm-allstar"
>> <arm-allstar at hamvoip.org> wrote:
>> > Jim,
>> >
>> >?? The Raspberry Pi has no direct audio input, no A/D so anything
>direct
>> > would not be possible. The USB works fine on the Pi with thousands
>of nodes
>> > out there using it.
>> >
>> > The two approaches I mentioned (FOB mod and Nano) are both good
>choices.
>> > The Nano gives you the option of using unmodified FOBS, like the
>ones you
>> > have with blobs, for audio so don't throw them out. It also gives
>the
>> > future option of using better, albeit more expensive, sound devices
>like
>> > the Behringer UCA222. Devices like this give two channel input and
>output
>> > which opens up a lot of new possibilities.
>> >
>> >
>> >
>> > *73 Doug*
>> >
>> > *WA3DSP*
>> >
>> > *http://www.crompton.com/hamradio
><http://www.crompton.com/hamradio>*
>> >
>> > On Mon, Jan 23, 2017 at 9:29 AM, "Jim Kinter Jr. via arm-allstar" <
>> > arm-allstar at hamvoip.org> wrote:
>> >
>> >> Thanks David, and my condolences.
>> >>
>> >> I have been curious for a while now why no one uses the built in
>audio
>> >> system (not just this project)? Is it that buggy?
>> >> A while back, I built a Pi Echolink (svxlink) link node (it used a
>USB fob
>> >> as well), using VOX for COS and a GPIO for PTT.
>> >> It worked for the most part, but sometimes the PTT would get stuck
>> >> (Murphy's law- at the worst possible moment, like when still 1.5
>hours away
>> >> coming back from a hamfest in north Texas & it is deadkeying the
>local
>> >> repeater--called the house and had daughter unplug the powerpole
>connection
>> >> feeding the whole thing). That might have been an RFI thing
>causing it, as
>> >> I had it in a plastic box, so I wonder if a metal
>enclosure/ferrites might
>> >> have helped....
>> >>
>> >> I just think, why did they include such things (sound and GPIO) if
>they
>> >> dont work? :-)
>> >>
>> >> thanks again, and Ill have a look at the Nano solution.
>> >>
>> >> 73
>> >> Jim
>> >>
>> >>
>> >> At 12:13 AM 1/23/2017, David Lang wrote:
>> >>
>> >>> On Sun, 22 Jan 2017, "Jim Kinter Jr. via arm-allstar" wrote:
>> >>>
>> >>> Greetings,
>> >>>> I have been searching over the info on the site and mail list,
>and cant
>> >>>> seem to find if any instructions are available for using the
>Pi's GPIO for
>> >>>> COS/PTT yet.
>> >>>> I have found where it said it will be included in a future
>release, and
>> >>>> some other instructions with config settings, but nothing more
>definitive
>> >>>> (which pins to use for what, config settings for those pins,
>etc).
>> >>>>
>> >>>> I friend of mine is using this setup on his repeater with URI,
>and Id
>> >>>> like to use what I already have without spending $100 a pop on
>URIs per
>> >>>> setup (I already have a few Pi's at my disposal)
>> >>>> I had bought a half dozen USB sound FOBs, but all were blobbed
>(they
>> >>>> were cheap, so I even attempted to mine down into one blob to
>see what I
>> >>>> could see, probably effectively destroying the one FOB/losing
>$2).
>> >>>>
>> >>>> So is this capability available yet, and if so, where might I
>find more
>> >>>> info?
>> >>>>
>> >>>
>> >>> It is not yet available, they have decided to not use the GPIO
>pins
>> >>> directly, but to run things through an arduino nano, so it's a
>$20 option
>> >>> instead of a $100 option.
>> >>>
>> >>> hardware details are available at:
>> >>>
>> >>> https://sites.google.com/site/radiofarmprojects/home/hamvoip
>> >>> -nano-interface
>> >>>
>> >>> https://hamvoip.org/hamradio/Nano_Allstar_Interface/
>> >>>
>> >>> support for this is not yet in any release of the allstar
>software, but
>> >>> they were planning a release in December that was postponed due
>to a death
>> >>> in the community. They were planning to have this support either
>in that
>> >>> release or within a couple of weeks after.
>> >>>
>> >>> David Lang
>> >>>
>> >> _______________________________________________
>> >>
>> >> arm-allstar mailing list
>> >> arm-allstar at hamvoip.org
>> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> >>
>> >> Visit the BBB and RPi2/3 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/3 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/3 web page - http://hamvoip.org
>> 
>
>
>
>------------------------------
>
>Message: 2
>Date: Sat, 28 Jan 2017 02:19:46 -0500
>From: Doug Crompton <wa3dsp at gmail.com>
>To: Tom Hayward <tom at tomh.us>
>Cc: ARM Allstar <arm-allstar at hamvoip.org>
>Subject: Re: [arm-allstar] The hamvoip Allstar V1.5 release is now
>	available!
>Message-ID:
>	<CAMp6vsuuNsu4mh0Qz9d-aTz1epDxkmDSg6G6hAboJKG71q9DHg at mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>Tom,
>
> The answer to your question is on page 11 of the readme!
>
>
>
>*73 Doug*
>
>*WA3DSP*
>
>*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>On Fri, Jan 27, 2017 at 9:45 PM, Tom Hayward <tom at tomh.us> wrote:
>
>> On Fri, Jan 27, 2017 at 4:24 PM, "Doug Crompton via arm-allstar"
>> <arm-allstar at hamvoip.org> wrote:
>> > The archived files are noticeably smaller as the source is not in
>the
>> image
>>
>> Does this mean Allstar is no longer open source? If it is open
>source,
>> can you share a link to the source? I wasn't able to find a link on
>> hamvoip.org.
>>
>> Tom KD7LXL
>>
>
>
>------------------------------
>
>Message: 3
>Date: Sat, 28 Jan 2017 07:09:36 -0600
>From: Josh W4ZZK <w4zzkjosh at gmail.com>
>To: David McGough <kb4fxc at inttek.net>, "\"Josh W4ZZK via
>	arm-allstar\"" <arm-allstar at hamvoip.org>
>Subject: Re: [arm-allstar] UCA222 info --was:RPi GPIO COS/PTT
>Message-ID: <AB667299-8E4F-498A-9ABA-3FA8591A8C46 at gmail.com>
>Content-Type: text/plain; charset=utf-8
>
>David
>Thanka for that info. I will look into this.
>Josh W4ZZK
>
>On January 28, 2017 12:48:26 AM CST, David McGough <kb4fxc at inttek.net>
>wrote:
>>
>>Hi Josh,
>>
>>I've used UCA222 devices at Field Day for HF digital modes a couple of
>>years now and around the shack.? They have worked well for me, with
>far
>>superior audio quality to the bargain basement CM1xy fobs.
>>
>>I've got one hooked to some JBL LSR305 monitors with a JBL PSW-1200,
>>via a
>>10 foot USB extension cable. No problem. (And shockingly good audio!)
>>
>>I've got medium-power (110W class) VHF and UHF gear nearby, high-power
>>HF
>>in the other room.
>>
>>The caveat I've found is to make sure to break-up USB ground loops,
>>they
>>will cause major grief. I've found these isolators work very well. At
>>Field day, this isolator made the difference between being completely
>>functional and totally useless:
>>
>>http://us.hifimediy.com/index.php?route=product/product&product_id=69
>>
>>
>>73, David KB4FXC
>>
>>
>>
>>
>>On Wed, 25 Jan 2017, "Josh W4ZZK via arm-allstar" wrote:
>>
>>> Just a note about the Behringer UCA222
>>> I'm an Audio Engineer and Production Manager in AL/MS/TN market, and
>>> have "played" with these little boxes for several years.? The newer
>>> 222's are quite better in manufacturing than the older ones.? Hard
>to
>>> believe, but since Behringer had been bought up by Music Group,
>their
>>> QC has went up some in this device's pro-sumer market... even by
>>leaps
>>> and bounds in the commercial/professional sector.
>>> 
>>> Do note that these 222 boxes are VERY susceptible to RFI. For
>>example,
>>> I attempted to use it as a "receiving" sound card for a few Online
>>> Streams at a local EMA office.... typical install scenario....
>>> computer, radios, and this box all were in a rather active RF
>>> environment. (HF VHF and UHF).? I don't know if I simply had a
>unique
>>> scenario on my hands, but there would be some times where it would
>>> "lose sync" with the computer, like I had disconnected the USB
>cable.
>>> That meant restarting the streaming app to regain sync.? Remoting in
>>> to the PC again and again to resync the device got old pretty
>>quickly.
>>> Perhaps there were more RFI choking and eliminating I could have
>>done,
>>> but I exhausted all feasible, and "affordable" options before going
>>> with individual $3 CM108 Cards, which work GREAT.? Maybe some way to
>>> bleed off transient voltage from active RF environments would
>work...
>>> I don't know.? But, in their normal operation, the little 222 boxes
>>> are halfway decent. Very simple audio interface. Would love to see a
>>> schematic of it, and know how we could go in the future with using
>>> that box.
>>> 
>>> Josh Hatton W4ZZK
>>> Muscle Shoals, AL
>>> w4zzkjosh at gmail.com
>>> 
>>> 
>>> On Mon, Jan 23, 2017 at 11:16 AM, "Doug Crompton via arm-allstar"
>>> <arm-allstar at hamvoip.org> wrote:
>>> > Jim,
>>> >
>>> >?? The Raspberry Pi has no direct audio input, no A/D so anything
>>direct
>>> > would not be possible. The USB works fine on the Pi with thousands
>>of nodes
>>> > out there using it.
>>> >
>>> > The two approaches I mentioned (FOB mod and Nano) are both good
>>choices.
>>> > The Nano gives you the option of using unmodified FOBS, like the
>>ones you
>>> > have with blobs, for audio so don't throw them out. It also gives
>>the
>>> > future option of using better, albeit more expensive, sound
>devices
>>like
>>> > the Behringer UCA222. Devices like this give two channel input and
>>output
>>> > which opens up a lot of new possibilities.
>>> >
>>> >
>>> >
>>> > *73 Doug*
>>> >
>>> > *WA3DSP*
>>> >
>>> > *http://www.crompton.com/hamradio
>><http://www.crompton.com/hamradio>*
>>> >
>>> > On Mon, Jan 23, 2017 at 9:29 AM, "Jim Kinter Jr. via arm-allstar"
><
>>> > arm-allstar at hamvoip.org> wrote:
>>> >
>>> >> Thanks David, and my condolences.
>>> >>
>>> >> I have been curious for a while now why no one uses the built in
>>audio
>>> >> system (not just this project)? Is it that buggy?
>>> >> A while back, I built a Pi Echolink (svxlink) link node (it used
>a
>>USB fob
>>> >> as well), using VOX for COS and a GPIO for PTT.
>>> >> It worked for the most part, but sometimes the PTT would get
>stuck
>>> >> (Murphy's law- at the worst possible moment, like when still 1.5
>>hours away
>>> >> coming back from a hamfest in north Texas & it is deadkeying the
>>local
>>> >> repeater--called the house and had daughter unplug the powerpole
>>connection
>>> >> feeding the whole thing). That might have been an RFI thing
>>causing it, as
>>> >> I had it in a plastic box, so I wonder if a metal
>>enclosure/ferrites might
>>> >> have helped....
>>> >>
>>> >> I just think, why did they include such things (sound and GPIO)
>if
>>they
>>> >> dont work? :-)
>>> >>
>>> >> thanks again, and Ill have a look at the Nano solution.
>>> >>
>>> >> 73
>>> >> Jim
>>> >>
>>> >>
>>> >> At 12:13 AM 1/23/2017, David Lang wrote:
>>> >>
>>> >>> On Sun, 22 Jan 2017, "Jim Kinter Jr. via arm-allstar" wrote:
>>> >>>
>>> >>> Greetings,
>>> >>>> I have been searching over the info on the site and mail list,
>>and cant
>>> >>>> seem to find if any instructions are available for using the
>>Pi's GPIO for
>>> >>>> COS/PTT yet.
>>> >>>> I have found where it said it will be included in a future
>>release, and
>>> >>>> some other instructions with config settings, but nothing more
>>definitive
>>> >>>> (which pins to use for what, config settings for those pins,
>>etc).
>>> >>>>
>>> >>>> I friend of mine is using this setup on his repeater with URI,
>>and Id
>>> >>>> like to use what I already have without spending $100 a pop on
>>URIs per
>>> >>>> setup (I already have a few Pi's at my disposal)
>>> >>>> I had bought a half dozen USB sound FOBs, but all were blobbed
>>(they
>>> >>>> were cheap, so I even attempted to mine down into one blob to
>>see what I
>>> >>>> could see, probably effectively destroying the one FOB/losing
>>$2).
>>> >>>>
>>> >>>> So is this capability available yet, and if so, where might I
>>find more
>>> >>>> info?
>>> >>>>
>>> >>>
>>> >>> It is not yet available, they have decided to not use the GPIO
>>pins
>>> >>> directly, but to run things through an arduino nano, so it's a
>>$20 option
>>> >>> instead of a $100 option.
>>> >>>
>>> >>> hardware details are available at:
>>> >>>
>>> >>> https://sites.google.com/site/radiofarmprojects/home/hamvoip
>>> >>> -nano-interface
>>> >>>
>>> >>> https://hamvoip.org/hamradio/Nano_Allstar_Interface/
>>> >>>
>>> >>> support for this is not yet in any release of the allstar
>>software, but
>>> >>> they were planning a release in December that was postponed due
>>to a death
>>> >>> in the community. They were planning to have this support either
>>in that
>>> >>> release or within a couple of weeks after.
>>> >>>
>>> >>> David Lang
>>> >>>
>>> >> _______________________________________________
>>> >>
>>> >> arm-allstar mailing list
>>> >> arm-allstar at hamvoip.org
>>> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>> >>
>>> >> Visit the BBB and RPi2/3 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/3 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/3 web page - http://hamvoip.org
>>> 
>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>arm-allstar mailing list
>arm-allstar at hamvoip.org
>http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
>------------------------------
>
>End of arm-allstar Digest, Vol 32, Issue 28
>*******************************************
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>arm-allstar mailing list
>arm-allstar at hamvoip.org
>http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
>------------------------------
>
>End of arm-allstar Digest, Vol 32, Issue 30
>*******************************************

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.