lcs85 commissioning guide - johnson controlscgproducts.johnsoncontrols.com/met_pdf/12011568.pdf ·...

LIT-12011568

Release 10.1

Building Technologies & Solutions

www.johnsoncontrols.com

2019-10-14

LCS85 Commissioning Guide

ContentsContentsDocument introduction................................................................................................................. 7

Summary of changes.......................................................................................................................... 7

Related documentation................................................................................................................. 7

LCS85 commissioning overview................................................................................................... 8

LCS85 servers....................................................................................................................................... 8

LCS85 Commissioning......................................................................................................................... 8

LCS85 configuration.......................................................................................................................... 10

Site Management Portal user interface.......................................................................................... 11

Metasys UI........................................................................................................................................... 12

Metasys System Help......................................................................................................................... 12

Browser recommendations for downloading the launcher......................................................... 12

System Configuration Tool............................................................................................................... 12

SCT Pro................................................................................................................................................ 13

Archive databases............................................................................................................................. 13

Site Director........................................................................................................................................ 13

LCS85 computer name...................................................................................................................... 14

LCS85 object name............................................................................................................................ 14

Basic Access operating mode.......................................................................................................... 14

Login user names and passwords................................................................................................... 15

LCS85 connectivity............................................................................................................................. 15

Time zone, date, and time management....................................................................................... 15

Alarm and events............................................................................................................................... 15

Serial Printer DDA (Alarm Printer)................................................................................................... 16

Serial Printer installation considerations............................................................................. 17

Syslog DDA......................................................................................................................................... 17

Email notification............................................................................................................................... 20

Pager notification.............................................................................................................................. 21

SNMP notification.............................................................................................................................. 22

Initial default LCS85 configuration.................................................................................................. 22

System and user preferences.......................................................................................................... 23

Detailed procedures..................................................................................................................... 23

Commissioning requirements......................................................................................................... 23

Commissioning guidelines............................................................................................................... 24

Commissioning the LCS85................................................................................................................ 24

Adding a third party integration...................................................................................................... 25

Changing the LCS85 name and the computer name.................................................................... 27

Changing the LCS85 name and the computer name - overview...................................... 27

Preparing the computer........................................................................................................ 27

Creating a new archive........................................................................................................... 28

Downloading the LCS85......................................................................................................... 29

Testing the LCS85.................................................................................................................... 30

Licensing the LCS85........................................................................................................................... 30

Using Launcher to discover an LCS85............................................................................................. 31

Logging on to the LCS85.................................................................................................................. 32

Preparing an LCS85 for an Ethernet LAN that supports DHCP and DNS.................................... 34

Preparing an LCS85 for an Ethernet LAN without DHCP and without DNS support(LCS85 uses static IP address)................................................................................................ 37

Preparing the LCS85 for serial printing.......................................................................................... 39

Enabling the serial printer DDA....................................................................................................... 39

Enabling Syslog reporting................................................................................................................ 44

Creating Audit Entries for Discarded Events.................................................................................. 46

LCS85 Commissioning Guideii

Accessing the Site Management Portal UI on an LCS85............................................................... 46

Establishing basic LCS85 parameters in the Focus screen........................................................... 47

Establishing the LCS85 network parameters................................................................................. 48

Creating Email Alarm and Event Notifications and Destinations................................................ 49

Configuring encrypted email........................................................................................................... 54

Configuring encrypted email with no authentication required........................................ 54

Configuring encrypted email with SMTP authentication................................................... 55

Configuring encrypted email with POP-before-SMTP authentication.............................. 55

Creating Pager Alarm and Event Notifications and Destinations................................................ 56

Creating LCS85 SNMP Alarm Notifications and Destinations...................................................... 60

Setting the time, date, time zone, and time synchronization...................................................... 63

Setting up the LCS85 alarm parameters......................................................................................... 63

Editing the Existing Alarm Parameters................................................................................ 63

Creating a New Alarm............................................................................................................ 65

Designating an LCS as a child of a Site Director............................................................................ 66

Changing the Site Director with the SCT.............................................................................. 68

Removing user accounts from a demoted Site Director.............................................................. 68

Moving the Security database and clearing it from the demoted SiteDirector prior to Release 6.0................................................................................................... 69

Moving the Security database and clearing it from the demoted SiteDirector at Release 6.0 or later............................................................................................... 69

Printing information from the LCS85 Site Management Portal UI.............................................. 70

Replacing an LCS85........................................................................................................................... 70

Troubleshooting........................................................................................................................... 71

Common LCS85 problems................................................................................................................ 71

Login problems....................................................................................................................... 71

iiiLCS85 Commissioning Guide

Network connection related problems................................................................................ 71

LCS85 reset related problems............................................................................................... 71

Troubleshooting guide........................................................................................................... 71

LCS85 diagnostic tools...................................................................................................................... 74

Diagnostic tab......................................................................................................................... 75

Summary tab........................................................................................................................... 77

Troubleshooting procedures........................................................................................................... 78

Verifying Ethernet/IP network communications (Ping)..................................................... 78

Determining the IP address.................................................................................................. 79

LCS85 technical specifications.................................................................................................... 82

Appendix: configuring and maintaining preferences............................................................. 84

Preferences concepts........................................................................................................................ 84

System and user preferences................................................................................................ 84

Managing preferences........................................................................................................... 86

Detailed Procedures.......................................................................................................................... 87

Configuring preferences........................................................................................................ 87

Restoring default system preferences................................................................................. 87

Copying preferences between devices................................................................................ 87

Restoring default user preferences...................................................................................... 88

Removing user preference files............................................................................................ 88

Copying user preferences to another user.......................................................................... 88

Preserving preferences in an upgrade................................................................................. 89

Appendix: time zone, date, and time management................................................................ 89

Overview of Time Synchronization.................................................................................................. 90

ADS/ADX/ODS Site Director with LCS85s............................................................................. 90

LCS85 Commissioning Guideiv

Time Synchronization Methods....................................................................................................... 91

Windows Time Synchronization............................................................................................ 91

Multicast Time Synchronization............................................................................................ 91

BACnet Time Synchronization............................................................................................... 91

Example Network.............................................................................................................................. 92

Time Zone........................................................................................................................................... 92

Site Time Server................................................................................................................................. 93

Time in Device Object and SMP UI Status Bar............................................................................... 93

Steps for Successful Time Management........................................................................................ 93

Verifying the Site Director Defined for an Engine or Server.............................................. 94

Setting the Time Synchronization Method.......................................................................... 94

Configuring Time Settings in the Site Director LCS85........................................................ 95

Configuring Time Settings in the Site Director ADS/ADX/ODS......................................... 98

Configuring Additional Multicast Time Synchronization Settings.................................. 102

Single point of contact............................................................................................................... 104

Product warranty........................................................................................................................ 104

Software terms........................................................................................................................... 104

vLCS85 Commissioning Guide

Document introductionThis document describes how to commission a LonWorks® Control Server (LCS) 85 for operation ona Metasys® Building Automation System (BAS) network.This document does not describe how to build or download an archive database for a Metasys®system site or how to configure an LCS85 to monitor and control a specific BAS network or networkdevices.

Summary of changes

The following information is new or revised:The Software Manager application replaces the Software Application Manager (SAM) applicationthat was previously provided with licensable software. The reference to SAM has been updated inthe document to Software Manager.

Related documentationTable 1: LCS85 related documentationFor Information On See DocumentCreating, Editing, and Loading ArchiveDatabases with the SCT Metasys SCT Help (LIT-12011964)

Daily Operation of the Metasys System Network,Navigating the User Interface, Monitoring andControlling BAS Networks, and Connecting toCloud-Based Applications

Metasys Site Management Portal Help(LIT-1201793)

Integrating LonWorks Network with LCS85 LonWorks Network Integration with NAE and LCSTechnical Bulletin (LIT-1201668)

Installing LCS85 Software and Upgrading anLCS85 Server (includes Upgrading the LonWorksSoftware Driver)

LCS85 Installation and Upgrade Instructions(LIT-12011623)

General Network and Information TechnologyDefinitions and Concepts

Network and IT Guidance Technical Bulletin(LIT-12011279)

Security Issues, Including Adding Users andRoles to the System, and Configuring Standardand Basic Access Modes

Security Administrator System Technical Bulletin(LIT-1201528)

Installing the Launcher Application Launcher Installation Guide (LIT-12011783)Using the Launcher Application Launcher Tool Help (LIT-12011742)Creating an configuring a KNX third partyintegration

Network Engine Commissioning for KNX VendorIntegration Application Note (LIT-12013148)

Creating an configuring an M-Bus third partyintegration

Network Engine Commissioning for M-Bus VendorIntegration Application Note (LIT-12013149)

Creating an configuring a Modbus third partyintegration

Network Engine Commissioning for ModbusVendor Integration Application Note(LIT-12013150)

Creating an configuring a C•CURE-victor thirdparty integration

Network Engine Commissioning for C•CURE-victorintegration (LIT-12013151)

7LCS85 Commissioning Guide

Table 1: LCS85 related documentationFor Information On See DocumentLicensing the LCS85 Software Manager Help (LIT-12012389)

LCS85 commissioning overview

LCS85 servers

LCS85 servers provide supervisory-level control of Metasys networks that include a large number ofLonWorks® network system devices and BACnet© TCP/IP devices.The LCS85 provides the following:

• monitoring and control of BAS field devices using LonWorks and BACnet network protocol

• a web-based user interface using Hypertext Transfer Protocol Secure (HTTPS)

• web services for access to data and services in the LCS85

• LonWorks 852 tunneling device area network protocols over IP

• support of CEA-709.1B control network protocols through attached LonWorks IP routers

• support of 10,000 objects, and up to 25,000 objects with a 15,000 object upgrade

• standard protocol clients:

- Simple Network Management Protocol (SNMP) for network device management

- Simple Network Time Protocol (SNTP) for time and date synchronization

- Simple Mail Transfer Protocol (SMTP) for sending email notification of alarms and events

• routing of event and alarm notification to an Application and Data Server/Extended Applicationand Data Server (ADS/ADX) or Open Data Server (ODS)

• the capability to send event and alarm notifications to pager and email destinations directly

• data collection, trend sampling, and audit trail logging

The LCS85 supports only one language at a time. A Metasys system site must have the samelanguage for every LCS85 on the site.

LCS85 Commissioning

LCS85 commissioning includes preparing the LCS85 for connectivity, connecting to the LCS85,adding the LCS85 to the profile list in Launcher, and accessing and logging in to the SiteManagement Portal (SMP) UI.Each Metasys network installation, commissioning, and configuration scenario is unique. In somescenarios, the LCS85 (on a Metasys network) may be commissioned and configured before itis connected to the network; in other scenarios, the LCS85 is wired to the network before it iscommissioned and configured.The commissioning tasks, the task order, and the required attribute values (at commissioning)for an LCS85 are determined by the specific Metasys network installation, commissioning, and

LCS85 Commissioning Guide8

configuration scenario for the site. The LCS85 commissioning procedures presented in thisdocument are the procedures required for most scenarios regardless of when commissioningoccurs.The first task in commissioning an LCS85 is to use the Launcher application to establish aconnection with the LCS85. You must install the Launcher if it is not already installed on yourcomputer. Refer to the Launcher Installation Guide (LIT-12011783) if needed.

Note: The Launcher is a software application installed on each client computer that you canuse to access any Metasys server or supervisory engine on the building network, regardlessof its software version. Its purpose is to remove the dependency on the public Java® RuntimeEnvironment (JRE) for the SMP UI at Release 6.0 or later by placing a private edition of the JREon the client computer. For details, refer to the Launcher Help (LIT-12011742).

After a connection is established, you can then access the SMP UI on the LCS85 from the Launcher.See LCS85 connectivity for two typical network connection scenarios. See Site Management Portaluser interface and Accessing the Site Management Portal UI on an LCS85 for more information onaccessing and navigating the SMP UI.After you access the SMP UI on an LCS85, you can configure the following settings for the LCS85:

• object name and basic device parameters

• host name (Computer Name), domain name, and network parameters

• time and date management parameters

• alarm and event parameters

• SNMP messages and the network management destination

• Site Director status

After you commission an LCS85, you must configure the LCS85 for the specified job site. Figure1 is a flowchart that provides an overview of the sequence of steps needed to commission andconfigure a new LCS85.


Figure 1: LCS85 commissioning and configuration flowchart

LCS85 configuration

LCS85 configuration is preparing an LCS85 in the SMP UI and the System Configuration Tool (SCT)UI to operate on a specific Metasys network site. The LCS85 configuration also prepares the LCS85to communicate with, monitor, and control specific BAS field devices on that site. Configuration alsoincludes preparing the LCS85 to compile, generate, and communicate information about site status,alarms, events, and trends.You can typically accomplish LCS85 configuration by downloading a pre-built archive database(from the SCT) that contains the device objects, object references, attribute values, logic, graphics,user information, and other references and data required for the LCS85 to perform its specific taskson the network. See Archive databases.You can create and edit an archive database online in the SMP UI, but in almost all cases, youshould create and edit the LCS85 archive database offline in the SCT UI. When you download thedatabase, the values in the archive database overwrite the existing values on the commissionedLCS85. Refer to the Metasys SCT Help (LIT-12011964) for information on creating and downloadingarchive databases.After you configure an LCS85 with an archive database containing user information, you can set upthe email, pager, and SNMP DDAs and create specific alarm and event notifications for delivery tospecific email, pager, and network management destinations.


Site Management Portal user interface

You can view and edit LCS85 parameters and the parameters for associated devices in the SMPUI on the LCS85. Use the Launcher to access the LCS85 SMP UI. See Accessing the Site ManagementPortal UI on an LCS85 for an example of the SMP UI.

Note: Do not browse to the Metasys SMP UI from a computer running a server-class OS. Bydefault, Windows® Internet Explorer® Enhanced Security Configuration is enabled on server-class operating systems, and may block the Launcher download page from which you installthe Launcher application for access to the SMP. Open the SMP UI from a computer that is notrunning a server-class OS.

A series of tabbed screens is in the Display panel on the right side of the window. Table 2 providesa brief description of the information that you can view and edit in each tabbed screen. Thenavigation panel on the left displays the navigation tree for the BAS network integrations, fielddevices, field points, and their associated objects that the LCS85 monitors and supervises.When you view the online LCS85 SMP UI, the border around the panels is blue. When you view theoffline SCT UI, the border is black (Figure 2). The green shield icon in the lower left corner of theSMP and SCT UI screens indicate the current security level of the connection. For details, refer tothe Status Indicators section in the Metasys® Site Management Portal Help (LIT-1201793).Table 2: Metasys SMP UI tabbed screensScreen TabDesignation Purpose Access Online/

Offline

Focus

OR

Configuration

Provides description and name (label) of device object, thelocal time and date, the firmware version, message bufferand alarm, and audit repository sizes. The Focus tab alsoidentifies the local Site Director and includes generalsite information about the ADS/ADX or ODS to which theLCS85 reports (if applicable).

Both

Communications Establish communication parameters, including Serial portand internal or external USB modem configuration. Both

Network Establish Computer Name (host name) for networkidentity (online only) and LAN parameters. Both

EmailEstablish the LCS85 email alarm-notifications featurescommon to all email messages and create unique emailmessage destinations.

Both

PagerEstablish the LCS85 pager alarm-notifications featurescommon to all pager messages and create unique pagermessage destinations.

Both

SNMPEstablish the LCS85 SNMP features common to allSNMP notifications and create unique SNMP messagedestinations.

Both

AlarmProvides definition of alarm parameters for attributesinternal to the LCS85. See Alarm and events for adescription of the default LCS85 alarms.

Both

SummaryProvides network and field device status information andattribute values for supervisory and field devices on theLCS85 field trunks.

Online

Diagnostic Provides various status reports to aid in troubleshootingthe LCS85. Online


Menus, tab screens, attribute lists, values, and units of measure in the SMP UI are dynamic andchange in the displayed screen according to the item you select from the navigation tree. Refer tothe Object and Feature Tabs section in the Metasys® Site Management Portal Help (LIT-1201793) fordescriptions of menu items.

Metasys UI

In addition to the Site Management Portal UI, the Metasys UI is installed with Metasys serversoftware. The Metasys UI is a mobile-optimized software component that consolidates existingMetasys user interface products into a single, simplified, and easy-to-learn interface. The Metasys UIprovides a simple location-based navigation approach to finding information about the Metasys site,including the ability to search for any location or equipment by name and to bookmark a locationor equipment in a web browser. All data displayed in the Metasys UI is organized in a dashboardformat that gives you the overview of what is happening within a space, equipment, or centralplant. You can also and create and manage graphics and their associations to equipment andspaces. Access the Metasys UI from any type of client device with any screen size. For more details,refer to the Metasys® UI Technical Bulletin (LIT-12012115).

Metasys System Help

The Metasys Help files provide shared system information and individualized mode-dependentinformation for the Metasys SMP or the SCT. The Metasys Site Management Portal Help (LIT-1201793)provides information about alarming, commanding, auditing live data values, and other onlinefeatures. The Metasys SCT Help (LIT-12011964) provides information about offline operations such asmanaging archives, creating spaces, simulating systems, and establishing equipment and servingrelationships.For small-capacity engines at Release 9.0.7, a link to the Metasys Site Management Portal Help(LIT-1201793) stored on the Johnson Controls® literature website is available. For large capacityengines at Release 10.0 and later, the Metasys Help menu provides an option to open the Help file inPDF format.

Browser recommendations for downloading the launcher

The Metasys system currently supports Google® Chrome™ version 72.0.3626.121 or later, andApple® Safari® 11 or later for downloading the Launcher application. Other web browsers may alsofunction, but are not tested or supported.

System Configuration Tool

The SCT is an offline software tool used to create, edit, save, and restore the various archive andsecurity databases that are used to configure Metasys system networks, LCS85s, ADS/ADX or ODScomputers, and supported supervisory devices. The SCT UI (Figure 2) opens in its own window andhas a similar look and function to the online SMP UI.For information on using the SCT and navigating the SCT UI, refer to the Metasys SCT Help(LIT-12011964).


Figure 2: SCT UI screen

SCT Pro

SCT Pro is the next generation of interface for SCT. It provides streamlined workflows, andsimplifies tasks. For example, you can use SCT Pro to maintain healthy backup practices for a site,including the creation of backups automatically on a recurring schedule. SCT Pro does not includethe full range of features that are available in SCT, but each release adds new features; and you canuse SCT for the tasks that SCT Pro does not support. Refer to SCT Pro Help (LIT-12013035) for moreinformation on using SCT Pro.

Archive databases

A Metasys archive database contains the configuration information for LCS85s, ADSs/ADXs, ODSs,BAS network integrations, field devices, and field points that make up a single site or multiple siteson a Metasys system network. Multiple archive databases, representing multiple sites, can resideon a computer with SCT. The SCT navigation panel in Figure 2 provides graphical representation ofsome of the items that may be in a Metasys archive database.An LCS85 archive database, which resides in the LCS85 internal memory, contains only thespecific configuration information that makes up the network integrations, field devices, and fieldpoints that the LCS85 is supervising. Each LCS85 retains only its own archive database. A graphicalrepresentation of some of the items contained in an LCS85 archive database is shown in Figure 2 inthe SCT UI navigation panel.

Site Director

For each Metasys system network site, a single network engine or a Metasys server is designatedas the Site Director. When connected to the Site Director, the SMP UI provides a single point ofaccess to the site and all of the web-enabled devices on the site; and supports functions such asuser login, user administration, user views, time synchronization, and data traffic management.Additionally, a remote services connection allows you to connect your Metasys site to cloud-based


applications. For more information on how to connect to cloud-based applications, refer to RemoteServices Connection in the Metasys Site Management Portal Help (LIT-1201793).On larger Metasys system networks with an ODS or one or more ADSs/ADXs, an ADS/ADX/ODSis designated as the Site Director; the LCS85 cannot be the Site Director. On small network siteswithout an ADS/ADX or ODS, you must designate an LCS85 as the Site Director. When designated asthe Site Director, an LCS85 can supervise up to four additional LCS85s or engines on the site.

Note: If you attempt to add an LCS85 to a site and the new LCS85 exceeds the supervisorydevice limit for the Site Director, the Site Director does not accept the additional device. TheSite Director records an error message in the Site Director Audit Trail each time you attemptto add a new device that exceeds the device limit. If you attempt to add the same device morethan once, each attempt fails but no error message is recorded after the first attempt.

Each LCS85 installs as a Site Director. You must demote any LCS85 that is not the designatedSite Director on a site. See the Designating an LCS as a child of a Site Director section for moreinformation.You can establish or change the login user name and password for the LCS85 only when the LCS85is designated as a Site Director. Establish these values before demoting an LCS85 from Site Director.

LCS85 computer name

The LCS85 Computer Name is an editable Network Identification attribute on the LCS85 Networktab. Devices on the LAN and the Metasys system network use the LCS85 Computer Name to identifyand communicate with the LCS85 across the network. Computer Name is synonymous with hostname on a network.The LCS85 installs with an initial Computer Name that is the same as your Windows computername. Changing the LCS85 Computer Name value initiates a device reset on the LCS85.The initial computer name is often useful during commissioning for locating and connecting toan LCS85 before it is configured with an archive database download from the SCT. In most cases,the archive database download from the SCT overwrites the initial Computer Name value anddetermines the LCS85 Computer Name on the Metasys site.Changing the LCS85 Computer Name breaks any existing references between the LCS85 object andother objects on the site and may break the existing network connection to other devices on thenetwork.

Note: Before building the archive database in SCT, you should consult the networkadministrator or IT department to determine if there is an existing protocol for host names(computer names) on the network.

LCS85 object name

The LCS85 Object Name is an editable attribute on the LCS85 Focus tab that the Metasys softwareuses to identify the LCS85 in the SMP and SCT UIs. The Object Name is a label only and is not(necessarily) the same as the Computer Name. Changing the Object Name merely changes thename that you see in the navigation tree, alarm messages, trend reports, and other screens in theSMP UI and SCT that refer to the LCS85. Changing the Object Name does not impact the objectreferences or network communication with other devices on the site. You can change the ObjectName at any time. We recommend an intuitive name that clearly identifies the LCS85 in the SMPand SCT UIs and Metasys site.

Basic Access operating mode

Basic Access is a mode of operation allowing users with Basic Access user accounts access to asubset of the standard user interface capabilities based on their assigned permissions. Basic Accessuser accounts are created by Metasys system administrators using the Security Administrator


system. Basic Access meets the user interface requirements for most building operators. BasicAccess is provided on all of the Metasys system engines and servers.

Login user names and passwords

All LCS85s install with the same initial login user name and password. The initial login user name isMetasysSysAgent, and it is not case sensitive. For the MetasysSysAgent default password, contactyour local Johnson Controls® representative.You are prompted to change the login account password for your LCS85 when you log in for thefirst time.Notes:

• You can change the LCS85 login user name and password values only when an LCS85 is a SiteDirector. If you intend to change the LCS85 login user name and password, you must do sobefore demoting the LCS85 from Site Director status.

• When you change (or add) an LCS85 login user name or password, make sure to record the newuser name and password values and store the new values in a safe location. You cannot accessthe LCS85 SMP UI without a valid user name and password.

For more information on passwords, refer to the Security Administrator System Technical Bulletin(LIT-1201528).

LCS85 connectivity

You can establish a connection between a computer and an LCS85 by using one of the followingprocedures:

• Preparing an LCS85 for an Ethernet LAN that supports DHCP and DNS

• Preparing an LCS85 for an Ethernet LAN without DHCP and without DNS support (LCS85 usesstatic IP address)

Time zone, date, and time management

The procedure you use to set the time zone, date, and time on an LCS85 depends on how theLCS85 fits into the Metasys site hierarchy. See Appendix: time zone, date, and time managementfor information and detailed procedures on setting time zone, date, and time on an LCS85 and on aMetasys network.

Alarm and events

Each LCS85 stores alarm and event messages generated by the LCS85 and the connected fielddevices. You can configure an LCS85 to send alarm and event notifications through the LCS85Destination Delivery Agents (DDAs) to email destinations, paging devices, and SNMP devices.DDAs are agents that route and deliver alarm and event messages to destinations such as pagers,printers, email addresses, and SNMP management systems.If the site has an ADS/ADX/ODS, each LCS85 can forward alarm and event information to the ADS/ADX/ODS for centralized notification and long-term storage.You can designate multiple alarm and event sources in an LCS85 and in the connected field devices,and then configure the conditions that trigger those alarms or events. In addition, you can definemultiple notification types and multiple notification destinations for each alarm or event. Finally,you can edit the alarm parameters and add additional internal diagnostic alarms on the Alarm tab.


The LCS85 also has an internal diagnostic feature set to generate an alarm for CPU usage. You cancheck the status of the CPU usage alarm on the Diagnostic tab. See Diagnostic tab.Refer to Alarm and Event Management in the Metasys® Site Management Portal Help (LIT-1201793) formore information.

Note: After an alarm is generated, anyone who acknowledges the alarm clears that alarmnotification for all other users. If an ADS/ADX or ODS is the Site Director, you can set the ADS/ADX/ODS to deliver alarm and event notifications to a network printer.

Serial Printer DDA (Alarm Printer)

Alarms from supervisory devices can be sent automatically to an alarm printer if one is configuredand online. The Serial DDA must be enabled on the Site Director LCS85 that is connected to theserial printer and all LCS85s from which you want alarms printed. You can print alarms from allLCS85s using the serial printer connected to the Site Director (Figure 3). You can also print alarms toa local printer connected to a single LCS85.

Note: Alarms are sent directly to the printer and are not queued or stored by the supervisorydevice. Alarms sent to an alarm printer that is offline, turned off, or out of paper are notprinted and cannot be recovered. Figure 3 and Figure 4 show the possible printer connectionsto a Site Director LCS85.

Figure 3 shows a Metasys system with the alarm printer connected to the Site Director LCS85.Alarms for LCS85s (2 and 3) are routed to the Site Director LCS85 (1) for printing. All alarms from theLCS85s (1, 2, and 3) print on the serial printer. The serial printer DDA must be enabled on all LCS85s(1, 2, and 3).

Figure 3: Metasys System with one Alarm Printer

Figure 4 shows a Metasys system with a local alarm printer (A) connected to an LCS85 (3) forprinting. Only alarms from this LCS85 (3) print on this printer. The alarms from all LCS85s (1, 2, and3) are routed to the Site Director LCS85 (1), and all alarms are printed to serial printer B. The serialprinter DDA must be enabled on all LCS85s (1, 2, and 3).


Figure 4: Metasys System with local Alarm Printer

Serial Printer installation considerations

Follow these guidelines when installing a serial printer:

• The LCS85 uses COM1 for the physical connection of the serial printer.

• If your site contains multiple supervisory devices from which alarms are forwarded, you mustconnect the physical connection of the serial printer to COM1 of the Site Director and performthe installation sequence on all supervisory devices from which alarms are forwarded.

• You cannot filter alarms. All alarms forwarded from the device on which you install the serialprinter DDA are printed.

• If you have access to an LCS85 with a monitor and keyboard, you do not need to use RemoteDesktop and may perform the procedures in this document directly on the LCS85 computer.

Note: Use care and follow instructions carefully when using Remote Desktop to access theLCS85. Failure to follow the steps as written can render your LCS85 inoperable.

Syslog DDA

An LCS85 configured as a Site Director has the optional capability of sending its configuredaudit log entries and alarm notifications to the central repository of an external, industry-standard, Syslog server, conforming to Internet published RFC 3164. After you save the Syslog DDAconfiguration, all messages that are sent to the local ADS Repository are also sent immediately tothe configured Syslog server. You can then open a user interface at the Syslog server and use theprovided filters to interrogate or apply forensic analysis on these messages. To assist in readingthe log, a vertical bar symbol (|) separates individual fields of each Metasys message and a singlecharacter dash (-) replaces any blank field.By default, the Syslog option is disabled. Changing the Syslog Reporting Enabled attribute to Trueon the Syslog window enables the Syslog function. The prerequisites to the Syslog DDA are asfollows:

• The LCS85 must be running Release 8.0 software or later.

• No more than three Syslog destinations can be specified.


• The firewall port must be open.

The definition of the Syslog DDA requires:

• label to identify the Syslog server

• IP address of the Syslog server

• port numbers for the UDP send port and UDP receive port (for example, 514 for both)

• event and audit filters to apply against all events and audit messages. Only those events andaudit message that match the filters are passed to the Syslog server.

The Syslog DDA attribute called Syslog Reporting Enabled appears on the Shared Configurationsection of the Syslog tab of an LCS85 device object. This attribute has two selections: True or False.When the Syslog Reporting Enabled attribute is set to True, the feature is active and your Metasysmessages (events and audits) are forwarded to your destination Syslog server according to thefiltering you specified. When the Syslog Reporting Enabled attribute is set to False, the feature isinactive and no Metasys messages are forwarded to the Syslog server. The configuration examplein Figure 5 is set to route to the Syslog server all audits, event warnings, and alarms under 150 inpriority.The Syslog DDA implementation is UDP, not TCP. Therefore any audits or events generated whilethe Syslog server is offline example-reboot is not recorded at the Syslog server when it comes backonline. There is a gap in that time.If the Syslog server is offline, the Metasys system does not recognize it, and the software keepssending the messages out, regardless of whether they were received. There is no Syslog offlineversion or unreachable messages generated by the Metasys system.


Figure 5: Syslog tab in engine's Device Object

Figure 5 shows an example of Metasys system messages as they appear on the Kiwi Syslog® ServerConsole user interface. Use the console to filter the messages. If you do not have a tool, open a webbrowser and type the following URL:http://<IP of the server>>:<Port>/Events.aspxFor example:http://SysLogserver1:8088/Events.aspxWhen you browse to this site, type a valid username and password when prompted to gain accessto the Syslog server. A user interface appears with the captured messages.If you run into any trouble while implementing the Syslog DDA functionality, consult this followingtable.


Table 3: Syslog Server troubleshootingScenario Behavior

The engine is starting up but the Syslog DDAhas not yet started.

All generated audits and events are cachedand sent to Syslog DDA once it is started. Themaximum size of the cache is 1000 audits and1000 events per hour.

The Syslog server crashes.All generated audits and events that the enginesends to the Syslog server are lost; nothing iscached.

The Syslog server goes offline or is unreachable.

All generated audits and events that the enginesends to the Syslog server are lost; nothing iscached. No data is sent to the Syslog server untilit comes back online or becomes reachable.

The IP address, name, or port numbers of theSyslog server as defined in the engine's objectare invalid.

All generated audits and events that the enginesends to the Syslog server are lost; nothing iscached. No data is sent to the Syslog server untilyou correct the invalid parameters in the SyslogDDA.

The Syslog Reporting Enabled parameter is setto True, but no Syslog parameters are defined.

All generated audits and events that the enginesends to the Syslog server are lost; nothing iscached. No data is sent to the Syslog server untilyou specify the parameters that the Syslog DDArequires.

The UDP Send Port or UDP Receive Port isblocked by a firewall.

All generated audits and events that the enginesends to the Syslog server are lost; nothing iscached. No data is sent to the Syslog server untilthe ports on the Syslog server are opened.

A parameter of the Syslog server changes, butthe corresponding parameter in the Syslog DDAof the engine is not likewise changed.

All generated audits and events that the enginesends to the Syslog server are lost; nothing iscached. No data is received at the Syslog serveruntil you correct the invalid parameters in theSyslog DDA.

Email notification

You can configure an LCS85 to generate alarm and event messages through email to one or moreemail destinations using the email DDA.Configure custom email messages, and specify email message destinations in the Email tab ofthe SMP UI. Figure 6 provides an example of an email message destination that is active Mondaythrough Friday, from 7:00 A.M. to 4:00 P.M.


Figure 6: Example of Defining an Email Notification

Pager notification

You can configure an LCS85 to generate alarm and event messages using Telelocator AlphanumericProtocol (TAP) to one or more pager destinations using the pager DDA.TAP is an ASCII-based protocol that allows the submission of a numeric or alphanumeric message.Configure custom pager messages and specify the pager message destinations in the Pager tabof the SMP UI. Figure 7 provides an example of how to define a set of pager destinations that canroute a fire alarm to the same pager over the weekend (4:00 P.M. Friday to 7:00 A.M. Monday). Notethat this application requires the definition of three separate Pager destinations.


Figure 7: Examples of defining a Pager notification

SNMP notification

SNMP is a protocol governing network management and the monitoring of network devices andtheir functions. It is not necessarily limited to TCP/IP networks. SNMP monitoring is typically usedfor large BAS networks with many network devices. Alarm and event notifications are sent to andstored on an SNMP management computer that monitors all devices on the network.The LCS85 uses SNMP protocol to deliver network device status and conditions to a designatedSNMP management computer. You must set up SNMP monitoring at the network level, and youmust assign an SNMP management device on the network. If you are applying a Metasys system toan existing network, consult with the network administrator or IT department that administers thenetwork to determine if SNMP monitoring is available on the network.Configure custom SNMP messages and specify the SNMP message destinations in the SNMP tabof the SMP UI. Perform this configuration to each LCS85 individually. Take note that for the LCS85,SNMP communication is only one way. That is, the SNMP management computer can receivenetwork device status and conditions from the LCS85, but it cannot request information from theLCS85 or discover the LCS85 using the SNMP protocol. This behavior is reflected in the SMP UI asfollows: under the SNMP tab of the LCS85, the Destination Port Number attribute is effective, butthe SNMP Request Port attribute is ignored.SNMP functionality includes a Metasys system management information base (MIB) file forconfiguring third-party SNMP translation applications to request, receive, and translate specifiedSNMP trap messages generated by the Metasys SNMP DDA.

