Difference between revisions of "BACnet"
| Line 223: | Line 223: | ||
*requestedshedlevel (as Real number) | *requestedshedlevel (as Real number) | ||
|- | |- | ||
| − | |||
| − | |||
Revision as of 14:45, 28 February 2014
BACnet is a protocol developed by ASHRAE for building automation and control networking, specifically designed to meet the communication needs of building automation and control systems for applications such as heating, ventilating, air-conditioning control, lighting control, access control and fire detection systems. HSYCO conforms to a functional subset of the BACnet protocol, as defined in ANSI/ASHRAE Standard 135-2010. HSYCO can only be configured as a BACnet/IP client device. BACnet support is implemented as an I/O Server with a data point representation that you can use in the EVENTS language and Java to read and write BACnet’s objects and properties, and to manage asynchronous notification services.
Contents
Communication
HSYCO supports BACnet/IP, where the BACnet messaging protocol is transported over standard IP networks, over local networks. Routing of BACnet traffic is currently not supported by the HSYCO BACnet/IP I/O Server. You should configure only one I/O Server for each LAN used for BACnet traffic. Support for multiple BACnet/IP local networks is achieved by configuring one I/O Server for each network.
HSYCO Configuration
Options
| ID | Default | Values | Description |
|---|---|---|---|
| deviceid | 590001 | 0 to 4194303 | BACnet device identifier assigned to the HSYCO BACnet client |
| disableverbosedump | false | true | when verbose log is enabled, don’t write IP packets dump to the log files |
| false | when verbose log is enabled, all BACnet IP packets are written to the log files | ||
| eventslog | false | true | if the general eventsLog option is also true in System Settings, BACnet events for this gateway are written in the log files |
| false | BACnet events for this gateway are not written in the log files, even if the eventsLog option is true in System Settings | ||
| gui | false | true | enables support of the (bacnetutility) Web GUI object |
| false | disables support for the Web GUI |
BACnet Integration
The BACnet driver is implemented as a bidirectional I/O Server. All interaction is based on EVENTS’ IO events and actions. HSYCO conforms to a functional subset of the BACnet protocol.
The following services are supported:
- Alarm and Event Services:
- ConfirmedCOVNotification
- UnconfirmedCOVNotification
- SubscribeCOV
- Object Access Services:
- ReadProperty
- WriteProperty
- Remote Device Management Services:
- Who-Is
- I-Am
The BACnet I/O Server supports all standard object types and properties for the ReadProperty service, while object’s properties that could be written using the WriteProperty service are listed in the following table.
Following HSYCO’s naming convention for BACnet, all object types and properties are written in lowercase letters with no spaces or underscore characters. For example, Present_Value is written as “presentvalue”, and the binary input object type is written as “binaryinput”.
Objects Type Supported
| Object Type | Writable Properties |
|---|---|
| accumulator |
|
| analoginput |
|
| analogoutput |
|
| analogvalue |
|
| averaging |
|
| binaryinput |
|
| binaryoutput |
|
| binaryvalue |
|
| command |
|
| lifesafetypoint |
|
| lifesafetyzone |
|
| loop |
|
| multistateinput |
|
| multistateoutput |
|
| multistatevalue |
|
| program |
|
| pulseconverter |
|
| accessdoor |
|
| loadcontrol |
|
