Building Automation Knowledge Base

Issue The Automation Server is constantly using 100% CPU causing a slow operation Product Line EcoStruxure Building Operation Environment Automation Server Cause Check which process is taking the CPU. Cause 1: The cause was found to be a Function Block Program which was corrupt in some way. When trying to edit, open properties or do anything with this Function Block Program Workstation just hang. The root cause of the problem with the Function Block Program was never found. Cause 2: Some schedules have more than one entry for the same time stamp (likely if the process "CScanner" is taken the CPU) Resolution Solution 1: After deleting the particular Function Block Program (which took over 2 hours) the CPU usage was directly down to 20%. Another solution for an AS with the same symptoms: After downloading a new database to the automation server and then restoring a backup the CPU usage went down to normal levels.  Solution 2: Check all schedules for duplicate entries, especially around the time where the CPU goes to 100%. Also check out the SmartStruxure Quick Help - AS CPU and Memory Loading Quick-Help video on the Exchange.

Issue Does Sigma run on Windows 10? Product Line Satchwell Sigma Environment Sigma Windows 10 Cause Is Sigma 4.08 supported on windows 10? Resolution No version of Sigma is supported on a Windows 10 platform except: Sigma 4.08 can only be installed on Windows 10 when the software is used as a transition into EcoStruxure Building Operation ( EBO ) and used with the correct version of transition component. For full details of Sigma 4.08 versions, build numbers and operating systems supported, see What operating systems is Sigma 4.08 supported to run on?.

Issue How to use L-IP in Vista Classic network. Cannot service pin controllers under L-IP in Vista Classic network. Values in Classic network under multichannel L-IP are showing "Invalid Address" and "No such entity" Product Line TAC Vista Environment TAC Vista Workstation L-IP NIC852 Cause LOYTEC L-IP needs to be configured as a server and into the smart mode in order to be used in the Classic network. NIC852 needs to be used with LOYTEC L-IP in the Classic network. Resolution Configure L-IP as a web server (How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver).   Configure L-IP into Smart mode. There are two ways to configure L-IP into smart mode.  Flip the DIP switch or using a serial cable (RS232). Flip the DIP switch to activate the smart mode. The dip switch is at the side of the L-IP next to the Ethernet port. L-IP DIP switch has seven switches.  By default, DIP switch 3 is down and the rest switches are up. Flip dip switch 2 down to activate the smart mode.   Use RS232 serial cable to activate the smart mode. Read more information in the LOYTEC L-IP User Manual Chapter 4.4.2.2   Configure NIC852 Open LConfig and go to NIC852 tab (Start/All Programs/LOYTEC Network Interface/LConfig). NOTE:  LOYTEC Network Interface package can be downloaded from LOYTEC website, called NIC-LOYTEC Network Interface Software X.X.X Make sure “Enable device” is checked Click on “CNIP Configuration”. Under “Device IP Address” use computer's address and use 1628 as Port number. Under “Conf. Server IP Addr.” Use L-IP’s IP  address and use 1629 as Port number.   Click “OK”. Click on “Test Device”, and should return the serial number   Add LIP as a LTA in Classic network. Right click on the Vista Server and choose “New->Device->Communication Port-LOYTEC” Name the LTA (for example: LIP).   Edit LIP in Classic network. Right Click on the LOYTEC L-IP (in this example the LIP LTA) just added and choose “Properties”. Under Communication Settings, click on the arrow and select the available NIC852.   Commission the LIP in Classic network. Right click on the LOYTEC L-IP just added (in this example the LIP LTA) and choose New > Device > LonWorks Network Name the network (for example: LNS Right click on the LonWorks Network just added (in this example the LNS network) and choose “Commission and Download” Select the LonWorks Network (in this example the LNS network) and click the “Start the Selected Operation” button (up-down arrow button on the top) Click “Continue” when asking for “Continue operation?” Operation successful message should be displayed.   Refresh (F5) the tree in the left panel in TAC Vista Workstation. The L-IP LTA (in this example the LIP LTA) and the LonWorks Network (in this example the LNS network) should turn green afterwards. Now the L-IP is ready to communicate in the TAC Classic network.

Issue How can System Alarms be disabled? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There are over 230 system alarms and at times they need to be turned off temporarily. There is no straight-forward method to gain access to the (intrinsic) system alarms, so an instruction on how to disable them is needed. Resolution You cannot stop system alarms from triggering. But if there are system alarms that trigger often, you might want to "turn these off". The way to do this is to disable the alarms, which would cause the alarms not to trigger again until they are enabled. An alarm has to trigger first in order for it to be disabled. To disable an alarm, right click on the alarm in the alarm list and choose Disable alarm. There is no menu or object to access the system alarms only. For a list of system alarms see What system alarms can occur in StruxureWare Building Operation?

Issue How do I run Continuum Analyzer and get a report Product Line Andover Continuum Environment Continuum 1.7 onwards Cause The Continuum Analyzer is designed to provide installers and troubleshooters with a point of reference for discovering problem areas within their installations.  The software is proactive in that it enables you to 'clean' orphaned and mismatched objects from the database, thereby recovering from a minimal amount of database corruption.  Continuum Analyzer also performs a system information check and provides full reporting on all aspects of the installation, as well as alerts regarding deficiencies. Resolution Always ensure the site database backed up before Continuum Analyzer is used to "Clean" the database. Go to - Start - All Programs - Continuum - Continuum Analyzer Type in User Name and Password (usually andover97 and (not disclosed due to public access)) for the Continuum DB or you can use the system admin user name and password. Click on the version "System Tests", then "Run Wizards" There should be zero failed. Then "Generate Report". To save click on top left disk icon and save as .html file If there are any failures, then ensure the database has been saved before a "Clean" is performed There was a bug in some Analyzer versions that caused a ghost alarm on the AlarmInfo test, also see Continuum Analyzer Failure for Continuum 1.92 & 1.93

Issue When trying to commission a controller into a LonWorks network in SmartStruxure you get a DST error. Product Line EcoStruxure Building Operation Environment WorkStation LonWorks Interface Cause The DST error occurs during the commissioning of the controller when the DST settings are attempted to be downloaded. Resolution TAC Xenta 280 and 300 series Controllers If the DST error occurs when commissioning a Xenta 280 or 300 series controller then check the label on the side of the controller. If there is no /N/P after the model number then it is not a network presentation controller and can not be commissioned in SmartStruxure. For more information see Xenta 280/300 without /N/P designation cannot communicate in a Network.

Issue Xenta Controllers can report "offline" status if they encounter bandwidth limitations Completion Event Failure warnings CRC Errors showing in controller properties Loytec Multi-port router/switch channel LED blinking fast red (traffic overload) Product Line TAC Vista Environment Lon Networks Vista Xenta LPA Loytec Protocol Analyzer Cause HMI Vista on-line/off-line presentation is based upon receipt of the heartbeat messages. Every TAC Xenta 280/300/401 controller is periodically sending a message to the other members of its TAC Xenta reporting (including the group master) that it is on-line. Proprietary "LACNet-IAm" and "LACNet-GroupIs" are sent every 15 seconds to HMI Vista. Without the HMI receiving these heartbeats, Vista will display the controller or group in an offline state. The TAC Xenta group is specified by the tag_0 and the TAC Group is specified by tag_1 bindings in LonMaker or NL220. Resolution Actions for reducing Bandwidth: TAC Xenta 100s Slow down the SendHeartBeat Check sensors etc that are affecting all bound nvo's Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. 3rd Party LonWorks devices Change update rates for nvo's. If possible, the product manual should show how. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. TAC Xenta 280/300/401 TACNV and SNVTs Verify delta and period values make sense for the particular signal and application. Decrease traffic of SNVT group bindings. For large groups of bound controllers, use UNACKD/RPT instead of ACK service type. Increase the trend log time span (the total log time) if possible. Of course, this will increase the memory usage in the Xenta, but this will make TAC Vista to do the fetch more seldom and result in reduced traffic. TAC Xenta 280/300/401 + TAC Xenta I/O Modules If sensitive sensors (i.e. pressure sensors) are connected to I/O Modules, a high load of communication will be generated. Bandwidth issues may arise when 401s with many I/O Modules are each reading multiple sensitive sensors. Increase the Min Send Time for every I/O Module. Min Send Time is how often the I/O module is allowed to communicate with the TAC Xenta. This setting is located in Device Specification in Menta. Reduce Trend Log definitions in the controllers. If possible, try to have all your "high speed sensors" connected to one, or a few I/O modules, so it's only a few I/O modules sending a lot to the Xenta. LonWorks routers Implement L-Switch routers to reduce traffic on high bandwidth segments. Set router to Configured Mode, not Repeater Mode. Vista Server Trend Log Stagger Vista server Trend Log start times so that they do not all attempt to get fetched at once. See also Troubleshooting LON Network Communication More information can be found in Tool for LON / LPA Capture Traffic Analysis (login required) which discusses the LPA Analyzer Tool. This may be useful for interpreting the LP file data.

Issue To assist locating data sheets if you do not have access to The Exchange or other Schneider Electric storage areas Product Line Satchwell MicroNet Environment MicroNet 50 series Controllers Micronet Touchscreens Micronet LCD SLink sensor Cause To assist customers that do not have access to our internet or partner websites. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Links below to download: MLi and data sheets for MicroNet LCD Displays MLi and data sheets for MicroNet Touch Screens User Guide for MicroNet Touch Screen User Guide MLi and data sheets for S-Link Sensors Data sheets for MN 50 Series MicroNet Manager Interfaces Mli for MN Trunking kits (MN-TK) MLi for MN Wall Mounting Kits (MN-DK) MLis for Plug-In Cards MLi and data sheets for Satchwell MicroNet MN350 Controllers MLi and data sheets for Satchwell MicroNet MN450 Controllers MLi and data sheets for Satchwell MicroNet MN550 Controllers MLi and data sheets for Satchwell MicroNet MN650 Controllers Download all of the above (file size 12.0 MB) Data sheets for MicroNet 100 series controllers ETC can be downloaded from MicroNet 100 series controller MLi's and Data sheets.

Issue LMTOOLS was not installed on the computer that Vista 5.1.8 was installed on. Product Line TAC Vista Environment Vista LMTOOLS LMAdmin Cause The TAC Vista license administrator tool has been upgraded to LMAdmin, a web based license administration tool accessible using a web browser. Existing license files are compatible with the new LMAdmin tool that is included in the TAC Vista Server and TAC License installers. Resolution If the license server is not running as a service, Vista is unable to locate the license, or you need general troubleshooting help then see License troubleshooting in Vista 5.1.8 or greater. Flexnet License Admin   The default license file folder has changed with the new LMAdmin license tool. The new default license file folder is "C:\Program Files\Schneider Electric\License Server\taclic\licenses\". For 64-bit OS the default license path is "C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses\". The license server administration, LMAdmin, is installed as a web server and is accessible at http://localhost:8080 after the installation; a shortcut will also be placed in the start menu. The location of this shortcut can be found by going to Start > All Programs > Schneider Electric > TAC Tools 5.X.X > FlexNet License Admin. To check what your license file contains, how many seats are available for each program, and how many are in use click on the Concurrent icon.   To log into LMAdmin, click on Administration in the top right corner. The default login and password is admin/admin and it is recommended that this is changed after the installation is finished. User accounts can be managed in the Administration area, under the User Configuration tab. Click the New icon at the top of the window to add users. The edit button at the end of the row of each user will allow the user name and password to be changed. There is also a delete button to remove unwanted users. If the computer running the TAC Vista License server enters a power save mode, the license server may have to be restarted manually in Computer Management > Services and Applications > Services.   TAC License Setup It is recommended to use the "License Setup tool" in the start menu instead of the license popup dialog when specifying a license server name or license file location. The License Setup tool can be found here; Start > All Programs > Schneider Electric > TAC Vista Server 5.X.X. Note: When upgrading Vista from a version 5.1.7 or older to a newer version, the old license file path may still exist in the registry. This will not impact the license server in any way. The old path can be removed if you desire through the TAC License Setup. During the installation of TAC Vista Server and TAC License, any license files located in the old license file folder are automatically copied to the new license file location; the original files are not removed.

Issue The Save to Flash exclamation point (bang) shows on a Controller object. Hovering over the icon, a tooltip comes up indicating that the controller 'requires flash backup'. However when performing a backup to flash, a result comes back that the 'controller doesn't need flash backup' and the exclamation icon remains. Re-loading the controller and performing a send to database have no effect. Product Line Andover Continuum Environment Continuum Controllers Cause The ObjectStatus attribute of the controller, or an object in the controller, may be fixed on and falsely reporting a save to flash is required when one is not. Resolution Toggle the ObjectStatus attribute by forcing it to a value of zero: In Continuum Explorer, find the controllers that have bangs on them Browse in these controllers and see if there are any objects with bangs on them. Run a Default Class Listview on those objects that show bangs In the listview, select the object(s) that are affected, right-click and SetAttribute for the ObjectStatus attribute to 0. This will reset the bang until it gets set when the flash again needs to be updated.. Also, refer to Save to Flash yellow exclamation point remains after valid save to flash.

Issue Need to prevent passback in a Continuum access control system. Product Line Andover Continuum Environment Continuum Access Control Cause Access control users may try to "passback" their card in order to have another user enter an area. Resolution The way that anti-passback works in Continuum is that all the Door's entering into an Area that require the feature need to be setup for anti-passback. This then means that any one granted access at any of the Door's is then denied access at the other Door's into that same Area until they have badged out. There are two variations on the anti-passback implementation: Strict anti-passback. This restricts the same card from being used to enter the same Area until that Personnel badges out into an exit Area. It also ensures that the person's current area is adjacent to the area he/she is trying to access so if the system has the person's current area as OUTSIDE and the person tailgates into the premises and then badges at an internal door she will be denied access due to anti-passback violation. Relaxed anti-passback. This also restricts the same card from being used to enter the same Area but will allow access if the Personnel is in any different Area. As long as the Personnel is not currently in the Area they want to enter then they will be allowed in. (See Anti-passback enforcement on area re-entry only)   How to setup To setup anti-passback you will need to have at least two Areas created. One you want to restrict access to and another where they will be coming from. Next, you will need to configure the Door objects entering these Areas for both Entry and Exit. Make sure to define both of these Areas otherwise the anti-passback options will not be selectable. (See Anti-Passback Protection option is not available) Then go to the Entry Options and/or Exit Options tabs and tick "Anti-Passback Protection". This will provide strict anti-passback unless relaxed is enable by the next step. You can enable relaxed anti-passback by ticking the "Allow Entry on an Anti-Passback Violation" option. There is also an option for timed anti-passback, which if ticked, allows access on anti-passback after the "Timed Anti-Passback" time has lapsed.   Possible Solutions When Exit Readers Not Available You do need to have exit readers as well as entry readers to be able to configure and use anti-passback. To restrict access to an Area we need to know the current Area that each Personnel is in, we can only do this with Exit readers. This may not mean having to install exit readers at every entry reader though, there a couple of possibilities. First though, you will need to setup dummy exit readers in the Door objects you want to have anti-passback enabled. This will allow you to access the anti-passback function. The main problem will be that after entering the Area successfully, that same user will not be able to enter again unless they are shown to have exited that Area. There a number of possibilities on how to provide this: Install a single "badge out" reader at the exits for Personnel to badge out before exiting through free egress doors. This reader will be tied to a Door object with an exit area attached. Timed anti-passback could be used with a large enough window to deter tail-gating but still allow the cardholder to exit then enter again normally throughout the day. Could use the "allow access on anti-passback violation" option to monitor (and potentially trigger an alarm at the entry point) to note the violation for latter analysis but still allow the Personnel through.

Issue What are the typical steps to install and configure Vista OPC Server? Product Line TAC Vista Environment Vista 5.1.x Vista OPC Server 1.6.1 Cause OPC Server can be used in many integration situations to provide data to other parties or bring third party data into the Vista front end. Resolution  Install TAC Vista OPC Server 1.6.1 installation package Add a Windows Account for Vista OPC Server Start Computer Management In System Tools\Local Users and Groups\Users click New User Name the user OPC_Communication Provide a password Uncheck the User must change password at next logon checkbox Check User cannot change password checkbox Check Password never expires checkbox Click Create and Close. Add user to the Administrators group Configure Service In Services right click on TAC Vista OPC Server and click properties Ensure Startup type is Manual On Log On tab select This Account Browse to the local account OPC_Communication Provide the password in the Password and Confirm password fields Click OK Configuring DCOM Start Component Services Double click Component Services\Computers\My Computer\DCOM Config Locate the COM Server TAC Object Server OPC DA Services and select properties Click the Identity tab Select This User Select the local account OPC_Communication Provide the password in the Password and Confirm password fields Click OK Locate the COM Server TAC Object Server OPC AE Services and select properties Click the Identity tab Select This User Select the local account OPC_Communication Provide the password in the Password and Confirm password fields. Click OK Create a Vista User Account Start Vista Server Start Vista Workstation and Log In In the root TAC Vista folder create a new account (User - Vista or User - Windows Domain Group) Name the user TACOPC Modify the properties of the account Set the password Set an authority level that OPC Clients should use when accessing the OPC Server Set the Logout time to zero(0) Configure the Vista OPC Server Login Open TAC Vista OPC Server Setup (Program Files\Schneider Electric\TAC Vista OPC Server\Vista OPC Server Setup) Ensure the Retry connect period is 360 seconds. In the logon to TAC Vista Server click Login using the following Vista Account In the Username type TACOPC Type the password Click OK Confirm the change took place, if it is not refer to OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup. Configuring Windows Firewall If Vista Server and OPC Server are on the same computer then no firewall exceptions are required. Consult the OPC Server manual (Chapter 4) for the firewall exceptions if using a separated OPC Server and Vista Server setup. Configuring OPC Client DCOM Settings If the OPC Client is on another computer then create a user account to match the one used by Vista OPC Server. Start Computer Management In System Tools\Local Users and Groups\Users click New User Name the user OPC_Communication Provide a password Uncheck the User must change password at next logon checkbox Check User cannot change password checkbox Check Password never expires checkbox Check Create and Close Configure Access Permissions Start Component Services on the Vista OPC Server computer under Administrative Tools In the Tree Structure right click on Component Services\Computers\My Computer and click properties Click the COM Security tab In Access Permissions click Edit Limits Click Add Select the local account OPC_Communication (EXAMPLE: W7USCNU1342VXXX\OPC_Communication) In the allow column select Local Access and Remote Access Click OK In Access Permissions click Edit Default Click Add Select the local account OPC_Communication In the allow column select Local Access and Remote Access Click OK In Launch and Activation Permissions click Edit Limits Click Add Select the local account OPC_Communication In the allow column select Local Launch, Remote Launch, Local Activation, and Remote Activation Click OK In Launch and Activation Permissions click Edit Default Click Add Select the local account OPC_Communication In the allow column select Local Launch, Remote Launch, Local Activation, and Remote Activation Click OK Configure Local Security Policy Select the Local Policies\Security Options\Network Access: Sharing and security model for local accounts policy Set the policy to Classic - local user authenticate as themselves Click OK Repeat these steps for the OPC Client computer Configuring OPCEnum Start Component Services on the Vista OPC Server computer In the tree structure Component Services\Computers\My Computer\DCOM Config right click on OPCEnum and click properties On the general tab change Authentication Level to Default Ensure Run Application on this computer is checked on location tab Click the Identity tab Select This User Browse to the local account OPC_Communication Provide the password in the Password and Confirm password field Click OK Repeat these steps on the OPC Client computer Start the TAC Vista OPC Server In Services right click on TAC Vista OPC Server and click start For more OPC Server issues please see Vista OPC Server Installation and Known Issues. A good overview of  OPC integration and the necessary COM and DCOM settings is located here.

Issue The upgrade fails, and you may get the following error message: Warning Error: Could not create remote directory. Product Line TAC Vista Environment TAC Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause To upgrade the Xenta Server system software to version 5.1.3 and later, Xenta Server HW 2.0 or later is required (otherwise the upgrade will fail). All Xenta 700 have HW 2.0 or later. In some cases the file system of the Xenta Server can be corrupt, which prevents the upgrade software to connect to the device.   Resolution First of all, try to do the upgrade a second time. If the upgrade still fails, please do the following: Check if you can ping the device and that port 80 or 443 aren't blocked. If the above is ok, format the device from the console by typing "format". (Warning: All data will be lost!) Install the system software again. If it still fails, replace the Xenta Server. Please note that If the Xenta Server is HW 1.1 or earlier you can only upgrade to version 5.1.2 or earlier. If you have to upgrade to 5.1.3 or above you need to replace the Xenta Server to a unit that has HW 2.X. (See also Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller)

