Most proxy points for
R2 objects, including ones for “input writable” ones such as BinaryOutput, AnalogOutput, MultistateOutput, Loop, and so forth
are proxied as read-only points only—writable
AX point types like BooleanWritable, NumericWritable, etc. are not selectable. This applies to all nodes and properties that
appear in the Discovered table with a “Mode” of “RO” (read only).However, object commands are available, as actions of the read-only proxy point. See figure below and also the “Command Notes”
topic.
Some
R2 object properties show a discovered “Mode” of “RW”. Most are configuration types such as alarm limits (e.g. “lowLimit”, “highLimit”),
“deadband”, and “notificationClass” as a few examples. If desired, you can proxy such a property as a writable point type,
e.g. NumericWritable, BooleanWritable, etc. This allows you to write the
R2 property value from the AX station, either by an invoked action on the proxy point, or by linking to the proxy point’s input(s). NOTE: By default, right-click actions on a writable Obix proxy point include both
native
AX actions for the writable point - to change the value of the specific
R2 propertyactions for the commands on the parent
R2 object - to directly command that objectIn some cases, you may wish to hide some action slots, e.g. ones for the parent object’s commands. Or, if link control (via
proxy input) is the only intended method, you may wish to hide all action slots. If hiding any actions, be sure to hide the
“forceUpdate” one. Typically, “standard” control logic linking from
AX to an
R2 object requires additional engineering on both sides.Figure 24. Proxy point for
R2 object or property offers actions for commands, even as read-only point
