Any non-hibernating, networked, Jennic-based device can operate as a CHoPAN server. This lets its app respond to read and write CHoPAN client requests from the JACE, and/or from other networked Jennic-based devices.
Server functionality for a device includes support for Sedona proxy points, to allow the most efficient tuning policy “Comm
Type” (Chopan)—even if not otherwise making Chopan point requests to it.
Add chopan kit to Jennic-based device
With the JACE station open in NiagaraAX Workbench:
In the Nav tree, expand the SedonaJen6lpNetwork to reveal the child SedonaJen6lpDevices.
Right-click a device, and select .
An Authentication dialog appears for the Sox connection.
Enter the Username and password of a User in the Sedona app’s UserService (for example: the frozen admin
user), and click . A Sox connection is made tunneling through the running station.
The view space shows the Sedona device’s Nav Container View, with Tools and
App nodes.
If the connection fails, it may be because your Workbench host does not have the necessary manifest files for all the kits
installed in the Sedona device. In the error, examine any “Details” link to see if missing manifests are named. For related
details, refer to Sedona Manifest Manager - Engineering Notes. Another possible issue might be a user mismatch between the app’s users service and your station login. As a workaround,
in the JACE station’s SoxTunnel service (Config > Services > SoxTunnel), set the “Authenticate with User Service” property
to
false
and .
The tunneled Sox connection also appears in the Nav tree root of the JACE (on parity with the station). You can also work from the Nav tree, expanding and right-clicking, etc. as needed.
Add the chopan
kit to the device (if not already present) using the Kit Manager.
To do this, expand the tunneled Sox connection to select
Tools and double-click on the
Kit Manager to access the Kit Manager wizard. If the
chopan
kit is already present (and up-to-date), skip ahead to another procedure, such as Add Chopan server components to App.
Otherwise, install/upgrade the chopan
kit and select when the wizard completes. This drops the Sox connection, and the connection becomes “ghosted” in the Workbench Nav tree.
For complete details, see “About the Kit Manager” in the Sedona Framework Sox Tools Guide.
In the Nav tree, double-click the ghosted Sox connection for the device, to reopen it in Workbench.
Add Chopan server components to App
If the Sedona Framework device has the chopan
kit installed, you can configure it as a Chopan server. See the previous procedure Add chopan kit to Jennic-based device.
Using NiagaraAX Workbench, open a tunneled Sox connection to the device.
From the device’s Nav Container View, double-click the App node, for its Sedona Property Sheet view, and expand its
service
container (folder).
Open the Sedona Palette in the Workbench sidebar, and choose the
chopan
palette.
From the chopan
palette:
Add the ChopanService to the
service
folder of the App (if the ChopanService is not already present in the App). By default, the component’s name is trimmed to
“ChopanS”.
Add the ChopanServlet under the
ChopanService (again, if not already present). By default, the component’s name is trimmed to “ChoSvlt”.
This component hierarchy (App > service > ChopanS > ChoSvlt) is the recommended convention.
If using default Chopan ports (1810), no further configuration is needed.
If specifying a non-default Port in the property sheet of the ChopanService, remember a matching port number must be used later when configuring any client-side ChopanDevice that represents this device.
Save the App (right-click the App node and select -> ).
The device will now support Chopan client requests from remote devices.
Sometimes, you may need to enable a device to make its own Chopan client requests, say if requesting data directly from another Jennic-based device. If so, see Add core Chopan client components to App.
Copyright © 2000-2014 Tridium Inc. All rights reserved.