[arm-allstar] remote base node functioning question

David McGough kb4fxc at inttek.net
Wed Jun 24 00:31:41 EST 2015 

Hi,

Yes, I agree about the RB code being quirky! Long before I went the hamlib
route, I played with the built-in app_rpt control code. I quickly got
frustrated over several things, including minimal error handling. If the
radio control didn't happen like clock-work, Asterisk could lock up tight
or partly crash. This was a source of frequent frustration for several
months, because: My RB radios get used a lot--typically hours a day, about
every day. They needed to be very stable or it was constant frustration
via "tech support" calls (AKA: "RB xyz doesn't seem to be working right").

So, that's how I ended up using hamlib and leaving the RB setup like a
standard simplex node. I was happy, my systems were finally very stable, 
and I didn't look back except in studying how to improve app_rpt.

Anyhow, each user can certainly use whatever solution they're happy with!  
The app_rpt code is there, and many seem satisfied. As the ancient saying
goes: There are many roads to Rome!


73, David KB4FXC


On Wed, 24 Jun 2015 wb3awj at comcast.net wrote:

> By that method you would use what ever DTMF commands that you've mapped.
> 
> 
> But here's a gotcha.....
> 
> 
> I can't speak for the BBB or Pi versions, mine runs under Acid. I'm 
assuming most of the same follows suit here......
> 
> 
> If you designate the node as a "Remote Base" some of the functionality 
is changed. 
> 
> 
> For instance if the node is not connected to any other inbound node, or 
IaxRpt/Zoiper extension, it cannot initiate a command.  
> 
> 
> So let's say you have only CLI session going, "rpt fun xxxxx *yyyy" 
won't do a do a thing. But dial in with IaxRpt and then it will. But of 
course if you have your functions-phone assignment and context set 
properly you should be able to dial the commands from IaxRpt or Zoiper.
> 
> 
> In a community setting another thing is there can only be one 
connection at a time to the remote base. That's why I have a few extra 
hubs running. Connect to the base from a hub, then however many others 
you want in on it connect to the hub.
> 
>
> If you coordinate the DTMF commands on the remote base to be the same 
sequences as macros on your other nodes (like the *5217 in the one I 
posted where *52 replaced *0), and command of the base should be nearly 
transparent to the users.
> 
> 
> This agile remote base stuff is different and and a bit quirky.
> 
> 
> Robert A. Poff
> 
> Loganville, Pa
> 
> 
> 
> On Tue, Jun 23, 2015 at 5:10 PM -0700, "Michael Hebert" <mhebert1975 at gmail.com> wrote:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Let me add some more info. If I connect to my remote base node with putty and enter the asterisk -rvvv, how would I issue commands to the remote base node? 
> rpt fun 731 *????
> My goal is to be able to use my laptop at a remote location and remotely control the node using XIPRadio window client with * commands
> On Tue, Jun 23, 2015 at 5:02 PM, Michael Hebert <mhebert1975 at gmail.com> wrote:
> Ah, I see it now. 
> So the current setup I have now is a Pi version 2 1.0 image. It is connected to my IC-7000 using a USB cable. It is working using hamlib with putty. I am using "rigctl -m 360 -r /dev/radio -s 9600" then issuing the commands and the radio response correctly. I then quit rigctl
> I then connect to my remote base node using XIPRadio window client. I issue the *91 command and hear KD5DFB over the computer speakers. I have tried several different ways to issue remote commands directly to the remote base node. 
> Is it not possible to connect directly to a remote base , login and issue control command?
> 
> On Tue, Jun 23, 2015 at 4:38 PM, Robert A. Poff WB3AWJ <wb3awj at comcast.net> wrote:
> >From one of the other nodes, for example my UHF repeater (27784), it sends a "remote command" to a connected node.
> In this case my 2m remote base (28260).
> 
> *4         - Execute a remote command on another node
> 28260 -  The node to command
> *5217  - The command to execute  ( in this case tune the Syntor to channel 17 as defined in its rpt.conf)
> #           - End the remote command session.
> 
> From: "Michael Hebert" <mhebert1975 at gmail.com>
> To: "ARM Allstar" <arm-allstar at hamvoip.org>
> Sent: Tuesday, June 23, 2015 4:33:04 PM
> Subject: Re: [arm-allstar] remote base node functioning question
> 
> All,
> This is really good stuff!! I have been wanting to remote base my IC-7000 for years. I am on the last leg and needs some direction. I am able to control my 7000 using hamlib without any problems. I connect to my node using XIPRadio window client. I issue the *91 command and hear my callsign announced. For the life of me, I cannot find out the correct syntax to control the radio. 
> I am looking at the marco that Robert wb3awj posted "217=*428260*5217#                      ;Select Channel 17 on 2m"
> What does the *428260 reference to?
> Thanks in advance!
> Michael KD5DFB
> On Mon, Jun 22, 2015 at 5:44 AM, Sam Skolfield <kj6qfs at gmail.com> wrote:
> Before I get to embarrassing myself, I want to thank everyone that has helped me here on the thread. The helpfulness of this community never ceases to amaze me, and I can't wait to pay it forward. David even went so far (out of the kindness of his own heart) as to do research on my xcat and it's history with hamlib. 
> Now, *drumroll* 
> 
> I WASN'T DOING A # AT THE END OF THE REMOTE FUNCTION!
> 
> The system now works ABSOLUTELY perfectly. Very smooth and reliable so far. I've been exercising every feature I can, and I can't seem to get anything to misbehave.
> Thanks again to David, Sam, Doug, Ken, Tim, and Robert. 
> 
> 73
> On Thu, Jun 18, 2015 at 7:01 AM, <wb3awj at comcast.net> wrote:
> 
> 
> Are you ending the remote command with a # ?
> 
> For example the macro definitions to control the remote base on my other nodes looks like this :
> 
> [macros]
>  ..
>  ..
>  217=*428260*5217#                      ;Select Channel 17 on 2m
>  ..
>  ..
> 
> An entry for each channel.
> 
> On the remote base itself, I've used *52 instead of the default memory select code (*0 I think). That way whether you're on one of the other nodes or IaxRpt/Zoiper directly connected to the remote, the channel change command is the same.
> 
> Robert A. Poff
>  Loganville, Pa
> 
> 
> On Wed, Jun 17, 2015 at 8:50 PM -0700, "Sam Skolfield" <kj6qfs at gmail.com> wrote:
>  
> Upon further poking, I've established that my problem has nothing to do with remote bases; it seems like asterisk hangs for me after I function any linked node (anytime I use a *4 to prefix another connected node) 
> 
> I tried simply connected my main BBB's  simpleusb node (not a remote base node) to my other BBB's main simpleusb node (not a remote base node). I then functioned the linked BBB to do a *81. It did so properly, but then my "main" BBB locks up and wont take any more commands. 
> 
> Any ideas?
> On Wed, Jun 17, 2015 at 3:06 PM, Kenneth Grimard <n1dot1 at gmail.com> wrote:
> ok very good then
>  
>  i will have to try that then later when i get a bbb or raspi2,
>  
> ken
>  
> On 06/17/2015 05:58 PM, Sam Skolfield wrote:
> Ken, like I said, the USB-serial adapter is working perfectly with my BBB. Frequency commands, etc are working just fine!
> On Wed, Jun 17, 2015 at 7:20 AM, Kenneth Grimard <n1dot1 at gmail.com> wrote:
> as i said to you before sam I have gotten this to work with the acid code.
>  it will not work for full cat control using a usb serial adapter i had tried that myself.
>  you need a real pc with a real serial port. I am using a pc with a pentium 4 processor with a 
>  real serial port usb to serial just does not work at all.
>  
>  other wise it does work very well and you have to program the icon 706 a certain for it to work also.
>  
>  i have been successful with this. unless the code can be modified to use the gpio on a raspi.
>  
>  usb to serial just does not work at all not with out modifying the code.
>  
>  cat control is done via the icom ci-v protocol from with in app_rpt.c
>  
>  
> ken n1dot
>  
>  
>  
>  
>  
>  On 6/17/2015 2:11 PM, Sam Nabkey wrote:
> 
> 
> Sam Scofield is running the xcat.  I was just trying to run an icom 706 or a Kenwood tm700d. 
> 
> Whenever you call a node a remote base, weirdness happens to the usb adapter.   It's just not workable in the bbb or even later revs of acid.
> 
> This interests me... I will have to run some experiments soon.
> 
> Which radios are you running and do you have any good scripts you could pass on and maybe how you operate it as a user?  I'd appreciate any input.
> 
> Sam NABJEY K8SN..On Jun 17, 2015 8:40 AM, "David McGough" <kb4fxc at inttek.net> wrote:
> 
>  Sam,
>  
>  I haven't personally used the Syntor X-cat adapter. I looked at their
>  yahoo group and the documentation in the "files" section. Otherwise, I've
>  used rigctl to manage many different radios, with great success. The first
>  place to start is from the BBB shell prompt, with remote-base support
>  disabled in app_rpt.  Once you get familiar with the various rigctl
>  commands, macros for access via AllStar are pretty easy--just directly
>  call the rigctl command from AllStar.
>  
>  I'm guessing you're using the CI-V interface method for the Xcat? Are you
>  using full VFO capability, or just changing the Syntor's modes (AKA:
>  channels)?
>  
>  If simply changing modes, I'm guessing some command something like this
>  will work:
>  
>  /usr/local/bin/rigctl -r /dev/ttyUSB0 -m 311 -s 19200 -c0x20 h 27
>  
>  -r /dev/ttyUSB0   #### serial interface to use...
>  -s 19200    #### serial data rate (Xcat uses 19200, based on the manual)
>  -c0x20   #### CI-V address (Xcat is fixed at 0x20, from the manual)
>  h 27   #### "h 27"  changes to memory channel channel 27
>  
>  
>  "rigctl -l" will get a list of supported radio back-ends. I'd recommend
>  trying various Icom back-ends, hopefully finding something that works
>  100%.
>  
>  rigctl -l #### Get list of available back-ends
>  
>  "rigctl -m 311 -u" will get a list of supported features for a given
>  back-end, try this. Note that the "-m 311" uses the ic-706mk2g back-end.
>  
>  rigctl -m 311 -u #### Get supported features for back-end 311
>  
>  
>  I'll try to help further, once I understand more about your setup.
>  
>  
>  73, David KB4FXC
>  
>  
>  
>  On Wed, 17 Jun 2015, Sam Nabkey wrote:
>  
>  > That's cool.  Care to share some setup examples?  I'd love to see them.
>  >
>  > K8SN
>  > On Jun 17, 2015 6:51 AM, "David McGough" <kb4fxc at inttek.net> wrote:
>  >
>  > >
>  > > Hi Sam,
>  > >
>  > > I'm guessing that you're trying to use the built-in remote-base code in
>  > > app_rpt??  If so, the only thing I can suggest at this point is to use
>  > > hamlib (the "rigctl" program), instead of the built-in code.
>  > >
>  > > I use hamlib for several radios hosted by BBB's, etc., and it works
>  > > perfectly for me.
>  > >
>  > >
>  > > 73, David KB4FXC
>  > >
>  > > On Wed, 17 Jun 2015, Sam Skolfield wrote:
>  > >
>  > > > Really too bad, I'm so close to success with what is obviously one of
>  > > very
>  > > > few attempts at a frequency-agile BBB node. Looking at the console with
>  > > any
>  > > > level of verbosity doesn't seem to reveal any useful information.
>  > > > Unfortunately, it doesn't look like I'll be able to fix this any time
>  > > soon.
>  > > >
>  > > >
>  > > > On Tue, Jun 16, 2015 at 2:50 PM, Sam Nabkey <sam.nabkey at gmail.com>
>  > > wrote:
>  > > >
>  > > > > I wish I had time and more knowledge. ..
>  > > > >
>  > > > > It's fun to try and figure it all out. .
>  > > > > On Jun 16, 2015 5:06 PM, "Sam Skolfield" <kj6qfs at gmail.com> wrote:
>  > > > >
>  > > > >> Hi Sam!
>  > > > >> That's frustrating! Perhaps someone can help us fix this bug? There
>  > > has
>  > > > >> to be more people that want to use frequency agile remote bases than
>  > > just
>  > > > >> the two Sams....
>  > > > >>
>  > > > >> On Tue, Jun 16, 2015 at 8:05 AM, Sam Nabkey <sam.nabkey at gmail.com>
>  > > wrote:
>  > > > >>
>  > > > >>> This is one of the same issues I experienced with the bbb code.  The
>  > > cli
>  > > > >>> will be blowing can't hang up errors at you while this is going on.
>  > > My
>  > > > >>> only recourse was to reboot.
>  > > > >>>
>  > > > >>> I went to an acid version before the changes were made to the channel
>  > > > >>> drivers that was "fixed" to work reliably on the bbb to get my
>  > > remote to
>  > > > >>> work.
>  > > > >>>
>  > > > >>> Sam K8SN
>  > > > >>> On Jun 16, 2015 8:04 AM, "Sam Skolfield" <kj6qfs at gmail.com> wrote:
>  > > > >>>
>  > > > >>>> David, I'm using a *1 xxxx (xxxx being the node)
>  > > > >>>>
>  > > > >>>> _______________________________________________
>  > > > >>>>
>  > > > >>>> 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/
>  > > > >>>
>  > > > >>
>  > > > >>
>  > > > >>
>  > > > >> --
>  > > > >> KJ6QFS
>  > > > >> Sam Skolfield
>  > > > >>
>  > > > >> _______________________________________________
>  > > > >>
>  > > > >> 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/
>  > >
>  >
>  
>  _______________________________________________
>  
>  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/
> 
>  
> 
>

More information about the arm-allstar mailing list