Issue
Create a solution with an alarm definition and event filtering that will pulse an output to a phone dialer for alarm monitoring. Trigger the dialer when another output is active and when any of the inputs for door contacts, motion sensors, etc. have become active. Perform this solution on an Access Expert Intrusion only system without any readers.
Product Line
EcoStruxure Access Expert
Environment
AccessXpert Intrusion system with no readers
Cause
Without Security Readers, there is less hardware to process and monitor the logic required for a solution. Event filters cannot reliably evaluate both an input event and the current state of a separate output together.
Resolution
The following approach can be implemented using hardware I/O-level logic. This method combines the required conditions externally and presents them to the system as a single input event, eliminating the dependency on multi-event evaluation within the filter query.
Concept
Create a single system input that activates only when:
- The original input condition (GC/PIR/DC) is active, and
- The Notification Active output is active.
This is achieved by using outputs and relay contacts wired in series, allowing the system to see a single input that represents both conditions being true.
Wiring Logic
Once dry contacts are available, wire the following relay contacts in series:
- Output driven by the input condition (GC/PIR/DC)
- Notification Active output
The series relay path is then connected to a spare input, referred to as the Notification Alarm Input.
The Notification Alarm Input will only activate when both relay contacts are closed, meaning:
- The original input condition is active, and
- The Notification Active output is active.
Implementation
Step 1: Create an Output for the Original Input Condition
Configure the original input condition (GC/PIR/DC) to activate a dedicated output.
This output will serve as a representation of the input condition in the relay wiring scheme.
Step 2: Obtain a Dry Contact from the Notification Active Output
Depending on how the Notification Active output is configured:
Scenario A – Dry Contact Relay
If the Notification Active relay is being used strictly as a dry contact and is not switching external voltage, it can be used directly in the series wiring.
Scenario B – Power-Switched Relay
If the Notification Active relay is switching power (for example, 12VDC to a device), it should not be used directly in the input circuit. An isolated relay should be added to provide a dry contact interface.
Scenario C – No Spare Outputs Available
If no spare outputs are available, an external relay may be driven from the existing Notification Active output. The dry contacts from this relay can then be used to complete the series wiring.
Alarm Workflow
The resulting sequence is as follows:
- A GC/PIR/DC input event occurs.
- The event activates the dedicated input-driven output.
- The Notification Active output remains active for its configured timer duration.
- The input-driven output and the Notification Active output are wired in series.
- When both conditions are present, the signal is sent to the Notification Alarm Input.
- The Notification Alarm Input triggers an Alarm Definition.
- The Alarm Definition activates the Alarm Monitoring Service Notification Output.
- The Alarm Monitoring Service Notification Output generates a pulse to the dialer.
This approach has been tested and confirmed in a lab environment to produce consistent results, allowing the system to trigger only when both conditions are present.
Conclusion
When Alarm Definition Filters cannot reliably evaluate an input event and a separate output state together, combining the logic at the hardware I/O level offers a reliable alternative. By wiring the input-driven output and Notification Active output in series to a dedicated Notification Alarm Input, the system can accurately trigger the Alarm Monitoring Service Notification Output and generate the required dialer pulse.
Note: The above multi-step solution is needed for success. When attempting to create this with a single Trigger and Procedure, it would not work and would produce an error in Access Expert.
“Filter references element that is not in the event data. Element 'Output' not found.” This occurs when a filter attempts to evaluate both input and output conditions together and fails to trigger as expected.
The filter references the “Output” field in event data where that field does not exist. Input-driven events (such as DC, PIR, or GC) typically only contain “Input” and “Status” fields and do not include “Output.” As a result, combining input and output conditions within a single filter causes the evaluation to fail because both cannot be processed together in the same event context.
