Data logging error?
Hey guys, when I'm datalogging, in my WOT full boost, my ignition is set at 13.5* but when I datalog, it's reading 17.5*, do I have to compensate and turn my ignition on my map lower till the log reads 13.5*?
I am going to assume you have NepTune? It has the ability to display actual timing with all modifiers applied rather than just table timing. So you are trying to see 13.5° because that is what is on the map table correct?
Sorry I didn't specify, it is on crome pro. When I enable live tuning, it pops up a table on the right with the degrees the car is running at. When I enter the wot full boost ignition cell (which is set at 13.5*), the datalog table reads 17.5*. Which one do I go off of? I set the base ignition on the dizzy to 16*
As OneBadTurboCRV stated, there are corrections and modifiers. I'm guessing this probably happens as the RPMs are increasing? The ignition timing is advanced by the ECU/software to a certain degree to "keep up" with the engine spinning faster. This is normal. You can change the corrections but I would recommend leaving it alone if you're just street tuning it.
For example, my Accord has 20 degrees table timing at 18psi, but if I look at the actual timing in Neptune it will show 24-25 degrees at certain points because of the RPM correction. I'm not familiar with Crome Pro but it sounds like it is showing you the actual timing and not the table timing in the datalogs. If you wanted it to read 13.5 actual, you can either edit the correction or lower table timing to compensate for it. Either way, if you're not detonating or having issues as is I would leave it alone. I don't know the specifics on your setup but neither 13.5 or 17.5 degrees of timing are what I would consider aggressive on the average street car.
For example, my Accord has 20 degrees table timing at 18psi, but if I look at the actual timing in Neptune it will show 24-25 degrees at certain points because of the RPM correction. I'm not familiar with Crome Pro but it sounds like it is showing you the actual timing and not the table timing in the datalogs. If you wanted it to read 13.5 actual, you can either edit the correction or lower table timing to compensate for it. Either way, if you're not detonating or having issues as is I would leave it alone. I don't know the specifics on your setup but neither 13.5 or 17.5 degrees of timing are what I would consider aggressive on the average street car.
Yes its happening as the rpm is increasing. The degrees at the bottom right is reading 17.5* in full boost and my actual ignition map is at 13.5*. My question is do I go off on the degrees at the bottom right or go off of the actual ignition cell map?
Thread
Thread Starter
Forum
Replies
Last Post
RACEPAK
Engine Management and Tuning
2
Oct 30, 2014 06:13 PM





