Issue Using Schneider Electric actuators with competitors' globe valves Product Line Field Devices Environment Schneider Electric actuators (Americas field devices) 3rd party globe valves Cause To replace 3rd party / competitor valve actuators with Schneider Electric valve actuators, a linkage / adapter may be required to install the Schneider Electric actuator onto the 3rd party / competitor valve.  Resolution Refer to the AV-800 Series Competitive Globe Valve Adapters Selection Guide for a list of adapter kits, recommended Schneider Electric actuators and supported 3rd party / competitors' globe valves (Johnson Controls, Siemens, Honeywell).  The Selection Guide can also be downloaded from the Publication Zone with iPortal. If you do not have access to the iPortal, use the guest access credentials. Once you have logged on, go to 'Links' > 'Publication Zone'.  Installation instructions showing assembly drawings can be downloaded here.

Issue For various reasons, it is sometimes necessary to change a b3's mac ID. For example, a b3 that is removed from a site and will later be used at a different site needs to have its mac id reset to factory default to avoid the possibility of introducing a duplicate mac id. NOTE: To set the MAC ID to the factory default you need BACnet Service Tool version 1.110004 or newer.   Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b3 Controller Continuum Service Tool RoamIO2 BACnet Service Tool Cause The MAC ID needs to be set or changed on a b3 controller. Resolution IMPORTANT: If the b3 has previously been assigned a valid mac id then proceed to step #1. If the b3 has factory default slave mac id then see  CHANGING MAC ID ON A BRAND NEW B3 FROM THE FACTORY below Make sure the b3 is disconnected from the MSTP network then connect the RoamIO2 directly to the b3 using the service port. Launch the BACnet Service Tool and de-select the 'By Networks' and 'BACnet only' menu options in the view menu. Click the green icon to make the RoamIO2 sync to the baud rate of the b3 and discover it. In the 'Tools' menu select 'Set Offline B3 Mac Id' as shown below.  In the 'Modify MAC Id' window enter the b3's serial number and the new mac id to be set then click Apply. (NOTE: To set the MAC ID to factory default enter 172, DO NOT USE ZERO) To set the MAC Id to the factory default you need BACnet Service Tool version 1.110004 or newer. Tested working on beta version 1.119903). This beta version is attached. Download it and remove the .txt at the end to make it a zip file, unzip then see the readme.txt. A feedback message 'Success! will be returned if the MAC id was changed EXCEPT when setting the MAC Id to factory default (172) When setting the MAC Id to the factory default you will NOT get SUCCESS feedback, this is because the default id of 172 is a slave id (chosen because in hex it is AC for Andover Controls). Slave Ids are not allowed to initiate communication on the MSTP network. So, as a result of that, the b3 is unable to report to the RoamIO2 that the id was successfully changed. A visual sign that the ID was changed to 172 is that the TD led on the b3's RS485 port will shut off. Disconnect and re-connect to have the RoamIO2 communicate with the b3 using the new MAC id (unless you changed it to the factory default of 172). CHANGING MAC ID ON A BRAND NEW B3 FROM THE FACTORY The RoamIO2 can also be used to assign a mac id to a brand new b3 which has a factory default mac id of 0xAC (172 decimal) but the steps are a little different. In order for a RoamIO2 to be able to send communication packets to the b3, it first has to sync up with the baud rate of the b3, it does by listening and analyzing the packets sent by the b3 until it is able to determine the baud rate. As mentioned before, the factory default mac id of a b3 is slave id 172 which prohibits the b3s from sending out packets and makes it impossible for the RoamIO2 to determine the baud rate. There are several ways to work around the baud rate issue... Set the baud rate manually. Click on the green icon to attempt to connect the RoamIO2 to the b3. You will get an error that the baud rate could not be determined, click YES to proceed anyway From the 'Tools' menu select 'Set B3 Baud Rate' and set the baud rate to what you believe the last baud rate was for the b3. (The factory default baud rate is 19200) You should now be able to set the mac id per the steps above. NOTE: You may have to try all the baud rates until you find the one the b3 is operating at.

