BMW E46 MSS54/MSS54HP — DTC Removal & CSL-HP Conversion Tool (Beta)
Hey all - I've been building a web-based tune file utility for myself and figured it was time to let a few people kick the tires before any wider release. Happy to take constructive feedback.
What it is: A browser-based tool for modifying MSS54/MSS54HP partial BIN files. No install, no OS dependency, works on mobile. The whole idea came from being tired of doing repetitive hex editor work for tasks I do regularly.
What it does:
What it isn't: This won't replace TunerPro/XDF for serious tune work, and it can't flash — you'll still need MSS Flasher or ECUworx for that. It's a focused utility for automating the specific tasks I got tired of doing by hand.
Testing: I've done a fair amount of negative testing myself against a personal library of stock and modified BIN files covering a mix of MSS54, MSS54HP, and MSS54HP-CSL variants, but more real-world testing across different files and versions would be really valuable. If you have files to test against and spot anything unexpected I'd love to hear about it.
Future direction: Long term I'd love to add flashing capability (EDBIAS-style integration like MSS Flasher would be ideal) and eventually bring in some of the existing ECUworx functionality so everything lives in one place. For now the focus is on making what's here solid and useful before expanding scope.
Tech: Built on Flutter/Dart — first time diving into it, been a fun experience. Deployed on Netlify, pretty small footprint.
Credit where it's due: The DTC database comes from the PDF resources here on the forums (converted to CSV), and the DTC definitions from Polar's work. I didn't discover anything new here — just built tooling around existing community knowledge. Appreciate everything this forum has contributed.
Tested on Chrome and Brave — Safari testing coming soon via BrowserStack.
🔗 Tool: https://mss54dtctool.netlify.app 📄 Documentation: https://docs.google.com/document/d/1...it?usp=sharing
Bandwidth is on a free Netlify account so if it gets hammered I'll sort that out — should be fine for low volume testing.
A note on DTC deletion methods: There are several ways to zero out a DTC and I went with the full 14-byte zero method since that's what's always worked reliably in my own testing. Worth noting that ECUworx uses a different approach — it only zeroes the 13th byte. I looked into supporting that method but ran into too many false positives during testing: a number of offsets in completely stock untouched tune files already have the 13th byte set to 00 by default, even though the documentation defines it as 01. Until I can reliably distinguish intentional patches from stock defaults I'm sticking with the full 14-byte method which is unambiguous.
Anyway — thanks for reading, go easy on me.
What it is: A browser-based tool for modifying MSS54/MSS54HP partial BIN files. No install, no OS dependency, works on mobile. The whole idea came from being tired of doing repetitive hex editor work for tasks I do regularly.
What it does:
- Deletes DTC codes from BIN files and validates the changes against a known database
- Auto-detects ECU type (MSS54 vs MSS54HP vs MSS54HP-CSL) from the file itself
- HP Conversion modifications: pressure sensor scaling, vanos offsets, injector 151 DTC
- Bidirectional — patch forward or revert back to stock
- Scan a loaded BIN to find previously zeroed DTCs and restore them
- Drag and drop or browse file upload
- Post-patch verification so you're not second-guessing your work
What it isn't: This won't replace TunerPro/XDF for serious tune work, and it can't flash — you'll still need MSS Flasher or ECUworx for that. It's a focused utility for automating the specific tasks I got tired of doing by hand.
Testing: I've done a fair amount of negative testing myself against a personal library of stock and modified BIN files covering a mix of MSS54, MSS54HP, and MSS54HP-CSL variants, but more real-world testing across different files and versions would be really valuable. If you have files to test against and spot anything unexpected I'd love to hear about it.
Future direction: Long term I'd love to add flashing capability (EDBIAS-style integration like MSS Flasher would be ideal) and eventually bring in some of the existing ECUworx functionality so everything lives in one place. For now the focus is on making what's here solid and useful before expanding scope.
Tech: Built on Flutter/Dart — first time diving into it, been a fun experience. Deployed on Netlify, pretty small footprint.
Credit where it's due: The DTC database comes from the PDF resources here on the forums (converted to CSV), and the DTC definitions from Polar's work. I didn't discover anything new here — just built tooling around existing community knowledge. Appreciate everything this forum has contributed.
Tested on Chrome and Brave — Safari testing coming soon via BrowserStack.
🔗 Tool: https://mss54dtctool.netlify.app 📄 Documentation: https://docs.google.com/document/d/1...it?usp=sharing
Bandwidth is on a free Netlify account so if it gets hammered I'll sort that out — should be fine for low volume testing.
A note on DTC deletion methods: There are several ways to zero out a DTC and I went with the full 14-byte zero method since that's what's always worked reliably in my own testing. Worth noting that ECUworx uses a different approach — it only zeroes the 13th byte. I looked into supporting that method but ran into too many false positives during testing: a number of offsets in completely stock untouched tune files already have the 13th byte set to 00 by default, even though the documentation defines it as 01. Until I can reliably distinguish intentional patches from stock defaults I'm sticking with the full 14-byte method which is unambiguous.
Anyway — thanks for reading, go easy on me.