OnlineTool After replacing a control unit, its protected communication with other vehicle units may need to be restored. Settings may already be written, while the program still requires validation. This is a separate repair stage involving electronic certificates and unit bindings.
The CBB Validation service prepares a response to the original request from that procedure. This guide explains the terms, where the request comes from and how to use the result.
What CBB Validation means
CBB means Certificate and Binding Box. It is the system for working with control unit certificates and bindings. In E-Sys, the corresponding module is Certificate Management.
ECU means electronic control unit. Here, the relevant units use individual certificates and associated data for protected communication within the vehicle.
Validation means checking those certificates and related unit data to establish whether they are valid. A repair may require obtaining and writing new data, then performing the check again.
The service processes a request. The response must still be applied in the program carrying out the repair procedure, and the result checked in the vehicle.
Certificates and bindings explained
A unit's electronic certificate contains digital data used to establish its identity in protected communication. The certificate and its validity matter during checks.
A binding links a unit to the relevant vehicle. The system may also use data defining which units can establish protected communication with each other.
Think of a team whose members need to be recognised and allowed to interact. A vehicle checks this using digital data, rather than the name printed on a unit's housing.
Two units that look identical may belong to different vehicles. Matching models do not make their certificates and bindings interchangeable. Do not select a response from another repair merely because the ECU name is familiar.
When a repair needs validation
Unit replacement is one case where protected communication may need restoration. Validation can be part of the repair plan after replacing certain multimedia, telematics or instrument cluster units.
After a head unit replacement, for example, the vehicle must work correctly with the installed device and its interaction with other units. The affected units need the appropriate certificates and related data.
Participants and repair procedures vary by vehicle. Determine whether validation is needed from the procedure and diagnostic results. Replacing any unit does not automatically mean that CBB Validation must be ordered.
If validation fails, the program message helps locate the stage involved: data preparation, application or the subsequent check. It is more useful than simply saying “the unit does not work”.
How CBB differs from other operations
Coding provides settings for the vehicle and equipment. CBB concerns certificates and bindings, so coding and validation may be separate stages of one repair.
KDS concerns component theft protection and the link between a protected component and the vehicle. It uses its own request and token. The word “binding” in both explanations does not make the procedures interchangeable.
SFA manages permission for protected features. Restoring a feature permission is a different task from checking a unit's certificates.
FSC is another type of permission used for particular functions and procedures. A CBB response does not replace an FSC.
The repair plan and program show which result is required at each stage. For CBB, keep the original validation request.
The request and the service result
A request is created by the working program for the current vehicle and procedure. A response is prepared from that request for application afterwards.
Create the request in the certificate and validation procedure. Save it unchanged and submit it for CBB Validation. VIN and equipment information help describe the vehicle but do not replace the request.
FA and SVT also have different purposes. SVT may be needed when preparing the procedure because it describes the unit configuration. The data submitted for CBB are the created request, rather than the unit list alone.
After processing, keep the response with its request so their purpose remains clear. Apply the result in the procedure that created the request.
The general sequence is create a request → obtain a response → apply it in the original program → perform the check. Processing an order produces the digital result. Completion of the vehicle work is checked separately.
Example: a CBB request and response in E-Sys
This example uses the standard Certificate Management module in E-Sys 25.10.01, on Offline. The CBB Validation service accepts a request from this module, and its response is applied through Write data.
1. Prepare the vehicle data
With the vehicle connected, open Certificate Management. Read the current unit configuration with Read SVT (ECU) and VIN with Read VIN. If loading a saved SVT Actual, it must relate to this vehicle; enter VIN in the corresponding field.
The SVT tree shows units using individual certificates. The standard module works with all such units in the tree. Individual ECU selection is provided in the extended module.
2. Create the original request
On Offline, under Create CBB Request File, select Read data and create temporal CBB Request File. E-Sys reads the required data and creates the request.
Save the request without manual edits and submit it for CBB Validation. Keep the prepared response with it after processing.
3. Apply the appropriate response
Under Write data, select the response using … beside Use locally available CBB Response File. Write data starts writing the data to the units.
The request is used to prepare a result; the response is used to apply it. Keep both until the work is complete.
4. Perform the check
Select Start data check. E-Sys checks certificates, bindings and related data for the units shown in the tree. Results appear in SVT, and a result file is saved in the Cert folder.
Use the result of the newly performed check. Reading a previously stored status may show an earlier result and does not establish the state after the new write.
After a successful check, complete the remaining repair steps and test the affected equipment in the vehicle. This establishes both the digital state of the units and the repair result needed by the customer.
Obtain a CBB Validation response
Keep the original validation request. Apply its response through Write data, then perform a new check of the unit data.
Orders are handled through the Telegram bot. Open the bot from the service page, check the selected service and follow its input instructions. Keep the result for the original procedure.