Building Automation Knowledge Base

Issue Does Port Based Network Access Control Ethernet 802.1x apply to Continuum controllers? Product Line Andover Continuum Environment Continuum Ethernet Controllers Cyberstation Cause A question that may be asked by Customers IT Departments Resolution No, the 802.1x protocol is not applicable to controllers, it is a Port based Network Access Control (PBNAC) that is used by Routers and computers. It is related to the Operating system user accounts and policies so is above and outside the scope of Continuum. Not all devices support 802.1X authentication. Examples include some network printers, Ethernet-based electronics like environmental sensors, cameras, and wireless phones. For those devices to be used in a protected network environment, alternative mechanisms must be provided to authenticate them. One option would be to disable 802.1X on that port, but that leaves that port unprotected and open for abuse. Another, slightly more reliable option is to use the MAB option. When MAB is configured on a port, that port will first try to check if the connected device is 802.1X compliant, and if no reaction is received from the connected device, it will try to authenticate with the AAA server using the connected device's MAC address as username and password. The network administrator then must make provisions on the RADIUS server to authenticate those MAC-addresses, either by adding them as regular users, or implementing additional logic to resolve them in a network inventory database. Many managed Ethernet switches offer options for this. Network Security is an available option add on for IP level controllers. Please refer to IPSEC and Network Security on Controllers for more information. Another potential option would be to secure the controllers on a separate VLAN.

Issue Muster Report triggered to generate and print Product Line Andover Continuum Environment Muster Reports on a Continuum site Cause With Muster Report loaded, can you trigger from a input (example: fire alarm) for a report to be generated and automatically print? Resolution With some workstation PE programming, you can launch the Muster Report to automatically print. You will need to install and configure the "Plain English Alarm Function" available from Can Plain English interact with the Continuum Alarm Engine? This will trigger a workstation Function each time an alarm is received. You will write PE code to detect the specific alarm and/or point, then "Shell" to launch the Muster Report. Please find the attached Muster Report User Guide and .dmp file which is renamed as .txt file which should be useful.

Issue Knowing the procedure to follow when hosting a site license for the first time with Vista. Product Line TAC Vista Environment Vista Licensing Cause The TAC licensing website is divided up into different areas depending on the task to be performed. An account must be created the first time using the site before creating a license file from the entitlement ID. Resolution Note: In order to rehost an existing Vista license file, see Rehosting a Vista 5 License on the FlexNet License Server. Log onto https://schneider-electric.flexnetoperations.com/flexnet/. Click on the link that says "New User?".   Fill out the entire page with your information. Insert the Entitlement ID that was purchased in the space titled "Activation ID". Once everything has been filled out, click Complete.   This will log you into the Start Page of the licensing site. A temporary password will be emailed to the address you provided on the New User page. This temporary password is required to set your new password which can be done by clicking on Profile in the top right corner of the screen.   Enter the temporary password into the "Old Password" field. Then enter your new password into the "New Password" and "Confirm Password" fields. Click Save.   On the left side of the Start Page, click "Activate" underneath Manage Entitlements.   Check the entitlement ID that you want to use and click Activate.  Fill out all of the information on this page. Click Next.   Click on "Add New Host" at the top of the Server Hosts panel. Select MAC address or Hardware dongle as the Server Hosts. Type in the MAC address of the computer or the dongle ID of the hardware dongle that the license file will be associated too and click OK. In order to find out the MAC address of your computer, reference How to locate a computer's MAC address.   Check the box next to the host name that was just added. Click Next.   Enter the number of licenses you would like to activate in the "Fulfill Count" box and click Verify. The file should verify successfully. Click Next.   Review all of the information. Click Generate.   Select the box next to the newly created license file. Either select to "Save to File" (save a copy of the license file to the local PC) or "Email License" (email the license file to a desired address). Click Complete.  

