Preparing alarms to send to the cloud
The CloudAlarmRecipient receives alarms from the framework as they are generated and sends them to the cloud using the configured cloud connector.
The
CloudSentienceDevice protocolType determines the protocol to use.
Prerequisites: The nCloudDriver palette is open.
- Expand the and drag a CloudAlarmRecipient component from the palette to the AlarmService.
- Double-click the newly-added CloudAlarmRecipientThe Cloud Alarm Recipient Property Sheet opens.
- To connect the recipient with the cloud device, use the Ord Chooser to navigate to the CloudSentienceDevice in your NiagaraCloudNetwork and select it.This
ORDdefaults to null, which prevents the cloud connector from routing alarms received by the recipient to - If
Enable Batch Alarmsis disabled, enable it (the default), configure theAlarm Batch DelayandAlarm Batch Sizeproperties and click Save.As with all aspects of cloud communication, message bandwidth is a primary area factor in system performance. Sending a group of items is always preferred over sending a single item (or sending multiple messages, each containing a single item). Grouping items into a single batch request improves both the performance (due to more efficient network usage), and the cost (incurring fewer message sends).The CloudAlarmRecipient groups alarms into batches when
Enable Batch Alarmsis enabled. When an alarm occurs, the station holds it for a brief time, configured by theAlarm Batch DelayandAlarm Batch Sizeproperties. As soon as the recipient either receives a number of alarms greater than or equal to the batch size or as soon as the batch delay transpires, it sends the group of alarms to the cloud. You can place a maximum upper bound on the additional delay introduced. By default the batch delay is 30 seconds; this can be decreased if you require faster alarm delivery.