The following things are unique to the Sedona Point Manager:
Point discovery can be online or offline
Starting in Sedona TXS-1.2, providing a Sedona device has an app file “associated” with it, you can perform either an online or offline point discovery to add Sedona proxy points to the station database. For the online procedure, see Create Sedona proxy points (and action points). For details on “device to app association”, see Sedona device Association. For offline discovery details, refer to the Sedona Framework TXS Offline Engineering Guide.
Manifests required on the JACE
For proxy point support of any Sedona Framework device, the host (e.g. JACE) running the station with the Sedona Framework network requires at a minimum, the manifest file for each kit installed in the device. Otherwise, a “Sedona Discover Points” job will fail, and an error popup similar to Figure 58 below appears in Workbench.
To fix this, we recommend you install all the necessary Sedona environment files on the JACE to support networked Sedona devices, which include the appropriate kit manifest files. The recommended way to do this is with a platform connection to the JACE, using the Sedona Environment Manager view. Then rerun the point discovery.
For related procedures, see sections JACE workflow and Installing Sedona environment files in a JACE in the Sedona Framework Network Driver Installation section.
If a platform connection in unavailable, you could obtain the appropriate kit manifest file(s), and then transfer them to
the JACE using the Manifest Manager view on either Sedona Framework network (SedonaNetwork, SedonaJen6lpNetwork). See Run the Manifest Manager to ensure kit manifests are loaded. Then rerun the point discovery.
Action points available
In addition to Sedona proxy points, the Sedona Point Manager lets you add “action points”, which are unique to Sedona Framework devices. Each action point is a primitive component that represents a single action on the source Sedona component. Action points do not read data values nor accept point extensions like alarm, history, and so on—and have only a single property (Address).
An action point makes that same action available in Niagara, named using the action slot name on the parent Sedona component. If needed, you can add a display name for that action, working from the slot sheet of the action point. For more details, seeAbout Sedona action points.
Default point type may need changing
Each Sedona proxy point represents a single property of a Sedona component in the device’s Sedona Framework app. Knowledge of the device’s app is often required when making these decisions.
Variations between data types in Sedona and Niagara should be understood for type selection of proxy points. There is no “enum” (multistate) data type[4] in Sedona, however, “enum” point types default for any selected property that uses an integer data type (int, long). Sometimes this may be appropriate. Other times, you may wish to change type when adding, for example from “Enum” to “Numeric” for an integer property representing a count.
For more details, see About Sedona proxy points, and Sedona and Niagara data types and null notes.
[4] The boolean data type in Sedona is effectively multistate, as it can be either false, true, or null. This is the only multistate instance in Sedona. For more details, see Booleans as Enums.
Copyright © 2000-2014 Tridium Inc. All rights reserved.