Object Parameter Validity about canopen-stack HOT 2 CLOSED

Great that you can use it, nice to hear!

Regarding the issue with the write access of your mentioned COBID object entries from the master side, I think you are right that we are not 100% standard conform when using object variables of a basic type (e.g., CO_LONG). The basic data type is allowing every value in the full range of the corresponding data type.

When we need to check certain values or limit the range of an object entry, we should add a user objects. With the type-functions (read, write, ctrl, and size), we can implement any logic. The user object type functions are separated in a small structure, so we can reuse them in multiple objects easily. The example Write serial number illustrates the mechanism.

For some DS301 defined objects, there are such type-functions already implemented (unfortunately not for writing your mentioned objects).

If you have some time:
The types for the handling of write operations to these objects are a highly welcome enhancement for the stack.

There is a similar type function already available for the SDO server COBID (see: COTypeSdoIdWrite).

If you can wait:
I try to manage an update next month, with some documentation enhancements. I think I can include these needed type functions for any COBID objects in a standard object dictionary, too.

from canopen-stack.

That sounds like a great plan.

from canopen-stack.