-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Cruise Fault when powering the car for the 1st time in the day #1586
Comments
Can you provide a route where this happens? |
There should be many people encountering the same problem,like me |
@sshane sorry for the delay. I haven't seen the issue again since I opened this issue until yesterday. What do you need to me to send to you about yesterday's episode? (what you mean by "route"?) |
Find where it happens and send the link from https://connect.comma.ai/ |
I will do that, thank you (Last week route is not appearing anymore in connect.comma.ai) |
@sshane it happened yesterday and I went to connect.comma.ai and cannot see the the recordings there. I see all recordings before and after the episode, but not the one with the Cruise fault. Maybe Comma does not record when it has Cruise fault? |
Describe the bug
I have been using comma 3 for 1.5 years now and in the last few months I started to get the "Cruise fault" error a lot (I don't think I ever had that error on the first year using Comma).
I was able to identify that the error happens when I am powering on my car usually in the morning and the Comma was totally powered off.
So my car powers on while the Comma is still loading and then Comma indicates that that Car is offline and only after Comma indicates the Car is online I can then power off and on my car and the error goes away (If I try to power off/on the car while Comma indicates the Car is offline, it will still throw the Cruise fault error).
Which car does this affect?
Honda Oyssey 2019
Provide a route where the issue occurs
n/a
openpilot version
0.9.7
Additional info
No response
The text was updated successfully, but these errors were encountered: