Gent Vigilon Fault Workflow for Service Engineers

Short answer: start with the event log, record the exact fault wording, identify the loop and device, then work methodically from the panel outward. The Vigilon gives you more diagnostic information than most panels if you know where to look.

Who This Is For

Fire alarm service engineers attending Gent Vigilon faults. This is a workflow support guide — it does not replace Gent's official Vigilon documentation, applicable standards, or competent engineering judgement on site.

What to Capture Before Touching Anything

When you arrive at a Vigilon fault call, the most valuable time you spend is at the panel before any reset or investigation work begins.

Record:

1. The exact fault wording on the panel display — The Vigilon uses specific fault descriptions. The exact text tells you the fault category and often the affected loop or device. Photograph the display or write it down word for word.

2. The loop number — Loop 1, Loop 2, and so on. On multi-loop or networked Vigilon installations, also note which panel is generating the fault.

3. The device address or zone — If the panel is showing a device-level fault, record the device address. If the fault is loop-wide (e.g., earth fault, open circuit), record the loop.

4. The time the fault first appeared — Available in the event log. This matters for intermittent faults and for the log book entry.

5. Any recent site activity — Has any other trade been on site? Has any work been done near the affected area? This context often points directly to the cause.

Do not reset the panel until you have recorded this information. Once reset, some fault data is harder to retrieve.

Using the Vigilon Event Log

The Gent Vigilon logs events with timestamps. This is one of its most useful diagnostic tools and is often underused.

Access the event log via the panel's menu. Review the history for:

• Repeated fault/restore patterns — A fault that has appeared and cleared multiple times points to an intermittent issue: loose connection, cable that contacts metalwork under temperature change, or a device with intermittent failure.
• The sequence of events before the current fault — Did an alarm precede the fault? Did another fault clear shortly before this one appeared? The pattern often reveals the mechanism.
• Time correlation — If the fault appears consistently at the same time of day, look for an environmental or operational cause (heating system starting, equipment switching on, changes in occupancy).

Retrieve and photograph or note the relevant event log entries before starting any physical investigation.

Fault Categories and Initial Approach

Earth Fault / Ground Fault

The Vigilon continuously monitors loop insulation and will report an earth fault when it detects a path from a loop conductor to earth.

Initial steps:

• Note which loop and, if available, which half of the loop (some Vigilon configurations can indicate the fault direction)
• Disconnect the loop at the panel — if the fault clears, the issue is in the field wiring or a device, not the panel
• Use a megohmmeter (insulation resistance tester) to check insulation resistance on the disconnected cable: conductor-to-earth on each conductor, and conductor-to-conductor

Walk the loop route looking for cable damage, moisture ingress points, areas near pipework, and junction boxes that may have been disturbed.

Open Circuit Fault

An open circuit means the loop continuity is broken. The Vigilon will typically indicate which section of the loop is affected.

Initial steps:

• Identify the last communicating device address before the break — the panel may show this directly or you can identify it by which devices are online vs offline
• Check the boundary devices: remove each from its base and inspect the base terminations
• Use a continuity tester or multimeter to check the cable run between the last online device and the first offline device
• Check every junction box in the affected run

Common causes: cable damage by other trades, a device removed from its base without a continuity plug, loose terminal block in a junction box, or a failed isolator module.

Device Communication Fault

A specific device is not communicating, but the loop is otherwise operational.

Initial steps:

• Go to the device's physical location
• Remove the device from its base and reseat it — poor contact is a common cause
• Check the base for contamination, moisture, or mechanical damage
• If the device remains offline after reseating, swap with a known-good device to determine whether the fault is the device or the wiring
• Check for duplicate addresses if the fault appeared after recent commissioning or device replacement work

Short Circuit Fault

The Vigilon uses isolator modules (EN 54-17 compliant) to automatically section a short circuit fault, limiting the number of devices taken offline.

Initial steps:

• Identify the isolated section from the panel display
• Locate the isolator modules at the boundaries of the isolated section
• Disconnect devices in the isolated section one by one until the short clears, to identify the faulty device or cable section
• Inspect device bases for cracked or contaminated bases, foreign objects, and cable damage

Site History and Repeat Faults

On a site you have attended before, check whether this fault has appeared previously. Prior fault records should be in the system log book and, if your company uses a fault management tool, in the digital record.

Repeat faults on the same loop or device indicate an underlying issue that wasn't fully resolved on the previous visit. Document this pattern and escalate if the root cause remains unresolved.

Documentation

Per BS 5839-1, all fault investigations and remedial work must be recorded in the system log book. Your entry should include:

• Date and time of attendance
• Fault type and panel/loop/device reference
• Diagnostic steps taken and results
• Cause identified
• Remedial action taken
• System status on departure

If you could not fully resolve the fault — awaiting parts, inaccessible area, further investigation required — document the outstanding items and notify the client clearly.

How Incognito Fire & Security Helps

Search the Gent Vigilon fault database by symptom or device type, use the AI assistant to work through diagnostic steps, and log the result directly to the site record.

Search Gent faults → | Open site history →

Disclaimer

This article is a workflow support resource. It does not replace Gent's official Vigilon technical documentation, BS 5839-1, EN 54, applicable standards, site assessment, or competent engineering judgement. Always verify fault causes by testing and with reference to manufacturer documentation before carrying out remedial work.

Next Step

Search Gent Vigilon faults → or start a free trial to access the fault database and AI assistant on site.