Building Automation Knowledge Base

Issue Alarms stops coming into Vista from Xenta 280/300/401 in the Lonworks network under a Xenta 913 or a Xenta 701. Xenta 280/300/401 controller goes offline/online in Vista. Unable to disable an alarm from a Xenta 280/300/401 that are under a Xenta 913 running as Xenta Server in Vista. Product Line TAC Vista Environment TAC Vista TAC Xenta 913 TAC Xenta 701 TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 TAC Xenta 281 TAC Xenta 282 TAC Xenta 283 Cause There is no support for adding Xenta 280/300/401 to the Lonworks network under a Xenta 913/Xenta 701 running as Xenta Servers in Vista (even though if it is possible to do it in the software). Resolution Use a different Xenta Server that supports adding programmable Xenta controllers in the Lonworks network. Please see the table in chapter 1.1 of the TAC Xenta Server - Networks Technical Manual or Xenta Server version 5.1.5 and after Major Features.

Issue When trying to run an EBO virtual server in PCT2 the following error message is received: Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information. Server failed with reason 'unschedulable, 0/1 nodes are available: 1 Too many pods. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..'. Go to diagnostics page for more information.   Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The maximum number of running servers in PCT 2 has been exceeded. Resolution PCT 2 supports a maximum of 250 running servers. If this limit is reached with 250 servers already operational, no additional servers can be started.

Issue Cannot activate embedded license on Automation server, either online or offline, with error: FlexNet Embedded error: The allowed time to process the response has expired.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Automation Server has wrong date and time. Resolution Make sure that Automation Server has correct date, time and time zone. Automation Server can be connected to NTP server to synchronize its clock, refer to Synchronizing the Automation Server Clock.

Issue SCD100 is obsolete and needs to be replaced. Product Line Field Devices Environment SCD100: 004630100 004630110 SCD110: 5152300000 5152302000 (SCD110-D) 5152304000 (SCD110-D-H) 5152306000 (SCD110-H) Cause Replacing obsolete sensor SCD100 with new range of sensors SCD110. Resolution The range of SCD110 sensors are replacing the old and obsolete SCD100 sensors. For a complete overview and for more technical details, please see the SCD data sheet.

Issue Unable to back up the Automation Server Unable to retrieve a working backup from an Automation Server Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Enterprise Server Building Operation Enterprise Central Cause Corrupt configuration.db Network environment issues Power failure Resolution Database Corruption When the server backup process is initiated, the server tests the integrity of the configuration.db.  If the database does not pass the integrity test, the backup process is terminated, and no resulting backup is produced. In this case, an older backup will need to be used.  The backup should be bench tested for integrity before restoring to the production server.   Network Environment In some cases, the AS may produce a valid backup file, but when the backup is saved off of the server the file size is unusually small.  This can happen when network issues interfere with the backup save to disk process.   In such cases, Automation Server backups taken from the Enterprise server will usually be damaged as well.    You can work around this problem by connecting a Workstation laptop PC directly to the AS with an ethernet cable, thus eliminating the network from the process. Backups can also be retrieved in this way using most versions of Device Administrator.    Power Failure The power fails while the EcoStruxure BMS server is backing up and the system displays a “Failed backup” message in the Event view. The solution is to initiate a new backup when the power resumes and the EcoStruxure BMS server goes back online. Power Failure Occurs During Backup     

Issue Procedure to Install and Configure Continuum Reports Suite Product Line Andover Continuum Environment Continuum Reports Suite Cyberstation 1.81 and above Cause Need to generate Continuum Reports using the Continuum Reports suite package Resolution

Issue Sigma Release note for 4.07 makes reference to the Sigma Standard Edition Installation and Users Guide.   Environment Electronic documents Cause Location Resolution Click here to download the Sigma Standard Edition Installation and Users Guide.

Issue Can an export file from one version of EcoStruxure Building Operation(EBO) be imported to another version of EBO?  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Export files are in general NOT backward compatible. A Script or Function Block Program that is exported from for example version 3.1.x is NOT guaranteed to import successfully into an earlier release Resolution Starting in version 3.0.x, import files exported from a later release than where they are imported will be denied. An export file from 3.1.x cannot be imported in 3.0.x. An export file from 3.0.x can however still be imported in 2.0.x, but it's not recommended, and it may fail to import successfully. In version, 3.1.x import files exported from versions older than version 1.3, will be denied. Starting in version 3.2.x, import files exported from versions older than 1.8.x will be denied.

Issue When proportional 0-10Vdc type valve actuators are used with a SE8000 room controller, the actuators behavior is inconsistent. Environment SE8300 SE8350 SE8600 SE8600 Cause Some valve actuators e.g. wax filled (thermic type) have a high input impedance e.g. 100 Kohms. When connected to a SE8000 room controller, the actuators operation may be sluggish or may never operate. The SE8000 has a maximum output of 5mA when set to proportional control, using actuators with high impedance, the SE8000 room controller fails to recognise there is an actuator and does not drive it. Resolution A burden resistor can be fitted to draw some current from the SE8000 room controller because the actuator's impedance is too large. The burden resistor needs to be large enough not to affect normal use, but small enough to draw a current from the SE8000 room controller. Using ohms law: Valve actuator @ 100 Kohm SE8000 UO output is 5 mA, maximum Vdc output is 10 Vdc. Minimum size of burden resistor: 10 Vdc/5 mA = 2 Kohm. It may be necessary to increase the size of the burden resistor e.g. 10Kohm. The burden resistor is then installed between the signal ground and the signal, either at the controller or the actuator end. Test the actuators for correct operation.

Issue Switching from the Demo license to the Entitled License in Vista 5 Product Line TAC Vista Environment TAC Vista 5.X.X Cause In most cases the license will begin to work just fine after starting Vista and selecting "Use License Server" upon startup. For unknown reasons, Vista may need to be forced to ask you for a License File Or License Server option when Vista is first started after the license is switched. Resolution Unlike the Demo license, the site license must be placed in C:\Program Files\TAC\License Files (or C:\Program Files\Schneider Electric\License Files for TAC Vista 5.1.4 and above) and accessed via the License Server. It is imperative that the license file retains the .lic file extension, which importing to certain Windows environments may append a .txt extension to the filename The easiest way to force TAC software to use a License server versus pointing directly to the Demo License is to modify a registry setting of the Flexnet Licensing Software.   Start the Registry Editor from the Command prompt (type "regedit" in the start menu run box) and navigate to HKEY_LOCAL_MACHINE>SOFTWARE>FLEXlm License Manager.  Modify the TACLIC_LICENSE_FILE string and delete the Value data. By leaving this key empty, the next time you start any TAC software you will be prompted to "Specify the License Server System" or "Specify the License File".  Start a TAC Software package that requires a license.  Select "Specify the License Server System" and enter the computer name preceded by an "@" symbol. If the License Server resides on the local machine, "@localhost" can also be used. Note: In more recent versions of License Server, the "@" symbol is optional. If in doubt, putting it in will work with all versions. If the changes were successful, the registry entries should appear as follows (in a typical installation). If registry settings are different that the ones below, please contact Product Support Services.   If the above changes were performed but the License fails to read,  in some cases the License Server system will not work properly until rebooting the PC. If unable to read the license use LMtools utility located in the TAC Tools to troubleshoot the issue. If additional assistance is needed for using LMtools, watch the video overview published in Vista 5 Macrovision/Flexnet Licensing: Lmtools diagnostic utility overview. For help with Vista versions >5.1.7, see License troubleshooting in Vista 5.1.8 or greater

Issue Using a 4-20 mA sensor on a Xenta 451A or 452A Product Line TAC Vista Environment Xenta 451A Xenta 452A Cause There is only enough power onboard a Xenta 451A or 452A for one 4-20mA.  Resolution Wire each sensor, using an external power supply for cases where there is more than 1 4-20mA sensor. Create an AI in the Menta file Bind the object to the 451A Select the correct Terminal Ref Choose the 4..20mA sensor If using this device as a stand alone LON module chose the 4-20 mA option for the nci NOTE: only Xenta devices ending in "A" have truly Universal Inputs.  For complete details on input configuration, see Configuring inputs on Xenta 421A or Xenta 451A when using the controller as a stand alone Lonworks node.

Issue When using a USB to RS-232 adapter and an MN-CIM, cannot connect to MicroNet 2000 controllers. Receive an ERROR = -510. The problem has also been seen on laptops with an integral serial port. Environment Laptop computer running the MN-CI or MN-FLO-BAL software tools,  any version MN-CIM Controller interface Module Cause One cause of ERROR = -510 is that the serial port or USB to RS-232 adapter does not supply enough power to the "port-powered" MN-CIM. When the CI software is running, but not communicating on the U-LINK, it requires only 12 mA at 5 VDC. To communicate on the U-LINK, the MN-CIM requires 14 mA at 5 VDC from the DTR control line of the port.  Some computers have a mechanism to sense the increased current draw and shut down the DTR line. This loss of power causes the MN-CIM to reset, and after 3 attempts to communicate the MN-CI software issues the ERROR= -510 message. Resolution See Technical Bulletin 01-104 for information  on the Patton Electronics power supply adapter, model 3PMF9-BC.

Issue Upgrade Xenta I/O modules Environment Xenta 421A, Xenta 422A, Xenta 420A Xenta 411, Xenta 412 Xenta 491/492 Xenta 451A, 452A, 450A Xenta 471 Cause It is not very common to upgrade I/O modules. If it must be done, they are upgraded the same as any other LonWorks device without a host processor. Resolution Right click on the target file to store the file locally on the hard drive. To be able to download the NXE-file, you need both the NXE and the according XIF-file for the specific device. In LonMaker, select Replace or Commission, depending if the device are already in the database or not. If the XIF-file already exist in the database, select the correct Device Template. In the next dialog, select Load application image. Browse to find the directory for the NXE-file. Change File of type to NXE. Browse to find the directory for the XIF-file. Select Next to decide about source for CP values. Select Next, if you do a Replace, you could select the Neuron ID manually, and the old Neuron ID will already be in the dialog. Select Finish to download the new NXE-file into the device.

Issue In a life safety-related application, such as a fume hood, it is a requirement that the status of the end switch is not shared via peer-to-peer bindings. Instead, the end switch status must be hard-wired to all four controllers. What precautions should be taken to ensure that this will not cause issues. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Cause Connecting multiple RP-C to the same dry contact.    Resolution Make sure to use individual transformers to each controller (i.e. one transformer to one controller power supply) to minimize the risk of short circuit.

Issue Receive Error: "Unexpected file format" when attempting to open Graphic Page Environment I/NET Seven 2.41 graphic pages Cause When creating, modifying and saving graphics in revision 2.41 and then attempting to open these graphic pages in previous versions of I/NET this error "unexpected file format" is presented. Resolution This issue has been rectified in 2.41A and above. I/NET Software are available for licensed Partners to download on The Exchange Download Center.

Issue After configuration, Suprema readers are showing as offline in the Security Expert client. There are Security Expert Download Service events logged in the windows application event log. Cannot load DLL - LoadLibrary() Failed. Cannot load DLL event mesage Product Line EcoStruxure Security Expert Environment Security Expert Suprema biometric readers Cause Required DLL SecurityExpertSV2.ThirdParty.dll is missing from the installation folder. Some versions of Security Expert installer will not install this required DLL and the file need to be manually added. Resolution Check the Security Expert install folder, typically C:\Program Files (x86)\Schneider Electric\Security Expert, to confirm if the file SecurityExpertSV2.ThirdParty.dll is present. SecurityExpertSV2.ThirdParty.dll   If the file is not in the installation folder then it can be sourced from the integration guide ZIP package. AN 264 Security Expert - Suprema Biometric - Integration Guide contains the three DLL's required for the integration. Install the file by copying it into the installation folder, then restart all of the Security Expert services or restart the Security Expert server.

Issue 'Error waiting service pin' when attempting LonWorks communications in WorkPlace Tech Environment I/A Series WorkPlace Tech Echelon U10 USB Network Interface Cause WorkPlace Tech is not recognizing the Echelon U10 USB Network Interface.  The U10 USB Network Interface is recognized correctly in Windows Control Panel > LonWorks Interfaces.  Resolution Reinstall the U10 USB Network Interface and the Echelon Open LDV driver. To uninstall the U10 Network Interface (with the U10 Network Interface physically connected to an USB port): In Windows, go to 'start' > 'run', type in 'devmgmt.msc' and click 'OK'. This will bring up the Device Manager.  Expand 'Universal Serial Bus controller'. You should be able to see 'Echelon USB Network Interface'. Right-click on the 'Echelon USB Network Interface' and select 'Uninstall'. Remove the U10 Network Interface from the USB port. To reinstall the Open LDV driver: Uninstall Echelon Open LDV driver from Windows Add or Remove Programs. Install Echelon Open LDV driver using the installation file.  After completing the above steps, connect the U10 Network Interface to an USB port on the computer. It should automatically install. Test with WorkPlace Tech. 

Issue Valid cards are being denied access at doors with "Read Raw" events seen in the Status Page. Read Raw Data Read Raw Data Events Read Raw Credential Data Read Raw Credential Data Events Product Line EcoStruxure Security Expert Environment Security Expert Cause The credential being supplied to the doors reader can be read but is not able to be matched to a valid User in that controller. There could be a couple of reasons for this: Pending downloads have not yet gone through to the respective controller The User in question does not have access to any of the Doors in that controller. Resolution Wait for downloads to complete or manually perform a download to send any pending User updates down to the controller. If the User is supposed to have access to the door they are badging at then confirm they have been assigned an Access Level that includes that door. To hide the events refer to Do Not Display Read Raw Data Message. To display a different message for the event refer to  Add Users to a Controller so all Card Events are Associated.

Issue The LIB-4-485 converter is no longer available through Schneider Electric Environment MicroNet Satchnet Communications Cause Obsolecence Resolution The LIB-4-485 USB to RS232 converter can no longer be purchased through Schneider Electric. The LIB-4-485 USB to RS232 converter can be purchased directly through B and B Electronics. Click here (1) to be linked to the port powered RS232 to 422/485 converter page.  http://www.bb-elec.com/Products/Serial-Connectivity/Serial-Converters/Port-Powered-RS-232-to-RS-422-485-Converters/485SD9TB.aspx Click here to download the data sheet. B and B Electronics contact details: Westlink Commercial Park, Oranmore, Co. Galway, Ireland Phone:   +353 91 792444 Fax:       +353 91 792445 Customer Service: eorders@bb-elec.com Tech Support: techSupport@bb-elec.com General Inquiries: info@bb-elec.com

Issue Web pages opened in TAC Vista Workstation is shown in compatibility view. That might have unwanted impact on some web pages. Product Line TAC Vista Environment TAC Vista Workstation Cause By default TAC Vista Workstation will use the newest version of Internet Explorer installed on the PC, but enable compatibility view. That might have unwanted impact on some web pages. Resolution Add a registry entry to define what version of Internet Explorer you want TAC Vista Workstation to use. Navigate to the following registry key: 32 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION] 64 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION] Add a new DWORD (32 bit) value Give it the name "TACVistaExplorer.exe" Give it the decimal value 11000 to set Workstation to use IE11 This ZIP file contains registry imports that will set the browser used to IE9, IE10 or IE11