Thanks Scott!

I kinda figured as much, but it was the first time I noticed it.

Alan

From: Scott Weis [mailto:kb2ear@kb2ear.net]
Sent: Wednesday, June 06, 2012 11:37 PM
To: 'Alan Adamson'; 'app_rpt mailing list'
Subject: RE: [App_rpt-users] Ok, this was puzzling.

It’s normal, while in remote control mode the controlling node stays keyed until the #.

From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Alan Adamson
Sent: Wednesday, June 06, 2012 10:42 PM
To: 'app_rpt mailing list'
Subject: [App_rpt-users] Ok, this was puzzling.

I have a full duplex connection between my allstar server and my repeater via a RTCM acting just as a ROIP box, not a voter.

When I connect that node to another node on my box and then connect it in *command mode*, it causes the repeater to stay keyed down even though I'm not bringing it up via the repeater input …. UNTIL I finish the command mode and press the "#", then it go back to tracking the repeater input…

Is this normal?  It works in all other modes as you would expect so no it's not an inverted COR, etc… It only does this when you put a node that’s connected to the repeater node into command mode.

Very bizarre… it works just fine because I'm in full duplex, but it did surprise me the first time and I never saw the PTT drop on the repeater even though I wasn't on the input of the repeater (COR wasn't active).

I'm not sure if this is from the RTCM, or the allstar server, or as a result of the command mode.  I know it does not do this when the node is a half duplex node

Alan