Label: andover continuum - Building Automation Knowledge Base

Issue Cameras have learned in successfully but live video shows as black or the Video Administrator shows the preview as black. Product Line Andover Continuum, Pelco Environment Continuum Endura Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause Live video is showing black because of a configuration issue. Resolution There can be a number of reasons why live video is showing as black in Continuum. Here are some steps to correct or troubleshoot this: Time between devices is not synced. Verify that the controller(InfinintySystemVariable Date), Cyberstation(DateTime Date), and the Endura system(SM) time are all synced. Video Driver or Card. To allow for Sarix cameras in 1.92 changes were made that could cause a standard VGA driver to not display video. Update the standard driver or change the video card. (Test with a different PC which uses a different card) Multicast traffic. Check that the switches on the LAN are broadcasting traffic using multicast. Run the Sherlock utility which is a free codec utility to determine the codec on the Cyberstation and send the results to Product Support. It can be found at the following web site: http://www.free-codecs.com/Sherlock_The_Codec_Detective_download.htm Ensure that the cameras were renamed from the default name in Endura (defaults to camera, but it's actually a null). Ensure that each camera has its own unique non-zero input/channel number. Both of these two items can cause the Continuum camera learn to not be successful and cause issue when trying to access video. Video.log files. Configure the video.log files per How to create a log file for troubleshooting video integration issues in Continuum. Send these files to Product Support for analysis.

Issue Where can I find datasheets, install guides and other documentation on the HID SmartID, iClass, HID Proximity and Indala Proximity cards and readers? Product Line Andover Continuum, Field Devices, TAC INET Environment Electronic Access Control cards and readers for Continuum and I/Net products. Cause Additional product information from HID may be required that is not available on Schneider Electric's own websites. Resolution Schneider Electric supply a subset of the full HID range of cards and readers and these are detailed in the Electronic Access Control Catalogue or see How to determine the part number for the card format required for part number information. For HID product information this can be directly downloaded from the HID Global website. This contains  datasheets, installation guides, application notes, feature lists, brochures and other documentation. HID also have a "Knowledge Center" website that allows you to search for product information and help: HID Knowledge Base. Information on the specific ranges can be obtained from the following links: SmartID: SmartID Cards iClass: iClass Readers iClass SE Readers iClass Cards HID Prox: HID Proximity Readers HID Proximity Cards Indala Prox: Indala Proximity Readers Indala Proximity Cards

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 1. Cyberstation PC Windows Application Event Logs showing SQL errors about being unable to allocate space for each of the event tables. Similar to the below errors. Could not allocate space for object 'dbo.AlarmEvent'.'PK_AlarmEvent' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Could not allocate space for object 'dbo.ExtendedLogReservation'.'IDX_EXTENDEDLOGRESERVATION' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 2. Controllers are online but unable to modify existing objects or create new ones. In addition; all events were not being logged to the database. This was seen by reviewing the AlarmEvent, ActivityEvent, AccessEvent, AlarmEvent, and ExtendedLog tables not having any new events being recorded at all. reviewing the distribution properties after performing tasks in Continuum showed no entries at all. Normally, user events initiated from the Workstation are shown in the distribution properties window as they occur. Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Cause 1. One of the Database files is set to not grow with Autogrowth set to none. This stops any new data from being able to be entered into the database. One example of this is when the ContinuumDev file was modified by the end-user to inhibit its growth by changing this setting to none. Check all of the following databases files (both the DEV and LOG file) to ensure that they are all set to either autogrowth or to an adequate restricted value so that they are able to write new entries. ContinuumDB MSDB TempDB   2. The disk where the database resides does not have enough available disk space. Resolution 1. Change this database file growth setting to "by 10MB, unrestricted growth" or to an adequate restricted value. Use SQL Server Management Studio Express, see Move / Backup / Restore a database on a Single User SQL2005 Express system on where to get this if it is not already installed on your SQL Server. It is highly recommended to backup the ContinuumDB before attempting any changes to the database, steps on how to do this are in the above article. Start up SQL Server Management Studio, or in my example, Management Studio Express. Log in with your SQL SA password or windows administrator. Expand the server tree, expand the Databases tree. Right-click on ContinuumDB and select "Properties" from the menu; this will show the Database Properties window. Select the Files tab on the RH side of this window and you are now where you need to be to check the Autogrowth setting.   2. If the problem is due to disk out of space your options are; a) Make room on the disk, b) Shrink the ContinuumDB,  c) Install a larger disk in the machine.

Issue What is the process for converting a Continuum Single User system to a Continuum LAN system. Product Line Andover Continuum Environment Continuum CyberStation ContinuumDB SQL Cause Site wants to upgrade from Continuum Single User system to a Continuum LAN System. Resolution PRELIMINARY WORK Order Continuum Key Upgrades from all Continuum CyberStation workstations and WebClient Servers. Coordinate with customers IT department Order all TCP/IP node addresses Coordinate the purchase and installation of all software Order all necessary domain accounts Make sure all domain accounts have sufficient permissions to support the installed systems. PREPARE THE NEW CONTINUUM DATABASE ON SQL SERVER Set up your server and install SQL Server 2005 or 2008. SQL must be configured with the proper collation sequence.  (See CyberStation SQL collation) SQL must allow Name Pipes (See After installing Continuum 1.93 LAN, failure to initialize a new database) Install CyberStation on a service Laptop or PC . Disable all virus protection software Disable all spyware software Disable all firewall software. Install Continuum CyberStation Run Database Initialization on service laptop Create new Continuum database..  NOTE: The new database should be given a name that differs from the existing database. Create the service Laptop workstation with a unique Device ID and Network ID. Launch Continuum Logon and verify that Continuum appears to be running normally. MOVE FILES FROM EXISTING SU WORKSTATION TO THE SQL 2008 SERVER Backup PinFiles on original stand alone Cyberstation and move them to New Graphics Files folder on the new database server. Backup Background image files on original stand alone Cyberstation and move them to the background image files folder under New Graphics Files on the new database server. Backup the existing database and move it to the backup folder under SQL on the new Database server. Restore backup to Continuum database in SQL on the new database server.. Shut down all the Cyberstation workstations that are attached to the old database. Change DB Owner Run query on new Continuum database Enter the text SP_ChangeDBOwner Andover97 Execute this query.   Query should return Success. Run Database initialization on the service CyberStation and update the new SQL 2008 Continuum database. Launch CyberStation on the service laptop and verify that the system is fully functional. Shut down service laptop. CONNECT EXISTING WORKSTION TO THE NEW DATABASE SERVER Startup Existing CyberStation PC Launch Database Initialization Under Server, Update the new Continuum database with the same information entered via the service laptop..  Under Workstation update the server information and apply. Launch Continuum. Configure Graphic File Location From Start Programs Continuum, run Pinpoint Under the View menu select Options. Enter the path on the new Continuum database server for the Graphic (Pin Files) Enter the path on the new Continuum database server for the Image files Enter the path on the new Continuum database server for the Background files Select Check and verify that no errors appear (Red X) Ideally uninstall SQL Express or MSDE or at least stop the service from running. Delete the Windows Scheduled tasks: CS_Distn, CS_Hrly, CS_ Minute as these are now performed by Jobs on the SQL server. Test all Continuum functionality. Setup a scheduled automatic db backup routine in SQL. Setup a scheduled trend log truncation routine in SQL.

Issue Having blown the power fuse of an i2/b3 controller, what is its part number? 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 2A Rating: i2/b3867, i2/b3850 series. (If you purchase via the US, this fuse is currently available in iPortal with part number: 01-2180-004) 3A Rating: bCX1, i2/b3810 series, i2/b3800 series, i2/b3600 series. (If you purchase via the US, this fuse is currently available in iPortal with part number: 01-2180-009) 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.  CX9702 (115 VA) Main Power Fuse 250 VAC 1.5Amp Outputs have 125 VAC 3.5Amp replaceable Inputs/Outputs are surface mount non-replaceable For i2/b3814 outputs see What is the part number of the i2814's output fuse?

Issue Installation cable requirements Product Line Andover Continuum Environment Continuum Cause Need to specify a cable type for a site Resolution Installation cables have to be chosen taking in to account the local regulations and legislation, the installation environment and the electrical requirements. The Continuum specifications give the electrical requirements. For this reason actual cable types, makes or Belden numbers can not be stated, only as helpful guidance as a cable that may meet the electrical requirements only. BACNET MSTP - See What cable type should be used for BACnet MS/TP communications?. INFINET - See What cable type should be used for Continuum Infinet bus communications. CARD READER - See the manufacturers requirements for the cables, also Maximum Cable Length Between ACX and Card reader. ANALOGUE and DIGITAL INPUTS - See the relevant Continuum specification eg. I/O Modules. See Andover Continuum IO System Reference (especially note screening and grounding requirements) I/O MODULE (RS-485 & LON) - See the relevant Continuum specification eg. I/O Modules See Andover Continuum IO System Reference For ETHERNET, LON, MODBUS RTU, OTHER THIRD PARTY BUS/NETWORK - See the relevant external documents

Issue Getting DCOM errors when trying to access WebClient and need to determine which of the various permissions have not been set properly. Product Line Andover Continuum Environment WebClient IIS Cause DCOM permissions have not been set properly. Resolution Open EventViewer, go to System Events, and note the DistributedCOM error. Open the error and find the CLSID that it is referring to. In the DCOM Config, look through all of the DCOM objects and find the one with the matching CLSID. Make sure that it has the correct permissions according the WebClient installation document. If this does not resolve the problem, you can also consult WebClient most common installation problems for further troubleshooting steps.

Issue BACnet bCX schedules cannot be edited without an error. Product Line Andover Continuum Environment Continuun bCX4040 Schedule Firmare v4.500082 Cause Following an upgrade to firmware v4.500082 the  Schedule end date year 2038 now enforced and schedule cannot be modified if the end (effective) date is beyond this Resolution For all schedules newly created or otherwise, the end (effective) date needs to be set to 2038 or earlier see Script Programs in Continuum compared to StruxureWare Building Operation and using floats (32 bits) and 64 bit numbers If the date is set after 2038 then an error is seen when trying to edit the schedule "An error code was returned from a BACnet operation, but the reason could not be determined."   Creating a new schedule with a date > 2038 can also give the error: " Error setting attribute 'DeviceID' An error code was returned from s BACnet operation , but the reason could not be determined " Defect was corrected in v4.500083

Issue Without knowing the Device ID / Device Instance these devices cannot add to the MSTP network in the AS or ES. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment Automation Server Enterprise Server BACnet SE7000 Cause Only the MAC ID / Com Address is shown in the display but not the Device ID / Device Instance. Resolution SE7200x Models Default Device ID is set to: 72000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7200F5045B controller with a MAC address of 41 is connected to a network, its default Device Name will be SE7200F5x45B-41 and its default Device ID will be 72041. SE73xxx Models Default Device ID is set to: 73000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7300C5045B controller with a MAC address of 63 is connected to a network, its default Device Name will be SE7300C5x45B-63 and its default Device ID will be 73063. Click here for the Integration Manual. Please refer to the SE7300 series BACnet controller does not come online in StruxureWare Building Operation if SE7300 controller does not come online.

