[App_rpt-users] Default *2<node#> MONITOR mode is not just monitor to far end.

[Stephen Rodgers]

Steve Gladden wrote:
> Stephen Rodgers wrote:
>> Steve Gladden wrote:
>>   
>>> Have a node setup (repeater) with usbradio..
>>> Using mostly default setup.
>>> at the moment I have rx /repeater setup for carrier access (no ctcss)
>>>
>>> Been testing this and the far end nodes report that they get get 
>>> repeater tones & hang time from me if I try to just 'monitor' them using 
>>> the *2
>>> monitor functionality..
>>>
>>> *3 works as expected but when I try to use *2 I'm getting those 
>>> unexpected results and the far end is experiencing some grief/confusion.
>>>
>>> Am I misunderstanding how this should work?
>>> Or are there any common gotchyas where you'd think you're just 
>>> monitoring but it's doing more than that?
>>> Sorry this is a bit vague.. I probably need to bring up another note and 
>>> test this and report step by step what's happening.
>>>
>>> Thanks
>>>
>>> Steve
>>>
>>>  
>>>
>>>
>>>
>>>     
>> Versions of app_rpt.c which are older than version 0.199 might be sending telemetry to foreign nodes under some
>> conditions, especially if the foreign node is running a really old version of app_rpt.c which does not use the
>> new keying scheme.
>>
>> You should check what version of app_rpt.c you are running and see if the foriegn node is running a really old
>> version of app_rpt.c
>>
>>
>> Steve
>> WA6ZFT
>>
>>
>>
>>   
> Hi Steve I have the latest version installed or almost the latest 
> version (3 days old).
> So what I'm hearing you say is that the far end may have an older 
> version (causing this issue) and this is out of my control.
> Is this correct?
> 
> Thanks!
> 
> Steve
> 
> 
> 
> 
I guess the question would be does it do it when connected to my node (2010)?
Try connecting to me in transceive mode to see if I'm monitoring, then tear down the connection and
try monitor mode. I'm running the latest app_rpt.c there as well.

Steve
WA6ZFT