Wann ist ein Differenzdrucksensor tot? | Posts 16+

New record:

Code:

22:47:21 Block 067: Partikelfilter (Abgaswerte I)   190.4°C  Temperatur vor Abgasturbolader   308.7°C  Temperatur im Partikelfilter   13.8 mbar  Druckdifferenz Partikelfilter   -16 mbar  Offset Differenzdruck

Ignition off, ignition on.

Code:

22:50:13 Block 067: Partikelfilter (Abgaswerte I)   222.5°C  Temperatur vor Abgasturbolader   259.5°C  Temperatur im Partikelfilter   3.3 mbar  Druckdifferenz Partikelfilter   -26 mbar  Offset Differenzdruck

I want a new one for Christmas.

Okay.

At EUR 40, I couldn't resist.

The differential pressure sensor was installed in a rather awkward location, but it's new now.

Interestingly, it seems like it might have been replaced before, as it's dated 2008 (although my car was manufactured in December 2006/January 2007).

m;

Code:

Adresse 01: Motorelektronik  (03G 906 018 EM) 17:13:35 Block 067: Partikelfilter (Abgaswerte I)   150.0°C  Temperatur vor Abgasturbolader   63.0°C  Temperatur im Partikelfilter   14.2 mbar  Druckdifferenz Partikelfilter   1 mbar  Offset Differenzdruck

It would be interesting to see if any measurable changes occur in fuel consumption and DPF regeneration.

That's exactly what I'm trying to grasp.

Unfortunately, I don't have a detailed record of how far he got using a registration.
A Bronkens DPF module would be appreciated ).

Lately, distances of 1xx kilometers have been more common.

But even with 184km and 42%, you can still drive 150km - because at 160km/h, it actually regulates itself passively .
He reclines again when the speed reaches 120 km/h.

m;

Hmm, do you really think this kind of module makes sense? I can't think of many other situations where this would be necessary, except for this specific case.

Because my RKS+CAN system can actually do that... it was just never installed.

Best regards, Rainer.

I come from this "measuring and evaluating" area.

Data that disappears, such as the kilometers driven, as soon as a registration is complete, is always a bad thing. It is certainly interesting to examine these increasingly shorter cycles in more detail, to understand their cause and find a solution.

When I look at the data now, I see things like 184 km and 42%, and I think, "oh crap," it's running really fast. Sure, that was just city traffic.
If I then realize that the subsequent highway driving fits perfectly into the cycle, meaning I can easily cover the 405 km without it needing to inject any additional fuel, that alleviates the panic and represents normal, error-free operation.

I would like a module that logs everything.
- always
- automatically (without me having to connect cables or turn on my laptop)
- stores data for later retrieval.

With 10 cycles, Torsten covered over 4000 km. This is already a good approach to capture *all* the cycles. For me, it would take approximately 2 months for data to be lost due to rotation.

m;

dieselmartin wrote:

Recently, there have been more instances where the distance was around 1xx km.

Hi,

Approximately 1xx kilometers until regeneration?
Then it was really time...

Exactly for that reason,

While I recently discovered that an apparently imminent rain event doesn't always actually happen (like in the example of 184km/42%), if the sensor is slightly miscalibrated and has an illogical offset, it will mainly shift the measurement range rather than distort it – at least, that's how I interpret "offset."

And it's precisely then that the area with low pressures becomes very unclear. A difference of 10 mbar "nearby" is a huge difference when the idle pressure is 3.3 mbar, while at 400 mbar under full load/with a full DPF, it's almost a normal measurement inaccuracy.

That means a sensor that's slightly inaccurate will mostly have consequences in urban traffic... and I happen to drive through the city more often.

m;