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
I dig into code to see how it can be implemented, unfortunatly canopen use struct library that not support 24bit data. Perhaps with this work arround it could work unpack('<l', b'\x57\x15\x00' + b'\x00')[0] # unsigned littleendian
The latest release 2.3.0 contains support for UNSIGNED24 and all the other types that were missing. Done in PR #440. Is there anything that's missing or not working properly?
Tanks @sveinse@acolomb i m just late from one week , i have not noticed new release. Anyway i confirm it is fixed with 2.3.0.
Unfortunatly i have noticed some issue with latest python_can 4.4.0 library. I ll open a new ticket if needed.
What issues specifically? The canopen 2.3.0 release should work around an incompatible change in python-can 4.4.0 already. And for the next python-can release, the incompatibility is fixed again on their end already, just not released.
Activity
sveinse commentedon Jun 19, 2024
I'm not familiar with UNSIGNED12 in canopen. Datatype 0x16 is according to CiA 301 UNSIGNED24. Where is UNSIGNED12 used?
prunith commentedon Jun 19, 2024
Hi @sveinse you are right i made a mistake UNSIGNED24 is missing UNSIGNED12 does not exist so far.
[-]Missing datatype 0x16 -> UNSIGNED12[/-][+]Missing datatype 0x16 -> UNSIGNED24[/+]prunith commentedon Jun 19, 2024
I dig into code to see how it can be implemented, unfortunatly canopen use struct library that not support 24bit data. Perhaps with this work arround it could work unpack('<l', b'\x57\x15\x00' + b'\x00')[0] # unsigned littleendian
prunith commentedon Jun 19, 2024
I see also that pull request already submited to correct that #267 unfortunately it was mixed with other change and not implemented.
sveinse commentedon Jun 19, 2024
The latest release 2.3.0 contains support for UNSIGNED24 and all the other types that were missing. Done in PR #440. Is there anything that's missing or not working properly?
prunith commentedon Jun 19, 2024
Tanks @sveinse @acolomb i m just late from one week , i have not noticed new release. Anyway i confirm it is fixed with 2.3.0.
Unfortunatly i have noticed some issue with latest python_can 4.4.0 library. I ll open a new ticket if needed.
acolomb commentedon Jun 19, 2024
What issues specifically? The canopen 2.3.0 release should work around an incompatible change in python-can 4.4.0 already. And for the next python-can release, the incompatibility is fixed again on their end already, just not released.