Monitoring BACnet Devices with CAS Watchdog: Step‑by‑Step Tutorial

Monitoring BACnet Devices with CAS Watchdog: Step‑by‑Step Tutorial

Overview

This tutorial shows a practical, step‑by‑step process to monitor BACnet devices using CAS Watchdog. It assumes a small- to medium-sized building automation network, a central CAS Watchdog server (Windows or Linux), and BACnet/IP-capable devices. Steps cover installation, network discovery, device monitoring setup, alerting, and basic troubleshooting.

Prerequisites

• CAS Watchdog installer or package for your OS.
• Administrator access to the server running CAS Watchdog.
• BACnet/IP devices on a reachable subnet.
• Static IP or DHCP reservation for CAS Watchdog server.
• Basic knowledge of BACnet objects (Device, Analog Input/Output, Binary Input/Output).

1. Install CAS Watchdog

1. Download the appropriate CAS Watchdog installer for your OS from the vendor.
2. Run the installer with administrator privileges.
3. During setup:
   • Choose a dedicated data directory.
   • Set the service user (recommended: a non‑privileged service account).
   • Configure the application port (default 8080) and API credentials.
4. Start the CAS Watchdog service and confirm it’s running by opening the web console at http://:.

2. Configure Network and BACnet Interface

1. Ensure the server network interface is on the same VLAN/subnet as BACnet/IP devices or that appropriate routing/BBMD is in place.
2. If using BBMD, configure BACnet Broadcast Management Device settings on CAS Watchdog:
   • Enable BBMD.
   • Add peer IPs and ports for other BBMD nodes.
3. Open firewall ports for UDP 47808 (BACnet/IP) and the application port used by CAS Watchdog.

3. Discover BACnet Devices

1. From the CAS Watchdog web console, navigate to Device Discovery.
2. Choose the network interface and discovery method (Who‑Is/I‑Am).
3. Start discovery; discovered devices will appear with Device Instance, IP address, Vendor ID, and supported objects.
4. Review the list and select devices to import into monitoring.

4. Add Devices to Monitoring

1. For each device:
   • Click Add or Import.
   • Assign a friendly name, location, and device group.
   • Verify Device Instance and IP address.
2. Define polling parameters:
   • Polling interval (start with 30–60 seconds for critical points).
   • Timeout and retry counts.
   • Maximum concurrent polls (tune to avoid flooding the network).
3. Save and apply configuration; CAS Watchdog will begin polling selected objects.

5. Configure Points and Object Mapping

1. For each monitored device, map the BACnet objects to monitoring points:
   • Select object type (Analog Input, Binary Input, etc.).
   • Enter Object Identifier (e.g., analogInput:1) or use automatic mapping from discovered objects.
2. Set scaling, engineering units, and value ranges.
3. Configure state mapping for binary objects (e.g., 0 = Normal, 1 = Alarm).
4. Add descriptive labels and comments for clarity.

6. Set Alerts and Notifications

1. Define alert rules based on thresholds, state changes, or comms loss:
   • Example: Analog Input > 80% for 2 consecutive polls = Alert.
   • Communications timeout (no response for N polls) = Device Offline alert.
2. Configure notification channels:
   • Email (SMTP server settings).
   • SMS or push (via third‑party gateway if supported).
   • SNMP traps to enterprise monitoring systems.
3. Create escalation policies and suppression windows (maintenance windows).

7. Dashboards and Reporting

1. Build dashboards showing device status, alarms, and key trends:
   • Add gauges for temperatures, graphs for trends, and lists for active alerts.
2. Schedule automated reports (daily/weekly) for uptime, alarm history, and trends.
3. Export reports in PDF/CSV as needed.

8. Testing and Validation

1. Force test alerts:
   • Simulate a point exceeding threshold and verify notifications are sent.
   • Disable a device or block BACnet traffic to test offline alerts.
2. Verify polling rates and adjust to balance timeliness vs. network load.
3. Check logs for communication errors and resolve any address or routing issues.

9. Troubleshooting Common Issues

• Discovery fails:
  • Check UDP 47808 is open and no subnet isolation is blocking broadcast.