Technical data

Glossary • 345
WAGO-I/O-SYSTEM 750
BACnet/IP Controller
N
Natives BACnet
"Native" BACnet objects are those objects that are recognized by BACnet/IP
controllers during run-up, without a configuration being loaded. These ob-
jects are created automatically for the plugged binary and analog input and
output modules. The configuration for the native objects is loaded from the
firmware and an internal database.
Besides the BACnet/IP controller, no additional hardware is necessary for
integrating BACnet into a network. All requisite, native BACnet objects,
properties and services are directly available. This standard behavior for a
BACnet/IP controller can be deactivated in the BACnet Configurator, or in
the I/O Configuration using the option "Disable native BACnet".
A gateway is required for communication with non-native BACnet de-
vices/networks.
Complex modules do not have any direct equivalent as BACnet objects. Ob-
jects for these modules must be created and configured using the WAGO I/O
PRO CAA I/O Configurator.
O
Object
BACnet communication takes place using standardized objects (DIN EN
16484-5). These objects are tailored specifically to the HVAC sector for
building automation services. Both simple field devices as well as complex
automation control systems can be modeled in the object presentation. Ob-
jects may represent both physical inputs and outputs and virtual objects,
such as counting values.
Objects possess certain properties, whose values can be read and/or written
using services.
All of the objects supported by a device are also described in the PICS data
from the specific manufacturer.
Open MODBUS/TCP Specification
Specification, which establishes the specific structure of a MODBUS/TCP
data packet. This is dependent upon the selected function code or upon the
selected function (import or export bit or register).