Cloud Point Device Ext (nCloudDriver-CloudPointDeviceExt)

This component is the parent container for cloud proxy points that export station data to the cloud. All four base point types can be handled. Cloud proxy points are referenced and linked to station control points during discovery. Point data is written to the cloud platform either on change of value, or periodically using a batch update.

Figure 44. CloudPointDeviceExt properties

To access these properties, expand Config > Drivers > NiagaraCloudNetwork > CloudSentienceDevice, right-click Points and click Views > AX Property Sheet.

Name	Value	Description
Batch Update Enabled	`true` (default), `false`	Enables (true) and disables (false) batch updates. Setting this value to `false` can be useful to temporarily stop all traffic related to points for the purpose of diagnosing a problem with another aspect of the station.
Batch Size	`500` (default)	Specifies the number of point updates to be included in a single message. This may be tuned upward for larger stations to optimize bandwidth usage. Settings beyond around 5000 may not produce significant improvements due to restrictions on maximum message size by the SentienceIoTHub. This value is dependent upon the exact station structure, as the `Point Id` is included in the update. Its size depends upon the station folder structure. Stations with a flatter folder structure have shorter `Point Id`s, allowing the update message to fit more points. The tradeoff to this is that the flatter folder structure means more points are in each folder. Loading and viewing these folders might take longer. Stations with a deeper folder structure (or particularly long folder names) can fit fewer points in the update message (compression will mitigate this), but may have faster load times for viewing a particular folder.
Priority Update Interval	`0000h 00m 30s` (default)	Specified period for priority batch point updates as determined by the NiagaraCloudNetwork Priority Tuning Policy. Minimum limit is 5 seconds.
Standard Update Interval	`0000h 05m 00s` (default)	Specified period for normal batch point updates as determined by the NiagaraCloudNetwork Default Tuning Policy. Minimum limit is 1 minute.
Background Update Interval	`0000h 15m 00s` (default)	Specified period for background batch point updates as determined by the NiagaraCloudNetwork Background Tuning Policy. Minimum limit is 5 minutes.
Max Cov Points	`20` (default)	Specifies the maximum number of points that can be configured for COV messaging. CAUTION: This value should only be increased with care, as sending individual point updates is very inefficient and can cause the cloud platform provider to block systems communication to the cloud if too much traffic is sent.
Use Handle For Point ID	`true` (default), `false`	Configures the Point Id for the proxy points. It specifies whether Cloud Proxy Points will use Niagara Handle (true) or Slot Path (false) ord for generating their point ids. The option to select false is available only for backward compatibility, to allow installations to retain continuity of historical data that may have been pushed to the data storage using the old slotpath-based point id. The option to use slot path may be removed in a future release, so users are strongly encouraged to use this as a temporary option only. NOTE: When this property is changed, the Point Id of all proxy points is updated to reflect the new setting.
Force Relinquish Enabled	`false` (default), `true`	As of Niagara 4.10u3 and later: `false` allows Forge Connect Niagara to change a point value at a certain priority level only if Forge Connect Niagara executed the current override. `true` allows Forge Connect Niagara to change a point value at a certain priority level only if Forge Connect Niagara did not execute the current override. For example, when this property is set to `true` and a local operator directly overrides a point value in a Supervisor station without using Forge Connect Niagara, another operator can use a cloud application (such as Centralized Control) and force a relinquish action that allows the cloud application to override the local change. CAUTION: When `Force Relinquish Enabled` is `true` and a cloud application initiates a relinquish of a point from the Cloud, Forge Connect Niagara triggers a write of the latest value to the specified priority, then, after a delay, relinquishes control of the point. The `Force Write Delay` property configures this delay. Limitation: Only the Niagara driver supports this property. It is not supported for any other driver. Keep this property set to `false` for points under all other drivers.
Force Write Delay	`00000h 00m 00.100s` (default)	As of Niagara 4.10u3 and later, specifies how long of a delay to allow between a point write and relinquish when `Force Relinquish Enabled` is set to `true`. You should base this time on the maximum time it takes for a point write from Niagara’s Forge Connect. You may need to adjust this value based on the performance of each deployment. The qualified value for the Niagara driver (ndriver) in a lab environment is `00000h 00m 00.100s` (default value).

Actions

Learn Points — creates a CloudPointFolder for each folder in the station that it finds. This helps to organize the potentially large number of points into some logical structure. It also improves the performance for large stations significantly over creating all the cloud proxy points in the same folder. This is strongly recommended over standard point discovery and adding, for any station with more than several thousand points.