Issue What is the proper way to enter data in ID Works and print a badge? Product Line OTHER, TAC INET Environment ID Works I/NET Seven Cause Enter data properly to avoid losing data or having to redo personnel entry. Resolution Log into the ID Works Program Default user name is lowercase admin Default password is lowercase admin Choose the badge project for the card you are going to print. If you do not see the Project in the window area, select the "More Projects" button to see the complete list of projects. Once you choose the project, a window will pop up for you to log into the ID Works Project. You have a choice on how to log in. You can either choose to check the box next to "Use Trusted Connection" or under the "INetThirdParty" Login ID the password is lower case passinetdb3p. Typically, select the “Trusted Connection” option. This is a view of the Sample project that is on the I/NET Seven CD under the "Support" file folder on the CD. Next fill in all the information listed on the Production Form including taking the photo. Now that you have filled in all the info and took the picture, it is time to print the badge. On the Bottom ICON Task Bar, the second ICON in going from left to right is the "Print ICON." Before you actually print the badge, make sure the Blank cards that are in the printer magazine are the correct ones. Once you verify that the correct blanks are in the printer, and then depress the Printer ICON with the mouse. Printing the badge will also save the information in the I/NET Seven system and the ID Works system. There is NO need to save the info first, and then print the badge. Now that you still have the information in the Production Form on the Screen, DO NOT choose the RED X on the Top ICON Task Bar to clear the page. If by accident you do choose the RED X, you will get the following pop up window. DO NOT CHOOSE the YES BUTTON, if you do, you WILL DELETE ALL THE INFORMATION AND PHOTO you just entered in the I/NET Seven System and the ID Works system. If you find yourself in this situation, you NEED TO CHOOSE the NO BUTTON, doing this choice WILL NOT DESTROY ANY DATA. In order to refresh the project, go to the Top Task Bar and choose the "FILE" option. In the drop down list choose the "Close Project" option. Then select a new Project for the next badge, this process will open a new clean Production Form to fill out.

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue Unable to rehost license. Gets "Only deployed entitlement line item can be fulfilled" error message. Environment Vista SmartStruxure Vista FM Cause Rehost or changes in configuration of licenses are impossible.  Resolution This message is given because the licenses are made obsolete. For more details about the status of your licenses, please contact your local Orders Department.

Issue Replacement Satchwell pneumatic parts not available or obsolete and other pneumatic control brands e.g. Barber Colman used in the UK marketplace. Product Line Field Devices, Other Environment Pneumatics Part Number examples: 541, T100, 2212 Cause Replacement parts required. Resolution Contact OEM Comfort Telephone: +44 (0) 208-344 8777 Website: http://www.secureseal.com/ Email: lewin@secureseal.com

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue V-Box fails to install network interface/Virtual Adapter during Project Configuration Tool Installation. Product Line EcoStruxure Building Operation Other Environment OracleVM VirtualBox (all versions) Project Configuration Tool (all versions) Cause Some security or anti-virus software prevents V-Box from installing virtual adapter during PCT/V-Box installation or prevent PCT from connecting to a virtual adapter.   Example: The anti-virus software can flag V-Box file as possible threat. Resolution Uninstall or Disable security and Anti-virus software. Install PCT. Install or Enable the software after PCT works properly.   NOTE:  You may have to disable and/or completely remove the security software even after PCT is installed and works properly.  Contact your IT group to get assistance with getting exceptions entered to have PCT work correctly in conjunction with your security software.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP-server from the virtual machine. Resolution To configure a portgroup or virtual switch to allow promiscuous mode: 1.Log into the ESXi/ESX host or vCenter Server using the vSphere Client. 2.Select the ESXi/ESX host in the inventory. 3.Click the Configuration tab. 4.In the Hardware section, click Networking. 5.Click Properties of the virtual switch for which you want to enable promiscuous mode. 6.Select the virtual switch or portgroup you wish to modify and click Edit. 7.Click the Security tab. 8.From the Promiscuous Mode dropdown menu, click Accept. Note: The setting on the portgroup overrides the virtual switch setting. For more information, see How promiscuous mode works at the virtual switch and portgroup levels (1002934).  

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7 Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7 Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue BAS terminal receives system messages from a PIU with no explanation and is asked to contact Product Support. For example "Message No. 19920 not available. Please contact Product Support" Product Line Other, Satchwell Sigma Environment BAS PIU  and Sigma Pre-release 4 System Messages BAS (1 - 10499) SNP Gateway ( 10500-10999 ) CHUBB Remote Access Management ( 11000-11499 ) CEGELEC ( 11500-11999 ) OTIS   ( 12000-12499 ) CCURE ( 12500-12999 ) WORMALD ( 13000-13499 ) ASIC ( 13500-14999 ) SIMPLEX ( 14000-14499 ) CARRIER DATAPORT  ( 14500-14499 ) EXPRESS LIFT ( 15000-15499 ) CARDKEY ( 15500-15999 ) Mitsubishi ( 16000-16499 ) Liebert ( 16500-16999 ) IMPACC ( 17000-17499 ) YORK ( 18000-18499 ) AUTOFLAME (19000 - 19100) AUTOMETERS (19100-19199) MITSUBISHI PLC (19200 - 19299) SIEBE MICRONET (19400 - 19499) CROWCON (19500 - 19599) MNI (MicroNet Interface) ( 19700-19799 ) Colt OPV ( 19800-19899 ) MODBUS ( 19900-19999 ) MCQUAY (20000 - 20199) FIDELIO (20200 - 20299) ATLAS COPCO ( 20301-20399 ) UNIFACT PRO ( 20500-20599 ) Cause Due to a size limit (64Kb) not all the PIU error messages are included in the Messages.ini file. Resolution A more complete list of the of BAS error messages can be found here. Copy the appropriate section Paste into the C:\Bas\Data\Messages.ini file into the correct sequence as by message number The maximum size of the message.ini file must not exceed 64Kb Example:

Issue When browsing to the LNS database on the new NL220 project screen, an error message says, "Setting NeuronID of router <%s> ..._O" Product Line Other, TAC Vista Environment Lonmaker Newron NL220 Cause The name of the database folder is over 12 characters. For example, C:\LM\Db\367_Collins_St Resolution To correct this error, rename the folder containing the lonworks database to 12 characters or less. The above example folder name in the Cause heading could be renamed to  C:\LM\Db\367CollinsSt

Issue Every time the computer reboots, LMGRD errors are shown at startup. LMGRD encountered a problem and needed to close. lmgrd.exe - Application Error The instruction at "0x0012e854" referenced memory at "0xffffff91". The memory could not be "written". Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista Server 5.0 FlexNet Licensing Remote Alarm Manager Sigma BAS2800+ Micronet Errors Cause There is a known issue with the new license server from Flexnet. The LMGRD.exe is actually crashing during shut down of the PC. Resolution This is nothing dangerous. What happens is that when you turn off the PC, something is happening with the license server during the shutdown phase. Since LMGRD runs as service, it can not display this error message during this shut down. The error message is shown the next time the PC is started. It will not affect anything since the error messages is queued from the last shutdown sequence, NOT during the startup. We think it has something to do with having a license server installed and not using only an entitlement license. In some situations, placing a customer license file from any project into the license folder along with the monthly demo license stops the LMGRD error. The license server may read the customer license, note that it is invalid, then use the monthly license. Flexnet is looking into this issue. Look for a fix in upcoming versions. On Sigma, BAS2800+, and Micronet systems where Remote Alarm Manager is installed, the TAC license server can be uninstalled as it is not used.

