Ranger Mods

Run a xlt Ranger (2018), with probably 250-300 kg load constantly around city. My economy is 13.7 km/l which i think is poor. Checking my scangauge for dpf burn off i never see it get close to the 100 number before it does a burn off, it always appears to be low numbers
Can some one confirm that they see the gauge get close to the 100 number and then reset
I am wondering that it is doing constant burns and affecting the fuel economy
ps the best economy i have seen is a frag under 13km/l

I can see my DPF slowly move upto to 100% before doing a burn off. When on open road hardly moves at all but around town in constant stop start traffic it moves up quite quickly.

Economy seems normal to me for a dpf vehicle. You won't get down to the same as earlier models from what I've seen.

My DPF temp starts to rise at about 93%
The temp continues to rise to a max of around 700deg by the time it reaches 100%
Temps then slowly drop.

a1bert wrote: ↑Sat Sep 12, 2020 9:28 am Run a xlt Ranger (2018), with probably 250-300 kg load constantly around city. My economy is 13.7 km/l which i think is poor. Checking my scangauge for dpf burn off i never see it get close to the 100 number before it does a burn off, it always appears to be low numbers
Can some one confirm that they see the gauge get close to the 100 number and then reset
I am wondering that it is doing constant burns and affecting the fuel economy
ps the best economy i have seen is a frag under 13km/l

Manually calculated or read from the cluster?
Tyre size?

Question in relation to the scangauge math in relation to the dpf’s reading.
000200010000 - shows a dpf soot % reading between 50 - 100.
So burn starts at 100, but will finish when it gets to 50. It also counts in increments of 2.

If I change to
000100010000 - it shows a dpf soot % reading between 25 - 50.
So burn starts at 50 but will finish when it gets to 25. It also counts in increments of 1.

What math do I need to get it to count in increments of 1, showing a range of 0-100?
P.S - this is for an LC200, not a Ranger / Everest.

Cheers

Not sure if Scangauge can show raw data, Ultragauge can. Ideally you will show the raw data and make a table of raw data and % from a known proper reading scantool. It is pretty quick and easy to determine the correct math this way.

x2/1 is just x 2 and 1/1 is 1. Seems to basic. It will be some weird like A/5. Log raw and compare and you will sort it quick. My brain it to fried tonight to think.

Also doubtful it would have an offset so forget about the last 4 characters.

Below are the codes which work perfectly.
All I want to do is expand the reading from a range of 50-100 counting in two’s to 0-100 counting by one’s.
Can this be done?

TXD 07E02138
RXF 032200000000
RXD 3808
MTH 000200010000

You cant just expand it as such, how do you expand something when you do not know what the true output really is, can you prove that it is 70 or 95 or even 100% or is it an assumption that it might be?

To do it properly raw data is required. What does 0% equal? hex 00 or ?
Is it really a 1 byte reply or should it be 2 byte?

It will change the math entirely. 0 to 100%range has to be calculated from something 1 byte hex 00 to FF, doubtful. It could be hex 20 to AF which would change the math entirley. Or if 2 byte then 0000 to FFFF but it is rarely a PID will start at raw data will start at 00 or 0000.

It is not always as easy as it looks and is why when trying to figure out the maths for a PID I have no data on I will look at the raw data and compare that to the % on a known working scantool. Grab about 5 different figures then the rest is easy.

End result is you need the correct math and cannot virtually expand something.

The only thing I know for certain is when it gets to 100, it starts a dpf burn and when it is finished, it stops at 50.
I can speak with confidence that this should be accurate, as the car is brand new (less than 700kms) and the 3 dpf burns it has done have all been exactly the same.

All good if it is complicated, I just thought there may have been some multiplier I could expand that would give me the end result I was looking for. Thanks for your help as always.

Hi all.
Have the same issue.
Running torque pro.
Soot level gets to 12% then burns to 1%.
Im only assuming its burning due to egt increase and soot level dropping.
Any suggestions? Could there be something wrong with my car?
Cheers

I know of no one that has had a real DPF issue with a Ford. Calcs are the cals, algorithm do what they do.

Different driving conditions, temperatures, peddle position. So many factors involved.

Let them do what they do unless you see 100% constant for weeks on end with no drop ever then, yes it is time to look in a block DPF.