-
-
Notifications
You must be signed in to change notification settings - Fork 261
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
Smart ECU: misfire detection on running engine #936
Comments
FWIW, Ford's IDS software has an awesome cylinder contribution graph that has also been copied by other scan tool software. It's great that the ECU can say "cylinder n is misfiring", but being able to visualize the data is awesome. |
@chuckwagoncomputing any screenshots? :) |
Even better, a video: |
Trying to start doing this with a low-resolution Miata crank trigger may be a tall initial hurdle to jump. Wouldn't this be easier using a 60-2 or 36-2 or similar trigger? |
even with this config you can clearly see the difference in timing (I just looked through the second file in saleae - without injector, I believe, without a spark it would be even more obvious) |
@thirstyone any specific numbers / any excel or google spread sheet to attach? :) |
Doesn't the trigger decoder already calculate where it "expects" the tooth to be, versus where it is? A visualization of this data would be better than nothing. Perhaps as an overlay of the trigger diagram in Console? |
@chuckwagoncomputing we have a proposal #2222 but only a proposal. Our reference diagram at https://github.com/rusefi/rusefi/wiki/All-Supported-Triggers#mazda-miata-nb |
We have data and proposal at https://rusefi.com/forum/viewtopic.php?p=42922#p42922 |
Can we please detect broken injector or broken coil programmatically?
The text was updated successfully, but these errors were encountered: