Kawasaki Versys Forum banner
21 - 40 of 51 Posts
Discussion starter · #21 ·
Believe I understand.

Green lines on the image have continuity, the red line does not.

I don't have continuity between 4 & 5, which means the GRND on the socket isn't bridging them.

I do not have K & L line mixed up - K line on the socket has continuity to 7.
that looks correct.
do you have dongle lights going on or is the BT turning on (can you connect with your phone?)

I can only assume that your dongle does not support the KWP protocol - unfortunately a lot of manufacturers use a bad clone ELM chip which doesn't do so and it's impossible to know until you try.
 
that looks correct.
do you have dongle lights going on or is the BT turning on (can you connect with your phone?)

I can only assume that your dongle does not support the KWP protocol - unfortunately a lot of manufacturers use a bad clone ELM chip which doesn't do so and it's impossible to know until you try.
Yes, I can connect to the dongle with my phone via bluetooth, however it won't connect to the ECU.

The dongle I have claims it supports KWP2000, however as you said, it's impossible to know if it's a good clone ELM.

Since the current cable I have is only attached to 4 for GRND and I can't bridge it to 5 without destroying the molded OBD II socket, I'm going to buy a new one, which explicitly states it has 4&5 on a single wire and repin it if the config isn't correct at the bike side:


A continuity check should prove out any issue with the adapter - we'll see on the dongle once I have the pinout correct.
 
Discussion starter · #23 ·
Put a piece of fine wire (AWG 32 wire wrapping wire) between pin 4 and 5 into the socket before you plug into the adaptor.

Do you have access to a scope? I'd be trying to scope the K Line. K line should be showing 12 V and dropping when sending data (it's a inverted logic signal).
 
The issue was ground to pin 5.

Bought this:
AMHTDOL Obd2 Adapter Fit for Kawasaki Motorcycle 4 Pin to 16 Pin OBD Diagnostic Cable,for Z250/Z650/Z1000/ER6N/EX650F/Ninja400 Motorbike ECU Programming,Work with ELM327 Obdii Code Reader/Scanner Amazon.com
Can confirm it connects and reads on a 17 Kawi Versys 650 with a Veepeak VP11 obd reader on Torque Lite and Car Scanner apps.
When I have more time, I'll try DMD to see if I can get it working.

Goal is tomorrow to have DMD running on a 10" tablet on the bike with an all in one dashboard.
 
Discussion starter · #25 ·
The issue was ground to pin 5.

Bought this:
AMHTDOL Obd2 Adapter Fit for Kawasaki Motorcycle 4 Pin to 16 Pin OBD Diagnostic Cable,for Z250/Z650/Z1000/ER6N/EX650F/Ninja400 Motorbike ECU Programming,Work with ELM327 Obdii Code Reader/Scanner Amazon.com
Can confirm it connects and reads on a 17 Kawi Versys 650 with a Veepeak VP11 obd reader on Torque Lite and Car Scanner apps.
When I have more time, I'll try DMD to see if I can get it working.

Goal is tomorrow to have DMD running on a 10" tablet on the bike with an all in one dashboard.
Very nice. I think you'll find the update rate too slow for a speedo etc. unless you have a really good ODB reader. The clone ELM chips simply don't read that fast, the legitimate readers that use the real ELM are hard to find and expensive. I only use my solution for coolant temp and voltage on my V650. However let me know please as I need another OBD reader and if your Veepeak works well I'll order one. The new STN chipsets are meant to be fast (OBD Solutions). ELM has stopped making chips since the pandemic.
 
I wasn't really worried about a speedo, DMD2 gives you gps speed.
I also wanted it working for the coolant sensor and DMD is also supposed to allow obd connection, but I need to research.

Idk if the VP11s will have the good chip or not-the one I have I bought off Amazon about 6 years ago. One can hope, though. And they're cheap.

I'll update as I learn more.
 
Many moons ago I built a DIY OBD board to get into a Fiat ECU.
The problem is the codes are not a standard.
For example here is the standard. Codes.
Or just google OBD2 DTC codes.
The only work arround for this I know off is to get your hands on the source code for the software and then mod it to work with the codes on your bike.
For example Harley guys have an open source android app that works on all harleys.
This is a huge job I wonder if anybody has done it for Kawasaki bikes.
And just how good this Torque app is at working with and reporting all the Kawasaki Codes.
The danger is it could give you wrong info as to what the real problem is.
I prefer apps which just report the Code than I look up what that code represents for that particular engine.
 
I wasn't really worried about a speedo, DMD2 gives you gps speed.
I also wanted it working for the coolant sensor and DMD is also supposed to allow obd connection, but I need to research.

Idk if the VP11s will have the good chip or not-the one I have I bought off Amazon about 6 years ago. One can hope, though. And they're cheap.

I'll update as I learn more.
So DMD 2 will connect to the VP11 OBD dongle.
I have coolant temp, RPM, voltage running on the dashboard.
I need to buy a plugin for the OBS to be consistent, but the rist time I took it out, the app used a TON of data (4.6 gb).
Still troubleshooting that.
 
Discussion starter · #31 ·
Many moons ago I built a DIY OBD board to get into a Fiat ECU.
The problem is the codes are not a standard.
For example here is the standard. Codes.
Or just google OBD2 DTC codes.
The only work arround for this I know off is to get your hands on the source code for the software and then mod it to work with the codes on your bike.
For example Harley guys have an open source android app that works on all harleys.
This is a huge job I wonder if anybody has done it for Kawasaki bikes.
And just how good this Torque app is at working with and reporting all the Kawasaki Codes.
The danger is it could give you wrong info as to what the real problem is.
I prefer apps which just report the Code than I look up what that code represents for that particular engine.
With all due respect the KWP protocol is documented and supported by the Torque App. I believe it's accurate from what I have observed. I don't think you need to do any of this. Just pay Torque $10 for unlimited use of their app and follow my instructions on connecting a generic ODBII BT reader.
 
With all due respect the KWP protocol is documented and supported by the Torque App. I believe it's accurate from what I have observed. I don't think you need to do any of this. Just pay Torque $10 for unlimited use of their app and follow my instructions on connecting a generic ODBII BT reader.
Just a quick question is it a two way connect as in can you clear codes with this setup ?.
Also any info on the 6 pin connector also found in the same location ?.

My recent 12 code went away / cleared by it self as soon as I reconnected the loose hose to the Map sensor.
 
Hi, I own a 2018 Versys 650 in India and I can't find 4 pin OBD connector cable . Can you help me with pictures of how I can make a connector from scratch because I don't have that much knowledge about motorcycle technology .
I have just made one I will share pics in a bit.
Only doubt I have why cant I have a switched 12 Volt Supply always on will drain the bat. I know just connect when you want to use it. Im doing all this just to track the coolant temps.
 
I have just made one I will share pics in a bit.
Only doubt I have why cant I have a switched 12 Volt Supply always on will drain the bat. I know just connect when you want to use it. Im doing all this just to track the coolant temps.
If you are asking about a 12 volt supply, as to the trouble of connecting and then disconnecting, why not use the tail light circuit. Once keyed on it is live.
 
I am trying on a 2015 but I get nothing out of it, I have the cable and it's wired correctly, I have tried many OBD readers but nothing connects, the one I have now is a OBDLink MX+ and it also doesn't connect, I have tried Veepeak V01 and V11 as well and nothing (tested with Torque Pro).
The only thing I can think of is that either the 2015 had a different system or that my flashed ECU is somewhat not communicating correctly over OBD.

Did anyone had it working on a 2015?
 
Hi. Was there a solution? 2015 doesn't communicate with me either.
I can't imagine your ECU would change the diagnostics data coming from your OE port.
You've done a continuity test on the cable you purchased, correct?
Everything is testing out on the right pins?
My VP11 dongle was bought many years ago-its possible the chip was changed in new production.
If you have continuity on the correct pins, my thoughts are you'll need to trial and error different dongles.
What protocol are you using in Torque?
I'm able to connect with Car Scanner app as well.
Didn't have a ton of luck with torque Lite.
 
@unfor2n8
To edit a post:
Click on the 3 vertical dots to the far right of the timestamp. Select “Edit”.
Image


Edit:
OK, looks like you already did. (y)
 
I can't imagine your ECU would change the diagnostics data coming from your OE port.
You've done a continuity test on the cable you purchased, correct?
Everything is testing out on the right pins?
My VP11 dongle was bought many years ago-its possible the chip was changed in new production.
If you have continuity on the correct pins, my thoughts are you'll need to trial and error different dongles.
What protocol are you using in Torque?
I'm able to connect with Car Scanner app as well.
Didn't have a ton of luck with torque Lite.
Megnéztem az adapterkábelt, minden érintkező a megfelelő helyen van. Szerintem nem a vezérlővel van a probléma. A régebbi modelleket is szkennerrel szkennelték. Nem is tudom, miért gondoltam először, hogy az olcsó kínai szkenner működni fog...
 
21 - 40 of 51 Posts