Issue Starting in EcoStruxure Building Operation 2.0, a new licensing structure has been implemented to reflect the new scalable pricing model.  This new pricing model is different from previous versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Version 2.0 and up Cause Due to the change in our pricing model within EcoStruxure Building Operation 2.0 and later, we have new policies regarding scalable pricing which has been different in the past. Resolution In regards to questions around the new scalable pricing structure For EcoStruxure Building 2.0, please reference the sources below. EcoStruxure Building Operation Scalable Pricing Frequently Asked Questions EcoStruxure Building Operation v2.01 - Scalable Pricing Policy Scalable Pricing Overview Video - EcoStruxure Building EcoStruxure WebHelp Article about Licensing Model General Notes: An upgraded or newly purchased 2.0 license will work with sites running older versions of EcoStruxure Building Operation. Each Enterprise Central and each Enterprise Server license comes with one client license.  It will always be possible to operate the system and will always be possible to add to the system (besides attaching automation servers to the enterprise server) if you do not have enough licenses. After certain time periods, the warnings, banners, and prompts will get larger and more noticeable.  If ONLY hosting IP devices and no Automation Servers under the Enterprise Server, it is still necessary to purchase the minimum size Enterprise Server license (10 or fewer Automation Servers) as well as then the appropriate number of hosted node licenses.  The intent of this is to limit the development and support costs of having a highly resourced user interface at the Enterprise Server and to distribute this load across multiple servers.

Issue There have been questions about how the new EcoStruxure Building Operation 2.0 demo license works with the new scalable pricing structure. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 2.0 and up All previous builds of SBO 1.9 and below Cause Understanding what the EcoStruxure Building Operation evaluation license will allow to function in the newer versions of the product.  Resolution The EcoStruxure Building Operation Evaluation License is a temporary license used when a database is being brought online before the permanent license has been deployed or on engineering laptops. All authorized Schneider Electric employees and partners can download the file from the Exchange Extranet. The file is updated every quarter as each one has an expiration date. The functionality of the demo license has not changed in version 2.0 and newer. This license file will still allow functionality and engineering of a database to take place as long as the file is valid. The only difference is the new warning banner that will be present until permanent licenses are installed.  Note: With the new scalable pricing starting in version 2.0, once the evaluation license is removed from the site, a license is needed for each Automation Server attached to the Enterprise Server.  More information on the Scalable Pricing structure can be found in EcoStruxure Building Operation Licensing and Scalable Pricing Info. 

Issue EL100DatabaseSetup.exe fails to execute correctly and will not build the EasyLobby database on the SQL server   Product Line Andover Continuum Environment SQL 2005 and SQL 2008 – All versions  Cause EasyLobby database creation via the .exe will not complete successfully due to a pathing issue with database file locations. Resolution Run the SQL script that is attached to this article via SQL Management tool. Make sure to double check the two lines near the top of the SQL script that specify the exact filepath(s) where the .mdf and .ldf files are to be created, as that could be unique on any given SQL Server. dbCreateSQLServer.zip Easy Lobby is available as a downloadable .doc: EasyLobby Schneider Electric Solution Guide. For all the add on products for Continuum, please visit this Exchange Extranet. For assistance with Add-On products, email COE.Support@buildings.schneider-electric.com Other add on software is Elevator Control, Reporting Modules for Continuum, Photo Album & Badge Printing App, Automatic Extended Log Archiver, Personnel Data Importer, Area Purge, Video Monitor, and Time Tracker. These products are available for a fee. PSS does not have pricing or availability for the programs. This can be found by contacting your sales representative for your region. Pricing is per machine rather than a site. Time Tracker for example,requires a software license and utilizes a software key, which is connected to the workstation’s printer port or USB dongle. A cookie is sent directly from the factory which updates the dongle used by the computer. Emailed instructions come with the cookie explaining how to install. Again, contact your sales representative to purchase a software license, software key, and activation code. EasyLobby Support: EasyLobby directly supports their software as well as the integration to Continuum. Please forward all EasyLobby support requests directly to them. support@easylobby.com (US) 001-781-455-8558  

Issue ES connect to 3rd party BACnet devices in StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Enterprise Server. Connection to BACnet devices such as ACX. Cause Desire to use ES rather than AS Resolution As of StruxureWare Building Operation 1.1 the ACX with BACnet I/P xDriver with the ES, we can see the points, load them into the BACnet interface, and view them in tgml. The BACnet IP xDriver and User Guide is available on The Exchange Download Center. The following screen captures are from the ACX where a simple Infinity Numeric is setup called ACXdevice:   Next the xDriver for the ACX is loaded and setup as Server with the following settings: (Note the IP Address references the IP of the ACX controller)   Next a simple Numeric is setup called BacTest1 with the following settings: (Note the IP Address is left blank)   Next another Numeric is created called CocaCola1 with the following settings:   Next from the Enterprise Server, a 'Find New BACnet devices' is done to find the ACX and the two Numerics created:  

Issue I/A Series G3 Modbus TCP communications to random Modbus devices randomly drop offline and stop communicating with the ENC or Enterprise Network Server.  Both the modbusCore and modbusTcp modules are at version 3.6.31. Product Line TAC IA Series Environment I/A Series G3, Modbus TCP 3.6.47 and lower Cause There were a few updates to the Modbus core and TCP modules between 3.6.31 and 3.6.47. Issue 18656 corrected communication reliability when there are a large number of Modbus TCP devices under a single ModbusTcpNetwork. Issue 19897 corrected transaction ID synchronization when a retry occurred. Issue 23578 added the ability to control the maximum transactionID used for ModbusTcp (I/A Series G3 Modbus TCP communications to Siemens Moore 353 controller stops updating after a period of time after ENC/JACE reboot or station start). Resolution Download the following modules from The Exchange Download Center: modbusCore-3.6.47.1.zip modbusTcp-3.6.47.1.zip Install to the appropriate I/A Series G3 Workbench modules folder Upgrade the modules in the ENC/JACE.

Issue ENC is licensed for Microsmart but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacms" when attempting to access the Microsmart Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses   Tridium.license (Tridium 3.5 - never expires)   TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates   Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)  TAC.license (Tridium 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.  If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center.  Use Workbench to import the downloaded file.

Issue ENC is licensed for ASD but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacasd" when attempting to access the ASD Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses Tridium.license (Tridium 3.6 - never expires) TAC_LLC.license (TAC_LLC 3.6 - never expires) Certificates Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   Tridium.license (Tridium 3.6 - never expires)   TAC_LLC.license (TAC_LLC 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue. If you have previously installed the TAC_LLC.certificate in any other version of the G3 software, you can import that certificate into the version you are currently running. Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] under the certificate section of the window. Browse to the "certificates" folder under any other G3 installation folder and locate the TAC_LLC.certificate file.  If the file is not found, check the "certificates" folder of another G3 folder.  Click on the TAC_LLC.certificate file name then click [OK]. The certificate will automatically be copied and installed.   If public ethernet connectivity is available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center. Use Workbench to import the downloaded file.

Issue ENC / JACE is licensed for MS but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException:" when attempting to access the MS Network property sheet. Environment I/A Series G3, ENC-520 or JACE-645 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses Tridium.license (Tridium 3.5 - never expires) TAC_LLC.license (TAC_LLC 3.5 - never expires) Certificates Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   TAC_LLC.license (TAC_LLC 3.6 - never expires)   TAC.license (Tridium 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)   TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue depending on network connectivity of the G3 Workbench computer. If public ethernet connectivity is available, the licenses and certificates can be downloaded from the I/A Series G3 (Tridium) license server, using the Workbench "License Manager". Open Workbench and connect to the subject ENC / JACE. Open the Platform then select License Manager. In the License Manager, select [Import] then check "Import licenses from license server".  This process will download any available licenses for the selected device, along with any available certificates.  After the download is complete, the licenses and certificates downloaded will automatically be installed.   If public ethernet connectivity is not available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center.  Use Workbench to import the downloaded file.  A reboot of the ENC / JACE may necessary.

Issue Using the EGL, EGRL, EGLL5 which are obsolete Environment Vista Cause temperature/resistance data of EGRL, EGRLL, EGRL5 temperature sensors, or customer needs data to calibrate the sensors. Resolution EGL is replaced by the STD100-250 EGRL - STR100 EGLL  (2 thermistors) was not really replaced, as the average temp calc nowadays is done in the controller. The room version was named EGRLL. All these are for the Vista series. For more information regarding sensors, please visit Exchange Extranet.    Click here for the temperature/resistance chart for the old EGL, EGRL, EGLL5 Click here for the original Product and Installation pdf.

Issue Downloading new NXE or APB files using Lonmaker for controller updates Product Line Other, TAC Vista Environment Lonmaker 3.2 Cause Updating of software in a controller for more features or fixes. Resolution To update a new NXE or APB in a Lonworks controller using lonmaker follow these steps. 1. Download the NXE or APB file you intend to use. If it is a 100 series controller the files are available on extranet. Here is the link to the Xenta 100 series NXE files.   2. Locate the device you wish to upgrade in you Lonmaker drawing and select the load option 3. The next option screen will indicate the existing template name. Retain this name if the SNVTs are not changing. You may want to create a new template name if the SNVTs are being amended. 4. Select the Next option and then in the image name area browse to the NXE or APB file you want to download to the controller. 5. Select the next option then select the state you would like the device to be in after the new NXE has been downloaded. Then select the finish button. The application will then be downloaded to the selected controller.

Issue Download a Menta application file to a Xenta controller using the Menta software tool and a directly connected serial RS-232 cable. Product Line TAC Vista Environment Menta Programming Tool Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cableguide Kableguide Programming Serial Kit 0-073-0920-0 Note: The Online command is not available for the Xenta Server 700 devices so the following procedures do not apply to these devices. Cause Throughout the engineering, installation and commissioning phases of a project it may be necessary to download directly to a Xenta programmable controller. Also, performing a directly connected Menta download may be necessary in order to fix certain issues. See the following: The device is applicationless, or is not associated with a program record. (Subsystem: NS, #5) Resolution Use Menta Setup program (this is found in the TAC Tools menu) to select the Com port that is being used. Do not change any other setting before clicking Close. Connect the RS-232 cable and Programming Adapter between the PC and the RS232 port on the TAC Xenta. (these are part of the TAC Xenta: Programming Serial Kit, part no. 0-073-0920-0 For more information about the cable and adaptor see Xenta Cable Guide , Adaptor A1 and Cable L1 or Schematic for the RS-232 cable used to direct download Menta applications and system files.)  Open the Menta file to be downloaded. Change to simulation mode in Menta by clicking Options menu and selecting Simulate. In the simulation mode click Online. In the Connecting to Device dialog click Download. In the Tam32 dialog choose whether or not to generate files for an OP menu. For more information regarding Menta direct downloads see the TAC Menta Technical Manual  Section 16.4.1. Notes: Network information containing network addresses and other properties for the Xenta device and it's I/O modules is included in the download. For more info about this network info see the TAC Menta Technical Manual listed above or for problems with downloading the network information see No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network!. If Menta returns Parser Errors during download see Menta Parser Errors. If Menta returns Unsupported I/O Warning during download see Reference to unsupported I/O Error in COD file - Error:13. If a serial connection is not available on the PC a USB adapter can be used. The appropriate version of the TAC Menta Engineering Tool can be downloaded from the Exchange

Issue When downloading a controller in the Vista System Plug-in, messages are received saying the System Plug-in is waiting for the controller to restart, but this never completes successfully. This message may be shown many times. Environment Vista System Plug-in LonMaker Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause There may be several different causes including communications errors or a corrupted application. However, by taking the controller offline in LonMaker, any extraneous interaction with the controller is temporarily ignored during the download. Resolution First, please double check the Vista ToolPack version that is installed, and make sure the version matches TAC Vista Server version. If not, please uninstall the Vista ToolPack and install the correct version of ToolPack. TAC Vista ToolPack can be download from Extranet (Software and Firmware > Engineering Tools). In LonMaker force the controller's neuron chip into a configured, bypass mode: Right-click the controller and select "Manage" In the LonMaker Device Manager window click "Offline" Download the controller in the Vista System Plug-in. In LonMaker set the controller's neuron chip back to configured, online mode: Click "Online" in the LonMaker Device Manager window then close window

Issue The SP-C Controller was deleted and recreated with the Controller wizard to create default objects. The Controller had previously been online and downloads were successful. After being recreated with the wizard, downloads are failing with a failed loading dat file error message seen in the Controllers Download Diagnostics Window. Failed to load DAT file. Path = 'C:\ProgramData\Schneider Electric\SecurityExpert\Download\13.dat' , Error code = 80070002 Product Line EcoStruxure Security Expert Environment Security Expert Client SP-C Cause The Controller still had configuration settings from the previous setup that were causing a conflict. Resolution Clear the Controller by factory defaulting it, then reconfigure. For instructions on how to default a controller, refer to the Hardware Configuration section Defaulting a Controller in the SP-C Installation Manual - System Controller.

Issue Instructions on how to download an .MOT file into a Xenta Programmable controller Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Download Wizard Cause To reinstall or upgrade the firmware of a Xenta programmable controller, a .MOT file must be loaded using the Download Wizard. Resolution Get the latest (or desired) .MOT version onto the PC's hard drive. Download the appropriate .MOT for the controller requiring new firmware. To find the version of firmware in a controller, see How to view the current firmware version on a Xenta controller using the RS-232 cable. Go to the The Exchange Download Center and view the MOT files Locate the proper version and controller combination in the asset title. Download the desired .MOT version   Download the .MOT file into the controller Start the Download Wizard. Note: The download wizard is installed when Menta or EcoStruxure Building Operation Workstation is installed on the machine. Start > Programs > Schneider Electric > TAC Tools X.X.X > Download Wizard (For versions prior to 5.1.4, the path will be "TAC" instead of "Schneider Electric.") Follow instructions on the Download Wizard. System Choose to Retain Current .MOT or Download new.  Typically the choice will be to download a new .MOT. Ensure the device type is correct and matches the controller and .MOT file. Browse to the .MOT file downloaded from the Buildings Business Extranet. Application Choose to Retain Current, Clear memory, or Download New.  Typically the choice will be to clear memory. This is referring to the Menta application inside the controller.  If the application is cleared, the controller will be "applicationless" and cannot be downloaded through the Vista System Plug-in.  Some Menta application will need to be loaded through a Menta direct download before the controller can function again in a network. If you choose to load a Menta application through the Download Wizard, browse to the desired .MTA file.  Configuration If the application is set to clear memory, the configuration section will be grayed out.  No selections are necessary. This refers to the network description files.  The typical selection if the option is available is to retain current. Press Apply Download status is shown in % finished.  Do not interrupt this process! When the dialog states that the download has completed, close Download Wizard.  Load a Menta application if necessary through Menta direct download. For more information on Menta Cable needed to download, see Schematic for the RS-232 cable used to direct download Menta applications and system files.

Issue Download Service fails to start after an upgrade to v.4.2.251 Product Line EcoStruxure Security Expert Environment Security Expert Server v4.2.251 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 for assistance. Cause Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501; (VC++ 2013 Redist v12.0.0.30501.0) is not installed. This package is a pre-requisite to installing Security Expert v4.2.251. It was needed for extending the Suprema integration but did not get added to the installer for that version. This is now packed with the Security Expert installer. Resolution There are two options to resolve this; 1. [Preferred Option] Install the current release of Security Expert. This required package is now included in all new versions of the Security Expert installation file. 2. Install the package from Microsoft before installing Security Expert 4.2.251. Locate the file on the Microsoft site https://www.microsoft.com/en-nz/download/details.aspx?id=40784. Download and install vcredist_x86.exe, the 32 bit version (because Security Expert is a 32 bit application), before performing the upgrade.

Issue DoorAjar alarms not showing up in an Access EventView even after hardware has been checked out and configuration is verified. Environment 1) Cyberstation Version: 1.90.0.20081030 2) Controller Type: ACX 5720 3) Controller Version: 1.000005 Event View Cause DoorAjar alarms not showing up in an Access EventView even after hardware has been checked out and configuration is verified. Resolution In this case the solution was to uprev the ACX to the latest version (ACX57xx v1.1000xx). The v1.0xxxxx firmware is used in CyberStation versions 1.81 and below and the v1.1xxxxx is used in v1.82 and above. Download ACX-57xx Series_v1.100013

Issue Error: "Tenant X individuals for door LLSSPPBB DO exceeds 24,000" when attempting to select additional doors within Tenant Editor Product Line TAC INET Environment I/NET Seven 2.15 and above DPU / SCU Firmware 3.23 and below Cause SCU / DPU firmware revision 3.3 and lower only supports 24,000 individuals per door, even though the I/NET Software (I/NET Seven 2.15 and above) allows you to allocate 32,000 per tenant.  This is why it is important to maintain consistency between I/NET Software Revisions and Hardware firmware. The I/NET Seven 2.xx Compatibility Matrix lists this information. Resolution To allow the controllers to support more than 24,000 individuals per door the firmware in the DPU / SCU must be at revision 3.24 or above. This firmware is included with I/NET Seven Revision 2.15 or above. Although TAC I/NET supports up to 32,000 individuals per tenant, the model type and revision date of a tenant's door controllers will ultimately determine how many individuals will be supported. The following table shows the capacity of various door controllers. For any door controller with revision 2.2x or later firmware, you would have to define multiple tenants in order to reach the door controller’s maximum storage capacity. Firmware Revision Door Controller Maximum Number of Individuals 2.1x and earlier  DPU7910, DPU7920 Up to 24,000 per door 2.2x to 3.23 DPU7910, DPU7920 without DPU48K Up to 48,000 per controller   DPU7910, DPU7920 with DPU48K Up to 48,000 per door 1 3.24 and later DPU7920 with DPU48K, SCU 1284 Up to 64,000 per door 1   1 Typically, the total number of individuals for a selected door cannot exceed 32,000. However, if one of the two doors controlled by a DPU is not being used (that is, no individuals are assigned to the door), you can assign up to 64,000 individuals to the door that is being used. This also requires the use of more than one tenant since no single tenant can have more than 32,000 individuals.  Refer to TCON300-06/11 Chapter 9-62 for further information.

Issue Does the NPR have a Diagnostic Utility? Environment I/NET site Cause Does the NPR have a Diagnostic Utility? Resolution Yes. The NPR is equipped with a self-diagnostic function that runs every time the unit is powered up. Four LEDs on the upper right side of the unit provide feedback of the progress of this test, and indicate any error conditions. See TCON209, 2-31 and TCON184 NPR Installation Guide.

Issue Has the AC256 Xdriver been qualified or modified to work on any second generation controllers (NC2, bCX)? Product Line Andover Continuum Environment bCx9640 CX9680 Xdriver AC256 LA-1 Cause With the obsolescence of the NetC (CX99xx), will the AC256 Xdriver be updated to work with NC2 and/or bCX controllers? Resolution There are no plans to upgrade the AC256 Xdriver for the NC2 and/or bCX. One option, if a site only has AC256 IOU boards, is to use the NC2 and the LA-1 LBus Adapter module or the NC2 with built in LBus support (on comm4 or comm1 with an RS232-to-RS422 converter) to communicate over the LBus with Plain English programming in the NC2. Note: If you configure the controller for Lbus (using the LA-1 or directly to comm1 or comm4) you cannot use Continuum IO modules on that controller. For further information on X Driver compatibility and how to request new drivers/ upgrades, please see Will Continuum communicate with a third party system?

Issue Does installing WorkPlace Tech version 5.6 load all of the Bin files required to upgrade the firmware of MNB controllers to rev 1.4x? Environment WorkPlace Tech version 5.6 MNB Controllers Cause The WorkPlace Tech version 5.6 doesn't contain all the require Bin files to upgrade the firmware of MNB controllers to rev 1.4x. Resolution No, installing only WorkPlace Tech version 5.6 will include only the bin files current at the time of its release. Additional Bin files are needed to upgrade firmware to the latest revisions. To load all necessary Bin files, load WPTech 5.6, then download the following two self-extracting Bin files: MNB Series v1.423 Firmware Pack.exe MNB v1.41 Firmware Pack – BTL Compliant To verify the minimum necessary Bin files have been loaded, compare the following list of Bin files to your C:\Program Files\Workplace Tech\Firmware folder. The list of Bin files on the computer may be longer, depending on how Bin files have been installed since originally installing WPT 5.0. MNBP01-011F -0120.bin MNBP01-0120 -0121.bin MNBP01-0120 -0130.bin MNBP01-0130 -0131.bin MNBP01-0131 -0132.bin MNBP01-0132 -013F.bin MNBP01-013F –0140.bin MNBP01-0140 –0141.bin MNBP01-0141 –01411.bin MNBP01-01411 –0142.bin MNBP01-0142 –01421.bin MNBP01-01421 –01422.bin MNBP01-01422 –01423.bin MNBU01 –0141.bin MNBU70 –0141.bin MNBV01 –0141.bin MNBV02 –0141.bin