Do this after configuring key SedonaJen6lpNetwork properties (see Configure key SedonaJen6lpNetwork properties). SedonaJen6lpDevices represent wireless Jennic-based devices. For background details, see About Jennic-based devices.
Adding discovered Jennic-based devices
Double-click the SedonaJen6lpNetwork for its default Device Manager view, and click the button. A “Sedona Learn Devices” job quickly runs, and shows discovered devices in the top pane.
(Optional) Use the
feature to make one or more device folders, each with its own device manager view—a common method to “group” devices. Then double-click a folder and do a discover.Click to select one or more devices, then click the Figure 4 shows the Add dialog.
button.Often properties can be left at defaults, including (initially) Name. After adding devices to the database you can rename devices with more meaningful text. See Rename SedonaJen6lpDevices.
Click
to add devices to the database.Figure 5 shows all discovered devices added to the station database using default names. Typically, now you rename all the SedonaJen6lpDevice components. See Rename SedonaJen6lpDevices.
Other device component properties and slots are available on each device’s property sheet. For related details, see SedonaJen6lpDevice.
Each device has a points extension, with a default Sedona Point Manager view. However, before adding proxy points you should (at a minimum) make sure the station’s host (typically a JACE) has the necessary Sedona kit manifest files.
Even better, and required to support “Sedona device provisioning through the station”, you should install all the necessary
“Sedona environment files” on that station’s host. In addition to the Sedona kit manifest files, this includes all the kit
files and platform archive files used by the networked Sedona devices.
For quick start procedures, see:
Installing Sedona environment files in a JACE (recommended over installing just the kit manifests).
Run the Manifest Manager to ensure kit manifests are loaded (not necessary if Sedona environment files have been installed in the JACE).
Copyright © 2000-2014 Tridium Inc. All rights reserved.