ICS controller port settings in web interface

[vader7071]

I have an ICS 1x controller hat, and my output port sets to 498 when load presets. The output port is highlighted in red and I get a fault from the pi (see attached image)

[Dloranger]

This looks like it’s not related to the repeater board, gpio26 is a native raspberry pi pin. The repeater board uses pins in the upper 400 to low 500’s

…

On Sat, Jan 10, 2026 at 12:35 PM Chris Wren ***@***.***> wrote: *vader7071* created an issue (OpenRepeater/openrepeater#123) <#123> I have an ICS 1x controller hat, and my output port sets to 498 when load presets. The output port is highlighted in red and I get a fault from the pi (see attached image) 20260110_095451.jpg (view on web) <https://github.com/user-attachments/assets/0d9dec81-1f1e-4254-8ead-ac215e9a331b> — Reply to this email directly, view it on GitHub <#123>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPI3DLKN3MDNPK7HM6LQQ34GEZ6TAVCNFSM6AAAAACRJDKG4WVHI2DSMVQWIX3LMV43ASLTON2WKOZTHAYDAMJRGM3DAMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[vader7071]

When the board defaults load, it sets Port 1 input to 26 and output to 498. What should the ports be? The manual says audio in and audio out are "FE".

[Dloranger]

The defaults are correct unless you’re using an rpi zero. If your using an rpi zero the cos is still correct, the ptt will change by +8 I would suggest to reimagine the as card, seems like something is taking ownership of the gpio or something else is wrong. The error you showed in the log says it can’t open the gpio26. You can check the controller board thru the console using the ‘i2cdetect -y 1’ which runs a bus scan, you should see 2 devices with ‘UU’ which means the processor has control of them. One is the gpio expanders and 1 is the sound card Daniel Loranger

…

On Sat, Jan 10, 2026 at 12:48 PM Chris Wren ***@***.***> wrote: *vader7071* left a comment (OpenRepeater/openrepeater#123) <#123 (comment)> When the board defaults load, it sets Port 1 input to 26 and output to 498. What should the ports be? The manual says audio in and audio out are "FE". 20260110_114812.jpg (view on web) <https://github.com/user-attachments/assets/44bf204a-1967-479b-8d97-d3365033143b> — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPI3DIXYTDJGRKMJUPGBQ34GE3QVAVCNFSM6AAAAACRJDKG4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGI4DENRRHE> . You are receiving this because you commented.Message ID: ***@***.***>

[vader7071]

Ah, you hit the target. This is on a Pi Zero 2W. Did not know that would be an issue.

Looking at the interface page, in the green box, I need to set it as 34/Fe-Pi Rt and in the red box set it to 32/FE-Pi Rt? Or do I need to leave the red as 498/Fe-Pi Rt?

[Dloranger]

Only change the ptt, nothing else will change. 506 is the right gpio, but that doesn’t explain the error for gpio26 Daniel Loranger

…

On Sat, Jan 10, 2026 at 1:23 PM Chris Wren ***@***.***> wrote: *vader7071* left a comment (OpenRepeater/openrepeater#123) <#123 (comment)> Ah, you hit the target. This is on a Pi Zero 2W. Did not know that would be an issue. Looking at the interface page, in the green box, I need to set it as 34/Fe-Pi Rt and in the red box set it to 32/FE-Pi Rt? Or do I need to leave the red as 498/Fe-Pi Rt? — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPI3DKYUKEP3UY3JEWB2U34GE7TNAVCNFSM6AAAAACRJDKG4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGM2DEMRTGY> . You are receiving this because you commented.Message ID: ***@***.***>

[vader7071]

Wait, am I changing COS or PTT?

Let's simplify this. On the interface tab:

Default Interface settings:

• port 1

• • 26
• • RX Aud: Fe-Pi Right Ch
• • 498
• • TX Aud: Fe-Pi Right Ch

Change to:

• port 1

• • 34
• • RX Aud: Fe-Pi Right Ch
• • 506
• • TX Aud: Fe-Pi Right Ch

Beyond that, is there any other locations I need to update or modify? And for clarification, the "26/34" is the GPIO pin for COS and the "498/506" is the GPIO pin for PTT?

And oddly enough, I may have to rebuild the whole image, because I updated the ports from the web interface and now I can't log into the Pi at all. No ssh or web interface. I can't even ping it.

[Dloranger]

Don’t change cos, only change the ptt from 498 to 506. Nothing else needs to be changed, don’t do any OS updates or etc as there have been structural changes in the OS that may (will) break the gpio behavior and who knows what else. Daniel Loranger

…

On Sat, Jan 10, 2026 at 2:08 PM Chris Wren ***@***.***> wrote: *vader7071* left a comment (OpenRepeater/openrepeater#123) <#123 (comment)> Wait, am I changing COS or PTT? Let's simplify this. On the interface tab: *Default Interface settings:* - port 1 - - 26 - - RX Aud: Fe-Pi Right Ch - - 498 - - TX Aud: Fe-Pi Right Ch *Change to:* - port 1 - - 34 - - RX Aud: Fe-Pi Right Ch - - 506 - - TX Aud: Fe-Pi Right Ch Beyond that, is there any other locations I need to update or modify? And for clarification, the "26/34" is the GPIO pin for COS and the "498/506" is the GPIO pin for PTT? And oddly enough, I may have to rebuild the whole image, because I updated the ports from the web interface and now I can't log into the Pi at all. No ssh or web interface. I can't even ping it. — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPI3DITKULELAWVDDA56DD4GFE35AVCNFSM6AAAAACRJDKG4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGM4TQNJTGU> . You are receiving this because you commented.Message ID: ***@***.***>

[vader7071]

So leave 26 alone and change 498 to 506? That doesn't make sense. 26 was the GPIO that started all this. The OS could not initialize 26 and would fail.

When you say don't do any OS updates, you mean once I recreate the SD card, do not do any OS updates from what was bundled in the img file?

[Dloranger]

Correct, 26 does not change, only the PTT and that’s why my first statement was that it’s an rpi problem not a controller board problem. Mentioning the rpi zero is just a trip point I have seen before when there is a problem out of the box. The cos and ctcss inputs use the rpi native pins to ensure the fastest response to incoming activity, the PTT is controlled so it was deemed not as timing critical. Daniel Loranger

…

On Sat, Jan 10, 2026 at 2:17 PM Chris Wren ***@***.***> wrote: *vader7071* left a comment (OpenRepeater/openrepeater#123) <#123 (comment)> So leave 26 alone and change 498 to 506? That doesn't make sense. 26 was the GPIO that started all this. The OS could not initialize 26 and would fail. When you say don't do any OS updates, you mean once I recreate the SD card, do not do any OS updates from what was bundled in the img file? — Reply to this email directly, view it on GitHub <#123 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACPI3DMLTISIJFL4GKK34GL4GFF2ZAVCNFSM6AAAAACRJDKG4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGQYDKMZSGE> . You are receiving this because you commented.Message ID: ***@***.***>

[Dloranger]

And correct, leave the OS as built. The gpio scheme in use was deprecated a while back and might be completed obsoleted by now Daniel Loranger On Sat, Jan 10, 2026 at 2:21 PM Daniel Loranger ***@***.***> wrote:

…

Correct, 26 does not change, only the PTT and that’s why my first statement was that it’s an rpi problem not a controller board problem. Mentioning the rpi zero is just a trip point I have seen before when there is a problem out of the box. The cos and ctcss inputs use the rpi native pins to ensure the fastest response to incoming activity, the PTT is controlled so it was deemed not as timing critical. Daniel Loranger On Sat, Jan 10, 2026 at 2:17 PM Chris Wren ***@***.***> wrote: > *vader7071* left a comment (OpenRepeater/openrepeater#123) > <#123 (comment)> > > So leave 26 alone and change 498 to 506? That doesn't make sense. 26 was > the GPIO that started all this. The OS could not initialize 26 and would > fail. > > When you say don't do any OS updates, you mean once I recreate the SD > card, do not do any OS updates from what was bundled in the img file? > > — > Reply to this email directly, view it on GitHub > <#123 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACPI3DMLTISIJFL4GKK34GL4GFF2ZAVCNFSM6AAAAACRJDKG4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZTGQYDKMZSGE> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

[vader7071]

Then i need to redo the SD card anyway. 1st thing I did was an OS update.