This project's funding goal was not reached on May 23, 2013.
About this project
The OBD-II PIC32 Development Board is an open-hardware, open Android software & open Windows GUI software PIC32 microcontroller development board that can help you to troubleshoot your car’s problems and fix them yourself. The board’s hardware is designed by an Automotive/Hardware engineer who has been in the car repair business for over 15 years. It is equipped with fully functional OBD-II hardware to interface with your car’s Engine Control Unit (ECU). In essence, our OBD-II board is capable of doing everything those expensive Automotive Scanners can do at your local car repair shops. Furthermore, because we periodically provide free, unlimited firmware and GUI software updates as we acquire more information about new features of new car models, our OBD-II Development Board may even be a better car diagnostic tool than most existing Automotive Scanners that don't provide software updates.
Currently, our OBD-II board can support the two most commonly used OBD-II protocols: Controller Area Network (CAN ISO 15765-4) and K-Line (ISO 9141-2) protocols. By law, all vehicles manufactured in 2008 and later must use the CAN protocol to communicate with Automotive Scanners. The K-Line protocol (ISO 9141-2) is used in most Chrysler, European and Asian vehicles manufactured from 1989 to 2007.
Since our OBD-II PIC32 Development Board can be used as a diagnostic tool, you can use it to perform the following tasks with your cars:
1. Scan ERROR CODES to know what is wrong with the vehicle.
2. Clear the “CHECK ENGINE” light after the errors have been remedied.
3. Retrieve useful engine sensor information such as temperature, RPM, throttle position, etc…
The one annoying fact about your car’s Check-Engine light is that, even after you have fixed all of the problems with your car, the Check-Engine light still stays ON, and, until now, only an Automotive Scanner can turn it OFF. Considering that on average, repair shops charge around $75 for turning off the Check-Engine light, it is a no brainer and fairly obvious that this product will pay for itself in virtually no time. In addition, it can also save you and your loved ones numerous trips to the repair shop to pay for minor repairs that you can fix yourself once you know the source of the problems.
The OBDII PIC32 Development Board also provides many other functions and interfaces for developing real-world applications such as: Ethernet, Micro-SD card, IR circuit, FTDI, USB, Physical RS232, A/D, CAN nodes, LIN node, etc.
VIDEO DEMO OF ODB-II PIC32 DEVELOPMENT BOARD INTERFACE WITH WINDOWS GUI SOFTWARE VIA BLUETOOTH
FEATURES OF ODB-II PIC32 DEVELOPMENT BOARD
Beside the state of the art OBD-II hardware, our PIC32 microcontroller board is packed with many useful interfacing circuits used to create real-world applications. They are listed below:
100-Pin PIC32MX795F512L Microcontroller, Roving Network Bluetooth, Virtual COM, Ethernet circuit, IR Receiver/Transmitter, Micro SD socket, Micro USB, Mini USB, Type A USB, Type B USB, Physical RS-232 Port, FTDI Virtual Serial USB, A/D Converter with 8 indicator LEDs, SPI (Serial Peripheral interface), I2C interface, Two CAN Protocol Nodes, and LIN Protocol.
The OBD-II PIC32 Development Board is a well conceived and planned out development board. It is a 6 layers heavy duty PCB microcontroller board built the old-school way. As an example, it even provides physical RS-232 COM port in addition to the virtual FTDI COM port. It even contains every USB connector in popular use today; even the micro USB and USB On-The-Go. It contains many DIP switches to route almost all of the I/O pins to a break out socket when not being used by internal circuits, thus, user can alternatively use them to interface with other peripherals.
WHY COMBINE AN OBD-II CIRCUIT WITH A MICROPROCESSOR DEVELOPMENT BOARD?
That’s simple: because it is a perfect combination. If you’re interested in developing microcontroller projects of your own, there is no project more practical than to interface your microcontroller board with your vehicle’s Engine Control Unit (ECU) and other vehicle control modules such as Transmission Control Module (TCM), ABS module... It is a very rewarding experience using your programming skills to fix your car.
The day we successfully transmitted the ECU’s raw data wireless to the laptop via Bluetooth, we immediately conceived of this Kick Starter project featuring a microprocessor development board with OBD-II hardware to help out people who are interested in fixing their car’s problems themselves. In today’s economy, every dollar counts and when you do the repairs yourself and you do them correctly, you will not only save the hundreds, if not thousands, of dollars in repair costs, but you will be able to enjoy your vehicle for perhaps years longer. This can translate in a huge amount of money saved.
OPEN SOURCE GUI SOFTWARE & OPEN SOURCE HARDWARE
"Life would be so much easier if we just had its source code." Code Project member Crusiatus Black.
Well, nobody has life’s source code. But at least, our backers can have the full source code to our Windows GUI software along with documentations describing how to decode raw digital data from your car’s Engine Control Unit (ECU) to figure out what’s wrong with your car. To be worthy of your support, we have decided to open-source our Windows GUI application which is capable of receiving vehicle’s ECU raw data either wirelessly via Bluetooth or through wired USB interface.
Having access to our Windows GUI’s source code is the most compelling reason for you to support us in this venture. As far as we know, no Automotive Scanner manufacturers out there can offer the same deal, because they just don’t want to reveal their trade secrets. They don’t even allow you access to the ECU’s raw data. All current scanners simply interpret the ECU’s raw data internally and display what’s wrong with your car on their displays. Thus, if they fail to cover some error codes related to some of your car’s features, you would have to wait for their software updates before you can fix your car.
Using our Windows GUI source code, you can easily add any command that our current software doesn’t support yet. And because our OBD-II board’s firmware is designed to transmit the vehicle’s ECU raw data to our GUI application, you can add your code to analyze the raw response data and figure out your car’s problems yourself.
Another advantage of having our GUI’s source code is the ability to redesign the GUI elements to suite your tastes and personal requirements. There is no doubt that many of our backers are talented programmers who can definitely enhance our software to be much more intuitive and user-friendly and to perform functions that have never even occurred to us. With that in mind, to create even more interest in our Open-source projects, we intend to award those who significantly contribute to our Open-source programs with free OBD-II PIC32 development boards.
Beyond the Windows GUI software, we also provide Open-source schematics to our OBD-II PIC32 development board. For those of you who may have worked with some microcontrollers other than Microchip PIC, you can alternatively utilize our OBD-II hardware circuits and connect them to the microcontroller of your choice. We do offer the OBD-II cable only option to help save you time in designing your own OBD-II hardware.
THERE ARE 3 VERSIONS OF OBD-II PIC32 DEVELOPOMENT BOARDS TO CHOOSE FROM:
1. Monster version: This version includes 100-pin microcontroller (PIC32MX795F512L), OBD-II circuits, many types of most commonly used digital interface protocols and other useful components as explained above such as micro SD card and physical RS-232 port.
2. Mini+Bluetooth version: This version includes 64-pin microcontroller (PIX32MX795F512H), OBD-II circuits, USB and Bluetooth (Roving Network) interfaces. This version is perfect for backers who are only interested in using our OBD-II board to interface with their vehicles either by wired USB or Bluetooth interface.
3. Mini version: This version includes 64-pin microcontroller (PIC32MX795F512H), OBD-II circuits and an USB interface. It contains all components the Mini+Bluetooth version does, without the Bluetooth interface hardware to save you money. It can only interface to your vehicles through the wired USB interface.
WE NEED YOUR HELP:
We are asking for your support in order to be able to accomplish the remaining goals:
Hardware aspect: As shown in the video, the OBD-II circuits are working flawlessly to interface with Engine Control Unit (ECU). However, we need to interface with other modules in the vehicle such as Transmission Control Module (TCM) and ABS module. Your fund will help us to hire hardware engineers to perform data acquisition process to gather as much proprietary information on as many different models of vehicles as possible. As you know, there are many car models out there, each of them has its own features that others don’t. The main reason we decided to build our OBD-II PIC32 Development board is because we are fortunate to be in the car repairing business. We have physical access to many different car models every day to experiment with. Our hardware engineers will works with different car model to study its proprietary features, and we will share those valuable pieces of information with you on our Knowledge Base Forum. Also, we need to perform tests to make sure other interfacing circuits such as Ethernet, IR transmitter/receiver, SD card, Serial Peripheral Interface (SPI) and I2C interface function properly.
Software aspect: Currently our GUI software can work on both Android devices and on Windows operating system. Your fund will help us to acquire more programmers to improve our GUI software to work with other functions of the board and to make it more user-friendly. Because there are many other smart phones and tablets besides Android OS that have Bluetooth connectivity, our programmers will port our Android and Window GUI software to work with those devices, as well as Linux and Mac. We will open-source those application software as well.
A WORD OF PROMISE:
We have been working diligently on our ODB-II PIC32 Dev Board product for more than one and a half years, as we committed to build an affordable Automotive Scanner; so affordable that every family can own one. Because we have been in the car repair business for more than 15 years, there are many associated repair shops in the area willing to use our product and to share with us their invaluable feedbacks. We will set up a Knowledge Base (Forum) to share that knowledge with our backers too.
Q1: Can I just use your on-board PIC32MX795F512L microcontroller?
A1: Yes, just disable all the existing functions onboard by turning off all DIP switches then you have access to all the I/O pins of the PIC microcontroller.
Risks and challenges
The CAN (ISO 15765-4) and K-Line (ISO 9141-2) protocols hardware has proven to work flawlessly.
Challenges for this project include hardware provisions to allow users to utilize it for other applications.
In the software arena, we are trying to make our GUI program more user-friendly with a more inviting and intuitive interface.
First and foremost, though, we want to make the board work flawlessly, while at the same time we want to keep the cost low enough to be affordable to every vehicle owner. Most of the components are surface mount devices and compact, which as a core product concept will streamline and simplify the integration process naturally resulting in reduction of errors. The board should be able to be used by hobbyist without any problem.
Have a question? If the info above doesn't help, you can ask the project creator directly.
- (60 days)