14CUX diagnostic software (libcomm14cux / RoverGauge)

C

cmb

Active member
Mar 17, 2009
29
0
NH
Hi all,

For a while now, I've been working on diagnostic software for the 14CUX. It's entirely free and open source (licensed under GPLv3), it will run on both Linux and Windows, and you can check it out here:

http://code.google.com/p/rovergauge

To connect to the ECU, you'll need to modify an FTDI USB-to-serial converter. I explain this in detail here:

http://code.google.com/p/libcomm14cux/wiki/HardwareInterface

If anyone has a chance to try it out, let me know -- I'd love to hear what you think.

--Colin
 
carlosz

carlosz

Well-known member
Apr 20, 2004
581
0
Annandale,Va
CMB thanks for the heads up, I have the eas software and cable for the rr classic the old eas and the 14 cux share plug styles, I believe the way the eas wire is pined out should work straight up with the 14 cux.
I attempted to download your software but for some reason, I was unsucessful, it seems the link takes you all over but with out actually finding the programm.
Am I missing something... Im a rover technician and use autologic on a daily basis so I should be able to test them side by side.
Carlos
 
C

cmb

Active member
Mar 17, 2009
29
0
NH
carlosz said:
CMB thanks for the heads up, I have the eas software and cable for the rr classic the old eas and the 14 cux share plug styles, I believe the way the eas wire is pined out should work straight up with the 14 cux.
I attempted to download your software but for some reason, I was unsucessful, it seems the link takes you all over but with out actually finding the programm.
Am I missing something... Im a rover technician and use autologic on a daily basis so I should be able to test them side by side.
Carlos
Click to expand...
I'm not familiar with the EAS cabling, but I would guess that it won't work with my software. The problem is that standard serial ports on a PC can't be set to 7812.5 baud, which is the speed used by the ECU. The FTDI converter works because it can set arbitrary baud rates.

There's a "Downloads" tab near the top of the project page. Here's a direct link to the list of downloadable files:
http://code.google.com/p/rovergauge/downloads/list

If you use Windows, then you'll want the file "rovergauge-0.2.2-Windows.zip".

--Colin
 
R

robertf

Well-known member
Jan 22, 2006
4,792
363
-
I've been meaning to check this out. Got another source for the diagnostic plug?
 
C

cmb

Active member
Mar 17, 2009
29
0
NH
robertf said:
I've been meaning to check this out. Got another source for the diagnostic plug?
Click to expand...

If you mean the 5-pin TTS connector, I'm afraid not -- British Wiring (http://www.britishwiring.com) is the only supplier I know of.

Of course, you don't need to keep the original connector in the vehicle. You could cut off the TTS one and replace it with a DB9, for example.
 
C

cmb

Active member
Mar 17, 2009
29
0
NH
sven said:
Yeah but they dont reset adaptive idle, etc.
Click to expand...
I have no plans to write a GEMS library, mainly because OBD2 systems are massively more complicated than a fuel-only system like the 14CUX.

The best way to go about reversing the GEMS serial protocol would be by sniffing the traffic from a Testbook / T4. I'm a little surprised that no one has done this already, but I suppose that they're rather hard to find for a reasonable price.
 
R

robertf

Well-known member
Jan 22, 2006
4,792
363
-
ok, tried it out. excellent work. I've been toying with 14cux tuning for years but haven't been able to figure out the diagnostics.

Any idea what the data in the fuel table correlates to? AFR, Injector pulse width, VE? I'm guessing IPW look up tables. Have you managed to figure out what check sum strategy they are using and what location its at?

The interface could use some more gauges like o2 and fuel trims, but its a great start.
 
C

cmb

Active member
Mar 17, 2009
29
0
NH
robertf said:
ok, tried it out. excellent work. I've been toying with 14cux tuning for years but haven't been able to figure out the diagnostics.

Any idea what the data in the fuel table correlates to? AFR, Injector pulse width, VE? I'm guessing IPW look up tables. Have you managed to figure out what check sum strategy they are using and what location its at?

The interface could use some more gauges like o2 and fuel trims, but its a great start.
Click to expand...
The fuel map contains unadjusted injector pulse width values. The highlighted location in the map is actually just a closest-match display; the true initial value is a weighted average of four map locations in a 2x2 grid. This averaged value is then further adjusted by the fuel-map scale factor (displayed just above the map). This scale factor is typically the value that changes the most when a map is adapted for a different engine displacement. After it's scaled, the value is adjusted further depending on coolant temperature, fuel temperature, etc. This is all just the simple open-loop processing; there's a lot of other code that runs when processing feedback from the O2 sensors.

In the PROMs we've looked at, the checksum is forced to be 0x0001 by adjustment of the first value in the PROM (mapped in at $C000.)

I'm working on a white paper that will attempt to explain the programmatic flow of the code in the PROM.

--Colin
 
R

robertf

Well-known member
Jan 22, 2006
4,792
363
-
ptschram said:
Any possibility of modifying the fuel maps???
Click to expand...


yes. It is eprom based, so on the fly changes require hardware. I use this http://www.moates.net/ostrich-20-the-new-breed-p-169.html?cPath=64

I have run my rover off of one before, but since I didn't know the checksum location all it was good for was setting the prom error code.

Once you tune it with the eprom emulator you burn a traditional eprom chip and its tuned.
 
You must log in or register to reply here.
Top Bottom