Create Sedona proxy points (and action points)

NoteBefore creating Sedona proxy points, you should make sure the station host (typically JACE) has the necessary Sedona kit “manifest” files for all the Sedona Framework devices. Otherwise, errors will occur when trying to discover points. Even better would be to install all appropriate “Sedona environment files” on the station’s host platform, which includes kit files and platform files, in addition to kit manifest files. For procedures, see sections JACE workflow and Installing Sedona environment files in a JACE in the Sedona Framework Network Driver Installation section.If Sedona device provisioning “through the station” is not needed, or in the case of a JACE-2 without the “maxHeap” license feature for expanded 128MB memory, you can simply transfer only the manifest files. See Run the Manifest Manager to ensure kit manifests are loaded.

As with device objects in other drivers, each Sedona Framework device (whether SedonaDevice or SedonaJen6lpDevice) has a Points extension that serves as the container for proxy points. The default view for any Points extension is the Point Manager (in this case, the Sedona Point Manager). You use it to discover and add Sedona proxy points and action points under any Sedona device component.

NoteThe Sedona Point Manager differs from other point managers in that actions on Sedona components are separately (and individually) modeled in the station as “Sedona action points”, different from Sedona proxy points (standard Niagara control components with a Sedona proxyExt). You create both point types, that is proxy points and action points, from discovered slots of Sedona components in a device using the Sedona Point Manager.

To create Sedona proxy points and action points

Once a Sedona device is added to the network (SedonaNetwork or SedonaJen6lpNetwork), you can discover the Sedona component slots in its app to select for modeling in the NiagaraAX station. Use the following procedure:

  1. In the Sedona Device Manager, in the Exts column, double-click the Points icon   in the row representing the device you wish to explore.

    This brings up the Sedona Point Manager.

  2. (Optional) Use the New Folder feature to make one or more point folders, each with its own point manager view—a method to “group” proxy points under a device. Then double-click a folder to continue.

  3. Click Discover to initiate point discovery using Sox connectivity. The view goes to a split-pane (learn mode) and a Configure Point Discovery popup dialog appears, as shown below.



    The default discovery type is Online when online with the device. Click OK to initiate the discover.

    NoteOffline is the other discovery type. It is more appropriate for offline engineering, and it requires the Sedona device component to have an associated app file. For related details, see Sedona device Association.

  4. A Discover launches a “Sedona Discover Points” job, with progress bar near the top of the view.

    Figure 9. Sedona Discover Points job in progress


    Sedona Discover Points job in progress

    The job ends with a single app component in the Discovered pane, which you click to expand.

  5. Click to select the data items you wish to model in NiagaraAX. Folders and components appear as red orbs, which you expand to see selectable slots—either properties ( , , ) or actions ( ).



    You can map selected items in the station in a number of ways:

    • Drag from the Discovered pane to Database pane (brings up an Add dialog).

    • Double-click an item in the Discovered pane (also brings up an Add dialog).

    • Click to select in Discovered, then press “a”. (“Quick Add”, meaning no Add dialog).

    This works the same as in other drivers’ Point Manager views (however, note if adding multiple items using the last method, all must either be properties or actions—but not a combination of both.)

  6. When the Add dialog for a property appears, you can edit the configuration of that proxy point’s SedonaProxyExt before it is added in the Niagara station. Initial property values are determined by Niagara, based upon the property’s data type and whether config or runtime. See Figure 10.

    Figure 10. Example Add dialog for selected property


    Example Add dialog for selected property

    The following entries are in the Add dialog (and Edit dialog) for a Sedona component property:

    • Name defaults to SedonaComponentName.propertyName for example, OccIn.out or AvgTemp.in

      This is the Niagara point name only—change if needed (it does not affect Sedona component).

    • Type is the Niagara control point type to use for the proxy point. For most Sedona config types, the default selection is a “writable” control point; whereas runtime types are typically “read-only” points. Float and double data types are Numeric points; integer and long data types default to Enum points.

      Boolean data types default to Boolean points; and string types are String points. For related details, see Sedona property data types to default Sedona proxy point types.

      NoteChose Type before making changes to other properties below; otherwise they become reset. Unlike other editable entries in the Add dialog, you cannot edit Type later in the Edit dialog.

    • Address is the numerical Sedona address (compID.slotID) of the property slot. It is recommended you do not manually edit this.

    • Type Id is the numerical type ID of the data.

    • Property Type reflects whether the value is stored in the device’s non-volatile Flash memory (config) or not (runtime).

    • String/Buf applies only if the target property is type Sys::Buf, and determines if Niagara attempts to interpret the byte array as a Sedona string, or just leave it as a byte array.

    • Enabled is to enable (true, the default) or disable the proxyExt. If set to disabled (false), the point’s out value has a disabled status.

    • Facets lets you set the proxy point’s facets, where some default facets may exist (e.g., if associated “device facets” are present), or there may be no facets defined. Typically, except for string data, you assign facets if they are needed to define units, decimal precision, or states of enumeration, etc.

      Often, Boolean points use the two facets: falseText and trueText, and Numeric points use the two facets: units and precision.

      To assign facets if none exist:

      1. Click the (open) control for Facets for a popup Config Facets dialog.

      2. In the Config Facets dialog, click (time saver) to select from any previously entered facets, and repeat as necessary. If facets needed are not listed, add facets by continuing on to 3

      3. Click (add) for a new key.

      4. Either type over the highlighted “key” name with another key name such as: units (if a Numeric point), or falseText or trueText (if a Boolean point), or click the (drop-down) control for key to select a key name from the list.

      5. Type or use controls as needed for the Type and Value fields, for example for falseText or trueText, type in a text value in the Value field. Or, for units, in Value click the (more) control and in the next popup select the (left side) unit class, then (right side) specific unit.

      6. Click OK to add the facet key/value, and if needed repeat again to add more facets.

    • Device Facets reflects native facets used in the device, if any.

    • Conversion specifies the conversion to use between the “read value” (in Device Facets) and the parent point’s facets, where “Default” is typically used.

    • Tuning Policy Name specifies which of the available TuningPolicies in the network should be used to read data from and (if applicable) write data to the property. The “Default Policy” is the default selection—other tuning policies are selectable in the drop-down list. For related details, see:

  7. When you have Sedona proxy point(s) configured properly for your usage, click OK.

    The proxy points are added to the station, and appear listed in the Database pane. Within a few seconds, the points will display current values.

NoteIf you selected one or more action slots ( ) instead of properties, the Add dialog is completely different, as shown in Figure 11.

Figure 11. Example Add dialog for action slot on a Sedona component


Example Add dialog for action slot on a Sedona component

In this case, there are only three entry fields, as follows:

For more details on Sedona points in NiagaraAX, see the following sections