-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
"Blip" with trigger error on several boards #4552
Comments
@BeerMoneyMotorsports please recomment snapshot firmware since we've added EXTI errors data logging - need to reproduce issue with that logging #4473 @BeerMoneyMotorsports how many miles do you put on rusEFI yourself on an average week? |
@rusefillc i will have them update to latest snapshot and report back. @rusefillc somewhere between 50-100 miles a week |
Here is one with snapshot. 58 second mark https://rusefi.com/online/view.php?log=1022 SD card log does not contain new EXTI error because SD card logs are overall limited :( #3985 |
Her'es my log of it happeneing on a Hellen NB1. 662seconds in https://www.rusefi.com/online/view.php?log=1025 |
Any update? |
Vaguely related to #4553 |
i could not upload this file to REO but i think i had the issue at the end of this log. ive been driving and logging all day. it was at idle and just decided to shut off. Not peter out and die, just cut off. https://drive.google.com/file/d/1LgBXt_V72_rVc6iSb9b8lJ7vOliuQ3Fm/view?usp=sharing |
@BeerMoneyMotorsports please clarify which of four kinds of log files is there @BeerMoneyMotorsports would you be available to paste a screenshot focusing on the relevant portion of the log here showing RPM and trigger error counter? that kind of raw data processng / more clear description of what you have would help. |
@mck1117 check this out we have a loss of second in time at the moment of trigger error https://www.rusefi.com/online/view.php?log=1025 - note blue value jump from 662.6 to 663.6 Kudos @dron0gus |
Same in 1022 This is highly suspecious :) |
Reminds us of #4554 |
It is a Tuner Studio log. I have been logging all day in an attempt to catch it. On my car, both occurrences show no trigger error. They were both around idle and then the engine cuts off. another occurrence https://rusefi.com/online/view.php?log=1038 |
@rusefillc both of mine have 1 second loss as well. edit- the original na6 and 97 above show the same loss of about 1.1 seconds. |
@rusefillc i had several instances tonight on a date with the wife. below is one of them and they all show 1 second missing. These were all with SD logging at 3ms. |
The whole 1s jump is exciting progress. Now that I was able to reproduce this on a bench twice we are getting closer to resolution. #4557 |
@rusefillc i changed from 50ms to 3 ms on sd logging earlier. The issue happened far more frequently after that change. |
See also #4560 |
I have 3 reports of a "Blip" while driving. The report is that the engine and tach die, then come back on if the car is in motion(restarts itself) but will die if not in motion. This issue is started under NA6 due to the first one reporting the issue.
Current reports-
NA6 firmware-- [rusEFI 2022.06.29.hellenNA6.1831869224]
NA8 96 firmware-- [rusEFI 2022.06.29.hellenNA8_96.4107948449]
NB1 firmware-- [rusEFI 2022.07.01.hellen-nb1.3773366088]
logs-
NA6- https://rusefi.com/online/view.php?log=952
96- https://rusefi.com/online/view.php?log=1004
nb1- incoming
The text was updated successfully, but these errors were encountered: