EECTuning.org

For the sake of moving four more injector wires I think that is preferable to playing around with the injector firing order and injector output port.

What is the engine? I am curious why the injector firing order has been changed.

SMD-333 is used on the '94-'95 5.0 L manual transmission Mustangs.

I am guessing from the lack of response that no one knows. I suspect that Paul's EEC Editor may well be the only software to support that hardware.

'A' is closest; the BE executable was installed rather then the full installer program.

If you are just using the wideband controller's 0-5 volt output as an input into the eec to datalog via an unused A-D line (such as the EGR) then BE does not care what controller you are using.

The calibrations were supplied as binary files to the chip manufacturers, this is described in the ROM identification section of the strategy documents.

One of the options the LA3 ecu uses to determine when to go into open loop fuelling is a simple rpm vs air charge function together with a global air charge multiplier. It probably looks like it always goes into open loop at 3000 rpm because the air charge value at 3000 rpm is less than a sixth of t...

Have a look a couple of lines above, at 0x4456, where a different entry point to the subroutine is used.

I also wonder why Ford didn't simply do a LDW to get both registers in one hit Bits 8-15 of some special function registers are only accessible using a word sized read or write of an even valued memory address. This feature of the MCU looks like it's only used on the 8065 (for example, see the HSO ...

It's not obfuscation, just a neat way of saving 8 state times. I doubt you could automate commenting this out in the disassembly due to its subtlety.

This is just a bit of cute coding by Ford, in this particular instance using SHRDW has saved using SHRW twice (i.e. separately on 0x38 and 0x3A) as the value is 0x38 is not double word sized and the lowermost bits of 0x3A are zero.

Even if the temperature at the sensor is greater than 254 deg F the ACT value is limited in the code to a maximum of 254 deg F.

Providing the first and last input (Y axis) values for the function are set to the maximum and minimum limits of the input variable then there is not going to be a problem as the function's interpolated output value will be limited to be within those values in the function. Problems which occurs in ...

I believe the 4TAB ecu has an 88k rom so I suspect both of the bin files you have are not correct.

I've just issued an updated definition that includes the DFSFLG flag so you will be able to see if DFSO is causing your issue.

Are you sure it's going into DFSO?

Are you allowing the use of the DFSO Profile Correction mode? If you are then the normal DFSO parameters won't disable DFSO if the relevant KAM correction factors have not matured.

OK, from some rummaging around I now think this particular example of OR'ing and XOR'ing with a zero relates to how the BiDi port works at the hardware level. I suspect it's a hangover from programming the port directly rather via a 'image' variable. See the 1985 Intel Microcontroller Handbook secti...

For clarity, it is only with respect to the line at 0x5736 that I meant it was possibly there to waste some state times and not as a rule to be observed for all instances of XOR'ing with a zero.

XORing with a zero doesn't change any bits in the destination register. It's probably done to waste some state times for some reason.

I suspect an error in the code or a bodge to avoid re-compiling the binary because the line at 0x571E is redundant.

The SAFTOT value is the foreground calculated spark advance that is used to generate the Spark Angle Pulse Width (SAPW) value sent to the EDIS module. The ODB-II spark value should track the SAFTOT value very closely as it is derived from the SAFTOT value converted to meet the requirements of the J1...

86GT wrote: ↑

Tue Jun 19, 2018 5:32 pm

Bob is still on a Windows 95 PC

No, I'm not.

No point in checksumming unused areas of ROM and, IIRC, the VID block is excluded.

The multiple bank checksum calculation is the same as single bank checksum with each bank being added in turn. In the BWAK3 strategy the routine is at 0x872D9.

You can only tell by looking at what the various rev limit scalar values are to determine whether a particular rev limiter is used. An example would be if the 'Rev Limit Low Gear Stage 2' (aka NLMTLO_0) parameter was set to a higher rpm than the 'Rev Limit Low Gear Stage 3' (aka NLMTHI_0) parameter ...

The CDAN4 strategy has three ways of limiting the engine speed: Stage 1 - The rpm at which fuel delivery is enriched and spark advance is retarded. Stage 2 - The rpm at which fuel delivery is cut to alternate injectors. Stage 3 - The rpm at which all fuel delivery is cut. Not all the stages are nece...

tvrfan wrote: ↑

Wed Apr 11, 2018 6:04 pm

I haven't entirely worked out what some of the extra chips do either, for example what DUCE stands for

DUty Cycle Expander

Format - I copied the 8096 format, which Ford also use in their handbook. For an easy rule of thumb for reading , I treat the operands as BACKWARDS, like this - - - AD3W, R32, R34, R36 is R36 = R34 + R32 AD3W, op1, op2, op3 is op3 = op2 + op1 In the Intel documentation I have seen this is not their...