Quantcast
Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/09/2024 in all areas

  1. In order to connect with the ECU we need two cables. The first is a USB ODBII cable. HUD ECU Hacker’s documentation has a lot of different confusing options, but here’s what I went with and managed to get working, the cable is called “VAG KKL” it is a USB to ODB2 cable. It is available from a variety of sources for $10-15. The second thing we need is a “6 pin delphi to ODB2” adapter cable. It is also available for a similar price. In my case I ordered both from ebay, but there are other sources. Once we have our cable in hand we need to find the plug it in on your machine. My personal rig is a Coleman UT400, but the wire location should be similar for all Hisuns. My cable was located under the middle of the seat area. Just inboard of the battery, where the main wire harness split loom runs. The cable is a 6 pin (3x2) with a dust cap. Remove the dust cap and plug in the 6-pin end of the Delphi adapter cable. Note: When I was done, I left the 6-pin adapter connected, and zip tied it so it now runs to in front of the battery for easier access in the future. Next download and install HUD ECU HACKER DOWNLOAD Open HUD ECU Hacker on your PC It should prompt you to choose a driver to install. This particular cable uses the “CH340” driver (First choice on the menu) click to install, once installed hit the X in the corner to go back to the main page Once the driver is installed plug in the USB Cable, and plug the ODB2 end into the 6 pin adapter. The red led on the adapter should light up indicating it has power. Drop down and pick a com port on the main screen, it should show the VAG KKL adapter as a com port. Click connect on the main menu. It will pop up a bunch of fast scrolling text indicating it is connecting. Once connected you can click through the various tabs to see different data sets. The main menu also has the option to show fault codes, clear fault codes, reset the EPROM back to factory. The other function that may be helpful is recording a log file. You can record a log while operating the unit, and come back later and replay it to try to better diagnose what is happening. Within the various pages you will see the reading from each sensor. Sometimes a sensor reading will be off enough to cause running issues, but not enough for the ECU to realize its an issue. For example if the engine thinks it’s really warm, but its actually cold, it may not inject enough fuel to start. There are also more advanced functions, like adjusting fuel mapping, but that is beyond the scope of this tutorial. Full HUD ECU Hacker Documentation (Very technical reading) If you find this helpful give me a comment below or a thumbs up.
    1 point
This leaderboard is set to New York/GMT-04:00
×
×
  • Create New...