AERCO XPC GATEWAY Communications - Manual (Page 95)

GF-122 AERCO XPC GATEWAY
95
downloaded to the XPC module. The communications protocol used by the Device Port is configured at
the factory through software and is dictated by the specified equipment. BACnet objects are spawned
within the device as a result of downloading graphical control programs.
BACnet Standardize Device Profile (Annex L): B-AAC
List of all BACnet Interoperability Building Blocks Supported (Annex K):
DS-RP-A* AE-N-I-B SCHED-I-B T-VMT-I-B DM-DDB-A*
DS-RP-B AE-ACK-B SCHED-E-B T-ATR-B DM-DDB-B
DS-RPM-A* AE-ASUM-B DM-DOB-A*
DS-RPM-B AE-INFO-B DM-DOB-B
DS-WP-A* AE-ESUM-B DM-DCC-B
DS-WP-B DM-PT-A*
DS-WPM-A* DM-PT-B
DS-WPM-B DM-TS-B
DS–COV-A* DM-UTC-B
DS–COV-B DM-RD-B
DS–COVU-
A* DM-LM-B
DS–COVU-
B DM-BR-B
NM-CE-A*
* Dynamic Binding is not supported when MS/TP is configured in slave mode.
Segmentation Capability:
Able to transmit segmented messages: (NO) Window Size:
Able to receive segmented messages: (NO) Window Size:
Standard Object Types Supported:
On a separate page, please list each standard Object Type supported (i.e., an object of this type may be
present in the product). For each standard Object Type supported provide the following data:
• Whether objects of this type are dynamically creatable using BACnet’s CreateObject service
• Whether objects of this type are dynamically deletable using BACnet’s CreateObject service
• List of all optional properties supported
• List of all properties that are writable where not otherwise required by this standard
• List of proprietary properties and for each its property identifier, datatype, and meaning
• List of any property range restrictions