Archangel, thanks for the video. Wow, Skimask, what a project! And it is pretty cool to "meet" you. Its interesting that our perceptions of someone are usually greatly different than reality.
Bo
Archangel, thanks for the video. Wow, Skimask, what a project! And it is pretty cool to "meet" you. Its interesting that our perceptions of someone are usually greatly different than reality.
Bo
.As far as the OBDII, the system is primarily for emissions and doesn't often monitor basic engine functions for older models.
There, fixed it for you.
Robert
:-)
You are correct, Boroko, in my zeal to define how I see the system I have not adequately accounted your specific needs. Only vehicles 1996 and newer are OBDII equipped and, sadly, the '96 Subaru was improperly implemented and so still we offer an alternate test for that vehicle. I am anxious to help however. Here is a list of the "P" codes available from that vehicle.
I would suggest that if there is a sensor it is being monitored by something (if there is no indicator in OBD or no gauge on the dash... I suspect there is no sensor) and it is likely (to my limited electronics experience) outputting variable voltage - to be read by ADC through a voltage divider, variable current - can be modified to be read by ADC, or a PWM output. I have used "Frequency to Voltage" chips with success - or perhaps the PBP functions of COUNT or PULSIN will be adequate. Once you are able to capture the signal (either from an existing sensor or one installed by you - while only 2015 Subaru may come with the sensor, it might be added...), Let the PIC condition the signal, then output to Android with one of the serial Bluetooth links. There are some pretty good "BASIC" programming apps for Android that should, with some study, allow the development of a display.
I suspect you have come to this same conclusion and are looking for a template, so as not to have to reinvent the wheel. Alas, I do not know of one; however, for a limited number of channels this project might require a reasonable amount of effort and, if the Bluetooth is eliminated, seems almost trivial once the sensors are located or installed. I am using several "analog" voltmeter gauges, driven by I2C DAC's - with custom background templates - they look quite nice and, such gauges are traditional in vehicles, even those without OBDII.
Whatever you decide, I wish you the best of luck and stand willing to help in any way I can.
Last edited by Amoque; - 11th December 2014 at 12:37.
I started a project some time ago with the following features.
1. Battery voltage monitoring
2. 4 EGT thermocouple channels
3. 4 CHT thermocouple channels
4. Electric water pump current monitoring
5. Water temp
6. Oil temp
7. Charge Air temp
8. O2 sensor via serial port
9. Manifold pressure
10. Barometric sensor
11. Tachometers
12. Log data to a compact flash card
13. Graphic LCD output via serial port (Text and bar graphs)
Software is 80-90% complete but written in Proton syntax. Would be a relatively simple port to PICBasic.
Circuit board is complete.
Project was designed for an aircraft application, but the project went away.
PM me. We'll talk.
I have an agriculture Android based electric motor controller that I use Bluetooth to communicate with the PIC chip(s)
I use B4A (basic for android) It is great.
Example screen shots
http://www.grahamelectricplanter.com/gc/
That looks quite nice. thanks for letting me know about it.
bo
Bookmarks