Edit Point view, Configuration tab

This view configures individual points. These can be module points or camera event points. You use this view to set up alarms for the event and to configure histories. You can also provide links from an event to other available Boolean-writable points.

NOTE: This description covers both reader and input/output points. Differences are noted where appropriate.

Figure 248. Edit Point (input view) for a remote module

The point’s display name appears at the top of the view. The screen captures show two flavors of this view. The one with three tabs opens when you edit a camera event point. The one with two tabs opens when you edit a remote module point.

There are several ways to access the views that edit points. For example:

To access camera points, you click Controller Setup > Remote Devices > Remote Drivers followed by double-clicking the Axis Video Network row in the table, click the Cameras tab, double-click a camera row in the table, click the Events tab, discover events, and double-click an event row.
To access module points you clickController Setup > Remote Devices > Remote Modules > Remote Module Setup, double-click the module row in the table, click the Additional Points tab, and click a link to a point.

Module point links

The Manage Devices link opens the Manage Devices window.
The Base Reader Module link opens the Base Reader Module properties.

Camera event point links

The Manage Extensions link opens the Manage Point Extensions window.
The camera configuration view opens the camera tab.

Remote module point properties

In addition to Status and Enabled, these properties support the configuration of points.

Property	Value	Description
Edit button and Facets	button and additional properties	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.
Inactive State	`Open` and `Closed`	Defines the normally inactive state of the digital input or relay output as either `Open` or `Closed`, depending on the device requirements.

Camera event point properties

In addition to Status, these properties support camera event points.

Properties	Value	Description
Facets	Edit button	Opens a window for configuring the text that appears when a camera event occurs.
Proxy Ext	additional properties	Expands to display proxy extension properties, which apply to camera events. Refer to Proxy Extension properties.

Proxy Extension properties

Figure 249. Proxy Ext properties

In addition to the standard properties (Status, Fault Cause, and Enabled), these properties support camera events.

Property	Value	Description
Facets	button and additional properties	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 (defaults to `Default`)	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.
Tuning Policy Name	drop-down list (defaults to `Default Policy`)	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.
Read Value	read-only	Displays the last value read from the device, expressed in device facets.
Recipient (general)	additional properties (defaults to `device-1` which indicates that the destination is not defined)	Specifies one of two alarm event destinations. `Device` identifies a unique object `Instance Number`. `Address` provides an alternate address with separate properties. Niagara Alarms Guide
Write Value	read-only (applies to writable types only)	Displays the last value written using device facets.
Most Recent Event	read-only	Indicates the most recent “motion start” or “motion stopped” event.
Auto Expiration	`true` (default) or `false`	Turns this feature on and off.
Auto Expiration Interval	+ or — hours, minutes, seconds (defaults to 45 seconds.	Configures when the event is no longer valid.
Point Id	read-only	Identifies the point.
Enable Detection On Boot	`true` (default) or `false`	Configures the system to detect this point when the station starts.