What’s Wrong With Your Fleet GPS Tracker, Fleet Dash Camera or ELD?

1. The vehicle hasn’t been driven. Many devices only send a full report with the ignition on.
2. The device or harness is loose at the port.
3. No power at the port: dead battery, blown accessory fuse, or a battery kill switch.
4. No cell coverage or no view of the sky (metal building, garage, rural dead zone).
5. The device was deactivated on the account.

1. Look at the last report time and place in your fleet software.
2. Drive the vehicle in an open area with good cell signal.
3. Push the device firmly into the port and check the zip tie and harness joints.
4. Start the vehicle to rule out a dead battery, and check the cigarette lighter or accessory fuse, which often feeds the port.
5. Unplug any other accessory sharing the port, then power cycle the tracker.

Call us when the lights stay off after a power cycle, the port has no power, or the device is hardwired behind the dash.

A tracker or ELD plugged into a dead OBD2 port gets no power, so it shows offline. On most vehicles the port’s power comes through a fuse, and on many it shares that fuse with the cigarette lighter or accessory power outlet. The fuse chart in the owner’s manual or on the fuse box cover names the exact one for your vehicle.

1. Plug a phone charger into the cigarette lighter. If it doesn’t work either, a shared fuse has probably blown.
2. Find the OBD or accessory fuse on the fuse chart, check it and replace it with the same rating.
3. Look into the port with a flashlight for bent, pushed-back or corroded pins.
4. If a fuse keeps blowing, stop replacing it and leave the device unplugged.

Call us when the fuse is good and the port still has no power, the pins are damaged, or a fuse keeps blowing. That usually means a wiring fault behind the port. For wire colors on a specific vehicle, see our Vehicle Wiring Database.

A normal status light means the device has power and has reached its servers. If the vehicle still doesn’t appear, the problem is usually on the account side, not the wiring.

1. The device hasn’t been activated or assigned to a vehicle on the account yet.
2. The serial number was entered wrong.
3. The device was added as a new vehicle instead of to the existing one.

1. Compare the serial number on the device label with the one in your fleet software.
2. Check the device is active and assigned to the right vehicle.
3. Drive the vehicle for a few minutes after any change.

Call us when the account side checks out and the vehicle still doesn’t report, so the install can be checked.

1. The device was never pushed fully into the port.
2. No zip tie holding it in place.
3. Road vibration, or a driver’s knee knocking it.
4. A worn or loose port.

1. Push the device fully in and fasten it with a zip tie.
2. Look for unplugged or power loss alerts on that vehicle.

Call us when the port is worn or damaged, or the device should be moved behind the dash on a harness so it can’t be knocked loose.

Yes. Keying a high power radio can disrupt the link between an ELD and the truck’s computer, and drivers have reported a new CB knocking out their ELD’s GPS. Poorly routed radio and device wiring makes it worse.

1. Turn the radio off and see whether the problem stops.
2. Note whether it only happens while you are transmitting.

Call us when the device or radio wiring needs rerouting, better grounding, or more distance between the antenna and the device.

1. No clear view of the sky: garages, overpasses, tall buildings, metal roofs.
2. Something sitting on top of the device, or the device mounted under metal or next to a heater vent.
3. Weak cell signal, so points arrive late. Straight dotted lines on the map mean GPS was lost and the points were joined up.
4. A GPS jammer in the cab.
5. A failing GPS antenna or module.

1. Park outside with open sky and drive it.
2. Clear anything stacked on or around the device.
3. Check the GPS light. On many units it goes solid once it has a fix.
4. Look for GPS or antenna fault messages in your fleet software.

Call us when the GPS light never goes solid in open sky, the device needs moving to a spot with sky view, or the software shows an antenna fault.

1. Normal trip rules. On some platforms a trip ends when the engine stops, or when the vehicle sits still for a few minutes with the engine running, so a long stop splits one trip into two.
2. A driver change mid-route.
3. The device lost power for a moment from a loose plug.
4. Lost cell or GPS signal, so data arrives late or with gaps.

