In a station’s Sedona network, each Sedona device component is either “unassociated” or “associated” with a particular Sedona app file. These are the two association states.
When you first add a Sedona device component from a network’s device manager view, it is typically unassociated (unless you copied or duplicated a device component that was associated).
As shown in Figure 30, all but one SedonaDevice shows “App File Not Configured” in the App File column of the Sedona Device Manager. This reflects the initial state (unassociated). At this point, you could still perform an online point discovery with any of these devices. A Sox connection is made to the device when doing this.
However, you cannot perform an “offline” point discovery with an unassociated Sedona device. An offline point discovery reads the associated Sedona app file to present proxy point candidates (instead of communicating via Sox to the device).
Copyright © 2000-2014 Tridium Inc. All rights reserved.