[arm-allstar] courtesy tones while node connected

[David McGough]

Hi Jeff,

I'm catching up on this message thread just now. I use duplex=0 on various 
RF linking nodes and it is completely quiet---no telemetry, nothing.

So, I'm not sure what's happening in your scenario. I'll review the 
videos....In the meantime, if you can send me your rpt.conf file directly 
(off-list), I'll take a look at it.

73, David KB4FXC


On Fri, 11 May 2018, "Jeff Karpinski via arm-allstar" wrote:

> Yeah, there's definitely some weirdness going on. Here’s a vid that 
demonstrates. Node A (the Kenwood side) is now set to duplex=0. I do a 
couple kerchun ks on Node B to demonstrate no connectivity, then connect 
it to Node A. The connection notice plays out BOTH nodes. Another 
kerchunk shows AllStar tone out of B only (good). Requesting a *76 from 
Node B results in a disconnect message playing from Node A only! Red LEDs 
are PTT, left one is radio node A, right is radioless node B. Note this 
behavior is NOT 100% consistent. Watch vid #2. Same steps, no changes 
made to either node.

https://www.youtube.com/watch?v=QYy2-MjeX74 <https://www.youtube.com/watch?v=QYy2-MjeX74>

https://www.youtube.com/watch?v=ZJ9yaYGCe1k <https://www.youtube.com/watch?v=ZJ9yaYGCe1k>
> On May 11, 2018, at 11:13 AM, Chuck via arm-allstar <arm-allstar at hamvoip.org> wrote:
> 
> Jeff and Doug,
> I have experienced ​something similar.  But 2 nodes on separate pis.  One
> node was set up to not output audio to any interface.  That node when
> connected to over the network would send it's local telemetry and it's CW
> ID over the network to the connected nodes.  Very disturbing to hear 2
> different ID's on the air at the same time.   My solution was to add a usb
> interface to the radio-less node and configure it to output audio, even
> though there was no radio connected to it.  This restored normal operation
> and prevented local telemetry from being sent over the net connections.
> Sorry I can't tell you more, I just worked around the issue.  I also did
> verify that the issue was common to the "dial" on rpi and to this version
> of software.
> Chuck
> _______________________________________________
> 
> 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