Issue Looping script programs continuously loop around the code, but a fallthrough needs a trigger to start it running and will stop at the end. How is this configured. Environment Script programs set as Fallthrough in an AS or ES Up to Release 1.3 Cause Plain English used Triggers in points to start a program, these do not exist in an AS or ES Binary value, so what is used to start the program running? Resolution Once a script program has been written, checked and  saved as a Flow Type "Fallthru", you can then edit the bindings. In the bindings use the variable called "Restart" a binary value to bind to the triggering point/ value which should also be Binary. This object can then be triggered on the required event to start the program, which will then execute the code and stop at the end awaiting the next restart. When you Bind a Digital Value to a Scrip program, you may get an error message like the one here: By Default, a Digital Value has no Configuration Settings defined. Enter 0 and 1 for the binary states and then performing your binding to the Program alleviates the error message.  Note: This functionality operates for versions up to Release 1.3. From Release 1.4 the Restart attribute is read only showing the restart status from the program and does not allow a point / value to be bound to this flag. In Release 1.4 a looping program will need to be used checking the state of the trigger point and action accordingly.   Note: in newer releases e.g. 1.7, 1.8 and above, triggers are now supported and you can bind directly to the Trigger attribute of the program, each change of the bound point will trigger the script to run.

Issue Are DDC Controllers Leadership in Energy and Environmental Design Certified? Environment Site wanting Green Building Council Certification Cause Are DDC Controllers Leadership in Energy and Environmental Design Certified? Resolution The USGBC does not certify particular devices or controls systems such as I/NET, Continuum, or Xentas. LEED focuses on the design of the building and not on its actual energy consumption, and therefore it has suggested that LEED buildings should be tracked to discover whether the potential energy savings from the design are being used in practice. Five basic categories make up the design points system. Totaled together, these points determine your certification level. The level of certification depends upon the total number of points. As you can see, energy and atmosphere along with indoor environmental quality factors make up half of the available basic points. Five categories for accumulating points 1. Sustainable sites.... 26 Points 2. Water efficiency ....14 Points 3. Energy and atmosphere ....35 Points 4. Materials and resources.... 10 Points 5. Indoor environmental quality.... 15 Points 6. Innovation and Operations.... 6 Points 7. Regional Priority.... 4 Points Subtotal: 100 Points LEED 2009 for Existing Buildings: Operations & Maintenance 100 base points; 6 possible Innovation in Operations and 4 Regional Priority points Certified 40–49 points Silver 50–59 points Gold 60–79 points Platinum 80 points and above The U.S. Green Building Council is a national, non-profit organization that works to “promote the design and construction of buildings that are environmentally responsible, profitable and healthy places to live and work” (USGBC Mission Statement). The USGBC created the Leadership in Energy & Environmental Design® (LEED) Green Building Rating System. LEED was fashioned to provide a standard of measurement for defining a “green” building. It takes a whole building approach that encourages and guides a collaborative, integrated design and construction process. The program evaluates and recognizes performance of your buildings in accepted green design categories—Energy & Atmosphere, Water Efficiency, Materials & Resources, Indoor Environmental Quality and Sustainable Sites. Buildings are given a certification rating based on the number of points they receive in their evaluation. The four levels of LEED certification include: Certified Level, Silver Level, Gold Level, and Platinum Level. By becoming certified, building owners are given third-party validation of their contribution environment; qualify for various state and local government incentives; contribute to the growing knowledge base; receive a LEED certification plaque and official certificate; and receive marketing exposure through the USGBC website, case studies, and media  

Issue How to find the MAC address / Physical Address of a computer. Product Line Andover Continuum, EcoStruxure Building Operation, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment All computers Cause The MAC address of a computer may be required when working on licensing issues. MAC stands for Media Access Control and is a unique identifier assigned to network interfaces for communications on the physical network segment. Resolution Go to the Start > Run.   Type "cmd" into the Open field. In the CMD window, type the command "ipconfig /all". Locate the connection that the computer is currently using (For this example it is the Ethernet adapter Local Area Connection). You will find the Physical Address (MAC address).

Issue Need to perform autosensing on an ethernet port but do not have a cross over cable. Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment Ethernet connection to an Automation Server Xenta device ACX BCX Auto-Sensing, Auto Sensing direct connect Auto uplink and trade Universal Cable Recognition Cause Need to direct connect with a straight through or normal patch cable from a computer or laptop to the AS, Xenta, BCX, ACX  Resolution Since 1998, the distinction between uplink and normal ports and manual selector switches on older hubs and switches are obsolete. If one or both of two connected devices has the automatic MDI/MDI-X configuration feature there is no need for crossover cables. Now you can plug your laptop right into the Ethernet port of the device with just a regular patch cable. 

Issue Problems with the speed a script was appearing to run. How to adjust the Variable Connector. Environment StruxureWare Building Operation site with BACnet or LON  Cause Definition of a variable connector Problems with the speed a script was appearing to run Resolution Definition Variable connectors The SmartStruxure system has a base philosophy where different objects and properties are connected using bindings. Bindings do not usually cause any significant load to the system, but in some cases the bindings need to be driven by an external object called a variable connector. The user does not create variable connectors. The system creates variable connectors either when there is no obvious direction of the binding (analog value to analog value, for example) or when passing data between protocols (LonWorks to BACnet or LonWorks to Modbus). Due to load caused by the variable connectors, limit the number of variable connectors according to the variable connectors table above. It is possible to increase this number, but close monitoring of CPU load and memory consumption is needed. Release 1.4 Anticipated removal of Variable Connectors and replaced with a Binding Table. Variable Connectors cannot be removed. The maximum number of variable connectors is (Used when the binding has no obvious direction or when passing data between protocols) Enterprise Server: No practical limit known Automation Server:500 There are 'variable connector' objects in the system folder underneath the server that have a polling time associated with them and these are applied to both incoming and outgoing script variables. They default to 10 seconds polling time so regardless of the setting of a script cycle time it is subject to these polling times. Note: The default value of 10 seconds polling time for values regardless of BACnet, LON or otherwise.  Variable Connectors are automatically created when the bound values themselves are of a kind that lack the logic needed for polling. Editing the binding (by clicking the pencil icon next to the binding list path) indicates that there is a variable connector associated with the binding.   Below is a screen capture for Variable Connector Settings. Transfer Value Click the Force value button and enter the value that you want to force onto the binding. Type Select how the binding is updated. Periodic polling updates the destination value at regular intervals. Change of value updates the destination value only when the source value changes, and only when the change is significant enough. Interval Select the number of seconds between updates. Propagation delta for value changes Enter how much the source value must change to trigger an update of the destination value. Retransmit interval(s) Enter the number of seconds between forced updates. In most cases, you bind a source value to a destination property that is an input variable in a program. The binding is direct, and the input variable actively reads the source value during every execution cycle of the program.However, not all bindings have a destination property that is an input variable in a program. When you create a binding, with a destination property that cannot read or poll the source value, StruxureWare creates a variable connector. Most bindings do not need variable connectors, but when they do, StruxureWare creates them automatically. There are basically three things you can do with a variable connector: Configure polling method Configure polling rate Force the bound value In a direct binding, you do not need to concern yourself with the polling of a bound value. There will be a program execution cycle involved that manages polling. With a variable connector you can configure the default polling settings in the properties of the variable connector. For more information, see Configuring a Variable Connector . Also, in a direct binding, you may be able to force the bound value in the destination property. With a variable connector, you force the bound value in the properties of the variable connector. Variable connectors and their properties are accessible from the Control Panel. There is a Variable Connectors list in the System folder of each server. Variable connectors are also accessible from the Binding point list. LonWorks network variables and configuration properties can be bound to each other in LonWorks bindings. They can also be bound to most points in StruxureWare, such as programs, graphics, alarms, and trend logs, but then StruxureWare bindings is used, not LonWorks bindings.

Issue Changing a value from a WebStation. Environment Web Changing a value Changed value returns to its original value Cause The value appears to have been changed correctly, but when the page is refreshed, or changed and returned to, the original value is shown. Resolution There are two ways to change a value as shown below; 1 - Using the edit option. -  Select "Edit" which is located on the right-hand side of the current value.   The "Edit" box is displayed.     Enter the required value and select "OK". Now go to the lower right-hand side of the window and select "Apply".   2 - Typing over the current value -  Wipe over the current value to highlight it, and enter required value. Now go to the lower right-hand side of the window and select "Apply".  

Issue Telnet does not come enabled on Windows 7 PCs Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 OS Cause This feature does not come enabled in Windows 7. Resolution Click on the Start Icon and type Programs in the Search Window Click on Programs and Features Click on Turn Windows features on or off When the window becomes populated, check the box for Telnet Client   Click on Ok to apply change, exit Programs and Features window Type Telnet at the prompt and start your session

Issue Binding a PVR module in the Function Block Program directly to a "Value" object? Environment Function Block Program FBP PVR module Cause The PVR module is not available to bind in the binding window. Resolution To enable the PVR module to be bound, it must first be made "Public", this is selected when editing the module.     Having saved the Function Block Program, the PVR module can now be bound in the normal way.  

Issue While attempting to activate a purchased license, the entitlement ID shows that it is valid, but there is no available licenses that can be activated, or less available than listed on the entitlement certificate. The entitlement ID or certificate is lost. Unable to return the license in order to activate it on another PC Getting "This Operation is not applicable for Trusted Fulfillments" Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In order to activate a SmartStruxure license, it must be available and unused. If a license is already in use, it needs to be returned before it can be activated. Note that all handling of licenses are to be carried out using the License Administrator. Licenses are not returned or rehosted as it was done for TAC Vista. Resolution Refer to WebHelp article #6687 for instructions on how to return a license If you are unable activate a license because you don't have the entitlement ID or certificate, note the activation ID before you return the license, and send that to Product Support Services in order to get the associated entitlement ID Launch the License Administrator Go to the Diagnostics tab and click the refresh icon in the top left corner. The entry in the list that is labeled Entitlement ID is actually the Activation ID. In the case that the computer has crashed or you are unable to successfully return the license on your own, contact Product Support Services providing the following details: A copy of the entitlement certificate The site name An elaborate explanation of why you are not able to return the license yourself

Issue COVNotification messages in BACnet captures. Product Line EcoStruxure Building Operation Environment BACnet IP network BACnet MSTP network BACnet networks with controllers that support COV (Change of Value) Cause COV increment is an attribute that is available in several BACnet points that is settable and when this attribute COV Increment is left at a setting of zero can cause COVNotification messages appearing as broadcast storms creating un-necessary network traffic. Resolution It is suggested to set the value of the COV increment attribute to something other than the default zero or to a value that is pertinent to the point in question. The COVNotification services are uni-cast messages and can have a many to one relationship depending on how may clients are subscribing to the point. Example: Jobsite has a BACnet OAT (outside air temp) input point with the COV increment of zero. The OAT point is added to the watch window or a binding to a graphic or program. The OAT is changing ridiculously fast due to wind and intermittent clouds. The value is changing by 1/1000 of a degree and each COV (change of value) message is delivered out to any object that is referencing the point. But does the value need to display or do we care if the point changes by 1/1000 of a degree. Let's say that the sites requirement only needs value changes of 2 degrees or more. The COV increment can be set to 2.0 and now the UnconfirmedCOVnotification message would only be sent if the OAT changed by 2 degrees or greater. This alone would reduce 100's if not 1000's of network packets. Imagine a jobsite with the above scenario and 100 different points all with the COV increment of zero. Setting the COV increment to something other than the default of zero is one of many ways to improve BACnet communications and reduce what may appear as broadcast storms on the network.

Issue LonPort is discovered and shows as online but no Service Pin is received Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation ES 1.1 LConfig Cause Since StruxureWare Building Operation ES is running as a service, the legacy driver also has to be. Resolution Open LConfig Click advanced Change Legacy Driver to run as service

Issue Description in List View editing causes error Environment StruxureWare Building Operation 1.1.xxx Cause 1. Enter a description in the List View. This can be for anything, I selected a folder in the following two screenshots. 2. Boiler1 Folder: Description is Boiler 3. Boiler2 Folder: Description is Chiller 4. Graphics Folder: Description is Chiller 5. When I cut Ctrl-X the Graphics description and them on down the list, (imagine I have a lot of folders or devices I am putting descriptions in) if I save when not in that field, the error below occurs.  Resolution Upgrade to StruxureWare Building Operation Workstation release 1.2.0.659 or higher.

Issue Unable to select extended trend logs in Trend Log Comparison Report. Environment StruxureWare Enterprise Server Cause Extended Trend Log property " Include in reports? " defaults to false. Resolution Extended Trend Log property " Include in reports? " must be set to true.  

Issue Values of Units change when viewing English OS from Metric OS Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Site Cause Changes in Unit Value English OS example of Pressure Unit of Bar: Metric of same exact unit from a Metric OS: Resolution This behavior of different Units being displayed on OS systems with metric units. In the State the English units for measurement are on the OS and StruxureWare Building Operation. The issue described is Functions as Design in StruxureWare Building Operation. Not just IO, but all the functions are like this. The localization follows the regional settings of the PC’s operating system, out of the control of users. To change your PC's measurement System, complete the following steps: Open the Control Panel on your PC and browse to "Region and Language" In the Region and Language editor, click on the "Additional Settings" button found at the bottom of the "Formats" tab. Change the measurement system to the desired system                                                                  Click OK to close all Windows Restart all applications for changes to take effect.

Issue AS-P is restarting on its own intermittently. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (All Versions) Cause Log entries found within the system_log.txt file confirm that the intermittent restart issue is caused by power interruption. See the below example of what to look for: Apr 08 19:03:34 AS-P-04619A kernel: pmem: shutdown interrupt: pid=0, comm=swapper/0 Apr 08 19:03:34 AS-P-04619A kernel: [<80013920>] (unwind_backtrace+0x0/0xe0) from [<801f569c>] (pmem_shutdown_irq+0x54/0x74) Apr 08 19:03:34 AS-P-04619A systemd-journal[1360]: Journal stopped -- Reboot -- Apr 08 19:03:54 cpud pmem_util[656]: Found SyncBlock Partition at sector 0x5dc00, 192000 sectors long. pmem_util[656]: ---------------------------------------------------- pmem_util[656]: SyncBlock Header summary (from previous power fail): pmem_util[656]: Sequence number:             94 pmem_util[656]: Exit critical regions:       0ms pmem_util[656]: SyncBlock file systems sync: 20ms pmem_util[656]: SyncBlock write map:         0ms pmem_util[656]: SyncBlock write speed:       6399kB/s (Wrote 128kB) pmem_util[656]: Total power fail time:      ~130ms pmem_util[656]: ---------------------------------------------------- pmem_util[656]: Finished moving 240 sectors (120kB) pmem_util[656]: Exit Resolution When an AS-P detects a power outage, regardless of how brief, it will initiate the process to backup the run-time and configuration data from memory to storage and reboots itself.  Check the power source connected to the AS-P and take appropriate actions to improve uninterrupted power delivery. An example would be to deploy a UPS solution.

Issue Definition clarifications for Thermistor Type in Technical Reference Guide for StruxureWare Building Operation Environment StruxureWare Building Operation site with Thermistor temp sensors Cause In the image below of the technical reference guide for StruxureWare Building Operation on page 3164 the accuracy of the supported thermistors seems to be difficult to decipher or at least very hard to figure out what accuracy goes to what thermistor type. The issue is the input specifications does not clearly separate the Thermistor type (Continuum, I/NET, etc) with the accuracy. If there was a line or something to separate the accuracy definitions from each other that would help. What defines one set of values from the next? The ending of the parenthesis defines the end of the information for each sensor type, but this is not clear.  Resolution A defect has been recorded and it has been requested that in the next release of the Technical Reference Guide for StruxureWare Building Operation, this be corrected and offer clarification as to the accuracy with a Hard Return. The lines are actually separated by the end of the parenthesis, but this is difficult to decipher.  

Issue What are the values named Temp_FBValue Environment StruxureWare Building Operation Site with Function Block Cause Site is wondering about the values named Temp_FBValue. What is the meaning and why you cannot bind them.   Resolution A function block variable with the name XXX_FBValue is an output variable from an Input block (e.g. RI- BI- II- PI- block). It’s an internal variable and ought to be hidden, but it’s not so today. It should not be possible to bind theses variables.

Issue Enterprise Server does not start when computer is started/rebooted or shuts down right after starting it StruxureWare Building Operation Software Administrator log shows the following error: nsp.NspServer The server has made too many unsuccessful attempts to start... Product Line EcoStruxure Building Operation Environment Software Administrator Enterprise Server Cause StruxureWare Building Operation is prohibiting the Enterprise Server from starting up because the ES has exceeded the number of startup retries defined in server_startup.properties. When the server_startup.properties file is opened in a text editor, the first line indicates a startup failure. NspServer.Startup.Service.Status: fail Resolution Windows XP: This is caused by a dependency, set in the registry, on the service netprofm (Network List Service), which exists on Windows Vista and later, but not on Windows XP. The error has been verified on a new installation of Windows XP. Steps 1 and 2 below help to resolve this on the XP operating system. Windows 7 and Windows Server 2008 R2 including Virtual: Start ES manually from the Software Administrator. If this fails, the log in the Software Administrator explains why. Start the ES manually from the Services listed in Services (Start, My Computer, right-click, Manage, Services click the + to find Services) find StruxureWare Enterprise Server Go to the Software Administrator and modify the HTTP, HTTPS, and TCP ports to available ports. (suggested: 81, 444, & 4444). The number of startup retries is defined in the following file: 1.2.0 and below : C:\Program Files\Schneider Electric\StruxureWare X.X\Enterprise Server\etc\server_startup.properties 1.3.0                  : C:\Program Files\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\etc\server_startup.properties 1.4.1 and above : C:\ProgramData\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\db\etc\server_startup.properties Increasing this threshold in server_startup.properties will allow the Enterprise Server to have a better chance of achieving a successful startup. server_startup.properties -- Original settings NspServer.Startup.Service.Status: fail NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 2 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 2 server_startup.properties -- Threshold increase to 10 retries. NspServer.Startup.Service.Status: success NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 0 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 10   Last option, and please go through all the previous steps mentioned before attempting: Open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Building Operation X.X Enterprise Server. Open the DependOnService and remove the first line (netprofm) and then reboot. The ES will now start automatically.     Alternative Workarounds Go to Computer Management by right clicking on Computer and going to Manage. In Computer Management, go to Services and Application > Services > Building Operation X.X Enterprise Server. Right click on Building Operation X.X Enterprise Server and go to properties. The two different settings that can be changed so that the Enterprise Server starts automatically as a service after a reboot are as follows. Under the General tab, change the Startup type from Automatic to Automatic (Delayed Start). Or under the Recovery tab, change the Restart service after to a value of 3 or more minutes.

Issue How to register LonTalk Protocol Analyzer Software Product Line EcoStruxure Building Operation, TAC Vista Environment Vista LPA Cause The LonTalk Protocol Analyzer software is a tool for LonWorks network troubleshooting. There are two kinds of LPA license. Some customers may be confused about it. Resolution To use the LPA, you need to purchase the software license. There are 4 kinds of LPA license. Refer to this page for further explanation. LPA-SW: This license is bound to NIC709-USB.  Need to use specific NIC709-USB to be the network interface of the software. LPA-IP-SW: This license is bound to NIC852. Need to use specific NIC852 to be the network interface of the software. LPA-IP: Same as the above, but includes a dongle.   The steps of registration for the current version of LPA using the current NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec's Website. Open the LPA program Click on "Help->Register Product"   Enter the Registration Code in the product package, and click Add.   The steps of registration for previous versions of LPA using the previous NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec Website. Open the LConfig program.   Click Register / Activate to open the registration window. Enter the Registration Code in the product package, and click Add. Then the registration is finished. Open the LPA software to test whether the license works fine.

Issue Clarity in protocols and capability from StruxureWare Building Operation's Normalization Layer and the integration of BACnet/IP for data out of StruxureWare Building Operation. Environment StruxureWare Building Operation Site Cause Protocols and desire to input/output point data from the Normalization Layer. Desire to pull point data into StruxureWare and then back out, via BACnet/IP.  Resolution The Normalization Layer in StruxureWare Building Operation is probably more of a design philosophy than a documented product feature, per se. It is StruxureWare’s attempt to present data (analog data, for example) to the user in a consistent manner, regardless of the protocol in which the data is natively encoded – BACnet, LON, Modbus, etc. This “data normalization” occurs automatically, although there may be some options for adjusting how certain values are presented. In other words, the  “Normalization Layer” is a term that was coined by the Product Marketing side of the use and has been embraced by  many to refer to the various parts of StruxureWare Building Operation that allow us to gather information from a wide variety of field protocols, such as BACnet, LON and Modbus today as well as being in a position to communicate with OBIX or OPC or any other protocol and to present it to the user in the same way as we present the other protocols. In other words, we make it “normalized” for the end user so that he or she does not need to know or care from what type of device the data comes. The StruxureWare Building Operation system can send point values or alarms to third-party system via BACnet/IP. StruxureWare can do this even in the present 1.0 release. The typical method to share point values would be to use either a Script or Function Block program to bind a StruxureWare point value to a third-party point value. To share alarm information just add the third-party device to the Recipient_List property of one of StruxureWare’s NotificationClass objects that is associated with an alarm.