-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
CAN messages in plotjugger across different buses has timing that doesn't make sense #23340
Comments
Double check with matplotlib and open an issue on plotjuggler? |
It could be how we load the data for plotjuggler, for example accurate timing requires proper use of the bus time for each CAN message that rolls over frequently, which I know cabana does found here. |
Actually my plot from cabana wasn't even the same bus (128 vs 0) and since the message was sent by openpilot bus 128 makes sense and bus 0 for this message doesn't even show up in cabana. If this bus 0 message is real I can't think of a way cabana could filter it out, so I am not sure what is going on. so it seems like this an issue with something to do with how we process the data for plotjuggler |
I haven't looked into the underlying code at all, but commaai/cabana#79 may be of interest to you, insofar as busTime (or lack thereof after the recent major Panda refactor) might affect your results in either PlotJuggler or Cabana. |
I see in the log that the messages are on bus 0 and 128 and the bus time is always zero
|
bus 0 messages for this address only seem to be from here is the data from the log for
|
Resolved by commaai/PlotJuggler#40 |
I noticed the hyundai car controller when using hyundai longitudinal theenabled
flag can get out of sync with controls stateDepending on what bus you look at, the same message can appear to have very different timing (large enough that it cannot just be how long it took to send a message, see comments below)
example:
![image](https://user-images.githubusercontent.com/4112046/147810678-a3440d6d-4ee4-409e-af4a-93e09bd81058.png)
5decac85ab437ed1|2021-12-24--12-48-45--75
Note how we continue to send non-zero ACC commands for a short period of time after brake press (although the brake controller already disabled on the brake press)The text was updated successfully, but these errors were encountered: