Building Automation Knowledge Base

Issue Communication issues between the Enterprise Server and Automation Servers result in an offline status of the AS. More information is required on how this status is detected.  Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause An AS behaves as if it is online yet shows up as offline in Workstation.  Resolution As of 1.5.0.10001 there is a new model for detecting online / offline servers. Prior to 1.5.0.10001 When a communication error was detected the Automation Server was marked as offline. As of 1.5.0.10001 and Newer An immediate DetectOnline call is scheduled. Only after three failed DetectOnline with an interval of one second we consider the  server to be offline. When offline an alarm is generated.and set the offline status as normal, and also go back to one minute interval for online detection. In 1.5.0.10001 the number of retries and interval is possible to set in server.properties. From 1.6.0 this is configurable from WorkStation. *** Server Communication folder is hidden in more recent versions of SBO See Also: How BACnet b3 controllers are established as being Online / Offline How the communication status of BACnet devices are verified

Issue Trying to order a controller part number that has been discontinued due to low volume sales / duplicate part numbers. Product Line Andover Continuum Environment Continuum IP level Controllers NetController II Series bCX1 Series ACX Series Cause Discontinuation of duplicate and low volume parts has removed a number of previously existing part numbers from the Continuum catalog. These parts are still available but will need to be ordered as a base unit and then upgraded through Repairs. Resolution The IP level controllers were part of a roll up of the product numbers where low volume part numbers were discontinued. These parts can still be obtained but will need to be chosen from the list of available parts and then get an upgrade through Repairs to add the additional features that may be required. See Active Network Level Controller Part Numbers, and Discontinuance of Low Volume Part Number Configurations - Andover Continuum - PA-00269A on this which includes the currently available part numbers. To order a BCX1-CR-127-SA part which is no longer available, you will need to order the base unit BCX1-CR-127 and then have Repairs add the -SA (SNMP) option to that controller. Note: for further Continuum parts that have been discontinued see What Continuum products have been discontinued?.

Issue How to enable and use the HTML5 Viewer instead of the Java Viewer in SmartStruxure WebStation Product Line EcoStruxure Building Operation Environment WebStation Cause Starting with SmartStruxure WebStation 1.6.0 there are HTML5 viewers available for both graphics and trends. However, the Java viewer is the default so the HTML5 viewer must be enabled. Resolution Note: As of WebStation version 1.6.0, the HTML5 viewers are still in beta and still have some compatibility issues. To use the HTML5 viewers take the following steps: Log into WebStation On the upper right-hand side click on Settings Check the Use HTML5 viewers option

Issue Is there a way to concatenate access events from two Personnel objects into one Personnel object?  Environment Continuum Cyberstation Cause A Personnel object had a history of events and was then mistakenly recreated as a duplicate object. The original object was disabled and new events have now been tied to the new duplicate Personnel resulting in events for the same person being spread across two Personnel objects. Resolution The Access events produced are linked to each individual Personnel object that created them. There is no way to transfer these events from one Personnel to another.

Issue When sending BACnet devices to database the operation does not return an error but NO objects (or only some objects) are created in the DB. Inspection of ACCTrace shows the following... In the case at hand the device had 28 objects which the system identified correctly as seen below, but trying to add each object to the database resulted in error inserting the object in the dictionary. Error inserting a row into the object dictionary. [Microsoft][ODBC SQL Server Driver]Maximum stored procedure, function, trigger or view nesting level exceeded (limit 32) Product Line Andover Continuum Environment CyberStation Cause The ContinuumDB's recursive triggers property has somehow been changed to ON (1) from its default of OFF (0) The following query can be used to determine what the value of the property is using SQL Management Studio select DATABASEPROPERTYEX ('ContinuumDB', 'IsRecursiveTriggersEnabled) Resolution Close all Continuum workstations Reset recursive triggers to its default of OFF with the following query using SQL Management Studio ALTER DATABASE ContinuumDB SET RECURSIVE_TRIGGERS OFF

Issue Cannot interface to the GE Lighting Control Panel PSLP Object nviPattern and nvoPatternFb with G3 lonGe-3.8.37.  Network variables nviPattern, nvoPatternFb, and nciChannelCfg are missing from the proxy points within the object definition. Environment I/A Series G3 - 3.8.37 Cause Network variables nviPattern, nvoPatternFb, and nciChannelCfg are based upon manufacturer types (GEPatternType and GEChType) and are not properly defined in the lonGe 3.8.37 module. The pslp object within the lonGe module generates warnings when added. WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nviPattern WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nvoPatternFb WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_0 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_1 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_2 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_3 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_4 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_5 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_6 WARNING [09:03:14 16-Dec-14 CST][lon1.DynaDev] No lonData for PsLp.nciChannelCfg_7 Resolution Upgrade to lonGe-3.8.38.1.   The updated module is available for download from the Schneider Electric Download Center. https://ecobuilding.schneider-electric.com/search?documentUUID=c52247c8-921b-4f51-90cf-d8d79adc93b7&title=lonGe%203.8.38.1%20-%20G3%20Firmware

Issue Unable to launch Continuum Reports Suite on a Windows 7 64-bit workstation Product Line Andover Continuum Environment Windows 7 64 bit workstation Cause "Continuum_Reports" directory permissions Invalid "Reports.exe" launch path in PE Program "Reports_Suite" (or other PE Program) is Disabled Attempting to launch Continuum Reports directly Resolution "Continuum_Reports" directory permissions Log into the workstation with Administrative privilege Edit the "Continuum_Reports" directory properties Click on the "Security" Tab Click on "Edit" button Highlight "Users" Click on the "Allow Full Control" checkbox Click on "Ok" button Invalid "Reports.exe" launch path in PE Program Edit PE Programs, such as "Reports_Suite" Change the statement: RepPath = "c:\progra~1\continuum_reports\" -to- RepPath = "c:\progra~2\continuum_reports\" Save change Enable the PE Program if Disabled "Reports_Suite" (or other PE Program) is Disabled Edit the PE Program Review the Program Configuration Enable the Program if Disabled Run the PE Program Attempting to launch Continuum Reports directly Continuum Reports cannot be launched directly from the Windows Explorer by double-clicking on "Reports.exe".  Continuum Reports are launched by running a workstation PE program from a Menu Page button or a Pinpoint button

Issue Necessary settings must be made to enable the SBO Exception Shedule Environment Exceptions in an SBO Schedule Cause Incorect settings on the Exeption Schedule Resolution   Adding a "Holiday Calendar" reference as an Exception to a schedule, an initial value of zero and "no end time" must be checked by editing the green area shown in the example below.

Issue When editing a Script program, the Automation Server or Enterprise Server crashes when clicking "Save." After that, the connection is never restored to the server. The server needs to be formatted, software reloaded, and a backup restored to it. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.0.0 to 1.5.0 Cause In SmartStruxure 1.5.0 and earlier, publics were not supported in Script functions although they could be used. If used, the server will crash in some cases and render the database unusable. Resolution The workaround is to not use publics in Script functions in the affected versions. The issue is solved from version 1.6 RC.

Issue Which version of USB serial leads work with Sigma and BAS Environment Sigma BAS Cause Newer laptops do not have an onboard RS232 serial port. Can a USB-Serial converter be used. Resolution Not all types of USB to serial converters work with Sigma and BAS2800+. USB to serial converters work in conjuction with the laptop. Local testing may have to be done to find the best product. Generally, USB to serial leads have 2 version of chipsets, Prolific and FTDI. Note, there are also fake versions of these chipsets, the original versions are available from RS and other well known distributors. Sigma seems to work only with Prolific converters and can work on a low COM port no. e.g. 1, ensure that the comm port is not in use by any other applications e.g. Bluetooth. For Sigma, remember to change the setting in the sigma.ini file when using serial communications. BAS seems to work only on FTDI converters and can work on high COM port no. e.g. 7.

Issue The discontinuation of the SVT controller due to component obsolescence. Product Line Field Devices Environment SVT Optimiser 4201 4251 Cause What replacements are available for the SVT 4201 / 4251 controllers? Resolution Important Note - The replacement controller mentioned in this article is no longer available, and therefore a replacement for the SVT 4201 / 4251 is not available. The SVT controller range has been discontinued due to component obsolescence. The SVT controller was a basic optimiser that performed the start calculation using only an internal temperature sensor. There are no exact replacements for this controller available. What is available? The Schneider Electric DC1400 Optimiser / Compensator is the recommended replacement, but this is not a direct replacement. Differences in the controllers. The SVT controller provides only an optimum start, the DC1400 provides optimum start and stop. The SVT controller uses only a room temperature sensor for the start calculation, the DC1400 uses only a room temperature sensor and an outside temperature sensor for the start/stop calculations. The SVT controller has a dedicated "Boost" relay, which allows overriding of a CSC compensator, and control valve. This is an internal function with the DC1400 optimiser/compensator. The DC1400 has many other built in functions.   Controller wiring - Modifications will be required. SVT general wiring connections. Relay R1 is the main plant relay and relay R2 is the boost relay. To see the full controller details, please click SVT Optimiser DS2001 0210.pdf DC1400 general wiring details.   To see the full controller details, please click DC1400 DS2044A.pdf Controller Sensors As already indicated, the SVT controller uses only a space temperature detector, and this sensor is NOT suitable to use with the DC1400. The DC1400 controller will, as a minimum, require a room temperature sensor and an outside temperature sensor, meaning that extra wiring for the outside temperature sensor, and the sensor itself, will need to be installed. For details on suitable sensors, please refer to What sensors does the DC1400 optimiser/compensator require?

Issue Communications with IP devices does not work. Environment IC3-Modbus Modbus IP devices Cause The IC3-Modbus is configured to poll two IP Modbus servers, but only the first configured server communicates. Resolution The IC3-Modbus uses a Gateway.txt file to list the Modbus IP servers, and the registers required. This file consists of general setup information and a section where the servers and registers are listed.  Note that the Sigma objects but be sequential in the list. Final section of the Gateway.txt file. ; 7  Min Value (output objects only, 0 for inputs) ; 8  Max Value (output objects only, 0 for inputs) ; 9  Hardware Alarm Message Suppression Flag (optional), ;   0 = Don't suppress,   1 = Suppress ; read a single 16 bit register ;51,1,4,062,1,1,0,0,0 ; read three 16 bit consecutive registers to objects 52, 53, 54 ;52,2,4,065,1,3,0,0,0 ; read two 16 bit consecutive registers to objects 55, 56 ;55,1,3,101,1,2,0,0,0 ; read two 16 bit consecutive registers containing un-swapped 32 bit unsigned data ;68,2,3,110,1,0x0102,0,0,0 ; read two 16 bit consecutive registers containing swapped 32 bit unsigned data ;70,2,3,112,1,0x1102,0,0,0 ; read two 16 bit consecutive registers containing un-swapped 32 bit signed data ;72,2,3,114,1,0x0202,0,0,0 ; read two 16 bit consecutive registers containing swapped 32 bit signed data ;74,2,3,116,1,0x1202,0,0,0 ; read two 16 bit consecutive registers containing un-swapped 32 bit float data ;76,2,3,118,1,0x0302,0,0,0 ; read two 16 bit consecutive registers containing swapped 32 bit float data ;78,2,3,120,1,0x1302,0,0,0 The section below lists the input objects, which consist of a number of fields, the fields are made up as follows; 1   Sigma Object Number, 2   Controller Address 3   Modbus Command ( 3, 4, 16, 144) 4  Register Address 5  Min time in seconds before polling same controller (Default 1 second) 6  Number of consecutive objects to read (inputs objects only, 0 for outputs) 7  Min Value (output objects only, 0 for inputs) 8  Max Value (output objects only, 0 for inputs) 9  Hardware Alarm Message Suppression Flag (optional), Notice that the Sigma object numbers are in sequence, they must be sequential. 52,1,3,0x804,1,0x1102,0,0,0 54,1,3,0x808,1,0x1102,0,0,0 56,1,3,0x80C,1,0x1102,0,0,0 58,2,3,0x810,1,0x1102,0,0,0 60,2,3,0x814,1,0x1102,0,0,0 62,2,3,0x818,1,0x1102,0,0,0 64,2,3,0x81C,1,0x1102,0,0,0 OUTPUT 111,1,144,0,1,1,0,100,0 112,2,144,0,1,1,0,100,0 113,1,16,4,1,1,1,30,0 ; Controller to IP address mapping table (Serial comms will ignore this table) ;   1 - Controller Address ;   2 - IP address of the Controller or the gateway/router to access the ;       controller IP_ADDRESS_TABLE Configure the Controller IP addresses. 1,10.158.100.114 2,10.158.100.205 ; End of Gateway.txt file. Do not write below this line.

Issue Manually add individual components to a Component Library Environment TGML Graphics Editor Cause Components are sometimes stored as a file type TGMLCOMPONENT File with the extension .tgmlcomponent file. Resolution Open the Graphics Editor and Select a Component Category you wish to add components to Open Windows Explorer and browse to the .tgmlcomponent files. Drag the file(s) from Windows Explorer to the the TGML Graphics Editor Component Category window. Click OK or press enter to acknowledge each file as it is added.

Issue What are the Continuum door's attribute which values persist for ONE scan only. Environment Plain English Cause Documentation Resolution DURESS VALID ACCESS VALID ATTEMPT ENTRY EGRESS VIOLATION INVALID ATTEMPT DATABASE FAULT ENTRY KEYPAD TAMPER EXIT KEYPAD TAMPER

Issue The Modbus communication stops from time to time, and never gets back until the COM port is reconfigured. The device is still online; it is only the values that will not update. This is usually only an issue if Modbus groups are used. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.5 Automation Server Cause If a trendlog with a very long sample time (e.g. 1 hour) is set to log a point and nothing else is bound to the Modbus device, all values from the device will be updated at the same interval as the trendlog. This is solved in newer versions. Resolution Add a single Modbus point to a new Modbus group. Set the group poll rate to the same as the Device poll rate. To enable polling of the Modbus point, add an alarm that will not activate. This will result in polling of the device at the group poll rate.

Issue The value of DateTime will different depending on how the variable is declared Differences between DateTime declared as a local variable and as input, output or public in Script program Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Script Editor Cause Local and bound variables will initialize differently Resolution Local DateTime variables are local and known only to the Script program or function, and are initialized to the current local date-time value of the sever in which they  execute. Binding variables, including Input, Output and Public variables, are not effected by the Script engine by default. The EBO system uses the 1/1/1970 date as default and the Script simply uses that. If a different initial value is required then one can be set in the script

Issue If a binding variable is commended out in the program when the line is put back the binding is gone. Consider the following program... TheOUT3 binding variable is commented out... If the comment is removed and the line restored, the corresponding binding is NOT restored. Environment Workstation Script Cause Documentation Resolution This is functioning as designed, if the binding variable is removed in the program code, the associated binding is removed to avoid leaving an orphan binding. When the comment is removed and the binding variable is put back, you will need to re-bind it as SBO does not keep track of deleted bindings and can't automatically restore it.

Issue After completing the installation for 2.0 WebClient the first attempt to logon results in HTTP Error 500.21 Internal Server Error logging into WebClient. Trying to register .NET 2 using aspnet_regiis.exe produces  ASP.NET setup custom has stopped working. Product Line Andover Continuum Environment WebClient Cause .NET 4 not registered with IIS Resolution Register .NET 4 with IIS from Command Prompt (NOTE: Run command prompt as administrator)

Issue After updating FireFox to version 34 and later, you get the message "Unable to Connect Securely" when accessing a Xenta Server using HTTPS   After updating Chrome to version 40 and later, you get the message "This webpage is not available" when accessing a Xenta Server using HTTPS   In Internet Explorer, you get the message "This page can't be displayed" when accessing a Xenta Server using HTTPS Product Line TAC Vista Environment Xenta Server FireFox Chrome Internet Explorer Cause From version 34 of FireFox and version 40 of Chrome, SSLv3 is disabled by default for security reasons as SSLv3 is no longer considered secure enough. As per Vista Server Cryptographic Protocols TAC Vista, TAC Xenta Server and TAC Xenta 911 is using SSLv3 and is therefore blocked when using SSL (HTTPS). In the newest versions of Chrome and FireFox, not even the work around described below works, so you need to set the Xenta Server to low security through the XBuilder project. Resolution In Internet Explorer, FireFox and Chrome you can manually reenable SSLv3.   Solution 1: Set the Xenta server to only use HTTP and not HTTPS This is done in TAC XBuilder   Solution 2: Allow SSLv3 in FireFox 1: In the FireFox address bar, write about:config 2: Accept the warning 3: Write security.tls.version.min in the search field - below you can see the default setting 4: Double click the line, and change the number to 0 5: Try logging into the Xenta Server again. If it doesn't work the first time, restart the browser and try again   Solution 3: Allow SSLv3 in Internet Explorer Check the advanced settings in Internet Explorer. SSL 3.0 must be enabled. If it's not, then enable it. If you can't, it's because it's disabled by a policy, and you need to get the IT department to enable it.   Solution 4: Allow SSLv3 in Chrome 1: In the Chrome address bar, write chrome://flags/#ssl-version-min and select SSLv3 in the drop down box. Solution 2: Allow SSLv3 in FireFox 1: In the F

Issue It is not clear how to register a SmartStruxure system, and what information to write in case it's not a customer site (For example a test bench/controller or engineering PC). Product Line EcoStruxure Building Operation Environment S2Connect Workstation Cause Guidelines are needed regarding how to properly register a system. Resolution Starting in SmartStruxure 1.5, we have introduced a registration process to know more about SmartStruxure systems. In order to know our customer and/or partner better and provide better services we should register our SmartStruxure system with correct information. The SmartStruxure registration process requires a Buildings Exchange account. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Please make sure below points while registering SmartStruxure system. Test site: If you are registering a test site to test registration process, write "[Test]" keyword in Site note*. Demo site: If you are registering a site which is for demo, then write "[Demo]" keyword in Site note. Training site: If you are registering a site for training or you want to explore registration process, then write "[Training]" keyword in Site note Customer site: if you are installing an actual site for customer then DO NOT use above keywords in Site note field *Site note field can be found under Site Administrator tab (Shown below in screen shots) New system registration: If you are registering new system then you continue enter all information in Step 1 and continue to Step 2. In Step 2 you will find a Site note field. Fill the Site note field as explained above.  Already registered system: If you have registered your site without providing above explained details then you can browse to below website https://registration.smartstruxure.schneider-electric.com After successful login; Navigate to Systems -> Site Administrator and click on Edit button, now you can edit Site note field. Registration Process Does Not Complete In some cases after registering either the Enterprise or Automation server, it still prompts you to register when you log back in. There are two different procedures that can be taken to correct this issue. Procedure 1 - By editing the registration and clicking submit again, it can help the system complete the registration. Log into the sever again and either click Register now on the initial prompt or go to Help > Registration once you are in Workstation. Log into the Registration Portal. If you have issues creating, activating or using a Buildings Exchange account, refer to Register for The Exchange. Select the server that is experiencing the issue on the right side of the window. Click Edit. Click Submit. Procedure 2 - If procedure 1 still does not work, then the registration can be completed manually by entering the Registration code in the offline mode. Log in to the Registration portal directly through this link (registration.smartstruxure.schneider-electric.com). Select the server on the right hand side of the screen that has the registration issue. Take note of the Registration code. Insure that the Enterprise or Automation server does not have internet access and log into the server with Workstation (In the case of an Automation server you will need to connect directly to it via Ethernet). Click to Register now (Since the server does not have internet access, it will automatically launch the offline registration). Insert the Registration code the three fields provided and click Register now. Also check out the SmartStruxure Solution Connect (S2C) - SmartStruxure Product Registration Registration Quick-help video on the Exchange.