Procedures that write, program or authenticate
What protects each write to the vehicle and what is not available yet.
Reviewed by Daniel Morales, founder of Reprorace SL, on
Where: Remote sessions › Diagnostics › Service functions › Channel “v2 procedures (beta)”
Important: Everything that writes is in beta, only on enrolled own units, and has not yet been tested on real vehicles. Always compare with the manufacturer's information.
| Type | What it does and what it asks of you |
|---|---|
| Read | Reads values, faults and identification. Changes nothing. |
| Writing a value | Reads the value, keeps a copy, writes, reads it back and restores the previous one by itself if something fails. You see “Changed values” with before and after. |
| Routines and resets | Ask you to confirm, the second factor, the vehicle stopped and a press of the unit's button. |
| Security access | The key is calculated by a contracted provider. Without a provider you see that it is not available. |
| Programming | Only from the web, with the passkey, the approval of two people other than you and the customer's consent. |
| Control unit authentication (UDS 0x29) | Not available yet: it is a draft waiting for tests and a provider. |
1. Before programming
- Connect a battery charger and do not remove it until it finishes.
- Leave the vehicle stopped, with the engine off. Do not disconnect the unit or switch the ignition off.
- Tick “I have read the notice and the vehicle is ready”, press “Prepare the programming” and, with the approvals, “Program now”.
- Press the unit's button when asked. If the control unit is not the expected one, nothing is touched.
- The unit requires at least 12.5 V on 12 V vehicles and 25 V on 24 V ones.
- If it is interrupted, “Resume programming” appears, which again needs the two approvals.
- “Emergency stop” halts the operation: type the word you are asked for and the reason.
- The vehicle identification, the airbag and pyrotechnics are never written. Immobilizer and keys are excluded.
Tip: The unit checks the button and that the vehicle is stopped on its own: confirming on screen is not enough.
More guides in this section
- How a remote session works
- Tunnel plan: connect a tool to the vehicle remotely
- Accept or withdraw remote access to your vehicle
- Collaborating in a session: messages, prompts and photos
- Unit PassThru mode from the app
- PassThru on Mac, Linux and iOS
- Assistance requests, appointments and work orders
- Legacy vehicle configuration and diagnostics: VAG and other makes
- Modern vehicle coding and programming
- Automatic diagnosis: one tap and it explains
- Reading a vehicle and sharing the report
- CANopen diagnostics for machinery
- Vehicle details: identifying it by the VIN
- Live dashboard, service functions and battery test
- v2 procedures: beta and operational
- Compatibility notices for your tool
- CAN captures
- Pre-purchase report
- Battery health of electric and hybrid cars
- Asking Diaglana for help
- Your first read: understanding the result and what to do
- Diagnosis options: each setting and when to change it
- Workshop settings: requests, orders, network and notices
- Reading: choosing the protocol and understanding the OBD on UDS report
- What a fault code means
- Live data: dashboards, recording and export
- Attaching fault codes to a work order
- ISOBUS: reading and changing an implement's NAME
- Diagnosis over Ethernet (DoIP)
- Download Diaglana PassThru for Windows, Mac and Linux
- Authorizing a PC for PassThru
- Diaglana PassThru updates