Hello,
We’re having a few issues with the Intrepid and Milestone integration.
Problem tamper of PM casing:
If we open a Intrepid PM (Processing module) we receive a tamper alarm from the PM housing through the MIPS plugin.
This alarm arrives correct in alarm monitoring.
The problem is that if someone acknowledges the alarm whiteout closing the case the alarm does not arrive again in Milestone
Our clients want that the alarm comes in again as long as the casing is open.
We have already spoken with developers of Intrepid and they told is that Intrepid sends an alarm the whole period that the casing of the PM is opened.
Problem Interpid wire cut
This problem is similar to the problem that we have with the tamper alarms.
The alarm of a wire cut only arrives one time.
We want that the alarm of a wire cut keeps arriving in Milestone as long as the wire is not repaired.
Even after an acknowledge in Milestone his alarm monitoring it should keep coming back.
We have already spoken with developers of Intrepid and they told is that Intrepid sends an alarm the whole period the cable is cut.
No Problem:
If a certain zone of the fence goes in alarm and you acknowledge it in Milestone it arrives again in Milestone when the same zone goes again in alarm.
This function works as supposed to be.
Question:
Our client wants that we process the comm failures of the intrepid devices.
How is this possible?
Conclusion:
All alarms that arrive as a pulse work great.
Alarms that should arrive as an contact that is sustained don’t work.
Kind regards,
Myron Cuffez