This walk-through describes using CHoPAN to exchange data between a hibernating Jennic-based device and the JACE station, where the “Chopan Server” of the SedonaJen6lpNetwork is enabled (default), and the hibernating device has its app configured as a CHoPAN client and server (as described in section Required configuration in the Jennic-based device). Note all of the following replaces Sedona proxy point usage for this hibernating Jennic-based device.
Example Chopan point setup using Chopan Virtual gateway
Before using the Jen6lpDevice’s Chopan Virtual gateway, it would be best to have “target” writable Niagara points ready to receive read-only values from the hibernating Jennic-based device. In the Niagara jen6lp palette, there is a folder named “ChopanTargetPoints”, with two conveniently “trimmed” writable points:
ChBoolTarget — a normal BooleanWritable, but with all actions and all inputs except “in10” hidden.
ChFltTarget — a normal NumericWritable, but with all actions and all inputs except “in10” hidden.
Actions and other input slots are hidden to avoid confusion trying to control (write to) this read-only value from Sedona, say if dragging this control point on a Px page. Typical usage of these points is to receive some value like a temperature, or an equipment state from the device’s Sedona Framework app.
As a best practice, and for database portability/replication, it is recommended that you place such Chopan target points in a folder under the SedonaJen6lpDevice that represents the hibernating device. Note that the standard “Points” folder is not the best choice—as these are not proxy points, and for this reason do not appear in the Sedona Point Manager view.
Figure 44 above shows three such points copied from the jen6lp palette into a “ChopanPts” folder under the SedonaJen6lpDevice (named “Shed_Sed_Hibernatng”).
Now, onto using the gateway.
In the following steps, virtual components must be clicked (versus expanded) to “enter” them.
The Chopan Virtual gateway is clicked, and it soon expands to reveal a
ChopanN component (Virtual Chopan Network) in its property sheet.
The ChopanN component is clicked, and the view changes to the Chopan Device Manager for that device. See Figure 45.
As shown in Figure 45, initially the Chopan Device Manager is empty—a Discover is needed to find other devices configured with a Chopan server.
The button is clicked, launching a Learn Chopan Servers job.
As shown in Figure 46, five devices were found, of which one is the JACE station (“SedJ6_5_6LPa”). In most cases, this is the device of primary interest—and the one to be added here.
The discovered JACE station is double-clicked to bring up the Add dialog, shown below.
Notice that Name is truncated at 7 characters—the maximum number of characters for naming any Sedona component. In this case, the name is changed from “SedJ6_5” to “SedJACE”, and then added (
).The added SedJACE Chopan Device is then double-clicked.
As shown in Figure 48, this brings up a “Choose Root of Discovery” dialog, reflecting the contents of the Config node of the JACE station, in an expandable tree.
The tree is expanded to find the previously added “ChopanTargetPoints” for this device.
As shown in Figure 49, the previously-created folder “ChopanPts” is selected as the root ( ). The view changes to the Chopan Point Manager for the (JACE) device.
In the Discovered pane, the folder is expanded to reveal the target points, then available properties.
The “in10” property is double-clicked to bring up the Add dialog.
The Add dialog defaults to a NumericPoint, with truncated name (in this case, “Shed_Te”).
As shown in Figure 51, name is edited to “Temp_in”, and point type changed to NumericWritable, and the point is added ( ). The actual Sedona component added is a ChoFltWr
(Chopan Float Writable).
This needs to be a writable point, because the source Sedona temperature component will be linked to it in the device’s Sedona Framework app.
The same method is used to add two other Chopan points in the device, also writable (Figure 52).
Note that these three Chopan point components, as well as the parent Chopan device component, now exist in the Sedona Framework app of the hibernating device. To make them operational, a Sox Workbench connection must be made to this device, such that the source Sedona components can be linked to them.
A “Maintenance Mode Request” action is invoked on the SedonaJen6lpDevice for this device, and following the “Maintenance Mode Active” popup, a tunneled Sox Workbench connection is made to it.
As shown in Figure 53, the Chopan points in the device’s app are under the “ChopanN”, “ChopanDeviceName
” node under the service folder (and must remain there). One way to link the source Sedona components to them is using the Nav tree, and right-click
“Link Mark” and “Link From” menu options.
Source Sedona components are linked to the Chopan points, using “Link Mark” and “Link From” methods.
Figure 54 shows the Link dialog for the “Temp” (temperature) source component to the “Temp_in” writable Chopan point, where the “In” slot is used.
After making source links to all the writable Chopan points, the app must be saved.
Figure 55 shows the right-click Save command invoked on the App node. The Workbench Sox session to the hibernating device is now closed, and the target Chopan points are checked in the JACE station.
Chopan target points in the station are now receiving updates from the hibernating device, via CHoPAN, as shown in Figure 56.
Control points shown in Figure 56 still need point facets assigned, and whatever linkage into station control logic, and/or bindings to Px page(s).
Copyright © 2000-2014 Tridium Inc. All rights reserved.