Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: FORD ISO9141 - can any OBD2 tools sniff it correctly?

  1. #1
    Constant Bitrate
    Join Date
    Mar 2007
    Location
    Rutherford, Australia
    Posts
    151

    FORD ISO9141 - can any OBD2 tools sniff it correctly?

    Ford seems to have some sort of proprietary implementation of ISO9141 on it's cars.

    My experience is that the ELM and J2534 style tools can send and receive messages on Ford's ISO9141, but they can't be used effectively for sniffing because of the custom way that Ford implement the message length.

    The tools appear to concatenate query and reply messages, thinking they are one message, and error when the message length is too long.

    Has anyone else experienced this or found a way around it? I'd imagine that support for this method would need to be added to the microcode on an ELM for it to work right.


    Lukeyson

  2. #2
    Newbie
    Join Date
    Jun 2008
    Posts
    38

  3. #3
    Constant Bitrate
    Join Date
    Mar 2007
    Location
    Rutherford, Australia
    Posts
    151
    Interesting link, but not helpful for my specific issue.

    These are Australian Fords, and the German Bosch 5.3 ABS modules, Canadian Airbag Modules and Mexican Bosch Reverse Park Aid Modules all use what appears to be an implementation of ISO9141 that does not conform 100% to the standard - like in the 1st byte format and the Init process.

    It's curious to note that not even that Ford Protocols table shows ISO for Ford. But then I find that a lot - US or European specifications that don't match what Ford builds in Australia.


    Lukeyson

  4. #4
    Newbie
    Join Date
    Jun 2008
    Posts
    38
    fords in the UK tend to lean toward KPW2000 and ISO was mentioned before but I never seen it,
    the ABS 5.3 Bosch can be probed with a breakout box due to the small size of the cable adapter there are a few ABS systems used here Mecatronic III / Mecatronic III with traction control ( TCS ) and of course Bosch 5.3

  5. #5
    Constant Bitrate joeyoravec's Avatar
    Join Date
    Oct 2005
    Location
    Livonia, MI
    Posts
    205
    Quote Originally Posted by Lukeyson View Post
    The tools appear to concatenate query and reply messages, thinking they are one message, and error when the message length is too long.
    You probably need to adjust the P-timers. When there's a delay you use these timers to decide if you got one long message or two separate messages. The timeout is surely faster for non-emissions networks. Don't you have a Mongoose? It's adjustable on there.

  6. #6
    Newbie
    Join Date
    Jun 2008
    Posts
    38
    Mongoose now that looks interesting ( I googled it ) not available in the UK hmmmm I wonder why as the cash register clicks at the dealers lol

  7. #7
    Constant Bitrate
    Join Date
    Mar 2007
    Location
    Rutherford, Australia
    Posts
    151
    Well, while I do I have a Mongoose, the problem is I don't have two. You see, when I am using J2534 software with the tool (Like Ford Module Programming for example), I need something else to sniff what's going on.....


    Lukeyson

  8. #8
    Newbie
    Join Date
    Mar 2008
    Location
    Sydney Australia
    Posts
    6
    Also with Ford Australia it seems that they sometimes use different Baud rates i.e the AU model uses ISO at a baud rate off 9400

  9. #9
    Newbie
    Join Date
    Jun 2008
    Posts
    38
    9600 is the lowest speed

  10. #10
    Constant Bitrate
    Join Date
    Mar 2007
    Location
    Rutherford, Australia
    Posts
    151
    The AU has ISO9141?

    I thought it was just J1850PWM (Standard Corporate Protocol) ?


    Lukeyson

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •