Australian VX Commodore

[GML-VX]

Could somebody provide some help, please. I want to but a nice package to work on my Commodore VX 2002(Australia). I have downloaded the demo version V4 and have problems establishing coms, I think.

I built a small circuit using a MAX 232 dual line TRX. I seems to work OK and it echos back any chars I send it. I tested it with my BERT up to 38400 with no errors.

I connected it to pin 9 on the ODBC2 plug under the steering (used gnd and +12 v from there too).I get a steady flow of data on my serial analyser with the IGN off.

I get data flow with the IGN on. I think there is something wrong with the
serial data but don't know. At times I select a Macro to run and the DTC pane turns green and there are a number of items listed in it. They never seem to change.

What I want is the dials page to work. I tried the other model Commodore XLM files but the software complained more about incorrect data headers.

I have had a CRO on the data and it looks about right for TTL, swings right down to ground both ways and up to +5. Frequency looks close but haven't measured the bit width.

The top of the screen is just clicking the green stop sign icon. Sometimes (without my understanding)it runs indefinitely usually just a second or so with "Com timeout expecting header frame".

The green chatter icon and the one next to it both seem to display data.. I have noticed the engine fan and the Engine check lamp do go on, which seems to indicate some sort of communication on the ECU bus.

I am really stuck and would appreciate any help.

I have tested the car with a CARMA scantool and it work OK.


I get with the green stop icon

Start macros:Engine data
Synchronizing ALDL comms....
waiting for heartbeat:$08,$55$A3
waiting for ALDL bus silence for 50 ms
send: $f5,$57,$01,$01,$82
comm timeout expecting header byte

with Display chatter and Auto detect chatter I get loads of green data all byte of $(hex?) with the occassional "comm timeout expecting header byte"

Graeme

[Blacky]

Try changing the Module ID from $F5 to $F7 for each of the three defined messages:

1. ECM/PCM_$01
2. ECM/PCM_$04
3. ECM/PCM_$0A

Regards
Paul

[Blacky]

See image for the value to change.
Paul

[GML-VX]

I check that variable you mentioned. It was set to $F5 I changed it to $F7, no change. I took the time to get some proper blocks of data. I ran tests with the ignition off then on then with the engine running. There seems to be some 2way comms but it halts after a few seconds. My Vx is from 200 not 2002 as i thought, if that makes any difference.

Your help is appreciated!

Thanks,

Graeme

Ignition OFF -run aldl

40:05.312: Start macro: Engine data and DTCs: DATADTC
40:05.328: Synchronising ALDL communications...
40:05.328: Waiting for heartbeat: $08,$55,$A3
40:05.328: Waiting for Aldl bus silence of at least 50ms...
40:05.388: Start reading frame
40:05.398: Aldl frame header byte: $11
40:05.398: Aldl frame length byte: $5C
40:05.413: Recv: $11,$5C,$00,$00,$0D,$00,$0B,$00,$00,$7B
40:05.413: Finished reading frame
40:05.413: Frame: 0 = $11,$5C,$00,$00,$0D,$00,$0B,$00,$00,$7B
40:05.413: Start reading frame
40:05.413: Aldl frame header byte: $ 8
40:05.413: Aldl frame length byte: $55
40:05.413: Recv: $08,$55,$A3
40:05.413: Finished reading frame
40:05.413: Frame: 1 = $08,$55,$A3
40:05.413: Found heartbeat: $08,$55,$A3 - ALDL synchronised
40:05.413: Send suspend command: $F1,$56,$08,$B1
40:05.413: Start writing frame
40:05.413: Send: $F1,$56,$08,$B1
40:05.413: Finished writing frame
40:05.413: Wait 10 ms after writing, before reading...
40:05.423: Start reading frame
40:05.425: Aldl frame header byte: $F1
40:05.425: Aldl frame length byte: $56
40:05.425: Recv: $F1,$56,$08,$B1
40:05.425: Finished reading frame
40:05.425: MAX232 echo: $F1,$56,$08,$B1
40:05.425: Wait 10 ms after writing, before reading...
40:05.435: Start reading frame
40:05.435: Aldl frame header byte: $F1
40:05.435: Aldl frame length byte: $56
40:05.435: Recv: $F1,$56,$08,$B1
40:05.435: Finished reading frame
40:05.435: Start writing frame
40:05.435: Send: $F7,$57,$01,$01,$B0
40:05.435: Finished writing frame
40:05.435: Wait 10 ms after writing, before reading...
40:05.445: Start reading frame
40:05.446: Aldl frame header byte: $F7
40:05.446: Aldl frame length byte: $57
40:05.446: Recv: $F7,$57,$01,$01,$B0
40:05.446: Finished reading frame
40:05.446: MAX232 echo: $F7,$57,$01,$01,$B0
40:05.446: Wait 10 ms after writing, before reading...
40:05.456: Start reading frame
40:05.560: Com timeout: Expecting frame header byte
40:05.627: Aborting request due to previous error
40:05.630: Start writing frame
40:05.630: Send: $F7,$57,$01,$00,$B1
40:05.630: Finished writing frame
40:05.630: Wait 10 ms after writing, before reading...
40:05.640: Start reading frame
40:05.641: Aldl frame header byte: $F7
40:05.641: Aldl frame length byte: $57
40:05.641: Recv: $F7,$57,$01,$00,$B1
40:05.641: Finished reading frame
40:05.641: MAX232 echo: $F7,$57,$01,$00,$B1
40:05.641: Wait 10 ms after writing, before reading...
40:05.651: Start reading frame
40:05.747: Com timeout: Expecting frame header byte
40:05.775: Aborting request due to previous error
40:05.777: Start writing frame
40:05.777: Send: $F7,$57,$01,$00,$B1
40:05.777: Finished writing frame
40:05.777: Wait 10 ms after writing, before reading...
40:05.787: Start reading frame
40:05.788: Aldl frame header byte: $F7
40:05.788: Aldl frame length byte: $57
40:05.788: Recv: $F7,$57,$01,$00,$B1
40:05.788: Finished reading frame
40:05.788: MAX232 echo: $F7,$57,$01,$00,$B1
40:05.788: Wait 10 ms after writing, before reading...
40:05.798: Start reading frame
40:05.904: Com timeout: Expecting frame header byte
40:05.931: Aborting request due to previous error
40:05.933: Resuming normal ALDL communications...
40:05.933: Send resume command: $F1,$56,$09,$B0
40:05.933: Start writing frame
40:05.933: Send: $F1,$56,$09,$B0
40:05.933: Finished writing frame
40:05.933: Wait 10 ms after writing, before reading...
40:05.943: Start reading frame
40:05.945: Aldl frame header byte: $F1
40:05.945: Aldl frame length byte: $56
40:05.945: Recv: $F1,$56,$09,$B0
40:05.945: Finished reading frame
40:05.945: MAX232 echo: $F1,$56,$09,$B0
40:05.945: Wait 10 ms after writing, before reading...
40:05.955: Start reading frame
40:05.955: Aldl frame header byte: $F1
40:05.955: Aldl frame length byte: $56
40:05.955: Recv: $F1,$56,$09,$B0
40:05.955: Finished reading frame
40:05.962: Stop macro: Engine data and DTCs: DATADTC

[Blacky]

Ignition OFF -run aldl

If you had ignition off, then it probably won't work. You need ignition on to communicate with the engine controller.

Regards
Paul

[Blacky]

VT V6 uses ID $F5
VX V6 uses ID $F7
Model year 200 is probably a VT.
What's the 4th digit of your VIN?

Regards
Paul

[GML-VX]

I tried with the ign off and on and with the engine running. Results were the similar. I will have to wait to get the VIN it was made in 2002 and sold as VX. I did try other files(VT etc).

I could not attach all the data I had. Which would be the most helpful for working this problem out. I can send new datasets.

Thanks again

Graeme

[GML-VX]

VIN = 6H8VXX69A1L674***

I ran the test again being sure to have the IGN ON use VX xlm file

14:07.481: Start macro: Engine data and DTCs: DATADTC
14:07.484: Synchronising ALDL communications...
14:07.484: Waiting for heartbeat: $08,$55,$A3
14:07.484: Waiting for Aldl bus silence of at least 50ms...
14:07.732: Start reading frame
14:07.808: Aldl frame header byte: $40
14:07.808: Aldl frame length byte: $58
14:07.808: Recv: $40,$58,$DD,$49,$06,$3C
14:07.808: Finished reading frame
14:07.808: Frame: 0 = $40,$58,$DD,$49,$06,$3C
14:07.808: Start reading frame
14:07.808: Aldl frame header byte: $41
14:07.808: Aldl frame length byte: $63
14:07.831: Recv: $41,$63,$00,$00,$00,$6C,$4A,$00,$00,$70,$F8,$22,$0 0,$00,$10,$00,$0C
14:07.831: Finished reading frame
14:07.831: Frame: 1 = $41,$63,$00,$00,$00,$6C,$4A,$00,$00,$70,$F8,$22,$0 0,$00,$10,$00,$0C
14:07.831: Start reading frame
14:07.843: Aldl frame header byte: $A8
14:07.844: Aldl frame length byte: $55
14:07.844: Recv: $A8,$55,$03
14:07.844: Finished reading frame
14:07.844: Frame: 2 = $A8,$55,$03
14:07.844: Start reading frame
14:07.844: Aldl frame header byte: $A9
14:07.844: Aldl frame length byte: $57
14:07.844: Recv: $A9,$57,$00,$00,$00
14:07.844: Finished reading frame
14:07.844: Frame: 3 = $A9,$57,$00,$00,$00
14:07.844: Start reading frame
14:07.861: Aldl frame header byte: $20
14:07.861: Aldl frame length byte: $55
14:07.861: Recv: $20,$55,$8B
14:07.861: Finished reading frame
14:07.861: Frame: 4 = $20,$55,$8B
14:07.861: Start reading frame
14:07.861: Aldl frame header byte: $21
14:07.861: Aldl frame length byte: $58
14:07.867: Recv: $21,$58,$BC,$22,$46,$63
14:07.867: Finished reading frame
14:07.867: Frame: 5 = $21,$58,$BC,$22,$46,$63
14:07.867: Start reading frame
14:07.876: Aldl frame header byte: $D8
14:07.876: Aldl frame length byte: $55
14:07.876: Recv: $D8,$55,$D3
14:07.876: Finished reading frame
14:07.876: Frame: 6 = $D8,$55,$D3
14:07.876: Start reading frame
14:07.896: Aldl frame header byte: $90
14:07.896: Aldl frame length byte: $55
14:07.896: Recv: $90,$55,$1B
14:07.896: Finished reading frame
14:07.896: Frame: 7 = $90,$55,$1B
14:07.896: Start reading frame
14:07.896: Aldl frame header byte: $91
14:07.896: Aldl frame length byte: $58
14:07.902: Recv: $91,$58,$18,$00,$00,$FF
14:07.902: Finished reading frame
14:07.902: Frame: 8 = $91,$58,$18,$00,$00,$FF
14:07.902: Start reading frame
14:07.914: Aldl frame header byte: $A0
14:07.914: Aldl frame length byte: $55
14:07.914: Recv: $A0,$55,$0B
14:07.914: Finished reading frame
14:07.914: Frame: 9 = $A0,$55,$0B
14:07.914: Start reading frame
14:07.914: Aldl frame header byte: $A1
14:07.914: Aldl frame length byte: $57
14:07.914: Recv: $A1,$57,$08,$00,$00
14:07.914: Finished reading frame
14:07.915: Frame: 10 = $A1,$57,$08,$00,$00
14:07.915: Start reading frame
14:07.929: Aldl frame header byte: $11
14:07.929: Aldl frame length byte: $5C
14:07.943: Recv: $11,$5C,$FF,$00,$4D,$00,$00,$00,$00,$47
14:07.943: Finished reading frame
14:07.943: Frame: 11 = $11,$5C,$FF,$00,$4D,$00,$00,$00,$00,$47
14:07.943: Start reading frame
14:07.943: Aldl frame header byte: $40
14:07.943: Aldl frame length byte: $58
14:07.943: Recv: $40,$58,$DD,$49,$06,$3C
14:07.943: Finished reading frame
14:07.943: Frame: 12 = $40,$58,$DD,$49,$06,$3C
14:07.943: Start reading frame
14:07.954: Aldl frame header byte: $41
14:07.954: Aldl frame length byte: $63
14:07.970: Recv: $41,$63,$00,$00,$00,$6C,$4A,$00,$00,$70,$F8,$22,$0 0,$00,$10,$00,$0C
14:07.970: Finished reading frame
14:07.970: Frame: 13 = $41,$63,$00,$00,$00,$6C,$4A,$00,$00,$70,$F8,$22,$0 0,$00,$10,$00,$0C
14:07.970: Start reading frame
14:07.979: Aldl frame header byte: $ 8
14:07.979: Aldl frame length byte: $55
14:07.979: Recv: $08,$55,$A3
14:07.979: Finished reading frame
14:07.979: Frame: 14 = $08,$55,$A3
14:07.979: Found heartbeat: $08,$55,$A3 - ALDL synchronised
14:07.979: Send suspend command: $F1,$56,$08,$B1
14:07.979: Start writing frame
14:07.979: Send: $F1,$56,$08,$B1
14:07.979: Finished writing frame
14:07.979: Wait 10 ms after writing, before reading...
14:07.989: Start reading frame
14:07.990: Aldl frame header byte: $F1
14:07.990: Aldl frame length byte: $56
14:07.990: Recv: $F1,$56,$08,$B1
14:07.990: Finished reading frame
14:07.991: MAX232 echo: $F1,$56,$08,$B1
14:07.991: Wait 10 ms after writing, before reading...
14:08.001: Start reading frame
14:08.001: Aldl frame header byte: $F1
14:08.001: Aldl frame length byte: $56
14:08.001: Recv: $F1,$56,$08,$B1
14:08.001: Finished reading frame
14:08.001: Start writing frame
14:08.001: Send: $F5,$57,$01,$01,$B2
14:08.001: Finished writing frame
14:08.001: Wait 10 ms after writing, before reading...
14:08.011: Start reading frame
14:08.012: Aldl frame header byte: $F5
14:08.012: Aldl frame length byte: $57
14:08.012: Recv: $F5,$57,$01,$01,$B2
14:08.012: Finished reading frame
14:08.012: MAX232 echo: $F5,$57,$01,$01,$B2
14:08.012: Wait 10 ms after writing, before reading...
14:08.022: Start reading frame
14:08.122: Com timeout: Expecting frame header byte
14:08.513: Aborting request due to previous error
14:08.518: Start writing frame
14:08.518: Send: $F5,$57,$01,$00,$B3
14:08.518: Finished writing frame
14:08.518: Wait 10 ms after writing, before reading...
14:08.528: Start reading frame
14:08.529: Aldl frame header byte: $F5
14:08.529: Aldl frame length byte: $57
14:08.529: Recv: $F5,$57,$01,$00,$B3
14:08.529: Finished reading frame
14:08.529: MAX232 echo: $F5,$57,$01,$00,$B3
14:08.529: Wait 10 ms after writing, before reading...
14:08.539: Start reading frame
14:08.638: Com timeout: Expecting frame header byte
14:08.665: Aborting request due to previous error
14:08.667: Start writing frame
14:08.667: Send: $F5,$57,$01,$00,$B3
14:08.667: Finished writing frame
14:08.667: Wait 10 ms after writing, before reading...
14:08.677: Start reading frame
14:08.678: Aldl frame header byte: $F5
14:08.678: Aldl frame length byte: $57
14:08.678: Recv: $F5,$57,$01,$00,$B3
14:08.678: Finished reading frame
14:08.678: MAX232 echo: $F5,$57,$01,$00,$B3
14:08.678: Wait 10 ms after writing, before reading...
14:08.688: Start reading frame
14:08.794: Com timeout: Expecting frame header byte
14:08.821: Aborting request due to previous error
14:08.824: Resuming normal ALDL communications...
14:08.824: Send resume command: $F1,$56,$09,$B0
14:08.824: Start writing frame
14:08.824: Send: $F1,$56,$09,$B0
14:08.824: Finished writing frame
14:08.824: Wait 10 ms after writing, before reading...
14:08.834: Start reading frame
14:08.835: Aldl frame header byte: $F1
14:08.835: Aldl frame length byte: $56
14:08.835: Recv: $F1,$56,$09,$B0
14:08.835: Finished reading frame
14:08.835: MAX232 echo: $F1,$56,$09,$B0
14:08.835: Wait 10 ms after writing, before reading...
14:08.845: Start reading frame
14:08.845: Aldl frame header byte: $F1
14:08.845: Aldl frame length byte: $56
14:08.845: Recv: $F1,$56,$09,$B0
14:08.845: Finished reading frame
14:08.853: Stop macro: Engine data and DTCs: DATADTC

