Quote:
Originally Posted by SeeThruHead
I'm letting my imagination run away with me. Like what would a low cost easy to integrate sensor server look like that runs on bluetooth. You have all the parts already built for it just need a generic data transport that lots of "clients" support.
|
Just to be clear, the bluetooth sensor server is just for the analog sensors (temperature and pressure) that are in the engine bay, eliminating the need to bring wires through the firewall.
The bluetooth data is then merged with the CAN bus and OBD live data, which is displayed on the LCD display.
The only generic (or well documented) client I am aware of is RealDash and maybe RaceChrono. (overlays gauges on track video)
Down the road I will spend some time to see how I can all the data into those above items. The good news is, that anything can be changed to fit another format.
Quote:
|
The other ones out that that do similar things are very expensive and usually part of a larger ecosystem like Motec. And don't have bluetooth. I think you could get them to a tablet via the MX+ and custom PID settings in the apps tho. But honestly I haven't looked at it.
|
With the OBD system, it can only have 1 master (MX+) and one slave (ECU) as the same CAN bus addressing IDs are used for the scantool and ECU. I can't think of a way to add data to the MX+.
Quote:
|
Is your project going to be open source? I would be interested in poking around the code if so.
|
For right now, it isn't open source. I have a few thousands hours in development over the past 2 years and I need to get some kind of return.
Down the road I would love to let people more talented than me to see what they can do. -OR- I may just give up and get a real job
