Skip to content
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

Unable to map Sub Indexes of Records to PDOs #258

Open
StormOli opened this issue Jun 2, 2021 · 1 comment
Open

Unable to map Sub Indexes of Records to PDOs #258

StormOli opened this issue Jun 2, 2021 · 1 comment

Comments

@StormOli
Copy link

StormOli commented Jun 2, 2021

I'm unable to map any sub index of a RECORD object to either a Tx or Rx PDO.
It either selects a random entry that doesn't even have PDO permissions, or it adds an unknown blank entry. Sometimes it also gets stuck on the dropdown after I press enter with no way to continue without closing and opening the device.

All other object types seem to work as expected. I'm currently running version 0.8-125-g85dfd8e

@StormOli
Copy link
Author

StormOli commented Jun 4, 2021

The issue seems to be known about.
In DevicePDOView2.cs in method Vcc_ValueChangedEvent there is a comment

//warning if the subindex is still hex the converter will not know about it
//we may need to append 0x to keep it correct

I can confirm that all my subindexes in my RECORD are marked as hex in the 2nd value of "bits".
When would this not be the case and what is the reason for not appending 0x?

When I do append "0x" in the "UpdatePDOinfo" method then the PDOs map as I would expect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant