What
If you plot your diagnostic stream on a timeline, the gaps usually do not fall randomly across the day. They cluster in places you can see with your own eyes when you ride along: hard pulls from a stop, merging onto a highway, climbing a long grade with a loaded trailer. The pattern repeats across different drivers and different routes. That is the moment most fleet managers start pointing at the engine, and that is exactly where careful work begins, because the same pattern can come from three very different layers, and only one of them is actually about the engine. Start by holding on to what engine diagnostics really means in a fleet tracking context. It is a continuous stream from the vehicle's ECU covering fault codes, RPM, coolant temperature, fuel usage, and idle time. Nothing in that stream is optional decoration. It is the raw material behind service visibility, maintenance planning, and often compliance records too. When part of that stream thins out during high engine load, you lose the exact window where interesting things tend to happen. The first candidate layer is the ECU itself. Some control units rate-limit how often they broadcast certain data when the engine is busy. Under load, the ECU is already juggling fuel delivery, emissions control, and torque management. Broadcasting a rich block of ECU telemetry every second is not its first priority, and some units simply throttle the messages they emit until conditions settle. Software tuning cannot fix a hardware transmission cap, so if this is your cause, no amount of configuration will close the gap. The second layer is the telematics gateway. At scale, with hundreds of vehicles feeding thousands of points per second, many gateways quietly make a choice: keep the location pings flowing and let diagnostic messages wait. That is data prioritization, and it is usually built into the device logic rather than something you enabled on purpose. The result looks like a vanished engine while the map keeps moving. The third layer is the network path. Signal jitter in tunnels or around heavy interference makes the unit buffer data, which then arrives as a burst instead of a steady flow. Under high load, a burst can also be the surge of fault codes themselves, and if the buffer fills, output can freeze until it clears. To sort this out in the field, work in order. Overlay your gap timeline against engine load, then ask a simple question: did location keep reporting during the same window? If the map track is unbroken while diagnostics vanish, the vehicle was clearly transmitting, which points away from the engine and away from a dead zone. Next, check configuration. Polling the engine computer every 10 to 30 seconds is a reasonable balance during active driving. Pull the buffer and sampling settings back if they are aggressive, and watch whether the gaps narrow. If they survive that tuning and still correlate only with load, the constraint sits in the broadcast behavior of the ECU or the handling capacity of the unit. Ruling out the engine takes one more step, and it matters because treating a data delay as a mechanical fault leads to unnecessary downtime and replacement of perfectly good sensors. Some fault codes are genuinely load-related. They can appear during a pull and clear on their own before the next poll cycle, which is normal behavior, not lost data. Compare your observed fault history against maintenance records and driver reports. If there is no matching symptom on the road, no drivability complaint, no repeat visit to the shop, the engine is likely fine and the diagnostic latency is a data problem. Put together, the decision is fairly clean. Gaps that shrink after polling and buffer changes, or that follow terrain and interference, are configuration and network issues you can address in place. Gaps that persist through tuning and track engine load almost exactly are a hardware ceiling. At that point the fix is not maintenance software, it is the telematics unit itself, and knowing that difference keeps your shop from chasing a fault that was never mechanical.