21 replies to this topic

[Marcos Controls]

The software I'm using only reads whichever specfic PID's you assign to the guages you've created, so it doesn't matter if the ECU isn't receiving all of the sensors it expects, I'm only reading the ones I'm actually using and as I don't need the 90% of the sensor channels I haven't connected them. That's why I can use the throttle position sensor channel for my fuel guage

 

As for the odometer reading in the ECU, I would need the speedo ECU from the Bini clocks that my engine ECU came from as it compares the mileage against the engine ECU and updates the engine ecu every 100km or so. If there is a discrepency it won't display the mileage.

 

I might look into using a Ford ECU as there are alot more SAE PID's available than with the Bini ECU

[Kieranlee999]

http://www.esky-sh.c....php?f=20&t=509

 

spotted that :) im looking for a touchscreen for my raspberry pi so if anyone finds one under £40 then let me know :)

 

Edit: http://blogspot.tenettech.com/?p=2807 just found this as well

Edited by Kieranlee999, 20 September 2013 - 09:50 PM.

[Ethel]

I really like Marc's tactic of using an existing "front end", that's where most of the work would be. Feeding it with the data would be relatively easy. Two approaches seem to be open: Pinch an obd compatible car's ECU and try to run it off the Mini's sensors, or fit the sensors that match the ECU where possible. Emulate the obd responses sent, via bluetooth, to the Android device using a programmable gizmo like Arduino or Pi. There are projects & info on reading OBD with Arduino so I guess it wouldn't be too hard to turn that round. The Arduino/Pi route seems to most flexible, particularly if you have other gizmos (Wideband, Megajolt) that can give you data streams. There are other software, digidash options, such as Winlog, but nothing that's likely to match on cost & features for a road car.

[Stevelee10]

The software I'm using only reads whichever specfic PID's you assign to the guages you've created, so it doesn't matter if the ECU isn't receiving all of the sensors it expects, I'm only reading the ones I'm actually using and as I don't need the 90% of the sensor channels I haven't connected them. That's why I can use the throttle position sensor channel for my fuel guage

 

As for the odometer reading in the ECU, I would need the speedo ECU from the Bini clocks that my engine ECU came from as it compares the mileage against the engine ECU and updates the engine ecu every 100km or so. If there is a discrepency it won't display the mileage.

 

I might look into using a Ford ECU as there are alot more SAE PID's available than with the Bini ECU

 would be nice to see some photos of your project and maybe a video of it working, im really considering something similar for my project.

[Marcos Controls]

I'm not going to be at home for another 6 weeks or so, stuck out in the middle of the North Sea at work. I'll sort you out with some photos when I get back. But fire away if you have any specific questions

[Stevelee10]

do you have an update on how your project is going, would love to see some pics as im getting closer to the stage where i can start building my dash. one question i do have is how have you overcome the odometer issue?

[MiniNoobJhb]

I haven't looked into this too much but from what I have read, I think the easiest from the dash side of things is to find an ecu from a donor car that has a compatible OBDII plug and then there are adapters (bluetooth or wired) for sale (ebay) that can send the information to a touch screen that could use something like Marc has used on his tablet.

 

The issue comes in with finding an ecu that fits into the Mini sensors or modifying them accordingly.

 

Here in South Africa we never got any injection models so they are all carb based with no ecu's.

 

*Quick Hi jack here, wanted to know if it was possible under normal circumstances (even if it had to be a normal gauge) to measure non standard things like oil pressure and temp? And how you would go about doing so?