-
Notifications
You must be signed in to change notification settings - Fork 397
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
DBC <=> XLSX initial_value #781
Comments
Hi @nexulm it is implemented, but maybe it does not work. |
Hy @nexulm - in deed - it was not implemented while switching to openpyxl, but should work just now |
It seems that the existing additional column "signal.initial_value" of the xlsx source file isn't used. Initial_value is always "0", only a few inital_value which are depending on the offset are showing another value than "0". But in this cases the offset calculation is the seems to be the reason to have the same value (initial_value = offset). For all signals the converted dbc shows initial_value = offset although the xlsx source has different values in the corresponding columns (signal.iniital_value and signal.offset)
|
Hi @nexulm could be fixed in branch: https://github.com/ebroecker/canmatrix/tree/issue_781 Additional: You don't need '--additionalSignalAttributes ... --additionalFrameAttributes ...' while importing xlsx files, they are only needed for export. |
should be merged |
InitValue is transmitted to .xslx by converting .dbc to .xlsx with parameter:
--additionalSignalAttributes initial_value
How can I get the InitialValue back from the generated .xlsx row "signal.initial_value" back to the dbc?
So far, it seems for me that this functionality isn't integrated in the code?
The text was updated successfully, but these errors were encountered: