In the case of the
R2 station, you copy one of the three types of “export objects” from the
R2 tridiumx/obix jar (ObixAnalogExport, ObixBinaryExport, ObixMultistateExport) and paste it into the station, linking its output
into the priorityArray input of the
R2 object being controlled. Another link is also required, from the statusOutput of the controlled object back to the feedbackValue
input (fIn) of the export object. See “R2 ObixExport objects” on page 2-4 for more details.Then, back in the
AX station with the ObixClient, you rediscover the Points (“lobby” object tree), and add a new proxy point for the “root node”
of each added export object, selecting the default writable point (NumericWritable, BooleanWritable, etc.) for each one.
These Obix proxy points provide the array of priority inputs for link control from the local
AX station, as well as actions to invoke. Note that as with other discovered
R2 objects, in addition to the “root node” they are expandable to select properties to proxy separately. Several config properties
may offer utility to proxy as writable types, for instance the “limit” associated properties of ObixAnalogExport objects,
providing they are “limit enabled.” See the next section “AnalogExport Limit Notes” for related details.