How to get dynamic "C" to save as real time???

TurboQueef · 06-03-2006, 02:04 PM

This has got me sideways.....

I have been working on my timing.. to date I have copied dynamic "A" to B&C but "C" won't save in real time. If I save it as a base map and then open the base and save it as a realtime it seems to stay for a while... until the critical moment when I am at the drag strip and it decides to go back to the original dynamic "C" values...

Has anyone figured out why it does this and how to correct it?

Thanks,

Jeff B

WolfPlayer · 06-03-2006, 03:40 PM

DA C does NOT save as a realtime. Actually, I think the first 2 rows save as realtime - rofl. However, even though it is marked as a real time map, it is NOT save-able as a realtime map. This is just the way it works

. Cobb is limited to a particular amount of memory for use with realtime maps for saving. That memory limit is reached with regard to DA C and the '05 STi. '04 STIs have it worse.

t

RacerXS · 06-13-2006, 08:37 PM

"Supposedly" this will be fixed in the new release.
It seems if you make the changes to your base map, then load your real time map & make the changes after loading again they will stay. Kinda a pain, but it works.

TurboQueef · 06-13-2006, 11:52 PM

Quote:

Originally Posted by RacerXS

"Supposedly" this will be fixed in the new release.
It seems if you make the changes to your base map, then load your real time map & make the changes after loading again they will stay. Kinda a pain, but it works.

Good news on a possible fix with next release... I am following this procedure:

Editing my changes to "C" map (& A,B) to a base map I created.
Saving the base map as a realtime
Loading the real time to the ECU

It works but I never know for sure if it loads to the ECU so after loading the realtime to the ECU I:

Exit from "live tuning"
Re-connect (enter live tuning)
Verify I am in "ECU MAPPING<ECU MAPPING>" <ECU MAPPING>and then verify the changed values show up in this mode.

You are correct, this is a PITA especially if you are rushing to change things in the staging lanes in between 1/4 mile passes.

Thanks for the info..

WolfPlayer · 06-14-2006, 04:39 AM

This also happens with the injector latency too. So, keep that in mind for you guys with bigger injectors who are tuning the latency.

t

cnstman · 06-14-2006, 06:31 AM

Quote:

Originally Posted by WolfPlayer

This also happens with the injector latency too. So, keep that in mind for you guys with bigger injectors who are tuning the latency.

t

Thanks for the heads up

jays05 · 06-14-2006, 06:37 AM

Odd - I have never had a problem with injector latency not saving in a realtime map.

I reflashed my base map recently (to disable a wastegate CEL from installing my EBC) and put my latest dynamic advance C map into the base map.

daemon · 06-14-2006, 06:50 AM

My latencies would do that. At first I thought I was going crazy. Then I realized I was crazy, but it was doing that regardless.

Nixlimited · 06-26-2006, 01:02 PM

Has anyone fully figured out the functionality of DA A, B, and C?

crystal_Imprezav · 06-27-2006, 04:57 AM

From the trends I have seen, table A is used most often for most conditions, table B is used for optimal conditions based on temp, elevation and various other factors, and table c is used for not so optimal conditions. The only time I have seen values from table c are when it is extremely hot out, and it looks like the ecu is retarding timing to the values in my c table. I could be wrong but this is what I have been seeing.

TheMadScientist · 06-27-2006, 05:54 AM

Quote:

Originally Posted by crystal_Imprezav

From the trends I have seen, table A is used most often for most conditions, table B is used for optimal conditions based on temp, elevation and various other factors, and table c is used for not so optimal conditions. The only time I have seen values from table c are when it is extremely hot out, and it looks like the ecu is retarding timing to the values in my c table. I could be wrong but this is what I have been seeing.

For me tha DA works like this.

DA-A until the engine reaches 180*F as read on my SM3.
DA-B just about all conditions after the engine has warmed up past 180*F.
I have seen DA-C for ~20min total. I saw this map being used when my uppipe heat shield was rattling and causing false knock.
So far I have not seen ambient temp affect the DA useage. I am sure ambient temp does affect how the DA maps are used, but I have not been able to corelate it.

