Hi lads,
What's the wisdom on AUI diagnostics? My searching has revealed little useful information on actually pulling codes from an AUI.
Obviously there's an OBD-II port, but various sources say it's non-standard pins, non-standard protocol, and others say it's an EF/EL style "flashing codes" arrangement just reterminated in a different socket.

What is the actual truth here?
Can the old "STI/STO" method be used, and if so, what's the pinout?
Is a digital reader/scanner required? If so, which ones support the AUI?

I bet I'm not the only one with this question...

The XF and Eseries use the Ford OBD1 STO/STI signalling method (a meter or lamp can be used).
The AU uses a data link which needs a PC, or processing device, to communicate (i.e. is not STO/STI).
The AU uses the OBD2 connector but the communication is not OBD2 compliant.
The BA/BF/FG also use the OBD2 connector but the protocol is OBD2 compliant... less so with the BA and more so with the FG.... so many of the after market readers will work to varying degrees (e.g. the ELM devices).

Hope that helps.

Thanks muzza, how'd I know the resident diags man would come up with the goods

Any reports of working setups for an AU series I ?

I thought the AU setup is ODB2 compliant, it just uses PWM instead of CAN?

Yes uses PWM but a proprietary Ford protocol....is similar to OBD2 but different structure.
We have been working on a Diag Tool for the AU.
The basic software is now working.
Is an interface to USB and needs a PC/laptop to operate.
Will also have the ISO bus connection to ABS, Airbag etc (that still to be tested).
Should be ready to go within a few months.

Been playing around with the AU ECU's as of late. Trying to get on the PWM bus.

What I have discovered is the AU wont reply to functional addressing, you need to use physical addressing.

I don't have an ELM but my own built hardware but ELM should be the same. Change the Functional address header byte on the ELM to 10 ( ECU Physical Address ) and the ECU will at least respond to you.

Im not sure what PIDS are supported and such, Im more interested in the flash programming capabilities so haven't explored diagnostics.

As the header needs changing, elm software wont work, you will need to use AT commands to discover anything.

Have not looked at flashing...only diags and testing.
So far the functions operational are:-
Read/Clear all PIDs
Live sensor data
KOEO and KOER tests
I'll post full description and some screenshots once it is closer to being able to be supplied.
As I said, it will be a few months hence.

Had a bit more of a play, to get codes for an AU with an elm, fire up hyperteminal and enter the following where the prompt is >

// Set the protocol for J1850 PWM
>atsp1
OK

// Set the header for Physical address 10 and Type 1 IFR
>ATSH E4 10 F1
OK

// Request diagnostic codes, this is the same as j1979 functional addressed mode 03 except directed at the ecu
>13
53 01 08 01 13 01 18
53 01 22 02 01 02 02
53 02 03 02 04 02 05
53 02 06 04 43 04 80
53 04 81 05 33 07 08
53 07 13 07 43 07 53
53 07 58 07 63 07 68
53 07 78 11 82 13 49
53 14 34 14 37 14 65
53 15 20 00 00 00 00

This ECU was on the bench so lots of codes, from the response I get codes

108, 113, 118, 122, 201, 202 and so on...


// Next send mode 14 to Clear the codes
>14
54

Thats all I have for now.

sorry to hijack here guys, but from what i've read above, you're saying ALL e-series (ie EL) use ODB-1?
is the ECU ODB-1 compliant?

Yes, all ECUs from XF to EL use the Ford OBD1.

Hey guys i got a conecting lead form china but guess i need to change around the way it connects to my AU2 ford..pitty that they didnt comply with world standards make life so much easyer ...
would be realy interesting to know exactly what can be changed and ajusted buy reprogramming

anyone tried the Autel US703 on a AU falco? I've heard there working on BA's +
this one says it does AU
http://cgi.ebay.com.au/MaxiDiag-US703-G ... 0396645333

edit
confirmed with him 20 people have bought this for AU but will not show the 'Live data'
He say AUs don't have this feature (only BA+), but I remember someone saying the ford WGS/new star scanner can??

If this is able to stream live sensor data and integrate WB02 output to build AFR maps, I'll be very interested.

Hi muzza,

I realise that this was posted about 6 years ago but were you able to make this work?

I have an AU1 Fairmont (built October '98) and I'm looking for a scantool. Do you have something available?

Thanks.

Hello, answer is yes and no.
It did get progressed up to a point, but the guy who did the interface lost interest.
So development halted.
I have been using the development system myself on my and other cars.
But, I like to play with stuff, so subsequently, in playing around with various interfaces and software I did find an "off the shelf" solution.
The only issue I had with the development version as well as with the solution described below is that it would not connect to the BEM nor could we access the Adaptation Tables.
Looks like Ford Aust placed these it a non standard locations.

The "Off the Shelf" solution.....

1. Get yourself one of these:-



They sell for $10 to $75 on eBay or AliExpress.
When you receive it, if it comes with a disk of software, don't use any of that except perhaps the USB driver files.
There are Bluetooth versions as well. Those would be OK (but I prefer the cable type with a PC).
Do not use any other type other than the one pictured (it has the physical interface types required for the AU).

2. Google "Forscan" and go to the site (http://www.forscan.org).
It is free software and developed to work with Fords, including the protocol used in the AU, and the ELM327.
Download the software and install it.
Note that I have only used it on a laptop(PC) and have not tried the Android or iPhone versions.

Note that the protocol used in the AU was used in other parts of the Ford world from around 1995.
It is a variant which closely resembles OBD2 but is not pure OBD2... hence standard OBD2 readers cannot read the AU.
Forscan was developed to read this protocol as well as OBD2.