Issue Unable to assign output channels on a some b3/i2 series controller under an AS. CCT(Continuum Conversion Tool) unable to assign channel with error "Could not find channel" in the conversion report. When creating an output channel, that is out of range, the workstation error is "Could not find channel" eg. if output channels 15 or 16 (on b3810) are assigned Product Line EcoStruxure Building Operation Environment AS ES b3, i2 Expansion Module xPD04, XPD02, xPA04, xPA02 Cause b3/i2 series expansion channels are software limited in line with the maximum xP module capacity The maximum b3/i2 expansion current available is 180mA, so some combinations of 2 xP modules are not supported, see below   Resolution Both input and output channels are limited in line with the allowable xP expansion units that can be added. For example a maximum of 6 xP output channels can be added to b3/i2920, b3/i2810, b3/i2814, b3/i2850, b3/i2851 & b3/i2853 controllers, (2 xPD/A04 Output modules is above the maximum power supply to xP units from the b3/i2 series controllers)                                   Output Channels               On board                               xP Modules    b3920     1 to 16                                   18 to 22 b3810     1 to 8                                      9 to 14 b3814     1 to 8                                      9 to 14 b3850     1 to 4 (5 reserved)                  6 to 11 b3851     1 to 4 (5 reserved)                  6 to 11 b3853     1 to 4 (5 reserved)                  6 to 11 NOTE Continuum did not limit the channel numbers, thus unsupported configuration could be installed and in some cases these may work. This can cause an issue during an upgrade/conversion.

Issue How to order more NL credits in order to commission more devices. If the following message displays when opening a NL220 database, then more credits will need to be purchased soon. " BEWARE: less than 20 credits are available on this machine. If you need to install more than 20 device please order the amount of needed credits as soon as possible. Do you want to ask for new credits?" Product Line TAC IA Series, TAC Vista Environment NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   Echelon LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. Echelon LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. Newron NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LNS credits see Ordering more LNS credits. To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. Resolution When working in NL220, it is wise to maintain a higher level of LNS credits than NL credits to help avoid locking out the LNS server license. To check the amount of NL credits remaining go to Start > All Programs > NL Suite > NLCreditsGenerator and look for Remaining NLCredits. The number of NL credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open. To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available. The number of LNS credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open.   To order more NL220 credits: Open the NLCreditsGenerator Utility that is installed with NL220. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Enter the number of NL220 credits to be added  in the request area. Click Next. Click "Yes, this PC will be used for commissioning" Enter your name and contact details. Select "Copy to clipboard". Then either paste the information into notepad or in an email. Send the NL credit request to your local Schneider Electric Buildings Business order department  (NLCredits@buildings.schneider-electric.com). When you order has been processed by the local Schneider Electric Buildings Business order department you will receive an upgrade key. Open the NLCreditsGenerator Utility again. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Click the Next button. Enter the key into the "Upgrade key" field of the credits generator. A message indicating you credits were added is then displayed.   Note: Once the request key has been generated, DO NOT commission or decommission any devices with the dongle until the upgrade key has been applied to the dongle. If devices are commissioned before then, the upgrade key will no longer be valid.

Issue 7771 (Modbus ICI) will not keep station address after station restore. Environment I/NET Seven 7771 (Modbus ICI) Cause The cause is the EEPROM rev in that unit. Resolution Update EEPROM to version 3.32 to work correctly in I/NET Seven.

Issue A site configured a schedule to have 2 different holiday durations during a spring break holiday week. The schedule is not working as expected. The Holiday week is set up as a range for Monday - Friday and assigned to a single Holiday group.   Two new schedule durations have been added with the respective days selected that they would like the durations to activate on. On the 2 new durations, they added the Holiday group in the "Always Active On" area.   Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Access Expert V3 Premise Cause Holiday and special date durations will activate on the holiday dates regardless of the day(s) of the week selected in the scheduled duration. The day(s) of week checkboxes in each duration is only used for setting a recurring weekly activation on those days and are not required for Holidays. For durations that will only be used during holidays, do not select any day(s) of the week. Resolution In this case, since you need two different durations during your holiday week, you will need two new durations but with different holiday groups for each duration. Set the M, W, and F duration as holiday group A and T, R for holiday group B. Now apply the Holiday Groups to the right dates via the Holidays Menu.      

Issue It has come to our attention that people are using Backup and Restore to duplicate Automation Server databases, this is not supported and should not be used as it results in various issues.  Some of the known issues at this time are listed below: When attempting to update Server IP addresses using the advanced feature "Repair server communication"; one or more Automation Servers are listed as Offline even though they are shown as Online within the System Tree. (Click on image for larger view)   When performing a backup / restore from the Enterprise Server the Automation Server(s) are not listed as part of the Child view.    Right-clicking on the Automation Server does not give all the options available and most are grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server 1.2, 1.3, 1.4 and 1.5 Cause This situation arises because each Automation Server receives a unique identifier, global unique identifier (GUID), when using the backup and restore function this GUID is retained.  Therefore when restored to other Automation Servers these will retain the same identifier.  The only course of action available within this environment is to detach the Automation Server from the Enterprise Server and create a new database from scratch. The correct duplication process across Automation Servers is to use the export and import feature or copy and paste (drag and drop) across Automation Servers.   Resolution StruxureWare Building Operation 1.6 and above update:   You can now use the Restore function to re-use the configuration data from a backup set in a new standalone Automation Server. Rather than manually configuring your preferred Automation Server configuration, you can save time and configure the standalone Automation Server from a backup set. Online help topic: Duplicating an Automation Server Using Restore Backup and Restore feature should NOT be used to duplicate multiple Automation Server's databases it should only be backed up and restored to the same server.  Instead the Export / Import and copy and past features are designed for this function.   A warning note in the Technical Reference and IT Reference guides (versions 1.2, 1.3, & 1.4) has been added warning the users not to use the backup and restore function for duplication.  See the online StruxureWare WebHelp for this current Important Note (login required): Backup and Restore Overview However if you have this situation then it may be possible to recover some or most of the database, please contact Product Support and reference this article number so that this issue can be confirmed.  

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (511/555/527/913) can not create Menta object. Xenta Server (701 and 913) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server version after 5.1.5 (5.1.5 included) TAC XBuilder version after 5.1.5 (5.1.5 included) Vista, I/NET, LON, MicroNet, ModBus Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.5 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Menta Supp. Xenta 511 X       X C   X   Xenta 527 X X     X C   X   Xenta 527-NPR   X       S       Xenta 555 X   X   X C   X   Xenta701 X       X ST 10   X Xenta 711 X       X C 10 X X Xenta 721 X       X ST 20 X X Xenta 731 X X X   X C 20 X X Xenta 913 *** X X   X X S       * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service. NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.4 major features, please read Xenta Server 5.1.4 Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue Various controller install guides suggest fitment of an optional varistor for surge/spike protection, what components should be used? Product Line Andover Continuum Environment Surge and transient protection Metal Oxide Varistors (MOV) Part Number Line voltage protection, power line protection, mains spike protection. Noise, EMC resilience. Cause Install guides specify 39V, 130V or 250V varistors but what component part numbers should be used? Resolution For controllers with a 24VAC power feed, these are specified as a 39V Varistor, a suitable component would be: V39ZA1 This is also equivalent to Part # 01-2020-095 as listed in some install guides. For controllers fed from a 115VAC power feed, these are specified as a 130V Varistor, a suitable component would be: V130LA20A For controllers fed from a 230VAC power feed, these are specified as a 250V Varistor, a suitable component would be: V250LA40A Littelfuse Varistor ZA Datasheet PDF showing the full specification for each varistors is attached.

Issue The hostId for a computer running I/A Series G3 version 3.8u1 (or earlier) and N4 versions 4.2 (or earlier) may be changed from the result of a Windows update. Product Line TAC IA Series Environment I/A Series G3  I/A Series N4  Cause The hostId is automatically generated upon first install of the software and stored within the registry.  The location of the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update.The hostId is automatically generated upon first install of the software and stored within the registry.  The location of    the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. Resolution I/A Series G3 version 3.8.213 (or higher) and I/A Series N4 version 4.3.58.18 (or higher) have been modified to guard against Windows updates to prevent hostId changes.  Installations of N4 4.3 and/or G3 3.8u2 will continue to operate normally and will not assume a new hostid after a Windows update.  All previous versions of Niagara could generate a new hostid after a Windows update, requiring a license replacement.   Schneider Electric recommends updating I/A Series G3 and N4 installations to the latest released software in order to maintain the latest security protection and to gain benefit from the latest features.  These builds are:   I/A Series 3.8 Update 2 (3.8.213 and later) I/A Series 4.4 (and later)   Patch to address multiple Host IDs on a single Microsoft Windows© platform   A set of patch files have been created to stabilize the Host ID for cases where customers have not upgraded to the latest version of Niagara (see installation instructions below). Once these patches are applied to the older versions of Workbench the Host ID is stabilized and should not change if Windows updates are installed.   Note: This is a reminder that a 32-bit install will always generate a different host-id than a 64-bit install.   IMPORTANT NOTES REGARDING THE PATCHES   Patches are only supported for the latest update (maintenance) version for the relevant release. Patches are not available for I/A Series G3 release 3.5 and earlier, or I/A Series N4 release 4.0 or 4.1. Builds prior to G3 3.8.213 are considered unsupported. Customers applying these patches do so at their own risk. Newer versions of Niagara (3.8U2 and 4.3) have introduced a stabilized method of managing the Host ID and do not require any patch. The patches do not eliminate the issue of different Host IDs generated when installing 32-bit and 64-bit Niagara. Installation Instructions   The Host ID patch file is available for download on the EcoBuilding Exchange Download website.  Login to the Schneider Electric EcoBuilding Exchange Download Center and enter G3 and N4 Host ID Patches in the search area or the filename of the zip shown below.    Download the G3_N4_HOSTID_PATCHES.zip and unzip into a temporary folder. The archive contains 'nre.dll' for various versions of I/A Series G3 and Series 4.2 in a directory structure identifying them first by version and sub-directory identifying 64-bit or 32-bit Windows. The 4.2 folder also contains 'njre.dll' which will need to be copied only for 4.2 installations.  Follow these instructions:   Verify the installed java version to be either 64-bit or 32-bit. Start a Niagara Command Line (Home>/bin/console.exe) from the desktop of the platform to be patched. From the Niagara Command Line execute the command: nre -version One of the listed items will be java.vm.name. If the text contains “64-Bit” then the installation is 64-bit otherwise the installation is 32-bit. Stop any running station using Workbench's Platform Application Director on the platform to be patched. Exit Workbench if running on the platform to be patched. From the Niagara Command Line ... /bin/console.exe execute the command: plat uninstalldaemon  Prior to replacement, save a copy of the existing nre.dll located in /bin folder. If Niagara 4.2 is being updated also save a copy of the existing njre.dll located in /bin folder. Copy the version appropriate and OS appropriate (64-bit or 32-bit) downloaded version of nre.dll file to the Home>/bin folder. If Niagara 4.2 also copy njre.dll to /bin folder. Overwrite the existing file(s). From the Niagara Command Line (/bin/console.exe) execute: plat installdaemon Start Workbench.  Open a platform connection to the patched platform. Using the Application Director, start the station.  

Issue An application created using WorkPlace Tech was working properly when created.  As many additional changes have been made to the application, unchanged portions of the application that were working no longer work correctly. Some observed examples of this issue are as follows: MNB-1000 application that includes the ADI interface worked when the first few ADI points were linked but after moving the application to another computer and linking the remaining ADI points, the ADI interface no longer worked. Hardware I/O points are not being properly handled after editing, compiling and downloading the application to the target controller.  This application was originally created on a different computer but with the same version of the WPT software. When downloading an application to the controller, WorkPlace Tech reports "Unknown error" but no errors were reported when compiling the application. Connecting lines that are a valid connection but are displayed as a red line. Application not correctly using configuration as specified by Hardware Wizard even though Hardware Wizard has been run and appeared to properly configure the application. Some internal program objects do not appear to operate as documented. Environment WorkPlace Tech Tool version 5.x.x Cause If the application data stored in the WorkPlace Tech application drawing file (vsd file) becomes corrupted, the application continues to compile correctly but does not operate.  This corruption is not observed on the drawing itself.  The application data and drawing data are independent of each other within the Visio file.  In some cases, an application created in WPT 4.x may contain application database information that is not correctly recognized by WPT 5.x.x. Resolution After opening the application in the WorkPlace Tech Tool software, run the "Rebuild Application" function to rebuild the internal representation of the application database.  The location of the "Rebuild Application" function in the Visio menu varies depending on the version of Visio that is running the WorkPlace Tech Tool software.  When starting the Rebuild function, a Windows WARNING dialog box is displayed.  To accept the displayed conditions of the Application Rebuild function, click the [Yes] button.  Further information on the information displayed in the dialog box is shown in the NOTE and Warning paragraphs, below. If using a version of Visio prior to Visio-2010, i.e., no ribbon bar, and WorkPlace Tech Tool version 5.6 or 5.7.x, the "Rebuild Application" function is found under the "Application" menu. If using Visio-2010 with WorkPlace Tech Tool version 5.8, the "Rebuild" function is found under the Application menu of the WorkPlace Tech ribbon bar. Note: After rebuilding the application database, the object order of any or all of the control objects may change.  If an attempt is made to monitor the controller containing this application, without downloading the rebuilt application to the controller, the monitor tags may display incorrect information. Warning:  Before running the "Rebuild Application" function on an application for a MNL-800 controller, confirm that index numbers have been properly assigned to ALL LON network variables and constants used in the application.  Failure to confirm that all LON network variables and constants have been manually indexed could result in changes to the LON application profile (XIF file).  This will result in binding issues between the controller LON network variables and other devices on the LON network.

Issue When attempting to rename a newly created Enterprise Server, the following validation error may be encountered: "Validation failed for property 'HttpPort' Path: 'Enterprise Server/HttpPort' Type: 'HttpPort' The value '0' is outside the range of allowed values" Product Line EcoStruxure Building Operation Environment Enterprise Server Cause Although the error message references an invalid HTTP port assignment, the underlying issue is typically related to the Enterprise Server's certificate configuration. This scenario often arises when a new Enterprise Server is created from a backup containing a base configuration, which includes an outdated or incompatible certificate. Resolution To resolve the issue: Remove the active certificate associated with the Enterprise Server. EBO WebHelp documentation for detailed instructions on certificate removal: Removing a Certificate Using WorkStation  Once the certificate is removed, the renaming operation should proceed without triggering the validation error.

Issue When editing an EBO graphic in Webstation rather than Workstation, there is an inherent feature which allows a user to zoom in and out of the graphic using the mouse scroll. They can also pan around the page by holding down the left mouse button as they move. In many cases however, this feature is not wanted and makes the graphic more difficult to use. Image Zoomed Out  Image Zoomed In and Panned Right Product Line Building Operation Webstation Environment Graphics Cause Pan and Zoom in Webstation are features that are enabled by default in all TGML Graphics Resolution Edit the graphic object and select the top TGML root of the page properties. There is a 'Disable Pan and Zoom' option which by default is set to False.  Setting this option to True and then saving turns off the Pan and Zoom functions for that graphic

Issue DBCreate database restore fails with error message: "The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally." Product Line TAC INET Environment I/NET Seven SQL Server 2000 all editions and SQL 2005 all editions Cause It is not possible to restore a SQL Database which was backed up using SQL 2005 back into a SQL 2000 database. Resolution The simplest method to rectify this problem would be to uninstall I/NET and SQL (Refer to Procedure for uninstalling I/NET Seven on a stand-alone host on how to do this) and then re-install I/NET using SQL 2005. The second method would be to upgrade the installed MSDE Default instance to SQL 2005 Express. There is a published white paper from Microsoft on this and is attached here: MSDEtoSQLExpress.doc.  Refer to the steps on page 11 to 14. The SQLExpress installation file is available on the I/NET CD under the folder SQLExpress\.SQLEXPR32.EXE. After performing these steps its advisable to run up DBCreate and upgrade the SQL database.

Issue How do I set up a Continuum system to do automatic log truncation to save database space? Product Line Andover Continuum Environment Continuum Trend logs Cause Database maintenance. Resolution Setting up Automatic Log Truncation with SQL Server and MSDE Database  MSDE Engine For MSDE, you can download the Stand Alone MSDE Database Utilities from Buildings Download Center.  These utilities are capable of automatically truncating the logs, as well making automated backups, checking for low hard drive space, etc.  SQL Server For full SQL Server, you can easily create a scheduled Job. Details are described below.   To create a scheduled Job that will truncate the Continuum logs in the SQL Server: Open up SQL Enterprise Manager  (Note that the SQL Server Agent service must be running in order to create a Job) Highlight the Continuum database From the Menu, select Tools \ Job Scheduling A wizard opens: "Welcome to the Create Job Wizard." Click Next Select Transact-SQL Command,  Click Next For the Database Name, select ContinuumDB (or whatever the name of the DB is) In the large white space for the Transact-SQL Command, cut and paste the code from our web site: ****** Replace 90 with the number of days to maintain in each log ******** delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 Click Next On the next screen, you are asked when you do want to run this job Select "On a recurring basis" and hit the Schedule button On the Schedule page, set up whatever schedule you desire Click OK to close the Schedule Page • Click Next On the Job Notifications screen, you can choose (if you want) any email or net send alerts. This is optional • Click Next In the final page, you are given a summary of the Job you have just created and you can change the name of your Job to anything you want. It might be a good idea to give it a more descriptive name like "Weekly Log Truncation" Click Finish and you are done. You should get a message that the job was created successfully. To verify that the Job is running correctly, you can go to the Enterprise Manager of SQL Server and click on the Management Folder, then expand the SQL Server Agent folder and click on Jobs. On the right-hand pane, you will see a list of created jobs. Scroll down and find the job that you just created. You can get information about the history of the Job, whether it ran successfully or not.

Issue Troubleshooting 2-Output PWM on a Xenta 102-AX Floating actuator for heating applications (hot water valve) Product Line TAC Vista Environment Xenta 102-AX PWM_2 floating hot water valve actuator Cause Multiple causes legitimately keep the hot water valve two-out floating control from stroking. Resolution The Xenta 102-AX controller supports auxiliary heat with two outputs. Both outputs can be utilized in a 2-output pulse width modulated (PWM) signal for control of floating actuators. This document suggests troubleshooting techniques to help narrow down the cause of improper operation of these hot water valve outputs. Start with Universal Output #2 On the Status tab of the 102-AX Plug-in, each of the universal outputs are listed under the “Network Bound Inputs” column. In the 102-AX Plug-in version 5.1.4, this column has been erroneously omitted. Download TAC Toolpack version 5.1.4 Hotfix 72 from the Buildings Business Extranet to resolve the issue. The output that represents the 2-output PWM is Universal Output #2 only. Even though output #3 is involved in the process, only #2 in the Plug-in represents the actuator position. The first thing to do is override the output to three different positions: 0, 50 and 100%. Cycling between three different values ensures the actuator is actively stroking. Forcing the valve to 100% will cause the open signal to energize for the full stroke time (throttling range) of the actuator, after which it will be de-energized. Wiring problems discovered after this time period has elapsed would require the output to be forced to 0% and then back to 100% to energize the open signal for the full stroke time again.   Figure 1. Network Bound Inputs If the valve strokes correctly, then the unit parameters, wiring, and actuator are all correctly configured. Skip directly to the chapter entitled “Overriding the Output Successfully Stroked the Actuator.” If the valve did not successfully stroke, proceed to the next chapter where three possible problems are addressed. Overriding the Output Failed to Stroke the Actuator There are three main reasons why overriding the output would fail to stroke the actuator. Unit Parameters The Unit Parameters tab of the 102-AX Plug-in is where Universal Outputs #2 and #3 are configured to work in tandem to accomplish 2-Output PWM control of a floating actuator. Heat 1 configures both outputs when OUTPUT_PWM_2 is selected. There is no need to configure Heat 2. Changes to Heat 2 will have no effect on the heating operation.   Figure 2. Heat 1 Unit Parameters Make sure the output type is set for OUTPUT_PWM_2. The stroke time should match the manufacturer’s documented stroke time of the actuator. Delay on start and stop are dictated by user preference or customer specifications. Normal Stroke should be set for normally closed. Wiring Check the wiring of the actuator to the 102-AX. It should be wired as follows: Point Label Terminal Actuator Universal Output #2 V2 15 OPEN Universal Output #3 V3 16 CLOSE Ground G0 13 COM Actuator The last step to troubleshoot an issue with the actuator not moving is to test the actuator itself. This can be done by jumping out the open or close leg of the actuator to 24Vac power. If the actuator still does not move then it is faulty and should be replaced. Overriding the Output Successfully Stroked the Actuator If overriding the output causes the valve to move accordingly, then the configuration of the output and the physical configuration are all correct. The 102-AX controller logic is not calling for the valve to open. There are a number of reasons why this might be occurring. The Basics The 102-AX must be in a heating mode to open the valve (cooling mode will close the actuator). It may be displaying either HVAC_HEAT or HVAC_MRNG_WARMUP. The space temperature must be below the effective setpoint to be in heat mode and will generate a negative terminal load down to -100%. The terminal load will equal the heating valve position. Check that the heating/cooling setpoints and heating/cooling bands are set such that no overlap in the two modes occurs. Heating/cooling bands must be greater than 0°. Hardware Configuration If the 102-AX is not configured for a sufficient number of stages of heat, it will not cycle the valve. If there is no fan, then only one stage of heat needs to be defined. However, if a fan is defined, then there needs to be at least two stages of heat, because the fan is considered the first stage.   Figure 3. Fan Type and Heat Stage If the heating valve is to be utilized in morning warm up mode (when the duct inlet temperature indicates that the air handling unit is providing central plant heat), then the hardware configuration must state that supplemental heat is allowed during warm up.   Figure 4. Enable Heat on Warm Up If a supply temperature sensor is wired to Universal Input #1, it could be that it is sending the VAV into morning warm up mode when the heat is enabled, and thus, disabling the heat. If this is the case, there are two options. Universal Input #3 can be used instead and set as an outside air temperature. Alternatively, Universal Input #1 can be configured as "None."   Figure 5. Input 1 Selection Setting Input 1 Selection to "None" will not disable the reading of the sensor. UnivIn1_Sense.nvoAuxTemp1 will continue to report the duct supply temperature. Setting it to "None" disables the signal from affecting the internal logic – preventing the 102-AX from entering morning warm up mode. Note: If the VAV is already in morning warm up mode when the input is set to "None," the box will remain in morning warm up mode. Override the input temperature to something below room temperature prior to changing the input selection. Application Mode The SNVT input VAV_Controller.nviApplicMode can allow a supervisory controller to override the current mode of the VAV. Upon receipt of a new application mode, the 102-AX will encounter a brief synchronization period where the terminal load is held to 0%. If the SNVT is being sent from a data manager, and the period on the output SNVT in Menta is set to 60 seconds, then the 102-AX will zero out the terminal load every 60 seconds, preventing proper operation. Set the SNVT output to a period of 0 seconds, and it will only write a new value on change and allow proper external control of the mode. Airflow Setpoint The Warm up Maximum airflow setpoint must be greater than or equal to the Heating Minimum airflow setpoint.  If this is not the case, then the airflow setpoint will default to the unoccupied flow setpoint (typically 0 CFM) any time the VAV is in heat mode, and the heating output will not be utilized.  This can be easily overlooked in applications where Warm up Mode is not being used, but this one parameter must still be set. This is fixed in the Xenta 102-AX firmware v2.18.   Figure 6. Airflow Setpoint Actual Airflow In order for the heating outputs to be energized, the airflow must be at least 80% of the minimum heating airflow setpoint. This is hard coded into the controller and cannot be disabled. The only way to remove the interlock is to set the minimum heating airflow setpoint to 0 CFM; however, in this situation, the VAV will close the damper in an attempt to provide 0 CFM of airflow. The heating will modulate without any airflow at that point.   Figure 7. VAV Status not providing 80% Airflow Check on the VAV Status tab of the 102-AX plug-in to compare the airflow to the airflow setpoint. If the box cannot provide the necessary 80% of setpoint or there is no airflow available during the commissioning stage, lowering the airflow setpoint can allow checkout to continue. This 80% airflow requirement is looking at the on-board flow sensor of the Xenta 102-AX. If the flow value is coming from another controller on the network via the nviBoxFlow SNVT, the heat will be disabled. The nviBoxFlow input will override flow values for damper control, but heating outputs will ignore it. In this situation, setting the pressure offset (UCPToffsetPress) to 1” will bypass the limitation. This will be fixed in the Xenta 102-AX firmware v2.18. Wrap Up If everything is configured properly physically and in the 102-AX Plug-in, then the box should be stroking the valve to maintain the space temperature setpoint. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta 102-AX. If further assistance is required, or if you would like to add to steps suggested here, call or email Schneider Electric Product Support.

Issue Can the backplane, which consists of the Power Supply, Automation Server, and I/O Modules be installed in the cabinet horizontally or vertically? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation hardware installation in a cabinet with limited space. Cause Customer would prefer vertical installation rather than the typical horizontal installation. More than one Automation Server per Power Supply** Resolution What could happen if you mount the system vertically? Due to the lack of ventilation the temperature will increase, which will have negative impact on component life time. The operational temperature is defined up to +50°C. At this temperature, the horizontally mounted system will fulfill the specified lifetime of the different electrical components. In a vertically mounted system the temperature will be higher inside the modules, having negative impact on the component lifetime. Unfortunately it is not a linear relationship between temperature and lifetime - the lifetime decreases rapidly with increased temperature. Not all modules are generating the same amount of heat, and are therefore more or less sensitive to mounting direction. In my view, the most critical component is the AS. The CPU generates heat (even more important on the coming AS-P). In the AS there are also critical components that maintains power during shut-down. These component's life time is effected if the temperature becomes too hot. These components are, as stated, critical during power-down. How will this be visible to the user? During normal operation, there will be no visible effect. However, after some years when the AS goes through a power cycle, it will not restart. So, what to do if you have a cabinet with the conduits running vertically? The official answer is that the system shall be mounted horizontally. This is how the system is designed and tested. What can you do to minimize the risk you choose to take if not mounting the system horizontally? The key is operational temperature. If you are far from 50°C, then the risk is less. One thing you always should consider is to mount the PS+AS in the bottom of the cabinet horizontally, and then have the CIO modules vertically, connected via an S-Cable. This is even more important on AS-P. If you are close to 50°C operational temperature, you need to consider external cooling or at least ventilation in the cabinet in addition to mount the PS+AS horizontally.** To conclude - the system is designed for horizontal mounting and this is the only supported mounting. If you choose to mount it vertically it is at your own risk. Operational temperature is key - you need to make sure it is far from max to decrease risk. Always try to mount the PS+AS horizontally. Negative effect of not managing operational temperature is not visible short term, but can and will effect the life time of the product. **Ambient temperatures for operating should be taken into consideration. For vertical installations, ambient temperature should not exceed 35 C (95 F) and the load on the power supply should be reduced from 30 watts to 25 watts. Convective Air Cooling is used in the modules anticipating the currents of warm air being allowed to escape the confines of the module casing to be replaced by cooler air from the bottom. Since warm air normally rises, this method usually requires venting at the top and bottom of the casing to be effective. This is why horizontal installations are preferred. **One PS can supply one or more units connected to the backplane, consisting of several terminal bases connected together. At the moment you cannot connect more than one AS to the backplane though, because the backplane provides a path for communication between the connected units, and two AS cannot communicate on the backplane. StruxureWare Building Operation allocates 32 slots for the I/O Bus including the Power Supply and Automation Server. All devices can be installed on one linear section of DIN rail or they can be installed on multiple parallel sections of DIN rail by using connector cables*. Be reminded an empty position (back plane without module) will still keep a position (slot). As a general rule, there are 10 I/O modules followed by a Power Supply, then 10 I/O modules followed by a Power Supply and 8 remaining slots for I/O modules.Please keep in mind the I/O Bus backplane requires a particular order. Position 1 is always the Power Supply, Position 2 is always for the Automation Server, and then up to 30 remaining I/O devices interlaced with additional Power Supply modules.

