Hondata

Hi All,

I'm working on a Kswap into a non-Honda, and am wanting to use the original clocks. They speak CANBUS and I've been able to reverse engineer almost everything I need on the bench with a spare set of clocks. My plan is to take the Hondata KPro CANBUS output, do some manipulation to be the right format, and resubmit to the clocks in the car.

However, what I don't have at the moment is access to the car itself and therefore I can't do a CANBUS dump from the KPro4, therefore I don't know the format of the messages. This page (https://www.hondata.com/help/kmanager/i ... output.htm) is a good reference, but it's not clear to me how the data is structured in each of the CANBUS frame ID's.

For example, that page suggests 0x660 is the frame ID for RPM, speed, and gear, but it provides no example data bytes (and the position of each parameter). Does anyone have a CANBUS dump that I can look at from a KPro4, or any further details into the byte structure of each of the frames?

Thanks a lot!

Or perhaps this is actually as simple as it seems?

Assuming 0x660 is 6 bytes in length, that would make
- byte[0] and byte[1] == rpm (16 bits)
- byte[2] and byte[3] == speed (16 bits)
- byte[4] == gear (8 bits)
- byte[5] == voltage (8 bits)

?

Yes. Values are big endian.

That's great, thank you for the reply. I've been simulating Hondata CAN via a RaspberryPi for my project and I've got it all working, i.e. frame manipulation in real-time, just not sure if I've got the endian the right way round yet. Here's an example of my simulated/random code...

(1566766982.659444) can0 660#15dc00fa0384
(1566766982.669563) can0 661#0046000f
(1566766982.679681) can0 662#004b0145

If you have any real data I'd really appreciate it. Thanks!

Endian looks ok.

Hi i need help kpro v4 canbus can be connect the defi dsdf canbus ? https://www.defi-shop.com/media/manual_ ... e4.0_e.pdf