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

Cranking with reasonable compression waves does not stay synced #6511

Open
ggurov opened this issue May 14, 2024 · 1 comment
Open

Cranking with reasonable compression waves does not stay synced #6511

ggurov opened this issue May 14, 2024 · 1 comment

Comments

@ggurov
Copy link

ggurov commented May 14, 2024

Describe the bug
With addition of reasonable compression waves, trigger decoder appears to lose sync after 4 revolutions

Hardware

  • Board: stm32_mega
  • Engine info: bench-ardustim with compression waves 36-2 + 1 tooth cam

To Reproduce
Steps to reproduce the behavior:

  1. Set up ardustim to 150 rpm min with compression waves enabled
  2. start stim
  3. observe 4 revolutions and syncloss with no attempt to resync - sync errors now going up

Expected behavior
ECU to start synced with the trigger wheel

Screenshots
image

image

Additional context
see .zip file for SALEA logic analyzer capture, crank/cam are 1st and 2nd channel
tune and log are included.

rusefi_compression_wave_trigger.zip

@ggurov
Copy link
Author

ggurov commented May 14, 2024

proposed solution: experimental dev bit (maybe not even ?) for more relaxed synchronization timings below cranking RPM

it is possible someone's battery that's low enough could cause a no-start in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant