Hello! I am starting to look into how to use UAVCAN 1.0 and one of my primary questions is regarding how I can create a device as a vendor that speaks UAVCAN and publish the message info for users to use. I generally understand the concept of DSDL for creating datatypes, and I read in the guide document that the Public/Unregulated type messages are primarily the ones recommended for vendors of devices to use, and that the public regulated ones are very limited and reserved for general widely applicable messages. My concern is that the guide recommends that vendors provide a way to reconfigure their devices to allow non-fixed IDs for their DSDL messages. This seems very complex, and something that a user of my devices doesn’t care about at all.
Let me give an example: A user has an aircraft with a PX4 flight controller. They buy a UAVCAN GPS device that supports a few public regulated messages, but it also has a few public unregulated messages that give additional data and control. This is a popular device and PX4 has a parameter that allows you to chose this specific GPS device, which then signals to PX4 that it should try to use the additional public unregulated messages, which it knows because the DSDL was published by the device vendor, along with the ID numbers. The ID numbers can’t change, because the device has been released and doesn’t have any UI for users to change the IDs. PX4 also needs to know it’s device IDs and it gets those from the vendor.
How does this not work? It seems like there should be a global spreadsheet or something where vendors can go in and choose their device IDs or something. It could be a way of notifying others that they plan to use these, but doesn’t preclude others from creating devices with the same IDs. It could then be kind-of driven by the market. If someone releases a successful device, people would know not to try to use those same IDs. If someone else marked that they plan on using a block of 1000 IDs and has no market share and products that actually use them, then people could just ignore his claim on those and win them by releasing a device that does use them.
Any guidance here would be very helpful! Thanks in advance.