AU Scantool Experiments (codes/live data!)

[AUFanboy]

Hi Folks,

I bought a cheap ELM327-based OBDII to USB scantool recently ($20) to play around with getting codes and live data from my AU. I've found some info floating around on fordmods and managed to get code reading working, and am now in the processes of figuring out the live data. I've written a small Windows application for reading and clearing codes which I'll be releasing (freely) soon. Will be using this thread to document my findings, so stay tuned!

The AU is not OBDII compliant and therefore won't work with standard OBDII scantools and software. But it does have an OBDII type connector under the dash and a J1850 PWM data network. It does not support standard OBDII Mode 01 to mode 09 PIDs, codes, etc, but does support some of the extended OBDII modes (mode 13 for getting codes, mode 22 for data). It does not support functional addressing so we need to know the physical addresses of the various modules, but the info for that is out there (PCM is address 10).

First we need to set up the ELM327 to talk to the car using AT commands. This can be done from hyperterminal or any other terminal emulator, see the ELM327 datasheed for more info elmelectronics.com/DSheets/ELM327DS.pdf

ATSP 1

This tells the ELM327 to use J1850 PWM protocol.

ATSH E4 10 F1

This sets the headers which the ELM327 will stick on the front of the messages we send. E4 specifies that we are using physical addressing, 10 is the address of the PCM, F1 is the address of the scantool.

13

This gives a list of codes. The response in my case was:

53 03 50 00 00 00 00

The first byte signifies a sucessfull request (40 + 13). Then the codes are sent as two bytes each. In this case we have one code, 0350, which is ignition coil malfunction. The following four bytes (00) are just fillers.

To clear the codes:

14

Google SAE J2190 for more info on these modes...

By issuing commands to mode 22 we can get live data from the PCM. Mode 22 PIDs are manufacturer-specific, but seems to be similar accross many fords, so there is some info out there. EG, to get current spark advance:

22 11 6B

Response with engine off:

62 11 6B 00 00

62 signifies sucessfull request (40 + 22), then the PID request is echoed (11 6B), then the data is sent, in this case as two bytes. However, there are often scale factors and offsets applied to the data returned. This is the tricky part. Going to have a play this afternoon and will post more later...

[Maka]

G'day AUFanboy, welcome to AFF! Im very interesed in the work you are doing & i dare say many others here as well. Keep up the good work and keep updating your progress.

cheers,Maka

[mik]

yes, welcome to the forum mate, you are a bit braver than i am with computers, but good luck with it all the same.

[Uncle_Ken]

I've been looking at a HUD that supports these:
1.ISO 9141-2(5 baud init,10.4Kbaud)
2.ISO 14230-4 KWP(5 baud init,10.4Kbaud)
3.ISO 14230-4 KWP(fast init,10.4Kbaud)
4.ISO 15765-4 CAN(11bit ID,500Kbaud)
5.ISO 15765-4 CAN(29bit ID,500Kbaud)
6.ISO 15765-4 CAN(11bit ID,250Kbaud)
7.ISO 15765-4 CAN(11bit ID,250Kbaud)
with an OBD II conector
Do you think this would work with an AU?
UK

[AUFanboy]

@Uncle_Ken:

That won't work the the AU unfortunatly, it doesn't support J1850 PWM and most likely only uses standard mode 1 OBD11 commands. The AU is a "special needs" car when it comes to diagnostics and won't work with normal OBDII stuff.

Here are the PIDs that the AU should support, from the Ford AUII workshop manual. These are meant to be accessed using the Ford NGS tester ($$$$).

http://fordforums.com.au/attachment....1&d=1344742345
http://fordforums.com.au/attachment....1&d=1344742433

[AUFanboy]

Here's some data I've found on the net about Ford mode 22 PIDs:

http://www.paladinmicro.com/documents/200304PIDs.pdf

And attached is some data from the Ford Escape Hybrid forums, including some scale factors. Unfortunately it seems many of the AU scale factors and offsets are different.

[AUFanboy]

So I took the PIDs from the documents in the above post and fired them at the AU PCM, and managed to peice most of them together. Still need to work out some scale factors and offsets though. Temperature doesn't quite agree with the values displayed in dash diagnostic mode... seems to be an offset of 10 degrees or so.

Also still missing a few PIDs, notably transmission fluid temp and engine MAP. Currently running a "brute force" scan to test all possible mode22 pids from 0000 to FFFF.

I've got a small app up and running than can log a few parameters to help work things out. Will post it somewhere if anyone is keep to help work out how to decode the data.

Ive attached a spreadsheet with the PIDs I've gotten a response to so far, and some comments on the scale factors/offsets (not sure about a lot of them).

[BHDOGS]

Mate I can follow a few things your saying but most is over my head haha but keep up the good work

[LuciferDarklord]

Has anyone tried FORScan on an AU? I'm not near my car for a few more days so I cant try it. http://www.forscan.org/home.html

[Maka]

Originally Posted by LuciferDarklord

Has anyone tried FORScan on an AU? I'm not near my car for a few more days so I cant try it. http://www.forscan.org/home.html

When you end up testing it on your au please let us know how it goes.

cheers,Maka

[LuciferDarklord]

Will do. It looks fairly basic, wont be a custom built AU tool like AUFanboys. I tried Torque (for android) and it wouldnt talk to the PCM - even when set to J1850 PWM.

[rowan194]

Watching this thread with interest. I'm (very) slowly working on my car computer, which features a forward (and possibly reverse) facing camera with some telemetry at the bottom of the frame. So far I've been planning to keep it simple - km/hr speed (via GPS), L/R indicators, stop lamp, maybe horn to signify an event - but if there was a way to hook into the OBD connector permanently it may be possible to pull out some more interesting data. How cool would it be if the vid capture also showed throttle position, RPM, and the current gear the auto was in?

[parker]

Subscribed!

[auIILTD]

Fanboy, can I assume that you have seen this from this website?

http://www.fordforums.com.au/vbporta...article&id=563

The PIDs that I am able to log (unconfirmed, I have not tried all) though my Quarterhorse strategy are.

ACT air charge temp
AM air flow #/min
AMON airmass/espeed
APT thrt mode flag
ATMR1 time running
BP baro pressure
DASPOT dashpot lb/min
DELPR pfe pressure
DESMAF desired maf idle
DSDRPM des idle rpm
DT12S time pip edge
ECT coolant temp
EGRACT egr percent act
EGRDC egr duty cyc
FNVFS_0X pr solenoid 1x
FNVFS_0Y pr solenoid 1y
FNVFS_1X pr solenoid 2x
FNVFS_1Y pr solenoid 2y
FNVFS_2X pr solenoid 3x
FNVFS_2Y pr solenoid 3y
FNVFS_3X pr solenoid 4x
FNVFS_3Y pr solenoid 4y
FNVFS_4X pr solenoid 5x
FNVFS_4Y pr solenoid 5y
FUELPW1 fuel pw clktic1
FUELPW2 fuel pw clktic2
GRDSRD desired gear
GRLVR shifter pos
IEGO1 hego 1 volts
IEGO2 hego 2 volts
IMAF maf ad counts
INJDLY injector delay
INJON num injs on
IPSIBR isc integrator
ISCDTY isc duty cycle
ISCFLG idle mode flg
ISCKAM0L isc corr d noac
ISCKAM1 isc corr d ac
ISCKAM2 isc corr n ac
ISCKAM3 isc corr n noac
KAMRF1 ltft bank 1
KAMRF2 ltft bank 2
LAMBSE1 stft bank 1
LAMBSE2 stft bank 2
LBMF_INJ1 fflw per inj b1
LBMF_INJ2 fflw per inj b2
LOAD load
N rpm
OFFST shft tab offset
ONOFSOLC on-off sol code
PWM_0_PER_CNT pwm 0 per count
PWM_0_PER_HLD pwm 0 per hold
PWM_0_WID_CNT pwm 0 wid count
PWM_0_WID_HLD pwm 0 wid hold
PWM_1_PER_CNT pwm 1 per count
PWM_1_PER_HLD pwm 1 per hold
PWM_1_WID_CNT pwm 1 wid count
PWM_1_WID_HLD pwm 1 wid hold
PWM_2_PER_CNT pwm 2 per count
PWM_2_PER_HLD pwm 2 per hold
PWM_2_WID_CNT pwm 2 wid count
PWM_2_WID_HLD pwm 2 wid hold
PWM_3_PER_CNT pwm 3 per count
PWM_3_PER_HLD pwm 3 per hold
PWM_3_WID_CNT pwm 3 wid count
PWM_3_WID_HLD pwm 3 wid hold
PWM_4_PER_CNT pwm 4 per count
PWM_4_PER_HLD pwm 4 per hold
PWM_4_WID_CNT pwm 4 wid count
PWM_4_WID_HLD pwm 4 wid hold
PWM_5_PER_CNT pwm 5 per count
PWM_5_PER_HLD pwm 5 per hold
PWM_5_WID_CNT pwm 5 wid count
PWM_5_WID_HLD pwm 5 wid hold
PWM_6_PER_CNT pwm 6 per count
PWM_6_PER_HLD pwm 6 per hold
PWM_6_WID_CNT pwm 6 wid count
PWM_6_WID_HLD pwm 6 wid hold
PWM_7_PER_CNT pwm 7 per count
PWM_7_PER_HLD pwm 7 per hold
PWM_7_WID_CNT pwm 7 wid count
PWM_7_WID_HLD pwm 7 wid hold
PWOFF pw offset in tics
RATCH tp adcnt clthrt
RETINC knk ret incr
RMP1DUR curr ramp1 dur
RMP2DUR curr ramp2 dur
RMP2I5TQMAX max chg ramp2
RMP2I5TQMIN min chg ramp2
RMPI5TQMAX max chg ramp1
RMPI5TQMIN min chg ramp1
SAFTOT spark advance
SHIFT_MODE shift mode
SOL1_DTY_HI snoid1 dc hi
SOL1_DTY_LO snoid1 dc lo
SOL1_PER_HI snoid1 p hi
SOL1_PER_LO snoid1 p lo
SOL12DELDUR snoid12 dly dur
SOL12DELTM snoid12 dly tm
SOL2_DTY_HI snoid2 dc hi
SOL2_DTY_LO snoid2 dc lo
SOL2_PER_HI snoid2 p hi
SOL2_PER_LO snoid2 p lo
SOL3_DTY_HI snoid3 dc hi
SOL3_DTY_LO snoid3 dc lo
SOL3_PER_HI snoid3 p hi
SOL3_PER_LO snoid3 p lo
SOL4_DTY_HI snoid4 dc hi
SOL4_DTY_LO snoid4 dc lo
SOL4_PER_HI snoid4 p hi
SOL4_PER_LO snoid4 p lo
SOL6_DTY_HI snoid6 dc hi
SOL6_DTY_LO snoid6 dc lo
SOL6_PER_HI snoid6 p hi
SOL6_PER_LO snoid6 p lo
SOL6SPDTHRS snoid6 sp thrhd
SOL6TPTHRES snoid6 tp thrhd
SOL7_DTY_HI snoid7 dc hi
SOL7_DTY_LO snoid7 dc lo
SOL7_PER_HI snoid7 p hi
SOL7_PER_LO snoid7 p lo
SOL8_DTY_HI snoid8 dc hi
SOL8_DTY_LO snoid8 dc lo
SOL8_PER_HI snoid8 p hi
SOL8_PER_LO snoid8 p lo
SOLDELDUR slnd delay strt
TCSTRT strtup temp eng
TOT trans oil temp
TP tp absolute
TPPER throttle %(tp)
TPV Throttle Position Voltage
TQ_MAX_ALLOW max allowed tq
TQ_NET calc net eng tq
TQ_SOURCE torque source
TQI5MAX final curr rmp1
TQI5MIN init curr rmp1
TR_DESIRED tq ratio des
TR_SPK_LVL tq ratio spk
VBAT battery volts
VMAF maf volts
VSBAR vehicle speed
WOT_F wot flag


My strategy was written by 5.0 ED. It may be worth a PM to Matt (5.0 ED) if you are looking for assistance. I am sure that he can assist, and at minimum, he can point you in the right direction.

Good luck,
Stu

[auIILTD]

Sorry, copy and paste did not work really well. PIDs are in capitals, Description in lower case.

Stu

[Swedishmoose]

Hmm...

Hopefully there will be a scanning tool available soon for the AU Falcon that can actually read everything (including the tranny).

Has anybody heard of the Autel Maxi Diag 703?


I am not sure if that thing will do te trick...

The Moose

[AUFanboy]

I did a brute force scan off all mode 22 PIDs from 0000 to FFFF - here are the ones that gave valid respones. Also tried the Forscan program linked above - it works! Plugged in and it found the ECU, ABS, airbag module and instrument cluster and could read trouble codes. It can also get the live data, but it's missing a fair few parameters.

2202001,62 02 00 01
2202021,62 02 02 00
2209261,62 09 26 00 ?
2209281,62 09 28 80 ?
2209291,62 09 29 02 ?
22092B1,62 09 2B 34 ?? AC something
22092C1,62 09 2C 00 0D ?? TFT?
22092D1,62 09 2D 7F FF ?
22092E1,62 09 2E 00 EF ?
22092F1,62 09 2F 00 00 ?
2209311,62 09 31 00 ?
2209321,62 09 32 00 ?
2211001,62 11 00 09 FF 00 00
2211011,62 11 01 00
2211031,62 11 03 00
2211041,62 11 04 00
2211051,62 11 05 30
2211071,62 11 07 00
2211231,62 11 23 1A
2211251,62 11 25 FF
2211391,62 11 39 1B
2211411,62 11 41 19 A7
22114D1,62 11 4D B7 00
2211531,62 11 53 00 00 // IAC %
2211541,62 11 54 19 40
2211561,62 11 56 00 00
2211581,62 11 58 80 00
2211651,62 11 65 00 00
2211661,62 11 66 00 00
22116B1,62 11 6B 00 00
2211721,62 11 72 C8
2211731,62 11 73 00 08
2211B01,62 11 B0 00 00
2211B31,62 11 B3 02
2211B51,62 11 B5 00 D9
2211B61,62 11 B6 0A
2211C11,62 11 C1 00 00
2214401,62 14 40 01 95 // MAP, kPa, div 4?
22160D1,62 16 0D 00
2216241,62 16 24 00 1B
22163C1,62 16 3C 01
2216721,62 16 72 00 00
2216861,62 16 86 1D ? AC head pressure switch pressure (psi?)
2216911,62 16 91 00
2216CF1,62 16 CF 00 00
2216E61,62 16 E6 FF FF
2231011,62 31 01 00 ?
2261871,62 61 87 00 ?
22990A1,62 99 0A 3B
22A2131,62 A2 13 00 ?
22A2151,62 A2 15 00 00
22C1151,62 C1 15 33 ? AC something temp?
22C1171,62 C1 17 00 80 0A 00 ??
22C9001,62 C9 00 DE 00 ??? no idea from here down
22C9011,62 C9 01 37 03
22C9021,62 C9 02 F3 02
22C9031,62 C9 03 39 01
22C9041,62 C9 04 00 00
22C9051,62 C9 05 DA 02
22C9061,62 C9 06 00 00
22C9071,62 C9 07 00 00
22C9081,62 C9 08 01 00
22C90B1,62 C9 0B 13 03
22C90C1,62 C9 0C 66 02
22C90D1,62 C9 0D 01 00
22C90E1,62 C9 0E FD 03
22C90F1,62 C9 0F F7 02
22C9101,62 C9 10 00 00
22C9111,62 C9 11 00
22C9121,62 C9 12 00
22C9131,62 C9 13 80
22C9141,62 C9 14 00
22C9151,62 C9 15 02
22C9161,62 C9 16 9E
22C9171,62 C9 17 AD
22C9181,62 C9 18 9A
22C9191,62 C9 19 92
22C91A1,62 C9 1A 00 00
22C91B1,62 C9 1B 80
22C91C1,62 C9 1C 00 00
22C91D1,62 C9 1D 00 00
22C91E1,62 C9 1E 00
22C9201,62 C9 20 B4
22C9211,62 C9 21 80
22C9221,62 C9 22 01
22C9231,62 C9 23 EE
22C9301,62 C9 30 5B
22C9311,62 C9 31 92
22C9321,62 C9 32 53
22C9331,62 C9 33 68
22C9FE1,62 C9 FE 00 00 00 00
22D1001,62 D1 00 01
22E0001,62 E0 00 00
22E1001,62 E1 00 0D 4C

[humpmeimfamous]

Subscribed Subscribed Subscribed Subscribed All the way.
desperate for something like this. I have an au2 LTD 5.0. its a work in progress... i would love to be able to scan for things that need work....

[Gaz]

Fantastic work mate!

Can I ask - is this similar to what you bought?

http://www.ebay.com.au/itm/ELM327-US...item19d2fc77b4

Need to create a bloody paypal account... Been avoiding that for years!

[LuciferDarklord]

Tried FORScan but no go, sometimes it would say that it couldn't communicate with the vehicle, other times it would lock up at the 'trying to connect to vehicle' stage. I tried a few different baud rates but still no go. AUFanboy, did your's work straight out of the box or did you have to fiddle with baud rates? Mines a bluetooth ELM327, AUII XR6 vct manual ute.

[AUFanboy]

