Working With Diagnostic Data Cable & Software
 

UPDATE (June 2020)

The PCHUD software is now completely obsolete & has been superseded by the fully functional HUD ECU Hacker software.

Thanks goes to Raptorix (Elmüsoft) for creating & developing this new software.


Detailed description & download for the HUD ECU Hacker can be found here

https://netcult.ch/elmue/HUD%20ECU%20Hacker/


************************************************** *******

LINK UPDATE (2018)
See post 164 & 165 for PCHUD download

This is an all in one download that includes

PCHUD with instructions

"Clear fault codes" software with instructions

A guide to making your own data connection using a vag com cable

and other info




Requirements
----------------

1/
Data Cable
Attachment 2726

Taobao link

http://item.taobao.com/item.htm?id=39520023502

so far the only one known to work


2/
PC or laptop running Win7 (32bit), Tested

May work with other O.S. NOT 64bit

----------------------------------------------

The diagnostic software comes indirectly with the cable. If this is not the case, below is a link to the software I received (PCHUD)

https://mega.co.nz/#!skACACIT!Kv8o9g...KYCK-q08TiBUs8

The software is in Chinese, below is a link, in the download are files and instructions translated in to English. I will go in to more detail of these files further on in this post

https://mega.co.nz/#!wwgkDAwR!QzhC2n...cYKva96H8_KMuY


Installing USB drivers and running software
-------------------------------------------------

The translated instructions included in my link should do the trick, so i will only write an overview here.

The setup.exe for the USB drivers can be found in the "USB数据线驱动程序及安装指南" folder

Run the setup without the cable connected to your laptop

No installation is required for the PCHUD software

The folder "德尔福电脑检测软件（PCHud_Chinese)" needs to be renamed to PCHUD, then just place the folder in the root of the harddrive .

I used D:\ as described in the instructions, but probably would work else where if you edit the pchud.ini

Check the pchud.ini anyway to make sure the directory entries are correct.

---------------

Launch and experiment with the software without anything connected (run hud.exe)

The important data to load is the .par file, this holds all the parameter data. The VARI54CN.PAR file

is the one that you can see being used in the Delphi Scan Tool Manual (included in my download).

Unfortunately the VARI54CN.PAR is in chinese but i have done my best at translating it (3.par)

The .hud files are user configuration files for the gauges. You are able to create new ones from within the program.

so to get you started use -

3.hud with 3.par

or

1.hud with 1.par ( slightly different translation of VARI54CN.PAR)

Translating or editing of .par files yourself i will cover in a later post, but i have included a hex/text editor that will be required in my download)

----------------------------------------------------------

The Chinese TR125 (QJ125GY-16A) uses the Delphi MT05 , i have included the EFI section of the manual in my download.

The images show them using the MT05common.PAR as their parameter file.

For this use 2.hud with 2.par (slight variation on the MT05common.PAR)

----------------------------------------------------------

connecting up
---------------

with ignition off plug the cable into the bike, USB to laptop and run PCHUD.

make sure comports are configured, bike kill switch is to "run" turn on ignition.

"com time out error " should go after a short while, if not start engine and all should be good







apologies for the length of, post now completed ;)

Thanks for posting this excellent thread, Kat. :tup:

My fifth order with Taobao is ready for shipment, but I am delaying it, because I am adding this cable to my order. ;)

Thanks Spud,

I'm still adding more stuff to my first post over the next few hours, fitting it in around other things i have to do, will mark it as completed when done :tup:

I also added the cable to an existing order, the agent received the cable very quickly, so in the end it was waiting on components to arrive for my existing order that held up the shipment.

I had 2 orders shipped at nearly the same time, this one got through, the other got caught in customs. so i will have to pay duty on that one :cry:

Translating,Editing .par files
 

Open the .par file with M.S. Word , select other encoding Chinese simplified(EUC).
From here you can translate by copying in to google translate.

For editing ( software provided in 1st post download)

Open .par file , in the right hand column you will see sections of code strings.

select view, character set, International, Chinese simplified so you can match the chinese characters .

Note the start point , change back to ACSll and edit

TIP - 00 in the left hex column = nothing.

** this all takes forever to do**

If your editing one of my .par files , they are already in English. :tup:

Simulating A Fault
 