Issue You get an error, "Unable to load the .Net control for this page." when trying to open a schedule in WebClient. Product Line Andover Continuum Environment webClient Cause The problem is that the .Net zone permissions are not set on the browser machines. Resolution Depending on the revision of the WebClient the procedure for correcting this on the browsing machines is different. If you are running WebClient version 1.73 or below then refer to the WebClient installation guide on setting the .Net zone permissions. If you are running WebClient version 1.74 or higher, which uses .Net 2.0, the procedure is different. Below is the procedure that will need to be performed on the browser machines at the command prompt to set the .Net Zone Permissions for .Net 2.0. The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success You should then be able to open the .Net 2.0 editors on your web.client browser machine. In some cases adding the webclient IIS PC to the trusted sites in the browser is needed Internet Explorer> Internet Options> Security> Click Trusted Sites> Click Sites Type in http://your server name/webclient and click Add (i.e your server name is specific to your install) Deselect the checkbox for 'Require server verification (https:) for all sites in this zone Click Ok, Ok Close explorer and access webclient schedules Note: Every browser PC that will be accessing schedules needs to have the caspol commands run on it. Download a batch file that can be run on each PC (Rename the .txt file to .bat and run at a DOS prompt  C:\> caspolwebclient.bat)   Note: When using 1.94 SP1 check the application pools .net version selected Name .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic 4.0 Classic .NET AppPool 2.0 Default AppPool  2.0 WebClient  4.0 Note: If .net framework 4.5.x has recently been installed on browser PCs, see Webclient Cannot open .net editor with .NET Framework - 'There was an error trying to create the .NET control for this page'.

Issue Unable to successfully install Continuum keyless license software. Product Line Andover Continuum Environment Continuum Keyless Soft License Hasp Key Utility Sentinal HASP License Manager Cause Various causes. Resolution The following articles address issues with the Continuum Keyless license software. Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped Web based email should not be used to deliver Keyless Licensing information files (c2v) or activation files (v2c) How to determine the Continuum version, features and the Hasp license ID on a Keyless Continuum License Hasp Key Utility will not activate keyless license Version Error Getting Id. -- Key Id Not Found Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped

Issue Every so often one or two programs on the Continuum workstation stop working. Editing the program results in: A Cached Program cannot be opened while it is being written. Product Line Andover Continuum Environment CyberStation WebClient Continuum Programs Cause CyberStation was not installed properly. Too many demands are being placed on the workstation. Resolution If the problem results from a problem with the installation of Continuum Cyberstation, refer to Problems installing Continuum. Once Continuum has been properly installed, the problem may result from placing to many demands on the Continuum workstation.  Some questions that should be asked are... How many programs are being run on the Cyberstation concurrently. The default setting for Run on any workstation when a workstation program in created is false. This property should be checked for all workstation programs whether they must be run from another workstation or not. This setting can be found in the Program properties editor. An a cached program cannot be opened while it is being written error may occurring when a report program is writing to disk. Verify that the Cyberstation PC conforms to the Continuum Compatibility Matrix for the Continuum version. How many PE programs are running on this workstation, how complex are these programs and are high level commands such as: Rotate, Run, Shell, OpenFile, OpenList, GetName, GetObject being used frequently. How many report programs are running concurrently.  Is the report workstation 100% dedicated to running reports and nothing else; no alarm reporting, no schedules, no extended log downloading, no Access server functions? Is the workstation hardware and operating system sufficient for the work CyberStation is expected to do. Managing these demands may involve sharing the reporting load over several CyberStations and/or adjusting the timing of processor intensive programs so that the workstation is executing fewer tasks at any given time.  In some cases program performance may be impaired due to insufficient memory allocation. See Getting a Smart Heap error when starting Cyberstation or not all processes start and Cyber doesn't open.

Issue Invalid user name or password dialog when logging into webclient with acc that works in Continuum Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows 2003 Windows 2008 Cause Activex control didn't download or an update to .Net requires a re-register of .Net to IIS Resolution This happens when attempting to login to webclient when there are higher security restrictions on Internet Explorer so files that need to get installed on the client machine get blocked. A. Add the webclient server as a Trusted site in Internet Explorer on each client machine as follows: Open Internet Explorer and select> Tools> Internet Options> Security> Click on Trusted Sites and Click the Sites button Deselect "Require server verification (https) for all sites in this zone Add the webclient server name Ex. http://Servername (This typically populates automatically.) B. Also, change the default security settings to medium-low as follows: Open Internet Explorer and select> Tools> Internet Options> Security>Click on Trusted Sites and Click the Custom level button In the "Reset to" drop down, select Medium-Low and then Click The Reset button Click Yes to the "Are you sure you want to change the settings for this zone?" In the Settings list, manually enable "Download unsigned ActiveX controls Click OK, Click Yes to "Are you sure you want to change the settings for this zone?" Click Ok and Ok again C. Run the aspnet_regiis.exe -i command from DOS to re-register .Net with IIS From DOS> CD\ Windows\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe –i Once these steps are completed, enter the URL for webclient again, the appropriate activeX controls will install and the login will work normally. If this still doesn't work and you get a message that "Internet Explorer is currently running without add-ons" then take a look at the following Microsoft articles.   https://social.technet.microsoft.com/Forums/ie/en-US/53a3b82c-e61a-4576-8d80-91e204d4b1e9/internet-explorer-is-currently-running-with-addons-disabled?forum=itprovistaie Also see Internet Explorer gets "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" when logon to the Webclient server. This article is similar, but mentions changing the compatibility view in Internet Explorer.

Issue The network administrator requires that the SQL Andover97 password be changed every three months.  How will this affect the Continuum System? Is it necessary to do a Database Initialization each time the password is changed? Product Line Andover Continuum Environment Andover97 SQL Database Initialization Cause Once the Andover97 password has been changed, the workstations will lose their connection with their access to the database until the workstation (not the database) can be initialized with the new password. This will be indicated by a Database Fault error at the workstations.  Resolution The proper way to change to transition to the new password is to: Shut down all cyberstations. Change the Andover97 password in SQL. Launch Continuum Database Initialization. Select Workstation and enter the new password on the Database page, then select OK. Relaunch all cyberstations.  Once the password is changed, it is only necessary to do perform a workstation initialization (not a database initialization), but this must be done on each workstation.   Refer also to the following article that discusses how Continuum uses the sa password: When is the SQL System Admin (sa) password required?

Issue BACnet bCX MSTP network loses communication when a b-Link is added or removed Product Line Andover Continuum Environment MSTP b3 bCX4040  b-Link Cause The bCX MSTP circuitry is slightly different to the b-Link  MSTP circuitry , thus under some circumstances, other faults on the MSTP network can cause communication to change, when the network is connected via a b-Link Resolution If an MSTP network is installed correctly, then it will operate correctly at all speeds up to 76.8k (assuming all devices operated up to this speed) If the MSTP network is not stable up to 76.8k, or adding or removing a b-Link causing a loss of communication, then it is likely there is some fault on the network. (adding or removing the end of line termination resistors, is also a useful fault finding option) The bCX MSTP components are slightly different to the b-Link MSTP components, thus under some circumstances, other faults on the MSTP network can cause communication to be lost, when the network is connected via a b-Link Example This has been seen when third party variable speed drives (VSDs) were connected to a bCX MSTP network (these unit had switchable termination resistors that by default were in circuit) The communication was ok at a low speed (19200) connected directly to a bCX, but when the network was put on the secondary side of a b-Link, the communication failed. Once the termination resistors were switched out of circuit, the communication via the b-Link was fine. In the example above the VSDs were by ABB Related: How to change the Baud Rate of a field bus (Infinet or Bacnet MSTP) when there is an Infilink or B-link on the network