1. Look at what happened at the split. A long stop or a driver change is normal.
2. Look for power loss or unplugged events near the gap.
3. Reseat the device and the zip tie.

Call us when power loss or unplugged events keep showing on a vehicle nobody is touching. That points to a loose install or harness.

1. A GPS-based odometer will always differ a little from the dash.
2. The starting odometer was entered wrong, or never entered.
3. The vehicle doesn’t send an odometer or engine hours reading the device can read. This depends on year, make and model.
4. The device was moved from another vehicle and the vehicle record wasn’t updated.
5. Another device on the port is interfering.

1. Enter a current dash reading as an odometer and engine hours adjustment in your fleet software.
2. Check the VIN shown in the software matches the vehicle.
3. Unplug other accessories on the port, then retest.

Call us when the odometer has never read on a vehicle that should support it, or the harness doesn’t match the vehicle.

1. The wrong cable or harness for the vehicle.
2. Corroded, bent or pushed-back pins in the diagnostic port. On heavy trucks with a round 9-pin connector, a pin that doesn’t make good contact causes engine data to come and go.
3. A second device on the same data line, such as another tracker, a wheelchair lift or a scan tool.
4. The device has stopped asking for data after too many data errors.
5. The vehicle doesn’t send that data at all.

1. Unplug every extra accessory and power cycle the tracker.
2. Check your plan includes engine data. Some dash cam only plans don’t show it.
3. Take a clear photo of both ends of the cable and the port.

Call us when pins are damaged, the harness is wrong for the vehicle, or the truck needs a different connection point.

A healthy, correctly installed tracker goes into a low power sleep when the vehicle is off. When a truck is dead in the morning, the tracker is one suspect, not the only one.

1. An old battery, short trips or cold weather.
2. Other aftermarket devices drawing power.
3. A setting in the fleet software that keeps the device awake with the ignition off.
4. A device or harness that never goes to sleep.
5. A second tracker nobody knew about, sometimes left by a previous owner or dealer.

1. Have the battery tested and the terminals cleaned and tightened.
2. Look at the device’s voltage history and low voltage alerts in your fleet software.
3. Turn off any keep awake setting you don’t need.
4. Look for other devices on the port.

Call us when you need a parasitic draw test with a meter, a hidden tracker found, or a hardwired unit moved to the right circuit.

1. A driver alert rule is turned on in the fleet software, such as speeding, harsh braking or seatbelt.
2. Some devices beep when they first power up, or when they have no cell connection.
3. The vehicle’s own horn or alarm chirps when it is locked, because the device asked the engine computer for data with the ignition off. Some platforms have a setting that stops this.

1. Look at the driver feedback rules for that vehicle and turn off the ones you don’t want.
2. Note exactly when it beeps: driving, starting, or parked and locked.

Call us when the buzzer is wired in behind the dash, or the vehicle keeps chirping after the setting is changed.

Every brand uses its own colors, but most trackers have the same three jobs on their lights: power, cell connection and GPS. On a Geotab GO9, for example, red means power and ignition, green means it has reached the servers, and blue means GPS lock.

1. No lights at all: no power. Check the plug, the fuse and the battery.
2. Power light only: the device is on but has no cell connection or GPS. Drive it in the open.
3. A light blinking for hours: it is struggling to get a signal. Drive it, then power cycle.
4. Lights flashing during a firmware update: leave it plugged in until it finishes.

Call us when the lights don’t change after a drive and a power cycle in the open.

1. A two-wire install with no ignition wire, so the device guesses from voltage and movement.
2. A battery kill switch or other aftermarket switch.
3. An intermittent connection at the port.
4. A keep awake setting turned on.
5. A damaged device or harness.

1. See whether the vehicle shows engine RPM and speed in the software.
2. Turn off any keep awake setting.
3. Power cycle the device.

