Building Automation Knowledge Base

Issue Should automatic updates be turned on for Continuum workstation? Are there certain known issues of updates that have caused problems with Continuum or Webclient? Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows 10 Windows XP  Windows Vista Windows Server 2003 Windows Server 2008 Cause Microsoft Windows has an automatic update feature and frequently releases updates which can potentially affect Cyberstation and Webclient Server. Resolution Automatic updates should not be turned on for a Continuum or Webclient workstation. The Continuum compatibility matrix indicates Windows Operating Systems, Windows Service packs, SQL Server, .Net and Internet Explorer versions that were tested by Quality Assurance at the time of product release. Continuum Quality Assurance does not perform regression testing where new Microsoft updates are tested with Continuum products released in the past. Product Support recommends setting Windows updates to one of the other two options to allow for testing of Microsoft updates: Additional details can be found at: http://support.microsoft.com/kb/306525 Download updates for me, but let me choose when to install them Notify me but don't automatically download or install them   There are several specific updates that have caused issues with Cyberstation or Webclient. This is not a comprehensive list. Occasionally updates will break certain features and we discover this from our internal testing or from reports from partners or branches. Here is a list of some updates that have caused issues. KB835732-  Pinpoint 1.52 crashes when installed on a machine and you are accessing graphics from a network share. If you remove the hotfix the problem goes away.  This is the same hotfix that caused the SmartHeap out of Memory errors that was fixed with SP5 for 1.6.  KB828741- IIS (Webclient) machines without this patch may receive “Unable to establish a link to the remote Infinity services” Webclient 1.73 - Any patches that will install .Net Framework 2.0 will cause problems with webclient 1.73 since we don’t start using .Net 2.0 until webclient 1.74. KB911280 - this update blocks the acc.scp script from setting controller to PPP mode. This will a cause a Cyberstation using RAS controllers to not allow a connection. It will authenticate, but not connect. KB928366 – Webclient machines that use .Net 1.1(Listed on the compatibility matrix) will receive the error "Could not connect to server cause; type missing for member of type object _context id'. Could not create acwppserverproxy."  when opening web pinpoint graphics.  Remove this hotfix or upgrade to webclient 1.74 or greater. KB929969 – this hotfix does not require a reboot by Microsoft, but can cause the Cyberstation install to fail, if the install is performed before rebooting after the installation of the hotfix. See the Technical bulletin. KB968749 - SQL Express install fails on XML6 SP2 See SQL Express install fails on MSXML 6.

Issue Continuum supports different Wiegand card formats and Custom formats, what is the largest card number that can be used? Product Line Andover Continuum Environment ACX57xx (ACX5740, ACX5720) AC1, AC1-A, AC1 Plus ACX780, ACX700 Custom Wiegand - AccessFormat Array Corporate 1000, 26 bit, 32 bit, 37 bit. Cause When ordering access cards and configuring personnel you need to know the maximum numbers allowed. Resolution When configuring a Personnel object the maximum card number that can be entered is 4,294,967,295 the largest 32 bit number. This is the largest possible card number when working with Custom Wiegand. The maximum site code that can be used is 65,535 the largest 16 bit number. Other Wiegand formats: Continuum 37 bit: (Also known as Infinity 37) Card number range: 1 - 524,287.  Site Code range: 1 - 4,095 Note: This is a proprietary format and further format details are not available. Continuum 32 Bit (old format, not recommended for new sites): Card number range: 1 - 8,191.  Site Code range: 1 - 2,047 26 Bit open standard: Card number range: 1 - 65,535. Site Code range: 1 - 255 Corporate 1000 standard: Card number range: 1 - 1,048,575. Site Code range: 1 - 4,095 NOTE For custom formats the maximum format must not exceed 64-bits (i.e. start/end bit of the site code, card number, etc.) See Which HID card formats are supported by Continuum?.

