Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: V Tune Help  (Read 781 times)

0 Members and 1 Guest are viewing this topic.

CVOmedic

  • Junior CVO Member
  • **
  • Offline Offline
  • Posts: 75

    • CVO1: 2012 CVO Street Glide Slate Gray/Black
V Tune Help
« on: March 10, 2012, 03:54:23 PM »

2012 CVOSG
X-Pipe
CFR Slip Ons
TTS with Fullsac Map

Hey guys, quick question...have an email off to Steve but not sure if he will be checking them this weekend.

When setting up the base map to load prior to doing a Vtune run, I am unable to set all the 95 kPa cells in the main lambda table to 0.981.  The highest I can set these cells is 0.940.  What am I missing here???  Also, when I am done Vtuning and want to set the Lambda back to original, should I click return to baseline or return to original?  Clicking baseline gives me the table that Steve sent, while clicking original gives me a different table all together.

Also,out of curiosity why is the CID in the tuning constants set to 115 vs. 110?  Definitely not to question Steve here by any means, just curious as to why this setting is changed from what the stock motor is.  Does this directly affect the VE tables or other settings?

THANKS!!!
Logged

glens

  • Senior CVO Member
  • ****
  • Offline Offline
  • Posts: 352
Re: V Tune Help
« Reply #1 on: March 10, 2012, 04:34:15 PM »

You can't "closed-loop" the 95kPa column because it won't go closed-loop by design. 

The instructions say to merely extend the VE tables with the row values obtained at least to 80kPa.  If you'll note what you have in what Steve sent you, they likely decline a little on the way to the right end of the rows from there, and you can emulate that roll-off instead if you wish.  If you simply extend you'll be a tad rich on the right end of the row, which is better than a tad lean, probably.

You'll be wanting to return the Lambda values to "baseline" when you're done if you want to go with Steve's plan.

The CID is upped a bit to ensure that none of the VE table cells hit 127.  If when you're v-tuning you get up there yourself, you'll want to increase the CID by some small percentage and reduce the entire VE tables by that same percentage.  The CID and VE values are just factors in an equation.  If you increase one of them by X% you'll want to decrease the other by the same percentage.  That is CID×X% and VE÷X% or vice versa.  The increase/decrease are multiplicative not additive.
Logged

CVOmedic

  • Junior CVO Member
  • **
  • Offline Offline
  • Posts: 75

    • CVO1: 2012 CVO Street Glide Slate Gray/Black
Re: V Tune Help
« Reply #2 on: March 10, 2012, 05:03:59 PM »

Thanks Glens!  That answers a lot.

I just want to clarify with you real quick though...

The instructions actually state to set all columns in the main lambda table below 100 kPa to 0.981 when preparing to do Vtune runs.  You spoke about extending the 80 and up columns which I want to say is out of the smoothing or VE finalization section. (I am doing the initial set up for Vtune runs).

The illustration in the manual also shows 90 and below being set at 0.981 (there is no 95 kPa column in the picture), with the 100 kPa column being left alone as the instructions state not to change any settings in this column.

When I change all of the columns in the Lambda table that the program will let me, the 95 kPa column is automatically changed to 0.940 and turns yellow but I cannot raise this value any further although the instructions state to do so.

So the way I am understanding your response, is after I VTune I will be extending the VE tables to fill in the Columns above 80 kPa, which makes sense, but I am still a little lost on setting the main lambda table in the 95 kPa column when I create the map to Vtune with.

« Last Edit: March 10, 2012, 05:11:45 PM by CVOmedic »
Logged

glens

  • Senior CVO Member
  • ****
  • Offline Offline
  • Posts: 352
Re: V Tune Help
« Reply #3 on: March 10, 2012, 07:57:47 PM »

Yeah, I combined tail-end stuff with what you wanted to know.  Sorry.

You can click the upper left corner of the table (outside the cells) to highlight all the cells and "increment" until nothing will go any higher, then click in the upper left cell and drag the click to the lower right 90kPa cell and "decrement" back back down to "0.981", or you can just start out clicking the upper left cell and dragging the click to the lower right 90kPa cell and increment until they all get in sync, then bring it all back down together.

The increment and decrement buttons will auto-repeat after an initial pause while the mouse-click is held on them.

I just click/drag the upper-left cell to the bottom 90 cell.

The instructions are merely unclear regarding the 95kPa column.  You don't need to try to get it to go closed-loop; it won't anyway.

You mainly want to make sure you get the 90kPa column included because 80kPa values will be influenced more as they go from 85 to 89 by what's in the 90 column.  Once out of the exact center of a cell, the actual value is derived by proportion from the (up to) four cell centers surrounding the pinpoint location within the table where the engine is running at any given moment.  If that don't make sense, let me know and I'll try to explain it with more words that each mean less.
Logged

glens

  • Senior CVO Member
  • ****
  • Offline Offline
  • Posts: 352
Re: V Tune Help
« Reply #4 on: March 10, 2012, 08:16:21 PM »

Here's something I threw together a while ago for an example on another forum.  It shows in a rudimentary way how the surrounding cell values get used when a place the engine is operating isn't exactly in a cell center.

Whether or not the 80kPa column will be closed-loop in the final results, you want to make sure when you're calibrating that column that you actually have the same value being used by the ECM anywhere you might be in a cell in that column.  In order to ensure that, the next cell to the right should contain the same value at the time.  I hope this helps to clarify things instead of the converse.

[edit:  One more thing...  This example is a good illustration of why "smoothing" the VE tables via the EGR tables is a good thing as there'll be less interpolation error in the end that way.]
« Last Edit: March 10, 2012, 08:21:53 PM by glens »
Logged
 

Page created in 0.216 seconds with 21 queries.