Tutorial
i.CanDoIt® Guided Tour
BACnet IP Servers
This set of pages will provide a brief overview of i.CanDoIt® features and functions. Cruise through using the Next and Previous buttons, or skip around using the links at the bottom of the pages.
i.CanDoIt® Guided Tour
Table of Contents
1. Background
2. Device Overview
3. I/O Configuration
4. I/O Data and BACnet Objects
5. Calculations and I/O Cascade
6. Data Trending and Plotting
7. Thresholds or Event Rules
8. Data Logging
9. Event Logging
10. Email notifications
11. Time & Date Scheduling
12. XML Configuration Files
13. PL/i Programming
14. Internet Network Configuration
15. BACnet Port Configuration
16. BACnet IP Client
17. Modbus/RTU Gateway
18. User HTML/JavaScript and CGI
i.CanDoIt® Guided Tour (p.7)
Thresholds or Event Rules

What are Threshold Rules? What are Events? 
Where are the Alarms?

These questions all point to essentially the same answer. You build an alarm by defining a threshold rule. When the threshold rule is triggered or activated, we call this an event. There are several things you can do with an event, and you may treat any of them as an alarm. An event may result in turning specific I/O on or off. An event may result in a notification message being sent (e.g., via email to your cell phone). An event may send a message to a central server which then decides what to do. An event may simply be logged in an event file to simply record the fact that it happened sometime.

How do I set up an Alarm?

I/O point data is placed in "registers" by easily configured I/O. Threshold "rules" determine what constitutes an event. The image below is a screen shot of a threshold rule that will result in an event when the sensor on Analog Input #1 exceeds a level of 90. Data values are scaled to any units you decide. You find the threshold rules in the System->Action Rules->Thresholds page.

How do I prevent spurious events when the test value is hovering around the threshold?

Hysteresis will prevent spurious events near the threshold. In the following example, the event will occur when Analog Input #1 reaches a level of 90. If AI 1 drops below 90 by a margin less than 2, then returns to above 90, the event will not repeat. The value of AI 1 must drop below 88 and return to over 90 before the event will repeat.

How do I generate an event only after the condition has existed for a minimum time?

The on/off time qualifications are used to add time to the criteria. The following example shows a minimum on time of 5 minutes. This means the level on Analog Input #1 must exceed a level of 90 for at least 5 minutes before an event will be generated. If the minimum off time was also set, the rule must test false for that amount of time before it can repeat the "true" event.

How do I change event thresholds based on time of day?

Start by using a value object for the test threshold rather than fixed value as shown below:

Then alter the contents of this object based on schedule in the Advanced->Scheduler->Weekly Schedule page as shown below.

Using the example setup shown above, the event will be generated any time Analog Input #1 exceeds a level of 85 between 8AM and 4PM, Monday through Friday. The rest of the time, Analog Input #1 needs to exceed a level of 95 before an event will be generated.

How do I control outputs based on threshold rules?

Use all of the same criteria for setting up the rule. Now add a destination object and value to write to that object.

The above example says that Binary Output #1 will turn on any time Analog Input #1 is above 90.