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

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 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.  

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 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 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 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 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.