Recent Posts

Hello, I have a dpfoff problem on a Takeuchi TB260 excavator with Yanmar engine 4TNV86CT-PTB and Bosch edc17cv54 ecu. I did the dpf off but I have a problem with regeneration every aprox. 90 hours. The sensors are disconnected (2x temp, differential pressure), there are no faults except with the mentioned regeneration. I also have the Texa OHW diagnostics, I reset the dpf but it doesn't help. I'm looking for someone who can help.

So the calculated soot content still increase. Please post the original, I can take a look if it similar I have done before.

I don't have a ton of cash to get a proper tune but I have to get this back on bw road. Can someone please help me with. A tune.. I got a little cash I can through your way

Post your ECU original read and we can make it together.

It is known issue, it came with new software updates somewhere 2018 I think? That needs some specific changes to flash and I don't mean stupid "torque monitor off".

I have this ECU M3.2 from 1.8T audi -
if i understand correct this has the chip SST39SF010A-55-4C-NHE that has the tuning on it?

Yes, but it's not original chip. Somebody changed original chip witch was non flashable type.

But my question is how can i read this? any reccomended tools?
autel xp400 programmer, or vvdi multiprog or foxflash can help?

The chip can be read and reprogrammed only by desoldering it from the printed circuit board in an external parallel programmer.
For example cheap XGecu T48 Universal programmer + PLCC32 adapter.

Hi,

I have this ECU M3.2 from 1.8T audi -
if i understand correct this has the chip SST39SF010A-55-4C-NHE that has the tuning on it?

But my question is how can i read this? any reccomended tools?
autel xp400 programmer, or vvdi multiprog or foxflash can help?

Marantz, thx for the info with spark plugs, I have this car only for a while so they might be worth replacing.

As this is meant as a guide, here is my take on boost vs "load": The standard boost level on a 150hp AGU engine is allegedly 0.55bar, which translates to 1.55bar MAP. The requested load for this level seems to be around 7ms. So, running at 9.5ms (as I am now), this should translate to around 2.1bar, or 1.1bar boost. Seems quite a lot. On some tunes, I have seen numbers as high as 10.5ms, this translates to over 1.3bar boost? How does the poor k03 cope with this?

I shoot an equation: MAP = load[ms] * 0.22.  But I believe the turbo efficiency comes into play a bit here...

Btw, the apparent difference when going from 7ms to 9.5ms actual load is BIG. The stock engine is not sluggish, but it is boring. There is no turbo kick. After the remap it is fun to drive.

Hi mate, it's all about code optimisation. I cannot explain myself how a reputable tuner everybody knows across europe and the states only managed to make 187hp from absurdly high values in KFLDS. This is something I have seen personally, no assumptions made or "a friend told me".

My advice is to follow your own path as I did and as you're doing: make your own learning, observations, experience, and do what works for you. I learnt a ton from this and other forums, but I did my own testing and observations and I am using what has been working for me.

Also yes, the stock tuning while obviously super reliable, is obviously super boring too. Since I made my first test to 180hp I haven't understand how Audi/VW ever let the 1.8t go into production with only 150hp. I believe this had to be a financial decision as they also had to sell those V6's and 180hp versions for an extra cost. There is a cool video on youtube of two A4 B5, 180hp AJL and a V6 30v 193hp runs compared, and the 180hp keeps up with the V6 untill 200km/h.

Best regards,

did u end up figuring it out?

There's nothing to figure out. The engine needs the flaps to start well.
The alternative is to dump a ton of fuel, which he did.

This is on turbo. On NA the flaps are responsible for manifold length tuning and midrange torque takes a nosedive with them removed (should never be done).

On hex editor I'm comparing files. If I go to checksum section in picture attached I'm not sure what it means

On hex editor I'm comparing files. If I go to checksum section in picture attached I'm not sure what it means

I get that . I would like to learn how to do it manually . If i went down this route is the checksum actually in the map itself. Does it start or end with a zero? And when checksum is corrected does the modified file just need the checksum to read the same as the original file or should i say match up. If i use tuner pro from what i understand it will only except a bin file and not just file well the free version anyway