Building Automation Knowledge Base

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.

Issue How can we exclude Hosts or Users from accessing the Workstation Professional license i.e. Script, Function Block and Graphic editors from another Workstation? Product Line EcoStruxure Building Operation Environment Building Operation License Server FLEXnet Cause When accessing various editors from within Workstation a particular license does not differentiate host or user who should have access to which editors. Using the option file taclic.opt allows you to exclude certain Host / Users of StruxureWare Building Operation from accessing these Workstation clients. The Workstation clients referenced are as follows: client.station (Workstation) client.script (Script Editor) client.functionblock.view (Function Block Editor) client.graphiceditor (Graphic Editor) Resolution FLEXnet Licensing provides the options file to be included in the License Server directory. Each time the License Server service is started this file is checked. Syntax and use can be found in the attached document - Chapter 13 The following option file must reside on the License Server in the following path: Building Operation 1.9 and below: C:\Program Files(x86)\Schneider Electric StruxureWare\Building Operation 1.x\License Server Building Operation 2.0 and above: C:\Program Files(x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Once this file is copied into the License Server folder, you must restart the license service (via the Windows Control Panel, Administrative Tools, Services). Examples: # The following text excludes the features from Workstation Professional # # Use the following 3 Exclude statements if you wish to exclude an entire Workstation from accessing editors # EXCLUDE client.script HOST enter_host_name EXCLUDE client.functionblock.view HOST enter_host_name EXCLUDE client.graphiceditor HOST enter_host_name # # Use the following 3 Exclude statements if you wish to exclude a Building Operation User from accessing editors # (remove #'s below as required) # # EXCLUDE client.script USER enter_user_name # EXCLUDE client.functionblock.view USER enter_user_name # EXCLUDE client.graphiceditor USER enter_user_name # Notes: The HOST can be defined by either DNS or IP Address The USER is the user name as defined in Building Operation, this may be the same as the Windows username if using Windows Domain.

Issue Right clicking on a Xenta time schedule in the tree view and choose View-Watch pane-Select property, it doesn't exist It is not possible to see the property "Value" for a Xenta time schedule Environment Building Operation Workstation Cause It is not possible to select the Schedule object from the tree view and display its value.  Performing this will result in the 'default' property being display which is the description property.  This is a known issue which will not be corrected. Resolution Although you can not directly select the Schedule object itself and display its value in the Watch window, it is possible to see and add the value to the watch window as follows: From the respective Xenta Controller select the Application folder From the Variables tab expand the application folder Locate the Public Signal showing the Schedule name which you wish to display.   Right-click on this signal and select View > Watch pane The value of the schedule will now be displayed in the Watch window.

Issue Attempting to map a 3rd party bacnet alarm and there is no way to navigate down to the object Click here to see the following snapshots illustrating the issue Environment SmartStruxure Windows XP SP3 Windows 7 Cause We currently do not support external alarming (that is a BACnet alarm in the AS or ES monitoring a property in some other device.) This is being considered for a future revision. Resolution If the 3rd party device does not support alarming they would have to create an SmartStruxure alarm to monitor it.    An alternative work around if the 3rd party device supports alarms (Ex. Veeder Root in this case) is to create a BACnet Value in the AS (or ES) and then binding it from the Veeder Root object to the local value, and configure alarming from there.

Issue This is a short guide to show the correct use of output blocks with forced values in Function Block programs Environment SmartStruxure AS using Function Block programs Cause There is a design difference between the Vista Menta function block programming and the new version for SmartStruxure. In the old Menta programs it is possible to connect the output from an output block and connect it to an expression block. The forced value from the output block was passed to an expression block connected downstream of the output block. This is NOT supported in SmartStruxure at the current release Ver 1.3 (April 2013) If this is done in SmartStruxure then should the output block be forced in any way the forced signal is ignored by the downstream block Resolution Follow the guidelines as detailed in the attached document.

Issue SmartStruxure integration with BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Can SmartStruxure integrate or be used with other BMS, CRM, SQL, SCADA, PLC, HMI, TouchPanels, Citrix, or UNIX types of systems? Resolution Integration and use with third party systems is sometimes possible with SmartStruxure. The question is how much is the third party system willing to integrate or be used with SmartStruxure? OnQ, which is a proprietary CRM or Contact Resource Management built by the Hilton company and deployed to more than 2,100 hotels worldwide, is using the same communication protocol than Micros Fidelio/Opera so you can use a Bacnet to Fidelio gateway. Fingi Operational Services(FOS) All features of the Fingi Mobile Platform operate from within FOS server. There has not been an integration with FOS for an example. We have several references with these systems (Hilton Manchester, Hilton Copenhagen, Hilton America, ...) - some information are in the Solution Toolbox/Hotel under BMS to PMS integration. Some gateway examples are available: Hotels Gateway - Lonbox PFG4000 is a Fidelio Lonworks® hotel booking gateway The Lonbox PFG4000 Users Guide IntesisBox BACnet gateway catalogue - designed to allow supervision and bidirectional control of all the parameters and functionality of systems and equipment with KNX, ModBus, LonWorks and Fidelio systems from BACnet/IP networks IntesisBox BACnet Server – Fidelio IP - Datasheet Citrix - Building Operation is not Citrix verified, nor has it been put through the process of Citrix Ready. The Building Management WorkStation and WebStation have not been tested on a Citrix platform. One solution would be to inquire through your local sales/marketing channel to see if this is something they want to pursue with the business case which has been put together. Integration is a proposed TVDA for 2013 - to be confirmed depending on resources on StruxureLab.

Issue Which models of the SE7300 series room controllers can be used with the SC3000 series relay packs? Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SE7300 series Room Controllers Cause The SC3000 series relay packs allows existing line voltage wiring between the fan coil unit and temperature controller to be re-used. Only certain models of the SE7000 series room controllers can be used with the relay packs.  Resolution The SER7300 is used with the SC3000. Refer to F-27797 SER7300 and SC3000 Series datasheet. Refer to the F-27777 SC3000 Series datasheet to select the appropriate relay pack for your application.  SE7000 series Room Controllers documentation can be found on The Exchange Download Center.   

Issue The values read from an IAC600-S imported point are multiplied by 256. Environment StruxureWare SNP IAC IAC600 IAC600-S Values Cause The cause is believed to be the data bits for the value are read in the wrong order. Resolution This issue has been raise on the StruxureWare quality report system. (21033) It is possible to correct this reading on a point by point basis with a simple script program. 1  numeric input A 2  numeric output B 3  4  B = A/256 Or with the use of a function block.   Linking the object to the input and the output then linked to the graphical display / log ETC.

Issue The address of the IAC touch screen will reset to default (65) on Sundays when time broadcast is used Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Building Operation Enterprise Server Building Operation Automation Server MicroNet transition IAC touch screen Cause When the time broadcast on an AS or ES MicroNet interface the address of the touch screen will reset Instead of broadcasting the day number as a 7, the day number is sent as a 0. The IAC touch screen does not understand day 0, resulting in the touch screen resetting to defaults. No other days are affected. When the touch screen resets, the touch screen's address is also reset and defaults to address 65. Unless the touch screen was originally configured as address 65, the controllers on the SubLAN of the touch screen will not be available, until the correct address is entered into the touch screen. Resolution A hotfix is available from Product Support for SBO version 1.7.1.12604 This correction has been included in SBO 1.8 and later releases. Earlier SBO version will need to be upgraded to SBO 1.7.1 with the hotfix applied or upgrade to version 1.8 when available

Issue Can a BS5308 part 1 type 1, 2 pair individually screened cable be used for M-Bus communications? Environment M-Bus Communication Cables Cause A BS5308 part 1 type 1 cable was installed for Modbus communications, but it was then found that the communications were M-Bus Resolution The correct cable to use for M-Bus is J-Y(ST)Y.  These indoor telephone cables transmit analogue or digital signals; Aluminium-laminated plastic foil static screen with tin-plated drain wire minimises the interference of high frequency, electromagnetic field;TP structure minimises crosstalk. For the datasheet please click HERE. The BS5308 part 1 type 1 cable can be used, and the chart below shows the calculations used to establish this. For the cable datasheet, please click HERE. For the Excel spreadsheet please click HERE.

Issue List of Tables and Offsets for MicroNet 50 series, 100 series, and IACs Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment VisiSat VisiView MicroNet View Cause Need to define the Tables and Offsets for MicroNet 50 series, 100 series, and IACs. Resolution Click here to download the list of tables and offsets for the MicroNet range of controllers. Click here to download the list of tables and offsets for the IAC range of controllers. Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 and PA-00528 

Issue Automation Server -Trend does not record at time interval when it is stopped and restarted by AS power cycle or reboot. Trend log cycle is thrown off when the trend is stopped and started again due to an AS power cycle or reboot. For example, an Interval Trend Log set up to log ever 15 minutes with an activation time right on the hour (1:00, 1:15, 1:30 etc.) that lost power for a while would start logging as soon as the power was restored (this might be 2:07, 2:22, 2:37 etc. for example). UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Product Line EcoStruxure Building Operation Environment Automation Server Struxureware Workstation Cause This is how Interval Trends behave. For interval trending based on the time a different approach must be taken. UPDATE: This issue has been corrected in SBO version 1.5, any SBO version 1.5 or grater will synchronize the interval log to the clock. Resolution Rather than using Interval Trend Logs use Variable Triggered Trend Logs and trigger them using the following method: Create a new binary value and a new function block program. The value will serve to trigger the Variable Triggered Trend Logs. The program will set the trigger variable based on a certain time interval (for example on the hour, 15 minutes, 30 minutes and 45 minutes). Edit the program and configure it as seen in the image below. This include an integer input, an expression that will evaluate the minutes attribute of the AS and a binary output. You can also download an export of the program and value here. Bind the input of the program to the minutes attribute of the Automation Server and the output to the trigger value that you created. Note that you should also bind the Task to Task 1 (100 ms) for best performance. Create your Variable Triggered Trend Logs on the points that you want to trend. Do this by right-clicking the point to trend and selecting New > Trend and then in the dialog select Variable Triggered Trend Log. Click Next and then set the Trigger Variable to the value that you created. Make sure Trigger when is set to Change to true. Note that this example will create a log at 0, 15, 30 and 45 minutes past the hour. You can modify the program to trigger only every hour, every half hour or however you want.

Issue Requirements / specifications on cables used in a LonWorks network Environment LonWorks Cable Wire Guide LonMark Cause There are special requirements on cables used for LonWorks networks between Lon devices. Resolution LonMark organisation is recommending cables according to their specification. An example of this is the Belden LonWorks cable guide. Also, Echelon has a Wiring Guideline and Users Guide.

Issue StruxureWare Building Operation uses the old PI-Modbus-300 protocol Environment StruxureWare Building Operation using Modbus protocol Cause Does StruxureWare Building Operation use the MODICON protocol with the reference PI-MBus-300? Resolution Modicon was purchased by Groupe Schneider (which eventually became Schneider Electric) in 1996, way before Schneider Electric bought TAC. The PI that referred to is just a prefix of the technical document describing the Modbus communication protocol. The 300 is the version of the protocol. StruxureWare Building Operation supports a subset of the Modbus protocol. StruxureWare Building Operation does not support all Functions defined by the document specified. Modicon is still the only one that does.

Issue StruxureWare Building Operation AS status data Environment StruxureWare Building Operation AS Automation Server Cause AS Information program such as CpuUsage, MemUsage, ProductID, Partnumber, Serial, SWversion, and much more. Resolution The attached file can be imported into a AS (with any or the releases 1.1.x  through the current release 1.5.x). It will create two graphics that supply a wealth of operational information. Screenshots are shown below:   After import into your AS, look for System View folder. Open to view the two ProgramInfo and SystemInfo tabs. Please note that you can also see the CPU% and memory usage of the AS by using Building Operation Workstation, highlight the AS, go to the Properties tab and in Basic, the stats are listed.

Issue What sensors can be used in Clean Rooms  What sensors can be used outdoors for temperature measurement What sensor can be used in a swimming pool What sensor would be explosive proof What color is the wall sensor and are custom colors available Environment Building Automation System such as I/NET, Vista, or Continuum at a site containing a clean room, swimming pool, or outdoors Cause Questions concerning the uses of Schneider Electric sensors in Clean Room applications Questions concerning temperature sensors for Outdoor installations Questions concerning temperature sensors for swimming pools Questions concerning explosion proof sensors* Questions concerning color and custom colors for sensors Resolution All the Schneider Electric temperature sensors found in the HVAC Sensor Catalogue as well as on iPortal provide high accuracy and can be mounted on the wall, in ducts, or in a J-Box. Appendix A provides the accuracy for each of the temperature sensors. Color: STR series wall sensors are: Front Cover: White NCS S-0500 N Core Plate: White NCS S-0500 N and Gray NCS S-2500 N Base Plate: Gray NCS S 1502-R Manufacturing in custom colors in not available. One option could possibly to have the sensors locally custom finished to meet customer's requirements. While there is not a direct cross reference to RAL colors, our engineering team has found the closest alternates. Please see the attached pdf. Clean Room: Depending on the specified limits of the clean room, the variety of sensors offered by Schneider Electric are possible solutions. Thing you may want to research are the standards required for the site. Clean rooms are a controlled environment where products are manufactured. It is a room in which the concentration of airborne particles is controlled to specified limits. Eliminating sub-micron airborne contamination is really a process of control. These contaminants are generated by people, process, facilities and equipment and must be continually removed from the air. The level to which these particles need to be removed depends upon the standards required. The most frequently used standard is the ISO 14644 Standards, which were first formed from the US Federal Standard 209E Airborne Particulate Cleanliness Classes in Cleanrooms and Clean Zones.  ISO 14644 is a document that establishes standard classes of air cleanliness for airborne particulate levels in cleanrooms and clean zones. Strict rules and procedures are followed to prevent contamination of the manufactured product. The only way to control contamination is to control the total environment. Air flow rates and direction, pressurization, temperature, humidity and specialized filtration all need to be tightly controlled. Outdoor:  Schneider Electrics selection of Outdoor Temperature Sensors are the STO100, 200, 500, & 600. These outdoor sensors are intended for outdoor wall mounting. Variants are available for Vista, I/NET, Continuum and Satchwell systems. The body has a 20mm conduit entry and the product is supplied with a conduit gland. Range -40 to +90 °C Accuracy See Appendix A: Table A, C, F in the attached HVAC Sensor Catalog.pdf Outdoor Temperature Sensor STO100 Order Code 5141100010 Part Number STO100 System Vista, Xenta Outdoor Temperature Sensor STO200 Order Code 5123246000 Part Number STO200 System I/NET Outdoor Temperature Sensor STO500 Order Code 5141104010 Part Number STO500 System Continuum Outdoor Temperature Sensor STO600 Order Code 5126060000 Part Number STO600 System Satchwell Outdoor Temperature Sensor STO600D Order Code 5126000000 Part Number STO600D System Drayton Outdoor Temperature Transmitters STO300 The STO300 transmitter is supplied as a complete unit, comprising a sensing element and an amplifier mounted in a housing which is resistant to ultraviolet light. The transmitter is intended for mounting on an outside wall, on the north side where possible. The transmitter is connected over a 2-wire cable, which serves both as power supply and signal transmission. The reading of the measured signal is made over an external load resistance. Outdoor Temperature Sensor STO300 -50/50 Order Code 006920501 Part Number STO300 -50/50 System All Note for each of these outdoor sensors, find the Description, the Order Code, Part Number, and the System it works with for the iBAS (intelligent Building Automation System) Please note the difference in Weatherproof and Outdoor. I put a lot of these outdoor sensors in at a university in Texas, and always installed in places that were a little protected. I found that under porches, up under the eves and out of the sun, or along a loading dock out of the rain and ice gave me accurate readings. Swimming Pool: In the piping system of a swimming pool is a corrosive environment with steadily harmful and gradually destructive minerals and chlorine in the water which present a challenge finding sensors able to withstand for extended periods of time. Schneider Electric makes several immersion temperature sensors. Beginning on page 12 of the above HVAC Catalogue, there is a variety of immersion sensors for the different iBMS lines.  One example is the STP660 is a Temperature Sensor for the European market, and intended for immersion mounting in pipe or the circulating systems. The stainless steel probe is a good solution but remember,  if the sensor is to be installed in pool water that contains chlorine, the best bet is to use a stainless steel pocket. I suppose it all depends on if sensor is in pipe associated with the secondary pool side of the system or the heating side of the system. If the sensor head is in an area exposed to Chlorine, then there may be an issue.  Chlorine may attack the solder connections of the wired joints inside the sensor. In the old days products from Satchwell used to produce special sensors for such applications where the wire connections were varnished in order to prevent corrosion. I think at the end of the day, our sensor would have a similar life expectancy to other devices in the plant that were no designed for use in such corrosive atmospheres. Explosion proof sensors: Schneider Electric does not manufacture explosion proof sensors. We do not partner with another manufacturer who provides such sensors. The closest is an 3rd party explosion proof enclosure with one of our available sensors. Our sensors are designed for building installations and if in extreme environments, we suggest enclosures.  

Issue Certain animations in graphics may cause StruxureWare Building Operation to inadvertently close. Crash Report A problem occurred in this application Exception message: NO_MODIFICATION_ALLOWED_ERR: An attempt is made to modify an object where modifications are not allowed. Environment StruxureWare Building Operation 1.0 Cause Creating a graphic animation page without specifying the visibility will cause the graphic to close the StruxureWare Building Operation program.  Resolution In the image below, showing the Graphics Editor in SmartStruxure, this is a simple graphic page with one Ellipse which alternates between hidden and visible depending on the state of a single digital value being True or False. The red arrow shows that we are viewing the Source code for the graphics page. The blue arrow is pointing out the Appearance and the Visibility being selected. The green line in the source code shows the text which is inserted upon selecting the visibility the blue arrow refers to. The key is, failure to select the visibility, which inputs the Visibility="Visible" causes StruxureWare to close without notice and produces the Crash Report shown in the Issue. Download this Graphics Test Folder, which includes the Graphic, and the Digital Value for import to your Graphics Folder Note: Close or Crash does not occur in StruxureWare releases greater than 1.0.0.173

Issue When using the STR-350/351 as an I/O module in Menta (Options > Device Specification > IO Expansion and Wall Module Table) some programming consideration must be made to keep the occupancy and setpoint in sync between the stat and the program. Both STRIN and STROUT Menta simple blocks should be used for the most robust synchronization. Environment STR-350/351 as an I/O Module Menta Cause The STR-350 takes roughly 30 seconds to recover from a power failure. The Xenta is much faster than that resulting in reading an invalid setpoint from the STR-350 on a power cycle. By storing the last known setpoint in a DELR block with the "backup" option set, the setpoint will be restored (provided the power has not been off longer than 3 days, in which case it would default back to the initial value of the backed up value). Resolution Click the pictures of the Menta macro below to download the source file. Occupancy To control occupancy from the programmable controller time schedule, the occupancy must be sent to the STR-350. 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 synch with the program. 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 programmable 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 synch with the program, including stat adjustments. Note: This code protects against unwanted behavior following a power failure. A download the Xenta base unit will not trigger the Reset block protection and will cause the stat to go outside the bounds of, and then be limited by, either the high or low setpoint limit. Precaution should be taken following a download to manually reset the setpoint to the desired value. Additional logic for controlling the setpoint remotely could be incorporated into this code. 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 Failing communications when Xenta 555/731, VisiSat, StruxureWare Building Operations automation server/enterprise server connected to MicroNet ARCnet system through an MNMi. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN StruxureWare Building Operations automation server/enterprise server communicating to a MicroNet ARCnet LAN Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position. Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Switch 1 only must be ON for direct connection to Xenta 555. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue Instructions and programming example for using SNVT_Switch as an input or output in Menta Product Line TAC Vista, EcoStruxure Building Operation Environment Menta Function Block Cause The attached programming example is intended to clarify how to properly use SNVT_Switch in Menta. SNVT_Switch is a structured SNVT with two attributes, or members, State and Value. Programmatically this will be one SNVT in the device template, but it will be programmed as two separate analog points in Menta. These two public blocks will have different names in Menta, but they will share the same SNVT name with the exception of one of the points being the state member, and the other being the value member. It is important to remember that these points must always be programmed as analog points in Menta. AI's for input points, and AO's for output points. The state attribute is intended to be used for a binary on-off signal, but also contain the value -1 for Invalid value. The value attribute is intended to be used as a 0-100% signal. This SNVT is typically used in the market for starting and stopping a VFD drive and sending a speed reference with the same SNVT. The 0,1 value on the state member will start and stop the drive, and the value member will send a 0-100% speed signal. Resolution Please see the attached Menta macro as a guide to using SNVT_Switch in Menta. This example shows you SNVT_Switch as an input and as an output to the Xenta controller. To use this macro please follow these steps: Download the attached macro from above. Unzip the file and extract the SNVT_Switch.MTA from the archive to the local hard drive. Open Menta Right-click in Menta and click Load Macro Browse to the SNVT_Switch.MTA on the local hard drive and open it. It should import into the Menta file that is open.