The Chopan Virtual gateway is used to configure “Chopan points” in the device’s Sedona Framework app, via a virtual “Chopan Network” with “Chopan Devices” and “Chopan Points” in the Niagara station. The resulting Chopan components added in the device’s app act as the Chopan client interface to other devices’ “Chopan servers” (including the one for the station, in the SedonaJen6lpNetwork).
To support virtual gateway access from Niagara, the Jennic-based device requires the chopan
kit installed, and its Sedona Framework app configured with components from it.
If a non-hibernating (typically continuously-powered) device, Chopan usage is optional. However, Chopan as a “comm type” for normal Sedona proxy points offers bandwidth efficiencies. Also, via Chopan points, a device can exchange data directly with another networked Jennic-based device.
Such configuration is required if a hibernating[3] device (typically a battery-powered device), as Chopan points must be used instead of normal Sedona proxy points to exchange data with the station. Chopan is also used in the “maintenance mode” mechanism for a hibernating device.
A brief overview on Chopan points follows in this document, in the following sections:
For complete details see the Sedona Framework Chopan Usage document.
[3] Currently, Sedona Framework support for hibernating devices is not widely available. Chopan Virtual gateway usage without this support should be minimal, as it is necessary only if a Jennic-based device needs to request data directly from another networked Jennic-based device.
Copyright © 2000-2014 Tridium Inc. All rights reserved.