What it can do — Schrack Integral ISP-IP¶

Feature by feature, as assessed on 2026-09-21. Read the limitation column before you promise a customer something the hardware cannot do.

Connection, health and audit¶

Feature	Supported	Limitation
Connection & session	Yes	—
Liveness / keepalive	Yes	—
Time synchronization	Yes	—
Offline audit recovery	No — the hardware cannot do it	Events that happen while the link is down are not replayed afterwards; Protequ only shows the current states once the panel is connected again.
Health & supervision	Yes	—
Configuration & reset audit	No — the hardware cannot do it	The panel does not report when its project is restored or wiped, so those actions leave no line in the Protequ audit.
Configuration discovery	No — the hardware cannot do it	The panel does not send its device tree. Groups and detectors appear in Protequ only after you import the Intmel XML export.

Feature	Supported	Limitation
Fire panel state	Yes	—
Fire detection & address state	Partially	Flooding zones, fire-brigade panels, alarm areas and printers are not modelled as their own devices; unusual states from them appear as a supervisory note on the panel.
Fire signaling outputs	Partially	Sounders can be muted and reactivated. HAL and SAL relays hold until the alarm is reset and are not treated as sirens.
Fire intervention window	Yes	—
Fire system control	Partially	Mute buzzer works only after a full fire alarm, not during T1 or T2. Battery check and simulate-alarm are deliberately not offered.

Feature	Supported	Limitation
Inputs	Partially	Protequ cannot close an input. The contact is read only; the operator can bypass it or put it in test.
Outputs	Partially	Outputs can be switched on or off and inhibited. There is no separate general On/Off/Reset command beyond those.
Output schedules	No — the hardware cannot do it	Output timing and schedules are set in the Integral project; they cannot be programmed from Protequ.