[arm-allstar] BCD Control

Tue Apr 10 17:07:39 EST 2018

That fixed it! Many Thanks! Eric (N7JYS) Marshall's Communications

      From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
 To: ARM Allstar <arm-allstar at hamvoip.org> 
Cc: Doug Crompton <wa3dsp at gmail.com>
 Sent: Tuesday, April 10, 2018 3:38 PM
 Subject: Re: [arm-allstar] BCD Control

OK now I understand. I thought you were talking about sending actual data
to another radio.

Change -

  /usr/bin/asterisk -rx "rpt localplay $NODE1 /tmp/set-channel"

to

  /usr/bin/asterisk -rx "rpt localplay $NODE /tmp/set-channel"

Will make the change in the distributed version.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Tue, Apr 10, 2018 at 4:29 PM, "Eric Harrison via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> I understand how bcd_control_pi.sh is suppose to work but as i stated, is
> dose notfunction the way it should. When you change the second parameter in
> the command it does not send the voice  to that node specified. It defaults
> to sending it to $NODE1 regardless of what the second parameters say.
>  Eric (N7JYS) Marshall's Communications
>
>      From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
>  To: ARM Allstar <arm-allstar at hamvoip.org>
> Cc: Doug Crompton <wa3dsp at gmail.com>
>  Sent: Tuesday, April 10, 2018 1:37 PM
>  Subject: Re: [arm-allstar] BCD Control
>
> Eric,
>
>  As I stated in my response the bcd_control_pi.sh version does NOT handle
> more than one node. The second parameter in the Pi version only changes
> where the output voice goes. Only the USB control version which is the
> preferred to use handles multiple nodes with different bits. I recommend
> you use the USB FOB GPIO if you want to use more than one node. The pi
> version would need to be modified to do this and you would need to use
> another set of four GPIO lines.  The reason behind using the FOB is that it
> is already connected to the radio it is controlling and adding the extra
> GPIO bits is trivial assuming you are using a FOB where you can get to the
> bits. It gets away with a bunch of lines run from the Pi GPIO which end up
> being an RF antenna both in and out.
>
> If you must use the Pi version for more than one node the easiest way right
> now would be to copy it to a new script name -
>
> cp bcd_control_pi.sh bcd_contrl_pi2.sh
>
> Then in the 2 version change the GPIO ports to those you are using for the
> second radio.
>
> Then hook the various defined bits from the pi2 version to the second
> radio.
>
> You would then call the pi version for radio 1 with its node# for voice
> and the pi2 version for radio 2 with its node# for voice.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
> On Tue, Apr 10, 2018 at 2:10 PM, "Eric Harrison via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Doug, I am using the latest and greatest most up to date software on a
> pi3
> > utilizing the GPIO Pins
> >
> > In stanza 42408  I have this command for every channel i use.
> > C701=cmd,/usr/local/sbin/bcd_control_pi.sh 1 42408 ect.
> > C716=cmd,/usr/local/sbin/bcd_control_pi.sh 16 42408
> > My understanding of this command is if you don't specify the node it will
> > defualt to the first Node configured.
> > And if you do specify with a node number regardless of which node stanza
> > you have it under it should execute based
> > on  the node in the command,  just like the  /usr/local/sbin/sayip.sh
> > <Node> command works. It doesn't  matter what node stanza it is under.
> > Changing thenode number at the end of this command sends it to that Node
> > that is configured.
> >
> >  Eric (N7JYS) Marshall's Communications
> >
> >      From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
> >  To: ARM Allstar <arm-allstar at hamvoip.org>
> > Cc: Doug Crompton <wa3dsp at gmail.com>
> >  Sent: Tuesday, April 10, 2018 10:30 AM
> >  Subject: Re: [arm-allstar] BCD Control
> >
> > Eric,
> >
> > I assume you are using the bcd_control_usb_fob.sh in the current
> > distribution of V1.5? There is no bcd_control.sh???
> >
> > You need to define the GPIO commands in each stanza in simpleusb.conf -
> it
> > basically would be the same in each stanza. The script sends the command
> to
> > the defined node and unless there is a bug in cop,61 it should work. Do
> you
> > have it defined in both stanzas in simpleusb.conf? I have not tested with
> > multiple nodes on one server but it should work.
> >
> > If you are using the Pi version then this would not work. You would have
> to
> > modify the code to use different GPIO ports for each node. Which actual
> > script are you using?
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> >
> >
> >
> >
> >
> > On Tue, Apr 10, 2018 at 10:32 AM, "Eric Harrison via arm-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > I have started to use the bcd_control_pi.sh script and have notice no
> > > mater what node number I attache to the endof the command the ptt and
> > voice
> > > are sent to $NODE1. I have two nodes configured on one pi and have
> > > verifiedboth node are functioning correctly. Running
> > > /usr/local/sbin/sayip.sh 42408 sends it to 42408 and
> > > /usr/local/sbin/sayip.sh 42409  sends it to 42409.
> > > If is issue the cmd.,  /usr/local/sbin/bcd.control.sh 1 42408, it
> sends
> > > the ch.1 command to 42408. If I issue the cmd., /usr/local/sbin/bcd.
> > > control.sh 1 42409, it still sends the ch.1 command to 42408.
> > >
> > > Guessing a bug or am I missing something in setup?
> > >
> > >  Eric (N7JYS) Marshall's Communications
> > > _______________________________________________
> > >
> > > 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
> _______________________________________________
>
> 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