Building Automation Knowledge Base

Issue It is not possible to bind a point in a Function Block program to the RelinquishDefault property of a BACnet Multistate value in an SE8000 controller. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation(SBO) 1.6.1 SE-8000 series Room Controller Cause In some circumstances the user may wish to change the value from both the HMI in SE8000 and from a Function block program in SBO, and in this case the RelinquishDefault property must be used. Resolution A possible workaround is to use a LUA script in the SE8000 controller. Idea 1: Write a LUA script that will check if the Priority array (ex. priority 16) value has changed for the list of points that the user wants to modify. If there is an entry in the Priority array, have the LUA script copy that value to Relinquish_default, then relinquish the corresponding priority array entry. Idea 2: There are 6 LUA "scratchpad" BACnet AVs that the user can write too. When the LUA script sees a change in those AVs, it can copy the value to a specific AV's relinquish default. For example, scratchpad AV25 can be used to "shadow" a setpoint. So when AV25 changes, the LUA script will copy the present value of AV25 into the Relinquish_default of whatever the Setpoint's AV is. Example of the LUA script in the SE8000 controller for the above: If value AV25 is bigger than 0, the value of AV25 is written on AV39 Relinquish_default property (priority17) and then AV25 is set to 0. if ME.AV25 > 0 then ME.AV39_Present_Value[17] = (ME.AV25/10); end ME.AV25 = 0 LUA programming guide for SE8000 Room controllers

Issue Can the old Robertshaw T99 temperature sensors be integrated to SBO? Product Line EcoStruxure Building Operation, TAC IA Series Environment SBO all versions Cause Retrofit job installation Resolution According to the RTD-DI-16 specification sheet, the T99 sensor can be integrated to SBO as follows with some limitations. Configuration Use an RTD-DI-16 module with a 2 or 3 wire RTD resistive input. Select 1000 ohm for the Sensor class property of the RTD input object. Configure the Conversion Settings properties of the RTD input object near the endpoints of the temperature range to be measured using values from the T99 temperature/resistance table. Configure the remaining properties of the RTD input as needed. Limitations Input Range. An RTD-DI-16 input configured for 1000 ohm operation is limited to an input resistance range of 500 to 2200 ohms. This will limit the temperature range that can be measured with a T99 sensor to ~115 deg. F maximum. Linearity Error. Depending on the range of temperatures to be measured and the needs of the application, linearity error may be significant. This can be corrected by using a script or function block program to linearize the signal based on the T99 temperature/resistance table values.

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 Services for assistance. Issue No events are transferred to the Report Server SQL database. Trend logs are transferred just fine. In the report agent log you can see this message "Sequence contains no elements" Product Line EcoStruxure Building Operation Environment Report Server Cause The Enterprise Server has been renamed before the Report Server has been installed or before the Report Server Agent has started collecting data. Resolution This issue will be fixed in a future version, but until that, do the following to correct the issue: The fix is split into two sections. First, a section working with the "event.db" file from the SBO database, and second a section working with the "StruxureWareReportsDB" from SQL Management Studio. "event.db" from the SBO database Download http://www.sqliteexpert.com/download.html (Just take the personal one) Stop the Enterprise Server Copy the "event.db" file to a safe location Attach the "event.db" file to "SQLite Expert Studio" Get the first event from the event.db using the following query in the "SQL" tab: SELECT SEQNO,TimeStamp,EventGUID,SourceServer FROM t_7E_2FSystem_2FEvents_2FEventLog_2FEventRecords ORDER BY SeqNo LIMIT 1; Convert the TimeStamp with this "SBO TimeStamp Converter" tool "StruxureWareReportsDB" using SQL Management Studio Write the following SQL query in SQL Management Studio, using the converted time stamp, and the Guid you found previously. INSERT INTO StruxureWareReportsDB.dbo.tbEvents (DateTimeStamp,SeqNo,OriginalSeqNo,Guid) VALUES ('2014-04-17 08:35:23.857','1','1', '380d1c4c-c60b-11e3-8ecb-b8ac6f81243c') Start the Enterprise Server again Restart the Report Agent and let it run for a while.

Issue When logging in to SmartStruxure WorkStation you get a security certificate risk warning Security Certificate Risk There were errors validating the security certificate in use. This may pose a security risk to the system. The certificate presented by this server was issued for a different server's address. How do you wish to proceed? Trust certificate or Cancel You can also get a warning when logging in through WebStation if you use the https address Warning in Google Chrome - FireFox - Internet Explorer Product Line EcoStruxure Building Operation Environment SmartStruxure version 1.6 and newer WorkStation WebStation Cause Starting in version 1.6, a new security feature has been introduced validating the ES and AS server identity based on security certificates. In order to avoid seeing this warning each time you log in, you need to apply a certificate to each server (ES, AS, ASP or ASB) - either a self-signed or an existing. Resolution This article will describe how to import or generate a certificate, and how to install the certificate through WorkStation or a browser. If you generate the certificate for an Automation Server, make sure that the time and time zone is correctly set in the Automation Server before generating the certificate. Regarding external CA certificates In step 8 below, it's shown how to generate a self-signed certificate. It might be that it's required to use an external CA certificate issued by a trusted issuer e.g. Verisign. All X509 certificates are supported. The format of the certificate must be PEM (as opposed to DER, PKCS7 or PKCS12). More about certificate types here. SBO currently only supports certificates using the PEM format which is the most common. If the external CA certificate is delivered in a container format (such as .pfx) it must be extracted before it can be used in SmartStruxure. More about extracting certificates here. Importing or generating a certificate Log in to Workstation clicking "Trust certificate" Navigate to the control panel Click on "Security Settings" Click on "Certificates" If you see a message saying that a secure communication protocol is not in use, it means that one or more AS's are communicating with the ES using the TCP port (4444) rather than https. In order to manage certificates for all servers in one operation, you need to change the communication ports. Click on "Configure communication settings" to do that. - and change the protocol to HTTPS and the port to 443 Back in the certificates settings, select one or more servers (in this example just the ES) and click "Manage Certificate" Select a certificate type to add. Unless a certificate is bought from a third party provider, select "Generate certificate" which will make a self-signed certificate. Enter a name, tick "Use IP/DNS..." and select a date when the certificate will expire as a minimum, and fill out more info if needed. Click "OK".  NOTE: Do not exceed year 2060 in the "Valid to" field, doing so will result in a certificate expired error when trying to apply the certificate. Select the certificate just created and save   Installing a certificate through Workstation Close Workstation (just logging out is not enough) Open Workstation and log in using the IP address or DNS name - never "localhost" as that name will not match the certificate. Now you will be able to tick "Always trust this certificate" as the name (IP address or DNS name) in the certificate matches the server you are logging on to. Tick the box, and click "Trust Certificate". Click "Yes" to confirm the installation of the certificate Now you will not get the security warning when logging on Installing a certificate through a browser Access the server using Internet Explorer (important) entering the https address (e.g. https://localhost) Click on "Continue to this website" Click on the "Certificate error" field next to the address bar Click on "Install certificate" Select "Trusted Root Certification Authorities" Click next and ok Close the browser Now you can use both Internet Explorer, Google Chrome and FireFox to access the server from Webstation using https and not get the warning If the certificate fails to install and be trusted properly, it might be because you need to manually select which physical storage to add it to. Refer to the following discussion

Issue Site looking for a sample program to monitor the thermostat and alarm if it stops updating the temperature. Environment AS PE Script MPM EnOcean Cause Documentation Resolution Write a PE script to monitor the temperature and alarm as necessary. Click HERE for sample PE Script program.

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