Healtech Obd and Tuner pro RT

[Deamon]

Hi everyone, I'm trying to tune the fuel in a Kawasaki 1500cc engine with a turbocharger. The engine is from a Jetski. I have a Healtech OBD device that I connect to the ECU. Unfortunately, the logging controller doesn't provide information like injection timing or ignition advance. However, it does provide RPM, TPS, and Load Map. I have the original BIN and XDF files from this controller. I was thinking about using Tunerpro RT to see where I'm at on the fuel map, etc. Unfortunately, I'm missing an ADX file. Could anyone help me create an ADX file for the Healtech OBD? Nothing comes for free, of course. It would be a great alternative for Healtech users. I also have an Innovate LM-2, but it unfortunately has problems with stable RPM readings from the CDI. By the way, will the ADX file for the LC-1 be compatible with the LM-2? Regards.

[Chatchai]

I tried something similar before on the 2017 Kawasaki SXR1500. In my case, I wasn’t using Healtech I used a Kawasaki Marine diagnostic tool and captured the communication traffic to observe how the message structure looks
From what I saw, Kawasaki uses proprietary protocol KWP2000 with fast-init sequence (similar to KDS). Because of that, basic tools like ELM327 won’t wake the ECU properly, so you can’t talk to it directly through TunerPro without first handling that special init.

I also planned to make an ADX for TunerPro, but got stuck at the fast-init stage since TunerPro doesn’t handle that part automatically.

So yes, it’s definitely possible, but the challenge is completing the initialization handshake.
Once someone cracks that and gets a stable session, then building the ADX to read RPM, TPS, etc. and track map position should be straightforward.

[Deamon]

Hello, Czatczai, and thank you for your interest. I once read that older Kawasakis use the KWP2000 protocol, but not entirely.

In summary:

The Healthtech OBD connects to the vehicle, but Tuner Pro won't process its data stream. (I'm keeping my fingers crossed that someone will solve this problem.)
The Innovate Lm-2 won't connect to the Melco via the OBD port again.
My question now is: could I use the data from the Lm-2 analog cable and then, via the USB port, to Logworks, such as RPM, TPS, and MAP, and then configure it in TunerPro RT? Will an ADX file written for the Lm-1 be compatible with the Lm-2 device?

I built an rpm signal filter for the Lm-2, but I haven't had a chance to test it yet. I hope the analog rpm reading will now be stable.

[Chatchai]

the HealTech OBD does communicate with the Kawasaki Jetski ECU, and in theory TunerPro RT can work with it as well - but only if a custom ADX file is created for this protocol. That’s where the real challenge is. Kawasaki uses nonstandard K-Line KWP2000 style for communication (very similar to KDS), not standard OBD-II, so before data logging works you need to reverse the initialization sequence and PID data structure.

HealTech already solved this internally, but when using TunerPro RT we need to decode it ourselves and that part takes time and effort.

Regarding the LM-2
The LM-2 only supports standard OBD-II services 01 commands. It cannot communicate directly with the Melco ECU because Innovate does not allow custom protocol definitions like TunerPro RT does. So OBD streaming from the Kawasaki ECU to the LM-2 is not possible.

However, you can still use the LM-2 for logging through its analog inputs and LogWorks. You just need to manually configure the channels (RPM, TPS, MAP, etc.), which is more work compared to getting native OBD data.

And to answer your last question the ADX file for the LM-1 is not compatible with the LM-2. They use different formats.

[Deamon]

I see that I'm left with the Lm-2.
Czatczaj, thank you for all the information you've given me. We'll just have to wait until some wise person looks into this someday. Regards.