Building Automation Knowledge Base

Issue Do I need an X Driver to send simple ASCII strings to a third party system? Environment Plain English Drivers PE Driver, Raw Mode CX Controllers Netcontroller II bCX ACX Cause Require the limitations of Plain English drivers Resolution It is possible to create a Plain English driver to print ASCII data out of a Comm port. Use the Open, Close and Print keywords to develop your program in a CX or bCX controller, if you go to the "Help, Contents" on Cyberstation Explorer you can enter these keywords and get full details on their use including example programs. You can also read responses from the 3rd party system with the "Read" keyword. The Plain English program would be able to print out any information that can be put into an InfinityString. The characters that a PE Driver cannot handle are the FFh (255) and 0H (null) characters, to use these would require the use of an X Driver or another form of gateway to an open protocol. If you have a first generation controller (CX9900, CX9400 etc) there is a Generic ASCII "X Driver Filter" that can be used to print/ read an ASCII string with no character limitations. If the port is X Driver enabled then download software X-Driver Filter The CHR keyword can be used to send "Non printable characters". The other thing is that a Plain English Driver will be dependent on the controller scan time so it would not be suitable for any protocols that are timing critical and the controller scan time must be kept low. As a general rule of thumb, if you can send the required characters out using Hyperterminal and the system accepts it, then a PE program should be able to send them too.  The attached document is an example of a Plain English driver that was written a while ago to communicate with a Video Recorder over an RS232 link, the principles and techniques used in this example show the use of the above keywords as well as some of the string manipulation keywords. Download it here. This also applies to the ACX57xx controllers but they only have a single half duplex RS485 port which may not be suitable for all applications.

Issue Can the xPBD4 be used with an i2 or b3. Environment xp Expansion Module Cause Is the xPBD4 compatible with an i2 or b3. Resolution No. The following note is from the xP Expansion Datasheet: The xPBA4 and xPBD4 Expansion Modules can only be connected to the bCX1 Controller/Routers and ACX Series Access Controllers. The other xP expansion modules do work with the i2/b3 controllers. See the attached data sheet for more info.

Issue Panel layout. Environment  ERG-UNIV-ENC-1 ERG-UNIV-ENC-2 Cause Need to determine panel layout for a project using the universal enclosures. Resolution From the data sheet... Medium Enclosure: Andover Continuum Power Supply and NetController, and up to two I/O modules or up to six I/O modules or CX 9702 SiteController.   Small Enclosure: Up to three I/O modules or CX 9702 SiteController or NetController (without a Power Supply) or VS-8-4 Video Switch Module. Both units are designed to hold two standard 12 VDC 7AH lead acid batteries (not provided). See the full data sheet here.

Issue Poor or unreliable ground connection of IO modules can cause controller failure, inputs to stop updating and communications to be poor. Environment Netcontroller IO modules Cause Strings of IO modules were installed on each DIN rail in a panel. One IO module per row had directly landed ground wires, but each of the other modules on the row relied on contact between a metal clip on the back of the module and the DIN rail.  Observed an average of two I/O modules per panel with inadequate earth ground (where this clip was not making an electrically sound connection). In some cases, resting a hand on one of the modules caused a wide variance in the grounding quality. Resolution After installing a panel (not just in the panel fabrication shop), measure each IO module's ground terminal to ground. Do not just assume that each IO module is properly grounded  to the DIN rail via the clip on the back. And do not just assume that the DIN rail is properly grounded - some DIN rail is plated to reduce corrosion and this can increase resistance. If there is (or will be) any vibration or moisture, or there are any other concerns that site conditions may negatively effect grounding of the IO modules in the future, consider grounding each IO module's ground terminal via a conductor to ground.   There is a Technical Product Advisory here that will provide further detail on this.

Issue Object level security using SecurityLevel Environment CyberStation Cause Documentation Resolution Click -> Continuum Security Levels explained.

Issue How to have Continuum automatically lock a Windows workstation when the person leaves his/her office. Environment CyberStation Windows 7 Windows XP Cause Documentation Resolution Click here for a procedure to set up a mechanism for programmatically locking a Windows workstation based on the person's current area as obtained from the Continuum physical access control system. 

Issue How to Logon / Logoff Continuum using a button on a Graphic or Menu page. Environment Continuum Cyberstation Cause Want to be able to Logon Continuum with the click of a button from Graphics or Menu page and also bring up the Logon prompt the same way. Resolution ** DISCLAIMER ** This application is not a supported part of Continuum and is provided as-is. 1. Copy the "Logoff.tx_" file in this archive, here, to the Continuum folder (c:\Program Files\Continuum). 2. Rename the .tx_ file extension to .exe. 3. Create hotspots / buttons as below to call the program with the two available command line arguments; 1 will logon, 2 will logoff. Suggested usage: On the Main Continuum Menu page create two buttons, one for logon, one for logoff. (Pinpoint could also be used for Logoff but would not work for Logging back on - Pinpoint closes when the user is logged off.) For the Logon Button:                 Set control to:        Execute                 Open:                     C:\ProgramFiles\Continuum\Logoff.exe                 Arguments:             1                   Button Text:           Logon   For Logoff Button:                 Set control to:        Execute                 Open:                     C:\ProgramFiles\Continuum\Logoff.exe                 Arguments:             2                   Button Text:           Logoff

Issue Getting error cannot create ACWPPServerProxy application on the remote server when trying to use Web Pinpoint. Environment WebClient Cause Configuration issue Resolution Get the web.config file Download and place it in the Webservers. Do not edit this file with Notepad (Use Textpad ot Notepad++, etc.) 64-bit systems directory: C:\Program Files (86)\Continuum\DNWACServerfactory (delete the old one) 32-bit systems directory: C:\Program Files \Continuum\DNWACServerfactory (delete the old one) Reboot the Webserver. Start Continuum and edit any Graphic. Once the graphic is opened, select View / Options and set the Web locations. There shouldn't be any red X's Check the following file: 64 bit systems:.C:\Program Files (86)\Continuum\DNWACServerfactory\ web.config   32 bit systems: C:\Program Files\Continuum\DNWACServerfactory\web.config The server  name should be correct.  It should match you Webservers name. Now test Webclient on the webserver first before any client systems. Make sure you run RegIIS and Caspol.exe  C:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i C:\Windows\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust C:\Windows\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust Please note that the above may be case sensitive.

Issue How do points map from a i2 controller and the xP expansion modules to Infinity SX8000? Environment Using Continuum i2 controllers and xP modules on SX8000 Infinity systems. Cause The I/O channels on expansion modules are different from Infinity to Continuum. Resolution You can add an i2 controller to your Infinet networks on Infinity and it will co-exist with the other Infinity controllers. The controller will be seen as a equivalent infinity controller i.e. a i2850 will be seen as a TCX850. Also you will not be able to use any of the additional features that a i2 controller has like the flash memory or the smart sensor connection. For Expansion modules you could however use the xP modules (not including the xP display) the attached spreadsheet that shows how the i2 controllers I/O channels will be seen by the Infinity Controller. Download the spreadsheet here.  

