If making use of the Chopan server in the JACE station, allowing one or more Jennic-based devices to make Chopan read or write client requests to NiagaraAX, some best practices are recommended. These practices include:
Before adding Chopan points in a device (typically using the “Chopan Virtual gateway” under a SedonaJen6lpDevice in the JACE’s station),
copy “ChopanTargetPoints” from the NiagaraAX jen6lp
palette into a folder you created under that device component. For example, create a folder named “ChopanPts” under the device,
at the same level with “Points”, “Parent Pan Info”, and so on.
Two ChopanTargetPoint types are in jen6lp
palette: ChoBoolTarget and ChoFltTarget. Each is a conveniently “trimmed” standard BooleanWritable or NumericWritable component, with all actions and all inputs
but “in10” hidden.
If reading (pulling) the value from the station, the client request is to the “out” property of this component. The “in10” property is linked in the station to another source component.
If writing (pushing) the value from the app, the client request is to the “in10” property of this component. The “out” property is linked in the station to another target component.
Copy one ChopanTargetPoint for each data item you are writing (from app to station) or reading (from station to app) into that folder.
Rename each ChopanTargetPoint to something descriptive, yet compact—as each will be a “target” for a Chopan point created in the Sedona app, with default names truncated at 7 characters. For example, if adding a ChoFltTarget to hold the out value of a NumericShedule in the station, used for a temperature cooling setpoint, then a name of “ClgSP_S” would help make this clear.
Copyright © 2000-2014 Tridium Inc. All rights reserved.