# Port/Node assignment + Tooling for integrators

**URL:** <https://forum.opencyphal.org/t/port-node-assignment-tooling-for-integrators/1099>\
**Category:** Applications & Usage\
**Created:** [February 1, 2021, 7:56pm UTC](https://forum.opencyphal.org/t/port-node-assignment-tooling-for-integrators/1099 "2021-02-01T19:56:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mawildoer](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/mawildoer/32/742_2.png) [@mawildoer](https://forum.opencyphal.org/u/mawildoer)\
**Post date:** [February 1, 2021, 7:56pm UTC](https://forum.opencyphal.org/t/port-node-assignment-tooling-for-integrators/1099/1 "2021-02-01T19:56:37Z")

</div>

Hi All,

Is there any existing tooling which can assist system integration to generate code with port and node IDs?

**[nunavut](https://github.com/UAVCAN/nunavut)** does a good job of transcompiling DSDL definitions, but the next step gets rather clunky.

It seems like this tooling would be fairly universally applicable and a valuable addition to the current UAVCAN toolset.

---

<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:** [February 1, 2021, 8:46pm UTC](https://forum.opencyphal.org/t/port-node-assignment-tooling-for-integrators/1099/2 "2021-02-01T20:46:45Z")

</div>

The question is timed perfectly. Watch me post a proposal with a working MVP in a few days.

---

<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:** [February 28, 2021, 10:54pm UTC](https://forum.opencyphal.org/t/port-node-assignment-tooling-for-integrators/1099/3 "2021-02-28T22:54:56Z")

</div>

Hi again @mawildoer! Here is my proposal: [https://github.com/UAVCAN/pyuavcan/pull/154](https://github.com/UAVCAN/pyuavcan/pull/154)

The related Spec amendment can be discussed here: [https://github.com/UAVCAN/public\_regulated\_data\_types/pull/109](https://github.com/UAVCAN/public_regulated_data_types/pull/109)