I disconnected the O2 sensor to see what would happen.

as you can see in the pic it displayed that the fault light was on and recorded at fault number of 49.

This means from the table a P0031 fault, Oxygen sensor Heater high voltage.:hmm:

Not quite what I was expecting but at least it was the right component
http://i85.photobucket.com/albums/k7...psmsnwgfsw.jpg
http://i85.photobucket.com/albums/k7...psey1cx1tj.jpg

As a total nube what does this do for me and the bike? Is it for going in and changing parameters to make it a BMW or KTM? :)) Need a 101 wannabe geek coarse for changing any of it. How and why? The rest of the mechanical things I can screw up all by myself. rj

It can be used as an aid for diagnosing faults and monitoring your electronic fuel injection system. This is what I'm interested in :)

The ability for changing parameters which will effect the way your bike runs is yet unknown.

The parameters I have mentioned in my posts are only related to the diagnostic software (PCHUD) on your PC so that it understands the data it is being feed from the bike.

Also its well cheap :D

You are certainly going to get more data from a computer than you will from an OBD2 scanner. :tup:

What???

Don't apologize for an awesome contribution like that! You're the man. :tup:

He's not the Grand Poobah for nothing. ;)

:hehe:

Not that this is apples to apples, but I have a wifi OBDII connector in my truck, and I can access it with a free app on my iPhone. It allows me to choose from several monitoring options, and I'm most interested in temperature.

The gauge in my truck is somewhat vague, and it's in Metric. I still think in Fahrenheit when it comes to cars, and I like to know what my engine is doing when I'm towing my holiday trailer.

The connector and software for an RX3 will allow you to pinpoint trouble down the road, because it will tell you if you have a faulty throttle position sensor, oxygen sensor or whatever else. A very wise tool investment.

VW cable (twenty-odd yuan) mod :http://www.chyangwa.net/forum.php?mo...uthorid=652893

On the XT660 the fault code is displayed on the dash automaticly once a fault is detected.
you instantly know what bit just stuffed up yer day....
Dose the RX3 do the same?

you can change some of the injection setting from the dash in dialoge mode...
TPS / CO etc




.

My Nissan Juke (built in the UK!) has an option in the settings to change between MPH/KPH C/F Miles per Gallon / Litres per Kilometer etc.

Maybe an option buried somewhere deep in the OBC?

Nope. Old '99 GMC truck with analogue gauges. Not the fancy modern type.

I was wondering the same thing. Is there more than a check engine light on the RX3?

The Siemens microprocessor of the RX3 dashboard is not designed to interface with, nor configure the Delphi MT05 ECU. However, the engine fault light of the Siemens dashboard does receive a signal from the MT05 ECU. Therefore, the engine fault light might flash an error code if the ignition key is switched on/off for three cycles, as described below.

Fault light is located on the dashboard. Under normal circumstances, open the key, the fault light will be on, which means that the EFI system is in power state and can work.

After the engine is started, the fault light is off, which means there is no fault; conversely, if the engine is started the fault light is still on for long, which said the EFI system is not working properly, and there is a failure needing to troubleshoot.

Directly use fault light flashing on the instrument for diagnosis.

After confirming there is a fault, if open and close the key for three times, namely, open —close—open—close—open the key, the fault light will come to a flash code corresponding to the fault. And then through the fault code table identify the corresponding fault. With fault light reading fault, the rules of the flash code are as follows, for example, if the fault is the intake air pressure sensor is disconnected or the signal-side pin shorts to battery negative, after the key is opened and closed for three times the fault light will first flicker for 10 times on behalf of 0, flicker for 1 times on behalf of 1 after an interval of 1.2 seconds, flicker for 10 times again on behalf of 0 after an interval of 1.2 seconds, and after an interval of 1.2 seconds flicker for 7 times on behalf of 7 , namely, P0107. It is thus clear that other figures from 0 to 9 are expressed by the times of the flicker of the fault light except that figure 0 is expressed by flicker for 10 times. If there are other fault codes, such as fault P0201, which means there is a fault in the front cylinder injector, the fault light will continue to flicker P0201 fault code in 3.2 seconds after finishing P0107; if there is no other fault, the fault light will flicker P0107 and P0201 circularly, and then check the fault code table for related faults.

