[arm-allstar] node insists on sending CW ID every idtime

Steve Goldsmith steve at stevegoldsmith.com
Wed Dec 12 21:34:55 EST 2018


Hey David & Doug:

Thanks for the quick response and for all the work you have put into this platform, we really appreciate it.  

> You're digging deep in the pot of spaghetti!

Yea, it looked pretty noodley in there -)

> For now, in your first message, you mentioned that you're using duplex=1 
> in the rpt.conf node stanza. And, you mentioned this is a repeater?
> 
> Please give me a complete (but brief is fine) description of your system 
> layout?

The allstar node is located at a remote location, it is plugged into a URI connected to an Alinco DR-235TMKIII 220 radio. Up on the hill we have a TYT 220 radio plugged directly into a RLC2 repeater controller link port.

Non default rpt.conf items are:
nounkeyct=1
duplex=1

With regard to Doug’s comments:
>  If you are sending a Courtesy tone (nounkeyct=0) then it will give a tail
> Courtesy tone at each key. This would be an RF key and count towards ID
> time. Someone does not have to actually talk. So if someone kerchiunks the
> repeater it will still ID. 
> 

I have nounkeyct set to 1, not sure if that changes how the id timer is handled (i didn't look at that bit of code).

While I understand the logic behind if you hear something you must have transmitted something in the timer code, for a remote link it’s not always a valid assumption.     If the remote doesn’t transmit, it seems it shouldn’t ever start the id timer as there’s no legal reason to id.

I can obviously make the problem go away with duplex=0, but then the 220 uplink won’t ever ID, and that’d be bad.

> You can somewhat eliminate kerchunks by setting rxondely in simpleusb-tune-menu to
> some value higher than the default 0.  5 might be a good number.

I don’t think the problem is the kerchunks, I referenced that as part of my troubleshooting trying to prove out that the idtime reset on received signal.  We’re seeing the allstar node ID every 10 minutes.   Pretty sure that the repeater is IDing on the 220 link, we’re hearing it and starting the idtime, 10 minutes later we ID at the repeater, which hears it, starts it’s timer, id’s at us and so on.

Thanks again


-- 
73,
/steve - W1HS



More information about the ARM-allstar mailing list