TDStuart Tuning Adventure

[engineermike]

Ya I changed mapped point 0 and 1.

I set mapped point 0 exhaust to 35 and mapped point 1 exhaust to 10. It’s just something I saw another person do. I’m not sure if mapped point 1 needs to be changed at all.

In post 7 of your ghost cam thread I said DO NOT change the location of a mapped point. You’ve completely invalidated 100% of the calibration data for those mapped points.

Sponsored

 

[markmurfie]

How does my logic sound for the mapped points?

And do you remember which table that is at?

The power index modes ( stability, best fuel, best drive, and OP) are choosen based on Barometric pressure and DPL, desired percentage load. Theres max and min load tables. Load determines distance along the array, and that is where the cams atttempt to go.

The cams physical positions determine the mapped points used, not the other way around.

Its three tables, I dont know them in PCMtec. Its two base tables one for neutral and one for drive that have engine run time as an axis. Then its an adder table that has cat temp as an axis.

Seperate from this is startup time for idle, which increases the engines RPM for a period after startup. This can move where the cams are going to try to go to as well. it is possible to have it startup and go right to 750RPM in the mode you want, and have the cams to an overlap position in just a couple seconds. You make the temperature based RPM for cold warm and hot all the same or move the entry/exit ECT values down so it always starts up using the hot desired RPM.

Theres multiple ways of setting things up and achieveing the same results.

Found them in the sheet.

 

[tdstuart]

In post 7 of your ghost cam thread I said DO NOT change the location of a mapped point. You’ve completely invalidated 100% of the calibration data for those mapped points.

I tried using existing mapped points that have lots of overlap and it doesn’t idle good. Using mapped point 0 and changing it for overlap seems to work a lot better

 

[markmurfie]

AuF# in that sheet seems to be different from in your tune file.
Its the three I have checked. They need to be raised to come out with a higher spark value then other spark sources.

 

[tdstuart]

AuF# in that sheet seems to be different from in your tune file.
Its the three I have checked. They need to be raised to come out with a higher spark value then other spark sources.

I have it going to commanded good and chopping good but I’m having weird issues where when I go from drive to idle the rpm flares to about 1400 then dips down and sometimes gets in a cycle of rpm dips then spikes and it never will hold rpm and chop when it gets in that cycle

 

[K4fxd]

If you can find one look at a track key Boss 302 tune. I can't find one with the choppy idle. But they do show a change in the o2 sensors to account for the unburnt fuel.

If you find a real track key tune pass it along please.

 

[tdstuart]

If you can find one look at a track key Boss 302 tune. I can't find one with the choppy idle. But they do show a change in the o2 sensors to account for the unburnt fuel.

If you find a real track key tune pass it along please.

I tired messing with the PI controller thing for the o2 but doesn’t seem to be doing much.

 

[tdstuart]

Here is a log with the idle issues. Once I take it on a short drive it starts acting up and then when you put it in park it wont idle right.

 

[engineermike]

@tdstuart the fact that you changed the location of a mapped point tells me you don’t really understand how they work. You’ve invalidated 100% of the calibration for those two mapped points. This means torque, spark, and map will be incorrect any time those mapped points are used. Depending on imrc setup, this could even affect wot.

 

[K4fxd]

@engineermike

Have you got a track key tune with the idle changed for chop? All the tunes I found have no changes for idle between track key and non track key.

 

[tdstuart]

@tdstuart the fact that you changed the location of a mapped point tells me you don’t really understand how they work. You’ve invalidated 100% of the calibration for those two mapped points. This means torque, spark, and map will be incorrect any time those mapped points are used. Depending on imrc setup, this could even affect wot.

I tried what you suggested and set the vct commanded to an existing mapped point and the car barely idled.

Its setup to map point 0 with imrc closed so it will never affect wot and probably won't ever be used except when at idle.

I understand that the torque spark and map will be incorrect. But the car idles better being set to mapped point 0 with different cam positions than a mapped point that has high overlap.

 

[markmurfie]

@engineermike

Have you got a track key tune with the idle changed for chop? All the tunes I found have no changes for idle between track key and non track key.

Theres lots of changes for the idle using red key.

 

[K4fxd]

@markmurfie
Does it show any changes to the cams?

 

[markmurfie]

@markmurfie
Does it show any changes to the cams?

To the mapped points no, but tons to the power index arrays of emissions reduction and best fuel economy and the distance tables for those.

Unfortunately its like comparing a gen 1 coyote to a gen 2, and unless you are experienced with both, their differences could be even more confusing than helpful.

 

[tdstuart]

Looks like when the car goes into dashpot mode it really struggles idling. Should I try disabling dashpot mode in idle or is there a way I can adjust dashpot to idle better?

Sponsored