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

Stephen Rodgers sales at qrvc.com
Sat Nov 28 20:51:58 EST 2009

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


More information about the App_rpt-users mailing list