Healtech Obd and Tuner pro RT
Healtech Obd and Tuner pro RT
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.
Re: Healtech Obd and Tuner pro RT
I tried something similar before on a 2017 Kawasaki SXR1500.
In my case, I didn’t use Healtech; instead, I used a Kawasaki Marine diagnostic tool and captured the communication traffic to analyze the message structure.
From what I observed, Kawasaki uses KWP2000 fast-init only for ECU wake-up (ISO 14230 timing).
After initialization, the communication is not OBD-II compliant:
- No service 01
- No standard OBD PIDs
- Uses proprietary headers
- Uses manufacturer-specific KWP2000 services
Because of this, basic tools like ELM327 or generic OBD scan tools cannot communicate with the ECU properly, even though the ECU does respond at the KWP level.
As a result, it’s not possible to talk to the ECU directly through TunerPro without handling the proprietary session layer.
I also planned to create an ADX for TunerPro, but I got stuck after the fast-init stage, since establishing and maintaining a stable proprietary diagnostic session is required first.
So yes, it’s definitely possible.
Once someone cracks the proprietary session handling and gets a stable connection, building the ADX to read RPM, TPS, and track map position should be straightforward.
In my case, I didn’t use Healtech; instead, I used a Kawasaki Marine diagnostic tool and captured the communication traffic to analyze the message structure.
From what I observed, Kawasaki uses KWP2000 fast-init only for ECU wake-up (ISO 14230 timing).
After initialization, the communication is not OBD-II compliant:
- No service 01
- No standard OBD PIDs
- Uses proprietary headers
- Uses manufacturer-specific KWP2000 services
Because of this, basic tools like ELM327 or generic OBD scan tools cannot communicate with the ECU properly, even though the ECU does respond at the KWP level.
As a result, it’s not possible to talk to the ECU directly through TunerPro without handling the proprietary session layer.
I also planned to create an ADX for TunerPro, but I got stuck after the fast-init stage, since establishing and maintaining a stable proprietary diagnostic session is required first.
So yes, it’s definitely possible.
Once someone cracks the proprietary session handling and gets a stable connection, building the ADX to read RPM, TPS, and track map position should be straightforward.
Last edited by Chatchai on Wed Jan 28, 2026 5:36 pm, edited 4 times in total.
TunerPro RT | ADX files project creator
Re: Healtech Obd and Tuner pro RT
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.
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.
Re: Healtech Obd and Tuner pro RT
The HealTech OBD is able to 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 specifically for this protocol.
That is where the real challenge lies.
Kawasaki uses KWP2000 over K-Line with manufacturer-specific (non-OBD) services, very similar to the Kawasaki KDS system, rather than standard OBD-II.
Because of this, before any data logging can work, the initialization sequence and proprietary PID / data structure must be reverse-engineered.
HealTech has already solved this internally in their firmware.
However, when using TunerPro RT, we need to decode and implement this proprietary protocol ourselves, which takes significant time and effort.
Regarding the Innovate LM-2
The LM-2 only supports standard OBD-II Service 01 commands.
It cannot communicate directly with the Melco ECU, because Innovate does not allow custom or proprietary protocol definitions, unlike TunerPro RT.
As a result, OBD data streaming from the Kawasaki ECU to the LM-2 is not possible.
That said, the LM-2 can still be used for logging via its analog inputs together with LogWorks.
This requires manually configuring channels such as RPM, TPS, MAP, etc., which involves more setup work compared to receiving native ECU diagnostic data.
Finally, to answer the last question:
the ADX file for the LM-1 is not compatible with the LM-2, as they use different file formats.
That is where the real challenge lies.
Kawasaki uses KWP2000 over K-Line with manufacturer-specific (non-OBD) services, very similar to the Kawasaki KDS system, rather than standard OBD-II.
Because of this, before any data logging can work, the initialization sequence and proprietary PID / data structure must be reverse-engineered.
HealTech has already solved this internally in their firmware.
However, when using TunerPro RT, we need to decode and implement this proprietary protocol ourselves, which takes significant time and effort.
Regarding the Innovate LM-2
The LM-2 only supports standard OBD-II Service 01 commands.
It cannot communicate directly with the Melco ECU, because Innovate does not allow custom or proprietary protocol definitions, unlike TunerPro RT.
As a result, OBD data streaming from the Kawasaki ECU to the LM-2 is not possible.
That said, the LM-2 can still be used for logging via its analog inputs together with LogWorks.
This requires manually configuring channels such as RPM, TPS, MAP, etc., which involves more setup work compared to receiving native ECU diagnostic data.
Finally, to answer the last question:
the ADX file for the LM-1 is not compatible with the LM-2, as they use different file formats.
Last edited by Chatchai on Wed Jan 28, 2026 5:32 pm, edited 1 time in total.
TunerPro RT | ADX files project creator
Re: Healtech Obd and Tuner pro RT
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.
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.
Re: Healtech Obd and Tuner pro RT
I have a question: does this Adx for the Lc-1 really work without any problems? I'm asking because I'm planning to buy this device, either the Lc-1 or the Lc-2.