Building Automation Knowledge Base

Issue What is the difference between SQL Server 2005 and SQL Express Edition. Environment SQL 2005 Cause Why would I need SQL Server instead of SQL Express. Resolution Limitations for SQL Express Edition are: CPU:  1   CPU RAM:   Maximum 1 Gig. Database Size:  Maximum  4 Gig.

Issue Workstation has had a number of its system variables renamed to names such as FanStatus and HHWV. These objects have also changed their Object Class to BACnet objects such as AnalogueValue.   Environment Continuum BACnet Cyberstation Cause This can occur when the Device Node ID of your Device object (Workstation) is the same as a BACnet devices BACnet ID. Resolution The best way to resolve this is to "cut out the bad bits" by deleting the BACnet device from the BACnet tree, the Workstation Device object, and Workstation Folder.   Perform the following: Backup the ContinuumDB. Backup any WS programs or other objects in the WS that you will require later. Export these to dump files. Export any graphics that reference your BACnet Devices.  Shut down all other Cyberstations. Delete the BACnet Device that is conflicting from the BACnet side of Continuum.  Delete the Workstation Device object and Workstation Folder. Shut down Continuum and then re-initialize the Workstation object into the database using a unique number for its BACnet ID (this is the Device Node ID). This number can be between 1 and 4194302, but must be unique in your entire BACnet network. Log-on and re-find the BACnet controller and import anything that you previously backed up in steps 2 and 3.

Issue Any objects created get placed in the folder Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Selecting the checkbox for put object in folder and specifying a folder causing all objects to default to this folder.  Resolution By default, this checkbox isn't selected. To go back to normal functionality, uncheck the checkbox to 'put object in folder' and remove the specified folder. When this mistake is made, not one single point can be named the same in similar controllers that are under that NetController or BCX.  This can affect drag and drop also.

Issue Can I set up a door in Continuum which allows either a card validation OR a general code validation? Environment AC-1 family HID RK40 Reader/Keypad Cause Customer wants employees to access a gated area using their badges and the garbage company to enter a general code to get to the dumpster (they don't want to have to issue the garbage company a badge.)  Can the door object be set up to do this? Resolution No, the access validation is coded as an "AND" not an "OR". What is meant by this is that when a door object is configured with the checkboxes for Validate Site, Validate Card and Validate General Code, the person must present a valid card and enter a general code - it is not either/or. The easiest workaround for this is to add another AC-1,  another reader and create a second door with a different configuration. Different groups of people will be instructed to use different readers.     

Issue What is the part number for the female connectors to plug in the right side of a Netcontroller or I/O Module Environment Netcontroller CX9900, CX9940 Netcontroller II, all I/O Modules Cause The part number for the I/O Module connectors is not listed on the I/O Systems reference guide. Resolution The part number for the Female (Right hand) connectors for I/O Modules and Netcontrollers is: P/N - 01-0010-840 bag of 20 connectors

Issue Is the b4920 still available for new purchase and is it still supported? Environment b4920 Cause Is the b4920 still available for new purchase and is it still supported? Resolution Yes, the b4920 is still available as of this article publication (October 2011). However, the same functionality can be obtained less expensively by purchasing a bCX1 with 127 node support AND a b3920. In addition you get the added reliability of distributing the combined functionality across two different devices. If a b4920 goes down you lose control of your on-board IO and communication to your Infinet or MS/TP bus. If you lose one of two devices the other will continue to operate. On the other hand, the b4920 takes up less physical space than the two devices.

Issue Even though Windows Server 2008 R2 is exclusively a 64-bit operating system, 32-bit applications are supported by enabling the WoW64 optional feature. NOTE: These are general instructions for utilizing the WoW64 function. Not all Schneider Software will be able to run in an emulated environment. If uncertain, please check with Product Support Services to ensure proper installation. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows Server 2008 R2 WoW64 feature. All 64bit OS Cause If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. WoW64 option in in undesired state. Resolution If the WoW64 feature is not enabled and you try to run a 32-bit application, the application will fail to execute. The WoW64 execution layer is an optional component that is installed by default on R2 releases. You can save resources by removing the feature if you are not going to be running 32-bit applications on your Server Core install. Install the WoW64 Execution Layer using the following command: dism /online /enable-feature /featurename:ServerCore-WOW64 If your solution has a .NET 32-bit dependency, then also invoke the following sequence: dism /online /enable-feature /featurename:NetFx2-ServerCore dism /online /enable-feature /featurename:NetFx2-ServerCore-WOW64 Note: In Windows Server 2008 R2 RC1, WoW64 is enabled by default. If you don't want WoW64 enabled, just disable the feature as follows:  dism /online /disable-feature /featurename:ServerCore-WOW64

Issue My customer does not want to have to make changes to schedules in different controllers when changing door unlock times or personnel access times to areas. How can this be solved? Product Line Andover Continuum Environment CyberStation ACX5720, ACX5740 NetController Refresh Cause How to consolidate door unlock schedules in different controllers. Resolution Multiple solutions: 1. The easiest and recommended method is to create the schedule in one controller and simply enter the numeric being set by that schedule in all the applicable door objects, whether in that controller or other controllers.  When you look at the point in the door editor, if it's in another controller it will include the path to the point. This "remote" point becomes part of the import/export (aka IE) table in the controller in which the door is programmed. Even if communication to the remote controller is lost, the import/export table in the door controller will hold the value obtained from the last successful IE table update.  The IE system is very efficient - when the point in the "host" controller changes, that controller knows to update the other controllers to which it exports the point. There is only one downside to this - for a digital point, like a schedule numeric, which  does not change often, if the controller looking for the change misses it, the value there will not be updated. To eliminate this problem always include in the controller with the schedule numeric(s) a program that "refreshes" the value of the schedule numeric(s). A simple fallthru program triggered by minute works great. The syntax is: ++++++++++++ Set ScheduleNumeric1Name refresh to true Set ScheduleNumeric2Name refresh to true  etc  ++++++++++++ 2. Another solution is more complicated but will also work. Set up a schedule and schedule numeric point in one controller. We'll call this the schedule host controller. Then set up a schedule numeric point and program in all the other applicable door controllers that synchronizes (mirrors) the local numeric point to the host controller point. Make sure you use a Line E in the program and alarm if the program becomes, or keeps trying to become disabled.  Also, for the "next guy" who is trying to understand the system, you may want to enter, in the description field of the local flags, what is setting the flags, ie, the program name. 

Issue Following a clean upgrade from Continuum 1.74 to 1.93, all ACX78x controllers show their No Server LED illuminated.  Environment ACX780 ACX781 Cause The SystemStatus system variable value is No Database. The AccessServer system variable on the ACX78x controller is not set to the ACCID of the primary access server workstation. Resolution Set the value of SystemStatus to Normal. An ACX78x controller must have it's AccessServer system variable set to 0 or to it's own ACCID.  While setting it to any other value, including the value of a workstations ACCID will cause the No Server LED to illuminate. 

Issue Customer would like to eliminate using a relay on a digital input by monitoring for 24V directly.  Environment i2 / b3 terminal unit controllers Cause Customer would like to eliminate using a relay on a digital input by monitoring for 24V directly.  Resolution The input protection is rated for "24 VAC or 24 VDC temporarily on any single channel, +/- 1000V transients". Beyond a temporary 24V on an input will likely cause all the inputs on the controller to read incorrectly and prolonged exposure will likely cause permanent damage to the input circuitry on the board. A 24V relay with a contact wired to the input must be used.   

Issue Can not get xPBA4 / xPBD4 to operate on a b3 controller Environment xPBA4 xPBD4 b3 / i2 controllers xP Modules Cause When connecting a xPB module to an i2 or b3 module the CPU light does not flash Resolution The xPB modules are only supported on the master level controllers. They can be plugged into a ACX57xx,  a bCX1-CR 9640 or 4040 But not the bCX1 4000 router only or any of the field controllers.   The i2 and b3 controllers with expansion ports will only support the Input only or Output only modules. Maximum of  2 xP modules on any controller (plus an xP Display if required).

Issue Changing an object attribute value (i.e. InfinityOutput state) results in error: An error was detected while attempting to set an attribute in a remote Infinity object: Infinity error duplicate item name. Environment All CXs All i2s All B3s Cause An object with the same name as the one being edited exists in the database. Resolution Rename the object in question. From the Continuum Explorer, right click the item Click on 'Rename'. Modify the name and alias to make it unique. For example, change CondensatePump1 to CondensatePump_1 References to the name (PE programs) will automatically pick up the new name as they refer to the object by handle id. Another possible solution is to reload the controller to sync up the controller's DB with the SQL DB.

Issue A particular turnstile requires a one second pulse, thus the door is configured with a one second strike time, turnstile works fine but getting intermittent forced entry alarms when person takes more than a second to go thru. Environment CyberStation ACX5740 ACX5720 CX9680 CX9900 AC1 AC1Plus Cause Continuum generates forced entry if door switch opens after the door strike time has expired. Resolution In the door editor, go to the 'Channels' tab and enter a value for ForcedEntryDelay. For example: Entering a value of 3 suppresses door forced enter for 3 seconds following valid access (or Request to exit) at the door.

Issue What is the procedure on transferring Continuum from one PC to another PC?   Environment Cyberstation SQL Cause Workstation hardware must be replaced. Resolution Collect information from the existing machine Backup the Continuum Database Collect all IP address, DNS server and WINS server IP information from the existing workstation. Determine if the workstation was a member of a network domain and record the domain name.  Run Continuum Database Initialization on the existing machine. Select Workstation. Record the following information. Workstation Name Folder Name Device Node ID Network ID Data Source Name Database Name User Login ID Server Name. Verify that you have the correct database User Password. Start Continuum and run PinPoint. From the View menu select Options Record the folder path indicated under Graphics (Pin Files):. Record the folder path indicated under Image:. Record the folder path indicated under Background:.  Install CyberStation on the new machine Before removing the existing machine from the network, start the new Workstation without connecting it to the network. Log on to the PC using an the Local Administrator password. Configure the IPaddress, DNS server and WINS server IP address collected from the existing machine. Disable all Virus protection software. Turn off all FireWalls (Windows 7 has three firewalls). On Windows 7 machines disable Windows Defender. On Windows 7 machines shut off SPS Software Protection Services. Install Cyberstation on the new Workstation PC Shut down the PC. Note: Do not run Continuum Database Initialization at this point. Swap the workstations Shutdown the existing workstation and remove it from the network. Connect the new workstation to the network Start the computer. Log on to the computer using an Administrator level user account. If the existing workstation was connected to a network domain, join the network domain. Verify that you have full network connectivity by pinging known ethernet addresses. Update the Continuum Database. Run Continuum Database Initialization. Select Workstation. Enter the information under Workstation using the information collected on the existing machine and apply changes. Launch Continuum CyberStation and verify that Cyberstation is working properly. Run PinPoint From the View Menu select Options Enter the pinpoint file path location collected from the existing workstation. Select the Checkbutton and verify that a failure notice (a red "X") does not appear beside any item. Apply changes. Verify that all Continuum functions are operating as expected.

Issue Andover97 would not create, but the database did create Environment Continuum Windows Server 2008 R2 Windows SQL 2008 R2 Cause Permissions were somehow restricting the Andover97 user from being created Resolution The dbo was set to sa as seen in Enterprise Management Studio under the database > Security > users There may be a number of ways to correct this: Fix the reason why the dbo cannot be created and recreate the db. Run a query to change the dbowner New Query> sp_changedbowner 'Andover97'

Issue I reloaded a netcontroller in the Eastern Time Zone from a PC whose time was set to Pacific time.  Now all the controllers under this Continuum Network have their time set to Pacific time, not local time. Environment BCX NC CX ACX Cause Reloaded a controller from a workstation that was configured for a different time zone. Resolution When a controller is reloaded from a Cyberstation, the Cyberstation sets the controller time to the local time that configured in the Cyberstation PC. Once the date and time has been set, the controller broadcasts it's date and time to all of the Infinity network controllers on the same Continuum network.  These controllers in turn set their own time to the time that they received via the broadcast.

Issue Event Viewer in some workstation are displaying duplicate events. Swiping a valid card at a door results in the Valid Access event showing up twice in some Event Viewers. Environment CyberStation Cause Duplicate subscription entries in the Access Event subscription table of the primary/secondary access server. Resolution Close all Access Event Viewer. Reboot Primary/Secondary access server

Issue Performing an automatic learn or manually commissioning i2/b3 device results in the error "Unknown model number" ACCTrace shows a model number zero Product Line Andover Continuum Environment CyberStation CX/bCX I2/B3 Cause This error can be caused by communication issues. Resolution Verify field bus is properly terminated if required. Follow standard Infinet/MSTP troubleshooting techniques to solve any communication problems inducing the unknown model error.

Issue Drop down fields are no longer showing the drop down menu or any fields to select in Personnel Manager Environment Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There is a limitation set for the number of entries and if this is exceeded they will no longer show. Resolution By default the number of drop down entries is set to a maximum number of entries of 1000. This is usually an ample number of these types of fields, but if more are needed then do the following: Find the file PersonnelManagerCtrl.dll.config in C:\program files\Continuum\Common Edit this file in a text editor and find the entry called GridComboMaxEntries="1000" Restart Cyberstation for this setting to take affect, repeat for each Cyberstation. Caution: This is not an unlimited number and can affect system performance, increase this in small increments i.e. 10-25.

Issue PE program in i28xx controller controls the VAV with TriState Triac output, and the Triac output gets damaged randomly. Environment i2 controller ( i28xx , i28xx-V ) with Triac output. Cause The output channel can get damaged / burned when Triac output value is changed to +ON from -ON ( or to -ON from +ON ) without setting the output value to OFF before the change. Resolution Check the VAV control PE program and make sure the program sets the Tri-state Triac output value to OFF before changing it to the opposite value.