Building Automation Knowledge Base

Issue Errors occur when trying to open up graphics in Vista Workstation similar to these: Microsoft .NET Framework Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. A generic error occurred in GDI+. TAC Vista Workstation Encountered an improper argument. Environment Windows 7 Windows XP Vista TGML Cause Installing Windows XP on a machine that came pre-installed with Windows 7 has been observed to cause this problem. Resolution Computers that are sold with Windows 7 pre-installed typically have hardware that is optimized for Windows 7 and often experience a variety of problems when they are re-imaged to Windows XP. The best solution is to re-install Windows 7. TAC Vista 5.1.4 and newer is compatible with Windows 7 as well as some third-party LNS network tools (check manufacturer's websites for more information). Windows 7 Professional, Ultimate and Enterprise can run programs using "XP Mode". XP Mode is a separate download available for free from Microsoft's website.

Issue Support for HID Corporate 1000 Product Line TAC I/NET Environment HID Corporate 1000 35-bit Wiegand Cause Desire for higher security HID Corporate 1000 Cards Resolution I/NET will work with Corporate 1000 cards, but there are several things to check and go over concerning this type of setup.   Below is a link to the HID Corporate 1000 information page and FAQs https://www.hidglobal.com/access-control/corporate-1000-program   One other consideration is the site will have to go to a Large Number format for the Corporate 1000 format.  The site requesting Corporate 1000 card certification will need to be verified, and though this is not an expense, it will take time.     Note: I/NET will not allow two variations of Wiegand in the same controller. In the door parameters, set up a single Reader type, such as Wiegand 26. 

Issue The SX-KLCS Keypad is offline in the Client and shows ' Keypad 256 error address size' on screen If you attempt to adjust the Keypad Address in the Client it is not even visible Product Line EcoStruxure Security Expert Environment Security Expert SX-KLCS-B, SX-KLCS-W Cause SX-KLCS Keypads are normally delivered brand new to site with a default Keypad Address of 256 which the SP-C controllers cannot use and the Security Expert Client cannot even recognize to change the address via software Resolution The Keypad's address must be manually changed to a value between 1 - 254 using its touch pad. Keypad Address   Please refer to the full SX-KLCS_Security_Expert_Touch_Sense_LCD_Keypad_Installation_Manual from which this extract was taken.   Once the Keypad Address has been set to a value between 1- 254 the Keypad should then be visible to the Client and you should be able to bring it online as usual.       The SX-KLCS Keypad will now display 'Security Expert by Schneider' by default.

Issue What is its part number of the power fuse of an i2/b3 controller? Product Line Andover Continuum Environment Power fuse replacement i2 and b3 controllers 24VAC supply Cause Most controller fuses are not supplied through the factory. Resolution Faulty controllers can be repaired through the regular repairs process, but power fuses can be purchased through local suppliers. The power fuse for the following 24VAC controllers is: Type: Surface Mount Fuse NANO2® Very Fast-Acting, 448 Series Datasheet Ratings: 2A Rating: i2/b3867, i2/b3850 series. 3A Rating: bCX1, i2/b3810 series, i2/b3800 series, i2/b3600 series. 5A Rating: ACX5740, ACX5720 Note: Fuses are fitted to protect the controllers from damage, when replacing one always replace it with an equivalent rating. Also determine the reason why a fuse has blown before replacing, under normal operation a fuse should never blow.  Additional Information CX9702 (115 VA) Main Power Fuse: 250 VAC 1.5Amp Outputs: 125 VAC 3.5Amp replaceable Inputs/Outputs: Surface mount non-replaceable i2/b3814 outputs: see What is the part number of the i2814's output fuse? Note: The part numbers that used to be listed in iPortal have been removed from this article since they are no longer available from Schneider Electric. The fuses may be obtained from third-party vendors such as Littelfuse or Digikey.

Issue Launching Continuum results in error "This workstation is currently unable to connect to the database. Click OK to exit." Also, running Continuum DB initialization results in error: SQL Server [server name] does not exist or access denied. Workstation Setup Failed! Please try again or click Cancel to exit. Environment CyberStation LAN system Cause Fire wall on the server machine is blocking TCP port 1433 Another cause for this happening is a Windows firewall or McAfee firewall being enabled and blocking the IP of the 2nd Cyberstation that is trying to connect. Resolution Disable fire wall at the server or add an exception for TCP port 1433 (or the port used by the client to get access to the server if different).

Issue Cannot generate a report from Access Expert V2. Getting an error when attempting to generate the report "Could not load file or assembly Microsoft.ReportViewer.WebForms, Version=11.0.0.0"   Product Line EcoStrucure Access Expert Environment Version 2 Report Viewer Windows Cause The ReportViewer files that are from Feenics's website contain version 11. Microsoft does have older and newer versions of the file (i,e 10 and 12) so there is a potential that these files will not work. Resolution To resolve this issue 1. Download the Microsoft Report Viewer (Feenics Training> Web App V2> Miscellaneous Downloads) http://www.feenics.com/Downloads/ReportViewer.zip 2. On the Access Expert application PC (Not the SQL Server PC in a 2 PC system)     Uninstall all versions of Report Viewer and SQLClrTypes from Windows> Control Panel> Programs and Features 3. Stop the Feenics Keep Render Service 4. Unzip the Download files (Report Viewer.msi  and SQLClrTypes.msi) and install both of them 5. Restart the Feenics Keep Render Service Test Reports 6. If they are still not working, reboot the Access Expert PC and test again. If this is still not working, contact your local country support.

Issue Can not find Controller Web Server documentation on the web sites. Product Line Andover Continuum Environment Continuum Custom Web Server pages Infinity Web Server Cause Unable to find Continuum Web Server documentation. Resolution The attached Web Server chapter is extracted from a Plain English programming guide.  The Infinity Web Server User Guide is also relevant to Continuum. Also an example program can be seen in How to create custom web pages in the CX controller using Plain English.

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. 

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 for assistance. Issue If TLS 1.0 is disabled on Microsoft Server 2016 you cannot connect to SQL Server 2016 database using Continuum database initialization. Product Line EcoStruxure Building Operation, Continuum Environment Continuum Cyberstation Microsoft SQL Server 2016 Microsoft Server 2016. Cause Microsoft no longer supports TLS 1.0 protocol and IT departments are disabling it. The current version of the ODBC driver (SQL Server) used with Continuum will not function correctly when TLS 1.0 is disabled on Windows Server 2016 in order to use TLS 1.2. A defect/hotifx QC#2290 has been issued for this issue. Resolution There is a hot fix for QC#2290 that needs to be applied to the cyberstation after the installation of the ODBC driver version 13. Use the following link to download the appropriate version of the ODBC driver for your version of the OS. Link to download ODBC driver version 13 https://www.microsoft.com/en-us/download/details.aspx?id=50420 This hotfix fixes the following defect 2290 = When TLS 1.0 is disabled on server 2016 ODBC does not connect to SQL database. Hotfix is attached below. Contact PSS for the hotfix for Cyberstation 2.03 Please note: The ODBC Driver 13 for SQL Server needs to be installed before the hotfix is applied Deprecation date   Steps to apply this hotfix: Create a ContinuumDB backup Shutdown Continuum if it is running Make a backup of OmsInst.exe in the Continuum folder Extract the OmsInst.exe from the hotfix zip file and copy the new file to the Continuum folder Do an update/initialized database Start Continuum

Issue “Invalid certificate for https communication” alarm pops up after upgrading to EBO 4.0     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause "Invalid certificate settings for Server to Server communication" is set to enabled (Generate Alarm) by default for new installations/upgrades. This function was deliberately designed to alert existing installations that their sites might be subject to security-related issues, and necessary action needs to be taken. Resolution If users want to get rid of this alarm, they need to: Suppress the alarm by unchecking the “Generate alarm” under Security Settings/ Invalid certificate settings for server to server communication   Or Replace the server certificates with one that can be validated against a CA certificate.   Note: Please refer to the following web pages for more information. CA Certificate Management Security Settings – Control Panel  SSL Certificates 

Issue Unable to have BACnet alarm trigger directly on a variable from a Function Block Program Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause Building Operation does not have the possibility for a BACnet alarm to directly monitor a variable from a Function Block Program.  The problem with doing this is that a Function Block Program is not a BACnet visible object (a BACnet client cannot see it, even as a proprietary object type), and we do not see any provision in the BACnet standard for an alarm object to reference something not visible to BACnet. Resolution The workaround is to create a BACnet point (a BACnet Value object would make the most sense), and bind it to the Function Block Program variable.   There is however an option which may avoid "double" work.  In Building Operation we have implemented intrinsic alarming on the BACnet points and values.  This means that the point can detect and report alarms without creating a separate alarm object.  (they still need to reference to a BACnet notification class just like normal BACnet alarm objects).   The only limitation is in the choice of algorithm: Analog objects (Input, output, Value) support the out-of-range algorithm (high-limit, low-limit). Digital and Multistate objects* (input, and value) support the change-of-state algorithm. *In Building Operation, we do not have digital or multi-state outputs with alarming, because we do not support "command-failure" type alarm that those require.

Issue In the Personnel Manager, the template field shows an error: "Error in datagrid DataGridViewComboBoxCell value is not valid." Product Line Andover Continuum Environment Continuum 1.93 and below Personnel Templates Cause Error occurs while attaching the Personnel Templates to a personnel from the Personnel Manager. The selected Template is not in the default template folder (Personnel Templates). Note: It is still possible to attach the templates through the method of CSV importing/exporting of personnel. If the Templates are created under the "Templates" Folder, this error occurs. The Personnel Templates should be created under "Templates\Personnel Templates". Resolution Select all the Personnel Templates and move them (Right Click + Drag) to "Personnel Templates" Folder. It will give you an option to "Move Here". See the below screen shot. Click on "Move Here" to complete moving the Personnel Templates. Alternatively: Go to the "Properties" of the Template, then change the path of the Owner.

Issue Checklist to be used as a basis for Maintenance visits. Product Line Andover Continuum Environment Continuum Hardware Continuum Software Cause Having a checklist available for routine maintenance will help with service calls to ensure Continuum sites continue to run smoothly over the life of the installation. Resolution There is no official maintenance checklist but some of the things you might want to consider checking on a regular basis are the items below. Continuum Analyzer Run the tests which check the database for known issues and provides a results file. See How to run Continuum Analyzer and get a report.   Review Windows Event Logs Check the Application and System Event logs for Continuum or SQL related errors. See Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes.   Check the size of the ContinuumDB The Database can't be more than 2GB in MSDE, 4GB in SQL Express, and the size of available space on the drive if using full SQL Server. Continuum will always run better when the database is kept trim, as the database size grows, Continuum transactions may start to slow down. If general system slowness is observed then check the database size and SQL Server resources first.   Truncate/trim event tables in ContinuumDB Especially the ExtendedLog table which can grow very rapidly if not kept in check. See Set up a Continuum system to do automatic log truncation to save database space.   Check that the Continuum Workstation is patched and up to date Periodically service packs and hotfixes are released for different versions of Continuum to resolve identified issues. Consult The Exchange Download Center for the current updates. Service Packs | Hotfixes   Check that Controller Firmware is up to date Check that the Controller firmware versions are supported for your version of Continuum and that they are up to date. Same as service packs for Continuum, new firmware builds are released as issues are identified and resolved. You can find supported firmware for each version of Continuum in the Compatibility Matrix. See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation. And new firmware updates are available on Exchange Extranet.   Check battery charges On controllers that have them, check that the battery for holding up the active RAM still has a charge. How to check -> Battery life in Andover Continuum controllers that have onboard batteries Replacement batteries -> Replacement batteries for the various Continuum controllers   Run the Continuum Errors listviews to see if there are any recurring errors that may need to be investigated.   Most Importantly - Backup the ContinuumDB before leaving site! Backup and restore instructions for a single-user system are below but these also apply to full SQL Server using Management Studio. Steps 1 and 2 in the article below apply to backing up a ContinuumDB. See Move / Backup / Restore a database on a Single User SQL2005 Express system.

Issue External resistors are required for Biasing and Terminating RS-485 trunks connected to an Automation Server (AS) Product Line EcoStruxure Building Operation Environment SmartStruxure Automation Server (AS) with  RS-485 trunk(s) under it. Field controllers on the RS-485 trunk; for example, the Network 8000 ASD controllers (MZ2, PEM1, etc)  Cause Bias and terminating resistors are not built into the AS hardware. Resolution External resistors are required for Biasing and Terminating RS-485 trunks connected to an  Automation Server (AS). See the Technical Reference Guide, revision 1.3, pages 2723, 2724, and 2771. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange. Biasing and Termination details are now found in the "RS-485 Communications" chapter of SpaceLogic - Hardware Reference Guide

Issue Unreliable documentation Environment Butterfly valve Cause Replacement Resolution The MF20 / MF40 actuator data sheets are supposed to be updated in regards to the use on old TRV-S valves.   Basically the standard MF40 fits to the TRV-S DN150-200, but the unique MF20-R fits to everything else.   So you need to know the valve.   No other adaptors are required. Click here for data sheet

Issue When discovering the SLP Series Living Space Sensors they show up in the BACnet discovery summary as Non-conformant. Attempting to add this non-conformant sensor results in a WorkStation error similar to the following:  Validation Error Workstation Error in "~/BACnet Interface/MSTP Network/Living Space Room Unit 4E5932F5_«1»_07/ForeignAddress". Property value "<device, 10000>" already assigned to "~/BACnet Interface/MSTP Network/SLPSTC2/ForeignAddress". COML Validator0 Product Line EcoStruxure Building Operation Environment BACnet MSTP Living Space SLP Series Air Quality Sensors Living_Space_REV2.05.21 Cause Building Operation does not allow duplicate BACnet IDs and hence, during discovery, if a device is found with a BACnet ID (Object Identifier) the same as an existing device it shows as a non-conforming BACNet device. The default device ID for SLP devices should be equal to (Vendor ID * 1000) + MAC Address. Where vendor ID is our Schneider Electric BACnet vendor ID = 10 and the MAC address is unique to each devices MAC address DIP switch setting. This will be corrected in a future release of the Living Space firmware.  Until corrected, and since the Device ID is a read/write attribute the customer is able to change it to avoid duplicates on the bus. Unfortunately, Building Operation does not currently have a method to write a new device ID. Resolution The current workaround is to use a third-party BACnet Explorer such as Yet Another BACnet Explorer (YABE) to write a new device ID value. Once the new ID has been updated the SLP device can then be rediscovered within Building Operations'. 

Issue The SQL Server 2008 is running the 64-bit version as well as the Continuum Workstations are using 64-bit Operating Systems. In the interest of increasing the SQL access speeds can the ODBC connection between them also utilize the 64-bit ODBC driver? Product Line Andover Continuum Environment Continuum v1.94 (or greater) Microsoft SQL Server 2008 64-bit Microsoft SQL Server 2012 64-bit Microsoft SQL Server 2014 64-bit Microsoft SQL Server 2016 64-bit Cause Want to know if the SQL access speeds can be increased by taking advantage of using the 64-bit ODBC drivers. Resolution The Continuum application itself is a 32-bit application, this will require the 32-bit ODBC drivers to make a connection to the SQL Server. Even though we support Continuum in a 64-bit environment, it is still only a 32-bit application so the 32-bit ODBC drivers are used for the SQL connection. Be aware that this is just the communications on the SQL side, the SQL application itself will still process data at 64-bit speeds if the 64-bit version is used.

Issue What is the BACnet point data refresh rate and how is the rate changed? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation AS-P and AS-B Cause Subscriptions are the connection between the value from the BACnet Interface point to the value on the ES or AS. Resolution These subscriptions can be edited using the Binding of the value. Using 1.4, edit the configuration of the Binding as shown below: Here, the default 10 seconds interval in the Requested Transfer Rate can be changed. The default is 10 seconds. This allows changing the default interval of 10 seconds down to a minimum 100 milliseconds a maximum 24 hours:  Using 1.3: Edit the configuration of the Binding as shown below:  Here the default 10 seconds interval in the Requested Transfer Rate can be changed. The default is 10 seconds.

Issue "Root element is missing" error window come up when attempting to edit a personnel object using the Personnel Manager. Environment CyberStation Cause Corrupted Personnel Manager data file. Resolution Navigate to the Continuum installation folder. Locate the file "PersonnelEditorWorkstationSettings.xml" Edit the file and try to identify and fix the problem, if not able to identify/fix the problem you can delete the file but you will lose any customizations done to the personnel manager that are saved in the file such as the default location of area link schedules etc. 

Issue Links not working after TGML conversion Converting I/NET graphics to TGML using the "Create Source Tree" option Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.44 Cause I/NET stored graphics on the hard disk and allowed for complex folder structures to be used in organizing those graphics. When these graphics are converted to TGML, this structure may need to be preserved in order to prevent duplicate graphic names. Resolution For this example I have created a site with 3 buildings containing Identical I/NET graphics. Each Building has a summary page and a VAV page. All pages link back to a home page. In I/NET select System>Export Graphics to TGML(you can also right click on the I/NET interface in StruxureWare Workstation) Set your Source and Destination Path and click All Yes.  When you set your destination path, it must point to a folder that already exists in Windows.  The Export INET Graphics to TGML tool does not create this directory Notice that the default setting is to "Use destination path" If we click convert with that option, we will get only 3 graphics.  The graphics from other folders with the same name are over-written. Select the "Create Source Tree" option, ensure the correct graphics are scheduled to convert and click convert. Notice that In Windows Explorer a new folder structure is created that is identical to the original folder structure. Open StruxureWare Workstation. Create a folder system that matches what is on the Hard disk. Drag and drop the TGML files from Windows explorer to the corresponding folders in StruxureWare Workstation. Test you graphic links to ensure everything is functional. Note: Once the graphics are imported, StruxureWare will allow you to move them freely without breaking the binding between pages. There is another way to import all the I/NET graphic folders in one time. Refer to Import all converted I/NET graphic folders into EcoStruxure at one time.