[arm-allstar] TS-2000 Hamlib - DTMF command structure

Mon Apr 9 10:18:51 EST 2018

John,

  Here is the short answer on this using the method from the howto's to
call the extensions file.

- DTMF a command via Allstar

- extensions.conf file routes the command to a script
   This could be written in any language you are comfortable with - bash,
perl, python, C, you name it.

- The script communicates the command to hamlib where it is processed and
sent to the rig

- If hamlib has a return code you check it or execute a hamlib command to
see if what you changed actually happened.

- Send verbal confirmation of the command back to the user

- end the script and wait for another command

and a little more detail -

- User sends *8410

- Command is sent to extensions.conf

- Parameter "10" is sent to script

- Script processes parameter and see's that this means raise frequency by 5
Khz

- Script sends command to do this to hamlib

- Script checks hamlib for actual frequency

- Script talks the frequency over Allstar locally to user

- Script ends

Another example for setting a frequency -

- User sends *842014655

- Parameter 2014655 is sent to script

- Script determines 20 is followed by frequency strip 14655

- New frequency is sent to hamlib in proper format

- Frequency is sent to the radio

- Frequency is read back from radio

- Confirmation is send to user via Allstar - "Frequency set to 146.55"

- end script

So you see most all of the work is done in the script passing parameters to
hamlib.

*73 Doug*

*WA3DSP*

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