Issue The TAC Xenta group master is online but not the other Xenta devices in the group. Product Line TAC Vista Environment TAC Vista 5.1.x Classic network Menta 5.1.x Cause The TAC Xenta Group Master is a TAC Xenta 301/302/401/901 (in the TAC Xenta Group) that monitors the on-line and off-line status of the TAC Group and its members. The Group Master forwards the on-line and off-line information to TAC Vista. If devices have been added it's possible that  the current group isn't updated. Resolution The entire Xenta group must know it has a new device for proper communication to occur. To accomplish this download the applications and parameters to the entire group.  If the Group master goes offline, the whole group will be considered off-line by TAC Vista. The separate on-line group members, however, can send alarms and other information directly to TAC Vista as usual. Information about resolving this issue with an LNS network can be found in Xenta Programmable Device is Offline in Vista but Online in LonMaker.

Issue References Guide and changes from release 1.3 to release 1.4.x and forward Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with regards of release 1.3 to release 1.4.x Cause In release 1.3 and earlier the reference system was relaxed allowing for bindings to be created in ways that made the applications error prone. In release 1.4 this is now being more strictly controlled, which will allow the system to: Help the user to not unintentionally create faulty combinations of references, resulting in bad/unpredictable application behavior and last man win situations Better understand and control how references will behave in copy/paste/move/delete situations. Improve performance in the system, e.g. the limitation of variable connectors is removed. For the complete Reference Guide, please download the pdf from the Download Center For instructions on how to upgrade an Automation Server and how to get the conversion log, See Upgrading Automation Servers from 1.3 to 1.4. For explanations of the entries found in the conversion log, See AS Conversion Log Analysis. Resolution What has changed There are 2 areas which have changed:   1. Rules Programmatic control: A reference means that data is sent from A to B. In Release 1.3 it was possible to send data from A to B and from C to B. This gave a "last man win" situation. In Release 1.4 it is only possible to send data from exactly one source to a recipient. This means A to B and C to B is no longer allowed. User control: This is where properties are displayed in graphics, watch windows and other client components. In release 1.3 it was possible to change a property that was programmatically controlled. This gave a "last man win" situation. In release 1.4 it is not possible to change a property as a user if this property is programmatically controlled by something else. The property will automatically be read only for the user.   Public signals: In release 1.3 and earlier, it was possible to programmatically control a public value in programs. Public signals are intended to be used for user control, while inputs are intended for programmatic control. In release 1.4 this is now changed to the following: Public signals in programs (FB/Script/Menta) can be referenced by user control - NOT by programmatic control Public signals intended for programmatic control must be changed to inputs and rebound. This will give the following benefits: Public signals cannot be forced, while inputs can. If a user needs to take control of a programmatically controlled input, via e.g. graphics or watch window", he will force the signal and there will be no risk of a program overwriting the user value. As stated above - if an input is programmatically controlled, this will for the user be read only. However, force is still possible. There is no more risk for "last man wins" situation between user control and programmatic control. The system will remove any ambiguity with these new sets of rules. Update: Release 1.4.1 and later version add the feature of binding to PVB/PVI/PVR back. But for Script, it still keeps the same. LonWorks Local Node nvis: In release 1.3 it was possible to programmatically write to local node NVIs. These NVIs exist to receive data from the LonWorks network. This gave a "last man win" situation. In release 1.4 it is no longer possible to programmatically control local node NVIs.   2. Definitions In release 1.3 a reference could be a) relative b) system absolute c) server absolute In release 1.4 a reference will be a) "normal" b) Locked A reference created by the user will always be normal (which means relative). In the bindings view the user can then choose to "lock" a reference (which means server absolute). The references will behave identically until a copy/paste (or import/export)  operation is done.         Upgrade Upgrading from release 1.3 to release 1.4 will apply the new sets of rules. It is there for very important to read the log to understand if any existing references in release 1.3 will be impacted during the upgrade For AS: In the Device Administrator the logs are available before the upgraded DB is deployed to the AS. It is up to the user to either examine the upgrade log, make changes in running release 1.3 and rerun the upgrade, or to make the changes after upgrade. It is recommended to do changes prior to upgrade to ensure a fully functional system directly after upgrade. Some warnings are benign and can be disregarded, please refer to release notes for more information. IF an upgrade detects that references will be impacted, the user will be informed about this with a orange progress bar indication and a written information that the upgrade succeeded with warnings. After upgrade, all invalid or unresolved references will be visible from WorkStation for further examination if needed.

Issue Many customers still have a requirement to run Lonmaker 3.13, but have project specific issues related to software fixes in newer version of LNS Server, and an LNS Server upgrade is required. Product Line TAC Vista Environment Echelon Lonmaker LNS Cause Older versions of Lonmaker 3.1 and LNS server had multiple defects that were addressed in later version of Lonmaker Turbo and LNS Server Turbo. However, it is possibly to run Lonmaker 3.1 and only upgrade the LNS server engine to take advantage of software fixes over time. Resolution NOTE: Any LNS Server version older than 3.10 needs to first be upgraded to 3.2x before 3.2x service packs can be installed. Also, please take into consideration that after upgrading the LNS Server on a system that any other system that needs to open that same database will have to be at the same version or higher. For example: a database upgraded to 3.27 can not be opened on the machine running 3.08.   Please follow these steps for upgrading LNS server to 3.22 and finally up to 3.27: Identify what version of Lonmaker and LNS server are currently running on the system. Please see How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS Server currently running. As seen in the screen shot below the system is running Lonmaker 3.13.10 with LNS Server version 3.08. Download LNS Server 3.22. Once this file is downloaded please unzip all of the contents to the desktop of the local machine. Run setup.exe from the extracted files in the LNS Server 3.22.zip, and step through the installation process. Once the installation of 3.22 is complete please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.22. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.22 like below: Now that the system is upgraded from LNS Server 3.08 to 3.22, service pack 7 should be installed to upgrade the system to LNS Server 3.27. Please download LNS Server/Turbo edition Service Pack 7 file to your local machine. Unzip the contents of the LNSServerTurboSp7.zip to the desktop of the local machine, and run the LNSturboServerSp7.exe file. Step through the installation process. When the installation is completed please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.27. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.27 like below:

Issue Webclient currently unavailable Error 80070005 Check your DCOM permissions when launching webclient or webclient is currently unavailable. Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A remote reboot will not write DCOM permissions the same way a local reboot does. Other Server configurations can cause this. Resolution A webClient installation was performed using Windows Remote Desktop or some other remote access software and the reboot after the webclient install was executed using the remote software. To fix this, reboot the Webclient server directly from the server itself. There are security permissions that do not get written properly when rebooting remotely and a direct reboot corrects this problem. Start Continuum on the Webclient PC locally, not remotely. Be sure Continuum has been started on the webclient PC. Also see, Webclient unavailable error when attempting to logon which mentions making sure the Network Service is selected for the default app pool. 64-bit OS will cause this error as well. Webclient versions pre 1.94 are not supported on any 64 bit platform. If that doesn't work then a complete reinstall and reboot on the server will be required. Remote installs are typically problematic. If changes were made to .net try the following steps: Start> Run> cmd (Enter)  To get to a DOS prompt cd\Windows\microsoft.net\framework\v2.0.50727 (change directory to this folder) run the command aspnet_regiis.exe -i (It will say installing .net, this re-registers .net with IIS) Restart Windows on the webclient PC and restart Continuum

Issue When trying to add a Xenta 421A, 422A, 451A or 452A I/O module in Menta to a Xenta 300/401, the following warning is displayed. Tam32 Warning, IO modules of type TAC Xenta 421A, 422A, 451A and 452A requires at least system program version 3.6. Environment Menta Vista Xenta 301, 302, 401 Cause To utilize the full functionality of the "A" series I/O modules, the version of Menta and firmware in the associated programmable controller must be compatible. Resolution Use the Xenta 4XXA modules as old 4XX modules The I/O modules with an "A" in the name can be used with programmable controllers earlier than 3.61 as well as Menta earlier than 4.2.2 but the functionality will be limited. The functionality is limited to that of the modules' predecessors, modules without the letter "A" in the name (Xenta 421, 422, 451, 452). The TAC Xenta 421A/422A modules can only have digital inputs and the TAC Xenta 451A/452A modules can only have four 1.8k ohm thermistor and four limited universal inputs (digital input, 1.8k ohm thermistor or 0-10 V). In any running system with TAC Xenta 300/401 version 3.X, TAC Xenta 421, 422, 451, and 452 can be replaced with an "A" module the same way as an old module. The "A" module will detect that it is sitting in an old environment and behave as an old module. Use the full functionality of the Xenta 4XXA modules In order to gain full functionality of the "A" modules, the firmware in the Xenta 300/401 controller must be upgraded to a version 3.61 or higher and Menta must be version 4.2.2 or higher. Instructions on how to download a .MOT file can be found in Download an .MOT file into a Xenta Programmable controller. The additional features of these controllers include all inputs are universal inputs (0-10 V, 0-20 mA, 1.8k ohm and 10k ohm thermistor), universal inputs set as digital inputs can act as a pulse counter, and all configurations, inputs, and outputs can be accessed by means of the SNVT interface. Note: If updating the firmware in a Xenta 300/401 and the following conditions apply than see the Xenta Programmables section of The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Working on a database with multiple Xenta programmable controllers that reference the same device template A firmware version earlier than 3.52 is installed

Issue When upgrading to a different revision of software in I/NET Seven, there are a few steps that are highly recommended to ensure that the database doesn't get corrupted during the upgrade. Product Line TAC INET Environment I/NET Seven Cause Performing an upgrade of I/NET Seven software. Resolution Close I/NET Start DB Create and select the Verify Database option. Verify that the database has 0 differences. Select Upgrade Database to force an upgrade Select the Verify Database option again. Now back up the database to the local drive or media and proceed with the upgrade. Once completed, Select Restore database and proceed to where the back up is and restore the database to the system.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Cannot find any installation instructions documentation for the WorkPlace Tech Tool software, versions 5.8 or 5.8.1. Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.8 & 5.8.1 Cause An updated version of the document "WorkPlace Tech Tool Version 5.7 Installation Instructions" has not yet been released by our publications group. Resolution The existing "I/A Series WorkPlace Tech Tool Version 5.7 Installation Instructions", F-27367 can be used for installing the release 5.8 or release 5.8.1 of the WorkPlace Tech Tool software. There are two items applicable to the newer versions of the WorkPlace Tech Tool software that are not covered in the published installation instructions. The WorkPlace Tech Tool software, releases 5.7.7, 5.8 and 5.8.1 will run on the 32 bit versions of Windows-XP, Windows Vista or Windows-7.  These releases of the software will also run in XP-Mode under the 64-bit version of Windows-7.  See I/A Series (Niagara) R2 Windows Compatibility Matrix and the linked PA-00163 product announcement for more information on Windows 7 compatibility.  Make sure that the computer meets or exceeds the recommended requirements, not the minimum requirements, for the operating system being used. Beginning with release 5.8.5 of the WorkPlace Tech Tool software, Windows 7 64-bit Professional and Microsoft Visio 2010 is supported (32-bit version only), in addition to the documented Microsoft Visio 2003 and Microsoft Visio 2007 (32-bit versions). The use of Visio 2010 and its ribbon bar menu system are described in the WorkPlace Tech Tool release 5.8 release notes.  This same version of the release notes (5.8) is applicable to the use of Visio 2010 with the WorkPlace Tech Tool software release 5.8.1.

Issue What is the unit load of SE8300 that will help me to count how many SE8300 controllers that can be added on AS ComA and ComB Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SER8300 room controller SE8300 room controller Automation Server Cause Documentation does not state the unit load of the SE8000 range Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SE8000 range use the ADM4850A transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/8 UL load. In addition the 100K local bias resistors have been eliminated and therefore the 1/8 UL of the transceiver would be the total UL presented to the bus by the SE8000.   Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus ADM 4850A0 0.125 Yes None None 0.125 Yes** ** Unlike the normally recommended interconnection of the communication common/reference (ground) terminal on all bus devices such as documented in the generic application note for the isolated RS485 bus interfaces, the Viconics bus should be operated with the communications REF (reference) terminal open on each SE8000 and not connected to the bus shield wire, or to any other circuit. Based on the above the total number of devices can be calculated as 32/0.125 = 256 The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore an Automation Server is limited to 127 devices per com port (254 total per AS) so this should effectively be the limiting factor.   Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue When installing the TAC Vista remote workstation, an error message is displayed. Details listed below: TAC Vista Workstation Remote Error 1935. An error occurred during the installation of assembly 'Integral.Common.SystemInfo, Version="7.0.70.0",Culture="neutral", FileVersion="7.0.70.0", ProcessorArchitecture="MSIL", PublicKeyToken="6853E3D8122788A2";. Please refer to Help and Support for more information. Product Line TAC Vista Environment TAC Vista 5.1.7 Workstation Remote (may happens to other version of TAC Vista Workstation Remote). Another version of Vista has been installed Cause When installing Workstation Remote the first time, it will automatically remove the other version of TAC Vista Workstation (ONLY) which has been installed earlier on the same computer. However, it will not remove other parts of TAC Vista (Vista Server, Menta, XBuilder, etc.) and causing the installation of Workstation Remote later crashes. Resolution Follow the instructions in How to uninstall and completely remove TAC Vista 5 to completely remove other parts of TAC Vista. NOTE: if you want to keep the SQL database, you can skip the SQL part.  Restart the computer.  Run the Workstation Remote installation file again. Now the issue should be solved. Corrupt Windows file system transaction log In some cases this error has been the result of the Windows file system transaction log becoming corrupt. Follow the steps found on the Microsoft support website forum to correct this issue.

Issue Replacing Satchwell Sensors with Schneider Electric part numbers Product Line Field Devices Environment Sensors Cause Cross referencing older 'T' type sensors to the current version. Resolution Outside Sensor DOT2301 , DOT0001, DOT0002 is now STO600 Immersion Pipe Sensor DWT1701 (125mm), DWT1702 (200mm), DWT0001 is now STP660 (note, if replacing sensor only then DWA0001 required). Strap On/Pipe Contact Sensor DST1601 , DST0001 is now STC600 Duct Sensor (mainly FCUs) DDU1803 , DDU0001 is now STD670 Duct Sensor DDT1701 (300mm) , DDT1702 (460mm) , DDT0001 is now STD660 Room Sensor DRT3453 (sensor only, no setpoint adjust) is now STR600 For other DR and DRT sensors see Replacements for Satchwell sensors Drayton Room Sensor A701 is now STR600D Drayton Outside Sensor A702 is now STO600D Drayton Immersion Sensor A703 is now STP600D Drayton Strap On / Contact Sensor A704 is now STC600D

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 Alarm Control Panel items created within the Enterprise Server are not been pushed down to the Automation Server. Product Line EcoStruxure Building Operation Environment StruxureWare Buildings Operation 1.3 SP1 Cause There seems to be a corrupt entry in the Automation servers Resolution Log into each Automation server and remove the Lead object from the Alarm panel. Refresh the automation server and the categories are now editable. Delete all user created categories leaving the default Energy Exceptions. Delete all the Cause Notes, Action notes and Check lists. Do the same procedure on all Automation Servers. Log back into the Enterprise Server and then on each Automation server add the Lead object back into the Alarm Control Panel that was removed in step 1. The Enterprise Server will now distribute the entries to the Automation server. If this fails, ensure that all firewalls are open between the AS and the ES. You may want to use the SBO Firewall Config Tool.

Issue Archiving historical information Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Serve Workstation Cause Options for archiving historical information Resolution Archiving of historical data is available via WorkStation and Enterprise Server or WebReports Server. (Archiving is not available via Automation Server or WebStation, also the IE built in option to "Export to Microsoft Excel" has not been implemented) The Archive options on the ES are shown below. A manual archive can be forced by right clicking on "Archive Settings" and choosing "Actions" then "Create archive(s) now" NOTE1 - CSV option currently produces a Semicolon Separated Value file. NOTE2 - Individual logs can be saved to a CSV or XML file from an AS or ES within WorkStation only, see How to Export a Trend Log List as a .csv File.   The .CSV file that is used by SBO to export logs uses a semi colon to separate the fields. This makes it suitable for use in all countries around the world. Some countries use the comma to signify decimal places, so they would show a temperature of 22.5 DegC as 22,5 DegC which would confuse a CSV import with Comma delimiters. CSV files can have many delimiter characters not just commas. To show the formatted data in Microsoft Excel the following options can be used: One option is to rename the SBO log file as a .TXT file, then from Microsoft Excel, go to Open a file and select the type from the drop down list a "Text file". Browse to your log file and press Open. It will then start the Text Import Wizard. Choose the "Delimited" option and go to the next page. Here select the "Semicolon" option, select next, choose a date format and press finish. This will show the data formatted in columns as shown in the manual.   A second way to show the data is to open the .csv file in Microsoft Excel where all the data will be shown as text in the first column as per your description. Select the first column. Then go to the "Data" tab and start the "Text to Columns" Wizard. Select "Delimited" Original Data Type. Press Next. Select the "Semicolon" as the delimiter. Press Next. Change the date format if required and press Finish. This will also show the data in individual cells. Also other vendors Open Office applications may be used that unlike Microsoft Excel will allow semicolon delimited files to be opened directly.

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue Planning an upgrade and need to know which Infinity system controllers can NOT be upgraded to Continuum. Product Line Andover Continuum Environment Infinity Continuum CX9000, CX9100, CX9001, CX9101 CMX220, CMX221, CMX222, CMX230, CMX231, CMX232, CMX240, CMX241, CMX245, CMX246 Cause Some Infinity system controllers can NOT be upgraded to Continuum. Resolution CX9000, CMX220 series,CMX230 series, CMX240 series and CX9500 ranges can not be upgraded to Continuum, all other controllers can be upgraded, some via a chip change, others can be upgraded via Continuum update. The LSX280 Laptop service tool is not compatible with Continuum, a RoamIO should be used. Check out the Software and Firmware compatibility matrix for older versions of the traditional product lines for the minimum versions required for Cyberstation, but the following gives an overview of the requirements: CX9200 (CX9300,CX9201) - Requires chip replacement with Continuum firmware V1.5x CX9400 Eclipse (CX9410) - Requires flash upgrade to Continuum V1.5x firmware, but will require working SX8000 system to flash the controller, otherwise send to Repairs for upgrading. ACX780 -  Requires chip replacement with Continuum firmware V1.5x ACX781C ACX700 -  Requires chip replacement with Continuum firmware V1.5x ACX701C DCX250 - Requires Infinity V2.16 firmware chip Other i1 (generation 1 infinet controller) controllers require a minimum of V1.4 firmware chips

Issue Upgrading an AS results in an empty database. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 StruxureWare Building Operation 1.1.0.362 to 1.2.0.767  Cause When upgrading the database, the Enterprise Server (ES) upgrades without error, but when upgrading the AS, the result is an empty database. Resolution StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 The problem is caused by the initial engineering of the system being carried out on an old AS that was not LON or BACnet specific, copying into new hardware at R1.0 then when upgraded to R1.1 the upgrade fails due to the wrong type of AS being used (LON or BACnet). This practice is not common place and rather rare. When the trace log is examined, they find that the upgrade fails due to the fact that an illegal object type is attempted to be created – a BACnet interface. This is not legal in an AS-L. The reason that this occurs is that the backup file is from an AS-L that had been restored from a 1.0 AS-B backup file. Check New Release or Upgrade StruxureWare Building Operation Site Software. The issue you face could possibly be a procedural one and this article clearly defines the steps. StruxureWare Building Operation 1.1.0.362 to 1.2.0.767 The solution is identifying problems with a period, space, or other character in names. Placing a period at the end of a name or accidentally having a space at the end is suggesting something is following or further action. If using BACnet, please see the note below. Problems with bindings which were still in tact when values were removed also are a potential issue and not properly removed.    Work Around: Backup AS Upgrade PC to 1.2 Open Device Administrator Upgrade AS to 1.2 DO NOT close Device Administrator Open StruxureWare Workstation Log into AS If Database is Blank go back to Web Browser Connect to AS Log in In the top right hand corner of the screen select Setting>Device Configuration Select the Server Log tab Click “Get all log files” Once downloaded, open “trace” using Notepad Click Edit>Find Type the word “nsp.csc.UpgradeManager ERROR:” The error lines run from date stamp to date stamp so isolate the line beginning with the year and ending with the next instance of the year. Here is an example: 2012-08-29 16:39:32.990 [32] nsp.csc.UpgradeManager ERROR:    Error Parsing Dump Objects:  RecoverableException: source/Path.cppy) ) Error: Invalid_Path (0x10001), module Coml(11), moduleCode 0, dispString "Heatsink Temp.", techString "Path& Path::Append(const UTF8String& name)"  The “dispString “_______”” section of this line will give you the object name that contains an illegal character. Downgrade the AS back to 1.1 Locate the dispString object and change the name so that it does not contain any illegal characters. This is typically a name ending in a period. NOTE: when the rename dialogue pops up, it will indicate that an illegal character is present to confirm you are modifying the right object. Backup the AS Re-Upgrade the AS to 1.2 If the upgrade fails, repeat steps 9-20 or call product support. Be prepared to provide a Db backup at 1.1 as well as the trace file from the 1.2 failed upgrade. BACnet Note: A BACnet device including an object name "East Duct Max." is no longer valid because of the illegal character at the end of the name. Before upgrading the ES from 1.1 to 1.2, remove any full stops/periods from any object names. "East Duct Max." is changed to "East Duct Max"  Other illegal characters include *°?|/"<> or ~ and an object cannot begin or end with a white space or period. Select TPA-SBO-12-0008.00 - ES upgraded from 1.1 to 1.2 loses database to review this TPA.

Issue The ZigBee network configuration parameters (Channel and PAN ID) of the MPM matches those of the room controller, but the room controller will not come online. Symptoms: For SE(R)8000 Series: The "ZigBee Short" field in the "Network" menu option keeps changing. For SE(R)7000 Series: The Green LED is blinking twice where 3 blinks are expected. (Description of LED status defined in LED status for SE7000 Room Controller ZigBee communication module) Product Line EcoStruxure Building Expert, Field Devices Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350 Viconics branding VT8000 Series Cause A temporary bug causes the MPM to prevent a specific ZigBee com module (installed inside the room controller) from joining the network on a particular channel. Resolution MPM has to be reset using one of the following methods Method 1: Unplug and replug power to the MPM Method 2: Click on the "Restart Controller" button as shown in image below. Note: Database must be saved before restarting the controller to avoid loss of data.    

Issue Links not working after TGML conversion Converting I/NET graphics to TGML using the "Create Source Tree" option Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.44 Cause I/NET stored graphics on the hard disk and allowed for complex folder structures to be used in organizing those graphics. When these graphics are converted to TGML, this structure may need to be preserved in order to prevent duplicate graphic names. Resolution For this example I have created a site with 3 buildings containing Identical I/NET graphics. Each Building has a summary page and a VAV page. All pages link back to a home page. In I/NET select System>Export Graphics to TGML(you can also right click on the I/NET interface in StruxureWare Workstation) Set your Source and Destination Path and click All Yes.  When you set your destination path, it must point to a folder that already exists in Windows.  The Export INET Graphics to TGML tool does not create this directory Notice that the default setting is to "Use destination path" If we click convert with that option, we will get only 3 graphics.  The graphics from other folders with the same name are over-written. Select the "Create Source Tree" option, ensure the correct graphics are scheduled to convert and click convert. Notice that In Windows Explorer a new folder structure is created that is identical to the original folder structure. Open StruxureWare Workstation. Create a folder system that matches what is on the Hard disk. Drag and drop the TGML files from Windows explorer to the corresponding folders in StruxureWare Workstation. Test you graphic links to ensure everything is functional. Note: Once the graphics are imported, StruxureWare will allow you to move them freely without breaking the binding between pages. There is another way to import all the I/NET graphic folders in one time. Refer to Import all converted I/NET graphic folders into EcoStruxure at one time.