Intermittent faults are some of the hardest faults to diagnose.

The system fails on Friday night, works on Saturday morning, fails again during a power event, then behaves perfectly when the technician arrives.

That does not mean the client imagined the fault.

It means the fault needs a timeline.

The time of the fault matters

Date and time can reveal patterns.

If a CCTV recorder loses cameras every evening, heat, PoE load, lighting circuits or scheduled network activity may be relevant.

If an AV receiver shuts down only during long movie sessions, ventilation or speaker load may be involved.

If Wi-Fi drops after load shedding, restart order and UPS support matter.

If a streaming service fails only at peak times, internet performance may be part of the story.

The exact time gives the support team a starting point.

“It happens sometimes” is difficult to act on

“Sometimes” is honest, but it is not enough.

Support becomes more useful when the report includes:

  • when it happened,
  • which room was affected,
  • what source or app was being used,
  • whether other rooms still worked,
  • whether there was load shedding,
  • whether the rack felt hot,
  • whether anything had just been changed,
  • and whether the fault cleared by itself or after a restart.

Those details turn a vague pattern into a technical clue.

Logs can be checked against the client’s notes

Many modern systems keep logs.

Network controllers, CCTV recorders, routers, managed switches, UPS equipment and some automation systems may record events.

But logs are only useful if support knows where to look.

If the client can say, “The camera dropped at about 21:10 on Thursday,” the technician can check logs around that time.

Without that note, the fault may be buried in days of normal activity.

Heat faults need usage history

Some AV equipment works when cold and fails when hot.

That kind of fault often looks random.

It may only appear when the cabinet doors are closed, when the amplifier is playing loudly, when the projector has been running for a while, or when several source devices are active together.

Recording how long the system had been in use before the fault appeared is useful.

It separates a start-up fault from a heat or load problem.

Power events need context

In South Africa, power quality is part of almost every serious support conversation.

Load shedding, inverter changeover, generator start-up, brownouts and voltage fluctuations can all expose weaknesses.

If a fault appears after a power event, say so.

If it appears only when the house moves from grid to backup, that matters.

If it appears after power returns, restart order may matter.

A simple note is enough

The client does not need to write a technical report.

A useful note can be as simple as:

“Friday 19:40, cinema Apple TV picture dropped twice during Netflix. Sound stayed on. No load shedding. Cabinet door was closed. Worked again after TV input changed.”

That is far more useful than:

“Cinema faulty again.”

DG Technologies values those details because they help solve the real problem instead of chasing the last symptom.

Intermittent faults need patience.

They also need evidence.