Add/Edit point
This type of window adds and edits proxy points in the Supervisor station’s database. Edit does not apply to point folders.
This window configures mostly proxy extension properties plus the parent point’s Name and Device Facets. These properties vary among drivers. To access all properties of the proxy point, including all those under any of its extensions, go to its Property Sheet.
To open an instance of this window under the NiagaraNetwork, expand , expand a NiagaraStation, double-click the Points folder and either click New or select an existing point and click Edit.
To open this type of window under other driver networks, expand , expand the network (for example BacnetNetwork), double-click its Points folder and either click New or select an existing point and click Edit.
You can select one or more proxy points in a station to edit.
| Property | Value | Description |
|---|---|---|
| Name | text | Provides a name for the object.
Editing this property is equivalent to the right-clicking Rename command on the component. In this case, the object is a point. |
| Display Name | text | Defines a BFormat
string used to format text by using values obtained from objects. You specify this string as normal text with embedded scripts identified by the percent (%) character. The driver maps calls within the script to an object’s methods. Use the dot operator (.) to chain calls. To insert a percent symbol itself, use two percent symbols (%%). For examples, click the question mark icon next to this property. |
| Type | drop-down list | Specifies the type of object. In this case, the type is a point. |
| Point Id | text | Specifies an ID for the point. |
| Enabled | true (default) or false | Activates (true)
and deactivates (false) use of the object (network,
device, point, component, table, schedule, descriptor, etc.). |
| Facets | Config Facets window | Sets up the text string that represents true and false values. For example, instead of true and false, the strings could be yes and no or enabled and disabled. |
| Tuning Policy Name | drop-down list | Selects a network tuning policy by name. This policy defines stale time and minimum and maximum update times. During polling, the system uses the tuning policy to evaluate both write requests and the acceptability (freshness) of read requests. |
| Device Facets | Config Facets window | Determine how values are formatted
for display depending on the context and the type of data. Examples
include engineering units and decimal precision for numeric types,
and descriptive value (state) text for boolean and enum types. With the exception of proxy points (with possible defined device facets), point facets do not affect how the framework processes the point’s value. Besides control points, various other components have facets too. For example, many kitControl and schedule components have facets. Details about point facets apply to these components too, unless especially noted. You access facets by clicking an Edit button or a chevron >>. Both open an Edit Facets window. |
| Conversion | drop-down list | Defines how the system converts
proxy extension units to parent point units. Default automatically converts similar units (such as Fahrenheit to Celsius) within the proxy point. Note: In most cases, the standard Default conversion is best. Linear applies to voltage input, resistive input and voltage output writable points. Works with linear-acting devices. You use the Scale and Offset properties to convert the output value to a unit other than that defined by device facets. Linear With Unit is an extension to the existing linear conversion property. This specifies whether the unit conversion should occur on “Device Value” or “Proxy Value”. The new linear with unit convertor, will have a property to indicate whether the unit conversion should take place before or after the scale/offset conversion. Reverse Polarity applies only to Boolean input and relay output writable points. Reverses the logic of the hardware binary input or output. 500 Ohm Shunt applies to voltage input points only. It reads a 4-to-20mA sensor, where the Ui input requires a 500 ohm resistor wired across (shunting) the input terminals. Tabular Thermistor applies to only a Thermistor input point and involves a custom resistance-to-temperature value response curve for Type 3 Thermistor temperature sensors. Thermistor Type 3 applies to an Thermistor Input point, where this selection provides a “built-in” input resistance-to-temperature value response curve for Type 3 Thermistor temperature sensors. Generic Tabular applies to non-linear support for devices other than for thermistor temperature sensors with units in temperature. Generic Tabular uses a lookup table method similar to the “Thermistor Tabular” conversion, but without predefined output units. |