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

J1939 Multiplex Signal Handling #12

Closed
pesky-cpu opened this issue Nov 9, 2021 · 3 comments
Closed

J1939 Multiplex Signal Handling #12

pesky-cpu opened this issue Nov 9, 2021 · 3 comments

Comments

@pesky-cpu
Copy link

pesky-cpu commented Nov 9, 2021

Issue: For multiplexed signals currently, you have to add the signal to a ‘Numeric Display’, which takes a long time to set up if trying to see multiple multiplexed messages:
Bug fix: The ‘Numeric Display’ only updates the bottom value if it’s a multiplexed message. On the below screenshot, the ‘a)’ ‘Battery_voltage’, is updated correctly. But the ‘b)’ ‘Feedback_Current_2’ and ‘Diagnostic_2’ are not updated.
Feature Request: Have a toggleable option somewhere on the ‘CAN / CAN FD Trace’ window to have persistent memory for multiplexed messages, vs displaying ‘N/A’ when data isn’t received. It might be worthwhile having a toggle to show absolute time received for each signal?
image

@freshhope
Copy link
Member

the multiplex engine is fully re-written, so could you please upg within software to latest beta version and check if this issue still exists?

@pesky-cpu
Copy link
Author

pesky-cpu commented Feb 10, 2022

Way better - thanks! Only issue is that if replaying a log and you have a message collapsed, if you open the message it will only show the most recent signal. Is it possible to fix this?
image

@freshhope
Copy link
Member

Have you try the chronological mode? You need to use this mode to view message history.
image

The message list max length may have limitation, if you want to view more message, you can create a new trace and let it only show certain id.

I am also trying to implement x64 version and unlimited message buffer, please wait for the new features.

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

2 participants