Issue Knowing just the serial number of a controller, how to determine the options configured. Environment CX, bcx Cause How to determine a controller's configured options when only knowing the serial number. Resolution When a controller is online with CyberStation simply run ContinuumExplorer, navigate to the controller, select and right-click on the controller and select Edit. Look at the Options tab. However, if the controller is non-functioning then contact the US Repair Dept at (978) 475-9600 Press 2 then 3 or via email at tacus.WLCrepair@schneider-electric and provide them with the serial number and controller type. They can look up the options that have been configured.

Issue After installing Continuum, on launching Cyberstation Continuum does not display the logon dialogue box.  Cannot launch the logon dialogue manually because no Continuum icon appears in the notification area of Windows task bar. Environment Cyberstation Continuum Logon Cause Problem with the OS installation or the corporate image that was used to install the operating system. Resolution Following a reformat of the workstations hard drive and reinstallation of the operating system, Cyberstation installed properly. 

Issue Does Schneider Electric offer replacement labels to convert the Smart Thermostats to other languages? Environment Viconics T-Stats French, German, Italian, etc. Cause It is desired to have labels on the wall mounted thermostats that are in the native language of the installation site. Resolution Unfortunately, there is not an offering for labels for the sensors for any other languages.

Issue How much future schedule data can be put into a BACnet Schedule and stored in the controller. Environment Continuum BACnet Cause Need to store a years worth of Exception events in a BACnet controller and unsure if the BACnet Schedule performs the same as the Infinet where it only stores 7 days of events going forward. Resolution Unlike Infinet controllers, BACnet controllers will store all the Exception events in there schedules. This includes past as well as future exception events. (It's important to clear out the past events to free up space on the controller.) The total number of exception events depends on the amount of memory available in the controller being used. In Continuum v1.94 with the latest build of v4.5 firmware, we find that a Schedule in a b3 controller has the following memory requirements. 1. Blank b3 had 46624 bytes available. 2. Each BACnet Schedule object will consume 416 bytes. 3. Each Exception Event will consume 60 bytes. 4. Each Time Value in the Exception Event will consume 12 bytes. 5. Exception Events can be created (and saved to the controller) up until 1-Jan-2105. These events, all the way up to 2105, were stored in the controller. In this example, and only using an ON/OFF time value pair for each Exception Event, you will (theoretically) be able to store a bit more than 535 Events in a single Schedule (If this was the only created object in the controller.)

Issue Since the TA224 controllers are obsolete, a replacement is requested Environment TA224V 2241030000 TA224VL 2241040000 Cause No current products are listed as replacements for the obsolete TA224 controllers. Resolution No direct replacements are available- Free programmable Xenta controllers would probably be the only way to replace these old style controllers

Issue Continuum logs clear logged data when size or interval is changed. Environment All Continuum CXs i2 devices Cause Function as designed. Resolution Continuum logs automatically clear any existing logged data if the size of interval are changed.

Issue Modbus RTU enabled on controllers comm port, loaded with correct XDriver, and configured correctly but does not communicate. Environment bCX1 Netcontroller II Cause There is a rare occurrence where older implementations of Modbus RTU upgrade cookies may not be properly installed even after seeming to uprev properly. Enabling both the Modbus RTU and Modbus IP bits in the upgrade file seems to resolve this. The upgrade procedure has now been changed and all future implementations of Modbus will have both the Modbus RTU and Modbus IP options enabled on the comm port being upgraded. Resolution For existing controllers that have already had the Modbus RTU option added to the comm port but have not validated that it works and are now seeing this problem, obtain a new upgrade cookie from Repairs requesting that both the Modbus RTU and Modbus IP options be enabled. All new orders for Modbus RTU or Modbus IP will have both options enabled on the comm port so this problem does not occur in the future.

Issue Continuum Standalone system use SQL Express without function of maintenance, So other method need to be implemented  to do this task Environment Cyberstation SQL Express Cause Require to backup the database with a record. Resolution Install SQL Server Management  Studio Tools for SQL Express Backup the database to specify path, such as "D:\backup\ContDB_Mon.bak" Run SQL Server Management Studio Express and create a new query Copy the following SQL syntax and paste in this new query then  run it EXEC Sp_Addumpdevice 'disk', 'ContinuumDB', 'D:\backup\ContDB_Mon.bak'   Create another new query called ContDB_BU_Mon.sql, copy the following SQL syntax and paste in the query  then run it Select getdate() as "ContDB backup startTime" go BACKUP DATABASE  [ContinuumDB]  TO [ContinuumDB] with Format, INIT,NAME= N'Contdb_Mon Database Backup', SKIP, Norewind, NOUNLOAD, STATS = 10 go select getdate() as "Contdb Backup Endtime" go  Close the query above and save it to D:\backup\ContDB_BU_Mon.sql Create a .txt file with the following command then save it as .bat file OSQL -S(Local)\SQLEXPRESS -E -i  "D:\backup\ContDB_BU_Mon.sql" -O  "D:\Backup\Contdb_BU_Mon.log"   From Windows Control panel > Performance and Maintenance > Scheduled Tasks, Add Scheduled Task, select the "Browse" button, find the .bat file you want to run, then set the time schedule you desired. After the scheduled task created successfully, the database backup will be executed scheduled with record. the record was written in the file Contdb_BU_Mon.log.

Issue Get error message "Could not open or load translation table" when trying to save a Menta file after having edit it in StruxureWare Building Operation. Environment StruxureWare Building Operation version 1.2. Cause Error in the installation of the German Language pack. Resolution Reinstall the language pack.

Issue Since all actuators listed in the V392 documentation are obsolete, a replacement is requested.  Environment Valve V392 M5C M15C EM5C M44 M42 EM42 TAC Forta Cause Obsolete actuators need to be replaced Resolution The Forta series actuators are suitable as replacements. Make sure the correct size is chosen for the application.

Issue Not possible to download a MTA file to a Xenta from the System Plugin. The download was really slow and finished with an error. When the Xenta was decommissioned in Lonmaker it was possible to do the download.   Environment Tac Vista 5.1.7 System plugin 5.1.7 Lonmaker Cause The download problem is probably due to too much traffic to or from the Xenta on the Lon channel or that the Xenta have to much to do. If the problem is too much traffic to the Xenta is most likely to the I/O modules, one reason I have seen before is that an I/O module is specified in the Xenta but it doesn't exist, then the Xenta will try to reach it over and over again and it is very hard to get a download of the mta to work.   Resolution Workaround to get the mta file down:, Decommission the Xenta, Download the file  Commission it again.   To solve it check that no I/O modules is specified in the Xenta which don't exist on the network.

Issue Is it possible to calibrate a Controlli TQ-A31 Air Quality sensor? Environment Controlli TQ-A31 Cause In field calibration procedure. Resolution It is not possible to calibrate the TQ-A31 sensor on the field. You should read a 0..10Vdc voltage between B and C terminal. If the signal between these two terminal is not in the 0..10Vdc range than it can be the product is defective and therefore I suggest you to send it back to us through the usual claim system.

Issue When attempting to create a SOAP Web Service in StruxureWare,  WorkStation crashes after pressing the "Get operations" button for a WSDL file. Environment StruxureWare Workstation version 1.2.0.767 (released 1.2 build) Cause StruxureWare only accepts simple data types in the WSDL file.  Some WSDL files (e.g. Microsoft Exchange Server) uses complex data types (types.xsd) for input parameters and StruxureWare cannot process these data types.   Workstation crashes because of an unhandled exception. Resolution The unhandled exception error crash will be addressed in a future release so that Workstation does not crash upon receiving the error.  At this time, StruxureWare cannot process complex data types in WSDL files, and there are no plans to add this feature.

Issue With the valve obsolete, are the spare stuffing boxes available? Environment V294: 7219406000 7219410000 7219414000 7219418000 7219422000 7219426000 7219430000 7219434000 7219438000 7219442000 Cause Obsolete products and their spare parts Resolution V294 and all accessories/spare parts are obsolete since the end of 2010. No direct replacement parts are listed.  

Issue Popup window displays "License Invalid", "License Registry Error", "License on wrong machine" or other related error when starting the WPT software. Environment WPT software (any release) Cause License information stored in license file does not agree with the WPT/WPTL license information stored in the Windows registry. Resolution Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file.  NOTE: If the old computer has WorkPlace Tech release 4.0.0 or release 5.x.x prior to release 5.7, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed).  If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open".  This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. Locate the license file listed on line 1 of the WIB License Diagnostic display. Email the complete displayed text error message along with a zipped copy of the license file and diagnostic output file to Product Support A product support case will be created for you with the submitted information.  A product support engineer will contact you after reviewing your submitted information to assist you in correcting the issue.

Issue In some cases, the annual drift of sensors are requested. Environment STR500 004606000 STR502 004606100 STR504 004606200 STD500 5123074010, 5123078010 STD501 5123082010 Cause The annual drift of the sensors is not documented in data sheets or similar. Resolution Unfortunately, this information is not available from the manufacturers of the sensor elements.

Issue With the M42 series actuators being obsolete, they need to be replaced. Environment M42 Actuator M42/230 8401000000 Actuator M42/230 8401300000 Actuator M42P/24 8402100010 Actuator M42PBB/24 8402400010 TAC Forta series M9/EM9 Cause Replacement of obsolete actuators. Resolution Spare part for actuator for valves with linear moving stem the complete actuator TAC Forta should be used. When a 230 Volt actuator is requested the TAC forta needs a supplementary 230/24 Volt transformer. Depending on the electrical installation certain modifications may be necessary. For valves with rotating stem, actuators M9/EM9 can be used.

Issue What effect does it have on a BACnet network if the Network Id - UDP setting in bCX40x0's on the same BACnet IP network have been set to different values? Product Line Andover Continuum Environment Continuum BACnet bCX4000 bCX4040 Cause A site had it's routers configured with different Network Id - UDP values and communications between controllers were not reliable. Resolution In the scenario below, the routers have different Network Id's for the UDP network. They may still be able to talk with each other, but they will all think they are on different networks which could cause routing issues and much more traffic than is required.  Controller         UDP NET ID                                         UDP COMM2 1                                  1                                                            2701 2                                  2                                                            2702 3                                  3                                                            2703 4                                  4                                                            2704 5                                  5                                                            2705 6                                  6                                                            2706 7                                  7                                                            2707 If all of these bCX's are on the same IP network then they will need to have the same Network Id - UDP value. By default we (and most other BACnet vendors) use a Network Id of 1. Change all of the bCX's so they are on Network ID - UDP of 1, as below. Controller           UDP NET ID                                         UDP COMM2 1                                  1                                                            2701 2                                  1                                                            2702 3                                  1                                                            2703 4                                  1                                                            2704 5                                  1                                                            2705 6                                  1                                                            2706 7                                  1                                                            2707

Issue 'Error waiting service pin' when attempting LonWorks communications in WorkPlace Tech Environment I/A Series WorkPlace Tech Echelon U10 USB Network Interface Cause WorkPlace Tech is not recognizing the Echelon U10 USB Network Interface.  The U10 USB Network Interface is recognized correctly in Windows Control Panel > LonWorks Interfaces.  Resolution Reinstall the U10 USB Network Interface and the Echelon Open LDV driver. To uninstall the U10 Network Interface (with the U10 Network Interface physically connected to an USB port): In Windows, go to 'start' > 'run', type in 'devmgmt.msc' and click 'OK'. This will bring up the Device Manager.  Expand 'Universal Serial Bus controller'. You should be able to see 'Echelon USB Network Interface'. Right-click on the 'Echelon USB Network Interface' and select 'Uninstall'. Remove the U10 Network Interface from the USB port. To reinstall the Open LDV driver: Uninstall Echelon Open LDV driver from Windows Add or Remove Programs. Install Echelon Open LDV driver using the installation file.  After completing the above steps, connect the U10 Network Interface to an USB port on the computer. It should automatically install. Test with WorkPlace Tech. 

Issue Request for technical documentation and data sheets for Senseair aSENSE m III Environment Senseair aSENSE m III 6553064000 Cause The requested documentation is not available through Schneider Electric. Resolution Since this is a Class3 product, the manufacturer is providing technical documentation. Please see www.senseair.com for details and download.