Sedona Device Manager view

Figure 15. Sedona Device Manager view


Sedona Device Manager view

The Sedona Device Manager is the default view on a SedonaNetwork, used to add and edit SedonaDevice components to represent remote Ethernet/IP-capable Sedona Framework devices.

This manager view operates in the standard way as many other NiagaraAX drivers; see “About the Device Manager” in the NiagaraAX Drivers Guide for general information.

NoteStarting in Sedona TXS-1.2 with AX-3.7, the Sedona Device Manager supports online device discovery for those devices that support it (must implement Sedona 1.2). In addition, support was added for “offline discovery” of proxy point candidates, providing the selected SedonaDevice has an “App File” associated.

For “quick start” procedures on using the Sedona Device Manager view to add SedonaDevices, see:

Other details on the Sedona Device Manager are in the following sections:

Sedona Device Manager discovery notes

Only Ethernet/WiFi-equipped Sedona Framework devices implemented with Sedona 1.2 may be capable of device discovery in the Sedona Device Manager. Devices implemented with Sedona 1.0 or 1.1 you must add manually, using the New button.

To support device discovery, a device’s SoxService joins an IPv4 multicast group and listens on port 18760 (the UDP port Niagara always uses to send the request). Devices respond on the “Discovery Port” specified in the configure discovery popup (Figure 16).

Figure 16. Configure Sedona Device Discovery popup dialog


Configure Sedona Device Discovery popup dialog

In this dialog:

  • Discovery Wait Time is the number of seconds that Niagara waits to receive Discover responses, at which point the discovery job completes. If no devices are found, the job is marked failed.

    Depending on the numbers and speed of devices, you may need to increase this time.

  • Discovery Port is typically left at 1876 (default), unless devices’ SoxService use a different Port.

  • Available Ethernet/IP interfaces are listed on the right, as shown in Figure 16 example for a JACE.

    You can select (click) only one port at a time for any discover job.

NoteOn the same SedonaNetwork, you can run multiple device discover jobs, selecting a different Ethernet/IP interface if needed. Thus, a single SedonaNetwork may have SedonaDevices installed on different LANs. To help organize, you could use the New Folder button to make Sedona Device Folders first, and then run the Discovers from the Sedona Device Manager of each folder.

Information from discovered Sedona devices

Sedona devices return their Platform ID value in a discovery response, which appears next to the IP address used by the device in the (top) Discovered pane.

Figure 17. Platform ID value returned with discovered IP address


Platform ID value returned with discovered IP address

As shown in Figure 17, Platform Id is a property of the Plat component in the device’s App (typically located in a service folder).

Troubleshooting Sedona device discovery

Associated with a discover, look in the Application Director of the platform running the station for output similar to below:



As shown in the example successful job above, station output lines indicate the start of the discovery job, the network interface and port used, and finally responses from discovered devices. If no devices respond, make sure the Sedona devices you believe should be discovered are attached on the network.

NoteIf no discovery message is sent by the station, make sure the host platform’s TCP/IP settings (subnet mask and default gateway) are set correctly.

Sedona Device Manager data columns

By default, table columns in the Database pane of the Sedona Device Manager include the following:

  • Name

    Niagara name for the SedonaDevice.

  • Type

    For the standard SedonaNetwork (sedonanet module), always “Sedona Device”.

  • Exts

    Two extensions

    • Points extension for the device — double-click for its Sedona Point Manager view.

    • Device Info extension for the device — double-click for its property sheet.

  • Address

    IP address of the Sedona Framework device.

  • Status

    Device component status, typically “ok” but possibly “fault” (license issue), “down”, or “disabled”.

  • Health

    “Ok” or “Fail” with timestamp of last device monitor ping. Fail typically coincides with a down status.

  • Fault Cause

    Typically blank, unless health is Fail, where any available “Fault Cause” string appears.

  • App File

    The currently associated Sedona app file in the station’s Sedona “app store” file space for this device. Initially, this is “App File Not Configured” for a newly-added (unassociated) device. For related details, see Sedona device Association.

NoteNot included by default, but available in the Table Options (menu), are items “Enabled” and “Credentials”.

Sedona Device Manager buttons

Figure 18. Buttons at bottom of Sedona Device Manager


Buttons at bottom of Sedona Device Manager

Across the bottom of the Sedona Device Manager are the following buttons:

  • New Folder

    Always enabled. Click to add a new SedonaDeviceFolder, each with a default Sedona Device Manager view.

  • New

    Always enabled. Click to manually add a new SedonaDevice component, after specifying its address, port, and credentials in a popup Add dialog. See Manually add SedonaDevices.

  • Edit

    Enabled if one or more SedonaDevice(s) are selected in the Database pane. Click for the Edit dialog, where all fields (except Type) can be edited.

  • Discover

    Enabled if the station is online. Click to start a Sedona Device Discover job, where you first choose a discover wait time, target Sox port, and Ethernet/IP port. See Sedona Device Manager discovery notes. For a detailed procedure, see Discover and add SedonaDevices.

  • Cancel

    Enabled if a discovery job is in progress; click to cancel.

  • Add

    Enabled if one or more discovered devices (in top Discovered pane) are selected. Click for an Add dialog, where you specify credentials for its app in a popup Add dialog.

  • Match

    Enabled if one discovered device (top pane) and one added device (bottom pane) are selected (as in most Niagara drivers that support online discovery).

  • Associate

    Enabled if one added device in Database pane is selected. Allows you to select a local Sedona app file (on your local Workbench PC) to associate with the device in the station’s “app store” file space.

    • If online with the station, the file is copied in its Sedona “app store” location for the device. For example: ^sedona/store/SedonaNetwork/Dev1/apps/app-20121030-085058.sax

      NoteIf also online with the SedonaDevice, after associating an app file to the device, you typically immediately use the Application Manager (under the device’s Sedona Tools) to install (Put) that app in the device.

    • If programming the station offline, the file is copied in that same spot in the config.bog file, and will be copied to that station upon a station install (Station Copier).

    A device with an associated App File can have proxy points discovered “offline”. For related details, see Sedona device Association.

NoteNot included by default, but available in the Table Options (menu), are items “Enabled” and “Credentials”.