Injector Latency Algorithm change
#1
Injector Latency Algorithm change
Originally Posted by Hunt for Red October
Captain, radio. We're receiving flash traffic on the V.L.F. emergency circuit.
So while tuning up some ID2000's I have made a startling discovery.
In previous Evo's (CT9A) the injector latency raw value was multiplied by 0x18 (or 24) to get it into "microseconds".
So in your scaling for "InjectorLatency" you will see x/0.024 (which is really 24/1000, we divide by 1000 to get microseconds into milliseconds)
HOWEVER, and this is the cool/ghey bit, for CZ4A the wizards at Mitsubishi decided to use 0xF (or 15) as the multiplier.
So here we are still using 0x18.. So all of our latencies are being DISPLAYED incorrectly.
Now as long as when you tune you use the tried+true method of "trim watching" then your fine.
But hasn't it always IRKED you that the manufacturer latencies didn't match what you were putting into the table?
So to fix this SNAFU simply open up your evo10base.xml and replace
Code:
<scaling name="InjectorLatency" units="ms" toexpr="x*0.024" frexpr="x/0.024" format="%.3f" min="0" max="4" inc="0.024" storagetype="uint8" endian="big"/>
Code:
<scaling name="InjectorLatency" units="ms" toexpr="x*0.015" frexpr="x/0.015" format="%.3f" min="0" max="4" inc="0.015" storagetype="uint8" endian="big"/>
BTW - The ID2000's that I am tuning now actually match the 14V latency as specified by the manufacturer - chance or co-incidence?
Cheers
D.
Last edited by tephra; Aug 19, 2010 at 12:11 AM.
#7
Evolved Member
iTrader: (6)
Join Date: Mar 2003
Location: Deeetroit
Posts: 1,020
Likes: 0
Received 0 Likes
on
0 Posts
Sweet! I was wondering why the latencies were a bit off on the DW1000's compared to the spec sheet! Will implement these changes when I switch out to the big MAF housing! Thank you!!!
Trending Topics
#9
Evolved Member
iTrader: (1)
Join Date: Nov 2009
Location: Omaha, NE
Posts: 1,456
Likes: 0
Received 0 Likes
on
0 Posts
I converted my definitions. But now I will be off from Cobb AP stuff. I'll probably have to have them both (old and new).
Mine looks closer now too. Data sheet says 1.000 for 14v. I have .915 for 14.12 v. And the old way was 1.464 for the 14.12 v. A lot closer.
This also explains why 8/9's had such different scalers for the exact same injectors.
Mine looks closer now too. Data sheet says 1.000 for 14v. I have .915 for 14.12 v. And the old way was 1.464 for the 14.12 v. A lot closer.
This also explains why 8/9's had such different scalers for the exact same injectors.
#11
Evolved Member
iTrader: (1)
Join Date: Nov 2009
Location: Omaha, NE
Posts: 1,456
Likes: 0
Received 0 Likes
on
0 Posts
Yeah, just like the scaler changes for Airflow. I have an old set and a new set for copy and paste.
I really should make a Cobb Load Scaler so that I can just copy and paste over the target boost load tables. It would make it easier than having to subtract 32 from them. I still don't understand why they add 32 to all those tables and the Load Values.
I really should make a Cobb Load Scaler so that I can just copy and paste over the target boost load tables. It would make it easier than having to subtract 32 from them. I still don't understand why they add 32 to all those tables and the Load Values.
#14
Evolved Member
iTrader: (1)
Join Date: Aug 2009
Location: Saint Paul
Posts: 1,468
Likes: 0
Received 0 Likes
on
0 Posts
It wasn't that long ago that there were no options between 1k and 2k. I have a set of the ID2000's waiting to go back in on the 31st (we couldn't get them to work well enough a few months ago). These findings are very timely. I didn't want to get stuck with $900 paper weights.
#15
EvoM Community Team
iTrader: (15)
If anyone wants to keep their original and just add this as a new item, you can add this XML to your _mods file for 52680015:
Code:
<scaling name="InjectorLatency_NEW" units="ms" toexpr="x*0.015" frexpr="x/0.015" format="%.3f" min="0" max="4" inc="0.015" storagetype="uint8" endian="big"/> <table name="Injector Battery Voltage Latency Compensation NEW" category="Fuel" type="2D" scaling="InjectorLatency_NEW" address="556cc"> <table name="Battery Voltage" type="Y Axis" elements="7" scaling="BatteryVoltage" address="6512e"/> </table>