Building Automation Knowledge Base

Issue A message saying "no license available" or starting the license finder popup.  Sometimes Flex license system needs a little extra time to load the licenses. Product Line TAC Vista Environment FLEXnet Licensing Cause The problem is in the Flex license system and not in TAC Vista, the same issue occurs on other Software vendors using the same license system. Resolution Make sure that you are logged in as an admin on the computer. Right-click on This PC > Properties > Advanced system settings Click the button in the lower-left corner labeled "Environment variables" Add a new system variable named FLEXLM_TIMEOUT Give it the value 3000000, press OK Restart TAC Vista Server and Workstation, the Flex license system will now have 3 more seconds before throwing out a message saying "no license available" or starting the license finder popup.

Issue NRE default configuration and RAM disk removal Product Line TAC IA Series Environment I/A Series N4.11 Jace 8000 Cause In Niagara 4.10u1 and earlier, the RAM disk was used to temporarily store alarm and history data. During station save, this data was copied from the RAM disk and zipped up, and stored on Flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the Flash. Resolution A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. JACE-8000 NRE Memory Default for (older) Niagara 4.10 - sizes in MB: System Reserve Size:          0 Heap Space Size:              360 Meta Space Size:              56 Code Cache Size:              16 RAM Disk Size:                384 Free Memory:                  ~16 JACE-8000 NRE Memory Default for (newer) Niagara 4.11 - sizes in MB: System Reserve Size:          0 Heap Space Size:              384 Meta Space Size:              64 Code Cache Size:              32 RAM Disk Size:                Not present (cannot be created) Free Memory:                  ~352   These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000.

Issue Tridium N4.11 Upgrade Considerations  Product Line TAC IA Series Environment I/A Series N4.11 Enterprise Server I/A Series N4.11 Jace 8000 Cause Detailed information about N4.11 upgrade prerequisites and best practices  Resolution The following details a set of upgrade considerations and known issues and their workarounds regarding Niagara 4.11. Please review prior to upgrading to Niagara 4.11. Niagara 4.11 and Default NRE Memory Changes: A change to the JACE-8000 file system has been introduced with the release of Niagara 4.11. The RAM disk was used to store alarm and history data. During station save, this data was copied from the RAM disk and zipped up into a single file that was stored on flash. In Niagara 4.11, the RAM disk has been removed entirely. This data is now written directly to the flash memory. This change has enabled ~384MB of RAM to be freed up to improve performance. Some of the space has been reallocated to code cache, metaspace, and heap space in the 4.11 NRE default settings. Any additional memory space is now available as general free memory. These changes should be transparent to most users and will provide moderate performance improvements on the JACE-8000. Prior to upgrading your JACE-8000, please review NRE default configuration changes and RAM disk removal In 4.11. Niagara 4.11 and Third-Party Modules Keeping your Niagara installations safe and secure is our highest priority. In Niagara 4.11, ALL third-party modules must be signed with either a trusted valid certificate or a self-signed certificate to successfully run on a station. This new policy greatly increases the security posture of Niagara installations by making administrators aware of any modules that may have been tampered with, compromised, or derived from untrustworthy sources. Niagara's new signature enforcement feature is being rolled out over multiple Niagara releases. The first iteration was built into release 4.8 to give developers adequate time to make the transition to always signing any third-party modules. Niagara 4.8 produced console and Security Dashboard warnings about unsigned modules but allowed them to run on a station. As of Niagara 4.11, unsigned modules will not execute. For more information, please review the Niagara documentation on Third-Party Module Signing Niagara 4.11 Updated Operating Systems, Browsers, and Databases For the latest information on supported operating systems, please refer to Supported OS and other software in the Niagara 4 Framework Installation Guide. Tridium remains focused on keeping pace with advancing IT infrastructure to enable more efficient, long-term support of each release version. This policy enhances the security posture of a Niagara installation by ensuring that only the most robust, secure operating systems and enterprise applications are compatible with the framework. The list below provides information on what we will be supporting with Niagara 4.11.   OS, Browser, Database Version Red Hat Enterprise Linux 8.1 (64 bit), 7.7 Ubuntu Linux 20.04 LTS – Desktop & Server Windows Server 2019 (64 bit), Server 2016 (64 bit), Windows 10 (64 bit) VMWare ESXi 6.7 Oracle Database 19.3, 18.3, ... 12.2/12.1 MySQL Database 8 MS SQL Database 2019, 2017, 2016 Browsers Chrome, FireFox, Microsoft Edge Mobile Browsers Safari (iOS 12, 13), Chrome (Android 8, 9, 10) As with all software products, we must also deprecate support for some operating systems and enterprise applications.  Nevertheless, you can be confident that the above list will handle your needs moving forward. Using Web Launcher with Niagara 4.11 Web Launcher 21.4.1 was recently revamped for Niagara 4.11 to include essential software dependencies updates along with critical defect fixes. This version of Web Launcher has Java version 8 update 311 and certificate management has been updated to work with Niagara 4.11 along with any legacy or prospective release. Prior to using Web Launcher with Niagara 4.11, customers should update Web Launcher accordingly (see steps below). How to update Web Launcher? Web Launcher has a feature to check for updates over the internet and prompts the user when a new version is available in the cloud. However, the existing version of Web Launcher has a bug that prevents a smooth update. Users will be required to perform a fresh install by downloading the latest version from the cloud via the station web Login page. Click on the Niagara Web Launcher Installer link on the station's Web Launcher Web Page, which can be reached via the link on the Login page itself. Once the download is successful, click on the msi file and follow the installation wizard. You do not have to uninstall the older version. The new installation will automatically update to the latest version. Niagara 4.11 Release Notes: The release notes for Niagara 4.11 are located here.

Issue Java is no longer available or supported in most web browsers so accessing Niagara using the Java Applet is no longer possible Product Line TAC IA Series Environment I/A Series G3 Enterprise Server/Jace 3.8U4 I/A Series N4 Enterprise Server/Jace 4.4U3 and subsequent Cause Oracle announced the end-of-life of Java SE 8 (Standard Edition). As of January 2019, free public updates for commercial users are no longer available. Customers accessing Niagara with the Java Applet/Web Start are impacted by this change. Those who have upgraded to full HTML5 versions for your browser front-end will not be affected. For customers who use the Java VM and Java Web Start for their legacy systems, Tridium has developed a suitable alternative, the Niagara Web Launcher. Resolution The Niagara Web Launcher application is now available. You can download Niagara Web Launcher using the following link: 64-bit systems: Web Launcher for 64 bit, 32 bit OS 32-bit (-x86) systems: Web Launcher for 64 bit, 32 bit OS Niagara Web Launcher download links are also available from the Niagara station login page. Niagara Web Launcher support is included in Niagara versions: 4.4U3 –Included in (4.4.94.14). 4.7U1 - Included in (4.7.110.32) Subsequent releases of Niagara 4 will include Niagara Web Launcher support. A patch for Niagara 3.8 U4 can be downloaded from here.  Copy web.jar module version 3.8.403.1 into the modules folder of your Niagara AX 3.8 U4 workbench or supervisor station.  This module may also be installed on JACE platforms.  To use Niagara Web Launcher, Web Start must be enabled in the Web Service of the station.

Issue Troubleshooting guide for ASD bus communications. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Legacy Controllers ( GCM, MicroZone II, MicroFlo II, LIM, PEM, MN-ASDI) I/A Series R2 UNC I/A Series G3 ENC Building Operation Automation Server Premium ( Pre EBO 2022 ) I/A Series N4 Jace 8000 Cause Troubleshooting guide for ASD bus communications. Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. NOTE:  The ASD protocol is not supported in EBO 2022 or subsequent versions

Issue It is not possible to change Primary or Secondary Reader Formats as they are greyed out. Product Line EcoStruxure Security Expert Environment Security Expert Client, Security Expert Server Cause When the Reader Expander Port network type is set to Schneider Electric RS485 the Reader format is edit locked and unable to be changed. Resolution The Port network type on the Reader Expanders General tab needs to be temporarily changed to Wiegand.  Under the Reader tab the Reader Format and Reader Secondary Format can now be changed. Repeat this process for Reader 1 and/or Reader 2 as required. On the Reader Expanders General tab change the Port network type back to Schneider Electric RS485. Save your changes, perform a download and update the Reader Expander.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Proper configuration of supervised inputs, Mercury IO modules (i.e MR52) versus Continuum IO modules (AC1/AC1Plus) for transitioned Continuum sites. Product Line EcoStruxure Access Expert Environment Access Expert Controller Access Expert Reader Interface Access Expert Premise Software Access Expert Hosted Software Continuum AC-1 IO Module Cause Guidance is needed on the proper configuration of Access Expert custom EOL resistor tables in order to achieve full supervision of inputs associated with readers/doors. Full supervision in this context means not only being able to detect normal input operation (activation/deactivation) but also detection of attempts to tamper with the input's circuit (short circuit, open circuit, grounding, the introduction of foreign voltages, etc.) Please note that not all resistor configurations can detect all the various circuit issues, for example, a NO Series resistor configuration can't detect a cut in the wire given that the open circuit is the normal state for the Deactivated value of the input. The resistor configuration that provides the most supervision is the Series/Parallel configuration, using 2 resistors is possible to detect both short and open circuits. Resolution Continuum supported a fixed 10K Ohms resistance for supervised inputs, furthermore, Continuum IO modules (AC1/AC1Plus) transitioned to Access Expert under an AX-SSC controller continue to operate with Continuum firmware, this means that they do not support the custom EOL tables in Access Expert, the only configuration that is possible for AC1/AC1Plus modules is the mode of connection of the resistor (parallel, series or both).   Also, when using 2 resistor configuration, the placement of the resistor is different in Continuum compared to Mercury hardware   CONTINUUM When the switch is open only the resistor on the left is seen by the input. When the switch is closed, the two resistors are presented to the input in parallel with each other resulting in the input reading half the sum of the total resistance value.   SECURITY EXPERT       When the switch is open, the two resistors will be presented to the input in series with each other resulting in the input reading the sum of the two resistors value.  When the switch is closed only one resistor is presented to the input   For the above reasons, Continuum transitions sites where the AC1/AC1Plus has been replaced with Mercury hardware like the MR52 for example, need to configure one or more custom EOL table(s) for 10K resistors.   *** The sample tables provided below contain resistance values calculated to take into account wide variations in total supervised loop resistance due to wire distance, gauge etc., supervised loops should be installed in accordance to distance and gauge guidelines for wires as well as recommended resistor tolerance. It may be necessary to make adjustments to the resistance values in the tables on a site by site basis.   See below sample tables for all six possible 10K resistor configurations   Normally Open Parallel (10K-NO-P) Normally Closed Parallel (10K-NC-P) Normally Open Series (10K-NO-S) Normally Closed Series (10K-NC-S) Normally Open Series/Parallel (10K-NO-SP) Normally Closed Series/Parallel (10K-NC-SP)+ 1. Normally Open Parallel (10K-NO-P) 2. Normally Closed Parallel (10K-NC-P) 3. Normally Open Series (10K-NO-S) 4. Normally Closed Series (10K-NC-S) 5. Normally Open Series/Parallel (10K-NO-SP) 6. Normally Closed Series/Parallel (10K-NC-SP)+

Issue Getting "Commport is not XDriver enable" error when attaching the driver file to the comm port. Comm port has been flashed to enable XDriver operation. Controller Options shows Xdvr Comm2:00000009 (0000) Product Line Andover Continuum Environment BCX NCI NCII B4920 XDriver Comm Port Cause Bad controller XDriver support flash file. Resolution 1. Take the Workstation offline, edit the comm port, and set the default mode to "XDriver". 2. Go back online and send the comm port to the Controller. 3. Attempt to attach the Driver file to the comm port, if the same error occurs then contact Schneider repair department for a new XDriver option flash file. See article Determine if a controller comm port is XDriver enabled - Communities (se.com) 

Issue WorkPlace Tech Tool reports Database Error when attempting to link to the output of a copied custom object. The displayed error message shows the name and attribute of the object being connected along with the error "Exception error occurred during WriteProperty [0xE0330020]". Product Line TAC IA Series Environment WorkPlace Tech Tool Software Version 5.7.x or newer Workplace Tech application file containing a custom object copied from another WPT application. Cause Unknown, believed to be an internal Visio error. Resolution Open the application file in the WorkPlace Tech Tool software and select the page for the Custom Object that is reporting the error. Break the connection (disconnect the link) between the Custom Object output tag and the corresponding source object. When breaking the link, it is suggested that the wire link be dropped onto the drawing page before being re-linked. Select the link and reconnect it to the proper object. It may be necessary to perform this unlink and relink operation for all output tags within the Custom Object that had been copied from another WPT application file.

Issue The following Popup window is displayed when attempting to open WorkPlace Tech. WPTech Unable to load WorkPlace Tech Ribbon for Visio. There was a problem loading the WorkPlace Tech Fluent Ribbon for Visio, therefore, it will be unavailable. Product Line TAC IA Series Environment Visio 2010, 2013, 2016, and 2019 WorkPlace Tech Tool release 5.8 or later Cause If Visio crashes when a third-party ribbon bar function is in use, Visio may lockout that ribbon bar, believing that something on that ribbon bar caused Visio to crash.  In this case, a menu function, selected from the WorkPlace Tech (WPT) ribbon bar was being processed at the time Visio crashed, therefore Visio locked out the WorkPlace Tech ribbon bar. This is a system protection mechanism built into the ribbon bar handler in all Microsoft Office applications including Visio.   Resolution To re-enable the WorkPlace Tech ribbon bar, perform the following steps: Open Visio.  NOTE: Open Visio, not WorkPlace Tech. Select Options from the File menu. From the menu in the Visio Options window, select Add-ins At the bottom of the window, you will see a field that says 'Manage:' with a selection box after it, select 'Disabled Items' and then click the [Go] button. In the 'Disabled Items' window, select 'WorkPlaceTech.VisioRibbon' then click the [Enable] button. Close the open Visio windows and sub-windows. After closing Visio, the WorkPlace Tech ribbon bar will be available in WorkPlace Tech.  

Issue After editing an MNL-800 application with the WorkPlace Tech Tool Editor, an error is displayed indicating that the application file could not be saved. Product Line EcoStruxure Building Operation Environment Building Operation Workstation >1.4 Building Operation WorkPlace Tech Editor Cause The name of a LON Network Variable (nvi or nvo SNVT) or a LON controller configuration constant (nci SNVT) contains a space. Echelon standards do not allow spaces in network variables or configuration constant names. Resolution Edit the application file removing any spaces or other non-supported characters from network variable and configuration constant names. More information is contained in the SBO WebHelp topic "WorkPlace Tech Editor"

Issue After the successful installation of Continuum 1.9x, users are receiving a DCOM Permission error when logging on to Continuum webClient. The error is intermittent. Product Line Andover Continuum Environment Microsoft Server 2008 Standard Microsoft Windows 7 Continuum 1.9x and 2.0 Continuum webClient Server Remote Desktop Cause When a remote desktop connection is made on Windows 7 or Windows 2008 Server the console occasionally gets locked. It stays locked until the local session is restored with a logon. Resolution Create a .bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console **************************************************************************************** Place this file on the desktop of the Continuum webClient Server system. When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be run "As an Administrator." This will disconnect the session and restore the console.

Issue Detailing configuration and starting DWiz on a computer running EcoStruxure for Buildings Operation. Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Xenta 281 Xenta 301 Xenta 401 Cause DWiz (Download Wizard) was a part of the TAC Vista installation, but not so commonly used in EcoStruxure Buildings Operation, and therefore no longer included in the Start menu. It is however still installed and could be started from Windows File Explorer. Resolution   Verify the Com port used. If your computer does have a serial port, this is normally Com1 or Com2. If you are using a USB to RS232 adapter (like Aten), you could get a much higher number. The program requires a port number between 1 and 9. You may need to change the port number. This could be done via Windows Device Manager. In Windows File Manager, go to the directory where EcoStruxure Buildings Operation Workstation is installed. Here you will find DWiz.exe as well as MentaSetup.exe. Start MentaSetup.exe, adjust Com Port, select Apply and Close. MentaSetup        5.  Now it should be possible to start DWiz.exe located in the same directory.

Issue Despite using valid credentials at the Web Client login screen, the attempt fails with no error being shown and the user is dumped back to the login screen once more. These login failure events can be seen in Windows Logs with the error 'Too many connections' Event Viewer > Applications and Services Logs > Schneider Electric Security Expert Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Web Client Security Expert SOAP Service Cause When the SOAP service attempts to connect to Security Expert it performs an Operator login to the Data Service, pulls/pushes the information it needs, and then closes the connection. If all concurrent Operator Logins are already in use (with Thick Client connections for example) SOAP will not be allowed to log in, and any services requiring the SOAP connection will not work. The specific operators that are consuming the licenses can be seen once again in Windows Logs Event Viewer > Applications and Services Logs > Schneider Electric Security Expert An Operator Logging on is shown as a 'New Operator Logon' Event (Concurrent Client + 1) Operator Log in An Operator Logging off is shown as a 'Remove Operator by Disconnect' Event (Concurrent Client - 1). Operator Log off Resolution If all the Client Connections are being consumed with Thick Client logins etc, then reduce the number of connections that are logged in at any given time or purchase an additional concurrent client license SX-CLNT so there is always one free for SOAP to use. Note:  SOAP will only use one concurrent connection even if it has multiple services connected to it, so you would not need multiple client licenses if you had Web Client, Data Sync, and EWS, for example.

Issue When attempting to login to Security Expert Web Client the below error is seen. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause The typical cause of this error is a mismatch in the security bindings between the SOAP Service and the Security Expert Data Service. For example if you enable the Windows Authentication checkbox in the Security Expert installer but not in the SOAP Service installer (or vice versa) then you have a mismatch. Resolution Either uninstall the SOAP service and update the checkbox selection to match whatever was selected in the Security Expert installer, or follow the instructions under Troubleshooting | Communication Fault/Failure in the SX-WEB - Security Expert - Security Expert Web Client - Installation Guide for editing the config files of the SOAP service to match the Security Expert Data Service.

Issue When reviewing events from Doors or Users, the below error is shown. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. Error - The communication object Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Workstations SP-C Controllers. Cause Firewall and/or Port settings are incorrectly configured. Certain ports must be opened to enable communication between the server, client workstations, and controllers. Resolution Check the Firewall to ensure that all required ports are open between the Security Expert Server, Security Expert Client Workstations and the SP-C Controllers. Refer to the IP Networking Ports section in the SX-SRVR Security Expert - Networking Guide for Administrators - Reference Guide for details on required ports.

Issue Instructions on how to configure a Bosch Integration on Version 3. Product Line Access Expert Environment Access Expert Version 3 Microsoft Windows 8.1 and above Access Expert Hosted software with Bosch integration Access Expert Premise with Bosch integration Cause Configuring a Bosch Integration on Version 3 to communicate to Access Expert. There are certain settings that need to be configured from both the Access Expert side and Bosch so that the integration can be seamless and function as designed. Resolution One of the first things when doing this Integration is to have the Bosch Appliance ordered and installed on the Network where the Bosch Panel resides. The device comes pre-configured from Feenics and all that is needed is to make the necessary changes in Access Expert using the following steps: 1. Verify that the connected instance does have the Bosch Services Enabled by going to the Hardware Provisioning and looking at the Bosch Services.  2. Click on the Bosch Services. 3. This entry would come up automatically as it was preconfigured into the Hosted Instance by Feenics. 4. Click on the Panels label and add the Bosch Panel Type from the dropdown. 5. Enter the necessary values on the various fields that correspond to the Bosch Panel, the Password must match what the Bosch Panel is using. 6. Import the Configuration and then save and close. 7. On the Bosch Panel verify that the Port is set for Port 7700, Automation Mode is set to 2 and the Firmware is 2.0 or greater If changes need to be made, you need to first connect to the Panel from RPS > make the changes > sync to the panel > disconnect from the panel Go into the appliance and stop/restart the Feenics Bosch Service within Windows Services 8. Make the necessary changes if needed then save and recycle power 9. Bring up the Hardware Tree and verify that the Panel is Online and communicating 10. All preconfigured Areas, Points, and Outputs will show up in Green, indicating that everything is working properly.

Issue OEM conversions allow for a non-Access Expert/Feenics Mercury board to be converted to an Access Expert board. This is only applicable to the IP level controllers and the AX-OEMC codes are not needed for the downstream controllers.  The process will change the OEM code within the Device info page of the controller. This allows the board to receive the correct firmware and operate within Access Expert.  Product Line EcoStruxure Access Expert Environment Access Expert Controller Cause Not all controller boards are compatible with Access Expert by default Resolution To perform the OEM conversion on an intelligent controller, an AX-OEMC code is needed per IP Controller connected to your system.  These are ordered through iPortal and will require some specific information from the customer's site.  With your order, please include (both are located on the white sticker located on the actual controller: Model of controller Serial number Email address for recipient The OEM flash code will be emailed to the person whose email address is used in the order as the recipient.  To convert the controller: Using IP Server. Connect directly to the controller with an ethernet cable Locate the IP address of the controller (The default IP address can also be used). Go to the 'Host Comm' section of the configuration manager. Set the connection type to 'IP Server'. Take note of the Port Data Security should be set to none or TLS if Available Save and apply changes. Open the OEM & firmware utility. Download Here Set the controller connection type of the utility to 'Server'. Enter the MAC address of the controller. Enter the IP address of the controller. Enter the TCP port used by the controller. Select 'Connect'. Once connected, enter the Authorization code provided by Schneider Electric. Select 'Convert'.   OEM conversion complete. Once the conversion has been completed, the panel will need to be set back to the IP client to connect to the Access Expert Mercury Communication Servers. See the Configuring Controllers for IP Client page for instructions.  

Issue Many LonWorks network installation problems can be avoided if the appropriate network design rules are followed when the network is being designed. Product Line TAC IA Series, TAC Vista, Satchwell Sigma Environment I/A Series MicroNet (LON) Controllers Satchwell Sigma MicroNet series LON Controllers Vista Xenta Controllers Cause The I/A Series MicroNet System Engineering Guide (F-26507) was written as a resource of information for the installation of the I/A Series MNL-100, 200 & VAV controllers as well as the Sigma MicroNet 440 and 620 controllers.  The Resolution, below, is a summary of the LON design rules presented in this document. Resolution FTT-10 LON network wiring must be installed using Echelon-approved wire.  The most common type of wire used is described as Category 4  cable.  This wire is normally unshielded stranded twisted-pair 22AWG (0.65mm).  An example of this wire is the W221P or W222P series cable from Connect-Air International (http://www.connect-air.com).  This type of cable is normally available both in plenum rated and non-plenum rated types.  Consult the job specifications to determine if plenum-rated or shielded cable is required. The LON network can be wired using "Free Topology" or "Bus Topology" wiring segments.   1.  BUS Topology Guidelines BUS Topology LonWorks wiring extends from device to device (daisy chain format) with no branches or stubs. A LON-TERM-2 terminator must be installed at each end of the LON bus. When using standard Category 4 LON cable with the recommended terminators, the bus may be up to 4593 feet (1400 meters) in length. When extending LON wire to the MN-Sx sensor base in a bus topology network, the sensor base must be wired as part of the daisy chain and not as a stub connection. 2. FREE Topology Guidelines Free Topology imposes essentially no restrictions on the layout of the network -- some controllers may be wired point to point and others branching from a common point.  The free-topology LON network must be terminated at one point with a LON-TERM-1 terminator. When using standard Category 4 LON cable, the total wire length in a free topology LON network may not exceed 1641 feet (500 meters).  In addition, the longest wire path between any two controllers on a free topology LON network may not exceed 1312 feet (400 meters). 3. Common LON Network Wiring Guidelines LON wiring can not be part of an active bundled telephone trunk even if the telephone trunk is wired with Category 4 wire. Shielded Category 4 wire may be used in high EMI/RFI environments.  The shield must be wired continuously and grounded through a 470 Kohm resistor at one end. LON wiring must not be bundled with or housed in the same conduit as controller I/O and power wiring.  4. LonWorks Network Wiring and Addressing Guidelines When the number of controllers on a LonWorks network exceeds 60, the network must be split into segments with not more than 64 controllers or devices per segment using LonWorks Repeaters or Routers.  When counting the controllers and devices on a LonWorks network segment, a LonWorks Network Interface Device and the repeater itself must be included in the device count in each segment. In a LonWorks network containing repeaters or routers, each LonWorks network segment must be properly terminated, as described above. Domain / Subnet / Node addressing is used when configuring the LON controllers. A LonWorks Subnet consists of a series of LonWorks controllers all configured within the same LON Subnet number. A single LonWorks Subnet can have a maximum of 127 device and controller Node addresses.  This Node address count includes the LonWorks Network Interface, all controllers on the subnet, and repeater and/or router node addresses.  An allowance is typically made for additional addresses to be used by LonWorks tools connected to the Subnet.

Issue How to troubleshoot a communication issue with the Sigma interface Is there a log available within the ES that shows the Sigma communication between Sigma controllers and the ES Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Workstation Building Operation Enterprise Server Cause When troubleshooting Sigma issues in an ES it can be helpful to see the communication between the Sigma controller and the Sigma interface in the ES to help identify this issue. The trace log within the ES is available and is configured as described below in the resolution. Resolution The level of logging for Sigma in the Trace Log needs to be increased: Open Workstation and navigate to [ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin. Right-click "nsp.pin.sigma" and choose Properties. Under Level, change from "Information" to "Trace", then click ok. Let it run a few minutes. If there are some user input needed to recreate the Sigma issue, then perform these steps now. e.g. If ifs a graphics issue then run the respective graphic. Retrieve the log by right-clicking [ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log.  Save the log file. A useful tool available on the Community, the Sigma decoder can be used to assist in viewing/debugging the Sigma trace log file information saved in the previous step. Once debugging is complete remember to change log level back to "Information" (reverse of step 3).   Note: If the ES is restarted for any reason whether by manually stopping in the Software Administrator or other, the nsp.pin.sigma will default back to 'Information'.