ISOBUS: reading and changing an implement's NAME
See the NAME of each ISOBUS module and change its instances, for example when fitting a second identical implement.
Reviewed by Daniel Morales, founder of Reprorace SL, on
Where: Remote sessions › Diagnostics › Service functions › Channel “v2 procedures (beta)”
On ISOBUS each module (tractor, terminal, implement) is identified by its NAME. If you fit two identical implements, their NAMEs can clash; changing the instance tells them apart.
- “Current or pending ISOBUS NAME of each module (NAME Management)”: read-only. Shows the NAME of each module, or the pending one if a change is half-done. Needs the ignition on.
- “Change the NAME instances of an ISOBUS implement (NAME Management)”: changes only the ECU instance and the function instance of one module.
- Stop the machine: parking brake, engine off, ignition on and task stopped.
- Run the read first to see the NAMEs and choose the module.
- Run the change, confirm on screen and press the unit's button.
- If the module refuses it, nothing changes. If something fails after the change, the unit restores the original NAME.
Important: After the change, the terminal and the task controller may see the implement as a new module and the module may change address. It is in beta and only tested in simulation.
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
- Procedures that write, program or authenticate
- Diagnosis over Ethernet (DoIP)
- Download Diaglana PassThru for Windows, Mac and Linux
- Authorizing a PC for PassThru
- Diaglana PassThru updates