Initial default LCS85 configuration

LCS85s install with standard initial values for many of the editable attribute values; see Table 4.Table 4: LCS85 initial configuration valuesAttribute/Field Name LCS85 Initial ValueComputer Name This is the same as the Windows computer name.


Table 4: LCS85 initial configuration valuesAttribute/Field Name LCS85 Initial Value

DHCP Client

Enabled

Notes:

• When commissioning an LCS85 for an Ethernet LAN that supportsDynamic Host Configuration Protocol (DHCP) and domain namesystem (DNS), we recommend configuring DHCP to assign the sameIP address to an LCS85 when the IP address lease expires and afterthe LCS85 device resets. If a different IP address is issued to theLCS85, address binding to the LCS85 from other devices breaks.

• If you are using a static IP address, make sure you disable DHCP inthe SMP UI. You may need to check the Default Gateway setting inthe Registry Editor if you encounter communication problems. Referto the LCS85 Installation and Upgrade Instructions (LIT-12011623) fordetailed procedures.

Site Director

A new LCS85 installs as a Site Director. If that LCS85 is not going tobe the Site Director, you must demote it by entering the ComputerName or IP address of the designated Site Director in the Site Directorattribute field on the Advanced Focus tab of the LCS85.

Initial SMP UI LoginUsername MetasysSysAgent (not case-sensitive)

Initial SMP UI LoginPassword Contact your local Johnson Controls representative.

System and user preferences

The Metasys system provides customized preferences for the SMP UI. The preferences allow you toconfigure how the user interface behaves, including the sounds and colors, the startup view, andthe ability to add links to external applications that can be accessed from within the user interfaceof the LCS85 device. See Appendix: configuring and maintaining preferences for information anddetailed procedures on how to customize system and user preferences.

Detailed procedures

Commissioning requirements

To commission an LCS85, you need the following:

• a server computer installed with the Metasys LCS85 software and connected to the buildingnetwork

• a computer monitor, a USB keyboard, and mouse (these do not need to be dedicated to theLCS85)

• an Ethernet patch cable

• the network information for setting up the LCS85 on the customer network


We strongly recommend using a UPS. We recommend APC Smart-UPS® SC450 (APC Part No.SC450RM1U) or equivalent.

Commissioning guidelines

Follow these guidelines when connecting to and commissioning an LCS85:

• You should connect the LCS85 to a reliable UPS to avoid data loss in the event of a power outage.We recommend APC Smart-UPS SC450 (APC Part No. SC450RM1U) or equivalent.

• Keep the OS up-to-date by applying Windows OS security updates to the LCS85.

Note: Do not install any Service Pack updates for the Windows OS unless the Service Packupdate is approved by Johnson Controls.

• If an LCS85 resides on a Metasys site with an ODS or one or more ADSs/ADXs, an ADS/ADX mustbe the Site Director. If an LCS85 is applied to a site without an ADS/ADX/ODS, the LCS85 can bethe Site Director for up to four other LCS85s or network engines.

• Time, Date, and Time Zone settings for the LCS85 must be set in the SMP UI. See Appendix: timezone, date, and time management for detailed procedures on setting time and date on an LCS85.

• The LCS85 does not support the Reset Device command. Reset the LCS85 by restarting theWindows OS by going to Start > Shut down. (If you are using Windows Server 2012 R2 orWindows Server 2012, open the charms bar and go to Settings > Power > Restart.)

• The LCS85 supports communication with LonWorks network system devices on a User DatagramProtocol (UDP) or TCP port using unicast or multicast addressing. The default are ports1628/1629.

• You should back up the LCS85 data regularly by uploading the archive database to an SCT.Frequent backup preserves the LCS85 data and enhances the recovery procedure in the event ofa system failure.

• Certain power conservation options on the LCS85 computer have been intentionally disabled. Besure to maintain the following settings:

- Under Power Schemes, do not allow the computer’s hard disk to turn off or the computer toenter Standby mode.

- Under Hibernation, do not allow the computer to enter Hibernation mode.

- Do not allow the LCS85 computer to turn off its network card to conserve power. Underthe Power Management tab of the network card’s properties, clear the option Allow thecomputer to turn off this device to save power.

Commissioning the LCS85

1. Connect a monitor, keyboard, and mouse to the LCS85 (if you have not already done so).

2. Install the recommended UPS (if you have not already done so). Refer to the UPSmanufacturer’s installation documentation.

3. Connect the Ethernet Port 1 on the LCS85 to the BAS network with an Ethernet patch cable.


Note: Before powering on the LCS85 for the first time, the LCS85 must be connected to anactive network on Ethernet Port 1. Failure to follow this sequence prevents the LCS85 objectfrom appearing in the SMP UI navigation panel.

Note: We support the use of only one Ethernet port; any additional Ethernet ports shouldhave been disabled before the LCS85 was installed. Refer to the LCS85 Installation and UpgradeInstructions (LIT-12011623).

4. Power on the LCS85.

5. Update the antivirus software and the virus definition files according to the antivirus softwaremanufacturer’s instructions, and then restart the computer.

Note: Updating the antivirus software and virus definition files requires Internet access. Somenetwork applications require a proxy server or special permissions to access the Internet.Contact the network administrator for proxy server address, port number, or any requiredpermissions to access the Internet.

6. Update the Windows OS. To update the Windows OS, go to Start > All Programs > WindowsUpdate. (If you are using Windows Server 2012 R2 or Windows Server 2012, go to Control Panel> System and Security > Windows Update.) Follow the instructions at the Windows Updatewebsite and then restart the computer.

Notes:

- Updating the Windows OS requires an Internet connection. Some network applicationsrequire a proxy server or special permissions to access the Internet. Contact the networkadministrator for proxy server address, port number, or any required permissions to accessthe Internet.

- Update the Windows OS by downloading and installing all of the critical and security patches(only) for the OS. Do not install any Service Pack updates for the OS unless the Service Packupdate is approved by Johnson Controls.

7. If you need to change the LCS85 computer name, see Changing the LCS85 name and thecomputer name.

If you do not need to change the LCS85 computer name, the LCS85 is now commissioned and canbe configured in the LCS85 SMP UI. See Using Launcher to discover an LCS85.

Adding a third party integration

About this task:You can add third party integrations for Modbus, M-Bus, KNX, or C•CURE-victor to an LCS85. Asbest practice, refer to the appropriate application note listed in Related documentation for detailedinformation about how to add the integration. In each application note, all information that appliesto an NAE85 also applies to the LCS85.For general information about how to add an integration, see the following steps:

1. Use the Launcher application to access the SMP of the LCS85.

2. In the All Items tree, select the LCS85 device object.

3. Click Insert > Integration. The Insert Integration Wizard appears.


4. In the Select Object Type window, click VND Integration, and then click Next.

5. In the Destination window, click the LCS85 object, and then click Next.

6. In the Identifier window, enter a unique name for the integration trunk, and click Next.

7. In the Configure window, click the Hardware tab. In the Vendor DLL field, enter the nameof the driver. Enter only one driver name and type the characters exactly as indicated in thefollowing table, paying attention to letter case.

Table 5: Vendor DLL filenamesIntegration First driver Subsequent driver

KNX KNXDriver.dll

KNXDriver_1.dll

You can add a maximum of two KNXintegrations to an LCS85.

M-Bus MBusDriver_TCP.dll

MBusDriver_TCP_x.dll

Where x is 1 for the second M-Busintegration, 2 for the third, and 3 for thefourth.

Modbus ModbusDriver_TCP.dll

ModbusDriver_TCP_x.dll

Where x is 1 for the second Modbusintegration, 2 for the third, and 3 for thefourth.

C•CURE-victor Victor_CCureDriver.dll You can only add one C•CURE-victorintegration to an LCS85.

8. For the Vendor Reference field, choose one of the following options:

- For a KNX or a C•CURE-victor integration, do not modify the field.

- For an M-Bus or a Modbus integration, enter TCP to indicate the communication mode.

Note: If you add an M-Bus integration, the level converter must already be configured. Ifyou have not yet configured the level converter refer to the NAE/NIE Commissioning for M-Bus Vendor Integration Application Note (LIT-12013149) for more information and follow thedirections for setup.

9. To configure a C•CURE-victor integration, in the Vendor Configuration Data list, click theellipses icon to open the Modify List window, and then enter the required parameters. If oneof the parameters from 1 to 4 is incorrect, the LCS85 cannot connect to the C•CURE-victor webservice. For details, refer to the NAE Commissioning for C•CURE-victor integration (LIT-12013151).

10. Click Next.

11. In the Summary window, click Finish.

12. Optionally, back up your <driver>.dll file.


Changing the LCS85 name and the computer name

Follow the steps in this section to change the name of an LCS85. The LCS85 name and the computername must match (including the domain name if used) for proper functionality. You need tochange the LCS85 name and computer name only on network applications that specify namingconventions for computers on the network.

Note: When you follow these procedures for an existing Site Director, all references used inuser views, graphics, and control systems break. To update the user views after changing thename of the Site Director, open each user view in Edit mode in the SCT and save it. The SiteDirector portion of the reference updates to match the new Site Director name.

Changing the LCS85 name and the computer name - overview

About this task:This section is an overview of the steps to change the LCS85 name and computer name. Follow allthe steps in this document in the correct order to ensure success.To change the LCS85 name and the computer name:

1. Prepare the computer. See Preparing the computer.

2. Create a new archive. See Creating a new archive.

3. Download the LCS85. See Downloading the LCS85.

4. Test the LCS85. See Testing the LCS85.

Preparing the computer

1. Verify that the time zone, date, and time setting are correct in the SMP UI.

Note: Time Zone, Date, and Time must be set in the SMP UI. Do not use the Windows OS timedialog box to set time zone, date, or time on the LCS85.

2. Write down the name you want for the LCS85. Note the case of the name. The desired LCS85name must:

- begin with a letter

- contain a maximum of 15 characters

- contain only letters A–Z, numbers 0–9, and hyphens

3. In Control Panel, select System and Security > System.

4. Click Change settings. The System Properties dialog box appears.

5. Select the Computer Name tab.

6. Write down the original computer name as it appears in the Full computer name field. Notethe case of the name and also include the domain name, if present. See Figure 8.


Figure 8: System Properties dialog box

7. Click OK to close the System Properties dialog box.

8. Log in to the LCS85 SMP UI to verify that the LCS85 is running.

Note: Ignore the label for the LCS85 that appears in the Navigation tree.

9. Exit the LCS85 SMP UI.

10. Go to Creating a new archive.

Creating a new archive

1. Log in to the SCT.

2. Select Item > New Archive.

3. In the New Archive Wizard window, click Create.

4. When prompted to create a new site, click Yes.


5. Follow the wizard instructions to create a new site. In the Configure step, verify the TimeZone attribute exactly matches the time zone for the computer that you verified in Step 1 ofPreparing the computer. If the time zone does not match that of the computer, select the correcttime zone.

Note: The order of the time zones in the Metasys software does not match the order in whichthey are presented in the Windows OS.

6. Finish the rest of the steps in the wizard.

7. When the Create Device? window appears, select Supervisory Device from the drop-downselection box. Click OK.

8. Follow the wizard instructions to create a new LCS85 device. On the Identifier screen, enterthe name of the original computer name from Step 6 of Preparing the computer, making sureyou use the same capitalization and include the domain name, if present. Finish the rest of thesteps in the wizard.

When you are finished creating the new device, in the navigation tree, the name of the servershould match the original computer name.9. On the Tools menu, select Manage Archive.

10. On the Action screen, select Update From Device as the type.

11. Click Next and follow the wizard instructions.

12. On the Site Login screen, click Test Login. Finish the steps to start the upload process.

Note: If the upload is not successful, restart the computer and go to Log on to the SCT in thissection.

13. When upload Completion Status reads OK, right-click the server in the navigation tree andselect Rename. The Rename window appears.

14. In the New Name field, enter the desired LCS85 name from Step 2 of Preparing the computer(including the domain name if used).

15. Click OK.

16. Exit the SCT. Do not download or make other name changes in the SCT.

17. Go to Downloading the LCS85.

Downloading the LCS85

1. Log in to the SCT.

2. Select the LCS85 in the navigation tree.

3. On the Tools menu, click Manage Archive.

4. On the Action screen, select Download to Device as the type.

5. Click Next and follow the wizard instructions.


6. On the Site Login screen, click Test Login. Continue to follow the wizard instructions.

7. On the Device Change screen (Figure 9), select the Use this option to rename a device viadownload check box and enter the original computer name from Step 6 in Preparing thecomputer. The computer name is case sensitive.

Figure 9: Device Change screen in the SCT

8. Click Next.

9. Click Finish in the Summary screen to begin the device download.

10. When Download Completion Status reads OK, exit the SCT. The rename is complete.

11. Go to Testing the LCS85.

Testing the LCS85

1. Log in to the LCS85.

2. On the View menu, check Extended Labels.

3. Double-click the LCS85 in the navigation tree.

4. On the Focus tab, click Edit.

5. In the Name attribute, enter the desired LCS85 name. Note the case of the name.

6. Click Save.

7. Right-click the navigation tree tab, and select Refresh.

8. Exit the LCS85.

The LCS85 name and computer name change is complete.

Licensing the LCS85

The Metasys system checks for an active license at startup. If you try to log on to an unlicensedLCS85 server, a message appears that indicates that the product is not licensed. You must use theSoftware Manager to license the LCS85 server, and then restart the LCS85 to activate the Metasyssystem.

Note:


If the object count of the LCS85 exceeds 10,000 objects, you need the 15K object upgradelicense. You must license the 15K object upgrade in the Software Manager. You must notexceed 25,000 objects. If it exceeds the object limit, a warning message appears in the Meta-sys SMP UI. You also receive a warning message if you download an archive database from SCTthat exceeds your object count limit.

For detailed information, refer to the Software Manager Help (LIT-12012389), and the Licensing theLCS85 section in the LCS85 Installation and Upgrade Guide (LIT-12011623).

Using Launcher to discover an LCS85

About this task:Use the Launcher application to discover an LCS85. If the Launcher application is already installedon your computer, skip to Step 2 of Full Launcher installer. If the Launcher application is notinstalled, follow these steps:

1. Open either the Internet Explorer web browser or the Safari web browser.

2. Enter this URL in the address field: https://<LCS85-computer-name>/metasys. See the LCS85computer name section. The Windows Launcher Download screen appears.

3. Click Full Launcher Installer. Follow the instructions on the screen to install the Launcher.Refer to the Launcher Installation Instructions (LIT-12011783) if needed. When the Launcher isinstalled on your computer, proceed to Step 2 of Full Launcher installer.

4. Start the Launcher application. The Launcher screens appears.

5. Click Add. The Add New window appears.

Figure 10: Add New Device

6. Enter the host name of the LCS85, and then click Discover. The Launcher searches for thedevice on the building network. When the device is found, the Add New window refreshes toindicate the found device.

7. Make sure the Add box next to SMP is selected. You may enter a descriptive name for the LCSin the Description field to make the LCS85 easier to find in the profile list. Click Save. The LCS isadded to the profile list on the SMP tab.


Note: If the device has SCT installed, you may add the device to the SCT tab as well.

8. Select the LCS85 from the SMP profile list and click Launch. If the device you are adding hasnot yet been downloaded and installed on your computer, a Downloading screen appears,followed by an Installing screen. When these screens clear, the Metasys system login screenappears.

9. Log in to the LCS85. See Logging on to the LCS85 if necessary.

10. Set the time, time zone, and date. See Appendix: time zone, date, and time management.

Logging on to the LCS85

1. Enter your user name and password in the login window of the LCS85 SMP UI.

Notes:

- All LCS85s install with the same initial login user name and password. The initial login username is MetasysSysAgent and it is not case sensitive. For the MetasysSysAgent defaultpassword, contact your local Johnson Controls® representative.

- For added security, the user name is obscured as you type it.

2. Click Login.

Note: When you log in for the first time, you must change the account password for the LCS85.

3. Click OK when the Password has expired message appears. The Change Password dialogbox appears.


The following password rules are enforced for English (en_US) users only. The password rules areas follows:• The password must include a minimum of 8 characters and a maximum of 50 characters.

• The password cannot include spaces or include a word or phrase that is in the Blocked Wordslist.

• The password and the username cannot share the same three consecutive characters.

• For the en_us locale, the password must meet the first four of the following conditions. ForChinese Simplified (zh_cn), Chinese Traditional (zh_tw), Japanese (ja_jp), and Korean (ko_kr)language locales, the password must meet two of the following conditions. For other languagelocales, the password must meet three of the following conditions:

- Include at least one number (0–9)

- Include at least one special character (-, ., @, #, !, ?, $, %)Note: For the en_us locale, only the special characters listed above can be used; allother special characters are invalid.

- Include at least one uppercase character

- Include at least one lowercase character

- For non en_us locales: include at least one Unicode character that is categorized as analphabetic character but is not uppercase or lowercase

4. Type the old password, and then type your new password twice. Make sure to follow thepassword rules when you create your new password.

5. Click OK. The message Successfully changed the password appears.

6. Click OK. The Terms and Conditions window appears.

7. Click Accept to accept the terms and conditions. The SMP UI opens (Figure 11).


Figure 11: LCS85 in the SMP UI

Note: The user name in the upper right corner of the SMP UI is partially obscured for addedsecurity (Figure 11).

Preparing an LCS85 for an Ethernet LAN that supports DHCPand DNS

About this task:The following scenario is typical when installing an LCS85 on an existing building LAN. Your com-puter must be connected to the LAN. The computer must be a DHCP client or configured to use astatic IP address appropriate for the LAN.

Note: We recommend that DHCP be configured to assign the same IP address to an LCS85when the IP address lease expires and after the LCS85 device resets. When a different IPaddress is issued to an LCS85, address binding to the LCS85 from other devices breaks.

To set up an LCS85 for an Ethernet LAN that supports DHCP and DNS:

1. Your LAN Administrator must update the DNS server and the DHCP server with the LCS85Ethernet MAC address and the LCS85 host name.

2. Connect the LCS85 to the LAN with an Ethernet patch cable.

3. Connect 120 VAC supply power to the LCS85.

4. Power on the LCS85 and wait for the LCS85 to complete the startup and initialization sequence.


Note: If the DHCP server is not online when the LCS85 is powered on (or if the LCS85 Ethernetcable is disconnected and reconnected with no DHCP server online), the LCS85 assumes aunique IP address between 169.254.0.1 and 169.254.255.254 and a subnet mask of 255.255.0.0.This is a feature of automatic private IP addressing (APIPA) that applies when DHCP is enabledin the LCS85.

5. Go to Using Launcher to discover an LCS85, follow all instructions, then return to the next stepsin this section.

6. After you log in to the LCS85, select the LCS85 device object in the Navigation panel, and drag itto the Display panel of the SMP UI. The Focus tab for the selected LCS85 appears in the Displaypanel (Figure 12).

Figure 12: LCS85 Focus tab - basic

7. Go to the Network tab and check the Computer Name and Domain Name values. Change thesevalues to the assigned values for your network site (Figure 13).

Note: Changing the Computer Name value forces a device reset on the LCS85. See LCS85computer name.


Figure 13: LCS85 Network tab - edit mode

8. Go to the Focus tab and check the LCS85 Object Name value (Figure 14). Change the ObjectName value to the descriptive label used to identify the LCS85 in the SMP and SCT UIs.


Figure 14: LCS85 Focus tab - advanced mode

Depending on the DNS server configuration, the LCS85 should be reachable from the subnet onwhich the LCS85 resides or from other subnets.

Preparing an LCS85 for an Ethernet LAN without DHCP andwithout DNS support (LCS85 uses static IP address)

About this task:This scenario is typical when installing the LCS85 on a stand-alone LAN dedicated to building controlonly. Using this scenario when using APIPA is not appropriate. The steps can be performed froma computer attached to the LAN or a computer connected directly to the LCS85 with an Ethernetcrossover cable. If attached to the LAN, the computer must be connected to the same subnet as theLCS85.

Note: To connect to the LCS85 with this procedure, you may need to know the IP address ofthe LCS85. See the Determining the IP address section.


To set up an LCS85 for an Ethernet LAN without DHCP and without DNS support:

1. Check the LAN IP address and subnet mask of the computer. If needed, change the IP addressand subnet mask of the computer so that the computer and LCS85 are on the same subnet.The IP address assigned to the computer must be unique for the subnet.

2. Connect supply power to the LCS85.

3. Power on the LCS85 and wait for the LCS85 to complete startup and initialization.

4. Go to Using Launcher to discover an LCS85, follow all instructions, then return to the next stepsin this section.

5. After you log in to the LCS85, select the LCS85 device object in the Navigation panel, and drag itto the Display panel of the SMP UI.

6. Set the time, time zone, and date. See Appendix: time zone, date, and time management.

7. If this LCS85 is not going to be the Site Director, demote it from Site Director. See Designatingan LCS as a child of a Site Director.

8. Select the LCS85 device object from the Navigation panel of the SMP UI and drag it to theDisplay panel. The LCS85 device object user interface opens in the Display panel.

9. Select the Network tab of the LCS85 device object and click Edit (Figure 15).

Figure 15: Network tab - edit mode


10. Change the Computer Name value, if desired. Change the DHCP Enabled attribute value toFalse. This setting disables DHCP and APIPA. Change the IP address and subnet mask. Thenetwork administrator typically assigns static IP addresses. Record the assigned IP address forthe LCS85 for future reference. The LCS85 automatically logs out and resets when you save theComputer Name change.

11. Wait for the LCS85 to complete the startup and initialization sequence.

Initial setup is complete.Note: If you connected your computer directly to the LCS85 with an Ethernet crossover cable,disconnect the crossover cable and connect the LCS85 to the LAN with an Ethernet patch cable.

You can log in to the LCS85 by entering its IP address in Launcher on any subset of the LAN.

Preparing the LCS85 for serial printing

About this task:To prepare the LCS85 for serial printing:

1. Disable COM port 2 in the Windows Device Manager.

2. Configure COM port 1 for 9600-8-N-1-N.

3. Connect the serial printer to COM port 1.

Note: The printer has only one physical port.

4. Install the printer driver.

5. Return to Enabling the serial printer DDA. If you have access to an LCS85 with a monitor andkeyboard, start with Step 14; otherwise, start with Step 3 of Enabling the serial printer DDA.

Enabling the serial printer DDA

About this task:Note: Use care and follow instructions carefully when using Remote Desktop to access anLCS85. Failure to follow the steps as written can render your LCS85 inoperable.

Note: Perform a database archive prior to completing this procedure to ensure you do notlose any data. The Metasys system shuts down after configuring the Serial Printer DDA file.

To enable the Serial Printer DDA:

1. Complete the steps in Creating Audit Entries for Discarded Events.

2. Make sure Remote Desktop is enabled.

Note: Remote Desktop must be enabled to access the LCS85 remotely, otherwise you must usea direct connection. If you are using direct connection, skip to Step 13.

3. Go to Start > All Programs > Accessories > Remote Desktop Connection.

4. Click Options.


5. Select the Local Resources tab (Figure 16).

Figure 16: Remote Desktop Connection - Local Resources tab

6. In the Local devices and resources section, click More. The Local devices and resources dialogbox appears (Figure 17).

7. Make sure the only selected check box is Drives.


Figure 17: Local devices and resources

8. Click OK.

9. Select the General tab, and enter the name/IP address of the LCS85 in the Computer field(Figure 18).


Figure 18: Remote Desktop Connection - General tab

10. In the User name field, enter MetasysSysAgent.

Note: MetasysSysAgent is the default user name. If your Metasys system user name has beenchanged, enter the current user name.

11. Click Connect. The Windows Security Dialog box appears (Figure 19).


Figure 19: Remote Desktop Windows Security dialog box

12. Enter your password in the password field and click OK.

Note: If you do not know your password, contact your local Johnson Controls representative.

When Remote Desktop successfully connects to the LCS85, or the user is logged in locally to theLCS85, the Windows desktop appears and displays your IP address and Remote Desktop at the topof the window.13. On the Start menu, select Run. In the Open field, type notepad and click OK. Microsoft

Notepad opens in a new window.

14. In Notepad, on the File menu, select Open.

15. In the Files of Type field, select All Files.

16. Browse to JCI_LCS (C:)\Inetpub\wwwroot\MetasysIII\WS and select Web.config.)

17. Click Open. The Web.config file opens in Notepad.

18. In the <EventRouter> section, locate the serial printer DDA line:



19. Delete  at the end of the serial printer DDA line.

Note: Be sure that you have archived your most recent database before proceeding tothe next step. The Metasys system shuts down automatically when you save edits to theWeb.config file.

20. On the Notepad File menu, click Save.

Note: If the file is not saved as Web.config (the original name), the DDA is not enabled.

21. Restart the computer.

The Serial Printer DDA installation is now complete. The LCS85 restarts and closes the Remote Desk-top connection (if used).

Enabling Syslog reporting

About this task:An LCS85 can be set up to generate custom alarm and event email messages and send the mes-sages to one or more specified email destinations.

1. In the Site Management Portal UI, display the LCS85 device object and click the Syslog tab.

2. Click Edit. The Shared Configuration section of the Syslog tab appears.

Figure 20: LCS85 Syslog configuration - edit mode

3. Click the down arrow for the Syslog Reporting Enabled attribute and select True.

4. In the Destinations section, click New. The Destination Configuration edit fields appear.

5. Enter the Destination Configuration values according to Table 6.

Table 6: Attributes for specific Syslog destinationsAttribute Description (Value Requirement/Range)Label Specifies a name for the Syslog server (for example, Syslog1).

Syslog Server Specifies the IP address or resolvable host name of the Syslog server that isconfigured to receive events and audits from the LCS85.


Table 6: Attributes for specific Syslog destinationsAttribute Description (Value Requirement/Range)UDP Send Port Specifies the Syslog port that is used to send messages to an LCS85.UDP Receive Port Specifies the Syslog port that is used to receive messages from an LCS85.

Event Filters Specifies the rules for filtering the alarms and events that are sent to theSyslog server. Each filter has an Item, Operator, and Value.

Audit Filters Specifies the rules for filtering the audit messages that are sent to theSyslog server. Each filter has an Item, Operator, and Value.

6. In the Event Filters section, click New. The Add Filter dialog box appears.

Figure 21: Add Filter dialog box: events

7. Select the item, operator, and value of the condition that you want to trigger a message to theSyslog server.

8. Add any additional event filters as desired.

9. In the Event Filters section, click New. The Add Filter dialog box appears.

Figure 22: Add Filter dialog box: audits

10. Select the item, operator, and value of the condition that you want to trigger a message to theSyslog server.

11. Add any additional audit filters as desired.

12. Add additional Syslog destinations and filters as desired.


13. Click OK.

14. Click Save.

Creating Audit Entries for Discarded Events

About this task:By default, discarded events that originate at the LCS85 are not recorded. You can change thisbehavior so that an audit entry is recorded and shown in the Audit Viewer each time an event is dis-carded.To create audit entries for discarded events:

1. Access the LCS85 remotely using Remote Desktop.

2. Open Notepad.

3. Open the following file for editing:

C:\Inetpub\wwwroot\MetasysIII\WS\web.config

4. Find the line for WriteAuditAckDiscard:

<add key="EventRepository.WriteAuditAckDiscard" value="false"/>

5. Change the value from false to true.

6. Save the file.

7. Terminate your remote connection to the LCS85.

Accessing the Site Management Portal UI on an LCS85

About this task:After an LCS85 is set up for connectivity, you can access the SMP UI through the Launcher.See the Site Management Portal user interface section of this document and the Metasys® Site Man-agement Portal Help (LIT-1201793) for additional information about navigating the SMP UI.You need to know the host name (or IP address) for the LCS85 you wish to access. If you do notknow the host name but want to specify the IP address of the LCS85, see the Determining the IPaddress section.If the LCS85 has been added to a building’s DNS server, you can access it by its host name.To access the SMP UI on an LCS85 through the Launcher:

1. Open the Launcher application.

2. Select the host name (or IP address) of the LCS85 on the SMP tab of the Launcher and clickLaunch. The Metasys system login screen appears.

3. In the Metasys system login screen, type the LCS85 Username and Password, and then clickLogin or press Enter.

4. To view an LCS85, select the LCS85 object from the Navigation panel and drag it to the Displaypanel. The LCS85 object opens with the Focus tab active (Figure 23).


Establishing basic LCS85 parameters in the Focus screen

About this task:To establish some of the basic LCS85 parameters in the Focus screen:

1. In the SMP UI, display the LCS85 device object and click the Focus tab.

2. Click Edit (Figure 23). Edit the LCS85 Object Name and Description values as required.

Figure 23: LCS85 Focus tab (basic)

3. Click Save.

4. Select the Advanced option and click Edit (Figure 24).


Figure 24: LCS85 Focus tab - advanced edit mode

5. Edit the advanced attribute values as needed. (Refer to Engine Device Object and Audit Trails inthe Metasys® Site Management Portal Help (LIT-1201793) for guidance.) If the LCS85 is on a sitewith an ADS/ADX or ODS, enter the ADS/ADX/ODS’s IP address in Local Site Director field in theSite section of this screen so the LCS85 can find the ADS/ADX/ODS.

Establishing the LCS85 network parameters

About this task:The LCS85 Computer Name and Domain Name on the Network tab identify the LCS85 on the net-work so it can be found by other computers. In many commissioning scenarios, you can use the ini-tial Computer Name value to commission the LCS85. See LCS85 computer name for more informa-tion.In most site configuration scenarios, you configure many of the Metasys network values in theLCS85 SMP UI by downloading a pre-built archive database from the SCT to the commissionedLCS85. The download from SCT overwrites the initial Computer Name value with the new value forthe Metasys network.


Note: If you are building the LCS85 database online, you must establish the productionnetwork LCS85 Computer Name value before establishing references to objects on theLCS85. After creating object references, changing the Computer Name value breaks all objectreferences to local objects on the site.

To set up the LCS85 network identification and LAN configuration attributes:

1. In the SMP UI, display the LCS85 device object, select the Network tab, and then click Edit(Figure 25).

Figure 25: LCS85 Network tab - edit mode

2. In the Network Identification section (Figure 25), type the Computer Name value.

3. Edit the Network Identification and LAN attribute values as needed and click Save (Figure 25).

Creating Email Alarm and Event Notifications andDestinations

About this task:An LCS85 can be set up to generate custom alarm and event email messages and send the mes-sages to one or more specified email destinations.

Note: In most scenarios, we recommend that you set up the Email DDA and configure theemail notifications and the notification destinations after the LCS85 is configured with anarchive database that includes the user database.

To create email messages and specify email destinations for the messages:

1. In the SMP UI, display the LCS85 device object, select the Email tab, and then click Edit. (See thetop half of the Display panel in Figure 26.)


2. Enter the Shared Configuration values according to Table 7. These fields establish values forattributes that are common to all email alarm notifications generated from this LCS85. Referto Alarm and Event Management in the Metasys® Site Management Portal Help (LIT-1201793) foradditional information on setting the attribute values for alarm and event notifications.

3. In the Destinations section of the Email tab, click New. The Email Destinations Configurationedit section appears (Figure 26).

Figure 26: The LCS85 email configuration - edit mode

4. Enter the Destination values according to Table 8. Refer to the Alarm and Event Managementsection in the Metasys® Site Management Portal Help (LIT-1201793) for additional information onsetting the attribute values for alarm and event notifications.

Table 7: Shared attributes for all email destinationsAttribute Description (Value Requirement/Range) Initial Value

SMTP Server Host Specifies the SMTP server name that handlesoutgoing email. (Required Value) Fully qualified host name

SMTP PortSpecifies the TCP port that the server uses todeliver email message. (Required Value/1 to25)

25

Authentication Type

Specifies the Authentication Type the LCS85uses to log in to the outgoing email server.Select SMTP or Point of presence (POP)before SMTP.

None

SMTP User NameSpecifies the user name the LCS85 usesto log in to the SMTP server that handlesoutgoing email messages. (Required Value)

--


Table 7: Shared attributes for all email destinationsAttribute Description (Value Requirement/Range) Initial Value

SMTP PasswordSpecifies the password the LCS85 uses to login to the SMTP server that handles outgoingemail messages. (Required Value)

--

POP Server Hostname

Specifies the POP server name for incomingemail messages. (Required only if the emailserver requires POP before SMTP, beforeit accepts email messages from client. Ifthis field is left blank, POP before SMTP isdisabled.)

--

POP User nameSpecifies the POP user name. (Required onlyif POP Authentication is required and thereis a value specified for POP server host.)

Maximum 20 characters

POP PasswordSpecifies the POP Password. (Required onlyif POP Authentication is required and thereis a value specified for POP server host.)

Maximum 20 characters

From Email AddressSpecifies a valid email address that isrecognized and exists on the SMTP Server.(Required Value)

Email address

SSL Email Enabled

When True, the email is sent over anSSL-encrypted connection. If SSL is notsupported, the email is sent unencryptedunless the SSL Email Ignoring Errorsattribute is False.

False

SSL Email Ignoring Errors

When True, the email is sent even if theemail server certificate appears to be invalid.When False, the email is sent only if theoperating system can verify that the serversent a valid SSL certificate. This feature isonly enabled if SSL Email Enabled is True.

False

Email Diagnostics

Displays diagnostic information regardingthe communication between the EmailDDA (SMTP Client) and the SMTP Server.This attribute displays both successful andunsuccessful email message deliveries.

--

Table 8: Attributes for specific email destinations and notificationsAttribute Description (Value Requirement/Range) Initial Value

Label Specifies a name for the email destination(for example, John Doe). --

Email AddressSpecifies the destination email addresses(for example, [email protected]). (RequiredValue)

--

Priority Specifies the email message priority (High,low, or normal). Normal


Table 8: Attributes for specific email destinations and notificationsAttribute Description (Value Requirement/Range) Initial Value

Subject Contains the body text of the emailmessage. (Maximum of 256 character.) --

Retries Specifies the number of attempts at sendingthe email message. (0-10 Retries) 3

Enabled Enables or disables Email Destination. (True,False) True

FiltersEnables you to specify the rules that filteralarm and event notifications. Each filter hasan Item, Operator, and Value.

--

Format

Enables some predefined formatcharacteristics of the notifications that aresent to a destination. Predefined formatcharacteristics include:

• Notification Priority

• Notification Message (content)

• Value

• Site Name

• Item Description

• Item Fully Qualified Reference

• Item Category

• Acknowledge Required

• Previous Status(Enable a format by checking the box next tothe format.)

--

5. Click the browse button in Email Address. The Email Addresses dialog box appears. Import usernames and the associated email addresses from the list of user names for the site. (Refer tothe Metasys Site Management Portal Help (LIT-1201793) for more information.)


Figure 27: Import Email Addresses dialog box

6. To filter the email messages that are sent to a destination, click New next to Filters. The AddFilter dialog box appears (Figure 28).

Figure 28: Add Filter Dialog Box

7. Select the Item, Operator, and Value (from the drop-down lists) for the condition that you wantto trigger the email notification. Refer to Event Message Routing, Filtering, and Destinations in theMetasys Site Management Portal Help (LIT-1201793) for additional information on adding filters.

8. Click OK.

9. Enable the Format characteristics for email notifications sent to the specified destinations byselecting the check boxes next to the Format characteristic.


10. Add additional email destinations with filters and formats as required.

11. Click Save.

Configuring encrypted email

Your user name and password is encrypted by Metasys software once you enter it into the SMP UI,but the software does not automatically encrypt email messages. This feature allows embeddedand server machines to send email to email servers over a secure channel (secure socket layer[SSL]). The software encrypts the entire email payload, and allows our software to communicate toemail servers that require SSL connections.Consider these points when using email encryption:

• The SMTP port is different when using secure socket layer connections. This port is usually 465.

• Server-class machines and embedded devices do not have the same list of trusted CertificateAuthorities. An embedded device may not trust a certificate that is trusted on a server-classmachine. To increase the chances of an embedded device trusting a certificate used by a server-class machine, you need to have the certificate signed by a major authority.

• To maximize efficiency when using this feature, set up mailing groups instead of individual usersin the destination field to minimize the number of users to which the machine has to send anemail. This setup allows you to create different email groups and customize the type of messagesthat each user receives.

• To increase the chance of an embedded device or an ADS/ADXODS trusting the certificate themail server uses, ensure a major certificate authority obtains the signed certificate.

• If you use an embedded device as your site director, no option is available to update the TrustedCertificate Authority list at this time.

• To ensure you have the latest list of Trusted Certificate Authorities installed on your ADS/ADXODS, install any available certificate updates from Microsoft Windows® Update.

You can configure encrypted email in three ways:

• Configuring encrypted email with no authentication required

• Configuring encrypted email with SMTP authentication

• Configuring encrypted email with POP-before-SMTP authentication

Configuring encrypted email with no authentication required

About this task:Note: Encrypted Email with No Authentication Required functions only when you AnonymousAuthentication on the mail server.

1. View an engine or ADS/ADXODS device.

2. Click the Email tab.

3. Click Edit.


4. Edit the Attributes in the Shared Configuration as shown in Table 9.

Table 9: Attributes for no authentication requiredAttribute Selection

SMTP Server Host For example: mail.yourdomain.com oryourdomain.com

SMTP Port 465Authentication Type NoneSSL Email Enabled TrueSSL Email Ignoring Errors False

5. Verify that you sent the email correctly.

Configuring encrypted email with SMTP authentication

1. View an Engine or ADS/ADXODS device.


3. Click Edit.

4. Edit the Attributes in the Shared Configuration as shown in Table 10.

Table 10: Attributes for SMTP authenticationAttribute Selection


SMTP Port 465Authentication Type SMTPSSL Email Enabled TrueSSL Email Ignoring Errors False


Configuring encrypted email with POP-before-SMTP authentication

About this task:Note: When you enable SSL Email and you use POP-before-SMTP Authentication, the Metasyssystem uses port 995 to communicate to the mail server. Ensure that the mail server you areconnecting to uses port 995 for secure socket layer connections for POP3 access. When youenable SSL Email and you use POP-before-SMTP Authentication, the Metasys system uses port110 to communicate to the mail server. Ensure that the mail server you are connecting to usesport 110 for non-encrypted POP3 access.

1. View an engine or device.


3. Click Edit.


4. Edit the attributes in the Shared Configuration according to the following table:

Table 11: Attributes for POP-before-SMTP authenticationAttribute Selection


SMTP Port 465Authentication Type POP-before-SMTPPOP Server Hostname yourdomain.com or pop.yourdomain.comSSL Email Enabled TrueSSL Email Ignoring Errors False


Creating Pager Alarm and Event Notifications andDestinations

About this task:You can set up an LCS85 to generate custom alarm and event pager messages, and send the mes-sages to one or more specified pager destinations.

Note: In most scenarios, we recommend that you set up the Pager DDA and configure thepager notifications and destinations after an LCS85 is configured with an archive database thatincludes the user database.

To create pager alarm and event notifications:

1. In the SMP UI, display the LCS85 device object and select the Pager tab.

2. Click Edit. The Shared Configuration section of Pager Edit tab appears. (See the top half of theDisplay panel in Figure 29.)


Figure 29: LCS85 Pager Configuration edit mode

3. Enter the Shared Configuration values using Table 12 and Table 13 as references. These fieldsestablish values for attributes that are common to all pager alarm notifications generated fromthis LCS85. Refer to Alarm and Event Management in the Metasys® Site Management Portal Help(LIT-1201793) for additional information on setting the attribute values for alarm and eventnotifications.

Table 12: Shared attributes for all pager destinationsAttribute Description (Value Requirement/Range)Connect Using Specifies the connection type: Internal Modem, External Modem.

Access NumberSpecifies the service or modem phone number that the LCS85uses to access phone service. (This is not a pager destinationphone number.)

Redial Attempts Specifies the number of attempts the LCS85 makes to connectwith the destination pager before stopping.

Time Between Redial Attempts Specifies the time-delay interval between subsequent attemptsto connect with a destination pager.

Idle Time Before Hanging Up Specifies the amount of idle time allowed on the connectionbefore disconnecting.

Redial If Line Is Dropped Specifies whether to redial if a connection with destinationpager is broken.


Table 12: Shared attributes for all pager destinationsAttribute Description (Value Requirement/Range)

Pager Diagnostics

Displays the diagnostic information regarding communicationbetween the Pager DDA, modem, and customer's pagingService. It displays both successful and unsuccessful attempts tosend a page.

Table 13: Attributes for specific pager destinations and notificationsAttribute Description (Value Requirement/Range)

Label Specifies a functional name for the destination pager (forexample, John Doe). (Maximum 20 characters)

Pager Phone Number Specifies the complete telephone number of the destinationpager. (Maximum 20 characters)

Max CharactersSpecifies the maximum number of characters allowed (by theservice provider) in the text string that is sent to the pager. (Thisfield cannot have a value of zero.)

Retries Specifies the number of redial attempts that can be made.Enabled Enables or disables the Pager Destination.

Filters Enables you to specify the rules that filter alarm and eventnotifications. Each filter has an Item, Operator, and Value.

Format

Enables some predefined format characteristics of thenotifications that are sent to a destination. Predefined formatcharacteristics include:



• Value

• Site Name



• Item Category


• Previous Status(Enable a format by checking the box next to the format.)

4. In the Destination section (Figure 29), click New. The Destinations Configuration edit fieldsappear (Figure 30).


Figure 30: LCS85 Pager Destination tab - edit mode

Note: The Max Characters field defines the length of the text string that is sent to the pager.This field cannot have a value of zero (Figure 30).

5. Enter the appropriate values for the specified pager message destination.

Note: These fields establish values for attributes that are specific to the pager destinationand message for specified alarm notifications generated from this LCS85. Refer to Alarm andEvent Management in the Metasys® Site Management Portal Help (LIT-1201793) for additionalinformation on setting the attribute values for alarm and event notifications.

6. To filter the conditions that trigger a pager notification, click New next to the filters section ofthe Pager Destination Configuration tab (Figure 30). The Add Filter dialog box appears (Figure31).

Figure 31: Add Filter dialog box

7. Select the item, operator, and value of the condition that you want to trigger a pagernotification. (Refer to Event Message Routing, Filtering, and Destinations in the Metasys® SiteManagement Portal Help (LIT-1201793) for additional information on adding filters.)


8. Add additional pager destinations and filters as desired.

9. Click OK.

10. Click Save (Figure 30).

Creating LCS85 SNMP Alarm Notifications and Destinations

About this task:You can set up an LCS85 to generate and deliver alarm and event messages on a network usingSNMP network monitoring.You can typically use SNMP monitoring for large BAS networks with many network devices. Alarmnotifications are sent to and stored on an SNMP management computer that monitors all deviceson the network.You must set up SNMP monitoring at the network level and an SNMP management device must beassigned on the network. If you are applying a Metasys system to any existing network, consult withthe network administrator or IT department that administers the LAN to determine if SNMP moni-toring is available on the network.

Note: In most scenarios, we recommend that you set up the SNMP DDA and configure theSNMP notifications and the notification destinations after an LCS85 is configured with anarchive database that includes the user database.

To create LCS85 SNMP alarm notifications and destinations:

1. In the SMP UI, display the LCS85 device object and select the SNMP tab (Figure 32).

Figure 32: LCS85 SNMP configuration tab

2. Click Edit. The SNMP Configuration Edit screen appears.

3. In the Shared Configuration section, set SNMP Enabled value to True if your networkapplication uses SNMP monitoring.


4. Type the IP address or host name values of the SNMP Management device (computer).

5. In the Public Community Name field, enter the community string used by the NetworkManagement System (NMS) to retrieve data from objects maintained by managed devices(Table 14).

Table 14: Share attributes for SNMP destinationAttribute Description (Value Requirement/Range) Initial Value

SNMP Enabled Enables or disables SNMP DDA on theLCS85. (True, False) False

SNMP Trap VersionSpecifies the version of SNMP used on thenetwork on which the LCS85 resides. (Notrequired if SNMP Enabled is set to False)

SNMP Version 1

SNMP Management Device

Specifies the IP address or host name ofthe SNMP Management device on thenetwork on which the LCS85 resides. (Notrequired if SNMP Enabled is set to False)

--

SNMP Request Port

Specifies the port on the SNMPManagement device that requestsinformation from the LCS85. The directionof communication is from the SNMPManagement device to the LCS85.Currently, this function is not supportedon the LCS85. (Not required if SNMPEnabled is set to False)

161

Contact PersonSpecifies the contact person for the SNMPnotifications. (Not required if SNMPEnabled is set to False)

--

Public Community Name

Specifies the community name used by theNMS to modify data in objects maintainedby managed devices. (Not required ifSNMP Enabled is set to False)

Public

SNMP Trap Message Format

Specifies the format used to generateSNMP notifications. Change to MIB Basedwhen SNMP management applicationuses the Metasys MIB file to translateSNMP notifications. (Not required if SNMPEnabled is set to False)

String Based

6. Click New in the Destinations section (Figure 32). The Destination Configuration edit screenappears (Figure 33).


Figure 33: SNMP Destination Configuration Tab - Edit Mode

7. Enter the Destination information for the SNMP trap (Table 15).

Table 15: Attributes for specific SNMP notificationsAttribute Description (Value Requirement/Range) Initial Value

LabelSpecifies a functional name for thedestination SNMP server. (Maximum 20characters)

Destination #

Trap Community Name

Specifies the SNMP Community Nameused by the Network ManagementSystem (NMS) group to listen to the traps.(Maximum 20 characters)

Public

IP Address Specifies the IP address of the NMS systemthat receives the trap messages. 0.0.0.0

Destination Port Number

Specifies the port on the SNMPManagement device that receivesmessages from the LCS85 (typicallyPort Number 162). The direction ofcommunication is from the LCS85 to theSNMP Management device.

162

Enabled Enables or disables the SNMP destination. True

FiltersEnables you to specify the rules that filteralarm and event notifications. Each filterhas an item, operator, and value.

--


Table 15: Attributes for specific SNMP notificationsAttribute Description (Value Requirement/Range) Initial Value

Format

Allows you to enable some predefinedformat characteristics of the notificationsthat are sent to a destination. Predefinedformat characteristics include:



• Value

• Site Name



• Item Category


• Previous Status(Enable a format by checking the box nextto the format.)

--

8. Click Save when finished.

Setting the time, date, time zone, and time synchronization

The time zone, date, and time settings on an LCS85 are dependent on how the LCS85 fits into theMetasys site hierarchy. See Appendix: time zone, date, and time management for information anddetailed procedures on setting time zone, date, and time on an LCS85 and on a Metasys network.

Setting up the LCS85 alarm parameters

LCS85s install with several pre-configured default diagnostic alarms that monitor the LCS85hardware. You can edit these default alarm settings or create new alarms for the LCS85 hardware.You can also create new alarms and edit existing alarms for supported field devices on the LCS85field trunks.

Editing the Existing Alarm Parameters

About this task:To edit the existing alarm parameters:

1. In the SMP UI, select and drag the desired LCS85 object or field device object from theNavigation panel and drop it in the Display panel. The LCS85 or field device Focus screenopens.

2. Select the Alarm tab. The Alarm Configuration screen opens (Figure 34).


Figure 34: LCS85 Alarm Configuration tab

3. Select items in the Select Item(s): list to edit existing alarms. (To create new alarms, seeCreating a New Alarm.)

4. Click Edit. The LCS85 Alarm edit screen appears (Figure 35).


Figure 35: LCS85 Alarms tab - edit mode

5. Edit the desired Attributes for the LCS85 or field device, and click Save to save the edited alarmsettings.

Creating a New Alarm

About this task:You can create new alarms for the LCS85 or any of the supported field devices on the field trunksattached to the LCS85.To create a new alarm:

1. Select and drag the desired LCS85 or field device object from the Navigation panel into theDisplay panel. The LCS85 or field device object Focus screen opens.

2. Select the Alarm tab. The device’s Alarm screen appears.

3. Click New. The Insert Alarm Wizard appears (Figure 36).


Figure 36: Insert Alarm Wizard

4. Select the device Attribute for which you want to create an alarm.

5. Follow the Wizard instructions and create or edit the values for the Attribute for which youwant to create an alarm.

6. Click Save when you have finished creating the desired alarm parameters for the deviceAttribute.

Designating an LCS as a child of a Site Director

About this task:All LCS85s install with a Site object and therefore are Site Directors by default. However, you canonly designate a single network engine or a Metasys server as the Site Director. You must demoteall other LCS85s. To demote an LCS85, designate it as a child of the Site Director. When an LCS85 isdemoted, it must be reset.

Important: At Metasys Release 10.0 the Advanced Security Enabled attribute indicates whetherthe site uses the advanced security settings. You can use this attribute to enable an improvedlayer of security between Metasys Site Directors and devices. If you set this attribute to true,you disable backward-compatible methods of communication between the Site Director andits network engines, which means a Site Director at Release 10.0 discards all communicationattempts from network engines prior to Release 10.0. This setting applies to the entire site, sokeep this attribute set to False (default) if you have any network engines on the site that arerunning a Metasys release prior to Release 10.0.

In many Metasys network site commissioning and configuration scenarios, the Site Directorstatus of the LCSs on the site is built into the archive database for the site. The status of thesedevices is established on the LCSs when the archive database is downloaded from the SCT tothe site devices. The SCT database download overwrites the existing values in the LCSs.


Note: If an ADS/ADX or ODS is on a site, an LCS85 cannot be the Site Director.

You typically demote an LCS85 from the Site Director offline in the SCT UI, but you cancomplete the process online in the LCS85 SMP UI. The procedure in this section describes howto use the LCS85 SMP UI to demote an LCS85 from the Site Director. To do so with the SCT, goto the Changing the Site Director with the SCT section.

Note: If you do the site demotion online, you may lose any navigation trees built for the site.If User Views (navigation trees) have already been built, upload them to the SCT, establishthe Site Director, and then download the navigation trees back to the source devices. The SiteDirector and LCS85 Computer Name values in the LCS85 SMP UI must match the values in theSCT archive database.

To demote an LCS85 from Site Director, complete the following steps:

1. On the Navigation panel, select the LCS85 that you wish to demote from Site Director.

2. Drag the LCS85 into the Display panel to open its Focus tab.

3. Click Advanced.

4. Click Edit. The LCS85 Focus (Advanced) edit screen appears (Figure 37).

5. Scroll down to the Site attributes and select the Local Site Director field.

Figure 37: Designating the Site Director

6. Type the host name or IP address of the LCS85 or ADS/ADX/ODS that you want to designateas the local Site Director. After you complete the process, the demoted LCS85 is a child of thedesignated Site Director.

7. Click Save. A confirmation message box appears (Figure 38).


Figure 38: Confirmation for demoting Site Director

8. If you wish to proceed, click OK to this confirmation message; otherwise, click Cancel.

9. If the LCS85 that you wish to demote from Site Director is at Release 10.0 or later, complete thefollowing steps to pair the demoted LCS85 with the designated Site Director:

a. The Site Director Login dialog box appears. Enter an administrator account user'scredentials for the Site Director, and click OK.

b. If the credentials that you enter are incorrect, an error message appears. To continue, clickOK to return to the Site Director Login dialog box, enter the correct credentials, then clickOK.

If you successfully start the process to demote an LCS85, you are disconnected and the LCS85resets.

Note: To see the Site Director changes just made, wait several minutes for the LCS85 to reset,then log in again. The navigation tree shows the LCS85 is no longer the Site Director.

Changing the Site Director with the SCT

About this task:Note: If you have already changed the Site Director and downloaded the site, go to Moving theSecurity database and clearing it from the demoted Site Director prior to Release 6.0.

To change the Site Director:

1. Start the SCT, open the archive database for the site, and choose the new Site Director from theavailable list in the Site Director attribute of the Site object.

2. Perform a Download to update all devices. During the download process, pair all LCS85s andNxEs at Release 10.0 or later with the Site Director. For more information about device pairingin the SCT, refer to the Metasys SCT Help (LIT-12011964).

Removing user accounts from a demoted Site Director

If you demote a supervisory controller or LCS85 server from a Site Director to a child device on thesite, all user accounts that you added to the device while it was a Site Director remain in the securitydatabase. If you determine that user accounts on the demoted site should be removed after thedemotion has occurred, you must move the security database and clear it from the demoted SiteDirector. If your demoted Site Director is at a Metasys release prior to 6.0, follow the instructions inMoving the Security database and clearing it from the demoted Site Director prior to Release 6.0. If


your demoted Site Director is at Release 6.0 or later, follow the instructions in Moving the Securitydatabase and clearing it from the demoted Site Director at Release 6.0 or later.

Moving the Security database and clearing it from the demoted Site Directorprior to Release 6.0

1. Create a backup of the Security database of the demoted device, but only if you are using thesame set of users on the new or existing Site Director.

2. Create a backup of the Security database from one of the devices (LCS85) on the site that hasnever been a Site Director and has never had a Site Director’s Security database restored to it(in other words, has a clean Security database with only the default user accounts).

3. Restore the clean copy of the Security database that you created in Step 2 to the device thatwas demoted from the Site Director.

4. If you are using the Security database of the demoted device on the new Site Director, restorethe Security database that you backed up in Step 1 to the new or existing Site Director.

5. Create a backup of the Security database from the device that was demoted and restored witha clean database in Step 3.

This step ensures that the device Security database in the SCT matches the clean Security yourestored to the device in Step 3.

Moving the Security database and clearing it from the demoted Site Directorat Release 6.0 or later

About this task:Note: Starting at Release 6.0, the Security database backup is performed as part of the SCTupload, regardless of whether or not the supervisory controller or LCS85 server is a SiteDirector.

1. In the SCT,go toTools > Security to verify that a Security database exists for the demotedsupervisory controller. This database is the Security backup that was originally used by the SiteDirector.

Note: If the Security database does not exist, it means the controller has never been accessedfrom the SMP and uploaded to the SCT.

If the Security database does not exist, go to Step 2. If the Security database does exist, go to Step5.2. Log in to the demoted controller from the SMP.

3. Change your password when prompted at the login.

Note: Changing your password creates the Security database automatically the next timetheSCT database is uploaded.

4. Perform an SCT upload. Once the upload is complete, click Tools > Security Copy in the SCT.


5. In the Security Copy Wizard, do one or both of the following:

- If the Security database of the demoted Supervisory device is required on the new SiteDirector, perform a security copy to the SiteDirector by selecting the Supervisory device thatcontains the correct security database.

- If you do not want to use the Site Director Security database on the demoted Supervisorydevice, perform a security copy by selecting a Supervisory device that has never had usersadded to the Security database and copy to the demoted Supervisory device.

6. Perform an SCT upload for all Supervisory devices that have had their Security databaseschanged. This upload ensures that the security database backup is synchronized with theSupervisory device.

Printing information from the LCS85 Site Management PortalUI

About this task:The LCS85 allows printing of the information displayed in the panels of the SMP UI. The informationmust be selected before it can be printed.To print information from the LCS85 SMP UI:

1. Select an LCS85 object in the Navigation panel and drag it to the Display panel of the SMP UI.The Focus tab for the selected LCS85 appears in the Display panel.

2. Select Item > Print.

Note: You can preview the output by selecting Print Preview.

3. Select from the available printers and click OK.

Replacing an LCS85

About this task:If you need to replace an LCS85 on a network site for any reason, update the site registration toensure that devices on the site communicate with the new (replacement) LCS85; otherwise, devicesmay attempt to communicate with the LCS85 that was removed from the site.If you do not remove an LCS85 from a site correctly, the Site Director may attempt to send mes-sages to the old LCS85, creating unnecessary network traffic.To replace an LCS85:

1. Using the SCT, upload the current copy of the LCS85 database so that it can be downloaded tothe new LCS85 later.

2. Physically replace the old LCS85 with the new LCS85, connect the new LCS85 to the network,and power on the new LCS85.

3. Do one of the following:

- Configure the LCS85 with the same host name and IP address of the old LSC85 from the SMP.Note: This configuration allows an SCT download without having to use the DeviceChange option when downloading the SCT database.


- Verify that the SCT can communicate with the LCS85, then select the Device Change optionavailable from the SCT download to identify the Site Director and host name of the newLCS85.

4. Download the existing LCS85 archive database to the new LCS85.

TroubleshootingThis section describes some of the most common problems encountered when setting up andoperating LCS85s. Use the general solution guidelines and procedure references in this sectionto avoid or resolve these problems. Table 16 provides a list of common LCS85 problems and theirsolutions.This section is not a troubleshooting guide for Metasys system networks, customer LANs, BASnetworks, or the field devices connected to the LCS85.Troubleshooting field devices is covered in the field device documentation. Refer to the appropriatefield device documentation for additional information.

Note: To effectively troubleshoot an LCS85, it may be necessary to isolate the LCS85 from theEthernet network and the associated field trunks and field devices, and then direct connect tothe LCS85 with a computer to browse the SMP UI.

Common LCS85 problems

Use the following sections and Table 16 when you encounter a problem with an LCS85.

Login problems

Login problems may occur when the Username or Password are incorrectly entered at login.If the default Username and Password fail, these initial values may have been changed by anadministrator-level user. You need the designated user name and password to log in to an LCS85.See Login user names and passwords and Logging on to the LCS85.

Network connection related problems

Many network connection/communication problems result from incorrect device names, IPaddresses, and other attribute value errors entered into the SMP UI or incorrect values entered intothe user interface of the associated network devices. If the LCS85 attribute values do not match therespective values entered in the devices connected to the LCS85, the LCS85 and associated devicesmay not establish network connections or communications.Check for proper device names, IP addresses, gateway, subnet masks, ports, and other networkparameters in the SMP UI. Also check the appropriate servers, other computers, and field devicesconnected to the LCS85, and ensure that the attribute values are correct for each computer ordevice.See LCS85 technical specifications and Verifying Ethernet/IP network communications (Ping).

LCS85 reset related problems

Certain setting changes, initiated in the SMP UI, do not take effect until the LCS85 is restarted.Restart the LCS85 whenever prompted to, and allow the LCS85 to complete the restart sequence.See Detailed procedures.

Troubleshooting guide

Table 16 provides information for troubleshooting the LCS85.


Table 16: Troubleshooting the LCS85Problem SolutionYou try to log in to an LCS85and the following messageappears:

Login failed: Thisproduct is not licensed.

Action Required: Licenseand restart thisproduct.

There is no active license for the LCS85. Activate a license usingthe Software Manager, and then restart the LCS85 computer. Fordetails, refer to the Software Manager Help (LIT-12012389), and theLicensing the LCS85 section in the LCS85 Installation and UpgradeGuide (LIT-12011623).

You are logged in to anLCS85, and the followingmessage appears:This product exceeds thelicensed object countlimit.Action Required:Delete objects or obtaina license that supportsmore objects.

Do one of the following:

• Delete objects until you are within your licensed limit. (Thenumber of objects is listed in the Object Count field on theDiagnostic tab of the LCS85 in the SMP UI.)

• If you have a license for 10,000 objects, purchase the 15,000object upgrade and use the Software Manager to licensethe 15,000 object upgrade. Refer to the LCS85 Installationand Upgrade Guide (LIT-12011623) and Software Manager Help(LIT-12012389).

Check to make sure that power is connected correctly.Check to make sure that communication connectors are firmly inplace.Check the integrity of the wires and cables.

LCS85 does notcommunicate with any otherdevice.

Check that the Ethernet connection is in the enabled port.


Table 16: Troubleshooting the LCS85Problem Solution

If you are using a Loytec™ Configuration Server, verify that theLCS85 is part of the Loytec Configuration Server channel list andhas a status of registered (indicated by a green check mark).Refer to the appropriate Loytec L-IP Router documentation on theLoytec website for details (http://www.loytec.com).

If you are using an Echelon® IP-852 Configuration Server, referto the documentation on the Echelon website for details (http://www.echelon.com).Connect LN Builder, the COM.PRO Tool, or a third-party LonWorksnetwork configuration tool to the LonWorks network. Verifythat it is possible to communicate with the devices on thenetwork including the LCS85. If communication is good, verifythat the LCS85 database has been generated correctly andthat the LonWorks enabled device data corresponds to thedevices installed. If the LCS85 does not respond, verify that theLCS85 is defined with the correct device template, assigned thecorrect Neuron ID, and commissioned in the LonWorks networkdatabase. Refer to the LonWorks® Network Integration withNAE and LCS Technical Bulletin (LIT-1201668) for LCS85 databasegeneration information.

No LonWorks networkcommunication

Check the entire LonWorks network. Refer to the LonMarkGuidelines - Physical Layer for details (http://www.lonmark.org).Check that the Ethernet connection is in the enabled port.Verify that you are using a patch cable for a hub or switch and acrossover cable for a single computer connection.

No Ethernet Communication Check the port and cable integrity. Make sure either the 10/Linkor 100/Link LED is green (indicating an established Ethernetconnection). Check that the hub or switch into which the LANconnector is plugged works and is connected correctly.

LCS85 loses data. If data loss is the result of a power failure, connect the LCS85 to areliable UPS to protect data.

LCS85 runs slowly.

Reduce the size of the database. The amount of data you aretrying to process is too much for the LCS85 to handle. A value of50% or less for the CPU Usage attribute of the LCS85 is consideredOK, although other performance indicators should also beassessed. Refer to the LON Controller Object and the Diagnosticstopics in the Metasys® Site Management Portal Help (LIT-1201793)for more information.


http://www.loytec.com

http://www.echelon.com

http://www.echelon.com

http://www.lonmark.org

Table 16: Troubleshooting the LCS85Problem Solution

LCS85 is generating high CPUalarms.

Programming objects (LCT, Signal Select, Global Data) referencinganalog objects with small COV values (0.5%) are the mostcommon cause.

To determine the source of the high CPU usage follow thesesteps:

1. Add a Trend extension to the Last Idle Sample of the LCS85.This attribute is the inverted instantaneous CPU Usage. Forexample, if this number is low (5%), then the CPU usage ishigh (95%). The CPU usage is an average over 15-30 minuteperiod.

2. Locate programming objects (Control System objects [LCT]or Signal Select) that reference objects with small COVIncrements and disable them one at a time. Monitor theLast Idle Sample value after disabling the object. Within 30seconds, the Last Idle Sample should significantly increase ifthat object was a contributing factor to the high CPU usage.

3. When the problem object is determined, then eithermanually or with Mass Edit Live, update the COV increment toa larger value before re-enabling the programming object.

Check that the unit has been installed according to the installationinstructions.Make sure cables are not blocking the ventilation of the unit.LCS85 overheats.Clean out the dust in the unit with canned air (pressurized airused to clean computers and other sensitive devices).

A KNX, ModBus, M-Bus, orC•CURE-victor third partyintegration does not comeonline.

Refer to the appropriate integration application note. See Relateddocumentation. Verify that the value in the Vendor DLL field iscorrect, paying attention to letter case. Verify that any requiredvalues are entered correctly in the Vendor Reference field andthe Vendor Configuration Data list.

LCS85 diagnostic tools

The LCS85 hardware and user interface provide tools for diagnosing and troubleshooting hardwareand software problems with the LCS85.The primary LCS85 diagnostic tools include:

• the Diagnostic tab

• the Summary tab

• a serial point monitor

Other tools are also available, such as the SNMP Trap Browser and the ping command fordetermining the LCS85 IP address and ability to communicate on the TCP/IP network. See theTroubleshooting procedures for information on using the Trap Browser and the ping command.


Diagnostic tab

The Diagnostic tab displays LCS85 hardware status information that may aid troubleshooting.With the LCS85 object selected, select the Diagnostic tab to view current information about theLCS85 hardware status (Figure 39).

Figure 39: LCS85 Diagnostic tab

You can also select, drag, and drop the LonWorks Integration object into the Display panel andclick the Diagnostic tab to view information for the selected LonWorks Integration object. Figure 40shows the Diagnostic tab for the LonWorks Integration object and Figure 41 shows the Diagnostictab for the BACnet IP Integration object.


Figure 40: LonWorks integration Diagnostic tab


Figure 41: BACnet IP integration Diagnostic tab

Summary tab

The Summary tab (Figure 42) in the SMP UI provides a quick view of the status of the objects anditems currently in your site.Select, drag, and drop an object from the Navigation panel in the Display panel, and click theSummary tab. When you first select the Summary tab, the LCS85 requests the status of the items inthe Display panel (Figure 42). This request may take a few minutes.For additional information and explanations of the attributes found in the Summary and Diagnostictabs, refer to the Object Help in the Metasys® Site Management Portal Help (LIT-1201793).


Figure 42: LCS85 Summary tab

Troubleshooting procedures

Verifying Ethernet/IP network communications (Ping)

You can use the ping command to verify that computers on the Ethernet/IP network cancommunicate with other computers on the network.To use the ping command, you must have a computer configured to use the TCP/IP protocol and atleast one other computer connected to the network.To verify the computers can communicate on the network using the ping command:

1. Go to Start > Run.Type cmd, then click OK to display the Command prompt. (If you are usingWindows 8.1, Windows 8, Windows Server 2012 R2, or Windows Server 2012, type CommandPrompt from the Start screen, then select Command Prompt from the Apps results.)

2. Type the ping command. Use the format ping xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IPaddress or domain name of the computer you want to ping. (For example: ping 198.81.196.2 orwww.jci.com.)

3. Press Enter.

If you get a reply, the computers are communicating on the network.If you do not get a reply, try pinging your own computer address.

• If you can ping your own address but not any other addresses, the problem is with the network.Check the Link light on the network card.

• If you cannot get a reply from your own address, the problem is probably with the network cardin your computer or with the TCP/IP properties. Check the network card in your computer, andverify the TCP/IP properties.

Note: Certain firewall and antivirus settings can cause an unsuccessful ping. If a ping isunsuccessful, check your configuration settings.


Determining the IP address

You can find the IP Address of the LCS85 using Control Panel or by using a Command Prompt.To determine the LCS85 IP address using Control Panel:

1. In Control Panel, select Network and Internet > Network and Sharing Center. The Network andSharing Center appears (Figure 43).

Figure 43: Network and Sharing Center

2. Click Local Area Connection. The Local Area Connection Status window appears (Figure 44).


Figure 44: Local area connection status

3. Click Details. The Network Connection Details window appears and displays the current IPaddress (Figure 45).


Figure 45: Network connection details

To determine the LCS85 IP address using the Command Prompt:

1. On the Start menu, select Command Prompt. (If you are using Windows Server 2012 R2 orWindows Server 2012, type Command Prompt from the Start screen, then select CommandPrompt from the Apps results.) The Command Prompt appears (Figure 46).

Figure 46: Command Prompt


2. Type ipconfig and press Enter. The IP address appears (Figure 47).

Figure 47: IP address displayed in Command Prompt

LCS85 technical specifications

Table 17: NxE85/NIE89/LCS85 Software System Recommendations for Installation/Upgrade

Product Code Number

MS-NXE85SW-0 Network Integration Engine Software for 10,000objects (new projects only software)

MS-NIE89SW-0 Network Integration Engine Software for 10,000objects (new projects only software)

MS-LCS85SW-0 Network Integration Engine Software for 10,000objects (new projects only software)

Recommended ComputerPlatform

IntelXeon E5506, 2.13 GHz, 4 MB Cache

2 x 160 GB 7.2K SATA, 8.9 cm (3.5 in.) Cabled

3 Gbps, RAID 1 configuration with add-in SAS6/iR (SATA/SASController)

Recommended Memory 8 GB RAM minimumHard Disk 160 GB minimum

Supported 64-bitOperating Systems andSoftware

• Windows® Server® 2016 with Update (KB4489890) (64-bit)

• Windows® Server® 2012 R2 with Update (KB2919355) (64-bit)

• Windows® Server® 2012 with Update (KB3172614) (64-bit)Note: Microsoft .NET Framework 3.5 Service Pack (SP) 1 andMicrosoft .NET Framework 4.6.1 are required for any of theoperating systems.


Table 17: NxE85/NIE89/LCS85 Software System Recommendations for Installation/Upgrade

Supported OperatingSystems for Metasys ClientComputers

Windows® 10 Pro and Windows 10 Enterprise Editions (version 1809or later) (64-bit)

Windows® 8.1 Pro and Windows 8.1 Enterprise Editions with Update(KB2919355) (64-bit)

Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1(64-bit)

Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1(32-bit)

Apple® OS X® 10.12 Sierra

Apple® OS X® 10.11 El Capitan

Apple OS X 10.10 Yosemite

Note: Apple operating systems are supported for Metasys clientcomputers only. Also, in Apple OS X, you cannot view Graphics+graphics in the Site Management Portal UI.

Internal Optical Drive DVD ROM, SATA

Supported Web BrowserSoftware for Metasys SiteManagement Portal ClientComputers

Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47or later

Note: In Internet Explorer 11, select the Use Microsoftcompatibility lists option, found under Tools > CompatibilityView Settings, to ensure that websites appear and functioncorrectly.

Google® Chrome™ version 72.0.3626.121 or later

Apple® Safari® 11 or later

Other browsers, such as Mozilla® Firefox®, may also be used but arenot fully supported.

Supported VirtualEnvironments Microsoft Hyper-V™, VMWare®

Network Communication

Selectable Network Interface (if computer has multiple network cards,during NxE85/NIE89/LCS85 installation, select the network card thatwas configured for Metasys system use before installation)

Ethernet network interface card 10/100/1000 Mbps (100 Mbps orbetter recommended)

Recommended DataProtection

Uninterruptible power supply (UPS)

Smart-UPS SC 450VA, 280 W, 120 VAC input/output, NEMA 5-15Routput connections, OEM Part No. SC450RM1U

The performance specifications are nominal and conform to acceptable industry standard. Forapplication at conditions beyond these specifications, consult the local Johnson Controls office. JohnsonControls shall not be liable for damages resulting from misapplication or misuse of its products.


Appendix: configuring and maintainingpreferencesThe Metasys system provides customized preferences for the SMP UI. The preferences allowauthorized users to configure how the SMP UI behaves, including the sounds and colors, thestartup view, and the ability to add links to external applications that can be accessed from withinthe user interface of the LCS85 device.

Note: Preferences do not persist after an upgrade unless you take steps to save the settingsbefore you begin a system upgrade. See Preserving preferences in an upgrade.

Some steps in the following sections involve certain file operations, such as copying files andnavigating to specific folders. You can use Windows Explorer for these operations. Use RemoteDesktop to log in to the LCS85 remotely, and then type explorer at the command prompt.

Preferences concepts

System and user preferences

Preferences are divided into two categories: System preferences and User preferences.

System preferences

System preferences apply to all users who log in to the site or device. System preferences affect theperformance and operation of the system. Only the MetasysSysAgent user and the BasicSysAgentuser are authorized to configure system preferences. The maximum results shown in Global Searchand status colors used to show events are examples of system preferences. The SCT supports asubset of system preferences. If the SCT is installed on an ADS/ADX or ODS, the preferences areshared by the SMP and SCT UIs.Before you make system preference changes, the preferences are read from theDefaultSystemPreferences.xml file (Figure 48). This file contains the default system preferences. It isinstalled as part of the standard installation for all Metasys system devices.Once you make system preference changes, a new file called SystemPreferences.xml is created(Figure 48). This file stores the configured system preferences. If you have not yet configuredsystem preferences, this file does not appear in the directory.Both the default system preferences and system preferences files are located in the directory onthe Metasys system device (Table 18).Table 18: Location of preferences filesMetasys System Device File Location

LCS85 C:\ProgramData\Johnson Controls\MetasysIII\Preferences

Synchronizing system preferences within a site or reusing the system preferences on another site isa manual copy-and-paste process. Use this process to copy system preferences to other devices onthe site or to other sites. See Copying preferences between devices.


Figure 48: System preference files (Windows Server 2008 R2)

User preferences

User preferences apply to a specific Metasys system user. User preferences define how theinformation is displayed in the user interface and do not affect the operation of the system.The colors and marker styles of a trend display are examples of user preferences. Each user isauthorized to view and edit their own user preferences.The user preference file for each user is named UserPreferences-userID.xml, where userID is theidentification number of the user. Using a system-assigned identification number, rather than theactual user name, serves two purposes: it avoids any conflicts that might arise if the user namecontains special characters, and it maintains the connection to the user preferences file if the useris renamed.To view user identification numbers, open the Security Administrator screen and select UserPreference File Names under the View menu (this option is available only to the MetasysSysAgentuser). The user preference file names appear in the Roles and Users pane (Figure 49and Figure 50)and correspond to files on the Metasys device in the directory, as indicated in Table 18.Synchronizing user preferences within a site or reusing user preferences on another site is amanual copy-and-paste process. Use this process to copy user preferences to other devices on thesite or to other sites. See Copying preferences between devices.


Figure 49: User preference file (name as seen in the Security Administration in the SMP UI)

Figure 50: User preference file (as seen when accessing an LCS85 using Remote Desktop)

Managing preferences

If your Metasys system device is currently at Release 8.0 or later, preferences are archived on theSCT and are part of the upload/download process. Additionally, preferences are saved during asecurity backup when you upgrade.If your Metasys system device is currently at Release 7.0.x or earlier, preferences are not archivedon the SCT and are not saved during a security backup when you upgrade. You must managepreferences manually.


For information on managing preferences for each preference type, see the following sections:

• System preferences

• User preferences

Detailed Procedures

Configuring preferences

About this task:Note: To configure a user's preferences, you must log in as that user or as a user withAdministrator rights.

1. On the Tools menu of the SMP UI, click Configure Preferences. The Metasys Preferences dialogbox appears.

2. Set the preferences according to the Preferences section of the Metasys® Site Management PortalHelp (LIT-1201793).

If you specified Level 1-4 Sound Files on the Alarm Settings tab, place the alarm sound files into theaudio folder on the Metasys system device. The audio folder is located in the following directory:C:\Inetpub\wwwroot\MetasysIII\UI\audio

Note: If a sound file is missing from the folder, the Metasys system uses the default systembeep for that alarm priority.

Restoring default system preferences

1. Access the Metasys system device on which you want to restore the default system preferences.(For example, if this is an LCS85, use Remote Desktop or connect directly and log in with theMetasysSysAgent account.)

2. Navigate to the Preferences directory for the device, as shown in Table 18.

3. Delete the SystemPreferences.xml file. This file is recreated the next time the MetasysSysAgentuser defines a new system preference.

Copying preferences between devices

1. Access the Metasys system device that contains the preferences you want to copy. Forexample, if this is an LCS85, use Remote Desktop or connect directly and log in with theMetasysSysAgent account. If you are using Remote Desktop, make sure you also map thedevice disk drive by clicking the Local Resources tab and clicking Disk Drives under LocalDevices.


3. Copy SystemPreferences.xml (the system preferences file) and each UserPreferences-userID.xml (the user preferences file), where userID is the identification number that appearsin the Security Administration tool.

4. Paste the files onto the desktop of your computer.

5. If you are accessing the Metasys system device remotely, log out.


6. Access the Metasys system device to which you want to copy the preferences with theMetasysSysAgent user, and navigate to the Preferences directory for the device as shown inTable 18.

7. Paste the SystemPreferences.xml file and UserPreferences-userID.xml files that you copied toyour computer desktop in Step Paste the files onto the desktop of your computer. .

Restoring default user preferences

1. Log in to the SMP UI as the MetasysSysAgent user.

2. On the Tools menu of the SMP UI, select Administrator. The Security Administration toolappears.

3. On the View menu, select User Preference File Names. The user preference file names appearin the Roles and Users pane of the Security Administration tool.

4. Record the file name of the user whose preferences you want to restore.

Note: If the user has been removed from the system, there is no record of the user preferencefile name in the Security Administration tool. In this case, remove user preference files fromthe Metasys device that do not have a corresponding user preference file name in the SecurityAdministration tool.

5. Close the Security Administration tool and continue with Removing user preference files.

Removing user preference files

1. Access the Metasys device from which you want to remove the user preference files, andnavigate to the Preferences directory for the device as shown in Table 18.

2. Delete files named UserPreferences-userID.xml, where userID is the identification number thatappears in the Security Administration tool.

Note: Do not delete DefaultUserPreferences.xml.

Copying user preferences to another user

1. Log in to the SMP UI as the MetasysSysAgent user.

2. On the Tools menu of the SMP UI, select Administrator. The Security Administration toolappears.

3. On the View menu, select User Preference File Names. The user preference file names appearin the Roles and Users pane of the Security Administration tool.

4. Record the file name of the user whose preferences you want to copy (source user) and the filename of the user with whom you want to share those preferences (destination user).

5. Close the Security Administration tool.

6. Access the Metasys device and navigate to the Preferences directory for the device as shown inTable 18.

7. Delete the preference file (if it exists) of the destination user that you recorded in Step 4.


8. Copy and paste the user preference file of the source user that you recorded in Step 4. If youare using Windows Explorer, the file appears in the folder with Copy of appended to the frontof the file name.

9. Rename the copied file to the original name of the destination user's preference file.

Preserving preferences in an upgrade

About this task:If your Metasys system device is currently at Release 8.0 or later, you can preserve your system anduser preferences before you upgrade to a new system release. To do so, before you upgrade, useSCT 11.1 or later to upload the Metasys system device, then back up the archive. The preferences aresaved to the archive and are retained for either an in-place and an out-of-place upgrade. Then, torestore preferences after your system is upgraded, open the archive in SCT, upgrade the archive tothe new release, then download the archive (including security) to the system. The system and userpreferences are restored.If your Metasys system device is currently at Release 7.0.x or earlier, you need to manually preserveyour system and user preferences before you upgrade to a new system release. To preserve prefer-ences in an upgrade, follow these steps:

1. Before you begin the upgrade process, access the Metasys system device that contains thepreferences you want to copy. For example, if this is an LCS85, use Remote Desktop or connectdirectly and log in with the MetasysSysAgent account. If you are using Remote Desktop, makesure you also map the device disk drive by clicking the Local Resources tab and clicking DiskDrives under Local Devices.


3. Copy SystemPreferences.xml (the system preferences file) or UserPreferences-userID.xml (theuser preferences file), where userID is the identification number for each user with customizedpreferences. If you are saving preferences for multiple users, be sure to copy all files.

4. Paste these files to a safe location on your computer or network drive, or store them on othermedia.

5. Upgrade your system according to the Metasys® Server Installation and Upgrade Instructions(LIT-12012162) or the SCT Installation and Upgrade Instructions (LIT-12012067).

6. Copy the files from the safe location in Step 4 to the directory in Step 1.

Appendix: time zone, date, and time managementThe time zone, date, and time used by all devices connected to a Metasys site are synchronizedautomatically, preventing errors from manual time entry and clocks that become inaccurate overtime. Network-wide time management ensures that scheduling, trending, audit trailing, datacollecting, time-stamping of alarms, and other functions that require accurate time managementuse the same time, date, and time zone consistently for all system operations.Time synchronization occurs on the Metasys network when an engine or server sends an IAmLivemessage to the Site Director. If the IAmLive message fails, the engine or server sends anothermessage to get the time from the Site Director. When the time is synchronized between the devices,a second IAmLive message is successful.For network-wide time synchronization, the LCS85 designated as Site Director is considered thedevice time server because it provides the time zone, date, and time for all other engines/servers


on the site. All other devices are considered time clients because they receive the time zone, date,and time from the Site Director.To set the date and time in the Site Director (and therefore the entire site), you can set the timemanually or select a time server for the Site Director. The time server for the Site Director isreferred to as the site time server and should be a reliable source not on the Metasys network.Regardless of how you set the date and time, you must set the time zone in the Site Director.

Note: Do not edit the Device Time Servers attribute or Time Sync Period attribute for anyMetasys system engine or server.

Note: To ensure that the correct time is displayed on the SMP UI accessed from a clientcomputer, apply the most recent daylight saving time (DST) patch for the operating systemon all clients that access the Site Director. The DST patch is available from the Microsoft®Download Center (http://www.microsoft.com/downloads).

Overview of Time Synchronization

This section summarizes how time synchronizes on a site with various system components. Table19 lists the time sources for various system items. All time is in UTC time, and all system deviceshandle DST.Table 19: Time sourcesItem Time SourceLCS85 Trend Data LCS85LCS85 Events LCS85LCS85 Commands LCS85Annotations ADS/ADX or ODSEvent Acknowledgments ADS/ADX or ODS

ADS/ADX/ODS Site Director with LCS85s

About this task: On a site with an ADS/ADX or ODS Site Director and LCS85s, the following occurs:

1. The ADS/ADX/ODS Site Director comes online.

2. The LCS85s come online and check in with the Site Director.

3. Every 15 seconds, the LCS85s check for ADS/ADX/ODS online/offline conditions. If the ADS/ADX/ODS is offline, the LCS85s send an IAmLive message to the ADS/ADX/ODS every 20seconds.

4. When the ADS/ADX/ODS receives the IAmLive message, it attempts to validate the securitycredentials of the LCS85s. If the time in the LCS85s is different than the time in the ADS/ADX/ODS by 5 or more minutes, the LCS85 security credentials are invalidated.

5. When the LCS85 receives an invalid credential, the LCS85s request the current time from theADS/ADX/ODS and update the LCS85 time to match.

Note: The time synchronizes between an ADS/ADX/ODS and LCS85s only if the time differs by5 or more minutes. In the worst case scenario, one LCS85 could be 4 minutes and 59 secondsahead of the ADS/ADX/ODS, and another LCS85 could be 4 minutes and 59 seconds behind theADS/ADX/ODS.


http://www.microsoft.com/downloads

6. After time is synchronized and the ADS/ADX/ODS is online, the LCS85s send IAmLive messagesto the ADS/ADX/ODS every 5 minutes (instead of every 20 seconds).

Time Synchronization Methods

There are three methods for network time synchronization available in the Metasys system,including Microsoft Windows Time Synchronization Methods time synchronization, Multicast, andBACnet time synchronization.You can use the Microsoft Windows and Multicast methods when an SNTP master time serveris available. If the Site Director has no access to SNTP time servers, you can use the BACnetsynchronization method.To enable a time synchronization method, modify the Time Sync Method attribute for the Site. Seethe Steps for Successful Time Management and Setting the Time Synchronization Method sections.

Windows Time Synchronization

Windows time synchronization is Microsoft Corporation’s implementation of the standard WindowsSNTP w32time service. This method is also referred to as unicast synchronization. With this formof time synchronization, all routers can route UDP traffic. Windows time synchronization may havea larger time interval in which devices are out of sync with the SNTP master time server due toskewing and convergence.

Note: With Windows time synchronization, if you implement an intentional time change foryour site, all other devices on the site update with the new time within 5 minutes.

Multicast Time Synchronization

Multicast time synchronization is the Johnson Controls implementation of the SNTP w32time servicewith multicast capabilities and RFC-2030 compliance. This method provides the same features asthe Windows method, but also provides multicast functionality. The multicast method providesimproved Metasys time synchronization between the Site Director and supervisory devices. A timeserver provides the master time to the Site Director, and the Site Director in turn multicasts thetime to all supervisory devices on the Metasys network.When a supervisory device first signs up with the Site Director, it polls the Site Director for thecurrent time and matches its time with the Site Director time. By default, every 5 minutes the SiteDirector broadcasts the current time to all supervisory devices. If a particular device is 1.5 secondsor more adrift from the Site Director time, the device adjusts its time to match. Additionally, if theSite Director time changes by more than 1 to 1.5 seconds, it sends out a multicast time message toall devices within 2 seconds of the change.This form of time synchronization requires that all routers on the site support multicast routing(Internet Group Management Protocol, or IGMP) because the multicast time message crossesrouters. The Johnson Controls SNTP time synchronization reduces the time interval in which devicesare out of sync with the SNTP master time server.

Note: With multicast time synchronization, if you implement an intentional time change foryour site, all other devices on the site update with the new time within a few seconds.

BACnet Time Synchronization

BACnet time synchronization uses the BACnet protocol to synchronize with BACnet devices such asthe LCS85. Use this method when the Site Director has access to a BACnet time server. This methodis not available on the ADS/ADX/ODS.


Example Network

Figure 51shows an example system with a common time zone, date, and time management setup.This example is representative of the multicast and Windows time synchronization methods.The Site Director (in this case, an ADS) is configured to receive the date and time from an intranettime server. The date and time originates at an Internet time server (such as the atomic clock at theUnited States Naval Observatory). Using SNTP, the intranet time server requests the time from theInternet time server. The Site Director requests the time from the intranet time server. Then, usingthe Metasys system automatic time synchronization, and the manually configured time zone, theSite Director automatically provides the time zone, date, and time to the other engines or serverson the Metasys network.

Figure 51: Time Management sample system

Time Zone

The time zone of the Site Director defaults to (GMT-06:00) Central Time (US & Canada). If your siteis not in the Central time zone, set the time zone for your location. When you set the time zone inthe Site Director, it propagates the current time to all the engines and servers on the site. You mustset the time zone in the Site Director even if you select a site time server. In addition, set the timezone in all ADS/ADX/ODS devices, even though none of them are the Site Director.When a non-Site Director LCS85 is downloaded in a time zone that is not Central time, the LCS85might revert to Central standard time. This problem indicates that domain name resolution is notworking properly. Consequently, the LCS85 cannot reach the ADS/ADX/ODS Site Director afterdownload. You can solve this problem in one of two ways:

• Add the ADS/ADX/ODS name and IP address to the LCS85’s host file. (Search the Internet for helpwith editing a computer's host file.) The LCS85 communicates to the Site Director as long as bothhave the same date based on their time zones.

• Set the LCS85 to the Site Director’s time zone and write the LCS85’s Local Site Director attributeto the ADS/ADX/ODS’s IP address; then, upload the LCS85. After this step, each download of thedevice is given the site director’s IP address and correct time zone.


Site Time Server

Instead of setting a device's date and time manually, you can select a site time server. A site timeserver sets the date and time in the Site Director. Site time servers can be on your intranet, such asa domain controller, or on the Internet, such as the U.S. Naval Observatory Master Clock.For a list of Navy master clocks, go to http://tycho.usno.navy.mil/what.html.See the Selecting a Site Time Server for the Site Director LCS85 or Selecting a Site Time Server forthe Site Director ADS/ADX/ODS (Multicast Method Only) sections.

Time in Device Object and SMP UI Status Bar

The time zone, date, and time in the status bar of the SMP UI and the time zone, date, and time inthe device object of the device to which you are browsing are the same time; however, there maysometimes seem to be a discrepancy or delay between the two.In the Site Director, the time zone, date, and time in the device object of the device are set by youor by the designated site time server. In a non-Site Director LCS85, the time zone, date, and timein the device object comes from the Site Director. In a non-Site Director ADS/ADX/ODS, the timezone in the device object comes from your manual setting, but the date and time come from theSite Director.The Device object then passes the time zone, date, and time along to the status bar for display. Ifthe device is busy, it may take a few minutes for the time zone, date, and time to update correctly inthe status bar.

Steps for Successful Time Management

About this task:For successful time management, do the following:

1. Verify that each non-supervisory engine or server on the Metasys network has the correct SiteDirector defined.

See the Verifying the Site Director Defined for an Engine or Server section.2. Set the time synchronization method for the site.

See the Setting the Time Synchronization Method section.3. Set the time zone and then set the date and time, or select a time server for the site.

See the Configuring Time Settings in the Site Director LCS85 or Configuring Time Settings inthe Site Director ADS/ADX/ODS section.If an LCS85 is the Site Director, the time zone, date, and time are set in the user interface of theLCS85. See the Configuring Time Settings in the Site Director LCS85 section. If you have non-Site Director ADS/ADX/ODS device on the site, you must set the time zone for these servers.If an ADS/ADX/ODS is the Site Director, the time zone, date, and time are set in the WindowsOS of the computer where the ADS/ADX/ODS resides. See the Configuring Time Settings in theSite Director ADS/ADX/ODS section. If you have non-Site Director ADS/ADX/ODS devices on thesite, you must set the time zone for these servers.

4. For multicast time synchronization only, configure the SNTP multicast attributes for the site.

Note: See the Configuring Additional Multicast Time Synchronization Settings section.


http://tycho.usno.navy.mil/what.html

Verifying the Site Director Defined for an Engine or Server

About this task:For time synchronization to work properly, all engines or servers on a site must have the correctname for the Site Director in the Local Site Director attribute. If an engine or server has the wrongdevice defined as the Site Director, time synchronization may not work properly on your Metasyssite.

1. Log in to the engine or server.

2. Drag and drop the engine or server object to the Display frame.

3. Click the Advanced option button.

4. Scroll to the Site section and verify that the Local Site Director attribute contains the correctdevice (Figure 52). In this example, the Site Director is an LCS85.

Note: The Local Site Director may be entered as an IP address or host name. If entered as ahost name, the name is case sensitive (for example, QALOU-LCS85-1 is not the same as qalou-lcs85-1).

Figure 52: Site Director field

Note: If the Site Director field contains the wrong device or is empty, click Edit. Edit the SiteDirector entry and click Save.

Setting the Time Synchronization Method

See the Time Synchronization Methods section for descriptions of the methods.

1. Log in to the Site Director engine or server.

2. Drag the Site object to the Display frame.

3. Click Edit.


5. In the Time section, in the Time Sync Method drop-down box, select the desired timesynchronization method (Windows or Multicast).


Figure 53: Time Sync Method field

Note: To enable BACnet time synchronization, select the Windows option of the Time SyncMethod attribute. This attribute cannot be set to Multicast for BACnet time synchronization towork. Do not configure the Site Time Servers and Device Time Servers attributes. Leave themundefined.

6. Click Save.

Note:

• When the Time Sync Method attribute is set to Multicast and the ADS/ADX/ODS computer issynchronized with a time source other than itself, the Site Time Server must be an SNTP timeserver to allow the ADS/ADX/ODS to perform time synchronization. Time synchronizationoccurs when a change is detected in the ADS/ADX/ODS computer local clock or at the site-configured Time Sync Period.

• Enabling multicast time synchronization terminates the Windows win32time service, butchanging the Time Sync Method attribute back to Windows does not re-enable the service.Therefore, if you change Time Sync Method back to Windows, you must manually start thewin32time service or restart the Site Director. To restart the LCS85, you must have directaccess or a Remote Desktop connection. You cannot manually restart the LCS85 from theSMP UI.

Configuring Time Settings in the Site Director LCS85

If an LCS85 is the Site Director, you must set the time zone first, then set the date and time or selecta time server for the Site Director LCS85.

Note: Do not use the Windows OS time settings to set the time zone, date, or time on theLCS85. You must set the time zone, date, and time in the SMP UI.

Note: See the Verifying the Site Director Defined for an Engine or Server and Setting the TimeSynchronization Method sections before following the steps in this section.

Setting the Time Zone in the Site Director LCS85

1. Log in to the Site Director LCS85.


3. Click Edit.


4. In the Time section, in the Time Zone drop-down box, select the correct time zone for thedevice (Setting the Date and Time in the Site Director LCS85).

Figure 54: Time Zone in Site Object

5. Click Save.

If you are also manually setting the date and time in the Site Director LCS85, go to the Setting theDate and Time in the Site Director LCS85 section.If you are selecting a time server for the Site Director LCS85, go to the Selecting a Site Time Serverfor the Site Director LCS85 section.

Setting the Date and Time in the Site Director LCS85

About this task:Before manually setting the date and time in the Site Director LCS85, follow the steps in the Settingthe Time Zone in the Site Director LCS85 section.

1. In the navigation tree, right-click the Site object and select Command. The Command dialogbox appears.

2. Click the Set Time option button and enter a value in the text box (Figure 55).

Figure 55: Time in a Site Director LCS85

3. Click Send.


Note: If you have a site time server selected, do not attempt to set the time manually. If youhave one or more site time servers defined, sending this command generates an error.

4. In the navigation tree, right-click the Site object and select Command. The Command dialogbox appears.

5. Select the Set Date option button and select a date from the calendar (Figure 56).

Figure 56: Date in a Site Director LCS85

6. Click Send.

Note: If you have one or more site time servers defined, sending this command produces anerror. If you have a site time server defined, do not attempt to set the time manually.

The Site Director time zone, date, and time are now set and propagate to all other engines on thesite.

Selecting a Site Time Server for the Site Director LCS85

About this task:Before selecting a site time server for the Site Director LCS85, follow the steps in the Setting theTime Zone in the Site Director LCS85 section.

1. Reset the LCS85 for the time zone change to take effect.

2. Log in to LCS85.


4. Click Edit.

5. In the Time section, in the Site Time Servers field, click the browse button (Figure 57).

Note: Leave the Device Time Servers field blank. Do not change the value for the Time SyncPeriod attribute.


Figure 57: Site Time Servers in the Site Object

6. In the screen that appears (Figure 58), click Add.

Figure 58: Add Site Time Server

7. Enter the IP address of the SNTP server from which the Site Director receives its time.

Note: Specify a host name only if a DNS server is available to the Site Director. Leave theDevice Time Servers field blank.

Note: If you add more than one address, the Site Director LCS85 tries to contact the firstaddress. If that contact fails, the LCS85 contacts the second one, and so on.

8. Click OK.

9. Click Save.

The Site Director now requests the date and time from the selected time server and propagates itto all other engines on the site.

Configuring Time Settings in the Site Director ADS/ADX/ODS

Set the time zone first, then set the date and time or select a time server for the Site Director ADS/ADX/ODS.Notes:

• See the Verifying the Site Director Defined for an Engine or Server and Setting the TimeSynchronization Method sections before following the steps in this section.


• If you select a site time server for your Site Director ADS/ADX/ODS, and you also set the timemanually in the ADS/ADX/ODS, the manual time is overridden at the end of the time specified inthe Time Sync Period attribute (the default time is 1 hour).

Setting the Time Zone in the Site Director ADS/ADX/ODS

1. In the lower-right corner of the ADS/ADX/ODS computer screen, click the time. The Date andTime Properties box appears (Figure 59). The appearance of this screen varies depending onthe OS.

Figure 59: Time and Date on a Site Director ADS/ADX/ODS

2. Click Change date and time settings, then click Change time zone. The Time Zone Settingsbox appears (Figure 60).

Figure 60: Time Zone on a Site Director ADS/ADX/ODS

3. Select a time zone from the drop-down list.

4. Select Automatically adjust clock for Daylight Saving Time, if present.


5. If you have a non-Site Director ADS/ADX/ODS on your site, set the time zone in the server byfollowing the instructions in this section.

If you are also manually setting the date and time in the Site Director ADS/ADX/ODS, go to theSetting the Date and Time in the Site Director ADS/ADX/ODS section.If you are selecting a time server for the Site Director ADS/ADX/ODS, click OK and go to theSelecting a Site Time Server for the Site Director ADS/ADX/ODS (Windows Method Only) orSelecting a Site Time Server for the Site Director ADS/ADX/ODS (Multicast Method Only) section.

Setting the Date and Time in the Site Director ADS/ADX/ODS

About this task:Before manually setting the date and time in the Site Director ADS/ADX/ODS, follow the steps in theSetting the Time Zone in the Site Director ADS/ADX/ODS section.

1. Click the time in the lower-right corner of the screen. Click Change date and time settings.

2. Set the time and date.

3. Click OK.

The Site Director time zone, date, and time are now set and propagate to all other engines orservers on the site.

Selecting a Site Time Server for the Site Director ADS/ADX/ODS (Windows MethodOnly)

About this task:If you set up a site time server for your Site Director, you can set the date and time manually in theADS/ADX/ODS, but the manual settings are overridden at the end of the Time Sync Period.Before selecting a site time server for the Site Director ADS/ADX/ODS, follow the steps in the Set-ting the Time Zone in the Site Director ADS/ADX/ODS section.

1. On the ADS/ADX/ODS computer, press the Windows key + R. The Run dialog box appears(Figure 61).

2. Type Net time /setsntp:"10.10.16.1 10.10.16.2", where 10.10.16.1 and 10.10.16.2 are exampleIP addresses of time servers.

Figure 61: Run dialog box


Note: Obtain the address of a suitable time server from your IT department. Be sure that thequotation marks are included, especially when listing multiple time servers.

3. Click OK.

The Site Director now requests the date and time from the selected time server and propa-gates it to all other engines and servers on the site.

Selecting a Site Time Server for the Site Director ADS/ADX/ODS (Multicast MethodOnly)

About this task:Before selecting a site time server for the Site Director ADS/ADX/ODS, follow the steps in the Set-ting the Time Zone in the Site Director ADS/ADX/ODS section.

1. Log in to the ADS/ADX/ODS.


3. Click Edit.

4. In the Time section, in the Site Time Servers field, click the browse button (Figure 62).

Note: Leave the Device Time Servers field blank. Do not change the value for the Time SyncPeriod attribute.

Figure 62: Site Time Servers in the Site Object

5. In the screen that appears (Figure 63), click Add.


Figure 63: Add Site Time Server


Note:

- Specify a host name only if a DNS server is available to the Site Director. Leave the DeviceTime Servers field blank.

- For Windows time synchronization, if you add more than one address, the Site DirectorADS/ADX/ODS tries to contact the first address. If that fails, the ADS/ADX/ODS contactsthe second one, and so on.


8. Click OK.

9. Click Save.

The Site Director now requests the date and time from the selected time server and propagates itto all other engines and servers on the site.

Configuring Additional Multicast Time Synchronization Settings

In addition to selecting the multicast time synchronization method (Setting the TimeSynchronization Method), you must define other multicast attributes.

1. Log in to the Site Director engine or server.


3. Click Edit.


5. In the Time section, modify the attributes listed in Figure 64.


6. Click Save.

Figure 64: Multicast time synchronization fields

Table 20: Multicast time synchronization fieldsAttribute Description

Multicast Group Address

Specifies the IP address used to multicast the SNTP message.This address identifies the group of devices to receive the SNTPmessage. The RFC-2030 defined standard address is 224.0.1.1.The address is configurable to allow site specific use.

Multicast UDP Port

Specifies the UDP port on which multicast time synchronizationpolls and listens for messages. The RFC-2030 defined standardport is 123.The UDP port defined here must match the TimeServer’s UDP port for successful polling to occur.

Multicast TTL

Specifies the Time to Live (TTL) for a multicast message. Thevalue indicates the number of router hops (number of routers topass through) allowed before the message is not sent. Routersmust be configured to pass multicast messages to allow the timesynchronization message to pass.

A default value of 1 typically stops the multicast messagefrom leaving the IP subnet of the Site Director. Most routersdecrease the existing TTL upon arrival of a packet, and dropthe packet instead of rerouting it when the TTL reaches 0.

Multicast Heartbeat IntervalSpecifies the number of minutes between forcing a multicasttime synchronization message from the Site Director toparticipating devices.


Single point of contact

APAC Europe NA/SAJOHNSON CONTROLS

C/O CONTROLS PRODUCT MANAGEMENT

NO. 32 CHANGJIJANG RD NEW DISTRICT

WUXI JIANGSU PROVINCE 214028

CHINA

JOHNSON CONTROLS

WESTENDHOF 3

45143 ESSEN

GERMANY

JOHNSON CONTROLS

507 E MICHIGAN ST

MILWAUKEE WI 53202

USA

For more contact information, refer to www.johnsoncontrols.com/locations.

Product warrantyThis product is covered by a limited warranty, details of which can be found atwww.johnsoncontrols.com/buildingswarranty.

Software termsUse of the software that is in (or constitutes) this product, or access to the cloud, orhosted services applicable to this product, if any, is subject to applicable terms set forth atwww.johnsoncontrols.com/techterms. Your use of this product constitutes an agreement to suchterms.

© 2019 Johnson Controls. All rights reserved. All specifications and other information shown were current as of documentrevision and are subject to change without notice.

https://www.johnsoncontrols.com/locations

http://www.johnsoncontrols.com/buildingswarranty

https://www.johnsoncontrols.com/techterms

lcs85 commissioning guide - johnson controlscgproducts.johnsoncontrols.com/met_pdf/12011568.pdf ·...

Documents