Gent
MANUFACTURER KNOWLEDGEBASE
Gent Engineer Guide
Vigilon / Vigilon Plus / Vigilon Compact / Nano: practical field notes for testing, disablements, logic and restoration. Menu wording can vary by firmware and site configuration.
Before changing a live system: agree the test/disablement with the responsible person, identify any ARC/fire-routing connection and plant interfaces, decide what must remain operational, record every temporary change, and restore/verify everything before leaving.
GENT
Vigilon / Vigilon Plus / Vigilon Compact / Nano
Gent systems use panel-specific terms such as zones, devices, sectors, groups and command builds. Site configuration is especially important because sectors/groups can control major output functions.
Protocol / ecosystemGent proprietary addressable ecosystem
One-man / walk test
- Use the authorised Test function applicable to the installed Vigilon/Nano family.
- Choose the smallest suitable zone/device test scope and understand whether sectors/outputs are suppressed.
- Operate devices and verify panel text, loop/device identity and expected output behaviour.
- Exit test and confirm no TEST or DISABLE state remains.
Disable / enable
- Typical Vigilon workflow: MENU ON/OFF β Control β authorised user code β choose Disable or Enable.
- Select the object type required (for example Zone or Device), enter the site-specific number/loop and confirm.
- For output-related isolation, understand sectors and interface-line assignment before disabling; one sector can affect multiple outputs.
- After restoration, verify the Disablement indicator clears and review active events.
Cause & effect / groups
- Gent cause/effect may use sectors, groups and command builds.
- Do not treat a sector as just a βsounder groupβ; it can contain interface outputs with plant implications.
- Retain the site-specific configuration documentation and use trained Gent engineering procedures for programming changes.
Engineer notes
- Some Vigilon documentation notes that disabling a zone does not necessarily disable MCP operation; verify the installed family and configuration.
- Network Nodes can have different operator capabilities from full control panels.
- Gent commissioning should prove every cause/effect path against the approved fire plan.
Return to service:Exit test modeClear temporary disablementsRestore sounders / outputsRestore fire routing / ARCRestore delays / time controlsProve a normal event pathCheck panel = normalRecord work
PRIMARY REFERENCES
Manuals and manufacturer resources
External links are references only and require internet access. The knowledgebase itself remains usable offline.