CZ Installed on N Flash with Major Mods
05-14-2005, 01:49 PM
#27
Registered
iTrader: (1)
Join Date: May 2003
Location: PA
Posts: 3,754
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Nemesis8
Awesome - post your log files from the CANScan or PM me for my e-mail :D
I am still tuning.... As you can tell
I am still tuning.... As you can tell
i'd richen things up between 7500-8000 rpms... looks like the knock sensor may be pulling timing out on you
05-14-2005, 02:19 PM
#28
Originally Posted by pr0ber
i'd richen things up between 7500-8000 rpms... looks like the knock sensor may be pulling timing out on you
05-14-2005, 02:32 PM
#29
Originally Posted by WantedTwo
here ya go buddy. I got a car show to go to today so I got to go scrub on my car :\
How was the car show?
05-14-2005, 06:12 PM
#30
Registered
iTrader: (1)
Join Date: May 2003
Location: PA
Posts: 3,754
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Nemesis8
Yep - thanks. I noticed that also and added fuel there. Should make another log today with the changes. I wish I had help doing this... Dan?? :D
I basically looked at the stock a/f ratio (~12.6) and my old 13.0 a/f ratio map - took the numbers in the cells, devided each by the new a/f ratio - stock a/f ratio for the rpms effected by that cell, then took that number and multiplied it by the wanted a/f ratio - stock a/f ratio (but capped it off at 50 if it was above) and it seemed to work beautifully...
in other words...
k = (emanage fuel #)/(a/f - stock a/f) .... per cell
and the new tune number = k * (wanted a/f - stock a/f)
so basically its just doing some linear interpolation...
Last edited by pr0ber; 05-14-2005 at 06:15 PM.
05-14-2005, 06:20 PM
#31
Originally Posted by pr0ber
in other words...
k = (emanage fuel #)/(a/f - stock a/f) .... per cell
and the new tune number = k * (wanted a/f - stock a/f)
so basically its just doing some linear interpolation...
k = (emanage fuel #)/(a/f - stock a/f) .... per cell
and the new tune number = k * (wanted a/f - stock a/f)
so basically its just doing some linear interpolation...
05-16-2005, 01:17 PM
#36
Originally Posted by Nemesis8
I don't think I did this right... I confused myself :o
OK, I am going to run this tonight on the way home based on interpolation of my stock tune and my last cz tune. I'm tuning for 13.0 on this map. I want to stay safe until I know what I am doing better. When Maurice releases the new ROM chip for me, I will eliminate the red safe plot line. Here it is in case you are curious. I still have the timing zeroed out also. I also attached my stock AFR and my most recent CZ tune in case you are curious... Fingers crossed.
05-16-2005, 06:10 PM
#39
PingMobile
Join Date: Feb 2005
Location: Oakland
Posts: 356
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Nemesis8
Yep - I did after I posted that. Thought the same thing....
You're using the version of CanScan that sees the knock sensor?
What octane fuel are you running?
Thanks!
05-16-2005, 08:15 PM
#40
Originally Posted by Sapphonica
Wow, that's some serious fuel trim you've got at 7000 & 7400 rpm! Especially since the modd'ed intake & exhaust would tend to lean you out a bit anyway.
Originally Posted by Sapphonica
You're using the version of CanScan that sees the knock sensor?
Originally Posted by Sapphonica
What octane fuel are you running?
05-16-2005, 11:43 PM
#43
Consiglieri
Join Date: Feb 2004
Location: yourI'mgirl
Posts: 1,275
Likes: 0
Received 0 Likes
on
0 Posts
Since you are not using the first few columns of your map, I'd re-scale and maximise your resolution. You might be able to tune those spikes then.
BTW, for what its worth, I have had lean areas much worse than that! I started with a map that was around 50% adjustment and had to work my way back to about 15% adjustment max. There was a lot of time spent with really lean areas in my AFR. No damage yet. I wouldn't be concerned about it. Of course, I eventually got it richened out, but it took a while. My point is that I doubt you have done any harm.
BTW, for what its worth, I have had lean areas much worse than that! I started with a map that was around 50% adjustment and had to work my way back to about 15% adjustment max. There was a lot of time spent with really lean areas in my AFR. No damage yet. I wouldn't be concerned about it. Of course, I eventually got it richened out, but it took a while. My point is that I doubt you have done any harm.
Last edited by MadDog; 05-16-2005 at 11:46 PM.
05-17-2005, 11:54 AM
#44
Registered
iTrader: (1)
Join Date: May 2003
Location: PA
Posts: 3,754
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Nemesis8
Well, that didn't work out very well... I'm loading back an older map that I know is safe to use until I can figure this out. Look at those lean spikes! Yikes 
05-17-2005, 12:43 PM
#45
A note from Maurice about this curve:
"Adding .6 to the numbers is not a solution. It is nothing like a linear curve. Although that addition will keep you in the safe zone for the most part. Be careful around 6,600 to 6800rpm. N is a bit lean there from what I have seen so far. Your curve is not bad looking. Perhaps richen up a bit at the top around 7700-8000." CZ
So the .6 is staying until the new ROM chips are released, I think it is a good idea to "stay safe". I'll add more fuel at 7800 RPM and run this again today. Does this mean that all of you out there are tuning too lean because of the original CANScan's problem with reading the O2S1 sensor correctly? Or am I the only one? I'm going to tweak this map leaner until the CZ AFR reaches 13.1.
"Adding .6 to the numbers is not a solution. It is nothing like a linear curve. Although that addition will keep you in the safe zone for the most part. Be careful around 6,600 to 6800rpm. N is a bit lean there from what I have seen so far. Your curve is not bad looking. Perhaps richen up a bit at the top around 7700-8000." CZ
So the .6 is staying until the new ROM chips are released, I think it is a good idea to "stay safe". I'll add more fuel at 7800 RPM and run this again today. Does this mean that all of you out there are tuning too lean because of the original CANScan's problem with reading the O2S1 sensor correctly? Or am I the only one? I'm going to tweak this map leaner until the CZ AFR reaches 13.1.
Last edited by Nemesis8; 05-18-2005 at 08:32 PM.
05-17-2005, 02:44 PM
#46
Consiglieri
Join Date: Feb 2004
Location: yourI'mgirl
Posts: 1,275
Likes: 0
Received 0 Likes
on
0 Posts
Okay. Educate me. We are all saying that 13.1-ish is "safe".... why? Its safe to run stoich at lower RPM, why is is not safe to do so above some magic threshold? We've probably all done it inadvertantly anyway. Is it a long-term concern? Obviously, the engine won't blow doing it occasionally. How is this more stressful than running boost?
05-17-2005, 03:03 PM
#47
I need the education 
Until my CANScan can correctly read the O2 sensor, I'm not really sure where to tune for. Maybe that is another reason why some keep getting inconsistency in their logs. So, in the meantime, I'm shooting for 13.1. When the new chip and software is released, which is real soon, I will tune for more power.
Until my CANScan can correctly read the O2 sensor, I'm not really sure where to tune for. Maybe that is another reason why some keep getting inconsistency in their logs. So, in the meantime, I'm shooting for 13.1. When the new chip and software is released, which is real soon, I will tune for more power.
05-17-2005, 06:43 PM
#48
Registered
iTrader: (1)
Join Date: May 2003
Location: PA
Posts: 3,754
Likes: 0
Received 0 Likes
on
0 Posts
It still looks to me that you are up against the knock sensor - I also have the N flash but have the ecu sending out 30 degrees of advance from 7000 rpms to redline and it looks like yours is bouncing around under 30 degrees.
Then again i could be just completely wrong... the more i think I understand things the more complicated they are :o
< the attachement is from 2 seperate runs >
Then again i could be just completely wrong... the more i think I understand things the more complicated they are :o
< the attachement is from 2 seperate runs >
05-17-2005, 08:55 PM
#50
Timing adjustments made on the CZ unit will not show up on the CanScan...it will only tell you what the PCM is doing. You have to add the CZ value to the stock values to find out true timing advance. The PCM seems to pull timing based on Airflow......thats why the advance curve is not 30deg from about 7K up like on stock. Knock will also pull timing.....have yet to see that though :D