EFIDynoTuning Forum

Not quite sure about how to adapt the fueling writeup to tunerpro, since the SP integral to the definition file. The default values from my ECU for AP** AHISL and SP** Global Fuel K-Constant give a DO NOT CHANGE - Scaling Percentage of 13.3171, but according to the writeup it should be closer to 19#/30?

So to modify the bin with the TFS injector values (HS=38.557, BPT=0.00001284, LS=38.557, SP:38.557/30 = 1.2853), I would:
1. set SP** Global Fuel K-Constant = 30
2. set SP** (WARNING) AHISL - Injector High Slope = 38.557 ? Or scale by SP to 30? Not sure as this param used to calculate the Scaling Percentage param.

3. set SP** ALOSL - Injector Low Slope to 38.557 scaled by SP = 30?
4. set SP** FUEL_BRKPT - Injector Breakpoint (2 of 2) to 0.00001284 scaled by SP = 9.6e-6?

And then would I need to rescale the remaining tables/params (maf curves, SARCHG, etc), or would tunerpro do that for me with this xdf?

I have TFS-89036 installed and set at 45PSI. I'm following the fueling page in the guide, I've attached a screenshot of the values read from the ECU before modification. Do the AHISL (255.996 lbs/hr) and ALOSL (286.184 lbs/hr) values make sense, or is there a possible mismatch between the adx/xdf and my ecu?

Also, just to confirm, SP**Global Fuel K-Constant is the value to set to 30, as per the guide?

I'm all set up and reading real time data, thanks again for the help. I can now confirm that the ECU does not command more than about 12deg SAFTOT at 2-3k RPM, and hangs around 4-5deg at 1500 RPM. I've attached two screenshots of the dashboard, one at idle and one at 22k rpm. Both tests conducted in park, engine warm. Does anything stand out?

One potential issue, HEGO values stay pegged near 0V regardless of RPM/throttle position/throttle movement, even when my wideband (not hooked to ECU) reads 12 or less. That would potentially cause ECU to pull timing, right? HEGO signal is good at wire, going to verify that it's on the right ECU pin shortly.

Great, thanks for the help. I've been using Binary Editor for logging, as I did not find the ADX file for VEX1. Is one available? Not sure about whether I can just dump all of the tables in the VEX1.xls file into one big CSV and import?

Alternatively, is it possible to apply the logging patch in Binary Editor? Didn't see it in the docs.

sorry, I may not have had the ignition on when I tried reading. Had better luck with tunerpro, please see attached. It looks like at least some of the mappings in VEX1 are correct for this binary, would appreciate if someone more knowledgeable could confirm. Trouble is during real time logging most of the values make sense (e.g. TPS, spark advance) but a few of them don't (e.g. RPM pegged at ~12k).

ah, I see the continuous fuel pump running is addressed in getting started, will try cleaning J3 contacts again.

not seeing any values while attempting datalogging either, not even garbage, and the status lights are green in binary editor.

Thanks for the help. Attached is my attempted read of the calibration.

Something's weird though, with the quarterhorse plugged in the CEL is on and idle oscillates around 500 RPM. With key on engine off fuel pump runs continuously and I can't get the self test to run or error codes displayed...

If your using VEX1 def, you must use VEX1.bin. It is possible DEX0.bin will need a different definition.

Can you dump a bin from an ECU with a quarterhorse if you have the correct def? Or at least get real time ECU values without the corresponding bin on your laptop?

After some fortuitous googling, looks like VEX1 has the same hardware code...do hardware codes map 1:1 with strategies? I.E. can I use the VEX1 def to probe/tune this ECU?