Hochiki FireNET Troubleshooting Guide

Overview

This guide covers the most common Hochiki FireNET gateway failures Chipkin is likely to see: panel-family mismatch, incomplete loop and address schedules, multi-node template gaps, and projects that rely on example files without a verified point list. Use it with the Hochiki FireNET when exposing fire-panel data into BACnet or another supervisory environment.

Diagnostic Flow

1. Confirm the exact panel family and expected driver alignment.
2. Confirm the loop and address schedule exists.
3. Confirm the point labels and event expectations.
4. Validate one known-good fire-panel point.
5. Only then review downstream object mapping.

Symptoms & Solutions

Symptom	Likely Cause	Action	Related Page
The example config looks close, but nothing lines up in the field	The installed panel does not match the assumed driver behavior	Reconfirm the panel family before changing the map	Hochiki FireNET
The gateway is online but there are no meaningful points	The loop and address schedule was never collected	Stop and collect the real panel schedule	Hochiki FireNET
One cabinet or node behaves correctly but the rest do not	A single-panel template was used on a larger multi-node system	Rebuild from the actual node and loop topology instead of copying one template	FieldServer
The team says the panel is working, but BACnet objects are still wrong	Target-side supervisory mapping now needs review	Recheck BACnet exposure after proving source alignment	BACnet
The project keeps switching terminology between panel families	Protocol-family ambiguity is blocking correct configuration	Normalize the panel description before deeper troubleshooting	Notifier
One sample point works and the rest do not	The example file was used without a full point schedule	Rebuild the map from the loop and address schedule	QuickServer

The Panel Family Is Wrong Or Unclear

This is the first thing to resolve.

Confirm The Installed System Identity

Confirm:

• Panel family
• Output behavior expected by the gateway
• Whether field terminology matches the driver you are using

[!WARNING] If the panel family is wrong, every later troubleshooting step is likely to mislead the team.

The Loop Schedule Is Missing

Fire-panel point work depends on engineering artifacts, not assumptions.

Rebuild The Point Model

Look again at:

• Loop numbers
• Device addresses
• Labels
• Event and alarm expectations

Example Files Were Treated Like The Real Project

Reference files help, but they do not define the field installation.

Recheck The Actual Scope

Confirm:

• Which example-file sections truly match the installed panel
• Which points are site-specific
• Whether the downstream object model reflects the real point schedule

The Multi-Node Topology Was Under-Scoped

Some Hochiki jobs work at one cabinet or node and fail when the build expands.

Rebuild The Real Node Layout

Confirm:

• Number of cabinets or nodes
• Loops per node
• Whether the template was built for a smaller topology
• Whether the current firmware or template supports the required scale

[!WARNING] If a multi-cabinet FireNET job was started from a single-panel template, do not assume the remaining nodes will align automatically.

Quick Diagnostic Decision Tree

• Start by confirming the installed panel family and driver alignment.
  • If that is unclear: resolve it first.
  • If it is clear: continue to the point schedule.
• Check whether the loop and address schedule is available.
  • If not: collect it before continuing.
  • If yes: continue to source-point validation.
• Check whether one known-good point validates correctly.
  • If not: recheck panel-family alignment.
  • If yes: continue to mapping scope.
• Check whether the remaining points still fail while the known-good point works.
  • If yes: rebuild the map from the loop schedule rather than the example file.
  • If no: continue to target-side validation.
• Check whether the failure appears only on higher cabinets or nodes.
  • If yes: treat the topology or template as the main issue.
  • If no: continue to target-side validation.
• Check whether downstream BACnet objects are still wrong after source validation.
  • If yes: recheck target mapping.
  • If no: the main fault was on the FireNET side.

Related Pages

• Hochiki FireNET
• BACnet
• Notifier
• Simplex 4100
• QuickServer