EFIDynoTuning Forum

big_bertha wrote: ↑2022 Mar 02, 17:29 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...

Bin file is corrupt, from what I can tell.

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).

Well, good news, your bin is fine, and is correct in that the mappings are same as WAY1 & VEX1, as far as I can tell.
AHAC2 should work for you.

Your bin does not have the data logging patch enabled. Did you patch the bin, then upload back to QH?

yes thats correct. DIX0 is a native AHAC2 calibration same as WAY1 VEX1 VEX2 TIP1 HOG0 HOG1 etc...

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.

your all mixed up

its not vex1 its ahac2, its in the downloads.

logging patch is for tunerpro. be handles it differently.

viewtopic.php?t=63

Unless something has changed, you cant use binary editor with Decipha's tunes. You must use TunerPro RT.

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.

the hego voltage may not be logging you can verify by lambses ramping up and down in closed loop

fuel write up has specifics