C6 Scan & Tune Onboard Diagnostics, Service Advice, Dyno Tuning, and Fuel Management for the Corvette
Sponsored by:
Sponsored by:

GM E38 OS 12653249 conversion to 2bar SD conversion

Thread Tools
 
Search this Thread
 
Old 09-16-2016, 10:25 AM
  #1  
NJ_phil
Burning Brakes
Thread Starter
 
NJ_phil's Avatar
 
Member Since: Jul 2016
Location: Joisey
Posts: 777
Received 50 Likes on 48 Posts
Default GM E38 OS 12653249 conversion to 2bar SD conversion

Moving to 2bar shows 6800 RPM limit on VE tables.
Any way to increase this limit?

Looks like original OS used coefficients to calculate VE rather than a table.
OK to copy over someone else's VE table from same LS3 tune to get me going?

Thanks
Old 09-16-2016, 10:52 AM
  #2  
schpenxel
Race Director
 
schpenxel's Avatar
 
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,193 Likes on 1,052 Posts
St. Jude Donor '15

Default

You can click on the axis headers and change the MAP/RPM axis break points to whatever you want within reason

E38 2 bar OS's are generally set up to go up to 175kpa by default--I would change it up to whatever the max boost value you'll ever run is and a little higher. Same for RPM. This is a pain to change later. If 175 kpa is enough then leave it as-is (it's around 11psi boost)

Then open up your original tune, open VVE editor. Same thing, click on the axis for MAP, change the values to match whatever you used in the new tune. Same for RPM.

Now copy the whole factory table, paste it into Excel.

Copy it in Excel, paste special / transpose somewhere else. That will flip the X/Y axis around (VVE and regular VE are backwards)

Then you should be left with something you can paste into the new 2 bar OS tune.

There is probably an IMRC open and closed VE table, I just make them the same. Only one is used on Corvettes but I can never remember which

For whatever reason this never works out "quite" right... every time I've done this fueling has been off 10-15% from where it was when using VVE, but it's at least close enough to get the car started.

Last edited by schpenxel; 09-16-2016 at 10:57 AM.
Old 09-16-2016, 11:13 AM
  #3  
NJ_phil
Burning Brakes
Thread Starter
 
NJ_phil's Avatar
 
Member Since: Jul 2016
Location: Joisey
Posts: 777
Received 50 Likes on 48 Posts
Default

Any negative side effects of going 0 - 8192 RPM range? Easier for me working with base 2
Is the VVE editor built into v3.2x or a separate utility

thx
Old 09-16-2016, 11:16 AM
  #4  
schpenxel
Race Director
 
schpenxel's Avatar
 
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,193 Likes on 1,052 Posts
St. Jude Donor '15

Default

Built in. It's under edit I believe

8192 should be fine. You lose some resolution throughout the table if it goes that high but not a big deal IMO.
Old 09-16-2016, 11:26 AM
  #5  
NJ_phil
Burning Brakes
Thread Starter
 
NJ_phil's Avatar
 
Member Since: Jul 2016
Location: Joisey
Posts: 777
Received 50 Likes on 48 Posts
Default

See it under Edit now....but only after going back to MAF, VVE wasn't visible in SD.
Old 09-16-2016, 11:27 AM
  #6  
schpenxel
Race Director
 
schpenxel's Avatar
 
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,193 Likes on 1,052 Posts
St. Jude Donor '15

Default

Right, it doesn't exist in the upgraded OS--uses regular VE tables instead
Old 09-16-2016, 11:35 AM
  #7  
NJ_phil
Burning Brakes
Thread Starter
 
NJ_phil's Avatar
 
Member Since: Jul 2016
Location: Joisey
Posts: 777
Received 50 Likes on 48 Posts
Default

Originally Posted by schpenxel
Right, it doesn't exist in the upgraded OS--uses regular VE tables instead
Or coefficients as per my E38 OS version.

Uggh.. I have to manual enter the axis settings since VVE doesn't interpolate or use one of their "canned" ranges.... but selecting a canned range crashes and says "Report this error to HPT".

I get the drift here and should be able to get it going one way or another and will post the tune later on if you'd be kind enough to take a look.
Old 09-16-2016, 11:36 AM
  #8  
schpenxel
Race Director
 
schpenxel's Avatar
 
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,193 Likes on 1,052 Posts
St. Jude Donor '15

Default

Yeah just post it up whenever. Honestly you're just looking for something close enough to get it started.

You should be able to copy the axis values out of the 2 bar OS then paste them into the VVE axis settings
Old 09-16-2016, 03:58 PM
  #9  
NJ_phil
Burning Brakes
Thread Starter
 
NJ_phil's Avatar
 
Member Since: Jul 2016
Location: Joisey
Posts: 777
Received 50 Likes on 48 Posts
Default

Originally Posted by schpenxel
Yeah just post it up whenever. Honestly you're just looking for something close enough to get it started.

You should be able to copy the axis values out of the 2 bar OS then paste them into the VVE axis settings
Understand exactly what you're saying but increasing RPM beyond 6800 or map above 105 kpa generates negative numbers at the extremes of the generated VE table and crashes HPT.

A whole afternoon of reading shows VVE uses settings under Dynamic to generate the table and I get some strange looking tables when adjusting Boundaries for higher RPM and Kpa as well as the coefficients.

Hard to believe it's this difficult to generate a simple table to get me going

Here's the result... Doesn't look right to me though
Attached Files
File Type: hpt
NJPhil_SD_ID1000.hpt (736.8 KB, 121 views)

Last edited by NJ_phil; 09-16-2016 at 04:04 PM.
Old 09-16-2016, 04:15 PM
  #10  
schpenxel
Race Director
 
schpenxel's Avatar
 
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,193 Likes on 1,052 Posts
St. Jude Donor '15

Default

Email me and I'll send you a VE table to start with, I'll PM you my address
Old 09-16-2016, 10:55 PM
  #11  
Unreal
Team Owner
 
Unreal's Avatar
 
Member Since: Nov 2007
Location: Gilbert AZ
Posts: 24,035
Received 2,313 Likes on 1,793 Posts

Default

I would keep as much resolution as possible. No reason to goto 8200. Go ~200rpm past your fuel limit. No reason to have a good chunk of map that you can never use.
Old 09-17-2016, 09:43 AM
  #12  
NJ_phil
Burning Brakes
Thread Starter
 
NJ_phil's Avatar
 
Member Since: Jul 2016
Location: Joisey
Posts: 777
Received 50 Likes on 48 Posts
Default

Originally Posted by Unreal
I would keep as much resolution as possible. No reason to goto 8200. Go ~200rpm past your fuel limit. No reason to have a good chunk of map that you can never use.
Good idea. Kept it at 7200 which is the limit for this motor. Gave up on generating a map with HP's VVE which works perfectly at 1bar/6400 but gets flakey and crashes generating a 2 bar, obviously because I'm doing something wrong. There are ways to get it working depending on which physics professor you talk to and some claim to generate maps that track AFR error within 2% but I'll pass on that science project and just want a safe base and dial it in with WB.

Wound up generating a map with Bluecat, using a somewhat close characterization to my mods and used Excel to scale it into my kpa and RPM limits (175kps vs 7200 RPM) .

After going through this, confidence on setting this up properly is down to about 80% and might check out ECS for a base tune to get me going. Well worth the $149 bucks if that's the going rate.

VE %



Airflow:

Last edited by NJ_phil; 09-17-2016 at 12:06 PM.

Get notified of new replies

To GM E38 OS 12653249 conversion to 2bar SD conversion




Quick Reply: GM E38 OS 12653249 conversion to 2bar SD conversion



All times are GMT -4. The time now is 04:01 PM.