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

Smart ECU: misfire detection on running engine #936

Open
rusefi opened this issue Sep 15, 2019 · 11 comments
Open

Smart ECU: misfire detection on running engine #936

rusefi opened this issue Sep 15, 2019 · 11 comments

Comments

@rusefi
Copy link
Collaborator

rusefi commented Sep 15, 2019

Can we please detect broken injector or broken coil programmatically?

@chuckwagoncomputing
Copy link
Member

#925 #343 #2180

@rusefillc rusefillc changed the title misfire detection Smart ECU: misfire detection Jun 26, 2021
rusefillc added a commit to rusefi/rusefi_documentation that referenced this issue Jul 18, 2021
rusefillc added a commit to rusefi/rusefi_documentation that referenced this issue Jul 19, 2021
@rusefillc
Copy link
Contributor

@chuckwagoncomputing
Copy link
Member

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.

@rusefillc
Copy link
Contributor

@chuckwagoncomputing any screenshots? :)

@chuckwagoncomputing
Copy link
Member

Even better, a video:
https://www.youtube.com/watch?v=G6WYnNlYuiQ
The video is a diesel, but the same thing exists for gas vehicles.

@stefanst
Copy link
Collaborator

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?

@thirstyone
Copy link
Contributor

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)

@rusefillc
Copy link
Contributor

@thirstyone any specific numbers / any excel or google spread sheet to attach? :)

@chuckwagoncomputing
Copy link
Member

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?

@rusefillc
Copy link
Contributor

@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

rusefillc added a commit to rusefi/rusefi_documentation that referenced this issue Jul 21, 2021
rusefillc pushed a commit that referenced this issue Sep 6, 2021
rusefillc pushed a commit that referenced this issue Sep 6, 2021
rusefillc pushed a commit that referenced this issue Sep 6, 2021
rusefillc pushed a commit that referenced this issue Sep 6, 2021
@rusefillc
Copy link
Contributor

We have data and proposal at https://rusefi.com/forum/viewtopic.php?p=42922#p42922

@rusefillc rusefillc changed the title Smart ECU: misfire detection Smart ECU: misfire detection on running engine Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants