CAPA know how to make a buck.

I don't know if it works the same as the SCT (US) version, which CAPA resell???

Yes it behaves the same...

Hmm. With all this PCM version and Revision stuff floating around, I did some analysis on some captures I had lying around and came up with some new info today.

It appears that just about all modules have data available in a few PIDS that allow diagnostics tools to get revision information. I thought it might have been harder to get than this, but once I found these PIDS, I pretty much found that all modules had data in them - ISO (ABS, RCM, PAM) and CAN (Everything else)

The PIDS are:

E200 - Software Version (Number and Date)
E205 - Not sure yet - maybe CAN provisioning Level?
E217 - Module Part Base NUmber (eg 12A650 for PCM)
E219 - Part Version suffix (AA, AB etc)
E21A - Part version prefix (3R23 etc)
E231 and E232 - Module Serial Number


To issue these queries on ELM:

atspa6 for CAN
atspa3 for ISO

atshaaa (where aaa is the module you're querying in can - 7e0 for PCM, 720 for IC etc There's a list in this thread at the start.) or
atshaabbcc (aa = 64, bb = dst module, cc = test id)

ath1

22xxxx - where xxxx is one of the PIDS above.

Interpreting the data is a bit tricky, and doing ISO work isn't straight forward because Ford don't seem to adhere to ISO correctly.


Lukeyson

Today's discoveries:

(1) How to enable/disable the HDC Jewel in the IC. Still researching enabling HDC in the ABS Module though.
(2) How to Enable/Disable support for the Park Aid Module in the BEM
(3) How to enable or disable the clock in the ICC.

#3 is interesting, because in later firmware versions of the ICC, it's possible to have the clock on the Dual-Zone ICC screens - which wasn't an option in the earlier versions. Which is why we have the dash-clock on Fairmonts and the Ceiling clock on Terri's.

Would be useful for guys who want dash-pods instead of the dash-clock....


Lukeyson

Luke, so the earlier firmware can be made to show the clock or you would need an update to the firmware to allow it?

Lemme know the ICC clock code!!!!

FPV's got the roof mount clock too. s**t cheap quartz LCD thing that it is.

Yep.. I've realized that I will probably loose my clock with my ACC conversion.. I'd be interested in seeing if the firmware needs an update or what as well.

Well, according to ASL on Ford Forums, there's nothing that can be done about the firmware.

However, one possibility may exist - it's an internal Ford utility called PTDIAG, and there are rumours that it has found it's way onto the net somewhere.

I'd welcome any sort of discrete 'forensic' information on it's whereabouts....


Lukeyson

Oky Doky.

atsp6
ath1
atsh727

Enable 2E 8000 02
Disable 2E 8000 00
Read 22 8000

of course, this is Read by PID/ Write by PID, with a PID of 8000. This PID has other stuff in it, some settable, some not.


There's also a setting for enabling the Clock in the top right hand corner when in Video mode, however I've never toyed with changing this value:

PID 8004

Bit 2 = Clock Overlay Display on Video


Lukeyson

Last edited by Lukeyson on Tue Mar 11, 2008 10:04 pm, edited 1 time in total.

B E A utiful.

Will post back with my results. (BF1 GT-P)

I just had 'barrel' ask me to clarify the Police Mode setting.

The Offsets for writing to the ODO are:

00 = ODO
01 = Body/Fuel - and maybe more. The data in here is very cryptic and we've been working for awhile to decode it without much luck.
02 = Police Mode 'Offset' for fine tuning the digital speedo (usually 00)
03 = A bunch of settings. I'll focus on this.

To write by offset remember that it's 3B. So go back to the original post for setting up an ELM to write to the IC.

For offset 03, low series clusters use 1 byte, and high series clusters are 2 bytes.

Byte 1:

Bit0 = Seatbelt Reminder
Bit1 = TCM Jewel
Bit2 = Police Mode
Bit3 = May be the Shift Alert - but not sure yet

Bute 2:

Bit0 = HDC Jewel
Bit1 = DSC Jewel.

So if you have a low series cluster, when you read offset 03 you type '2103' and you should see something like:
727 03 61 03 03

It''s the last byte we're interested in here.

A high series cluster with DSC on and TC off may look like:
727 04 61 03 01 0E

It's the last 2 bytes we're interested in.

03 HEX = 11 Binary (Or 00000011).
01 HEX = 1 Binary (0000001), 0E HEX = 1110 Binary (00001110)

(Note: I don't yet know what the bits 2 and 3 do yet in the high series Byte. )

Bit 0 is LSB - or Least Significant Bit - and is the rightmost bit. To enable Police Mode you need bit 2 set to 1, so thats 00000111, or 07 Hex. So you write this as:

3B0307 for low or
3B03050E for high

Hope this helps.


Luke

Thanks for that Luke,

When i enter 3b0307 (low series)

It activates police mode as it should, but it also turns on the traction control light on the cluster. My ute doesn't have traction control so I have not seen this light on before.

It doesn't really bother me if the light stays on but if I can run police mode without it on, then that would be great.

OK, so don't turn it on.

Do a 3b0305 instead.

Given that 05 is 00000101, that should leave bit1 as 0 turning off TCM.


Lukeyson

Looks like the older ICC's don't have the code for the clock in their firmware.

N.A. f150 parameters in InstrumentCluster are 2 bytes AF BF
Bit =A7 BSM present=1, A6 Overspeed warning present=1, A5 Outside Air Temp & compass present=1, A4 A/C ETAC=1, A3 Outside air units Celsius=1, A2 Belt Minder=1, A1 Speedometer Scaling=1, A0 Flex Fuel =1, B7 Auto Lamp delay=1, B6 Autolocks=1, B5 Transit Mode=1, B4,B3,B2 unused, B1 & B0, 00 Small 28gal tank, 01 Mid 33 gal tank, 10 Large 28 gal Tank, 11 Large 33 gal Tank. I have not figured how to write to it from HSCAN bus yet. (Learning C# for small project I need to write). I have dumped the eeprom and write to it directly. Once I can get into the eeprom thru HSCAN, I will see the offset from the data in eeprom. Hope to use this method to figure out offset in PCM as well.

Last edited by Hard_ware on Sat Dec 22, 2007 8:39 am, edited 2 times in total.