Those were two different points; I know where Prusas come from. But China still has duties/import taxes (which I know because I had to pay them for boxes I got from China.) I used Prusas as an example because importing them would be more comparable to swerve modules.
Omios come from China. When we bought ours we did not pay any import duties that I was aware of. Import duties are all over the place depending on what is being imported.
I’m not sure what you mean here? CAN ID is set on a per-device basis, not per device type. I am not aware of any reserved IDs on our networks, can you share more information on what you are referring to?
Gotcha. So in this image from that link, the CAN ID that is set on a device (motor controller or whatever other device) is the “device number” field value? Do the device type and manufacturer code get inferred from the class instantiated in the code?
Yeah. So when you make a new LittleEngineThatCould(4) in code and set something, IThinkICAN’s vendordep would send out a message with a Device Type corresponding to LittleEngineThatCould and a Manufacturer code corresponding to IThinkICAN. Apart from listening for the universal heartbeat and the disable message, I don’t think rest of the fields have to actually be followed.