Looking for something like this for the id1700x they only give out info for the 32bit ecu _-
Injector Dynamics took away the graphs from their site, but they added something even better... Plug and play data for various ECU tuning software in Excel Spreadsheet form! Crazy awesome.
Of course nothing we use on a regular basis is listed, but the GM_EFI data has 60+ data points to describe the low pulse width characteristics of each injector. I modeled the data for ID1000 / ID1300 / ID2000 and what the values would translate to for 32bit and Carberry ROMs, using some of Jason's data from the ID1000 to fabricate / guess at / make engineering assumptions of data at voltages other than 14v.
These values are just theoretical at this point, I haven't tried them in a ROM. Note that the ID plug and play values use a small pulse threshold of 3.0 for ID1000 and 1300 and 3.25ms for ID2000. These are considerably larger than I've seen for other setups.
Incoming picture-bomb of the Excel sheets after I worked on them to translate them to our ROMsFirst we have the GM_EFI_Live data ID provided for the ID1000, ID1300 and ID2000:
Looks like ID1300s use a little different strategy than the 1000/2000 with overdriving then settling from the negative direction.
Even though the % delta at most pulse widths is lower for the ID1300 and 2000 than the 1000, I put my idle data in the screen cap to demonstrate that the flow scaling of the larger injectors means they're still seeing significantly larger errors (especially the enormous 2000s, obviously.)
Next low pulse data on ID1000s:
ID1300s:
And Finally ID2000s:
I will try out the ID1000 corrections when I get around to porting my CarBerry map to the version that has pulse width compensation. Hope this is helpful for others.
I suddenly want to try to dial in ID2000s on my car. Not that I really need them (I do need about 100cc bigger than ID1000s.) I just want to try it out.
The next question is how do we get other MFRs to provide this data... or where do we send other MFR injectors to get this kind of detailed data for a reasonable cost? I think it'd be adequate to have about half the data points ID provides (about every .1ms step size). As long as the equipment is repeatable enough.
Presumably latency will need to change when we adjust these low pulse width tables, as they are probably slightly higher than normal in order to work as a sort of rudimentary low pulse width correction.
Take my car as an example... Logged idle is average of 1.02 latency and my 14v table value is 1.03. Subtracting from total pulse width, I get 1.16 pulse width with no compensation. If I add the ID1000 low pulse width correction, I will add 2% pulse width, or about 0.025ms. I need to decrease latency by about that much to get the same total pulse width if my idle trim is zero (it's slightly positive, so I need to take out slightly more than that).
