Latin America, and the UK. Johnson Controls N2 Master Driver Product Update. Development Status

Transcription

1 Building Technologies CPS Products Product Update Restricted! Product Line: Other BAS Product Manager: John Nicolson Distribution: USA, Canada, Asia Pacific, Latin America, and the UK T Date: July Johnson Controls N2 Master Driver Product Update Development Status The Johnson Controls N2 Master Driver has been completed for some time now with many successful installations. Custom applications must be created. The recent change to this driver includes the following new enhancements: The Johnson Controls N2 Master Driver can be loaded onto the TC Modular or TC-36 hardware platform. With Firmware Revision 3.4 and later, the Johnson Controls N2 Master Driver is fully compatible with the BACnet Field Panel Web Server (FPWeb). You can now incorporate the benefits of the FPWeb user interface and Launch Pad in combination with popular integration drivers. This driver is also compatible with FIN Builder and FINlite-based graphics, which are licensed options. Integrated points are fully available in FIN Builder graphics, plus the controller database is supported by the FPWeb configuration tools. Desigo CC Revision 2.1 Editors are fully compatible with the Johnson Controls N2 Master Driver License Revision 3.4 and later. Platform Type TC Modular or TC-36 Configuration The Johnson Controls N2 Master Driver provides communication between the TALON Automation Level Network (ALN) and the Johnson N2 protocol network. Johnson Controls has multiple field panels/controllers that support the Johnson N2 bus. The configuration consists of removing a Johnson Controls Metasys field panel/controller and replacing it with the Siemens Johnson Controls N2 Master Driver. The driver s FLN port is directly connected to the Johnson N2 bus. Any global programming in the Johnson Controls field panel being replaced must be duplicated within the driver. 1 9 Restricted

2 Johnson Controls Metasys Devices that can be Replaced with the Johnson Controls N2 Master Driver The following Johnson Controls Metasys field panels/controllers can be replaced with the Johnson Controls N2 Master Driver: NCM (Network Control Module) Located in an NCU enclosure N30 Supervisory Controller N31 Supervisor Controller (also known as Facilitator) NAE (Network Automation Engine; NAE35, NAE45, NAE55) NIE (Network Integration Engine) NCE (Network Control Engine) Johnson Controls Devices Supported on the Johnson N2 Bus The following Johnson Controls devices are supported on the Johnson N2 bus: VAV XTM-105/XPx VMA DX-9100 XT-9100/XP910x XTM-905/XPx AHU UNT TC9102 with point commanding limited as follows: Only the point PM6K1 Common Setpoint (COMMONSP) can be commanded from a TC9102 device when using Driver Revision J2C2.1 and later, J2D2.1 and later, or J2E1.0 and later. No other PMK points can be commanded. No other Johnson Controls N2 Master Driver revisions support commanding PMK points. Third-party Controllers Supported on the Johnson N2 Bus The following third-party controllers are supported on the Johnson N2 bus: SZ1017N SZ1022N SZ1024N ABB ACH 400 Series Frequency Drive ABB ACS 600 Series Frequency Drive This driver supports other devices that have properly implemented the Johnson N2 open protocol. Please contact the Integrated Systems department for help in evaluating other vendor devices. 2 9 Restricted

3 Johnson Controls N2 Master Driver Support The Johnson Controls N2 Master Driver can support: Device addresses in the range of 1 through 255; however, there is a maximum of 96 devices, whichever comes first. A maximum of 96 devices or a maximum of 8000 unique points, whichever comes first. See the Ordering Information [ 6] section for part numbers. See the Johnson Controls N2 Master Driver on the TC Series Platform Technical Specification Sheet ( T) for a system architecture diagram. Functionality The Johnson Controls N2 Master Driver allows data from Johnson N2 bus devices to be mapped into TALON points. The driver acts as a node on the ALN network. All programming functions PPCL, TX-I/O modules, and point definition remain intact. It is recommended to replace each Johnson Controls panel (NCM, N30, N31, NAE or NCE) with one driver. If the N2 bus networks have less than 96 total devices or 8000 points, then more than one bus can be integrated to a single driver. However, performance may be compromised. It is possible to connect multiple Johnson N2 buses to a single driver. The three (3) FLN ports on the driver can be individually configured to support either an N2 or P1 bus or both. For example, the FLN 1 port can have a Johnson N2 bus connected and P1 devices connected, the FLN 2 port can have a P1 bus connected, and the FLN 3 port can have a Johnson N2 bus connected. A driver on TC Modular can support a maximum of three buses. A driver on PXC Compact 36 can support 1 FLN. The Johnson Controls N2 Master Driver can be used in combination with the FPWeb database editors and graphics. This includes support for FIN Builder-based graphics when used in combination with the LSM-FPWEBPLHST.T or LSM-FPWEBPL.T license. The driver supports auto-unbundling and TX-I/O modules. The driver performs basic monitoring and control functions. Standard system functions are supported including PPCL, alarming, trending, scheduling, and runtime accumulation. Functionality Not Supported The driver does not provide the following functionality: Support for Johnson Controls DSC8500 controllers. These controllers are older technology with a different protocol (not N2). Support for Johnson Controls L2 Bus and L2 devices (that is, C210). Support for uploading/downloading the Johnson Controls database programs from or to the TALON Automation System. Only the point PM6K1 Common Setpoint (COMMONSP) can be commanded from a TC9102 device when using Driver Revision J2C2.1 and later, J2D2.1 and later, or J2E1.0 and later. No other PMK points can be commanded. Metasys Integrator devices (MIG) (see Important Considerations [ 4]). Johnson Controls devices that are not N2 Open Protocol (see Important Considerations [ 4]). 3 9

4 Johnson Controls Facility Explorer Building Automation System Johnson has introduced a system to its distribution channel (not Branches) called Facility Explorer. This is a system that is marketed and sold by distributors only. This system s supervisory controller is referred to as FX40, FX20, or FX60. The FX40 supports an N2 bus and/or a BACnet bus. The system supports the following N2 contollers: FX05 FX06 FX07 FX14 FX15 FX16 TEC1100 TEC2100 TEC2000 It is believed these N2 devices use the same N2 protocol as the Metasys system. None of these devices has been tested with the Johnson Controls N2 Master Driver. It is believed the Johnson Controls N2 Master Driver would support these devices by replacing the FX40, FX20, or FX60 panel and integrating the N2 bus; however, this has not been tested and verified. If further information is required, contact the Integrated Systems department. For detailed information on this system refer to: Smoke Control Can be connected to a smoke control network, but may not perform any smoke control functions. Important Considerations You must have a person with thorough knowledge of the Johnson Controls system to make these projects a success. Because the Johnson Controls panels are eliminated, all functions previously supported by the panel (global point sharing, programming, schedules, point modules) must be duplicated using equivalent TALON products and functionality. Be sure to consider this when estimating. Each application is created based on the current configuration of a given N2 device. If the configuration of the device changes, the application must also change. Be sure to consider this when estimating. Not all Johnson Controls devices are supported by this driver. Some devices are so old (for example, LCPs) that test equipment cannot be obtained. If the equipment is not listed in the Configuration [ 1] section, contact the Integrated Systems department to decide what should be done. 4 9

5 The Metasys Integrator devices (MIGs) are similar to Siemens Integration Drivers since they interface to an entire third-party system, yet they reside on the N2 bus. Integrating to these devices is not desirable for several reasons. First, the entire system will look like a TEC in System Profile. Second, the Johnson Controls implementation of the third-party integration must be learned. Third, the integrator integrity does not come close to that of a TALON driver. Last, if the third-party changes anything on their side (as they are known to do), you are now responsible for making changes to a MIG, and then to the N2 application file. For these reasons, it is best to remove the MIG and replace it with the equivalent Siemens Integration Driver. If an equivalent Siemens Integration Driver is not available, please contact the Integrated Systems department to decide what should be done. In addition, Johnson Controls devices that are not N2 Open Protocol, are not supported by this driver. These include NCU, DCM140, XBN101, XRE101, XRL101, and XRM101. These devices should be replaced with the equivalent TALON devices. Estimating NOTE: For more information on creating your own custom applications with Application Builder Tool, see Product Announcement 625T. If custom applications must be created, be sure to include labor cost in the estimate. How to Estimate this Solution 1. Obtain the Johnson Controls Controller Information report by using HVAC PRO (Johnson Controls equivalent to the Siemens Industry Voyager tool). A function in this tool provides specific N2 bus information to determine what N2 devices are on the N2 bus, the address occupied by each device, each device type, and the most recent device configuration. HVAC PRO can be purchased by calling EECI at (800) 360-EECI. 2. Use the Controller Information report to determine the number of unique applications required for the N2 bus. Estimate one hour per unique custom application. 3. Identify the number of N2 buses. One driver per N2 bus is recommended; however, each driver can accommodate a maximum of three N2 buses. 4. Estimate the driver(s) using the Siemens Price List. Integration to the Johnson Controls N2 Master Driver requires an application. The hours listed below are for one driver and one application. If multiple drivers or applications are installed, multiply this time by the number of drivers or applications. 5 9

6 Item Table 1: Engineering Hours Project Manager Hours Specialist Hours Remarks Installation of the driver This time is for one driver. Use of pre-existing or standard applications that are available on the Standard Apps drive or the Integration SharePoint Site. Custom applications must be created using the Application Builder tool This time covers one application. This time includes acquiring the point map. Standard applications can be found on the Partner Extranet Web site This time covers one application. When a custom application must be created, it is necessary to have object list to create the application file, be sure extra time is added to cover this labor in the estimate. Ordering Information Custom applications are required; the labor to create them is not included in the estimate. TC Series-based Integration Drivers are comprised of standard TC Modular or TC-36 hardware loaded with Integration Driver firmware. Driver firmware must be loaded onto the TC Modular or TC-36 using the Firmware Loading Tool (FLT). The driver is then licensed using TALON Commissioner, Siemens software, or the HyperTerminal HMI port. Loading the driver firmware replaces the existing firmware and converts the FLN to a driver-specific protocol. Ensure that you order all the parts for an Integration Driver on the TC Series platform. 1. Select a hardware option: Order the standard TC Modular hardware and RS-485 Expansion Module (as needed) per Product Announcement 700T. Order the standard TC-36 hardware per Product Announcement 735T. 2. Then order the Driver License. The Integration Driver firmware is available on the Vantage Web site. To enable the firmware for operation, load the driver license into the TC Series-based Integration Driver. For more information on installing the firmware or loading the driver license, see the Johnson Controls N2 Master Driver for TC Modular and TC-36 Technical Manual ( T). See the Parts Orderable through the Factory section for orderable part numbers related to the TC Series. 6 9

7 Parts Orderable through the Factory NOTE: The TC Series hardware is standard hardware and not unique to Integration Drivers. The Integrated Driver solution is comprised of the standard TC Modular or TC-36 hardware, loaded with the Johnson Controls N2 Master Driver firmware and license. Table 2: Licenses. Product Description License to enable the Johnson Controls N2 Master Driver on TC Modular or TC 36 hardware. Enables a TC Series controller to host FIN Builder graphics. Enables any TC Series controller to supply the host controller with data for FIN Builder graphics. LSM-INT-JCIN2M.T LSM-FPWEBPLHST.T LSM-FPWEBPL.T Table 3: TC Modular. Product Description TC Modular, BACnet/IP or MS/TP ALN, 96 FLN nodes. Expansion Module, three RS-485 FLN connections. TC1000-E96.T PXX Table 4: TC-36. Product Description TC Compact, 36 point, BACnet/IP or MS/TP ALN. TC36-E.T License Manager Web Site License Manager is a licensing tool that provides a flexible field configuration capability for TALON firmware features. Licensing is now integrated with SAP; you can order and generate licenses within an hour by using the License Manager Web site. For detailed instructions, see the TALON License Manager Start-up Procedures ( ). Number of Drivers Required per Job The following factors determine driver capacity, and therefore, the number of drivers needed to support a particular job: Available RAM in the driver. Number of devices the driver can support. Based on each factor, calculate how many drivers may be needed. The calculation that results in the highest number of drivers reflects the most limiting factor and the actual number of drivers required for the job. The Johnson Controls N2 Master Driver is most often limited by the number of vendor devices. 7 9

8 Available Bytes of RAM In general, use the following guidelines for RAM sizing: Available RAM. Product Description Approx. RAM (MB) TC Modular, BACnet/IP or MS/TP ALN, 96 FLN nodes. TC1000-E96.T 50 TC Compact, 36 point, BACnet/IP or MS/TP ALN. TC36-E.T 50 Number of Devices Supported The Johnson Controls N2 Master Driver can support a maximum of 96 devices. Documentation Sales Documentation Document Siemens Price List BACnet Field Panel Firmware Revision 3.4 with BACnet Field Panel Web Server (FPWeb) and Launch Pad Updates List SR-874T Technical Documentation Document Johnson Controls N2 Master Driver Release/Upgrade Notes T Johnson Controls N2 Master Driver TC Modular and TC-36 Technical Manual T Johnson Controls N2 Master Driver TC-Series Installation Instructions T TC Modular Series Installation Instructions TC Modular Start-up Procedures TC Modular Technical Reference Manual TC-36 Installation Instructions TC Compact Series Start-up Procedures TC Compact Series Technical Reference Manual

9 Support Sales Support For sales support, contact the Product Manager listed in the Who to Contact list Deerfield Parkway Buffalo Grove, IL USA Technical Support Contact your Regional Operations Manager. Information in this document is based on specifications believed correct at the time of publication. The right is reserved to make changes as design improvements are introduced. TALON is a registered trademark of Siemens Industry, Inc. Desigo and Desigo CC are registered trademarks of Siemens Schweiz AG. Other product or company names mentioned herein may be the trademarks of their respective owners Siemens Industry, Inc. All presented offerings are subject to a cyber security disclaimer which is available at: Siemens Industry, Inc. Building Technologies Division 1000 Deerfield Parkway Buffalo Grove, IL USA Tel Your feedback is important to us. If you have comments about this document, please send them to SBT_technical.editor.us.sbt@siemens.com. Document No T Printed in the USA Page 9 9