Seat Ateca 2018 - Auxiliary Heater

Auxiliary Heater (Entertainment Bus):

521#0100000000000000 On
521#1A00000000000000 Off

These codes need some additional testing, but seem to work


Did anyone find out what bytes 2,3,4,5,6,7,8 could mean ?

Example:
521#0100000000006A20 On
521#1A00000400FA6E28 Off

010
011
012
013
01A
01B
040
0FD
101
107
116
12B
147
155
157
184
1FA
29D
29E
29F
2A7
2A9
30B
30C
30D
30F
31B
31E
324
32A
32F
366 - Alarm Lights / All Blinkers - 366#0000103E80030000
386
391
394
395
397
3B5
3BE
3C0
3C7
3CE
3CF
3D0
3D1
3D4
3D5
3D6
3D8
3DA
3DC
3E5
3E9
3EA
3EB
462
463
464
481
484
485
486
48B
48E
48F
504
520
521 - Auxiliary Heater -> 521#xx00000000000000 01=On / 1A=Off
52A
530
551
569
582
583
584
585
588
58C
592
593
5A0
5AC
5BB
5BF
5E0
5E1
5E9
5EA
5EB
5F0
5F2
5F4
5F5
5F7
640
641
642
643
645
647
64A
64E
650
656
658
65A
65D
65E
661
663
668
66E
670
671
672
6A6
6AE
6B0
6B2
6B4
6B5
6B6
6B7
6B8
6B9

Did you see this:
https://github.com/commaai/opendbc/blob/master/vw_mqb_2010.dbc
Ateca is MQB based, so it should fit. I have translated DBC to xls for better viewing.

Thank you so much! I am going to take a dive into this. This upcoming weekend I have a business trip to Germany Essen, but after that I will have more time.. can't wait !

Great! the details of the 521h seem to work. The byte 7 temperature calculation also results in correct cooling water temps.

My understanding of the German language is not so good: does the XLSX file contain ID and byte info on the J386/J387 Door Control Units (connected to the Convenience Can-Bus) ?

Found these codes on this forum, but my car doesn't respond to them:

// Front Left Glass Up
181#0200
// Front Left Glass Down
181#0800
// Front Right Glass Up
181#2000
// Front Right Glass Down
181#8000

This weekend i am going to try to sniff the codes for controlling the windows. Will report back when found

Hi,

just size the column header line in the sheet bigger and you can see the English descriptions of the columns.

Best regards, Rainer

Did you succeed in enabling the headlights on MQB platform?

When i send the following codes (sniffed) then the headlights flash once every time i send it. If i remove one of the two codes, nothing happens.

3C0#74000300
658#0070040000000200

It seems there is some other module which repeats other commands, resulting in my codes only making the headlights flash very shortly like a photo-flash (they are LED headlights).

Also i have tried to enable the headlights using VCDS plug from RossTech, but i can't seem to find the option to enable the headlights through OBD. The idea was to sniff the codes from the VCDS plug and use them to enable headlights.

DatafoxChris hat folgendes geschrieben:

Did you succeed in enabling the headlights on MQB platform? When i send the following codes (sniffed) then the headlights flash once every time i send it. If i remove one of the two codes, nothing happens. 3C0#74000300 658#0070040000000200 It seems there is some other module which repeats other commands, resulting in my codes only making the headlights flash very shortly like a photo-flash (they are LED headlights). Also i have tried to enable the headlights using VCDS plug from RossTech, but i can't seem to find the option to enable the headlights through OBD. The idea was to sniff the codes from the VCDS plug and use them to enable headlights.

In more clever cars, like Passat B8, Golf VII, steering wheel ECU is communicating with BCM over CAN. So you can control blinkers, high beam.. But you should keep correct timing, counter and check sum.

For enabling headlights with VCDS you can try this:
Goto BCM module;
Output test;
Choose light which you need
Press start

Check CAN bus and you will see how easy you can control this.
BUT! It works only with ignition.

P.S.: In output tests you can find more interesting stuff, not only lights

Daytime running lights can be switched off using this output test.

Sniffed the bus while executing output test, and filtered it.

Log is attached. Next step: interpret the commands

I would propose to do printouts of the Message Changes View in KCANMonitor and to put the paper sheets over each other.
One sheet printed with Auxiliary Heater on and one with off.

You should see which bytes are different and be able to concentrate your work on them.

Best regards, Rainer

Thank you for your response: the heater can be controlled now At the moment i am trying to control the headlights when the car is parked and off.

DatafoxChris hat folgendes geschrieben:

Sniffed the bus while executing output test, and filtered it. Log is attached. Next step: interpret the commands

Its quite easy
If i good remember...
0x700 - keep session alive
0x70E - tested ID
0x778 - BCM ID.

Output control is working with command 0x2F.

So basicaly you need send periodic message, open diagnostic session and control output. Check log files, analyse what each CAN msg does and you will understand how easy its..
But as i said - it works only if ignition in on..

More about message structure and etc you can find in google: ISO14429. Or simply UDS diagnostic.

Short info about commands:
https://automotive.wiki/index.php/ISO_14229

What could be the meaning of EKP Ansteuring please ?

What is EKP ?

AKP = ElektroKraftstoffPumpe ?

What would be the meaning of KVS (having a value in milliLiters) ?

KVS represents the amount of milli liters of gasoline used in the current session.

KraftStoffVerbrauch = fuel consumption

The heater can be switched on from within home using my app

One question:
How to keep the bus (and the connected modules) active ?

When i send a 0x700 message with 8 zero bytes, most modules keep sending messages but not the heater.

Any tips would be very much appreciated

Hi Chris,
nice things that you're doing

Take a dive into "NM High" thema. This stands for "Netzwerkmanagement High". Look at extended ids which starts from 0x1B0.

Regards, Michal.

Built a VB.NET 4.5 project called CanProxy, which sits between SocketCanD and a WebSocket (one per client). This can be run on the Raspberry using Mono. Works really well !

A python script watches the ACC-line and starts and stops the recording of GPS data into NMEA logfiles.

From the MQb xlsx file, message 0x30B:

Does anyone know what 'KBI_V_Digital' means ?

Guess: KBI = Kombiinstrument (instrument cluster)