Go Down

Topic: Bike interface OBD (Read 95257 times) previous topic - next topic


Yes it is strange but maybe the TPS is limited by the ride by wire maps on the ECU while not in gear and a very low RPM.... I have to test it on the road logging the value.

I'll let you know


I just got started with this library.
I got a vfr 1200 and want to create a new cockpit.

I've order the additional component. And started with the emulator on a pi 3. But I can't get it to work with the latest version of python.

It doesn't handle request.clear()
Can you help out with a new version?



Jun 03, 2019, 10:28 am Last Edit: Jun 03, 2019, 10:30 am by sudolea
(Sorry, this post should have come in another thread on this forum)



I finally got the OBDII port hooked up to my bike and want to test the 21 08 command that TriB mentioned in post 190. I am hoping for some assistance so that when I go to try i'm not stuck researching for hours to get it to work.

Initialization command (Post 190): ATWM8012F1013E\nATSH8112F1\nATFI\nATSH8012F1

Bluetooth Terminal App:

"Bluetooth Terminal" by Qwerty

My questions:

1) do I initialize through RaceChrono App and then use a bluetooth terminal to send the 21 08 command? Or do I send the Initialisation command directly through the bluetooth terminal application?

2) To send the 21 08 command what is the exact numbers that I have to type in the command prompt?



If you want to configure RaceChrono to make it work, take a look at Anttis Forum:
There you will find all you need  8)


Hey guys would this work on Yamaha? I sniffed some communication lines from the YDS scan tool and I cant seem to understand the protocol and format. See below

Line 1: Initializing ECU
FD 00 E5 ED E5 ED FE 10 FF 15 FE 10 FF 15

Line 2: Sensor Data Log
00 00 01 00 02 06 03 57 12 00 13 00 0A 00 0B 00 14 00 15 00 16 00 17 00 20 00 21 00 04 03 05 00 06 FF 07 FF 08 02 09 99 0E 00 0F 00 42 FF 41 F2 26 00 27 27 30 04 31 02 32 50 34 02 37 80

These 2 lines keep repeating over and over.

I dont know if any of this makes sense. But I need to figure out what is the Transmit command so I can get a reply from ECU



Hello swellracing,

as far as I know, Yamaha does not work with a header. And I cannot see any kind of format with known SID and PID values, which Suzuki and Kawasaki are using.
So it is not a proper KWP2000 or ISO14230 protocol.

If both lines are getting repeated over and over, it seems to be a keepalive-value rather then a real message.

So to guess what this values means, we need:
  • The message from YDS to the adapter, accordingly to what will be displayed on the YDS-tool (f.e. RPM)
  • The response from the bike to the YDS-Tool, with the value shown within the tool (f.e. 2,500)

Then move on to the next value like speed, temperature, pressure, etc.
Or reading diagnostic information.


Hi Guys,

I have had a quick read of this thread and it seems to be olong the lines of what I am chasing.

Firstly, I am just getting into this Arduino thingy so be gentle.

I have a Suzuki VZ1800, the tacho has crapped itself so I want to do a bit of a custom job with fancy effects on a colour disply. You guys have managed to play with the OBD code from the ECU, what I am specifically looking for is the data stream from the ECU to the tacho. I know what wire it is on and I have captured a couple of minutes of data with a logic analyser but it is all Greek to me. Where do I start? How do I pul apart this data? I am assuming there will be some sort of start byte. How would I recogonise it?

Would it be possible for one of the GSX owners be able to have a play and detemine what I am looking for or at least direct me in the right direction.



Hi Dragondude,

it is possible to grab the cable from the ECU to the tachometer. There are several different approaches. It can be controlled by raising voltage on older bikes. But also by some kind of a bus-like system.
There are plenty of aftermarked speedometer, which also can show the milage and stuff.

This thread covers the diagnostic interface, only. Which will not cover what you want.

Me personally does not know enough about the communication between the ECU and tachometer-unit.

Go Up