http://i442.photobucket.com/albums/q...psnszhywba.jpg

I discovered the information above in an online manual which contains information for diagnosing the Delphi MT05 EFI system. :tup: The Delphi EFI information begins on page 133 of the manual, which is shown at the following link.

http://www.manualslib.com/manual/816...age=138#manual

If you click the 'download' button at the top of the webpage, you can save the entire manual to your computer. :tup:

The manual describes three methods to diagnose the EFI system.

1) Engine warning light
2) Motorscan Diagnostic Tool
3) PCHUD software on computer

:yay:

Thanks for posting the good information, HB. :tup:

According to that thread, we can also adapt the following cable. :)

http://www.ebay.com/itm/VAG-COM-KKL-...275&rmvSB=true

http://i.ebayimg.com/00/s/NzYxWDc1Mw...DrQ~~60_12.JPG

Where can we find the following connector?

http://attachments.motorfans.com.cn/...WmO0Kh4731.jpg

On the XT code 55 is the last one yer want to see....
55 = ECU is toast

Similar to some http://item.taobao.com/item.htm?id=40884598106 Yamaha CDI
http://item.taobao.com/item.htm?id=43132525510
---
http://item.taobao.com/item.htm?id=36657258931
Furukawa https://www.furukawa.co.jp/tukuru/pd...pcon_01rfw.pdf

I disconnected the O2 sensor to create a fault so the "engine" light would stay on when the bike was started.

Tried this method a few times and got absolutely nothing :doh:

Went on to do a few other things to my bike which involved disconnecting the battery.
The battery was out for about 1/2 hour.
Re fitted the battery, turned the ignition on and there it was flashing at me with the correct code :hmm:

I haven't as yet repeated this so I'm not sure which part of what I did made the difference.

One more point is that I know I already have this fault code stored in its fault history. So not sure if it is reading this one or the fresh fault I created.:shrug:

But it does prove that the flashing fault light does work :tup:


Soon I will be adding a new section to the first post

" What the hell is all this EFI stuff doing" &

" WTF are these gauges telling me"

A very basic guide for myself and anyone else , so check back ;)

Forget the battery bit, it was just a coincidence .

Seems you have to wait 60 seconds before the light starts to flash.

Its difficult for me to test properly now as I can't seem to clear historic fault codes so it flashes these :hmm:

Anyone For Graphs ?
 

Using the log program that comes with PCHUD

In seconds along the bottom starting at 0.23sec to 215.8 sec

http://i85.photobucket.com/albums/k7...pszkmabdbp.jpg

http://i85.photobucket.com/albums/k7...psp7jhptat.jpg

http://i85.photobucket.com/albums/k7...psq8iuuck7.jpg

http://i85.photobucket.com/albums/k7...ps8aoeatot.jpg

Cheers for the info Katflap, just tried the ignition on off on off on test.....got 10 flashs 5 flashs 10 flashes 5 flashs coming up in a loop, anyone know what fault this means? Is it 0505? Will be booking first service soon so see what the dealer says .....


Once again thanks to Katflap, got the code from a file included in a download from one of your PCHUD links, 0505....idle control error. Makes sense now as when I start off from cold starts although no more stalling at the moment the first few minutes riding at idle the revs are all over the place 1800 to 3000rpm until the engine warms up. Faulty stepper motor maybe? Bad or wet connection possible.....try the WD40 spray fix first and see if it clears.

Yes, page 81 of the Delphi Small Engine EMS Service Manual specified code P0505 as an 'idle speed control error.' I suspect you are correct, and the problem is related to the stepper motor.

Vic,

I could be wrong here but if the light stays on after you have started the engine you will see the current fault flashed then followed by the historic faults when doing this test.

If the light goes out after the engine is started then when you do the test, historic fault is flashed.

At one point I disconnected the input plug to the ignition coil and turned the ignition on without even attempting to start the engine .

This now flashes as a historic fault code.

I'm still trying to find out how to clear the historic fault code from its memory. PCHUD has this ability but at present it is "greyed out".

Have you tried to adjust the idle speed using the adjusting screw. The reason I ask is that from some of the stuff I've been reading gives the impression that the idle speed should only be adjusted using software and the data connection.
:)

