Building Automation Knowledge Base

Issue How to reset an ACX 57xx model controller Product Line Andover Continuum Environment ACX 57xx Cause While upgrading/downgrading the controller firmware, communications were lost and the controller is not communicating afterwards. Resolution Consult How to reset a ACX 57xx controller to reset the controller and then re-commission.

Issue How does the import/export (IE) system work in the Continuum controllers? Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller. The principle is that the value of a controller point that is referenced by other controllers on the network only needs to be sent out when it changes, much like the BACnet COV which stands for Change Of Value. The two parties involved in the IE transaction are the controller that owns the point (the owner) and the controller(s) referencing the point's value (the subscribers), a second CX controller may also be involved and acting as a router when a value is imported/exported from/to a remote field device under a remote CX. Resolution Read more in the attached document, Understanding Continuum IE System.  See how to correct Import Export tables KBA

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. Issue Finding the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line Andover Continuum,EcoStruxure Building Operation Environment Continuum Cyberstation Building Operation Automation Server Premium (1.9 onwards) Building Operation Automation Server Bundled (1.9 onwards) Cause The wrong procedure has been followed which is not the approved and tested procedure to be used when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet The RS-485 network cable should be routed in a continuous daisy chain bus configuration. There should not be any stub connections, stars or ring configurations. The bussed cable should pass through each node to be connected with no splits or branches in the cable network. Repeaters can be used to achieve the star, distributed star (backbone with clusters), off of the backbone. For additional information, review the article: EBO Webhelp Cabling Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site From Continuum CyberStation,  the following must be completed to each Infinet controller that you are moving to an AS-P. Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. If the conversion was done on the PCT, deploy the AS-P. Verify that the AS-P firmware is 1.9.0.73 or higher. Disconnect Infinet bus from the Continuum controller com port(s). Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. Confirm that the Infinet devices are all showing online under the AS-P Download the Infinet devices. * Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Please also see the "Infinet under the hood" community post Continuum Conversion Tool NOTES V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly v4.0.3 has an issue converting Infinet controllers, 4.01 or 4.02 should be used instead Now fixed in v4.0.3.5005 CP3(Known Issues) v3.x outperform 4.x, 5.x and 6x.(known Issues). The Workaround is to convert the dmp file in CCT 3.x then upgrade the DB to the expected version in PCT or AS-P.

Issue Where are example Plain English programs and functions stored for typical BMS applications? Product Line Andover Continuum Environment Plain English (PE) Functions and programs. ACSM, PID, Optimiser, ISM, First Aid. Standards Bacnet Optimiser Cause It is always easier to write your Plain English programs starting from documented examples rather than a blank page. What is available? Resolution The following link is to a .zip file containing various BMS standard modules originally developed by the UK Application engineers for Infinity SX8000 and were known as the Infinity Standard Modules (ISM's), they were then updated to Andover Controls Standard Modules (ACSM's) for Continuum. These modules are example functions or building blocks that can by used globally by application engineers to provide the control and monitoring appropriate for your own buildings. Link: Click here. In addition to these functions other examples are in the online help for the corresponding Plain English keywords, and other applications can be found on the Forums; see Sample PE functions and programs for further details. For Smart Sensor examples see Example programs for Smart Sensors TTS-SD-LCD-1 and TTS-SD-LED-1 for details. For example Security programs see the Download Center link, Click Here.

Issue MBus to Modbus TCP Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Mbus Modbus Cause How to read MBus devices into a BMS System using Modbus TCP Resolution There are different methods, but these are generally using a Modbus RTU / Mbus gateway and then converting it to Modbus TCP. The following ADFweb solution allows Mbus to be read directly into a Modbus TCP device. Click here for the datasheet.

Issue Understanding and Troubleshooting Modbus Product Line EcoStruxure Building Operation, TAC IA Series, Other  Environment All Modbus environments. Cause Modicon first introduced Modbus in 1979. Modbus is an open standard,and it is the most widely used in the industrial environment. Modbus is publicly available and,due to its simplicity, many manufacturers use Modbus as a solution for integration in their own products. Many commercial products and systems support the Modbus RTU and Modbus TCP protocols. For further information, visit the Modbus website at http://www.modbus.org. Resolution For a brief understanding on Modbus and how to troubleshoot Modbus, refer to the Modbus Troubleshooting PDF

Issue The specifications and setup details of the EH series humidity sensors. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, TAC IA Series, TAC INET, TAC Vista Environment Humidity Sensor Cause The EH Series Room, Duct and Outside humidity sensors are a universal Relative Humidity transmitter that can be powered with either a +15 to 36 Vdc or 24 Vac supply voltage. The EH series sensors are designed with a field selectable 4-20 mA, 0-5 Vdc, or 0-10 Vdc output signal that is equivalent to 0 to 100% RH. The EH Series is used in building automation system, humidity chambers, and OEM applications and is compatible with Vista, Continuum, I/Net, I/A, and SmartStruxure systems. Resolution EH Series Humidity Sensors Click the below links to look at the documentation for these sensors including the dip switch settings. EH Series Humidity Sensor Data Sheet EH Series Humidity Sensor Installation and Operation Instructions Old EH Series Humidity Model For information on the older style of dip switches (models with two separate sets of dip switches), see the document below. Old EH Series Humidity Sensor Installation and Operation Instructions

