Prevent the mapping of objects with a data length of 0 bytes#220
Prevent the mapping of objects with a data length of 0 bytes#220trojanobelix wants to merge 2 commits into
Conversation
|
Do you have a pre-built version with this fix in it? (Or with other fixes from the development branch latest commit). On the top github page here the latest and only release is old. Maybe time to update it? |
|
(Files deleted: New files later in this thread)
Here is the binary file for Windows. Unfortunately, I can't test it on Linux. |
|
The windows build is ok for me, but the version does not run, it asks for the .NET runtime. I tried different versions of the runtime but it always refuses to run. |
|
|
That is strange, it will not run at all (I have also the .NET 8.0.22 runtime). I also tried to copy over all files in the existing (running) tool to a new directory, copy over the files in the zip and rename it to the original name. Still not running. -edit- VS2017 does not seem to be available any more, what is recommended to use, if I want to build it myself? |
|
I use 2026, latest version |
|
Here is the new binary file for Windows. Unfortunately, I can't test it on Linux. |
2 participants
project.zip
Prevent the mapping of objects with a data length of 0 bytes.
The importer should prevent string objects with a data length of 0 from being imported.
In my opinion, string types without a defined length are formally allowed according to DS301, but:
ToDo:
Object 0x2000 in the OD is formally correct IMHO, but is created in the CANopen Editor with a data length of 0; for strings, the data length should be initialized to 1.