To support Chopan, the Jennic-based device requires the following:
The chopan kit installed.
To function only as a CHoPAN client (hibernating device support), its Sedona Framework app must configured with the following:
ChopanService (from chopan kit) added to its Service container.
ChopanNetwork (from chopan kit) added to its Service container.
ChopanDevices and ChopanPoints can then be added to its app using the special manager views under the Chopan Virtual gateway of the SedonaJen6lpDevice that represent it in the station.
To function as a CHoPAN server, its Sedona Framework app must configured with the:
ChopanService (if not already present, from chopan kit) added to its Service container.
ChopanServlet (if not already present, from chopan kit) added under the ChopanService.
Chopan server configuration is typical for most Jennic-based devices (non-hibernating), to allow Sedona proxy point updates using a tuning policy with “Chopan” as the comm type. See Chopan comm type considerations. Additionally, the device can be configured for Chopan client operation too, if direct access to data in some other networked Jennic-based device is needed.
Copyright © 2000-2014 Tridium Inc. All rights reserved.