Building Automation Knowledge Base

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!    

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