RxDuino: Development Chat
 

http://www.normalexception.net/images/rxduinologo.jpg

Contents

• Intro - Page 1
• Rev.1 Hardware Photos - Post 17
• OBD2 Cable Integration - Post 20
• First Message To M.I.D. - Post 22
• Live Data Monitoring on M.I.D. - Post 29
• Software Version 0.5 (Custom Text) - Post 42
• Rev.2 Hardware Photos (Bluetooth Integration) - Post 69
• Android Logging - Post 74
• MSCAN Testbed - Post 77
• Software Update (Wheel Speed Monitor) - Post 101
• Software Version 0.9 (TPMS and Temps) - Post 114
• Reading Cruise Control Signal - Post 128
• Integrating Cruise Control Buttons - Post 139
• Fab Design Layout - Post 155
• Console Application Design - Post 168
• Hardware Revision 1.2 Design - Post 214
• Hardware Revision 1.2 Layout - Post 222
• Hardware Revision 1.3 Design - Post 226
• Hardware Revision 1.4 Design - Post 254
• Enclosure Prototype - Post 295
• Assembled Enclosure - Post 311

Project Status
- Protyping is complete!
- Software is complete!
- Enclosure is complete!
- Track testing is complete!
- Instruction Manual in progress

Purchase Information
Once the product has been finished, I will be working with the admin's and mods of rx8club.com to set up vendor status and a group buy.

Project Information
http://www.normalexception.net/index...canbus-scanner

Project Roadmap
http://www.normalexception.net/redmi...xduino/roadmap

Introduction
As a computer engineer, I have a very high addiction to hardware, software, and data collection. If there is a piece of hardware that is worth tinkering with, I try my best to get my hands on it and give it a try. For my thesis work, I have played around with the TelosB development boards, and used the TinyOS operating system as a basis for development.


Spending so much time with my car, I have really grown to understand the ins and outs of how the actual mechanics of the car work, but I have been very curious to investigate the software communications that happen. One idea was to purchase a premade obd2 scanner and just view data, but I wanted to go a step further.
During my investigation of trying to get my LCD to properly display the time and temperature after changing out the stock radio, I came to understand how the LCD actually works. Residing on a CANBUS, the LCD is primarily communicated with by each peripheral on the network talking to a specific address. Just like how one can retrieve information from the ECU, I wanted to see if I could actually go a bit further and not only scan for information, but also display some important information on my LCD screen.


In doing this research, I came across the Arduino boards. I have always heard a lot of buzz around these boards, but have never had a need to actually get my hands on one. After finding out that these are a perfect light weight development board, as well as an available CANBUS interpreter, it was exactly what was going to suit my needs.


The first step was to actually design a board and some software to get some information out of the OBD2 port. The first thing I did, was to take a simple stupid application just to get some data.




Once I confirmed that I could actually read some data at a reasonable rate, I decided to spice up the GUI a bit and read some more information, through multiple montiors

You Tube

So far so good, except I found that by having 6 monitors at a time, I get a bit of LCD lag. I will either need to fabricate a lower latency serial bus for the LCD, or do what I decided, and just display 4 at a time.


I will keep you guys updated as time goes. I have some more hardware coming so that I can easily display more info, as well as some tools to fab my own OBD2 cable to communicate to the MSCAN. Let me know what you guys think so far, and feel free to throw in some suggestions.

Looks good, I loved my Scanguage II but I like being able to see the data on my factory LCD VIA the Good Box.

Yep, that's my ultimate goal. Not to rehash what was done with the GB, this will hopefully end up working out for us S2 folks that are unable to use the GB :)

Subscribed! I love the arduino board. I used it to regain button functionality on the OEM nav dash piece and some other minor carputer tasks.

I also just moved to an R3 and will def be installing a carputer on it at some point. Your project is of a lot of interest for me.

You should actually work with MazdaManiac on trying to get that freaking accessport work in S2 cars ;)

Great read. Keep up the good work.

not bad.

