Building Automation Knowledge Base

Issue Objects have become edit locked and can not be unlocked Property unlock, CTRL-U and "Object editlock=false" do not unlock the object. The Plain English Integrated Development Environment may crash Product Line Andover Continuum Environment SQL Server Database Cause The hard disk on the SQL server has no more space Stand Alone database may have reached its limit Resolution Once the hard disk on the SQL server PC is too full, Continuum can no longer write to the SQL database, thus object can become editlocked. Space on the hard disk needs to be released, it is likely that old backups have filled the hard disk up. Backups should be moved to a different hard disk If a Stand Alone install, MSDE (SQL2000) has a 2GB limit (up to v1.81), SQL2005Express has a 4GB limit (v1.82 and after) NOTES The database may go to Status "In recovery" until space is made on the hard disk, this may also cause CyberStations to loose contact with the database. It may note be possible to edit or create new objects when in this mode (database or hard disk full)

Issue SQL Management Studio Express is not installed and ContinuumDB needs to be backed up.   Environment CyberStation Standalone Cause Need to backup a standalone database but have no internet access to download & install SQL Management Studio Express Resolution Open command prompt. Type sqlcmd -SComputername\sqlexpress   where Computername is the name of the computer. Press Enter. You should see this: 1> Type backup database continuumdb to disk = 'mycontinuumdb.bak with init;    Press Enter You should see this: 2> Type go and press Enter You should see something like this: Processed ### pages for database 'continuumdb', file 'ContinuumDev' on file 1. Processed ### pages for database 'continuumdb', file 'ContinuumLog' on file 1. BACKUP DATABASE successfully processed ### pages in ###.# seconds. On a default SQLExpress install (on the C Drive) the file created from the above command (mycontinuumdb.bak) will be created in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup.

Warning Issue Although Continuum 1.94 is installed, when the workstation is edited Version 1.73 is seen on the Details page under Software Revision and Firmware Revision. The Cyberstation startup splash screen shows Continuum 1.94. Continuum 1.94 is shown under Continuum Explore/Help/AboutContinuumExplorer. Environment Cyberstation. Cause The erroneous version number is most likely an artifact of a Continuum upgrade that was done without fully uninstalling the previous version of Cyberstation. Resolution Uninstall Cyberstation from Control > Panel Add Remove Programs. Backup all profiles and graphic pin and background files, then delete the Program Files\Continuum folder. Delete all occurrences of the Andover Controls folder from the registry. HKEY_LOCAL_MACHINE/Software/Andover Controls and HKEY_CURRENT_USER/Software/Andover Controls Reboot the PC and install Cyberstation. Run Continuum Database Initialization and select Workstation to reinitialize the workstation.   .        

Issue The instructions for configuring PE Alarm Functions in Continuum call for the creation of four new keys in the workstation registry under HKEY_LOCAL_MACHINE\Software\Andover Controls\Continuum\Settings. This folder does not exist in the registry of a Windows 7 64-bit PC. Environment Cyberstation PE Alarm Functions Registry Cause On Windows 7 64 bit machines, Continuum no longer writes its registry keys under HKEY_LOCAL_MACHINE\Software\Andover Controls Resolution Write the new registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Andover Controls\Continuum\Settings.

Issue With a 10K Ohm resistor wired across the controller input (at the controller) the supervised input reads trouble with the door switch in either the closed or open position.  Environment UI Supervised Input IO Modules 10K Ohm resistor Cause The input voltage selector switch was set to 5 volts instead of 10 volts. Resolution Changed the voltage selector switch from 5 to 10 volts and power cycled the IO module.

Issue b3 Schedules Environment StruxureWare Building Operation site with b3 controllers Cause What actually takes place within the system to ensure the current weeks schedule is downloaded to the controller periodically and can this be adjusted by the user? The Enterprise Server and Automation Server may not even need weekly downloads of a schedule as they are of course servers, but b3 controllers will most certainly still require some kind of period download as they can only hold one weeks schedule at any one time. Resolution B3 devices hold their entire schedule configuration. All weeks, and all exception schedule events. The entire configuration is of a schedule is written to the device when it is modified by the user. There may be several schedule objects in the b3. As such, there is no periodic download. Note that compared to Continuum which performs a default download every Saturday at midnight and updates the schedule whether needed or not.  

Issue On the extranet site, there are two .zip files (SNMP+V1.0+MIBs.zip and SNMP+v2C+MIBs.zip). What is the difference? Environment SNMP Alarming Cause Not sure which file to use.   Resolution On The Exchange Download Center, there are two .zip files (SNMP MIBs v1.0 and SNMP MIBs v2C). The choice between the above files will likely be dictated by the site IT Department, based on their Network Management System. The V1.0 and V2C is the version of the SNMP protocol and is independent of the Continuum controller model and version.  Here's some background information on the protocol versions: http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol#SNMPv1_.26_SNMPv2c_interoperability  

Issue Continuum presents an error when starting up. "Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client" Environment Continuum Cyberstation Microsoft Outlook Cause When Outlook is installed on the Workstation, Continuum will try to make a connection to Outlook when it starts up. If Outlook has not been configured as the default mail client then it can't make this connection and presents the error. Resolution Either make Outlook the default email client or uninstall from the Workstation. See Microsoft KB here that describes how to set your default email client.

Issue After drag/drop/copying a b3 to many other b3s an InfinityProgram called FiringOrder is listed with the other InfinityPrograms within some of the b3s  Environment 1.94 standalone, b3 VAV controllers Cause Appears something went wrong with the drag/drop/copy. Possibly tried to copy to too many controllers. Resolution ContinuumAnalyzer identified the problem in the InfinityProgram Object Integrity Test and the Clean fixed it up.  

Issue Do i2600 Series controller support expansion modules? Environment i2608 i2624 Cause Documentation Resolution i2600 Series controllers are input only devices (8 or 24) and DO NOT have an expansion port.

Issue Is the Niagara G3 Floating License Repository (FLR) available for purchase? The FLR is a licensed feature that runs as a service in a Niagara station to provide licenses to other Niagara Runtime Environment (NRE) applications. Available licenses are 'leased' by authorized NRE applications at startup and 'returned' when the application shuts down. Environment Niagara G3 (version 3.5 and higher) Cause Field question Resolution The FLR was introduced with version 3.5 and discontinued shortly thereafter by Tridium. It is no longer available for purchase.

Issue Can a soft or hard reboot command be sent to a MNB controller from a Niagara R2 UNC-520? Environment Niagara R2 Cause Avoid the need for using the WorkPlace Commissioning Tool Resolution Any kind of reboot command from a Niagara R2 station, to a MNB controller, is not possible. The WorkPlace Commissioning Tool is required.

Issue Which Modbus driver is required for I/A Series Niagara G3 ENC-520 to support Modbus TCP? Environment I/A Series G3 ENC-520, JACE-645, JACE-6E, JACE-7, JACE-NXT, ENC-SW Cause Select the correct part number to enable the ENC to function as a Modbus TCP Client (Master) or Server (Slave).  Resolution ENC-DRV-MOD-T (ENC 520 acts as Modbus master (client) using Ethernet TCP) ENC-DRV-MOD-R (ENC 520 acts as Modbus server (slave) using Ethernet TCP) using Ethernet TCP master using Ethernet TCP

Issue The SEQROT object in the Network8000 integration in the AS seems to work with constant input values but not reference pointers. Environment AS version 1.3.0 & 1.3.0 SP1 with Network8000 interface Cause After the object has been defined to use constant inputs those input values must be reset to Null before the reference inputs will be used. Resolution The Analog input constant can be returned to Null by highlighting the value it contains and clicking the delete key.  The field will be empty until a save is done.  With a digital input such as the Rotate stages constant simply highlight the value and click the delete key and it will change to Null.

Issue Fail to communicate with Xenta/LonWorks devices under Xenta Server although Xenta Server is online and commissioned. The Neuron ID can't be pinged. Environment Vista Xenta Server Cause The Xenta Server is online and commissioned, but the LonWorks network needs to be commissioned with asterisk symbol on the LonWorks network. Resolution Remember to commission the LonWorks network after the Xenta Server is downloaded in Xbuilder.

Issue Is it a problem in StruxureWare Building Operation to start many trend logs at the same time? Environment StruxureWare Building Operation version 1.3 Cause When starting several trend logs at the same time the Servers will try to read all the logged values at the same moment which is causing a big load on the system. Resolution Starting several trends at the same time should not have a big impact on the rest of the system, and our internal thread management shall ensure that no logs are missed. But it could cause a big load on the field bus and field devices so this is something to consider.    

Issue Supported Version of Windows Server and SQL Server for StruxureWare Reports Server Environment Reports Server Cause Reports Server is only supported on a specific operating systems and SQL Server versions. Resolution SmartStruxure 1.4.1 and below  Windows Environment: Microsoft Windows Server 2008 R2 (64-bit) SQL Software Options Microsoft SQL Server 2008 R2 Express with Advanced Services (64-bit) SP2 (Download Page - Direct link) Microsoft SQL Server 2008 R2 Standard (64-bit) SP2 (Download SP2: Download page - Direct link)   SmartStruxure 1.5 and above  Windows Environment: Microsoft Windows Server 2008 R2 (64-bit) Microsoft Windows Server 2012 (64-bit) Microsoft Windows Server 2012 R2 (64-bit) SQL Software Options Microsoft SQL Server 2008 R2 Express with Advanced Services (64-bit) SP2 (Download Page - Direct link) Microsoft SQL Server 2008 R2 Standard (64-bit) SP2 (Download SP2: Download page - Direct link) Microsoft SQL Server 2012 Express with Advanced Services (64-bit) SP2 (Download page - Direct link) Microsoft SQL Server 2012 Standard (64-bit) SP2 (Download SP2: Download page - Direct link)

Issue A MicroSmart controller is not communicating and the red watchdog timer (WDT) LED is on solid. Environment DMS Cause Possible hardware issue or power issue Resolution Things to try: - Power cycle the controller - Verify it has a good earth ground and 24 Vac - Hardware clear the controller - Replace the line driver and disconnect the communications trunk - If it is a MSC-MPC, remove all modules.  If the WDT LED begins flashing normally, re-connect the modules one at a time until the WDT LED goes solid   On-board hardware issue.  Replace with another controller

Issue Importing a Menta application for a Xenta 301 controller cannot be saved. Environment Xenta 301 importing Save Saving Cause Importing a Menta application for a Xenta 301 controller, and then saving it, works correctly. If the application is modified in some way, requiring a second import, then this import cannot be saved. Resolution This issue has been assigned to defect 22178, which is due to be fixed in release 1.5. Work around. Delete the existing controller object, and then create a new controller object before importing the modified Menta application.

Issue Both errors indicate WorkPlace Tech cannot determine if the vsd file being opened is in the current project. Environment WorkPlace Tech Cause The names of the folders that were brought forward contained an apostrophe, i.e. Vav's, AHU's, etc. Resolution Rename the folders eliminating the apostrophe before bringing the folders\drawings into the new project and these errors will not occur.