Issue It is not clear how to register a SmartStruxure system, and what information to write in case it's not a customer site (For example a test bench/controller or engineering PC). Product Line EcoStruxure Building Operation Environment S2Connect Workstation Cause Guidelines are needed regarding how to properly register a system. Resolution Starting in SmartStruxure 1.5, we have introduced a registration process to know more about SmartStruxure systems. In order to know our customer and/or partner better and provide better services we should register our SmartStruxure system with correct information. The SmartStruxure registration process requires a Buildings Exchange account. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Please make sure below points while registering SmartStruxure system. Test site: If you are registering a test site to test registration process, write "[Test]" keyword in Site note*. Demo site: If you are registering a site which is for demo, then write "[Demo]" keyword in Site note. Training site: If you are registering a site for training or you want to explore registration process, then write "[Training]" keyword in Site note Customer site: if you are installing an actual site for customer then DO NOT use above keywords in Site note field *Site note field can be found under Site Administrator tab (Shown below in screen shots) New system registration: If you are registering new system then you continue enter all information in Step 1 and continue to Step 2. In Step 2 you will find a Site note field. Fill the Site note field as explained above.  Already registered system: If you have registered your site without providing above explained details then you can browse to below website https://registration.smartstruxure.schneider-electric.com After successful login; Navigate to Systems -> Site Administrator and click on Edit button, now you can edit Site note field. Registration Process Does Not Complete In some cases after registering either the Enterprise or Automation server, it still prompts you to register when you log back in. There are two different procedures that can be taken to correct this issue. Procedure 1 - By editing the registration and clicking submit again, it can help the system complete the registration. Log into the sever again and either click Register now on the initial prompt or go to Help > Registration once you are in Workstation. Log into the Registration Portal. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Select the server that is experiencing the issue on the right side of the window. Click Edit. Click Submit. Procedure 2 - If procedure 1 still does not work, then the registration can be completed manually by entering the Registration code in the offline mode. Log in to the Registration portal directly through this link (registration.smartstruxure.schneider-electric.com). Select the server on the right hand side of the screen that has the registration issue. Take note of the Registration code. Insure that the Enterprise or Automation server does not have internet access and log into the server with Workstation (In the case of an Automation server you will need to connect directly to it via Ethernet). Click to Register now (Since the server does not have internet access, it will automatically launch the offline registration). Insert the Registration code the three fields provided and click Register now. Also check out the SmartStruxure Solution Connect (S2C) - SmartStruxure Product Registration Registration Quick-help video on the Exchange.

Issue How to send an event based alarm to one or multiple email addresses using an MPM Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager MPM-VA MPM-UN MPM-GW Cause Emails can only be sent using a Lua script Resolution To send e-mails to alert a list of recipients when a pre-defined condition is met, you need to create a Lua Program object (PG1 for example) on your monitor MPM. Copy and paste the attached Email_Alert_AN015 script in the Loop section of the program object and activate it by pressing the green Play button. Don’t forget to save both the object and the database when you are done. You will need to modify this script to represent your own event, including the server information, the list of recipients and the content of the message sent. The monitored variable and the limit conditions can be modified directly from the Event object in Building Expert. In the above example, room temperature is 23 which means that the "Event State" is 0. An email alert will be sent out when the temperature exceeds the high limit (Event State = 3) or when the temperature goes below the low limit (Event State = 4) defined by the event.   Tip 1 Only a Manager connected via Ethernet has the ability to send emails. For a network composed of a daisy chain (CANbus) or a wireless mesh (ZigBee mesh), the Lua program that manages e-mail alerts for all the nodes on the network must reside on the monitor node. The variables in the Lua program will be obtained from any remote node on the network, and the email sent by the monitor if a condition is met. To get an object from a remote node, refer to Display values/objects from a remote MPM on dashboard of the monitor MPM Tip 2 Should you have issues sending emails with the above script, verify that the User and Password defined in the script are accurate and up to date and that all server information is accurate. Also ensure that the Ethernet configuration (ETH1 object) of your SmartStruxure™ Lite Manager is accurate and represents the current settings of your network. Pay special attention to the DNS and Gateway settings. Your monitor Manager will be able to operate on a local network even if these settings are not accurate, but will not be able to access the Internet, which is required to send emails. Tip 3 When using Google’s server mentioned below, it is important to use the following information Google* Server aspmx.l.google.com Domain google.com Port 25** Sender *** Recipient   Username (Not Required)**** Password (Not Required) *Google can only be used to send emails internally from Gmail to Gmail **When port 25 is used, emails are stored in the spam folder ***Bracket < > are not to be discarded, otherwise syntax error 5.5.2 appears ***Note that the user authentication is not required for the google server and if included, will be rejected. Tip 4 The AOL’s server mentioned below can be used to send emails from an AOL account to any other email and does not send the emails to the spam folder AOL Server Smtp.aol.com Domain Aol.com Port 25 or 587 Sender email@AOL.com Recipient Your_email@AOL.com Username (Required) email@AOL.com     (or any other email) Password (Required) Your password   Tip 5 Email server using Port 25 and not requiring authentication, sendUser and SendPassword lines needed to be deleted from Variables section

Issue After updating the computers Java version to Java 7 update 51, graphics are not displayed when using Webstation. Then a security warning is displayed. Missing required Permissions manifest attribute in main jar: http://xxx.xxx.xxx.xxx:/com.SE.webstation.Main/applet/applet-1.4.1.68.jar If you don't see the error above, but just get a blank window, please refer to Webstation graphics not working after updating to Java 7 Update 65. Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC Vista Environment Webstation Cause From Java 7 Update 51 and onwards, Java has enhanced the security model to make user system less vulnerable to the external exploits. The new version of Java does not allow users to run the applications that are not signed (Unsigned), Self signed (not signed by trusted authority) and the applications that are missing permission attributes. Risks involved in running each kind of applications: Unsigned applications An application without a certificate (i.e. unsigned apps), or missing application Name and Publisher information are blocked by default. Running this kind of application is potentially unsafe and present higher level of risk. Self signed application (Certificate not from trusted authority) An application with self-signed certificate is blocked by default. Applications of this type present the highest level of risk because publisher is not identified and the application may be granted access to personal data on your computer. Jar file missing Permission Attribute Permissions Attribute verifies that the application requests the permission level that developer specified. If this attribute is not present, it might be possible for an attacker to exploit a user by re-deploying an application that is signed with original certificate and running the application at a different privilege level. Resolution As a workaround, the user can use Exception Site list feature to run the applications blocked by security settings. By adding the URL of the blocked application to the Exception Site list allows it to run with some warnings. Steps to Add URL to the Exception Site list: In control panel go to the Java Control Panel Click on the Security tab Click on the Edit Site List button Enter your site details (This example http://www.SBO-Site.com) Click the Add in the Exception Site List window. Select continue Repeat the process until all the sites AS/ES have been added. Then select OK to complete and OK on the next window to exit the Java control panel. Next time you use Webstation to access the AS/ES you will be asked if you want to run the application. Tick the box so this is not displayed again. Then select Run. The graphics should now be displayed. You will need to repeat this process on any computer you which to use Webstation on.

Issue The default dynamic port range for TCP/IP has been changed with Windows Vista and later Microsoft operating systems. Product Line Field Devices, Satchwell Sigma Environment Microsoft Windows Vista Microsoft Windows 7 Microsoft Winsow 8/8.1 Microsoft Windows Server 2008 Ethernet communications Microsoft Windows 10 and server 2012, when Sigma is part of an SBO/EBO front end system. Cause To comply with Internet Assigned Numbers Authority (IANA) recommendations, Microsoft has increased the dynamic client port range for outgoing connections in Windows Vista, Windows 7 and in Windows Server 2008. The new default port range starting at port 49152 through to port 65535. This is a change from the earlier Windows configuration that used a default port range of 1025 through to 5000. Sigma used port 49152 as default for communications between Sigma server and Sigma controllers. Resolution You can use SE Legacy Port Reservation to reserve the port used by Sigma. Another resolution would be to redefine the dynamic port range Windows Server 2008 can use to 50000 to 65535, hence keeping the port free for Sigma. (Sigma port requirements can be found in What port numbers are used by the Sigma system?). You can view the dynamic port range on a computer that is running Windows Vista, Windows 7, Windows Server 2008 or 2012 by using the following netsh commands: netsh int ipv4 show dynamicport tcp netsh int ipv4 show dynamicport udp netsh int ipv6 show dynamicport tcp netsh int ipv6 show dynamicport udp Note The range is set separately for each transport and for each version of IP. The port range is now truly a range with a starting point and with an endpoint. Microsoft customers who deploy servers that are running Windows Server 2008 or 2012 may have problems with RPC communication between servers if firewalls are used on the internal network. In these cases, we recommend that you reconfigure the firewalls to allow for traffic between servers in the dynamic port range of 49152 through 65535. This range is in addition to well-known ports that are used by services and by applications. Or, the port range that is used by the servers can be modified on each server. You adjust this range by using the netsh command, as follows: netsh int set dynamic start=number num=range This command sets the dynamic port range for TCP. The start port is number, and the total number of ports is range. The following are sample commands: netsh int ipv4 set dynamicport tcp start=10000 num=1000 netsh int ipv4 set dynamicport udp start=10000 num=1000 netsh int ipv6 set dynamicport tcp start=10000 num=1000 netsh int ipv6 set dynamicport udp start=10000 num=1000 These sample commands set the dynamic port range to start at port 10000 and to end at port 10999 (1000 ports). The minimum range of ports that can be set is 255. The minimum starting port that can be set is 1025. The maximum end port (based on the range being configured) cannot exceed 65535. To duplicate the default behavior of Windows Server 2003, use 1025 as the start port, and then use 3976 as the range for both TCP and UDP. This results in a start port of 1025 and an end port of 5000. Note When you install Microsoft Exchange Server 2007 on a Windows Server 2008-based computer, the default port range is 1025 through 60000. Click here to be linked to the Microsoft Knowledge Base Article Number 929851.

Issue Where to begin troubleshooting Ethernet (TCP/IP) communication problems with a NPR Product Line TAC INET Environment I/NET NetPlus Router (NPR) Model Series 2000 Cause Possible Causes: Ethernet Communication is down Ethernet Port is closed Device is configured incorrectly Device failure Resolution Gather detailed information about exactly what is happening Ethernet Communication is down Using the command prompt ping the devices IP and trace its route. "ping xxx.xxx.xxx.xxx" and "tracert xxx.xxx.xxx.xxx" Watch to see if the Domain server prints out the correct Host name. If the device is shows as offline there may be an error with Firewall settings or Ethernet communication at the Host Workstation Disconnect the Ethernet cable from the Device and plug it into a laptop. See if you are on the network. Ethernet Port Is closed If the above process shows that Ethernet communication between the Workstation and Router is valid, you may have port closed. Use a crossover cable to connect a laptop to the device and see if you can connect to a controller ON THAT LINK in I/NET. Look for live values in Controller Summary. If you are able to do this, and you are able to show that Ethernet communication between the 2 devices is working then you most likely have a firewall that is block the UDP port 50069 Contact the building IT department to assist in rectifying this problem. Device is configured incorrectly If, in the above process, you were unable to connect to I/NET while direct connected to the Router via an Ethernet crossover cable, the device may be configured incorrectly Open the active I/NET configuration Profile Ensure that TCP/IP is enabled Add the Router’s IP address to the Reference Host Table Restart the I/O server Check communication Alternatively you can connect to the router via I/NET Direct Connect configuration profile. Refer to Troubleshoot an NPR problem with Windows Telnet utility on how to do this and check that the IP Address and details are set correctly. Communication should be restored. Device failure Try to reset the NPR: Remove the NPR cover. Depress the center tab of the I/DISC slot and hold it down. Next press the reset button on the front of the unit and hold for 10 seconds. Release the reset button and then release the center tab. Two LEDs should display steadily. Next depress the center tab and hold it down. Press the reset button on the front of the unit and hold for 10 seconds. Release the center tab and reset button simultaneously. The LEDs should display steadily. The NPR unit should now be ready for a software restore. Download and install the latest system file for the NPR. Configure the I/NET communication in your active Configuration Profile. If you not able to successfully update the firmware in the NPR then it is likely that the device is faulty and may require repair or replacement.  The current replacement for the Series 2000 NPR is the Xenta 527-NPR. Other Troubleshooting Steps See if the communication error shows up on multiple computers and if possible multiple locations. There may be an error with Firewall settings or Ethernet communication that only effects part of a large system Host Workstation Use a different Ethernet port to connect the NPR or workstation too. Direct connect to a controller on the controller LAN via TAP and see if any stations are offline. It is theoretically possible that some form of electrical failure on the controller LAN has caused the NPR to appear offline. If you are unable to see the entire controller LAN from anyone one device, you should troubleshoot Controller LAN communication. Contact Product Support with your findings.

Issue What Techniques can be used to troubleshoot Modbus TCP/IP X Driver? Product Line Andover Continuum Environment Continuum Modbus TCP/IP X Driver Cause Advice/ tips required to help isolate & determine Modbus IP communications problems. Resolution The first thing to check is that you are using the latest release of the driver and manual, also that it is the correct one for the controller model you are using, currently V2.00002 for the 1st Generation controllers (e.g. Netcontroller CX9900 etc) and V2.00018 for the 2nd Generation controllers (e.g. Netcontroller II and bCX1). Download Modbus TCP/IP xDriver. Ensure you are using only 1 XDriver for all your Modbus IP comms, if say you are using Comm1 as your X Driver enabled port then all of the Modbus IP points must be under Comm1, you cannot have 2 X Driver ports loaded with this X Driver (See Can multiple Modbus TCP/IP XDrivers be installed on a single 2nd Generation NetController?). The following points should be checked with reference to the Modbus TCP/IP X Driver Manual downloaded with the software: Set the X Driver accordingly for Client or Server mode (Client mode and will be polling the 3rd party devices, server mode responds to requests for data). Check that your Configuration point has been setup correctly as a Infinity String and the parameters are correct for the mode you are using. For Client mode check that Param 1 is set to a polling rate that the 3rd party devices can cope with also that Param 3 is long enough for the devices to respond between 20 and 60 seconds. Use Parameter 4 to enable the error logging in an appropriate date format, this will then put the errors into the String array behind this point, ensure you have set the log size to say 50, automatic log and the interval to be 0 (a semi automatic log See How to log data only when a point changes). This will then log the error in the string each time they occur, you can view these errors with a function that loops for the log size printing out each line to the Message Window, or put a number of lines of the error log array lines on a graphic as lines of text. Create a Remote Device Status point to monitor the state of the remotely connected Modbus IP servers, again this can be put on a graphic to show which devices are on/offline. By selectively disabling or removing some of the X Driver points you can limit the polling to certain devices, that way each device can be tested in turn. Another tool that can help debugging Modbus IP comms is Wireshark as it allows you to monitor the IP comms between the Client and the Servers. Check the correct addressing and function codes are used in the polls and that the servers are responding correctly. As per the Compatibility Matrix check that your NCII has a compatible firmware loaded for the Cyberstation software used (2.0x or 2.1x) In Client Mode, ensure the 3rd party system does not poll the driver too fast, see Typical data throughput rates for Modbus XDrivers. Ensure the Xdriver Objects (usually Numerics) have correct details within the Parameter Fields. An incorrectly formatted IP address can cause the Controller to Cold Start following a download. The quickest way to check the Parameters is to load the Controllers with all the objects apart from the Xdriver Configuration String, then create a listview with parameters 1 to 6.  

Issue Remove the Routing tables from I/NET and Xenta 527 devices Host conflict or station conflict error messages displayed at the I/NET Host. Incorrect Links, Hosts and IP addresses that do not exist in your Network are shown when penetrating Network Configuration. Product Line Other, TAC INET, TAC Vista Environment I/NET IP Routers Xenta 527 Cause Host or station conflict errors can be caused by old information stored in a routing table. From time to time, it may be necessary to purge that information and allow the tables to be rebuilt automatically. The only way that routing tables can become corrupted is if a laptop was used to connect to the system from a different Network or from the Outside. Once connected, its IP table is broadcasted to the other devices like PCs and NPRs, thus populating the table with entries that does not belong or is non-existent for this location or system.  Resolution Managing I/NET Routing Tables   I/NET Host Workstation View the I/NET Routing Table See Viewing the routing tables on a PC using I/NET Seven for complete instructions. Delete a Single entry in the I/NET Routing Table Go to Start > Run Type Telnet and hit Enter Type open, hit the space bar, then enter the IP address of the PC Press Enter When the login comes up, type csi, hit enter Type LA  and hit enter to list all routing table entries Type ipdel xxx.xxx.xxx.xxx with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table Shutdown the I/O Server Open Windows Explorer Browse to C:\INET Seven Data (or C:\Program Files\INET Seven) Delete the .dat files (you may want to save a backup to another location) Delete the routing table from any device listed as a Reference Host or the table will repopulate Start I/NET Other Method: See Bogus Links, Hosts and IP's in Netcon for instructions on using the delall command in Telnet     Xenta 527-NPR; Xenta 913; Xenta 527 Web Server (See Clear the IP routing tables of a Xenta 913)  Viewing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ip” Press enter Deleting a Single entry in the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet ipdel” then the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table View Connecting a serial cable to a Xenta 5/7/9xx controller to configure HyperTerminal to communicate to the Xenta Device. Log into the Xenta Device as the root user At the dsh/> type “inet delall” Press enter Type “inethost” and press enter Verify or set the Reference Hosts Clear the routing table from any referenced device to ensure old data is not repopulated Restart the Controller to re-populate the routing table   You can also realize this through the web page of Xenta device. Open the web page of Xenta controller, browse to Utilities-I/NET-I/NET Command Line, and type the command below or above. The result is the same as using HyperTerminal, which is also an easier way. Typing “inet help” or “inet” gives every I/NET option within the controller inet - I/NET Help ip - Display IP table list ls - Display Link/Station table list cp - Display Compressed table list gp - Display Global Point table list mm - Message masking all - Display all lists ipadd - Add an IP address to the tables ipdel - Delete a single ip record delall - Delete all ip records   NPR-2000 Viewing the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Deleting a Single entry in the I/NET Routing Table Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the NPR Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “ipdel xxx.xxx.xxx.xxx” with xxx.xxx.xxx.xxx being the IP address of the device you wish to delete Press enter Clearing the I/NET Routing Table (See Bogus Links, Hosts and IP's in Netcon)  Go to Start>Run then type “Telnet” and hit Enter Type open hit the space bar then enter the IP address of the PC Press Enter When the login comes up, type csi hit enter Type “LA”  and hit enter to list all routing table entries Type “delall” and hit enter to clear the table   Appendix A: I/NET Telnet Commands Glossary: Help – Displays all available commands in the NPR or I/O Server.  Note there are some differences between the NPR and I/O Server. ipadd a.b.c.d – Adds the IP to the routing tables. ipdel a.b.c.d – Deletes the IP from the routing tables. gpadd LLSSPPBBTT XX | a.b.c.d – Adds a global point link or global point IP to the routing tables. delall – Deletes “all” local routing table entries. setpass password – Change the telnet login password (6 characters max). +cpdel LLLL SS – Deletes the specified link/site address from the CP table. +debug gp on|off – Turns global point debugging on or off. +reboot – Reboots the NPR. +wdog – Reports watchdog errors. +wdogrst – Clears the watchdog errors. +Dx – Toggle debug output to COM3.  x=0/1; 0 = off, 1=on.   List Commands: +LR – IP Stack routing table. LI – IP routing table. LM – IP routing masks. LL – Link/Station routing table. LG – Global point routing table. +LC – Compressed routing table. +LS # - Compressed routing table: station to site maps for the specified link #. LA – All routing tables. LU – System metrics. *LD – Dial maps.  + = NPR only * = Host PC only   Appendix B: Method for Clearing Routing Tables at a Large Site See Possible solution to doing a Telnet session with a system wide firewall setup.   Appendix C: Suggested Reference Host Settings   Click here to be linked to the TAC INET Seven Getting Started. Click here to be linked to the TAC INET Seven Operator Guide.   A Reference Host is any TAC I/NET workstation, NPR, or Xenta 527/527-NPR that will serve as a source of IP addresses. Any of these devices attached to an Ethernet LAN can be used as a Reference Host. Each time I/O Server is started on a workstation, it provides the workstation’s IP address to each remote host designated as a Reference Host. I/O Server also requests and receives a list of all host IP addresses that are known to the remote host at that time. I/O Server must be running on the remote host for this address exchange to occur. I/O Server compiles and maintains a list of all the remote hosts that it learns about. Ultimately, all hosts in the network will know the IP addresses of all the other hosts. Ideally, you should determine 1 or at most 2 devices to serve as your Reference Host.  This device would ideally be a Xenta Server or an NPR, but a Host workstation that has I/O Server running 100% of the time will work as well.  All devices on the system will use this as a single Reference Host. No others are needed.  When the device comes online it will contact the Reference Host and get the site’s Routing Table.  The Reference Host can have an empty routing table.  Once the Routing Table is shared, Reference Hosts are no longer needed.  You can leave the single entry in place. This will allow a quick recover, in the event of a critical system failure. Here are a few reasons for using multiple Reference Hosts: Temporarily add a new device as a Reference Host on the Sites Reference Host or a workstation to aid in bringing it online A large site may desire to have 2 Reference Hosts in case one is offline when a device comes online. An I/NET site that spans multiple locations may wish to declare a local Reference Host for each building and a network Reference Host