[hasenwerk]

Bitte entschuldigen Sie mein Englisch auf diesem Deutschen Forum.

I am trying to get a 2009 2.0L TDI CBAA engine running in my Volkswagen T3. I have figured out all the necessary CAN information with the exception of the Cruise Control (GRA).

From my traffic sniffing, I have discovered 0x03A = GRA and that it is 3 bytes of information. However when I feed the ECU this information, it doesn't change that status of the switches when I monitor measuring block 006 in VCDS.

0x0 = 0x2+"offset"
Off = 0
On = -1
(-) = -3
(SET) = -21
etc . . .

0x1 = Binary representation of switch:
00000000 = no buttons pressed
00000001 = ON
xxxxxx1x = CANCEL
xxxxx1xx = Decelerate
xxxx1xxx = Accelerate
xxx1xxxx = Set
xx1xxxxx = Resume

0x2 - Clock
Repeats: 20, 52, 84, 116, 148, 180, 212, 244, 20, 52 . . .

0x3 - Always "0"


What else is needed for the ECU to use my inputs for GRA???

Pedal inputs are all correct (all show 0). Speed is shown in the first block of 006. Accelerator pedal input is working . . . I have a strong feeling it is depending on another address as well... I'm stuck!

mit freundlichen Grüßen!

[majonez]

Hello and welcome.
From my notes the cruise control system buttons are at ID 0x289. Source of the message is at comfort bus (steering wheel module) and then this message is translated to ID 0x38A by the gateway and forwarded to the powertrain bus later.

Code:

byte0: XOR checksum byte1: 00000000 = CCS off 0000000? = stuck ON 000000?1 = pressed OFF 00000?01 = decelerate (-) 0000?001 = accelerate (+) 000?0?01 = decelerate (-) stuck 00?0?001 = accelerate (+) stuck ?0000000 = ACC coded byte2: 0000000? = set 000000?0 = resume 0000??00 = coding. 11 = GRA im blinkerhebel, 01 = GRA im drittenhebel 0x?X = counter from 0x00 to 0xF0 byte3: 00000100 = distance- 00001000 = distance+

[hasenwerk]

Lieber Leser, Du hast keine ausreichenden Rechte um weiter zu lesen, weiter hier.