door contact works fine in Security Check during testing but fails to arm

[flata4]

I am reaching out as I cannot find a rational explanation for the unusual behaviour of a wired shock and door contact detector. I am lost unless the faulty zone 16 has somehow not been programmed properly (although zone 15 if fine) or there is a strange software bug associated with zone 16.

1. Comfort CP9000-ULT/EN03 “Ultra” with firmware 7.183
2. LEM03-M2 for 16 additional inputs.
3. 24 zones in total, all 24 are used.
4. Comfigurator version 3.13.6.0
5. Detector is dual shock + magnetic reed Premier Impaq+ with Contact by Texecom model # AED-0001.
6. Faulty detector is zone 16. There is an identical detector in zone 15 which is working fine.
7. Zone 16 and zone 15 are set as “DoorWindow [1]”, identical setup in Comfigurator.
8. Security Check “walk mode” in Alarm > Arming and Disarming confirm that both zone 15 and zone 16 respond as expected to opening/closing of doors.
9. The fault is lack of debounce i.e. the detector stays “active” as if the door were opened so the system cannot arm, although the door is clearly closed. Closure of door in zone 16 has been simulated by magnet too such in case, no difference.
10. The obvious step is replacing the detector in zone 16, it has been done with new stock. Twice.
11. Resistors are 2.2k and 4.7k. They have been swapped between zones 15 and 16 just in case, no difference.
12. Impedances have been measure on zone 15 and zone 16 with their respective doors closed or open, the values are similar.
13. Power to detector in zone 16 has been tested.
14. Wiring detector in zone 16 to panel has been tested and continuity confirmed.
15. Wiring at panel level has been swapped between zone 15 and zone 16 as a test. In that test zone 16 detector (now wired as zone 15) works fine. I wished I had tested that detector in zone 15 (now wired as zone 16) has now gone bad but I had not thought about it until writing this – this would have confirmed a firmware bug.
16. Because of all the above, hardware fault of the detector or of the panel has been excluded.
17. That leaves incorrect setup of zone 16 in Comfigurator so file is attached although zone 15 is programmed exactly the same as zone 16.
18. Alternatively, there is a software bug in firmware 7.183 preventing arming due to incorrect reading of zone 16. Happy to provide data dump if told how.

[slychiu]

Can you replace zone 16 detector by an open close contact (a shorting wires will do) wired direct to zone 16 WITHOUT EOL resistors? 


Program zone 16 as NO EOL.  Then test zone 16 again. 

This method takes out the detector and EOL external resistors.
If the zone still does not behave as expected the CM9001 zone is faulty. It could also be a firmware bug but unlikely