This article provides guidance on the resolution procedure when a new vehicle VIN cannot be looked up and on server synchronisation of vehicle shipment information. This applies to all vehicle models.
VIN Lookup Failure Symptoms
The new vehicle VIN cannot be looked up, and the error "VIN information does not exist on server (502)" is displayed.
[Auto VIN] fails on vehicles without a VIN recorded in the engine ECU (Code 1003).
VIN Lookup Resolution Procedure
-
Check the server synchronisation schedule for new vehicle shipment information. Information on shipped new vehicles is synchronised with the server in a daily batch at 10:00 ~ 12:00(KST). If lookup is unavailable immediately after shipment or receipt on the same day, look it up again after the synchronisation time.
For new vehicle models, specification information may not yet have been transmitted.
-
Check the online connection when entering the VIN manually.
Manual VIN entry performs a real-time lookup, so Wi-Fi must be connected.
-
Check for vehicles without a VIN recorded in the engine ECU (Code 1003). If [Auto VIN] fails on vehicles such as those with a replaced ECU, access the engine controller using a general-purpose diagnostic tool (GDS Smart) and first check whether [VIN Write] has been performed.
Unsupported Vehicles
Non-mass-production advance test vehicles (Pre-Product) and locally assembled completely knocked down (CKD) vehicles are excluded. Advance development vehicles and locally assembled CKD vehicles without official mass-production shipment information from headquarters are not supported by the global PDI system.
Vehicles produced at CKD factories cannot be looked up because no production information is available (not supported under policy).
For CKD/DKD details by region, refer to the dedicated document.
Comments
0 comments
Please sign in to leave a comment.