-
-
Notifications
You must be signed in to change notification settings - Fork 225
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
detect and ignore doubled trigger edges #4656
Conversation
this looks also OK, proteus CI still sad 🙁 |
What do we perceive to be root cause here? Is it expected to get double edges or it is some specific hardware issue? Do we want to changelog this improvement? |
@ElDominio tell me about 4b11 is it Hall or VR? |
Hall |
@mck1117 please blink if alive |
I'm alive! Was racing this weekend and getting ready before that. |
What do we perceive to be root cause here? Is it expected to get double edges or it is some specific hardware issue? Do we want to changelog this improvement? |
@mck1117 is this abandoned? |
My only question with this is how do some other ECU companies trigger properly on both edges (no crazy sync loss) |
sort of unrelated discussed offline re: #4635 |
175f479
to
d0a8af3
Compare
It is a case we can detect cheaply, so why not detect it? Perhaps it will be a useful metric to detect issues we know about but haven't narrowed down to a root cause. |
I like this justification! My preference would be to have this filtering enabled by default but have an option to turn it off, what do you think? I am fine adding the option later myself. |
Right now it only filters truly doubled edges (no trigger should have 1/2 degree tooth spacing), but sure |
Detect when we get a "doubled edge" trigger input.
Will enable the second check (very wrong tooth timing) later, as it causes problems at the moment.
#987 #2222 #4650