OBD for Proton - new bluetooth project

It has been a while... There are some requests for the Obd reader (dashxtender) but since it involves a lot of hadware I found it difficult to make. It also needs to have the look to be attractive, for which I am not very good at aesthetics. Plus, the LCD that I used are no longer in the market and new ones has different pinouts. I need to change my circuit...!

Hence, I have been working on this bluetooth thing. I found one cheap bluetooth to serial board. I just received them last week.

I ordered the wrong ones!. This one has no pin. With my age and eyesight, it was a strain to solder some wires on those small things.

This board that I build can communicate with my Galaxy Note. Yeay...!

I also built some codes so that this thing can communicate to my Proton Saga BLM ECU via OBD. I also incorporated some translation codes so that TORQUE can communicate with my ECU via this board. Findout about Torque here http://torque-bhp.com/ or you can download from Google Play. There is free version - torque lite. Paid version lets you do a lot more things..!

Initial tests proved a success..! I can display things such as speed, rpm, manifold pressure, load, temperatures on my Android..! and error codes! Now you can use TORQUE for your PROTON...!

This kit is also much cheaper to make..!

Here is a video of the kit in action....

You can add more display such as injection pulse width, battery voltage by using customised PID in Torque.

Interested? Leave a comment below or email azrisyamilATyahooDOTcom

kepada Joy , kalu pakai Kancil dengan carburettor je  tak payah pasang la...   



.

OBD reader : Data, error codes and erase error codes

The OBD reader now has the capability to read error codes and erase them after repair. It can read up to 10 error codes (I think nobody needs more than 10 error codes... unless you are a repairman. Several error codes is enough to get you to the workshop and get professional help).

One thing good is that the error codes for Proton EMS700 and ems400 is in accordance with the standard error codes. You can find the codes and what it means from the internet. This one lists the error codes

http://www.nology.com/OBD2FaultCodes.htm

This one has details on the symptoms and recommended solutions.

http://www.obd-codes.com/trouble_codes/

The new upgraded software also has improved data speed. The display now is a lot more responsive and real time.

Here is a video of the dashXtender...

OBD reader new update

The OBD based dashboard extender for PROTON Campro engine was squeezed into small electronic hobby box.

I read recently that someone managed to get Scangauge to work on PROTON persona elegance. He mentions that the new Scangauge has updated firmware and should work with Campro based engine. I certainly have doubts as it was unlikely (in my opinion) that Scangauge people would consider upgrading their kit for such a small market. My feeling is that, it is the new PROTON ecu that is compatible with OBD2 protocol. Note that the new Persona has new 32bit ECU, unlike its predecessors.

Thus,I still think the kit shown in this picture is the only one that works on older EMS400 and EMS700 ecus....; ). I can also change the codes for use on Perodua MyVi.

Things that can be shown:
1. engine rpm
2. throttle position
3. engine coolant temperature in degree Celcius
4. intake air temperature
5. Injection pulse width in milliseconds
6. intake manifold pressure
7. oxygen sensor correction factor
8. load (this is actually volumetric efficiency)
9. oxygen sensor voltage
10.Battery voltage
11.lambda adaptation 1 and lambda adaptation 2 (I am not sure what these are, but are available from the ECU data)
12. fuel consumed in liter (calculated by my own calculation)
13. Fuel economy in litre/100km. This is average fuel economy.(calculated by my own calculation)
14.fuel consumption in km/liter. This is instantenous data. (calculated by my own calculation).

The display can be in the form of digital values and also simple horizontal bar graphs.

The new source codes also assists for acceleration tests to be carried out. (Passby and standing start acceleration tests). It prompt the driver to execute the tests and automatically measures and display the data.

Interested? Leave a comment below or email azrisyamil AT yahoo DOT com.


And here is another equally poor quality video.




and here is another

Student project using OBD reader

Here are some example data obtained from the OBD reader as was collected by one of the student groups. This is actual driving in KL. I think this is from Kajang to KLCC. Here it can be seen that the fuel economy changing along the route. At beginning of the route, at kilometers 5-10 and at 17kms there are peaks of fuel consumption (in litre/km). This could be due to traffic jams etc. Thus, if there are 2 routes available, one can compare the data and tell which route is more cost effective.




Below is the raw data of engine rpm, vehicle speed and injection pulse width. There are other data that can be monitored.


There are a lot more possible projects that can be carried out using the OBD reader. One can plot the fuel consumption along major roads in major cities and relate that to CO2 emissions. Hence hot spots can be plotted on a map.

One can also monitor the data when driving in Malaysian cities and compare the driving pattern to the adopted emission test cycles (based on European test cycles). See whether the adopted test cycles represent our roads and cities. See whether the emissions measured by the adopted test cycle over or under-estimate the real emissions produced when driving in our own cities.

One can test different fuels and see whether there are significant differences

One can test all gadgets/additives on the market and see whether they really perform as claimed.

and many more......

Diesel Common Rail System pressure controller and injector driver

Here are the diesel common rail pressure regulator controller that I developed ( it is the strip board on the left, inside the black box). It is based on simple PID control. The output is a pulsed voltage to the regulator.

