![]() |
Rx3 fault code look up prog
1 Attachment(s)
I've made a little program , for my self, for looking up the engine management fault codes.
You can input the flashing light (hex) codes and the PCHUD (dec) codes. The example below shows the P031 code being entered. The result gives a discription of the fault and where to find the relevant info in the included manual. The included manual is for a large mower engine that shares quite a number of Engine management components as our RX3. I do intend to test some of the values given in this manual when I get time. For now please only use as a guide. The program needs no installation, You just need to run it. https://mega.nz/file/Ngs2hRaL#4bNsDC..._8ndVy2fuOF9nA :tup: Update:- Download now only contains the manual etc. See post #8 for the code look up program http://www.chinariders.net/showpost....85&postcount=8 Attachment 7124 |
Katflap, you're an amazing resource to RX3 riders. Thanks for your contributions.
|
Quote:
however, some of the hat tricks human being has pulled on the tech information scale have been near incredible. |
Testing The Manual part 1
Tested on an RX3 that is running well with no errors
In the manual It states, before doing anything else, to verify That the ECM is powering up. The procedure is on page 49. In the procedure it refers to the connector pins of the ECU, these can be found on page 38 & 39. The pins appear to be correctly labelled. My results from following their procedure are - Step 1, 12.94v (stated range 12.2v - 13.5v) Step 2, 12.6v (stated range 12.2v - 13.5v) Step 3, 0 ohms ( stated range below 2 ohms) Step 4, 0 ohms ( stated range below 2 ohms) --------------------------------------------------------- J2-18, voltage comes directly from the battery J2-15, voltage comes from the Ignition switch via the "engine run" switch. This particular wire also provides the voltage to energize the fuel pump relay. J2-2 & J1- 9 , go to ground. this first test seems good :) http://i85.photobucket.com/albums/k7...psa7inyh8v.jpg |
Testing The Manual part 2
Tested on an RX3 that is running well with no errors
Testing the procedure for P031/P032 , O2 voltage high/low (page 52-53) Firstly, the O2 connector is labelled correctly :tup: step2, "use a test light", on page 14 it suggest to use a test light that draws no more than 0.3A, I found a bulb rated 3W for the job. It draws 0.26A. It Illuminated as brightly as when connected directly to the battery. (stated - Illuminates brightly) step3, 12.16 v ( a bit low :hmm:) , (stated range 12.2-13.5v) step4, " connect to J2-17", this is not possible as it is plugged in to the ECU. I tested point "C" on the O2 sensor connector, it connects directly to "J2-17". 4.78v (stated range 4.20v- 4.95v) step5, 4.74v (stated range 4.20v- 4.95v) http://i85.photobucket.com/albums/k7...pswaqgpqld.jpg http://i85.photobucket.com/albums/k7...psmowaxgc4.jpg |
Testing the manual part 3
1 Attachment(s)
Tested on an RX3 that is running well with no errors
( pins are correctly labelled) Testing the procedure for P0107 Map Sensor low voltage (page 54-55) ------------------------------------------------------------------------------- step2, Cycled fault code P0108 & P0112 while running but when re assembled no current code remained. step3, 4.96 v (stated range, above 4v) Testing the procedure for P0108 MAP sensor high voltage (page 56) ---------------------------------------------------------------------------- step2, Cycled fault code P0107 & P0112 while running but when re assembled no current code remained. step3, 4.96v - (stated range, above 4v) Testing the procedure for P0112 MAT sensor Low temp indicated (page 57 -58) ---------------------------------------------------------------------------- step2, 4.8v (stated range, above 4v) step3, 4.94v (stated range, above 4v) Testing the procedure for P0113 MAT sensor high temp indicated (page 59) ---------------------------------------------------------------------------- step2, 4.96v (stated range, above 4v) Attachment 7210 |
Kat,
As always, thanks for doing the great research, and sharing your knowledge with us. :tup: I successfully downloaded the manual. :tup: However, my anti-virus software detected a trojan horse virus associated with the look up program. :ohno: |
1 Attachment(s)
Quote:
A lot of antivirus programs are not too clever and will shout Trojan at every horse in town. :ohno: Here’s a link explaining a little about the problem in this instance. http://www.hide-folder.com/overview/false-positive.html Anyhoo, Nobody likes even a whiff of Trojan mentioned on their computer even if it is a false-positive, myself included. My little program is just a visual basic script inside a “wrapper” that creates the “exe” file. The reason I put it inside a wrapper was , ironically , to help prevent it being tampered with by the wider web, where possibly some malicious script could be added. It will work perfectly well without a wrapper but because a VBS script is vulnerable , on the wider web a “virus” script could be added and distributed as my work , I chose not to upload it in this format. So the simple solution is for people to make it themselves , this is really easy to do Requirements- 1/ Any computer running a version of Windows 2/ make sure you have file extensions visible. Steps – 1/ Copy the script below to notepad Code:
Title = "RX3 Delphi MT-O5 ECU FAULT CODE LOOK UP v2 - by katflap" 3/ rename the extension of your new notepad file from .txt to .vbs 4/ then just "click" your new "vbs" file to use :tup: Attachment 7599 |
Thank you, Kat. I just followed your instructions, which took 5 minutes or less to complete, and the program is working great. :tup:
|
Quote:
I would like you to help me with the Software to read the error codes of my Zongshen RX3. |
So, what does a P0132 error code actually mean? Bad O2 sensor? Or something else?
Charles. |
Quote:
|
Right right. But what does this diagnosis mean? Bad 02 sensor or bad maf/mat or something else?
Bike was running lean, not rich. Big flat spots. But then it was idling at 2500-3000rpm. Charles. |
Quote:
In your case, the O2 sensor is outputting a high voltage, what voltage exactly I can't say without a multimeter or an oscilloscope, but definitely more than .5 volts if I had to guess, since .45 indicates an "ideal" combustion mixture. This could be because the bike is genuinely running rich, which causes the O2 sensors to output more voltage, thereby signaling the ECU to subtract fuel via the short term and long term fuel trims. If so, that could be causing your lean condition and weird high idle. No way to know for sure until you get your diagnostic stuff, set it up, link up to the bike, and see what the ECU has to say. I just received mine yesterday, by the way. I haven't had the ambition to work out in the garage due to the heat and humidity, so I can't say yet whether or not it actually works. I also need to get one of my old Windows 7 netbooks upgraded to Windows 10, so that I can run the diagnostic software. When you get yours up an running, the HUD ECUHacker software will come in very handy, since it will display those data PIDs mentioned, allowing you to see exactly what the ECU is seeing, which will help you decypher what is going on. When you link up, check the short and long term fuel trims - yours should be negative if the ECU is seeing a rich condition from the O2 sensor. Also, look at you MAP sensor values, since manifold pressure is used as a surrogate for engine load; high vacuum, which occurs at idle, causes a low MAP sensor signal to the ECU, which will in turn cut fuel, since the engine is not under load. Note: A vacuum leak can throw off the MAP signal, so be sure to check for intake manifold and throttle body vacuum leaks before you go and condemn your existing MAP sensor as bad. |
I already waved an unlit propane torch around the intake, with no change in behavior. One of those big brush-clearing torches. It's enough propane to stop an EX500 motor in under a second when waved around the airbox intake. And nothing budged on my RX3.
Charles. |
All times are GMT -4. The time now is 01:48 PM. |
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.