# RFC: add array of ports

**URL:** <https://forum.opencyphal.org/t/rfc-add-array-of-ports/1878>\
**Category:** Specification\
**Created:** [May 1, 2023, 10:44am UTC](https://forum.opencyphal.org/t/rfc-add-array-of-ports/1878 "2023-05-01T10:44:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [July 3, 2023, 12:31pm UTC](https://forum.opencyphal.org/t/rfc-add-array-of-ports/1878/3 "2023-07-03T12:31:50Z")

</div>

I think this is a worthy proposal and it does indeed address a salient problem. Initially, I wanted to postpone its discussion until the named topic support is implemented; however, @maksim.drachov is unable to continue his work on the named topics support due to other commitments at Zubax, so delaying this further is probably unwise.

A related problem was brought up just recently at [Subject-ID Assignment](https://forum.opencyphal.org/t/subject-id-assignment/1882).

> [@Dima](#):
>
> A `PORT_NAME` may end with [N], for example: `uavcan.sub.feedback[32].id` `uavcan.sub.feedback[32].type`.

I think this option is the most aligned with the existing design. We can modify the `uavcan.register.Access` specification accordingly to permit arrays and the bracket syntax. The same specification should also provide a detailed explanation of the feature (close to what is written in the OP post).

> [@Dima](#):
>
> This feature most likely should be considered only for a group of subscribers, but not for publishers. Though it is clear to think about a group of setpoints as it is described in UDRAL, I’m not sure if this logic applies to redundant sensors. A sensor doesn’t need to worry about its number in the system - that’s actually why we don’t need a sensor\_idx in its message.

I think there is merit in extending this proposal not only to subscribers but also to publishers, as nodes that publish multiple related topics are not entirely uncommon (continuing the topic of ESCs, it might be a 4-in-1 motor controller). Another matter is the inner consistency of the specification: publishers and subscribers are two sides of the same thing, and any significant divergence between the two is undesirable.

As there are no other comments so far, I assume there are no strong objections to the proposal, hence I recommend @Dima to submit a pull request to the standard DSDL definitions so that we can discuss the specifics further.

---

_[View the full topic](https://forum.opencyphal.org/t/rfc-add-array-of-ports/1878)._