Call us when the install needs a proper ignition wire, a kill switch is interfering, or anything needs rewiring.

1. The new device was added as a new vehicle instead of swapped into the existing vehicle record.
2. The device was moved to another truck without updating the software.

1. Use the device swap or replace option on the existing vehicle record so its history stays together.
2. Check the VIN in the software matches the truck.
3. Enter the current odometer again.

Call us when devices need physically moving between vehicles, or a hardwired unit needs removing. Some platforms advise against moving a device yourself.

An unplugged or tamper alert means the device lost power. It doesn’t prove a driver pulled it. A shop unplugging it for service, or a loose install, sets the same alert. On many devices the alert only shows once the device is plugged back in.

1. Match the alert time to service records and who was driving.
2. Check the device is still zip-tied in place.
3. Set up a regular report of devices that stopped communicating.

Call us when you want the device moved out of the driver’s reach with a harness behind the dash.

A tracker, an ELD, a dash cam and a scan tool can all fight over the same data line. On heavy trucks, more than one device on the data link can cause errors, and a manufacturer service bulletin recommends only one telematics device on it.

1. Unplug everything except the tracker and retest.
2. Add devices back one at a time to find the one causing trouble.

Call us when the vehicle needs a proper Y-harness or a separate connection point for each device.

Some vehicles react to a device asking the engine computer for data, or to the wrong harness for that make and year. This can show up as a check engine light, a network or data link code, or odd warnings on the dash. Truck drivers have reported data link faults and false dash warnings that stopped once the tracker or ELD was unplugged.

1. Write down the warning and the code.
2. Turn the engine off, unplug the device, and see whether the light clears over a few drive cycles.
3. Don’t keep driving with a warning light, a stall or a loss of power.

Call us every time this happens. The fix is usually the correct harness or connection point for that vehicle.

1. The device isn’t held firmly, so road vibration looks like a hard event.
2. The device is still calibrating after an install or power cycle.
3. Rough or off-road routes.
4. Alert settings that are too sensitive.

1. Check the device is firmly zip-tied and not swinging.
2. Drive normally for a while so calibration can finish.
3. Review the sensitivity of the alert rules.

Call us when the device or harness needs securing or relocating.

Most platforms only count idling after the engine has run with the vehicle stopped for a few minutes, so short stops at red lights don’t count. Idle data is also weaker on two-wire installs and on vehicles that don’t send engine data.

1. Find your platform’s idle time rule in its settings.
2. Check the vehicle shows engine data at all.

Call us when the install needs an ignition wire added or the engine data connection fixed.

Fuel level and fuel used only show if the vehicle sends them, and not every engine computer does. Electric vehicle support is set model by model. This is usually a vehicle limit, not an install fault.

1. Check whether the vehicle reports fuel signals at all in your software.
2. Import fuel card transactions to fill the gap.

Call us when a wrong harness is blocking engine data on a vehicle that should report it.

Technicians often unplug devices to use the diagnostic port, and dealers chasing a battery drain or a warning light are sometimes told to remove aftermarket devices.

1. Check the device is plugged back in and zip-tied.
2. Ask the shop whether they removed it.
3. Check the fuses if the shop did electrical work, then power cycle.

Call us when the device is missing, the harness was cut, or it was put back on the wrong connector.

Data diagnostics are warnings, not malfunctions. Most clear on their own. Follow the carrier’s and the ELD maker’s instructions.

1. 1 Power: the ELD wasn’t working within a minute of engine start, or lost power while running. Check the cable.
2. 2 Engine sync: engine data arrived late. Same checks as code E.
3. 3 Missing data: usually a missing location. The driver enters it when asked.
4. 4 Data transfer: the transfer test failed. Restore the connection.
5. 5 Unidentified driving: more than 30 minutes of unassigned driving in 24 hours. Assign or explain the driving.
6. 6 Other: set by the ELD maker.

