Injector data & scaling for HP Tuners

Modern Ford and GM injectors aren't linear. At low pulse widths the injector hasn't fully opened, so it flows less than its rated rate; once it's fully open it flows on a clean, predictable slope. HP Tuners VCM Editor models this with two numbers — a High Slope and a Low Slope — plus a Breakpoint that tells the PCM where to switch from one to the other. Slope is expressed in mass per unit time (lb/hr or g/s depending on the OS), and getting both slopes from your injector vendor's data sheet matters far more than just punching in a single "60 lb/hr" figure.

The Breakpoint is the pulse width below which the low-slope (non-linear) behavior dominates. If your vendor publishes a characterization done on a specific fuel and pressure, that breakpoint is only valid at that pressure. Run a return-style regulator at a different base pressure, or a returnless system that bleeds pressure under load, and your real breakpoint moves. TuneVault flags when your slopes and breakpoint look like they came from three different data sheets stitched together — a classic copy-paste-from-a-forum signature.

An injector takes time to physically open after the PCM commands it, and that dead time grows as battery voltage drops. The injector Offset (a.k.a. dead time or latency) table in VCM Editor is indexed by voltage — typically a row per volt from roughly 6V to 16V. Each cell is the extra time the PCM must add to the commanded pulse width so the injector actually delivers the intended fuel.

Here is where people blow up their tune: most injector data sheets publish offset in milliseconds (e.g., 0.95 ms at 13.5V), but several HP Tuners operating systems store this value in SECONDS. Typing 0.95 instead of 0.00095 inflates dead time by a factor of a thousand, and the car will run obscenely rich at idle and refuse to control fuel. TuneVault explicitly checks the magnitude of your offset cells against the voltage axis: values clustered near 0.0006–0.0015 are sane for seconds-based tables, while values near 0.6–1.5 mean you fed milliseconds into a seconds field. We never flash for you — we just stop you from making the one mistake that the data sheet practically guarantees.

Reputable injector makers characterize their injectors on a flow bench across pressures and voltages, and they publish that data so you don't have to reverse-engineer it. DeatschWerks ships HP Tuners-format data with their DW injectors; Injector Dynamics publishes full slope/breakpoint/offset tables (ID's data is famously thorough and is given for a stated fuel and pressure); and many OEM-style Bosch injectors have community-characterized data. Always use data matched to YOUR fuel pressure and YOUR fuel — ID's gasoline data is not valid on E85, and a returnless platform behaves differently from the bench's fixed-pressure rig.

TuneVault checks that the data you entered is internally consistent (slopes, breakpoint, and offset all plausibly from the same characterization) and reminds you that injector data gets you in the ballpark — it does not replace verifying delivered AFR with a wideband. No published data sheet knows your exact rail pressure under load.

On some GM operating systems you'll see an IsX or InjFlowRate-style master scalar alongside the slope tables. That single number scales overall injector flow and interacts with the slope/offset model; changing it without re-deriving the rest leaves you with trims that look fine at one load and garbage at another. The cleaner path is to enter the full characterization (both slopes, breakpoint, offset-vs-voltage) rather than fudging a single flow scalar to mask an error.

If your short-term and long-term fuel trims are stuck rich or lean across the whole map by a roughly constant percentage, that's a flow-rate (slope) problem. If the error only shows up at idle and low pulse widths, suspect the low slope, breakpoint, or offset instead. TuneVault uses that exact symptom split to tell you which table to look at first.

Once injector data is in, the proof is in VCM Scanner. Log short-term and long-term fuel trims, commanded vs wideband AFR, and battery voltage, then drive through idle, cruise, and a few light pulls. Healthy injector data drives trims toward single digits and keeps delivered AFR tracking the command as voltage swings.

TuneVault reads those Scanner channels from your screenshot and tells you whether the remaining error is an injector-data issue or actually a MAF/airflow issue downstream — because correcting the wrong table is how people spend a weekend going in circles. Always confirm with a wideband before adding any boost or timing.