Online “point learns” are possible in some driver networks, for example the NiagaraNetwork, BacnetNetwork, LonNetwork, and NdioNetwork. Whenever available, this method is the easiest way to accurately add proxy points to the station database.
Any proxy point learn in NiagaraAX is a two-step process using the Point Manager, where you:
Under a selected device component, use its (Points device extension) Point Manager view to Discover data items as point candidates for inclusion in the station database.
Select and Add from those candidates, creating proxy points under the device’s Points container. (If you already used New to add points, you can also Match to those existing points).
The Point Manager reinforces this process by providing two separate panes in the view whenever you enter “Learn Mode.” See
About Learn toggle.
The Discover button is available in the Point Manager only if the driver supports online discovery. When you click Discover, the Point Manager view splits into two panes (Learn Mode), and at the same time typically launches a discovery “job” (Figure 55).
Under a LonNetwork, Point Manager has a Learn Mode, but no point Discover. All possible data items were already discovered when the parent device was discovered and added. Here, enter Learn Mode by toggling (see About Learn toggle).
Under a NiagaraNetwork (only), a Niagara Point Manager discover produces an intermediate dialog: the Bql Query Builder. You use it to browse the remote station and specify what items to select from as discovered proxy
point candidates. For details, see Bql Query Builder.
In Learn Mode, the two panes in the Point Manager operate as follows:
Discovered (top pane)
Lists data items discovered on the driver’s network, as proxy point candidates. For any data item found that already exists in the station database, it will appear “ghosted” (listed faintly). Note items listed may be “expandable”—see Discovered selection notes.
A job “progress bar” is also included on top of the Discovered pane.
A Cancel button is available during a discovery job. If needed, use it to stop discovery.
Database (bottom pane)
Lists proxy points and point folders that are currently in the station database.
As necessary, drag the border between the two panes to resize. Also (at any time), toggle between the two-pane Learn Mode and the single-pane (Database) view by clicking the Learn Mode tool in the toolbar (Figure 24), or using the Learn Mode command in the Manager menu.
Often, data items listed in the Point Manager’s discovered pane are expandable, having one or more related items, each individually selectable. Expandable items are indicated by a leading plus (+), which you click to expand (a toggle control).
Figure 56 shows an example item (Lonworks nvoUnitStatus) expanded to reveal individual numeric-type elements, each selectable as a separate proxy point.
Here, if you selected only the top “mode” element to add, you would have one proxy EnumPoint to monitor the enumerated unit status (auto, heat, cool, etc), but would not have any of the related numeric-type items proxied as control points.
Depending on the driver/device type, expandable discovered items represent individual properties or other “structured” data. Some examples:
BacnetDevice—Each top item is typically the “present value” property of the BACnet object (most commonly selected). Expand the item to see other properties of the object.
NiagaraStation—Using Bql Query Filter defaults (Config, control, ControlPoint), each top item is equivalent to the “Out” slot of the Niagara component (and most commonly selected). Expand the item to
see other slots in the component (including Out).
LonDevice—Each top item is typically the first element (field) in a structured SNVT (multi-field data structure), as used in that particular network variable (nv or nci). To access other data fields in the SNVT’s structure, you must expand that item.
For specific details, refer to the “Point discovery notes” section in a particular driver document.
The Point Manager's Add button is available in Learn Mode when you have one or more data items selected (highlighted) in the top discovered pane. When you click Add, an Add dialog appears that allows you to edit properties before the proxy point(s) are created in the station (Figure 57).
Whenever you select one or more items in the top discovered pane, the toolbar also has an available Add tool (“plus” symbol),
and the Manager menu has an Add command. Also, you can simply double-click a discovered item to bring it up in the Add dialog.
The Add dialog is nearly identical to the point Edit dialog, but allows you to edit Type as well as other properties.
Often, you may wish to change Type from the pre-selected one, at least between read-only points and the equivalent writable control point within that data category. For example, if adding a proxy point for the present value (default) property for a BACnet Binary Output object, you may wish it to be a read-only BooleanPoint point rather than the default BooleanWritable. As shown in Figure 58, you can do this in the Add dialog before it is added to the station database, (but not later using the point Edit feature).
In most cases, alternate point Types include StringPoint, and possibly others. Generally speaking, there are few practical
applications in changing the data category of a proxy point type (e.g. from Boolean to Enum or Sting), however, this may be an option. Note that if working under a
NiagaraNetwork, only read-only proxy points are available.
Address-related properties in the Add point dialog already have acceptable values for operation (otherwise, the data item would not have been discovered). It is possible you change only Name and possibly Type, unless you know other settings you wish to change now. You can always Edit these properties in the proxy point(s) after you click OK and add them to your station.
Match is a feature that may be useful when you have an application with proxy points you wish to reuse, or if you have programmed offline using the New point feature.
In the first case (application for reuse), you could have some number of proxy points included in an application that you have saved and now recopied under the target Points container. Often, address-related properties in the copied proxy points are incorrect. However, you can use the Point Manager’s Learn Mode and step through each proxy point in the copied application, and use the Match feature to “sync” with the intended (and discovered) data item.
In the second case (offline programming) where a connection to the actual device network is unavailable, you can manually add New devices and New proxy points, and begin station engineering of a driver network. Typically, most component creations under a driver network are possible (including all levels) using the New command in the various “manager” views (Device Manager, Point Manager, other device extension managers). Or, you can add saved applications (from the device level on down) and edit as necessary. Then, when online with the driver network later, you could use Match to “sync” to existing components (device-level, proxy points, and so forth).
The Match button in the Point Manager becomes available when in Learn Mode, and you have:
Selected one point candidate in the top (Discovered) pane.
Selected one existing proxy point in the bottom (Database) pane.
In this case, the toolbar also has an available Match tool, and the Manager menu has a Match command.
When you click Match, the Match dialog appears, as shown in Figure 59.
Match is strictly a “one-to-one” function for “discovered-to-database”—note that it is unavailable any time you have multiple items selected either in either the top Discovered pane or bottom Database pane.
The Match point dialog is nearly identical to the single-point Edit dialog, and typically provides the “discovered” point address values. Often, most properties in the Match dialog have acceptable address values required for operation (otherwise, the item would not have been discovered). You can always Edit the proxy point after you click OK and add it to your station.
Copyright © 2000-2014 Tridium Inc. All rights reserved.