Building Automation Knowledge Base

Issue Confused about which file is for the CX9680 Environment Xdriver Cause The two BACnet IP Xdriver files on the Extranet are called: bacnetip120000.xdr BacnetIP_bcx_122002.xdr When loading the first one in a CX9680 the controller reset. Resolution The file bacnetip120000.xdr is for first generation Continuum network controllers like the CX99xx, CX94xx, CX9201. The file BacnetIP_bcx_122002.xdr is for the second generation controllers like the bCX9640, CX9680 (aka NC2) and the ACX57xx. It is NOT just for the bCX controller.

Issue When an object is edited the Apply button becomes selectable, but when selected no changes are saved. Environment Continuum ContinuumDB SQL ContinuumServer Cause Insufficient space on hard drive. Resolution Move database backup files. Truncate log tables. Install automated log table truncation routines. 

Issue The RoamIO2 does not seem to be able to communicate with an ACX5740, why? Environment RoamIO2, RoamIO Cause What must be done to get a RoamIO2 to communicate with an ACX57xx controller? Resolution The ACX57xx must have comm1 configured as Infinet. This is because the RoamIO2 hardware only communicates via the Infinet protocol (when running the InfinetServiceTool software) or BACnet protocol (when running the BACnetServiceTool software). An ACX57xx is not communicating either of these protocols unless comm1 is configured for Infinet.

Issue When upgrading Continuum Cyberstation to a higher version on a webClient machine without uninstalling webClient first, the installation will not be successful. Error 1311, Source file not found, pls verify the file "....\Cyberstation1.94\continuum\webcli~1.cab" existed and can access it. Environment Windows XP SP3 webClient 1.93 Cyberstation 1.94 Cause The webClient was not uninstalled successfully. The Cyberstation install process interprets the installation as an upgrade and tries to find the webClient install file "webcli~.cable." When the file is not found in the Continuum folder, the error is encountered. Resolution Uninstall Webclient and delete Continuum folder from the machine From Windows Control Panel, click "add/remove program" and find  "Continuum" then click. Click "yes" button from the pop-up alarm dialogue window. After uninstallation finished, go to  C:\program files\continuum, and then delete the whole folder. Restart the machine Re-Install Cyberstation

Issue Continuum entries in the windows application events occasionally shows error related to the database connection. A database fault warning state was detected and cleared. This is an indication that the connection to the Continuum database was lost for a moment. "wuaueng.dll (46108) SUS20ClientDataStore: The database engine stopped the instance (0)". "wuaueng.dll (46108) SUS20ClientDataStore: The database engine started a new instance (0)."   Environment CyberStation Windows Event Viewer SQL Server Cause Informational entries in the windows application event viewer frequently refer to Continuum reporting a database fault warning. The warning may or may not be accompanied with other information such as: ClientDataStore: The database engine stopped the instance (0) ClientDataStore: The database engine started a new instance (0) These events can occur in the ordinary operation of the SQL Server environment, or they may be associated with errors. Resolution If a 'stopped' instance warning is immediately followed by a 'restarted' instance warning and not associated with an error then the event took place in the context of ordinary operation of the SQL server and can be ignored. If on the other hand there is an error reported such as ‘The database instance ran out of disk space.’ then corrective action will be required.

Issue Each time an I/O module is commissioned the NetController II goes offline. Environment IO modules NetControllerII CX9680 Cause If there is a problem with the controller configuration it may be possible to commission the IO modules on an empty controller.  The controllers would then have to be reloaded by class or may have to be rebuilt manually. Resolution Access the controllers webpage. Select Clear Database Backup Commit changes to the controller. Do not reload the controller. Commission the IO modules on the empty controller.

Issue If the schedule for a personnel area assignment is in a different network to the door that uses the area it does not work. Environment ACX5740, ACX5720 Access Control Cause Objects can not be passed between different Continuum networks.   Resolution For sites with 2 or more networks, when a schedule is linked to the area assignment of a person, that schedule must reside in the same network as the door that uses the area. It is also good practice to locate schedules within the controller for that door, that way should it go offline the schedule will still operate correctly.

Issue NetController 2 IO Modules not powering up when using third party power supply Environment NetController 2, NC2, NCII, IO Modules Cause When using a third party power supply (ac or dc) for a NC2, the IO modules need to be powered separately Resolution When using a third party power supply (ac or dc) for a NC2, the modules need to be powered separately. The IO modules are only powered via the NC2 connector if the Continuum Power supply is used NOTE This is all as the NC2 documentation.

Issue ROAMIO2 fails to connect to i2 controller when the controller is connected to Infinet.  But it succeeds to connect to the i2 controller when Infinet is disconnected from the controller. Environment Netcontroller - CX9900, CX9940, CX9702 Infinet controller - i2 controllers Cause When the netcontroller (CX9900, CX9940, CX9702)  version is old , the ROAMIO2 does not communicate well with the Infinet with the CX connected. Resolution Upgrade the Netcontroller OS (firmware) to the latest version.

Issue What is required to configure controllers to use the wireless network adaptors? Environment Wireless Infinet CX 9680 (Netcontroller II) bCX 9640 (bCX1-INF) i2xxx controllers Wireless MSTP bCX 4040 (bCX1-BACnet) b3xxx controllers Cause Require more information on how to enable Continuum controller subnet to use wireless communications instead of wired communications. Resolution To setup and enable wireless Infinet or MSTP networks, you will require two things: 1. Firmware There is separate Wireless Firmware that needs to be loaded into the i2xxx and b3xxx controllers to enable wireless communications. The Netcontroller II or bCX1 controller do not have a separate wireless version of the Firmware. FW -> Ecobuildings   2. Wireless Adapters You will need to attach wireless adapters to each controller including the master and change the commport to wireless mode. (Note: bCX or NC2 controllers only; wireless has not been enabled in the ACX57xx controllers at this time.) For further information see the Wireless documentation at the link on ExchangeOnline below. Ecobuildings

Issue How do our field controllers keep their own internal time? ( Clock , Real Time Clock , RTC , Frequency) Product Line Andover Continuum Environment Continuum Controllers Cause Not sure how the local time is kept on the controllers. Resolution Throughout the life of the Infinity and Continuum product line, the method of keeping the time on the controllers has changed. The older controllers (9000,9200,9400 era) used the AC frequency as a pulse, or heartbeat, to keep time. This was calculated at a 60Hz cycle and if there was a dirty power cycle or a different frequency power supply (say 50Hz), the local time on the controller would drift out over time. The newer controllers (anything with a Real Time Clock) use the Real Time Clock and its crystal to keep the time; this is in no way affected by the AC or DC power. On any newer generation controller that has a  battery backup (battery backed RAM), the battery also keeps the Real Time Clock functioning as well as the controller RAM in case of a power failure.

Issue Get ACCDataServices crash during Continuum shut down Environment Continuum WS ( Cyberstation & Webclient ) Cause The most possible scenario of the cause of the issue is when PE programs in the Continuum WS are running for DB backup or truncating events from event tables during shutting down of Continuum. Resolution Modify the PE programs not to run during the period of Continuum shut down.

Issue McQuay third party device on MSTP running at 76.8K baud does not show up under BACnet folder following a 'Find New BACnet Devices' from the root. Environment bCX4040 Cause Looking at the Comm2Count system variable of the bCX reveals the third party device is not actively passing the token on the MSTP field bus. The count does not include the device in question. Resolution One or more of the solutions below. 1. Third party device not able to communicate at the higher baud, change the baud rate on the bCX comm2. 2. Third party device is unable to auto baud and must be manually configured for a given baud rate. Configure the third party device accordingly. 3. Wiring issues in the MSTP field bus.

Issue For various reasons it may be necessary to temporarily stop a schedule from driving its occupancy point, is there an easy way to accomplish this? Environment CyberStation All CXs All i2s All b3s Cause Documentation Resolution If the schedule object is a Continuum schedule... 1. Edit the schedule object 2. Go to the 'Configuration' tab 3. Set the state to disabled. For a BACnet schedule... 1. Edit the schedule object. 2. Go to the 'Current State' tab 3 Check the 'Out of service' box  To return control to the schedule re-enable it/put it back in service.

Issue Why are all/some entries in the 'Active Components' menu grayed out? Product Line Andover Continuum Environment CyberStation Cause The 'Active Components' menu is context sensitive; it only enables entries that are applicable to the selected control. Resolution Display the 'Drawing' toolbar (View\Toolbars\Drawing) Select a shape from the drawing tool bar and draw a shape on the canvas With the shape on the canvas selected pull down the 'Active Components' once again Observe that there are menu entries enabled now, only those menu entries that are applicable to the control on the canvas are enabled.

Issue Cannot create a new Continuum database with Database Initializer. Environment Continuum database Database Initializer SQL Cause Occasionally, when a misconfiguration occurs in Database Initializer during the database creation process, the ContinuumDev.mdf and ContinuumLog.ldf will be created in SQL but the database instance will not be created. The presence of an existing database device will prevent SQL from creating an instance with the same name. Resolution Delete the ContinuumDev.mdf and ContinuumLog.ldf files in the SQL data folder and retry.

Issue CX controller going offline or exhibits intermittent communications problem. When the Infinet bus is disconnected from the controller the problem goes away. Environment All CX controllers that support Infinet field bus. Cause Malfunctioning infinet device disrupts the Infinet bus and brings down parent CX controller. Resolution Follow standard Infinet troubleshooting techniques to identify offending field bus device and remove/replace.

Issue Importing personnel object gives attribute name error. Environment CyberStation Cause Info1 - Info6 attributes were renamed, the export file contains the new attribute names. Resolution During the import process the system expects the original attribute names. Edit the export file and change names back to info1-info6.

Issue How to run a controller program (InfinetProgram) when the controller first starts up? Environment Continuum Controllers Plain English Cause Need to be able to set specific parameters at startup time of the controller. For example, with a VAV controller, you may want to re-calibrate the closed position of a damper by having this done at power up. This will allow just a power cycle of the controller after been serviced locally. Resolution Have a program run at start-up of the controller that resets any required parameters back to default values. To do this, create a Program that sets these values and then configure that Program with a FlowType of 'FallThru' and with AutoStart set to 'True'. This will run the program only once at start-up of the controller.  

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 Reloading ACX2/NC2 produces error when reloading the following system variables AllowedCreds PersRecordCount PIVReaderFormat Environment CyberStation ACX5720 ACX5740 CX9680 Cause The system variables in question (AllowedCreds, PersRecordCount, PIVReaderFormat) only apply to versions 1.1xxxxx and 2.1xxxxx of the ACX2 and NC2 respectively. Resolution Make sure the controller is running the appropriate version of the firmware. If the problem persists even with the correct firmware version then... Export the controller to text file Edit the dump file and remove ALL system variables Delete the controller Import the file to re-create the controller (the system variables will be created when the controller is created) Reload the controller, the errors should not longer appear.