You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for boolean data could be added for SDOs.
However, the PDO granularity will be kept at 8, so single bits cannot be mapped for performance reasons.
The following should be suffiicient to get basic support:
add data type enum
add parser
add C type to lookup, bool?
prevent mapping of objects with type 1
testing
It should more or less straight-forward, but needs some testing with devices that offer bit-access.
The text was updated successfully, but these errors were encountered:
To support further can devices and eds-files for a customer, the boolean datatype is required soon. An implementation of 1-bit SDOs would be extremly helpfull. Would it be possible in the near future?
It should more or less straight-forward, but needs some testing with devices that offer bit-access.
I have access to such a device and would like to help. If f.e. some beta-version is available for (pre-)testing, please give me a hint. Many thanks and best regards!
Hi, I actually just added support for booleans in my fork, because my EDS file wasn't parsing because of boolean. I don't have the device in question with me at the moment, but I verified that:
EDS file containing booleans are parsed without throwing a std::bad_cast
When the user requests the object to be published, it's registered as an std_msgs/Bool topic
I'm happy to create a PR. Does it add on to melodic or melodic-devel?
Support for boolean data could be added for SDOs.
However, the PDO granularity will be kept at 8, so single bits cannot be mapped for performance reasons.
The following should be suffiicient to get basic support:
bool
?It should more or less straight-forward, but needs some testing with devices that offer bit-access.
The text was updated successfully, but these errors were encountered: