LonWorks Network Integration with NAE and LCS Technical Bulletin

Transcription

1 LONWORKS Network Integration with NAE and LCS Technical Bulletin Code No. LIT Software Release 9.0 Issued August 2017 Refer to the QuickLIT website for the most up-to-date version of this document. Introduction...3 Summary of Changes...3 Related Documentation...3 Key Concepts...4 Archive Database...4 Engine Database...4 Engine Database Generation...4 Network Configuration and Device Limits...4 NAE...4 LCS...5 LONWORKS Configuration Tool...5 LNS Device Configuration Plug-in...5 Integration Overview...5 LONWORKS Network Integration...6 Integrated LONWORKS Objects...6 Object Hierarchy...6 LONWORKS Integration Object...6 Views...7 Resource Files...10 Items in the Navigation Tree in the Metasys Site Management Portal User Interface...11 LONWORKS Device Object...11 Device Naming Conventions During Auto Discovery...11 LONWORKS Point Objects...11 Mapping of Field Values...11 LONWORKS Field Point Object Support...11 Mapping Internal Points of LN Series Controllers...11 LONWORKS Device Extensions...20 Detailed Procedures...24 Adding a LONWORKS Integration Object...24 Inserting Resource Files...28 Defining an Engine on the LONWORKS Trunk...32 Using Auto Discovery...32 Mapping LONWORKS Devices Using Auto Discovery...33 Mapping Field Points in LONWORKS Devices Using Auto Discovery...37 Manually Mapping a Series of LONWORKS Enabled Devices...40 Manually Mapping Field Points in LONWORKS Enabled Devices...45 Using Relearn in the Engineering View...47 Using the Engineering View to View Device and Point Data...48 Using the Engineering View to Command Network Variable Inputs and Edit NexSys Point Data...49 Viewing Routers...50 Viewing Detailed Router Information...53 Trending LONWORKS Device Data

2 Troubleshooting...59 Appendix: Using a Flat LONWORKS System with LCS...61 Basic System Overview...61 Physical Components...61 TCP/IP Network...61 LCS85 Control Server...61 LNS Computer...61 LONWORKS IP Routers...61 Logical Components...62 CEA-852 Standard...62 CEA-852 Channels...62 CEA-852 Configuration Server...62 Basic System Setup...62 Choose the 852 Configuration Server...63 Configure the 852 Configuration Server...63 Configure the LONWORKS IP Routers...63 Configure LNS Computer...63 Complex System Setup...64 Network Partitioning...65 Guidelines for Network Partitioning...66 Basic Partitioned System Setup...67 Choose the 852 Configuration Server...67 Configure the 852 Configuration Servers...67 Configure the Channels...67 Configure the LNS Computer...67 Complex Partitioned System Setup...68 Appendix: LCS85 Gesytec 852 Configuration Settings...69 Easylon IP Interface Configuration Settings...69 Configuring the LCS85 for Use with the Loytec Configuration Server...70 Configuring the LCS85 for Use with the Echelon Configuration Server...72 Configuration Servers...73 Configuring the Loytec Config Server...73 Configuring the Echelon Config Server...79 Configuring LONWORKS Interfaces...81 Troubleshooting Communication between the Configuration Server and Devices...83 Technical Bulletin 2

3 Introduction The Network Automation Engine (NAE) models and LONWORKS Control Server (LCS) with a LONWORKS network interface serve as LONWORKS network integrators within the Metasys system. Note: The LCS is a server; however, in this document, engine refers to both the Network Automation Engine (NAE) and LONWORKS Control Server (LCS), unless otherwise noted. As a LONWORKS network integrator, the engine monitors and supervises LONWORKS enabled devices on multiple network segments (or trunks) and is configured as a device on the LONWORKS network. Data is presented on a web browser that is logged in to the web-enabled user interface of the engine, or to any other NAE, LCS, Application and Data Server (ADS), or Open Data Server (ODS) requesting data over the IP network. This document describes how to perform the tasks required to configure the engine as a LONWORKS network integrator, including how to: add a LONWORKS Integration object insert resource files define an engine on the LONWORKS trunk map LONWORKS enabled devices using Auto Discovery map field points in LONWORKS devices using Auto Discovery map a series of LONWORKS enabled devices manually map field points in LONWORKS enabled field devices manually use the Engineering view to view device and point data use the Engineering view to command Network Variable Input (NVIs) and NexSys points view detailed router information trend LONWORKS device data Summary of Changes No technical changes were made to the document for this release. Related Documentation The documents in Table 1 contain information related to the installation, operation, and troubleshooting of the NAE and LCS in a Metasys system environment, and information on the software tools used to configure and update the engine and the Metasys system. Once you are connected to an ADS, Extended Application and Data Server (ADX), ODS, NAE, or LCS, you can access important user information in the Metasys SMP Help (LIT ) and Metasys SCT Help (LIT ). Table 1: LONWORKS Network Integration with NAE or LCS Related Documentation For Information On See Document Installing the NAE55 or NIE55 Installing the NAE35 or NAE45 Upgrading the LCS85 Creating, Editing, and Loading Archive Databases with the System Configuration Tool (SCT) Metasys System Supported LONWORKS Objects, Using the Command Status Mapping Tool Commissioning the NAE Commissioning the LCS85 NAE55/NIE55 Installation Instructions (Part No ) NAE35/NAE45 Installation Instructions (Part No ) LCS85 Installation and Upgrade Instructions (LIT ) Metasys SCT Help (LIT ) 1 Metasys SMP Help (LIT ) 1 NAE Commissioning Guide (LIT ) LONWORKS Control Server (LCS) 85 Commissioning Guide (LIT ) 3

4 Table 1: LONWORKS Network Integration with NAE or LCS Related Documentation For Information On See Document Configuring and Commissioning Devices on the LONWORKS trunk General LONWORKS Network Information 1 This LIT number represents a print-friendly version of the Help. LN-Builder 3.4 Technical Bulletin (LIT ) Echelon Corporation website ( LONMARK Interoperability Association website ( Key Concepts Archive Database The archive database is the Metasys system site database stored (archived) by the System Configuration Tool (SCT). The archive database includes the engine databases for one or more engines on the site. Engine Database The engine database contains configuration information about the field controllers supervised by that engine, and the points within those controllers mapped into the Metasys system. The engine database resides in flash memory for the NAE and hard disk for the LCS. Any online changes to the database are not automatically saved to the flash memory or hard disk; you must perform an Archive command to save your changes. The SCT uploads and archives the engine database from the flash memory to hard disk or other long-term storage media. The uploaded database or a database created offline in the SCT can also be downloaded to the engine from the SCT. Engine Database Generation To generate an engine database of LONWORKS enabled field devices, you must first set up a site database, define the engine, and then populate the engine with LONWORKS enabled field devices and point objects. You can do this online by accessing the engine in the Site Management Portal (SMP) UI from a separate computer or offline with the SCT; then the database can be downloaded later to the engine. Note: We strongly advise that you do not browse to the SMP UI from a computer running a server-class operating system (OS). By default, Windows Internet Explorer Enhanced Security Configuration is enabled on server-class operating systems, and may prevent the SMP UI from launching or loading properly. Access the SMP UI from a computer that is not running a server-class OS. In online generation mode, the engine database can be created using the Auto Discovery feature for LONWORKS enabled devices and points within a network that are already configured and in operation. For other options, see the LONWORKS Network Integration section. Network Configuration and Device Limits Configuration and commissioning of the LONWORKS trunk is performed using the LONWORKS network configuration tool LN Builder. You may also use a third-party LONWORKS network configuration tool, such as the Echelon LonMaker tool to configure and commission the LONWORKS trunk. See the LONWORKS Network Integration section. NAE Each NAE monitors and controls LONWORKS field devices connected to its single LONWORKS trunk. The LONWORKS trunk from the NAE is a single network segment, supporting up to 64 nodes without a repeater. Adding a physical repeater to the trunk allows the NAE to support 127 nodes on a single segment. Depending on the hardware model, the NAE can support up to 255 nodes if LONWORKS routers are used on the trunks. Optimum performance is achieved using a maximum of 100 nodes or 1,000 Network Variables (NVs). The NAE supports up to 5,000 total objects, depending on the hardware model. 4

5 LCS The LCS connects to a CEA-852 channel, which runs on a TCP/IP-based network. It supports up to 20 LONWORKS IP routers, up to 1,000 total LONWORKS devices under those routers, and 10,000 objects total. Note: The implementation of up to 20 LONWORKS IP routers has been tested in a lab environment. However, there are sites that successfully run with more LONWORKS IP routers. Run more than 20 LONWORKS IP routers at your own risk. You can increase the number of objects supported to 25,000 with an LCS license upgrade; however, permanent status item limitations apply after this upgrade. See the LCS Permanent Status Item Limitation section. LCS Permanent Status Item Limitation When you upgrade your LCS to 25,000 objects, Permanent Status Item support is limited to 11,000 items. If you exceed the 11,000 Permanent Status Item limitation, point values for Permanent Status Items no longer continuously update on each polling cycle (see Point Object Polling). In most cases, increasing the number of continuously polled items (Permanent Status Items) degrades the performance to an unacceptable level before reaching the 11,000 Permanent Status Item limit. For example, if your system has 10,000 Permanent Status Items with a 50 point-per-second scan rate, then the total scan time to complete one polling cycle is approximately 200 seconds, assuming optimal field conditions and router performance. User interaction, such as displaying LONWORKS point objects, does not exceed the limit. The majority of Permanent Status Items stem from extensions and feature objects. For more information on Permanent Status Items, see the Permanent Status Item Count section. LONWORKS Configuration Tool Any LNS based configuration tool (including LN Builder and LonMaker) can configure LN Series controllers. LNS Device Configuration Plug-in LONWORKS devices are configured using LN Builder. For ease of programming, all LN Series and Flexible System Controller (FSC) devices have plug-ins that allow the user to change device parameters. In addition to changing parameters, the FSC Plug-in allows the user to create an import file that preserves the custom point names that can be imported into the NAE. You can also use the Point Scheduler to make changes to points. Integration Overview In the Metasys system, information coming from devices within an integrated network (LONWORKS trunk, N1 network, N2 Bus, BACnet IP network, or Master-Slave/Token-Passing [MS/TP] network) appears in the same user interface framework as data native to the engine. The following standard engine functions are available for field points that are mapped into the engine from devices in the integrated networks: basic monitoring and commanding alarm and event management control system sequences and interlocking scheduling energy optimization historical data management (trending) audit trails (transaction data management) system diagnostics 5

6 LONWORKS Network Integration LONWORKS network integration enables the integration of LONWORKS devices into the Metasys system. The LONWORKS Integration object runs in an engine. The engine serves as a LONWORKS compatible workstation, from which you can monitor and command LONWORKS objects using network variables in LONWORKS devices. The engine maps the LONWORKS network variables, NexSys points, and LN Series free-programmable internal objects to integrated objects that you can use in Metasys system applications, and provides features such as alarming. Integrated LONWORKS Objects Integrated LONWORKS objects represent LONWORKS devices and network variables and appear in the Navigation tree. When you select an integrated LONWORKS object, the Focus view displays LONWORKS parameters in an available panel on the user interface. Object Hierarchy Figure 1 illustrates the LONWORKS object hierarchy found in the Navigation Tree. Figure 1: Object Hierarchy LONWORKS Integration Object Use the LONWORKS Integration object to configure the parameters for LONWORKS network integration and its individual LONWORKS trunk. Each LONWORKS Integration object supports a single LONWORKS domain, and only one LONWORKS Integration object is allowed per engine. Refer to the Metasys SMP Help (LIT ) for further details on supported objects. 6

7 Views The LONWORKS Integration object offers five views: Focus View Hardware View Diagnostics View Engineering View Summary View Note: Only the Focus view is available during offline configuration with the SCT. Focus View The Focus view contains basic user data including the object name and the device name of the host engine for the LONWORKS Integration object. Hardware View The Hardware view displays the selected object s hardware related attributes/parameters and their defined values. Diagnostics View The Diagnostics view displays LONWORKS diagnostic attributes, such as Statistics and Metrics, for troubleshooting purposes (Figure 2). You must send a Latch Statistics command to the LONWORKS Integration Object to update these values. Users with high privileges can have access to this view. 7

8 Figure 2: Diagnostics View and Permanent Status Item Count Permanent Status Item Count Found under the Metrics section of the Diagnostic view, the Permanent Status Item Count displays the number for Change of Value (COV) signups for LONWORKS Point Objects (Figure 2). This attribute is especially important when observing the 11,000 Permanent Status Item limitation associated with an LCS85 license upgrade. Objects associated with the Permanent Status Item Count include the following: Alarm Extensions (including Intrinsic Alarming) Trend Extensions (COV only) Totalization Extensions (including Event and Runtime) Load Extension LCT Object (Input Reference Attribute) Auto Shutdown (Control Attribute) DLLR Object (EOI Attribute) Data Broadcast Object (Input Reference Attribute) Event Enrollment Object 8

9 Generator Load Control (JCI Control Start Reference and JCI Current Consumed WH Reference Attributes) Global Data Share Object (Master and Alternate Master attributes) Interlock Object (Interlock Definition Attribute) Loop Object (Reference Attribute) Optimal Start Object (Control Attribute) Signal Select Object (Input List and Average Output Attributes) When active, the following panels place the objects in the Temporary Status Item list and then move the objects immediately to the Permanent Status Item list until the panel is closed. Once you close the panel, the object moves back to the Temporary Status Item list if the Temporary Status Item Expiration Time has not expired. If the Temporary Status Item Expiration Time has expired, the object is removed from the Permanent Status Item list. Graphic Object (each instance of a LONWORKS Point Object when the graphic is active) Global Search Query Group Object (only when the Group Object is active) Point Summary Display Panel Device Point Summary Display Panel User View Engineering View The Engineering view allows you to view data in LONWORKS devices that are connected to the NAE or LCS LONWORKS trunk. This view is typically used by advanced users with the appropriate access authority to directly view and change data in LONWORKS devices. LN Series free-programmable internal points cannot be viewed or modified. The devices and network variables may or may not be integrated (mapped) to engine objects in the NAE or LCS Navigation Tree. Routers are shown in this view, but cannot be mapped as devices. Any devices or network variables that are mapped to engine objects are displayed in a Mapped Devices folder. The Engineering view contains the Integration Tree and Integration view panels. The Integration Tree panel contains a list of known LONWORKS devices connected to the engine along with their network variables. The Integration view panel displays the details about the LONWORKS device or network variable selected in the Integration Tree. Note: You must issue a device discovery command to view any routers in the Engineering view. After you create a LONWORKS Integration object, the Integration Tree is empty until you add LONWORKS enabled devices, either manually or by using Auto Discovery. See Detailed Procedures for instructions on adding LONWORKS devices. The Engineering view Integration Tree is the only place you can view routers, as they are not shown in the Navigation Tree. Detailed information about each router is available in the Summary view. Mapped Devices Folder A Mapped Devices folder is located under the LONWORKS Integration object in the Engineering view. This folder only contains mapped devices and does not show routers because they cannot be mapped. Summary View In the Integration view section, you can use the Summary view to display a list of devices and the values of their network variables, or the Detail view to see the parameters of a selected item. The content in the Summary view is dependent on the device selected in the Integration Tree. 9

10 Resource Files The LONWORKS network integration requires resource files to support integrating LONWORKS enabled devices. Device resource files have file extensions of.xif (External Interface File),.TYP (Type File), and.fpt (Functional Profile Template), and provide device type and configuration data. For example, an LN-VAVLF-1 controller has the following three device specific resource files: LN-VAVLF XIF, LNVAVL1.TYP, and LNVAVL1.FTP. Note: TYP and.fpt resource files may not be provided. In this case, only the.xif file is needed. Engine In addition to the device specific resource files, the LONWORKS Integration object requires the STANDARD.TYP and STANDARD.FPT resource files, and a NVConfig.dat file. This NVConfig.dat file is created automatically, but you need to update it with the correct configuration data using a network configuration tool, such as LN Builder. See Defining an Engine on the LONWORKS Trunk. Note: Once you have created and updated the LONWORKS Integration object, add all the resource files for the LONWORKS enabled device types you intend to add to the LONWORKS trunk. Adding, importing device data, or mapping a LONWORKS enabled device before loading the resource files can produce undesired results that may require a reboot. Field Device The engine indicates whether the required XIF resource file is present with an attribute called XIF Present. This attribute is located under the Focus and Hardware tabs of the field controller (Figure 3). A value of True indicates that the required XIF resource file is present, and False indicates that the file is missing. If the file is missing, Critical Resource Missing is shown for the status of the device. An alarm message appears when an object without the required XIF file is added to the integration. If any other resource file type is missing, the point object may display Data Conversion Error. Figure 3: Resource File Indication 10

11 Items in the Navigation Tree in the Metasys Site Management Portal User Interface You can use LONWORKS enabled devices, folders, and NVs that appear as integrated (mapped) objects in the Navigation Tree as object references, allowing the integrated object to be referenced as any other Metasys system object. The following rules apply when adding integrated LONWORKS enabled objects to the Navigation Tree: You must add integrated LONWORKS device objects under the LONWORKS Integration object. Note: You may add devices under a folder as long as the folder resides under the LONWORKS Integration object. You must add LONWORKS point objects under a LONWORKS device object. To group LONWORKS point objects within a LONWORKS device, add folder (container) objects under the LONWORKS device object and add the LONWORKS point objects under a folder object. Note: See the Object Hierarchy section for an illustration of objects in the Navigation Tree. LONWORKS Device Object LONWORKS Device Objects are a representation of a single LONWORKS Field device. Each field device, identified through the DSN address, can be mapped only once. Device Naming Conventions During Auto Discovery Device names for auto-discovered devices consist of the device type (extracted from the device's Program ID) and its DNS address, providing a unique identifier for each device (for example, Plant Controller 42 0D 04). The DSN number is used as a unique identifier for each device. Since the DSN number is not a required part of the name, it can be removed if necessary. LONWORKS Point Objects LONWORKS Point Objects represent point data from a particular LONWORKS Device Object. The data is represented as an analog input (AI), analog output (AO), binary input (BI), binary output (BO), multiple input (MI), and multiple output (MO). Generic integration objects (GIOs) can be added via import file only. Mapping of Field Values Each LONWORKS Point Object can be mapped from an LN Series Internal, Network Variable, or NexSys Point object. In the case of Network Variable or NexSys Point, the mapping can be of the whole or a portion of the entity. LONWORKS Field Point Object Support The Metasys system supports network variables of all LONMARK SVNTs, all point types in NexSys controllers, and all LN Series Free Programmable Controller internal point types. Mapping Internal Points of LN Series Controllers You can map the internal points of LN Series Free Programmable Controllers. Once you expose these points, you can monitor and control them from the network engine. The points include internal variables, constants, inputs, outputs, controllers, timers, and optimal start objects. Keep in mind that each mapped object contributes to the maximum object count allowed for the engine. Table 2 shows a list of available mapping points. Table 2: Mapping of LN Points to Engine Objects Object Type Target Reference 1 Valid Engine Object Types 2 Variable Constant LNV.x LNC.x AI/AO/BI/BO/MI/MO AI/AO/BI/BO/MI/MO Controller Type Supported LN-Basic LN-Basic 11

12 Table 2: Mapping of LN Points to Engine Objects Object Type Target Reference 1 Valid Engine Object Types 2 Controller Type Supported Input LNI.x AI/AO/BI/BO LN-Basic Output LNO.x AI/AO/BI/BO LN-Basic Controller LNCO.x AI/AO LN-Basic Optimum Start LNOS.x BI LN-Basic Timer LNT.x AI/AO LN-Basic Numeric Variable LNVN.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Enumeration Variable LNVE.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Numeric Constant LNCN.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Enumeration Constant LNCE.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Hardware Input LNHI.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Hardware Output LNHO.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Smart Sensor Inputs LNSI.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Wireless Sensor Inputs LNWI.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) Boolean Variable LNVB.x BI/BO LN-GPI-600 (all versions) Boolean Constant LNCB.x BI/BO LN-GPI-600 (all versions) Setpoint Constant LNCS.x AI/AO LN-GPI-600v2 only Wireless Output LNWO.x AI/AO/BI/BO/MI/MO LN-GPI (all versions) 1 The target reference is the type and number of the mapped field point or network variable, which must correspond to the point or NV index in the host LONWORKS enabled device. When defining the object, replace the x by the index of the object being referenced. 2 For valid engine object types, AI stands for analog input, AO stands for analog output, BI stands for binary input, BO stands for binary output, MI stands for multiple input, and MO stands for multiple output. Mapping Internal Points of LN Series -12 Model Controllers The LN Series -12 model controllers require the Communication (referred to as Comm) Sensors and Wireless Sensors to be manually mapped. The Auto Discovery process does not correctly identify the configuration for these NVs. Each LN Series -12 model controller supports up to 12 dynamic User Network Variable Types (UNVTs) that are configured by the LNS GPI Plug-in. Figure 4 shows configured Comm and Wireless Sensors. The Network Variable names and Format Names are updated to reflect defined configuration. The configuration must be known before mapping the LON points into the NAE. 12

13 Figure 4: Configured Comm and Wireless Sensors Table 3 shows a list of available mapping points of the LN Series -12 Controllers for Comm and Wireless Sensors. Table 3: Mapping of LN Points to Engine Objects for LN Series -12 Models Object Type Target Reference Valid Engine Object Types Controller Type Supported Comm Sensors Wireless Inputs Wireless Outputs LNSI.XXYYZZ 1 LNWI.XXZZ 2 LNWO.XXZZ 3 AI/AO/BI/BO/MI/MO AI/AO/BI/BO/MI/MO AI/AO/BI/BO/MI/MO LN-GPI v12 LN-GPI v12 LN-GPI v12 1 LNSI.XXYYZZ, where XX is 1-12 (leading zero omitted), YY is the Comm Sensor from (leading zero required), and ZZ is the point number from 1-4. For example, LNSI = Uses nvostatus02 (renamed to nvocomsensr05_08) and represents the fifth Comm Sensor for point 3. 2 LNWI.XXZZ, where XX is 1-12 (leading zero omitted) and ZZ is the point number from (leading zero required). For example, LNWI.728 = Uses nvostatus07 (renamed to nvowrin22_28) and represents wireless point 28. A single wireless sensor can have up to 4 points defined. 3 LNWO.XXZZ, where XX is 1-12 (leading zero omitted) and ZZ is the point number from (leading zero required). For example, LNWO.612 = Uses nvostatus06 (renamed to nvowrout08_14) and represents wireless point 12. For future use. Commands Integrated LONWORKS objects support only those commands that can be executed by a standard LONWORKS (LonTalk ) service and network variables. Most Integrated LONWORKS objects support commands by writing a value to the network variable. Refer to the Metasys SMP Help (LIT ) for specific objects and the commands supported in the system. Command and Status Mapping Tool The Command and Status Mapping Tool provides the ability to perform command and status mapping conversions for digital point objects. Custom Scale/Offset LONWORKS network communications are broadcast in metric units. The LONWORKS Integration can automatically convert those units for most cases. In those situations where automatic conversion is insufficient, Custom Scale/Offset provides the ability to scale analog values through the Custom Scale/Offset field on the Hardware tab of analog objects. 13

14 For the normal case, a temperature value polled from an NV on a LONWORKS device using a SNVT_temp_p has a metric value in Deg C. By setting the Hardware tab (field) units to Deg C and the Focus tab (display) units to Deg F, the conversion between the two is performed automatically. This conversion may be insufficient when mapping network variables using SNVT_count_inc because it has no units and often contains encoded values. In this case, consider disabling the automatic unit conversion, depending on the encoding of the value. To disable the automatic unit conversion, set the units for both the field and display units to the same selection. Any Custom Scale/Offset calculation is still performed, but the unit s conversion is ignored. For example, to add a multiplier of 0.1 to a mapped network variable that normally shows 831 to represent 83.1 Deg F, add a Custom Scale/Offset formula of x*0.1 and set both the Field Units and the Units to Deg F. Note: By default, the math performed by the Custom Scale/Offset is applied after the unit conversion. To apply the conversion first, place a B in the field before the formula. In the Focus tab (Figure 5), if a conversion sends a value that is outside the Min/Max range, the point displays??? and Unreliable in the header. The Reliability attribute located under Status indicates if the value is above or below the range. In Figure 5, the Reliability attribute indicates Out of range high, or a value above the maximum. Figure 5: Focus Tab Figure 6 shows the Hardware tab with Custom/Scale Offset formula (X*.1). Using this formula changes the original value from 1418 to The Out of Range and Unreliable errors no longer appear, since the point is now in range. Note: The point status in the header only changes when a COV occurs. The units and reliability change shortly after the units change or the point goes into range. 14

15 Figure 6: Hardware Tab Unreliable may appear if the point is out of range (high or low) or the Hardware and Display units are not valid (gallons per minute [GPM] to Deg F and other invalid unit conversions). Unit Conversions The Display Units and Field Units attributes define the conversion required to display the Present Value correctly. Table 4 and Table 5 show examples of some valid and invalid configurations. For SNVTs that are mapped using the Auto Discovery process, the Display Units and Field Units attributes are automatically set to the correct units. When manually mapping LON Point Objects, take care to correctly set the Display Units and Field Units attributes to prevent an incorrectly displayed Present Value. Table 4: SNVT_temp_p Conversions Field Units Display Units Valid Unit Conversion Custom Scale/ Offset (Hardware Tab) (Focus Tab) Deg C Deg F Yes Automatic Optional Deg C Deg C Yes No Optional Blank Blank Yes No Optional Deg F Gpm No Data Conversion Error (temperature to flow) You can select display units for hardware temperature points on the LN-PRG controllers through the point s Hardware tab. If Deg F is selected and the engine is polling a SNVT_count_inc or a UNVT field, the value represents a raw Deg F value; otherwise, the controller displays a raw Deg C value. Table 5: SNVT_count_inc Conversions Field Units (Hardware Tab) Display Units (Focus Tab) Valid Field Data Unit Conversion Custom Scale/Offset Lps Lps Yes 200=100 LPS Disabled x/2 Lps Gpm Yes 200=100 LPS Yes x/2 15

16 Table 5: SNVT_count_inc Conversions Field Units (Hardware Tab) Display Units (Focus Tab) Valid Field Data Unit Conversion Custom Scale/Offset Deg F Deg F Yes 831=83.1 Deg F Disabled x*0.1 Deg C Deg F Yes 252=25.2 Deg C Enabled B x*0.1 No Units No Units Yes 1000=1000 Disabled None Deg F Gpm No 831=83.1 Deg F Data Conversion Error (temperature to flow) Update Interval (Command Heartbeat) The Update Interval attribute is provided for every LONWORKS output point object (Figure 7). This attribute enables a recurring heartbeat message from the engine to controllers that require periodic contact. If a heartbeat message is not present, some LONWORKS devices revert to local control. Update Interval takes an integer value in seconds. The default is 0 seconds, which disables the heartbeat. The engine can issue one heartbeat per second (maximum). Note: To prevent excessive traffic over the network, we recommend that you use an interval between 2 and 5 minutes (120 to 300 seconds), and enable the interval for no more than two objects per LONWORKS device. Use this capability sparingly. You may configure an update interval of 1 minute, but if you do so, decrease the number of points on the network that use this attribute. For example, if you configure over 60 objects at 1-minute update intervals each, the engine cannot issue updates to all of them within that minute, which causes delayed updates. Once you enable the Update Interval, you must activate it by commanding the point to a different value or state, restarting the engine, or taking the LONWORKS device offline temporarily. You should also make sure the point is set for Auto Restore by assigning a value of True. Auto Restore restores the last command on the field device when the point returns from an offline condition, or when it is first starting up. 16

17 Figure 7: Update Interval Attribute Indication of Hand-Off-Auto Switch The Focus and Summary screens show the current condition of a Hand-Off-Auto (HOA) switch for all hardware outputs (analog and digital) supported by the FSC and LN-PRG410/510 controller. The condition is indicated on the Focus and Summary screens for these point types on these device types (Figure 8). If you place the switch in the Hand or Off position, the condition shown for its point is HW Override. The actual value for an analog output (AO) in the Hand position is unknown to both the FSC and the engine. A binary output (BO) placed in the Hand position correctly reports the value to the FSC and the engine. For LN-PRG410/510 controllers using basic programming, the engine automatically reads the actual output for any point in Hand or Off mode, regardless of whether the point is binary or analog, as defined by the output potentiometer when you enable HOA. The LN-PRG410/510/610 controllers that use the graphical programming interface (GPI) do not support the HOA indication status feedback. 17

18 Figure 8: HOA Switch Indication Point Object Polling Point object polling provides on-demand point status updates. Point objects can be polled on either a permanent or temporary basis, depending on the configuration of the system. Permanent Status Items Permanent point object polling occurs for point objects having an alarm extension, a change of value/change of state (COV/COS) extension, or a trend COV extension. (Sample trends are not considered permanent status objects.) Temporary Status Items Temporary point object polling polls the point as long as Present Value reads continue. This scenario prevents unnecessary polling of points. Whenever Present Value requests for that point are received, the Temporary Status Item Expiration Time period begins. When the Temporary Status Item Expiration Time period expires, all polling for that point stops. Temporary point object polling is typically used for interval trends. Temporary Status Item Expiration Time The Temporary Status Item Expiration Time is the global, user-defined time period for temporary point object polling, applied per individual object. Each time a point object receives a Read Attribute of the Present Value, the Temporary Status Item Expiration Time begins. Polling for the point stops when the Temporary Status Item Expiration Time expires. 18

19 Notes: The Temporary Status Item Expiration Time is configured in the Detail view Hardware tab of the LONWORKS Integration Object, and defaults to 60 seconds. Changing the Temporary Status Item Expiration Time to a value greater than the trend interval results in nonstop data trending. Priority Levels All point objects are assigned a priority level. Priorities are assigned on a point-by-point basis, using a three-level priority scheme. The most critical points are assigned Priority 1, less critical points are assigned Priority 2, and non-critical points are assigned Priority 3. Priority 3 is the default value for all objects. Note: The three-level priority scheme is not maintained if the number of point objects assigned Priority 1 is greater than the number of point objects assigned Priority 2 or Priority 3. Every time a polling cycle takes place, a preset number of objects have their status updated, based on their priority setting. Table 6 shows the number of objects updated per polling cycle for each priority level. Table 6: Priority Object Status Updates Priority Level Critical Designation Total Objects Updated per Polling Cycle Priority 1 Priority 2 Priority 3 Most Critical Critical Least Critical Priority Polling Example The priority polling process follows a specific pattern where each priority value is selected individually in a sequential manner. The following example moves through two complete cycles, using the priority values in Table 7, Table 8, and Table 9. Each polling cycle consists of a pattern of six polls that result in the ratios shown in Table 6. The complete polling sequence for the first two cycles is as follows: 1. First Priority 1 value (A). 2. Priority 2 value (B). 3. Priority 1 value (C). 4. Priority 2 value (D) 5. Priority 1 value (E). 6. Priority 3 value (F). (Second Cycle) 7. Priority 1 value (G). 8. Priority 2 value (H). 9. Priority 1 value (I). 10. Priority 2 value (J). 11. Priority 1 value (K). 12. Priority 3 value (L). 19

20 The two priority polling cycles described in this document assume that all three priority levels exist. If no objects exist for a particular priority level, then the priority level is skipped, and the cycle continues until the sequence starts again. For a single priority polling cycle, if only one object exists for Priority 1, then that object would be polled three times per priority polling cycle. The same execution occurs for Priority 2 and Priority 3 polled objects, with the exception of the number of times the objects are polled per priority polling cycle. See Table 7, Table 8, and Table 9. Note: In these tables, numeric value indicates the priority of the objects polled. The sequence of polling is from left to right. Table 7: Priority Polling Example, Priority 1, Priority 2, and Priority 3 Items Priority Polling Sequence using Priority 1, Priority 2, and Priority 3 Items (2 cycles) 1 A 2 B 1 C 2 D 1 E 3 F 1 G 2 H 1 I 2 J 1 K 3 L Table 8: Priority Polling Example, Priority 1 and Priority 2 Items Priority Polling Sequence using Priority 1 and Priority 2 Items (2 cycles) A B C D E G H I J K Table 9: Priority Polling Example, Priority 2 and Priority 3 Items Priority Polling Sequence using Priority 2 and Priority 3 Items (2 cycles) B D F H J L Note: Adding any Priority 1 or 2 polling to points increases your overall scan time. LONWORKS Device Extensions Alarming Alarm extensions may be generated for any integrated LONWORKS object. All alarm processing is handled by the engine from point data received from the LONWORKS enabled devices on the LONWORKS trunk. Node State Events The Alarm Event State attribute (Figure 9) defines how Node State events are handled. Node State events are separate from device ONLINE or OFFLINE events. The Node State is in a Configured Online, Configured Soft Offline, or Configured Bypass state. 20

21 Figure 9: Alarm Event State When the Alarm Event State attribute is set to TRUE, any off-normal state (Soft Offline or Bypass) causes a Node State is not normal event (Figure 10), and is logged. In addition, the status of the LON device transitions to an Unreliable state. The Diagnostics Tab of the LON device logs the unreliable condition in the Node State attribute (Figure 11). When the LON device returns to a normal Node State, the event is logged in addition to setting the status of the LON device to Normal. Figure 10: Alarm Event Logged in Event Viewer 21

22 Figure 11: Node State in Diagnostic Tab When the Alarm Event State attribute is set to FALSE, all off-normal conditions are suppressed including events. The status of the LON device remains Normal, but the Diagnostics Tab of the device logs the unreliable condition in the Node State attribute. Trending LONWORKS Point Data The Trend extension is used to trend LONWORKS point data. It monitors and records the changes in behavior of an individual attribute and displays the results in both graphical and tabular formats. When trending LONWORKS network device objects using samples taken at fixed predetermined intervals, the initial trend period results may differ from the expected trend start time. LONWORKS network status reporting for trend objects reports trend data correctly but always remains one interval cycle behind the actual field value. For example, in a 60-minute cycle where the value always increments by 2, if the current Present Value of the object is 0, then 0 is logged in the trend even through the field has a value of 72. The LONWORKS object is then polled, and the Present Value updates to 72. After 60 minutes, the field value changes to 74, but the trend sample logs the current Present Value, which is 72. The only exception to this pattern is if the LONWORKS object is polled by some other means. See Trend Process in this section for more information. Trend Buffer The trend buffer resides on the engine and provides buffer space for each individual trend. The number of trend samples stored in each individual trend buffer is user configurable. When an individual trend buffer is full, you can configure the trending process to either stop trending or overwrite the older data with the newer data. You can configure an alarm to report whenever the buffer is full and you can also configure the trend buffer to transfer samples to a configured ADS or ODS. Trend Process The following example shows a step-by-step trend process. Figure 12 shows this same process graphically. The following trending example assumes: field value is a linear, increasing value trend interval is 60 minutes (3,600 seconds) 22

23 Temporary Status Item Expiration Time is 60 seconds initial field value is 71.8 Present Value is not updated by any other means 1. Trending begins when the engine receives a trend request for the trend point s Point Value (PV). Trending reads the initial PV at 9:00 A.M., which is Polling begins and the Temporary Status Item Expiration Timer starts. 3. Polling acquires the point s current value and stores it as the update value of At this point, the trend has a value of 0 with a timestamp of 9:00 A.M., even though the actual field value is seconds later at 9:01 A.M., the Temporary Status Item Expiration Timer expires and polling stops (PV is now 72.0) minutes later at 10:00 A.M., the hourly trend request restarts the trending process and reads the last stored PV (72.0). 6. Polling begins and the Temporary Expiration Timer starts. 7. Polling acquires the point s current value and stores it as the update value of At this point, the trend has a value of 72.0 with a timestamp of 10:00 A.M., even though the actual field value is seconds later at 10:01 A.M., the Temporary Status Item Expiration Time expires and polling stops (PV is now 74.3) minutes later at 11:00 A.M., the hourly trend request restarts the trending process and reads the last stored PV (74.3). 10. Polling begins and the Temporary Status Item Expiration Timer starts. 11. Polling acquires the point s current value and stores it as the update value of At this point, the trend has a value of 74.3 with a timestamp of 11:00 A.M., even though the actual field value is seconds later at 11:01 A.M., the Temporary Status Item Expiration Timer expires and polling stops (PV is now 76.7). The process continues for the duration the trend settings dictate. Trend Process Graph Figure 12 is a graphic representation of the trend process. 23

24 Figure 12: Trending Process Detailed Procedures Adding a LONWORKS Integration Object The following process is generally applicable to online configuration in the SMP or offline configuration in the SCT. Note: There are no Engineering or Diagnostics views when using the SCT, as these are online features. To use Auto Discovery, you must be online with an engine and its LONWORKS network of devices. To add a LONWORKS Integration object: 1. On the Insert menu, select Integration. The Insert Integration Wizard Select Object Type screen appears (Figure 13). 24

25 Figure 13: Insert Integration Wizard (Select Object Type Screen) 2. Select LON Trunk and click Next. The Insert Integration Wizard Destination screen appears (Figure 14). Figure 14: Insert Integration Wizard (Destination Screen) 3. Select the engine to which you want the LONWORKS Integration object added and click Next. The Insert Integration Wizard Identifier screen appears (Figure 15). 25

26 Figure 15: Insert Integration Wizard (Identifier Screen) 4. Enter a unique name for the LONWORKS network of devices that you are integrating and click Next. The Insert Integration Wizard Configure screen appears (Figure 16). Note: It is best to keep this name as short as possible. Figure 16: Insert Integration Wizard (Configure Screen) Notes: You can view the Driver Name value by clicking the Hardware tab. The Driver Name value differs for the NAE and LCS. For all NAEs, the Driver Name value displays lpcdrv (Figure 17). For the LCS85, the Driver Name value displays 852drv. In SCT, the LONWORKS Integration has the driver name lpcdrv when LONWORKS Integration is added to the LCS85. When the database is downloaded to the LCS85, the driver name is automatically changed. Once the database is uploaded to SCT, the name changes to 852drv. 26

27 Figure 17: Insert Integration Wizard (Configure Screen, Hardware Tab) 5. Click Next to accept the defaults. The Insert Integration Wizard Summary screen appears (Figure 18). Note: In most cases, you can accept the default Configuration parameters. Figure 18: Insert Integration Wizard (Summary Screen) Note: If you need to change anything, click Back. 6. Click Finish to create the LONWORKS Integration object and display the Extension Wizard (Figure 19). 27

28 Figure 19: Extension Wizard Notes: At this time, you can add resource files, trend, totalization, or alarm extensions to the new LONWORKS Integration object. The NV Configuration Data file shown in Figure 19 is created automatically, but you must update it with the correct configuration data using a network configuration tool, such as LN Builder. See Defining an Engine on the LONWORKS Trunk. 7. Add all required resource files. See the Inserting Resource Files section for details. 8. Add any desired alarm extensions and click Done when finished. The Insert Integration Wizard closes. Inserting Resource Files Note: If you insert a resource file under a device that has already been mapped, you must reboot the engine. A reboot is not required if the resource file is added before the device is mapped. See Resource Files for more information about resource files. To insert resource files: 1. Click the LON Trunk in the Navigation Tree All Items. 2. On the Action menu, select Show Extensions. The Extension Wizard main screen appears (Figure 20). Note: The NV Configuration Data file shown in Figure 20 was created automatically when you completed the steps in Adding a LONWORKS Integration Object. 28

29 Figure 20: Extension Wizard (Main Screen) 3. Click the New button on the right of the Resource area. The Insert Resource File Wizard Select File screen appears (Figure 21). Figure 21: Insert Resource File Wizard (Select File) 4. Click Browse. The Open screen appears (Figure 22). 29

30 Figure 22: Insert Resource File Wizard (Open) 5. Browse to the folder with the resource files, and click a required resource file in the list for its name to appear in the File name field of the Open screen. Note: The STANDARD.TYP and STANDARD.FPT resource files are required and must be added to the LONWORKS Integration object. 6. Click Open, and the Select File screen reappears with the selected name displayed. 7. Click Next, and the Configure screen appears (Figure 23). Figure 23: Insert Resource File Wizard (Configure) Note: Use the original file name for future traceability. However, you can enter a different name if desired. 8. Click Next; the Summary screen appears (Figure 24). 30

31 Figure 24: Insert Resource File Wizard (Summary) 9. Review the information in the Summary screen. If any changes are needed, click Back. If no changes are needed, click Finish. The Extension Wizard screen appears (Figure 25) with the newly added resource file. Repeat this process until all required resource files have been added. Note: Once you have added all required resource files, use the engine Archive command to save the changes. Figure 25: Extension Wizard (Add Extensions) 10. Click Done to exit the Extension Wizard. 31

32 11. Use the SCT Upload command to archive the engine database to the SCT. This command saves a copy of the database that includes all inserted resource files. Defining an Engine on the LONWORKS Trunk You must define the engine on the LONWORKS trunk (network) to complete the integration process. This defining process creates critical internal bindings and produces a network image of the engine. Notes: The LCS85 must be defined in the Configuration Server before it can be commissioned in LNS. See Appendix: Using a Flat LONWORKS System with LCS and Appendix: LCS85 Gesytec 852 Configuration Settings for details. You must use LN Builder, LonMaker, or LNS Object browser to add an NAE or LCS85 to the system. To define the engine on the LONWORKS network: 1. Connect LN Builder or a third-party LONWORKS network tool to the LONWORKS network. 2. Using LN Builder, add the Engine Device Template to the LNS database by entering the key sequence Ctrl + K and browsing to the XIF file on the hard disk. 3. Using LN Builder, add the engine to either an existing Subsystem or create a new Subsystem for the engine. The engine can be commissioned during this process provided the Neuron ID is known and the engine is online. Note: The Neuron ID of the LCS can be found on a label on top of the server. The Neuron ID of the NAE can be found on a label on the front of the NAE. 4. Continue advancing through each section making sure to select the correct Channel, the correct Device Template, and manually entering the correct Neuron ID. 5. Click Finish to complete the process. Note: Refer to the third-party LONWORKS network tool documentation for the equivalent commands in Steps 2, 3, and Archive the changes in the SMP UI. 7. Upload the engine database to the SCT archive database. Using Auto Discovery LON Point Auto Discovery only allows a defined number of points to be discovered for a single instance. If the total number of discovered points exceeds the limit, then the returned discovery indicates Page 1 of X, where X is the total number of pages (Figure 26 and Figure 27). A restart increments the page and displays the next set of discovered points. Each completion of the point mapping process also increments the page. After the last page, the point mapping process begins again at Page 1. 32

33 Figure 26: Wizard Auto Detect Utility Figure 27: Wizard Auto Detect Utility Page Increments Mapping LONWORKS Devices Using Auto Discovery After you add the LONWORKS Integration object and the required resource files, you need to map the devices on the LONWORKS network to the engine. Auto Discovery is an alternative to the manual process. To map the devices using Auto Discovery: 1. On the Insert menu, select Field Device. The Insert Field Device Wizard Destination screen appears (Figure 28). 33

34 Figure 28: Insert Field Device Wizard (Destination) 2. Select the LONWORKS Integration object within the engine and click Next. The Insert Field Device Wizard Select Definition Mode screen appears (Figure 29). Note: If you do not see a LONWORKS Integration object, follow the procedures in Adding a LONWORKS Integration Object. Figure 29: Insert Field Device Wizard (Select Definition Mode) 3. Select Assisted Device Definition and click Invoke Auto Discovery. The Wizard Auto Detect Utility starts. When Auto Discovery is complete, a list of discovered devices appears (Figure 30). Note: The engine must have been commissioned on the LONWORKS network. It must also be online with the LONWORKS network of devices to use Auto Discovery. At this point, you may also select Manual Device Definition and proceed with manual item creation. 34

35 Figure 30: Insert Field Device Wizard (Auto Detect Utility) Note: If the desired device does not appear, verify that the device's resource files have been added to the integration. 4. Select a device from the list. This starts the Insert Field Device Wizard Identifier screen (Figure 31). Figure 31: Insert Field Device Wizard (Identifier) 5. Enter an identifier for the device that is unique on this LONWORKS trunk. Note: Always replace the existing default identifier found in the identifier box because this is the generic device-type name and may not be unique on the trunk. Identifier names are limited to 32 characters. The identifier you enter is displayed in the device s Advanced Focus view under the Engineering Values - Item Reference listing. The DSN number in the identifier is used to identify which subnet a device is on when routers are present. The DSN number is removable. 35

36 6. Click Next and the Insert Field Device Wizard Configure screen appears (Figure 32). Figure 32: Insert Field Device Wizard (Configure) 7. Enter a name unique to the site into the Object Name box, enter a description into the Object Description box (optional), and click Next. The Insert Field Device Wizard Summary screen appears (Figure 33). Note: The Object Name and Description you enter appears in the device s Focus view Object section. Figure 33: Insert Field Device Wizard (Summary) 8. Review the configuration information. Click Back to make any changes. Click Finish and the Extension Wizard appears (Figure 25). 36

37 9. Add any extensions and click Done. This saves the field device s configuration, and the Field Device Extension - Field Points screen appears. See Mapping Field Points in LONWORKS Devices Using Auto Discovery. Mapping Field Points in LONWORKS Devices Using Auto Discovery Once one or more integrated LONWORKS device objects have been configured, you can add LONWORKS Field Points, which map to network variables in the LONWORKS device. To map field points in LONWORKS devices using Auto Discovery: Note: The engine must be online with the LONWORKS network of devices in order to use Auto Discovery. If you are mapping points offline, see Manually Mapping Field Points in LONWORKS Enabled Devices. 1. On the Insert Menu, select Field Point. The Insert Point Wizard Destination screen appears (Figure 34). Note: The Insert Point Wizard starts automatically after inserting a Field Device. Since it selects the newly added device as the destination, the wizard opens to the Select Definition Mode screen, bypassing the Destination screen. Figure 34: Insert Point Wizard (Destination) 2. Select the LONWORKS device from which you want to map the points and click Next. The Insert Point Wizard Select Definition Mode screen appears (Figure 35). Note: If you do not see a device to select, click the plus sign next to the LONWORKS Integration object to open the list of mapped LONWORKS devices. 37

38 Figure 35: Insert Point Wizard (Select Definition Mode) 3. Select Assisted Point Definition and click Invoke Auto Discovery. The Wizard Auto Detect Utility starts (Figure 36). Figure 36: Insert Point Wizard (Auto Detect Utility) Notes: When Auto Discovery is complete, a list of discovered LONWORKS network variables appears. The fields are automatically filled with the auto-discovered data from the LONWORKS device and its resource files. Each engine has a limited number of objects it can discover at one time. If you have more than the limit, you need to perform subsequent discoveries until all objects are accounted for. The SMP UI keeps track of multiple Auto Discoveries by incrementing the pages displayed. 4. Close the window by clicking the x in the upper-right corner of the screen. 5. Click Next. The Point Mapping Utility screen appears (Figure 37). Use this screen to select which point objects/fields you want to map as points from your LONWORKS device. 38

39 Figure 37: Insert Point Wizard (Point Mapping Utility) 6. Select Map All to map all discovered LONWORKS network variables as integrated LONWORKS point objects (1,000 child object limit). You may also select network variables individually for mapping by clicking them. A green check mark is placed next to the selected network variable, and the right side of the screen displays the newly selected network variable ready for mapping (Figure 38). At this point, you have the option to change the point object name and object type on the right side of the screen. Note: Previously mapped network variables are noted by a blue check mark. Figure 38: Insert Point Wizard (Point Mapping Utility Map All) 39

40 7. Select all the network variables you want to map, and then click Next. The Insert Point Wizard Summary screen appears (Figure 39). Figure 39: Insert Point Wizard (Summary) 8. Review the Summary screen and click Finish. Manually Mapping a Series of LONWORKS Enabled Devices Note: The following steps assume that LN Builder and the SCT are on the same computer. Using the same computer allows you to toggle between LN Builder and the SCT to expedite the mapping process. Manually mapping a series of LONWORKS devices is typically used for many field devices of the exact same device type (for example, VAV Modular Assembly [VMA] or Heat Pump) that all require the exact same point and NV configuration. These devices often do not require all their points to be mapped, with the only difference being their name, Neuron ID, and DSN number. The SCT Copy/Paste command is the key to this timesaving process. Note: The Neuron ID is only stored as a reference and can be removed. The DSN Number is used to communicate to the LONWORKS device. If LN Builder and the SCT are on different computers, create a list that includes the device name, Neuron ID, and DSN number of each device in the series of devices on the LN Builder Physical Tree. To map a series of LONWORKS field devices manually: 1. Use LN Builder to add and configure all LONWORKS field devices in the series. 2. See the manual procedures included in Mapping LONWORKS Devices Using Auto Discovery and the section Manually Mapping Field Points in LONWORKS Enabled Devices to manually add the devices and points. You must upload the changes to SCT before continuing. Note: The Neuron ID cannot be duplicated from within a single LONWORKS Integration. The Neuron ID must contain all zeros before a paste is allowed. Use Steps 8 and 9 in this section to modify the Neuron ID of the device that is being copied. Only the DSN number needs to be modified to match the pasted device. 3. Select the new device and on the Edit menu, click Copy (Figure 40). 40

41 Figure 40: Copy Selected Device 4. On the Edit menu, click Paste to paste a copy of the first device, as the second device, into the Integration Tree. A message prompts you to enter a new name for the second device in the series (Figure 41). Duplicate names are not permitted. Figure 41: Paste Item Name in Use Message 5. Enter a new name for the second device. Click Paste in the Paste Item Wizard window to add the second device to the Integration Tree (Figure 42). Note: Name devices consistently to avoid confusion when you enter the corresponding DSN number for each device in the series. 41

42 Figure 42: Second Device Added to the Integration Tree 6. Repeat the paste and renaming process for every device in the series. Note: Once all devices in the series have been added to the Integration Tree, you must enter the correct DSN number for each device in the series, with the exception of the first device, which is already correct. 7. Use the SCT to select the second device in the series to begin the editing process. 8. On the View menu, click Selected Item to open the Focus window. 9. Select the Hardware tab to display the DSN number field (Figure 43), then click Edit. Figure 43: Edit Hardware Screen (Neuron ID and DSN Number) 42

43 Note: The DSN numbers, initially displayed for the second device and for all remaining devices in the series on the Integration Tree, are the same numbers as the first device in the series on the Integration Tree. The second device and all remaining devices in the series on the Integration Tree must be edited to match the DSN number of the corresponding device as shown on LN Builder from the list view. 10. Toggle to LN Builder and select the second device of the series. Right-click and select Properties, then select the Identifier tab. You can copy and paste the Subnet/Node ID into the corresponding attributes of the engine (Figure 44 and Figure 45). Notes: The Domain can be identified in LN Builder by highlighting the database, right-clicking, and selecting Properties. When mapping a series of LONWORKS field devices manually using LN-Builder, make sure you record the hexadecimal format (Base 16) and not the decimal format (Base1 h10) when entering the data into the engine. Both are available. Devices imported into the Integration Tree using an.imp file have the decimal DSN number automatically converted to hexadecimal. Manual device discovery requires you to enter the DSN number in hexadecimal. Figure 44: LN Builder Device Properties Screen 43

44 Figure 45: Device Summary View of Hardware Tab 11. Toggle to the SCT. 12. Use the SCT to select the DSN box and replace the existing Subnet and Node number with the new hexadecimal number. Note: The Domain does not need to be changed if the device is being copied from within the same LONWORKS Integration. Figure 46: Replacing the Subnet Node Number 13. Click Save to save all changes. 14. Repeat Step 7 through Step 13 until all devices in the series have the correct DSN number. 15. Use the SCT Database Create Backup command to save all changes. 44

45 16. Use the SCT Load Archive command to download the changes to the engine. Manually Mapping Field Points in LONWORKS Enabled Devices Manually mapping LONWORKS Field Points or Network Variables (NVs) is considered an advanced procedure and requires an experienced operator. To map LONWORKS Field Points manually: 1. On the Insert Menu, select Field Point. The Insert Point Wizard Destination screen appears (Figure 47). Note: The Insert Field Points Wizard starts automatically after inserting a Field Device. Since it selects the newly added device as the destination, the wizard opens to the Select Definition Mode screen, bypassing the Destination screen. Manual point insertion that does not follow automatic device insertion displays the Insert Point Wizard Destination screen first. Figure 47: Manual Insert Point Wizard (Destination Screen) 2. Select the LONWORKS device from which you want to map the points and click Next. The Insert Point Wizard Select Definition Mode screen appears (Figure 48). Figure 48: Manual Insert Point Wizard (Select Definition) 45

46 3. Click Manual; the screen changes to the manual mode with a list of point object types that you can add (Figure 49). Note: Manual Point Definition can be distinguished from the Assisted Point Definition by the list of steps on the left side of the screen. In Manual Point Definition, a Data Source step is added and the Identify and Configure steps are separate. LONWORKS devices are added during the Mapping LONWORKS Devices Using Auto Discovery procedure. If you do not see a selectable device, click the plus sign next to the LONWORKS Integration object to open the list of mapped LONWORKS devices. Figure 49: Manual Insert Point Wizard (Select Definition Mode) 4. Select the type of point you wish to create and click Next. The remaining steps of the Insert Point Wizard manual mode are listed in Table 10. Table 10: Insert Point Wizard - Manual Mode Screens Screen Purpose Data Source Identifier Configure Summary 5. When finished with the Wizard, click Finish. Enter the index of the field point or NV you are mapping. This index must be Point.x or NV.x.x, where x = the Target Reference Number. See Table 2 in the Mapping Internal Points of LN Series Controllers section for additional Target Reference structures. The Target Reference Number must correspond to the point or NV index in the host LONWORKS enabled device. You can find the Target Reference Number in the LN Builder Nv Attributes tab of the properties box for that NV. For structured SNVTs, use LN Browser in addition to the Attributes tab to identify the SNVT part that is needed (such as NV.12.3). For more information on Target References, see Target Reference. Enter a unique name (within the device) for the field point or NV you are mapping. Enter the field point or NV. The Hardware tab of the Configuration Screen displays the Target Reference Number. View a summary of the information that you have entered. If anything looks wrong, press the Back key and make corrections. 46

47 Using Relearn in the Engineering View The Engineering View allows a detailed examination of the integration items. Although mapped devices and points are shown, the Engineering View also provides details for objects that are not mapped into the Integration. Note: Only viewing and commanding are applicable in the Engineering View; there is no option for mapping. Relearn uses Auto Discovery and requires that the engine be online with the LONWORKS network of devices being discovered. To add Integrated LONWORKS objects to the Integration Tree using Relearn: 1. Select the LONWORKS Integration object in the Navigation tree. 2. Click the Engineering tab, and then click the Relearn button that appears underneath the Summary tab (Figure 50). Figure 50: Engineering View with Relearn Button 3. The discovery begins automatically and finds all new LONWORKS devices on the network. The Relearn screen appears (Figure 51). The Restart button repeats the discovery process. Note: Discovery by Relearn removes from the Integration Tree devices that are unmapped and not communicating with the engine. After discovery, the newly found devices appear in the Integration Tree in the Engineering view. 47

48 Figure 51: Engineering View (Relearn Screen) 4. When discovery is complete, close the Relearn screen. Using the Engineering View to View Device and Point Data When online with a LONWORKS device, you can use the Engineering view of the LONWORKS Integration object to view the data of LONWORKS devices and points that the engine has discovered. The Mapped Devices folder contains a list of all mapped devices. The devices and points do not have to be mapped to the Navigation Tree to be acted on. Note: LN Series internal points are not visible in Engineering View. To use the Engineering view to view devices and points: 1. Right-click the LONWORKS Integration object in the Navigation tree and select View. The LONWORKS Integration object appears (Figure 52). 48

49 Figure 52: LONWORKS Integration Object (LON Trunk) 2. Click the Engineering tab and navigate to either a field device or a field point in the Integration Tree. 3. Double-click the selected field device or field point; the Details screen appears (Figure 53). 4. Click the x in the upper-right box to close the menu. Using the Engineering View to Command Network Variable Inputs and Edit NexSys Point Data When online with a LONWORKS device, you can use the Engineering view of the LONWORKS Integration object to command network variable input (NVI) values for any LONWORKS device and to edit NexSys point data. The Mapped Devices folder contains a list of all mapped devices. The NVIs and NexSys points do not have to be mapped to the Navigation Tree to be acted on. To use the Engineering view to view and edit NVIs and NexSys points: 1. Right-click the LONWORKS Integration object in the Navigation tree and select View. The LONWORKS Integration object appears (Figure 53). 2. Click the Engineering tab and navigate to either a field point or NVI in the Integration Tree. 3. Double-click the selected field point or NVI. The Details screen for the selected field point object or NVI appears (Figure 53). 49

50 Figure 53: Engineering View (Details Screen) 4. Click Edit. The fields that are editable from this screen are shown in a box with a line border. 5. Make the desired changes, click Save, and close the screen. Viewing Routers The Device Auto Discovery is used to recognize the routers as being on the LONWORKS routers are discovered as part of the Device Auto Discovery process. The routers are visible in the Engineering View's Integration tree (only if the Device Auto Discovery process has been run), but are not visible in the Navigation tree, since the routers cannot be mapped. Routers are not visible on the Navigation tree and are only visible on the Integration tree in the Engineering view after using the Relearn or Auto Discovery command to expose them. Devices added below a router on the LN Builder Physical tree must be physically connected to the LONWORKS network somewhere on the far side of the router. Device order is not important. Subnet addresses are hexadecimal, are automatically assigned, and are not always sequential by subnet level. 50

51 Figure 54: Router Subnet Levels To view routers in the Integration Tree: 1. Add and commission the routers using LN Builder. 2. On the engine, drag the LONWORKS Integration object to the Display frame. 3. Click the Engineering tab to display the current devices on the Integration Tree (Figure 55). 51

52 Figure 55: Integration Tree before Discovery 4. Click the LON Trunk, then click Relearn to start the Auto Discovery process. 5. Click Restart (Figure 56) to complete the discovery. Figure 56: Discovery Screen Note: Routers are not shown in the Relearn screen until after discovery is finished. 6. When the discovery is finished, click Close; the newly discovered router now appears as a folder in the Integration Tree (Figure 57). 52

53 Figure 57: Integration Tree After Discovery Note: Even though the router, with its mapped devices, appears in the Integration Tree, the Mapped Devices folder only displays the mapped devices under the router. Routers cannot be mapped. Viewing Detailed Router Information 1. Click the Engineering tab of the LONWORKS Integration to display the Integration Tree. 2. Double-click the router to display the summary information (Figure 58). If the router is not visible, follow the steps Viewing Routers. 53

54 Figure 58: Router Summary Screen Trending LONWORKS Device Data 1. Right-click the point you want to trend. Select Show Extensions to open the Extension Wizard (Figure 59). Figure 59: Extension Wizard 2. Click New to open the Insert Trend Wizard Select Attribute screen (Figure 60). Present Value is the default attribute. Attributes vary, depending on the point or device selected. To select a different attribute, click Other and select the attribute; otherwise, click Next to display the Insert Trend Wizard Configure screen. 54

55 Figure 60: Insert Trend Wizard (Select Attribute Screen) 3. Make any changes to the configuration settings (Figure 61), and click Next to display the Summary screen (Figure 62). Figure 61: Insert Trend Wizard (Configure Screen) 4. Click Finish to complete the Trend configuration, display the newly created trend in the Trend Extension Wizard, and begin trending the point. 55

56 Figure 62: Insert Trend Wizard (Summary Screen) Figure 63 shows a trend chart example, and Figure 64 shows an example trend table. 56

57 Figure 63: Trend Chart Screen 57

58 Figure 64: Trend Table Screen 58

59 Troubleshooting Use the information in Table 11 to assist in diagnosing and solving possible LONWORKS network system integration problems. Table 11: LONWORKS Network System Integration Troubleshooting Guide Symptom Cause Solutions Auto Discovery fails to find all devices after clicking the Relearn button. The Relearn button calls the last saved relearn data from a queue. Devices added after the last relearn request are not in that data. Check for device specific resource files and then click the Restart button to rediscover the devices. This causes a poll of current devices and creates a new list. Auto Discovery fails to find all devices, and clicking the Restart button does not display all devices. Communication failure LONWORKS network wires at missing devices not connected properly. Connect LN Builder, the COM.PRO Tool, or a third-party LONWORKS network configuration tool to the LONWORKS network and verify that it is possible to communicate with the devices on the network including the engine. If communication is good, verify that the engine database has been generated correctly and that the LONWORKS enabled device data corresponds to the devices installed. If the engine does not respond, verify that the engine has been correctly installed in the LONWORKS network database and that the network configuration image has been sent to the engine from LN Builder. If the engine cannot be installed, replace the engine. Check the entire LONWORKS network. Refer to the LONMARK Guidelines Physical Layer for details ( Critical Resource Missing is shown for the status of the device. Data Conversion Error is indicated as a point's reliability status. A required XIF resource file is missing from the integration of the controller to the engine. A required resource file is missing from the integration of the controller to the engine. Insert the required XIF resource file under the LONWORKS Trunk, and then reboot the engine. See Inserting Resource Files for details. Insert the required resource files under the LONWORKS Trunk. See Inserting Resource Files for details. If the resource file is present, try rebooting the engine to see if that resolves your issue. Routers are not displayed on the Navigation Tree after Auto Discovery. Routers are only visible in the Engineering view Integration Tree. This issue may also occur if the Field Units and Units are mismatched. From the Engineering view of the LONWORKS trunk, select the LONWORKS Integration object and click Relearn. Routers are shown in the Integration Tree. 59

60 Table 11: LONWORKS Network System Integration Troubleshooting Guide Symptom Cause Solutions Adding a device under a Router in LN Builder results in the following Error Message: Node/router on the wrong channel. The wrong channel was selected in LN Builder during the insert device process, the device is physically wired incorrectly, or the network interface defined in the LNS database does not match the physical connection to the LON Network. Change the channel assignment for the device in LN Builder, rewire the device in the field, or change the channel assignment for the network interface as defined in LN Builder to match the physical connection to the LON Network. After defining a LON Integration, adding a resource file extension, and creating an object, the resource file does not download to the the NxE. The object created cannot be found or used during Auto Discovery. Windows 7 and server-class Windows operating systems may require changing the User Access Control (UAC) settings to allow resource files (LON and Vendor Integrations) to be added to NxE or LCS engines. The Metasys SMP does not inform the user when a resource files fails to download. Disable UAC settings. 60

61 Appendix: Using a Flat LONWORKS System with LCS Basic System Overview A flat LONWORKS System differs from a typical LONWORKS network because of its open architecture. This appendix describes the components, setup, and the role of the 852 Configuration Server in a flat LONWORKS system organization. Physical Components TCP/IP Network The TCP/IP network provides the transport medium for LONWORKS packets according to the CEA-852 standard. This standard provides management and encapsulation for the LONWORKS packets on the TCP/IP network. A site may have a single TCP/IP network, but multiple CEA-852 channels may be configured within that TCP/IP network. LCS85 Control Server The LCS85 Control Server is a server-based machine that supervises many LONWORKS field controllers through a CEA-852 Configuration Server. LNS Computer The LNS computer runs a LONWORKS network management tool such as LN Builder or LonMaker. LONWORKS Network Services (LNS) is the underlying software that performs the actual LONWORKS network management tasks, such as assigning LONWORKS addresses, binding, running data queries, and so on. These tools provide a user-friendly interface that directs commands down to the LNS computer to perform actual network operations. The LNS computer can either be a laptop, which is only connected to the network temporarily (when changes to the system are made), or it can be a dedicated computer always attached to the network. LONWORKS IP Routers LONWORKS IP routers allow EIA-709 (LONWORKS) packets to travel to and from the TCP/IP network. They are also true LONWORKS routers because they must be configured by a LONWORKS network management tool to function on the LONWORKS network. Note: If you use an IP852 router that is not manufactured by Echelon Corporation, Loytec, or Adept Systems, it might not be compatible with the LCS85. Refer to the LONWORKS Control Server (LCS) 85 Product Bulletin (LIT ) for a complete list of supported CEA-852 routers. Loytec L-IP Router The L-IP router is a combination device. It is a LONWORKS IP router that can also serve as the CEA-852 Configuration Server. Echelon i.lon 600 Router The Echelon Ii.LON 600 is a LONWORKS IP router for purposes of an LCS85-based system. The previously released I.LON 1000 is a LONWORKS IP router, but it uses an Echelon proprietary protocol that is neither compatible with nor upgradeable to the CEA-852 standard. Note: The Echelon i.lon 100e3 and i.lon SmartServer are fully compatible. : Appendix: Using a Flat LonWorks System with LCS 61

62 Logical Components CEA-852 Standard The CEA-852 standard specifies a method for transporting LONWORKS (EIA-709) packets over a TCP/IP network and managing the devices that exchange LONWORKS packets. The CEA-852 packets travel across the network as User Datagram Protocol (UDP) or TCP packets using unicast or multicast addressing. Note: Not all devices support multicast addressing. CEA-852 Channels CEA-852 channels form logical groups of nodes that interact on an IP network. The CEA-852 channels are managed by a Configuration Server. Each LCS85 can only connect to a single CEA-852 channel. CEA-852 Configuration Server The Configuration Server is a critical part of any CEA-852 channel. It tracks all of the devices belonging to a channel and ensures that each device communicates with all other devices on that channel. If all devices are in communication, they can route traffic to each other. In an LCS85 flat LONWORKS system, you can use either the Loytec L-IP router or the Echelon Configuration Server. Unlike the Echelon Configuration Server, each L-IP router can only manage a single CEA-852 channel. Notes: Echelon and Adept Systems routers are compatible with both the Loytec Configuration Server and the Echelon Configuration Server. For full functionality, settings must be adjusted in the Gesytec Easylon IP Interface Configuration Utility, depending on the Configuration Server you are using. See Appendix: LCS85 Gesytec 852 Configuration Settings for details. Basic System Setup Figure 65 shows a basic system setup using LONWORKS IP routers. The system contains a single LCS85, a single LONWORKS Network Services (LNS) based network management tool, and several LONWORKS IP routers, including one Loytec L-IP router designated as the 852 Configuration Server. In a basic system, a single LCS85 Server maps all LONWORKS devices in a single LNS database containing many LONWORKS IP routers on a single Ethernet/IP 852 backbone. The basic system is the easiest to set up because you enter all Ethernet TCP/IP addresses (shown in Figure 65) into the 852 Configuration Server. The Ethernet TCP/IP addresses include the LNS computer, LCS85, and all LONWORKS IP routers. Notes: If you are using the Echelon Configuration Server instead of the Loytec Configuration Server, the setup is identical to Figure 65, except that the embedded Configuration Server is disabled on the Loytec L-IP router and the Echelon Configuration Server resides on the LNS Tool (LN Builder). Computers occupying other addresses on the network are not shown in this system. The routers have been assigned generic Ethernet addresses to show how individual components are organized into the final system. : Appendix: Using a Flat LonWorks System with LCS 62

63 Figure 65: Basic Flat LONWORKS System Choose the 852 Configuration Server To set up a channel, you must first designate an 852 Configuration Server. You may use either the Echelon Configuration Server or the Loytec L-IP router as a Configuration Server. Consider easy access or the nearest location if you are using a Loytec L-IP router. You can choose any L-IP router to set up as the 852 Configuration Server, but you cannot choose more than one L-IP router. Configure the 852 Configuration Server After you designate a 852 Configuration Server, configure it with the Ethernet TCP/IP addresses of all system devices. See Appendix: LCS85 Gesytec 852 Configuration Settings for details. Configure the LONWORKS IP Routers You need to configure LONWORKS IP routers only if you are setting up a new system. If you are working with an existing system, the port number is the only changeable value in the Configuration Server s related routers. If this is a new system, the routers need IP addresses. The IP addresses must be static IP addresses, and assigned in cooperation with the IT department to ensure that no current or future conflicts exist. Configure LNS Computer The LNS computer resides on the Ethernet backbone. The LNS computer must be enabled with a standard CEA-852 communications capability because of its location. The LNS revision determines the type of driver that can be used. LNS 1.x and 2.x LNS versions prior to 3.0 have not been tested and are possibly incompatible with the CEA-852 standard. We strongly advise upgrading to LNS Version 3.0. : Appendix: Using a Flat LonWorks System with LCS 63

64 LNS 3.x (prior to LNS TURBO Edition) There are two options if the site is using LNS 3.x: Loytec NIC-852 The Loytec NIC-852 driver consists of software and a dongle (required for licensing). In the setup utility for the driver, you must enter the address and port for the Configuration Server. Upgrade to LNS TURBO Edition The other option is to upgrade the site to LNS TURBO Edition network operating system, with its integral 852 driver. Once a database is opened with LNS TURBO Edition, it is converted to the new format. However, consider this option carefully because no utilities are yet developed to revert a database back to the previous format. LNS TURBO Edition LNS TURBO Edition has an integral 852 communications driver, and can communicate directly over IP. Driver configuration consists of entering the Ethernet IP and port address of the Configuration Server. Important: Removing LNS TURBO after installation to revert to a previous version of LNS is a manual process that could result in data loss. Carefully consider this issue if you choose to install LNS TURBO Edition on your computer. Complex System Setup Figure 66 shows a complex system setup with multiple LCS85s operating within the same LNS database (same domain). This setup differs from a basic system because of the additional LCS85 servers. Note: If you are using the Echelon Configuration Server instead of the Loytec Configuration Server, the setup is identical to Figure 66, except that the embedded Configuration Server is disabled on the Loytec L-IP router and the Echelon Configuration Server resides on the LNS Tool (LN Builder). : Appendix: Using a Flat LonWorks System with LCS 64

65 Figure 66: Flat LONWORKS Complex System Network Partitioning Figure 67 shows a complex system partitioned into two separate LNS databases (2 domains). In this example, devices to the left of center are on Channel 1 (Domain 1), and devices to the right of center are on Channel 2 (Domain 2). Note: If you are using the Echelon Configuration Server instead of the Loytec Configuration Server, the setup is identical to Figure 67, except that the embedded Configuration Server is disabled on the Loytec L-IP router and the Echelon Configuration Server resides on the LNS Tool (LN Builder). : Appendix: Using a Flat LonWorks System with LCS 65

66 Figure 67: Complex System with Partitioned Network Guidelines for Network Partitioning Consider the following when you partition a network: The LNS computer must sit on both networks. Only one Loytec L-IP router can be designated as the Configuration Server for each CEA-852 channel. The Loytec L-IP router can be mounted in the server enclosure. As an example, Channel 2 shows a Loytec L-IP router near the LCS85 server at address This router has no nodes attached. The Loytec L-IP router designated Configuration Server may or may not have nodes attached. The device functions primarily as a LONWORKS IP router, but has configuration server capabilities. Using it in the field as a router and as the Configuration Server utilizes the full capability of the device. Systems are based on network addresses. Therefore, the logical organization (such as the example in Figure 66) may not match the physical location of the network. The communication in a partitioned system is divided. In the Figure 66 example, the left LCS85 (at address ) communicates only with Ethernet routers , , , , and The right LCS85 communicates only with Ethernet routers , , , , and Binding and other data sharing cannot occur between these two systems. Any data sharing between the two groups can only be done with the Metasys system through an Application and Data Server (ADS), Extended Application and Data Server (ADX), or Open Data Server (ODS). : Appendix: Using a Flat LonWorks System with LCS 66

67 Basic Partitioned System Setup Choose the 852 Configuration Server On each system, you may use either the Echelon Configuration Server or designate one of the Loytec L-IP routers as the Configuration Server. For Channel 1, consider easy access or the nearest location if you are using a Loytec L-IP router. Configure the 852 Configuration Servers After the Configuration Servers have been designated, each must be configured with the Ethernet addresses of the devices belonging to its own 852 channel. See Appendix: LCS85 Gesytec 852 Configuration Settings for details. Configure the Channels This partitioned system example includes two channels. Table 12 provides the IP addresses of all devices on Channel 1. Table 13 provides the IP addresses of all devices on Channel 2. Note: If you are using the Echelon Configuration Server instead of the Loytec Configuration Server, the channel configuration is identical to what is shown in Table 12 and Table 13, except that the embedded Configuration Server is disabled on the Loytec L-IP router. Additionally, the Echelon Configuration Server resides on the LNS Tool (LN Builder) and is configured to handle two separate LNS networks. The defined Configuration Server uses the same IP address with a unique port number in each instance to segregate the separate LNS networks. Table 12: Channel 1 IP Addresses IP Address Table 13: Channel 2 IP Addresses IP Address Device Loytec L-IP Router Configuration Server Loytec L-IP Router LONWORKS Ethernet Router Loytec L-IP Router Loytec L-IP Router LCS85 Server LNS Computer Device Loytec L-IP Router Configuration Server LONWORKS Ethernet Router LONWORKS Ethernet Router LONWORKS Ethernet Router LONWORKS Ethernet Router LCS Server LNS Computer Configure the LNS Computer The LNS computer has particular requirements for configuration during setup. Setup must be carefully considered, as each configuration option has its own effects on the system. See the Basic System Overview section for information on CEA-852 driver issues. : Appendix: Using a Flat LonWorks System with LCS 67

68 Setting up two LNS Computers is the equivalent to having two basic systems. Each LONWORKS system is independent and set up separately. Both systems are simple, but the complete setup requires more hardware and software. Complex Partitioned System Setup This system comprises a single large LNS database containing all nodes in the system with multiple LCS85 servers. The LCS85 servers are segregated to communicate to different devices within the same network. Segregation is based on designating complete FTT-10 channels to each LCS85. You manually partition the system ensuring only specific LONWORKS IP routers (or specific nodes) are mapped to the LCS85. No device can be mapped to both systems. This system closely meets flat LONWORKS system specifications and is still considered flat because any node can be bound to any other node in the system. The purpose of LCS85 server segregation is to break up the network into manageable pieces for incorporation into a Metasys system. Partitioning a network is a way to manage large systems, but does require some caution. Consider the following issues when you partition a large system: 1. Partition the system carefully. Cleanly divide the system to provide easily understood system organization. Clustering all devices under a single router is one method to clearly partition the system. Keeping each part of the system isolated prevents numerous smaller problems. 2. Consider command interference. Commands can interfere or clash with each other if two different LCS85 servers are commanding the same point in the field or if the same point is mapped to multiple objects. When commands clash with one another, the device carries out the last issued command. Systems that have this problem behave erratically. 3. Isolate devices to one router and one server. When two LCS85 servers are communicating, each one checks message error rates (messages unsuccessfully communicated). The error rate rapidly increases if multiple units start communicating down to a single router because the router can only handle a certain amount of traffic on the FTT-10 channel. As traffic increases, error rates increase and may overload the server. In response, all LCS85 servers reduce their communication rate to reduce the error rates. In a situation where error rates are high, both LCS85 servers reduce their communication at the same time and in the same manner because all machines use the same algorithm. When the error rates decrease, they increase communication at the same time and same manner. If multiple units are competing for bandwidth on the same router, this rise and fall in traffic continues indefinitely. You can avoid this problem by keeping all devices under one router isolated to one LCS85 server. : Appendix: Using a Flat LonWorks System with LCS 68

69 Appendix: LCS85 Gesytec 852 Configuration Settings The LONWORKS Control Server (LCS) 85 is certified for use with either the Echelon Configuration Server or the Loytec Configuration Server. The Gesytec Easylon IP Interface router resides on the LCS85 and requires different settings depending on which configuration server the LCS85 uses. Other configuration servers may work with the LCS85, but are not supported by Johnson Controls. Follow the instructions in this appendix to ensure successful operation of your LCS85. To review complete configuration procedures for each configuration server: Click Help > Contents in the Echelon LONWORKS/IP Configuration Server window. Go to and download the L-IP User Manual. Easylon IP Interface Configuration Settings Table 14 defines the Easylon IP Interface Configuration window settings. Go to Configuring the LCS85 for Use with the Loytec Configuration Server or Configuring the LCS85 for Use with the Echelon Configuration Server, depending on the configuration server you are using, and follow all directions in that section. See Table 14 as necessary as you configure the LCS85. Table 14: IP Interface Field Definitions Option Definition Device Name Config Server Address Config Server Port 852 Interface Address 852 Interface Port RNI Interface Port Multicast Multicast Address Multicast Port Enable Soft License Node-Id MAC-Address Key Debug Output Debug Mask User-defined name that identifies the device. Note: The Loytec L-IP embedded configuration server updates the members list using this name. Address of the Configuration Server. Must be user configured. Port used by the Configuration Server. Must match what is defined in the IP-852 Configuration Server. The default value is 1629 but may be changed. IP Address of the LCS which must be selected from the pulldown menu. The same address must be entered in the IP-852 Configuration Server members list. Port used by the 852 Interface. Must match what is defined in the IP-852 Configuration Server members list. The default is 1628 but may be changed. Port used by the installed Remote Network Interface. The default is and should not be changed. Enables Multicast support to deliver one packet to a group of IP hosts. The default is unchecked. If the Multicast option is selected, this IP address is used for the multicast group. If the Multicast option is selected, this port is used for the multicast group. This option must be checked to use a software license. A unique 12-digit hexidecimal Neuron Identifier used by LNS to commission and set the Domain Subnet Node address of the LCS. The default value is (12 zeros), but it may be pre-configured. MAC Address of the Network Interface that is defined by the 852 Interface setting in the IP Configuration setting. The license key that is generated by Gesytec licensing and is tied to the Node-Id and MAC Address. If the Node-Id or MAC Address changes, then the licensing is not valid and the 852 driver does not function. Used for troubleshooting purposes only. The default is unchecked. When Debug Output is selected, this is a user-defined value (in hex). : Appendix: LCS85 Gesytec 852 Configuration Settings 69

70 Table 14: IP Interface Field Definitions Option Definition Aggregation Multicast -TTL Config Server Pollinterval Enable Channelrouting Wants all packets Load saved channel config MD5 Authentication Shared Secret Hide Console Automatic Start as Service Apply button Cancel button Stop App. Log Groups multiple CEA-709 packets into a single IP packet. When checked, a value must be entered in ms to define how long the driver waits before sending the IP packet. The default is unchecked. Note: Although aggregation can improve throughput, care must be taken when configuring this setting. A long delay can cause LCS devices to go offline intermittently. Multicast Time-To-Live specifies the number of router hops that multicast traffic is permitted to pass through before expiring on the network. The default is 64. How often, in seconds, the driver checks to see if the Configuration Server is online. When selected, IP packets are routed to the correct destination. When selected, the 852 driver receives all packets. Defines whether or not the 852 driver loads the saved channel configuration settings. This setting varies depending on the configuration server being used. When selected, enables encryption. The default is unchecked. When MD5 Authentication is selected, this user-defined value encrypts packets over the LONWORKS IP Network and all IP 852 members must be configured with the same setting. Hides the console from Desktop view. The default is checked. Must be enabled for proper LCS operation. The default is checked. Must be enabled for proper LCS operation. The 852 driver starts as a service, removing the need for a user to be logged in to the LCS. The default is checked. Saves the settings and starts the 852 driver. Reverts any unsaved settings back to the previous value. Stops the 852 driver. Displays the executed commands. Configuring the LCS85 for Use with the Loytec Configuration Server 1. Go to Start > All Programs > Easylon > 852, then right-click Config 852 Interface and select Run as administrator. The Easylon IP Interface Config Settings window appears. 2. In the window, configure the settings to match Figure 68. See Table 15 for the options to select. Note: The IP Configuration and Soft Licence Configuration sections contain information that is unique to the site configuration and the hardware installed. Do not change these settings. : Appendix: LCS85 Gesytec 852 Configuration Settings 70

71 Figure 68: Easylon IP Interface Config Settings for the Loytec Configuration Server Table 15: Easylon IP Interface Config Settings for Use with the Loytec Configuration Server Field Selection or Entry Aggregation Config Server Pollinterval Enable Channelrouting Load saved channel config Automatic Start as Service 3. Click Apply. Must be selected with a setting of 8 ms. Note: This selection and its setting may be modified on a per-site basis if you wish to match the aggregation of the LCS85 with the aggregation of the Loytec router. Must not be selected. May be selected if you wish to reduce traffic, but it is not required. Must not be selected, otherwise the LCS85 does not communicate on the LONWORKS network. Because the channel information is not saved, the configuration server must be online and communicating when the LCS85 starts up. Must be selected. Must be selected. : Appendix: LCS85 Gesytec 852 Configuration Settings 71

72 Configuring the LCS85 for Use with the Echelon Configuration Server 1. Go to Start > All Programs > Easylon > 852, then right-click Config 852 Interface and select Run as administrator. The Easylon IP Interface Config Settings window appears. 2. In the window, configure the settings to match Figure 69. See Table 16 for the options to select. Note: The IP Configuration and Soft Licence Configuration sections contain information that is unique to the site configuration and the hardware installed. Do not change these settings. Figure 69: Easylon IP Interface Config Settings for the Echelon Configuration Server Table 16: Easylon IP Interface Config Settings for Use with the Echelon Configuration Server Field Selection or Entry Aggregation Config Server Pollinterval Enable Channelrouting Must be selected with a setting of 8 ms. Must be selected with a setting of 60. May be selected to if you wish to reduce traffic, but is not required. : Appendix: LCS85 Gesytec 852 Configuration Settings 72

73 Table 16: Easylon IP Interface Config Settings for Use with the Echelon Configuration Server Field Selection or Entry Load saved channel config Automatic Start as Service Must be selected, otherwise the LCS85 does not communicate on the LON network at startup if the configuration server is not running. The LCS85 must initially communicate on the LON network before the channel configuration can be saved. Must be selected. Must be selected. 3. Click Apply. Configuration Servers Configuring the Loytec Config Server The Loytec Configuration Server is embedded in the Loytec L-IP router and can be enabled or disabled. Only one router may have the configuration server enabled. 1. Open the Windows Internet Explorer web browser. 2. Enter your assigned IP address in the URL. The Loytec Device Info screen appears. 3. Select Config from the vertical menu on the left. 4. Log in with the administrator password to access the Loytec Config Server. If you are using firmware prior to Release 4.0, the default administrator password is admin. If you are using firmware at Release 4.0 or later, the default administrator password is loytec4u. 5. Select IP from the vertical menu on the left. The Config IP screen appears (Figure 70). : Appendix: LCS85 Gesytec 852 Configuration Settings 73

74 Figure 70: Config IP 6. Configure the settings shown in Figure 70. See Table 17 for the options to select. Some settings vary on a per-site basis and must be modified accordingly. The IP settings are unique to your computer. Table 17: Config IP Settings Field DHCP/BOOTP IP Address IP Netmask IP Gateway Hostname Selection or Entry Disabled Modify accordingly. Modify accordingly. Modify accordingly. Modify accordingly. : Appendix: LCS85 Gesytec 852 Configuration Settings 74

75 Table 17: Config IP Settings Field Domainname DNS Server 1 DNS Server 2 DNS Server 3 NAT Address MAC Address Link Speed & Duplex Multicast Address Connection Keep Alive Selection or Entry Modify accordingly. Modify accordingly. Modify accordingly. Leave empty. Leave empty. Select Use Factory Default check box. Auto Detect Leave empty. Disable 7. Click Save Settings. 8. Click EIA-852 Device in the menu on the left. The Config EIA-852 Device screen appears (Figure 71). Figure 71: Config EIA-852 Device 9. Configure the settings shown in Figure 71. See Table 18 for the options to select. Some settings vary on a per-site basis and must be modified accordingly. The Config server address and Config server port settings are : Appendix: LCS85 Gesytec 852 Configuration Settings 75

76 unique and cannot be used by any of the devices defined in the members list. The Config client port setting must match all devices defined in the members list. Note: An encryption warning message may appear when you are configuring the settings. You can ignore this message. This behavior is typical for LONWORKS protocol. Most sites do not require encryption. Table 18: Config EIA-852 Device Settings Field Config server address Config server port Config client port Device name Escrow timeout [ms] Aggregation timeout [ms] MD5 authentication MD5 secret Location string Selection or Entry Modify accordingly. Default is Modify accordingly. Default is Modify accordingly. Modify accordingly. Modify accordingly. 8 (Must match the Aggregation setting in the Easylon IP Interface.) Default is off. Enable for authentication. Leave empty unless MD5 authentication is on. Modify accordingly. 10. Click Save Settings. 11. Click EIA-852 Server in the menu on the left. The Config EIA-852 Server screen appears (Figure 72). : Appendix: LCS85 Gesytec 852 Configuration Settings 76

77 Figure 72: Config EIA-852 Server 12. Configure the settings shown in Figure 72. See Table 19 for the options to select. Some settings vary on a per-site basis and must be modified accordingly. The server is enabled on only one device. All others are disabled. Table 19: Config EIA-852 Server Settings Field Config server status Config server port Channel name Pri.SNTP server Sec.SNTP server Channel timeout [ms] Auto members Roaming members Selection or Entry enabled Default is Modify accordingly. Modify accordingly. Leave empty. Leave empty. Leave empty. off off : Appendix: LCS85 Gesytec 852 Configuration Settings 77

78 Table 19: Config EIA-852 Server Settings Field MD5 authentication MD5 secret Selection or Entry Default is off. Enable for authentication. Leave empty unless MD5 authentication is on. 13. Click Save Settings. 14. Click EIA-852 Ch. List in the menu on the left. The Config Channel List screen appears (Figure 73). Note: This screen is only available on the device that is enabled to be the configuration server. Figure 73: Config Channel List 15. Click Add Device. 16. Enter the device name, IP address, and port in the open fields. 17. Click Save. 18. Repeat Steps 15 through 17 for each device. Each device name in the list updates after the IP address and port are entered and saved. A successfully configured system has a green check mark in the Stat column. 19. See Table 20 to determine the status of your devices. Systems that do not have a green check mark do not function correctly. If necessary, see Troubleshooting Communication between the Configuration Server and Devices. : Appendix: LCS85 Gesytec 852 Configuration Settings 78

79 Table 20: Device Status on Loytec Config Server Icon Status Unregistered Not Contacted Registered Not Responding No Extended NAT Disabled Description The CEA-852 device is not registered with the IP-852 channel. The CEA-852 device has not been contacted since the configuration server has started. The CEA-852 device is successfully registered with the IP-852 channel and is fully functional. The CEA-852 device is registered, but it is not responding at the moment. The CEA-852 device does not support the extended NAT mode. This device is disabled. The CEA-852 device is disabled, or rejected, on the channel. 20. When the configuration is complete, go to Configuring LONWORKS Interfaces and complete all steps in that section. Configuring the Echelon Config Server Note: Most installations that use the Echelon Config Server also use an LNS network management tool on the same computer. 1. Go to Start > All Programs > Echelon IP-852 Configuration Server > IP-852 Configuration Server. The Echelon LONWORKS/IP Configuration Server window opens. 2. Select Channel > New Channel to create a new channel named Configuration Server ( ). Note: You can rename the channel by clicking the channel, then selecting Channel > Rename Channel in the menu. 3. Right-click Configuration Server and select Channel Properties. Ensure the channel properties match those in Figure 76. The Configuration Server port is unique and is not used by any of the devices in the list (Figure 74). The default port is Select Channel > New Device. Notes: You can rename the device by clicking New Device, then selecting Device > Rename Device in the menu. (All the devices in Figure 74 have been renamed.) If the config server resides on the same computer as the device, all device statuses update immediately. If the config server and the device reside on different computers, the status of the added device may not update until you select Update Members (Step 7). 5. Right-click the new device and select Device Properties. Ensure the IP address is the same and that the port is not the same as that in the Configuration Server. The default port is 1628 for the device. 6. Repeat Steps 4 and 5 for each router that exists. The IP address and port must match what is defined in the router. 7. Once all devices have been added, select Channel > Update Members. The configuration server establishes communication with and updates the configuration of all the devices (Figure 74). If the update is successful, the device icon turns green ( ), indicating normal operation. Systems that are not green do not function correctly. : Appendix: LCS85 Gesytec 852 Configuration Settings 79

80 Figure 74: Echelon LONWORKS/IP Configuration Server 8. See Table 21 to determine the status of your devices. If necessary, see Troubleshooting Communication between the Configuration Server and Devices. Table 21: Device Status on Echelon Config Server Status Color Description Blue Green Red Yellow Orange Red/White There is no communication with the device in this session. Normal. Communication has occurred with the device during this session. Communication with the device has failed after you select Update Members. Usually, this status indicates that no response is received from a device to which a request was made. Make sure that all security and IP settings are configured properly. Normal communication, but the Time Check has failed. The i.lon 600 router configuration is out of date, incorrect, or incomplete. This status normally indicates work in progress. When the Configuration Server updates the i.lon 600, the icon turns green. For a large channel (more than 40 devices), this update can take several minutes. If you change a bind in LonMaker, this can require that the routing tables in every i.lon router be updated. In this case, you may see many icons turn orange, and then one-by-one turn green again when their routing tables have been updated. Device is disabled. 9. When the configuration is complete, go to Configuring LONWORKS Interfaces and complete all steps in that section. : Appendix: LCS85 Gesytec 852 Configuration Settings 80

81 Configuring LONWORKS Interfaces The LONWORKS Interfaces (also referred to as the Open LDV Network Driver by Echelon) must be installed on a computer that is running LN Builder using an IP-852 connection. Important: Skip this section if LN Builder (or another LNS Network Management Tool) is not using an IP-852 connection. You must have a functioning configuration server set up before you configure LONWORKS Interfaces. Follow all directions in Configuring the Loytec Config Server or Configuring the Echelon Config Server, depending on the configuration server you are using, before completing the steps in this section. 1. Go to Control Panel > LONWORKS Interfaces. The LONWORKS Interfaces window opens. 2. Select Interface > Add to see the interfaces you may add (Figure 75). Note: Though not shown in Figure 75, the USB Interface automatically appears in the list when it is connected. Figure 75: LONWORKS Interfaces 3. Select IP-852 Interface from the menu. The IP-852 properties appear in the right pane of the window (Figure 76). : Appendix: LCS85 Gesytec 852 Configuration Settings 81

82 Figure 76: Adding an IP-852 Interface 4. Ensure that the IP address and port are correct. The IP Address field defaults to the IP address defined for the computer and the port defaults to This port must match the port defined in the routers. Any changes are saved automatically. 5. Click View and enable the Diagnostics pane if it is not already enabled. The Diagnostics pane displays the results of the connection when you test the communication between the configuration server and the device. 6. Select the device in the left pane and click Test. The IP-852 Configuration Server Properties dialog box appears. 7. Select the check box and enter the IP address and port of your configuration server (Figure 77). Figure 77: IP-852 Configuration Server Properties Window 8. Click OK. The dialog box disappears and the diagnostics pane displays the message The test has started. Waiting for reply from IP-852 Configuration Server. : Appendix: LCS85 Gesytec 852 Configuration Settings 82