pcmhacking.net

Hey all,

I haven't yet wrapped my head around creating custom commands, so can someone check what I've collected? I am trying to add commands to the VX/VY adx to clear as many DTCs as possible, so that I can use TunerPro as a scan tool.

So far I have:

CLEAR PCM DTC: 0xF7 0x57 0x0A 0x00 (Auto checksum, 2s compliment)
CLEAR BCM DTC: 0xF1 0x57 0x0A 0x00 0xAE (As is, no checksum)
CLEAR ABS DTC: 0xF9 0x57 0x0A 0x00 0xAE (As is, no checksum)
AIRBAG RESET: 0xFA 0x56 0x0A 0xA6 (As is, no checksum)
BLM RESET: 0xF7 0x68 0x04 0x00 0x00 0x00 0x00 0x08 0x00 (Auto checksum, 2s compliment)

How much of this is correct? And is there any more commands that people can give me?

Cheers, Matt

The PCM DTC reset command should be....
0xF7 0x56 0x0A <checksum>

I think the BCM and ABS also use the same size message for a DTC reset.


BLM reset byte of 0x08 looks correct but you will likely need to add the extra bytes for a valid message size....
0xF7 0x68 0x04 0x00 0x00 0x00 0x00 0x08 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 <checksum>

Might also want to add a mode 4 clear so the PCM goes back to normal afterwards....
0xF7 0x68 0x04 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 <checksum>

It'd be great if you can post up your adx when its completed to contribute back to the site

Thanks guys. I still have trouble getting my head around the message strings and the byte sequences. So should the reset commands use 0x56 or 0x57?
So far I understand that F7, F1 and F9 are the PCM, BCM and ABS identifiers respectively, the rest is a mystery to me. I am also assuming that everything should be set to auto checksum and the given checksums deleted?

The main reason for all this is that I have started an auto elec traineeship and our workshop's scan tool has a busted LCD. But we have I think 4 VX/VY commodores including mine that we work on, and we need to scan and reset codes. And yes I will share the ADX once these are in. It is going to need some reviewing by everyone though.

Yeah the first byte is the device ID - as you say the PCM, BCM, ABS etc, and the next byte is the length of the packet. If you can count hex (0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F, 10, 11, 12... etc), or use a calculator that has programmer mode/hex (eg windows calculator) you can do it. So the 2nd byte is 52 plus the length. So to go the other way, 68-52 (hex) = 16 bytes (so windows calculator in programmer mode in hex -> enter 16) then hit dec for decimal and it converts to 22, so thats 22 bytes long and the last byte is the checksum. Either enter the checksum manually or get tunerpro to add it, but consider if tunerpro is adding it then thats one more byte so you need to enter one less. Just while on the subject - generally speaking hex is denoted with a $ or 0x, so 68 is usually considered decimal, but $68 or 0x68 is a sign that it should be read as hex.

Hi guys, just wondering if someone has an .ADX to clear the ABS light on a VX please?

have a look at the enhanced adx's i think i added some to them, but if people would like more let me know.

The cluster is F2

The1 wrote:have a look at the enhanced adx's i think i added some to them, but if people would like more let me know.

The cluster is F2

Thanks for that info... just one thing - where do I find the enhanced adx's ? (sorry newbie here)

Thanks again