Issue After receiving the CyberStations Who Is broadcast  via the BCX4040 the third party device responds with an I Am packet.  However, the BCX is not passing the information back to Cyberstation.  Product Line Andover Continuum Environment Cyberstation BACnet Who is I Am 3rd Party Find Bacnet device Learn Cause In the attached mstp capture images, neither of the responses from the Automated Logic device at packets 1713 and 5379 have the necessary information that would cause the bCX or any BACnet router to send the message to another network. 3rd Party device responds with an I Am Looking at the NPDU layer of either message, you’ll notice a destination network (DNET) is not indicated. If you compare these messages with those from the b3 (at packet 1716 or 5382), you’ll see a DNET of 1 indicated, which is why the I-Am’s from the b3 reach Cyber, as Cyber belongs to Network 1. BACnet end devices are expected to dynamically detect the presence of SNET/SADDR information in the NPDU and reply with a message that includes the matching values for the DNET/DADDR. b3 responds with an I Am In the preceding Who-is packets you can see that the network number has been communicated to the third party device Resolution BACnet routers or BACnet Building Controllers do not cache or otherwise correlate requests and responses. BACnet end devices are expected to dynamically detect the presence of SNET/SADDR information in the NPDU and reply with a message that includes the matching values for the DNET/DADDR. The role of the BACnet router is to remove the DNET/DADDR information and add the SNET/SADDR information when they route messages from one network to another.  

Issue There is a need to be able to calculate and estimate the amount of power being consumed by IOU modules and their readers Environment 99xx 9680 IOUs Cause Power supplies have a wattage limit and adding to many modules can cause the bus to become unstable Resolution To estimate the amount of wattage being consumed by IOU modules, please download the following Excel Spreadsheet. Continuum I/O Module Power

Issue Internet Explorer 9 not supported Environment Internet Explorer 9 IE9 IE 9 webClient Continuum webClient Cause Internet Explorer 9 ( IE 9) is not supported in webClient 1.94 Resolution Please click HERE to see attachment for details on uninstalling Internet Explorer 9 This procedure will remove IE 9 and IE 8 will be available on the machine.

Issue "Relock upon Door Closure" option is greyed out and feature is not available.  Environment Continuum Access Control Cause The "Relock upon Door Closure" feature is not implemented at this time.  Resolution For this "Relock upon Door Closure" functionality you will need to use Plain English code. The code located here is a sample of how this can be accomplished.

Issue Showing a list of doors in a web browser using a custom web page in the controller. Environment CX9900 CX9702 CX9680 ACX5720 ACX5740 Cause Documentation Resolution Click here to see sample PE code to show web page that can be accessed from the controller's 'Custom Reports and Services' link.

Issue Controller crashes during reload. Error log shows illegal instruction. 0xbadd0004 0x00002000 0x01802174 0x40102000 0x085be4d8 Reset (illegal instruction) Environment All CX controllers Cause Incompatible XDriver loaded. Continuum controllers can be either first or second generation. The XDriver used must be matched with the controller generation.   First generation controllers are 92xx, 94xx, 99xx Second generation controllers are 9702, 9640, 4xxx, 9680, and 57xx Resolution Load the appropriate XDriver in the controller. If upgrading a controller such as going from a 9200 to a 9680, review the Third Party Interface Data Sheet to locate the re-compiled second generation Xdriver. NOTE: Not all XDrivers have been made available for second generation controllers, if the Xdriver is not available check with the third party vendor to see if a standard ModBus or BACnet plug in/upgrade is available for the device.

Issue Report objects being emailed using the ReportCmdLine.exe application do not get sent properly. The emailed attachment is unable to be opened as a PDF or Web object. When the same report is being saved to file, the resulting file is readable. When the same report is being email from the Report objects Email button, the resulting attached file is readable. Only when the ReportCmdLine.exe program is used to send an email attachment of the report does this fail.  Environment Continuum Cyberstation v1.81 Microsoft Outlook Cause This is a defect in the original Continuum v1.81 Hotfix that this BETA hotfix resolves. Resolution Install this new BETA patch (now included a new Util.dll and Reportviewer.exe files) into your Continuum folder using the below method for both files. Find the patch here. Shut down CyberStation(s) Copy the existing file reportviewer.exe in the Continuum directory to another file so you now have a new file named "copy of reportviewer.exe". Delete the original reportviewer.exe. Copy the new reportviewer.exe file from the hotfix archive to the Continuum directory. Copy the existing file Util.dll in the Continuum directory to another file so you now have a new file named "copy of Util.dll". Delete the original Util.dll. Copy the new Util.dll file from the hotfix archive to the Continuum directory. Restart the CyberStation(s) You should now be able to view the email attachments both in PDF and Web format.  

Issue While PSS does not write PE for partners we do in some instances provide sample PE code for guidance. This article provides sample PE code for optimized Start/Stop routines. Environment CyberStation All CXs All b3s All i2s Cause Complex PE routines may be difficult to implement without sample. Resolution See Self-adaptive Optimized Start and Optimized Stop Routines Sample PE Code.pdf

Issue Upgrading site from Continuum v1.8x to v1.9x. with Elevator Control software. Continuum v1.91 and above now supports the Elevator Floor Module directly from within the Personnel Manager. Information on this new feature and how to implement is required. Environment Continuum Cyberstation v1.91 and above Elevator Control Software Personnel Editor Elevator Floor Module Cause Elevator floor selection is now done through the new Elevator Floor Module selected from a button within the Personnel Manager, thus removing the requirement to use the external Elevator PIM application for floor selection. Resolution The Elevator Floor Module is a free add-on for Elevator Control V2.6x.  It allows you to open the Elevator Floor selection window directly from the Continuum V1.91 (and above) Personnel Manager.  There is now no need to run the external Elevator PIM for Elevator Template or floor assignment.  Another added feature with the new Module is that Personnel objects can now reside in any folder. You can see more information on the features available and how to configure the Module at the link below. Elevator Floor Module Configuration For the Floor Module to work, it does require the Elevator Software to be installed and configured on the Continuum Workstation as well as the Continuum Security Key to be enabled with the Elevator option.

Issue Error when trying to add exceptions to a schedule is seen when trying to "apply" the changes. Example: Personnel Manager Error saving data Communication Error Exception has been thrown by the target of an invocation. The personnel object was created Product Line Andover Continuum Environment Continuum Cause Too many old exceptions in the schedule. Sometimes RPC (Remote Procedure Call) errors happen on Cyberstation following the above error. Resolution Delete the old exceptions. This must be done manually for infinet schedules. 1.94 NOTE: If this issue is happening for 1.94, there is Hotfix for TPA CONT 12 0002.00 Schedule Exception Errors.zip that has been released for this issue. The V1.94 issue is also detailed in Technical bulletin: TPA-BOST-12-0002.00  

Issue Change of Value alarm is configured to alarm when an analog value changes by certain value but does not produce an alarm when the monitored object changes by that amount. Environment Continuum Cyberstation bCX1 b3xxx Cause EventNotification or monitored object has not been configured properly. Resolution There are a number of configuration reasons for these Change of Value alarms to seem like they are not being delivered to the Workstation. Check the Current State tab of the EventEnrollment to see if the ToNormal time is changing when you modify your monitored object. If this time is not updating then the EventNotification or monitored object are not configured properly, check the following: Confirm that the BACnet object type in the monitored object is configured properly. If this numeric is a number then it needs to be set to "AnalogValue". Confirm that a "send to database" has been performed on this controller on the BACnet side to send these points to the BACnet side. See details here on how to create BACnet alarms. If this time is changing then the EventNotification and monitored object are configured properly but the alarm is not being delivered to your Workstation. Check  that one or more of the following is the cause: The Change of Value alarm will generate a ReturnToNormal alarm, confirm that the EventNotification is configured to Send Return to Normal alarms - this option needs to be ticked under "Send". Confirm that the option to  remove the alarm from the active alarm list is configured so that the alarm is not removed as soon as it is delivered. A selection of Returned to Normal or Acknowledged OR Returned to Normal on the Deactivate tab will mean that the alarm is removed from the active alarm list as soon as it is delivered. Select any of the following Deactivate options for the alarms to show up in the alarm list: Acknowledged, Acknowledged AND Returned to Normal, or Acknowledged AFTER Returned to Normal.