Announcement

Collapse
No announcement yet.

2001 Ford F250 OBDII Problem

Collapse
This topic is closed.
X
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 2001 Ford F250 OBDII Problem

    Hi everyone,

    i new here and i just finish my first CarPc, everything goes 100% the only thing that isn't working is the OBDII port.
    I have a 2001 Ford F250 4.2 180hp v6 intercooler Diesel, i find the OBDII port under the steering wheel and everthing is OK.
    I'm using a ElmScan 5 Compact Scan Tool (ELM327) and OBDWiz, so i pluged the scanner into the OBDII port and the Power led just turn on, ok. Pluged into the PC and turned the Ignition ON, open the software click on connect button, the software connect into the Scanner but the scanner just check all the protocols and don't connect into my car and gave the error saying to check the ignition is on and if is connect properly into the car.
    I just don't know what else i need to do.
    The pins that are present into the car connector are: 4,5,7 and 16.

    Any one can help me ?

    Thank you everybody!

    P.S: Sorry my english, i'm from Brazil.

  • #2
    Was this Ford originally sold in the US, or was it made specifically for export to Brazil?

    Go to the Raw Data tab, click "new", attempt to connect again, and then copy/paste the contents of your communication session here.

    Thanks!
    OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
    Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

    You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

    Comment


    • #3
      Vitaliy,

      i think was made for export to Brazil because i bought it here.
      I will check the log and paste here when i back to home.

      Thank you very mutch since now.

      Comment


      • #4
        If it was made for export, it may not be OBD-II compliant. But let's look at the log.
        OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
        Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

        You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

        Comment


        • #5
          That truck was built for the US but the V6 TDI was never released in NAmerica. In '01 in NA, there was a 5.4L V8gasser, optional V10gasser, and optional 7.3L Turbo Diesel
          My 2007 Ford F350 Work Log located HERE

          Comment


          • #6
            Vitaliy,

            sorry for the delay, here is the log of my OBD Wiz

            Version: 2.10.0.172
            Product: OBDwiz

            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            System.TimeoutException - The operation has timed out.
            ATI: [ATI
            ELM327 v1.4]
            Opening communications: COM8, 115200
            Port Open
            Flushing communications buffer
            ?: [?
            ?]
            Sending Reset Command: ATZ
            ATZ: [ATZ


            ELM327 v1.4]
            Interface connected
            Sending ECHO OFF Command: ATE0
            ATE0: [ATE0
            OK]
            Sending LINEFEEDS OFF Command: ATL0
            ATL0: [OK]
            STI: [?]
            ATI: [ELM327 v1.4]
            [email protected]: [OBDII to RS232 Interpreter]
            [email protected]: [SCANTOOL.NET]

            Trying Protocol: SAE J1850 PWM (41.6 Kbaud)
            ATSP 1: [OK]
            Sending request: 01 00
            01 00: [NO DATA]

            Trying Protocol: SAE J1850 VPW (10.4 Kbaud)
            ATSP 2: [OK]
            Sending request: 01 00
            01 00: [NO DATA]

            Trying Protocol: ISO 9141-2 (5 baud init, 10.4 Kbaud)
            ATSP 3: [OK]
            Sending request: 01 00
            01 00: [BUS INIT: ...ERROR]

            Trying Protocol: ISO 14230-4 KWP (5 baud init, 10.4 Kbaud)
            ATSP 4: [OK]
            Sending request: 01 00
            01 00: [BUS INIT: ...ERROR]

            Trying Protocol: ISO 14230-4 KWP (fast init, 10.4 Kbaud)
            ATSP 5: [OK]
            Sending request: 01 00
            01 00: [BUS INIT: ERROR]

            Trying Protocol: ISO 15765-4 CAN (11 bit ID, 500 Kbaud)
            ATSP 6: [OK]
            Sending request: 01 00
            01 00: [CAN ERROR]

            Trying Protocol: ISO 15765-4 CAN (29 bit ID, 500 Kbaud)
            ATSP 7: [OK]
            Sending request: 01 00
            01 00: [CAN ERROR]

            Trying Protocol: ISO 15765-4 CAN (11 bit ID, 250 Kbaud)
            ATSP 8: [OK]
            Sending request: 01 00
            01 00: [CAN ERROR]

            Trying Protocol: ISO 15765-4 CAN (29 bit ID, 250 Kbaud)
            ATSP 9: [OK]
            Sending request: 01 00
            01 00: [CAN ERROR]

            Trying Protocol: Automatic
            ATSP 0: [OK]
            Sending request: 01 00
            Command timed out
            Connected to the scantool but unable to connect to the vehicle
            ATSP 00: [OK]
            ATZ: [ELM327 v1.4]

            Comment


            • #7
              Unfortunately, this is the kind of response you would expect if the vehicle is not OBDII/EOBD compliant. Sorry.
              OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
              Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

              You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

              Comment

              Working...
              X