Chopan usage in Sedona Framework terms

The following is a list of terms and abbreviations used in this document when describing Chopan usage in the Sedona Framework. For other Sedona Framework terms, see “Sedona Terms” in the NiagaraAX Sedona Networks Guide. For general NiagaraAX terms, see the Glossary in the User Guide. Note that this glossary may grow over time, or may simply be eliminated.

Glossary

6LoWPAN

Acronym for IPv6 over Low power Wireless Personal Area Networks. It is an international open standard that enables using 802.15.4 and IP together. The Sedona Framework was created with 6LoWPAN networking capability in mind, reflected in its DASP and Sox protocols.

app

The app in a Sedona Framework device is its application of Sedona Framework components and services, including links between them, and all configuration properties. Components and services are selected from kits installed in the device.

Chopan

Or CHoPAN, for Compressed HTTP over Personal Area Networks. It is a Tridium proprietary protocol used in Sedona TXS to support Jennic-based devices, particularly any hibernating device. Chopan runs over UDP/IP and is a “session-less” protocol (unlike Sox), offering a number of advantages over Sox in certain applications. Chopan usage involves different components and views in the NiagaraAX and Sedona Frameworks, and is the subject of this document.

ChopanService

The component in the Jennic-based device’s app that provides communication capability over CHoPAN. By convention, it is located in the app’s “service” folder.

ChopanServlet

The component in the Jennic-based device’s app that handles incoming CHoPAN point reads and writes (server-side functionality). By convention, it is a child of the ChopanService component.

Note that equivalent functionality in the JACE station is provided by the ChopanServer child of the station’s SedonaJen6lpNetwork component.

ChopanNetwork

The top level component in the Jennic-based device’s app that can initiate reads and writes (client-side functionary). By convention, it is located in the app’s “service” folder. It can contain child ChopanDevice components.

ChopanDevice

A component in the Jennic-based device’s app that is a proxy representation of a remote CHoPAN server device, providing addressing information. It can contain child Chopan point components. The device may represent another Jennic-based device or the JACE controller (coordinator).

Chopan point

A component in the Jennic-based device’s app acting as Chopan proxy point, either of type ChoBoolPt, ChoBoolWr, ChoFltPt, ChoFltWr. You link these points to other components in the device’s app to share data.

coordinator

In a network of Jennic-based devices, the JACE station acts as the single “coordinator” node for all child nodes, using the Sedona Jennic option card installed in that JACE. The coordinator maintains info about its child nodes, each of which may provide routing functionality or be end devices. Properties of the station’s SedonaJen6lpNetwork configure the coordinator’s operating parameters.

DASP

For Datagram Authenticated Session Protocol. This is the low-level, secure session-based protocol that Sox utilizes. DASP operates in networks that include 6LoWPAN and resource-limited devices. Sedona network and device components in NiagaraAX provide debug properties that allow examining DASP and Sox messaging.

hibernating device

Refers to a type of Jennic-based device that “hibernates” (sleeps) the majority of time, periodically “waking up” for short periods to execute routines and exchange data with other devices. Typically, such a device is powered by an onboard battery or batteries. Such devices require configuration using CHoPAN (Chopan).

At the time of this document, Sedona Framework support for hibernating devices is not widely available. However, the SedonaJen6lpNetwork driver in the NiagaraAX station is “ready” for such device support. This is also noted in other sections of this document that reference “hibernating devices”.

Jennic-based

A Jennic-based device is the term used in Tridium tech docs for a wireless Sedona Framework device based on a Jennic micro-controller, with built-in 802.15.4 connectivity and 6LoWPAN stack support. Such devices are modeled as “SedonaJen6lpDevices” in the NiagaraAX station of a JACE controller (with an installed “Sedona Jennic” option card), under a SedonaJen6lpNetwork.

Note other Jennic-based devices exist that do not use the Sedona Framework application layer. Currently no Tridium products or tech docs apply to those “non-Sedona Framework” Jennic-based devices.

JenNet

The Jennic protocol that manages wireless 802.15.4 network formation and message routing, sitting above the 802.15.4 layer and below the 6LoWPAN layer. JenNet provides a “self healing tree” network. In a SedonaJen6lpNetwork, the JACE station is always the top “coordinator” node of the network tree.

kit

Sedona kits are the basic unit of modularity of Sedona software, encapsulating code, types, and metadata. A kit is analogous to a module on a NiagaraAX platform. The app in a Sedona Framework device instantiates components and services contained in its installed kits. You must have the appropriate kits available on your Workbench platform to change a device’s “core” software. Sedona Sox Tools in Workbench include a “Kit Manager” view to manage kits on a Sedona device.

PAN

Personal Area Network, a generic term for a device network that is typically limited to a small area.

Sedona Framework device

A Sedona Framework device (or “Sedona device”) is Sedona Framework Certified, and runs a Sedona app in a Sedona VM (virtual machine), using installed Sedona kits, and is configured in Workbench using a Sox connection. Devices may vary in a number of ways, including device connectivity—for example Ethernet/IP, WiFi, or 802.15.4 (wireless PAN). Currently, Chopan applies only to wireless Jennic-based devices.

Sox

Sox is the standard protocol used to communicate with Sedona Framework devices. It runs over UDP via the lower-level DASP protocol. Workbench always uses Sox to connect to (open) a Sedona Framework device, and to do initial configuration. A Niagara station also uses Sox to discover, and if so configured, to read and write to Sedona proxy points. However, if a Jennic-based device is configured with Chopan as a Chopan server, that comm type can be used for proxy point updates.

WPAN

Wireless Personal Area Network, a PAN (personal area network) using a wireless technology.