Hey guys. I had a question about ID setup using a repeater. I have a CW ID. What I noticed, let’s say you have a 5 second hang time on the repeater. When the repeater IDs, it will play the ID, then hang for 5 seconds after the ID, in other words, it re-starts the hang time after the ID. Is there any way to have it ID, then drop like most controllers? This would be really helpful.
Any info on how to fix this would be greatly appreciated.
modify the “wait times” stanza in rpt.conf. Here’s mine done for mostly the same reason plus to narrow the time from unkey to telem and ID. I like the telemetry to be real short and as close to unkey as possible
[wait-times]
telemwait = 20 ; Time to wait before sending most telemetry
idwait = 500 ; Time to wait before starting ID
unkeywait = 20 ; Time to wait after unkey before sending CT’s and link telemetry
calltermwait = 2000 ; Time to wait before announcing “call terminated”
GeorgeC W2DB
If there is a way around this, I don’t know of it. It would be nice if it could use althangtime just for IDs and other telemetry to avoid exactly this problem.
That doesn’t address the issue, because the hangtime restarts again when it’s about to drop out for the ID. So the repeater ends up transmitting for two entire cycles when it could just drop immediately after the ID, like pretty much every real repeater controller I’ve ever seen does. To my knowledge, anyway, there isn’t a built-in way to handle this situation. Hope I’m wrong.
Adjusting the wait times to be less conservative than the defaults is a good thing, in my opinion, but won’t fix this problem.
Also, if you happen to be using sa818 radios, anything under about 800 ms will cause the first bit of telemetry to be truncated.
Odd for sure. Mine are all controlling Quantar repeaters. Then too I am not running ASL V3 on anything
GeorgeC