Pages: 1 ... 6 7 [8] 9 10
 71 
 on: August 08, 2026, 01:44:45 AM 
Started by jojolepirate - Last post by jojolepirate
Hello guys!
I'm looking for definition / map file for the VAG 1.4 TSI CZCA block, more info here:
HW PN: 04E907309AC
VAG SW PN: 04E906027DA
SW version: 8231

I was unable to send the message with ori attached, I uploaded it here instead:
https://drive.proton.me/urls/P0QN9QJ4V8#9paLsP4XXhTf

Thank you for your help!

 72 
 on: August 06, 2026, 12:58:09 PM 
Started by maZer.GTi - Last post by _nameless
I fixed some bugs, made it a gui rewritten in python source and compiled files on git https://github.com/ugtuner05-sys/me7mafadjust

 73 
 on: August 05, 2026, 05:29:44 PM 
Started by _nameless - Last post by _nameless
updated first post

 74 
 on: August 05, 2026, 03:05:36 AM 
Started by koinfo - Last post by koinfo
I'm offering the following solutions/code packages. Feel free to contact me if interested.

VAG (Volkswagen/Audi) immobilizer data parsing

Bosch EEPROM checksum (ME7, EDC17, ME17, MED17, MG1, MD1, etc.)

IMMO OFF

Honda DTC OFF

DTC OFF for other ECU models

Checksum calculation / correction

OBD Readiness calibration

Vmax (speed limiter) removal

Fuel quality defect fixes

Idle speed modification

Lambda/O₂ sensor disable

ADBLUE / SCR removal

VIN modification

Cooling fan temperature adjustment

ECU read/write routines

PM me for details and pricing.

 75 
 on: August 03, 2026, 11:55:09 PM 
Started by marchewa - Last post by Olivia88
Could the issue with me7logger be securty access ? in that case we can mod the file to always grant security access by making 04 -> 14 @ 0xAB39

added patched file

edit: got the tp ecu, vcds is a no go. will have to finish my car now.
Me7l works on bench.

 76 
 on: August 03, 2026, 04:09:11 AM 
Started by RafU - Last post by iLimitless
 Everything you need for MED9  is
KFTSRL
DNMAXH
NMAX
FUBAOF (FTOMN) don't exist in MED9

 77 
 on: August 02, 2026, 09:35:27 PM 
Started by userpike - Last post by userpike
# Bosch Torque Lab — Gear Recognition Module v0.8.3                                                    ***scroll all the way down for the download, it's there. I promise***

Welcome to the first public module from a project I have been working on called **Bosch Torque Lab**.

This module analyzes the Bosch **BBGANG manual-transmission gear-recognition strategy** used in ME7. It was originally developed to diagnose my own car after changing the transmission gearing, but I expanded it so it is still useful even when your car has completely stock gearing and does not need any calibration changes.

The module supports both **5-speed and 6-speed manual transmissions**, selectable during setup.

Changing NVQUOT values is only one part of what it can do. Most users may run the module and receive the best possible recommendation:

**Your gear recognition is working correctly. Leave the calibration unchanged.**

That is still a successful result.

## What the module can do

* Analyze ME7Logger CSV files
* Selectable 5-speed or 6-speed analysis, including sixth-gear recognition, NVQUOT coverage, calibration, and validation when applicable
* Determine the physical gear independently from engine speed and vehicle speed
* Compare the physical gear with the ECU-reported `gangi`
* Detect false Gear 0 events
* Detect incorrect gear recognition
* Measure gear-acquisition behavior after shifts
* Analyze NVQUOT distribution and coverage for every gear
* Replay the Bosch BBGANG state logic against the log
* Read current NVQUOT calibration values from supported binaries
* Search unknown ME7 binaries for plausible NVQUOT calibration blocks
* Rank unknown binary candidates using structure and log evidence
* Compare before-and-after logs
* Perform post-flash validation
* Analyze clutch coupling after shifts
* Look for probable in-gear clutch or drivetrain slip
* Separate normal low-speed launch engagement from loaded clutch slip
* Show required, recommended, optional, and missing logger variables
* Load an ME7Logger `.ecu` definition and display RAM addresses, data types, scaling, masks, and variable status
* Export WinOLS-friendly calibration changes
* Provide an experimental live-log viewing mode


## Two interface modes

### Funktion Shamen Mode

This is the full educational and engineering mode.

It explains the who, what, where, when, why, how, how much, and why not behind the analysis. It includes Bosch Funktionsrahmen-based explanations, evidence, graphs, confidence levels, warnings, and the reasoning behind each recommendation.

This mode is enabled by default for first-time users.

### Expert Mode

This is for users who already understand the Bosch strategy and mainly want the conclusion, warnings, calibration values, and next action.

The supporting evidence and graphs remain available, but they are collapsed so the interface is faster to work through.

## You do not need modified gearing

The module can still be used to:

* Verify a stock calibration
* Establish a known-good baseline
* Confirm that a tune did not accidentally damage gear recognition
* Diagnose false Gear 0 or wrong-gear behavior
* Check shift acquisition
* Review clutch engagement
* Compare logs before and after drivetrain work
* Learn how Bosch BBGANG actually works

It will not recommend changing values merely because it found tighter values around the measured gear ratios. Bosch intentionally provides tolerance for tire variation, driveline movement, filtering, acceleration, deceleration, and other real-world conditions.

