What
You can isolate the cause by testing one layer at a time, and the order matters because each test eliminates a suspect. Start with a timed baseline on a stationary vehicle parked where signal strength is strong. Command the immobilizer and record the exact time from dispatch to confirmation that the engine control unit responded. Write that number down, because every later test is compared against it. A clean baseline under ten seconds tells you the command path works at all, which already rules out a broken solution and points you toward conditions rather than components. If the immobilizer control analysis is going to be useful, it starts with this reference point, not with opinions from drivers or guesses about bad hardware.Next, test sleep mode, because it is the cause operators misread most often. Many GPS tracker installs cut power to the communication module when the ignition is off to protect the battery. Leave the vehicle off with the ignition killed, watch the tracker status in your fleet tracking platform, and send the immobilizer command again. If nothing arrives, the vehicle never heard you. That is not a failed immobilizer. It is a sleeping radio. You can confirm this by repeating the exact same command a moment after the ignition is switched on. If it lands instantly, sleep mode is your culprit, and the fix is a wake strategy, not new hardware.Now examine the CAN bus layer. Immobilizer control works by sending a message across the vehicle network, and many units sit on a separate CAN bus interface from the tracker itself. A message that leaves your telematics platform but produces no physical disable usually means the command reached the wrong address. Pull the arbitration IDs your system is broadcasting and compare them against the CAN database for that exact vehicle model. A Ford E-Transit and a Freightliner Cascadia do not share the same signals, and a firmware update can quietly remap priorities. The telltale sign here is a command marked as sent while the starter still turns freely. That symptom appears across every vehicle of one model and never on others, which separates it from anything network related.Then test handover behavior, which is where timing and motion interact. Take a vehicle through a known handover zone, a highway stretch, a tunnel mouth, or a dense urban block, and command the immobilizer while it is moving. Watch whether the action completes while rolling or only after the vehicle stops. Signal jitter in these conditions delays delivery, and under peak load in an industrial zone a command can take up to 45 seconds to land. If your failures cluster around movement, weak coverage, or busy hours, you are looking at command delivery, not at the immobilizer itself. Geofence alerts from the same trip will often lag in the same window, which is a useful cross check.Finally, run the decision tree. Fails only when ignition is off, suspect sleep mode. Fails only on specific vehicle models, suspect CAN bus mapping. Fails only in motion or poor coverage, suspect network handover. Fails at scale with rising timeouts across an aging fleet, suspect congestion and queueing rather than a single bad unit. Each branch carries a different remedy. Latency under ten seconds usually responds to tuning. Wrong signals on one model call for reconfiguration. Repeated dead zones in garages or rural areas may leave no software option at all. Before you replace anything, get a delivery receipt from the vehicle, because a telematics platform that cannot confirm the command arrived leaves you blind to which layer actually broke.