EFIDynoTuning Forum

The name IPSIBR has changed to DESMAF_PID_N, correct?
In the bin, DESMAF ram location is a different location than IPSIBR, and is a different value.

Why was the name changed?
This has confused me.

correct

name changed cuz its a different payload. Its ipsibr + isc kam correction so gives the total correction

IPSIBR is what logs on the older stuff such as A1C. What address did u have for ipsibr?

For A1C:
- IPSIBR = 0x0396
- DESMAF = 0x0150

Did this ever get resolved? I'm trying to dial in idle on A1C and I can't get the ISCDC, Air Mass, and DESMAF/IPSIBR payloads to behave in a logical manner. I'm wondering if the addresses are pointing to something else....

I don't use A1C any longer.
A quick look, shows only IPSIBR is being logged and is the correct address.
DESMAF is not being logged.

Are you running in open loop?

Closed loop. Fuel control works fine, I just can't get idle figured out. 0 - 45% on ISCDC makes no difference in idle rpm, AM and IPSIBR are all over the place and don't respond logically to changes I make in throttle stop, FN800, FN875, or ITHBMA. It somehow does kinda/sorta control (not great) to whatever I set NUBASE to, but without logical change in ISCDC payload. I've been frustrated with this for months and am at the point of suspecting the addressing for some of these payloads.

Post your bin, I'll have a look.

Attached is my latest bin. I'm using this with A1C_210211 xdf and DECIPHA_210620 adx. If this turns into a big troubleshooting session, I should probably start my own thread. I think the two main things that are causing me trouble are 1) understanding where the AM payload is coming from since this is a speed density strat and obviously doesn't have a MAF, and 2) understanding how idle stability fuel control (which I understand is unique to speed density strats) interacts with the IAC valve position control (ISCDC) and idle air requirement calculations.

There are a lot of changes in your bin. Going to probably need Decipha to verify/validate.

There are so many reasons I chose not to use A1C.
In stock form, the code loads a bunch of parameters from lists, and stops when it hits 0xff.

The DMA logging patch is inserted at 0xBF5C where 0xff should be to stop the parameter lists from loading or to indicate end of lists.
This is an issue for me and could be irrelevant, but since there is code there, the EEC will continue to load parameters into ram. Very bad bug in my opinion.

I do not know it was intentional to insert the logging patch at the same address as the end of list marker.

Well now you're a few levels over my head. I'd like to learn the addressing and programming stuff, but there's only so much time and it's just not something I have time for at this point. On the flip side, I really need to get this truck running and driving and I just can't get idle and dashpot to work right in A1C.

Do you have any suggestions for which hardware/strategy might be a better bet to run a 4.9 six in a '95 F-150? I'm not sure if Efloth's J1X has the same issues as A1C, but is probably the closest. Other than that, are the EEC-IV MAF strategies compatible with batch fire? Adding a MAF wouldn't be too hard but sequential is going to be a pain to convert.

Beyond that, I'm looking hard at the megasquirt options. The code part of that system should be fairly bug free at this point. Just hesitating to start over with a new system.