Closed martinwag closed 3 years ago
Is this still relevant? If not please close
Yes, it is. It's more like do we want to change that (and lose compatibility) or keep it as it is (and violate CiA 309-3).
I'd encourage staying as close to the specs as possible.
TODO RFC2045 mime-base64
RFC2045 mime-base64 is implemented in CANopenNode v2.0 and v4.0. See example https://github.com/CANopenNode/CANopenSocket/tree/master/examples/basicDevice
Encoding for data types "os - octet string", "us - unicode string" and "d - domain" is currently hex-string. According to 309-3 this should be RFC2045 mime-base64.