Data type regulation policy and membership fees

[ka_ru (Andrew)]

Uavcan and raspberry pi

As explained in Data type regulation policy and membership fees, the idea is to enable vendors to collaborate on abstract, reusable interfaces in a well-regulated fashion. In the longer term, we will use regulated vendor namespaces (such as regulated.zubax) as a base to define standard vendor-agnostic profiles. Keeping such generic namespaces in one repository is necessary to reduce the risk of fragmentation and to simplify their maintenance. I don’t think the name of a namespace could prevent …

“I don’t think the name of a namespace could prevent other companies from using it in their systems or products.” I think you are mistaken. A simple example. I need the types of RPM, MOTOR_TYPE, MOTOR_NUM_POLE_PAIRS, MOTOR_Rr, MOTOR_Rs, MOTOR_Ls_d, MOTOR_Ls_q, MOTOR_RATED_FLUX, MOTOR_MAGNETIZING_CURRENT, MOTOR_RES_EST_CURRENT, MOTOR_IND_EST_CURRENT, MOTOR_MAX_CURRENT, MOTOR_FLUX_EST_FREQ_Hz and so on. This is necessary for the normal operation of the FOC controllers. Do you think that a company producing controllers will use data types of another company? Never.