This article provides procedures for resolving new vehicle VIN lookup failures and synchronizing vehicle shipment information with the server. These apply to all vehicle models.
VIN Lookup Failure Symptoms
The new vehicle VIN cannot be looked up, and the "VIN information does not exist on server (502)" error is displayed.
[Auto VIN] fails on vehicles with no VIN recorded in the engine ECU (Code 1003).
VIN Lookup Resolution Procedures
-
Check the server synchronization cycle for new vehicle shipment information. Information on shipped new vehicles is synchronized with the server in a daily batch from 10:00 ~ 12:00(KST). If the lookup fails immediately after shipment or receipt on the same day, try the lookup again after the synchronization time.
For new vehicle models, specification information may not have been transmitted yet.
-
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 with no 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 pre-production test vehicles (Pre-Product) and locally assembled completely knocked down (CKD) vehicles are excluded. 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.
Vehicles produced at CKD plants cannot be looked up because production information is unavailable (not supported under policy).
For CKD/DKD details by region, refer to the specialized document.
Comments
0 comments
Please sign in to leave a comment.