An implausible network message is different from a completely missing network connection. Ross-Tech’s U1122 reference describes a specific Audi Q3 F3 lane-change-controller case involving software guidance. The reporting module and extended fault text define that example’s scope.
Preserve the extended description
Send the full lane-change report, controller software identity and all related faults. A generic reader showing only U1122 leaves out the information needed to compare the vehicle with the published example. Do not assume every U1122 on every VAG model has the same cause.
Record the actual symptom, including whether the assistance function is unavailable continuously or only in particular conditions. Mention bumper work, sensor replacement and prior software operations without treating any of them as an established cause.
Separate message content from wiring integrity
A network complaint does not automatically justify harness replacement. Equally, a software reference should not suppress physical checks where the vehicle’s evidence calls for them. The diagnostic plan should explain why the selected route fits this case.
AXION can review supported network and programming enquiries using that evidence. Any manufacturer bulletin must be checked against the current vehicle specification. Driver-assistance warnings require their own verification after repair; a code clear does not establish correct sensor performance.
Arrange an assessment
For complex electrical and network diagnostics, send the vehicle details and fault report to AXION. We support enquiries from drivers and garages. Workshop, postal and remote options depend on the job and are confirmed before booking.
Technical reference
Read the supporting technical documentation. The referenced design or vehicle application defines its scope; it is not a universal repair procedure.
Related reading
CAN arbitration is normal traffic management, not a wiring fault. Browse the automotive electronics repair library for other systems and symptoms.