[GML-VX]

I have managed to get some coms going. I made some changes to the interface to improve the HF response and it started to work!.

I used the VX XML file with $F7 as the ID in the macro.

Thanks for your help.

One thing still not quite sure of is the DTC codes.

I select the Macro and it seems to run. the DTC engine icon on the top of the pane goes green. And the icon list appears

The icons on that page that are always green (engines). They are not a complete list of the DTC and never change. I know they are not the DTC codes from checking it with a scanner

What I see is:

RH O2 missing CEL(what is CEL?) True etc
ECT high True
ECT low True
ECT unstable True
ECT circuit False
Linear EGR flow check False
TPS stuck False
TPS high True

Makes no sense. The ALDL and dashboard panes run OK.
Any tips?

Seems to be a great program. What did you write it in. Not planning to release the source?

Is there a combination license for V5 and the later Vs for ODB2?

Cheers,

Graeme

[Blacky]

I have managed to get some coms going. I made some changes to the interface to improve the HF response and it started to work!.
I used the VX XML file with $F7 as the ID in the macro.
Thanks for your help.

Glad you figured that out - I would not have been much help with that.

One thing still not quite sure of is the DTC codes.

I select the Macro and it seems to run. the DTC engine icon on the top of the pane goes green. And the icon list appears

The icons on that page that are always green (engines). They are not a complete list of the DTC and never change. I know they are not the DTC codes from checking it with a scanner

Makes no sense. The ALDL and dashboard panes run OK.
Any tips?

The DTCs are limited to only displaying the first 8 in Eval mode.
All DTCs are listed, the SET DTCs will be displayed with a red icon.
See the user manual: "Relaese Notes -> Pro vs Eval" section to see the differences between Pro and Eval versions.

Seems to be a great program. What did you write it in. Not planning to release the source?

Thanks, although it is fairly primitive compared to the current V7 software for OBDII. It's written in Delphi (so is EFILive V7). No plans to release the source.

Is there a combination license for V5 and the later Vs for ODB2?

No

Regards
Paul