[RESOLVED] Ford DCL communication protocol standard
Home | Reviews and Features | Special Reports | Forums |

Page 1 of 5 123 ... LastLast
Results 1 to 15 of 66

Thread: [RESOLVED] Ford DCL communication protocol standard

  1. #1
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7

    Thumbs up [RESOLVED] Ford DCL communication protocol standard

    Dear Sirs.

    I am from Argentina and I have an Ford Escort 1998 with EEC IV DCL.
    In Brasil and Argentina Ford has used, from 1997 to 1999 the EEC IV DCL, that is a EEC IV (60 pins) modified with a 16 pin communication connector (J1962). It connector use pins 4,5 to ground, 16 to + Battery, 3 and 11 data pins. But nobody know Ford Data Communication Link (DCL) specification. I have found information that Ford has used between 1989 to 1995 the same protocol DCL in USA, but with other connector and in another country too.
    I am looking for this specification to connect the computer with my car. I hope that you have any information about that and you can share it with me.

    Thanks and regards.

    Sergio

  2. #2
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    I have post this thread, because have seen that some users like OneEng or Deanril has Knowledge about Ford´s technicals designs.

    http://discussions.hardwarecentral.c...light=ford+dcl

    And I think that may be they or other user can help me.
    Thanks and Best regards.
    Sergio
    Last edited by Sergio2007; September 12th, 2008 at 09:20 AM.

  3. #3
    Join Date
    Oct 2000
    Location
    Dallas, Tx.
    Posts
    2,670
    FYI-> The thread you linked to is SEVEN YEARS OLD.
    "Imagine a world where dogs took bad owners to the pound."


    http://www.hopeforpaws.org/

  4. #4
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    Hello Steve.
    Yes, It is right, that link is SEVEN YEARS OLD
    But I have seen that the last activity of OneEng was August 26th, 2008 12:32 AM, and then I thought that may be could help me.
    I will try to ask him.
    Thanks again.
    Sergio
    Last edited by Sergio2007; September 12th, 2008 at 10:29 AM.

  5. #5
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    I have tried to send a PM to OneEng and the system say me... Sergio2007, you do not have permission to access this page.

  6. #6
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    Quote Originally Posted by Sergio2007
    I have tried to send a PM to OneEng and the system say me... Sergio2007, you do not have permission to access this page.
    Do anybody can help me ?? (Administrator?)
    Regards.

  7. #7
    Join Date
    Sep 2002
    Location
    Raymond, WA
    Posts
    1,081
    I sent a P-M to OneEng for you.
    AMD AM2 5600+ Arctic Cooling Freezer 64Pro Asus M2N 2gb Corsair XMS2 250gb SATA Seagate Barracuda XFX GTX260 Core 216 LeadTek PVR2000 Capture Card CoolerMaster Centurian 5 case Corsair VX550 PSU 19' DCL LCD Vista Home Premium 64

    Folding@Home Stats Join the Team

  8. #8
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    Thank you edhe62.
    I really appreciate your help.
    Best regards.
    Sergio

    I have found this information for physical layer

    At this site http://www.sae.org/technical/papers/940142 you can read.

    Acp--FordS Audio Control Protocol
    .... ACP is based on the physical layer of SAE J1708 (same as Ford's DCL) and a portion of the SAE J2178 message structure ...

    and an interface here
    http://pinouts.ru/SerialPortsCables/...e_pinout.shtml

    and ACP paper SAE protocol here
    http://www.mictronics.de/?page=cdc_proto#FordACP

    Regards.

  9. #9
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    I am needing now, to know how exactly is DCL code.

  10. #10
    Join Date
    Jan 1999
    Location
    MI
    Posts
    4,144
    I am needing now, to know how exactly is DCL code.
    Hi Sergio2007,

    I am an (ex) Ford engineer in diagnostics.

    The Ford DCL vehicles universally supported diagnostic functions on the original "under hood" connector affectionately called "the doghouse connector" by engineers inside of ford because of its dog house shape. The single wire connector was called "the pigtail" and was not part of the main connector, but was usually physically located very near the doghouse connector.

    All DCL vehicles supported "blink codes". If all you want is to get the codes from your vehicle, all you need to do is to connect a wire to the pigtail connector to the ground (any good one on the vehicle will do) of the vehicle.

    After doing this, the vehicle will "blink" the engine light to you. Your vehicle supports 3 digit codes. You should see the light blink a digit quickly separated by a pause, then another blink set, then a pause, then a last digit of fast blinks. This is called the KOEO (Key On, Engine Off) test. After this set of codes, the "Continuous" or stored codes. You should be able to find a list of code descriptions on the web. If not, let me know and I should be able to dredge up a list for you.

    Then there is data reading. This is much much more complicated.

    On the doghouse connector there are a pair of pins called DCL+ and DCL-

    As you have suggested in your previous post, these are UART based communication lines. In specific, an RS422/485 transceiver works just fine.

    That is most surely the simple part.

    I have worked with practically every vehicle protocol for vehicle communications. DCL is the most silly, mixed up one I have ever seen.

    TS1 XXX-XXXX
    TS2 XXX-XXXX
    TS3 XXX-XXXX
    TS4 XXX-XXXX
    TS5 XXX-XXXX

    If the above diagram represents time stamps of messages and bytes in the message, then the dashes represent a "blank spot" in the byte timing.

    In the DCL protocol, if you wanted to send a message 1,2,3,4,5 .... it would look like this:

    TS1 XXX1XXXX
    TS2 XXX2XXXX
    TS3 XXX3XXXX
    TS4 XXX4XXXX
    TS5 XXX5XXXX

    It has been some time, but I could find the specifics for you (I am at home now and can't recite the messages from memory)

    You basically start communication with one message which results in a reply from the PCM module.

    In order to request data from the PCM, you need to know the specific PID's (Parameter Identifiers) for your vehicle. Today these are standard throughout Ford, but back then .... well, each vehicle had its own PID map.

    All of this is going to be quite an adventure. There are some old tools that you may be able to find on e-bay that will do all of this for you.

    If you could tell me your objectives, I may be able to provide specific information that would help you meet your goals.
    With greater knowledge comes greater understanding!

  11. #11
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    Hello OneEng I am very glad to read your answer.
    I am looking for this protocol some time ago.
    I am intrested in develop an interface to use with my car and see in real time all thouse sensors and actuators and if is posible make KOEO, KOER, clear error codes ...... all for these UART communication lines
    I am a computer technician, but I have a frend helping me, who has developed some interfaces to connect with the standard J1850, J2189 and others.. using microcontrolers.
    I don´t know the specific PID's (Parameter Identifiers) for my car or how can I discover it.
    I understand it is very important to know what data is sending the PCM and what we have to answer her.
    I have seen on e-bay some scanners like Actron 9150 and OTC 3753 but is not very simple buy from Argentina and I am not sure that work with my car.
    The makers of OTC say me that the OTC 3753 will not work with my car.
    Thanks OneEng and Best regards.
    Sergio
    Last edited by Sergio2007; September 15th, 2008 at 12:49 PM.

  12. #12
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    Helllo.
    I was talking with my friend and he say me that we need to know somethings like this:
    1.- Need the PCM a special initialization ?
    2.- Has each message header, mode, pid and checksum like OBDII.
    3.- Which is the speed it work for (RS485).
    4.- Some example to make a probe of communication.
    Thanks again.
    Sergio
    Last edited by Sergio2007; September 15th, 2008 at 08:09 PM.

  13. #13
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    I am thinking that may be OneEng forgot about me. :-))
    Last edited by Sergio2007; September 17th, 2008 at 06:40 PM.

  14. #14
    Join Date
    Jan 1999
    Location
    MI
    Posts
    4,144
    Nope. I didn't forget. I have been working obscene hours this last week and haven't even opened the internet.

    A few answers....

    I was talking with my friend and he say me that we need to know somethings like this:
    1.- Need the PCM a special initialization ?
    2.- Has each message header, mode, pid and checksum like OBDII.
    3.- Which is the speed it work for (RS485).
    4.- Some example to make a probe of communication.
    1. YES. There used to be 15 different initialization routines labeled DCL1-15. Over the years, Ford used predominantly DCL9 and DCL5 and DCL7. I believe that your vehicle (and the majority of later DCL vehicles) use DCL9.

    2. Yes. Even DCL had modes like OBDII protocols; however, target and source were not present since there was only 1 module on the bus (PCM).

    3. I am a little fuzzy, but I think it was 56Kbaud.

    4. I will see if I can dig something up.

    I am off work (on a much much needed vacation) this coming week. I need to have some information from the office (it has been over 10 years since I worked on this protocol). The PID id list, and the protocol definition and initialization routines for DCL9 I have at work (somewhere).

    Just a note, if you could find a cheep scan tool on e-bay like this one: http://cgi.ebay.com/ebaymotors/SNAP-...mZ190251204542

    I know it works because I was the lead engineer for the project on the 2001 cartridge that Snap-on outsourced to us.

    For $300.00 you would have some pretty comprehensive coverage.
    With greater knowledge comes greater understanding!

  15. #15
    Join Date
    Dec 2007
    Location
    Argentina
    Posts
    7
    Thanks OneEng.
    I really appreciate your answer.
    I can stay waiting here.
    I was decided to develop this proyect and will go ahead looking for information.
    May be the SAE J2178 part 3 can help to take a better approuch.
    Can some people help me with this part ??.
    Best Regards
    Sergio

    ED: Like I say you before, it is not so easy to buy in ebay from Argentina.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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