[arm-allstar] Trying to blue-sky a project...

[Doug Crompton]

Carl,

  I am not an expert on hamlib but it is a completely separate program and
not connected to Allstar other than you can call it and send commands to a
rig from Allstar.

First of all a little history.  Remote control of a limited number of rigs
was built into Allstar in its infancy. This was before the advent of so
many rigs having this capability and a program, hamlib, that consolidated
all this control into one program. We are taking the internal remote base
control out of Allstar and using hamlib to do this control. This eliminates
about 5000 lines of code that is largely undocumented , buggy, and also
only supports a very limited number of mostly older rigs. To expand on
this, which we are not going to do, would just be building another hamlib.

Hamlib has a fixed set of commands that are mapped to the radio selected.
So no matter what rig you use 'F' returns the frequency and 'F 147000000'
sets a desired frequency.

The setup for the rig is only done once specifying the rig, port, baudrate,
etc.  This would be done at boot via a script and could be changed at will.
Then you would use a script to translate DTMF sequences to actual hamlib
commands. This script does not exist and would have to be created. I gave a
simple example in a message about a week ago that could be expanded on. You
don't need all the commands mapped to DTMF, just the ones you want to use.

I suggest you test control the rig you intend to use via direct rigctl
commands at the Linux prompt. If that works then you can certainly map the
same command to a DTMF sequence.


*73 Doug*

*WA3DSP*

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

On Tue, Jan 8, 2019 at 1:23 PM "Carl Swanson via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Good day folks...
> I'm trying to conceptualize a remote base project I will be deploying
> early next month. I have a FT-897 on-site which I am endeavoring to control
> via Allstar. I'm going to use a RasPi 3b+ and the current hamvoip image. I
> have the parts and pieces, but I am trying to more fully understand the
> relationship between app_rpt and hamlib.
> I understand the idea that app_rpt will handle the audio and PTT via the
> DMK URI, and hamlib will change frequency, mode, power level, etc.
> 1) Is app_rpt and hamlib more interrelated in the backend? I have seen
> some older posts that specify that, for specific commands, you can invoke
> rigctl with a defined set of parameters to change the frequency and what
> not (I have perused the man pages, but it only got me so far).
> 2) If I setup rigctld and symbolically link the FTDI USB cable with an
> easily known moniker (such as /dev/yaesu), can you eliminate the need to
> call out rig type, COM port speed, stop bits, etc?
> I feel like I am missing something else big here. Are there any common
> pitfalls that I am falling into?
> 73,
> Carl, K6CRSNode 2391 under re-construction
> _______________________________________________
>
> 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
>