Thanks guys, no worries I will keep you guys update as I make progress. If anyone has a good idea on how I can multiplex the two busses that would be great. I was intending to grab a simple AD multiplexer, but it really isn't that easy since the canbus doesn't operate on a digital TX/RX but on an analog HI LO pinout.

Thinking I probably need two muxers

Mx = Mux X
Cx = Channel X

M1C1 = HS High
M2C1 = HS Low
M1C2 = MS High
M2C2 = MS Low

Sx = Select X
M1S1 = M2S1 = Arduino pin D1
M1S2 = M2S2 = Arduino pin D2
M1S3 = M2S3 = Arduino pin D3
M1S4 = M2S4 = Arduino pin D4

So essentially when I pass in 1000 to my selects I will be getting M1C1 and M2C1 enabled, and so forth...

Nerds.



This is very cool, btw. :D:

sweet. I was looking into getting into the arduino and i was thinking of doing the same thing. haha. Apparently the android phones can interface with an arduino board as well, so that could be fun.

uummmmm....yah....er, for sure........huh?

Yea I was impressed with the abundance of peripherals available for the arduino. Wireless modules, bluetooth modules and zigbee modules can all be added for cheap! Who knows, if all goes well with my testing maybe I can tack on a bluetooth module and see if we can get it working with the Torque android app :-p

Or instead of having buttons like the goodbox, we could use the android phone as a remote, have a small app running that has a "d-pad" like interface, and when you touch that it changes the display on the lcd....

but thats all thoughts for the future, my first goal is actually getting this stuff displaying on the screen.

interesting project. looking forward to it.

I'd suggest you patent that idea.. if it isnt already done. Freaking awesome if you ask me! :ylsuper:

It sure would be a sweet thing. I will def keep it in mind. Thanks for the support guys. I will keep you updated

Hey guys, a little update. I managed to double up my CANBUS circuit to now handle both the MS and HS can bus. The design uses two arduino canbus shields which essentially is using a total of two CANBUS interpreters and transmitters. The software I wrote leverages off of the SPI bus, so I can easily toggle which BUS i want to send and recieve data from.

I was actually doing some thinking and thought about what rafaga said about the AP for S2's. Not so much about the maps, but moreso about the masking of a MIL code. Not sure if he has come across this thread, but anyone (MM) know what methods the AP is actually using to mask an error code (mainly the cat.efficiency codes for those guys who want to run catless)? Could it be as easy as writing some data at a certain address on the ECU? I found the address and command to reset the MIL status.

I will post up some pics when I get home of the progress of the circuit.

I'm not into electronics, but this is cool.

Attachment 243608

Attachment 243609

Heres the pics I promised. The top layer is the MSCAN circuit while the middle layer is the HSCAN circuit. The bottom layer is the arduino development board. For those that understand tech jargon and want to know more about what is going on at the top layer with the headers ... thats a rewire of pin 10 (default chip select) to pin 3. This way I can software select which CAN to communicate to depending on what chip I enable via SPI.

I will keep you guys posted. Crossing my fingers that this ends up working out.

Looks like a hell of a start with a lot of potential Paimon. GL. I like seeing some progress being made on the S2 front.

Thanks bud, I appreciate it.

Finished up the OBD cable, DB9 contains HSCAN pinouts, Black = MSCANLO, Red = MSCANHI

Attachment 243588

Attachment 243589

Attachment 243590

Attachment 243591

Attachment 243592

Attachment 243593

I've said it before, and I'll say it again: You, sir, and your "outside the box" thinking is a credit to the forums!!

I know that you've seen this with other products (GB, etc), and call it "borrowed ideas". But, to actually pursue your projects is what I admire :) You're bringing a new strain of hope to SII owners lol Maybe Cobb AP for SII isn't too far away, after all... :suspect:

S2 owners rejoice :) :) :) :)

http://www.youtube.com/watch?v=d5IeEzGp6o4

awesome!

Ohh no:eek: very sick

FYI I ordered a bluetooth chip after I got the screen working. Next step is to see if I can get my android phone to act as a toggle instead of the joystick.