New Vehicle VIN Lookup Failure and Shipment Information Synchronisation

If a new vehicle VIN lookup fails, check whether it is a mass-production vehicle, server synchronisation, the Wi-Fi connection, and whether the VIN is recorded in the engine ECU.

Symptoms

• The new vehicle VIN cannot be retrieved immediately after shipment or receipt on the same day.
• Code 502: VIN information does not exist on server (502)
• Auto VIN fails on vehicles with no VIN recorded in the engine ECU (Code 1003).

Causes

• Information on shipped new vehicles is synchronised with the server.
• Code 502 occurs before new vehicle shipment information is synchronised with the server, or for CKD/pre-production vehicles.
• Manual VIN entry performs a real-time lookup, so Wi-Fi must be connected.
• Auto VIN may fail because the VIN is not recorded in the engine ECU, for example on vehicles with a replaced ECU.
• Non-mass-production pre-production test vehicles (Pre-Product) and locally assembled completely knocked-down (CKD) vehicles: pre-production development vehicles and locally assembled CKD vehicles without official mass-production shipment information from headquarters are not supported by the global PDI system.

Resolution

• If the lookup fails immediately after shipment or receipt on the same day, repeat the lookup after the server synchronisation time.
• For Code 502, check whether it is a mass-production vehicle and repeat the lookup after server synchronisation.
• Wi-Fi must be connected when entering the VIN manually.
• Vehicles with no VIN recorded in the engine ECU (Code 1003): if Auto VIN fails on vehicles with a replaced ECU or similar vehicles, access the engine controller using the diagnostic tool (KDS 2.0) and first check whether VIN Write has been performed.
• For CKD/DKD details, refer to the related document link.

Related articles

• CKD·DKD VIN Lookup and Inspection