Currently CHoPAN client points can be either Boolean or numeric, with read-only and writable versions of each. Points in the network are updated in a “round-robin” fashion by walking through the ChopanNetwork’s child devices, and through each device’s child points.
Read-only points (ChoBoolPt and ChoFltPt) are updated by issuing a CHoPAN GET request for their configured URI, and updating the out slot with the response value.
Writable points (ChoBoolWr and ChoFltwr) are updated by issuing a CHoPAN PUT request to their configured URI, with the value contained in their in slot.
Each point has a Status Code slot that reflects the response status of the latest request. Status codes that may appear are shown below. The friendly
text “Name” appears in the Sedona Property Sheet view for any Chopan point. In the Chopan Point Manager, the hex numerical 0xNN
status codes display (see Figure 14). Table 1 provides a listing of possible codes.
Table 1. CHoPAN Status Codes
Name | CHoPAN Code | HTTP Code | Description |
---|---|---|---|
OK | 0x40 (64) | 200 | Everything is fine—successful read or write. |
- - | 0x00 (0) | n/a | Point has not been read or written yet. |
Decoding Error | 0x01 (1) | n/a | There is an error in the decoding value from the sever. |
CHoPAN Timeout | 0x02 (2) | n/a | No response was received from the server. |
Bad Request | 0x80 (128) | 400 | The server rejected the request—see station output for details. |
Unauthorized | 0x81 (129) | 401 | The CHoPAN User in the station does not have permissions to modify this component/slot. |
Not Found | 0x84 (132) | 404 | The specified URI does not map to a valid component/slot reference. |
Server Error | 0xA0 (160) | 500 | The server experienced an internal error—see station output (if JACE server) or serial port diags (if Jennic-based device server) for details. |
Copyright © 2000-2014 Tridium Inc. All rights reserved.