I have the USB ELM327 module linked to by Gaz above. It worked straight out of the box with the Forscan program. Make sure you have the ignition on (engine doesn't need to be running though). Also give it some time, takes a minute or so to finish scanning and connecting for me.

I've also ordered a $20 bluetooth version to try with my Android phone. Might be able to get one of the existing apps working using custom headers and PIDs, or write my own.

I'm going to make a list of the useful/interesting PIDs that I've tested and worked out the scaling for here for ease of reference. These are all mode 22 requests, so to test them you can use hyperterminal, set the headers as described in my first post, then type 22 followed by the PID. Here I will list the PIDs, the number of bytes returned, and how to make them into useful units. Also note all the respones from the ECU are in hexadecimal, so have to be converted to decimal first.

1139 - engine coolant/cylinder head temp. 1 byte, multiply by 2 to get degrees farenheit. Then subtract 32, multiply by 5 and divide by 9 to get degrees celcius.

1123 - intake air temp - as above

1141 - fuel injector pulse width - 2 bytes - divide by 100 to get milliseconds

1156 - long term fuel trim percent - 2 bytes - divide by 2.56 then subtract 100

1158 - short term fuel trim percent - 2 bytes - subtract 32768 then divide by 327.68

163C - fueling status - 1 byte - 01 = open loop, 00 = closed loop

116B - timing advance - 2 bytes - divide by 2 to get degrees BTDC

11C1 - vehicle speed - 2 bytes - divide by 320 to get km/h

1165 - engine rpm - 2 bytes - divide by 4

1173 - O2 sensor voltage - 2 bytes - divide by 3200 to get volts

092C - transmission fluid temp - 2 bytes - degrees C (not 100% sure on this yet but it seems about right)

1440 - intake manifold absolute pressure (I6 only) - 2 bytes - divide by 4 to get kPa

1172 - battery voltage - 1 byte - divide by 16 to get volts

More to come when I get a chance to test them!

[auIILTD]

Hi Fanboy.

Great work. In reference to your transmission fluid temp, I have seen this in my logging with my Quarterhorse (on a different strategy to what I am running now). It was in DegF. I also believe that the addresses that you are listing will change dependant on the strategy required for the ECU involved (different catch codes).

Stu

[LuciferDarklord]

Well I had a good play with FORScan again, still no joy. It says it cannot communicate with the vehicle. I tried hyperterminal and it seemed to work ok, got a code '05 00' which seems to be "vehicle speed sensor fault" Cleared the faults, will try again when I get some more patience. BTW I know the ELM327 works OK, I've had it a while and it works with the missus' diesel i30 and my old FG G6 no worries. Its weird because I know I have a decent connection wiith the hyperterminal. Maybe I'll try an older version of FORScan as a new version was released on the 14th of August.

Thanks for the info AUFanboy!

[AUFanboy]

@LuciferDarkload - that's odd, but may be that the FORScan program doesn't like bluetooth. I was using the older version of the program so maybe give that a go. Also the USB ELM327 modules can be had for about $13 including postage from Hong Kong if you can't get it working with the bluetooth.

@auIILTD - thanks for the info on the data available with the quarterhorse. I'm using PIDs exposed over the OBD interface rather than memory addresses in the PCM so they should work with all AUs. I've tested on an AUII Forte I6 and an AUII XR8 so far and the above PIDs work on both (except MAP doesn't work on the V8 of course).

Also what sort of trans temps were you seeing? I'm seeing ambient temps on a cold start, getting up to 70-75 degrees C in urban driving after 25 minutes or so. Couple of hard runs up a steep hill got it up to 87 deg C. That's with the standard in-radiator oil cooler.

[auIILTD]

I just looked at some of my old logs from when the strategy I was running had TOT (Transmission Oil Temp). I never really paid a lot of attention at the time as my focus was on other things, but you may be correct. It may be in DegC? On startup (in Dec) I was seeing values of 27 and values of around 70 (external trans cooler - radiator bypassed).

I find it hard to believe as the EECV is US based and every other measurement is imperial??

Stu

[parker]

Sorry guys, trying to interpret the posts correctly here...
So if I buy a ELM327, could I use it to better diagnose any issues with my AUII I6 and AUII XR8?

[AUFanboy]

@parker - yes you can get trouble codes and live data using either hyperterminal or the FORScan program linked to above. I'd recommend a USB version rather than bluetooth. FORScan can view most of the live data but is still missing a few things. I'm also working on a simple app for viewing the AU-specific data but still need to work some bugs out.

@auIILTD: yeah it seems wierd that TFT is in degC, but from my reading most Fords use PID 1674 for TFT in degF... the AU doesn't respond to 1674 and instead uses PID 092C which doesnlt seem to be used on any other Fords. So maybe Ford Aust. added that one in and changed it to sensible units!

Another odity is MAP. It always reads 405 with key on engine off, which divided by 4 gives 101.25 kPa, standard sea level pressure (i'm at 600 meters so it should be about 93 kPa). Not sure why it doesn't give the current pressure with the engine off. Works fine with the engine running, i get about 93 kPa at full throttle.

[Gaz]

My scanner arrived today.

Had a quick play, given my cold start miss issues interestingly my DTC's are;

Code: P0340
Camshaft Position Sensor (Cylinder Identification) (CMP) <CID> circuit malfunction DTC P0340 is reported if the CMP or its circuit have malfunctioned.

Code: P0350
Ignition coil failure DTC P0350 is reported if there is an failure of an undefined ignition coil or circuit - Reading further into this one ... ELECTRICAL CONDITION - coil signal shorted to ground, Vehicle Power (VPWR) or Signal Return (SIGRTN), coil pack faulty or damaged, faulty or improper coil signal connection, improper signal from Crankshaft Position Sensor (CKP)

Given my CMP and Coil packs are new, and the P0350 is coil pack related, but can be caused by CKP issues, and both sensors do have a multi meter reading, more investigation is needed in the wiring I think.


Just need to get a laptop with a working battery so I can go for a drive and log some sensors, pity CMP and CKP aren't supported by ForScan.

Here's a snip of the logging on sensor values

[AUFanboy]

@Gaz - I think P0350 is a "catch all" code thrown when the ECU detects missfiring/rough running but doesn't know why. Your MAF readings look about right for a v8 (assuming engine at idle) and the O2s are switching ok (maybe a bit slowly but they are ignored on cold start anyway). What do the long term fuel trims look like? Should be within +/- 10%.

Have heard of a few AU V8s with cold start missfires. If it's not ignition related (assuming you've tried new plugs, leads, coils) then it's probably insufficient enrichment in open-loop warmup mode. A few things I can think of - make sure coolant temp sensor and intake air temp sensor read roughly ambient temp after sitting overnight. Check the MAF readings on cold start - maybe it's reading low until it warms up a bit.

I've also received a OBDII Bluetooth adapter (v-gate scan brand - $20) and got it working the the Torque Pro Android app ($5). The standard OBDII gauges etc don't work but custom PIDs can be entered. Here's how to set it up:

Plug the BT dongle into the car and turn ignition on. Go to the phone's settings menu and pair the bluetooth device.

Install Torque Pro and go to the settings menu - OBD2 Adapter Settings. Tick the Faster Communication option and tick the Don't Calculate MPG/Fuel option (it won't work cause it tries to use standard mode 01 PIDs which the AU doesn't support). Under bluetooth settings select the device you just paired.

Create a new vehicle profile. Most of the settings in here don't really matter but the important ones are near the bottom. Set the OBD2 protocol to SAE J1850-PWM. Under the "very advanced" setting at the bottom enter the configuration string as follows:

ATSHE410F1

Click save. Then you need to enter the custom PIDs. Go settings/manage extra PIDs then add custom PID. Enter the mode and PID as described a few posts above. E.g. for MAP: under the Mode and PID setting enter 221440

set min/max to 0 and 102, and set equation to (A*256+B)/4 , and OBD Header to Auto.

Then go to Realtime Information (from the start screen) and delete all the default gauges. Add a new gauge and set it to use the PID you just entered, and it should work.

[Gaz]

Thanks AUFanboy...

The CKP sensor is reading fine and I note that ForScan uses the CKP for RPM display, which reads fine. The CMP was curious as it's new, unless I've installed it slightly advanced/retarded, but my miss was present before I changed it anyway.

I've unplugged the ECU to confirm the catch code (22CA) so the DTC's have been erased, but I've just gone for a 10 minute drive to see if they have returned and will go out and check soon (pain in the *** as my laptop battery is stuffed).

It passed the KOER test fine, however the KOEO test doesn't run, there's a loud click the fans spin and then pops up with something along the line of unable to complete, make sure parameters are correct.

Looking at the full log my #1 o2 sensor is a lot more jumpy than the #2 so they are probably due for replacement.

Will have to wait for a while for the long term fuel trims as the ECU has been disconnected. However this could make sense as when you first reset the computer the cold start issue isn't as bad and gets worse the next startup.

Would be nice to be able to see cmp and ckp readings on oscilloscope but do I read it right as it only detects faults and can't output the values?