Comprehensive User/Group Security Restrict or allow access to myriad of points based on individual or group credentials

Transcription

1 DATASHEET Aspect Nexus 2 DESCRIPTION Aspect Nexus 2 site controller is an embedded building automation network controller designed to provide flexible site control applications to medium to large scale building automation systems. It can be used to communicate with serial networks populated with field bus devices communicating on protocols such as BACnet MS/TP, AAM PUP, and Modbus. Aspect Nexus 2 provides all the same powerful features as any Aspect enabled product; alarming, trending, extensive custom programming and many of the features that have made the framework a recognised award-winning platform. In addition, it integrates with popular Internet programs to allow end-users more freedom. With Aspect, your PC and smart devices can integrate with your building easily and efficiently. Also included are features such as the ability to push and pull data with popular networked databases, and to serve graphical user interface pages - eliminating the need for a dedicated operator workstation or expensive add-on software to view a system. Nexus 2 FEATURES & OVERVIEW Centralised System Management Provides the ability to manage an entire network of Aspect products by acting as a centralised server providing web, data, and other building information from one single entry point Integrated MySQL Database Server Used to store all historic data as well as provide third-party interfaces with data from the building automation system without the need for special add-on protocol drivers Receive Important Building Information Aspect uses web technologies, including , Twitter, and common internet protocols, to provide the end-user more freedom HTML5 Integration The HTML5 interface is created automatically with no additional effort required and does not require proprietary software plug-ins. This intuitive HTML5 interface automatically scales to the PCs, smart phones, tablets, and other mobile devices you use every day Comprehensive User/Group Security Restrict or allow access to myriad of points based on individual or group credentials Aspect Supervisory Control Engine Supervisory-based control functions including but not limited to energy management routines, custom sequencing, alarm and event annunciation, historical alarming and trending, and master control scheduling Schedule & Calendar Implementation Interact with icalendar format tools such as Microsoft Outlook, Apple Calendar Google Calendar and other popular programs. (maximum of 10 schedules) Secure System Platform Utilising a secure and reliable Linux OS foundation Seamless integration with Unitron sites Integrates with existing Unitron installations via IP connection to UC32.netK Comms Controllers HARDWARE SPECIFICATIONS Intel CPU E GHz 4 GB RAM 64 GB SSD COMMUNICATIONS 10/100/1000 MB Ethernet RJ-45 Connection 2 x RS485 Ports 1 OPERATING SYSTEM Embedded Linux OS Aspect Runtime Engine

2 SYSTEM ARCHITECTURE Aspect - Network BACnet IP BACnet MSTP TCP/IP Modbus RTU a b Cylon BACnet Router CBR HVAC Controller CBM24 h i Unitary Controller CBT12iVAV Unitary Controller CBT14 s t Aspect-Studio Aspect-Enterprise c d e Boiler Controller CBM16 HVAC Controller CBM12 Lighting Controller CBM08 k m Aspect-Matrix MAX BACnet MS/TP BACnet IP Cylon BACnet Router CBR/MOD u v w BACnet Touchscreen Supervisor BACnet IP AHU BACnet IP Lighting Controller f g Unitary Controller CBT12 Aspect-NEXUS 2 BACnet MS/TP Modbus RTU BACnet IP Modbus TCP o p q r Active Energy Manager Remote Web Browser Internet Cylon Engineering Center X Y Z Communications Controller UC32.netK HVAC Controller UC32.24 Fancoil Controller UCU10FC Page 2 of 12

3 PRODUCT OPTIONS For each Fieldbus, you must choose the following: 1 Platform see CHOICE I : Nexus 2 Platforms on page 4 ASP-NEX2-DPO ASP-NEX2-DPX 2 No. of 3 rd -Party BACnet Licences see CHOICE II : 3rd Party BACnet on page 5 Quantity (0-23) : 3 Modbus RTU licence see CHOICE III : Modbus RTU on page 6 None ASP-MODR-NEX-DPO ASP-MODR-NEX-DPX 4 No. of Modbus TCP licences see CHOICE IV : Modbus TCP on page 7 Quantity (0-8) : 5 No. of Aspect licences see CHOICE V : Additional Aspect Devices on page 8 Quantity (0-2) : These choices can be filled in on form and sent to Cylon by with a purchase order. If you wish to upgrade the licencing on an existing Aspect Nexus 2, fill in choices 2,3, 4 and 5 on form Page 3 of 12

4 CHOICE I : Nexus 2 Platforms Part Number Description ASP-NEX2-DPO Nexus 2 DPO server supporting 5 Aspect Devices and 64 BACnet devices connected directly or indirectly ASP-NEX2-DPX Nexus 2 DPX server supporting 10 Aspect Devices and 128 BACnet devices connected directly or indirectly Supported BACnet/Modbus device limits Part Number Available RS485 Ports RS485 device limit IP device limit Total supported devices Port 1 Port 2 ASP-NEX2-DPO ASP-NEX2-DPX Note: The recommended maximum number of points in the map of a single Nexus 2 server is 10,000 Supported Aspect device limits Part Number Aspect device limit ASP-NEX2-DPO 5 ASP-NEX2-DPX 10 Without specific licencing, 4 3rd-party BACnet devices are supported : all other connected BACnet devices must be Cylon BACnet devices. No Modbus devices can be connected. If you need to connect to 3rd-Party BACnet devices (MS/TP or IP), see CHOICE II : 3rd Party BACnet on page 5 If you need to connect to Modbus RTU devices, see CHOICE III : Modbus RTU on page 6 If you need to connect to Modbus TCP devices, see CHOICE IV : Modbus TCP on page 7 If you need to connect to additional Aspect devices, see CHOICE V : Additional Aspect Devices on page 8 Page 4 of 12

5 CHOICE II : 3rd Party BACnet BAC-ENB licences provide flexibility. When an ASP-BAC-ENB-4 licence is applied, 4 of the device s BACnet total device count (MS/TP + IP) can change between 3rd-party or Cylon BACnet devices. Note: A licence is never required to connect Cylon BACnet devices, and BAC-ENB licences do not increase the total number of devices that can be connected (as shown in the table in Supported BACnet/Modbus device limits on page 4). [ A ] How many non-cylon BACnet MS/TP devices will be connected? [ B ] How many non-cylon BACnet IP devices will be connected? ASP-NEX2-DPO Total number of 3rd party BACnet devices (A + B) Number of ASP-BAC-ENB-4 licences required 1 to to to to ASP-NEX2-DPX Total number of 3rd party BACnet devices (A + B) Number of ASP-BAC-ENB-4 licences required 1 to to to to Page 5 of 12

6 CHOICE III : Modbus RTU A MODR licence is required if Modbus RTU is to be used on either of the Nexus 2 models. This allows either or both of the RS485 ports to communicate with Modbus devices, up to the RS485 device limit shown in the table in Supported BACnet/Modbus device limits on page 4). Note: A single RS485 port can communicate with either BACnet MSTP devices or Modbus RTU devices, but not both. ASP-MODR-NEX-DPO Enables Modbus RTU on ASP-NEX2-DPO ASP-MODR-NEX-DPX Enables Modbus RTU on ASP-NEX2-DPX Page 6 of 12

7 CHOICE IV : Modbus TCP MODT-ENB licences are required to allow either of the Nexus 2 models to communicate with a number of Modbus TCP devices: ASP-NEX2-DPO Number of Modbus TCP devices Number of ASP-MODT-ENB-8 licences required 1 to to to to 32 4 ASP-NEX2-DPX Number of Modbus TCP devices Number of ASP-MODT-ENB-8 licences required 1 to to to to to to to to 64 8 Page 7 of 12

8 CHOICE V : Additional Aspect Devices ASP-NEX-NET-5 licences are required to allow the Nexus 2 DPX server to communicate with additional Aspect devices. The DPO server has a maximum limit of 5 Aspect devices and does not require a licence. ASP-NEX2-DPO Number of Aspect devices Number of ASP-NEX-NET-5 licences required 1 to 5 0 ASP-NEX2-DPX Number of Aspect devices Number of ASP-NEX-NET-5 licences required 1 to to to to 20 2 Page 8 of 12

9 Device Count Examples Depending on the applied licence options, products in Cylon s Aspect range can communicate with the following types of devices: Aspect -Network devices BACnet devices directly connected to a serial port on the device either Cylon or 3 rd party BACnet devices connected over IP either Cylon or 3 rd party Modbus devices Each product option specifies a different maximum count for each of these types, and how those counts are used up is illustrated in the following diagrams. Legend Aspect Satellite Cylon BACnet Controller (CBM/CBT) Cylon BACnet Router 3rd-party BACnet device Aspect Supervisor (designated emap Master device) Aspect -Network BACnet IP Unitron Protocol BACnet MSTP Scenario 1 In this use case, a Matrix MAX is supervising a fieldbus of CBM/CBT controllers, directly connected to its serial port. The Supervisor project resides in the Matrix MAX, which acts as the emap Master device (Aspect Supervisor). It is not connected to any other Aspect -Network devices, so the Aspect Satellite count used is 0 Device Type Device Count Aspect Satellite 0 Local Cylon BACnet 5 Remote Cylon BACnet 0 Local 3 rd -party BACnet 0 Remote 3 rd -party BACnet 0 Modbus RTU 0 Modbus TCP 0 Page 9 of 12

10 Scenario 2 In this use case, a Matrix MAX is supervising a fieldbus of CBM/CBT controllers, directly connected to its serial port, and also a remote fieldbus connected over IP though a Cylon BACnet Router The Supervisor project resides in the Matrix MAX, which acts as the emap Master device (Aspect Supervisor). It is not connected to any other Aspect -Network devices, so the Aspect Satellite count used is 0 Device Type Device Count Aspect Satellite 0 Local Cylon BACnet 5 Remote Cylon BACnet 5 Local 3 rd -party BACnet 0 Remote 3 rd -party BACnet 0 Modbus RTU 0 Modbus TCP 0 Scenario 3 In this use case, a Nexus 2 is supervising two fieldbusses of CBM/CBT controllers, directly connected to its serial ports, and also a remote fieldbus connected over IP though a Matrix MAX The Supervisor project resides in the Nexus, which acts as the emap Master device (Aspect Supervisor). The Matrix MAX supervises its local fieldbus, so that the Nexus 2 does not use any remote Cylon BACnet device counts. Device Type Device Count Aspect Satellite 1 Local Cylon BACnet 4 Remote Cylon BACnet 0 Local 3 rd -party BACnet 0 Remote 3 rd -party BACnet 0 Modbus RTU 0 Modbus TCP 0 Page 10 of 12

11 Scenario 4 In this use case, an Enterprise installation is supervising 3 fieldbusses of CBM/CBT controllers, each connected to an emap device. The Supervisor project resides in the Nexus, which acts as the emap Master device (Aspect Supervisor). The Nexus 2 and Matrix MAXs supervise their local fieldbusses, so that the Nexus 2 does not use any remote Cylon BACnet device counts. Device Type Device Count Aspect Satellite 3 Local Cylon BACnet 0 Remote Cylon BACnet 0 Local 3 rd -party BACnet 0 Remote 3 rd -party BACnet 0 Modbus RTU 0 Modbus TCP 0 Scenario 5 In this use case, an Enterprise installation with ASP-BAC-ENB-4 is supervising 3 fieldbusses of CBM/CBT controllers, each connected to an Aspect Satellite, and 3 BACnet IP devices. The Supervisor project resides in the Nexus, which acts as the emap Master device (Aspect Supervisor). The Nexus 2 and Matrix MAXs supervise their local fieldbusses, so that the Nexus 2 does not use any remote Cylon BACnet device counts. Device Type Device Count Aspect Satellite 3 Local Cylon BACnet 0 Remote Cylon BACnet 0 Local 3 rd -party BACnet 0 Remote 3 rd -party BACnet 3 Modbus RTU 0 Modbus TCP 0 Page 11 of 12

12 SPECIFICATIONS Physical Form Factor Dimensions Weight IP Rating Operation Processor Memory Storage Power Input Note: Fanless design Optimized for wall and DIN-rail mounting Designed for industrial conditions 217 mm wide x 206 mm deep x 73 mm high (8.5 in x 8.1 in x 2.9 in) 3.4 Kg IP50 Intel Atom E GHz 2 cores 4G (8x 256Mx16 DDR3L) 1333MHz 64 GB SSD Nominal input 24V AC / DC ( V), 4.0 Amps* Also accepts standard Dell notebook AC adapter, 65 W, 7.4 mm plug* Nexus 2 requires a dedicated SELV 24 V 60VA AC / DC supply* (Class II supply) or a dedicated Dell SELV 19.5 V 65 W PSU*. The recommended supply is a 24 V 60 VA transformer. When using a higher VA transformer, care must be taken to ensure that the voltage stays within specification. * Warning: Earthing or Grounding of any of the terminals connected to the SELV power supply will cause serious damage to the power supply rectifier and will invalidate the product Warranty. Never Earth or Ground any of the terminals connected to this power supply. Never use this power supply to power CB, NB, or SBC control devices, or any other equipment, because it is possible that the other equipment may be connected to Earth or Ground. Performance Total Points 10,000 Background Points 4,000 Alarmable Points 1,000 Point Containers (controllers) 500 Trend Tables 1,000 Unique Graphics 200 Unitron Fieldbusses 4 Environmental Operating temperature 0 C to 50 C Relative humidity 5% to 95% non-condensing Communications Network Serial Interfaces Gigabit Ethernet (RJ-45) 2 x RS-485 Hardware Rating Safety UL /2 CAN/CSA-C22.2 No /2 IEC/EN /2 IEC/EN EN EMC (Emissions class: B) US CFR Title 47, FCC Part 2, 15 ANSI C Canadian ICES-3 (B)/NMB-3 (B), Issue 5 EN 55032/CISPR 32 EN 55024/CISPR 24 IEC/EN /3 IEC/EN EN55011 ROHS (Directive 2011/65/EU) EN This document must not be copied in part or in whole for any purpose other than that which it was intended, and does not constitute any warranty, expressed or implied. Every effort has been made to ensure that all information was correct at the time of publication. Should a variation in information or data between the English version and translated versions of this document occur, the English variant takes precedence. AAM reserves the right to alter the specifications, performance, capabilities, and presentation of this product at any time. All trademarks, trade names, service marks, or logos contained herein are the property of their respective owners and are only used to describe the product(s) being listed in this document. Every effort has been made to properly capitalise, punctuate, and identify and attribute all required trademarks with the use of the appropriate or wherever practical and possible. American Auto-Matrix, Smart Building Solutions, Solution Integrator, the Rocket-A, Aspect, Auto-Flow, Aspect Facility, Aspect Enterprise, Aspect Studio, Aspect Nexus, Aspect Matrix MAX, and vstat are either registered trademarks or trademarks of American Auto-Matrix, a Cylon Energy Inc company. Cylon is a registered trademark of Cylon Controls Ltd. Page 12 of 12