1. Power saving mode on the phone or tablet.
2. An old Bluetooth pairing.
3. The truck is already connected to another driver’s phone.
4. An outdated app.
5. The phone is busy with calls or music over Bluetooth.
6. The gateway has no power.

1. Turn off power saving.
2. Leave the vehicle in the app and log out.
3. Forget the device in Bluetooth settings, turn Bluetooth off and restart the phone.
4. Unplug the gateway until its lights go out, then plug it back in with the engine running.
5. Update the app, log in and pair again.
6. Try a different phone, then a different gateway.

Call us when the gateway lights show no power or no engine data, or it keeps dropping and needs a better location or a wired connection.

1. The driver wasn’t logged in or paired.
2. Mechanics, tow drivers or yard staff moved the truck.
3. Bluetooth dropped.

1. Review unidentified driving every day.
2. Assign each event to the right driver, or add a note explaining why it can’t be assigned.
3. Give shop and yard staff a way to log in, or have them note the unit, date and time.

The carrier must review these records and keep them at least 6 months (49 CFR 395.32).

Call us when the cause is a gateway that keeps disconnecting.

The log must show the vehicle actually driven, every edit needs a note, and recorded driving time can’t be shortened or turned into off duty time.

1. The driver leaves the wrong vehicle in the app and selects the right one.
2. The fleet manager reassigns wrongly claimed driving with a note, using the tools in your ELD software.

1. No cell or Wi-Fi coverage.
2. An outdated app or a login problem.
3. An outage at the ELD provider.

1. Restore the connection, update the app, and log out and back in.
2. If the ELD stops recording, follow the malfunction rules above and switch to paper.

Call us when the problem is the truck’s data connection rather than the app.

The ELD must switch to driving once the truck passes 5 mph, and for model year 2000 and newer trucks the speed, miles and engine hours must come from the engine computer, not GPS.

1. Read the gateway lights for engine data.
2. Reseat the cable and pair the app again.
3. Have the shop check for speed sensor fault codes.

Call us when there is still no engine data after reseating, or the cable is wrong for the truck.

When the dashboard and the engine computer disagree, the engine computer reading is the one that counts, and odometer readings can’t be typed in by hand.

1. Compare the engine computer reading with the dashboard.
2. If the engine was replaced, have the dealer sync the engine computer.

Call us when readings are missing altogether, which points to the cable or harness.

The driver follows the data transfer instruction sheet in the truck. If the transfer fails, the officer can look at the logs on the screen or a printout, so drivers need to know how to show them, including taking the device off its mount if needed.

1. Practice a transfer before you need one.
2. Keep the instruction sheet in the cab.

Call us when the mount won’t let the screen be shown outside the cab.

When FMCSA removes an ELD, carriers stop using it, go to paper logs, and must switch to a registered ELD by the deadline in FMCSA’s notice, which has been 60 days. After that, drivers using it can be treated as having no logs and placed out of service. Check the registered and revoked lists at eld.fmcsa.dot.gov.

Call us for a fleet-wide swap to a registered ELD. The clock is short, so book early.

No. Vehicles built before model year 2000, as shown in the VIN, are exempt, and so are trucks with an engine older than model year 2000. Keep the engine records at your main office. Those trucks still need paper logs unless another exception applies.

The cable was often knocked loose or unplugged to use the diagnostic port, pins were pushed back, a splitter was added, or the battery was disconnected.

1. Check both ends of the cable and the pins.
2. Remove any splitter and test direct.
3. Unplug for five minutes and plug back in.

Call us when the port or harness is damaged, or the shop needs a permanent splitter fitted.

A portable ELD must be mounted in a fixed position, visible from the normal driving position (49 CFR 395.22). A dead tablet means the driver can’t keep logs current, so a solid mount with steady charging matters.

Call us for fixed mounts, hardwired charging and moving a mount so it can be seen.