Support for service pin requires the JACE station has a working SedonaJen6lpNetwork, with communicating SedonaJen6lpDevice child components. Discovery and addition of devices is the typical method. For details, see “Adding discovered SedonaJen6lpDevices” in the NiagaraAX Sedona Networks Guide.
The remainder of setup for any Jennic-based device to support service pin messaging is as follows:
The device needs the chopan kit installed, with its app configured to support Chopan client operation. See Add chopan kit to Jennic-based device and Add core Chopan client components to App.
No further configuration of the ChopanN (ChopanNetwork) component in the app is needed.
If supported by components in kits available from the device’s vendor, where the device has some local physical input (say,
a certain pushbutton switch) that can physically initiate a message, add that component to the device’s app, along with a
SrvcPinTrig component from the
chopan
palette (from Sedona Palette sidebar of Workbench).
Such a configuration is shown below, where the two components are in a folder named “SvcPin”.
Link the bool out slot of the initiating component (in this case, Button) to the “in” slot of the SrvcPinTrig component, as shown in Figure 18. A transition on the “in” slot of SrvcPinTrig causes the corresponding row for that device in the station’s Sedona Device Manager (if being viewed) to become highlighted.
Note that another “programmatic” approach is possible, by invoking the “Service Pin” action on the ChopanNetwork component in the device’s app.
Figure 19 shows this action being invoked from the property sheet of a device’s App. This method does not require the SrvcPinTrig component (from the chopan
palette) to be used in the app.
Copyright © 2000-2014 Tridium Inc. All rights reserved.