# Allstar node won't key up with AIOC **URL:** \ **Category:** Third-Party Apps\ **Created:** [January 15, 2026, 2:42am UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138 "2026-01-15T02:42:10Z")\ **Posts on this page:** 8\ **Page:** 2
**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, 2026, 9:05pm UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/21 "2026-02-03T21:05:12Z")
I can't see why an older version of ASL code would matter for a hardware issue. ---
**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 3, 2026, 9:40pm UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/22 "2026-02-03T21:40:05Z")
My $0.02 : There are at least 2 AIOC board revisions. Do you have the original board? or the latest revision? There are at least 2 versions of the AIOC firmware. What version do you have installed? There is info @ [GitHub : AIOC : README.md](https://github.com/skuep/AIOC/blob/master/README.md) There is also info @ [GitHub : aioc-util : README.md](https://github.com/hrafnkelle/aioc-util/blob/main/README.md) and there's also the G1LRO info ... Personally, I've got a new board, loaded up the latest AIOC firmware, made use of `aioc-util`, and was able to setup/test ASL3 with a UV-K6. ---
**Author:** ![John\_Melchor](https://community.allstarlink.org/user_avatar/community.allstarlink.org/john_melchor/32/4658_2.png) [@John\_Melchor](https://community.allstarlink.org/u/John_Melchor)\ **Post date:** [February 4, 2026, 10:11am UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/23 "2026-02-04T10:11:14Z")
Where is aioc-util kept? ---
**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 4, 2026, 1:53pm UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/24 "2026-02-04T13:53:02Z")
The command is in the [GitHub : aioc-util](https://github.com/hrafnkelle/aioc-util) repo. ---
**Author:** ![Lee\_Maisel](https://community.allstarlink.org/user_avatar/community.allstarlink.org/lee_maisel/32/4635_2.png) [@Lee\_Maisel](https://community.allstarlink.org/u/Lee_Maisel)\ **Post date:** [February 4, 2026, 2:56pm UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/25 "2026-02-04T14:56:04Z")
SOLVED! I’ve got the v1.2 (hardware) board by s. Kuipper. All the guides had me flashing the AIOC v1.3x FW, but on his site, he specifically states that the v1.2 board REQUIRES v 1.4 and above firmware. I flashed it with 1.4 and now everything works. Thanks everyone! ---
**Author:** ![dimbulb](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/d/13edae/32.png) [@dimbulb](https://community.allstarlink.org/u/dimbulb)\ **Post date:** [February 4, 2026, 6:51pm UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/26 "2026-02-04T18:51:46Z")
Not really sure on how to talk on forums, I haven’t done it in some time. If this should be a new thread I’d be happy to start it. Mine seems to talk just fine with ASL3 on a pi zero 2W, but then it starts talking over me, which is counter-productive on a half-duplex hotspot. 🙂 My current working theory is the output COS is being set while COS is being received from the AIOC device, which for some reason sets PTT. I suspect I might need to make some changes using aioc-util, but I’m ont quite sure what. I have tried setting duplex to 0 and 1 in rpt.conf to no avail. I’ve done some stuff to abate any RF crawling in to the digital bits, but there’s always more I could do. ---
**Author:** ![Edoardo\_Aimaro](https://community.allstarlink.org/user_avatar/community.allstarlink.org/edoardo_aimaro/32/4759_2.png) [@Edoardo\_Aimaro](https://community.allstarlink.org/u/Edoardo_Aimaro)\ **Post date:** [March 13, 2026, 4:34pm UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/27 "2026-03-13T16:34:14Z")
Hi guys, Has the DTMF issue been resolved? EA ---
**Author:** ![John\_R](https://community.allstarlink.org/user_avatar/community.allstarlink.org/john_r/32/4753_2.png) [@John\_R](https://community.allstarlink.org/u/John_R)\ **Post date:** [March 19, 2026, 9:59pm UTC](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138/28 "2026-03-19T21:59:39Z")
Bit late, but will probably help someone else: The AIOC presents itself to Linux as both a USB audio device and a HID (Human Interface Device). The HID interface is what aioc-util.py uses to read and write configuration registers. By default on most Linux systems, access to HID devices is restricted to root, which means running aioc-util.py as a regular user will fail with a permission error. To fix this, you need a udev rule — a small configuration file that tells Linux to grant your user (or a group) permission to access the device when it is plugged in. Create a new rules file: sudo nano /etc/udev/rules.d/99-aioc.rules Add the following line: SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="7388", MODE="0660", GROUP="plugdev" What this does: whenever the AIOC is plugged in (idVendor and idProduct identify it uniquely), Linux sets the permissions on its HID device node so that members of the plugdev group can read and write it. The plugdev group is the conventional group for this purpose on Debian-based systems. Make sure your user is a member of plugdev: sudo usermod -aG plugdev $USER Then reload the udev rules and re-trigger them (or simply unplug and replug the AIOC): sudo udevadm control --reload-rules sudo udevadm trigger You will need to log out and back in (or start a new SSH session) for the group membership change to take effect. Note: If you changed the AIOC's USB VID/PID using --set-usb (e.g. to emulate a CM108), update the idVendor and idProduct values in the rule to match the new values. [Previous page](https://community.allstarlink.org/t/allstar-node-wont-key-up-with-aioc/24138.md?page=1)