|
# 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.
|