Building Automation Knowledge Base

Issue After creating the MSTP network from an imported XML file, all devices under the network are offline and the network is unreliable. Product Line EcoStruxure Building Operation Environment BACnet Cause The MSTP network number is not included in the XML and must be reset manually. Resolution In the MSTP network property window set the Network ID to the appropriate number. Note: To bring the devices online see Importing an exported MSTP network back into StruxureWare Building Operation.

Issue How and when does a Xenta 121 resynchronize floating control outputs? Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 121 - All versions Cause Documented reasons for floating control resynchronization on a Xenta 121 controller. Resolution There are 3 events that cause a Xenta 121 to resynchronize its floating control output logic. These reasons are: After a restart of the controller from a power cycle or reset command. The resynchronization is randomly initiated within the first 42 minutes after this restart. Testing shows an average of 20 minutes. After the controller is powered up and has done it's initial resynchronization, it will resynchronize every 18 hours there after. Commanding the snvt_switch input nviDOResync value member to  >0, and the state member to =1 Please see Programming SNVT_Switch in Menta for instructions on how to program snvt_switch in Menta.

Issue Making all Binary/Digital point types appear the same in a TGML graphic Product Line EcoStruxure Building Operation Environment TGML Cause When bringing multiple devices into the same system, 2-state values can be expressed in many different ways.  On/Off 0/1 True/False etc. Resolution Use this snippet Binary Corrector.zip to normalize the text content of all 2-state objects on a single graphics page. Delete existing binds Add this snippet to any text object and set the bound attribute as "Content" Change the True/False properties of the bind to the desired values Also check out the JavaScript Essentials - Episode 3 - Value Types Quick-Help video on the Exchange.

Issue Sigma Transition in StruxureWare Building Operation, where the Sigma controllers and the ES are on different subnets. Globals are not being passed to or from the Sigma system. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Globals Global values Link addressing Cause This issue is being caused because the Sigma controllers are on a different subnet to the Enterprise server. Sigma global data is passed between controllers using "Broadcast" messages, 192.168.1.255 for instance. These messages are normally stopped by network switches/routers, and are not passed between different subnets. To overcome this, Sigma employs "Link Addressing". For further information on this please review Link Addressing on a Sigma System Resolution As Sigma servers do not make use of the global broadcasts, on a current Sigma system there may not be any Link Addressing in place for the Server subnet, and this will mean that if an ES is placed on that subnet, it will not see any global broadcasts either. When carrying out a Sigma Transition consider if there is a need to pass global data to or from the Sigma system, and if so, add a DNN3 to the subnet and Link Address it..

Issue Can a Webpage be embedded in a TGML Graphics like in Continuum? Environment Workstation Cause Documentation Resolution As of version 1.4 web pages can not be embedded in graphics, however a similar solution maybe achieved using panels, see discussion in the community... https://community.se.com/message/8203

Issue Which substitution codes are available for write to file notification objects? Customer wishes to write dynamic values to file. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3/1.4 Cause When using write to file notification objects it may be desirable to have dynamic text containing actual values etc. Resolution For write to file notifications, the substitution codes can be used in the message but not in the file name. A substitution code for notifications has the form @([property]) where [property] is replaced by one of the alarm properties. If you use a substitution code that is invalid for the specific alarm event, the substitution code is replaced by an empty string. For alarm email notifications, see Displaying different properties of an alarm in an email notification.

Issue Xenta 102-AX temperature sensors reading in the range of 130°F (54.4°C) when they should be closer to room temperature. Wiring has been checked and everything appears correct. What kind of temp sensor do I use for a 102-AX? Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX ETD-1xx duct temperature sensors ETR-1xx room temperature sensors STR-1xx room thermostats Cause Every other Xenta controller uses a 1.8k-ohm thermistor as a standard. Because the Xenta 102-AX is a modified version of the I/NET MR-VAV-AX, it still uses the 10k-ohm thermistors native to the I/NET product line. Resolution The Xenta 102-AX uses 10k-ohm thermistors. See 10k Thermistor compatibility with Xenta controllers for detailed information on the thermistor curve that is acceptable. Approved sensors are: ETD-2xx duct temperature sensors ETR-2xx room temperature sensors STR-2xx room thermostats STD-2xx duct temperature sensors

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries   Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier'  field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue Is serial tunneling, using XPSI to Network 8000 controllers, possible through an Automation Server? Environment Automation Servers (all revisions) Cause Remote connectivity to Network 8000 controllers in a building is a desired feature Resolution There is no serial tunneling with XPSI available from Schneider-Electric. The Communities website may offer an option:  https://community.se.com/message/19507?commentID=19507?sr=search&searchId=b7102b14-5f13-4971-8a5d-ef0a0e591271&searchIndex=2#comment-19507

Issue Sometimes it is required to gather a trace log between the I/Net USB adapter and the AS or AS-P it is connected to for deeper troubleshooting investigation.  Product Line EcoStruxure Building Operation Environment Automation Server  Automation Server Premium  Workstation  Cause The I/Net adapter trace log may be requested by Product Support to help identify problem experienced in the field.  Resolution How to collect the I/Net interface adapter trace log In the Workstation System Tree, go to System > Modules > Trace > Loggers > nsp > nsp.pin > nsp.pin.inet-nsp.pin.inet.IoPort Right click on nsp.pin.inet.IoPort and go to properties. Under the Basic tab > Settings > Level, set the Level to Trace. Click OK.  Let the system run for the desired amount of time (usually 10-15 minutes). To collect the log, in the system tree go to System > Modules > Trace > TraceSettings Right click on TraceSettings and select Trace Settings and then Get trace log. Finally go back to System > Modules > Trace > Loggers > nsp > nsp.pin > nsp.pin.inet-nsp.pin.inet.IoPort, right click on nsp.pin.inet.IoPort and go to properties.  In properties under the Basic tab, change the Level back to Information.    Parse the Trace Log You can use the TAC INET LANMon Decoder tool found on the Community site. 

Issue Recovering from a Failed 1.4 upgrade. Product Line EcoStruxure Building Operation Environment StruxureWare Device Administrator Cause The upgrade to 1.4 requires special planning and site specific preparation. Before Upgrading you should always review the release notes with an eye for site specific implications. Please read these articles when performing an upgrade to 1.4: Reference Guide and References beginning with 1.4.x Contains detailed information about the changes to Reference Management in 1.4. Upgrading Automation Servers from 1.3 to 1.4 Contains the process for upgrading an Automation Server to 1.4 Resolution The following offers 2 scenarios for correcting issues post upgrade. Scenario 1 In this Scenario, the user will use the built in repair tools added in 1.4. These tools help the user fix issues that are typically fixed prior to upgrading. Please see Reference Guide and References beginning with 1.4.x for a complete description of the changes to the Reference Management in 1.4 In StruxureWare Workstation, browse to the Control Panel and click on "Reference Manager" Note the list of References with errors. Right Click on each item and click "Edit Bindings". Re-Bind any questionable item using the new rules for Reference management. Scenario 2 In this Scenario, the user will downgrade the system to 1.3. This is not a preferable solution, but may be required in specific instances. Please note, that in order to downgrade, you must have a valid backup of the ES and every AS from prior to the 1.4 upgrade. If you do not have a valid 1.3 backup, you will need to use Scenario 1. You will also need to be able to apply any service packs or hotfixes previously used. Validate that you have a 1.3 backup of the AS and every ES by going to C:/ProgramData/Schneider Electric StruxureWare/Building Operation 1.3/Enterprise Server/db_backup. If the Backups are present and the date and time stamps are acceptable, then copy these to another location, to ensure they are not lost. You can either install 1.3 on a second PC or install on the same PC. For this example, we are installing 1.3 parallel to the 1.4 upgrade. Stop the 1.4 enterprise server before proceeding. As you install each piece of software you will be informed that the installation will be done parallel to the current version. The exception to this is the License Server. You can have only one license server installation of any build on the same PC. After you have installed all of the 1.3 Software, Install any Service Packs or Hotfixes that had previously been installed on site. When you are finished, the Start Menu will show the parallel installations of StruxureWare. Open Device Administrator Connect to the AS or all AS Click Upgrade and select "New database" Click OK There is no point to attempt to upgrade the database to 1.3 as any problems will be converted back as well. Log into each Automation Server separately, right click on the server in the system tree, and click Restore. Import the backup set you have from prior to the 1.4 upgrade. Note that Red text indicates that your current build does not match the build used for that backup. At this point, you system will be back at 1.3, and should be running as it was before the upgrade, or at the very least, it will be at a manageable level. Use the links above to correct any Reference issues before proceeding with the 1.4 upgrade.

Issue How can many years worth of logged data be stored in an Automation Server? Product Line EcoStruxure Building Operation Environment Trend Logging Extended Trend Logging AS Cause Site requirements may dictate that longer-than-usual histories of data be kept on file. For example, to log a value every 5 minutes for 2 years equates to approximately 105120 records per year. A Trend log in an AS will store 1000 records. An Extended Trend Log will store 100,000 records. Therefore a single log will start to overwrite in about a year. For the latest up to date values please review  Maximum number using StruxureWare Building Operation (Scalability and Capacity). Resolution To overcome this issue, two Trend Logs and Extended Trend Logs are required. Create a Trend Log and Extended Trend Log for Year 1 (Odd Years). Create a second Trend Log and Extended Trend Log for Year 2 (Even Years). Both of the above Trend Logs with be set to log the same variable. Create a program to select if the year is "odd" or "even", a possible Script might be. In each trend log select the "Activation Method" as "Variable Controlled", and in the "Activation variable" field, "Browse" to the "Script Program" output that is appropriate. Logging will now take place in the Trend Log appropriate for that year.

Issue Alarms are produced by Sigma controllers, but these alarms are not received at the Enterprise Server Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Enterprise Server Sigma 4.08 Alarms Delayed alarms Transition Cause When Sigma alarms are manually tested from the Enterprise Server, the alarms are received normally, but alarms occurring during normal operation on the Sigma system, can be delayed, or not displayed at all at the Enterprise server. This issue is caused by the firewall. If the Enterprise Server is initiating the communication with the Sigma controllers, then the firewall will normally allow any alarm messages from the Sigma controllers to pass through the firewall, and the alarms be displayed normally. When the Enterprise Server is not initiating the communication the Sigma controllers, then the firewall will normally prevent any Sigma alarm messages from passing through, and therefore the Sigma alarms will not be displayed. Resolution The solution is to allow inbound communication to the Enterprise Server PC on port UDP 49152 Depending on the firewall used, the configuration steps can vary. If Windows Firewall is not used: Consult your vendor manual. Example of Windows Firewall not being used If Windows Firewall is used but managed by the IT department: Consult with your IT department. Example of Windows Firewall being managed by IT If Windows Firewall is used and you can manage it: See below Windows Firewall A quick solution is to use "SBO Firewall Config". While the tool is not officially supported, it has been used by various sites. To manually add the exception to Windows Firewall, refer to Using Sigma on Windows 7 with firewall.

Issue Continuum / Vista / I/NET / StruxureWare etc will not connect to any of the controllers on the LAN when using a Windows 7 and above PC. Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment I/NET 2.4x Continuum Vista StruxureWare Windows 7 8 8.1 10 Cause This is due to Microsoft improving their security in Windows 7 and above that will now block many types of connections across a network. Resolution To enable communications across the network; Disable all firewalls and any Anti-Virus software on the PC. (SE laptops, right click on McAfee shield, Quick settings and un-tick everything, this will temporarily disable the AV and firewall) Disable User Administrator Control (UAC) (As per Disabling administrator rights messages in Windows 7 OS and above) Re-install I/NET Seven / Continuum / Vista etc

Issue Event notification is grayed out in the AS and will not allow configuration.  Cannot add a category within the AS. Product Line EcoStruxure Building Operation Environment SmartStruxure Shadow AS Event Notification Cause The Event Notification in the AS can be locked due to a shadow relationship with an Event Notification in the ES. Resolution Note the IP address of the AS, as the shadow relationship can be re-established after necessary changes are made. Remove the shadow relationship to the ES to allow configuration of the AS. Detailed instructions can be found in Unable to add an Automation Server underneath an Enterprise Server. Re-established the shadow relationship if needed.

Issue Cannot connect network variable point from a third party LON device to a graphic within an XBuilder project.  XBuilder will not allow the drag and drop of LON network variable between the network pain and the system pain when you attempt to create connections. Product Line EcoStruxure Building Operation, TAC Vista Environment XBuilder Vista Lon Device .xif Cause XBuilder is very particular about the format of an .xif file and it will not allow certain characters in the function block name. Vista and LonMaker have far less limitations and these programs are able to parse these characters without causing problems. This explains why your values may show up in the LNS management tool and Vista Workstation. However, once you import the network into XBuilder you are unable to connect the SNVTs to your graphic. Resolution Replace the incorrect characters in the function block line of the .xif and reload the new .xif into your LonWorks Network.  Please see LON device can communicate in Vista, but fails in a Xenta Server / XBuilder for more information about incorrect characters in an xif file. INCORRECT FUNCTION BLOCK EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved. Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000-MP580,8500-SCC,8610-DAC The problem is the three dashes  between the object numbers and the object names in the self doc string.  This is "allowed" in Vista and LonMaker in some sense.  For  example, Vista "replaces this "-" to a "/" but then XBuilder can't handle this situation properly. CORRECTED EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved.  Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000MP580,8500SCC,8610DAC;Tracer MP580 The dashes 3 x (-)s have been removed from the function block name

Issue Is editing an exported XML file supported? Receive errors when attempting to import (a modified) exported XML file. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Export / Import  Cause There is minimal error checking on the import so errors could get through and cause problems further down the line and corrupt the database. Resolution Edited exported XML files is not supported and there is no documentation on how to properly edit exported files. This practice should not be attempted.   With 1.5 will comes Project Configuration Server (PCS) and the ability for the businesses to create their own country specific applications and mass create engineering tools. In a future release (currently indicated in 1.6) support for using the Backup and Restore feature to duplicate entire Automation Server databases will be available.  For now both these functions are not supported.  Refer to Do NOT use Backup and Restore to duplicate Automation Server databases! (1.5 and below).

Issue Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server Shadow Schedule in the ES syncs successfully to Lead Schedule in the AS Lead and Shadow Schedules in different AS are syncing successfully Product Line EcoStruxure Building Operation Environment SmartStruxure 1.x Cause Traffic is blocked by Windows Firewall.  Resolution Disable Windows Firewall. Disabling the firewall may not be possible due to security concerns, Exceptions can be added to Windows Firewall for ports that are used by SmartStruxure. Refer to Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port for details. If this doesn't work, please refer to Shadow Schedule in AS isn't synchronized with the Lead Schedule in ES.

Issue When using the LPA through an Automation Server (AS) as described in Using Loytec LPA with SmartStruxure AS, only traffic to and from the AS is captured. Product Line EcoStruxure Building Operation Environment LPA Automation Server Cause Due to a hardware limitation in the AS, it's not possible to capture all traffic on the segment Resolution Connect the LPA to the segment using a NIC-USB100 or similar

Issue Unable to Upload or display point data on an I/NET Controller in StruxureWare Workstation Environment I/NET to StruxureWare Integration Cause The most common cause for I/NET controllers to not integrate with StruxureWare are duplicate point names or illegal characters in use Resolution In Building Operation Workstation, right click on the errant I/NET controller and select "Upload" This is expected to fail at this point Browse to the Enterprise Server Directory as displayed in Building Operation Software Administrator Look in the db/Logs folder Locate the trace log and open it using a text editor scroll to the last line of the log and look for an entry that contains inet information. If the error is caused by duplicate point names, this will be the trace log entry: 2014-01-30 20:00:25.587 [6220] nsp.pin.inet.GetAllPoints InetPlugIn::ProcessChangeSetList failed RecoverableException: d:\dev\rb-int-v140-sp1-system\source\packages\commons\components\C3Po\nsp_servers\csc\changesetmanager\source\ChangeSetTransaction.cpp(987) Error: Object_Already_Exists (0x40006), module Runtime_Db_Manager(41), moduleCode 0, dispString "~/INET Interface/0321 - SBOtester/Point1", techString "" Note the text dispString "~/INET Interface/0321 - SBOtester/Point1", techString "" This indicates that there is a point on the controller named "Point1" which is causing the error Option 1: In I/NET workstation, connect to the controller Rename the point indicated above Perform a station save and attempt to upload the controller again. If it fails a second time, repeat steps 3-10 until you have removed all illegal entries Option 2: Use RdInet to view the Save file. Click on Save Page Open the .csv file in Excel and sort the data by Name Locate the Point indicated above and notice that there will be 2 objects of the same name. In I/NET identify these 2 points. Very likely, one will not actually exist. Copy the Point that exists to the address that was indicated as a duplicate in Excel Delete the newly created point to permanently remove the object from the .sav file. Perform a station save and attempt to upload the controller again. Repeat this process if necessary.