Welcome to the North American Subaru Impreza Owners Club Sunday August 20, 2017
Home Forums WikiNASIOC Products Store Modifications Upgrade Garage
Go Back   NASIOC > NASIOC Technical > Engine Management & Tuning > Open Source Reflashes

Welcome to NASIOC - The world's largest online community for Subaru enthusiasts!
Welcome to the NASIOC.com Subaru forum.

You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, free of charge, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, so please join our community today!

If you have any problems with the registration process or your account login, please contact us.
* Registered users of the site do not see these ads. 
Thread Tools Display Modes
Old 01-23-2008, 01:06 AM   #1
Scooby Newbie
Member#: 144523
Join Date: Mar 2007
Location: Modesto, California
2007 Sti
Satin Pearl White

Default questions about unused tables

I figured it would not hurt to view a copy of cobb stage 2 ots and compare it to my stock map just to get an idea of how things work. I have a question though.

Why is it that both on my target boost and initial wastegate duty cycle tables that the only tables that have any change on both are labeled "UNUSED". The other ones labeled A and B on both types of tables there is not difference in numbers when compared to the cobb stage 2 ots?

Target boost for my car according to data logging is deffinetly trying to follow the table labeled unused even though it is overboosting right now by about 1psi compared to the table.

Just to clarify I am just doing this to view and learn I am not messing with cobbs maps because I have no clue what I am doing if I were to change something.

Another question I have is if you have a target boost table why does the ECU just not control the wastegate itself? Why do you also need a duty cylce table? I am sure there is a reason but to such a noob like me when it comes to tuning it seems odd you give the car a target boost but then you als have to tell it how to get there with WGDC tables. Just random thoughts.
* Registered users of the site do not see these ads.
CenCali07sti is offline   Reply With Quote
Sponsored Links
* Registered users of the site do not see these ads.
Old 01-23-2008, 01:41 AM   #2
Scooby Newbie
Member#: 122595
Join Date: Aug 2006
Chapter/Region: NWIC
2005 LGT Wagon


The Cobb rom is not a stock rom. Cobb modified it to make room for their realtime tuning. Enginuity is really meant to be used with stock roms.

Do you know how the wastegate actuator is physically controlled? The ecu controls bleed off. That controls pressurization of the actuator. Read up on boost control.

mickeyd2005 is offline   Reply With Quote
Old 01-23-2008, 01:45 AM   #3
Scooby Specialist
Member#: 72829
Join Date: Oct 2004
Chapter/Region: W. Canada
Location: Calgary, Canada
2006 WRX
2015 WRX


The "unused" tables are unused in a normal ECU. Cobb uses these tables to store their maps. Something to do with their real time map system, IIRC.

As for the WGDC table, they help speed up the boost control process by starting with values that are "in the ball park".
Airboy is offline   Reply With Quote
Old 01-23-2008, 08:04 AM   #4
Tea cups
Scooby Specialist
Member#: 103136
Join Date: Dec 2005

Cobb's real-time tuning is simple. For the real-time capable maps, they simply redirect the ECU to always read these tables out of RAM which would be written there by the AP (real-time map). Then there's a small chunk of code that copies the corresponding RT tables from ROM (base map) to RAM after a reset (otherwise you would have problems).

The fact that the ECU always reads the RT tables from ram means that for the "base" map tables that have multiple maps in the factory ECU (for example, Target Boost), Cobb can place the "base" table in any one of the multiple maps (and leave the rest stock). So, on a manual transmission ROM, they could place it in the auto tranny map and it wouldn't matter because the ECU will always read the table out of RAM.

The 07 USDM STi is unique in that rather than having AT/MT multiple tables, it has a series of unused maps that the factory ECU never uses (as is). Cobb probably is using these maps as placeholders for the base map. Again, it doesn't matter as it is only used to copy from after a reset. In fact, the only reason I've added the unused tables and the opposite transmission tables (AT tables on an MT rom) for the USDM ECUs is so that users who own an AP can still tune with Enginuity. It isn't rocket science.
Tea cups is offline   Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
very quick question about dbw tables kh15 Open Source Reflashes 0 07-05-2009 09:02 PM
questions about new wheels..thinking about upgrading zzzzzxx Newbies & FAQs 6 06-01-2004 10:27 AM
Few questions about the Perrin Turbo Inlet and about the Samco MAF arm???? BLUETURBOWRX Factory 2.0L Turbo Powertrain (EJ Series Factory 2.0L Turbo) 27 08-21-2003 03:53 PM
question about what i should do about these 2 girls skylineR34 Off-Topic 28 07-23-2003 07:44 AM
About to buy STi, question about Subaru's fit & finish... JT-KGY STi Forum Archive 19 01-27-2003 02:39 PM

All times are GMT -4. The time now is 11:52 AM.

Powered by vBulletin® Version 3.7.0
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Powered by Searchlight © 2017 Axivo Inc.
Copyright ©1999 - 2017, North American Subaru Impreza Owners Club, Inc.