BACnet Client-Server Architecture

BACnet is based on a "client-server" model of the world. BACnet messages are called "service requests." A client machine sends a service request to a server machine that then performs the service and reports the result to the client. BACnet currently defines 35 message types that are divided into 5 groups or classes.

For example, one class contains messages for accessing and manipulating the properties of the objects described above. A common one is the "ReadProperty" service request. This message causes the server machine to locate the requested property of the requested object and send its value back to the client.

Other classes of services deal with alarms and events; file uploading and downloading; managing the operation of remote devices; and virtual terminal functions.

Please notice that ICONICS is compliant with ANSI ASHRAE Standard 135-2004.

NOTE: Types which are part of the specification above are supported by ICONICS as well as other BACnet standards. ICONICS supports read/write property for all BACnet objects, but only the objects defined in ANSI ASHRAE Standard 135-2004 would be correctly shown in ICONICS clients (e.g. GraphWorX64).