The most costly MDVR error is the one discovered when the footage is needed. A driver reports an incident. The transport manager checks the platform. The rear camera shows a black screen for the last two hours. Or the MDVR is showing offline and has been for three days. Or the footage exists but the timestamp is wrong by six hours, making it useless for the timeline the insurer needs.
MDVR errors are rarely catastrophic when found during routine maintenance. They become expensive when the discovery happens in the context of an insurance claim or a driver conduct review. This guide covers the most common MDVR faults, their likely causes, and what to do about them — so they are found and fixed before they matter.
A black screen on one or more camera channels is the most frequently reported MDVR issue. Before escalating to a hardware replacement, work through the likely causes in order:
Cable connection fault. The most common cause of a black screen on a specific channel is a loose or damaged aviation connector cable between the camera and the MDVR. Check the connector at both the camera end and the MDVR input. Aviation connectors should be fully seated and locked. Corrosion at the connector, particularly on vehicles that go through pressure washing, can cause intermittent signal loss. Inspect the cable run for damage from stone strike or chafing against metal bodywork.
Camera failure. If the cable and connector are undamaged, connect the camera to a known-working channel on the MDVR. If the black screen follows the camera to the new channel, the camera is faulty. If the channel works with a different camera, the MDVR input for that channel has the fault.
Power supply to the camera. Some MDVR systems supply camera power through the aviation connector cable. If the power wire within the cable is damaged or the fuse for that camera circuit has blown, the camera will not power on. Test power supply to the camera directly with a multimeter if no display image is present and the cable appears undamaged.
Infrared failure on night vision cameras. If a camera produces a colour image in daylight but a black screen in low light, the IR LEDs have failed. The camera sensor is functional but the illumination is not. IR LED replacement is typically a camera-level repair or replacement.
An MDVR that is powered and connected to cameras but not recording is a serious problem — there is no evidence being created, and the fleet operator may not know until a footage request reveals empty storage.
HDD or SD not detected. The storage device is not recognised by the MDVR. Check the HDD is correctly seated in its bay and the data/power connectors are fully engaged. For SD card slots, remove and re-insert the card. If the device is not detected after reseating, test with a known-good drive. If neither device is detected in the slot, the slot itself may be damaged.
Drive not formatted for MDVR. A new HDD or SD card may not be in the correct format for the MDVR. Most commercial MDVR systems require formatting through the MDVR’s own menu — not via a computer. Format the drive through the MDVR interface using the system settings. Do not use a computer to format an MDVR drive unless the manufacturer’s documentation specifies a particular format.
Drive full and not looping. If loop recording is disabled, the drive fills completely and recording stops. Confirm loop recording is enabled in the MDVR settings. If loop recording is enabled but the drive is full, the system should be overwriting the oldest non-protected footage — if it is not, this may indicate a firmware fault or a drive with excessive protected-file accumulation that needs to be manually cleared.
Drive health failure. HDDs have a finite operational life, and commercial vehicle environments accelerate wear through vibration and temperature cycling. An HDD that has begun to fail may still appear to record but produces corrupted or unplayable footage. If footage is consistently unplayable from a specific drive, replace the HDD. For fleets running 24/7, annual HDD replacement is good practice.
GPS data absent from footage is a significant gap for incident evidence. The likely causes:
GPS antenna signal blocked. The GPS antenna requires a clear view of the sky. If the antenna is mounted in a position with metal obstruction above it — beneath the cab roof, near the engine bay, or under a metal shelf — satellite acquisition will be poor or intermittent. Reposition the antenna to a location with unobstructed sky view, typically on the cab roof or windscreen area.
GPS module not initialised. Some MDVR GPS modules take 1–3 minutes to acquire satellite fix after power-on, particularly in areas with obstructed sky view. If GPS appears in footage after a short delay from vehicle start-up, this is normal. If GPS data never appears regardless of journey length, the GPS module may be faulty or the antenna connection may be broken.
Date and time synchronisation error. If the MDVR’s internal clock is not set correctly, GPS timestamps will appear offset from real time or may cause GPS data to appear invalid. Set the MDVR date and time manually, or confirm that GPS time synchronisation is enabled — most MDVR systems can set their clock automatically from the GPS signal once a fix is acquired.
A connected MDVR that has gone offline means the fleet manager has lost remote footage access and event notifications for that vehicle. This should be treated as a priority fault.
SIM card / data connectivity. Check the SIM card is correctly installed and active. On some MDVR systems, the SIM slot is user-accessible; on others, it requires the unit to be opened. Confirm the SIM plan is active and the data allowance has not been exhausted. Move the vehicle to an area with known good coverage and check whether the platform comes back online.
MDVR powered off or in sleep mode. Confirm the MDVR is powered on. Some systems enter a low-power mode when the vehicle ignition is off for extended periods. Check the ignition-triggered power schedule in the MDVR settings — if the system is set to power down after a short idle period, it may go offline regularly during breaks or overnight.
Firmware or platform configuration. If a firmware update was recently applied and the MDVR went offline shortly after, the update may have changed a network configuration setting. Review the APN settings for the SIM card and confirm they match the carrier requirements. Contact the MDVR supplier if the platform shows the unit as offline following a firmware update.
Footage with the wrong timestamp is a significant problem for incident claims, where the video timestamp needs to match the reported incident time. The causes are usually straightforward:
Time zone misconfiguration. If the MDVR was installed or reset with the wrong time zone, footage timestamps will be consistently offset by a fixed number of hours. Correct the time zone in the MDVR settings and confirm the footage timestamp matches a known reference time.
Battery-backed clock failure. MDVR units maintain their clock via a small internal battery when external power is removed. If this battery has failed, the clock resets on every power cycle. The symptom is footage showing a date/time of 2000-01-01 or similar default. The internal clock battery can be replaced — contact your MDVR supplier for guidance on your specific model.
GPS time sync not enabled. Most MDVR systems can synchronise their clock to GPS time, which self-corrects any drift. Confirm this setting is enabled in the MDVR configuration.
If a significant braking event or collision occurs and no G-sensor event clip appears in the platform’s event log, the G-sensor may be misconfigured or faulty.
First, confirm the sensitivity setting has not been inadvertently reduced to the lowest level. Check the G-sensor threshold in the MDVR settings and test with a controlled hard braking event to confirm the trigger fires. If triggering works in testing but failed during an actual incident, the incident g-force may have been below the threshold — consider adjusting sensitivity upward slightly.
If the G-sensor does not trigger in any test, the sensor may be faulty. This is a hardware fault requiring the MDVR unit to be serviced or replaced.
Most commonly a cable connection fault — check the aviation connector at the camera and MDVR ends. If the connector is secure, swap the camera to a working channel to determine whether the fault is in the camera or the MDVR channel input.
Check storage device: reseat the HDD or SD card, confirm the drive is formatted through the MDVR menu, and confirm loop recording is enabled. If recording still fails, test with a different known-good storage device.
Check and correct the time zone setting in the MDVR configuration. Enable GPS time synchronisation if available — the MDVR clock will self-correct to GPS time on next satellite fix. If the clock resets every time the vehicle is switched off, the internal clock battery may need replacement.
For HDDs: annual replacement is recommended for commercial vehicles in continuous operation. HDDs in vehicle environments experience accelerated wear from vibration and temperature cycling. If footage is becoming intermittently unplayable before the annual mark, replace sooner.
The MDVR is not connected to the cellular network. Check SIM card installation and active status, data allowance, and that the MDVR is powered on. Verify the SIM APN settings match carrier requirements. If a firmware update was recently applied, the update may have altered network configuration settings.
Yes. A brief weekly check of the platform’s vehicle status page — confirming all cameras show a live feed and all vehicles show online status — catches most faults before they matter. Many platforms support automated alerts for cameras going offline or recording stopping. Enable these alerts where available.
A printable checklist covering the six most common MDVR faults — black screens, storage errors, GPS failures, offline status, timestamp issues, and G-sensor problems — with step-by-step diagnostic actions for each.
Related guides: Downloading Evidence Footage for an Insurance Claim · UK MDVR Regulations Every Operator Should Know
4 August 2026
Monday to Friday:
8.30am-5.30pm
