Check the controller and software package
FLEX provides OBD, Bench and Boot operations according to controller coverage, protocol and activated software. The diagnostic connection, direct connector access and work on an opened controller are different procedures. Use the method documented for the actual unit instead of assuming that one connection covers an entire vehicle range.
Record the selected operation and controller identification for the file-service order. Check the current manufacturer coverage and your available software modules before scheduling the work.
Understand the encrypted Slave route
A FLEX Master can exchange editable calibration data in the appropriate format. A FLEX Slave uses encrypted files linked to its assigned Master. Send the complete original output and tell us how the device is connected. Do not extract parts from a Slave file or change its extension in an attempt to create an independent calibration file.
Confirm the handling arrangement before the first job. Uploading a file to a different service does not transfer the tool’s Master relationship. If your workshop is changing providers, settle that relationship and the return path before relying on a new file exchange.
Arrange the Master and Slave workflow ↗Build a clear original-file record
Include the original read, ECU or TCU identification, vehicle details and read method. Describe known previous tuning, repairs or software updates. An uncertain starting condition should be identified as uncertain rather than presented as untouched stock. This helps establish what the request can reasonably be based on.
Keep complete backups in your workshop records. If several memory files are supplied for review, explain which read session produced them and how they belong together. A file extension does not establish that a calibration area and a recovery backup contain the same information or can be used interchangeably.
Separate calibration reads from backups ↗Describe the engine calibration
A Stage 1 enquiry should identify the stock hardware, fuel and intended use. For Stage 2, add the actual component changes and the purpose of the build. Asking for an output number without describing the configuration leaves important development questions unanswered, particularly where torque delivery must work with transmission behaviour and component limits.
Request software options separately and state their intended behaviour. Speed-limiter changes and Pops & Bangs depend on the controller software and application. Mention functions already present so the requested change can be considered in context, rather than added to an unknown combination of earlier modifications.
Prepare a Stage 2 file request ↗Specify transmission work and Mapswitch
TCU tuning requires the correct transmission identification and original data. Describe the gearbox behaviour you want reviewed and identify the associated engine software. A general request to improve shifting does not establish which transmission strategy is present or what the customer is experiencing.
FLEX controller coverage and the requested calibration service are separate checks. Verify the relevant TCU operation with the manufacturer and agree the file scope with us. Mapswitch also needs its own ECU-variant check: the presence of a FLEX read does not establish that switching between calibrations is supported for that software.
Review Mapswitch ECU support ↗Return to the same job for technical review
Keep the delivered calibration with its portal order and record which version was written using FLEX. The workshop then carries out diagnosis and checks suited to the completed work. Describe observations in operating terms, with supporting data where available, instead of treating every issue as an unspecified file problem.
For a revision, send the relevant raw recording and identify software version, fuel, hardware and test conditions. Explain any changes since the original request. This lets the discussion address a reproducible vehicle state and preserves a useful history for later workshop visits.
Provide logs for a calibration revision ↗Plan equipment and credit-based services
Choose equipment around the controllers and connection methods encountered in your workshop. Discuss software activation, Master or Slave configuration and required accessories before a purchase. A vehicle name on a broad coverage list should lead to a protocol check, not an assumption that every software variant will follow the same procedure.
Our pricing page lists the current credit-based services and options. Use the portal to submit the original file and agree the required work.
Discuss FLEX and other ECU flash tools ↗Tool manufacturer documentation
Questions about this service
Should I unzip a FLEX Slave file?
Supply the complete output produced by the tool and identify the assigned Master. The encrypted container belongs to its supported handling process; extracting files does not create a new Master relationship.
Can an engine file replace a TCU calibration?
No. ECU and TCU jobs require their respective original data, identification and agreed scope. Explain how the engine and transmission configurations relate when requesting combined work.
