Results 1 to 5 of 5

Thread: Ford Focus TDci

  1. #1
    Potential Tuner
    Join Date
    Oct 2003
    Location
    Posts
    1

    Ford Focus TDci

    Hello,

    I have a Ford Focus European 2000 with a 1.8 TDci engine.
    I tried to build a PWM Interface to communicate with the ECU.
    The interface is built around a ELM320 and I'm able to log the network traffic, but the ECU doesn't answer any of my requests.
    My question is: I sthe ECU compliant to the ODB II standard?
    Or is there a different protocol?

    Regards
    Willhunt

  2. #2
    Tuner in Training jfunk's Avatar
    Join Date
    Apr 2003
    Location
    San Diego
    Posts
    46

    Re: Ford Focus TDci

    Are you requesting Legislated Diagnostics(6A) or Enhanced Diagnostic Test Modes? If your using the default header on the ELM320 of 61 6A F1 then sending a mode $01 (legislated diagnostics) request should get a response. I have a 2000 focus ECU that I was talking to and most of the modes $01-09 would respond using the default header. To get my ECU to respond to enhanced diagnostic test modes I changed the header to A4 10 F1.

    Mode $22 request of PID #1172 (Vechicle power voltage)
    >221172
    62 11 72 C5 <- 12 point something volts

    >221172
    62 11 72 94

    >221172
    62 11 72 B2

    I varied the input voltage to the ECU(it's not in a car) and could see the values changing. A hex value of C0=12.0v
    2000 Ford Focus SE

  3. #3
    Potential Tuner
    Join Date
    May 2011
    Posts
    2

    FORD Ranger enhanced PID

    Hi jfunk,

    there are 2 thinks I want to know from the OBD2 interface (scantool with elm327 chip)
    • Vehicle speed (standard PID: mode 01 D1)
    • if the vehicle is in reverse (enhanced PID: mode22 1697)


    We successfully request and receive the speed. But when requesting the 1697 (reverse switch on/off) or even the 11B3 (gear) we receive a "NO DATA" response.

    I have tried to set the "header" to ATSH C410F1 before requesting the enhanced PID, but no luck. Also ATSH c41033...

    I think my answer is WHAT the header should be. Have done fruitless research... Now my humble request for help here.

    Thank you in advance,
    Rudilof

  4. #4
    Potential Tuner
    Join Date
    May 2012
    Posts
    1
    Quote Originally Posted by Willhunt View Post
    Hello,

    I have a Ford Focus European 2000 with a 1.8 TDci engine.
    I tried to build a PWM Interface to communicate with the ECU.
    The interface is built around a ELM320 and I'm able to log the network traffic, but the ECU doesn't answer any of my requests.
    My question is: I sthe ECU compliant to the ODB II standard?
    Or is there a different protocol?

    I did not have success on Visteon-made TDDi or TDCi EEC-V modules with any OBD-2 tool (ELM-32x or handheld tools from China).

    The only tool that worked for me was FoCOM. And Ford IDS (which is a lot more expensive).

    These control units are a bit different compared to petrol EEC-V's.

  5. #5
    Quote Originally Posted by Willhunt View Post
    Hello,

    I have a Ford Focus European 2000 with a 1.8 TDci engine.
    I tried to build a PWM Interface to communicate with the ECU.
    The interface is built around a ELM320 and I'm able to log the network traffic, but the ECU doesn't answer any of my requests.
    My question is: I sthe ECU compliant to the ODB II standard?
    Or is there a different protocol?

    Regards
    Willhunt

    you can have OBDII standard but also check on some recalls, There are also recalls for power train on other ford models. You can see the latest Ford TSB and other models of ford.

Similar Threads

  1. HP Tuners VCM Suite v2.2.0 is Now Available!
    By Chris@HPTuners in forum VCM Scanner
    Replies: 54
    Last Post: 12-24-2007, 09:23 AM
  2. Ford Eec-v & Eec-vi
    By 2nr in forum Ford Tuning - Engine, Gas (Non Ecoboost, US)
    Replies: 1
    Last Post: 09-13-2007, 08:48 PM
  3. Any idea when HPT will support Ford or Dodge cars?
    By muncie21 in forum VCM Suite Product Info
    Replies: 22
    Last Post: 09-03-2006, 04:13 PM