Code
U0168
HYUNDAI
U — Network/User
Lost Communication With Vehicle Security Control Module
Views:
UK: 12
EN: 22
RU: 14
AI status
Completed
Completed
100%
Causes
- Blown fuse or lost power to the Vehicle Security Control Module (VSM)
- Poor or open ground to the VSM
- Damaged or corroded wiring/connectors to the VSM
- CAN/LIN bus physical fault (short to power/ground, open circuit, high resistance)
- VSM internal failure (hardware or firmware)
- Another module pulling the network bus off-line (bus-off condition)
Symptoms
- Security/immobilizer warning lamp illuminated or flashing
- Keyless entry, remote start, or alarm functions inoperative
- Vehicle may not crank or start (immobilizer active)
- Door lock/unlock or central locking inoperative
- Other network modules reporting communication errors
- Possible intermittent operation of security features
What to check
- Read and record freeze frame and all stored U-codes with a capable scan tool
- Verify battery voltage (should be 12.0–14.5 V with engine off/on as appropriate)
- Check fuses and fusible links related to VSM and body power distribution
- Visually inspect VSM connectors and harness for corrosion, damage or water intrusion
- Confirm good ground continuity between VSM ground and chassis/battery negative
- Use scan tool to confirm whether other modules on the same bus communicate
Signal parameters
- Battery supply to VSM: approximately 12.0–14.5 V
- Ground resistance:
- CAN bus idle voltages: CAN_H ≈ 2.5–3.5 V, CAN_L ≈ 1.5–2.5 V (pair differential ≈ 0 V idle, ~2 V dominant)
- Bus termination resistance: approx. 60 Ω measured between CAN_H and CAN_L with ignition on
- No continuous short to battery or ground on CAN_H or CAN_L (
- Module should respond to diagnostic request from scan tool (no response indicates comms fault)
Diagnostic algorithm
- Confirm the code and note whether it is current or history. Check for related U-codes (bus errors) and freeze frame data.
- Verify battery state of charge and charging system. Recharge or replace weak battery before in-depth testing.
- Inspect VSM power feed fuses and fusible links; replace any blown fuses and re-test.
- Visually inspect connectors and harness at the VSM for corrosion, bent pins, water intrusion or physical damage.
- Verify good ground(s) for the VSM: disconnect connector and measure continuity to battery negative.
- With ignition on, measure VSM supply voltage at the module connector; no supply indicates wiring/power issue upstream.
- Use a scan tool to poll other modules on the same CAN bus. If multiple modules are missing, focus on bus physical layer.
- Measure CAN_H and CAN_L voltages with respect to ground and with each other; check termination resistance (~60 Ω).
- Probe for shorts: disconnect suspected modules (after noting configuration) and check whether bus communication is restored.
- If physical layer tests good but VSM does not respond, try re-seating connector and clearing codes. If persistent, consider replacing or reprogramming the VSM per manufacturer procedures.
- After any repair or module replacement, perform required programming/initialization and verify all security/key functions and that codes do not return.
Likely causes
- Fuse for VSM or body electrical system blown
- Loose or corroded connector at VSM (power/ground/CAN)
- CAN_H/CAN_L shorted to power or ground or missing termination
- Battery low or disconnected causing modules to go to sleep
- VSM module failure or software corruption
Fault status
Status
Lost Communication With Vehicle Security Control Module (VSM) — no response from module on vehicle communication network.
Repair difficulty: Medium
Diagnostic time: 1.0 to 3.0 hours
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
