EEC-V AST1

[Dale Cooper]

Hi,

New to the forum and this kind of ECU work however I'm quite versed with a few stand alone systems.

I have a bit of a project on the go at the moment to adapt a pair of Ford EEC-V (Visteon) ECU's for a V12 Aston Martin (they run 2 ECU's per car, one for each engine bank) for use on an engine dyno. The main focus is to disable/remove the need for the PATS system and the engine out of the car in a test cell.

At present I have downloaded, via the ODB port and KESS v2 the ECU data file and viewed it in both HxD and TunerPro, trying the CDAN4.XDF file allows me to view elements but looking at the raggedness of the tables and 3D graphs I'd say it's not the correct one for me.

So my question is....

Is it feasible to have and .XDF file that will show the portion I'm looking to change and has anyone got any leads I could follow to help out?

[dex]

Do both banks use the same ECU and, if so, are the binaries identical?

The one AST1 binary I have shows the strategy as being R27EC or R27EC0 and I haven't seen an xdf for that.

[Dale Cooper]

Hi Dex

The ECU's operate interdependently, even though it's a V12 the only thing shared is the crankshaft! pretty much every sensor is doubled up.

The ECU I've downloaded has -

HW: 123968
SW: R27EV02M.HEX
VIN nr.: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
SW ver.:
Spare:
Engine:
HW Ver.:
SW upg.:
Installation: ECC-V 216K

when I run the ID function on my KESS V2 unit. I've tried to upload the HEX file but it gets knocked back for some reason.

Dale

[dex]

In answer to my question, for each ECU both the hardware and the calibrations are identical. Ford use an input to the ECU to let it know if it's the primary or secondary ECU which then sets a flag that is used to determine which routines do, or do not, get run. e.g. the fans are only controlled by one ECU. A neat way of not having to design and manufacturer an ECU capable of running 12 cylinders.