[arm-allstar] remote base node functioning question--real hamlib example

[Sam Nabkey]

That is a great idea..  I would ask that if you go that way, that you add
some hooks in the new version to help pace the audio.

One if the things I noticed doing linux scripts or python is they sometimes
talk over each other.
On Jun 24, 2015 3:37 PM, "Doug Crompton" <doug at crompton.com> wrote:

> Yes exactly and this is our goal in the future to move more stuff out of
> app_rpt which could run much more efficiently stand-alone. App_rpt is a
> kluge of code which is hard to analyze and troubleshoot and far less
> efficient than it could be without all the bloat. When Allstar was written
> some of this standalone SW was not available or not there yet. Now that it
> is there is no reason not to use it. Everything does not have to be built
> in to app_rpt. Doing things in Linux scripts is a great way to do it.
> Select your language, bash, perl, php, python, etc.
>
>
>
> *73 DougWA3DSPhttp://www.crompton.com/hamradio
> <http://www.crompton.com/hamradio>*
>
>
> ------------------------------
> Date: Wed, 24 Jun 2015 12:28:56 -0500
> From: mhebert1975 at gmail.com
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] remote base node functioning question--real
> hamlib example
>
> At this point, I think that might be the easier option! Thanks for
> posting.
>
> On Wed, Jun 24, 2015 at 11:08 AM, David McGough <kb4fxc at inttek.net> wrote:
>
>
> Hi,
>
> The most simplistic way to utilize hamlib is via simple shell-script calls
> from AllStar.  Here is a super simple -working- sample that demonstrates
> changing to channels 1, 2 and 3 on a 706mk2g.
>
> ....Add this to rpt.conf in the desired functions stanza:
>
>
> [functions]
> 921=cmd,/usr/local/bin/rigctl -r /dev/ttyUSB0 -m 311 -s 9600 -c0x58 h 1
> 922=cmd,/usr/local/bin/rigctl -r /dev/ttyUSB0 -m 311 -s 9600 -c0x58 h 2
> 923=cmd,/usr/local/bin/rigctl -r /dev/ttyUSB0 -m 311 -s 9600 -c0x58 h 3
>
>
>
>
> So, DTMF commands *921, *922, *923 change to channels 1, 2 or 3.  Note
> that the path to rigctl and path for the serial device must be correct.
>
> I use much more sophisticated scripting, including a sqlite3 database,
> etc....The sky is the limit!  And, this is all really quite easy to do,
> supporting a multitude of different radios.
>
>
> 73, David KB4FXC
>
>
>
> On Wed, 24 Jun 2015 wb3awj at comcast.net wrote:
>
> > Good point..
> >
> >
> > In fact,  I had to make  small changes on the  Acid source to get it
> to work.
> >
> >
> > Can you post some examples of how you link DTMF function codes to Hamlib
> calls?
> >
> >
> > Robert A. Poff
> >
> > Loganville, Pa
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page -
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
>
>
> _______________________________________________ arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit the
> BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB web page -
> http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150624/b22e55b6/attachment.html>