Building Automation Knowledge Base

Issue General Continuum instability is followed by the following error when viewing Graphic panels. "Pinpoint: Failed to call pILiveData->GetLiveData(). ACDataServices has an error." Product Line Andover Continuum Environment Continuum Cyberstation Cause Continuum has become unstable due to modules not starting up properly. This can be evidenced by looking at the Windows Application Event Logs for "Send Email" errors when alarms occur. This may then be followed by Continuum applications starting to crash and post errors. Resolution Remove "email" and "page" entries in Event Notifications if there has not been an Email client installed and configured to email alarms. Set Windows virtual memory settings to 4096. Ensure time synchronization between Cyber and CX. In Continuum General preferences set the Time Interval Between Requests to 100 (default is 30). Set COV increment for noncritical points to non-zero numbers (default is 0). Upgrade to 2.03. If already at 2.03, a reinstall of Continuum may be necessary or at least the pre-requisite 'Visual C++ 2005 redistributable'. Also refer to: Crash of ACCDataServices on start-up or run 

Issue What is its part number of the power fuse of an i2/b3 controller? Product Line Andover Continuum Environment Power fuse replacement i2 and b3 controllers 24VAC supply Cause Most controller fuses are not supplied through the factory. Resolution Faulty controllers can be repaired through the regular repairs process, but power fuses can be purchased through local suppliers. The power fuse for the following 24VAC controllers is: Type: Surface Mount Fuse NANO2® Very Fast-Acting, 448 Series Datasheet Ratings: 2A Rating: i2/b3867, i2/b3850 series. 3A Rating: bCX1, i2/b3810 series, i2/b3800 series, i2/b3600 series. 5A Rating: ACX5740, ACX5720 Note: Fuses are fitted to protect the controllers from damage, when replacing one always replace it with an equivalent rating. Also determine the reason why a fuse has blown before replacing, under normal operation a fuse should never blow.  Additional Information CX9702 (115 VA) Main Power Fuse: 250 VAC 1.5Amp Outputs: 125 VAC 3.5Amp replaceable Inputs/Outputs: Surface mount non-replaceable i2/b3814 outputs: see What is the part number of the i2814's output fuse? Note: The part numbers that used to be listed in iPortal have been removed from this article since they are no longer available from Schneider Electric. The fuses may be obtained from third-party vendors such as Littelfuse or Digikey.

Issue Why do the Architectural Guidelines specify a maximum of 1500 Extended Trend Logs in Automation Servers, whereas such a limitation did not exist with the Continuum Net Controllers, like the NetController II.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause EcoStruxure Building Operation's architectural guidelines specify a limit of 1500 Extended Trend Logs for the Automation Servers (AS-P/AS-B). Sites transitioning from Andover Continuum to EcoStruxure Building Operation need to understand the architectural differences that necessitate this limit. Resolution The architectural differences between Continuum and EcoStruxure Building Operation means that it is crucial that Extended Trend Logs are managed effectively to ensure ensuring optimal system performance.   In Continuum: Controller Role: Controllers do not participate in Extended Trend Log functionality beyond sending data from intrinsic logs upon request from Cyberstations. Log Management: Extended Trend Logs reside at and are managed by Cyberstations. Load Distribution: Multiple Cyberstations, configured to collaborate, maintain the Extended Trend Logs, minimizing the load on controllers.     This design puts very little load on the controllers when it comes to Extended Trend Log functionality.   In EcoStruxure Building Operation: Distributed Database Architecture: Extended Trend Logs are managed by the AS-P/AS-B servers. Server Load: The server performs tasks typically handled by multiple Cyberstations in Continuum, which often run on more powerful PC hardware. Performance Management: To prevent Extended Trend Log servicing from overwhelming the Automation Server's resources (CPU, memory), a limit of 1500 logs is enforced. Exceeding this limit can degrade server performance and potentially cause reboots due to critical memory usage.  This can be seen in the following example trace log entry: Nov 30 15:39:58 PSS-AS02 memcritsv[1011]: Memory usage critical!    

Issue In Andover Continuum, the model name of a field device (i2/b3) is always obtained from the SQL database as there is no direct way to retrieve the model directly from the controller. Consequently, discrepancies between the model stored in the SQL database and the actual controller may lead to uprev errors like "This Uprev file does not match this type of controller"     In the screenshot above, note that both the device's editor as well as the command line, report the controller's model as i2800, when in fact the hardware associated with the device is an i2920.   Note: In EcoStruxure Building Operations, where a distributed database design is employed, the device's model type is always obtained from the proxy representing the device in the Automation Server. Product Line Andover Continuum Environment All i2s All b3s Cause Frequent model mismatches for i2/b3 devices in Continuum installations often result in errors when attempting to upgrade the device's firmware. Resolution To obtain the device's model (controller type) from the Continuum controller hosting the device follow the steps below: In the master controller, create an InfinityNumeric, in this example we will name it 'DevModel' In the master controller, create an InfinityProgram, in this example we will name it 'GetDeviceModel' Enter the following lines of code in the program... DevModel = <device_name> CntrlType Stop ***Replace <device_name> with your i2/b3 device's name   Note in the screen capture above, that the program reports the actual device's model to be i2920. The mismatch needs to be corrected by either installing the correct hardware or adjusting the model in the device editor in Cyberstation to align with the hardware.   IMPORTANT If the program reports the model as 0 (zero) it means the proxy representing the device in the master controller has lost the model number, you will need to reload the whole master controller to recover, make sure to select the option to reload the controller but NOT its children.

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE EcoStruxure Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue Continuum Cyberstation running on Windows 7 machine.  Cyberstation crashes unexpectedly.  Cyberstation crashes when an alarm come is reported. Product Line Andover Continuum Environment Continuum CyberStation WebClient Outlook Cause Event notification alarm delivery configured to send email alarms when Outlook is not installed on the workstation. Resolution Either remove the email option from the event notification, or install Outlook and set it up for alarm emailing. If enhanced alarm delivery is selected (Database Initialization> Server(Stand alone)> See check box for enhanced alarm delivery Ensure that recipient Cyberstations do not have page, log, forward options selected. Only use email if it is being used. Example: Ensure that if an object is selected in an event notification action (i.e display graphic) that the point that is being alarmed on has that object (graphic) selected. Related article:  https://community.se.com/t5/tkb/workflowpage/tkb-id/knowledge-base_public/article-id/6986 

Issue The ACCDataServices application is crashing on start up of CyberStation Product Line Andover Continuum Environment CyberStation Windows XP Cause Windows permissions issue Windows Firewall Configuration  Resolution Make sure when installing CyberStation the user has Local Admin rights to the computer Make sure Windows Firewall is turned off during the install Make sure all VirusScan software is turned off during the install. Check the event notifications and verify that none of them are set for the recipients to have pager, log, forward or any unused option which can create unnecessary traffic when using enhanced alarm delivery. To check if you are using enhanced alarm delivery Database Initialization > Server (or Stand Alone) > see check box for enhanced alarm delivery An example of possible unnecessary check box recipient options:  Check that each action in the event notification i.e. 'Display Graphic' has a corresponding object for the point alarming. If no object is selected it may cause accdataservices errors. Run acctrace and/or the Continuum error  log and wireshark to determine if there are errors. Cleaning up these issues can relieve the system and these errors. The Windows application/system logs and system.nfo/Belarc advisor can help gather info about the PC. See Top 10 Steps for Troubleshooting Cyberstation and webClient issues. If there is a 3rd party bacnet device, disable or unplug the device to see if the issue is related to the flooding of traffic into Continuum Liebert Sitelink- If you are on 1.93 and below, the Sitelink trendlogs could affect Continuum. Upgrade to 1.94 and disable trendlogs. Engineering is working on a hotfix for this issue. (Not released as of 11/29/12) Stand Alone Windows 7 system - A stand alone system can easily tax resources when extended logging, graphics, SQL Server, Cyber, etc. are all running on the same system. Eliminate any errors in the error log and disable certain functions to see if this helps. Consider a server class PC depending on what the system functions that are required by the site. Install Cyberstation 1.94 SP1 and related firmware updates as there are many fixes to address accdataservices.exe crashes (See Continuum 1.94 SP1 Service Pack to address accdataserices.exe crashes and other issues) Do not mix 1.94 and 1.94 SP1 Cyberstations on the same db, this could cause accdataservices crashes

Issue Can Cyberstation setup and configure 3rd party BACnet devices. Product Line TAC IA Series, Andover Continuum Environment Cyberstation BACnet I/A Series MNB-1000 Cause It is desirable to configure all products from the same software. Resolution Cyberstation and the BACnet protocol do not allow you to do basic setup and configuration of 3rd party devices, most products will have their own configuration software or local display/ keypads for setup. The I/A MNB-1000 BACnet controllers will require I/A Series Software to setup and configure the controllers, this can not be done through Cyberstation. Once setup and communicating Cyberstation will be able to make changes / adjustments depending upon the PIC's statement of the device.

Issue How to determine if the IOU modules neuron chip is manufactured by Toshiba or Motorola? Product Line Andover Continuum Environment Continuum Cyberstation I/O modules (All modules affected except the AC-1 Plus, VT-1, Infistat, and LC-1) Cause Up-revving I/O modules to new firmware and there are 3 types that have been used,  Motorola, Toshiba and the most recent Cypress neuron chips. The program ID can help determine which neuron is in the IOU module to select the correct firmware. Resolution To determine the chip type, look at the Program ID using the object editor or a list view. The second digit or position of the second number of the Program ID is the chip set indicator. If the second digit is 2, the I/O Module has a Toshiba chip. If the second digit is 1, the I/O Module has a Motorola or if shipped after 2014 a Cypress chip.  See example of object editor below:   ***** Note: The image above doesn't show the Cypress information. a 1 could be Motorola(old) or Cypress (new). If the flash revision is 21 the it is the most recent flash version for the Cypress chip. The IOU modules that could have the Cypress chip are AC-1(Not Plus), A0-4,DI-8,DM-20, D0-4, D0-6, MI-6, UI-8. Motorola or Cypress Ui8s that have an 11 in the second position of the ProgramID are either Motorola or Cypress chips. The modules with ProgramID 11 in position 2 and firmware version 11 in position 4 of the ProgramID are Motorola and 11 is the most up-to-date version. The modules with 11 in the 2nd position of ProgramID and firmware version 21 in position 4 of the ProgramID are Cypress chips.  I have not seen a separate firmware version 21 file for the Cypress chip on Exchange or anywhere. 21 is the most up-to-date version and was shipped with those modules. The email we found indicates that since the Cypress chip was a direct replacement for the Motorola chip they used the same number (1) in the 2nd position of the ProgramID (instead of using 3). To summarize the most up-to-date firmware versions for the Ui8: Motorola: 11 Toshiba: 20 Cypress: 21   There is an old TPA that describes this in detail. You can download the TPA Technical Bulletin 1041 - Continuum IO Modules Now Using the Toshiba Neuron Chip from The Exchange Download Center.

Issue Can the UPS option be added to an existing Continuum power supply? Product Line Andover Continuum Environment Continuum Power Supply PS120/240-AC85 Cause Can the UPS option be added in the field to a Continuum PS120/240-AC85? Resolution No. There is no field upgrade kit to add the UPS option to a Continuum power supply.

Issue Will an i2 device work on an existing installation that uses a CMX241 controller? Product Line Andover Continuum Environment Continuum CMX241 Infinet Cause An installation that has a CMX controller with Infinet and the Infinet 1 controller needs to be replaced with an i2. Resolution The CMX241 controller will recognize an i2 controller, but it will handle it as if it is an infinet1 controller. Some infinity system variables and their functionality will not be recognized such as accrestart mode, accstatusflash, etc... The replacement for the CMX241 is the BCX9640

Issue What does Accuracy and Resolution mean when mentioned in the Datasheet of a controller with a airflow sensor Product Line Andover Continuum Environment B3-865 B3-866 B3-885 Cause Need definition of the meaning of Accuracy and Resolution when mentioned in the datasheet of a controller with an airflow sensor Resolution Accuracy is the amount that the measurement could be “off” from true reading, either above or below.  Resolution is the smallest change that can be detected. 

Issue Customer database server crashed with no backup. Customer needs to re-create the access control database. What data can be recovered from the acx781's? Product Line Andover Continuum Environment Netcontroller ACX781 Hyperterminal Terminal mode Cause Customer database server crashed with no backup. Customer needs to re-create the access control database. What data can be recovered from the acx781's.? Resolution Using terminal mode into the NetController the customer can dump out from the controllers all the doors, numerics, inputs, outputs and PE code. The personnel records are not retrievable, however, as they are not stored in text format in the controller.

Issue With no CyberStation or network controller available, need to load application programs into controller. Product Line Andover Continuum Environment RoamIO2 Cause This item is not in the documentation. Resolution The RoamIO2 does not have the ability to load a dump file into a controller.

Issue The programs Run Times are running fast. Product Line Andover Continuum Environment Continuum 1.82 BCX-4040 Cause Internal Programming corruption Resolution Verify the System variable time on the controller Reload the controller

Issue In the download center there are up to four files for the same version of the IOU modules firmware, how do I know which is the right file for my IOU module? Product Line Andover Continuum Environment Continuum IOU Module Cause The Neuron chip used in the Continuum IOU modules can support two different transceivers which are FTT-10A and RS-485, each type requires a different FW file. Additionally, the IOU module originally used a Motorola Neuron Chip ***, in 2001 the Motorola Neuron chip had to be replaced with a Toshiba chip when Motorola ceased production of their Neuron chips. A 3rd chip was used after, the Cypress chip. *** The AC-1 Plus, VT-1, Infistat, and LC-1 were not affected by the chip change as they did not use the Motorola Neuron chip. So you will only find 2 FW files for the same version and model these modules. Resolution 1. When up revving Continuum IOU modules first determine if the module is FTT-10A or RS-485. To determine the type lift the door cover of the IOU module and check the model written on the label. FT appended at the end of the model is for FTT-10A, RS-485 will either have 485 appended or only the model name with nothing appended at the end. If the door cover is missing then remove the inner cover and take a look at the label on the chip itself. The picture below shows an AC1-Plus FTT-10A module indicated by the FT on the label. If the label is missing you can easily identify FTT versus 485 by removing the upper part of the enclosure and inspecting the components populated in the communication section of the circuit. On the Net Controller itself (99xx or 9680) there will be an ECHELON FT component similar to the one in the picture below located in the upper right corner of the board, the Net Controller's cover will need to be removed to see the component.  2. Verify which Neuron chip (Motorola or Toshiba) is installed in the IOU module. 3. Get the appropriate FW file from the download center. R&D had to recompile for the Toshiba chip. The 20 version is the same as the 10 version and the 21 version is the same as the 11 version. Download the IO module firmware Note:  Version 10,11 are the Motorola processors  Version 20 is the Toshiba processor  Version 21 is the Cypress processor

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. Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue Need sample Plain English code that creates custom web page(s) served by the controller. Product Line Andover Continuum Environment CyberStation CX99xx CX9702 CX9640 CX968x ACX57xx Cause Continuum CX controllers allow user created custom web pages to be served directly from the controller's web server, this functionality requires embedding HTML in a PE program. The purpose of this article is to provide sample custom web pages for illustration. Resolution Get the sample code from the links below Home.txt  Home2.txt Home3.txt IMPORTANT: Some strange characters (i.e. 　) added to the code during upload to this site MUST be removed to make the code compile. Read the instructions on the document below Instructions for using sample code to create a custom web page menu system in the CX controller

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma, Security Expert, TAC INET Environment Existing intelligent Building Management System Open Mind High Availability Solutions (Deprecated by manufacturer) everRun MX ztC Edge Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing the system's reliability. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility are site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measures to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components are the leading cause of failure, followed by a lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity. Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with EcoStruxure Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide For ztC Edge solution guide please look at the following link; ztC Edge guide   

Issue What 10k Thermistor sensors are compatible with the I/A Series MNL and MNB families of controllers? Product Line TAC IA Series, Andover Continuum Environment I/A Series LON Controllers (MNL-xxxxx) I/A Series BACnet Controllers (MNB-xxxxx) Continuum 10K T3 Sensors Cause Specification information Job spec requires a specific family of sensors.  Need to know how to compare the TC curves. Resolution Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series.  NOTE: These sensors are no longer available for purchase. The TW2XAXK is the replacement Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S.Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span.   This includes the Continuum 10K T3 sensors.  The table below shows that the resistance in its normal operating range is within a few ohms of the TSMN non 11K shunted sensors.  The Continuum sensor can be used with a parallel 11K ohm resistor. The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here.  Please note that the controller may not be able to use the full temperature range shown in the table.