NXAC-120 Area Controller

Transcription

1 Date: 5/25/2017 Vendor Name: Hubbell Lighting, Inc. Product Name: NXAC-120 Area Controller Product Model Number: NXAC-120 Area Controller BACnet/IP Application Software Version: Firmware Revision: BACnet Protocol Revision: (Ver. 1, Rev. 12) Product Description: The NXAC-120 Area Controller acts as a BACnet server and virtual BACnet router between BACnet clients and a NX Virtual BACnet Solution. BACnet Devices served by the NXAC-120 Area Controller are Zones. Zones are virtual BACnet devices that represent a physical space within the building such as a conference room, open office, or corridor. Each Zone will have a single state of occupancy and some quantity of Relays and or Dimmers. BACnet Standardized Device Profile (Annex L): o BACnet Operator Workstation (B-OWS) o BACnet Advanced Operator Workstation (B-AWS) o BACnet Operator Display (B-OD) o BACnet Building Controller (B-BC) o BACnet Advanced Application Controller (B-AAC) þ BACnet Application Specific Controller (B-ASC) o BACnet Smart Sensor (B-SS) o BACnet Smart Actuator (B-SA) List all BACnet Interoperability Building Blocks Supported (Annex K): K.1.2 BIBB Data Sharing ReadProperty-B (DS-RP-B) K.1.4 BIBB Data Sharing ReadPropertyMultiple-B (DS-RPM-B) K.1.8 BIBB Data Sharing WriteProperty-B (DS-WP-B) K.1.10 BIBB Data Sharing WritePropertyMultiple-B (DS-WPM-B) K.5.2 BIBB Device Management DynamicDeviceBinding-B (DM-DDB-B) K.5.4 BIBB Device Management DynamicObjectBinding-B (DM-DOB-B) K.5.6 BIBB Device Management DeviceCommunicationControl-B (DM-DCC-B) Segmentation Capability: o Able to transmit segmented messages Window Size NA o Able to receive segmented messages Window Size NA Standard Object Types Supported: Non-standard application services are not supported. An object type is supported if it may be present in the device. For each standard Object Type supported provide the following data: Device 3) List of the optional properties supported: Description, Location Analog Input 1

2 Analog Output Analog Value Binary Input Binary Output Binary Value Multi-state Input Multi-state Output Multi-state Value 2

3 Data Link Layer Options: þ BACnet IP, (Annex J) o BACnet IP, (Annex J), Foreign Device o ISO , Ethernet (Clause 7) o ATA 878.1, 2.5 Mb. ARCNET (Clause 8) o ATA 878.1, EIA-485 ARCNET (Clause 8), baud rate(s) o MS/TP master (Clause 9), baud rate(s): o MS/TP slave (Clause 9), baud rate(s): o Point-To-Point, EIA 232 (Clause 10), baud rate(s): o Point-To-Point, modem, (Clause 10), baud rate(s): o LonTalk, (Clause 11), medium: o BACnet/ZigBee (ANNEX O) o Other: Device Address Binding: Is static device binding supported? (This is currently necessary for two-way communication with MS/TP slaves and certain other devices.) o Yes þ No Networking Options: þ Router, Clause 6 - List all routing configurations, e.g., ARCNET-Ethernet, Ethernet-MS/TP, etc. þ Annex H.2, Multiple Virtual BACnet Devices in a Single Physical Device o BACnet/IP Broadcast Management Device (BBMD) Does the BBMD support registrations by Foreign Devices? o Yes o No Does the BBMD support network address translation? o Yes o No Character Sets Supported: Indicating support for multiple character sets does not imply that they can all be supported simultaneously. þ ISO (UTF-8) o IBM Ô /Microsoft Ô DBCS o ISO o ISO (UCS-2) o ISO (UCS-4) o JIS X 0208 Hubbell Specific Object Information: Zone limitations The NX addressing in the Area Controller supports up to 128 areas. Each area can contain up to 128 addressable zones. Each zone can contain up to 16 addressable groups.. A zone can contain and mix between room controller devices and non-room controller devices. A zone is a direct binding to a gateway virtual device and all content of a zone becomes dynamic as defined in the export table. The number of available zones and their architecture is managed by the Device Manager GUI. Zone Object Lists The object list of a Zone can be sourced directly or indirectly from the following controls and devices: Relay/Dimming panels, various capacity, up to 100+ inputs and 100+ outputs Smart Port modules, 4 smart ports, up to 32 switches or 4 sensors each 3

4 Dry Contact I/O modules, 6 inputs, 6 outputs each Wired Room Controllers, 4 smart ports, 2 switching, 2 dimming each Wireless Room Controllers (same as wired room controller) Zone Object Enumeration Summary Object enumeration for a NX Zone: BV101 - BV116 Group 1 16 On/Off (read/write) AV201 AV216 Group 1-16 Level (write only) BV301 BV316 Occupancy State (read only) MV401 Preset 1-16 State (read/write), exports as one (1) Multi State Value object. MV501 Demand Response/Load Shed (read/write) * AV601-AV616 Daylight Foot Candles (read only) * AV701-AV716 Watts (read only) * AV801-AV816 Voltage (read only) * BO1001 BO10XX Relay 1 - XX (read/write). Count is limited by configuration. AO AO20XX Dimmer 1 - XX (read/write). Count is limited by configuration * planed for future release, contact factory Relays objects enumeration The number of relay objects can be stated as 0 XX, where XX is limited only by the configuration. BO1001 Relay Write/read property, read/write multiple BO1002 Relay Write/read property, read/write multiple Dimmer objects enumeration The number of dimmer objects can be stated as 0 XX, where XX is limited only by the configuration. AO2001 Dimmer Read Property, Read Multiple AO2002 Dimmer Read Property, Read Multiple Group On/Off objects enumeration BV101 Group Write/read property, read/write multiple BV102 Group Write/read property, read/write multiple Group Level objects enumeration AV201 Group Write property, write multiple AV202 Group Write property, write multiple 4

5 Presets objects enumeration MV401 Preset 1 Read/write property, read/write multiple MV401 Preset 2 Read/write property, read/write multiple Occupancy state objects enumeration BV301 Occupancy Read property, read multiple BV302 Occupancy Read property, read multiple 5