In the last two weeks or so, out of the blue, my public node will show COS Detected, which produces a tone.
I have one public node and 5 private nodes, with each private node connecting to the public.
I thought maybe it was SkyWarnPlus’ tail, so I disabled SkyWarnPlus. Not the issue.
When I noticed the issue, I started to disconnect private node by private node. I was down to nothing connected in the public node, but the COS continued.
I have disconnected my HotSpotRadio USB Hub and changed the public node to (as of 11/5, 07:00 ET) esentially a simple hub:
; duplex = 1 ; turned off hat
duplex = 0
hangtime = 400
;rxchannel = SimpleUSB/62499 ; turned off hat
rxchannel = dahdi/pseudo
I’ve indepently reached out to HotSpotRadio for their take, because I don’t know if its the hat.
It’s only been about 5 hours since I “disconnected” the hat, and possibly too ealry to tell if that fixed the issue.
FYI, SkywarnPlus just does telemetry and audio playback internally in app_rpt - it is not possible for SkywarnPlus to trigger a physical logic input such as COS.
What are your frequency and CTCSS/DCS settings for the node? And I assume you are not just using squelch and omitting CTCSS/DCS. You could simply be “conflicting” with something else.
I’m not sure where you’re located, but are there repeater inputs or outputs on 449.9… ? If there is a repeater on 444.975 and it’s PL is 100 you may be hitting the edge of that transmission. You may find it more reliable to put a hotspot somewhere in 446. I use splinters like 446.1375 and 446.6875.
I looked into the repeaters and P/L’s around me and that isn’t an issue, but again, I’ll change the freq once I determine that the Hat is or isn’t a suspect…