# How to enable COS LED on RX for SHARI devices? **URL:** \ **Category:** AllStarLink\ **Created:** [February 1, 2025, 5:37am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833 "2025-02-01T05:37:11Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 1, 2025, 5:37am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/1 "2025-02-01T05:37:11Z")
An older post from ASL2 era suggests: cop,62,GPIO4:1 = c|t|RPT\_RXKEYED cop,62,GPIO4:0 = c|f|RPT\_RXKEYED I tried this and it does not work (the COS LED does not come on). In 2022 and for ASL2 states something needs to be compiled to make it work - also suggests that this functionally will be added later. Was it added and what might I be missing to make this work? This older post is at: > [@COS LED for SHARI PIHAT](https://community.allstarlink.org/t/cos-led-for-shari-pihat/19656): > > Folks, I have SHARI PiHat running HAMVoIP, so far everything works. However, I am trying to move away from ARCH Linux by installing ASL 2.0 beta 6 image instead. Pretty much working out okay the only thing I was unable to get to work is the COS LED. It does not turn on when COS signal is detected. I was trying to follow some older instruction by adding two more lines in the rpt.conf cop,62,GPIO4:1 = c|t|RPT\_RXKEYED cop,62,GPIO4:0 = c|f|RPT\_RXKEYED But that does not work. Anyone running SH… Thanks! ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 1, 2025, 5:59am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/2 "2025-02-01T05:59:15Z")
If I am reading this correctly, this was done in ASL2 but was not brought over to ASL3. It is #22. > > > Some features added to ASL2 are not present in ASL3. I haven't gone through the …whole history so don't know many were lost, but perhaps as a starting point someone could clarify what point in time in the ASL2 code was decided as the starting point for ASL3? > > I did a PR that was merged on Feb. 3 2023 (adding a new configuration parameter enabling voxhangtime to be adjusted) and this is not present in ASL3. Why was this discarded and how many other improvements were discarded? ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [February 1, 2025, 2:04pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/3 "2025-02-01T14:04:55Z")
> [@n8lbv](#): > > An older post from ASL2 era suggests: > > cop,62,GPIO4:1 = c|t|RPT\_RXKEYED > cop,62,GPIO4:0 = c|f|RPT\_RXKEYED > I tried this and it does not work (the COS LED does not come on). Steve, I think those are status markers, not a toggle of logic. The logic is toggled with a electrical signal to the pin. And that is the only way to toggle COS logic. Not in software. But I can’t speak to the led or shari. Perhaps your electrical logic is inverted. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [February 1, 2025, 5:31pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/4 "2025-02-01T17:31:44Z")
Under `[events]` in `rpt.conf` put: ```ini cop,62,GPIO4:1 = c|t|RPT_RXKEYED cop,62,GPIO4:0 = c|f|RPT_RXKEYED ``` and in `simpleusb.conf` within the node’s stanza put: ```ini gpio4=out0 ``` Restart Asterisk. This is quasi-custom per board. ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 2, 2025, 2:46am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/5 "2025-02-02T02:46:49Z")
Thank you VERY much. I will try this and report back. Sounds like it will work! 🙂 ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 2, 2025, 4:26pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/6 "2025-02-02T16:26:15Z")
I tried this exactly as you have suggested. I still see no COS LED activity on RX. Should anything about the GPIO be getting logged? I do not see anything on the asterisk console either in terms of GPIO. And yes, I of course restarted asterisk and also tried rebooting. Thanks! ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [February 2, 2025, 5:08pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/7 "2025-02-02T17:08:33Z")
Just checking … In your `rpt.conf` file, do you have a line with `;[events]` with the leading “;” (starting a comment)? If so, you need to remove the “;”. … and the `cop,62,...` lines would go after the `[events]` line ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 2, 2025, 5:26pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/8 "2025-02-02T17:26:42Z")
My total bad here! I _thought_ I had [events] uncommented. SMH. Not sure if I can blame this on the default dark blue colored test in vim. Fix and works! Thank you! ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 2, 2025, 5:30pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/9 "2025-02-02T17:30:04Z")
Also in answer to my other question: they do log. 🙂 Connected to Asterisk 20.11.0+asl3-3.2.0-2.deb12 currently running on 2W (pid = 2838) – Event on node 64184 doing rpt command cop,62,GPIO4:1 for condition c|t|RPT\_RXKEYED – Event on node 64184 doing rpt command cop,62,GPIO4:0 for condition c|f|RPT\_RXKEYED – Hungup ‘DAHDI/pseudo-998408274’ ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [February 2, 2025, 6:19pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/10 "2025-02-02T18:19:39Z")
> [@n8lbv](#): > > Not sure if I can blame this on the default dark blue colored test in vim. `set bg=dark` is your VIM friend. ---
**Author:** ![KQ4YVO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kq4yvo/32/3729_2.png) [@KQ4YVO](https://community.allstarlink.org/u/KQ4YVO)\ **Post date:** [February 2, 2025, 7:54pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/11 "2025-02-02T19:54:44Z")
my etc/asterisk/rpt.conf file did not have [events] in the file but under [functions] ; 962 = cop,62 ;send Messages to USB to control GPIO pins Should I uncomment that line?? ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [February 2, 2025, 10:06pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/12 "2025-02-02T22:06:33Z")
> [@KQ4YVO](#): > > Should I uncomment that line?? No, that’s something else entirely. ---
**Author:** ![n1dae](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/22d042/32.png) [@n1dae](https://community.allstarlink.org/u/n1dae)\ **Post date:** [February 3, 2025, 1:48am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/13 "2025-02-03T01:48:17Z")
The Kits4Hams [instructions for the SHARI PiHat](https://kits4hams.com/wp-content/uploads/2024/04/SHARI-PiHat-Allstar-Node-Setup-Procedure-Version-2.00.pdf) include a section on enabling the COS light on page 21. Would assume this is the most current approach in ASL3 to enable the light? ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 3, 2025, 2:50am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/14 "2025-02-03T02:50:29Z")
I expect that is both a bit older and it also specifies it’s for HamVoip. So it’s likely to be different. Also if it were the same, maybe it would work out of the box. What was answered above works perfectly for ASL3. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [February 3, 2025, 12:41pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/15 "2025-02-03T12:41:03Z")
As I said above, the use of a COS light for GPIO is not standard which is why it doesn’t work out of the box. The basics of that are not different between ASL and HamVOIP. ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 3, 2025, 6:46pm UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/16 "2025-02-03T18:46:42Z")
True that. What I don’t get is in the hardware design (SHARI/NiceRF why didn’t they just tie the RXaudio enable line (pin one on the module) to also drive the COS LED. =SMH= This also kind of “wastes” one of the two normally free GPIO lines. ---
**Author:** ![n8lbv](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/n/a5b964/32.png) [@n8lbv](https://community.allstarlink.org/u/n8lbv)\ **Post date:** [February 4, 2025, 4:41am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/17 "2025-02-04T04:41:27Z")
–Steve from the future– While I was driving today I had a thought… It might be done this way for usbradio applications (vs using simpleusb)- Where you’d typically be running the receiver open squelch: And you wouldn’t want the COS LED stuck on all the time. Running this back through the GPIO via software would give you an option to have app\_rpt control the LED when _it_ has valid carrier or carrier+PL. ---
**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\ **Post date:** [February 7, 2025, 4:42am UTC](https://community.allstarlink.org/t/how-to-enable-cos-led-on-rx-for-shari-devices/22833/18 "2025-02-07T04:42:07Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.