Automotive Basics Part4

Calibration init session
This session description assumes that a login procedure has been performed. The first thing then would be to set the session status bit for calibration to “off” with SET_S_STATUS command. Thereafter the memory address containing the data to exchange is selected with SET_MTA command. To ensure that this memory address is available a BUILD_CHKSUM command is sent and an answer from the slave node that confirms this is expected. Thereafter the data byte(s) can be downloaded to the selected address. First a DOWNLOAD command is sent with the number of data bytes and the value of each byte. To actually perform the data exchange the SELECT_CAL_PAGE is sent. To indicate that calibration has started session status bit for calibration is set to “on” with SET_S_STATUS command.
DAQ init session
This session description assumes that a login procedure has been performed. The session status bit for DAQ is set to “off” with SET_S_STATUS. A DAQ list is selected with GET_DAQ_SIZE and the slave answers with the number of available ODTs. SET_DAQ_POINTER command selects which DAQ list, ODT table and element in ODT that should be written to. WRITE_DAQ command then assigns the memory address of the data parameter to the previous selected element. When all DAQ lists are filled as wanted the session status bit for DAQ is set to “on” using SET_S_STATUS. The transmission of a DAQ list is started with the START_STOP command. If several DAQ lists should be started at the same time and sent synchronously START_STOP_ALL command is used.
Areas of use
The most common area of use is in the automotive industry, where CAN is often used, but also in other industry where CAN is used. Conceivable areas of use include -
  • ECU developing.
  • Systems for function and environmental tests of ECUs.
  • In a test bench for combustion engines, gear box or climate control.
  • For measurements and calibration in pre-production vehicles.
  • In a general CAN application outside vehicle industry.
Click to view the CCP documents:
  1. CCP_diag
  2. CCP Version 2.1
  3. CANape_CCP_Communication
  4. Flash_Kernel__CCP__HC12_micro_controller
  5. Integration_of the_Vector_CCP_Driver_with_a_free_CAN_Driver
UDS is defined (Unified Diagnostic Services) in the standards ISO 14229 contains (the bus system-independent part) and ISO 15765-3 (CAN describes the specific implementation). Unlike OBD writes the UDS standards applicable to the general vehicle diagnostic no CAN identifier and no CAN baud rates. Here, then, any vehicle manufacturer is able to decide freely. be called The Standard, however, define how the SIDs and PIDs (hot at UDS Sub-level parameters). Unlike the OBD content of the messages in UDS is not defined in practice. That is, everyone can vehicle manufacturers specify how it defines data, under what parameters on the responsibility, as it codes etc.
The message structure of the UDS diagnostic services consistent with the structure of OBD: The first byte is the SID. Then a detail of the service follows the so-called sub-level identifiers (essentially corresponds to the PID in OBD).
At UDS, there is the possibility to give positive response to messages. For this, the diagnostic tester must be in the request, the top bit set of sub-level identifiers to 1. Negative responses on the other hand must always be sent. This absence of positive response messages is useful for example, to reduce the bus load in flashing.
There are a large number of UDS diagnostic services. The following two tables show an extract of it here. In the tables for comparison, the respective services for the predecessor of UDS, KWP 2000 are shown.


