Perhaps the biggest payback from using Chopan are the efficiencies it provides in polling of Sedona proxy points, providing that Jennic-based devices are configured for Chopan server operation. This applies to any “non-hibernating” device (typically, any device that remains continuously powered).
To take advantage of this, simply configure each Jennic-based device for Chopan server operation, and in the station’s proxy points for each device (under the SedonaJen6lpDevice’s Points extension), assign all proxy points to tuning policy(ies) that use “Chopan” as the “Comm Type” selection—the default type.
For more details, see Setting up Jennic-based devices as Chopan servers, and various sections in the NiagaraAX Sedona Framework Networks Guide, such as “Create Sedona proxy points (and action points”, “SedonaJen6lpNetwork properties”: tuning policy notes and Chopan comm type considerations.
In this scenario, any other client-side usage of Chopan is not typically required—unless perhaps, devices need to share data directly without station (Sedona proxy point) involvement.
Copyright © 2000-2014 Tridium Inc. All rights reserved.