-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CanopenEditor: Exporting to XDD v1.0 format sets wrong type on "Highest sub-index supported" #110
Comments
Thanks for reporting the bug @hepr-skylotec, Got a bugfix ready if you want to test it out now: |
@nimrof Hi, thanks for the fix. Unfortunatlely I still see the issue with the build you provided when exporting to "CANopen XDD v1.0, old" format. Output from the exporter is exactly the same with the build you provided, as with my older 4.2.0 version. Perhaps the fix did not get included in the build? |
What is the current status? Close it? |
It looks like this is still broken in v4.2.2-0-g07966bd |
@hepr-skylotec Please test if it solves the problem. |
@trojanobelix This seems to fix the issue. Subindex 01 now consistently gets datatype="0005" for Arrays and Records when exporting my dictionary. |
When using ARRAY types and exporting to XDD v1.0 "old" format, the 0x00 index of the arrays "Highest sub-index supported" gets the same type as the array elements in index 1 and up.
For SDOs of ARRAY type, the 0x00 index "Highest sub-index supported" is always an UNSIGNED8, regardless of the type used for the array elements. The editor handles this correctly in code generation and XDD v1.1 format but wrong in XDD v1.0 format export.
The
CANopenObject
for subindex 0 has thedataType
attribute set to the same value as the rest of the subindex entries in the array. ThedataType
attribute should always be0005
whic is for UNSIGNED8CanopenEditor version : v4.2.0-0-g3735e28 on Windows 11
Current output:
Expected output:
The text was updated successfully, but these errors were encountered: