Building Automation Knowledge Base

Issue Vulnerability affecting certain versions of OpenSSL. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment OpenSSL Cause Software vulnerability Resolution Information and Customer Statement located at the following link on the community: Schneider Electric Security Statement Regarding the Heartbleed Vulnerability. A corporate statement on this can also be found here: Schneider_Electric_Heartbleed_Customer_Statement_APR_15_2014.pdf.

Issue Information on the features that Video Monitor supports and details on how to configure it on a Continuum Workstation. Product Line Andover Continuum Environment Continuum v1.90 and above. Cause There does not seem to be a specific manual for Video Monitor. Resolution What Is Video Monitor? Video Monitor is CyberStation's powerful video-surveillance tool. Video Monitor, available in CyberStation Version 1.9 and higher, allows you to view live and recorded video images from cameras assigned to doors or points that trigger alarm events. It allows you to monitor doors, immediately capture video images from doors, unlock a door, monitor door status, monitor a person's access to doors, and get alarm information as soon as it happens. You customize the way Video Monitor operates using its powerful configuration tool, Video Administrator. Using Video Administrator, you can attach up to 16 cameras to a door or point. Video Monitor is launched when an event associated with the door or point triggers an alarm. Another video surveillance monitoring tool, VideoLayout, is also available for video matrix-frame viewing. The system may be configured to use either Video Monitor or Video Layouts as your primary video interface to alarms. Also see reference to supported features in the Feature Blast for v1.90 when Video Monitor was first added to Continuum. Configuration There is a large amount of information in the Continuum on-line help files that discuss how to configure Video Monitor in detail. See the Continuum online help contents and search for "Video Monitor."   Note: The Video Monitor option must be enabled on the Continuum Security Key to able to set this up and use it. This comes standard in v1.90 and above and can be enabled on your Key if it is not already.

Issue CyberStation program shows status running but current line is blank and elapsed timers are all zero. Environment CyberStation Cause Documentation Resolution Click HERE to see more information on the functionality of Cyberstation programs that are configured to run on any Workstation.

Issue How to have visibility into what a controller sees in its list of peer controllers and Cyberstations following a tech. Product Line Andover Continuum Environment All CX controllers Cause Documentation Resolution If controller is 9900 you can perform a "dump controller" from Hyper Terminal and see the list of peer controllers and CyberStations the controller has been taught. For Second Generation Continuum controllers that do not have a terminal interface you can put a program in the controller to get information about the list. (You can use the program in the 9900 as well.) Click HERE to see a sample PE program. IMPORTANT UPDATE: If the site has more than just a few (3-5) controllers comment out the line in the program that gets the controller names. Also, comment out the line that gets the security flag if there are first generation (9900, 9640) controllers involved.

Issue A method to create many objects with alarm links using CSV import files. Environment Continuum Cyberstation Cause A requirement was presented where many Inputs and Numerics needed to be created with attached alarm links. A quick method to create these similar objects was investigated. Resolution The CSV file was broken down into the minimum attributes that were required to create a numeric with an active alarm link. Attached is a copy of the CSV file that was used and a screencap showing the results. Follow the steps below to take the Workstation offline, import the CSV file, then send the changes to the controller. 0. Set the Workstation to offline. 1. Import the CSV file "alarmlinkexp" into the acx1 controller by right clicking on the controller and selecting "import into...". Note the success result in the distribution window. 2. set the Workstation to online. Refresh the continuumexplorer view, right-click on the new point and select "send to controller". Note in the distribution window that this succeeded without any errors. 3. The value of the object is set to "NotSet", set this to off, apply, then set to "On". 4. Note that the alarm is triggered and comes in to the alarm bar.   CSV Import file structure InfinityNumeric Name,Alias,DeviceId,Format,AlarmLink1,AlarmEnable test2,test2,net1\acx1,###$,Root\testAlarmEnroll,1

Issue How to create a set of manual logs to show the state changes of a digital point with time stamps. Environment CyberStation Any CX Any i2s Cause Documentation Resolution How to create a report for a digital input that shows the input change of state with a time stamp.pdf

Issue At times it is necessary to replace the battery. Environment BCX Cause  A procedure is needed to replace the battery. Resolution To download the PDF for the procedure to replace the BCX battery, click the following link: Battery Replacement Procedure.pdf

Issue In Physical Access Control lingo, the term Edge controller typically refers to a device that is installed at the door (or in close proximity to the door) and that has all of the components needed to fully control the door with only and IP connection running back for communications to the front end system. Typically Edge access controllers are PoE so that there is no need to provide a separate power feed to the device, they also provide power to all the components that comprise the door control (door lock, REX etc) Environment CyberStation CX9702 Cause Documentation Resolution Continuum does not have a physical access controller that can be considered an Edge access controller. The Continuum access controller that come closest is the CX9702, although it is NOT a PoE controller. Click HERE to see the specs of the CX9702.

Issue The bCX1 Series Technical Reference Manual shows part number 01-2100-299 as lightning protection for Continuum. The cut sheet on iPortal does not specify which model PC642C this is.   Environment Continuum Cause Details on iPortal do not specify which specific model of the PC642 series is supplied with part number 01-2100-299. Resolution The part number 01-2100-299 on iPortal (here) corresponds with the 15V model of that lightning arrestor. This also comes with the base, Emerson part numbers below. PN PC642C 015  Leaded    PN PCB1B BASE Leaded The PDF for the Edco PC642 Series is here.  

Issue Have lost disc to install RoamIO software for the version 1.0 RoamIO Environment Windows XP Continuum RoamIO 1.0 Cause Lost CD or CD broken for RoamIO  Resolution Below is the software / Drivers and install Guide for the RoamIO version 1.0 RoamIO User Guide.pdf RoamIO V1.0 Laptop.zip RoamIO V1.0 PPC.zip RoamIO V1.0 Driver.zip The latest RoamIO2 versions of the software can always be downloaded from The Exchange Download Center.

Issue Need to connect to an old CX / CMX via hyperterminal but don't know the pin out for the old style CX and CMX cable with  9 way to 25 way D type connectors Environment Continuum Windows Hyperterminal Cause Need to connect to an old CX / CMX via hyperterminal but don't know the pin out for the old style CX and CMX cable with 9 way to 25 way D type connectors Resolution Please see attached .pdf of wiring diagram for pin connections from 9 way to 25 way D type  

Issue Not able to find information on the DO-20, DIO-20, or DM-20 IOU modules. Environment DM-20 DIO-20 DO-20 Relay Cause Unable to find documentation. Resolution Below are documents that have information on the DM-20 IOU module, DO-20 board, and DIO-20 Eclipse board. DO-20 -> Here.  DIO-20 Eclipse Module Datasheet -> Here. Continuum I/O Modules Datasheet Continuum I/O Installation Guide Continuum I/O System Reference (start pg.80) DIO-20 Installation Guide   Note: The Eclipse product line is now discontinued, but the DIO-20 is available for the DM-20. The part number is 01-9000-DIO20.

Issue At times it's necessary to only display an alarm at certain times of the day based on a schedule. Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause An input alarm cannot be directly assigned to a schedule, another method is needed to evaluate when to send the alarm. Resolution Click here to download instructions

Issue When was the AC256 product discontinued? Environment AC256 Cause Discontinuation notices only seem to go back to 2007, at which time the AC256 had been discontinued for quite some time. Unable to find any reference to this products discontinuation. Resolution The AC256 was discontinued in 1998. A reference to this can be found in the Andover Controls Network News from February 1998. On page 2 on the right hand column, there is reference to discontinued products as of May 1, 1998. You find the bulletin here.

Issue A Siemens  power meter with a Modbus TCP/IP interface will not allow setting of the Device ID - only the IP parameters. Continuum Modbus TCP/IP Xdriver Remote Device Status Point (aka Comms Point] does not work if the Device ID is set to 0.   Environment Modbus TCP/IP Xdriver Cause Continuum Xdriver Modbus TCP/IP Remote Device Status Point does not work if the Device ID is set to 0.   Resolution Set the Device ID = 1 when configuring the Modbus TCP/IP Xdriver Comms Point For more information refer to page 12 of the Modbus TCP/IP Xdriver User Guide linked here.

Issue Created new Alarm Enrollment, attach to point and put point in alarm but no alarm is received and the points alarm value does not show the point is going in alarm. No problem when using an existing Alarm Enrollment created in the past when the total number of Alarm Enrollment objects was much less. Environment CyberStation CX9900 CX9640 CX9702 CX9680 ACX5720 ACX5740 Cause Controller's handle id limit on Alarm Enrollment objects has been exceeded. Resolution Click here to download this article as a PDF: Continuum Alarm Enrollment Handle ID Limits Continuum Alarm Enrollment Handle Ids Limit. (Note the information presented here applies only to non BACnet alarms) In Continuum there is a limit on the number of Alarm Enrollment objects that can be sent to the controller, the limit is 4000. Unlike the BACnet alarms, the Continuum alarm enrollments are meant to be re-usable, the system was designed for the Alarm Enrollment to be reused hence the limit, when the system is used as designed is very unlikely if not impossible to exceed the 4000 Alarm Enrollment objects limit. There have been cases where this limit has been exceeded due to site requirements that do not conform to the Continuum design, further more as of version 1.94 Continuum does not provided any feedback when the limit is exceeded, the alarm simply won’t work since the controller does not accept the alarm enrollment objects sent by the CyberStation. Guidelines to avoid exceeding the alarm enrollment handle id limit. Re-use, re-use, re-use. The Continuum system was designed for the Alarm Enrollments to be reused. If for some reason the number of alarm enrollment object is approaching the limit, do not delete Alarm Enrollment objects, if you have an alarm enrollment that is no longer needed rename it and re-purpose it instead of deleting it and creating a new one, the reason for this is that the handle ids once assigned are never re-assigned, so if you delete an alarm enrollment its handle id is lost forever. How to clean up if the limit is ever exceeded. If there are any Alarm Enrollment objects with handle ids out of range in the database they should be deleted to avoid confusion but before they are deleted all links to the enrollments have to be identified and the links removed. To find any links to alarm enrollment objects with id out of range run the following query against the ContinuumDB Select * from EventEnroll where AlarmRefLo > 562041735 If you get any results look at the uiName column, the uiName will consist of the point’s number and the AlarmEnrollment’s name separated by a period. Example: Num1.TempTooHigh Now From the Continuum explorer, find the point named ‘Num1’ that has a link to ‘TempTooHigh’ and remove the link. After all the links have been removed run the following query to find all the Alarm Enrollment objects with handle ids out of range. Select * from AlarmEnroll where ObjectIdLo > 562041735 Note the name in the uiName column, from the Continuum explorer delete the AlarmEnrollment objects.

