# Python API to configure the subject-IDs/service-IDs/registers

**URL:** <https://forum.opencyphal.org/t/python-api-to-configure-the-subject-ids-service-ids-registers/1705>\
**Category:** PyCyphal\
**Created:** [July 8, 2022, 8:42am UTC](https://forum.opencyphal.org/t/python-api-to-configure-the-subject-ids-service-ids-registers/1705 "2022-07-08T08:42:32Z")\
**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 8, 2022, 11:17am UTC](https://forum.opencyphal.org/t/python-api-to-configure-the-subject-ids-service-ids-registers/1705/3 "2022-07-08T11:17:56Z")

</div>

> [@pat1](#):
>
> Any suggestions for the python API to use to configure the subject-IDs/service-IDs/registers of an other node?  
> Like yakut command:

This is slightly offtopic, but your example looks concerning because this is not how you configure subject-IDs. Ports are named simply like `this_is_your_port` and the name is embedded into:

```auto
uavcan\.(pub|sub|srv|cln)\.PORT_NAME\.(id|type)

```

This is documented here:

> <https://github.com/OpenCyphal/public_regulated_data_types/blob/70573cb98a346f5a9aee54ce421a8a79700df2b4/uavcan/register/384.Access.1.0.dsdl#L103-L199>

Based on what I see, your register should be renamed roughly into **`uavcan.srv.th_get_data_and_metadata.id`** , and there also needs to be a **`uavcan.srv.th_get_data_and_metadata.type`** that contains the name of the data type.

It is also a design mistake to expose the name of the data type in the register name because these are unrelated entities. More on this in the Guide, look for [“syntax-semantic separation”](https://forum.opencyphal.org/t/the-cyphal-guide/778/4).

---

_[View the full topic](https://forum.opencyphal.org/t/python-api-to-configure-the-subject-ids-service-ids-registers/1705)._