TMS

daemon · 06-27-2006, 06:00 AM

Table B definitely appears to be the max allowed dynamic advance. The interesting thing about C is that it gives the most timing (if that is indeed its purpose) to low RPM high load locations (and none at all to any low load location).

One interesting thing I noticed was that if I drop the values in B to something very low like 4-5 and A to 0-2, then it takes for ever for my DAM to reach 1.0 after a reset, if ever. If I change those back to, say, 8, then the DAM will climb to one after one pull. So it almost seems like the ECU is saying, increase DAM only if I can run X degrees above the values in A (or just zero for that matter) without knocking.

cnstman · 06-27-2006, 06:45 AM

Quote:

Originally Posted by TheMadScientist

For me tha DA works like this.

DA-A until the engine reaches 180*F as read on my SM3.
DA-B just about all conditions after the engine has warmed up past 180*F.
I have seen DA-C for ~20min total. I saw this map being used when my uppipe heat shield was rattling and causing false knock.
So far I have not seen ambient temp affect the DA useage. I am sure ambient temp does affect how the DA maps are used, but I have not been able to corelate it.

TMS

Great info, thanks.

crystal_Imprezav · 06-27-2006, 11:33 AM

Hmm thats wierd. The way my maps are set are that I have A & B all set to the same value and +/- the PI to correlate the timing I was looking for. This way I can see if the ECU is pulling any timing and where/load/etc. because at WOT the DA should always be that set number I have in maps A and B. I have C set to lower values which is why I think the ECU defaults to C due to extreme temps. or knock detection beacuse when the ECU doest retard my timing it is usally to one of the values in my C table. I also think that ambient temps. have to do with C b/c I know I am not knocking at any of the loads and rpm's in my log and listening with headphones etc. I think it does it when the turbo is out of its efficiency range and the wastegate is working too hard and still not making target boost (or the turbo dynamics are extremely high). IAT could also correlate to the C map as well. As for the DAM, mine is always 1 even after I reset the ecu. Havent tried it after disconnecting the battery, but I have never seen it go under 1 even after many resets.

daemon · 06-27-2006, 11:42 AM

Quote:

Originally Posted by crystal_Imprezav

As for the DAM, mine is always 1 even after I reset the ecu. Havent tried it after disconnecting the battery, but I have never seen it go under 1 even after many resets.

I have DAM set to 0.7 in my base map. If you have it set to 1.0 there then you probably never would see less than one (on any decent tune oc).

06-03-2006, 02:04 PM	#1
TurboQueef Silver Member Car: 2005 STI Fav Mod: Shawn's brain Location: Southwest Michigan Posts: 418 Join Date: Aug 2004 Trader Rating: (0)	How to get dynamic "C" to save as real time??? This has got me sideways..... I have been working on my timing.. to date I have copied dynamic "A" to B&C but "C" won't save in real time. If I save it as a base map and then open the base and save it as a realtime it seems to stay for a while... until the critical moment when I am at the drag strip and it decides to go back to the original dynamic "C" values... Has anyone figured out why it does this and how to correct it? Thanks, Jeff B This ad is not endorsed by this member. Please register or login to hide this ad.

06-03-2006, 03:40 PM	#2
WolfPlayer Moderator & ECU Tech Car: 05 CGM STI Fav Mod: mo boostaz Location: Fredneck, MD Posts: 3,704 Join Date: Jun 2004 Trader Rating: (6)	DA C does NOT save as a realtime. Actually, I think the first 2 rows save as realtime - rofl. However, even though it is marked as a real time map, it is NOT save-able as a realtime map. This is just the way it works . Cobb is limited to a particular amount of memory for use with realtime maps for saving. That memory limit is reached with regard to DA C and the '05 STi. '04 STIs have it worse. t

