# New hardware interface to replace URI-X and voter board

**URL:** <https://community.allstarlink.org/t/new-hardware-interface-to-replace-uri-x-and-voter-board/17521>\
**Category:** AllStarLink\
**Created:** [September 4, 2020, 4:30pm UTC](https://community.allstarlink.org/t/new-hardware-interface-to-replace-uri-x-and-voter-board/17521 "2020-09-04T16:30:12Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Ken\_Jamrogowicz](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ken_jamrogowicz/32/970_2.png) [@Ken\_Jamrogowicz](https://community.allstarlink.org/u/Ken_Jamrogowicz)\
**Post date:** [September 5, 2020, 2:01pm UTC](https://community.allstarlink.org/t/new-hardware-interface-to-replace-uri-x-and-voter-board/17521/2 "2020-09-05T14:01:52Z")

</div>

That’s nice - the STM could do the CTCSS generation and detection.

But the connection to the host computer would be by USB - no? That is where the problems are right now. So you would still have those problems.

Of course, I suppose it could use a different format where perhaps larger chunks of data are transferred at one time. Or the connection could be by SPI? That might make it RPI-specific though.

Food for thought.

Ken

---

_[View the full topic](https://community.allstarlink.org/t/new-hardware-interface-to-replace-uri-x-and-voter-board/17521)._