Speed-limiter software requests for a defined application.
Confirm the vehicle, control-unit version and intended use before requesting a change to an electronic speed limit. Availability and permitted use must be assessed for the specific project.
On this page3 topics ⌄
01
Software scope and vehicle limits
Changing a software limit does not establish that tyres, brakes, drivetrain or operating conditions are suitable for higher speeds. State the complete configuration and clarify the required vehicle-related checks.
02
Confirm inclusion and separate pricing
VMax Off is included in the current Stage 1 and Stage 2 base services; it is also listed as a separate option. Check the applicable scope and availability in the portal before ordering.
Keep the original data and record the delivered version. Verification belongs in a safe, permitted environment with a suitable procedure, not an uncontrolled road test.
A speed-related enquiry should explain the observed behaviour, the control-unit data and the intended application. State whether the request forms part of an engine calibration or concerns a specific software function. Avoid reducing the brief to a model name followed by a target speed; that does not identify the relevant software or vehicle conditions.
Include the engine and transmission configuration and any changes that matter to the project. If the vehicle behaves differently from the customer's expectation, provide the workshop's findings first. The technical discussion needs to distinguish a requested limiter adjustment from another reason the vehicle may not achieve a particular operating condition.
02
Identify the software before selecting an option
Upload the appropriate original file and the ECU identification, with the tool and read method used. Where the request also involves transmission software, provide the relevant TCU details. A vehicle family or a previously supplied file is not sufficient to establish the correct software change for a different controller.
If the vehicle has been updated or tuned before, record that history. The available reading method may supply a different kind of starting file, so identify a normal read or virtual read accurately. Keep recovery data separately and ask about an unfamiliar format before altering or repackaging it.
The current price list states which base services include VMax Off and which separate options are available. Review that information with the intended order so the same requested function is not treated as an unexplained extra. The portal confirmation should reflect the agreed software work and any additional requirements.
An included option still needs a compatible software version and a defined application. Inclusion in a price does not establish that every controller implements a speed-related function in the same way. Clarify the actual request before development rather than assuming that a similarly named option has the same scope across vehicle platforms.
Confirm how the requested function will be checked without relying on an uncontrolled high-speed road test. The workshop should determine the suitable vehicle assessment and permitted test setting for the application. A software change alone does not establish that the wider vehicle is suitable for a different speed range.
Keep the test objective specific. If there is a question about the delivered file, explain the conditions and the available evidence. Do not infer the responsible function from a dashboard value alone. The relevant control-unit information and a clear description help the development discussion address the actual observation.
Retain the conditions agreed for the delivered file
Document the installed version, the requested work and the vehicle configuration at delivery. A later software update, hardware change or different use may require the project to be reviewed. Keep the original data and order correspondence so that subsequent work starts from an identifiable record.
If a revision is needed, use the existing order and state what has changed since the first request. Attach the appropriate diagnosis or measurement material with its context. That process is more useful than sending a previous file without explanation and asking for a more aggressive setting.
