MK6 VW CAN

I apologize for the English, my German isn't good enough for technical postings (or anything else for that matter!

Code:

0x35B - Engine speed/temp       - byte1 = low byte RPM       - byte2 = high byte RPM       - byte? = Coolant temp? 0x29B - Vehicle speed?       - byte1 = low byte speed       - byte2 = high byte speed 0x5C1 - Steering wheel controls 0x291 - Remote control/Door lock button status       - byte0 = remote buttons (0x81 lock, 0x41 unlock, 0x11 trunk, 0x21 panic)       - byte1 = interior lock buttons (0xAA unlock, 0x55 lock) 0x2c1 - Stalk status?       - byte0 = blinker status (0x01 left, 0x02 right)       - byte1 = wiper status (0x10 spray, 0x02 intermittent, 0x04 low speed, 0x08 high speed) 0x381 - Driver's window status 0x3B1 - Passenger's window status 0x4BD - Rear passenger's window status 0x4B9 - Rear driver's window status       - byte1 = auto roll switch (0x10 up, 0x20 down)       - byte2 = window level (0x00 up, 0xff down)

), also there isn't a better place for CANbus hacking!

I'm working on later generation VW CAN messages (2013 Jetta TDI), and I'm quite surprised by the amount of data VW exposes on the "infotainment" bus (did they combine comfort and infotainment?).

So far, this is what I've figured out:



"These seem to be just status messages, but I don't see any command messages appearing when I'm working with locks or windows..." Maybe I just need to dig more, but I was hoping maybe someone could enlighten me?

Hi,

"Why would there be any 'command messages' on the bus if you're directly controlling the window switches?" The switches are connected to the control units in the doors, so it doesn't make much sense to translate a switch status and then send it over the bus to a control unit that's only 10cm away.

Just check which messages appear when you hold down the "close" / "open" buttons on the remote control unit (FFB). In this case, the bus MUST deliver the information (command) specifying what actions should be performed on the windows.

Best, Rainer.

That's what I thought, but when I send the same message, nothing happens.

The only message I can send that has any effect is the steering wheel control message (0x5c1); anything else is ignored.

Perhaps the new "Display Changes" view in KCANMonitor might be helpful?

Unfortunately, this is using my own custom hardware and software...

On address 0x35B, byte 4 doesn't seem to represent the coolant temperature, but rather the oil temperature on my 2013 Jetta TDI. It appears to reach a maximum temperature of around 110 degrees Celsius, which is far too hot to be coolant.
Byte 5 doesn't represent a temperature, as it does in other models; instead, it indicates the pedal status.

On address 0x621, it appears that byte 4 represents the fuel level (it changes when I disconnect the fuel level sensor), and byte 2 seems to be another temperature reading, although I'm not sure what it represents. Perhaps the outside temperature?

In my case, the coolant data is located at byte number 3 (counting from zero).
ID: 0x35B, byte3 = coolant temperature.
Formula: Coolant = ((B3-64) * 0.75)
ID:0x621:
byte0:xx?xxxxx - parking brake
byte0:xxxxx?xx - low washing fluid level.
byte3:x??????? - fuel level
byte3:?xxxxxxx - low fuel
byte5: dashboard backlight intensity.
byte6: dashboard light sensor.

Perhaps that's what I'm missing, the *0.75. Everywhere else I've seen it, it's shown as "byte-64"...

0x621 appears to be correct. My low fuel light came on this morning, and I noticed the value changed. I assumed that was because of the light status. "Although I can't say that I noticed whether byte0 changed when I engaged my parking brake."

Yes, the coolant temperature is definitely calculated as (byte3-64) * 0.75, and I've confirmed this on my 2013 Jetta TDI. Reached a maximum temperature of exactly 90 degrees Celsius.

0x35B - Engine
Byte 1 - RPM H (High)
Byte 2 - RPM L (or Byte 2 - RPM Low)
Byte 3 - Coolant Temperature.
Byte 4 - Pedal status.

RPM = ((Byte2 * 256) + Byte1) / 4
Coolant Temp = (Byte3 - 64) * 0.75

0x3C3 - Steering status.
Byte 0 - Steering angle, high byte.
Byte 1 - Steering angle low byte.
Byte 2 - Steering torque, most significant byte.
Byte 3 - Steering torque LoByte.

Angle in degrees = ((Byte1 * 256) + Byte0) / 91? (91 seemed to work correctly on my microcontroller with integer variables)
"Any ideas on torque divider?" I'm assuming the data is in Newton-meters.

0x359 - Speed
Byte 1 - Speed HiByte.
Byte 2 - Speed LoByte.

I'm assuming it has the same dividers as the old 0x351 message.
MPH = ((Byte2 * 256) + Byte1) / 322
KPH = ((Byte2 * 256) + Byte1) / 100

0x621 - Gauge cluster data.
Byte 3 - Bits 0-6 = Fuel remaining in liters, bit 7 = low fuel light indicator.

These seem to be just status messages, but I don't see any command messages pop up when working with locks or windows... Maybe I just need to do more research, but I was hoping maybe someone could enlighten me?

You cannot control the locks or windows from the infotainment bus; they can only be controlled from the convenience bus. For some reason, they also appear on the infotainment system, but attempting to use them there does not work. But if you use the convenience bus, they work well.

I have it running on the "comfort bus" now, but the result is the same...
I can send the steering wheel control message, but that's the only one that's responding.

I'm unable to get the blinkers, wipers, locks, windows, etc. to function.

Do I need to be registered in the ring (0x4XX)?

Edit:
"There's something strange about this car, or at least this generation of it..." Nothing responds to my messages except for the steering wheel controls, and there isn't a single message that's for the windows (like on MK5 Golf, message 0x181), but there are messages for the individual doors (0x381, etc.).

I need to connect to my wife's 2012 Beetle and see if it's the same...