-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
v8.0.0 build crashes upon DBC decoding data #1083
Comments
Hi Daniel, this build seems to fail when I open the GUI:
|
Hi Daniel, just wanted to check if you've had the chance to review this further? |
Just FYI I tried also the latest dev build 8.0.2, but here I get below issue when trying to open it on Windows 10:
|
please try this versionhttps://github.com/danielhrisca/asammdf/actions/runs/11889185054 |
Hi Daniel, this seems to resolve the crashing and allows for DBC decoding data again - so that's much better! Minor observations:
|
Hello Martin, have a try with this build https://github.com/danielhrisca/asammdf/actions/runs/11893707166 All the layouts have been setup with 1px margins to reduce wasted screen space |
Thanks Daniel, this is great - solved the previous issues! One other issue we've had reports on from users is inconsistency in terms of the localized PC time across the 'Raw CAN bus trace' and the 'decoded' physical values plots. See below example: As evident, the raw CAN bus trace starts at 09:43 (+02:00) The decoded physical plot seems to start at 08:43 (+01:00), while the left-side timestamp shows 07:43 (+00:00). I realize that the times are in principle all correct because of the explicit time zone factor at the end of them. But I guess the intuitive solution from my view would be to have all of them show the same localized time, with the correct one being the +02:00 in this particular log file example case, i.e. what the raw CAN bus trace displays. But let me know if there is a reason for the differences that I am missing? |
Hi Daniel, wanted to check if you've had the chance to implement a solution for the time zone issue I mentioned? We'd love to get out asammdf GUI hosted version updated with some of these fixes. |
Hello Martin, please try the development branch code |
Latest build seems to give an error when opening:
|
I tried v8.0.0 just now to DBC decode an OBD2 file (attached) - it results in an unending loop of the decoded file being created, forcing a manual shutdown of asammdf. You can try to see if it's repeated on your end with the attached
test.zip
The text was updated successfully, but these errors were encountered: