This section demonstrates the typical workflow for engineering Sedona networks in offline mode.
The examples shown here use the app file and platform included in the sample device simulator download file available on the Niagara-Central portal. For details, see Sample device simulator platform included in TXS bundle.
There are known limitations to using the sample device simulator platform to engineer a SedonaJen6LpNetwork offline. For details,
see Limitations engineering Jen6Lp networks using the simulator
The following procedures are described in this section:
Discovering the simulated device and adding it to a locally running station
This procedure describes performing device discovery against the device simulator and adding the discovered device to a Sedona Network in a locally running station. Configuring this new device establishes the device’s app file association and places a copy of the app file in the station database.
For more details, see “Configure SedonaNetwork” in the NiagaraAX Sedona Framework TXS-1.2 Networks Guide.
Prerequisites:
An app file successfully running in the Device Simulator
A locally running station with a Sedona Network
You must to be licensed for
sedonanet
in order to run a Sedona Network.
In the nav tree under MyHost
, locate and expand the a locally running station containing a Sedona Network. Expand the Config node. Double-click on the Drivers node to display the Driver Manager view.
In the Driver Manager view, double-click the Sedona Network to open the Sedona Device Manager view, and click at bottom of the view to initiate device discovery against the device currently running in the simulator. The Configure Device Discovery popup displays showing the IP address for the local host, click OK. The Learn Devices progress bar displays while the simulated device is detected, as shown here.
In the Sedona Device Manager view, select the discovered device displayed in the Discovered pane and click .
In the Add dialog box, click the Directory icon to the right of the App File field to select the app file currently running in the device simulator and click OK, as shown below. This establishes the app association for the device, placing a copy of the simulator app file in the station directory database.
The added device displays in the Database pane in the lower half of the Sedona Device e Manager view, and the device also appears under the SedonaNetwork node in the Nav tree.
Performing point discovery on the simulated device
This procedure describes how to discover data items in the simulated device as point candidates for inclusion in the station database which can be used as binding targets for widgets in a Px View, alarm and history extensions, and links to schedules and control logic.
For more detailed information on discovering proxy points, see “Create Sedona proxy points” in the NiagaraAX Sedona Framework TXS-1.2 Networks Guide.
Prerequisites:
An app file successfully running in the Device Simulator
A station running locally with a Sedona Network
A new Sedona device associated with the app file currently running in the Device Simulator
In the new Sedona Device, open the Sedona Point Manager view and click to initiate point discovery against the device currently running in the simulator.
In the Configure Point Discovery dialog box, the default discovery type is Online when online with the simulated device. Click OK to initiate the discover.
After completing point discovery, expand the app node to see the point candidates, as shown here.
In the Discovered pane, right-click a point and click
to add a new proxy point.Using this method, the proxy point added to the database is matched to the point in the device, configured with the appropriate
Address
value.
When working off-site, the recommended method for creating proxy points is to right-click a point in the discovered pane and
click . “Adding” configures the proxy point with the correct
Compid:Slotid
address value. Other methods for adding new proxy points, such as using the New button or the palette, are not recommended.
When you have the proxy point(s) configured for your usage, click
. The proxy points are added to the station, and appear listed in the Database pane, as shown below. Within a few seconds, the points should reflect current values. Of course, these values will be static because you are running against a simulator SVM.Viewing proxy points to confirm expected behavior
This procedure describes how to view proxy points to see points, such as ramps, updating as polling occurs.
In the Nav tree under the expanded SedonaDevice, right-click
and click to display the wire sheet view.Confirm that the proxy point values are updating.
Accessing the simulator app via the Sox Gateway
This procedure describes how to access the app in the simulated device in order to modify app logic.
In the Nav tree, expand the Sox Gateway node under the device. Then right-click the App node and select to display the wire sheet view for the app, as shown here.
Modifying the simulator app, saving changes and updating station file space
This procedure provides an example of making changes to the app in the simulated device which you have accessed via the Sox Gateway, updating the app in the station file system by performing a Get, as well as saving the modified app to your file system.
When you modify the app running in the simulated device, those changes are not reflected in the copy of the app located in
the station. You must use the Application Manager provisioning tool to Get the updated app from the simulated device and place a copy in the station file space. Doing this ensures that the most recent
version of the app file is placed in the station file space.
To remove points from the app:
In the Nav tree, access the Wire Sheet view for app, select two of the point components, LED0
and LED1
, right-click and click .
In the Nav tree, expand the Sedona Tools node and double-click the Application Manager to launch the provisioning tool.
Perform a
operation which accomplishes two things:Saves the changes to the simulator app file running in the sandbox area for the Device Simulator
Places a copy of the modified app file in the station file space, updating the app file there
In the Device Simulator, click !sedona/store/apps
directory.
If you encountered any problems while working with the simulated device, see the Troubleshooting appendix.
The completed app can now be transferred to the actual job site for installation.
Copyright © 2000-2014 Tridium Inc. All rights reserved.