Anyone tried this before... OBD2 scanner output into SatNav?

[alex_gray255]

Hi folks

I was wondering if anyone had any suggestions for a OBD2 scanner system/processor that will read data from the MBE chip (tweaking the necessary settings to setup OBD2 data) that can then display data through a SatNav AUX port?

I had identified 2 systems that might have worked, but after some further research had to discount them.

Basically, what I'm after is something that can read the engine ECU data in real time and then display the results on the SatNav screen with graphing and further drill down capabilities.

Seen a few threads on thing like this, but with no real conclusion.

If no one has tried this before, then I'm happy to look into it further, but if someone has already cracked it, then I don't want to try reinventing the wheel (again)

Thanks!

[alex_gray255]

HKS Camp 2 (or 3) system might work...

[crypto]

What specific data would you like to display on the sat-nav ?
Didn't know that there are SatNavs around that can display "standard" OBD data ?
What type/model is it ?

[alex_gray255]

crypto said:

What specific data would you like to display on the sat-nav ?
Didn't know that there are SatNavs around that can display "standard" OBD data ?
What type/model is it ?

There used to be, but they aren't produced anymore, e.g. Pioneer.

What I'm thinking of is a module which will plug into the OBD2 socket (after the chip
is enabled to do OBD...) and read engine data from the ECU, then process it for display
via a AUX video connection.

If it is done right, you should be able to read any of the standard ECU output that the
current Speed six software can, create running graphics etc. All depends on the unit that
you have and its abilities. Like some data loggers can.

At the minimum, it will be able to display the dash data, but more accurately and IRT.

The bonus comes with any post processing that unit can do.

Np, if no one has done it before, I'll get it sorted. Just need to find the right system.

Found one that will wifi or blue tooth the data to an iPhone or Android, but not interested in that.

[crypto]

I always thought MBE had their proprietary protocol on the rs232 interface. What convinced you that it can be set in an OBD mode ?

I would assume you would need to make box that does the protocol conversion AND the physical adaption of the hardware interfaces (rs232 <> OBD-2) ?

[alex_gray255]

crypto said:

I always thought MBE had their proprietary protocol on the rs232 interface. What convinced you that it can be set in an OBD mode ?

I would assume you would need to make box that does the protocol conversion AND the physical adaption of the hardware interfaces (rs232 <> OBD-2) ?

Well, I spoke with someone who knows MBE systems well who said they could be switched to put out OBD2 data.

If that is not true, then I was also switching the Sag MBE chip on my car to a later version or a Syvecs system
later this year. Those should support OBD2 even if the early MBE ones do not.

Again, happy to admit it can't be done if it can't be, but what I've been told so far indicates it should be possible
- as long as the ECU can put out OBD data.

[alex_gray255]

Well, scratch this idea. Not doable with the standard MBE system without potentially going some sort of rs232 coms scraper route which is very messy.

However, looks like a new MBE chip is on the way which can. So, either I use that or chat with Ryan @ Syvecs and see what standard that uses.

[Mattt]

Easily do-able IF you had an OBD2 port.

Bluetooth transmitter to Torque app on Android which can produce an overlay onto a video.

[alex_gray255]

Mattt said:

Easily do-able IF you had an OBD2 port.

Bluetooth transmitter to Torque app on Android which can produce an overlay onto a video.

Yes, the keyword is IF, but sadly, no way to currently do it without a chip replacement.

So, out with the old...

[Mattt]

Syvecs interfaces into a little screen, so I'm sure you can find some way of interfacing the feed into a CarPC.

Raspberry Pi might be a handy little unit to use for the computer.

[alex_gray255]

Mattt said:

Syvecs interfaces into a little screen, so I'm sure you can find some way of interfacing the feed into a CarPC.

Raspberry Pi might be a handy little unit to use for the computer.

Yup. Already seen it and working on that basis now. called the T something or other. Looks a nice unit, but I'm going to integrate it into the existing LCD display space. Discussed it with someone this morning, saw the unit and we're going to figure out how to put it in the dash unit with the existing dials somehow.

Either that or pipe the info into the satnav with a converter.

Early days yet.

[paul1962]

What's wrong with the existing RS232 output or will other interfaces provide more data ?
The existing serial comms are very simply to implement.

[dvs_dave]

The syvecs is CAN bus compatible which is one of the many coms protocols that OBD2 allows for.

Fitting an OBD port is very easy and just a matter of wiring it up. In this case all that's needed is power, ground, and CAN high and low. Only a few of the pins are mandatory for OBD, with the spares left empty for manufacturer specific use as they require.

The hardware side of things is straightforward enough. Where you start to run into issues is determining what coding protocols you're going to use, and under what circumstances a code will be thrown? You can either develop your own (not sure where to even start), or you set it up with OEM software installed (e.g. Lotus) and then adapt it to work within your needs. How you do this I don't know.

The point is that the comms protocols and hardware are already there, but figuring how to make it work is the tricky part.