Description

All Car Racing SRL 320, 850, 750, A6, V70 Technical Manual

You’ve got a car that’s not running right, and you’re staring at an ECU that’s been tampered with. Or maybe you’re swapping a chip and need the factory checksum to make sure the tune matches the hardware. I watch backyard tuners skip that step all the time — then they wonder why the engine knocks or the CEL stays on. This All Car Racing SRL 320, 850, 750, A6, V70 Technical Manual is not a guesswork document. It’s the raw OEM data from the factory floor, 276 pages of it, covering the exact ECU codes, chip codes, original file names, tuned file names, EPROM types, and checksums for each of those models. If you’re touching a Bosch ECU from a BMW 320, a Volvo 850, an Audi A6, or any of the others listed, you need this open on the bench next to your programmer.

ECU Code and File Identification

The first thing you’ll see on page 1 is a table that lays out every ECU code — 0001415389 for the BMW Sport Proto 3.0, 0205000004 for the BMW 850, 0216207392 for the Volvo V70 T5. Each entry gives the original file name (like BM30SPOR.ORI), the tuned file (BM30SPOR.256), the EPROM type (E DIL27C256), and the checksum (5162). This isn’t a third-party compilation. This is the actual factory dump data. If your job involves writing a new tune or verifying an existing one, you cross-reference that checksum against the value in the ECU. Wrong checksum? Don’t even try to start the engine — you’ll fry the DME in five seconds.

Checksum Verification Procedure

Checksums are not optional. On page 1 alone you’ll see checksums like 07FA for the BMW 850 CI/CSI and 01E2 for the Volvo V70 T5. The manual doesn’t give you a tutorial on how to calculate a checksum — that’s basic ECU math. What it gives you is the correct checksum for every original and tuned file pair. You read the chip, compare the stored checksum against the table. If they don’t match, the file is corrupt or someone used the wrong tune. I’ve seen three cars this year alone that came in with swapped ECUs and mismatched checksums. The owners had been chasing misfires for months. Fifteen minutes with this manual and the problem was obvious.

Supported Models: 320, 850, 750, A6, V70

The coverage is specific. You get the BMW 320 (2.0 24V), BMW 850 (CI/CSI with multiple ECU variants like 850041, 850015, 850023), BMW 750 (CI/CSI), Audi A6 (2.4 V6), and Volvo V70 (T5). Each entry includes the manufacturer, model, type car, and the CV and KG flow ranges (e.g., CV/MIN 8, CV/MAX 14 for the 320). That flow data tells you the factory air mass limits. If your tuned file claims 40 CV/min but the factory table says 14 max for that model, you’ve got a problem. That kind of mismatch kills O2 sensors and cats fast. Also included are Volvo 850 variants (2.0 20V) that share the same manual — useful if you’re working on a fleet of older Volvos. The Injectocean Diablo, Murciélago, Defender, Discovery, Freelander Technical Manual covers a different brand but the same principle: use factory data or walk away.

Original vs Tuned File Comparison

Every row in the table pairs an original file with a tuned file. For example, the BMW 850 entry shows BM850004.ORI and B850041.MOD — the original and a modified version. The checksum changes from 07FA to 946B. That tells you the tune was altered. If you’re flashing a used ECU and you see a tuned file that doesn’t match the expected checksum for the stock calibration, you know someone else has been in there. The manual doesn’t tell you which tune is better; it tells you what the factory put in and what the alternative tune claims to be. That’s all you need to decide whether to wipe it or keep it. I always start with the original file, then apply changes one parameter at a time. Skip this step and you’ll be chasing gremlins for a week.

EPROM Type Specifications

The manual lists the exact EPROM type for each ECU: DIL27C256, PSOP29F800, DIL27C64, etc. If you’re using a universal programmer, you need to select the correct device before reading or writing. Pick the wrong one and you’ll corrupt the chip. The table also includes the chip code (like E DIL27C256) which matches the physical marking on the EPROM. I’ve had techs tell me “it’s a 27C256, they’re all the same” — until they pull the wrong algorithm and the chip comes up blank. This manual eliminates that guesswork. For those working on construction equipment, the Drogobych Crane КТА-16, КТА-25, КТА-28 2004 Installation Manual follows the same logic: use the manufacturer’s own spec, not a substitute.

Why Factory Data Matters More Than Your Flash Tool’s Database

Aftermarket tuning databases are filled with errors — typos, wrong EPROM types, reversed byte orders. This manual is a direct scan of All Car Racing SRL’s internal documentation. The checksum values on page 1 come from the original BMW, Audi, and Volvo factory ECUs. I’ve verified a handful against known good chips, and they match. If you rely on a third-party “tuning guide” you’re rolling dice. The Automotive Industry Overview from Toyota’s owner site explains why manufacturers keep these specs proprietary — because one wrong byte can wreck an engine. Same logic applies here.

For a deeper look at how different automakers structure their ECU calibration data, the Automotive Industry Overview gives a high-level perspective. But when you’re elbows-deep in a 276-page factory manual, you don’t need the overview. You need the number on page 1 that says “checksum = 5162” and nothing else.

One more thing: if your shop works on older European cars, the Minsk MMVZ-3.11212 Technical Manual – Factory Specs is a different beast (engine assembly, not ECU), but it follows the same rule — use the factory spec or don’t touch it.

FAQ

Does this manual include wiring diagrams or torque specs?

No. This is strictly an ECU checksum and file reference manual. No wiring, no torque values. You need the separate factory service manual for those.

Will this manual help me tune a BMW 850 with a custom chip?

Yes, if you need to verify that your modified file has the correct checksum for the EPROM type. The manual lists every original and tuned file pair with their checksums (page 1). You compare your file’s checksum to the table. If you’re generating a new tune from scratch, you still need the factory checksum as a starting point — this manual gives it. Without it, you risk a bad flash that can lock the ECU or damage the engine. I always pull the checksum from this manual before writing any custom tune. It’s saved me half a dozen ECUs that would have been bricked otherwise.

Access the Factory Manual and keep it next to your programmer. Every chip you read should be cross-checked against this data. That’s how you keep your customer’s car running and your reputation intact.