Issue Netcontroller is running slowly or occasionally goes offline (bCX NC2 ACX CX) Product Line Andover Continuum Environment Continuum Netcontroller, Net Controller, Infinet, MSTP, Bacnet, Xdriver, x-driver Cause There are various reasons why the operation of one or more Netcontrollers and or attached controllers is slow and/or goes offline occasionally.  This guide is primarily to help collate the right information which may identify the issues.  If the reason cannot be identify then this information can be provided to support for further analysis. Resolution General troubleshooting techniques should be used. Define the exact problem. What exactly is slow? eg. Sending to the controller or its connected devices, opening or refreshing graphics, opening or refreshing points, updating Xdriver points, saving programs, creating new points. Is the controller slow from all cyberstations? Is the controller always slow? If not then try to find what makes it go slow, it is time related? Can certain steps be taken to cause the slowness or offline to happen? Get a screen capture of any errors. Gather site information. Continuum version, Continuum hotfixes and service packs applied, number of Cyberstation. Cyberstation operating system, details of Ethernet network and subnets used, with BBMD information of Bacnet sites (Asbuilt or a spreadsheet with IPs, etc.) Continuum Analyzer report, site controller map or spreadsheet or text dump Check the PCs running Cyberstation, do they meet the system specifications? Gather controller information What is the Scan rate? Is the controller time sync. correct? How many objects are on the controller, how many programs are running? What is the firmware version of the netcontroller and b3 or i2 controllers? Ethernet connection - Is the controller on the same subnet as the Cyberstations? A wireshark trace may help to establish the quantity of traffic on the Ethernet (See Using WireShark to analyze communications on an Ethernet network) Comms Ports - XDriver being used? What is on the comms ports? Xdriver (how much communications, points etc) Comms Ports - Bacnet MSTP - How many b3 controllers? How much extended logging? How many alarms being sent? How many 3rd party devices? Look at bacnet settings, how many values are being sent across the network? Check COV settings. Try removing the MSTP cable from the bCX (there could be an issue with an MSTP device causing the bCX to go offline/go slow) Comms Port - Infinet - How many infinet controllers? How much extended logging? How many alarms being sent? Look at infinet settings, how many values are being sent across the network? Check port reconfigs and errors. Try removing the infinet cable from the NetController (there could be an issue with an infinet device causing the NetController to go offline/go slow) Comms Port - other. Again try removing the comms cable from the NetController (there could be an issue with a device on this network causing the NetController to go offline/go slow) Run the Controller error log tool to gather the controller errors See Gather Continuum Controller error logs if requested by Product Support for troubleshooting If the controller goes offline, run the alarm listview.  Does it line up with the Controller error log? Check the CPU LED flash rate on all connected devices (i1, i2, b3 etc) as Can't bring bCX online in Continuum but do get a response to pinging its IP address, also the RD and TD LEDs should be checked for anything unusual This guide is primarily to help the on site engineer by helping them to assess the site. If there is still a need to contact support, please review and record as many items above as possible and send them to the case owner.  Further tests can be carried out including an ACCtrace to determine if the restriction could be at the Cyberstation, See How to capture Continuum Cyberstation activity using ACCTrace NOTE: Ensure all Cyberstations, Controllers and other laptops used for logging are in time synchronization before recording any logs. If it is believed there is an issue with the Infinet or MSTP network see Infinet and mstp bus troubleshooting If it is believed the problem is with extended logging see Extended Logging gaps, performance and load balancing It is possible that something connected to the controller causes the controller to go offline, try disconnecting all other cables and connections to the controller and then re-testing Where a controller is offline when connected directly to a PC/Laptop, try resetting the IP address, otherwise the controller will probably need replacing. NOTE Disconnecting all networks from the NetController is often a good starting point (reconnected IP/Ethernet cable)  

Issue Netcontroller will not come online in Continuum although the unit can be pinged. Product Line Andover Continuum Environment Continuum 2nd generation controllers (NC2 (CX9680), ACX57, CX9702, bCX4040, bCX9640) 1st generation addendum Cause Even though a unit can be pinged, that does not mean the unit will come online within Continuum, as the "ping" is a very low level communication Resolution Check all settings are correct (IP address, ACCNetID, Subnet Mask, Default Router(Gateway Address)) Check the correct network ports are open, see Router required open port numbers to run a Continuum system Check the site fits within the compatibility matrix, see Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation Check there is only a single Network Card enabled on the CyberStation  For a second generation NetController (NC2, ACX57, CX9702, bCX) Check the web page can be accessed, if it can then double check the network settings. Connect a temporary single user Continuum laptop to the controller directly, manually reset the IP address and bring the controller online (using 169.254.1 Subnet). If this operates correctly then controller fault is eliminated. If the controller is not faulty then the network and/or the Continuum installations will need to be checked. Addendum for first generation controllers: Attach to the controller via hyperterminal to determine it's perspective and to verify the IP address, ACCNetID, Subnet Mask, Default Router. You can also verify if the netcontroller lists the Workstation as a controller indicating it can see the workstation. If not, perform a teach from the Workstation.

Issue What is enabled on a Continuum Security Key? Product Line Andover Continuum Environment Continuum Security Key Cause There's a need to know what version of Continuum is enabled on the key. Resolution Note: The Excel method for viewing enabled key features mentioned below no longer works with Windows10 or greater and because of CyberSecurity issues ActiveX controls have been deprecated by Microsoft in favor of more secure web technologies.  This feature will not be updated for Cyberstation.   The supported version of the keys and what options are available on the key can be verified by doing the following using Microsoft Excel on a Workstation with Continuum and the key installed: Open MS Excel Select Insert> Object Select SecurityKeyreader Control and then Ok You will see an object inserted into the spreadsheet with a list of products on the left and options on the right. Example: Serial Number 1016019 Options Number of Points -1 Adv.WebServerEnable Number of Personnel -1 EpiSuiteEnabled Platform Lan(Multi) OPTxtLoggingEnabled Type Prog.Intg. PESourceCntlEnabled Max Version 1.79 Global 1 0 Global 2 0 Global 3 0 Global 4 0 Windows 7 64 bit will not support the MMC.exe option (mentioned below)   Use the command       mmc.exe /32     This will allow the ActiveX snap-in to be added and will work on a 64 bit PC   ActiveX controls in Excel 32 bit are not exposed by default. Use the following Excel spreadsheet (zipped) to read the security key instead. (Excel must be installed and must be on a 32 bit PC(64 bit shows this as blank) Security Key Reader Excel File You may be prompted to enable the ActiveX control Excel 2003 - The application is about to initialize ActiveX controls that might be unsafe. If you trust this document, select Yes and the control will be initialized. Excel 2007/2010 - Notice the Security Warning below the Toolbar                                   Click options                                   Select Enable this content Upgrading a key requires a call to repair (978-975-9464) for a cookie to update the key. In order to install the cookie, you must use the program, CyberKeyWriter2.exe to enter the new key which is on every Cyber CD in the Continuum\bin folder.    Note: Also see Accessing Continuum Security Key information using MMC instead of Excel that describes another method to see this information using MMC. This feature does not work with newer versions of Windows 10

Issue Cannot bring controller online in Continuum even though all settings are correct. Unable to browse to that controllers configuration webpage but can ping the controller. CPU LED blinking approximately two times a second (2 Hz at 50% duty). Product Line Andover Continuum Environment bCX40xx bCX96xx b3xxx i2xxx Cause The controller is in bootloader mode and has lost its application program. Resolution If the bCX is in bootloader mode, with the CPU LED blinking approximately two times a second (2 Hz at 50% duty), then there are a couple things you can try to do to get the controller back online before sending it back for repair. Basically it has lost its application program and dropped into bootloader mode. Try to uprev the controller with its application firmware to see if that will bring it back online. Attempt to uprev (Update OS) the controller from its device object in Continuum even though it may not show as online. Alternatively uprev the controller using the RoamIO to send the application firmware to the controller. If neither of these options work the controller must be returned to be repaired through your normal RA procedure for your region. (this option may no longer be available, due to the age of the controller) Note: An error code including 6818(hex) (c2026818 has been seen) or 26648(dec) during an attempted download or on a graphic. Example1: Example 2: See a Quick time movie to indicate CPU light modes for controllers that shows the various stages of the CPU LED blink rate.

Issue Controller Error Logs - How to gather Continuum Controller error logs if requested by Product Support for troubleshooting. Product Line Andover Continuum Environment BCX CX  CMX 9680 9900 i2 b3 9702 Controller Error Log Gerry Log Cause Troubleshooting controllers often time requires obtaining an error log from the controller Resolution The controller error logs contain useful diagnostic information when it is necessary to troubleshoot a controller or system problem. Much of what is logged are normal system operations that may assist an engineer in diagnosing a problem in the field. To get the error logs from various controllers follow the procedures below: NetControllers - 99xx  Dumb terminal in using HyperTerminal Sign into the NetController Press V then E and press Enter over the NetController you are attached to Press F2 Hit Alt + Print screen and paste into a Word doc Arrow down to single space or Ctrl+D to page down Hit Alt + Print screen and paste into a Word doc Repeat this process until you are at the end of the errors (up to 200) F4 Exits the error log See the CX Controllers Programmer’s Guide for all terminal keystrokes Email the file to Product Support Services   BCX/i2/B3 Controllers CX9680/ACX5720/ACX5740/9702 Controllers Note: You can not retrieve errors from NetController I (CX9900) using this tool Controller Error Log Tool Navigate to C:\Program Files\Continuum Double click on ControllerErrorLogTool.exe to open (This will do an install the first time) Note: The ErrorLogTool.exe is an older version of this utility and will work, but gives less information and does not contain the error lookup feature. Enter in the BCX or master CX IP Transport type = UDP or TCP depending on controller configuration CX Enode ID = AccNetId from the main CX editor Select Continuum in the Mode area, top right If the controller is a field device then enter the following: CX infinet port = Select the one you want to report on Infinet Node ID = port number of the i2 device you want the error log out of Once all the above required entries have been made: Click Get Log and the page will populate with any errors Once this runs, select SaveAs and name the file Email the file to Product Support Services Suppliment - To gather error logs from Continuum controllers transisioned to StuxureWare please see How to pull the error log from a b3 or Infinet controller in SmartStruxure.

Issue WebClient most common installation problems Product Line Andover Continuum Environment Continuum webClient Server Microsoft IIS Microsoft .NET Framework Cause WebClient is not functioning properly. Troubleshooting steps are required. Resolution Below are some of the more common problems that Technical Support runs into when troubleshooting a WebClient installation. Microsoft DCOM settings (Manually setting up DCOM was needed prior to version 2.0) This is the most common problem that PSS runs into. There are two areas that these settings need to be set in are, “Access Permissions” and “Launch and Activation permissions”. Incorrect DCom settings in WebClient will cause many different problems. It could cause problems with logging into the system, opening graphics, seeing the Active Alarm view, etc… The users that should be in there are below for Windows 2000 IIS and Windows XP IIS servers: INTERACTIVE SYSTEM ComputerName\IUSR_ComputerName (Internet guest account) ComputerName\IWAM_ComputerName (Launch IIS process account) ComputerName\ASPNET (ASP.NET) Additionally for Windows 2003 IIS servers this additional user is needed: ComputerName\NETWORK_SERVICE To help pinpoint the DCOM permission that is not set properly, consult the steps at Identify which DCOM permission are causing DCOM errors when trying to use WebClient. Microsoft .Net Frame work Zone Permissions This is another one of the more common problems in WebClient installs. Not setting the .Net Zone permissions correctly will cause problems with opening schedules in the WebClient browser machines. The .Net zone permissions has to be set on each client browser. See the section in the WebClient install guide on setting the .Net Zone permissions. Microsoft .Net Framework is installed before the IIS is installed If .Net is installed prior to IIS you will see problems with logging into the system, editors may not work, schedules will not be able to be opened. If there is any doubt to whether or not .Net was install before the IIS then open a Windows command prompt and run the below commands. For Windows 2000 Professional it is: c:\WinNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i For Windows XP Professional, Windows Server 2003 it is: c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i For Windows10/Windows7/Server2003 it is: c:\Windows\Microsoft.NET\Framework\v2.05.50727\aspnet_regiis.exe -i Also, Windows10/Windows7/Server2003 using 1.94 SP1 and greater, .net 4.x is used  c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i Run both 2 and 4 commands  Microsoft .Net 2.0 This is not supported until V1.74 and will cause problems with WebClient. You will see problems with reports, schedules on earlier versions. SQL Authentication methods with WebClient The only authentication method for SQL server that WebClient supports is SQL Server and Windows. Due to the methods we use to access data in the SQL database with WebClient the authentication must be set this way. Internet Information Server Secure Sockets Layer (IIS SSL) Currently using SSL with WebClient is not supported in versions prior to V1.74. Remote installs of WebClient due to underlying Microsoft Security a WebClient cannot be installed through any kind of remote terminal services, or RDP. If the system is installed through remote services there will be security problems with accessing WebClient. The correction to these problems is to be directly on the WebClient / IIS machine and uninstall all the WebClient apps, Microsoft .Net, and Microsoft IIS then re-install the applications per our instructions while directly on the WebClient machine. Remote reboots of a WebClient IIS server If you use a remote terminal service and reboot and log on to an IIS server running WebClient you will run into problems with logging into WebClient. (webclient is unavailable error) If using VMWare with 2.0 and above, use the VMWare Open console feature Multiple Network cards in the IIS server Using multiple network interface cards in an IIS server is not supported. Doing this will cause problems with opening graphics through WebClient. Installation of files on the Client browsing machines The first time WebClient is accessed through a browser, either in new installs or upgrades, files need to be installed on that client browser machine. You will need to be logged in with a Windows user that has the permissions to install software. Install of WebClient on the IIS computer while virus scan software is running. Make sure that when installing WebClient, either new installs or upgrades, that any virus scan software is disabled. In some instances virus scan software has caused problems with WebClient installs or upgrades. "&" characters in names of objects Ampersands are special characters in web browsing and should not be used in anything in Continuum that the WebClient browser will have access to. Some of the problems that have been seen are alarms not showing up in the Active Alarm view and not being able to add areas to personnel objects. Setting up WebClient graphics Once WebClient is installed on the IIS server you need to make sure you open CyberStation Pinpoint and set the “Web Locations” for your graphics sharing. If you do not set this you will not be able to access graphics through WebClient. When these are set incorrectly you will see a red “X” next to the path. Ports used in WebClient Until V1.74 we only support the use of Port 80 in WebClient. CyberStation on the IIS WebClient server. In order for WebClient to function properly the CyberStation that is installed as part of the WebClient install on the IIS server must be running. You do not need to be logged on to the CyberStation it just needs to be running. WebClient graphics and firewalls Prior to 1.73 there were some special installation considerations when dealing with customers that had browsing machines both inside and outside a firewall. In the 1.73 WebClient there is no special installation/configuration that needs to be done. The system can be set up as if all the browsers are on the local network. Renaming or changing the Domain of the IIS Server after IIS is installed Renaming or changing the Domain that the IIS server was initially installed with will cause problems with IIS which in turn will cause problems with WebClient. If this has to be done then you will need to uninstall webclient before name change and then re-install webclient. Directory Browsing setting for WebClient graphics In some instances where the Windows security on the IIS server is restrictive you will need to add “Directory Browsing” to the NewGraphicsFiles share in the web site configuration on the IIS Server. In webclient 2.0 and greater, directory browsing is configured during the installation. Using underscores or hyphens in the name of the IIS Server This will cause problems with the operation of WebClient because those characters are special characters in the application.

Issue Is there a way to reset the password for web access to a BCX? Product Line Andover Continuum Environment Continuum site with passwords other than the default Cause The password was changed by mistake. Resolution Restore the controller's user names, passwords and configuration settings to the original factory values (Reset IP button using a two stage operation) The location of the Reset button and the Reset IP button on the controller board. Page 124 in appendix A of the Technical Reference Guide. If you cannot get into Continuum Explorer and edit the controller user under that controller and set the password. You will have to reset the controller and then re-commission and then reload.  Try acc/acc first and then after that the following: Using the Reset IP button The Reset IP button has two stages of operation: Stage 1 is initiated by depressing the button for 5 seconds. After 5 seconds, the IP address, and all network-related addresses entered on the Network Configuration page, are returned to the original factory default values. Stage 2 is initiated by depressing the button for 35 seconds. After 35 seconds, the database is cleared and all persistent configuration data is erased, with the exception of the error log. Note: Depressing the button for 35 seconds performs both operations, setting the IP address back to the factory default setting and clearing the database. When you initially depress the Reset IP button, the CPU Indicator LED will begin blinking. At 5 seconds, the LED will stop blinking and remain lighted in a continuous state. If you release the button before 5 seconds has passed, no changes are made. If you release the button after 5 seconds, but before 35 seconds, stage 1 is executed, but stage 2 is not. The IP address has returned to the original factory value, but the database has not changed. Please see Default IP address for BCX, ACX57xx, CX9702 and Netcontroller II for information on default IP addresses.

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 How to truncate event tables in Continuum databases. Product Line Andover Continuum Environment Continuum 1.xx SQL 7 SQL 2000 SQL 2005 Cause Stand Alone Continuum Databases use Microsoft MSDE and SQL Express databases which have size limitations. Once these databases reach full capacity they will need to have data truncated from tables to try and reduce the size of the database. Databases should never exceed their size limitations, but if they do, reducing the size of some of the tables will in most cases allow the database to be functional again. Microsoft SQL MSDE database size limit is 2 gig Microsoft SQL Express database size limit is 4 gig Resolution Once logged into the SQL MSDE or SQL Express database, the queries below will reduce the size of the database. As with any database, make sure you backup the database before running any queries. The Usernames and Passwords used below are defaults, your UN/PW may differ. To log into SQL MSDE use the following commandline. osql -Usa -P To log into SQL 2005 Express us the following commandline with your servername sqlcmd -Sput_server_name_here\sqlexpress -Usa -Padminadmin Once logged in you'll be prompted with a 1> at which time you'll change the context of the database you'll be truncating information on. For example if your database name is ContinuumDB you would use the following. 1>Use ContinuumDB 2> Go 1>Now put in one of the queries below 2> type in Go to execute /****** Replace 90 with the number of days to maintain in each log ********/ delete from accessevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from activityevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from alarmevent where DATEDIFF(day, timestamp, getdate()) > 90 delete from errorevent where DATEDIFF(day, timestamp, getdate()) > 90 ** To gain back the space after deleting rows SQL Express Right click on Continuumdb>Tasks>Shrink>Database MSDE(osql) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter) dbcc shrinkdatabase ('your_database_name',0) (enter) go (enter)   To truncate from the Full SQL server or SQL Express non command line interface, see Removing unwanted entries from an Alarm log, Access Event log, Error log, and Activity log automatically.

Issue How to properly configure Time Zone and UTC Offset settings in Cyberstations and controllers. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Controllers Cause There are a number of locations for time configuration settings, creating uncertainty as to what needs to be set, and where, to maintain the correct time in all devices. Resolution How to sync controller time with WS time with Server time. Set the correct UTC offset (time zone) in all of the below locations: Confirm Cyberstation(s) PC time zone (UTC offset) and regional settings are correct. [This has no effect on time synchronization but does have an effect on what time alarms and events are written to the database as well as when alarms will be delivered to Cyberstations] Confirm the SQL Server PC time zone (GMT settings) and regional settings are correct. [same as 1 above] In Continuum, the Workstations Device object's Time tab has the correct time zone setting (be aware this is in minutes, ex. GMT+10 = +600 minutes.) In Continuum, the Network folder has a setting for the time zone, this needs to be configured to the time zone the controllers are located. If GMT+10 then this gets set to +600. Note1: To synchronize controller time to Workstations time a program needs to be created in one WS that sets the Date object of the Netcontroller (IP level controller) with the lowest ACCnet ID. This controller will then push any time changes out to all other IP level controllers and down to its subnet controllers (i2’s or b3’s). See Time sync controllers to workstations for details on this. Note2: At 38 minutes past the hour the Netcontroller will push its time down to its subnet (aka Field Bus) controllers. Note3: When time is set in the Netcontroller with a reload of the controller, the UTC settings of the WS doing the reload, and the Network folder the controller is in, are accounted for and the controllers time is set with these UTC settings taken into account. When time is set with a PE program using the WS Date object, this does not take into account the UTC settings of the various locations and just sets the controller Date object to the exact value of the WS Date object. If the controller is in a different time zone than the WS setting its time, then it will now have the wrong time in it. To compensate for this, it is suggested that time offsets must be added to the Time Sync program to accommodate those networks in a different time zone than the WS. Other UTC setting locations and what these settings effect IP level BACnet Device UTC Offset The UTC offset value on the Time tab of the BACnet Device object is only used when the BACnet time synchronization method is being used to set time. This setting then follows the BACnet specification where it needs to be the negative value of the GMT setting. For example, if the BACnet device is in the GMT+10 time zone, then set this offset to -(10*60) = -600. Note4: If using the PE program method, the UTC offset value on the Time tab of the BACnet Device object does not change how time is set in the controllers. However, if the UTC offset value on the Time tab of the BACnet Device object is changed, it will change the current time of the controller to coincide with the new time zone until the time is set again in the controller, or the UTC offset value is removed. UTC offset in controller configuration Time Settings webpage This doesn’t change how the time of the controller is set. It is used to set the time of sent email messages when using the SMTP option on this controller.

Issue There are many issues that can happen at Cyberstation and some methods are needed to troubleshoot. Product Line Andover Continuum Environment Continuum Cyberstation Continuum webClient Server Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There are a number of steps and tools that can be used to troubleshoot Cyberstation Resolution This subject encompasses software and hardware. It isn't a comprehensive list but should offer some methods and tools to help troubleshoot Cyberstation or webClient. Typically errors that are Cyberstation or webClient related will display some sort of an error message on the screen which can be used to diagnose the problem. Isolated or System Wide - Is the issue happening on 1 or multiple Workstations? If so, it could be a system wide issue, but if it's just one workstation then it is isolated to this PC and could be an install, Windows OS, hotfix or hardware issue. Continuum Compatibility Matrix - A number of issues can happen if Continuum Service Packs or hotfixes or Windows Operating System (including Service Packs), Microsoft SQL Server, Internet Browser version and the version of Continuum or webClient do not match the matrix. See document Software and Firmware Compatibility Matrix Version 2.03 Cyberstation Error - Is there an error message that is being displayed. A list of some Cyberstation specific errors can be found by pressing F1 with Cyberstation open, select index, type in Error, select error messages, Cyberstation How do you locate error messages in Cyberstation? Windows Error - Is there an error showing in the Windows event viewer? This step can be very useful when troubleshooting Cyberstation problems from issues installing Cyberstation or SQL to problems happening because of a Windows Operating System issue. Typically there are errors, event ids, and details that occur at the time of an issue that can be used to search the web for a solution. These can also be sent into support for some help analyzing the issue. Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes Windows Service Pack or hotfixes- Were any Windows Service Packs or hotfixes recently applied to this PC that could be affecting this installation? To display all the hotfixes on a PC, see the following MS article: Windows: How to List All of the Windows and Software Updates Applied to a Computer Installed Software- Since the issue started happening has any additional software been installed on the PC. Take a look in Start> Settings> Control Panel> Add/Remove programs(XP) or Programs and Feature (Windows 10) and see what may have been recently installed. Antivirus / Malware -  On some occasions, we have seen Cyberstations or webClient PCs affected by viruses or malware. If an issue is specifically related to one PC and particularly if that PC is exposed to the internet, but doesn't have any Anti-Virus software installed, it could be infected. Updating Anti-Virus definitions and Malware/Spyware programs and running scans is recommended to clean up the PC. Hardware Issues - PCs will break over time from wear and power bumps, etc. Memory, NIC cards and Hard Drives are typically what goes first. *Memory - Many PC manufacturers supply memory diagnostic features in the system bios to detect if a RAM module is bad. This will often show in a certain spot every time in a certain program, not necessarily Cyberstation and can actually indicate that is can't access a memory reference. *Hard drives - drives can crash or certain files can become damaged. Checkdsk and the Windows OS attempts to keep the drive clean, but sometimes reformatting the Hard Drive and reinstalling the Windows OS will be required to correct the issue. If it's a physical issue with this drive then the problem could come back and a new hard drive may be needed. *NIC (Network Interface Cards) - can cause connection issues and affect system performance. Not all NIC cards are created equal and at times integrated NICs(built into the motherboard) can be less robust than a third party NIC card. See the following for extensive troubleshooting advice, but often swapping the card is easier. Advanced network adapter troubleshooting for Windows workstations *Graphics Displays - Some issue are more related to Pinpoint or Video. Check the graphics display and see if the most up to date video driver has been installed. Run any diagnostic that may be supplied by the video card manufacturer or swap out the card. Windows Device Manager - In Windows device manager you may see a black exclamation point on a yellow field which indicates the device is in a problem state. There can be many reasons this can happen and is beyond the scope of this article. See the following MS article for more information. Error codes in Device Manager in Windows System Info and Belarc Advisor - These tools can be used to see what hardware and software are installed on the PC. System info is installed with Windows. Description of Microsoft System Information (Msinfo32.exe) Tool This can be sent into Product Support as a .nfo file and can be brought up with details. This information can be difficult to work with. Belarc Advisor - This is a free tool that can be installed on a PC and will display the information in a very readable browser format. This tool will often find things that may have shown in System Info but was difficult to find. Belarc Advisor Restore Point - Windows XP, Vista and Windows 7 all have the ability to restore the system to a previous place in time by using Windows Restore Point. This is a Windows Operating System function and has some risks associated with it, but can be very useful to get back to especially when the issue is happening on a Stand Alone setup. What is System Restore? If the restore point doesn't work then a reinstall of Cyberstation or the Windows OS could correct the issue. Lastly, a reformat of the hard drive and a complete reinstall of the Windows Operating System and then reinstall Cyberstation or webClient may be needed.

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 How to change the firmware version in a controller. Product Line Andover Continuum Environment All flash-upgradeable controllers: CX9900, CX9940, ACX5720, ACX5740, all i2, b3, and bCX controllers.  Cause Controller firmware needs to be changed. Resolution Locate the firmware version that you need for each controller you want to change. The Continuum firmware files can be downloaded from the Schneider Electric Ecobuilding Exchange. The downloaded files are often a zip file which includes the release notes in PDF format and the flash file (UPD file). Note: You may need to upgrade or downgrade firmware (see also Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum?) Make sure you check the document Andover Continuum Software and Firmware Compatibility Matrix for the appropriate firmware version for your system.   Copy the file to a disk drive accessible to your CyberStation workstation. Edit the controller object in ContinuumExplorer and click on the "Update OS" button. Browse to the file location in step 2 and click "Open". A progress box "Updating Controller OS..." will appear. During this time the controller is reset and not functional.  Once complete, and if successful, you will get  a dialog box indicating that the upload was successful and the controller will return On-Line momentarily. Click OK. Click the refresh button in the controller editor. Once the controller is on-line the version field should indicate the new version. At this point some controllers may need a reload, others will be reloaded from flash memory. This depends on the controller type. For example, the CX9900 has no flash memory and therefore will need to be reloaded. This procedure also applies to upgrading controller options such as adding Xdriver support. In this case a UPD file will be provided by the Repair Dept. In the case of added Xdriver support, after doing the Update OS procedure the version will not change. Look at the controller Options tab after it comes back online following the upgrade. The information here, such as a non-zero entry in the numbers next to the appropriate Xdriver Commport will be changed. The above procedure was based on an IP level controller such as the CX, bCX and ACX II. Infinet and MSTP controllers are done in a similar manner. IOU models are also upgraded similarly via the "Update IOU" button in the IOUModule editor. However, the files are .IOU files instead of .UPD files and the versions are in the fourth pair of characters in the Program ID field.  

Issue Problems installing Continuum Continuum will not install correctly SQL Express will not install correctly Product Line Andover Continuum Environment Continuum Cause Cyberstation fails to install or run correctly Resolution Continuum Cyberstation can normally be installed very quickly (usually less than half an hour) on a normal windows installation that fits within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation, this would include SQL for a stand alone (Single User) installation. The Continuum Cyberstation uses many Windows components and services, and runs many executable files and batch files within its normal operation. We do not have a published list of services that Continuum requires to run since requirements vary depending on the site configuration. We obviously use Active Directory and .NET, RPC, MSMQ, SMNP, and all DCE services. SQL Server Management Studio Express is a free down from Microsoft and is an excellent tool for checking the SQL install Up to v1.94sp1 SQL2005 https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017 v2.0 and beyond SQL2012 https://www.microsoft.com/en-us/download/details.aspx?id=35579 There are a few items that can interfere with the smooth installation or running of a Continuum Cyberstation Ensure the workstation PC is within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for the version being installed, especially Windows service packs and .NET framework versions. Ensure the minimum requirement for the workstation PC, is observed, as stated in the Cyberstation installation guide. Ensure the recommended requirement is observed, if the Cyberstation will be used for video or other more intense operations.  Local administrator accounts are required for some version of installation with passwords set. See How to create a local administrator log on in Windows. Automatic updates. See the individual installation guides, however, it is normally wise or even mandatory (depending on Continuum version) to leave them off, as updates include service packs and .NET framework updates that would take the installation off the Compatibility Matrix and could compromise the installation. There have also been other updates that have caused issues. See 5 below. MSXML6 Update SQL Express install fails on MSXML 6 Firewall & Anti virus issues. These should be disabled during installation. Issues with starting Continuum after new installation (Anti-Virus and Firewalls) Error when starting Continuum 1.9: Cannot find acc video recording service Access denied errors when installing Continuum or Webclient Crash of ACCDataServices on start up or running Continuum Another example of antivirus interfering with Continuum install is getting Microsoft Visual V++ error when opening a pin point graphic, when the install is completed with AV "webRoot" enabled.  SQL2005 Express (1.82SA onwards) When creating the sa password ensure the password is tested in notepad before typing in Database Initialisation, as if the keyboard is not set up correctly, you may be using an illegal character (eg " rather than @, in this case you will need to uninstall SQL, before re-installing via Database Initialisation) Custom Windows Images - Some Windows Images installed on new PCs include modifications that interfere with the Cyberstation installation, always use a clean MS Windows if possible, as this avoid such issues. HP Protect Tools - MFC error on Continuum startup or Continuum won't start on HP PC IT tampered Windows & domains. It is important to install Continuum with local Administrator rights as item 3, above, beware of PCs locked down by IT departments, the installation can be slow and difficult Error 1001, windows event log full. Error 1001 when installing Cyberstation or Webclient Problems with MSMQ (MicroSoft Message Queue) can cause install problems MSMQ errors and Continuum fails to start MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." MSMQ error message: "Appears to be a problem with configuration of system please check to make sure you have MSMQ correctly installed" Trying to install CyberStation 1.9x.  It completes but then pops up 6 errors saying "Access denied" "Access Denied" messages during a CyberStation 1.9x installation Microsoft Update issues see Windows updates and Continuum Continuum Version 1.93 Fails to install. IssueReceive AccDataservice errors on startup. Continuum Version 1.93 Fails to install For Windows 7 installs see Disabling administrator rights messages in Windows 7 OS and above (Also known as UAC / User Account Control) If you see a Continuum install Error -  "Error, unable to open documentation list \misc\doclist.txt" then you are running the incorrect "setup.exe", you should install using the one in the Cyberstation root directory, not the one in the Continuum sub-directory. It has be found that Microsoft "Strong" passwords are required not only for the SQL sa password but also for Andover97 password, see Password requirements for Andover97 SQL Login for details For a v1.82 Stand Alone and beyond, if the install admin user has no password, it has been seen that the tasks (CS_Minute, CS_Distn and CS_hrly) are not always created, see Getting AccDataServices error with AlmUtil.dll error when closing Continuum If a Continuum re-install, on a LAN CyberStation is required (were some part or program has broken) then uninstall Continuum, then re-install. A workstation initialization may be required. Deleting the Continuum directory and clearing out Continuum from the registry may also be required (check for any local held graphics, .mnu files, etc. before deleting the Continuum directory) Seeing "Can not change directory to Continuum" see Cannot change directory to Continuum error during installation of Cyberstation Re-Installing Continuum is sometimes required, for example, an automatic update to the Antivirus software has been seen to stop listviews from working. The only way around this was to uninstall Continuum then re-install it. There are different levels to uninstalling possible, 1.Simple uninstall. 2. Uninstalled followed by removing the Continuum Directory and other .ini files. 3. Uninstalled followed by removing the Continuum Directory and other .ini files, followed by cleaning of the registry.  In a few more recent cases where Controllers will not come online (after testing for other errors) or where persistent MSMQ errors cannot be resolved, a complete re-install of the OS may be required to ensure a "clean" Windows OS is available. Uninstalling some Continuum required programs can cause issues, especially SQL. see Problem uninstalling software. The following method has been seen to work: Stop service, uninstall, delete folders, run CCleaner (or Revo) and clean registry, reboot, run CCleaner (or Revo) and clean registry, reboot, re-install SQL Shared Memory errors seen with 32b systems and v2.0SP1, see "Shared Memory" error on startup of Continuum

