Building Automation Knowledge Base

Issue There is no built-in Credential Type for the HID 37-Bit badge with no site code (H10302). Product Line Security Expert Environment Security Expert Server Access Card Format Cause Security Expert does not have the HID 37-Bit badge (H10302) with no site code as a built-in available Credential Type. Resolution 1) In the Security Expert Client, select Sites -> Credential Types 2) Create a new Credential Type with a name of your choosing. 3) Under Configuration, select the Format as Wiegand. 4) In the field labeled Wiegand or TLV Format, enter the following exactly as written:                                                        A,FACILITY,0,MSB,BIN__B,CARD,35,MSB,BIN__PBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBP_EXXXXXXXXXXXXXXXXXX.................._..................XXXXXXXXXXXXXXXXXXO 5) Save   NOTE: This article assumes that the reader is familiar with creating and deploying Custom Credentials, If this is not the case, then please reference the Complex Transition Programming section of the Transitioning Continuum Sites to Security Expert - Transition Guide

Issue The Forta range actuator does not fit onto the V321 Valve. Environment V321 M800 M1500 MV15B M3000 Cause The actuator has a 10mm fitting, the valve (DN65 to DN100 only) spindle has a 8mm stem. Resolution On V321 valves size DN65 to DN100 an adaptor piece is supplied with the valve part no. 880-0133-000 to adapt the valve spindle to the actuator drive. The part no. 880-0133-000 can be ordered separately.

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.

Issue I have an I/NET Controller with a forgotten DCU password. How can I recover it? Product Line TAC INET Environment I/NET Seven Site Cause A DCU password was set on the I/NET Controller and has been forgotten. Resolution Send an email to your local support. Include a copy of the current save file for the controller in question. Support will advise you on the password. Recommendation: For future use, either remove any controller passwords or record them in a secure location where they can be retrieved easily.

Issue Is it supported to access an Automation Server 1.4.0 with the Workstation 1.4.1? Are there any problems and what features are supported when accessing a 1.4.0 Automation Server with WorkStation 1.4.1? Environment Enterprise Server / Workstation 1.4.1 Automation Servers 1.4.0, 1.3 with SP1 and SP2 Cause Understanding of the new Runtime Compatibility mode available in 1.4.1 available during system upgrades Resolution Building Operation supports runtime compatibility between servers running two versions on a single system, during an upgrade process. Version 1.4.1 servers are runtime compatible with version 1.3 SP1 and 1.3 SP2 servers. The system is able to exchange runtime information between 1.4.1 servers and 1.3 SP1 or 1.3 SP2 servers. However, configuration changes cannot be made from an upgraded WorkStation via an upgraded Enterprise Server to a non upgraded Automation Server, such as creating, configuring, and deleting objects. There is also no runtime compatibility for WebStation. Runtime compatibility means you can delay the upgrade of some Automation Servers running version 1.3 SP1 or 1.3 SP2 while upgrading the Enterprise Server, WorkStation, Reports Server, and some Automation Servers to version 1.4.1. You cannot make any configuration changes on an Automation Server running the 1.3 SP1 or 1.3 SP2 version with WorkStation and Enterprise Server running the 1.4.1 version. However, you can make the changes using a parallel WorkStation running a 1.3 SP1 or 1.3 SP2 version that is connected to the Automation Server running the 1.3 SP1 or 1.3 SP2 version. Full compatibility is supported on Automation Servers running the 1.4.0 version   Additional detail is available on the Online Help http://help.sbo.schneider-electric.com/topics/show.castle?id=9807&locale=en-US&productversion=1.4&a=1 Supported Features: Navigate You can navigate in the system tree of an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, object and property types removed in the 1.4.1 version compared to the 1.3 SP1 or 1.3 SP2 version are not be displayed in the system tree. Search You can perform an object or property search on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, object and property types removed in the 1.4.1 version compared to the 1.3 SP1 or 1.3 SP2 version are not be displayed in the search list. View Events You can view detailed information and perform commands on events on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. The 1.4.1 Enterprise Server will also store events from an Automation Server running 1.3 SP1 or 1.3 SP2 version. View Trend Logs and Trend Charts You can view trend log lists and trend charts on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Extended trend log lists in the server running 1.4.1 version are functional and be able to retrieve values from a server running the 1.3 SP1 or 1.3 SP2 version. View Graphics You can navigate to and view a graphic on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server at 1.4.1 version. Graphic variable values can be changed with Graphics Editor, but configuration data cannot be changed. View Alarms You can view detailed alarm information from an Automation Server running the 1.3 SP1 and 1.3 SP2 version, with WorkStation and Enterprise Server at 1.4.1 version. Also actions on alarms can be performed, such as assigning or disabling an alarm and enabling a Change-state logging. View Dynamic Values You can navigate to and view dynamic values in the Watch pane from an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. However, because there is no way to navigate to and view objects or properties that have been removed in the 1.4.1 version, such dynamic values cannot be viewed. Transfer Values You can transfer values from an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with an Enterprise Server or Automation Server running the 1.4.1 version and the other way around. Change and Force Variables You can change and force variables using properties on an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Lead and Shadow relationships Lead and Shadow relationships work for all objects with the runtime compatibility support. Backup You can make a backup of an Automation Server running the 1.3 SP1 or 1.3 SP2 version, with WorkStation and Enterprise Server running the 1.4.1 version. Log on to the Enterprise Server and then make a backup of the Automation Server running the 1.3 SP1 or 1.3 SP2 version. You can also log on directly to the Automation Server running the 1.3 SP1 or 1.3 SP2 version with WorkStation running the same 1.3 SP1 or 1.3 SP2 version, and then make a backup of the Automation Server.

Issue Within the Network modem object, what settings are required/normal for both the alarm delay and dial parameters windows? Product Line TAC Vista Environment Xenta 901 Vista Modem Manual Cause Problem/tip using modem dial Resolution This depends on the desired functionality. One examples definitions for the TAC Xenta: Dial when priority 1 alarms have been tripped/reset/acked Dial when priority 2 alarms have been tripped/reset Dial remaining alarms only once per day when it is cheaper to dial It always depends on the site requirements. One recommendation is to use at least 5 minutes delay before dial up. Please read the TAC Xenta 901 Handbook.

Issue Requirement for a number of users to be able to access Security Expert using Web Client at the same time. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause Unsure how many Web Client users are licensed with the standard license or how to add additional user licenses. Resolution Included with the base SX-SRVR license is an allowance for having three (3) concurrent Web Client operators.  Additional operator licenses (SX-WEB-OPR) must be purchased to allow Web Client logins beyond the licensed amount of three, purchase as many of these as is required.

Issue Check the host and intermediate certificates with a CA certificate to verify the authentication chain before importing them into EBO servers. Product Line EcoStruxure Building Operation Environment Enterprise Central Enterprise Server Automation Server Edge Server Cause Certificates are provided and can be assigned incorrectly or to the incorrect server; therefore, they do not function as expected. Resolution Verify you have the following: Host certificate in PEM file format Intermediate Certificates in one pem file, not including Certificate Authority (CA) cert CA Certificate where Issuer and Subject Name are the same, indicating it is self-signed. OpenSSL is installed on the computer with the files. Use OpenSSL installed with EBO or install as mentioned in Ensuring the SSL Host Certificate and key file are a matching pair Use this command:  openssl verify -CAfile ca.pem -untrusted intermediate.pem server.pem​ The explanation of the command is as follows: openssl verify: This initiates the certificate verification process. -CAfile ca.pem: Specifies the path to the PEM file containing the trusted CA (Certificate Authority) certificate. -untrusted intermediate.pem: Indicates the path to the PEM file containing the intermediate certificates. They are marked as untrusted because the system does not directly trust them, but their validity will be checked against the CA certificate. server.pem: Specifies the path to the PEM file containing the host server certificate you want to verify. The expected responses are:  server.pem: OK: Verification successful, indicating the server certificate is valid and its chain of trust is established. Error messages: If any errors occur during verification, they'll be displayed in the output. Common errors include certificate expiration, invalid signatures, or missing intermediate certificates Additional information: Ensure the file paths are correct and the certificates are in PEM format Ensure the host and intermediate certificates are installed on the server device and the CA Certificate on the client device. If you encounter issues, double-check the validity of the file permissions and certificates. For more detailed output, add the -verbose option to the command. To check expiration dates, use  openssl x509 -in server.pem -noout -dates

Issue When trying to save a program in the Plain English editor, you receive the message "Infinity controller error: File took too long to open" Environment Plain English editor Cause This is typically caused because the program in the controller is busy executing a command that cannot be interrupted. Resolution A workaround for this issue is: Right-click within the PE panel of the editor Clicking "Configuration..." Set the program state to Disabled, click OK Save your program Repeat the steps above but select Enabled and then click OK

Issue How do you configure the I/A Series R2 LON Tunnel for operation with the WorkPlace Tech Tool software? Environment I/A Series (Niagara) R2 software, release 4.31 or later WorkPlace Tech Tool Software release 5.x Cause Need information on the entire process of configuring the I/A Series R2 LON tunnel software to work with the WorkPlace Tech Tool software running on Windows XP. Resolution There are four parts to configuring LON Tunneling. A. UNC configuration The UNC must be licensed for vlon (in the features line) Install the VLON jar file into the UNC using the Configure Modules function within the Admin tool Installation Wizard. There are no configuration requirements for the VLonService in the UNC. B. Check for an available LON port in WorkPlace Tech Open WorkPlace Tech but do not open a project. From the "Tools" menu, select "Configure Communications" Select the Lonworks radio button then click [Change] Click the pulldown arrow in the "Select a network interface device driver" selection box. Make a note of the LON ports currently defined.  This list will be used when configuring the tunnel on the PC. Click [Cancel] to close the communications configuration process then close WorkPlace Tech. C. Niagara LON Tunnel configuration on PC Download the "NiagaraLonTunnel.exe" module from The Exchange Install the NiagaraLonTunnel service on the Windows XP PC by running the downloaded NiagaraLonTunnel.exe program. From the Windows Control Panel, open the "Niagara App Tunnel" applet and select the LON tab if more than one tab is displayed. In the LON port name field, select a value not identified in step B.5, above. In the Host Address field, enter the IP address of the UNC. You may enter a UNC station User Name and Password in the two fields or those fields may be left blank. If you have entered a User Name and Password, the Silent Mode checkbox may be checked to prevent the LON Tunnel connection window from being displayed each time the connection is established. Click [OK] to close the Niagara Application Tunneling window. In the Windows Control Panel, double-click on Administrative Tools then double-click on "services". In the displayed list, locate "Niagara LON Tunnel", right click on that entry and click "Restart" in the displayed list. Wait for the Service to restart.  If Windows reports that it cannot restart the service, it will be necessary to close all application windows and restart Windows.  After restarting Windows, continue with part D, below. After the service restarts, close the Services window and close the Windows Control Panel. D. Configure WorkPlace Tech Communications. With the WPT application open,  select the "Tools" menu, then select "Configure Communications". Select the Lonworks radio button then click [Change]. Click the pulldown arrow in the "Select a network interface device driver" selection box Select the LON# port name entered in step C.4, above. Check the "This is a VLon device" checkbox. Click [OK] to save the settings. When you attempt to establish communications with the LON network, the "Niagara Lon Tunneling Logon" window will be displayed if "Silent Mode" was not selected in step C.7. If "Silent Mode" was selected in step C.7 and the UNC login failed, the "Niagara Lon Tunneling Logon" window will be displayed to allow entry of a different user name & password. The connection via the LON tunnel is available for use. 

Issue Customize the default graphic that opens after login. Environment Vista Workstation Vista Webstation Cause Vista defaults to a generic view which can be customized. Resolution The Home Graphic can be changed in any user profile, including the default Vista $UserProfile.  A user profile can be used by several users.  To create a User Profile In the folders pane, right-click the root object. Point to New, point to Object, and then click User Profile. Type the name of the object.  Browse the Home Graphic in the new User Profile and update each User properties to use the correct User Profile.

Issue Trying to install SSL certificate via Web browser but the 'Install Certificate' button is missing. Product Line EcoStruxure Building Operation Environment Building Operation Webstation SSL Cause User logged into the machine needs to have administrative privileges to install the certificate. Resolution When running the browser, right click on the browser's icon then select 'Run as administrator'

Issue Error displayed: "Extended logging time synchronization problem. The time on the workstation is less than the time of one or more controller log entries," when Workstation tries to download ExtendedLog data from controllers. Product Line Andover Continuum Environment Continuum Workstation (LAN & SU) NetController (CX99xx , BCX9640, BCX4xxx, ACX57xx) InfinetController (i2xxx & First Generation InfinetControllers) Cause Time setting is different between Workstation and Controllers or the time setting is same but the UTC Offset (Time Zone) is wrongfully set between the WS and the Continuum Network object of the controller. Resolution Set the correct UTC offset (time zone) in all of the below locations: Confirm Cyberstation(s) PC time zone (UTC offset) and Windows regional settings are correct. Confirm the SQL Server PC time zone (GMT settings) and Windows regional settings are correct. In Continuum, the Workstations Device objects Time tab has the correct time zone setting (be aware this is in minutes, ex. GMT+10 = +600 minutes). In Continuum, the Network folder has a setting for the time zone, this needs to be configured to the time zone the controllers are located. If GMT+10 then this gets set to +600. Note: See Configure Time Zone and UTC Offset settings so that time is synchronized across your system for more detail on the various locations for UTC settings and what these are required for. Setup Workstation and Controller Time Synchronization: Synchronize the time on all Workstations to a common source. See instructions in Cyberstation Installation Guide under "Workstation Time Synchronization." Synchronize controller time by creating a Program in one of your Cyberstations (only create on one Cyber). This synchronizes the controllers time to the Workstations time once every hour. There are detailed instructions on this in the Cyberstation Installation Guide (with a sample program) under "Controller Time Synchronization." (Also see Time sync controllers to workstations)

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, fails with the below error being shown. Hardware details do not match Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause The hardware details on record do not match the hardware details of the machine that is trying to be licensed. Resolution Contact support to have the hardware profile reset.

Issue USB LON adapter from Echelon (PS3 Part Number:ECH-75010R) is not recognized by Workplace Tech. Environment USB LON adapter (ECH-75010R) Workplace Tech Cause The ldv32.dll file (Open LDV driver) loaded with Workplace Tech (located in C:\Program Files\WorkplaceTech directory) is an older version of the driver and it does not support USB interfaces. Resolution Download the latest version of the LDV driver (153-0212-01A_OpenLDV340.exe) The latest version of the LDV driver can be downloaded from the Echelon website (www.echelon.com) and it contains support for USB devices. In order to download from Echelon’s website, a (free) user account is required. Once it is created, proceed to “Recommended Downloads” and the LDV driver will be listed (towards the bottom) as "OpenLDV 3.4 Network Drivers for Windows Vista/XP/2000/Server 2003 (includes drivers for i.LON 10/100/600 RNI, PCLTA-20/21, PCC-10, and U10/20". The LDV driver is also posted on The Exchange Download Center. Install the new LDV driver Copy the ldv32.dll file from the C:\lonworks\bin directory, and paste it into the C:\ProgramFiles\WorkplaceTech directory. This driver is required for Workplace Tech version 5.6 or earlier. After installing the driver, Workplace Tech will now recognize the USB adapter.

