Depending if adding property items or action items, the Add dialog in the Sedona Point Manager varies.
An example Add dialog for a Sedona proxy point is shown in Figure 61 below.
Data fields in the Add (and Edit) dialog for a proxy point contain most properties in the SedonaProxyExt, along with a few others. The fields are as follows:
Name
Niagara name of the Sedona proxy point, which defaults to Sedona ComponentName.slotName
, which can be left at default or changed if needed.
Type
Niagara control point type for the proxy point, for example, Numeric Point, Numeric Writable, Boolean Point, Boolean Writable, and so on.
Chose 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
Unique numerical ID of the property in the app, in form compId.slotId
, for example 9.4
for the fourth slot of the ninth component.
Automatically determined at proxy point add time. Manual editing is not recommended.
Type Id
Read-only integer value, used internally to properly encode write values.
Property Type
Either or Runtime
or Config
.
If Runtime, the property’s value is not saved to non-volatile Flash memory on an app save.
If Config, an app save preserves the property’s value to non-volatile Flash memory.
Often, runtime properties also have a “readonly” flag set—if so, typically the default proxy point type selected in the Add dialog a read-only type (BooleanPoint, NumericPoint, etc.).
String/Buf
Read-only value, either Buf or
Str. If Buf, the slot’s value may be interpreted as a byte array or other data structure. If Str, the slot’s value may be interpreted
as a null-terminated string. Applicable only if the Sedona property is type
sys::Buf
.
Enabled
Either true (default) or
false, to enable/disable the proxy point. If set to false, the point’s status is disabled, and any value polling is stopped.
Facets
Point facets for the proxy point value, which are typically edited from defaults.
Device Facets
Device facets for the source slot’s value, if any.
Conversion
Specifies the conversion used between the “read value” (in Device Facets) and the parent point's output (in selected point facets). Typically left at the “Default” selection.
Tuning Policy Name
Specifies which of the network’s (SedonaNetwork or SedonaJen6lpNetwork) tuning policies should be used for reads and (if applicable) writes to this proxy point.
For related details see:
Once added to the station, you can edit any of these fields if needed—with the exception of Type.
An example Add dialog for a Sedona action point is shown in Figure 61 below.
There are only a few fields in the Add (and Edit) dialog for an action point, described as follows:
Name
Niagara name of the Sedona action point, which defaults to Sedona ComponentName.slotName
. This can be left at default or changed if needed.
Type
Always Sedona Action Point, and not editable after adding point.
Address
Unique numerical ID of the action in the app, in form compId.slotId
, for example 17.7
for the seventh slot of the 17th component.
Automatically determined at action point add time. Manual editing is not recommended.
For more details on action points, see About Sedona action points.
Copyright © 2000-2014 Tridium Inc. All rights reserved.