The idle speed was adjusted by the dealer before I picked the bike up so don't know how it was done. I will ask on its service. Strange how its gone from initially stalling to uneven idle when cold. The engine check light did come on during my last ride home and now I know why getting the code.

That sucks, Vic,

With the light being on whilst riding home it definitely seems like a current fault.

The idle adjustment thing was just a thought. I'm sure the dealer would have done it all correctly.

I hope they can sort it for you quickly :tup:

I've dug out an old laptop running Windows XP and installed PCHUD and got it running using Katflaps HUB and PAR files.... will be testing it with my homemade lead and an old ELM327 KW2000 interface sometime today. You never know it just might work :-)




Tried my interface and lead this afternoon but no joy. On a plus side pulled the connectors off the stepper motor, reconnected them securely and the bikes running fine now from cold start no more surging or uneven idle, must have been a poor connection. Another thing I noticed if you just turn the ignition on and wait 60 seconds the engine fault light starts flashing any stored codes without using the on, off,on,off,on ignition cycle.

Mine are more for entertainment purposes than information.

That's why I'm now using EOBD-Facile on my iPhone. I feel much better knowing the temperature.

I need help with the driver setup, I downloaded these files and I don't see the USB folder.
Installing USB drivers and running software
-------------------------------------------------

The translated instructions included in my link should do the trick, so i will only write an overview here.

The setup.exe for the USB drivers can be found in the "USB数据线驱动程序及安装指南" folder

Run the setup without the cable connected to your laptop

ClassicRacer you need to open the 新版电喷检测软件（PCHud_Chinese）及数据线安装方法 folder.....you will find the USB driver folder in there.

I have now tested quite a lot of diagnostic software but PCHUD is still the only one which operates correctly. :cry:

In an earlier post i mentioned that PCHUD seemed unable to clear fault codes. This is still the case, i have been unable to figure out why. :hmm:

Fortunatley i have found a russian diagnostic program that will. :yay:

This is useful because if you leave your ignition on for 60 seconds without starting your engine the MIL light on the RX3 will start to flash historic fault codes even after the initial fault is fixed.

This software will allow you to start with a clean slate.

The software will clear all fault codes but if you have an existing fault this will return after switching your ignition off and then back on again.

Here it is http://www12.zippyshare.com/v/HfiID0fh/file.html (tested on WIN8) - new link

instructions
--------------

Install the program, locate where the program has installed and replace the OpenDiag.exe with the one in the katflap folder.

I have partially translated it to make it useable.

Getting It Up & Running
-------------------------------

plug in your cable in to the bike and laptop

run program

select adapter K-line

settings (f3)

select port or run "find adapter" then "ok"

select ECU (F2)

double click M74 , as shown in pic below

Attachment 2834

select Errors tab

Reset errors button then "ok"

Job done! :)

(All though i've not had any problems, any software that pokes around your ECU could cause damage, so please remember use at your own risk !)



Am I connected ?
--------------------

within 30 seconds of doing the above process data will be seen here
Attachment 2880

or here if you run the equipment definition (f1)
Attachment 2881

Can't get connected ?
-------------------------
try using method 2 then press "tuning initialization" or enter "17" in the "TiniL/TiniH box.

(I had to use method 2 on one laptop but on a different laptop method 1 was fine :hmm:)
Attachment 2882

It is good to hear from you, Kat. :) Thanks for posting the information on the Russian software. :tup:

Good news that you can now clear historic codes!

OBD-II Scanner / 6-Pin Connector and 16-Pin Pigtail
 

My first post. My bike was on the first shipment and has been great. There was an issue with the regulator that I was able to diagnose with the key trick. Steve and Ryan at CSC provided world class customer service and the problem was corrected very quickly. No issues since.

I thought these links might be of interest to anyone looking to make a connection to an OBD-II Scanner. The 6-pin male connector looks to be available domestically through Cycleterminal (Furukawa RFW 090 6-Pin Male Connector) and the OBD-II 16-Pin Pigtail via eBay from China (eBay Item # 301594172330). I hope this is of help whomever might be looking for these items.


http://www.cycleterminal.com/furukawa-rfw-090.html


http://www.ebay.com/itm/301594172330?

Welcome; that is a great first post. :tup: Thanks for doing the research and providing the web links for the connectors. :)

The 16 pin female http://item.taobao.com/item.htm?id=12412865618