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

Exhaust VVT angle jumps from 0 to 359.1 while craking. #57

Closed
ElDominio opened this issue Aug 9, 2022 · 19 comments
Closed

Exhaust VVT angle jumps from 0 to 359.1 while craking. #57

ElDominio opened this issue Aug 9, 2022 · 19 comments

Comments

@ElDominio
Copy link
Collaborator

Tuning a car, I added CAM sync stuff to enable VVT, the car lost sync and wouldn't even start correctly. Settting cam sync to inactive would still be impossible to start, had to disable injection to clear flood.

I suggest removing first/second half settings and only having a half moon setting, then allowing a +/-360 degree offset
My Big Turbo Meth 1500cc.zip

tune and logs attached

@rusefillc
Copy link
Contributor

rusefillc commented Aug 9, 2022

it looks like with your current offset your position was too close to 360, and above 360 puts you into negative position

can you substract 360 from offset to get closer to zero position? like "-510"

image

@rusefillc
Copy link
Contributor

just a reminer that "intake" cam is the important one, that one controls engine phase
the other one which we call "exhaust" should not affect engine phase

rusefillc pushed a commit to rusefi/rusefi that referenced this issue Aug 9, 2022
@ElDominio
Copy link
Collaborator Author

image

@ElDominio
Copy link
Collaborator Author

Things we have learned:
image

-Having "maximum cam/vvt sync RPM" to a value slightly above cranking makes the decoder go crazy and start changing values from positive to negative, it needs to be over idle if it is even being used.

-still don't understand what is the difference between "single tooth first/second half" and why can't we just offset crank trigger by 360

-Tunerstudio is not accepting any values in this table:
image

@rusefillc
Copy link
Contributor

@ElDominio i see the table values defect let me fix

@rusefillc
Copy link
Contributor

@ElDominio
Copy link
Collaborator Author

ElDominio commented Aug 11, 2022

https://youtu.be/pd6hGU-FxDA example of issues. Starts fine once, then after shutting down it will never restart since apparently vvt angle changes sync point

@rusefillc
Copy link
Contributor

@ElDominio I am just a java developer with pretty limited abilities

being far from the vehicle I need tune which matches video and logs matching video as a starting point to even have a chance to help

@ElDominio
Copy link
Collaborator Author

That matches yesterday's tune and log

@ElDominio
Copy link
Collaborator Author

VID_20220811_175503.mp4

Video log log5camfirst and log2camfirst tune

@ElDominio
Copy link
Collaborator Author

VID_20220811_175422.mp4

Video of log4cam.log and log1cam.msq

@ElDominio
Copy link
Collaborator Author

ElDominio commented Aug 11, 2022

@ElDominio
Copy link
Collaborator Author

@ElDominio
Copy link
Collaborator Author

Log1cam.msq is set to second half, log2camfirst is set to first half

@rusefillc
Copy link
Contributor

this one looks like VVT is happy, decoded intake position is close to zero. around 750 RPM at low RPM car starts to die and maybe as a result of car shutting down intake position goes a bit crazy.

I suspect that intake VVT here is consequiece not cause of car dieing

https://rusefi.com/online/view.php?log=958

image

@rusefillc rusefillc changed the title Cam settings causes car to lose sync/become inoperable. Something causes car to lose sync/become inoperable with specific tune at 700ish target idle Aug 11, 2022
@rusefillc
Copy link
Contributor

Separate story rusefi/rusefi#4433

@ElDominio ElDominio changed the title Something causes car to lose sync/become inoperable with specific tune at 700ish target idle Exhaust VVT angle jumps from 0 to 359.1 while craking. Aug 20, 2022
@ElDominio
Copy link
Collaborator Author

Logs at:

https://rusefi.com/online/view.php?log=985
Can be seen at 2s

https://rusefi.com/online/view.php?log=986
Can also be seen at 2s

@mck1117
Copy link

mck1117 commented Aug 21, 2022

this is probably the same-ish thing as rusefi/rusefi#4463 and/or rusefi/rusefi#4459

@ElDominio
Copy link
Collaborator Author

Close

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

3 participants