On the right is the injector driver, with 2 potentiometers to adjust the injector pulsewidth and the rpm. Both are driven from a PC power supply. Refer to earlier post on how to make use of PC power supply units. Note the large capacitor, it is used to store enough charge for the initial opening of the injector. The injector needs 50V to initiate. The other picture shows the voltage trace for the injector operation.

It seems that this topic on the injector driver may be of interest to many people, I am posting the schematics and the source codes. Again I am using the PicBasicPro compiler.

Note that I do not guarantee that this will work for any other applications. In my case, it works but not very reliable. Use at own risks. Modify the circuit as seems fit (e.g. increase the voltage to 80V, isolate the microcontroller better (use optoisolator?), adjust the capacitance, etc). If anyone has managed to make it work better, please let me know by putting some comments below.





The schematic above I got from the internet.I think this is from Freescale. An article here may be useful http://www.eetimes.com/design/automotive-design/4019437/Trading-Fuel-for-Silicon--151-How-Electronics-Drive-Fuel-Efficiency

Below is my own circuit. This is for one single injector operation only. There is a mistake in the schematics. The crystal should be 4MHz and not 20MHz. Thanks Juan Antonio who had pointed this out.

I just found out there is another mistake. The code uses portc.2 as output to drive the high side driver (denoted as IC2 in the circuit). So the connection should be to portc.2. The schematic erroneously show connection to portc.3.Thanks Mustafa Aydin for pointing this out to me....



The previous hex and PBP file also has some mistake. It will not adjust the injection duration. Here are the new files.(thanks also to Juan for reporting this to me)

HERE is the hex file.


HERE is the picBasicPro file.

There is LCD display showing the pulsewidth and also the delay in between the pulses.

There are also 2 potentiometers to adjust the pulsewidth and the delay between pulses.

Make sure you have strong 12 or 14volt supply (maybe from a car battery)

Also make sure you don't short out the high voltage circuits. This could be damaging to the circuits as well as give quite a nasty bang (you don't want to touch it). Put adequate insulation (maybe you want to put some tapes/silicon/hot glue underneath the board, if you are using stripboard/vero board)

the idea is to charge the capacitor by switching the injector on/off from12V repeatedly at certain frequency (I cannot remember what frequency that I used). This is done from the low side driver (i.e. repeatedly connect and disconnect the injector to ground) This charges the capacitor up to 50V (you may want to increase the capacitor to make it 80V).

Then switch on the injector (low side driver) and send voltage from the capacitor for a short time ( this also I cannot remember) by using high side driver. After that, switch off the high side driver and switch on 2nd high side driver to give 12 (or 14 Volt,depending on your supply).

Repeat the process.


Schematics and source codes for the pressure regulator control will be later.

OBD reader

just plug to the OBD port.




















































































Here are some pictures of OBD reader that I've made. It has similar functions as Scangauge in showing real time data of the engine operation. The only difference from those available on the market is that my system will work on Campro based PROTONs and possibly Perodua MyVi. No other system on the market that can work on these cars.

Things that can be shown:
1. engine rpm
2. throttle position
3. engine coolant temperature in degree Celcius
4. intake air temperature
5. Injection pulse width in milliseconds
6. intake manifold pressure
7. oxygen sensor correction factor
8. load (this is actually volumetric efficiency)
9. oxygen sensor voltage
10.Battery voltage
11.lambda adaptation 1 and lambda adaptation 2 (I am not sure what these are, but are available from the ECU data)
12. fuel consumed in liter (calculated by my own calculation)
13. Fuel economy in litre/100km. This is average fuel economy.(calculated by my own calculation)
14.fuel consumption in km/liter. This is instantenous data. (calculated by my own calculation).

The display can be in the form of digital values and also simple horizontal bar graphs.

At present I am working on displaying error codes or diagnostic trouble codes (DTC).

There is also a version of the kit that can tell the driver when maintenance is due (based on kilometer and calendar). This also includes reminder of road tax and insurance renewal.

The new source codes also assists for acceleration tests to be carried out. (Passby and standing start acceleration tests). It prompt the driver to execute the tests and automatically measures and display the data.

And here is a video showing the kit in action. Poor quality video, though..

week 9 fuel systems

For week 9, HERE and HERE areadditional lecture materials.

Please also get THIS macro codes for your StamPlotPro to communicate with the black box (I don't have a name for the thing!).I think they should now work on MyVi, the last test with Irvy's car seems to work.

Please get your own USB to serial converter (buy them from computer store, it may cost you RM25 at Serdang stores) and make sure you install the right driver. So far, I've only used driver for Vista.I am not sure whether you can get USB to serial driver for Windows7.I am pretty sure there are drivers for Vista and XP.If you are using windows7, search the internet and see whether you can find one.

We may want to try start the system on Monday and see whether you can get some data. I have 4 units of blackbox, three more are with some of you (1 with Chong, another with Karim. I am not sure who has the other one.) You may want to bring them Monday. There is an upgrade of the codes and the chip.