I made this post responding to a different topic that I didn't realize was in the ECU Analysis forum, and while it did answer some questions people had in that thread, it probably isn't the right place. So I'm replicating that post here...
-----------------------
Injector Dynamics took away the graphs from their site that Jason used to estimate low pulse width info for the ID1000s, 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. LOTS of data that can be used to model any other software. 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 VERY considerably larger than I've seen for other setups, which seem to turn off corrections around 1.2-1.5 ms.
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 because they're operating at lower pulse widths than 1000s are at idle and cruise conditions.
Next low pulse data on ID1000s:

ID1300s:

And Finally ID2000s:

The primary issue with getting the high pulse width data well fit is that the ROM takes about 0.78% steps in the data. Both the CarBerry and 32-bit ROMs do this. I chose the breakpoints available in the ROMs and moved latencies around to get the best fit I could. I didn't do any math on overall fueling errors, so it probably could be better, but this eyeballs out pretty well with most areas seeing well under 0.5% overall error from the ID data. CarBerry gives enough values to get a VERY good fit. 32-bit has much fewer cells available, so the fit isn't as good, but I think I did pretty well given it has to be modeled with 8 data points.
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.