Where should a new workshop start?
Start with the readiness check, build a structured request brief and confirm the read method before opening the secure request.
MG AutoTech Workshop Library
A compact index for request preparation, service selection, vehicle and controller identification, read methods and practical workshop tools.
Cornerstone guides
Focused guides for the questions that should be settled before a private ECU or TCU file request starts.
Understand how a professional online ECU file-service request moves from vehicle identification and original-file preparation to review, status tracking and secure delivery.
Read workshop guideA practical request-preparation guide for TCU and gearbox file service, including controller identity, transmission context, separate original reads and secure delivery.
Read workshop guideA customer-safe workshop guide to OBD, bench, boot and virtual ECU reads, why read method matters and what information should accompany a file-service request.
Read workshop guideUse a concise workshop checklist to prepare vehicle, ECU or TCU, read-method, service, diagnostic and original-file context before secure submission.
Read workshop guideLearn what ECU hardware, software and calibration identifiers contribute to a file-service request and why exact identity matters more than model name or file size.
Read workshop guide01 - Start here
Use the existing preparation tools before the secure upload so vehicle, service and workshop context arrive together.
02 - Service scope
Understand the available public request categories before entering the authenticated customer workflow.
Performance, diesel, diagnostics, transmission and support categories.
Vehicle context, original-file preparation and review workflow.
Required diagnostic and workshop context for a DPF request.
Prepare the relevant vehicle, ECU and diagnostic details.
Structure the request with exact symptoms and controller context.
Provide exact diagnostic codes without exposing private file data.
03 - Identification
Vehicle badges alone are not enough. Use brand, platform, ECU or TCU and read-method context before submission.
Workshop-oriented identification notes for supported brand families.
Controller-family identification and request preparation context.
Browse the public vehicle and engine context without private metadata.
Review the secure request boundary and available public routes.
04 - Workshop tools
Use transparent browser-based tools for preparation and estimates. These tools do not modify or upload ECU files.
Quick answers
Start with the readiness check, build a structured request brief and confirm the read method before opening the secure request.
No. These are public preparation routes. Private upload, credits, messages and delivery remain inside the authenticated portal.
No. ECU or TCU identity, software context, read method, file quality and workshop notes can all affect support and review.
Customers track request status, messages and available downloads inside their protected dashboard.
Use the public brand and platform guidance before the secure request.
Browse brandsReview the read-method checklist when OBD, bench or boot context is unclear.
Plan read methodRun a customer-safe readiness check before uploading the original file.
Check readiness