Issue Can a BS5308 part 1 type 1, 2 pair individually screened cable be used for M-Bus communications? Environment M-Bus Communication Cables Cause A BS5308 part 1 type 1 cable was installed for Modbus communications, but it was then found that the communications were M-Bus Resolution The correct cable to use for M-Bus is J-Y(ST)Y.  These indoor telephone cables transmit analogue or digital signals; Aluminium-laminated plastic foil static screen with tin-plated drain wire minimises the interference of high frequency, electromagnetic field;TP structure minimises crosstalk. For the datasheet please click HERE. The BS5308 part 1 type 1 cable can be used, and the chart below shows the calculations used to establish this. For the cable datasheet, please click HERE. For the Excel spreadsheet please click HERE.

Issue Do extended logs have accurate entries for the spring and fall time change periods?   Environment CyberStation, all Continuum controllers, extended logs, controller logs. Cause What happens to extended log data during time changes? Resolution When the clocks are turned back, log data in the controllers will not be updated for the time interval of the change and therefore that data will not be collected by the extended logs. When the clocks are turned forward, log data in the controllers is logged twice for the time interval of the change and therefore that data is collected twice by the extended logs.   This occurs due to the fact that each log entry in the controller does not consist of a value and a timestamp. The timestamp we see in a report is calculated by the time of the last log entry (LastLogTime) in conjunction with the configured logging interval (LogIntervalSecs). This mathematical calculation saves memory in the controllers. Extended logging is the mechanism most sites use to store, and report on data that is in excess of the amount of data stored in a controller. The extended log engine automatically collects the controller log data before it is overwritten. An added benefit of using extended logging is that the data can be easily backed up via several strategies such as database backups and/or running extended log archiving applications. In the controllers, not only is the memory limited, but the data is stored in volatile RAM, so extended logging is a more robust and long term strategy of collecting and storing the data. Extended logs can be set up on any of the automatic log types (LogInstantaneous, LogAverage, LogMinimum, LogMaximum).  During a period when the clock is moved forward, (for example, 2:00am Sunday March 11, 2012 on the east coast of the US), reports may display timestamps that essentially never existed (in this example 2:00am to 2:59:59am). It is recommended that these entries are simply ignored or crossed out. The period when the clock is moved backward is more difficult, if it is critical that data be captured for the duplicated time. An example is Sunday November 4, 2012. At 2:00am on the east coast of the US the clock is set back one hour. This means that the times from 1:00am to 2:00am occur twice. However, extended log reports will only show one set of data for the reason described above. The reports will show the first 1:00am to 2:00am data; the second 1:00am to 2:00am data needs to be captured separately.  If point log data must be captured for the duplicated timeframe, additional point configuration and Plain English (PE) programming must be used to capture and timestamp the realtime data values for the duplicated timeframe. This involves creating a numeric with a manual log  for each critical point which mirrors the live data value of the affected InfinityInputs, InfinityOutputs and InfinityNumerics. In addition, an InfinityDatetime point with a manual log must be created, one in each controller for each different loginterval of the points being mirrored in that controller. The PE program(s) capturing the point values will write the controller's date system variable to this InfinityDatetime at the same time it writes the live point value, thereby creating a timestamp that will be used for reporting. The last step will be writing the mirrored points and their corresponding timestamps to a file on disk and then printing and/or backing up that file for redundancy.  Click here to download a zip file containing sample dump files and a readme. This is an example of one way to accomplish the above data capture. 

Issue Under different circumstances, the comm port on infinet or bacnet devices will not be assigned and will show blank in their editor. The controllers may be controlling the equipment correctly, but they can't be reloaded and communication doesn't work to and from the device. Product Line Andover Continuum Environment CyberStation Webclient Windows XP, Windows Vista, Windows 7, Windows 10 Windows Server 2003, 2008, 2012, 2016 Cause This issue can happen on an upgrade where a send to database is used if the controller didn't exist previously or under other unknown database circumstances Resolution 1. Click the link to download the following TPA1498  NOTE: the TPA indicates the following at the bottom Save the new .dmp file Right click the NetController to reattach the Infinet controllers to -> select Import Into Right click the NetController to reattach the Infinet controllers to -> select Send to Database Commports will be reattached.  (THIS SHOULD BE SEND TO CONTROLLER) (The previous line, Import into, brings the corrected comm ports into the db) 2. It may be necessary to make changes to the database in order to reassign the ports to the controllers. Backup the database and send a copy to PSS for assistance The objects can be reassigned, but the queries should be tested prior to updating in the field.

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.