Most confusion around Security Gateways occurs when the diagnostic tool performs some functions normally but refuses others. The technician then naturally tries to determine whether the problem is in the device, the licence, vehicle communication or the vehicle itself. Very often the answer is: it is not a fault, but a vehicle security rule.
SGW typically distinguishes between reading information and writing or actively intervening. Reading is generally less risky. The diagnostic tool asks and the vehicle responds. Writing is more sensitive. The diagnostic tool changes configuration, starts a function, triggers a test, resets values or writes new settings.
Functions that are usually available without unlocking
- reading control unit identification
- reading fault memory on many manufacturers and models
- displaying measured values and system parameters
- basic orientation diagnostics without changing vehicle settings
Functions that may require unlocking
- clearing fault memory on some manufacturers
- actuator tests
- service functions, for example brake pad replacement mode for an electric parking brake
- resetting service intervals where the manufacturer classifies this as a protected operation
- adaptations, basic settings and calibrations
- coding and programming control units
Exceptions that must be known
The rules are not the same for all manufacturers. This is important because a universal statement such as “fault memory can always be cleared without SGW unlocking” would be misleading. On some Fiat vehicles, even clearing fault memory may be blocked without unlocking. On newer Mercedes-Benz vehicles, the protection may be more extensive and communication with control units may not be available in the scope technicians were used to. Newer Volkswagen Group vehicles may also introduce a multi-level model, where the gateway or diagnostic filter must first be addressed before working with protected ECUs.
This is exactly why caution is needed in any article or training about SGW. The topic cannot be reduced to one table valid for all cars. The correct answer always depends on the brand, model, model year, platform, specific control unit and diagnostic tool used.
A short diagnostic logic for workshops
For the workshop customer, SGW is invisible. The customer arrives with a car and expects a repair. For the workshop, however, SGW is an important organisational topic. If the technician discovers the need for unlocking only when the car is already disassembled, it may cause delays. If the workshop has registration, access and process prepared in advance, SGW is simply another step in the workflow.
In practice, it makes sense to have a simple internal routine for newer vehicles: before the service operation, check the model, expected protected functions, availability of access and unlocking time conditions. For TSPro and Troodon diagnostics, these accesses are managed through the DevCom diagnostic portal.