Hi everyone! I am new to this forum, hope everyone is having a good day.

I am currently making a project, it's basicly to make a 06 TSX Cluster work with any racing game on PC. I am using an Arduino and a CAN Shield bus.

However, in order to make it work, I would need, if someone has checked it out before, the CAN Bus adresses for the RPM Gauge and speed. So I can send the good signal through my hardware.

I do own a 2005 TSX, but as the 06-08 clusters are different, I can't sniff my car since the adresses might not be the same.

Let me know if someone did or can sniff some CAN adresses for me, that would be great!

Cheers fellas, have a good one!

 

They are the same messages.

 

Oh! Thanks for the reply, might just going to setup it into my car then. Cheers!

 

Hello again,

It appears I cannot sniff my vehicle current as the MCP2515 board I received is bad...

Anyone has any info on the CAN for Honda/Acura? That would be helpful, I need RPM/Speed if anyone has them...

Cheers!

 

There is a lot more to it than just sending rpm and speed. Probably a half dozen messages to make all the idiot lights turn off. And there is also that pesky issue of figuring out the checksum value to make the cluster believe the data you are sending. I have countless hours in reverse engineering CAN on various generations of Honda to integrate engine swaps.

 

Oh yeah, I know that. I learned a bit on the adresses and bytes and such, I know it's a bit more complicated. I am currently waiting on my CANable interface and I wanted to know if anyone had the K24 CAN Adresses lying around. I know Scania has a manual with ALL the information, so I wondered if Honda did the same thing?

 

Honda does not have any published information on CAN communications and what messages do what.

 

Copy that bud, thanks for the info! I'll stick with sniffing!

 

I too spent countless hours reverse engineering. I'm feeling generous today, so here you go. Enjoy.
Note: CAN ID 0x20C is specific to 06-08 TSX. Not used for 04-05 TSX.

 

Wow! You are a true legend! Thanks man!

 

Very generous. Checksum and all. Crazy your notes look almost exactly like my notes.

 

 

Hi! Again thanks for sharing this information.

Quick question, while reverse engineering, where did you hook up your stuff? Through OBD2 or Cluster? If it was the cluster, which pins did you hook up your CAN-H and CAN-L? (I know it's F and B-Can)
I assume that if you we're successfull by fetching the information it's actually possible to send data. Just want to confirm where you hooked up your wires as im appearing to be not able to send CAN messages to my cluster.

Cheers bud,
Radeon

 

I did my testing on the bench.

Connector B pin 12 is CAN H, pin 13 is CAN L

CAN didn't make it to the OBD port until the 2007 TSX.

 

Thanks for the info!

Im still unsuccessful on trying to make the cluster work. Im curious, you said that you bench tested, what hardware have you used and what did you do? Im starting to think my hardware is faulty.

 

Microchip's CAN bus analyzer for reading the bus.

Arduino with the Seeed CAN shield for reading and writing to the bus.

The cluster will have a constant output of CAN data. Try reading that data before attempting to write anything to make sure your CAN settings and connections are correct.

 

A CAN bus needs termination at both ends. This is in the form of a 120 ohm resistor. However, in automotive, it's common for designers to do a pseudo balanced configuration
with two 60 ohm resistors in series with the middle tied to half the supply voltage or a special pin on the CAN transceiver.

In a TSX, the VSA module and ECU have the bus terminations because they are at the two physical ends of the bus. For a few feet of wire length, you can probably get away
with a single bus termination. As Ryan suggested, monitor the bus for CAN messages from the cluster. It sends out CAN IDs 0x0D4 and 0x1F4 continuously.

 

I´m feeling generous too. Last byte is no only a checksum. To send can messages on a Honda fastcan (500kbps), there´s a 4 bit counter in the last byte (bits 0 to 3 is the checksum and bits 4 to 7 is the counter). Each message you have to increment the counter, and than do the checksum calculation (tip... each ID have a fixed value you need to add to the calculation).

oh.. If you failed to increment the counter in each sent message, the receiver of the messages will ignore the messages after a few miliseconds.

It´s easier to decode and find how to do the math visualizing the messages in binary.