Building Automation Knowledge Base

Issue There are many BCX1 on the site. All of the BCX1s go offline when reloading the controller. Environment BCX1-CR B3 Continuum Cause Checking the system configuration and programming. The reasons listed below may cause significant traffic on the network. A lot of Polling value of points across controllers COV increment is set to zero Check all the numeric points' setpoint attribute including Runtime, DamperPosition, etc. as these change all the time. Points under b3 controllers are referenced by more than 32 devices. Device in the BACnet Device folder doesn't match the controller in infinity side.(Not deleted device from BACnet folder after replace the controller) When the special trunk with low quality cable  connect to BLink also cause this issue. Remove the problem trunk, the issue will be  gone When the heavy traffic happens on the network or some other issues , it will cause unexpected issues. Resolution Change the programs way, create a program in the BCX1 to mirror the referenced points in b3s Uncheck the setpoint attribute of all numerics except  temperature setpoint. Change the polling program flow type from looping to fall thru and trigger every minute or trigger by other digital point. Set the COV increments to a non-zero value After device replacement, delete the device from BACnet Device folder and find new BACnet device again, then send to database Remove the problem trunk from Blink or try to change the terminal resistor will  resolve this issue  After the steps above are done, the network should be stable and the BCX1 will no longer go offline when reloading.

Issue How to back up a full version of SQL (not express)? Product Line TAC Vista Environment SQL 2005, 2008 full versions, i.e. Enterprise, Standard etc. TAC Vista 5.1.X Cause A customer may wish to backup the TAC Vista log database to prevent data loss if the SQL server crashes. Resolution There are 2 options available, depending on the TAC Vista SQL configuration the customer has configured. If the customer has selected "Typical" on the TAC Vista Server setup "SQL" tab, you can configure this through Vista workstation. Right-click on the Server object in Workstation and select "Properties". Select the "Log Backup" tab and configure the backup schedule there. If the customer has selected "Custom" on the TAC Vista Server Setup "SQL" tab, this can be configured through SQL Management Studio (which is free to download from Microsoft, if the customer doesn't already have it). Start SQL Management Studio and connect to the SQL server instance that is being used for TAC Vista. Expand the SQL server in the tree (in SQL Management Studio) and locate the "Management" folder. Expand that folder and locate the "Maintenance Plans" folder. Right-click on the folder and either select "Maintenance Plan Wizard" or "New Maintenance Plan". Configure as required.    

Issue The SE8000 documentation states that the power supply voltage is 7 Volts DC but the circuit board sticker says 7 VDC/24 VAC. Can the controller be powered from 24 VAC? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause An incompatible relay pack might have been used. Resolution Typically the SER8300 range are intended to have power supplied by the SC3000 relay pack which supplies the 7VDC. If an SC3000 relay pack is not used, for example, if the SER8300 is just being used as a wireless device then it is acceptable to power it from 24VAC.

Issue When deploying Automation Server or Enterprise Server from Workstation for Projects under PCS, it will fail. The error shown in the Progress view window is "The live server is not empty." Product Line EcoStruxure Building Operation Environment SmartStruxure Project Configuration Server Workstation for Projects Enterprise Server (ES) Automation Server (AS) Cause A project can only be deployed to a server when the server has an empty database and not has been part of a multi-server system. A server is considered empty when it does not contain any user-created objects, such as programs and graphics. Resolution The server database can be emptied in different ways depending on if it is an Automation Server or an Enterprise Server: Reinstall the Enterprise Server. Upgrade the Automation Server with a new database. For more detail about how to deploy AS or ES, refer to Offline Engineering with Project Configuration Server (PCS).

Issue The order of installation is dependent upon the SQL versions installed with Vista and I/NET. I/NET DBCreate does not open after installation is complete.  DBCreate application is not shown even though under Task Manager processes the application is active. Product Line TAC INET, TAC Vista Environment SQL MSDE Express Vista and I/NET Installed on the same PC Cause Vista and I/NET both use SQL databases for purposes of event and trend logging.  They must be installed in the correct order to coexist within the shared SQL installation. It can be confusing to know which software should be installed first on a certain installation because it is completely dependent upon both the I/NET versions and Vista versions.  Later versions are compliant with SQL 2005 Express while earlier versions must use SQL MSDE. Resolution If a previous installation has failed, it is best to start "fresh" before attempting a re-install. Removal of Vista instructions located here: How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Removal of I/NET instructions located here: Procedure for uninstalling I/NET Seven on a stand-alone host Empty Recycle Bin to remove evidence of previous installations.    Use the following guidelines to determine in which order to install I/NET and Vista: If the I/NET version is prior to 2.2.1, then I/NET must be installed before Vista, regardless of the Vista version. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 4.3.0 through 5.0.0, and the I/NET version is 2.2.1 or higher, then Vista must be installed before I/NET. These versions of Vista use TAC Config and SQL MSDE. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 5.0.1 through to 5.1.6, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET. These versions of Vista use SQL 2005 Express.  I/NET versions 2.2.1 and higher have an option to install SQL 2005 Express. When prompted during the I/NET installation, allow a new SQL instance on the existing SQL 2005 Express that was installed with Vista.   If the Vista version is 5.1.7 and above, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET The default installation of this version of Vista uses SQL 2008 R2 Express.  When prompted during the I/NET installation, select Default Instance of either MSDE or SQL 2005. (Note that if installing on Windows7 operating system, MSDE option is grayed out and cannot be selected, as it is not supported on Windows7)..   If the Vista version is 5.1.7, and the I/NET version is 2.4.0 or higher, you can choose either one to be installed first. If Vista is installed first, by default Vista will install SQL 2008 R2 Express SP1. But I/NET 2.4x fails to recognize the instance installed by Vista, while also fails to create a default instance. So after installed Vista, manually create a default instance for I/NET, and then install I/NET. Refer to Item 1 in How to Troubleshoot on DBCreate on how to create it; If I/NET is installed first, you can choose Custom Installation for SQL during the installation of Vista. You need to manually enter the SQL instance name, SQL username and password when installing I/NET SQL. If you don't know the instance name, there is a quicker way to identify it: Open DBCreate of I/NET, and you can see the SQL server name for I/NET. Just copy and paste it here. Then you can finish the installation. For Vista IV installation, the correct procedure can be found here: TAC Vista IV and Peripheral Software Installation Outline

Issue Node reset messages are received at the Sigma server on a regular basis. Product Line Satchwell Sigma Environment Sigma software - all releases. Sigma firmware - all versions. Cause Messages designed to be sent to a server are being sent to a device node. Resolution The BAS 2800+ system allows Controllers and Terminals to have the same numbers allocated. In Sigma this is not possible as all device numbers are unique. Should a reference to a terminal accidently be left in a controller configuration, then the controller may send messages to this device number, the receiving controller will then reset. There are two ways to locate the source of the messages being sent to the resetting controller, they are: Use SigView to display all of the object data for a controller, and then search the data for the node number of the resetting controller. You will be looking for entries such as T(resetting node number). OR Disconnect the controller from the network, and then connect a laptop, configured with the controller IP Address, and running WireShark to record all network messages. Allow WireShark to run for a period greater than the time between controller node resets. Filter the WireShark messages to review only messages sent to the IP Address of the resetting node. Check what the source IP address of these messages is, and then use SigView to review this controllers data. A typical Wireshark display is shown below, in this case the trace is filtered on the "Source" IP Address. For more information on using WireShark, please review Using WireShark to analyse communications on an Ethernet network.

Issue How to view the current Priority level controlling a BACnet object using Plain English. Environment Continuum Cyberstation BACnet AnalogOutput, AnalogValue Cause 3rd party is controlling a BACnet object at an unknown priority level. We want to see what the current Priority level is and relinquish this control. Resolution We can use the PriorityArray attribute to view the value of each Priority level. Then using a For loop we can loop through all 16 priority levels to determine the current priority level controlling the BACnet object. Below is a program that will allow you to see the current priority (aaPriorityValue) controlling your object (PriorityTest) and at what priority level (aaPriorityIndex). You will need to create two numerics (configure as AnalogValue) for this program to work (aaPriorityIndex and aaPriorityValue). With the method below we can see if a non-zero value is the current priority and at what priority level.  Unfortunately a 0 value is seen the same as a NULL value (both seen as 0), so if a 0 value is currently controlling the object we are unable to determine at what priority level this is set. If aaPriorityValue is 0 and aaPriorityIndex is < 16 then we know that aaPriorityIndex is the level of the non-zero value and can relinquish all priorities down to that level if needed. Still not exactly what we want but it does give a bit of flexibility to actually control the current priority level. ======================= ' Program to get the highest priority value and its index number ' Flow: Looping Numeric count Numeric PriorityValue CALC:   For count = 1 to 16   'Loop through the priority array, looking for the first non-Null value     PriorityValue = ReadProperty(PriorityTest PriorityArray, count)     If PriorityValue is not NULL then       Break 'stop at the first non-Null value. Side effect, also first non-zero value     Endif   Next count   If PriorityTest = 0 then 'Check for 0 value     aaPriorityValue = 0     aaPriorityIndex = count   Else 'If not 0 or NULL value, set current priority value and index     aaPriorityValue = PriorityValue     aaPriorityIndex = count   Endif =================================  

Issue Continuum and Mantrap or Interlock Interval Product Line Andover Continuum Environment Continuum site with Access Control Cause Site needing to setup a Mantrap or Interlock Interval for higher security of an area Resolution What is a mantrap? A mantrap is a security device that monitors and controls two or more interlocking doors to a small room that separates a non-secured area from a secured area. These interlocking doors allow only one door to be open at any time. What are interlocking doors? “Interlocking doors” is a security term used to describe how two or more doors are interfaced with each other and locked. Doors that are interlocked cannot be open at the same time. Either door can be unlocked and opened as long as the other door is locked and closed, and no other alarm condition exists. What types of locations require a mantrap? Mantraps are used at high value or critical security areas where only authorized persons are allowed to enter. Typical areas include sensitive data processing areas, cash handling areas, critical research labs, security control rooms, and automated airline passenger entry portals. Why would my company consider a mantrap? Typically, security personnel are posted in high security locations to control access into the area. An automatic mantrap used in this same location would control the access to the area, allowing security personnel resources to be available for other tasks. What is the difference between a mantrap and an interlocking door control system? When speaking of controlling two doors within a vestibule, “mantrap” and “interlocking door controller” can be used interchangeably. Once the number of doors controlled by a single controller exceeds two then the term interlocking door controller should be used. Continuum Mantraps are accomplished by a PE Program. Interlock Interval is available at the bottom of this article. Here is a simple mantrap program written as a sample. ManTrap_A and ManTrap_B are the doors that make up the man trap ------------- 'This program implements a Man Trap that allows one person at a time in the man trap. 'Once a person is in the man trap no access is allowed until the occupant leaves the man trap via the REX. ' The occupant is allowed to exit at either door but once they have activated the REX at one door 'they are required to leave via that door. 'If occupant stays in the trap longer than TrapMaxOccTime and alarm can be sent via ManTrapStuck 'TrapMaxOccTime and ManTrapStuck are InfinityNumeric objects in the controller. 'Program is Looping and AutoStart TRAP_READY: ManTrap_A DisRdrKpAccess = False ManTrap_B DisRdrKpAccess = False ManTrap_A OpenOnExitReqst = True ManTrap_B OpenOnExitReqst = True If ManTrap_A ValidAccess or ManTrap_B ValidAccess then Goto TRAP_OCCUPIED TRAP_OCCUPIED: ManTrap_A DisRdrKpAccess = True ManTrap_B DisRdrKpAccess = True  If ManTrap_B ExitRequest then ManTrap_A OpenOnExitReqst = False Goto WAIT_EXIT_B Endif If ManTrap_A ExitRequest then ManTrap_B OpenOnExitReqst = False Goto WAIT_EXIT_A Endif WAIT_EXIT_A: If ManTrap_A DoorSwitch = Opened then Goto TRAP_READY If TS > TrapMaxOccTime then ManTrapStuck = On WAIT_EXIT_B: If ManTrap_B DoorSwitch = Opened then Goto TRAP_READY If TS > TrapMaxOccTime then ManTrapStuck = On 'Keep program from disabling due to run time errors E: if ts > 30 then goto TRAP_READY   For Interlock Interval please use this PDF. Interlock is hardware controlled, not through a PE.

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 Function Block Editor does not open. Product Line EcoStruxure Building Operation Environment SmartStruxure Function Block Editor Cause There could be many reasons but in one of the case we found a malware called "sprotector.dll" somehow trying to hook into the Function Block Editor dll's. This malware is then crashing and prevents Function Block Editor from starting. SProtector.exe is typically added when you install another free software (video recording/streaming, download-managers or PDF creators) that had bundled into their installation this program. Resolution Reinstall this computer's Operating System completely, if that's not an option you can read more about how to remove "sprotector" here: http://malwaretips.com/blogs/sprotector-exe-virus-removal/

Issue Pin point crash issue: • Pinpoint crash • Scroll bar does not work on upgrade from older revisions of CyberStation • Making changes to a graphic created in Pre 1.94 CyberStation causes the graphic canvas size to become corrupted • Copying objects/controls of a graphic and pasting them to the same graphic causes the graphic canvas size to become corrupted    WebClient DMZ issue: This hotfix corrects an issue where web.Client positioned in the DMZ only communicates in one direction.   Web Client Personnel Area issue: This hotfix corrects an issue where the web.Client IE browser PC becomes disconnected from the web.Client server when attempting to remove area(s) of personnel objects. It also corrects an issue with web.Client not removing area(s) if the personnel records are not re-opened after saving. Environment Windows all versions Continuum 1.94 SP1  Web Client  Cause This is due to bugs which have been discovered and have now been fixed    Resolution Please go to the below link for hot fixes that apply to your problem, there is also a complete install pack of SP1 which includes all hot fixes which should be installed if SP1 has not already been applied CyberStation & web.Client Service Packs v1.94 Hotfix

Issue If an Automation Server should be used as a LON Device in an OpenLNS Database using the OpenLNS Commissioning Tool? Is that possible to do? Product Line EcoStruxure Building Operation Environment Automation Server 1.4.1.68 or newer   Cause Some sites may wish to use other Lonworks configuration tools than EcoStruxure Building Operation Workstation. Resolution This is possible in 1.4.1.68 and newer. Add a Lonworks Local FT-10 interface and then add an Externally Managed Lonworks Network.

Issue Cannot open Create/Edit Badge in Personnel Manager even though badging is enabled on Security Key Getting error message "Cannot init license" Environment Continuum Personnel Manager Cause Windows user does not have enough permissions to run EPI Designer (EPI the Print/Badge Program installed with Continuum) Resolution Change the Windows login to one that has sufficient permissions to run EPI Designer (the Print/Badge Program) The standard Windows User does not have permission to run EPI Designer (the Print/Badge Program) whereas a standard PowerUser or Administrator does have permission. NOTE This was an Windows XP issue, similar issues may still be present in newer Windows versions Continuum v1.92 was used for this document

Issue Personnel distribution shows error 5310 Product Line Andover Continuum Environment Cyberstation Cause Error 5310 (0x14BE hex) indicates a duplicate card number. Resolution Take a LAN capture of the distribution using Using WireShark to analyse communications on an Ethernet network and send it to PSS for analysis, a PSS engineer will decode the packet to extract the card number and card type that is being rejected as duplicate. Armed with the card number and type find the offending record in the DB and eliminate the duplication.

Issue What is the difference between Lonmaker 3.2 and "Turbo Edition"?  Environment Echelon LonMaker: 900800130: LonMaker 3.2 Standard Ed. 900800140: LonMaker 3.2 Professional Ed. 900800150: LonMaker 3.2 Std Ed Upgrade 900800160: LonMaker 3.2 Pro Ed Upgrade Cause In some documentation and price lists, LonMaker 3.2 is mentioned as "Turbo edition." Resolution There is no difference between Lonmaker 3.2 and "Turbo Edition." It is just a different name for the same product.

Issue SP-RDM2 Reader Expanders running firmware 1.12.544 appear to fail whenever an attempt is made to update their firmware revision. Product Line Security Expert Environment SP-RDM2 SP-MRDM2 Cause There is a known defect in 1.12.544 (Build .544) which prevents the SP-RDM from being upgraded or even downgraded. However, a number of SP-RDM units have been shipped from the factory with this build pre-installed. Any attempt to select an SP-RDM running this firmware and upgrade or downgrade it to a different revision will consistently fail with an error: 'Module not responding'. There is also a possibility that the SP-RDM can be permanently disabled in the process Resolution Since the .544 Build defect cannot be resolved the only recourse at this time is to swap out the unit via the Returns Material Advice (RMA) process for a new unit.      List of SP-RDM2 Serial #s affected thus far: Note: All other SP-RDMs running firmware both above and below .544 Build are unaffected

Issue Is there an easier way to get log information out of a Niagara R2 Enterprise Server station other than by using a web browser, saving the data, and importing it to Excel? Product Line TAC IA Series Environment I/A Series R2 (Niagara) station with logs. Cause Tech tip. Resolution There is no easier way to get log information than to use a web browser, save the data, and import to Excel. However, by default, a query to the archived log limits the number of records to 2500. This limit can be changed by adding $limit=xxxx.  Note:  Attempting to query a large number of records (> 7500) may cause the process to fail due to timeouts. A review of the cloudscape2excel document provides some details.

Issue Spare parts availability for Controlli MVL56 (Forta M700) Environment Controlli MVL56 Forta M700 Cause Replacement parts   Resolution Due to the spring return design of this actuator, no spare parts are available, with the possible exception of the PCBA. Any repairs should be done by the factory for safety reasons. However, MVL56 is a Controlli product and they should be contacted directly for further details. If the M700 fails after the warranty then a new actuator is required, the MG900 SR is a lower cost alternative to the M700.

Issue Occasionally get a alarm in Vista that is connected to the bit 16 of the error block in Menta (Mainloop overrun. The application program can not execute within the specified cycle time) Environment Vista Menta Xenta Cause In Menta under Program Specification there is a parameter called cycle time. This parameter tells how often the program should be run in the Xenta. If the program take more time to execute then the specified value Vista will show a error connected to a error block in Menta, "Mainloop overrun. The application program can not execute within the specified cycle time" Vista will not show this specific text, Vista will show the text that you choose to show in the Alarm block connected to the Error block. I.e. In Menta you have a error block that leads to a XPR block (expression block) that have the expression A&16, when this expression is meet it goes to the alarm block that will generate an alarm text of your choice. (16 is the bit that tells a Mainloop overrun. The application program can not execute within the specified cycle time have occurred.) The Error block has several condition and work like this The output of this block is an integer value where each bit represents an internal signal or error from the system program. Each output bit is set as long as the error condition remains, remains. In the case of a restart after a power failure, the output bit is set during the first program cycle after the restart. The output value is zero when no error conditions are set. Conditions:   Bit no. Output value Description 0 1 Restart after power failure 1 2 Integer underflow/overflow 2 4 CNT block overflow 3 8 RT block overflow 4 16 Mainloop overrun. The application program can not execute within the specified cycle time 5 32 At least one of the switches on one of the I/O modules associated with the application, is in the position for manual override (ON, OFF, MAN) of the output 6 64 Indicates that an OP is connected, and the user is logged in at medium (yellow) or high level (red). 7 128   8 256 Dial-up modem line to TAC Xenta unit disabled 9 512 Update of a Network variable value was not received within the set Period 10 1024 There are tripped priority 1 alarms in the alarm list 11 2048 One or several I/O modules offline 12 4096 I/O in forced mode 13 8192 There are tripped and unacknowledged alarms in the alarm list 14 16384 There are tripped and not reset alarms in the alarm list Resolution To remedy this error change the cycle time to a higher value or make the Menta code lighter

Issue  The Modbus TCP-IP XDriver can function as either a TCP Client or a TCP Server but not both at the same time. Environment Cyberstation Continuum Controllers Cause Documentation Resolution  It is the XDriver points themselves that define the mode of the driver, in every point created, Parameter 2 should be set to either “0” for Client Mode OR to “1” for Server mode. You can’t use both in one driver. ALSO, in Client mode you need to create the Remote Device Status point, one per server, but it is Parameter 2 in the points that determines the client/ Server mode. QUESTION: If the XDriver can only operate in one mode (client or server) why does each point need to be configured with the mode type? ANSWER: There is a historical reason for this, the original design envisioned the support of both client and server points simultaneously, but for reasons that are well beyond the scope of this article this was changed to support only one mode at a time.

Issue Setting up ID Works on a Remote Client PC Product Line TAC INET Environment I/NET Seven ID Works Windows XP Windows 7 32-bit Windows 7 64-bit Cause Configuring the I/NET System to be a “Server/Remote Client” format and the ID Works software is going to be on a Remote Client PC. Resolution The first procedure is to modify the ODBC Data Source. The steps for this are very dependent upon the PC's operating system. Reference page 2-14 through 2-23 of TCON 301, the chapter named Modifying TAC I/NET Seven's ODBC Data Source.  Once the ODBC Data Source is configured, proceed with the steps below: Go into the ID Works Administrator Editor and select the System tab. Scroll down to the Photo Path option. Direct the current path to the PC that is going to be the Server. In this example, the PCs Name and Photo location is: \\TPServer\CDrive\I7photos   Go into the ID Works Designer Editor open each of the site badge templates and modify them for the Server PC link. Open one of the templates. Highlight the Image path square and do a right mouse click. Go to the Field Properties option. Set the path to the Server PC location for the badge photos. See the example below for further information.   In this example the server PC is named TPServer. Badge photos are in the C:\I7photos\Thumbnail directory. There are only eight pictures entered at the time these captures were made. The jpegs for those eight individuals were saved to the folder using the CardNumber as the name shown below: