VW T6 Custom PID codes for DPF

[outcry666]

Hi, you know we cannot read DPF measurements by regular way. Only if you can see it with compatible OBD and the app called VAGDPF on Android based Head Units/Phones/Tablets.
So, i want to share these Custom PID codes for using another apps like Torque OBD. You can use these codes for on any app that allows you to enter Custom PIDs.

I inform you that i am using Torque OBD and Vgate Icar Pro. My Van is VW T6(2016).


- First enter "Manage extra PIDS/Sensors" section on Torque OBD settings.

- Then you can add Custom PIDs from there

- You have to enter Hex codes on "OBD Mode and PID" textbox.

These are the hex codes
22114f sooth mass calculated
22178c oil ash residue
22114e sooth mass measured
221156 distance since last regen
22115e Time since last regen
2211b2 Input Temp
2210f9 Output Temp

- Enter Min/Max values to textbox and unit symbol to related area (km,miles,minute etc. )
- You have to enter 7E0 to "OBD Header to Use" textbox.
- After these we have "Equations" textbox. This section is how we can convert returned hex codes to readable value.

Enter these formulas to Equations section
Sooth Mass Calculated(22114f ) ((a*256)+b)/100 gr.
Oil Ash Residue(22178c) ((a*256)+b)/10 gr.
Sooth Mass Measured(22114e) ((a*256)+b)/100 gr.
DPF fullness(22114f ) ((a*256)+b)/24 %
(For fullness i am using the Sooth Mass Calc. hex value and DPF full value is 24gr for my van.)
Distance Since Last Regen(221156) ((c*256)+d)/1000 km.
Time Since Last Regen(22115e) ((c*256)+d)/60 min.
Input Temp(2211b2) (((a*256)+b)-2731)/10 °C
Output Temp(2210f9) (((a*256)+b)-2731)/10 °C

My van starts regen at about %80-85 fullness.

 

[mmi]

Hi, you know we cannot read DPF measurements by regular way. Only if you can see it with compatible OBD and the app called VAGDPF on Android based Head Units/Phones/Tablets.
So, i want to share these Custom PID codes for using another apps like Torque OBD. You can use these codes for on any app that allows you to enter Custom PIDs.

I inform you that i am using Torque OBD and Vgate Icar Pro. My Van is VW T6(2016).


- First enter "Manage extra PIDS/Sensors" section on Torque OBD settings.

- Then you can add Custom PIDs from there

- You have to enter Hex codes on "OBD Mode and PID" textbox.

These are the hex codes
22114f sooth mass calculated
22178c oil ash residue
22114e sooth mass measured
221156 distance since last regen
22115e Time since last regen
2211b2 Input Temp
2210f9 Output Temp

- Enter Min/Max values to textbox and unit symbol to related area (km,miles,minute etc. )
- You have to enter 7E0 to "OBD Header to Use" textbox.
- After these we have "Equations" textbox. This section is how we can convert returned hex codes to readable value.

Enter these formulas to Equations section
Sooth Mass Calculated(22114f ) ((a*256)+b)/100 gr.
Oil Ash Residue(22178c) ((a*256)+b)/10 gr.
Sooth Mass Measured(22114e) ((a*256)+b)/100 gr.
DPF fullness(22114f ) ((a*256)+b)/24 %
(For fullness i am using the Sooth Mass Calc. hex value and DPF full value is 24gr for my van.)
Distance Since Last Regen(221156) ((c*256)+d)/1000 km.
Time Since Last Regen(22115e) ((c*256)+d)/60 min.
Input Temp(2211b2) (((a*256)+b)-2731)/10 °C
Output Temp(2210f9) (((a*256)+b)-2731)/10 °C

My van starts regen at about %80-85 fullness.

View attachment 151152

Hi,

I'm afraid I have missed something in the above. I couldn't get any live data from the custom PIDs mentioned above.

Torque + Carista dongle, which works very well with VAG DPF thus I must assume the Carista dongle would be capable of reading VW specific messages. T6 EU6 engine (CXEB) 2018.

Using 7E0 in "OBD header to use" results just this:​

Interestingly the response is the same for the all the hex codes/commands in "OBD Mode and PID"

Interestingly by using 7E1 in "OBD header to use" the result is something else.Then 7E2...7E9 - again no results for the equation.​

Note: the simplified equation above was just to see if there is anything live there.

Any ideas?

Meanwhile - what would be the hex code for "IDE01407 Particle filter: fuel consumption since last regeneration"

 

[n10n]

I'm afraid I have missed something in the above. I couldn't get any live data from the custom PIDs mentioned above.

T6 EU6 engine (CXEB) 2018.

I have similar experience using Car Scanner app with another 2018 CXEB engine. I spent fair bit of time trying to find working mode + pid combos but so far no success.

