v2 procedures: beta and operational

Where: Remote sessions › Diagnosis › Service functions › Channel “v2 procedures (beta)”

Important: They are unvalidated candidates and only run on the Hub's own or development units. Always compare the result with the manufacturer's manual or tool.

1. In the Hub, open Tools › Function catalog › Imported library and, in “Own units: beta and operational”, select “Enroll in beta” next to the unit. Enter the justification and the days (30 at most).
2. Have the unit in front of you: when it receives the order, the LED turns blue and it beeps. Press its button within 60 seconds. Without that press it does not store the beta key.
3. Check that the unit shows “With v2” (firmware 0.2.0 or later) and “In beta until…”.
4. In Service functions, choose the channel “v2 procedures (beta)” and select “Prepare” on the procedure.
5. Choose the unit, enter the vehicle details and, if the procedure asks for them, the ECU and the values for the evaluation. Select “Run on the unit”.
6. While it runs, answer what the unit asks for (ignition off, start the engine, raise the engine speed…). Only the person who started it answers, from the web or the app.
7. When it ends you will see the data of each ECU and the verdict of each rule with the source of its threshold.

• “Not enough data: repeat the phase” means there were not enough samples or the phase was not done as asked.
• “No verdict” appears when the rule has no sourced threshold: the value is shown as it is.
• “Stop” ends the run at any time; the unit leaves the ECUs in a safe state.
• If a procedure writes to the vehicle, the unit also asks for its button and a stationary vehicle before each write.
• With the unit in beta, “Enroll as operational” sends it another order: press its button within 60 seconds. From then on it receives the operational procedures. “Withdraw from operational” takes it back to beta and “Withdraw” erases its beta key and its operational mark.
• In the imported library, “Make operational” needs at least one completed beta run of the procedure and records who validated it, when, with which unit and on which vehicle. “Operational now (trusted source)” only appears when every source is trusted and the procedure does not write to the vehicle.
• One person with the publication permission publishes it, and it stays in the audit log. If the Hub turns the second approval on (Hub settings › Trusted sources and procedure publication), another person approves it. Changing those settings always needs two people.

Tip: Before the tests, write down the unit, the firmware version and the vehicle (make, model, year and VIN). Keep the full result; the platform keeps the samples.

Open the platform See it in the help centre