On Mon, Apr 9, 2018 at 7:05 AM, "John via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> David,
> Thank you for the link to WebRig.  I will work on implementing that.
>
> A question to all:
>
> I am trying to figure out the cleanest way to use DTMF commands from
> within app_rpt to utilize hamlib.
>
> I am currently able to issue commands from the shell to connect to and
> control the radio, as well as read values.
>
> My question is the best method to accomplish this remotely from a radio
> with a Touch Tone pad pad.
>
> For example, I can connect to the TS-2000 by writing at the command prompt:
>
> [root at N1CTF asterisk]#  rigctl -m 214 -r /dev/ttyUSB1 -s 9600 -D NONE f
>
> and it returns the frequency in Hz.
>
> My question is how best to send a command and wait for the response from
> the radio and synthesize speech and transmit it as confirmation.
>
> Is there a best practice for this within the function stanza in rpt.conf
> directly?
>
> Or should I write a Perl script to do that which would then receive
> arguments and concatenate the correct gsm files (much like say24time.pl)
> and then play them using localplay?
>
> In this case, I assume there would be a series of individual DTMF commands
> which would
> call the script and pass the desired arguments.
>
> My question is basically: do I need a script to handle the interface
> between app_rpt and  hamlib's rigctl class? Or is there a more preferred
> way?
>
> Thanks again for your assistance.
>
> Regards,
>
> John
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On March 28, 2018 1:00 PM, <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.  Re: Kenwood TS-2000 (David McGough)
> > 2.  Re: Echolink and Proxies / Relays.... (David McGough)
> > 3.  Re: Echolink and Proxies / Relays.... (Jeffrey Lehman, KC8QCH)
> > 4.  low audio with full-888s (VE3kai)
> > 5.  Re: low audio with full-888s (Doug Crompton)
> > 6.  Login problem after update - repeat announcement (Doug Crompton)
> >
> >
> > Message: 1
> >
> > Date: Tue, 27 Mar 2018 22:32:25 -0400 (EDT)
> >
> > From: David McGough kb4fxc at inttek.net
> >
> > To: ""john.chartkoff via arm-allstar"" arm-allstar at hamvoip.org
> >
> > Cc: "john.chartkoff" john.chartkoff at protonmail.com
> >
> > Subject: Re: [arm-allstar] Kenwood TS-2000
> >
> > Message-ID:
> >
> > Pine.LNX.4.44.1803272230080.23417-100000 at goliath.inttek.net
> >
> > Content-Type: TEXT/PLAIN; charset=US-ASCII
> >
> > Hi John,
> >
> > For a simple web-based access front end to hamlib, this might be a
> >
> > useful project to get ideas from:
> >
> > https://github.com/ntoulasd/Webrig
> >
> > 73, David KB4FXC
> >
> > On Tue, 27 Mar 2018, "john.chartkoff via arm-allstar" wrote:
> >
> > > Greetings to the group from Columbus, Ohio,
> > >
> > > I am trying to remotely control a Kenwood TS-2000 as a remote base
> using DTMF commands over AllStar. Can anybody point me in the right
> direction to anybody who is working on this currently?
> > >
> > > Ultimately, I would like to write a GUI so that I can control it
> digitally over the AllStar network. I can already control it using a TTY
> cable. I was hoping to come up with a cleaner, more integrated solution.
> > >
> > > Please comment on this, as I am a Java software developer, and am
> always looking for a new project.
> > >
> > > Thank you,
> > >
> > > 73'
> > >
> > > John R. Chartkoff --N1CTF --Node 29309
> > >
> > > 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: Wed, 28 Mar 2018 07:18:02 -0400 (EDT)
> >
> > From: David McGough kb4fxc at inttek.net
> >
> > To: ""Charles Powell via arm-allstar"" arm-allstar at hamvoip.org
> >
> > Subject: Re: [arm-allstar] Echolink and Proxies / Relays....
> >
> > Message-ID:
> >
> > Pine.LNX.4.44.1803280711080.23417-100000 at goliath.inttek.net
> >
> > Content-Type: TEXT/PLAIN; charset=ISO-8859-1
> >
> > This morning I tried duplicating this wrong callsign issue, connecting
> >
> > from a Win7 client (running the MSWin software rev 2.0.908) and various
> >
> > public proxies and I even setup a private proxy to experiment with
> >
> > (running the EchoLinkProxy java software, rev 1.2.3) ...No luck, the
> >
> > proper callsign showed on the AllStar side every time.
> >
> > Does anyone know how to duplicate this issue while using the MSWin
> >
> > software???? ....This is much more convenient for me than running an app
> >
> > for a mobile device. Thoughts??
> >
> > 73, David KB4FXC
> >
> > On Tue, 27 Mar 2018, "Charles Powell via arm-allstar" wrote:
> >
> > > This happens when the Echolink user has a proxy connection, such as
> >
> > from an iPhone, iPad, or Android phone. Dave, KB4FXC, has been working
> >
> > on the code. I pointed this problem out to him and he has it on his
> >
> > "to do" list. I think if you connect from a computer, you will see
> >
> > that the information that registers is correct - but not from a phone.
> >
> > > 73,
> > >
> > > Charles - NK8O
> > >
> > > > On Mar 27, 2018, at 1:16 PM, Sandy via arm-allstar
> arm-allstar at hamvoip.org wrote:
> > > >
> > > > Hi Doug, and the rest of the Allstar Team.
> > > >
> > > > When I connect or receive an Echolink connection the ID is wrong.
> > > >
> > > > Not only is the ID wrong it is random. Each connection has a
> different ID. (call and number)
> > > >
> > > > This is using the Android App connecting to Allstar with Echolink
> active.
> > > >
> > > > I connected to myself and then to a friend???s node ??? same results.
> > > >
> > > > When connecting Echolink via Allstar to Allstar, the ID is correct.
> > > >
> > > > The Echolink via Allstar to Allstar was just for a test.
> > > >
> > > > I almost never use Echolink, but I was told by a friend that they
> connected to me via Echolink.
> > > >
> > > > I examined my connection log and according to it, they did not. The
> log listed an Echolink ID for the same time period, but was not someone
> that I recognized.
> > > >
> > > > This maybe a problem on Echolink???s side, but thought that I would
> bring it up.
> > > >
> > > > Thanks for the effort and time that is given to Allstar by you guys.
> > > >
> > > > 73,
> > > >
> > > > Sandy ??? w9sbe
> > > >
> > > > http://www.avg.com/email-signature?utm_medium=email&
> utm_source=link&utm_campaign=sig-email&utm_content=emailclient
> Virus-free. www.avg.com http://www.avg.com/email-
> signature?utm_medium=email&utm_source=link&utm_campaign=
> sig-email&utm_content=emailclient x-msg://35/#DAB4FAD8-2DD7-
> 40BB-A1B8-4E2AA1F9FDF2_______________________________________________
> > > >
> > > > arm-allstar mailing list
> > > >
> > > > arm-allstar at hamvoip.org mailto:arm-allstar at hamvoip.org
> > > >
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > >
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> http://hamvoip.org/
> >
> > --
> >
> > Message: 3
> >
> > Date: Wed, 28 Mar 2018 08:10:56 -0400
> >
> > From: "Jeffrey Lehman, KC8QCH" kc8qch at gmail.com
> >
> > To: arm-allstar at hamvoip.org
> >
> > Subject: Re: [arm-allstar] Echolink and Proxies / Relays....
> >
> > Message-ID: 1ed886c6-a4a2-b555-376a-4e93c5782c97 at gmail.com
> >
> > Content-Type: text/plain; charset=utf-8; format=flowed
> >
> > Good Morning David,
> >
> > ?? Unfortunately, it only seems to happen with the mobile apps. When
> >
> > connecting from a PC client (either Windows or Linux) it works fine. I
> >
> > also have tried to duplicate it from the PC and have "failed" as well.
> >
> > However someone else may have had luck? Not sure what the difference
> >
> > would be but yeah.
> >
> > ?? Jeff, KC8QCH
> >
> > On 3/28/2018 07:18, "David McGough via arm-allstar" wrote:
> >
> > > This morning I tried duplicating this wrong callsign issue, connecting
> > >
> > > from a Win7 client (running the MSWin software rev 2.0.908) and various
> > >
> > > public proxies and I even setup a private proxy to experiment with
> > >
> > > (running the EchoLinkProxy java software, rev 1.2.3) ...No luck, the
> > >
> > > proper callsign showed on the AllStar side every time.
> > >
> > > Does anyone know how to duplicate this issue while using the MSWin
> > >
> > > software???? ....This is much more convenient for me than running an
> app
> > >
> > > for a mobile device. Thoughts??
> > >
> > > 73, David KB4FXC
> > >
> > > On Tue, 27 Mar 2018, "Charles Powell via arm-allstar" wrote:
> > >
> > > > This happens when the Echolink user has a proxy connection, such as
> > > >
> > > > from an iPhone, iPad, or Android phone. Dave, KB4FXC, has been
> working
> > > >
> > > > on the code. I pointed this problem out to him and he has it on his
> > > >
> > > > "to do" list. I think if you connect from a computer, you will see
> > > >
> > > > that the information that registers is correct - but not from a
> phone.
> > > >
> > > > 73,
> > > >
> > > > Charles - NK8O
> > > >
> > > > > On Mar 27, 2018, at 1:16 PM, Sandy via arm-allstar
> arm-allstar at hamvoip.org wrote:
> > > > >
> > > > > Hi Doug, and the rest of the Allstar Team.
> > > > >
> > > > > When I connect or receive an Echolink connection the ID is wrong.
> > > > >
> > > > > Not only is the ID wrong it is random. Each connection has a
> different ID. (call and number)
> > > > >
> > > > > This is using the Android App connecting to Allstar with Echolink
> active.
> > > > >
> > > > > I connected to myself and then to a friend???s node ??? same
> results.
> > > > >
> > > > > When connecting Echolink via Allstar to Allstar, the ID is correct.
> > > > >
> > > > > The Echolink via Allstar to Allstar was just for a test.
> > > > >
> > > > > I almost never use Echolink, but I was told by a friend that they
> connected to me via Echolink.
> > > > >
> > > > > I examined my connection log and according to it, they did not.
> The log listed an Echolink ID for the same time period, but was not someone
> that I recognized.
> > > > >
> > > > > This maybe a problem on Echolink???s side, but thought that I
> would bring it up.
> > > > >
> > > > > Thanks for the effort and time that is given to Allstar by you
> guys.
> > > > >
> > > > > 73,
> > > > >
> > > > > Sandy ??? w9sbe
> > > > >
> > > > > http://www.avg.com/email-signature?utm_medium=email&
> utm_source=link&utm_campaign=sig-email&utm_content=emailclient
> Virus-free. www.avg.com http://www.avg.com/email-
> signature?utm_medium=email&utm_source=link&utm_campaign=
> sig-email&utm_content=emailclient x-msg://35/#DAB4FAD8-2DD7-
> 40BB-A1B8-4E2AA1F9FDF2_______________________________________________
> > > > >
> > > > > arm-allstar mailing list
> > > > >
> > > > > arm-allstar at hamvoip.org mailto:arm-allstar at hamvoip.org
> > > > >
> > > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > >
> > > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> 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
> >
> > --
> >
> > Jeff Lehman, KC8QCH
> >
> > https://kc8qch.ddns.net
> >
> > kc8qch at gmail.com
> >
> > Webmaster
> >
> > Hamilton Couny ARPSC
> >
> > https://www.hamcoarpsc.org
> >
> > hamcoarpsc at gmail.com
> >
> > AllStar 47374 Node Administrator
> >
> > World Wide Amateur Radio Guild
> >
> > https://theguildglobal.org
> >
> >
> > ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ---------------------------------------------------------------
> >
> > Message: 4
> >
> > Date: Wed, 28 Mar 2018 10:43:52 -0400
> >
> > From: VE3kai ve3kai at gmail.com
> >
> > To: arm-allstar at hamvoip.org
> >
> > Subject: [arm-allstar] low audio with full-888s
> >
> > Message-ID: 9056ACDB-E121-4E85-AE2B-34F6AA2BCF91 at gmail.com
> >
> > Content-Type: text/plain; charset=us-ascii
> >
> > Hello all. I just did the modification to my baofeng bf-888s. I have a
> DMK URIx that I have connected to it. I followed Mr Crompton's instructions
> on his web site to the letter. My version on the board is the newer short
> version. So i followed the section contributed by WB3DZZ. I also have a
> Raspberry PI 3 using the latest version of code (1.5 xxx cr17)
> >
> > I am able to connect to a node or reflector no problem. I can issue all
> start and stop commands with no problem. I hear the audio of the east coast
> reflector with no problem. The staton ID is transmitted every 9 minutes
> which comes out very clear. The issue I have is my transmit audio is low.
> To the point people can't hear me. I disconnected the bf-888s from the URIx
> and just did a local transmit and sure enough the audio is very low. I will
> be rechecking all my solder connections etc. Has anyone had a similar issue?
> >
> > One thing I just thought of while writing this article is to try a
> handheld mic. I will try this when I get home later this morning.
> >
> > Peter VE3KAI 73
> >
> >
> > ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> ----------------------------------------------------------
> >
> > Message: 5
> >
> > Date: Wed, 28 Mar 2018 11:22:27 -0400
> >
> > From: Doug Crompton wa3dsp at gmail.com
> >
> > To: ARM Allstar arm-allstar at hamvoip.org
> >
> > Subject: Re: [arm-allstar] low audio with full-888s
> >
> > Message-ID:
> >
> > CAMp6vstDOZVTr6uVpMhQdsQ_Rbt0sjVx9AB8GCJnnE5EViAKNw at mail.gmail.com
> >
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Peter,
> >
> > I want to make sure we are talking about the same thing when you say TX
> >
> > audio. TX and RX audio for a node are usually always referenced to the
> >
> > node itself. So TX audio is what you hear on your handheld and RX audio
> is
> >
> > what other hear from your handheld or radio talking to your node.
> >
> > Pin 21 of the DMK URI is where RX audio is applied from, in your case,
> the
> >
> > 888. Pin 22 is is TX audio to the 888.
> >
> > The simpleusb-tune-menu program sets these levels. Item 2 in the menu is
> >
> > RX audio and item 3 is TX audio. So item 3 sets the level of what you
> hear
> >
> > on your radio listening to your node and item 2 sets what others hear
> from
> >
> > your radio.
> >
> > In addition the B command toggles the RX boost.
> >
> > The first thing to do is to use item 2 in the simpleusb-tune-menu to set
> >
> > you RX level. There is a bar graph and whn you talk into your radio,
> >
> > transmitting to your node radio, you will see the bar graph respond. It
> >
> > should got to 5-6 Khz on the display on voice peaks. It is does not you
> set
> >
> > the value higher. Values are 1-999 and it is set to 500 at start. If you
> >
> > are way up in numbers and still not where you want to be then you can
> turn
> >
> > the boost on. If you are way low and still to high you can turn boost
> off.
> >
> > Next Item 3 in the menu is what you hear from others on your radio. This
> >
> > can be set by adjusting the radio to a known level from a known sourse
> like
> >
> > a local repeater. Then adjust the level to match the known level. Never
> so
> >
> > high to cause distortion.
> >
> > If you can't get the level correct the resistors on the audio lines from
> >
> > and to the 888 can be can be raised or lowered in value to get in range.
> >
> > 73 Doug
> >
> > WA3DSP
> >
> > http://www.crompton.com/hamradio http://www.crompton.com/hamradio
> >
> > On Wed, Mar 28, 2018 at 10:43 AM, "VE3kai via arm-allstar" <
> >
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Hello all. I just did the modification to my baofeng bf-888s. I have a
> > >
> > > DMK URIx that I have connected to it. I followed Mr Crompton's
> instructions
> > >
> > > on his web site to the letter. My version on the board is the newer
> short
> > >
> > > version. So i followed the section contributed by WB3DZZ. I also have a
> > >
> > > Raspberry PI 3 using the latest version of code (1.5 xxx cr17)
> > >
> > > I am able to connect to a node or reflector no problem. I can issue all
> > >
> > > start and stop commands with no problem. I hear the audio of the east
> > >
> > > coast reflector with no problem. The staton ID is transmitted every 9
> > >
> > > minutes which comes out very clear. The issue I have is my transmit
> audio
> > >
> > > is low. To the point people can't hear me. I disconnected the bf-888s
> > >
> > > from the URIx and just did a local transmit and sure enough the audio
> is
> > >
> > > very low. I will be rechecking all my solder connections etc. Has
> anyone
> > >
> > > had a similar issue?
> > >
> > > One thing I just thought of while writing this article is to try a
> > >
> > > handheld mic. I will try this when I get home later this morning.
> > >
> > > Peter VE3KAI 73
> > >
> > > 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: 6
> >
> > Date: Wed, 28 Mar 2018 12:50:06 -0400
> >
> > From: Doug Crompton wa3dsp at gmail.com
> >
> > To: ARM Allstar arm-allstar at hamvoip.org
> >
> > Subject: [arm-allstar] Login problem after update - repeat
> >
> > announcement
> >
> > Message-ID:
> >
> > CAMp6vsvCTKJawFenf8GP1KOWDp5a8hGq+a=TP+n5Y1X6=ybsXA at mail.gmail.com
> >
> > Content-Type: text/plain; charset="UTF-8"
> >
> > I am repeating this in case someone did not see the previous message.
> >
> > The March 26 late evening update had an error in it that would preclude
> you
> >
> > from loging in if you logged out after the update.
> >
> > For those and only those that updated on the evening of March 26 until
> >
> > midday March 27 - and you are not able to login here is the fix -
> >
> > Best to cut and paste this if you are not a good typist. When you execute
> >
> > this line you will be asked to login. It will then do the update and log
> >
> > you out. Then you can login normally.
> >
> > ssh -p 222 root at ip_address "/usr/local/hamvoip-pacman/bin/pacman
> >
> > --noconfirm --yes -Syu"
> >
> > This will update you to fix the problem. Anyone who updates now will have
> >
> > the fix and will not experience this problem. If you updated during the
> >
> > period of the problem and have not logged out just do an update from the
> >
> > menu and it will be fixed.
> >
> > Sorry for the inconvenience. Hopefully it only effected a few of you.
> >
> > For those using Putty the fix is -
> >
> > Enter host or IP and port as usual. Select ssh from the left dropdown
> menu.
> >
> > On the top of the ssh screen you will see remote command. Enter -
> >
> > ? (no quotes)?
> >
> > /usr/local/hamvoip-pacman/bin/pacman --noconfirm --yes -Syu
> >
> > select open
> >
> > enter username and password.
> >
> > The command will execute and the session will close. You can then
> normally
> >
> > log back in.
> >
> > 73 Doug
> >
> > WA3DSP
> >
> > http://www.crompton.com/hamradio http://www.crompton.com/hamradio
> >
> > --
> >
> > 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 46, Issue 61
>
>
> _______________________________________________
>
> 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