Issue What does DLCU stand for? Environment I/NET site Cause What does DLCU stand for? Resolution Distributed Lighting Control Unit. This is a specialized type of controller or DCU. The 7780 is a DLCU. The DLCU is specifically designed for lighting.

Issue Replacement Satchwell pneumatic parts not available or obsolete and other pneumatic control brands e.g. Barber Colman used in the UK marketplace. Product Line Field Devices, Other Environment Pneumatics Part Number examples: 541, T100, 2212 Cause Replacement parts required. Resolution Contact OEM Comfort Telephone: +44 (0) 208-344 8777 Website: http://www.secureseal.com/ Email: lewin@secureseal.com

Issue How do you determine how large a database will grow when using Continuum? How do you know if a Stand Alone or LAN install should be used? Which version of Microsoft SQL Server is needed? Product Line Andover Continuum Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 MSDE SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of controllers, points and logging should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called MSDE and SQL Server Express. The size limitations are 2 and 4 gigabytes respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Continuum database, to determine if a Stand Alone or LAN is needed and which version of SQL should be used. The Continuum database estimating spreadsheet takes into consideration 6 main areas: Extended Logs- total amount of logs, intervals and the number of days to retain  Access Events- total amount of access events and the number of days to retain Alarm Events- total number of alarms and the number of days to retain Error Events- total number of Cyberstation errors and the number of days to retain Activity Events- total number of Activity events of all Continuum users and the number of days to retain Continuum Database objects- Total number of Netcontrollers, Infinet, BCXs , mstp controllers, total number of inputs, outputs and numerics. Any of the objects not mentioned above. Consider all objects not mentioned above The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate if a Stand Alone or LAN system is needed Indicate which version of SQL Server is needed Download the Continuum Database Size Estimation Tool.

Issue When upgrading a BCX Inf to BCX BACnet or vice versa , the BCX could lose any node count or X Drivers added using a post shipment factory *.upd cookies. The settings return if the controller is flashed back to the original model type. Product Line Andover Continuum Environment Continuum 1.xx 2.xx Windows Infinet  BACnet Node Count, X Driver, X-Driver Cause This is because the cookie upgrade to add the node count (or other features) will be sent out for the format it is intended for, i.e. if the controller was BACnet then the file will be sent as BACnet, and if the controller was Infinet then the cookie will be Infinet Resolution New controllers shipped from the factory can be flashed either way between a 4040 and 9640 and it will not affect the settings for Node count, X Drivers or other options. If a controller was to lose additional setting when it is convert from BACNet to Infinet or vice versa, there is a need to re-apply for the cookie upgrade file for the new model type. (it would of originally been ordered as additional options for the controller) To re-apply for the cookie, contact your local repairs department with the controller details i.e serial number, controller type, etc, this will enable them to find your order and reissue the upgrade in the version it has been changed to.

Issue The word TEST is displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation preventing it from being commissioned. Environment Satchwell Climatronic CSC5252 CSC5352 CXR5805 CXT5605 CZT5305  Controller Display TEST LCD Screen Cause The cause of the word TEST being displayed on the Liquid Crystal Display screen of a Satchwell Climatronic Controller when first powered up during initial installation and preventing it from being commissioned is normally due to a micro processor programming error occurring during the course of production. Resolution There is no field remedy that can be applied to a Climatronic Controller displaying the word TEST on the Liquid Crystal Display screen that will enable it to be commissioned successfully. The Controller should therefore be returned to the vendor for replacement under the terms and conditions of the warranty applicable at the time of purchase.

Issue Replacement an AF24-S Actuator? Environment AF24-S Damper Cause Customer requires a replacement actuator for a AF24-S. Resolution The AF24-S is a 24v power open, spring return damper actuator, it has a torque of 15 Newtons. To view the data sheet, please click HERE. The replacement actuator range is the MD10SR/MD20SR ranges. The MD10SR damper actuators have a torque of 10 Newtons (dampers up to 2m2) and are available in the models shown below. To view the full data sheet, please click HERE.   The MD20SR damper actuators have a torque of 20 Newtons (dampers up to 4m2) and are available in the models shown below. To view the full data sheet, please click HERE. In the specific case of the AF24-S the replacement would be the MD20SR-T or -TS if auxiliary switches are required.

Issue Writing directly to a SR (set-reset) simple block in a Xenta 700 Menta application where that SR output is sent to a Delay block, the Delay block may not delay. The output on the Delay block will be set immediately, without any delays. Environment Xenta Servers version 5.1.1 and lower Xenta 701, 711, 721, 731 Menta Cause This was a bug in version 5.1.1 and lower. Resolution Upgrading the Xenta Server to version 5.1.2 or later will resolve the issue. If upgrading is not an option, this can be worked around by not writing to the SR block itself, but to a block in the logic before the SR block.

Issue Can't see the Xenta Server Menta  program online in the browser Menta program is working but it is not possible to view it online All other viewers work correctly Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause One reason could be that there are texts (comments) in the Menta application that does not have any font specified. Resolution Edit the Menta file form Xbuilder Find any comment/texts Double click to edit Click on font Select a font and save Download the Xbuilder project again

Issue Weather information provided through the weather module in I/A Series G3 is no longer updating. Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server ENC-410 ENC-520 Cause The National Weather Service hosts the data service used by the Niagara weather module's default provider, the "NWS Weather Provider". At some point during the week of September 26th, the National Weather Service moved the location of their forecasted weather conditions service.  No advanced warning of the change was provided. The error message encountered may include: WARNING [10:04:20 30-Sep-11 EDT][weather] Updating forecast failed for WeatherReport javax.baja.sys.BajaException: 404 Not Found at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getForecast(NwsForecastReader.java) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java) at javax.baja.sys.BComponent.doInvoke(BComponent.java) at javax.baja.util.Invocation.run(Invocation.java) at javax.baja.util.Worker.process(Worker.java) at javax.baja.util.Worker$Processor.run(Worker.java) at java.lang.Thread.run(Thread.java:823) Resolution The weather service has been updated in patched weather modules to use the new data service location.  A number of other enhancements have also been made to better detect this situation and attempt to automatically resolve the issue by better following the 'HTTP Moved Permanently' error response messages. This may help reduce the impact of future unannounced National Weather Service data service changes. Although some users may wish to work around this problem by making changes to hidden fields on the weather provider, this is not recommended because it leaves stations exposed problems resulting from future data feed changes. forecast server: graphical.weather.gov forecast path: /xml/sample_products/browser_interface/ndfdBrowserClientByDay.php The NWS has also deprecated the current condition feeds previous retrieved from the www.nws.noaa.gov servers. These are now being replaced by feeds made available at www.weather.gov.  The new patched weather module will automatically use the feeds at the new location. As a temporary workaround, the Nws Weather Provider's hidden slot "conditions server" can be modified with the new value "www.weather.gov". It is recommended that weather service users upgrade to the most recent weather module for their release.  The modules can be downloaded from The Exchange Download Center. weather-3.4.67.3 or higher weather-3.5.39.5 or higher weather-3.6.37.4 or higher

Issue Valve Flange Tables Product Line Field Devices Environment Valves Flanged Gaskets Bolt holes PN rating PCD Cause What flanged tables are used with what valves? Resolution The PN of the valve and the valve size will indicate the diameter, PCD (Pitch Circle Diameter), number of bolt hole/size and bolt size and therefore size of flange and gasket. Download the flange tables for BS EN 1092 (metric), ANSI  (ASA) and BS10 or here for an alternative flange table document.

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 Where is graphic information stored in Continuum? Is any graphic information stored in the controller. Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Cause Need to know where Continuum Graphic information is stored. Resolution While during the Continuum installation process, pin files, image library files and background images are placed in the NewGraphicFiles folder on the workstation on which Cyberstation is installed, these files can alternately be stored on any network share.  Each workstation must have the location of these files defined in Pinpoint under View>Options.   The graphic information is stored in the dbo.Panel table in ContinuumDB.    The Graphics folder paths that are set from 'View\Options' are unique to each Cyberstation and are stored in the device table of the ContinuunmDB on the corresponding row of the appropriate Cyberstation in columns PPBackgroundsFolder, PPGraphicsFolder and  PPGraphicsLibraryFolder  No graphic information is stored in the controller

Issue A Security Expert reader that supports Wiegand and RS-485 is wired for Wiegand. It is not working. It only works on RS-485. Product Line Security Expert Environment Security Expert Smart Card Readers which support both 125Khz and 13.56Mhz (SX-DRD-xx, SX-DRK-xx, SX-RK-xx) Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Tried to use a Smart Card Reader wired for Wiegand after it had been connected by RS-485 to the controller. Resolution Once a Security Expert Smart Card Reader is used in an RS-485 configuration it will not work in Wiegand configuration until it has been re-programmed with a configuration card designed for that purpose. The configuration card  (SX-ISO-CONFIG) must be purchased through Schneider Electric. See the Security Expert Credentials Order Form for details.   This is because RS-485 is a two-way communication, intelligent wiring protocol. Once the reader is set in this two-way communication mode there is currently no way, without the configuration card, to go back to a less intelligent one-way mode like Wiegand.   Note: Readers manufactured in 2017 or before may have a firmware version that uses a configuration mode that will not respond to a configuration card. If you contact Schneider Electric for a configuration card, supply the serial number (SN) from the back of the reader on your request.

Issue Information on the features that Video Monitor supports and details on how to configure it on a Continuum Workstation. Product Line Andover Continuum Environment Continuum v1.90 and above. Cause There does not seem to be a specific manual for Video Monitor. Resolution What Is Video Monitor? Video Monitor is CyberStation's powerful video-surveillance tool. Video Monitor, available in CyberStation Version 1.9 and higher, allows you to view live and recorded video images from cameras assigned to doors or points that trigger alarm events. It allows you to monitor doors, immediately capture video images from doors, unlock a door, monitor door status, monitor a person's access to doors, and get alarm information as soon as it happens. You customize the way Video Monitor operates using its powerful configuration tool, Video Administrator. Using Video Administrator, you can attach up to 16 cameras to a door or point. Video Monitor is launched when an event associated with the door or point triggers an alarm. Another video surveillance monitoring tool, VideoLayout, is also available for video matrix-frame viewing. The system may be configured to use either Video Monitor or Video Layouts as your primary video interface to alarms. Also see reference to supported features in the Feature Blast for v1.90 when Video Monitor was first added to Continuum. Configuration There is a large amount of information in the Continuum on-line help files that discuss how to configure Video Monitor in detail. See the Continuum online help contents and search for "Video Monitor."   Note: The Video Monitor option must be enabled on the Continuum Security Key to able to set this up and use it. This comes standard in v1.90 and above and can be enabled on your Key if it is not already.

Issue Where are the DUI expander objects for the MNB-300 and MNB-1000 controllers in Workplace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech version 5.1 through 5.9.4 I/A Series WorkPlace Tech version 5.10.0 till current Cause The standard stencils do not include an object for Momentary SS or a DUI multiplexer.  Resolution The I/A Series BACnet controllers do not currently support the DUI object directly within the MNB-300 or MNB-1000. An application performing the same basic function was created and factory tested. This application was created as a custom object named "DUI_App". For support of these objects in Workplace Tech 5.1 until 5.9.4, log into The Exchange Download Center and download the file Application Objects_rev1.zip. There is also a detailed DUI_Application_Documentation_rev1.pdf that describes the operation of the "DUI_App". For support of these objects in Workplace Tech 5.10.0 until further notice, log into The Exchange Download Center and download the file Application Objects_rev2.zip. There is also a detailed DUI_Application_Documentation_rev2.pdf that describes the operation of the "DUI_App". Note: VAV box controllers do not have DUI expander objects available. See TB06-02 for additional details.

Issue When adding Shadow Schedule in AS, it isn't synchronized with the Lead Schedule in ES. This issue only happens when  there is an Exception schedule assigned with another Calendar added to the Lead Schedule in ES. Error: "cannot verify lead object status" Product Line EcoStruxure Building Operation Environment SmartStruxure Lead and Shadow Cause If a Lead Schedule contains an Exception with another Calendar assigned in ES, and a Shadow Schedule needs to be pointed to this Lead Schedule in AS, both the Shadow Calendar and Shadow Schedule need to be created and pointed to corresponding Lead Calendar and Lead Schedule. If only Shadow Schedule is created, it will fail to update to Lead Schedule, or even wipe the original setting with a blank schedule. When involving Calendars the following should be considered: The only way that the lead and shadow relationship can be maintained where calendars are concerned is where the calendar has the same name and is at THE SAME RELATIVE PATH as it does with respect to the lead schedule. Consider the following examples: Example 1 - Lead Schedule is at Root and Shadow Schedule is at root and Referenced Calendar is at root. - under these conditions there is only a need for one Calendar object. The Lead Schedule has an exception that references the calendar at the root and everything works great. Example 2 - Lead Schedule and Referenced Calendar are in Folder 1 and Shadow Schedule is in Folder 2. This will not work because the Shadow Schedule is trying to reference a calendar at the same relative path, i.e., in Folder 2, and there is none there. Example 3 - Lead Schedule and LEAD Referenced Calendar are in Folder 1 and Shadow Schedule AND SHADOW CALENDAR are in Folder 2. This will work fine. In simple terms keep the names and paths within the ES and AS consistent (the same) to avoid issues. Resolution Before the steps below, ensure the communication between AS and ES is OK. Refer to Binding between ES and AS or two AS shows Unresolved and Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server. If the communication is fine, continue to the following steps: Create Lead Calendar and Lead Schedule in ES, and assign the Lead Calendar to the Exception of Lead Schedule (Should already done before). Create Shadow Calendar and Shadow Schedule in AS, and point them to corresponding Lead Calendar and Lead Schedule in ES. Now the Shadow Calendar should be able to synchronized with the Lead Calendar after changes have been made to the Lead Schedule.

Issue Difficulty getting b3 controller online in order to replace a failed one Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Continuum b3 Controller Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause A b3 controller has failed and needs to replace with the same model. Resolution Remove the failed b3 controller. In EcoStruxure Building Operation Workstation change the serial number of the failed b3 to that of the replacement b3. Install the replacement b3 and ensure the MSTP bus is connected so it autobauds to the correct rate. Then power it up. Remove the battery tab from the replacement b3 (if applicable). In Workstation right-click on the replacement b3 and select Device -> Commission. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Download all objects. A green progress bar should appear with a success status message. In Workstation right-click on the replacement b3 and select Device -> Backup to flash.

Issue No events are transferred to the Report Server SQL database. Trend logs are transferred just fine. In the report agent log you can see this message "Sequence contains no elements" Product Line EcoStruxure Building Operation Environment Report Server 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. Cause The Enterprise Server has been renamed before the Report Server has been installed or before the Report Server Agent has started collecting data. Resolution This issue will be fixed in a future version, but until that, do the following to correct the issue: The fix is split into two sections. First, a section working with the "event.db" file from the SBO database, and second a section working with the "StruxureWareReportsDB" from SQL Management Studio. "event.db" from the SBO database Download http://www.sqliteexpert.com/download.html (Just take the personal one) Stop the Enterprise Server Copy the "event.db" file to a safe location Attach the "event.db" file to "SQLite Expert Studio" Get the first event from the event.db using the following query in the "SQL" tab: SELECT SEQNO,TimeStamp,EventGUID,SourceServer FROM t_7E_2FSystem_2FEvents_2FEventLog_2FEventRecords ORDER BY SeqNo LIMIT 1; Convert the TimeStamp with this "SBO TimeStamp Converter" tool "StruxureWareReportsDB" using SQL Management Studio Write the following SQL query in SQL Management Studio, using the converted time stamp, and the Guid you found previously. INSERT INTO StruxureWareReportsDB.dbo.tbEvents (DateTimeStamp,SeqNo,OriginalSeqNo,Guid) VALUES ('2014-04-17 08:35:23.857','1','1', '380d1c4c-c60b-11e3-8ecb-b8ac6f81243c') Start the Enterprise Server again Restart the Report Agent and let it run for a while.

Issue SoapEwsRestProvider serves data sourced from any EWS Server using the standard EWS SOAP protocol. The architecture for the SmartConnector REST Extensions integrates Swagger to provide a rich self-documenting API. Below errors indicate configuration issues. The User Name or Password were incorrect.The User Name or Password were incorrect. "Message": "Authorization has been denied for this request. ""Message": "Authorization has been denied for this request. " "Message": "The HTTP request was forbidden with client authentication scheme 'Digest' ""Message": "The HTTP request was forbidden with client authentication scheme 'Digest' " Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Building Operation Enterprise Central Cause Smart Connecter or EBO Incorrect configuration. Resolution Make sure that SboEwsRestProvider is started and has a correct port that is not used by any other Smart Connector data provider or other application.   Make sure that EWS server address has the following format: HTTP: http://ipAddress:port/EcoStruxure/DataExchange HTTPS: https://ipAddress:port/EcoStruxure/DataExchange For ES/EC, check software administrator to make sure there is no port conflict: Software Administrator shows red outline (box) on the Communication Ports (HTTP / HTTPS) - Communities (se.com) In EBO, make sure EWS server is enabled: Enabling the EcoStruxure Web Service Server Check if username and password used for the SOAP provide has correct permissions and can be used to login to EBO server. If the user is not located in the default domain, make sure to add the domain name in the Username string, ex. "Domain/User". If HTTP protocol is used (not recommended), check the following: In EWS server configuration, make sure that "Enforce Secure Communication" to Disabled. In Security Manager, make sure that "Enable Incoming http communication" is enabled.

Issue In TAC Vista 5.1.9 when trying to lock a license file to an end user dongle, the taclic vendor daemon starts briefly, but then stops again and you see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. Usually you only see that message if the license file has been tampered with. 8:48:28 (taclic) Invalid license key (inconsistent authentication code) 8:48:28 (taclic) ==>INCREMENT Menta.View taclic 5.1 permanent 1 ISSUER=TAC \ ISSUED=30-may-2014 BORROW NOTICE=3424672 \ SN=FID__47eba299_146164ca427__7ec5 SIGN="13DC 795D AF25 E8ED \ D6EG 7BAA 8495 2ED7 B4B0 F6E4 EDD8 C3C1 6EAE 2BF0 598D 0759 \ AE4A 3C9E 391C A6ED B313 9971 369A 349C 8671 E194 2E42 E2DC \ 8A9A 7905" Product Line TAC Vista Environment TAC Vista 5.1.9 License Server Cause An issue has been detected in TAC Vista 5.1.9 when locking a license file to an end user dongle. You see the error "Invalid license key (inconsistent authentication code)" in the taclic.log file. The error is located in the taclic.exe file. Resolution Contact PSS for a permanent hotfix for this issue, or download it from Exchange Download Center.  Work around 1: Lock the license to the MAC address of the PC Follow Rehosting a Vista 5 License on the FlexNet License Server to rehost a license file to a MAC address.  Work around 2: Use a previous version of the taclic.exe file Access a PC having a previous version of the license server installed Locate the file "taclic.exe" and copy it - it's normally located in the TAC Vista installation folder under "License Server" Stop the license server on the PC having TAC Vista 5.1.9 installed Rename the original taclic.exe file to taclic_11.12.exe Paste the "taclic.exe" file you copied into the folder Start the license again  In general when working with the license system on TAC Vista versions from 5.1.8 and above, this utility can come in handy: TACLicenseServer Settings.