[iDrivino]

After playing around with the iDrivino prototype for the better part of 9 months, I feel the rest of the turbo community is really missing out on something cool. Therefore I've decided to offer the entire source code and hardware schematic for iDrivino free to the public! My six plus months of work is yours in the matter of seconds.

If you haven't seen what the iDrivino is all about, see this post
http://www.e90post.com/forums/showthread.php?t=578237

I've shared the code on GitHub for people to learn, modify, and improve as you see fit.
https://github.com/idrivino/arduino-side
https://github.com/idrivino/propeller-side

I have attached a PDF of the hardware schematic in the idrivino/arduino-side repo. My prototype is built on the Chameleon AVR board, the SK-Pang Canbus shield for Arduino, and a bunch of hand-soldered components. It ain't cheap or pretty, but it sure does the trick.

There is a ton of cleaning up to do, and many half or unimplemented stubs of code commented out within the Arduino side of microcontroller. In addition, much of what I've added to my prototype as "extras" such as the external 3-bar GM MAP sensor, meth output pin, etc. you may neither want nor need.

Many thanks to RixSt3r for his friendly e-mail exchanges back and forth.

To all the nerds & geeks on e90post: I look forward to you implementing some awesome new features!

If anyone wants to make me an elegant integrated PCB of the prototype, that would be cool too.

[iDrivino]

Reserved for media to be uploaded.

[posite]

Very cool that you made it open source!

[hickoryE92]

i like this a lot... i think it could be much more appealing if the gauges/display was a different style. Like maybe make it more OEM looking or at least more modern and not so plain. Perhaps have some color too.

[E90Company]

Nice job! Too bad I won't be benefitting from it

[NiVeDh]

Very cool.

[EDM92]

Awesome!!

[AltecBX]

Very cool to put this out open source. Great work!

[R 4 5 T 4 M 4 N]

awesome, thanks!

[GetSomeE92]

Checked out your old thread. That is really cool. I already have the ModMyNav multimedia interface, too. Only thing I'm missing is the knowledge to make it work with my car and a JB4.

[iDrivino]

Originally Posted by hickoryE92

i like this a lot... i think it could be much more appealing if the gauges/display was a different style. Like maybe make it more OEM looking or at least more modern and not so plain. Perhaps have some color too.

Go for it! Open source, so login to Github and get to work. All the changes you're looking for are done on the Propeller chip using Spin, so time to get proficient at it. There are actually 4 colors in the current implementation If anyone wants to dedicate the time, you could display bitmapped images if so desired. You just have to get the Flash memory code working again and make a Prop driver to load it.

[Slops]

This is awesome! I was hoping it would be compatible with the USB rev3 but maybe there is some room for improvement! Great application though!

[Farewell]

hey guys, i've got an arduino uno and Can BUS Shield (sparkfun).
with this sketch: CAN-BUS ECU Reader demo sketch v4 - For use with Arduino 1.0
i tried changing the Canbus.h file:

#define ENGINE_COOLANT_TEMP 0x05

to

#define ENGINE_COOLANT_TEMP 0x5C


so it should show the Oil temp ... lazy version just dont wanted to change other files too.

but that doesnt work, does anybody know why?

[335xi Kevo]

It would be sick if you would produce the hardware for this set-up. I would totally buy the hardware from you.

[iDrivino]

Originally Posted by Farewell

i tried changing the Canbus.h file:

#define ENGINE_COOLANT_TEMP 0x05

to

#define ENGINE_COOLANT_TEMP 0x5C


so it should show the Oil temp ... lazy version just dont wanted to change other files too.

but that doesnt work, does anybody know why?

BMW OBD-II protocol does not support all PIDs listed. I am assuming you're using a list like on Wikipedia. Only a small handful are active. I don't have a list of the ones which work, but after discovering what you've found I abandoned the OBD-II implementation. You're better off using the K-CAN/D-CAN/PT-CAN buses available off the same connector.

[Farewell]

i took it from your sketch, i thought it would be easy like just changing the PID, but ok its not like that...

so i have to figure out, how to read the K-CAN/D-CAN/PT-CAN...

just started my little project, so it may take a while xD

[Farewell]

hm i dont get it -.-
if there is anyone out there, with a sketch, would be great.
just the oil temp, thats all ;(

[alexwhittemore]

Originally Posted by iDrivino

BMW OBD-II protocol does not support all PIDs listed. I am assuming you're using a list like on Wikipedia. Only a small handful are active. I don't have a list of the ones which work, but after discovering what you've found I abandoned the OBD-II implementation. You're better off using the K-CAN/D-CAN/PT-CAN buses available off the same connector.

Any idea where to find the pinout for the connector? I assume you mean BMW includes K/PT/D can all on the handfull of pins (1/3/8/9/11/12/13) left to 'vendor option,' but the Voltage Supply and Bus Systems and General Vehicle Electrical PDFs don't seem to have the actual connector documented.

Follow up question, K is the Body bus, yes? So K is the bus which traffics Window/door/lock messages? K is the bus that's exposed on the standard OBD-II CAN pins 6 (H) and pin 14 (L), right? Does K have ignition messages as well, or are those on the PT-CAN bus?

The reason I ask is that I'm planning a project along the lines of an open-source alarm/geolocation/perhaps remote start module. Door and lock messages are obviously most interesting to me, whereas remote ignition may well be impossible for reasons other than finding which bus the messages are on.

EDIT: for the record, the connector pinout is interesting to me since having a prototype on the connector is more convenient, but eventual implementation will almost certainly be IDC-style taps on the wires BEHIND the connector. So still, a pinout would be nice to have to locate the lines.

[iDrivino]

Originally Posted by alexwhittemore

Follow up question, K is the Body bus, yes? So K is the bus which traffics Window/door/lock messages? K is the bus that's exposed on the standard OBD-II CAN pins 6 (H) and pin 14 (L), right? Does K have ignition messages as well, or are those on the PT-CAN bus?

My bad, K-CAN is not available on the OBD2 connector. I don't use CAN via the OBD2 port, so I am by no means an expert on this. Based on my limited experimentation, PT-CAN are pins 6/14. D-CAN (I guess technically D-Bus for Diagnostic Bus) is the same 500k bus rate & pins, but the messages will be specially formatted diagnostic ID messages. I do not have a BT cable, but I am assuming these messages are how they're unlocking the features they do.

For K-CAN, you will have to tap into somewhere inside the cabin. If you have iDrive, the back of the radio is convenient (which is what I'm doing).

Good luck, sounds like an interesting project!

[alexwhittemore]

Originally Posted by iDrivino

For K-CAN, you will have to tap into somewhere inside the cabin. If you have iDrive, the back of the radio is convenient (which is what I'm doing).

Aww hell, that was my next question . No idrive here. I may just have to dive into the junction box, then, since all the bus terminations there are well documented.

[DallasBoosted]

It would be very nice if a vendor could come with a plug-n-play gauge box that displays some gauges on iDrive... AFR bank 1/2, boost, coolant temp, maybe fuel trims would be nice.

[VSmotorsports]

very nice, thanks for sharing and putting your time and effort into making this work!