Usage | ID | DLC | Data0 | Data1 | Data2 | Data3 | Data4 | Data5 | Data6 | Data7 |
Engine RPM | 0x100 | 6 | MSB RPM | LSB RPM | 0 | 0 | 0 | 0 | ||
Vehicle Speed | 0x110 | 6 | MSB Speed | LSB Speed | 0 | 0 | 0 | 0 | ||
Water Temp | 0x120 | 6 | MSB water temp | LSB water temp | 0 | 0 | 0 | 0 | ||
Gear Indicator | 0x121 | 2 | Gear number 1-6, 0 for neutral | 0x01 for neutral, 0x00 otherwise | ||||||
Tire Pressure Display | 0x130 | 4 | Front Pressure in 0.2 PSI increments | Rear Pressure in 0.2 PSI increments | Front pressure warning | Rear Pressure Warning | ||||
Front Pressure Sensor | 0x695 | 8 | ?? | ?? | ?? | ?? | Pressure in 0.2 PSI increments | Message counter | Pressure in 0.2 PSI increments | 0x00 |
Rear Pressure Sensor | 0x696 | 8 | ?? | ?? | ?? | ?? | Pressure in 0.2 PSI increments | Message counter | Pressure in 0.2 PSI increments | 0x00 |
Unknown Pressure Sensor | 0x695 | 8 | ID:3 | ID:2 | ID:1 | ID:0 | ?? | Pressure in 0.2 PSI increments | ?? | 0xff |
Condition | Data0 Value |
KTRC in Self Test Mode | 0x0e |
KTRC Mode off, KTRC button not pressed | 0 |
KTRC Mode off, KTRC button pressed | 2 |
KTRC Mode off, KTRC button held, mode changed | 3 |
KTRC Mode on, KTRC button not pressed | 2 |
KTRC Mode on, KTRC pressed | 3 |
KTRC Mode on, KTRC button held, mode changed | 1 |
KTRC Mode off, KTRC button released | 0 |
Condition | Data0 Value |
ECO Mode off, Mode button not pressed | 0 |
ECO Mode off, Mode button pressed | 1 |
ECO Mode off, Mode button held, mode changed | 3 |
ECO Mode on, Mode button not pressed | 2 |
ECO Mode on, button pressed | 3 |
ECO Mode on, Mode button held, mode changed | 2 |
ECO Mode off, Mode button released | 0 |
Condition | Data0 Value |
KACT High Combined mode, KACT button not pressed | 4 |
KACT High combined mode, KACT button pressed | 5 |
KACT High combined mode, KACT button held, mode changed | 3 |
KACT low combined mode, KACT button released | 2 |
KACT low combined mode, KACT button pressed | 3 |
KACT low combined mode, KACT button held, mode changed | 5 |
KACT High combined mode, KACT button released | 4 |
RedRambler,
you keep pointing out how low cost is your set up to hack into the CAN Bus, but you neglect the immense knowledge that you seem to have. I am an engineer myself, but mechanical, and I deem all electronic things as pure witchcraft; stuff that in terms of comprehension could as well be sitting after Saturn's rings. How a human being can accrue and put in use all this stuff is beyond me. Thanks a lot for sharing.
:hail:
Have you figured out the message that turns off warnings (such as TPMS low battery)? The message that gets sent when push and hold top button, push and release bottom button, release top button. Would love a way to do this with just a single button on the handle bars. I'm assuming these PANIC!!! ALL HOPE IS LOST!! warnings are one day going to get me killed and if I had an easy way of shutting them off, they might not kill me. I'm also assuming the only reason I'm still alive is because of BDF's device to turn off the low fuel warning.
2011 Kawasaki Concours CAN Bus
Over the past several weeks, I have been studying the CAN bus on the Kawasaki Concours to understand how it works. I wanted to determine some of the basic operating parameters of the system, as well as decipher the communication protocol that Kawasaki used. I have been partially successful in this effort, and I wanted to post my learnings here for others to build upon.
<snip>
Additional work needs to be done to understand what the TPMS flags and the system error flags.
The diagnostic interface needs to be documented.
Hopefully, my work will motivate some of the very talented folks here to take this a step further and figure out the rest of this protocol. By understanding the protocol, I think all sorts of useful things could be done. (think digital speedo and tach, speedo correction, TPMS sensor programming, Key FOB programming, and more.)
RedRambler
If we can get access to a KDS system for a few hours, it should not take long to capture all the data we need to document the diagnostic interface. Building a do-it-yourself programmer for key fobs and tire sensors would then be straightforward.
I look forward to seeing the results of your work. PM me if I can assist.
RR
RedRambler:
I have a TPMS sensor that needs to be programmed into the ECU and I thought instead of pulling the front wheel to maybe or maybe not find the sensor ID I would try setting up something similar to what you were experimenting with.
I am using the Arduino Nano as well and the MCP2515 Can Controller. I figured I would just send the data to the laptop for now and once I got it working I can fiter the ID's and take the laptop for a ride and get the sensor ID I need.
For some reason I am not getting any data off the bus and I am at a loss to see what I am doing wrong. I was wondering if you could take a look at what I have setup and see if you can point me in the right direction.
I am connecting to the Diagonostic conenctor on the the Can H and CAN L pins as below.
Diagnostic Connector:
-----------
| O O |
| O O O | <---GY/BL (Can High)
-----------
^
|________ LB (Can Low)
I initialize the can controller to 500kbs
if(CAN_OK == CAN.begin(CAN_500KBPS))
The read of data is just a loop so anything that comes into the Can buffer should be sent to the laptop screen. I configured another CAN controller that is transmitting and connected CAN H/L between them and I receive data so I can assume at least the harware is correct and working.
Any information wouyld be greatly apprecited.
Thanks;
Paul
MAN OF BLUES :
Finally figured it out, the libraries I was using didn't have any parameters for crystal frequency and therefore my baud rate was not correct.
Once I sorted that out I am getting data off the bus so with a little more programming I should be able to retrieve the data I need.
Thanks;