Building Automation Knowledge Base

Issue Need to know Electromagnetic Compatibility for Power Supply PS-24V Environment AS PS-24v Cause Electromagnetic Compatibility Resolution Please have a look at the attached document for Electromagnetic Compatibility test report  --Report--

Issue When trying to upgrade a database to version 1.5 or 1.6 the upgrade fails Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause There can be various reasons for the upgrade failing. At this moment there are two known issues: Issue with specific LonWorks devices such as the T-Stat T7300 Too complex or long list of email addresses in notification objects Resolution Solution for issue 1: Issue with specific LonWorks devices such as the T-Stat T7300 Contact Product Support and ask for hotfix 1.5.0.4801 Solution for issue 2: Too complex or long list of email addresses in notification objects Make a search for all email address objects searching for "EmailAddress" - You can import this search object to do it. Copy all rows to this Excel sheet Check the "Count" column - it counts the characters in the "Property value" column. There's no exact max character count as it also depends on complexity of the addresses, but a good indicator is if the count is over 270. In SmartStruxure, delete the content of the objects having more than 270 characters. Carry out the upgrade (if the upgrade fails, go back to step 3 and delete the content of all objects where the count is 260) After upgrading copy the property content from the Excel sheet back to SmartStruxure

Issue Changing a Sigma value from a graphic. Environment Object Override Graphic Slider Cause From an imported or transitioned Satchwell Sigma graphic it is possible to override an object value, from a StruxureWare Building Operation Trackbar graphic, it is not. Resolution Sigma's objects are unusual, in that they are not writable. To change their value you have to force them, (or manually override them in Sigma terms).  This means that the standard "Trackbar" component that comes with StruxureWare Building Operation, will not work with Sigma. To manually override the Sigma object, the existing "Trackbar" can be modified to call "setForce" on the object .  This is what legacy Sigma normally does if you have a slider on a graphic, and move the slider. It sets the object to a manual override state. The standard "Trackbar" component can be changed to make it work with Sigma objects. To do this, the "setForce" line was added to the function "setCurrentValue",  setForce(fullName, true);  return setValue(fullName, value);  Note:-  As with legacy Sigma, StruxureWare Building Operation Transitioned Sigma only supports changing certain values.  For example:- You can't make a graphic change the alarm high limit. You can't make it change the configuration value "Fixed value".  The modified "Trackbar in the StruxureWare Building Operation graphic must be bound to the "Value" property, just like it would have been in legacy Sigma.  It is not valid to bind it to the configuration value. To download a copy of the modified "Trackbar", please click HERE.

Issue When using the STR-350/351 in SmartStruxure Function Block Editor some programming consideration must be made to keep the occupancy and setpoint in sync between the stat and the program. Product Line EcoStruxure Building Operation Environment Function Block Editor Workstation STR350 STR351 Cause The STR-350 does not have a configurable Bypass time setting so this must be done using Function Block programming. STR-350 also takes roughly 30 seconds to recover from a power failure. By storing the last known setpoint in a DELR block with the "backup" option set, the setpoint will be restored. Resolution Click the pictures of the Function Block macro below to download the source file. Unoccupied Bypass In order to allow for local override commands from the stat, the occupancy must be read in from the STR-350. By allowing the programmable controller to control both the schedule and the override, the stat stays in sync with the program. The Bypass button of the STR-350 will only toggle the output of the nvoOccManCmd if the input nviEffectOccup matches the current button value. Setpoint The setpoint requires a little bit of extra programming to account for a power failure. The stat will report invalid setpoints for the first 30 seconds, which will cause it to come back in an undesired state. By letting the Function Block program hold onto the last known setpoint, and write it back to the stat on power up, there is no change in the setpoint after a power loss. Looping the setpoint in/out from the stat keeps everything in sync with the program, including stat adjustments. Note: If these macros are going to be used with a STR-350/351 set in degrees Celsius; make sure to change all initial values within the setpoint range. If the initial values are outside of the setpoint range, then the setpoint will always default back to the last known value.

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

Issue You want to search for a specific LonWorks device in the database Product Line EcoStruxure Building Operation Environment Lon Cause You might have a duplicate Neuron ID Resolution Make a new search right clicking the LonWorks network and then selecting "New" > "Search" Write an asterisk (*) in the search field Click "Advanced Settings" In "Include types:" select the type you want. Either select the specific device template, or just select all device templates. In "Conditions:" enter the neuron ID or other criteria you want to search for. Now click the search button, and you should find the device you are looking for. Here is an import file with a search sample.

Issue On rare occasions you will get an error during the installation of Echelon OpenLNS Server on Windows 8.1 64 bit saying that the installer can't create specific registry keys. Product Line EcoStruxure Building Operation, Other, TAC Vista Environment OpenLNS Windows 8.1 64 bit Cause The user does not have permission to access those registry keys. Resolution Add the registry keys manually. Alternatively, run OpenLNS on Windows 8.1 - Registry paths.zip reg file that will add the keys. Run the installer again.

Issue Status does not change. Environment CT current transformer H909HV-S6 Cause Although current flow is present, the current transformer status does not change. Resolution This issue was caused by the incorrect wiring between the Current Transformer and the DDC controller. To clarify this, please see below. The drawing shown as part of the installation instructions appears to show that four connections to the DDC controller are required, this is not connect, only two are required. The status output connections consist of two terminal sets, but only one connection is required from each. To download the H909HV-S6 datasheet please click HERE.

Issue XIF files for Version 1 and Version 2 of MNL controllers Product Line EcoStruxure Building Operation, TAC IA Series Environment SmartStruxure with MNL Cause Not available on other online resources Resolution Download the zip file available here for the following profiles:

Issue Vulnerability affecting certain versions of OpenSSL. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment OpenSSL Cause Software vulnerability Resolution Information and Customer Statement located at the following link on the community: Schneider Electric Security Statement Regarding the Heartbleed Vulnerability. A corporate statement on this can also be found here: Schneider_Electric_Heartbleed_Customer_Statement_APR_15_2014.pdf.

Issue E-mon D-mon Modbus Meter in StruxureWare Building Operation Environment Modbus Cause The Modbus device object in StruxureWare Building Operation requires a single poll to query to get its online status. This device will only respond to polls when 2 or more registers are polled. Resolution Create the Modbus Device Object Edit the Properties Set the poll register to 4001 Set the Poll Code to 03 Please see the attached guide for the complete register list for this device. Please note that this poll register is listed in the manual as 44001

Issue When opening I/NET on a secondary monitor, and open the point control window of I/NET summary for a digital output, the drop list for the point doesn't work. Nothing is shown in the drop list. Product Line EcoStruxure Building Operation,TAC INET Environment I/NET SmartStruxure Cause There is a 3rd party system dll file out of date for I/NET. Resolution There is a 3rd party system dll file under the folder C:\Program Files\INET Seven\Program Files (Program Files (x86)) if for a 64 bit Operation System called SftBx32.dll. Click here to download the new dll file and extract it. Close I/NET IO Server and SmartStruxure Enterprise Server Copy this new dll file and replace the old one under that path. Start I/NET and SmartStruxure again, and it should work now.

Issue Programming an application that requires a setpoint and deadband that operates in the same manner as the WorkPlace Tech Tool Thermostat object. Environment SmartStruxure AS or ES Cause No object exists in the Function Block library that is functionally equivalent to the I/A Series WorkPlace Tech LON/BACnet "Thermostat" object.   Resolution This is only one of several methods by which a differential type thermostat object can implemented in Function Block programming. The following Binary Expression (XPB) function block object can be used to simulate the differential type thermostat. Analog Input A is the "Input" Analog Input B is the "Setpoint" Analog Input C is the "Input Differential" Binary Input d is the "State Feedback"  This feedback link insures that the output state does not change when the input is within the range specified by the input differential The output of this object turns on when the Input value exceeds the Setpoint + 1/2 of the Input differential. The output of this object turns off when the Input value falls below the Setpoint - 1/2 of the Input differential. The xml file can be downloaded from here.

Issue Performing an action that normally starts WorkPlace Tech Editor or Monitor does not start the tool. A warning message is displayed. Schneider Electric StruxureWare has stopped working A problem caused the program to stop working correctly. Please close the program. Product Line EcoStruxure Building Operation, TAC IA Series Environment SmartStruxure WorkStation SmartStruxure WorkPlace Tech Editor and Monitor program Cause .NET support not enabled in Visio Resolution Enable the .NET programmability support in Visio. as documented in Section 4.6 of  the SmartStruxure WorkPlace Tech Editor and Monitor manual. Open Windows Control Panel Click Programs and Features In the list of programs, select Microsoft Office Visio and then on the File menu, click Change In the Change your Installation dialog box, select Add or Remove Features and then click Continue On the Installation Options tab, expand Microsoft Office and then Microsoft Office Visio Click .NET Programmability Support, select Run from My Computer, and then click Continue Windows reconfigures Microsoft Visio. When finished, click Close

Issue  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope. Environment Infinet Field Bus MSTP Field Bus Cause Documentation Resolution See  Evaluating Signal Levels on RS-485 Field Bus with an Oscilloscope.pdf

Issue MBus to Modbus TCP Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Mbus Modbus Cause How to read MBus devices into a BMS System using Modbus TCP Resolution There are different methods, but these are generally using a Modbus RTU / Mbus gateway and then converting it to Modbus TCP. The following ADFweb solution allows Mbus to be read directly into a Modbus TCP device. Click here for the datasheet.

Issue Need information on securing a building automation system. Environment Best practices Cause End user has requested assistance for their IT department to secure the building automation system. Resolution Click here to get a copy of Best_Practices_for_Securing_an+IBMS_WP.pdf,  a white paper written by Schneider' Electric's Buildings BU IT Security Group. This also located on the Download Center here

Issue Configuring a Smart Sensor in SBO. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operations b3xxx Controllers Smart Sensor (LCD or LED) Cause Unsure how to program for a Smart Sensor in SBO. Resolution Some considerations to be aware of first; Object naming differences Programming of the Smart Sensor is very similar to the old Plain English programming used in Continuum. One of the main differences is that each input must be specifically defined at the start of the program. Depending on the version of SBO, there may be some other considerations with setting up/reading the LcdDisplay array by renaming of the BACnet AnalogValue's to remove the "_AV" from the BACnet name. This naming issue affects SBO v1.4. Specific variables for Smart Sensor to be used in Plain English programming. Here is an old Smart Sensor Installation manual that will help explain which objects need to be created and how they work in the controller to enable the LCD display. Create the LCDDisplay and SpaceTempSP as numerics and any other objects that are not already created as InfinitySystemVariables. See "Configuration and Programming" section in the manual starting on page 14. Also note that the sensor will not light up until values are written to it. Sample Plain English code. LCDDisplay (or LEDDisplay) is not automatically created. Create this numeric and assign it as an array with 8-elements.  If it is an LCD Smart Sensor, then create a numeric and name it "LCDDisplay" and set its logsize to 7 (this configures it as an array with 8 elements from 0 to 7). If it is an LED Smart Sensor, then create a numeric called "LEDDisplay" instead. After creating this numeric you should be able to create the PE Program successfully. The simple program below will show the current spacetemp (LcdDisplay[1]) in two decimal place format (LcdDisplay[2]) when the Display key (LcdDisplay[0]) is pressed. The degrees symbol (LcdDisplay[7]) is also shown. Consult the Smart Sensor Installation and User Guide starting on page 16 for more details on how these values are configured. Numeric Input SpaceTemp Numeric Output LcdDisplay Initialise: LcdDisplay[2] = 0 If LcdDisplay[0] = 4 then Goto ShowTemperature ShowTemperature: LcdDisplay[1] = SpaceTemp LcdDisplay[2] = 12 LcdDisplay[7] = 1024 If TS > 30 then Goto Initialise In SBO, do the following under the Application section of the b3 controller: Create a BACnet Analog Value object in the b3 called "LCDDisplay". Go to the Advanced tab and under the Log Settings section change Log Records to be 7. Save the changes. Create the program and add the above PE Script. Add the binds to the LCDDisplay object created in step 1, RoomTemp input, and any other objects used in the program.

Issue Is it possible to use Sysman Alert Server with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Alarms and Events Cause Customers may wish to send important alarms to duty staff via SMS. Sysman Alert Server is one way of doing this and is easy to configure.  Resolution This is possible. The following document details the setup procedure: Sysman Alert Server with StruxureWare Building Operation The configuration will depend on the setup and location of the SysMan Server, but will generally involve "Write to File" Notifications if the Enterprise Server and Sysman Servers are installed on the same PC, or Emails to the SysMan Server (from Enterprise or Automation Server) More information can be found on Sysman's website. Part Numbers: SysManSMS ALERT SERVER: 900800600 SysManSMS GSM Modem: 900800610 In the UK when ordering please use the below part numbers. SysManSMS ALERT SERVER: 802000 SysManSMS GSM Modem: 100002

Issue Is there a SmartStruxure specification that includes a piece for Network 8000 migrations? Environment Network 8000 Cause sales request Resolution The document is available on the Buildings Business Extranet, under Products > SmartStruxure solution > Sales > Guide Specification. It's a Word doc so it can be modified to suite the desired needs. The current version is 1.4 and is available here for convenience.