I see there's been some great progress! Have ya'll seen CarbonSignal's digital gauges setup? The backend should be no different to what has been accomplished here so far except for the fancy UI for the gauges. Their setup sale price is $600+ (ya I know - ridiculus). We can accomplished something similar for a much lower cost. Consider a setup of:
-Raspberry Pi 2 1GB: $39
-Raspberry Pi 7'' Touch Display: $60 (RASPBERRYPI-DISPLAY - RASPBERRY-PI Raspberry Pi 7" Touch Screen Display with 10 Finger Capacitive Touch | Newark element14)
-Bluetooth Dongle: $10
-OBDII ELM Bluetooth Scanner: $15
Estimated Total: $124

I had started a while back with a quick proof of concept using python and an open sourced OBD library. I needs to be refined, better UI and of course implementation of certain functionality (needs to be defined). I would do this by myself, but honestly, would never finish it since I am always working multiple projects at a time, but if there's more people involved in the coding I will most certainly be available to collaborate. Any ideas? Anyone interested?

**EDITED**
-If your headunit has video input, you won't need the touch screen, but will need some sort of wireless keyboard/touchpad.
-Any C# development/efforts could be ported and tested on the pi using the Mono framework.

How would you interface this into the nav unit like carbonsignal did? Other than the obvious a/v input...

I'd help making a better python obdII library (the ones out there kinda suck) that could have all the extended Nissan PIDs.

I already released a GPS library that I made for my project (https://github.com/Knio/pynmea2) for anyone uses an external GPS unit.

CarbonSignal is not using the Nav unit display for their system. Instead their kit inclues a 7'' display or a series of smaller displays for each digital gauge.

The easiest way would be to use the a/v input on an aftermarket head unit (needs early raspberry pi models) or the display included in my post above for a second display that could be installed where the cubby/nav-unit sits.

I will be getting that display sometime this week, I will have it test fitted post pictures.

Also, since many people here have already made some progress with their logging tools and reading and sending commands to the vehicle with implementations on C#/Vb.net. Has any of you put some thought into making the implementation compatible with Windows 10 using the Windows Universal App SDK? Will make it a lot easier to create the gui, and can be run in a raspberry pi.

:)

Actually they are. They have a group buy at the moment with two options available, one gives you the 7" screen and the other option is utilizing your stock nav unit. I attached the link for the group buy for your review

http://www.the370z.com/body-interior...al-gauges.html

Aftermarket HU especially the multimedia units come with an HDMI input. Drawback is the lack of touch. C|S/Zadatech doesn't support touch either, which is why they resort to using a joystick.

If you want to use a different screen with the C|S/Zadatech product, just give them a heads up and they'll see if they can get their SBC to work with the display as long as it supports HDMI.

GUI development in Visual Studio is very easy even for different platforms. But we'll need custom UI controls and display, which requires a lot of custom paint and graphics controls. I'm no good with coding graphics after taking a shot at creating my own gauge face. Bleh.

C# programming is fun to pick up, which leads to a nice transition to learning Java for Android development. The difference is the programming paradigm, which is a pain (IMO, the adjusting to the learning curve).

What I've managed to figure out with the .NET environment, though, is manipulating web content on the fly from the .NET program. Basically you create a form and embed a WebBrowser control (runs IE, unfortunately). You create a simple web page with text fields containing unique attribute IDs. The .NET program pulls these fields in as DOM objects that can be manipulated in real-time. You can also invoke Javascript functions from .NET side, or invoke .NET functions from Javascript. Also, the DOM provides ability to manipulate CSS properties, so you can change font colors or show/hide objects on the fly. It's just string manipulation.

In plain English, you can create a table to display values. Make it fancy with fonts and graphics. The .NET program displays this page, but it is also able to pull data, decode, and display the values. For plots, I use Zedgraph. I can code up a UI resembling an oscilloscope.

Anyhow, I recommend the definitions be stored in a database (Access/SQLite). From there you can search for the PID names or sort them in a TreeView display.

If you guys need a functional flowchart and examples, let me know.

I've been working with cars and computers since the early-1970s, think this is a fascinating project(s), and would be willing to do whatever I can to help y'all out. My Googlefu is pretty good so I should be able to help with research. I have a server that could be used for collaboration (I already have a wiki running, see my sig), file sharing, &c. I no longer have a Z but could test non-Z-specific stuff. Any programming skills I had have been obsolete for a while, so I probably can't help much with programming. I might be able to setup rough-but-workable GUIs and other grunt work. If any of y'all need some, let me know.

Here's a test gauge I made for Android, which can be updated in real time. Still a lot of work to do. Ignore the degrees C, I was testing converting between units.

http://www.the370z.com/attachment.ph...1&d=1442597930

For reference
http://www.the370z.com/attachment.ph...1&d=1442598044

Nice.

FWIW: I don't know if you can use them (or would want to), but you can find idiot light symbols at DashBoardSymbols.com.

Some ideas...
 

Brad, under "Nissan 370Z," can you show the actual value? I think it's nice to see the analog and digital display at the same time.

How about a colored dot as a warning indicator? Then test with a preset threshold value. Here are some approaches to function:

• Single color indicating overage.
• Do it by percentage where color is yellow to warn you it is near threshold, and red when you've reached threshold.
• Flashing indicator similar to our shift indicator.

How about a thin gradient arc like tachometer redline, which is dynamic depending on user set threshold.

thanks for the info. Do you know the type of video input the nav display has? New pis have hdmi out, old one has analog vid and hdmi

Sent from my 0PJA2 using Tapatalk

Rca's

I just confirmed with an external 6axis accelerometer/gyro going through some hard turns:

CAN ID 0x292 is the Bosch yaw rate sensor: http://www.bosch-motorsport.com/medi...8925323pdf.pdf

The parameters are a bit different from that datasheet, probably a slightly different version.

0x292 B,C = lateral acceleration (zeroed at 0xf800, 1G = 1024)
0x292 D,E = yaw rate (zeroed at 0x8000, maybe 10240 = 90 degrees?)

http://i.imgur.com/2NytChe.png