Issue Where can I download the MicroNet View Monitor Tool (dongleless version) as referenced in document PA-00145 – Satchwell MicroNet Range Rationalisation? Product Line Satchwell MicroNet Environment MicroNet View Monitor Tool  Cause The MicroNet View dongleless Monitor Tool software is no longer available for purchase. However, it is now provided as a free download to support existing installations. Resolution You can download the required software directly via the links below: Available Downloads MicroNet View Monitor Tool (v3.38): Download MicroNet MNMonitor 3_38.zip SNP I/O Server (v3.14): Download MicroNet SNP IO Server 3_14.zip NCP/ARCnet I/O Server (v3.12): Download MicroNet NCP_ARCnet IO Server 3_12.zip USB Dongle Driver (for faster PCs): Download SPI 7.6.3.zip 💡 Note: The USB dongle driver may be required for compatibility with newer or faster PCs. Additional Resources 📄 PA-00145 - Satchwell MicroNet Range Rationalisation (PDF)

Issue The first time a WB-profile user connects a web browser to an I/A Series G3 station, the user is prompted to download software from Oracle. Product Line TAC IA Series Environment I/A Series G3 (AX), version 3.8.xxx Cause An earlier version of I/A Series G3 used an open-source library for 128 or 256-bit encryption.  I/A Series G3 version 3.8.xxx migrated to the Java Cryptography Extension (JCE) that requires the installation of add-on files from Oracle. Resolution Download the required files from Oracle. Depending on your version of Java, download either ... JRE8 ... http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html JRE7 ... http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html Otherwise, navigate to the Oracle download website and search for the links to "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files" for your Java version ... http://www.oracle.com/technetwork/java/javase/downloads/index.html Accept license and download. This may require registration or sign in to Oracles website. Locate the Correct Java Folder on Your PC Where the Software Must Be Installed. Launch... Windows > Control Panel > Java In the Java Control Panel, navigate to the "Java" tab, and then click "View" to see the installed Java version. The name of the folder where Java is installed precedes the "bin\javaw.exe" in the text. "JavaHome" is what this document will call that folder, no matter what the full name is. In the example below, the folder name appears as "C:\Program Files\Java\jre?" -- the obscured last character will be 7, or 8, or some other number, depending on the installed Java version. Install the Files on Your PC Use Windows (File) Explorer to navigate to the Java jre folder path as shown in the step above. From the jre folder, navigate to the lib\security\ folder. Copy the local_policy.jar and US_export_policy.jarfiles contained in the Oracle download and replace the older version files. Clear the web browser's cache Delete the contents of the C:\Users\username\niagara folder. Clear the java cache (Control Panel => Java => Temporary Internet File "Settings" => Delete Files => check installed apps and applets => OK Re-start the web browser NOTE: This procedure will need to be performed on each computer accessing the I/A Series G3 station via a web browser.

Issue XIF files for the standard MNL controllers are available on The Exchange Download Center.  Please do not use with SmartStruxure.  See XIF files for Version 1 and Version 2 of MNL controllers. Product Line TAC IA Series Environment I/A Series standard (fixed profile) controllers: MNLRF2 - Fan Coil profile MNLRH2 - Heat Pump profile MNLRR2 - Rooftop profile MNLRS1 - Satellite 1 / Rooftop profile MNLRS2 - Satellite 2 / Rooftop profile MNLRV2 - VAV profile MNLRF103 - Fan Coil profile MNLRH103 - Heat Pump profile MNLRR103 - Rooftop profile MNOTPVA3 - VAV profile MNLRF3 - Fan Coil profile MNLRH3 - Heat Pump profile MNLRR3 - Rooftop profile MNLRS3 - Satellite 3 / Rooftop profile (revised previous Satellite 1) MNLRS4 - Satellite 4 / Rooftop profile (revised previous Satellite 2) MNLRV3 - VAV profile Cause XIF files are available if needed. Resolution Download the file TAC_LLC.zip from The Exchange Download Center. Also see the accompanying Readme file.