The FordDiagnostic Transform is used to perform diagnostics on ECUs with the Ford DET (Diagnostic Engineering Tool) and a Vector CANcaseXL interface.

FordDiag-noports

Prerequisites

Windows 7 32-bit only.

The DET (Diagnostic Engineering Tool) from Ford should be installed on the test PC.

Vector CANcaseXL drivers should be installed in the PC. The drivers are available for download from Vector.

Connect the Hardware

1.Connect the Vector CANcaseXL to your PC.

2.Connect the ECU under test to the Vector CANcaseXL interface on the proper channel.

Set Up the Transform

FordDiag-properties-marked

1.Choose one or both of the following:

Click the DIDFilePath property, then 3dots_button to browse to the DID CSV file.

Click the DTCFilePath property, then 3dots_button to browse to the DTC CSV file.

The ports are displayed on the Transform.

2.Select the CANChannelNumber from the drop-down list. (This is the channel of the Vector CANcaseXL to which the ECU is connected.)

3.The FixedChallengeByes and KEYDOWNEncryptedKey properties are reserved for future use.

4.Export the ports.

5.Click Save to save the Harness.

Ports

FordDiag-ports

The following ports are common for all Ford Diagnostic Transforms.

Security Unlock: Used to unlock the particular ECU. (0-Lock, 1-Unlock)

ReadDataByIdentifier: Connects to a message type Signal. Used to specify a 2-byte DID ID to be read at a particular time.

ReadDTCByStatus: Connects to an enumerated Signal. Used to specify the DTC status to be read .

DiagnosticSessionControl: Used to start and stop the Diagnostic Session.

Tester Present: Used to keep the ECU in the current mode continuously.

DID

For DID, ports are populated based on the CSV file using the DIDID and DIDNAME columns. For example:

ECU,CANID,DIDID,DIDNAME,LENGTH,MIN,MAX,RW/R

RC6X,0x737,0xDE04,RCM Configuration ID,2,0,2,RW

Creates two ports:

iDID_DE04_RCM Configuration ID (inport)

oDID_DE04_RCM Configuration ID (outport)

If the RW/R parameter is R, then only an outport is created for DID.

DTC

For DTC, ports are populated based on the CSV file using the DTCID and DTCNAME columns. For example:

ECU,CANID,DTCID,DTCNAME,STATUSMASK

RC6X,0X737,0x801013,ERR_LOP_HIGH_RES_ERR 0,0XFF

Creates the outport: DTC_801013_ERR_LOP_HIGH_RES_ERR 0

TestCases

To read DIDs, use the ReadDataByIdentifier Signal to transmit DID IDs to read the specified DID.

      FordDiag1

To read DTCs, transmit the appropriate value on the ReadDTCByStatus Signal.

FordDiag2

 

CSV File Formats

DID CSV File Format

This file provides DID and port details. The columns listed below must be filled. Others are optional.  

ECU: ECU name

CANID: Diagnostic CAN Id of the ECU.

DIDID:  DID Id which are supported by the ECU

DIDNAME: DID name

LENGTH: Length of the DID message signal.

RW/R: RW=Read and Write , R=Read

Example:

ECU,CANID,DIDID,DIDNAME,LENGTH,MIN,MAX,RW/R

RC6X,0x737,0xDE04,RCM Configuration ID,2,0,2,RW

DTC CSV File Format

This file provides port details. The columns listed below must be filled.

ECU: ECU name

CANID: CAN Id of that ECU

DTCID: DTC Id which are supported by the ECU

DTCNAME: DTC name

STATUSMASK: DTC status mask.

Example:

ECU,CANID,DTCID,DTCNAME,STATUSMASK

RC6X,0X737,0x801013,ERR_LOP_HIGH_RES_ERR 0,0XFF