Solved: 2014 facelift 2.3l ducato tank resize
Posted: 21 Sep 2025, 16:51
Would it be possible for someone to aid me in resizing the tank please?
Ive tried with byte 60 and 67 but I'm probably doing something wrong. byte 67 has something to do with an airbag module and luckily I didnt set it to a correct range, it spit an error.
Ive purchased a new tank pump and tank for my ducato. Old tank was @70l and had the short-body pump.
New tank is the 125l variation and has the long-body tank pump with no limiter.
Solved: I figured out that there may only be two pump sizes, and there may be 4 or so models for the ecu to calculate from.
Essentially from what i can gather, either your ecu has the option to change the fuel tank size in which case modding with MES should be quite straight forward.
In my case, I modded byte 60 from 02 to 03. the fuel level now reads a logical amount. So I assume byte 60 is just telling the ecu which pump to expect and deal with the ohm curve accordingly.
Now the dash cluster can learn new percentages to fuel usage and distance traveled and , given time will learn the new range.
As shpuncik usefully pointed out, byte 90 should reflect a value saved in byte 60. so if byte 90 says 12, it should be changed to 32. In my case it was 00 so changing that value to 30 changed my range to closer to what it should be.
Ive tried with byte 60 and 67 but I'm probably doing something wrong. byte 67 has something to do with an airbag module and luckily I didnt set it to a correct range, it spit an error.
Ive purchased a new tank pump and tank for my ducato. Old tank was @70l and had the short-body pump.
New tank is the 125l variation and has the long-body tank pump with no limiter.
Solved: I figured out that there may only be two pump sizes, and there may be 4 or so models for the ecu to calculate from.
Essentially from what i can gather, either your ecu has the option to change the fuel tank size in which case modding with MES should be quite straight forward.
In my case, I modded byte 60 from 02 to 03. the fuel level now reads a logical amount. So I assume byte 60 is just telling the ecu which pump to expect and deal with the ohm curve accordingly.
Now the dash cluster can learn new percentages to fuel usage and distance traveled and , given time will learn the new range.
As shpuncik usefully pointed out, byte 90 should reflect a value saved in byte 60. so if byte 90 says 12, it should be changed to 32. In my case it was 00 so changing that value to 30 changed my range to closer to what it should be.