Confirm what the exact Q05 was built with before testing it. Sensor presence, fault-free diagnostics, correct parts, calibration records and a controlled road check each answer a different safety question.
Build a VIN-specific assistance feature list
Use the original market specification, build record where available, vehicle menus, steering-wheel controls and physical hardware to list installed features. Separate collision warning, automatic braking, lane functions, blind-spot monitoring, adaptive cruise, parking sensors and camera views rather than using “full ADAS” as one item. Compare the list with the seller advertisement and diagnostic configuration. The Q05 software and app guide helps distinguish local vehicle functions from region-dependent connected services. Missing hardware, unavailable menus or inconsistent module coding must be resolved before a road test or price comparison.
Keep source and market beside the feature list; another country’s brochure is not proof.
Inspect cameras, radar, glass and repairs
Check the windscreen around forward cameras for the correct glass type, bracket, optical area and installation quality. Inspect bumper surfaces, grilles, radar mounts, ultrasonic sensors, mirrors and camera lenses for damage, paint thickness, distortion or non-standard parts. Review suspension, steering alignment and tyre condition because vehicle geometry can affect aiming and lane behaviour. Ask whether glass, bumper, front-end, mirror or alignment work was completed and request invoices and pre-repair images. Use the accident and flood repair guide when evidence extends beyond minor cosmetic work.
Photograph sensor locations and adjacent repair evidence before adjustment.
Read diagnostic state before clearing faults
Scan assistance, braking, steering, restraint, body and camera or radar modules with compatible equipment. Save active, pending and historical faults, software identifiers, coding and calibration status before clearing anything. Confirm warning lamps and driver messages complete their expected self-test. A dashboard without warnings is not sufficient: a feature may be disabled, coded differently or unable to recognise a fault during a short static check. If a module was replaced or programmed, request its part number, workshop report and post-repair scan linked to the VIN.
Preserve the first scan; a later clean scan cannot show what changed.
Verify calibration and test functions safely
Determine which repairs or alignments require static or dynamic calibration under applicable service information. A receipt stating “reset” is not a calibration result. Record target equipment, workshop, date, ride height or tyre conditions and pass criteria where available. Conduct permitted function checks in safe conditions with a qualified driver, observing warnings and response without deliberately creating danger. Assistance has operating limits and does not replace attention. Road markings, weather and traffic may prevent complete dynamic assessment, so label every untested function clearly.
Record test limits and never turn the road check into a safety demonstration.
Confirm destination support and unresolved cost
Identify a destination workshop that can diagnose and calibrate the exact market version, then confirm access to compatible glass, brackets, radar, cameras, sensors and software. Check whether local rules restrict assistance functions or require inspection after repair. Add diagnosis, alignment, calibration and parts to the Q05 landed-cost worksheet. Do not pay a premium for a feature that cannot be demonstrated, supported or legally used. Written approval should distinguish confirmed functions, unavailable functions and work required after arrival.
Name the destination workshop, tool access and parts route.
Record the approval decision
Approve assistance systems only when the candidate’s market and trim establish expected equipment, physical sensors and surrounding repairs are inspected, diagnostics are saved before clearing, and required calibration has a reproducible record. Safe function checks must state conditions and limits. Hold feature value at zero or reject the vehicle when critical hardware, coding, calibration or destination support remains uncertain, especially after windscreen, bumper, steering or collision repair.
Retain the approval with the VIN file and reopen the review whenever the candidate, destination or commercial boundary changes.
Buyer approval checklist
Use these fields as a candidate-specific decision record. Assign each unresolved item before approving payment or shipment.
- VIN-specific feature list
- Sensor and glass condition
- Pre-clear diagnostic scan
- Calibration documentation
- Safe function checks
- Destination ADAS support
Primary references
Official Changan Thailand NEVO Q05 model page ↗Official Changan Thailand NEVO Q05 equipment news ↗Changan Q05 ADAS, Camera and Sensor Checks: buyer questions
Does the 2026 NEVO Q05 have the same ADAS everywhere?
Do not assume so. Equipment and software can vary by market, trim and production date.
Is no dashboard warning enough?
No. Confirm hardware, module configuration, stored faults, calibration and safe function checks.
When might calibration be needed?
Relevant glass, bumper, camera, radar, steering, suspension, alignment or collision repairs may trigger it.