BE to Decipha Translation?

[Gary Lewis]

Hello, y'all. I'm a newbie and am probably posting in the wrong place. But I'm looking for a translate table from Decipha's terminology to that of Binary Editor. Is there such a thing?

I ask because I find the writeups & explanations here, meaning those from Decipha or the rest of you, to be very helpful. But I'm using BE to tune my '96 EEC-V system in my '85 F250, and I'm finding it hard to determine which parameter is being discussed.

Am I missing something?

[dleach1407]

Go to the main page and click on the eec-v base tunes on the left side. It's listed in there which PIDs you should be modifying.

[Gary Lewis]

Thanks, but that's not quite what I was looking for. From what I can see that does some of the Ford functions, like FN 2200, to what Decipha calls it - Borderline Knock Table. But the folks at Core Tuning called it Spark Borderline Knock Threshold.

That's an easy one as it is obvious. But others aren't as obvious, at least to me. So I've been creating my own translate table so I can use Decipha's good instructions on my BE software. Here's what I have so far, but wondered if someone has done something better:

[dleach1407]

You can usually search the fn number to find it. Thing to keep in mind, Decipha has unlocked more PIDs than what you normally get with a base tune from coretuning. What you find in Deciphas tunes may not be unlocked in other base tunes. SailorBob has more broke out definitions and i would recommend paying 25$ for his base tunes over the free coretuning tunes

[Gary Lewis]

Thanks again, but I'm pretty sure that my tune has all of the PID's that I'm reading about in Decipha's writeup. They just go by a different name, and there's nothing I can find in BE that equates them to a function #. For the most part I've been able to map them to BE-speak, but it is painful. So I don't think I need another tune, although I'm not averse to paying for $25 if that will get me a Rosetta stone to translate between the two.

[wwhite]

What you need, is the Ford Strategy Module documentation.
I had a quick look at the CDAN2 document, and in your example the correct definition for FN2200 is:
"FN2200(N,LOAD) = Base borderline detonation table, degrees."

This is what FORD called it, this is what I call it.

For function FN2220 above, Ford called it:
"FN2220(N,LOAD) = Borderline detonation adjustment for coolant temperature, degrees spark/degree F."

"FN2230(N,LOAD) = Borderline detonation adjustment for air charge temperature, degrees spark/degree F."

"FN2240(N,SPK_LAMBSE) = Borderline detonation adjustment for a change in Air/Fuel ratio"

[Gary Lewis]

That would help. It would probably let me decipher "Decipha". :-) Where could I find that document? Or, are there multiples? If it matters I started with AGANN/YER2. That's for a 1996 California-spec 460 with EEC-V, MAF, SEFI, and manual transmission.

[jsa]

https://github.com/OpenEEC-Project/Strategy-Documents

[decipha]

without being able to search for FN# theres no way to know what the person who wrote your def file will label it as everyone labels things differently

[Gary Lewis]

JSA - Thanks! I'll check it out.

Decipha - Amen, brother! But there are no FN's I can find in the BE stuff. Perhaps I'm missing it, but I doubt it. So I'm stuck trying to translate between your explanations on how calc's are done and theirs so I know what parameters to tweak. Right now I think I'm ok on spark timing, although I would like a bit more. But need to sort out the idle as it doesn't come down to "desired", usually idling around 800 instead of 648. So I plan to work through your guide on that and think I've figured out what is what there.