Thank you for your detailed answer muzza.

I've seen those scantools on eBay but avoided them because I couldn't find anyone who could assure me that they would actually work with a series 1 AU.

I'll buy one and give it a shot. Even if it only talks to the ECU - that's a start.

btw: hadn't thought of the BEM until you mentioned it (I considered that my car might be too old for external BEM access). Is it actually possible to plug in a device to communicate with the BEM? What sort of information or control can then be done? I'm guessing door-locks, boot-release, etc...?

The AU, just like the Eseries has a BEM. And yes, it does much the same as in the EF/EL.

In Eseries only the modules - ECU, Airbag controller, ABS system and transmission ECU(V8) are brought out separately to the diag connector and each runs OBD1 (except ABS/Airbag in late 1997 EL).
In the AU every module except Radio (ECU, BEM, Airbag controller, ABS system, Instrument cluster, Climate Unit, etc) are connected via a "LAN" and able to be accessed via the OBD2 style connector.
All of the modules have a standard address (globally definited by Ford) within the protocol and Forscan can get to these except for the BEM. Ford Australia have done something different there (and with the Adaptation Tables) and Forscan cannot see it.

The info available is mainly PIDs (Problem Identifiers).
One could, in theory, access such things such as the :-
Odometer display in the cluster,
Smartshield keys within the BEM and ECU, etc
however, these are protected both by hidden access and by passwords.

The same interface scheme is used to "flash" the ECU and the flash unit makers have worked out the access arrangement (Odo and Smartshield are much more securely hidden).

Note that AU1 uses an "old" Ford developed physical interface and the AU2/3 used both that and the newer universal CANbus interface. BA onwards use CANbus.
That OBD2 ELM327 unit I nominated has the both interfaces implemented.

I have been using one of the blue USB Vgate scan/ obd scan tools haven't seemed to have any trouble with it and have scanned a au recently with Forscan, works well on AU/BA/BF.


Forscan Rocks. gets better with every relese and update which happens frequently.
Worth Noting that Forscan can do a PATS reset and match ECU/PCM to the BCM. as with ford doing it you need 2 keys (and a minimum of 1 already coded to the BCM to get you started)

I successfully changed my BCM yesterday in my BA from the LOW series blue module to the HI-series green one, all in all took me about 20 mins with the 12min wait for the timed security access.

Rob

awesome Rob .... i have a AU1/AU2 & a BA with my other half having a BF, so hopefully will be able to put this to good use on all

Rob, excellent update.
I have not looked at the new releases of Foscan for some time.
Good to hear that one can do the PATS reset with the current version of Forscan.
Have not needed to do that to date, but handy to know.

I will try the latest Forscan in relation to the BEM and Adaptation Tables.
Inability to view the Adaptation Tables, in particular, is annoying.
I would be surprised if it works, but fingers crossed.
Could always send an AU ECU to one of the Forscan development team and ask for them to investigate.

In relation to other units...
As long as they can do SAE J1850 PWM (AU1/2/3) plus ISO 15765-4 CAN (AU2/3, BA, BF,FG) then it should work OK.



Good stuff....

Still no go on getting the DTC's out of the AU BCM coumes up with unable to read or something from memory.
also to do PATS requires the extended licence which you can get a 2 month trial FREE when that 2 months is up you can get another trial for 2 months free haha!

I was hoping forscan would also code in the new ICC i have but it didnt its somkething they will have to add to there list of things to do

mines not working with forscan

Mad2, I assume you have Ignition On when you connect to the ECU ?
Otherwise, uncertain as to why it would not work.
Have used it on a bunch of AUs.

yeah i'm not sure either?? any way it was saying not connected. so not sure if my problem or software problem...

Hi muzza, a quick follow-up...

I received my $9.47 ELM327 from a seller on eBay about a week ago, downloaded a copy of Forscan and installed it on my laptop. Connected it up to the AU and it all works very well.

I was quite amazed at the quantity of information available. There are lots of sensors in the Fairmont. I played with it all last weekend, seeing what the different things do.

Checked for DTCs and only found 2 for the ECU. One of them I already knew about. The second one was a surprise (knock-sensor wiring). Cleaned the electrical connector on the knock-sensor (it needed it!), checked resistance on the sensor, cleared the DTC and I've been running the engine now for the last week without issue. It runs almost perfectly! Gear-shifts are occurring at different times, and the engine seems to have more power now and is not running rich like it was before. Outside of the exhaust tip is still clean after a week and not covered in black stuff. So, I guess the engine was knocking, but I couldn't hear it. Might have been a quiet knock....

For a car with 247,000km on it, I'm very happy.

Thanks muzza.

(now just need to fix that unsteady idle...)

Excellent to hear it worked.

Just be careful with the idle.
I have not recently surfed through this forum on the issue so the info may be here somewhere..
I know part of the AU idle info is here... but I'll cover it of quickly anyway....

In the XF-EL the ECU expects the engine to idle of its own accord (i.e. the throttle body plate is adjusted for base idle with the idle controller disconnected).
The Idle controller is used only to raise idle when the engine is cold, when the aircon is used (in I6 only) and in some instances when the engine is running.

In the AU, the idle is fully controlled by the idle controller.
The throttle body plate is adjusted just a smidgen off closed just to prevent binding.
The ECU must be "trained" to control idle correctly.
One of the guys here did outline the procedure so have a search.
Not sure of the history of you car, but it may be worthwhile performing the training procedure first.
Hopefully, no one has twiddled the throttle plate screw.

I did have an idle issue with my AU V8 and I did need to replace the idle controller.
One needs to run through the idle retraining procedure when the controller is replaced.
It was a few years ago, but I bought a genuine Motorcraft controller out of the US for around $90 incl postage ($500 from Ford Aust and $350 from Bursons).
I also replaced the PCV valve as those do not last forever and also affect idle.

Hope that helps....

Hi muzza. As the new problem I'm having is off-topic here, I've created a new post here, instead.

Thank you.

Thanks heaps for this advice, Muzza and all who contributed.
It's going to be wicked talking to the cars computer.

I bought a V1.5 on eBay for AU$10 from here:
http://www.ebay.com.au/itm/like/2218655 ... ue&viphx=1

Just thought I would add my 2 cents worth. My Jan 2000 AU XR8 came with no keys, zip zero nuthin'. A J3 was programmed to disable Smartshield and up to now I have been dealing with it.

As of today I now have 2 keys reprogrammed and a Jan 2000 Fairmont Ghia BEM in the car all thanks to the latest Forscan and PATS programming. Starts perfectly without the J3 and I was even able to program a Smartlock remote for the first time. This saved me $148.00 from NOT taking to a local Ford dealer for key programming although it did cost be about $45.00 for 2 new keys with transponders and a new USB ELM327 unit.

Still, I am so chuffed it worked out, gotta love the new Forscan!

Cheers
RD

Last edited by racedirector on Wed Mar 09, 2016 9:18 pm, edited 1 time in total.

BTW: is anyone else receiving junk emails to the email address you provided to this forum?

I created an email address specifically for this forum (as I do for all online forums): this address is now being spammed (fake PayPal alerts, etc...)

Contacted fordmods site admin - no response.

Any thoughts on how my email address ended up in the hands of spammers???