cyberfox007
11-01-2010, 06:34 AM
Hello Everyone
My name is Nick and i am currently doing research for my final year engineering project. Here is a description of the project that i am doing
The goal of this project is to design, build and make work a gadget that will act as:
- Trip computer:
> should be compatible with any car built after 1996 (North American made: GM, Ford, Chrysler)
> display current vehicle’s parameters such as:
> average speed
> current speed
> kilometers driven
> time on the road
> instant fuel consumption
> average fuel consumption
> etc… (depending on the parameters’ availability)
> log the selected trip data and store it on the external media
> warn if:
> a malfunction is detected
> the speed limit is exceeded (up to four limit values)
> other user-configurable events occur
- Diagnostic tool (stand-alone):
> display trouble codes in numeric format
> decode trouble codes to the messages (for selected/preset models)
> erase trouble codes
> change parameters (option)
- PC-based tool (software):
> include all trip computer’s functionality
> display trouble codes in numeric format
> decode trouble codes to the messages (for all models)
> erase trouble codes
> change parameters
> log the trip data
> analyze the driving habits and give advices (using own or the trip computer’s log)
> keep the service/repair book (date, part/service done, cost, garage name, expected next service/replacement date, etc.)
> configure the trip computer
> firmware upgrade
> run on laptops (WinXP, Win7; MacOS, Linux - optional), and portable devices such as iPad, pocket PC, etc. (optional)
The display requirements:
- graphic display
- configurable information
- touch-screen
PC-based tool should wirelessly communicate with the main gadget to get access to the car’s control modules.
Other useful features to be discovered and discussed with the customer.
A full description of the project can be seen here (http://www.ece.concordia.ca/currentstudents/undergraduatestudents/capstone/projectshow.php?id=217).
The information i am interested in is how to communicate with a car's ODB-II port. For our project, we need to communicate with the car's ECU and get data such as fuel economy, oil temperature and so fourth. I have looked into how this communication is done by looking at the following standards.
J1962 - SAE (Society of Automotive Engineers) standard defining the physical connector used for the OBDII interface.
J1850 - SAE standard for the Class B Communications Network Interface(this standard defines the actual J1850 signaling and timings, used in GM and Ford Vehicles)
ISO 9141-2 (Used in Chrysler Vehicles)
J2284
ISO 11898
J1978 - SAE standard for OBD II scan tools
J1979 - SAE standard for diagnostic test modes
J2012 - SAE standard for EPA emission test report format.
J2178-1 - SAE standard for Class B Communications Network Message: Detailed Header Formats and Physical Address Assignments
J2178-2 - SAE standard for Class B Communications Network Message: Data Parameter Definitions
J2178-3 - SAE standard for Class B Communications Network Message: Frame IDs for Single Byte Forms of Headers
J2178-4 - SAE standard for Class B Communications Network Message: Message Definitions for Three Byte Headers
I do have access to these and more standards with in a database at my school.
Chances are, we are going to use an ELM327DS (http://www.elmelectronics.com/DSheets/ELM327DS.pdf) to communicate between the vehicle and a computer with software we are going to develop. this is something we are going to start off with.
i have a few questions regarding this
Are there any other SAE/ISO/Other standards that i should look into other than the ones i have listed?
Any online resources or books that i can consult on how to connect and obtain diagnostic information about the car?
Any ides on this would be much appreciated.
Thank You
Nick
My name is Nick and i am currently doing research for my final year engineering project. Here is a description of the project that i am doing
The goal of this project is to design, build and make work a gadget that will act as:
- Trip computer:
> should be compatible with any car built after 1996 (North American made: GM, Ford, Chrysler)
> display current vehicle’s parameters such as:
> average speed
> current speed
> kilometers driven
> time on the road
> instant fuel consumption
> average fuel consumption
> etc… (depending on the parameters’ availability)
> log the selected trip data and store it on the external media
> warn if:
> a malfunction is detected
> the speed limit is exceeded (up to four limit values)
> other user-configurable events occur
- Diagnostic tool (stand-alone):
> display trouble codes in numeric format
> decode trouble codes to the messages (for selected/preset models)
> erase trouble codes
> change parameters (option)
- PC-based tool (software):
> include all trip computer’s functionality
> display trouble codes in numeric format
> decode trouble codes to the messages (for all models)
> erase trouble codes
> change parameters
> log the trip data
> analyze the driving habits and give advices (using own or the trip computer’s log)
> keep the service/repair book (date, part/service done, cost, garage name, expected next service/replacement date, etc.)
> configure the trip computer
> firmware upgrade
> run on laptops (WinXP, Win7; MacOS, Linux - optional), and portable devices such as iPad, pocket PC, etc. (optional)
The display requirements:
- graphic display
- configurable information
- touch-screen
PC-based tool should wirelessly communicate with the main gadget to get access to the car’s control modules.
Other useful features to be discovered and discussed with the customer.
A full description of the project can be seen here (http://www.ece.concordia.ca/currentstudents/undergraduatestudents/capstone/projectshow.php?id=217).
The information i am interested in is how to communicate with a car's ODB-II port. For our project, we need to communicate with the car's ECU and get data such as fuel economy, oil temperature and so fourth. I have looked into how this communication is done by looking at the following standards.
J1962 - SAE (Society of Automotive Engineers) standard defining the physical connector used for the OBDII interface.
J1850 - SAE standard for the Class B Communications Network Interface(this standard defines the actual J1850 signaling and timings, used in GM and Ford Vehicles)
ISO 9141-2 (Used in Chrysler Vehicles)
J2284
ISO 11898
J1978 - SAE standard for OBD II scan tools
J1979 - SAE standard for diagnostic test modes
J2012 - SAE standard for EPA emission test report format.
J2178-1 - SAE standard for Class B Communications Network Message: Detailed Header Formats and Physical Address Assignments
J2178-2 - SAE standard for Class B Communications Network Message: Data Parameter Definitions
J2178-3 - SAE standard for Class B Communications Network Message: Frame IDs for Single Byte Forms of Headers
J2178-4 - SAE standard for Class B Communications Network Message: Message Definitions for Three Byte Headers
I do have access to these and more standards with in a database at my school.
Chances are, we are going to use an ELM327DS (http://www.elmelectronics.com/DSheets/ELM327DS.pdf) to communicate between the vehicle and a computer with software we are going to develop. this is something we are going to start off with.
i have a few questions regarding this
Are there any other SAE/ISO/Other standards that i should look into other than the ones i have listed?
Any online resources or books that i can consult on how to connect and obtain diagnostic information about the car?
Any ides on this would be much appreciated.
Thank You
Nick