Each point has a proxy extension (Proxy Ext), a frozen property. The proxy extension is important—it indicates how the point’s data originates, including details specific to the parentage of the point’s network and communications (driver).
A point’s proxy extension is either:
-
Null
For any point that you copy from the control palette (or add using the right-click menu), the proxy extension is simply null (NullProxyExt)—an empty placeholder. The station itself originates the point's default Out value.
Also, many kitControl components also have a NullProxyExt, as they are based upon ControlPoints. For details, see “Extensions and kitControl components” in the NiagaraAX kitControl Guide.
-
<DriverType>
For any proxy point, meaning any of the 8 point types you create using the Points extension under a device represented in any of the network types, the proxy extension is <DriverType>ProxyExt. For example, a BooleanWritable proxy point under the Points container of a Bacnet Device has a proxy extension of “BacnetBooleanProxyExt.”
For any proxy point, its proxy extension contains information organized in child properties. Some properties may be unique to that specific driver type.
Figure 111 compares property sheet views of the proxy extension properties for two BooleanWritable points, on the left a control point, on the right a BACnet proxy point.
For more details, refer to Drivers Guide sections “About proxy points” and “ProxyExt properties”.