30/09/2026
PRECISION REMAPS UK TOOL MASTER — PRIVATE WORKSHOP PORTAL 💻
Something I’ve been building behind the scenes for quite a while is now starting to come together.
https://precisionremapsportal.com/login
The Precision Remaps UK Tool Master is a private ECU / TCU workshop platform I’ve personally built around the information we use every day for tuning, cloning, recovery and replacement-module work.
Instead of jumping between different manufacturer websites, PDFs, clone lists, spreadsheets and individual tool software, the portal brings the information together into one searchable system.
Current core coverage is built around:
• Magic Motorsport FLEX
• AutoTuner
• Alientech KESS3
The database already contains tens of thousands of vehicle, ECU, TCU and protocol records, alongside our dedicated FLEX clone database.
WHAT THE TOOL MASTER CAN SHOW
Search by:
• ECU / TCU family
• Manufacturer
• Vehicle / model
• Processor / MCU
• Tool
• Required job
• Connection method
• ECU or TCU type
Then compare the available programming routes, including:
• OBD
• Bench
• Boot
• Boot Glitch / Korhex
• Real Read
• Virtual Read
• Mail-In Unlock
• Patch / Password operations
• Beta / Coming Soon protocols
• Tuning capability
• Clone capability
One of the biggest reasons for building it was that ECU work is rarely as simple as:
“Does my tool support this ECU?”
You actually need to know:
Which tool supports it?
Which protocol?
OBD, Bench or Boot?
Does it need unlocking first?
Is it a real read or virtual read?
What memory areas are actually available?
Can it genuinely be cloned?
Does the donor HW/SW need to match?
Is an external EEPROM transfer required?
Does Technical Support need to adapt the data?
Those are completely different questions.
The portal is designed to make those distinctions clear before the vehicle or control unit is touched.
FULL FLEX CLONE INFORMATION
The FLEX section uses the clone classifications we work with:
1-to-1
Cloning can be completed by writing the full backup, or the individual supported memories, from the original ECU / TCU into the replacement unit.
No Clone
No supported cloning solution is currently available for that ECU / TCU type.
Not Tested
Cloning has not been validated by FLEX. The original dump may potentially be written into the replacement unit, but a functional result is not guaranteed.
1-to-Staff
Cloning requires a FLEX Technical Support ticket, with original and replacement data adapted by FLEX staff before programming.
1-to-Service
Cloning is completed through the FLEX automatic service.
1-to-1 EEPROM
Programming is combined with physical transfer of the required external EEPROM where specified.
So we do not treat “Bench supported” or “Full backup available” as automatic confirmation that an ECU can be cloned.
VEHICLE-SPECIFIC COVERAGE
Individual ECU records can include:
• Vehicle manufacturer
• Model
• Year
• Engine
• Power output
• Fuel type
• ECU / TCU
• Processor / MCU
• Available programming methods
• Related clone family
• Source information
• Matching and compatibility notes
Exact ECU identity always takes priority over a shared family name.
Hardware, software, MCU, immobiliser generation, PCB revision, vehicle application and tool licence can all affect whether a particular operation is possible.
BUILT-IN WORKSHOP & POSTAL JOB CHECKS
I’ve also built workshop and postal-job preparation directly into the portal.
We can record:
• Internal job reference
• Vehicle / registration
• Original ECU / TCU part number
• Original HW / SW
• Replacement / donor part number
• Donor HW / SW
• MCU verification
• Required dumps
• EEPROM requirements
• Pinout and cable requirements
• Stable power-supply checks
• Protocol and licence requirements
• Support / service / unlock requirements
• Existing faults
• Physical ECU condition
• Customer and return details
• Tracked postal packaging information
This is especially useful for postal ECU / TCU cloning and recovery work, where confirming the exact original and replacement units before programming can save a huge amount of wasted time.
CONNECTION & FILE METHOD REFERENCE
The portal also includes workshop-reference information explaining the difference between:
• OBD
• Bench
• Boot
• Boot Glitch / Korhex
• Real Read
• Virtual Read
• Mail-In Unlock
• Patch / Password
• Beta / Coming Soon coverage
For example, a calibration read does not automatically mean you have EEPROM or immobiliser data.
A virtual read is not the same as reading the actual contents currently stored inside the ECU.
A Bench protocol does not automatically mean the unit can be cloned.
A supported OBD protocol may still require an unlock first.
These distinctions matter when deciding whether a job is tuning, cloning, recovery, commissioning or data transfer.
DIAGNOSTICS & REPLACEMENT-UNIT COMMISSIONING
The platform also sits alongside the diagnostic side of the workshop.
For jobs involving Autel, Snap-on, ODIS or dealer-level software, the portal can be used as the programming reference while the correct diagnostic, adaptation, coding or security function is verified separately.
A replacement ECU, TCU or module may still require:
• Coding
• Adaptation
• Alignment
• Immobiliser synchronisation
• Basic settings
• Component protection work
• Post-programming commissioning
depending on the vehicle and module involved.
CONSTANTLY DEVELOPING — MORE TOOLS COMING
The current FLEX, AutoTuner and KESS3 coverage is only the beginning.
Over time I intend to expand the compatibility database to include additional professional programming platforms such as:
• CMDFlash
• PCMFlash
• BitBox
• Additional ECU / TCU programming tools as their data is integrated and verified
The long-term aim is to search one ECU or vehicle and compare the available programming routes across multiple tools from one screen.
So rather than checking five or six separate compatibility systems, the portal could eventually show:
FLEX — OBD / Bench / Boot / Boot Glitch / clone status
AutoTuner — supported methods and vehicle applications
KESS3 — supported protocols and access methods
CMD — compatible protocol and method
PCMFlash — module / package compatibility
BitBox — module and ECU support
Along with:
• Unlock requirements
• Patch / password procedures
• Real vs virtual read information
• Processor / MCU requirements
• Clone capability
• EEPROM requirements
• Licence / package requirements
• Known restrictions
• Special procedures
The important part is that new data will not simply be dumped into the system.
Different tool manufacturers describe the same ECU, processor, vehicle and access method differently, so the information needs to be normalised, matched and checked before it becomes useful.
FUTURE ECU KNOWLEDGE BASE
Another section I’m considering adding is a proper ECU-specific workshop knowledge base.
That could go beyond simple compatibility and include practical information such as:
• Components that should be unplugged for certain software solutions
• Pre-write checks
• Post-write ignition procedures
• Adaptation resets
• BMS / battery-monitor resets
• Immobiliser-related faults that may appear after certain programming operations
• Procedures for clearing or relearning those faults
• Known post-remap issues on particular vehicles
• Diagnostic checks before and after writing
• Common recovery procedures
• ECU-specific warnings
• Vehicle-specific programming quirks
• Relevant coding or commissioning steps
• Practical tips learned from carrying out the jobs repeatedly
So eventually, instead of the system only saying:
“This ECU is supported.”
It could tell you:
Which tools support it → how they connect → what they actually read → whether they can clone it → what needs checking before programming → what commonly catches people out → what may need doing afterwards.
That is where I ultimately want precisionremapsportal.com to go.
LIVE DATA & CONTINUOUS MAINTENANCE
This is not intended to become another static compatibility spreadsheet that is outdated six months later.
A lot of time has gone into personally collating, cleaning and matching the data across different tools and sources.
The platform is being built to re-check the underlying coverage information and surface changes as manufacturer support evolves.
There will always still be a final technical verification before carrying out a job, particularly where hardware revisions, MCU versions, immobiliser generations, Beta protocols or licence requirements are involved.
ACCESS, SUPPORT & SUBSCRIPTIONS
I’m still working out exactly how external access will operate.
Because of the amount of work involved in building and maintaining the database, it will likely remain a controlled-access platform with individual accounts and potentially a subscription model.
I’m also still deciding how technical support will work alongside it.
That may range from database access only through to higher levels of support for specific jobs, depending on how the system develops.
The priority at the moment is getting the technical platform and the underlying information right before opening it more widely.
This has taken a considerable amount of time to build properly, and there is still plenty more to come.
The objective is simple:
Identify the ECU correctly.
Choose the right tool.
Choose the correct access method.
Understand exactly what is being read.
Confirm cloning capability separately.
Check the job requirements.
Then carry out the work.
No guessing from an ECU family name.
No assuming a Bench read automatically means a clone.
No turning up to a vehicle before checking whether an unlock, support service or different access method is required.
Diagnostics first. Results that last.
Precision Remaps UK
Diesel Diagnostics & ECU Calibration Specialists
5★ Rated Service | Workshop & Nationwide Mobile Coverage
Office 41, Curzon House
Curzon Street
Burton upon Trent
DE14 2DH
07356 062066 WhatsApp & SMS