1 Load Kentec Syncro file (.syn)
Site summary
Cause & effect actions
Full cause & effect decoded from the Syncro config — click an action to see its causes and effects. Use the report as the re-programming schedule for the new panel (C&E still has to be programmed manually and verified during commissioning).
Device schedule
| Panel | Loop | Addr | Type (Kentec) | Zone | Action | Location text | Flags |
|---|
Device type mapping protocol: Hochiki (default) verify before generating
Kentec type codes found in this file, with the Advanced DeviceID each will be written as. Defaults are unverified guesses — set them from a known-good Advanced site file (open one in the Advanced PC software to read off the DeviceIDs). Saved on this device for next time.
| Kentec code | Interpreted as | Qty | Example label | Advanced DeviceID | I/O |
|---|
2 Generate Advanced site file (.skf) experimental
In the Advanced PC software, create the new site with the correct panel types and node addresses, save it, and load that file here as the donor. The converter injects the device schedule (loops, addresses, zones, location text) into it — panel settings, network config and everything else stay exactly as the donor was saved.
Panel mapping
| Syncro panel | Devices | → Advanced node | First loop number |
|---|
3 Generate Advanced Gen 1 file (.NCF) highly experimental
For Gen 1 (MxPro 4-era) panels. Workflow: install the new panel, auto-learn the loops in the Gen 1 PC software (this creates every device record with the correct type and learned serial), save the .NCF, and load it here as the donor. The converter writes the Syncro location text (23-char Gen 1 limit) and optionally zone numbers onto matching loop/address slots. It never creates device records — devices missing from the donor are listed in the report.
Panel mapping
| Syncro panel | Devices | → Donor panel (.pcf) |
|---|
Compare two configuration files
Load two files of the same type (.syn, .NCF or .skf) — e.g. the config before and after a change — to see exactly what differs: devices added/removed, label/zone/type changes, panel settings and C&E modifications. Everything stays on this device.
Differences
Device-level changes
| Device | Detail |
|---|
🔋 Battery impact
Indicative standby battery requirement for each file, with the change between them — currents are estimated by device category. Refine in the Battery tab before selecting batteries.
Interrogate a configuration file
Open any .syn, .NCF or .skf for a granular breakdown — by device, zone, device type, panel and loop — with colour-coded types, branded PDF export (choose the sections, preview first) and colour-coded Excel sized for A4.
1 Load source configuration (.syn)
Drop the existing Kentec Syncro file. Its panels, devices, zones and cause & effect are read in so you can edit the site details and generate a new file.
2 Site & panel details editable
Pulled from the source file — edit anything before generating. Each panel can be renamed, set to Apollo or Hochiki, and given its first loop number.
| Source panel | Devices | Output panel name ? | Protocol ? | First loop ? | Include ? |
|---|
2b Device type mapping ? check interfaces
Every device type in the source is listed here so nothing is missed. Correct any mapping before generating — especially interfaces, sounders and relays.
| Kentec code | Interpreted as | Qty | Example |
|---|
3 Output file
What this app does
It reads, explains, compares and rebuilds fire-alarm panel configuration files — all in your browser. Nothing you open is uploaded; the files stay on your device. Your settings and last work sync privately to your account.
Two panel families: Kentec Syncro (older panels being replaced) and Advanced (the new panels, in two generations). The app helps you move a site over, document it, and produce a station FastTrack.
Which tab do I use?
The tabs
The three file types, in plain terms
All three are really ZIP archives — a folder of smaller files zipped up — which is how the app opens them. What's inside differs:
- Inside: fixed-width binary tables (klNode, klLoop, klDevice, klSubDev, klAction…).
- Device types & cause/effect are decoded and verified against a panel printout.
- Zone names: Kentec stores only zone numbers — no names — so on a FastTrack you type the zone descriptions in once.
- Deleted devices/nodes are never erased, only flagged — the app filters those "ghosts" out.
- Inside: a binary .pcf per panel + a SITE index.
- Zone names live in the SITE table and are read automatically.
- Device types are decoded from the type byte (best-effort, confidence-rated).
- Can't be built from scratch — each device holds a serial the panel learns — so Gen 1 needs an auto-learned donor.
- Inside: ~40 plain-text JSON tables — the friendliest format.
- Zone names come from tblZone; device types from tblDevice (per loop protocol: Apollo or Hochiki).
- Cause & effect is stored as output groups.
- The app can build these most completely (from scratch or a donor).
How a conversion works
Building a FastTrack (for a fire event)
A FastTrack lets station staff find a device fast by its SID (location code, e.g. 1/131).
Your account, branding & theme
You sign in with your own email. Admins create accounts and can assign each user a branding profile (logo + colours), which is applied automatically at sign-in. Everyone's settings and last-opened files sync privately to their account, so you pick up where you left off on any device.
In Settings you can recolour the whole app — separate light and dark palettes, every colour editable — and control the PDF report look (page size, margins, accent colour, paper theme, and a banner-style footer).
A word on safety
FastTrack Builder
Build a station FastTrack from any config file — a simple device-finder for staff during a fire event. Devices by location (SID order), devices by loop, and a zone list. Export as a themed PDF or colour-coded Excel. Works for .syn, .NCF and .skf.
Document details
Report contents choose what to include
Zone descriptions editable ?
| Zone | Description | Devices |
|---|
Preview — devices by location
Battery / standby calculator ?
Kentec Syncro
| Loop device | Qty | Q mA | A mA |
|---|
Branding & appearance
Saved on this device and applied to the app, the PWA icon, and all PDF / printed reports.
Theme & colours ?
PDF report layout ?
Applies to every PDF the app exports. Reports use Helvetica and your accent colour.