Issue How to reset an NC2 9680 model controller Environment CX 9680, NCII, NC2 Cause While upgrading/downgrading the controller firmware, communications was lost and the controller was not able to communicate afterwards.   Resolution Reset controller and re-commission. Please click here for document on how to reset the CX9680 controller.

Issue Troubleshooting steps for the Infinet and MSTP bus. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum SmartStruxure RS-485 Infinet BACnet MSTP Cause Methods are needed to troubleshoot the Infinet and MSTP bus Resolution This is not a comprehensive list of all methods for troubleshooting, but a starting point. The Infinit-mstp troubleshooting document is available here. NOTE If BACnet MSTP devices do not support COV subscriptions, then care must be taken when reading values (eg EBO trends or alarms) as excessive traffic can be created that overwhelms the communication bus. For example, if 30 non-COV BACnet devices have EBO alarms (or EBO change of value trends) bound to 4 objects in each controller, this will create 240 packets (reads/replies) that will be attempted every "Minimum polling Interval". This is likely to fill the MSTP bus bandwidth  

Issue PID Definitions and definition for AutoTune PIDs. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum 1.94 StruxureWare Building Operation 1.1 and higher Cause Argument for bPID in Continuum and StruxureWare Building Operation are: Arg 1 Ena Arg 2 Type Arg 3 Cv Arg 4 SP Arg 5 Kp Arg 6 LKi Arg 7 LKd Arg 8 Db Arg 9 OP Arg 10 Bias Arg 11 Isum Arg 12 err Arg 13 Ltim Arguments for AutoTuner PID Continuum and StruxureWare Building Operation are: Arg 1 Ena Tuning Enable Arg 2 Type type of control Arg 3 Cv Measured variable Arg 4 SP Setpoint Arg 5 Kp Proportional gain constant Arg 6 Ki Integral gain constant Arg 7 Kd Derivative gain constant Arg 8 Db Deadband Arg 9 OP Output Arg 10 Lag Output Device Lag time Arg 11 Dev Deviation from setpoint allowed Arg 12 Pd Passed Data Array of 17 Numerics Arg 13 Ta Time Date Array of 3 Variables Resolution For AutoTunerPID Wizard keep in mind that it is different than PID or often referred to as BPID. There are 3 types of PIDs bPID (normal PID) Simple PID (which was used for less memory available in controllers and had 9 Arguments) AutoTunerPID (designed to be run once on a system to ascertain the required values of Proportional, Integral and Derivative factors (Kp, Ki, Kd), when complete the function is normally to be replaced by the standard PID function as it will run faster with less system overhead. However when tuning is complete the PID tuning function will continue to control the plant using the standard PID function.) Please note that PIDs are no longer autoconfig and there is no generic PID functionality with Continuum 1.94 and StruxureWare Building Operation 1.1 and higher, but custom solutions instead.  bPID information on page 101 available in PID Function.pdf Simple PID is on page 90 of the above link AutoTunerPID information available in PID AutoTuner.pdf

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell DxT sensors are replaced by STR600, STP660, STD600, STO600 type T with shunt, and use the Satchwell T range chart Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding INET, IA, the document Thermistor Types Tables (Veris Industries) is available.  The 1k Balco resistance chart is also available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series 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. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

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. Issue The size of ContinuumDB has reached or is near the 2Gb limit imposed by MSDE. The size of ContinuumDB has reached or is near the 4Gb limit imposed by SQL Express. Environment MSDE SQL Express Continuum Stand Alone. Cause The database is well over the SQL size limit (2Gb for MSDE, 4Gb for SQL Express) Since the database size has already exceeded SQL's limitations it is not possible to use the deletion query statement to truncate the log tables.  This is because SQL will attempt to guard against data loss during the deletion process by making a copy of the tables contents before deletion occurs. Before a single row has been deleted from the table the size of the database will actually grow larger, exacerbating the problem. Resolution You must delete the contents of each log table entirely (Alarm, event, error, log) using the TRUNCATE statement. This will delete the contents of these tables entirely without first storing them the data. Please note, you must... Make arrangements with the customer so that they can archive any log and event data they wish to retain. Backup the database before using the TRUNCATE TABLE command. Here is the syntax for the TRUNCATE statements TRUNCATE TABLE ContinuumDB.dbo.AlarmEvent TRUNCATE TABLE ContinuumDB.dbo.AccessEvent TRUNCATE TABLE ContinuumDB.dbo.ActivityEvent TRUNCATE TABLE ContinuumDB.dbo.ErrorEvent TRUNCATE TABLE ContinuumDB.dbo.ExtendedLog Once the table have been truncated, Right click on ContinuumDB and select Shrink > Database. Once the database size has been reduced, check the size and retest. Please note that once the database size has exceeded SQL's limit it is likely that the database has been damaged.  This process may or may not correct damage that has occurred to the database.  

Issue Which printers, signature pads, and capture devices are supported with the badging editor? Product Line Andover Continuum Environment Epi-Suite Epi-Builder Cause Determine which ImageWare systems (Epi-Suite or Epi-Builder) to use with the Continuum system. Resolution Continuum OEM's third-party badging software from Image Ware Systems are Epi-Suite and Epi-Builder. If your using Continuum version 1.8 and newer versions, Continuum uses the Epi-Builder version. For versions of Continuum 1.74 and prior, they use Epi-Suite as the badging editor. The hardware compatibility list for the Image Ware products can be found on their website. https://www.tech5-us.ai/epi-suite-support/    Once on their website select Support/Customer Service/ either IWS Epi-Builder or IWS Epi-Suite. The page that is displayed after these selections you'll notice a link on the left-hand side of the page for Compatible Hardware. The lists for printers, capture devices, and signature pad readers can be displayed when clicking on the links for each. The peripherals can be found at: https://www.tech5-us.ai/epi-compatible-hardware/ 

Issue Partners and branches need to understand the terminology used with Security Expert and what those terms mean from a Continuum perspective Product Line EcoStruxure Security Expert Environment Security Expert Continuum Cause A table key to map object terminology between Security Expert and Continuum Resolution   Continuum Security Expert Objects Records User Operator Personnel User Area Door Group (Area) = Intrusion/Antipassback/Counting Area Rights Access Levels AC1/IOUs Reader Expanders/RDM2 Numerics Virtual Inputs/Outputs Plain Enlgish Programmable Functions/Function Code/services Event Viewer Status Pages Alarm Viewer Status Pages Listview Status Pages Power Supply Analog Expander Network Sites NC/ACX Controller SPC Doors Doors Security levels Security levels Schedule Schedule Scedule Exception Calendar Action Holiday Holiday Reset Manual - Factory default – short Reader, L2D0, download Array Data Values Permisssions/Security Levels Record Groups +V V+ Ground V- Data 1 1 1 Clock 0 0 0 LED L1    

Issue Infinet/MSTP was running fine until a device was added or replaced, after wiring in the new device it brings down the Infinet/MSTP field bus when powered up, disconnecting the new device from the bus makes the bus resume operation. When the new device is connected the green (RD) LED goes solid instead of blinking and all communications to all devices on the bus stops, in some cases the master controller will reset. Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet devices i2s MSTP devices b3s Cause Power lines reversed. Continuum field devices (i1s, i2s and b3s) have their RS-485 communication lines connected to ground via an isolator as seen in the diagram below, if the LIVE and GND lines are inverted then LIVE is connected to the 485 communication lines instead of GND. This will make the field bus electrically unable to communicate and, in some scenarios, can even cause hardware damage. Resolution Ensure Correct Wiring: When powering 24VAC devices off the same transformer, make sure to continue the wiring chain LIVE to LIVE and GND to GND. In the field, it may not be very obvious that the 'Live' and 'GND/Neutral' wires have been swapped. A multi-meter can be used to verify the wiring. Set the multi-meter as appropriate to measure 24VAC. Place the black lead of the meter on the GND/Neutral termination at the power connector of the field device.  Use the red lead of the meter to measure the voltage at the +/- termination at the RS-485 (Infinet or MSTP) on the controller. The measured voltage should be very low, between 0 VAC and 1.1 VAC, a voltage reading of about 10 VAC indicates the Live and GND/Neutral wires have been swapped.

Issue BACnet requires applications to listen on the same port across the IP subnet to receive BACnet discovery broadcasts. Two applications running on the same machine can not use the same port as the Listening Port. Product Line EcoStruxure Building Operation, Continuum, TAC I/A Series Environment Building Operation Enterprise Server I/A Series WorkPlace Tech Continuum Cyberstation Cause The site can not provide a separate machine or VM for each BACnet application, which is recommended for independent operation. Resolution With this configuration, one application will act as BBMD to receive and distribute BACnet Broadcast Messages. The other application will act as a Foreign Device, relying on BBMD to relay BACnet Broadcast messages. Once BACnet devices and the Application, configured as Foreign Device, have shared their IP and Port, messages between them will be unicast and will not pass through the BBMD. Ensure one application can be configured as a BACnet BBMD and the other as a Foreign Device. Configure one as BBMD, usually EBO Enterprise Server Configure the other application as a Foreign Device referencing the BBMD IP and Port

Issue Attempting to add a Building Operation ES license using the entitlement ID results in an error indicating that the server cannot be contacted. Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Building Operation Device Administrator Cause The ES computer does not have an Internet connection Resolution To activate a license using an entitlement ID, an Internet connection is required to validate with the Schneider Electric main license server. Follow these steps: Ensure Internet Connectivity: Verify that the ES computer has a stable Internet connection. Refer to Documentation: Consult the following resources for detailed instructions: How to activate, release and/or transfer a license in EcoStruxure Building Operation License server and port used to reach Building Operation licensing server Additional Information: For further assistance, visit the Schneider Electric Building Automation Knowledge Base or contact support.  

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!