The following topics are not in the previous Chopan point “walk-through”, but are mentioned briefly below. For more details on Chopan topics, refer to the Sedona Framework Chopan Usage document.
When the Chopan Server of the SedonaJen6lpNetwork is enabled, this automatically results in the creation of a station user named “CHoPAN”. This is necessary because CHoPAN is an unathenticated protocol, where CHoPAN servers do not authenticate or prevent and reads or writes to local components. Niagara stations allow reads of any appropriate component, but writes to station components are checked for authorization (as part of this CHoPAN user scheme). Therefore, any incoming CHoPAN requests that result in station database modification are checked against the permissions assigned to the CHoPAN user. In other words, the Niagara component being written must be assigned to a category for which the CHoPAN user has write privileges.
Any Sedona Framework Jennic-based device can be configured in its app to support “service pin notifications”, using components
from the chopan
kit. The app must contain the “ChopanS” (ChopanService) and “ChopanN” (ChopanNetwork) components, with others optional. See
the “Service Pin support” section in the Sedona Framework Chopan Usage document.
Chopan points have a status code slot showing a numerical value that reflects the response of the latest request. Codes also have a descriptive “Name” that appear in the Chopan Point Manager view of a Chopan server device (under the SedonaJen6lpDevice’s Chopan Virtual gateway), which is useful for troubleshooting purposes. Refer to the “Chopan Diagnostics” section in the Sedona Framework Chopan Usage document for status code names, numerical values, and their meanings.
Copyright © 2000-2014 Tridium Inc. All rights reserved.