Capturing Tech1 Commands VS V6

[The1]

sounds interesting brett

[VL400]

It would be good to start an ADX for BCM and ABS logging. Will get my VT bench working and try on that too. From your ealier text file you know whats in the "F0: DATA LIST", so if you can either work out from the tech-1 where in the payload each item is or by trial and error - ie open a door and see which bit changes.

From the captured BCM packet...
Device ID of BCM: F1
Number of bytes: 6F (it is 6F - 55 = 1A = 26bytes which includes the mode byte)
Mode: 1
25 byte Payload: 0, C, B, 45, 84, A0, 7D, 0, C, 0, 0, 20, FE, FF, 0, 8, 9C, 2D, 0, 1, 0, F0, 30, 0, 0
CheckSum: 87

[The1]

ok this is in efilive this is me with the tech1 sitting in drivers side window status, then me pressing the drivers window up button on the center console.

[VL400]

I can see 5 different frames in there...
$F1,$6F,$01,$00,$0C,$0B,$41,$84,$A0,$7A,$00,$0C,$00,$00,$20,$FE,$FF,$00,$08,$9C,$45,$00,$01,$00,$F0,$30,$00,$00,$76
$F1,$6F,$01,$00,$0C,$0B,$41,$84,$A0,$7B,$00,$0C,$00,$00,$20,$FE,$FF,$00,$08,$9C,$45,$00,$01,$00,$F0,$30,$00,$00,$75
$F1,$6F,$01,$00,$0C,$0B,$41,$84,$A0,$7B,$00,$0C,$00,$00,$20,$FE,$FF,$00,$08,$9D,$45,$00,$01,$00,$F0,$30,$00,$00,$74
$F1,$6F,$01,$00,$0C,$0B,$41,$84,$A0,$78,$00,$0C,$00,$00,$20,$FE,$FF,$00,$08,$9C,$45,$00,$01,$00,$F0,$30,$00,$00,$78
$F1,$6F,$01,$00,$0C,$0B,$61,$84,$A0,$78,$00,$0C,$00,$00,$20,$FE,$FF,$00,$08,$9C,$45,$00,$01,$00,$F0,$30,$00,$00,$58

The bytes that changed from frame to frame and the binary equiv...
41 = 0100 0001
61 = 0110 0001

7A = 0111 1010
7B = 0111 1011
78 = 0111 1000

9C = 1001 1100
9D = 1001 1101


I would have thought the battery voltage would have changed, the likely one for this would be the 78 and 7A (if it follows the usual X/10 like the ECU that would be 12v and 12.3v respectively). The 61 byte (bit 5) is possibly the window status as that is when the battery voltage is also lower.

[The1]

the tech1 spits out so much info when the laptop and tech1 are connected at the same time, even alot of the time just sitting in a menu on the tech1 it's spitting out line after line like a wild dog.

[The1]

heres what i get when reading all modules at once for dtcs, definatly says to me srs isn't on the same bus

[charlay86]

I believe that the SRS has it's own dedicated bus, it is on a different pin of the DLC.

[VL400]

Here are the start of a VS and VT BCM monitor ADX. The VT one works and battery voltage (the only thing defined so far) changes correctly as I change the bench supply.

[brett_jjj]

According to the VS wiring diagrams the SRS system is completely seperate to the ABS, BCM and ECU.The ABS,BCM and ECU all share one serial data pin in the ALDL connector,which is pin 9.The SRS uses a different pin for its serial data.Not sure which pin,but the wire that goes to the ALDL plug from the SRS module is a white/blue wire..Just check out which pin in the ALDL connector has a white/blue wire going to it and thats the SRS serial data wire.Looking at the wiring diagram, the SRS module has diag enable on it as well as a serial data line.I wonder if the SRS error codes can be flashed up on the SRS dashlight like the ECU and ABS codes can?The SRS diag enable is a brown wire that goes to the ALDL connector as well as the SRS dashlight according to the diagram.I cant see why the SRS module would have diag enable on it if it couldnt go into diagnostic mode,unless the SRS module has to be put into diag mode before it can send data over its serial line..

[charlay86]

Data Link Connector Terminal Identification

Pin 1: Secondary UART - SRS
Pin 5: Signal Earth
Pin 6: PCM Diagnostic "Test" Enable
Pin 9: Primary UART - ABS BCM PCM
Pin 12: ABS Diagnostic "Test" Enable
Pin 13: SRS Diagnostic "Test" Enable
Pin 16: Battery Voltage