Building Automation Knowledge Base

Notifications

Community

Notifications

Categories
Forums
Knowledge Center
Blogs
Ideas
Events & Webinars

Share Your Feedback – Help Us Improve Search on Community!
Please take a few minutes to participate in our Search Feedback Survey. Your insights will help us deliver the results you need faster and more accurately.
Click here to take the survey

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Search in

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue The Windows Installer fails to complete the installation of an application. This may occur across various Windows operating systems. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Microsoft Windows Server 2003 Microsoft Windows Server 2003 R2 Microsoft Windows XP Windows 7 Windows Server 2008 Windows Server 2008 R2 Windows Vista Windows 8 Windows 8.1 Windows 10 Windows Server 2012 editions Windows Server 2012 R2 Cause Installation failures may result from: Corrupted system files Incomplete previous installations Conflicts with existing software Unsupported OS versions or outdated service packs Resolution For Windows 10: Use the official Microsoft Program Install and Uninstall Troubleshooter: 🔗 Launch Troubleshooter Note: This tool is not supported on earlier versions of Windows or Windows Server. For Other Windows Versions: Manual troubleshooting steps may be required: Run System File Checker (SFC): Open Command Prompt as Administrator and run: sfc /scannow Check Windows Installer Service: Ensure the service is running: Press Win + R , type services.msc , and locate Windows Installer Right-click → Start (if not running) Clear Temporary Files: Use Disk Cleanup or manually delete files from %temp% Review Event Viewer Logs: Look for installation-related errors under Windows Logs → Application Verify OS Compatibility: Confirm your OS version is supported by the application and has the latest updates. Additional Notes Always verify the official Microsoft support status for your OS version to ensure compatibility and security.

Issue Can not save the Diagnostic Files from IP Controller using Building Commission Share button Product Line EcoStruxure Building Operation Environment Building Commission Cause By default, the only apps you can share are Mail and OneNote for Windows. Neither allows you to save a file to the Windows File System. Resolution Install Clipboard by Justin Chase via MS Store or link. In Building Commission, navigate to the controller -> Device Settings -> Diagnostics Files Select either Device Report, Error Log, or Crash Report Click Share icon in the upper right corner. Select Clipboard icon. Click Copy button Right-click Paste on the desktop or in File Explorer folder. Note: *** This article applies to earlier versions of Building Commission/Windows. Starting from version 2025.1.57, users can share diagnostic files through multiple methods on devices running a Windows-supported version ***

Issue Power to devices are Full Wave or Half Wave. Device is connected to 24VAC and begins to smoke because the voltage power input from transformer is not wired correctly. Product Line TAC INET, TAC Vista Environment Devices such as a Xenta Router or a controller which is powered by an external 24VAC transformer. Cause Devices such as a Xenta Router or control board is connected to 24VAC and begins to smoke because the power input from transformer is not correct. Resolution Download Full Wave Half Wave.pdf which illustrates the transformer to device wiring configuration. PoE is not supported for any of the Ethernet ports on I/NET devices.

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network with integration of the FOI or Fiber Optic Interface Cause How the Fiber Optic Interface (FOI) fits into an I/NET site. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN and the integration of Fiber Optic or FOI. The FOI Spec sheet is available here, as well as TCON087. Click the image below to download as a PDF document.

Issue A method to remove access from a large number of Personnel by changing the Expiration Date using a Template. Product Line Andover Continuum Environment Continuum Access Control Cause Need to know how to disable large numbers of Personnel at one time using the Personnel Expiration Date. Resolution The Personnel Expiration Date is distributed down to the Controllers and used to allow or deny access at the Door. If a future date is set then the Personnel has normal access, if a past date has been set then they do not have access and a "Person Expiration Date Passed" error will be displayed when they are refused access. See the steps below on how to use a template to mass set this Expiration Date field for a large number of Personnel at the same time. 1. Create a Personnel Template in the Personnel Templates Folder. Notice that the Expiration Date defaults to a future date of "12/31/2099 11:59:59 AM". 2. Go to the Attribute Data Source tab and set the ExpirationDate attribute to InheritFromTemplate. 3. Use this Template to create your Personnel objects. 4. Notice that Personnel created from this template should show the Expiration Date in Blue which is also un-editable in the Details tab. 5. Edit the Template and change the Expiration Date to a date that has already past. After saving the Template the changes will be made to all attached Personnel and those Personnel distributed to all online controllers. Viewing the Distribution Properties, you should see an entry for each object refreshed by the Template. 6. Looking at the Access Distribution View you should see that the Personnel have been redistributed down to the controllers successfully. 7. Test your Personnel at the Door and they should no longer have access. Looking in an active Event View you can see that the Personnel are not being granted access with the Message "Person Expiration Date Passed". When setting the ExpirationDate back to a future time they will now have normal access.

Issue BACnet Schedule does not change the Digital Value when the Value attribute of the DV is bound to the Schedule Environment StruxureWare Building Operation BACnet controller B3xxx series. Cause When a user creates the BACnet Schedule object in the b3 controller, if the Default_Value attribute of the BACnet Schedule in the b3 is not configured, the schedule's default value is left as "NULL". And later on, when the Schedule turns to True, it sets the bound DV value to Active. But when the Schedule turns to False, it tries to change the bound DV value to NULL (as it is the default value of the schedule), which fails as it is not allowed to set the DV value to NULL. As a result, the bound DV value cannot be changed and it keeps its previous value "Active" without being able to change it any longer. Resolution Set the Default Value attribute of the BACnet Schedule object from NULL to False as below: - Right click the BACnet Schedule object in the b3 controller and select the Properties. - In the Basic tab of the Properties window, scroll down all the way to the bottom and locate the Default Value attribute. - Click the setup icon on the right side of the attribute, it pops the Default Value window. - Uncheck the Null checkbox and confirm the Value now shows False. - Click OK from the attribute window, verify the Default value is False now, click OK from the Properties window.

Issue Running I/NET Seven as a service on Windows Product Line TAC INET Environment I/NET Seven All supported Operating Systems Cause When you log out of Microsoft Windows or restart the computer, all running processes are shut down. These processes are not resumed at log on or at restart. You have to start I/NET manually again. To get I/NET to start up when the computer restarts, you can run it as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Resolution Use the INET Run Mode tool available on the Community. Alternatively, you can perform the following steps to set/unset the InetIoSrv.exe as a service or application. To register I/NET Seven to run as a service Open a Windows command prompt. Go to Start > Run and type "cmd" Use right-click on the command prompt and select "Run as Administrator" Use commands cd.. (to go back one directory) and cd (to go into a folder) to navigate to the following location: C:\Program Files\INET Seven\ If this is being run on a 64 Bit OS, the location then would be: C:\Program Files (x86)\INET Seven\ Type the following command. This will unregister I/NET as an application inetiosrv /unregserver Type the following command. This will register I/NET to run as a Windows service inetiosrv /service To verify the changes have taken effect Right-click on "My Computer" and select "Manage" Select Services and Applications > Services Look for Inet7Iosrv. It should be set to Automatic. You are now running I/NET as a service. IOSrv will now be running in the background when the PC boots up. This does not require a Log On to the PC, however, you will have to Log On to the PC as a user to launch I/NET or AMT from the desktop icon. You will notice that IOSrv has been logging all AMT transactions, messages and alarms. The SQL Server and Agent were also running in the background receiving data to the database. To set I/NET back to running as an application Open a Windows command prompt. Go to Start > Run and type "cmd" Use right-click on the command prompt and select "Run as Administrator" Use commands cd.. (to go back one directory) and cd (to go into a folder) to navigate to the following location: C:\Program Files\INET Seven\ Type the following command. This will unregister I/NET as a service inetiosrv /unregserver Type the following command. This will register I/NET to run as an application inetiosrv /regserver

Issue Unable to connect to a system that is using Server/Client Configuration. After promoting a stand alone PC to a remote client and clicking on the connect button, an error "No Entries in Database" comes up and the user cannot connect to any of the controllers on the system. After a restart of PC and an attempt to connect to the I/NET System, an error "No entries in database" is seen. Product Line TAC INET Environment I/NET Seven Windows 7, Windows XP, Windows Vista, Windows 10 Cause Some of the possible causes : After promoting a stand alone PC to a remote client the Reference Host information of both the server and the client must be updated with the IP addresses of each other. Bad communication or bad controller that is connecting the C-LAN to the Xenta 527 In some instances when running the I/NET IO Server as a service and after a restart of the PC hardware running a Windows 10 Operating System, it is has been seen to produce this "No entries in database" error. At this stage the reason is currently unknown but the connection to the Xenta 527 is not made and the IO Server service needs to be restarted. Resolution Open I/O Server Hit the Modify button In the Reference Host Column, add the IP address of the server Repeat steps 1-3 on the server, adding the IP address of the remote client. Note: Should the Xenta 527 still not communicate to the controller: Verify that the C-LAN wire is connected properly There is communications between the controllers and the Xenta 527 If not, unplug the C-Lan connector, from all the controllers and bring them online one at a time to determine which one could be bad. Replace possible bad controller and the system should come online again. To correct the issue after a PC hardware restart, two options are available Restart the I/O Server service Change the run mode of the I/O Server to an application. See Running I/NET Seven as a service on Windows for further information on options on how to achieve this.

Issue What is the password policy for Security Expert operators, and how can it be configured to meet specific cybersecurity requirements? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Cause Some sites require customized password policies to comply with cybersecurity standards. These may include requirements such as: Enforcing regular password changes Preventing the reuse of previous passwords Setting minimum password length Requiring strong password complexity Resolution Default Password Policy in Security Expert By default, Security Expert enforces the following password policy for operator accounts: Minimum password length: 8 characters Password change required: On first login For more information on Security Expert’s cybersecurity practices, refer to the SX-SRVR Security Expert System Hardening Reference Guide. Custom Password Policies via Active Directory Integration Security Expert does not support advanced password policy configuration directly within the client interface. However, enhanced password policies can be enforced by integrating Security Expert with Windows Active Directory. To implement this: Integrate Security Expert with Active Directory Follow the steps outlined in Option 1 of the How to Integrate Active Directory with Security Expert article or Option 2 for full Active Directory integration. See AN 288 Security Expert - Using Active Directory - Integration Guide for additional details. Configure Password Policies in Windows Domain Once integration is complete, operator accounts managed through Active Directory will adhere to the domain’s password policy. This allows you to enforce: Password expiration intervals Password history restrictions Minimum and maximum password lengths Complexity requirements (uppercase, lowercase, numbers, symbols)

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'.

Issue A third party BACnet system is able to host values from a SmartStruxure Lite MPM but an MPM does not seem able to host values from another BACnet system or device. Environment BACnet MPM-VA MPM-UN MPM-GW 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. Cause SmartStruxure Lite Managers have full BACnet server capabilities, however BACnet client functionality is not native to the MPM and is currently only available through Lua programming. Resolution Integrating SmartStruxure Lite™ Managers with third-party BACnet server devices requires a BACnet client script. A sample script (download here) can be used to perform read and write operations to other devices via BACnet IP, however, a few tips and limitations must be taken into consideration before deployment on site. NOTE1: The delay at the beginning of the script (if scl.sysclock() > 90 then) must not be removed or modified. Otherwise, the MPM will keep rebooting endlessly and would require restoring its factory defaults before gaining access to Building Expert again. NOTE2 : The more points used in the script, The higher the MPMs CPU% Usage will be and the less responsive the MPM will be. Therefore, it is recommended to only read/write the necessary points and not all the points on the third party devices. Also, if some points are more important that others, the polling time can be increased to 60 seconds for example. NOTE3: The more objects you have on the MPM, the less room you have for BACnet points. PGs, Trends and Events consume a substantial amount of CPU Usage so it is important to keep an eye on it as you add more points in the script. NOTE4 : Run the script every 5 seconds or more if possible Limitations: - Reading/Writing to Multi State Values (MSV) is not supported

Issue In Physical Access Control lingo, the term Edge controller typically refers to a device that is installed at the door (or in close proximity to the door) and that has all of the components needed to fully control the door with only and IP connection running back for communications to the front end system. Typically Edge access controllers are PoE so that there is no need to provide a separate power feed to the device, they also provide power to all the components that comprise the door control (door lock, REX etc) Environment CyberStation CX9702 Cause Documentation Resolution Continuum does not have a physical access controller that can be considered an Edge access controller. The Continuum access controller that come closest is the CX9702, although it is NOT a PoE controller. Click HERE to see the specs of the CX9702.

Issue Depicting the differences between Bacnet points and Central IO points. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and lower Cause Explanation of difference in points Resolution Creating Central IO points When you create inputs and outputs in a non-BACnet SmartStruxure system, you simply create the inputs and outputs and then provide programming to control the Requested value. Trends, alarms and graphics would monitor the value property. In a BACnet SmartStruxure system, the inputs and outputs are created under the IO Module in the same way; however an additional point is created in the Application folder under the BACnet Interface Device. On the property page of that point is a field designating the “Associated Value”. You should browse to the appropriate CIO point and select it. At this point all monitoring, display and control of the object should be accomplished with the BACnet point. (It is also possible to make the link between the associated value and the IO value by using the binding tool.) There is no other binding necessary to make the link between the CIO point and the BACnet “proxy” that is created in the application folder. For SmartStruxure versions prior to 1.4 please see the attached document for some implications and proper method of operation for using the IO associated value property: PSS Building Operation Attachment 14040rev2.pdf For SmartStruxure 1.4 and above see Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above.

Issue Access Control Spec for Tender Offer which usually comes from the Product Marketing Division Environment I/NET Site with Access Control Cause Bidding a job and requests for Access Control Spec or Specification Requests for: General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Security Management System (SMS) specified For the Access/Security Control Contractor. Typically the SMS provides and explanation and integration for: • Integrated Access Control • Alarm Monitoring • Integrated Digital Video Management • Interactive Alarm/Facility Graphics Display • Wireless Alarm and Video Transmission • Associated Access Control and Alarm Equipment Control • Multiple Language Operation • Multiple Tenant Operation • Access Initiated and Event Initiated Control • Elevator Control • Workstation and associated equipment General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Resolution I/NET Seven Access Control Specification (Available in a MSWord format)

Issue Functional block names are shorter in XIF file, LonMaker or NL220 than the names defined in SmartStruxure Environment Automation Server Externally Managed LonWorks Network Cause LonMark defines how a xif file must be structured and written. There are especially three rules that comes into play when creating the functional blocks from an Automation Server in the externally managed LonWorks network. In the LONMARK® Device Interface File Reference Guide it states that: "If the static interface contains functional blocks, the device selfdocumentation string must be formatted as described in The LONMARK Interoperability Guidelines." In the LONMARK® Application-Layer Interoperability Guidelines it states that: "Manufacturers are free to assign any functional profile number to new non-inheriting profiles, as long as they are in the range of 20000 to 25000, inclusive; and as long as the number is unique for the program ID template and scope of the resource file set containing the functional profile." In the same document it also states that: "The device self-documentation string is a string of up to 1024 bytes (subject to device memory limits)" and also "If the name is text, it must consist of ASCII printable characters, be of no more than 16 characters in length". Due to the above mentioned rules, any functional block defined in the Automation Server will always start with a functional profile number from 20001 and up and the name of the functional block (excluding the 5 digit profile number) will not be longer than 16 characters. If the name defined in SmartStruxure is longer than 16 characters, the characters from 17 and up will be deleted. If the complete length of the self documentation string is longer than 1024 bytes, the maximum character length will be lowered by one until the complete string fits within 1024 bytes. Resolution The only way to get around this is to either make fewer functional blocks on the Local Node in SmartStruxure, or to make their names shorter.

Issue Can I take a 26 bit Wiegand Hexadecimal Card Number format and find out what the Facility Code and Card Number are? Product Line TAC INET Environment 26 bit Wiegand Hexadecimal Card Cause Need to discover the Facility Code and Card Numbers Resolution Yes you can do this. This document will show you the process on how to determine these values: 26 Bit Wiegand Format Also see Conversion from I/NET hexadecimal code to Continuum Facility/Card Number for an Excel utility to perform this conversion.

Issue SNVT_flow will not display correctly in Imperial units on a TGML graphic on a Xenta Server Product Line TAC Vista Environment Xenta Servers version 5.1.1 or earlier Xenta 511, 527, 711, 731 Cause SNVT_flow will only display on TGML graphics as liters per second regardless of what unit the signal in Xbuilder is configured for when sent to the graphic page. This is a bug and has been reported. Resolution This has been corrected in version 5.1.2. Upgrading to 5.1.2 or later will resolve this issue. If upgrading is not an option, the conversion can be done in a script element of the TGML graphic page. This LS to CFM Snippet can be used to modify a numeric or text presentation object.

Building Automation Knowledge Base

Improve your search experience:

Related Forums

Intelligent Devices Forum

Windows installer fails to install an application

Save Diagnostic Files from Building Commission in Windows

Device connected to 24VAC begins to smoke due to power input from transformer not being wired correctly

BCX Battery Replacement Procedure

Fiber Optic Interface, Ethernet, C-LAN, and Sub-LAN communication.

A method to remove access from a large number of Personnel by changing the Expiration Date using a Template.

BACnet Schedule does not change the bound Digital Value

Running I/NET Seven as a service on Windows

Error: "No Entries in Database"

Security Expert Operator password policies

Understanding ''Run on any Workstation" programs.

Capture a Sigma trace log in EBO/SBO

SmartStruxure Lite MPM BACnet client capabilities

Is there a Physical Access Control EDGE controller for Continuum?

Bacnet and StruxureWare Building Operation Central IO points

I/Net Access Control Spec for Tender Offer

Functional block names are shorter in XIF file, LonMaker or NL220 than the names defined in SmartStruxure

Access Control Doc-to-Dif Report on an older I/NET system

How to find the Facility Code and Card Number

SNVT_flow will not display correctly in Imperial units on a TGML graphic on a Xenta Server

Ask our Experts

Email Us

Building Automation Knowledge Base

Related Forums

Ask our Experts

Email Us

Welcome!