MITSUOKA / ASPARK Viewt · Used-vehicle, service and variant verification dossier

Correct technical identity

Period

1993–

Platform / generation

Nissan March/Note taban

Powertrain / energy / driveline

Retro sedan/hatch • Donör motor/CVT

Research focus

verify platform/generation, powertrain/energy/driveline and market-specific application identity against manufacturer/source records before applying parts, service procedures or chronic-fault claims.

Step-by-step checks

1. Match registration/VIN, production label and market identity to the model name; the model name alone is not a technical identity.
2. Observe cold start, full warm-up and road load separately; a pre-warmed vehicle can hide important symptoms.
3. Run a full-module scan and interpret cleared/new codes with readiness, mileage and freeze-frame context.
4. Combine tires, brakes, suspension, fluid leaks, cooling, charging system and driveline behaviour in one budget/risk table.
5. Check recalls/service campaigns and part supersessions by VIN/market; do not automatically generalize another market result.

How to verify the result

Do not make a parts decision from one DTC, sensor value or symptom. Reproduce the fault under the same temperature/load conditions and verify commanded-versus-actual data, electrical measurement and physical result together. Exact OEM limits should only be used when matched to the correct variant service source.

Main variant dossier → · DTC Academy → · Service guide →