Building Automation Knowledge Base

Issue ASP.Net is not showing as a user to select in dcomcnfg list configuring webclient on XP Environment Windows XP ASP.NET Cause This is usually caused because .Net was installed prior to IIS. Resolution Run the aspnet_Regiis.exe -i to re-register the .Net framework with IIS C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i Go back into dcomcnfg and asp.net will now be available. This normally does not require a reboot or restart of IIS

Issue How do you get a list of previous operator history on a specific point from the active alarm view? Environment CyberStation Cause A report will need to be attached to a graphic to see a point's operator text history from the active alarm view. Resolution Create a report for this point to get the operator text Source Tab Data Source: AlarmEvent Report Type: Alarms-for-an-event-object-with-alarm-enrollment Type: Text Filter Tab Path: select the controller the point is in Member Object: Select the point you need Time Interval or Log Filter for the desired range   Setup a graphic page with a button to launch the report In the properties of the Active Button Action: Open Object Object: This is the path to the report you created in step 1.   Setup the point on alarm tab to open the graphic In the point editor that you want the operator history from, select the Graphic field by setting the path to graphic that contains the button for the report from step 2.   When the alarm is triggered in the active alarm view, click on the alarm then the Pinpoint button in the tool bar. This will launch the graphic with the button for the report you created.   Click on the button to launch the report which will contain the operator history for that point. Notes: For multiple points, the same graphic can be launched each time, but separate reports will need to be created for each point and a different button to launch those reports.

Issue Adding a new Netcontroller II (CX 9680) or a new ACX II(ACX 57xx) to an existing system creates problems if the versions are not compatible Environment Netcontroller II (CX 9680) ACX II (ACX 57xx) Cyberstation Cause Current Production of Netcontroller II and ACX II as of 12/1/08 have versions 2.1 and 1.1 on these products respectively. These versions are only compatible with Cyberstation V1.82 or greater.  Resolution If you have a system that is lower than Cyberstation V1.82 you will need to downgrade these controllers to V2.0 and V1.0 respectively. The flash files are available on the Exchange Extranet as is the complete version compatibility chart.

Issue Serial Commport Settings when using Roam IO/2 Environment RoamIO/2 Cause Serial commport settings Resolution The serial commport settings used to connect to the Roam IO/2 tool are listed below. Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None When using the Roam IO/2 with a Serial Cable, please make sure cable uses the following pinout assignments. Pin Signal 2 RXD (Received Data) 3 TXD (Transmitted Data) 5 GND (Ground) NOTE: In the field we've seen some success when using USB to Serial converters, but not all devices will work. Using Serial 9 pin to 9 pin with the above configurations is the preferred method for Serial connection.

Issue How do I use the Corporate 1000 card format on sites with a mixture of CX9900 and CX9680 controllers? Environment CX9900 CX9680 Corporate 1000 card format Cause You cannot use the card type of Corporate 1000 directly in a system that has access controllers other that Netcontroller II and ACX II's on it Resolution The problem here is that the CX9900 does not directly support the Corporate 1000 card type. The only way to do it on the CX9900 is to use a custom format which means the card type on the personnel record is also set to Custom Format. Setting up the AccessFormat on the CX9900 is standard but when trying to use this format on the CX9680 you will get an error. The reason for this is because in order to implement the Corporate 1000 card type on the CX9680 we had to create a custom format for it behind the scenes since the AC-1's could not directly support this new card type. In order to create this as a Custom Format on the CX9680 use the special numeric AccessFormat2 and set it up the same as you did in the CX9900.

Issue CyberStation stops sending Alarm Emails Environment Continuum CyberStation Cause There are spaces or special character in EventNotification names, which cause the emailing of alarms to stop. Resolution In order to send emails from Alarms you must make sure your EventNotification names do not have any spaces or special characters in them.

Issue How to install hotfixes that replace executable files. Environment Continuum Cyberstation Cause No longer need the existing executable file and want to replace with the hotfix file. Resolution The correct way to install a hotfix that replaces an executable file is to either delete the original file before installing the hotfix or to do the below. In Windows Explorer drag and drop copy the original file so you end up with a file called Copy of xxxxx.exe Delete the original file through Windows Explorer. Then extract the hotfix file into the Continuum directory through Windows Explorer.

Issue BACnet Programs Disable on a Reload This is an issue that will be addressed, but in the meantime an explanation of how this happens and a workaround is provided below. Environment Infinity Program in a Continuum Bacnet controller Cause How this happens: Create an Infinity Program in a Continuum Bacnet controller and then right click on the folder directory located under the controller you just created it under on the Infinity side. Now make sure there are two columns in the listview named State. You will most likely have to add one or both of these columns and make one of the columns source LIVE and the others source Database Notice when you run the listview both State columns will reflect Enabled for your running program. Now, perform a find new bacnet devices if you haven't already and then perform a send to database on the controller you just created the Infinity Program under. At this point go back and either run or refresh your listview we ran earlier and notice the Infinity Programs State attribute is set to disabled in the database view. At this point if you reload your controller in the Infinity side it will disable the program. Resolution Workaround on how to avoid this issue After a newly created program has been sent to the database on the Bacnet side, immediately run the listview we created earlier and Highlight either all or only the programs that are set to disable for the State attribute where the source is set to Database. Once you have selected the rows of the programs you want to set to enable, select the Edit menu item in the listview. Now select set attributes.. and in the drop down select State for the name and enter Enabled for the value and select OK. This will allow the program's to be reloaded without being disabled.  Most sites will never see this issue, since most will load up their controllers and back up the flash on the controller before performing a find new bacnet devices and send to DB on the bacnet side After controllers repower or reset the programs are just loaded back from flash. But the sites that reload their controllers will see the reload and programs disable issue. But like any reloading, you should always check your programs and alarms before leaving the site.

Issue Web Pinpoint displays different animation file(s) while Cyberstation's pinpoint displays correct animation files. Environment Cyberstation graphics Cause This issue happens when you create pinpoint graphics with different animation controls using the same animation file names. Although the files that are named the same are from different folders, Web pinpoint will not distinguish one file from the other. Resolution In order to provide faster response to Remote PC's WebPinpoint graphic, Continuum WebClient server caches animation bitmap files in a subfolder (..\Temp\Animation) under the graphic folder. As the file name is the unique key in the cache folder, it is required to use unique names for each animation bitmap file if the files contain a different animation control on a graphic. For example, first graphic displays a Fan animation with 4 bitmap files named as FAN1, FAN2, FAN3, FAN4 from below folder; C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN1.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN2.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN3.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup1\FAN4.bmp And the second graphic displays a Fan animation with 4 bitmap files named as FAN1, FAN2, FAN3, FAN4 from below folder; C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN1.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN2.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN3.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN4.bmp It is required to change the file names for the second graphic to be unique as below; C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN5.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN6.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN7.bmp C:\...\NewGraphicsFiles\ImageLibrary\Animation\FanGroup2\FAN8.bmp

Issue Problem with Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters The Controller was unable to poll all of the meters installed on the field bus. Environment Continuum controller being used to poll EMon Class 3000 MODBUS RTU Meters Cause When connecting multiple Class 3000 meters to a field bus, ONLY the last Class 3000 meter in the field bus string should have the biasing resistor pack installed. Having multiple termination resistors will load the bus down. Resolution All other biasing resistors should be removed from J17 on meters attached to the field bus. If there is still a problem Change the E-Mon "key2000" to the RS232 protocol. Using the E-Mon Repeater will provide a stronger RS-485 signal to drive their devices. Put the X-Driver on an RS-232 port of the controller.

Issue UI-4 Expansion module will not work with i2 controller. Points cannot be controlled. Environment UI-4 Expansion modules i2 Controller Cause The firmware of the controller is less than what is required. The compatibility matrix indicates that to use the ui-4 expansion module that the firmware must be at version 3.3x. Resolution Uprev the firmware to version 3.3x. Read through Technical Bulletin #1361 to ensure that the bootloader flash is at the correct version. 

Issue Error 5295  or invalid attribute when applying installing an xdriver Environment xdriver Cause Clicking apply prior to installing the driver will present the 5295 error. Resolution One of the following should resolve this: Make sure that you click "Apply" prior to checking the driver .  Do not map a drive to the server, place the driver on a local Cyber and do not place any spaces in the path. Ensure that the correct driver is being used.  Set the commport to xdriver, install the driver then apply. If you hit apply before you install the driver you will get the 5295 error

Issue Installation of a key on SQL server is not required Environment Continuum SQL Server Cause   Do I need a Continuum security key on my server? Resolution Installation of a key on SQL server is not required. For each Continuum workstation that accesses the database located on the server you will need a key for each Continuum workstation.

Issue This typically happens after upgrading Continuum on a workstation that uses add-on reporting. When attempting to run the reports this error pops up. Environment Continuum Environment with reporting requirements Cause ODBC settings altered on the upgrade.   Note: No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the “Reset_Password.bat” batch file to re-enter the default Continuum DB password.   Note: No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the “Reset_Password.bat” batch file to re-enter the default Continuum DB password. Resolution   The password needs to be re-entered. No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the C:\Program Files\Continuum_Reports\Reset_Password.bat batch file to re-enter the default Continuum DB password. (i.e. Andover97)

Issue 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." Environment Continuum loaded on a Microsoft Operating System computer Cause MSMQ has become corrupt on this PC. Resolution Continuum cannot be installed on XP HOME(XP Professional only) Verify that the msmq service is started Go to Add/Remove programs > Add/Remove Windows Components does not give the option of installing Message Queuing. Go to a DOS Prompt and change your directory to C:\Program Files\Continuum\Install (cd \Program Files\Continuum\Install) Run the batch file Runafterreboot.bat (This will reinstall the Continuum version of MSMQ. NOTE: Most recent versions of CyberStation RunAfterReboot.bat has been renamed InstallMSMQ.bat Run the batch file and re-boot the machine then run Continuum ** In some cases Windows Add/Remove programs may not completely remove MSMQ and a utility like Revo Uninstaller may be helpful in getting a clean uninstall, so that a reinstall is successful.

Issue Installation question on XP module Environment Cause Installation question on XP module Resolution Yes. Modules can be connected to the bottom of the controller with the built-in expansion port connector or they may be connected remotely via a 3-foot (1 m) or 10-foot (3m) ribbon cable. A total of 10 feet of cable may be used for all Expansion Modules. Mounting and securing of the xP modules is provided through four mounting holes in the base plate.

Issue Error when starting Continuum 1.9: Cannot find acc video recording service. Environment Windows XP SP3 Continuum Cyberstation Cause As with many software installations, installing with anti-virus running will block some registrations and registry entries. Resolution Install Continuum with admin privileges Turn off anti-virus software Stop any firewalls during Continuum installation

Issue Description of how the Bacnet TimeSync works Environment Windows OS XP-Vista versions Cause Description of how the Bacnet TimeSync works Resolution The Bacnet TimeSync that is available on the Time tab in a device editor will only send out a Bacnet UTC TimeSync message to the Bacnet IP controllers that are in the list. This is not a automatic function, but is available to use when integrating 3rd party controllers into our system.

Issue A Continuum database setup for IE. version 1.81 will only support Continuum software version 1.81. Environment Continuum all versions Cause Attempting to use different versions of the Continuum software on a Continuum database Resolution Using Continuum software version IE. 1.9 would not be able to access a database setup for ie... older Continuum version 1.81. This is true for all versions of Continuum. The Continuum software and database must be of the same version.

Issue An error is received on Continuum startup on videoLaunch Method 'There is an installation configuration problem, and this application is unavailable...constructor error' not found. Environment Windows XP SP3 Windows Server 2003 Continuum 1.91 Webclient 1.91 Cause Some PCs come with .net 3.5 pre-installed. If Continuum 1.91 is installed the installation will complete, but then the method, constructor error is received. The compatibility matrix indicates that we require .net 3.5 SP1.  Resolution Install .net 3.5 SP1 and attempt to start Continuum. If the same error pops up then do the following: Remove continuum from Windows Add/Remove programs from Windows Control Panel Reboot the PC Install 3.5 SP1 by running donetfx35.exe (This is on the service release CD in the NetFramewrok3.5 folder) It contains SP1. Reinstall Continuum This error could also occur if 1.90 is being used and .net 3.5 SP1 is installed