I think it would be nice to discuss the differences between addressable protocols, especially between Honeywell panels. Lots of hobbyists might be intimidated by the slew of protocols, like CLIP, FlashScan, Velociti, SD, IDP, and the like. Perhaps some more experienced folks could explain them?
1 Like
I’ll explain the Honeywell brands – how their protocols work.
These are the ones with the two dials – “TENS” and “ONES”. These dials are often referred to as “Decade”.
(photo credit BuyFireAlarmParts)
How the dials work is exactly how they sound. For address 95, you set the TENS to 9 and the ONES to 5.
The way these protocols work though is that there’s two sets of addresses: Detectors and Modules. This is different from other brands that have a single set of addresses that you can mix and match devices on.
CLIP was used first by Notifier, Fire-Lite, and FCI, who were all owned by Pittway at the time.
Later on, a high speed digital version of CLIP was developed by System Sensor and first implemented on Notifier… with FlashScan.
FlashScan is able to poll devices at a much faster rate, is more resistant to interference, etc.
Later on FlashScan was given to Gamewell-FCI and they brand it as Velociti.
The next ones are LiteSpeed, and SK, used by Fire-Lite, and Silent Knight, respectively. They’re all similar to FlashScan but work differently. This protocol is also (confusingly) used with the Notifier “FireWarden” series of panels.
Now for the compatibility…
There is an identification code in brand’s protocol… a Notifier CLIP device won’t work on a Fire-Lite or FCI CLIP system. Some of the smaller panels from other brands do not test for this identification code assigned to each brand. For example, Fire-Lite devices work on a Notifier “Firewarden” series panel, and vice versa. Notifier FlashScan devices work on the FCI 7100 as well.
Glossary:
CLIP: 198 device analog protocol developed by System Sensor.
FlashScan, Velociti, IDP, SK: 318 device high speed digital protocol developed by System Sensor for Notifier, then for Gamewell-FCI and Silent Knight.
LiteSpeed: 198 or 318 device (depends on panel) high speed digital protocol similar to FlashScan but not the same.
HFS: 25 device modified FlashScan protocol used only by the 25-point Silent Knight 5600 and Fire-Lite MS-25.
DCP: 127 device analog protocol developed by Hochiki. Silent Knight uses a similar protocol called SD500 but it is not exactly the same.
XP95: 127 device analog protocol developed by Apollo. Also known as Gamewell XP.
Discovery: 127 device analog protocol developed by Apollo. More sophisticated version of XP95.
MAPNET & MAPNET II: 127 device capacity analog SLC originally developed by Simplex in the 80s and 90s. Replaced with IDNET.
IDNET: 250 device digital SLC developed by Simplex in the 2000s to replace MAPNET II.
TFX: Autocall/Grinnell addressable protocol, developed in the 90s and had a very short life. Replaced by IDNET.
FAST protocol: Identical to CLIP. Used by FAST until they were bought out by EST.
EST Signature: 250 device self-addressing digital protocol used by EST systems. Has a lot of bugs.
FirePrint: 255 device digital protocol used by current Siemens and Faraday systems.
I know of another protocol that was used by Cerberus Pyrotronics before FirePrint but I do not know what it is. Since Gamewell was part of CP at one point, I bet it is the old Apollo protocol that came before XP95… whose name I do not remember.
2 Likes
I’ve been looking for this and it’s referenced as the XL3, which is a old addressable panel, the X series, or XL series (all the devices had an X in the name apparently). Take your pick, maybe you can connect something to an old Apollo protocol.
Notifier refers to it as the Cerberus XL3 in this document: http://www.notifier.com/salesandsupport/documentation/datasheets/dn_7075.pdf
I’m thinking the protocol never had an official name since it was proprietary. You’ll probably run into the same thing with EST.
Interesting… so you can hook Hochiki addressable pulls to a SK system or SK pulls to a FireNET system? That’s pretty cool.
I ask this because I’m looking at an IFP-100 and some inexpensive modules and sensors for it.
Depending on how old that IFP-100 is you may be able to use SK series devices.
Also I messed up a fact in my post… FireNET should be Hochiki DCP.
Also again… the Silent Knight devices are a slightly modified version of Hochiki devices and protocol. How it is different is the Hochiki modules need a programmer while the Silent Knight ones have DIP switches. The smokes from both brands need a programmer too. I believe the IFP-100 has a built in smoke detector address programmer though…
Unfortunately due to this difference, Hochiki DCP devices probably will not work on a Silent Knight panel.
I edited my post.
If I get it, I’d have to check the firmware version… At which version does it support SK devices?
Forget the IFP-100. Someone outbid me at the last possible second. :evil:
Great knowledge NewAge, let me clarify a few things.
Each brand as a unique ID code embedded in all the sensors. This prevents jobs from getting stolen between brand dealers/installers. Also is required for UL compatibility testing. Some panels (like the FireWarden) ignore or talk to multiple ID codes. For example the 7100 Series does not read the module code ID.
Actually was developed by System Sensor for Notifier NFS panels then given to FCI (renamed Velociti) for the E3 Series. Then a modified version was given to FireLite and Silent Knight.
Modified version of FlashScan to handle new unique ID codes and limit device count to 25 points. Both the 5600, MS-25, and GIF100 have firmware to handle FlashScan and HFS devices.
I’ve edited my post. Thanks for clarifying!
Are the Honeywell group devices interchangeable between firelight and notifier
No, not between Fire-Light and Notifier. I believe Notifier, Silent-Knight, and Gamewell-FCI (maybe?) are interchangeable, though, but someone please correct me if I’m mistaken.
So does that mean that I can only use firelight parts
If you have an addressable Fire-Lite panel, yes.
I believe your correct. As long as the panel doesn’t read the Manufacture ID i think, Destin knows for sure.
You’re correct about that. Known panels that do not read the ID are:
NFS-320
AFP-200, AFP-300, AFP-400
SK-5600
SK-5808
FCI 7100
Yay, i remembered. I wonder if System Sensor will only let Honeywell Companies use SSAP… :roll:
No actually, Mircom, Secutron, Fike, and another company I cannot remember the name of use system sensor addressable devices as well.
EST used them for a while too.
So if i wrote to System Sensor, could i get the stuff? It would be frigin’ cool to have a real protocol on my demo system…