I'm wondering if someone would clarify what I'm seeing.
This node is set for duplex = 0 with linktolink = yes.
I don't grasp the nomenclature "COS Input" and "COS Out".
When COS Input shows Keyed, so does COS Out. When COS Input is clear, so is COS Out. What is this telling me? Does COS Out refer to a valid COS signal is generated based on access mode (COS only or COS/CTCSS for tone access?)
Just guessing here...
Is it made for a GPIO pin that can trigger other devices when a valid CTCSS tone is detected and the repeater is unsquelched?
Just an idea.
-Shawn
I would also be interested in more information about how the COS lines work and what the status screen is indicating. I have one AllStar3 node that isn't working correctly. When I transmit to it from another radio, the Cos In/Out initially toggle to 'Keyed' for a split second. Then they both go back to Clear for maybe 2-3 seconds. When they go back to clear, the node radio transmits and the status shows as 'Transmit Telemetry/Playback'. If I keep the PTT down on the other radio, after 2-3 seconds the node then shows Cos In/Out as 'Keyed' and the status on the Monitoring Dashboard displays as 'Transmit - Local Source (00:00)' where 00:00 is the time keyed. If I hold the PTT, this timer increases until I reach the 3 minute timeout. So the fault I have is with the initial transmission to the node. Why does it toggle from Keyed > Clear (2-3 seconds) > Keyed. It should just toggle to Keyed when there is a local incoming transmission on RF. I have tried various fixes such as inverting USB, inverting PTT, fitting diodes, sink resistors etc. Plus changing hi/lo states on the radio itself but nothing is working.
After typing the above, I decided to change the Duplex type to 0 and half. This appears to have fixed the problem. But I normally have the Duplex type set to 1 on my simplex gateways. I wonder what the gateway is trying to send via telemetry for 2-3 seconds when it hears local RF?
I remembered I was running a recent Beta version of ASL3 while testing the lnkactivity fix. So I reverted to the current release but I still have the same issue. I was able to put duplex = 1 in the (node-main) stanza but only if I also included nounkeyct = 1. Therefore the problem remains. There was nothing obvious in the CLI with higher verbosity and debug levels. It would be useful to understand the difference between COS Input and COS Out. Is one aligned to local RF and the other to Telemetry?