My setup is a simplex link to my repeater over rf with a remote connection to 56332.
After the node transmits. Either due to a station or the remote link keying up my node will randomly kerchunk a couple to 3 times at random intervals for 1 to 15 minutes or so then stop.
Chatgpt suggested it was related to the frondelay setting and had me adjust it to -75
That had no effect, the problem will resolve itself on its own, however, during severe weather when my repeater is linked by rf to another repeater the problem goes on for hours and hours. With my node kerchunking once or twice every 10 minutes.
I assume it is due to the remote node hearing a squelch crash or something.
Lastly I think the remote node is to running clear node as a simplex node into that repeater.
What settings should I look at to curb this behavior
I would like to hear more about how you are using simplex link to the repeater? Are you using a 420 MHz link radio to the repeater site? Are you using ctcss or a DPL?
Simpleusb setting rxdelay is how long a signal needs to be present to activate the node, so +30 so going plus adds that much time till the signal would be passed thru to the network
So the repeater is 2m? Does the repeater have ctcss on the output?
the repeater is not kerchunking it’s the node?
When doing an offsite node shotgun to the repeater, the repeater should have a ctcss tone on the output, the node radio should ctcss tone on receive so the node radio is not in cos mode. This keeps any kind of signals activating the node like you using your ht talking into the repeater or other 2m activity. The only problem doing this is your repeater hangtime, id, any voice announcments gets sent down to any nodes you are connected to.
The node should be set to no hangtime, no id’s, no keyups unless something comes from the connected node.
If you can not get ctcss tone on repeater output, raise the squelch level on the vhf node radio so that no weak signals can not open the squelch.
The node should not be transmitting anything UNLESS there is activity on the Node you are connected to. It should never transmit for any other reason.
Sounds like you have it set to Duplex=1, which then some signal is received and after it stops it then transmits a courtesy tone with hangtime or just a brief hangtime which causes the repeater to go on then the node gets a signal… ping pong back and forth.
If some kind of signal is kerchunking the Node then a spurious signal with ctcss is triggering it or it is in COS mode. Check your SimpleUSB settings
In rpt.conf should be running Duplex=0
Half duplex with no telemetry tones or hang time
Also set this to 1
nounkeyct=0
; Disable courtesy tones (=1)