Extract the diagnostic services of UDS and KWP 2000
UDS is defined (Unified Diagnostic Services) in the standards ISO 14229 contains (the bus system-independent part) and ISO 15765-3 (CAN describes the specific implementation). Unlike OBD writes the UDS standards applicable to the general vehicle diagnostic no CAN identifier and no CAN baud rates. Here, then, any vehicle manufacturer is able to decide freely. be called The Standard, however, define how the SIDs and PIDs (hot at UDS Sub-level parameters). Unlike the OBD content of the messages in UDS is not defined in practice. That is, everyone can vehicle manufacturers specify how it defines data, under what parameters on the responsibility, as it codes etc.
The message structure of the UDS diagnostic services consistent with the structure of OBD: The first byte is the SID. Then a detail of the service follows the so-called sub-level identifiers (essentially corresponds to the PID in OBD).
At UDS, there is the possibility to give positive response to messages. For this, the diagnostic tester must be in the request, the top bit set of sub-level identifiers to 1. Negative responses on the other hand must always be sent. This absence of positive response messages is useful for example, to reduce the bus load in flashing.
There are a large number of UDS diagnostic services. The following two tables show an extract of it here. In the tables for comparison, the respective services for the predecessor of UDS, KWP 2000 are shown.
Example: Flash Programming I
As a practical example of the UDS diagnostic services, let us consider the typical structure of a flash programming, as illustrated. The diagnostic tester sends a Growl ReadDataByIdentifier. With this request, it reads the hardware ID and software ID from the controller to see which device it exactly right. Then, the diagnostic tester, the control unit switches to a special diagnostic session. Not the actual diagnosis session for the program, but a session in which there are a number of advanced services available. This is done with the diagnostic service diagnosticSession control. This advanced diagnostic session asks the diagnostic tester, the control unit whether the preconditions are met for flash programming. This is typically that the programming can be done only when the vehicle that the engine must be made, etc.
Basic sequence of a flash programming
Then, the diagnostic tester usually with the service Communication Control the fault memory and off the bus communication in other controllers. This advanced diagnostic session has served its purpose. Now the diagnostic tester on the diagnostic service diagnosticSession control to the programming session. At least now is a SecurityAccess necessary. Thereafter, the diagnostic tester usually sends the so-called fingerprint of the control unit. This is information that is stored in the ECU memory permanently, to indicate that programming. It typically has a workshop identifier in the memory of the controller is written, can be enacted so that afterwards who has reprogrammed the ECU.
Before the flash memory can be reprogrammed, it must be deleted. This is achieved by calling a routine in the ECU memory of the diagnostic service routine control done. Thereafter, the service request download the actual programming operation is initiated. This service allows the controller will also be notified of which are loaded into memory the data and how much data can be expected. Now starts the actual download of data in a loop with the service transfer data. The storage area is transmitted here in blocks. At the end of the diagnostic tester says the control device transfer exit Now that all data has been transferred. After examining the data transmitted in the control unit now takes place, the actual flash process. Typically, the programming operation will take some time. During this time the controller is not able to process requests from the tester. Therefore, the control unit the service transfer exit usually with a negative response and the error code ResponsePending . Reply Only when the programming is completed, the controller sends a positive confirmation transfer exit.
Then examine the diagnostic tester, whether programming was successful, he routine control a routine in the control unit is activated, which checks the memory. Thereafter, a further call to routine control different n dependence of the flash programming examined, such as whether the software or the corresponding record must be programmed. The download process is completed the controller, the controller is normally ECUReset reset. The controller will reboot and goes to normal operation, so back to the default diagnostic session.
In order for the other ECUs in the vehicle also restore the status quo, will Communication Control the normal bus communication again and the fault memory in the other control devices is turned on again. Hence the download process is complete. 

7 comments:



  1. David Brown Automotive has revealed the Speedback GT, a V8 sportscar based on the Jaguar XKR. It will make its public debut at the Top Marques show in Monaco.
    Adah Paulo

    ReplyDelete
  2. Hello

    Please, could you explain me the Format for request download service as in following example...

    34 00 44 00 F1 00 00 05 34

    Here First byte(34) of above data is request data download, 2nd byte (00) is the Encryption/Compression parameter[Data format ID], 3rd byte(44)[Please explain this to me], F1 00 is routine ID for ERASE EEPROM memory & so on...

    Please explain to me the significance of 3rd byte i.e 44 of above data.

    ReplyDelete
  3. The format of RequestDownload service is:
    34 00 XX1 YY2 YY2 ZZ3 ZZ3
    1) addressAndLengthFormatIdentifier
    2) MemoryAddress (1 byte: Mandatory, Other: Conditional)

    coming to your question, 44 means 0100 0100 in 3rd byte, meaning,4 bytes of memory address and 4 bytes of memory size.
    3) MemorySize (1 byte: Mandatory, Other: Conditional)
    4) LengthFormatIdentifier
    5) MaxNumberOfBlockLength (1 byte: Mandatory, Other: Conditional)|
    00- Data format ID(here 00 means that data is neither compressed, nor extended)

    ReplyDelete
  4. Much of the time, you will be given shabby auto protection in light of the way that you will allow the organization the majority of your business.RV'S for sale in Missouri

    ReplyDelete
  5. Emmbros Autocomp Limited is recognized as one of the reputed Indian organizations as the supplier, exporter and manufacturer offer an extensive variety of engineered products which includes Front Axle Shafts, Rear Axle Shafts and Universal Joints Differential Housings etc. the company manufacture these products of electrical machine parts using quality raw material and advance technology.

    ReplyDelete
  6. Flange Yokes are generally used to attach a Companion Flange to driveline on the power supply, differential in a variation of automobiles. There are many companies, offers a wide-ranging of automotive Flange Yokes suitable for imported and domestic automobiles with the proficiency to production for custom requests.

    ReplyDelete
  7. Your blog had very good knowledge and that gave huge instructions and that was really commendable ideas. you have provided good knowledge about professional obd scanner topic please share more information with us.

    ReplyDelete