Issue Using the keypad on the stat to set the comm address may result in duplicate Device Instance IDs on a BACnet network. Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconics Cause Find New BACnet Device does not result in new Viconics stat added to the system. This is due to the default assignment ID scheme used by Viconics. It is resulting in a duplicate Device ID on the BACnet network. Resolution By default, the Device Instance ID (called the Device Node ID in Continuum) is generated using the first two digits of the model of the thermostat + the comm (MAC) address assigned to the stat. Example: For a VT7200C5000 thermostats with MAC address 115, the default Device Instance would be 72115. The problem is that when installing the same model stats on multiple MSTP networks on the same BACnet system, this scheme can easily result in duplicate Device Instance IDs. The resolution is to change the duplicates or use a scheme to assign unique IDs manually to all the stats on a system. Any number between 1 and 4194303 (between 1 and 3FFFFF in Hex) is accepted by the thermostat. One scheme would be to use the BACnet Network ID and append the MAC address to it. Since each BACnet Network ID must be unique across the entire system, and the MAC address on each BACnet Network must be unique, this assures the combination is unique across the system. For example, if you have a bCX with an MSTP bus on comm2 that has a BACnet Network ID - Comm2 of 2765 and a stat with a MAC address of 9, assign it the Device Instance ID 2765009. A BACnet Explorer that provides write access to the Device Instance ID is required to change the default Device Instance ID. See Changing the BACnet device instance of the SE7000 series room controllers for a link to the Viconics VT7000 BACnet Configurator utility. For additional support on the above utility contact Viconics Support at 1-800-563-5660.

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue Right clicking the controller and selecting "Distribute Personnel" results in NO distribution There is no error Product Line Andover Continuum Environment CyberStation Cause Corrupted Personnel Distribution table in SQL ContinuumDB Resolution Truncate table PersonnelDistribution and re-populate it, then distribute personnel once again. WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. In SQL Management Studio execute the following query. truncate table PersonnelDistribution Once the table is truncated it must be re-populated by one of the following methods... If the total number of personnel objects is reasonably small (in the hundreds) launch Continuum and bring a list view of all the personnel objects, select all then right click and perform a 'Send to controller' OR In SQL Management Studio Invoke the stored SQL procedure that initializes the PersonnelDistribution table using the query dt_DIST_ In it_Personnel_Dist_Table IMPORTANT: Truncating the PersonnelDistribution table will remove all pending personnel distribution including personnel deletions; controllers could potentially continue to allow access to doors for the deleted personnel until reloaded. Conversely, removing a pending personnel distribution could potentially cause a person to be denied access at a door until a distribution is performed to the controller.

Issue What are the bCX and b3 COV subscription limits? Product Line Andover Continuum Environment CyberStation bCX4040 bCX4920 b3 devices Cause Confusion on the limits for COV subscription in the Continuum BACnet devices. Resolution The b3 controllers are restricted to 32 devices, which means they can simultaneously establish  COV CLIENTsubscriptions with up to 32 different devices (Andover Continuum or third-party). The bCX1 and the b4920 permit COV CLIENT relationships with up to 255 devices. These limits are device limits and NOT point limits, so if a bCX has established COV subscriptions with 500 points on device X, it can still set up multiple COV subscriptions with up to 254 other BACnet devices. IMPORTANT- See Limit of how many devices a Bacnet controller can know about (Known devices). This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to as a COV SERVER. For instance if a particular controller had a global point like OAT that 50 other controllers wanted and subscribed to this particular controller for that COV, 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 stated regarding this example however. 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.

Issue Does Port Based Network Access Control Ethernet 802.1x apply to Continuum controllers? Product Line Andover Continuum Environment Continuum Ethernet Controllers Cyberstation Cause A question that may be asked by Customers IT Departments Resolution No, the 802.1x protocol is not applicable to controllers, it is a Port based Network Access Control (PBNAC) that is used by Routers and computers. It is related to the Operating system user accounts and policies so is above and outside the scope of Continuum. Not all devices support 802.1X authentication. Examples include some network printers, Ethernet-based electronics like environmental sensors, cameras, and wireless phones. For those devices to be used in a protected network environment, alternative mechanisms must be provided to authenticate them. One option would be to disable 802.1X on that port, but that leaves that port unprotected and open for abuse. Another, slightly more reliable option is to use the MAB option. When MAB is configured on a port, that port will first try to check if the connected device is 802.1X compliant, and if no reaction is received from the connected device, it will try to authenticate with the AAA server using the connected device's MAC address as username and password. The network administrator then must make provisions on the RADIUS server to authenticate those MAC-addresses, either by adding them as regular users, or implementing additional logic to resolve them in a network inventory database. Many managed Ethernet switches offer options for this. Network Security is an available option add on for IP level controllers. Please refer to IPSEC and Network Security on Controllers for more information. Another potential option would be to secure the controllers on a separate VLAN.