Fix: Assign fixed port IDs for DSDL wrappers which have a fixed port ID assigned

[aentinger]

All existing DSDL wrappers stored in src/wrappers need to be checked against the DSDL specification in public_regulated_data_types. Any type that has a fixed-port ID (can be identified by a number prefixed to the type name), e.g. 409.Write.1.0.uavcan, the corresponding wrapper need to be modified as shown below:

-template <CanardPortID ID>
+template <CanardPortID ID = uavcan_file_Write_1_0_FIXED_PORT_ID_>
class Request
{
...
-template <CanardPortID ID>
+template <CanardPortID ID = uavcan_file_Write_1_0_FIXED_PORT_ID_>
class Response
{
...

[pavel-kirienko]

One might want to use a type with a fixed port-ID over a non-fixed port. Why don't you just say template <CanardPortID ID = uavcan_file_Write_1_0_FIXED_PORT_ID_>?

[aentinger]

This would work 👍 My only gripe is that the whole template concept is not future-proof when it comes to changing ports via register API during runtime. You've got a smart way out of that? (I wanted to address it only after fixing this).

[pavel-kirienko]

You've got a smart way out of that?

Ah yes. Irrespective of my above comment, templates shouldn't be used here at all because port-IDs are not meant to be hard-coded.

[aentinger]

I'll update above comment with your suggestions and let's fix the hard-coded port-id another time ;)

[aentinger]

Fixed by #109.