Thanks to the author for developing it. I am very interested in VE Assistant 1.62. The author's video explanation is very detailed. Is there a more concise usage process to share?
Thank you for explaining this. When the Air Calc Mode goes into "Unknown" with the MAF failed is this what the ECU is actually reporting or this just a limitation of the scanner's ability to interpret how the ECU is calculating fuel? On another note I've experienced the TCS issue while in SD mode on my CTS-V, it would cut power while going through a round-about without it, probably wouldn't be an issue without wheel speed sensors
Honestly I am not sure about the Unknown bit. I don't think it is a scanner issue, I think it is more defects inside the OEM code that are still trying to reference the MAF sensor. Aside from being reported as 'unknown' I don't know of any negative side effects from this. Good to know about the TCS issue, thanks for posting that!
I'm doing something "similar" with an LFX. I manually Zeroed out all coefficients with the word "cam" in it. Now, the VVE table remains the same no matter the cam position.... Effectively the cam position 0,0 VVE table represents my motor.... If I revise the cam timing then obviously the VVE will need re-tuning. Now that I seem to have wrapped my head around tuning VVE within HP Tuners I really need to move over to your tool...
Yes, if you want to use the variable cam timings (for more power) then you will need to account for the cam coefficients. In an older video I made I did cover this (it is the one with the "Egyptian" thumbnail). The second half is dedicated to Professional Mode for this topic. Admittedly it is a very crude approach, but VVE Asst2 will handle this properly to actually calc the cam coeff. Thanks for watching!
@@SilverSurfer77 I've watched that video, and imported the original coefficients, but having never VE or VVE tuned an ECU yet it was too much for me then. I have remapped the cam phasing (instead of floating to redline it now gets there in a hurry), but the VVE table doesn't change with varying cam position.... My concept was that the 0,0 VVE table represents "this motor with this cam phasing" regardless of what the cam phase actually is or whether it changes... This simplified process with one VVE table that is un-changing with cam position is working with the HP Tuners calc coefficients button... My next step is to re-visit your tool and start using it. Thanks a million!
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
Great Work. Looking forward to using it.
This version is out and available now! Hope you like it...next version release is imminent!!!
Thank you for the video👍
Thanks to the author for developing it.
I am very interested in VE Assistant 1.62.
The author's video explanation is very detailed.
Is there a more concise usage process to share?
Unfortunately there is not a more concise version. It is a complicated process. I wish I could make it easier and quicker to understand and use.
@@SilverSurfer77 I mean, Is there a more concise usage process ，For example, a 3-5 minute video
Awesome contribution as always. The Notepad++ tab names are funny. Are you going to be at LS Fest East 24? Thanks again for all your vids.
i am glad someone caught the N++ easter egg! LOL Unfortunately I will not be in attendance. Thanks for watching!
Thank you for explaining this. When the Air Calc Mode goes into "Unknown" with the MAF failed is this what the ECU is actually reporting or this just a limitation of the scanner's ability to interpret how the ECU is calculating fuel? On another note I've experienced the TCS issue while in SD mode on my CTS-V, it would cut power while going through a round-about without it, probably wouldn't be an issue without wheel speed sensors
Honestly I am not sure about the Unknown bit. I don't think it is a scanner issue, I think it is more defects inside the OEM code that are still trying to reference the MAF sensor. Aside from being reported as 'unknown' I don't know of any negative side effects from this.
Good to know about the TCS issue, thanks for posting that!
I'm doing something "similar" with an LFX. I manually Zeroed out all coefficients with the word "cam" in it. Now, the VVE table remains the same no matter the cam position.... Effectively the cam position 0,0 VVE table represents my motor.... If I revise the cam timing then obviously the VVE will need re-tuning.
Now that I seem to have wrapped my head around tuning VVE within HP Tuners I really need to move over to your tool...
Yes, if you want to use the variable cam timings (for more power) then you will need to account for the cam coefficients. In an older video I made I did cover this (it is the one with the "Egyptian" thumbnail). The second half is dedicated to Professional Mode for this topic. Admittedly it is a very crude approach, but VVE Asst2 will handle this properly to actually calc the cam coeff. Thanks for watching!
@@SilverSurfer77 I've watched that video, and imported the original coefficients, but having never VE or VVE tuned an ECU yet it was too much for me then.
I have remapped the cam phasing (instead of floating to redline it now gets there in a hurry), but the VVE table doesn't change with varying cam position....
My concept was that the 0,0 VVE table represents "this motor with this cam phasing" regardless of what the cam phase actually is or whether it changes... This simplified process with one VVE table that is un-changing with cam position is working with the HP Tuners calc coefficients button...
My next step is to re-visit your tool and start using it. Thanks a million!
Have you ever take a brake?🙃
Messing around with tuning is my break! 😅