Was this article helpful?
Aftermarket accessories: why the car started misbehaving after the dash cam went in
Dash cams, alarms, seat heaters, and audio are the most common cause of electrical faults that then get hunted for weeks inside factory systems. How they cause damage and how to avoid it.
The scenario repeats to the point of tedium: a dash cam or alarm goes in, two weeks later the car starts behaving oddly, and the next month is spent hunting a fault inside the factory systems.
Aftermarket equipment is one of the most common causes of electrical problems on modern cars, and the frustrating part is that nearly all of them are avoidable.
Three ways to cause damage
Practically every problem reduces to three mechanisms.
1. Parasitic drain
The most common. The device is wired to permanent live and does not sleep with the engine off.
The result: a flat battery after a few days parked. Then a voltage sag, a cascade of codes across systems, and a car that “broke everywhere at once”.
Normal for a sleeping car is under 100 mA. A dash cam in parking mode adds 20–50 mA, an alarm 10–30, an amplifier in standby can add more. Together they easily cross the line.
The search procedure is in its own guide.
2. Splicing into factory wiring
Twisted joints, insulation-piercing taps, cutting into the instrument cluster supply or the ignition line.
The result: a weakened contact, corrosion, raised resistance. Then intermittent codes that change between sessions and drive diagnostics mad.
That is the same picture as after a bad engine bay wash, and the mechanics are identical — see the washing article.
3. Connecting to the data bus
The most treacherous route. Alarms, trackers, and telematics devices frequently tap into CAN to read door status, ignition, and speed.
The result: if the device misbehaves on the bus — bad timing, noise, no sleep mode — modules start losing each other. U-series codes that look like a broken harness.
Mechanics in the U0100 guide; bus basics in CAN fundamentals.
How to recognise aftermarket equipment as the cause
A few signs that nearly always point here.
Timing. Problems started after installation. Not immediately — usually a week or two later, once the contact finally loosened. Which is why the link goes unnoticed.
A code cascade with a shared timestamp. Ten codes across systems is one cause, not ten failures; mechanics in ghost and false codes.
Codes return irregularly after clearing. A stable fault gives a stable code. A bad splice gives an intermittent one.
The battery goes flat in 3–5 days parked, with a healthy alternator.
The problem disappears when the device is disconnected. The most reliable test available, and it is free.
A thirty-minute check
- Read all codes and check timestamps. A cascade means power or the bus.
- Measure voltage: 12.4–12.7 V overnight, 13.8–14.4 V running.
- Disconnect everything aftermarket — dash cam, alarm, tracker, the insurer’s device in the OBD port.
- Clear codes and drive for three days, then read again.
- Nothing returned — case closed, it was the equipment.
- Something returned — hunt the factory fault, now without the extra noise in the data.
Step 3 closes roughly half of all cases and costs nothing.
How to install properly
Power from ignition-switched supply, not permanent live — for anything that should not run while parked.
If permanent live is genuinely needed — through a dedicated relay and its own fuse, not by splicing into somebody else’s circuit.
No twisted joints or piercing taps. Only proper connections with insulation rated for vibration.
A separate fuse per device. That is both safety and diagnostic convenience: suspicion is cleared by pulling one fuse.
Ground to a factory point, not a random bolt. Half of all “inexplicable” problems are a bad ground.
Bus connection only where there is no alternative, and only with equipment designed for your make.
Separately: a device in the diagnostic port
This category includes insurer telematics units and trackers that live permanently in the OBD port.
Two problems:
- Some of them never sleep — parasitic drain and all that follows.
- The port is occupied. Connecting a diagnostic adapter means removing the device.
One rule closes both: plug the diagnostic adapter in for the session and unplug it after. More on that in the telematics article and warranty and scanners.
What this means when buying a car
Aftermarket equipment in somebody else’s car is a black box: you have no idea how it was fitted.
What to look at:
- Code cascades in memory.
- Voltage and signs of sagging.
- A look under the dashboard — twisted joints, tape, wires disappearing somewhere unknown.
- A device in the OBD port — ask for it to be removed.
- Traces of a removed alarm — cut wires are more dangerous than a fitted system.
The general protocol is in the used car inspection guide.
In short
- Three damage mechanisms: parasitic drain, spliced wiring, misbehaviour on the bus.
- Problems appear a week or two after installation, so the link goes unnoticed.
- A cascade sharing a timestamp is one cause, not ten failures.
- Disconnecting everything aftermarket for three days is a free test that closes half the cases.
- Install through a dedicated relay and fuse, and ground to a factory point.
Download the app — codes across every system, timestamps, and voltage are read with an ELM327 adapter over Bluetooth SPP on Android.
Comments …
Loading…