The ES-50X manual and FS-Tools manual includes numerous possible detector types in programming, but it does not say much about their significance. Does a PTIR detector need to have its type set to ADAPT for proper functionality, or can it be set to Photo Super AR (or User-Defined-8) to make it non-latching? Also, if a Fire/CO or Photo/CO detector is set to report a supervisory for some event, does this supervisory latch?
Also, is there a way to map non-latching supervisories on the ES-50X to outputs that will automatically silence when the condition is clear?
The AD365 (I’m assume is the PTIR) would fall under ADAPT, as that’s what Fire-Lite calls them. You can try other options; any options that don’t work will result in a trouble.
Per the manual, CO conditions are considered latching supervisories.
As for mapping outputs to supervisory points, you can probably accomplish this by just mapping that detector and your desired outputs to a specific software zone.
Correct, the AD365 is the PTIR detector. I was asking about what options work in order to understand this functionality before buying a panel, since the function of this type selection determines whether an ADAPT detector can be made non-latching.
How about smoke/heat conditions coming from a Fire/CO or Photo/CO detector?
