Sedona Framework terms

The following is a list of terms and abbreviations used in this document when describing networks of Sedona Framework devices. For general NiagaraAX terms, see the Glossary in the User Guide. Note that this glossary may grow over time, or may else 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. Sedona 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 components and services, including links between them, plus all configuration properties. Components and services are selected from kits installed in the device. In this way, an app is analogous to a station on a NiagaraAX platform. Using a Sox connection, Workbench can be used to engineer an app and save it to the device’s Flash memory. Starting in Sedona TXS-1.2, each networked Sedona device also has an “App Manager” view under its “Sedona Tools” in a station connection, for getting/putting a device’s app in the station’s file space. This feature requires use of the Sedona Environment Manager (platform view) to station’s host.

A Sedona Framework device may also have a “fallback app”, residing in a different area of Flash memory. A fallback app is started via some local device-specific method, for example, pressing push-buttons in combination.

bundle

Sedona Framework TXS software is distributed in a “bundle”. A bundle is a special image (set of files) that is available from Niagara-Central (www.nigara-central.com). You use the Sedona Installer tool in Workbench to install a bundle. Bundles include Sedona TXS-specific NiagaraAX modules (.jar files), among other items. For more details, refer to the NiagaraAX Sedona Installer Guide.

Chopan

Or CHoPAN, for Compressed HTTP over Personal Area Networks. It is a Tridium proprietary protocol used in Sedona Framework TXS to support Jennic-based devices, particularly battery-powered devices. Chopan runs over UDP/IP and is a “session-less” protocol (unlike Sox), offering a number of advantages over Sox in certain applications. For related details, see About the Chopan Virtual gateway.

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. See SedonaJen6lpNetwork coordinator properties.

Alternatively, a special Sedona Jennic “USB stick” can be used as the coordinator with Sedona Framework Workbench (or Sedona Framework TXS-enabled Niagara Workbench) to support a Sox connection to a single Jennic-based device. No network functionality is possible. Setup of this USB coordinator is done using the “New Jennic Wireless Adapter” tool in Workbench. See the Jennic Serial Tools Guide for details.

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 Framework 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 is typically powered by an onboard battery or batteries. Such a device invariably “hibernates” (sleeps) the majority of time, periodically “waking up” for short periods to execute routines and exchange data with other devices. Such devices require configuration using CHoPAN (Chopan). See Hibernating devices.

Currently, Sedona Framework support for hibernating devices is not widely available. However, the SedonaJen6lpNetwork driver in the NiagaraAX station is “ready” for such device support if this changes. Other sections of this document that mention hibernating devices also note this.

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. See About 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, versus a mesh network. In a SedonaJen6lpNetwork, the JACE station is always the top “coordinator” node of the network tree. A special diagnostic “Pan Sheet” view of the network provides JenNet data.

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 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. Starting in Sedona TXS-1.2, kit files are also among the “Sedona environment files” you also install in JACE, using the Sedona Environment Manager (platform) view. This allows Sedona device provisioning of networked devices through a station connection, using a “Kit Manager” view under the “Sedona Tools” of each networked device.

manifest

Each kit has a corresponding manifest, with all metadata needed by tools like Workbench to Sox connect to a Sedona Framework device, and for a station to support Sedona proxy points in that device. Manifest files are compact XML files, named using a kitName-checksum convention similar to kit files, but with an .xml extension.

Starting in Sedona TXS-1.2, manifest files are also among the “Sedona environment files” you also install in JACE, using the Sedona Environment Manager (platform) view. This allows Sedona device provisioning of networked devices through a station connection, as well as “Sox Gateway” access to the app in networked devices.

You can also use the Manifest Manager view of either Sedona Framework network type to manage kit manifests on the NiagaraAX host (JACE or Supervisor), or the Sedona Manifest Manager view in Workbench tools to manage manifests on your Workbench host. However, starting in Sedona TXS-1.2 the primary use for the Manifest Manager view is for updating kit manifests in the local (Workbench) environment. For complete details, refer to the Sedona Manifest Manager - Engineering Notes document.

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 runs a Sedona Framework app in a Sedona Framework VM (virtual machine), using installed Sedona Framework kits, and is configured in Workbench using a Sox connection. Sedona Framework devices may vary in a number of ways, including device connectivity—for example Ethernet/IP, WiFi, or 802.15.4 (wireless PAN).

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. A Niagara station also uses Sox to discover and (typically) read and write to Sedona proxy points. However, if a Jennic-based device is configured with Chopan, that comm type can be used for proxy point updates.

WPAN

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