Issue Error when running the Checklic license utility: "InitCrypkey Error -103: NETWORK: REPLY FROM NETWORK DRIVER IS BAD" "InitCrypkey Error -102: NETWORK: NETWORK DRIVER APPEARS TO NOT BE SERVING THIS DIRECTORY" Product Line Other, TAC Vista Environment LNS 3.0 LNS Turbo Edition (Ver 3.2) LonMaker 3.0 LonMaker 3.1 LonMaker Turbo (Ver 3.2) Vista Cause A problem has occurred with the LonMaker licensing. Resolution There are two procedures for fixing this problem. Try Procedure 1 first, and if the license still has the same problem, try Procedure 2. Internet access may be required for Procedure 2 to in order to download the setupex.exe and cks.exe programs and request a replacement license. Procedure 1: Confirm that the Windows Crypkey License service is started. To confirm, click Start > Control Panel > Administrative Tools > Services. Verify the Crypkey License status is Started. Also verify that the startup type is Automatic. If not, right-click the name and then click Start. Double-click the name to enter the properties dialog and change the startup type to Automatic. Close the Service window.   Confirm the Crypkey NetworkX driver is started by running C:\Program Files\Common Files\Microsoft Shared\MSInfo\Msinfo32.exe. Expand System Summary > Software Environment > System Drivers in the category tree in the left pane, then locate NetworkX in the right pane. Confirm that the State is Running and the Status is OK. Close the System Information window. If you cannot find these software components, uninstall the Echelon Software product, reboot, and reinstall the product. Antivirus and Internet security software can interfere with the proper installation of the software. Disable such software before you re-install the Echelon software product. At this point, if you are still unable to run your LonMaker or LNS application because of a License Access error message and if the Checklic license utility still reports a -102 or -103 error, follow the steps in Procedure 2. Procedure 2: Check to see if two files exist in the C:\Windows\LNS Licenses folder. setupex.exe cks.exe The LNS Licenses folder is hidden; if you do not see it, open the Windows Explorer Tools menu, click Folder Options, and in the View tab, select Show Hidden Files and Folders and clear Hide Protected Operating System Files (Recommended). If you don't see these files, download them from Echelon and extract them to the C:\Windows\LNS Licenses folder. Open a Windows command prompt by clicking Start > Run and typing in cmd (or command for Windows 98). Type the following command to change your working directory: cd "\Windows\LNS Licenses" Type the following command: setupex /U Reboot the computer. Repeat steps 3 and 4, and then type the following command: setupex Reboot the computer. Open a Windows command prompt and enter "checklic lonmaker.vsl" for the LonMaker Tool or "checklic nsseng.exe" for other LNS tools and applications. If no errors appear, then the LNS application should start. Exit now. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening/creating network. If the -4/-1 error remains, use the license wizard to request replacement credits. If the InitCrypkey Error -102/-103 error is shown, delete the following files under C:\Windows\LNS Licenses (do not delete other files from the LNS Licenses folder): For the LonMaker tool: LonMaker.rst LonMaker.ent LonMaker.key LonMaker.41s For an LNS tool or application other than the LonMaker tool: nsseng.rst nsseng.ent nsseng.key nsseng.41s Delete esnecil.ind in the C:\windows\system32 folder. Reboot the computer. Run the Checklic license utility again. If the GetAuthorization Error -4/GetAuthorization Error -1 error is shown, which is expected, try opening or creating a network. If the -4/-1 error remains, use the license wizard to request replacement credits. Once the license is fixed, download and install the LNS Licensing Update 2006.

Issue What batteries and PSU cards can be used in a x96 Controller? Product Line Other, Satchwell Sigma Environment S-x96-STD S-x96-BAT Sigma BAS Cause What batteries and PSU cards can be used in a x96 Controller or BAS controller? Resolution See TPA-LOND-08-0017.02 S-ARM7-BAT is the Sigma UNC PCB Battery Spare for the ARM7 CPU Board. The battery itself is a Ni-MH 2-Button Cell, 2.4v, 80mAh. S-V53-BAT is the Sigma UNC PCB Battery Spare for the V53/V25 CPU Board. The battery itself is a Ni-MH 3-Button Cell, 3.6v, 150mAh. S-X96-BAT is the Sigma UNCx96 Hi-Capacity Battery for the x96 products. The battery itself is a Ni-MH D-Cell pack, 10.8v, 5Ah (12-Hour). S-X96-STD is the Sigma UNCx96 Standard Capacity Battery for the x96 products. The battery itself is Ni-MH AA-Cell pack, 10.8v, 1500mAh (1.2-Hour) Due to UK legislation in 2006 NiCad batteries could not be used and changes were made where NiMh batteries are used instead 2016-01-22: - Confirmed both the S-X96-STD and the S-X96-BAT battery packs are currently available. Note: Schneider sales do not understand dashes, so when asking for price and availability you need to remove the dashes or they will not find the parts. Specification Sales need Price provided by sales S-X96-STD SX96STD £ 198.05 S-X96-BAT SX96BAT £ 541.19 General Rules for battery replacement and PSU card replacement/modification are: 11/2008 to present - The controller was originally shipped with the NIMH battery and PSU card suitable for charging the NiMH battery. These PSU cards are suitable for charging both NiMH and NiCad batteries. 04/2004 to 10/2008 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. 1999 to 03/2004 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. Pre 1999 BAS PSU cards - 2 resistors are required, the TPA explains how. The resistors are shipped with the NiMh battery. Note: If upgrading to Sigma then the Upgrade kit S-x96-UPKIT should be used which includes a new PSU card.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Other,Satchwell Sigma,Security Expert,TAC INET Environment Existing intelligent Building Management System Open Mind High Avalibility Solutions everRun MX Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing reliability of the system. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. 1. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. 2. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility is site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measure to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components is the leading cause of failure, followed by lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity.   Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with StruxureWare Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide  

Issue ISO 9001 certificate for Schneider Electric Buildings Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices,Other, TAC INET, TAC Vista Environment Management Certification Certificate for the Design and Manufacture of Building Management System Controllers, Devices and Electronic Systems Cause ISO9001 certificates are sometimes requested for different projects. Resolution Download the ISO 9001:2015 certificate here.

Issue The Remote Alarm Manager sends a message to the recipient indicating that an alarm has been inactivated. The screen shot below shows how a typical message will appear on the receiving mobile phone. Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager version 1.2 Cause An alarm message is generated, and the Remote Alarm Manager processes it in the normal way. After three days and at midnight, the Remote Alarm Manager will send a inactivation message to the on-call recipient, indicating that this alarm has been inactivated. Resolution This is not a fault with the system, it is operating as designed. When a new alarm is received by the Remote Alarm Manager, it is acted on in the way the configuration dictates. If the alarm remains on the system, without being retransmitted, then after three days the inactivation takes place. The 3 days is the default setting and can be changed if required.

Issue Users or engineers may be unsure of how to access the best support for issues with Smart Connectors, especially where site specific Smart Connectors have been developed, or believe the issue is with the underlying framework. Product Line EcoStruxure Building Operation Environment SBO/EBO and general integration projects Cause Unlike SBO/EBO, which is a standard EcoBuilding product that falls under normal technical support, the Smart Connector (formerly known as Mongoose) was developed by Schneider Electric Buildings Labs. As such the necessary level of specific Smart Connector expertise is not found within the technical support teams Resolution If using a Smart Connector developed specifically for a project created by a separate Integration Team within Schneider EcoBuilding, then it is always best to go back to that team with your technical issues. In all other cases, the best place to raise any questions would be on the SmartConnector Developer Forum: Here, questions can be raised and speak directly to the Software Developers who originally created the Smart Connector Framework.

Issue With the offering of EcoStruxure Energy Expert (formerly Power Manager) for SmartStruxure there can be confusion on the difference between it and Power Monitoring Expert also referred to as PME. Product Line EcoStruxure Building Operation, Other Environment SmartStruxure EcoStruxure Energy Expert (formerly Power Manager) Power Monitoring Expert (PME) Cause Since EcoStruxure Energy Expert (formerly Power Manager) is an offering that combines EcoStruxure Building Operation with Power Monitoring Expert, there tends to be some confusion on what exactly EcoStruxure Energy Expert is and how it is supported. It also seems that the similarities of the names causes confusion. Resolution Definitions EcoStruxure Energy Expert (formerly Power Manager) for SmartStruxure - This solution is an engineered solution that combines two Schneider Electric software systems: Ecostruxure Building Operation (EBO) and StruxureWare Power Monitoring Expert (PME). Energy Expert utilizes EcoStruxure Web Services (EWS) to be able to share data between the the two different SmartStruxure software platforms. The tools that Energy Expert uses to complete the connection between EBO and PME include the ETL Tool and the Integration Utility. EcoStruxure Building Operation (EBO) - Schneider Electric's premier next generation building management system (BMS) software that powers SmartStruxure solution. Providing integrated monitoring, control, and management of energy, lighting, HVAC, and fire safety, it turns system data at the automation level into valuable business information at the management level. StruxureWare Power Monitoring Expert (PME) - This is a complete, interoperable, and scalable supervisory software dedicated to power monitoring that enables you to maximize operational efficiency, optimize your power distribution system, and improve your bottom-line performance. Real-time monitoring and alarming helps you to avoid critical conditions that can cause equipment failures and downtime. It also helps you to track consumption and the cost of power, gas, and other resources, and allocate costs by building. EcoStruxure Web Services (EWS) - This is the Schneider Electric standard for sharing data among various SmartStruxure software platforms to facilitate the creation of EcoStruxure solutions. EWS is based on conventional Web Services technology (SOAP, WSDL) and provides a way for solution architects and solution development teams to build solutions that require data to be shared among different SmartStruxure software platforms. ETL Tool - The function of the ETL is to connect to the EcoStruxure Building Operation EWS Enterprise Server or Application Server, extract select historical data (Trend logs), and insert that data into the Power Monitoring Expert database. Integration Utility - This tool shortens days of manual integration work into minutes. It brings the Power Monitoring Expert (PME) dashboards and reports into EcoStruxure Building Operation (SBO) via an EcoStruxure Web Services (EWS) connection.  For more information see the Energy Expert - Design Guide which can be downloaded off of the The Exchange.  EcoStruxure Energy Expert (formerly Power Manager) System Flow and Support Teams Corresponding Product Support Groups EcoStruxure Building Operation (EBO): EcoBuilding Product Support EcoStruxure Energy Expert (formerly Power Manager) for SmartStruxure: EcoBuilding Product Support or PMO Support (depends on where the issue resides; either in PME or in EBO) StruxureWare Power Monitoring Expert (PME): PMO Support

Issue On rare occasions you will get an error during the installation of Echelon OpenLNS Server on Windows 8.1 64 bit saying that the installer can't create specific registry keys. Product Line EcoStruxure Building Operation, Other, TAC Vista Environment OpenLNS Windows 8.1 64 bit Cause The user does not have permission to access those registry keys. Resolution Add the registry keys manually. Alternatively, run OpenLNS on Windows 8.1 - Registry paths.zip reg file that will add the keys. Run the installer again.

Issue Understanding and Troubleshooting Modbus Product Line EcoStruxure Building Operation, TAC IA Series, Other  Environment All Modbus environments. Cause Modicon first introduced Modbus in 1979. Modbus is an open standard,and it is the most widely used in the industrial environment. Modbus is publicly available and,due to its simplicity, many manufacturers use Modbus as a solution for integration in their own products. Many commercial products and systems support the Modbus RTU and Modbus TCP protocols. For further information, visit the Modbus website at http://www.modbus.org. Resolution For a brief understanding on Modbus and how to troubleshoot Modbus: Modbus Troubleshooting.pdf

Issue Where can we find the LON xif files for SE72xx, SE73xx, SE76xx controllers? Environment SE7200 / SE7300 / SE76000 Cause xif files are needed for LON applications. Resolution All LON related files for these controllers are available for download on The Exchange Download Center:   XIF files and plug-ins Resource files (DRF kit)