Wow! You guys have made some great progress. I just started to look for info on the 350Z CAN bus but ran back across this thread and started to work on my OpenXC firmware for the 370 based on Brad's spreadsheet.

I think OpenXC is dropping messages where the dlc != 8 but I haven't finished tearing into it yet.

Such a cool project!
 

Fantastic progress guys! :tiphat:

I've been away from this project but am back on board now. If there's anything I can do let me know :)

I've got an Android tablet in my 370Z now. (I might be repeating myself here...) Mine is an early one without Connect Premium. I'm doing it like this:

http://forums.nissansportz.com/uploa...412_165598.jpg

I've hit some problems with the whole USB OTG and power combination as well as standby power issues but I'm getting there slowly (see here).

So I'd vote to go Android!

Some info I found on the Bosch website. It listed part #'s for the 370Z 09+ models:

Yaw rate sensor, brake system
Bosch Part #: 0 265 005 806
Nissan Part #: 47931 1EA1A

Steering angle sensor, ESP (Electr. Stability Program)
Bosch Part #: 0 265 005 515
Nissan Part #: 47945JY00A

Wheel speed sensor, front
Bosch Part #: 0 265 008 025
Nissan Part #: ?

However, I can't find a datasheet for the yaw rate sensor part # listed there.

i have a similar codebase on iOS and have been going through some good and some very awful bluetooth API's to access canbus/odbii.

im planning on a multiple unit LCD approach, replacing a gauge or two with android wearables, a tablet feeding the bose stereo and an ipod touch sized screen somewhere in direct line of sight.

ive been developing video games for 20+ years and have been on ios since 2008. lots of great opportunities here thats for sure. Ive been focusing on the platform, less on the presentation as I still don't know what the product will be in the end.

I'll be integrating a 370Z 3d model next, there seems to be a good supply available turbosquid.com. I'll start with the 2009 fairly "free" edition and go from there.

http://www.the370z.com/attachments/t...-155.21-pm.jpg

I had these same issues (though with a windows tablet) and think I finally solved them. (incredibly annoying)

1) I found an OTG USB hub that takes external power, and powers both the tablet + peripheral devices, with a built in relay. It needs to trick the host USB controller though, so only works on a few specific models of tablets.

2) USB chargers suck, and USB cables suck. at 1A of power, if you have even 1 Ohm of resistance in all your cabling and connectors, you're only getting 4V at the end. Even with the best cables I could find, I was only getting ~4.6V at the tablet, and that wasn't enough to make it charge. I ended up solving this from both sides:

- I made my own USB cables using 18Ga wires
- I got an adjustable buck converter, so I can run the source at 5.25V, and then it's still 5.0V at the tablet after all the losses.

0x245 F=64 when stability control activates

Found this in the service manual, the Bosch sensor isn't hooked up to the main CANbus, and is instead relayed through the ABS controller, this probably explains why the signals don't match up exactly with the Bosch datasheets

http://i.imgur.com/Tnk2npx.png

From the link you posted:
"PID Number
Use this value to set the number of the PID that is sent with the request. This value can be one or more bytes in hexadecimal format. For mode 01 PIDs, this value should be a single byte (e.g. 04). For mode 22 PIDs, this value is typically two bytes (e.g. 0200)."

You are trying to use a 2 byte address (111F) so you'll need to use mode 22 instead of mode 01 similar to my post here:

https://projectbytes.wordpress.com/2014/06/29/nissan-370z-custom-pids/


Hopefully that'll fix it.

Just guessing, but:

You might be computing a number that the reader doesn't understand. Just as a check, I'd try A (or A * 1). Probably not the problem, but it's easy to try.

I'd also check and make sure the ECM's response is going to be formatted so that your reader understands it (eg, number of bytes). You may have to adjust settings in reader.

Everything I know about OBD/CAN can be found at the wiki link in my sig. I haven't updated the site in quite some time but what's there should still be valid.


Going by your description of readSaePid, it sounds like it is used to concatenate data, possibly for display purposes. But that's just a guess.

Great project. I am interested in doing some of this on my Nismo Tech.

Has this gone anywhere? I just got my Z last week and I would like to get in on this! I write firmware for brake controller ECUs (nothing for Nissan), so I have a little experience.

Sent from my Pixel XL using Tapatalk

I haven't heard of any further progress on this in a long time, but I think we have a pretty good understanding of the CAN architecture and signals built up. Is there anything specific that you're looking for?

Is the progress being documented somewhere other than this page? Would love to see the PID to see tire pressures, for example.

Brad's dropbox sheet is probably the best documentation. TPMS is CAN ID 385