Issue Sigma server fails when a Data Import is initiated during a Sigma transition Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Sigma Building Operation Enterprise Server Cause Sigma server fails when an EBO data import is initiated. Resolution It is important that the Sigma Database is checked with the Doctor utility (found in SigmaX) before a Sigma transition into EBO is undertaken. Longtext - Longtext file contains 'mandarin' type characters - probably from previous BAS/Sigma upgrades. If the file contains these, then Longtext has probably not been used in the past or not used currently. Delete the file (located c:\sigma\data), it will self re-create. Shorttext - Shorttext contains an incorrectly formatted entry. Find entry and correct. To find, delete 1 -250, if it continues to fails, the entry in question will be in the range 251 to 500 and keep halving until the entry is found. Index A errors - index contains a looping segment, where the page references itself. Correct index as necessary using SigmaX - Doctor. Index A errors - page is referenced more than once, i.e. the index page can be opened via two (or more) routes. Correct Index as necessary using SigmaX - Doctor. Note: the Index should be checked with SigmaX before a transition. Object corruption - open object in Sigma, if it fails to open, then correct by whatever means that is required, Sigma server will fail at a point during the Data Import. Log Sets - Fail to import log sets. To find, in Sigma, locate the logset.rec in the c:\sigma\data\server...folder file, take a copy. In Sigma, delete 50% of the log sets and try the import again. If it fails, delete another 50% and repeat. Or if it succeeds, then the issue may lie in the 50% of log sets originally deleted, re-instate these using the copied logset.rec file and try again by deleting the other 50% and so forth.

Issue After successfully downloading a Menta application directly through the serial connection, the pop-up window below is displayed:  tam32 No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network! Product Line TAC Vista Environment Directly connected Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The blueprint is also called an .NDB (network database) file.  It contains network information that allows the controller to communicate to other controllers or I/O modules.  When downloading a Menta application directly, this warning is displayed as a reminder that that necessary network information has not been included in the application-only download. Resolution If the controller is running stand-alone and no networked communication is required, then no further action is required.  The message is only a warning alerting the user to the fact that the NDB file has not been included in the download. If the controller needs network variables and I/O module communication, follow the direct download (most often done only for troubleshooting purposes) with a download from the front end Vista Workstation for classic networks Vista System Plug-In for LNS networks If no front end exists, but network communication is still required (most often for I/O modules), lonTool32 is a suitable work around for those rare instances.  See Using lontool32 to download a stand-alone controller.

Issue Replacing Satchwell Sensors with Schneider Electric part numbers Product Line Field Devices Environment Sensors Cause Cross referencing older 'T' type sensors to the current version. Resolution Outside Sensor DOT2301 , DOT0001, DOT0002 is now STO600 Immersion Pipe Sensor DWT1701 (125mm), DWT1702 (200mm), DWT0001 is now STP660 (note, if replacing sensor only then DWA0001 required). Strap On/Pipe Contact Sensor DST1601 , DST0001 is now STC600 Duct Sensor (mainly FCUs) DDU1803 , DDU0001 is now STD670 Duct Sensor DDT1701 (300mm) , DDT1702 (460mm) , DDT0001 is now STD660 Room Sensor DRT3453 (sensor only, no setpoint adjust) is now STR600 For other DR and DRT sensors see Replacements for Satchwell sensors Drayton Room Sensor A701 is now STR600D Drayton Outside Sensor A702 is now STO600D Drayton Immersion Sensor A703 is now STP600D Drayton Strap On / Contact Sensor A704 is now STC600D

Issue What virtual environments are supported for use with Security Expert? Product Line Security Expert Environment Security Expert Microsoft SQL Server Cause Which specific virtualization software has been qualified to work with Security Expert? Resolution No specific virtualization software has been qualified with Security Expert. The Security Expert Compatibility Matrix describes support for Virtual Environments as the following.   The Security Expert server is supported on Virtual Server Environments. However, Schneider Electric reserves the right to request customer replication of any errors in a non-virtual environment. When installing under virtual server environments special care must be taken to ensure that the system requirements are met by the virtualized hardware. The VM must be carefully reviewed with regard to resource and performance before completing any installation.

Issue A replacement for VisiView is required. Environment Satchnet VisiView Cause The VisiView software is now obsolete. Resolution VisiView can be replaced using a SmartStruxure Automation Server or TAC Xenta 555 Web server. Both the SmartStruxure Automation Server and the Xenta 555 provide web interfaces so that the customer can view their HVAC equipment graphically using an appropriate Web browser. Both the SmartStruxure Automation Server and TAC Xenta 555 Web server communicates with either IAC or Micronet controllers. Further information on the Micronet Transition to SmartStruxure can be found in PA-00228 The Xenta 555 is programmed using TAC Xbuilder, which allows data to be presented in a graphical format. Further information on the Xenta 555 can be found here.