06-13-2006, 08:37 PM	#3
RacerXS S204 Racer Car: 05' Sti Black Fav Mod: Dyslexia Location: Central, NJ Posts: 3,362 Join Date: Oct 2004 Trader Rating: (13)	"Supposedly" this will be fixed in the new release. It seems if you make the changes to your base map, then load your real time map & make the changes after loading again they will stay. Kinda a pain, but it works.

06-14-2006, 04:39 AM	#5
WolfPlayer Moderator & ECU Tech Car: 05 CGM STI Fav Mod: mo boostaz Location: Fredneck, MD Posts: 3,704 Join Date: Jun 2004 Trader Rating: (6)	This also happens with the injector latency too. So, keep that in mind for you guys with bigger injectors who are tuning the latency. t

06-14-2006, 06:37 AM	#7
jays05 Spec C Club Car: Blue 05 STI Fav Mod: Synapse FMIC Location: Upstate NY Posts: 1,721 Join Date: Nov 2004 Trader Rating: (0)	Odd - I have never had a problem with injector latency not saving in a realtime map. I reflashed my base map recently (to disable a wastegate CEL from installing my EBC) and put my latest dynamic advance C map into the base map.

06-14-2006, 06:50 AM	#8
daemon The Next Petter Solberg Car: 2004 STi Location: Florida Posts: 865 Join Date: Feb 2004 Trader Rating: (0)	My latencies would do that. At first I thought I was going crazy. Then I realized I was crazy, but it was doing that regardless.

06-26-2006, 01:02 PM	#9
Nixlimited Professional STI Racer Car: 05 STi CGM Fav Mod: Tuning... Location: San Diego Posts: 811 Join Date: Feb 2005 Trader Rating: (0)	Has anyone fully figured out the functionality of DA A, B, and C?

06-27-2006, 04:57 AM	#10
crystal_Imprezav Spec C Club Car: Slow 05 STi Fav Mod: Loping Idle Location: Chewy's Garage Posts: 1,881 Join Date: Mar 2005 Trader Rating: (12)	From the trends I have seen, table A is used most often for most conditions, table B is used for optimal conditions based on temp, elevation and various other factors, and table c is used for not so optimal conditions. The only time I have seen values from table c are when it is extremely hot out, and it looks like the ecu is retarding timing to the values in my c table. I could be wrong but this is what I have been seeing.

06-27-2006, 06:00 AM	#12
daemon The Next Petter Solberg Car: 2004 STi Location: Florida Posts: 865 Join Date: Feb 2004 Trader Rating: (0)	Table B definitely appears to be the max allowed dynamic advance. The interesting thing about C is that it gives the most timing (if that is indeed its purpose) to low RPM high load locations (and none at all to any low load location). One interesting thing I noticed was that if I drop the values in B to something very low like 4-5 and A to 0-2, then it takes for ever for my DAM to reach 1.0 after a reset, if ever. If I change those back to, say, 8, then the DAM will climb to one after one pull. So it almost seems like the ECU is saying, increase DAM only if I can run X degrees above the values in A (or just zero for that matter) without knocking.

06-27-2006, 11:33 AM	#14
crystal_Imprezav Spec C Club Car: Slow 05 STi Fav Mod: Loping Idle Location: Chewy's Garage Posts: 1,881 Join Date: Mar 2005 Trader Rating: (12)	Hmm thats wierd. The way my maps are set are that I have A & B all set to the same value and +/- the PI to correlate the timing I was looking for. This way I can see if the ECU is pulling any timing and where/load/etc. because at WOT the DA should always be that set number I have in maps A and B. I have C set to lower values which is why I think the ECU defaults to C due to extreme temps. or knock detection beacuse when the ECU doest retard my timing it is usally to one of the values in my C table. I also think that ambient temps. have to do with C b/c I know I am not knocking at any of the loads and rpm's in my log and listening with headphones etc. I think it does it when the turbo is out of its efficiency range and the wastegate is working too hard and still not making target boost (or the turbo dynamics are extremely high). IAT could also correlate to the C map as well. As for the DAM, mine is always 1 even after I reset the ecu. Havent tried it after disconnecting the battery, but I have never seen it go under 1 even after many resets.