<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">So, thinking out loud here...<div><br></div><div>By using two nodes, one with the HF radio’s audio and keying, the other that takes the DTMF commands and controls the HF radio. The second node is where your Zoiper connects. The “readback” is local to the Zoiper, DTMF node, and doesn’t key the HF radio. You can even command the Zoiper node to “monitor” the HF radio node (*2+HFnode#) so that it doesn’t key at all while you tinker with the Zoiper node. <br><br><div id="AppleMailSignature">tnx<div>Mike / W5JR</div><div>Alpharetta GA</div><div><br></div><div>sent via my HP95LX </div><div><br></div></div><div><br>On Jan 20, 2018, at 4:16 PM, Phil Visalli via arm-allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">So the short story is that im setting up a node for my HF radio, including having a way to control the radio via DTMF. Having just a single standalone node, 99% of it works perfect. I can connect up to my node via zoiper, enter in a frequency that i want to tune to, bump the dial up or down in set steps, change the power ect. I've done all that with a script that leverages rigctl and that autopatch method of calling the scripts. That's handy because it allows me to enter in dynamic input (like the freq i want to tune to for example). The ONLY part that's not working perfect is speaking feedback back to the end user. It works .... but as i mentioned before, it also keys up the radio and announces over the air as well.<div><br></div><div>When you mentioned having a second hub node to announce audio feedback to, that seemed like it was going to be the answer, but like i said.... if i use that autopatch method from the hubnode connected to the HF node, as soon as i hit *62 it keys up the HF node .... and thinking about it a little more i think that's expected. I could go back to calling a bunch of different scripts via dtmf like usual(and use a hub node) but having a way to enter dynamic input is more important to me than having audio feedback. I think at this point, since it works so well aside from audio feedback, that im just going to stick with the single HF node setup and forget about having audio feedback for now. I made my first QSO while about 35 miles away from my transmitter Thurs night and got a good signal report. Pretty cool !</div><div><br></div><div>Just to answer your questions. I've been using duplex=0 and linktolink=yes. I found some mention on an old post to the mailing list suggesting that configuration for an HF node setup and it works. I was not able to key up over the hf noise until i set duplex and linktolink that way. Yes the second node was psuedo.... and i tried putting dtmf_dsp=2 into the general section of simpleusb.conf as a longshot. I set up a very minimal functions stanza on the pseudo node thinking then i could operate from that node and when i hit *62 the DTMF would pass thru to the HF node and execute my script, but it did not seem to work so i figured that dtmf_dsp=2 only worked on actual radio nodes, not on pseudo nodes.</div><div><br></div><div>In the end, i have a pretty slick .... pretty close to perfect method to operate my HF rig when im away from home. I've been working with 2 other local hams who are creating the same setup so we'll keep tinkering. I should have a chance this week to document my setup to share. Maybe with a few other eyeballs looking over it there might be more improvements to be made.</div><div><br></div><div>Phil </div><div>K2ELV</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 20, 2018 at 2:31 AM, "Doug Crompton via arm-allstar" <span dir="ltr"><<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small">Phil,</div><div style="font-family:tahoma,sans-serif;font-size:small"><br></div><div style="font-family:tahoma,sans-serif;font-size:small"> I am trying to wrap my head around what you are doing. On the HF radio side you are using COS and PTT or are you using COS and VOX to/from the radio? If you establish a connection as long as neither end has COS true then it should be unkeyed. You definitely don't want to use duplex=2 in rpt.conf but maybe experiment with duplex=1 or 0. I have never done what you are doing so I have no first hand knowledge. The second node you setup is pseudo correct? So no FOB and therefore no COS? If that is the case perhaps it somehow thinks it is full duplex when you come in via zoipier and use the patch method. Allstar is full duplex and when using a device that is full duplex like a phone or computer and zoipier or iaxrpt it would probably assume that. In the windows version of iaxrpt you can select duplex but I don't think you have that option in the Android version and I have no idea about zoipier. If two people were running full duplex capable endpoints like iaxrpt on a computer it would or could be truly full duplex, both could remain keyed and talk back and forth. Just thinking out loud here about what could be happening.</div><div style="font-family:tahoma,sans-serif;font-size:small"><br></div><div style="font-family:tahoma,sans-serif;font-size:small">Maybe it would be better to not use the patch and instead use DTMF to functions defined on the node you are coming in on to control the radio. The functions would call the script and within the script would localplay to that node. I probably need a better understanding of what you are doing.</div><div style="font-family:tahoma,sans-serif;font-size:small"><div dir="ltr"><div style="font-family:tahoma,sans-serif;font-size:small"><br clear="all"></div><div><div class="gmail-m_6001788817232563785m_-2033792403576901437gmail_signature"><div dir="ltr"><div><div><b><font size="4">73 Doug<br></font></b></div><b><font size="4">WA3DSP<br></font></b></div><b><font size="4"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamrad<wbr>io</a><br></font></b></div></div></div>
</div>
<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 19, 2018 at 3:26 PM, "Phil Visalli via arm-allstar" <span dir="ltr"><<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Im working on trying this out with a second radioless node. The problem i have now is that when i hit *62xxxx, the radioless node is keying up, and keying up the radio on the node with the HF rig. The script runs and works, and it does what its supposed to... its just keying up the radio the whole time. This is why i asked about dtmf_dsp=2 in the other thread. My thought is now to execute the command on the HF node, from the radioless node and im trying to avoid having to use *4 to remote command it. That should work fine. Both nodes are on the same server so i can easily tell localplay what node to talk on. </div><div><br></div><div>Im trying to wrap my head around why running that script using the autopatch doesn't key up the radio when i execute it on the HF node, but does when i do the exact same thing on a radioless node connected to it.</div><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 18, 2018 at 4:35 PM, "Doug Crompton via arm-allstar" <span dir="ltr"><<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Phil,<br>
<br>
Unfortunately no if you are sending it on the same node as the radio is<br>
on. Maybe you could use two nodes connected together. One Zoipier and the<br>
other the radio. Then only send the localplay to the zoipier node.<br>
<span><br>
<br>
*73 Doug*<br>
<br>
*WA3DSP*<br>
<br>
*<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/hamra<wbr>dio</a> <<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/hamra<wbr>dio</a>>*<br>
<br>
<br>
<br>
</span>On Thu, Jan 18, 2018 at 4:18 PM, "Phil Visalli via arm-allstar" <<br>
<div class="gmail-m_6001788817232563785m_6680611345636313940HOEnZb"><div class="gmail-m_6001788817232563785m_6680611345636313940h5"><a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>> wrote:<br>
<br>
> I plan on writing it all up when i finish. I"ll def pass it along to you<br>
> when im done.<br>
><br>
> I do have one question and i probably should start a new thread, but here<br>
> goes.....<br>
><br>
> Is there a way to use something like speaktext to do an announcement, but<br>
> not key up the radio ? For example i have an option to have allstar speak<br>
> the frequency that the radio is tuned to.... and it works great, I hear the<br>
> announcement come over zoiper, but it also keys up the radio and speaks the<br>
> current frequency over the air. I know that speaktext.sh leverages<br>
> localplay... but im not sure if there is a way to not key up the radio when<br>
> using localplay (or if there is some other way to accomplish this).<br>
><br>
> The line of code thats Im using is:<br>
> /usr/local/sbin/speaktext.sh $cur_freq $NODE1<br>
><br>
> (I set $cur_freq earlier in the script)<br>
><br>
> ~P<br>
> K2ELV<br>
><br>
><br>
> On Wed, Jan 17, 2018 at 3:10 PM, "Doug Crompton via arm-allstar" <<br>
> <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>> wrote:<br>
><br>
> > Phil,<br>
> ><br>
> > Thank you. I am glad it is working so well for you. There are so many<br>
> > things you can do with Allstar and Linux. Our goal is to not put more<br>
> stuff<br>
> > internal to Allstar other than that which would naturally go there. So<br>
> many<br>
> > things can be done externally with the many scripting languages that are<br>
> > available. Allmon, Supermon, Autosky, hamlib, and many of the lesser<br>
> > scripts are prime examples of this.<br>
> ><br>
> > If you think what you have done would be useful to others it would be<br>
> great<br>
> > if you could share a write-up on it. This goes for anyone that has done<br>
> > things with Allstar that would be useful to others. I would be glad to<br>
> but<br>
> > them up on the web page. If it needs a little editing I could do that<br>
> also.<br>
> ><br>
> ><br>
> > *73 Doug*<br>
> ><br>
> > *WA3DSP*<br>
> ><br>
> > *<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/hamra<wbr>dio</a> <<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/hamra<wbr>dio</a>>*<br>
> ><br>
> ><br>
> > On Wed, Jan 17, 2018 at 1:45 PM, "Phil Visalli via arm-allstar" <<br>
> > <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>> wrote:<br>
> ><br>
> > > I dont know how i missed this before, but i saw it when you brought it<br>
> up<br>
> > > in another thread recently....<br>
> > ><br>
> > > <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" rel="noreferrer" target="_blank">http://www.crompton.com/hamrad<wbr>io/BeagleBoneBlackAllstar/</a><br>
> > > Allstar_extended_functions_usi<wbr>ng_autopatch.pdf<br>
> > ><br>
> > > That method works AWESOME! Im currently using that technique to set<br>
> up a<br>
> > > way to input frequencies to tune to, tuning up and down the band etc<br>
> on a<br>
> > > node i have set up to work with my 991A on HF. That, along with a<br>
> little<br>
> > > smart plug on got on amazon to turn the radio on and off remotely and i<br>
> > can<br>
> > > work HF pretty well from zoiper on my phone during breaks at work :p<br>
> > > ______________________________<wbr>_________________<br>
> > ><br>
> > > arm-allstar mailing list<br>
> > > <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
> > > <a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-b<wbr>in/mailman/listinfo/arm-allsta<wbr>r</a><br>
> > ><br>
> > > Visit the BBB and RPi2/3 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br>
> > ><br>
> > ______________________________<wbr>_________________<br>
> ><br>
> > arm-allstar mailing list<br>
> > <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
> > <a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-b<wbr>in/mailman/listinfo/arm-allsta<wbr>r</a><br>
> ><br>
> > Visit the BBB and RPi2/3 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br>
> ><br>
> ______________________________<wbr>_________________<br>
><br>
> arm-allstar mailing list<br>
> <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
> <a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-b<wbr>in/mailman/listinfo/arm-allsta<wbr>r</a><br>
><br>
> Visit the BBB and RPi2/3 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br>
><br>
______________________________<wbr>_________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-b<wbr>in/mailman/listinfo/arm-allsta<wbr>r</a><br>
<br>
Visit the BBB and RPi2/3 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br>
</div></div></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-b<wbr>in/mailman/listinfo/arm-allsta<wbr>r</a><br>
<br>
Visit the BBB and RPi2/3 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br></blockquote></div><br></div></div>
<br>______________________________<wbr>_________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-<wbr>bin/mailman/listinfo/arm-<wbr>allstar</a><br>
<br>
Visit the BBB and RPi2/3 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br></blockquote></div><br></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span></span><br><span>arm-allstar mailing list</span><br><span><a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a></span><br><span><a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a></span><br><span></span><br><span>Visit the BBB and RPi2/3 web page - <a href="http://hamvoip.org">http://hamvoip.org</a></span></div></blockquote></div></body></html>