Chip-Tools

ITDEENBGES

Starting Abrites Diagnostics for Ford/Mazda: vehicle context and ECU scanning ("Scan all")

First thing to do on every Ford or Mazda that comes into the workshop: connect the AVDI, narrow the ECU list down to the right model and run a full scan to see straight away which modules answer and which have a dirty fault memory.

Procedure

1. Connect the AVDI to the vehicle's OBDII port and to the PC, then start "Abrites Diagnostics for Ford/Mazda". On start-up the software looks for the hardware interface by itself and connects; if the connection fails, a window explaining the problem appears (check cable, drivers and power before going any further).
2. Turn the ignition ON and make sure the battery is in good shape: the scan interrogates every module and unstable voltage will drop the communication.
3. Set the vehicle context: by default the main list shows ALL the control units in the database. Select the model you are working on to cut the list down to the units actually fitted to that car.
4. Click the "Scan all" button on the main screen: a progress window opens showing the result of the interrogation module by module. It gives you a quick DTC check across every unit on the vehicle.
5. If you want to change how the scan behaves (which modules are interrogated and how), go to the "Options" tab and change the "Device Scanning" setting, then run "Scan all" again.
6. When it finishes, note which control units answered and which did not: a module that does not answer with the correct vehicle context points to a power supply problem, a CAN network problem, or the module itself being dead.
7. From here you can go into an individual ECU for identification, DTC read/clear, measured values and Special Functions.

Reference screenshots