Issue General use of the Wireshark program. Product Line Access Expert, Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Ethernet Networks Cause General Information on using WireShark. Resolution Wireshark is an Ethernet packet analysis programme, Which can be downloaded from: Latest version available from Wireshark Locally stored version 1.0.9 Installing Wireshark If necessary, unzip the WireShark executable file to a suitable location on the PC/Laptop you wish the programme to be installed on. Run the executable file and follow the on-screen instructions. Rules for capturing LAN traffic using Wireshark: Do not use a switch or router to connect the LAN capture PC to the network as these will filter important network activity that you will need to see. You will want to capture everything that is passing over the network at the point of concern. Usually, this means tapping into the ethernet at the Controller or controllers, that is having an issue. midBit-Technologies-LLC-10-100 is an example of a device that can be used to easily tap into the network to take the capture. The monitoring PC must see all traffic from the controller's point of view. The monitoring PC can be connected in either two ways: Connected to the network at the controller The customers IT department can mirror all the network traffic from the controllers port to another port the PC can be connected to. If connected to the network at the controllers, the connection must be made through a true ethernet hub. A hub will not selectively filter important network traffic as a switch or a router will do. More information on what a "true ethernet hub" can be found at http://wiki.wireshark.org/HubReference There are however some switches that feature port mirroring, please see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring. If connected to a mirrored port, the port must mirror 100% of the network traffic to and from the controller. No filtering should be done. Once a complete capture file has been obtained it can be filtered after the fact using WireShark or EtherReal. Using Wireshark Run WireShark Start a trace by choosing the "Capture" menu and then select "Interfaces" Choose the appropriate interface. Generally, this can be identified by its IP Address, but if not, then the packets increasing are an indication. Press the "Start" button. The trace will start and will be similar to the following screenshot. After an appropriate time, the trace can be stopped by selecting "Capture" menu and "Stop" To save the capture file, choose "File" menu and "Save As".

Issue How can Continuum be setup to read the 32 bit serial number from a Mifare smart card for use in access control? Product Line Andover Continuum Environment Using iClass serial number readers: R10, R15, R30, R40, RK40 Custom Wiegand, AccessFormat array Custom Format Cause Mifare smart cards that have been provided and programmed by others may not have the keys available to allow a reader to access the data on the card. Without sending the cards away for re-programming how can the card still be used for access control. Resolution The HID iClass readers (R10, R15, R30, R40, RK40) have the ability to read the 32 bit serial number from a Mifare Smart card. These readers will output a single 32 bit Wiegand string representing the card serial number. To use this on Continuum: Create a numeric point called "AccessFormat" and define it as a manual array with 19 entries. Create a Plain English program in the controller to fill up the array with values as per the Mifare Serial Number spreadsheet. In the door configuration select "Custom Format" and ensure one of the 4 site codes is set to 0. Swipe the card at the reader and open a list view of Events, this will show the card number as the serial number from the card. Create a new Person with card type Custom Wiegand, Site code 0 and set the Card number to the serial number as read in the list view. This may be a 9 or 10 digit number. Notes: If using card numbers in Plain English Programs or displaying in Pinpoint Graphics, you will be restricted to using a maximum of 6 digit numbers (maximum card number being 999,999). See Loss of resolution on metering points when the number is 7 digits or longer for details on this restriction. The old style Personnel editor will not allow the entry of site codes of 0. Use Personnel Manager or set attributes in List Views of Personnel.

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

Issue Some Windows OS do not come with Hyperterminal installed. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Vista Windows 7 Cause Hyperterminal was not included in the Operating System software package. Resolution Installing Original XP HyperTerminal Download this .zip file which contains the necessary executable and dynamic link library for running hyperterminal Unzip to local hard drive. Double click the hypertrm.exe to launch hyperterminal See Connecting a serial cable to a Xenta 5/7/9xx controller for proper cable connection and hyperterminal settings if needed. Alternatively, extract the two files from any XP installation and copy them to the new Windows OS. hypertrm.exe default installation is in C:\Program Files\Windows NT hypertrm.dll default installation is in C:\Windows\System32. Alternatively, from a Windows XP CD, both files reside in the i386 directory.