Have to wonder where app developers source the ECU documentations… sounds unlikely they could test each car and model year either.

 

[outcry666]

7e0 is the engine code header hex. This can be changed by the engine number. You can check these settings with bluetooth spoofing.
This header is always use to reply tx rx functions. You suggest tx to car and reply as rx from car.
There are some codes to bypass these with spoofing to your adapter.
You can firstly use these commands to get it working. As i said in the op, this is vary within obd manufacturers and elm protocol. I mentioned which adapter i am using. Commands to use, always you send a code, must return a value 'ok' or a value
Atz
Ate0
Atl0
Ath0
Atsp6
Atsh 7e0

These are the questionings communicate with elm/obd
That 7e0 is the hex number of the engine.
Hope i can help. Thank you.

 

[n10n]

Partial progress for 2018 CXEB:

7E0 22208B - soot mass calculated
can0 7E8 [8] 05 62 20 8B 0B BF AA AA
(hex) 0BBF => (dec) 3007 = 30.07g ((A*256)+B)/100

7E0 22208C - soot mass measured
can0 7E8 [8] 05 62 20 8C 01 DC AA AA
(hex) 01DC => (dec) 476 => 4.76g ((A*256)+B)/100

7E0 22208D - km since last regen
can0 7E8 [8] 05 62 20 8D 0F 86 AA AA
(hex) 0F86 => (dec) 3974 => 397.4km ((A*256)+B)/10

7E0 222089 - time since last regen
can0 7E8 [8] 05 62 20 89 01 8B AA AA
(hex) 018B => (dec) 395 => 395 minutes ((A*256)+B)

7E0 2220D8 - fuel since last regen
can0 7E8 [8] 05 62 20 D8 0C AB AA AA
(hex) 0CAB => (dec) 3243 => 32.43L ((A*256)+B)/100

7E0 22406C - oil ash mass
can0 7E8 [8] 05 62 40 6C 08 A0 AA AA
(hex) 08A0 => (dec) 2208 => 22.08g ((A*256)+B)/100

7E1 222104 - dsg temp
can0 7E9 [8] 05 62 21 04 34 00 AA AA
(hex) 34 => (dec) 52 formula is just 'A', ie temperature with 1 degree steps

70F 222BF1 - haldex temp
can0 779 [8] 05 62 2B F1 53 63 AA AA
(hex) 5363 - (dec) 21347 - 20.9 ((A*256)+B)/1024

Totally not sure about DSG / Haldex temperature formulas. And something weird with Haldex temperature - when tracing I get the values out fine but stuffing them into Car Scanner sensor definition it just comes out as zero. Maybe there's either limitations of how many controllers can be interacted with in a single screen or perhaps Carista cannot talk to Haldex controller while OBD11 can. Also DPF time unit currently not known.




Edit: fixed km since last regen and time since last regen formulas
Edit: looks like DSG temperature formula is just A

 

[mmi]

Indeed... thanks @n10n for sharing



Another pocket tool to keep track on things - connects with engine automatically. Takes advantage of Carista dongle.

Journey 32.5 km, 44 minutes​

Soot accumulation 3210 mg​

Fuel used on the journey 2250 ml - still need to be calibrated/verified by actual brim to brim fill-ups.​

---

​

Totally not sure about DSG / Haldex temperature formulas.

I believe for the DSG the equation should be:



to make the above look like this


because all DSG temperature readings were actually 80+ degrees as per VCDS report (below)

 

[n10n]

I believe for the DSG the equation should be:

View attachment 160238

Agree, and that equation can be simplified to just A as B seems to be all zeroes at least what I've observed so far. I found it from Any experienced Torque Pro users on the forum?. Also OBD11 shows the temperature without any decimal places further suggesting no divisions needed.

screenshot from dropbox file referenced in above link

 

[n10n]

Here’s my sniffing setup I used to extract above PID’s if that happens to be of interest… Y-cable from diagnostic port, canbus from free port wired to Raspberry Pi with a can hat. And a LTE modem ”mokkula” (not in pic) to get phone, laptop and Pi all on same network. On Pi, canbus software may just log all the traffic, it sees only diagnostic messages as gateway filters away all internal canbus messages.

 

[mmi]

Just another - duration of DPF regeneration - engine's view. Non-zero value = DPF regeneration active.

DPF regen duration

7E0​

22207d​

A*256+B​

seconds​

@n10n - by any chance - have you made notes of other PIDs? Vehicle distance driven (odometer) in engine?

 

[n10n]

@n10n - by any chance - have you made notes of other PIDs? Vehicle distance driven (odometer) in engine?

Try 7E0 22295A (((A * 256) + B) * 256) + C km

Can't verify right now as latest update of Car Scanner broke custom sensor functionality but here's the raw messages for mine with 57601km on clock. Need to find another good iOS app

can0 7E0 [8] 03 22 29 5A 55 55 55 55
can0 7E8 [8] 06 62 29 5A 00 E1 01 AA

Tracing is relatively time consuming so no, I haven't put in efforts to get 'em all

 

[mmi]

Spot on!
Massive thanks @n10n

Tracing is relatively time consuming

I concur.

latest update of Car Scanner broke custom sensor functionality

Hmmm, wondering if the same has happened with Android version, too. Just tried (first time) but could't quite understand how to get things done....

 

[n10n]

Hmmm, wondering if the same has happened with Android version, too. Just tried (first time) but could't quite understand how to get things done...

.

Could be. The app is little edgy for sure.

This is the connection profile


Then from main settings -> sensors, click plus on page top to add a new sensor. At least on iOS, seems like nothing happens but it adds a new empty one to the end of very long list so scroll all the way down to see the new one.

Then values into custom sensor like this:


Test button on sensors has never worked for me

After sensor is defined like above, you should be able to use it to build dasboards like with any built-in sensors.

Hope this helps some!

 

[mmi]

seems like nothing happens but it adds a new empty one to the end of very long list so scroll all the way down to see the new one.

Thanks again - this was the issue! Didn't realise the newly created one was all the way down.

Test button on sensors has never worked for me

So looks like no problems with Android version - even the Test button works, although to see the results had to scroll down - definitely helps to verify right away.

 

[n10n]

Little bit OT but what I especially like about Car Scanner is that there’s GPS speed as a sensor - no need for a separate app to observe true speed

 

[n10n]

Yay, thanks to the Car Scanner developer, it seems it might not be necessary to use custom PIDs - the profile descriptions are not, well, descriptive… diesel var.1, var.2 and var.3 are supposed to be the good ones. Developer suggested v2 or v3 for CXEB but Haldex is currently only in v1.



So… just a quick test with v1 but indeed DSG and Haldex temperatures can be read with this directly, here’s the working sensor names for the basic temperatures before I proceed to customize the dashboard:



Now it’s just more click fest to make it look nice and to add the rest of the stuff!

 

[n10n]

V2 seems to be the best for CXEB. Now I got this and I’m happy for time being - GPS speed under gauges and voltage at the bottom. Haldex % just for the fun of it.

Hmm but now that I think of it, if the app would also read BM2 to get leisure battery voltage on the same dashboard it would be sweet…

 

[mmi]

V2 seems to be the best for CXEB. Now I got this and I’m happy for time being - GPS speed under gauges and voltage at the bottom. Haldex % just for the fun of it.

Thanks for sharing! Captured the below with V1 profile (before your post) - the available data seem to vary between the profiles so some experimenting is needed.

Anyways, quite impressed with the capabilities of this 5€ app (+Carista dongle) - especially about the capability to communicate and display data from 4 different controllers below (ECU, DSG, AWD, A/C). Obviously need to try to add yet another controller to monitor - Parking heater (Webasto), before freezing temperatures arrive. Have you looked into app's recording capabilities?

​

Perhaps we need also these from ABS

 

[n10n]

Anyways, quite impressed with the capabilities of this 5€ app (+Carista dongle)

I agree. One thing I’m missing is the ability to format values better. For example, with custom sensor you have formula to tinker with value range, like convert 0..1 to a percentage, no such option with built-in sensors. I would love some more programmatic way of defining values, often for example unit would fit better with the value, or perhaps I would only like to show some values when they are out of bounds.

Have you looked into app's recording capabilities?

Nope. I guess it could be useful but so far I’ve only looked into dashboards.

Perhaps we need also these from ABS ​

What are you seeking to accomplish with that? Detecting binding break pads?

 

[mmi]

Nope. I guess it could be useful but so far I’ve only looked into dashboards.

Thanks - I tried but at first glance nothing that could be exported (e.g. CSV file).

What are you seeking to accomplish with that? Detecting binding break pads?

Just curiosity - that would be 6th controller! As marked calculated values probably not useful for such a fault finding.

I agree. One thing I’m missing is the ability to format values better. For example, with custom sensor you have formula to tinker with value range, like convert 0..1 to a percentage, no such option with built-in sensors. I would love some more programmatic way of defining values, often for example unit would fit better with the value, or perhaps I would only like to show some values when they are out of bounds.

Certainly there is room for improvement - good basis though - perhaps a kind request to the developer...
Also noticed the App seems to read VAG fault codes quite well - although just the numeric codes without the descriptions.

 

[n10n]

Thanks - I tried but at first glance nothing that could be exported (e.g. CSV file).

Swipe left on recorded file name and you get options to export in couple of formats