Recent Posts

powershell is a terrible language. Consider python.

ps is used mostly for the build scripts nothing else. The actual report analyze is written in python.

But I absolutely agree that ps is not the most pleasant language to work with.

Regarding the PR suggestion to be honest I haven't even thought about it. Because my goal was more like to build something that does the analyze for me and split the runs. But I will definitely consider to take a look at the source of ECUxPlot and see where and how I can integrate my stuff in there!

powershell is a terrible language. Consider python.

Has anyone got a compatible XDF or KP for this ecu?

why not submit a pr to https://github.com/nyetwurk/ecuxplot

Hi all,

So basically I woke up the other day and decided to create something to help me analyze my logs. Since I have some overboost issue on my shit box. However I know there are many other tools and applications which are widely used to analyze and view/open .csv logs.
But maybe because I'm dumb enough or lazy enough to spend more time researching why I wasn't able to work it out and be a friend with ECUxPlot for example I decided to create something of my own. (btw I'm a software developer and I have some knowledge here and there)

So it all started as a simple cmd app which is used to analyze ME7.5 logs and create detailed reports. But then because I got a bit greedy it all escalated to the following app with 3 options/versions of work. Why I'm saying that is because I thought in the big 2026 to avoid the usage of AI would be dumb even for such a lame project.

Sooo a thing let to another and I started working on this and things got out of hand ending with a console app where you can analyze logs. For now it works for ME7.5 as it has a bit more data for it but it also works for general purposes which I still haven't test to be honest.  But that's one of the main reason to open the topic in here. I will be glad to expand it and make it more robust and useful.

So at the moment we have this lite version which excludes any usage of AI basically can be used if you are skilled enough (not a noob like me) and you know what you're reading this will just maybe save you a bit of time.
But also we have 2 versions which are using AI one is enhanced Lite version using OpenAI_API_KEY which you should ofc have a plan to obtain but as per the estimations it takes less than 0.01$ per report build and review.
And here is the cherry on top way slower but basically comes at a cost of your PC setup which downloads and runs local AI server which will analyze and build your log report.

Here I leave the repo link. The installers are in the release sections.

https://github.com/wowtic/ME7_Log_Diagnostic

Feel free to reach me out on my email wowtic@abv.bg or wowtic@icloud.com for further input or maybe suggestions how to enhance it.
I'm also building some other cool stuff which might share here later. But that's all folks for now.

I'll also keep an eye on the topic here if it got some demand on it.

Also will be curious if there is anyone with logs on hand which are not from 1.8T and test it out and share his experience.

Hi everyone,

I am looking for some help and guidance on how to properly set up DSG Farts (Ignition Cut / Fast-Path torque reduction) on my VW Golf 5 GTI 2.0 TFSI.

Car specs:
- Engine: 2.0 TFSI (AXX), ECU: Bosch MED9.1
- Transmission: DSG DQ250 (TCU tune has clutch pressures raised to 16 bar by another tuner)
- Exhaust: Complete straight pipe from turbo to the back

Problem:
The car shifts completely silent under wide-open throttle. I suspect the current Stage 1 engine file uses Fuel Cut or throttle closure during torque reduction instead of proper Ignition Cut (fast-path torque reduction with ignition retardation). Also, since the ECU and TCU were tuned by different people, the torque monitoring and torque limiters might not be synchronized.

I want to learn which specific maps in MED9.1 handle the engine-gearbox torque coordination (like minimum ignition angles during shift torque reduction).

I have uploaded my current Stage 1 .bin file to Mega.nz. Could someone look at it or point me to the right map addresses/structures in WinOLS?

File name: OBD_Volkswagen_Golf_5th_1K1_2004_Bosch_MED9_1_Prt_3081_ChecksumNotVerified


All mechanical issues like the PCV valve leak are being sorted, so the car will be mechanically 100% ready for the changes.

Thank you very much for any help or definitions!

hi everyone
i have a stock 512kb dump from my bmw 735i me 7.2 _HW 0261204620 SW 350476, which i just read on the bench
i tried to find a working xdf for tuner pro or damos for winols to do this myself, but none of the public files available online match my software version -all axes and map addresses are completely shifted or showing 65535. because of this. i am kindly asking for help

could someone please modify my attached original file to add"
downstream lambda off and popsbang _maybe hardcut
or send me good xdf or damos
thanks you all who help me.

06A906032PL S003 .xdf and .kp with 4,048 definitions, as well as English translations included. Ill attach a clean, stock .bin as well.

That's BCConsulting. So why post it here? It's VIN locked.

You are really bothering about it is locked in a FREE forum with complete and CLEAR instructions how to do it yourself ?!

https://www.openmoose.net/blog/?page=renatus

check out the newest open moose update!