Ethernet/IP or WiFi-equipped Sedona Framework devices that are based on Sedona TXS-1.2 may support device discovery. If so, and they are on the same LAN as the station’s host, you can use the learn/discovery mode of the Sedona Device Manager to discover and add SedonaDevices to represent them.
You must manually add any Ethernet or WiFi-based Sedona devices that do not support device discovery. This includes any device based on Sedona Framework 1.0. See Manually add SedonaDevices.
Discovering and adding SedonaDevices
Device discovery uses UDP/DASP multicasting on the selected Ethernet/IPv4 adapter of the station’s host platform (IPv6 is
not supported in Sedona TXS-1.2). The host’s TCP/IP (IPv4) settings must be configured correctly, including subnet mask and
default gateway, for online discovery to work.
(Optional) Use the Step 2.
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 as inDouble-click the SedonaNetwork for its default Device Manager view, and click the button. A two-pane “learn mode” appears, with a Configure Sedona Device Discovery popup.
In the Configure Sedona Device Discovery dialog, select the Ethernet/IP port to use, and either accept or change the defaults for discovery wait time (10 seconds) and Sox port (1876) as shown above. A JACE controller with both LAN ports enabled lists “en0” (LAN1) and “en1” (LAN2).
Click
to begin the discovery. A “Sedona Learn Devices” job launches, with progress bar at the view top.Discovered devices appear in the top Discovered pane following job completion.
Click to select discovered devices (hold Ctrl while clicking to select multiple) and click .
The Add dialog appears for the selected device(s).
For each row (device) in the top of the Add dialog, do as follows:
In the Name field, you typically enter another name instead of “dev IpAddress
” (may be changed later at any time). This is a Niagara name—it does not need to match any Sedona Framework app or component
name.
In the Credentials area, enter Sedona user credentials for a Sox connection.
Typically you leave Username at default admin
(for this standard user).
In Password field, enter the required password.
For discovered devices leave all other fields at default values, described below.
Sedona Address area:
Ip field reflects the IPv4 address of the Sedona Framework device (e.g. 192.168.1.4
).
Sox Port reflects the Sox port used of the Sedona Framework device (default 1876).
Disregard Chopan Port — currently, Chopan applies to SedonaJen6lpDevices only.
Leave Enabled at true
.
App File is initially null (file:^sedona/store/SedonaNetwork/null
); it remains so until the device is “associated” with an app file (one way is to “get” the app currently in the device using
the Sedona Tools under the networked device). For details, see Sedona device Association.
Click
to add the SedonaDevice(s) to the network.If successful, you should see each device with “ok” health in the Sedona Device Manager (Figure 1).
Repeat the discover and device add if necessary for additional TXS-1.2 based Sedona Framework devices.
Other device component properties and containers are available on each device’s property sheet. For related details, see SedonaDevice.
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 networked Sedona devices.
For quick start procedures, see:
Installing Sedona environment files in a JACE (recommended over loading just kit manifests).
Run the Manifest Manager to ensure kit manifests are loaded. (not necessary if installing Sedona environment files).
Copyright © 2000-2014 Tridium Inc. All rights reserved.