Configuring point data for the cloud using Cloud Point Learn
Exporting cloud proxy points (that is, pushing point data to the cloud) is similar to point discovery in other drivers. The
key difference is that for other drivers you select data to be brought into the NiagaraStation, whereas for this driver, you select NiagaraStation data to send out of the station to the
In most cases, you want to export all (or nearly all) of a station points to
- Expand and double-click PointsThe Cloud Point Manager view of this component opens.
Two buttons for point discovery are available: Discover and Point Learn. For large stations, using the Discover button may cause you to experience very long wait times in both the discovery and the add phases. As the station gets beyond 10,000 points, this becomes significantly longer, and eventually will prevent a successful discovery job without modifications to the system properties for managing the fox connection between the
- Do one of the following:
- To use a discovery job for a small number of points, click Discover at the bottom of the view. When the Discovered table displays the points, select them and click Add.
- To use automatic point discovery in a large installation, click Point Learn at the bottom of the view.
When you click Point Learn, the Learn Points window opens.
The point learn configuration involves two parts: configuration of the discovery points and configuration of the cloud proxy points.
- The discovery of points in the station using point learn is the same as regular point discovery using the Discover button on the Cloud Point Manager view. The
Discovery Preferences’Point Queryis a BQL or a NEQL query that selects the points from the local station.NOTE: If the query is configured to return non-control point results, the points will not properly export to the cloud. - Proxy points in the cloud involve specifying two properties:
Tuning Policy NameandStation Point Input. These properties apply to the cloud proxy extension added for each discovered point.
You can limit the query to a particular part of the station database or to a type of point. You can also use
Tuning Policy NameandStation Point Inputto apply this setting to each added proxy point.You can perform repeated point learn invocations without conflict. Points that already exist are not to be duplicated or added again. This also means that you could learn different sections of the station database in chunks, if you prefer to make the construction of the necessary BQL queries easier.
- Expand
Discovery Preferences, configure the properties including thePoint Queryand click OK.The points that are identified by the configuredPoint Queryare added to the station. The folder structure of the station itself is replicated as needed in CloudPointFolders, so that the same organizational hierarchies created for the source points are present for the cloud proxy points. This makes it much easier to find cloud proxy points, and it makes the discovery process and subsequent management of the proxy points much more performing. - To view the Job Log that displays job results, expand and double-click JobService.The Job Service Manager opens.
- Click on the double chevron (>>) icon to the right of the Cloud Point Learn job to view the log.The Job Log opens.
