This post will explain how to hook up your PC to the ECU of a Hisun/Coleman/Etc UTV to be able to read error codes & engine parameters for troubleshooting purposes.
This is applicable to all small engines using the Delphi MT-05 ECU. This should cover all fuel injected Hisun models, as well as various other Chinese FI engines, as the Delphi MT-05 ECU seems to be the favored ECU solution.
Even though we get actual engine error codes to display on the dash, sometimes we have “pending codes” (not yet confirmed by the ECU) or other intermittent issues that are hard to diagnose, for example a poorly connected sensor that may give intermittent false readings, or a sensor that’s putting out bad date, but not bad enough for the ECU to realize.
The setup requires 2 cables, which are available for around $25 combined, a PC with a USB port, and some charityware software called “HUD ECU Hacker”. This gives the same functionality as the $300 dealer code scanner for a fraction of the price.
In searching I found info about HUD ECU Hacker, but I have yet to see info anywhere about how to hook it up to a Hisun, so I took the leap and bought some cables, and made it work. I will show a step by step of how to do so in post two.
I will be breaking this down into 2 posts:
Delphi ECU Info & Overview (This post) System setup & use Delphi ECU Info (Skip ahead to the next post if your eyes glaze over technical details)
The Delphi MT-05 ECU was developed to allow small engines to use fuel injection. A fuel injection system requires feedback from various sensors to operate efficiently. This feedback allows the adjustment of ignition timing, fuel injection volume, etc to efficiently and cleanly produce the most power possible from a given engine.
The MT-05 ECU has a number of sensors that are required for proper functioning including; Coolant temp, crankshaft position, intake temp, intake pressure, exhaust O2, throttle position, as well as some other optional sensors that are used on more complex vehicles.
From the sensors the ECU adjusts: Fuel injector timing/pulse, Idle air control valve, and ignition coil
The Delphi MT-05 puts out diagnostic data, however it is not ODB2 like a modern car, where is where it gets tricky reading it. There are three options, there is an old 16 bit piece of software Delphi has that is not able to run on a modern computer, there is the motorscanner tool for dealers ($300), or there is freeware HUD ECU Hacker with the proper cables.
I installed a new GY6 150cc engine in a Bull Dog Pup 200 and when I put it in drive, it grinds for a second and then runs fine. Works great when i place it in reverse. Could it be from it idling too high? Any help would be greatly appreciated.
Okay everyone, need some help here. I got my 2014 Bennche Bighorn 700 from my father inlaw. He has had it since new and as far as I know never had any problems with it until recently. It began with it being hard to start and having to give it some throttle for it to start up. Then it wouldn't stay running once it did start. If you go to start it, it will fire right off and only run for a split second and then die. If you give it some throttle it will start and stay running as long as your foot is on the pedal. While it's running its pretty rough and backfires. Here is a list of everything I've done so far. Initially I checked compression and it was low. I changed the cylinder, piston and rings. Took the head apart cleaned and laped the valves. Checked timing a few times. Adjusted the valves. New spark plug. Checked the air filter, it was fine. New battery. Changed the fuel pump because of a broken fitting. Changed the fuel filter, lines and fuel injector. Dumped the old fuel and put new in. Changed the air idle control, TPS, MAP sensor, Voltage Regulator, ECU and harness. I was getting codes 31, 107, 113 and 122 on the display. Once I changed the ECU no more codes have been displayed but still have the same issues. All fuses look good and as far as I can tell Grounds are good unless there are some I can't find. I'm at a loss here. Not really sure where to go. Compression was better after everything I did but I don't remember the numbers. I'll have to check it again if someone thinks that could be the issue. Any help would be greatly appreciated!