Calibration changes are recommended only when the available evidence shows a meaningful problem or drivetrain mismatch.

There is also a clearly labeled **Advanced Manual Value Editing** option for experienced users who deliberately want to experiment. Manual values are marked as user overrides and are not presented as module recommendations.

## Included hands-on example

The download includes a complete example using the actual files that were used to develop and validate the module:

* Before-correction road log
* Exact before-correction binary
* After-correction road log
* Exact corrected binary
* ME7Logger `.ecu` definition
* Logger configuration
* `START_HERE.txt`

My car has non-stock transmission gearing, so choose the **Adapt a Changed Drivetrain** workflow when running the included example.

The example does not contain an answer sheet. Run the files through the module and let it produce the diagnosis and validation results itself. This lets you confirm that the module is actually performing the analysis before loading your own files.

## Current testing and compatibility

Development and full regression testing were performed using:

* Bosch ME7.5
* `06A906032HS`
* Software `1037362937`
* Version `A906032HS`
* Software `1037362937`
* Version `0007`
* Five-speed manual transmission
* ME7Logger data

Known HS binary extraction is directly supported.

The module also includes an experimental unknown-binary discovery system intended to search other ME7 binaries for plausible NVQUOT blocks. Unknown candidates are ranked and clearly labeled by confidence. The program will not silently claim that an unverified address is definitely correct.

It should be useful across many manual-transmission ME7 applications using the same Bosch BBGANG strategy, but I only have complete development and validation data for the HS software at this time. Community testing on other software versions and six-speed applications is welcome.

## Important notes

* This module does not flash or modify your ECU.
* It analyzes files and produces recommendations.
* Always verify addresses and calibration values for your exact software.
* Keep each road log paired with the binary that was active when the log was recorded.
* Different driving routes can still be used for independent validation, provided each relevant gear has enough coverage.
* A matched route is helpful but is not required.
* “No changes recommended” is a valid and successful result.

Read `START_HERE.txt`, run the included example, and then try it with your own logs, `.ecu` definition, and binary.

Questions, bugs, strange results, and logs from other ME7 software versions are all welcome. If something does not make sense, post what you loaded and what the module reported so we can figure out whether the issue is the log, definition, binary discovery, calibration, or the module itself.

 78 
 on: August 02, 2026, 03:50:27 PM 
Started by eazydaz - Last post by timo_v8t
87F2 – 0261200346 / 037906022CP / 1267356046 
91F2 – 0261200346 / 1267356409 
6574 – 0261200552, Passat G60 
5E0F – usually 0261200280 / 037906022B 
5D4C – same program as 5E0F, padding differs 
841F, 9441 – likely 0261200346 variants 
5CBB, AC34 – modified 0261200346 family 
377E – modified, likely 0261200280 
29E3 – modified, 0261200280/0552 family 
55F5, 798B, FD5A – modified 0261200280/0552 family 
2019 – modified G60 file

 79 
 on: August 02, 2026, 09:34:01 AM 
Started by DennisLFJ - Last post by _nameless
Unless you have 2002 B6 which uses 512kb size bin file, all the various US market 2003-2005 B6 1.8T ECUs can be cross-flashed to use the 8E0909518AK-0003 .bin (1024kb) from the community stage 1 thread;
http://nefariousmotorsports.com/forum/index.php?topic=6955.0

The 8E0909518AK-0003 .xdf file included in the community stage 1 thread is populated with enough parameters to get started tuning but it is missing a lot of other available parameters. There are several other .xdf available for same .bin that contain more populated parameters if you search around.  Attached is my reorganized version of such an .xdf, the parameter addresses all come from other available xdf versions (Joshua Farwell, TylerW), but I have reorganized the parameter categories and descriptions to make them more self descriptive. I did remove/reorganize some of the 5120patch parameters (such as KFLDIMX with 5120 specific conversion factor formula) that was causing me problems for linear PID tuning with the stock pressure sensor, I would not recommend using the attached xdf for making a 5120 sensor conversion, find the original 5120patch version of xdf if you need to do that.     
None of the b6 are 512kb

 80 
 on: August 02, 2026, 07:04:05 AM 
Started by Yoyo65600 - Last post by Yoyo65600
​Hi everyone,

​Finally glad to join the NefMoto community! I'm based in the South of France and passionate about DIY automotive mechanics and ECU tuning.

​I'm currently working on two VAG projects:

​Audi TT Mk2 2.0 TFSI (BWA / Bosch MED9.1): The car currently has a Stage 1 tune from a previous owner, but I'm facing an OBD2 read issue (looks like a locked / protected file or NO READ protection). I'm waiting for a Kess V2 to pull the ID, get a clean stock .ori base, and flash a proper Stage 1 to reset everything before working on my own map (aiming for Flexfuel + HPFP upgrade later).

​Golf 4 1.9 TDI 90 (ALH / Bosch EDC15V): My daily/project car, perfect for learning the basics of logging and tweaking maps without taking big risks.

​My main goal here is to learn how to properly define maps, understand MED9.1 log analysis, and clean up my TT's ECU setup.

​Thanks for accepting my registration, looking forward to reading and sharing with you all!

​Cheers.



Envoyé de mon PJZ110 en utilisant Tapatalk


Pages: 1 ... 6 7 [8] 9 10
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 1.563 seconds with 12 queries. (Pretty URLs adds 0s, 0q)