Siemens N4 Appliance Revision 1.10.xxx User Guide

Transcription

1 Siemens N4 Appliance Revision 1.10.xxx User Guide A6V Building Technologies

2 Table of Contents Cyber security disclaimer... 5 How to Use This Manual... 6 Overview... 8 Network and System Requirements... 8 System Recommendations... 8 Siemens N4 Appliance Views Installation Installing Siemens Workbench Installing and Configuring a Siemens N4 Appliance Station and Platform Configuring a Site Structure Example for Creating a Job-Specific Site Structure Customizing Hierarchies User Accounts Identifying and Configuring the Required Networks Configuring a Computer Station BACnet/IP Links Configuring TNM BACnet/IP Links Configuring TNM BACnet MS/TP Links Network Statistics Configuring the Required Networks Configuring the BACnet Local Device Configuring a BACnet/IP Network Configuring a BACnet MS/TP Network Identifying and Configuring TNM Local Devices Determining if a Station Local Device is Needed Configuring a Station Local Device Using Station Local Devices Upgrading Siemens N4 Appliance Station Migrating the N4 Platform from Revision 4.2 to Updating an Installed Station from N4 Appliance 1.00 to Overview of the migrate_1_00_to_1_10 Program A Note on Updating Device Templates Before You Begin Updating Modules Adding Device Templates Restarting the System Updating the Station to 1.10 Required Steps Updating a Station Running on a PC Platform Updating a Station Running on a JACE Platform

3 Updating the Station to 1.10 Optional Steps Updating Installed Job Data Updating Installed Devices to Revision 1.10 Templates Optional Step Using the Siemens N4 Appliance Discovering Devices on the Network Adding Controllers Deleting an ALN or FLN Device Configuring Schedules Built-in Schedules and Schedule Editor Views Siemens_Day_Ngt_Schedule Siemens_OpMode_Schedule Creating Additional Schedules Sychronizing Station Schedules with BACnet Schedule Objects Configuring User Accounts Populating Summary Views Operator View Existing Schedules in Operator View Editing a Schedule or Calendar Object Opening the Alarm Console Using the Charting View Feature Customizing the Logos Configuring and Using Siemens Launch Pad Editing Points and PPCL Programs Disabling Launch Pad Integration Configuring a Landing Page Uninstalling Siemens Workbench Advanced Topics Adding a LocalDeviceAhu object to the station Updating Device Names and Hierarchies Appendix A - Supported Applications Appendix B - Application Templates Notes

4 4 100

5 Copyright Notice Copyright Notice Notice Document information is subject to change without notice by Siemens Industry, Inc. Companies, names, and various data used in examples are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Siemens Industry, Inc. All software described in this document is furnished under a license agreement and may be used or copied only in accordance with license terms. For further information, contact your nearest Siemens Solution Partner, Authorized TALON Dealer. Copyright 2018 Siemens Industry, Inc. To the Reader Your feedback is important to us. If you have comments about this manual, please submit them to: SBT_technical.editor.us.sbt@siemens.com Credits TALON is a registered trademark of Siemens Industry, Inc. Other product or company names mentioned herein may be the trademarks of their respective owners. Printed in the USA. Cyber security disclaimer Products, solutions and services from Siemens include security functions to ensure the secure operation of building automation and control, fire safety, security management, and physical security systems. The security functions on these products, solutions and services are important components of a comprehensive security concept. Drafting, implementing and managing a comprehensive and up-to-date security concept, customized to individual needs, is nevertheless necessary, and may result in additional plant- or site-specific preventive measures to ensure secure operation of your site regarding building automation and control, fire safety, security management, and physical security. These measures may include, for example, separating networks, physically protecting system components, user training, multi-level defensive measures, etc. For additional information on security as part of building technology and our product, solution and service offerings, please contact your Siemens sales representative or project department. We strongly recommend to always comply with our security advisories on the latest security threats, patches and other related measures

6 How to Use This Manual How to Use This Manual About This Manual This manual is written for the user of the Siemens N4 Appliance. It is designed to help you become familiar with the application. This section provides an overview of the manual, explains document conventions and symbols used throughout the manual and how to access help. How This Manual Is Organized This manual contains the following sections in the following order: Overview explains how to use the common functions of the Siemens N4 Appliance. Installation describes the installation and setup of system-related parameters. Upgrading Siemens N4 Appliance Station includes procedures to upgrade the N4 Appliance station from Niagara 4 Revision 4.2 to 4.3. Using the Siemens N4 Appliance describes the functionality of the Siemens N4 Appliance. Advanced Topics provides procedures for configurations that do not use a Siemens field panel. The Appendixes outline the applications supported for each type of controller and related notes. Document Conventions The following table lists conventions to help you use this manual in a quick and efficient manner. Convention Numbered Lists (1, 2, 3 ) indicate a procedure with sequential steps. Conditions that must be completed or met before beginning a task are designated with a. Intermediate results (what will happen following the execution of a step), are designated with a. Results, which inform the user that a task was completed successfully, are designated with a. Actions that should be performed are specified in boldface font. Error and system messages are displayed in Courier New font. New terms appearing for the first time are italicized. Examples 1. Turn OFF power to the field panel. 2. Turn ON power to the field panel. 3. Contact the local Siemens Solution Partner, Authorized TALON Dealer. Composer software is properly installed. A Valid license is available. 1. Select Start > Programs > Siemens > GMS > Composer. The Project Management window displays. 2. Open an existing project or create a new one. The project window displays. Type F for Field panels. Click OK to save changes and close the dialog box. The message Report Definition successfully renamed displays in the status bar. The field panel continuously executes a user-defined set of instructions called the control program. This symbol signifies Notes. Notes provide additional information or helpful hints

7 How to Use This Manual Cross references to other information are indicated with an arrow and the page number, enclosed in brackets: [ 92] Placeholders indicate text that can vary based on your selection. Placeholders are specified in bold print, and enclosed with brackets [ ]. For more information on creating flowcharts, see Flowcharts [ 92]. Type A C D H [username] [field panel #]. Safety Symbols The following table lists the safety symbols used in this manual to draw attention to important information. Symbol Meaning Description NOTICE CAUTION Equipment damage may occur if a procedure or instruction is not followed as specified. (For online documentation, the NOTICE displays in white with a blue background.) CAUTION WARNING DANGER Minor or moderate injury may occur if a procedure or instruction is not followed as specified. Personal injury or property damage may occur if a procedure or instruction is not followed as specified. Electric shock, death, or severe property damage may occur if a procedure or instruction is not followed as specified. How to Contact Us Your feedback is important to us. If you have comments about this document, please submit them to the following address: SBT_technical.editor.us.sbt@siemens.com

8 Overview Network and System Requirements Overview The Siemens N4 Appliance has been designed as an automated Niagara station builder for Niagara 4 with pre-defined and customizable configurations based on Siemens knowledge in the Building Automation industry. Using the Siemens N4 Appliance saves you time during the Niagara station setup process by using automation, customizable templates, default presets and license free PX based application graphics. It has been tested following Siemens quality procedures that provide a repeatable high quality result. Hardware Compatible with any TNM controller with hotspot VM (TNM-J6, TNM-J6E, TNM-J7 and TNM-8000). Compatible with TALON N4 Supervisor. Network and System Requirements Operating System: Windows 7 64-bit and Windows bit. Browser Support: Microsoft Internet Explorer (IE) 9, 10 or 11, Edge, Chrome, or Mozilla Firefox current versions. Cookies must be enabled. This is done by selecting Options from the Tools menu in most browsers. Memory: 1 GB minimum, 4 GB or more recommended for larger systems. Hard Drive: 4 GB minimum, more recommended depending on archiving requirements. Network Support: Ethernet adapter (10/100 MB with RJ-45 connector). System Recommendations Policy Value Notes For optimized system performance, Siemens recommends the following tuning policies, which are also the default settings in Siemens N4 Appliance. Siemens N4 Appliance Tuning Policy Recommendations Min Write Time 0 minutes (default) Applies to writable points. Specifies the minimum amount of time allowed between writes. Provides a method to throttle a rapidly-changing value so that only the last value is written. If this property value is 0 (default), this rule is disabled and all value changes attempt to write. Max Write Time 0 minutes (default) Applies to writable points. Specifies the maximum wait time before rewriting the value, in case nothing else triggers a write. Any write action resets this timer. If this property value is 0 (default), this rule is disabled (no timed rewrites). This is how often you want the station to take control over the BACnet device. Write on Start False (default) Applies to writable points. Determines behavior at station startup. If True, a write occurs when the station first reaches steady state. If False (default), a write does not occur when the station reaches steady state. This setting allows the station to take control of the BACnet device when it first starts. Doing this can put a load on the station while it is trying to start by adding multiple write commands to the station. Write on Up True (default) Allows the station to take control when the device transitions from Down to Up

9 Overview System Recommendations Policy Value Notes Write on Enable True (default) Allows the station to take control when the device transitions from Disabled to Enabled. Stale Time UseCOV 10 minutes (varies based on polling policy) False (true for the Siemens_COVPpolicy, false for the Siemens polled policies) Confirms that the device is working properly, but raises awareness that a point has not been updated in a reasonable amount of time. A longer period of time for slower polling rates and a shorter period of time for faster polling rates. If set to True, and assigned points are under a BacnetDevice that supports the Subscribe COV service, any necessary updates (Niagara proxy subscriptions) are attempted using BACnet COV subscriptions to the device. If the subscription attempt succeeds, the Read Status property of the point s BacnetProxyExt displays COV. If the subscription attempt for a proxy point fails, normal polling is used and the Read Status property displays Polled. Use Confirmed COV True (default) If UseCOV is enabled (set to True) and assigned points are under a BacnetDevice that supports Confirmed COV notifications, any necessary updates (Niagara proxy subscriptions) are attempted using BACnet Confirmed COV subscriptions to the device. If UseCOV is not enabled (set to False), the value of this property is ignored (true for the Siemens_COVPpolicy, false for the Siemens polled policies). COV Subscription Lifetime 15 minutes The lifetime, in minutes, for which Niagara will subscribe for COV notifications, and then, if necessary, periodically re-subscribe. A value of zero means an indefinite lifetime, although this is not guaranteed to persist across resets of the server device. Do not use zero in Siemens installations! If the UseCov property is False, the value of this property is ignored

10 Overview System Recommendations Recommendations for Metric Users NOTE: The user account setting only applies when using a browser. When using Siemens Workbench, the user account setting is ignored, and the unit system is selected from the Tools menu, Options > General, Unit Conversion. For Siemens N4 Appliance Revision and later, all Siemens FLN devices must be configured for English units. The English-to-metric conversion is handled by the station. Configuring a User Account to Display Metric Units when using a Browser Siemens Workbench unit conversions are set from the Tools menu, Options > General, Unit Conversion. 1. From the Nav pane, expand and select Station, UserService, [user name] (for example Siemens_Integrator). 2. Right-click the user name and then select AX Property Sheet. The Property Sheet displays. 3. In the Facets section, select Metric from the Unit Conversion drop-down menu. 4. Click Save

11 Overview Siemens N4 Appliance Views Siemens N4 Appliance Views Two customizable views are available in the Siemens N4 Appliance: Technical View (Workbench View) Operator View (Web Browser View) Technical View (Workbench View) The Technical View provides access to all the features of the station. It is used by building technicians (Siemens_Integrator user account type) to configure and navigate through sites. The set of sidebar panes (Nav, Template, Palette, and so on) are configurable from the Windows menu Path bar Displays the path bar of the current component selected from the Nav pane. View selector Allows you to choose between the views available for the selected component. Nav (Navigation) pane Provides access to the configuration, operation and monitoring features provided by the station. This is restricted by your user role. Palette pane Displays new station components, added by dragging items from this pane to the station in the Nav pane. Template pane Displays the list of available device templates. Header pane Displays alarm count, current ID of the user and job name. View pane Displays the active view

12 Overview Siemens N4 Appliance Views Operator View (Web Browser View) The Technical View provides access to all the features of the station. It is used by building technicians (Siemens_Integrator user account type) to configure and navigate through sites. The set of sidebar panes (Nav, Template, Palette, and so on) are configurable from the Windows menu. NOTICE The Operator View cannot access the engineering and commissioning features of the station. The customizable Operator View is primarily used for daily operation and monitoring of your customer site(s). This view is available through the station for Siemens_Customer and Siemens_Balancer user account types Pane selector Allows you to enable and disable individual panes (Navigation, Palette and Search). In the default customer view, only the Navigation pane is selectable. Nav (Navigation) pane Provides access to the operation and monitoring features provided by the station. This is restricted by your user account role(s). View selector Allows you to choose between the views available for the selected component. Header pane Displays alarm count, current ID of the user and job name. View pane Displays the active view

13 Installation Installing Siemens Workbench Installation Installing Siemens Workbench Siemens Workbench software files are available from the Niagara Central Web site. 1. Connect to Niagara Central\Software login. 2. Enter your Niagara Central username and password credentials and click Login. 3. In the Brands field, select Staefa. 4. From the Siemens N4 Supervisor section, select the latest *.zip file for download, select Save As, and then select a distribution folder on your computer where you want to unzip (extract) the files. 5. In the root distribution folder, double-click Installer_x64.exe. The Siemens Workbench Installation Program wizard displays. Click Next. 6. Select Yes, and then click Next to accept the End User License Agreement. The default location for Siemens Workbench installation is C:\Siemens\SiemensWorkbench-4.3.x.x. 7. Keep all default settings and click Next. If the installation folder does not exist, you are prompted by the system to create it. 8. If this is the first time you re installing Siemens Workbench, set the password used to encrypt sensitive information on the filesystem. The password must contain: 10 characters One lowercase character One uppercase character One digit 9. If desired, select one or both check boxes to create Start Menu or Desktop shortcuts. 10. Click Next. A progress bar displays during the installation, and then a confirmation message displays when the installation is complete. 11. If desired, select the check box for one or more of the following options: Launch Workbench. Install and Start Platform Daemon. Copy Daemon Data From Prior Version (only displays if a prior version exists). 12. Click Finish

14 Installation Installing Siemens Workbench Obtaining a License NOTICE If a previous version of Siemens Workbench was installed and you are connected to the Internet, you will automatically receive a new license. In this case, start Siemens Workbench and skip to the procedure Installing and Configuring a Siemens N4 Appliance Station and Platform. 1. Start Siemens Workbench. The Request License dialog box displays. 2. Call the Siemens number listed in the dialog box and provide the information displayed. 3. Do the following once you receive the license.zip file: Save the.zip file to your computer and extract its contents. Navigate to the location where Siemens Workbench is installed and open the security folder. (The default location is C:\Siemens\SiemensWorkbench- 4.3.x.x.)

15 Installation Installing Siemens Workbench Copy the.license file(s) into the target host s licenses folder. Note: You can rename any license file without affecting it. For example, you can change the name from Tridium.license to MyHost2.license to keep from overwriting an existing license file with the same name. Copy any.certificate files into the certificates folder. 4. Start Siemens Workbench. The Siemens Workbench welcome screen displays

16 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform Installing and Configuring a Siemens N4 Appliance Station and Platform The Siemens N4 Appliance files are available for download from the Partner Extranet Web site. 1 Installing a New Station This section assumes that Siemens Workbench software is already installed on your computer. 1. Extract the contents of Siemens_N4_Appliance_1_10_10x.zip to a folder on your computer. 2. Open the Siemens_Station_1_10_10x folder and copy the Siemens_Station_1_10_10x.ntpl template to the [user home station] templates folder. If Siemens Workbench is installed on the C: drive, the typical path is C:\Users\[your user name]\niagarar4.x\tridium. If a templates folder does not exist, create one. 3. Copy the contents of the Siemens_Templates_1_10_10x folder to the [user home station]\templates folder. 4. Find the modules folder under the program installation folder. For example, C:\Program Files\Niagara4_SiemensWorkbench \modules. 5. Copy the contents of the Siemens_Modules_1_10_10x folder to the modules folder under the program installation folder

17 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 6. From the Start menu, select Programs > Siemens Workbench 4.3.x.x > Install Platform Daemon. The Platform Daemon runs and Siemens Workbench detects any new module(s). 7. Start Siemens Workbench, right-click on the desired platform and select Open Platform. If necessary, use Application Director to stop and disable the Auto-Start function for any stations that are currently running on the host. 8. From the Tools menu, select New Station. The New Station Wizard displays. 9. In the Station Name field, enter a name. For example, Siemens

18 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 10. In the Station Templates section, select the most current version of the Siemens_Station from the list (Siemens_Station_1_10_10x.ntpl) and click Next. 11. Click Set Password to set the admin user password. Enter a password and then confirm the password. The password must contain: 10 characters One lowercase character One uppercase character One digit Continue with the appropriate subsection for your site. a If you re planning to run the station on the Workbench computer 1. Select copy it to secure platform for localhost with Station Copier and then click Finish. 2. Enter the platform credentials, if necessary. The Station Transfer Wizard opens. 3. If desired, change the parameters from the Station Transfer Wizard. Otherwise, click Next to use the default settings and then click Finish. 4. Click Close after the station transfer completes. 5. Copy the Siemens_Shared_1_10_10x folder to the [user home]\shared folder. This folder is typically located on C:\Users\[your user name]\niagara4.3\tridium\shared. 6. Start the Siemens N4 Appliance station in Siemens Workbench. 7. Expand [user home]/shared/siemens_shared_1_10_10x/1_10_files to view its contents. 8. Copy the files from the NewFiles/px/Siemens_Views folder to the station s Files/px/Siemens_Views folder. 9. Copy Background.png to the station s Files folder. Installation is complete. b If you re planning to run the station on a TNM controller 1. In the Station Transfer Wizard, leave the default setting to Open it in User Home and click Finish. 2. In the Nav tree, right-click on the TNM controller Platform, select Open Platform, and then enter the Platform credentials. 3. From Platform, select and open Station Copier, select the station you created, and then click Copy. 4. Enter a name for the station and click Next. 5. In Station Copier, if there is already a station on the TNM (JACE) controller, a warning displays stating that the existing station will be deleted. Click Next. 6. Select Copy every file in the station directory and its subdirectories and click Next. 7. Select the desired startup options and select Next. 8. Select Finish

19 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 9. When the Transferring operation completes, select Close. 10. Select Yes to navigate to Application Director. Wait for the station to start. 11. From Platform, select and open File Transfer Client in Files on this computer, navigate to 1_10_Files/px/Siemens_Views select velhischart.pxvm and VelHisTable.pxvm. 12. From Files on <TNM address>, navigate to UserHome\Stations\Shared\px\Siemens_Views. 13. Click Copy. 14. Click OK to close the Transfer Complete dialog. Installation is complete. 2 Opening the Station using the admin Account To start configuring the new station, you must logon using the admin account. 1. Find the new station in the Nav tree and double-click on it to open the station. 2. In the Username field, type admin. 3. Enter the password that you specified in Step 10 of the 1 Installing a New Station section

20 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform Configuring a Site Structure Default Configuration The N4 Appliance provides a default Site object and two default Area objects, each with predefined tags and structure relationships. The purpose of these default objects is to simplify the process of creating a job-specific site structure. The following figure displays the default tagged objects and predefined views. Links between objects and views are defined by preconfigured Site and Area object properties. Figure 1: Default N4 Appliance Site Configuration (tags and views)

21 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform The following figure displays the default structure relationship between the Area objects and the Site object. The relationships are defined using the Haystack site ref tag (hs:site). These relationships are mandatory, and they are used to auto-generate hierarchies for navigation and runtime processes. Figure 2: Default relationship between the Area objects and the Site object. Example for Creating a Job-Specific Site Structure NOTICE If you plan to customize the site, do this before the procedures Discovering Devices on the Network and Adding Controllers. This section provides an example for creating a job-specific Site structure. The example site is named MySite, and has three floors named Floor 1, Floor 2 and Floor 3. This example assumes that area summary views (for example, Floor1Summary.px) are desired. If not, delete the summaryview slots from the EastWing and WestWing objects before proceeding

22 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 1 Renaming Default Objects and Views This step renames the default objects and views to create a partial-site structure. Figure 3: Renaming default objects and views. 1. Navigate to Station > Siemens_Site and then expand Siemens_Site. 2. Right-click on DemoSite, select Rename and then assign a new name. MySite is used in this example. 3. Expand the site you renamed. 4. To rename the WestWing and EastWing Areas, right-clicking on each Area, select Rename and then assign a new name. Floor1 and Floor2 are used in this example. 5. Navigate to Files/px/Siemens_Summary_Views and rename the existing Area Summary Views to match the new Area names. 6. Do the following in the Summary View property to reference the new summary.px files: Open the AX Property sheet for each area (Floor1 and Floor2 are used in this example). Click on the folder icon and select Files on Station > Siemens_Summary_Views. Select the appropriate.px file. For example, Floor1Summary.px and Floor2Summary.px. Select Open and then select Save in the Property Sheet window for each Area

23 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 2 Creating Additional Areas This step adds another area for Floor3. The new area will have the same tags and relations as the existing areas. 1. Right-click on one of the existing Area objects and select Copy. 2. Right-click on the Site object and select Paste Special. 3. Select the Keep all relations check box and then click OK. The new Area is added but is not named correctly. 4. Right-click on the new Area, select Rename and then assign a new name. Floor3 is used in this example. 5. Right-click on the new Area, select Set Display Name and then assign a new name. Floor 3 is used in this example. 6. If desired, do the following to create a new Floor 3 summary view: In Files/px/Siemens_Summary_Views, right-click on one of the existing Area Summary Views. For example, Floor2Summary.px. Select Duplicate and name the new summary view. For example, Floor3Summary.px. Right-click on the newly created Area in Config/Siemens_Site (for example, Config/Siemens_Site/My Site/Floor 3) and open its AX Property Sheet. Set the Summary View property to reference the new summary.px file. For example, Floor3Summary.px. Click on the folder icon and select Files on Station > Siemens_Summary_Views. Select the appropriate.px file. For example, Floor3Summary.px. Select Open and then select Save in the AX Property Sheet window for the Area

24 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform The following figure shows the updated site structure. Figure 4: Updated Site Structure. 3 (Optional) Adding Floorplan Views The N4 Appliance does not provide default floorplan views, but it does provide a template to simplify the process of creating them. This step outlines how to create the views. 1. In the Files/px/Siemens_Views folder, make three copies of _emptyview.px. 2. Name the new files Floor1View, Floor2View and Floor 3View. 3. Right-click on Config/Siemens_Site/My Site/Floor 1 and select Views/New View. 4. Configure the New Px View as shown in the following figure. Select the new floorplan view that was created in the preceding step

25 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 5. Click OK, and then select Reuse on the File Already Exists dialog. 6. Repeat this process for Floor 1 and Floor Edit the newly-created views to make job-specific floorplan views. Figure 5: Completed Site Structure

26 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 4 Checking the Site Structure 1. In the Nav tree, right-click on Hierarchy and select Refresh Tree Node. 2. Expand the Site hierarchy. The hierarchy should correspond to the contents of the Config/Siemens_Site folder. In the Site hierarchy, right-click on each floor and check for a summary view and a floor view. Figure 6: The Final Site Hierarchy

27 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform Customizing Hierarchies The default Hierarchy is provided so that you can rename the Site and Area names and also create new sites and areas. You can customize hierarchies by adding/duplicating an area or site in the hierarchy. This is done by using the duplicate function. NOTE: Site names can be renamed. You can also duplicate sites using this procedure, except you do not have to perform Steps 2 and 3. When you duplicate a site, you will also need to duplicate the Siemens Summary View for the areas that were duplicated along with the site as described in Steps 4 through 11. To Add an Area in the Hierarchy 1. From the Nav pane, expand Config, Siemens_Site, Demo_Site and then select and right-click an area of the site (for example, West Wing) and then select Duplicate. The Name dialog box displays. 2. Enter a name (for example, North Wing) for the area you are adding. Click OK. 3. Right-click the new area you added and select Relation Mark. 4. Navigate to Station, Files, px, Siemens_Summary_Views, and then expand Siemens_Summary_Views

28 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform 5. Duplicate the [Original Area Summary Name.px] and assign a [New Area Summary Name.px]. 6. Navigate to Station, Config, Siemens_Site, and expand Siemens_Site [Site Name]. 7. Right-click on the new [Area Name] and select AX Property Sheet. 8. Expand Summary View, Px View. 9. Change the Px File to the new px file you created in Step 5, using the File Ord Chooser or typing the file name. User Accounts The Siemens N4 Appliance provides the following customizable pre-defined user accounts with specific rights that can be duplicated and modified to create job-specific user accounts. Siemens_Integrator A technical user with unrestricted access (super user) to the station. Uses the station for operation, monitoring, engineering and commissioning of the system. Has the ability to add, delete and modify station files and services, as well as read and write device configuration data. Configuration data is accessed using the device s property sheet. Siemens_Balancer A technical user with access to the station, but no access to the engineering and commissioning features of the station. Uses the station for operation, monitoring and configuration of the system. Siemens_Customer A user with limited access to the Technical View. Uses the station for everyday operation and monitoring of the system. NOTE: For cyber security reasons, there are no default passwords, even though the Password and Confirm fields in the Property Sheet are filled out. Passwords for default user accounts must be defined while configuring the Siemens N4 Appliance. Configuring User Accounts You have logged in to the Siemens N4 Appliance station using the admin account. 1. From the Nav pane, select and expand Config, Services, UserService, and then double-click Siemens_Customer. 2. From the Property Sheet tab, in the Authenticator section, enter a password, for example, Cust_ Leave all other settings at the default and click Save

29 Installation Installing and Configuring a Siemens N4 Appliance Station and Platform Creating new user accounts based on the default station accounts 1. Navigate to Station > Config > Services > User Service and select an account to duplicate. For a customer account, select Siemens_Customer. For a dealer technical specialist account, select Siemens_Intergrator. For a Balancer account, select Balancer. 2. Right-click on the selected account and select Duplicate. 3. Select a name for the new account and click OK. 4. Double-click on the new account to open the AX Property Sheet. 5. Enter a new password and confirm that password. 6. If you want to force the user change their password and set Force Reset at Next Logon accordingly. 7. Select Save. Continue to Configuring a Network

30 Installation Identifying and Configuring the Required Networks Identifying and Configuring the Required Networks Before configuring BACnet networks, you must identify the network layout. This section includes example layouts as guidance. These example layouts may be used to identify station communication links that must be added and/or configured. NOTE: Since TNM stations may connect to devices using both BACnet/IP and BACnet MSTP ports, in some cases, both of the examples in this section may apply. The devices outlined in this section are examples only. They are provided to illustrate the types of devices that would appear on various types of network. Computer-Hosted Station A computer-hosted station typically has a single BACnet/IP link, as shown in the following figure. For this type of network layout, follow the instructions in the section Configuring a Computer Station BACnet/IP Links [ 32]. Figure 7: Computer-hosted Station

31 Installation Identifying and Configuring the Required Networks TNM with BACnet/IP Link(s) A TNM station typically has a single BACnet/IP link, but may be configured with two, as shown in the following figure. For this type of network layout, follow the instructions in the section Configuring TNM BACnet/IP Links [ 33]. Figure 8: TNM with BACnet/IP Link(s). TNM with BACnet MS/TP Link(s) A TNM station without expansion modules may be configured with one or two MS/TP links, as shown in the following figure. For this type of network layout, follow the instructions in the section Configuring TNM BACnet MS/TP Links [ 35]. Expansion modules may be added to provide additional MS/TP ports. Additional ports are configured using the same instructions as on-board ports. Figure 9: TNM with BACnet MS/TP Link(s)

32 Installation Identifying and Configuring the Required Networks Configuring a Computer Station BACnet/IP Links Generally, the following parameters need to be configured for a computer station BACnet/IP link: Parameter Network Number Adapter Enabled Notes The BACnet network number of the network to which the computer station is connected. The network adapter used to connect to the BACnet network. If an adapter is missing from the drop-down list, right-click on Link and select Actions > Query for Adapters to refresh the list (see the following Figure Refreshing the Network Adapter List). Enables or disables the communication link. When configured correctly: Status transitions to {ok}. Ip Address corresponds to the computer s settings for the selected network adapter. For additional network diagnostics, see the Network Statistics [ 36] section. Figure 10: Configuring a Computer Station BACnet/IP Link

33 Installation Identifying and Configuring the Required Networks Figure 11: Refreshing the Network Adapter List. Configuring TNM BACnet/IP Links Generally, the following parameters need to be configured for a TNM station BACnet/IP link: Parameter Network Number Adapter Enabled Notes The BACnet network number of the network to which the station s IP port is connected. The IP network port used to connect to the BACnet network. Select dm0 for the port marked Pri on the TNM enclosure. Select dm1 for the port marked Sec on the TNM enclosure. If an expected port is missing from the drop-down list, use Platform/TCP/IP Configuration to setup network ports. Enables or disables the communication link. Routing_Enabled If the TNM will have BACnet MS/TP devices connected to any of its MS/TP ports (see the figure TNM with BACnet MS/TP Link(s)) and communication between BACnet/IP devices and the connected BACnet MS/TP devices is required, set Routing_Enabled to true. When set to true, the TNM routes messages between the BACnet/IP port and the MS/TP port(s). If the TNM will not have BACnet MS/TP devices connected to any of its MS/TP ports (see the figure TNM with BACnet MS/tP Link(s)) or communication between BACnet/IP devices and the connected BACnet MS/TP devices is prohibited, set Routing_Enabled to false. Maintain_Routing_Enabled When set to false, the station automatically disables routing in the presence of routing errors, such as router loops. When set to true, the station continues to attempt to route messages even when routing errors are detected. When configured correctly: Status transitions to {ok}. Ip Address corresponds to the Platform/TCP/IP Configuration settings for the selected port. For additional network diagnostics, see the Network Statistics [ 36] section

34 Installation Identifying and Configuring the Required Networks Configuring Multiple BACnet/IP Links To configure multiple BACnet/IP links, right-click and select Duplicate to duplicate one of the default links. Using Duplicate assures that the preconfigured network statistics counters and views described in the Network Statistics [ 36] section are available on the new link. Figure 12: Configuring a TNM BACnet/IP Link

35 Installation Identifying and Configuring the Required Networks Configuring TNM BACnet MS/TP Links Generally, the following parameters need to be configured for a TNM station BACnet MS/TP link: Parameter Network Number Port Name Baud Rate Mstp Address Enabled Notes The BACnet network number of the network to which the station s IP port is connected. The MS/TP network port used to connect to the BACnet network. Enter COM1 or COM2, based on the port markings on the TNM enclosure. The bit rate of the MS/TP network. The MS/TP network MAC address for the TNM on the connected MS/TP network. Zero (0) is usually a safe choice for this. Enables or disables the communication link. Routing_Enabled If the TNM will have BACnet MS/TP devices connected to more than one MS/TP port (see the figure Identifying and Configuring the Required Networks [ 31]) and communication between BACnet MS/TP devices on different ports is required, set Routing_Enabled to true. When set to true, the TNM routes messages between the BACnet MS/TP ports. If the TNM will have BACnet MS/TP devices connected to only a single MS/TP port (see the figure Identifying and Configuring the Required Networks [ 31]) use the Routing_Enabled setting determined in the section Configuring TNM BACnet/IP Links [ 33]. Maintain_Routing_Enabled When set to false, the station automatically disables routing in the presence of routing errors, such as router loops. When set to true, the station continues to attempt to route messages even when routing errors are detected. When configured correctly, Status transitions to {ok}. For additional network diagnostics, see the Network Statistics [ 36] section. Configuring Multiple MS/TP Links To configure multiple MS/TP links, right-click and select Duplicate to duplicate one of the default links. Using Duplicate assures that the preconfigured network statistics counters and views described in the Network Statistics [ 36] section are available on the new link

36 Installation Identifying and Configuring the Required Networks Network Statistics Each default communication link in the N4 Appliance is preconfigured with a set of communication throughput counters and a Network Statistics view. These counters and views may be used to determine whether network traffic exists on the link. Figure 13: Network Statistics View. Configuring the Required Networks The Siemens N4 Appliance station is semi-preconfigured with BACnet and MS/TP network defaults; however, you must complete the configuration with data that is specific to the project (job site) where the station is used. Configuring the BACnet Local Device The station must have a valid BACnet Device Object Id that is unique on the BACnet network. The Object Id consists of two parts: A fixed Object Type (device). A configurable Object Instance Number. To avoid conflicts with other BACnet devices on the network, Object Instance number defaults to -1, which is an invalid value. If Object Instance Number is left at -1, the station will not be able to discover or communicate with devices on the BACnet network. You have logged in to the Siemens N4 Appliance station using the admin account. 1. Find BACnetNetwork/Local Station and open its Property Sheet. 2. Select a unique Object Instance Number in the range 0 to The number must not be used by any other device on the BACnet network

37 Installation Identifying and Configuring the Required Networks Configuring a BACnet/IP Network NOTE: Only complete this procedure if the configuration includes BACnet/IP devices, such as Siemens field panels and DXR.E controllers. You have logged in to the Siemens N4 Appliance station using the admin account. 1. Select and expand Config, Drivers, BacnetNetwork, Bacnet Comm, and then double-click Network. You can also view the port and network number from the Property Sheet tab. 2. Enter the BACnet network parameters and enable the network(s). See the Niagara AX-3.x BACnet Guide located in the Niagar4.x\docs\docBacnet folder for more detailed information. 3. Use Link to select which network adapter the station uses for the BACnet network connection. Notice: There might be more than one adapter on a machine. 4. If an adapter is missing from the drop-down list, right-click on Link and select Actions > Query for Adapters to refresh the list. 5. Click Save

38 Installation Identifying and Configuring the Required Networks Configuring a BACnet MS/TP Network NOTE: Only complete this procedure if the configuration does not use a Siemens field panel. That is, if Siemens MS/TP devices are connected directly to MS/TP ports of the TNM controller. See the Configuring an Alternate Port section in the Siemens N4 Appliance Technical Manual (A6V ) to configure a device to use an alternate http port. For each TNM controller you have, you must configure a MS/TP port and each network number must be unique on the network. You have logged in to the Siemens N4 Appliance station using the admin account. 1. Expand BacnetNetwork and then right-click on Local Station and then select AX Property Sheet. 2. From the Nav pane, select and expand Config, Drivers, BacnetNetwork, Bacnet Comm, and then double-click Network. 3. From the Property Sheet tab, expand the MstpPort section. In the Network Number field, enter -1 for the network segment to which you are connecting. 4. Expand the Link section. In the Port Name field, enter the RS-485 port to be used on the TNM JACE controller. 5. In the Mstp Address field, enter a unique BACnet MAC address for that MS/TP port, in decimal format, with a valid range from 0 (default) through 127. Up to four MS/TP ports are supported depending on the host platform and licensing. 6. Click Save. 7. From the Nav pane, right-click the Mstp and select Actions > Enable

39 Installation Identifying and Configuring TNM Local Devices Identifying and Configuring TNM Local Devices NOTE: Only complete this procedure if the configuration does not use a Siemens field panel. For example, if FLN devices are connected directly to MS/TP ports of the TNM controller. It is recommended that you restart the station after adding a TNM controller. If the N4 station is acting as both a supervisory controller and an air handling unit controller, see the topic Adding a LocalDeviceAhu object to the station [ 91] in Advanced Topics. In previous revisions, you had to manually add tags and relations to the Local Station object in order to use the BacnetNetwork LocalStation object as a virtual field panel or AHU controller. With Revision 1.10.xxx and later, templates are provided for LocalDeviceTc and LocalDeviceAhu virtual devices, which eliminates the need to manually add tags and relations. This section outlines the following topics: Determining if a Station Local Device is Needed Configuring the Station Local Device, if one is necessary. Determining if a Station Local Device is Needed This topic outlines how to determine whether an N4 station local device is needed, based on the job configuration. When is a Station Local Device Needed? A local device is typically needed when the N4 station is performing the supervisory controller role that would normally be performed by one or more TCs (TALON controllers/siemens field panels). In this case, a LocalDeviceTc object should be added to the station. For instructions, see the section Configuring a Station Local Device [ 40]

40 Installation Identifying and Configuring TNM Local Devices When is a LocalDeviceTc Object not Needed? A LocalDeviceTc virtual supervisory controller object is not needed if TALON TC controllers have been used to supervise all other BACnet devices, as shown in the following figure. In other words, every child BACnet device appears in the database of a TC controller. Figure 14: TC Controller Example Topologies. Configuring a Station Local Device Typically, a TNM local device is needed in topologies that have FLN-class devices that are not supervised by Siemens field panels. Prerequisite The station s site structure is configured. For more information, see the section Configuring a Site Structure [ 20]. Adding a LocalDeviceTc Object to the Station The LocalDeviceTc template is used to create virtual ALN devices representing field panels, and includes the hs:equip and sie:alndevice tags. 1. Connect to the station using Siemens Workbench. 2. Open the Template sidebar

41 Installation Identifying and Configuring TNM Local Devices 3. Drag the LocalDeviceTc template onto the Config/SiemensUi folder 4. Follow the wizard prompts to select the site and area, just as you would for any other device. The LocalDeviceTc object displays in the Site and Devices hierarchies in place of a TC Controller

42 Installation Identifying and Configuring TNM Local Devices Using Station Local Devices After a LocalDeviceTc object is added to represent a virtual field panel, the process of integrating BACnet FLN devices using BACnet Device Manager is identical to the process used with a real field panel. The same is true when a LocalDeviceAhu is added. Remember that, just like with real BACnet field panels, LocalDeviceTc virtual controllers must be added first, followed by FLN devices

43 Upgrading Siemens N4 Appliance Station Migrating the N4 Platform from Revision 4.2 to 4.3 Upgrading Siemens N4 Appliance Station This upgrade section includes the following procedures to upgrade the N4 Appliance station from Niagara 4 Revision 4.2 to 4.3: Migrating the N4 Platform from Revision 4.2 to 4.3 [ 43] Updating an Installed Station from N4 Appliance 1.00 to 1.10 [ 46] Updating Installed Devices to Revision 1.10 Templates Optional Step [ 56] Migrating the N4 Platform from Revision 4.2 to 4.3 The steps in this procedure assume that the N4 Appliance station will be running on the same platform before and after the platform is upgraded from Niagara 4.2 to Niagara 4.3. Prerequisites A platform (Supervisor or JACE) with an Appliance station using N4 Appliance and running the Niagara 4.3 platform. N4 workbench computer running a licensed Niagara 4.3 Supervisor and capable of running the N4 Appliance station. If upgrading a JACE to Revision 4.3, you must have a 4.3 license for the JACE platform. NOTE: Do not start or stop Daemon, N4 Appliance station or Workbench from a console window. Instead, always start Workbench from the Windows taskbar and always start and stop stations using the Application Director. The result of starting and stopping a station using a console window is that the UserHome copy of the station will be modified, and it will no longer be possible to use station copier to transfer the station to localhost. Saving the 4.2 N4 Appliance Station The following steps apply for both the N4 Supervisor and JACE platforms. 1. In the Workbench, Application Director, stop the Appliance station. 2. From the Station Copier, copy the station from either the remote platform (a JACE) or Stations on localhost to Stations on this computer. 3. From Windows Explorer, copy the saved station from UserHome\Niagara4.2\tridium\stations to UserHome\Niagara4.3\tridium\stations. Upgrading to In the Siemens Workbench, Application Director, close the Siemens 4.2 Workbench. 2. From the Start menu, install the 4.3 platform daemon. 3. From the Start menu, open Siemens Workbench

44 Upgrading Siemens N4 Appliance Station Migrating the N4 Platform from Revision 4.2 to 4.3 Restoring the N4 Appliance Station Depending on which type of platform you are restoring, use one of the following procedures. Restoring the N4 Supervisor Platform Only perform the following steps if the N4 Appliance station is running on a Supervisor (computer) platform. 1. From the Siemens Workbench (4.3), Station Copier, copy the station from the Workbench computer to the localhost computer. Select Copy every file in the station directory and its subdirectories. 2. From the Start menu, select the migrated Appliance station. 3. Navigate to Config\Services\TemplateService, double-click Template Service to view the Template Manager. Select \Siemens_Graphics_Assets\commonStrings, and then click Detach. In the Detach dialog box, verify that the Remove Composite Slots box is checked, and then click Yes. 4. Navigate to Hierarchy\Apps\System\About and then double-click About. The Revision should display as The migration process is now complete. Restoring the JACE Platform Only perform the following steps if the N4 Appliance station is running on a JACE platform. 1. Open the JACE platform and log in. 2. Right-click the platform and select the Commissioning Wizard. Select the following and then click Next

45 Upgrading Siemens N4 Appliance Station Migrating the N4 Platform from Revision 4.2 to From the Licensing dialog box, select Install one or more licenses from files, and then choose the platform s license file and then click Next. 4. From the Enabled Runtime Profiles dialog box, select the following, and then click Next. 5. In the series of Station Installation dialog boxes, do the following: Select the station from the Saving the 4.2 N4 Appliance Station section, Step 2, and then click Next. Select Copy every file in the station directory and its subdirectories, and then click Next. Select Delete the existing directory before copying, and then click Next. 6. Follow the Commissioning Wizard prompts and accept the default settings. 7. Configure TCP/IP settings as appropriate for your system. The Commissioning Wizard process completes and the JACE reboots. 8. After the JACE reboots, navigate to Config\Services\TemplateService, double-click Template Service to view the Template Manager. Select \Siemens_Graphics_Assets\commonStrings, and then click Detach In the Detach dialog box, verify that the Remove Composite Slots box is checked, and then click Yes. 9. Navigate to Hierarchy\Apps\System\About and then double-click About. The Revision should display as The migration process is now complete

46 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to 1.10 Updating an Installed Station from N4 Appliance 1.00 to 1.10 Overview of the migrate_1_00_to_1_10 Program What the Program Does Removes vendorobjecttypesfile slots from all Siemens BacnetDevice components. These properties did not work as intended and generate nuisance warning messages. Adds new string constants required in px views. Updates a number of station components as defined in the Updates_1_10.bog file. HierarchyService: Replaces all hierarchy definitions to add Histories folders and work around some limitations in HierarchyService. TagDictionaryService: Replaces the Siemens tag dictionary. RoleService: Fixes ViewableHierarchy permissions in the sieoperator, sieintegrator, and sieadvancedoper role definitions. The process of replacing hierarchy definitions causes the Viewable Hierarchies entries to be deleted. This routine restores the Viewable Hierarchies entries. UserService: Fixes Role assignments in the example Siemens_Customer, Siemens_Balancer, and Siemens_Integrator user accounts. The process of replacing role definitions causes the role assignment entries to be deleted. This routine restores the entries. Replaces the SiemensUi/Apps folder with a new folder named viewhandle_donotremove. Replaces the siemensappliance:devicecredentials component. Updates SieUtilitiesService. Updates the revision number and revision notes. Copies the new files added in Revision What the Program does not do Check the migrated station for functionality and completeness. Fix the Viewable Hierarchies entries in user-defined role definitions in RoleService. Fix the Role assignments in user-defined User Account definitions in UserService. (Optional) Update installed devices to new template versions. These steps must be performed manually after running the migration program. A Note on Updating Device Templates If the station being migrated has devices that were integrated using revision 1.00 Siemens templates, you can choose whether or not to update the devices to revision 1.10 templates. In general, there is little reason to do so because the Revision 1.10 Update Database routine adds many of the new Revision 1.10 device template features

47 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to 1.10 NOTE: If existing devices are updated to new template versions, the devices will return to a newly integrated state, and any changes that were previously made will be lost. This includes history or alarm extensions that were added, mapped points that were added or removed, and graphics that were changed. The following sections outline how to keep existing 1.00 templates or update to 1.10 templates. Before You Begin Complete the following tasks before you begin the migration: 1. Back up your station using Station Copier, the Backup Station command, or both. 2. Upgrade Siemens Workbench and the target platform to Revision or later and apply the latest patches. 3. In the Siemens Workbench Nav bar, under My Host, expand Platform > Platform Administration. Verify that the Baja and Daemon versions are Revision or later. 4. Make a note of the System Home (SysHome) and User Home (UserHome) folder paths, which are needed later in the update process. 5. Shut down any stations running on the Siemens Workbench platform and close Siemens Workbench. 6. Unzip Siemens_Appliance_1_10_102.zip to a folder on your Siemens Workbench computer. Updating Modules 1. Using Windows File Manager, open the unzipped Siemens_Appliance_1_10_102/Siemens_Modules_1_10_102 folder. You should see the files shown in the following figure. 2. Copy the three.jar files to the SysHome/modules folder

48 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to 1.10 Adding Device Templates NOTE: Read and understand the section A Note on Updating Device Templates [ 46] before performing the steps in this section. If existing devices that were integrated using 1.00 templates will be updated to 1.10 templates: 1. Open the unzipped Siemens_Appliance_1_10_102/Siemens_Templates_1_10_100 folder. 2. Copy all files in this folder to UserHome/templates. If existing devices integrated using 1.00 templates will not be updated to 1.10 templates, do one of the following: 1. Copy the templates from your Siemens Workbench 4.2 UserHome/templates folder to your Siemens Workbench 4.3 UserHome/templates folder. 2. Copy the templates from Siemens_Appliance_1_00_102/Siemens_Templates_1_00_100 folder to your Siemens Workbench 4.3 UserHome/templates folder. Restarting the System 1. Restart the platform Daemon and Siemens Workbench. 2. Start the N4 Appliance Revision 1.00 station to be updated. Updating the Station to 1.10 Required Steps Complete the appropriate procedure for the station being updated: Updating a Station Running on a PC Platform [ 48] Updating a Station Running on a JACE Platform [ 52] Updating a Station Running on a PC Platform Copying Migration Files Using Windows File Manager, open the unzipped Siemens_Appliance_1_10_102/Siemens_Shared_1_10_102 folder, and then open the migrate_1_00_to_1_10 folder. You should see the files shown in the following figure

49 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to Double-click InstallMigrationFiles. The migration files are copied to the Siemens Workbench UserHome/shared directory. 2. In Siemens Workbench, under My Host/My File System, locate the UserHome folder. NOTE: The UserHome directory does not necessarily correspond to User Home under My File System! The relationship between UserHome as reported by Platform Administration and the My File System tree is shown in the following diagram

50 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to Open UserHome/shared/migrate_1_00_to_1_10. The migrate_1_00_to_1_10 folder should contain the files highlighted in the following figure. 4. Copy migrate_1_00_to_1_10.bog to the station s Config directory. A migrate_1_00_to_1_10 program component displays under Config

51 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to 1.10 Executing the Migration Utility 1. Right-click on the migrate_1_10_to_1_10 program and select Actions > Execute. Results display in Application Director and in LogHistory. 2. Delete Config/migrate_1_00_to_1_10 from the station after completion. Cleaning up and Updating the Database. 1. In the station, open TemplateService/TemplateManager and detach Siemens_Graphics_Assets/commonStrings. 2. Restart the station. 3. Run Update Database. For more details, see Updating Device Names and Hierarchies [ 95]. 4. Enable histories in HistoryService/History Ext Manager. 5. Run Add History Views. 6. Continue with the instructions Updating the Station to 1.10 Optional Steps [ 55]

52 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to 1.10 Updating a Station Running on a JACE Platform Updating Modules In Siemens Workbench, use Platform/Software Manager to update all out-of-date modules. Copying Migration Files 1. Open the JACE platform, and then open File Transfer Client. 2. In the left pane of File Transfer Client (Files on this computer), open the unzipped Siemens_Appliance_1_10_102/Siemens_Shared_1_10_102/migrate_100_to_1_10 folder. 3. In the right pane of File Transfer Client (Files on [jace address]), open the /home/niagara/shared folder. 4. Right-click in the right pane of File Transfer Client and select Create subdirectory. 5. Name the subdirectory migrate_1_00_to_1_ Double-click the new subdirectory to open it in the right pane. 7. Drag the following migration files one-at-a-time from the left pane and drop them on the right pane: Updates_1_10.bog migrate_1_00_to_1_10.bog The migration files are copied to the subfolder migrate_1_00_to_1_10 in the JACE shared directory

53 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to Open Platform/Remote File System/User Home/Shared/migrate_1_00_to_1_ Copy migrate_1_00_to_1_10.bog to the JACE station s Config folder. A migrate_1_00_to_1_10 program component now displays under Config

54 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to 1.10 Executing the Migration Utility From the station s Config folder, right-click on the migrate_1_10_to_1_10 program and select Actions > Execute. 1. Results display in Application Director and in LogHistory. 2. Delete Config/migrate_1_00_to_1_10 from the station after completion. Cleaning up and Updating the Database 1. In the station, open Config/Services/TemplateService/TemplateManager and detach Siemens_Graphics_Assets/commonStrings. 2. Restart the station. 3. Run Update Database. For more details, see Updating Device Names and Hierarchies [ 95]. 4. Enable histories in HistoryService/History Ext Manager. 5. Run Add History Views. 6. Continue with the instructions Updating the Station to 1.10 Optional Steps [ 55]

55 Upgrading Siemens N4 Appliance Station Updating an Installed Station from N4 Appliance 1.00 to 1.10 Updating the Station to 1.10 Optional Steps This procedure disables access to the Histories tree. This access is no longer needed because history views for station histories are now accessible in the Site, Devices, and AHU hierarchies. 1. Open Config/UserService/Siemens_Customer. 2. Under Default Web Profile set Enable Histories Tree to No. 3. Repeat this process for Config/UserService/Siemens_Balancer. Updating Installed Job Data Roles If the station includes any custom Role definitions, reconfigure the Viewable Hierarchies setting for each custom role. User Accounts If the station includes any custom User definitions, reconfigure the Roles setting for each custom user

56 Upgrading Siemens N4 Appliance Station Updating Installed Devices to Revision 1.10 Templates Optional Step Updating Installed Devices to Revision 1.10 Templates Optional Step A Note on Updating Device Templates If the station being migrated has devices that were integrated using revision 1.00 Siemens templates, you can choose whether or not to update the devices to revision 1.10 templates. In general, there is little reason to do so because the Revision 1.10 Update Database routine adds many of the new Revision 1.10 device template features. NOTE: If existing devices are updated to new template versions, the devices will return to a newly integrated state, and any changes that were previously made will be lost. This includes history or alarm extensions that were added, mapped points that were added or removed, and graphics that were changed. Only complete this procedure if you want to update device templates for installed devices. 1. To update device templates for installed devices, double-click on Config/Services/TemplateService. Template manager looks similar to the following figure. 2. Click Upgrade All Out of Date and then click Commit. Device templates for installed devices are now updated

57 Using the Siemens N4 Appliance Discovering Devices on the Network Using the Siemens N4 Appliance Discovering Devices on the Network Discovering BACnet Devices The Siemens Workbench is open. 1. From the Nav pane, select and expand Config, Drivers, BacnetNetwork, Views, and then select Bacnet Device Manager. 2. Click the Discover button at the bottom of the Database View pane. The Configure Device Discovery dialog box displays. 3. In the Device Low Limit and Device High Limit fields, enter a device instance number range for the discovery process. A list of discovered devices display within the range you define. 4. In the Networks section, select the Send Global? check box to discover devices on all connected BACnet networks. If you select one or more networks, you will receive discovered devices on all selected BACnet networks you define. NOTICE! The first time you perform the discovery procedure, you must select the Send Global? check box option. After the first successful discovery, discovered BACnet networks (for example, 1 through 77) are preselected, and it s generally not required to select the Send Global? check box again. 5. Leave the default setting for Wait Response Time and click OK. During the discovery process a progress bar displays at the top of the view and updates as the discovery occurs. Following the completion of the discovery process, a list of discovered devices then displays

58 Using the Siemens N4 Appliance Adding Controllers Adding Controllers NOTICE Devices must be added in the following order: 1. TNM/TC devices (field panels), LocalDeviceTC, or LocalDeviceTC. 2. AHU controllers (including UEC). 3. All other devices. Add a field panel or TNM before adding a UEC. Add an Ahu_UEC before adding VAV devices. Adding a Field Panel or UEC 1. From the Discovered list of installed device templates, select a TC Compact or Modular controller. 2. Select the Template Mode toolbar button to display the list of installed device templates. 3. Select one of the following in the Templates tab: If the device is a TC Compact or Modular controller that is performing AHU control, select Ahu_IP. If the device is a TC Compact or Modular controller that is not performing AHU control, select Panel_IP. If the device is a UEC that is performing AHU control, select Ahu_Uec. If the device is a UEC that is not performing AHU control, select GenericMstp

59 Using the Siemens N4 Appliance Adding Controllers 4. Click Add. NOTE: Select AHU_IP if the field panel controls an air handler that supplies air to pressure independent variable air volume controllers. 5. Follow the wizard prompts by selecting the site for the field panel and then the area. Click OK after each prompt. 6. The Template IO Bindings Results dialog box displays the configured relations. Click OK. 7. The Edit dialog box displays, click OK to leave default configuration settings. Adding a FLN Controller (non-vav) 1. From the Discovered list of installed device templates, select a FLN device you want to add. 2. From the Templates tab, select the corresponding template for the device application number from the list. For example, a fan coil application, App_ Click Add. Follow the wizard prompts by selecting the site for the device. 4. Click OK. 5. Select where the device is installed in the building. Since there is more than one area, a selection must be made. Click OK. 6. Select the device s parent field panel. If there is only one field panel, the panel is pre-selected. Click OK. The Siemens N4 Appliance has one preconfigured Day/Night schedule. The wizard prompts whether this schedule should be used to set the operating mode of the controller. If you want to use it, click OK. If not, de-select the schedule object and then click OK The Template IO Bindings Results dialog box displays the configured relations. Click OK

60 Using the Siemens N4 Appliance Adding Controllers 7. The Edit dialog box displays. Click OK to leave default configuration settings. 8. Repeat, as necessary, for any remaining controllers. Adding a VAV Device 1. From the Discovered list of installed device templates, select the VAV FLN device that you want to add. 2. From the Templates tab, select the corresponding template for the VAV device application number from the list. For example, App_ Click Add. Follow the wizard prompts by selecting the site for the VAV device. If there is only one controller, the site is pre-selected. 4. Click OK. 5. Select where the VAV device is installed in the building. Since there is more than one area, a selection must be made. Click OK. 6. Continue with the wizard prompts. 7. Select the controller s parent AHU field panel. If there is only one field panel, the panel is pre-selected. Click OK. 8. Select the required two references necessary from the VAV to the AHU. Select the AHU that supplies the VAV terminal box. Click OK. The Siemens N4 Appliance has one preconfigured Day/Night schedule for PTECs and one preconfigured Comfort/Economy schedule for DXRs. A prompt displays asking whether this schedule should be used to set the operating mode of the VAV controller. Selecting this option means that the schedule is stored at the station and it commands the Day/Night or Comfort/Economy modes directly. Assuming that this is desired, click OK. If not, de-select the schedule object and then click OK. If the schedule is to be maintained at the Siemens Field panel or another device, do not select this option. The Template IO Bindings Results dialog box displays the configured relations. 9. Click OK. 10. The Edit dialog box displays. Click OK to leave default configuration settings. 11. Repeat, as necessary, for any remaining VAV devices. Deleting an ALN or FLN Device In the Technical View, you can select and delete any ALN or FLN device from the database. The Siemens N4 Appliance station is open. In the Nav pane, select Hierarchy, Devices, select and right-click an ALN or FLN device, select Actions, and then select Delete. Device is deleted from the Siemens N4 database

61 Using the Siemens N4 Appliance Configuring Schedules Configuring Schedules This section outlines the following topics: The built-in schedules and schedule editor views. How to create additional schedules. How to synchronize station schedules with Schedule Objects in BACnet devices. NOTE: When you create or edit a calendar object, there are four data types you can choose from; Date, Date Range, Week and Day or Custom. You are able to use the first three data types if you are not using wildcard entries, however, the Custom data type is not available at this time. Built-in Schedules and Schedule Editor Views The N4 Appliance includes two predefined schedules, one day-night schedule for use with Siemens PTEC/ATEC controllers, and one operating mode schedule for use with Siemens controllers. Figure 15: Siemens Schedules. The predefined schedules are located in the Config/Siemens_Schedules folder. If additional schedules are needed, they should be added to this folder. The predefined schedules may also be accessed from the Apps hierarchy. This is typically how an end user would access the schedules in order to adjust times and modes at runtime

62 Using the Siemens N4 Appliance Configuring Schedules Siemens_Day_Ngt_Schedule The Siemens_Day_Ngt_Schedule is a Niagara Enum schedule with the following key characteristics: Table 1: Siemens_Day_Ngt_Schedule. Key Characteristic Notes Range of values DAY (0), NIGHT (1) Default Value Editor View Tags NIGHT Files/px/Siemens_Views/scheduleEditView.px sie:daynightschedule Scheduler View (scheduleeditview) The scheduler view is a standard N4 Appliance view with an embedded Niagara schedule editor plugin component. Use of this component is described in the Schedule plugins/scheduler section of the document Scheduling overview in Niagara Help. Figure 16: Siemens_Day_Night_Schedule Editor View. Default Weekly Schedule The default weekly schedule is DAY from 8:00AM to 5:00PM Monday through Friday, and default (NIGHT) for other days and times. Schedules are edited using the scheduler view

63 Using the Siemens N4 Appliance Configuring Schedules Default Special Event Days Default special event days are defined in the Siemens_Holiday_Calendar. On these days, the schedule will output its default value (NIGHT) for the entire 24 hour period. The output value during special event days may be edited using the scheduler view. Other Configuration Properties Figure 17: Siemens_Day_Night_Schedule Properties. Table 2: Siemens_Day_Ngt_Schedule. Property Default Output Facets Cleanup Special Events Notes An editable value that defaults to NIGHT. Defines the range of values for the schedule. DO NOT CHANGE THIS FACET! These values are defined in PTEC devices. If changed at the station, schedules will not work properly. Leave at the default value of true unless there is a specific reason to change it. If set to false, one-time special events are kept in the station database after they have occurred, even though they will not occur again. Tagging and Auto-Linking to New PTEC/ATEC Devices The default Siemens_Day_Night_Schedule is preconfigured with the sie:daynightschedule tag. N4 Appliance device templates for PTEC and ATEC applications include an optional link to a station schedule. When using BacnetDeviceManager to install a PTEC or ATEC using a Siemens template, one of the dialogs allows the user to select an existing schedule for auto-linking to the device s DAY.NGT point. The user may select a schedule from the list of compatible schedules or leave the DAY.NGT point unlinked by deselecting all schedules. Figure 18: BacnetDeviceManager Schedule Linking Dialog DAY.NGT. Notice in the Figure BacnetDeviceManager Schedule Linking Dialog (DAY.NGT), that there is only one entry in the list of available schedules, even though there are two predefined schedules in the N4 Appliance station. This is due to the fact that PTEC

64 Using the Siemens N4 Appliance Configuring Schedules and ATEC templates specify that only schedules with the sie:daynightschedule tag should be shown in the selection dialog. Only schedules that are compatible with Apogee DAY.NGT points should be given the sie:daynightschedule tag. Siemens_OpMode_Schedule The Siemens_OpMode_Schedule is a Niagara Enum schedule with the following key characteristics: Table 3: Siemens_OpMode_Schedule. Key Characteristic Notes Range of values Protect (1), Economy (2), PrComfrt (3), Comfort (4) Default Value Editor View Tags Economy Files/px/Siemens_Views/scheduleEditView.px sie:opmodeschedule Scheduler View (scheduleeditview) The scheduler view is a standard N4 Appliance view with an embedded Niagara schedule editor plugin component. Use of this component is described in the Schedule plugins/scheduler section of the document DocScheduling in Niagara Help. Default Weekly Schedule The default weekly schedule is Comfort from 8:00AM to 5:00PM Monday through Friday, and default (Economy) for other days and times. Schedules are edited using the scheduler view. Default Special Event Days Default special event days are defined in the Siemens_Holiday_Calendar. On these days, the schedule will output its default value (Economy) for the entire 24-hour period. The output value during special event days may be edited using the scheduler view

65 Using the Siemens N4 Appliance Configuring Schedules Other Configuration Properties Default Output An editable value. Default: Economy. Cleanup Expired Events Leave at the default value unless there is a specific reason to change it. Default: True. If set to False, one-time special events are kept in the station database after they have occurred, even though they will not occur again. Facets Defines the range of values for the schedule. DO NOT CHANGE THIS SETTING! These values are defined in System ONE devices. If changed at the station, schedules will not work properly. Tagging and Auto-Linking to New System ONE Devices The default Siemens_OpMode_Schedule is preconfigured with the sie:opmodeschedule tag. N4 Appliance device templates for DXR and RDY applications include an optional link to a station schedule. When using BacnetDeviceManager to install a DXR and RDY using a Siemens template, one of the dialogs allows the user to select an existing schedule for auto-linking to the device s RM_OP_MODE point (Schedule_Mode for RDY devices). The user may select a schedule from the list of compatible schedules or leave the RM_OP_MODE point unlinked by deselecting all schedules

66 Using the Siemens N4 Appliance Configuring Schedules Notice that in the Figure BacnetDeviceManager Schedule Linking Dialog (RM_OP_MODE), there is only one entry in the list of available schedules, even though there are two predefined schedules in the N4 Appliance station. This is due to the fact that DXR and RDY templates specify that only schedules with the sie:opmodeschedule tag should be shown in the selection dialog. Only schedules that are compatible with System ONE operating mode points should be given the sie:opmodeschedule tag. Creating Additional Schedules Siemens_Day_Ngt_Schedule To create additional schedules intended for use with PTEC/ATEC DAY.NGT points, duplicate Config/Siemens_Schedules/Siemens_Day_Ngt_Schedule and configure as necessary. Duplicating an existing schedule will assure that the new schedule has the correct tagging and enumerated value range. The new schedule will also use the same special event calendar as the original. Do not under any circumstances change the range facet on the schedule s Properties tab. Doing so will cause the schedule to work improperly. Also, do not remove the sie:daynightschedule tag. Doing so will keep the new schedule from appearing in the BacnetDeviceManager wizard (see the section Siemens_Day_Ngt_Schedule [ 63]). Siemens_OpMode_Schedule To create additional schedules intended for use with System ONE ROOM_OP_MODE points (Schedule_Mode for RDY devices), duplicate Config/Siemens_Schedules/Siemens_OpMode_Schedule and configure as necessary. Duplicating an existing schedule will assure that the new schedule has the correct tagging and enumerated value range. The new schedule will also use the same special event calendar as the original. Do not under any circumstances change the range facet on the schedule s Properties tab. Doing so will cause the schedule to work improperly. Also, do not remove the sie:opmodeschedule tag. Doing so will keep the new schedule from appearing in the BacnetDeviceManager wizard (see the section Siemens_OpMode_Schedule [ 65])

67 Using the Siemens N4 Appliance Configuring Schedules Other Schedules To create schedules for other purposes, create a new folder under Config and copy a schedule of the appropriate type from the schedule palette to the new folder. Configure the new schedule as necessary. See the document DocScheduling in Niagara Help for instructions. Sychronizing Station Schedules with BACnet Schedule Objects The sections Built-in Schedules and Schedule Editor Views [ 61] and Creating Additional Schedules [ 66] cover configuration and use of schedules running in the N4 Appliance station. This approach works in all cases. However, many BACnet devices include BACnet Schedule Objects, allowing them to provide scheduling of local BACnet objects and in some cases remote BACnet objects. Local BACnet objects are defined as objects on the same device as the Schedule object. Remote BACnet objects are defined as objects in devices other than the device with Schedule object. The ability to schedule local objects is referred to as local scheduling. The ability to schedule remote objects is referred to as remote scheduling. Table 4: Scheduling Capabilities by Device. Device TalonTC Talon PTEC/ATEC System ONE DXR/RDY Feature Local Scheduling, Remote Scheduling No scheduling Local Scheduling In Niagara system, it is possible to leave the scheduling capabilities of BACnet devices unused and to use Niagara station schedules exclusively. However, if use of BACnet schedules is required, it is possible to synchronize these BACnet schedules with station schedules, thereby allowing the N4 Appliance schedule editor views to edit the BACnet schedules. In addition, a single N4 station schedule may be synchronized with multiple BACnet schedules, thereby coordinating the operation of the linked BACnet schedules

68 Using the Siemens N4 Appliance Configuring Schedules The BACnet Schedule Export Manager BACnet schedule synchronization is configured using the BACnet Schedule Export Manager. 1. Right-click on a BACnet device with one or more schedule objects and then select Actions > Bacnet Schedule Export Manager. 2. In the BACnet Discover Schedules pane, click Discover. The Discovered pane is populated with the device s BACnet Schedule objects. 3. Do the following to use the weekly and exception schedules from an N4 station schedule to initialize the BACnet Schedule object: Select a schedule object to synchronize and then click on the down arrow next to the Add button and select Niagara

69 Using the Siemens N4 Appliance Configuring Schedules The Add dialog box is displayed. In the Supervisor Ord field, select the station schedule that will be used as a master. 4. Configure the following additional items in the Add dialog box: Priority for Writing: Default: 16 (lower values indicate higher priority). Increase the scheduler priority so that scheduler commands are at a higher priority than control program commands. Execution Time: Default: The schedule is sent to the panel every five minutes. Since schedules are edited infrequently, increase the Interval so that the schedule is sent less often. 5. Click OK to save your changes and close the dialog box

70 Using the Siemens N4 Appliance Configuring User Accounts Configuring User Accounts This section outlines the process for creating job-specific user accounts in an N4 Appliance station. Default Configuration The N4 Appliance UserService provides three example user accounts, each with a predefined user role and Web UI profile. The purpose of these default accounts is to simplify the process of creating job-specific user accounts. Table 5: Example User Accounts. Account Role Web UI Profile Siemens_Customer sieoperator Limited to Operation and Monitoring Tasks The Siemens_Customer account is preconfigured for users that are limited to everyday operation and monitoring of the building system. Account Role Web UI Profile Siemens_Balancer sieadvancedoper Limited to Operation and Monitoring Tasks The Siemens_Balancer account is preconfigured for advanced users that may perform a limited set of configuration tasks along with everyday operation and monitoring of the building system. Account Role Web UI Profile Siemens_Integrator sieintegrator Full access to all Workbench Web functions The Siemens_Integrator account is a superuser account equivalent to the built-in Niagara admin account. Siemens_Integrator provides access to system engineering and configuration functions along with everyday operation and monitoring of the building system. Creating Job-Specific User Accounts The sections below describe the process for creating an example set of job-specific user accounts. The example user accounts are as follows: Table 6: Example Job-Specific User Accounts. Account Name Based on bboiler Bob Boiler Siemens_Customer fhood Flo Hood Siemens_Balancer jtalon Joe Talon Siemens_Integrator Creating New Accounts This procedure creates a new account for Bob Boiler. 1. Right-click on the Siemens_Customer account and click Duplicate. 2. Name the new account bboiler. 3. Open AX PropertySheet for bboiler and configure the account. 4. Set the Password to a default value and set Force Reset At Next Login to true. 5. Set Enabled to true. The AX Property Sheet should appear as shown in the following figure

71 Using the Siemens N4 Appliance Configuring User Accounts Figure 19: Bob Boiler User Account. 6. Set other fields as necessary, then click Save. 7. Repeat this procedure for fhood and jtalon

72 Using the Siemens N4 Appliance Configuring User Accounts Figure 20: Completed User Accounts. Disable or Delete Example Accounts After adding the new accounts, the best practice is to disable the example accounts so that they cannot be used to log in to the system. In UserService, open the AX Property Sheet for each of the accounts listed in the Table Example Job-Specific User Accounts and set Enabled to false. Figure 21: Disabling Example User Accounts

73 Using the Siemens N4 Appliance Populating Summary Views Populating Summary Views Summary Views can be populated for many levels of an hierarchy, such as club level, entrance level, device level, AHU level, and so on. You can also duplicate the template to create an AHU-specific Summary in the Operator View, and then drag and drop the desired discovered devices onto the Summary View, applying application-specific Summary bar widgets. There are two types of Summary Views: Field panel or TNM controller UEC as an AHU NOTE: If summary views were created during definition of the site structure, use the instructions in this section to populate the views. The example below covers a summary view

74 Using the Siemens N4 Appliance Populating Summary Views 1. Open the Summary View by double-clicking on an area or panel and click Edit in the toolbar. 2. From Nav pane, expand Hierarchy, AHU. If all of the VAV boxes supplied by this AHU have controllers with the same application, then select and drag all desired VAV terminal boxes supplied by this AHU onto the Summary View pane. If the VAV boxes supplied by this AHU have controllers with different applications, then repeat this process for each VAV application. The Make Widget dialog box displays. 3. In the Make Widget dialog box, ensure that Include Px File is selected. Click the drop-down arrow to the right of the folder icon and then select File Ord Chooser. You must use the File Ord Chooser to reselect the file even if the desired file already displays in the Choose Px File dialog box. 4. In the File Chooser dialog box, under the File Space section, select Files on Station. Double-click the PX folder and then open the deploy folder. From the deploy folder, select the folder that has the device s application number in its name, and then click Open

75 Using the Siemens N4 Appliance Populating Summary Views 5. Select the Summary_[app_#.px] file in that folder. There is only one summary file per folder. 6. In the Make Widget dialog box, in the Select Pxfile variables to bind: section, highlight the item and then click OK. NOTICE! If this item is not highlighted in the summary bar, it will not populate with data. 7. Position the summary element and then from the toolbar, click the Save icon. 8. From Hierarchy, select AHU, [the building], right-click px8803 and select Views and Summary to view the results

76 Using the Siemens N4 Appliance Operator View Operator View A default Operator View template is provided to give you a standard graphical layout. The template can be customized to your specific requirements. Existing Schedules in Operator View Existing Schedules The Siemens N4 Appliance Schedule Editor in Operator View is a browser-hosted editor that allows you to view and edit pre-existing Niagara schedules created using Siemens Workbench. The following schedule types are supported: Local schedules that run in the station, independent of Schedule objects in BACnet devices. Local schedules that run in the station and are linked to Schedule objects in BACnet devices by the BACnet Schedule Export Manager. When the schedule editor modifies a local Niagara schedule that is linked to a BACnet schedule by the Export Manager, all linked BACnet schedules are updated. Figure 22: Exported Schedules. NOTE: When you create or edit a calendar object, there are four data types you can choose from; Date, Date Range, Week and Day or Custom. You are able to use the first three data types if you are not using wildcard entries, however, the Custom data type is not available at this time. NOTE: Using the every year wildcard will result in an error when synchronizing with the Siemens field panel. Schedule Selection Appliance schedules are found in the Apps/Schedules folder. Selecting any of these schedules opens the Schedule Editor in Operator View. Schedule Editor in Operator View The Schedule Editor in Operator View is a standard N4 Appliance template view with the native N4 schedule editor in the View pane

77 Using the Siemens N4 Appliance Operator View Weekly Schedule Tab Special Events Tab

78 Using the Siemens N4 Appliance Operator View Editing a Schedule or Calendar Object You can discover and edit existing schedule and calendar objects in Siemens field panels. This procedure assumes you have existing schedule and calendar objects in a TC Compact or Modular controller. NOTE: When you create or edit a calendar object, there are four data types you can choose from; Date, Date Range, Week and Day or Custom. You are able to use the first three data types if you are not using wildcard entries, however, the Custom data type is not available at this time. 1. From the Nav pane, select and expand Hierarchy, Apps, Schedules, and then select schedule or calendar object. 2. Double-click the selected schedule or calendar. The schedule displays in the Schedule Editor window/view. 3. From the upper-right corner, select the Edit Schedule drop-down menu, and then select Edit Schedule. 4. Enter the modifications you wish to make for the schedule or calendar, and then click Save. If editing a calendar and entering the wildcards for a holiday, the holiday dates will overwrite the field panel s calendar object. This is visible through BACnet Object browser or other application such as Field Panel Web UI (FP Web)

79 Using the Siemens N4 Appliance Operator View Opening the Alarm Console The main console operator view consists of a standard placeholder view with the Niagara-native AlarmConsole display in the View pane. The Siemens N4 Appliance station is open. In the Nav pane, select and expand Hierarchy, Apps, Alarms, right-click MainConsole, select Views, and then Alarms Manager. NOTE: You can also open the Alarm Console by clicking the Alarms or Unacked counter in the header Name of the BACnet device. Name of the station numeric point. Alarm class assigned to the device and the priority assigned to the alarm class.. Alarm class assigned to the point s alarm extension and the priority assigned to the alarm class. Standard Niagara alarm message for network connectivity loss. Alarm message assigned to the point s alarm extension

80 Using the Siemens N4 Appliance Operator View Using the Charting View Feature The Charting View feature, in Operator View, allows you to quickly view real-time and historical values in a graphical stripchart format. It is generic, with a standard native Niagara dashboard using the chart control from the WebChart palette. There is only one Chart View. To create additional Chart Views, for example for each device in the system, a dashboard view can be created and added to each device or to one or more device templates. Opening the Charting View The Siemens N4 Appliance station is open. In the Nav pane, select and expand Hierarchy, Apps, Charting, and then Chart View. Adding a History Extension to a Point 1. Select a point that you want to add a history extension. Right click on that point and select View > AX Property Sheet. 2. Click on Palatte and find the history palate. 3. Select the appropriate extension under the Extensions folder and drag it to the AX property sheet. 4. Expand the history extension select Enabled: True. 5. Make any other desired configuration changes. 6. Select Save

81 Using the Siemens N4 Appliance Operator View Viewing History Chart and History Table Views The appliance has customer History Chart and Table views. They can be accessed from the Histories folder for any device in the Hierarchy. Points will only display in this folder if all of the following are true: Have a History Extension. Update Database and Add History Views were run after the History Extension was added. For more details, see Updating Device Names and Hierarchies [ 95] Once the points have a History Extension right click on them and select History Chart view or History Table view Adding Real-Time Point Values without a History Extension From the Hierarchy tree, select one or more points and then drag-and-drop onto the chart. No historical point information displays; only the point name. Adding Real-Time Point Values with a History Extension From the Hierarchy tree, select one or more points and then drag-and-drop them onto the chart. The history name displays, instead of the point name. NOTE: Use the same step to see native Niagara point history information

82 Using the Siemens N4 Appliance Customizing the Logos Customizing the Logos The following logos can be customized: The logo displayed on the logon screen. The logo displayed in the header of the work area. Customizing the Logon Screen Logo This procedure customizes the logo displayed on the login screen. By default, when you login to the station using an Operator View (browser window), the Siemens logo displays. For more information, see the Tridium Web site for supporting documentation. You have created and saved a custom image you want to use on the logon screen. Note: The file must be named logo.jpg. 1. Copy your logo image to the file system of the station. The typical path is C:\Users\[your user name]\niagara4.x\tridium<stationname>\shared. 2. Rename the existing logo.jpg file. For example, logo_old.jpg. 3. In the Nav pane, drag your logo image from My File System\UserHome\Stations\<StationName>\shared folder and drop it in the station Files folder

83 Using the Siemens N4 Appliance Customizing the Logos 4. Restart the station and then logon through the Operator View (browser window) to view your customized logon screen

84 Using the Siemens N4 Appliance Customizing the Logos Customizing the Header Logo This procedure customizes the logo displayed in the header of the work area. For more information, see the Tridium Web site for supporting documentation. You have created and saved a custom image you want to use in the header of the work area. Note: The header logo file must be named headerlogo.png. 1. Copy your header logo image to the file system of the station. The typical path is C:\Users\[your user name]\niagara4.x\tridium<station Name>\shared. 2. Rename the existing headerlogo.jpg file. For example, headerlogo_old.jpg. 3. In the Nav pane, drag your header logo image from My File System\UserHome \Stations\<StationName>\shared folder and drop it in the station Files folder. 4. Restart the station and then open an application to see the customized header

85 Using the Siemens N4 Appliance Configuring and Using Siemens Launch Pad Configuring and Using Siemens Launch Pad NOTE: Use of Siemens Launch Pad within Siemens Workbench or a Niagara station is subject to the same requirements as use of Launch Pad as a standalone application. Siemens Launch Pad must be installed on the Siemens Workbench computer before performing the steps listed in this section. See the Siemens Launch Pad User Guide ( T) for details. If providing access to Siemens Launch Pad is not desired, or if the system does not include TC series controllers, links to Launch Pad may be removed by following the instructions in the Disabling Launch Pad Integration [ 88] section. Configuring Siemens Launch Pad The Siemens Workbench is open. 1. From the Tools menu, select Siemens Launch Pad Configuration. The Launch Pad Configuration dialog box displays. 2. In the Executable path field, enter a path or browse to a location on your hard drive where the Siemens Workbench is installed. Click OK. The SiemensAppliance.ini file is created on C:\Users\[your user name]\ AppData\Roaming\Siemens\siemensAppliance\. The Launch Pad Configuration dialog box closes. NOTICE! If you click Cancel or close the dialog, all changes are discarded. Starting Launch Pad The Siemens Workbench is open. 1. From the Tools menu, select Siemens Launch Pad. Siemens Launch Pad opens. 2. If the configuration procedure was not properly done or if the executable path is empty or incorrect, the following error message(s) display. Correct the error and click OK

86 Using the Siemens N4 Appliance Configuring and Using Siemens Launch Pad Configuring Station Links to Launch Pad Editors NOTE: Before proceeding with this procedure, be sure you have properly configured the Siemens Launch Pad. Devices must be first added to Siemens N4 database and configured properly. 1. From the Nav pane, select and expand Station, Config, Drivers, and then select Bacnet Network. 2. Double-click DeviceCredentials. 3. Enter the Username and password that will be used by the station to login to Siemens field panels and then click Save. NOTICE In order to create station links to Launch Pad editors, you must run Update Database with Add Field Panel Relations selected. If this was done previously, it s not necessary to run Update Database again. For more details, see Updating Device Names and Hierarchies [ 95]. 4. Navigate to Station, Hierarchy, Database, and then select the Update Database view. Ensure that the Add Field Panel Relationships is selected. During the update process, a relation is added in the FLN device(s) to associate it to its supervised field panel. NOTICE! This step is only necessary if the Add Field Panel Relations check box was not selected when the devices were initially added

87 Using the Siemens N4 Appliance Configuring and Using Siemens Launch Pad The FLN device field panel relationship is added. Editing Points and PPCL Programs The Editors hierarchy provides context-sensitive access to Siemens Launch Pad point and PPCL editors. The Editors hierarchy provides access to the following features of Siemens Launch Pad

88 Using the Siemens N4 Appliance Configuring and Using Siemens Launch Pad Feature Siemens Launch Pad PPCL Editor Point Editor Point Table Editor Point Commander Applies to TC, PTEC, ATEC, UEC TC, UEC PTEC, ATEC TC, and all BACnet devices supervised by a TC (PTEC, ATEC, UEC, DXR, RDY, third-party) To access device-level functions (PPCL Editor, Point Table Editor), right-click on the relevant item in the device s Configuration submenu. To access point-level functions (Point Editor, Point Commander), right-click on a point in the device s Points submenu. The Editors hierarchy only displays devices and features that are accessible in Siemens Launch Pad. Disabling Launch Pad Integration The following procedure removes the Editors hierarchy from the station. The choice to remove the Editors hierarchy may be based on the following: Launch Pad functionality depends on the existence of TC series controllers. If the job does not include TC series controllers, then Launch Pad integration should be disabled. Jobsite or integrator preference. The Siemens Workbench is open. 1. From the Nav pane, select and expand Station > Config > Services > HierarchyService. 2. Right-click on Editors and select Delete. 3. Right-click Hierarchy and select Refresh Tree Node

89 Configuring a Landing Page 0 Configuring a Landing Page This procedure sets the view when you first log in to the station. 1. Right-click Files, New, and then select NavFile.nav to add the landing page (default background graphic). 2. In the Name for New File field, enter homepage.nav and then click OK. This is the homepage.nav file. 3. Expand the Files folder, right-click homepage.nav, and select Views, Nav File Editor. 4. Select the Home icon and click Edit. 5. In the Edit dialog box, configure the.nav file as follows: Display name field: Home. Target Ord field: For example, Station: slot:/siemens_site/demosite (where DemoSite is the site name), or click the drop-down folder to browse and select the site. Icon field: Default is, module://icons/x16/home.png. 6. Click OK. The controller set-up is complete

90 0 Uninstalling Siemens Workbench Uninstalling Siemens Workbench NOTE: This procedure assumes you have a Siemens Workbench 4.x.x.x shortcut in your Windows Start menu. If not, then you must launch the uninstall program from the Installation folder on your hard drive. 1. From the Windows Start menu, select All Programs > Siemens Workbench 4.x.x.x folder > Uninstall. The Siemens Workbench Uninstall Program opens. 2. Click Next. A confirmation screen displays when the uninstallation is complete. 3. Click Finish

91 Advanced Topics Adding a LocalDeviceAhu object to the station Advanced Topics Adding a LocalDeviceAhu object to the station NOTE: Only complete this procedure if the configuration does not use a Siemens field panel. For example, if FLN devices are connected directly to MS/TP ports of the TNM controller. It is recommended that you restart the station after adding a TNM controller. If the N4 station is acting as both a supervisory controller and an air handling unit controller, see the topic Adding a LocalDeviceAhu object to the station [ 91] in Advanced Topics. When is a Station Local Device Needed? When the N4 station is acting as both a supervisory controller and an air handling unit controller, a LocalDeviceAhu object should be added to the station. The LocalDeviceAhu object contains a preconfigured rollup graphic and algorithm. For instructions, see the topic Adding a LocalDeviceAhu object to the station [ 92] in this section. Figure 23: Supervisory Controller and AHU Controller Example Topology

92 Advanced Topics Adding a LocalDeviceAhu object to the station When is a LocalDeviceAhu Object Not Needed? A LocalDeviceAhu virtual AHU controller object is not needed if the station is not responsible for AHU control. UEC AHU examples are shown in the following figure. Figure 24: AHU Example Topologies. Configuring a Station Local Device The LocalDeviceAhu template is used to create virtual ALN devices representing controllers performing both supervisory and AHU control. The LocalDeviceAhu template includes the hs:equip, hs:ahu and sie:alndevice tags. 1. Connect to the station using Siemens Workbench. 2. Open the Template sidebar 3. Drag the LocalDeviceAhu template onto the Config/SiemensUi folder

93 Advanced Topics Adding a LocalDeviceAhu object to the station 4. Follow the wizard prompts to select the site and area, just as you would for any other device. The LocalDeviceAhu object displays in the Site, Devices, and AHU hierarchies, in place of a UEC or other device used for AHU control

94 Advanced Topics Adding a LocalDeviceAhu object to the station Using Station Local Devices After a LocalDeviceAhu object is added, representing a virtual field panel, the process of integrating BACnet FLN devices using BACnet Device Manager is identical to the process used with a real field panel.remember that, just like with real BACnet field panels and AHU controllers, LocalDeviceTc and/or LocalDeviceAhu virtual controllers must be added first, followed by FLN devices

95 Advanced Topics Updating Device Names and Hierarchies Updating Device Names and Hierarchies 1. From the Nav pane, under the appropriate station, expand Config, Hierarchy, Database. 2. Double-click Update Database. 3. In the Database Configuration Parameters area, select the options you want applied to the database. See the following table for details on each option. 4. When you re finished, click Update Database. 5. Right-click Hierarchy and select Refresh Tree Node. The display name updates on the screen. 6. Expand the Hierarchy tree to display the results of the navigation hierarchy