Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
en:automation:02-glossary:bacnet-hidden [2020/01/13 12:10] mkudlacek |
en:automation:02-glossary:bacnet-hidden [2020/01/13 12:12] (current) mkudlacek |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| Modbus users are also probably used to communicate through functions for reading or writing data into registers and coils. BACnet designates these functions as services and defines over 30 of them. However, there are only few services each device must support (and which you will encounter most frequently). These are services for looking up devices in the network (the Who-is service), describing its objects (the Who-has service) and read/write functions for editing property values (Read-property + Write-property). | Modbus users are also probably used to communicate through functions for reading or writing data into registers and coils. BACnet designates these functions as services and defines over 30 of them. However, there are only few services each device must support (and which you will encounter most frequently). These are services for looking up devices in the network (the Who-is service), describing its objects (the Who-has service) and read/write functions for editing property values (Read-property + Write-property). | ||
| - | However, it is worth noting that most of BACnet definitions are well-hidden. This allows the BACnet users to focus on the most important task - to start up the device. BACnet devices can be easily added or swapped, while the protocol guarantees interoperability of devices from various vendors. | + | However, it is worth noting that most of BACnet definitions are well-hidden. This allows the BACnet users to focus on the most important task - to integrate the device into the network. BACnet devices can be easily added or swapped, while the protocol guarantees interoperability of devices from various vendors. |
