If a scanner cannot communicate with a vehicle or a particular controller, record the tool and adapter being used as well as the fault. The age of the car or the shape of its diagnostic socket does not establish that every interface supports every required function.
What the component does
Kvaser describes CAN FD as an extension of Classical CAN that can carry a larger data payload and use a faster data phase. Classical CAN allows up to 8 data bytes per frame; CAN FD allows up to 64. The network and interface requirements matter for reliable communication. CAN FD capability alone still does not establish that a tool supports a particular manufacturer’s diagnostic functions, software access or programming procedure.
Information that helps an assessment
Include the vehicle model and build year, scan-tool make/model, software version, adapter details and the exact communication error. State whether the same tool can read other controllers and whether any authorised update or replacement preceded the problem. Preserve logs from failed programming attempts and avoid repeated attempts with unconfirmed equipment or instructions.
Before ordering or removing a unit
A fault message identifies a system to investigate; it does not prove that its control unit needs replacement. Record the complete scan report and component identification before codes are cleared or parts are ordered. Repair suitability depends on the exact unit and the findings from diagnosis.
AXION handles automotive electronics enquiries from Didcot, Oxfordshire. Contact us with your vehicle details before arranging a workshop visit or posting a module. Use the vehicle and module finder or browse the repair library.
Technical reference
Kvaser: Classical CAN and CAN FD overview. This guide is an original overview for assessment preparation, not a vehicle-specific repair procedure.