Building Automation Knowledge Base

Issue Having issues configuring the pulse counter on the SEC-TE (TE2) Environment SmartStruxure Lite Multi-Purpose Manager SEC-TE (TE2) Cause N/A Resolution Navigate to the ZVC object of the SEC-TE and change "Analog Input 3 Mode" to "pulse counting". The value in AI3 (the counter) will then be incremented every time the pulse goes from 1 to 0 regardless of how long that takes. However, to convert the value of the counter to a more meaningful reading (e.g. water flow), you would need to use a Lua script in the MPM.   To reset the counter, click on the "Reset" button   Possible issues while testing: Using the Binary outputs of the TE2 for testing purposes will cause the counter to display unreliable readings. In fact, any binary output that induces voltage in AI3 will in inaccurate readings due to the noise induced. Instead, The binary outputs of the MPM can be used for testing before deploying the equipment on site.

Issue When a user attempts to connect to the Sigma 4.08 (3.46.57) Server using a WebClient, the client connects, but the screen remains blank. Product Line Satchwell Sigma Environment Sigma WebClient 4.08 (3.46.57) Cause When Sigma 4.08 is installed, the installed version of LogonSE.swc is blank. Resolution Download the correct version of LogonSE.swc. Shutdown the Sigma client and server. Navigate to Sigma/Data/Graphics/Drawings and delete LogonSE.swc. Copy the downloaded version of LogonSE.swc to Sigma/Data/Graphics/Drawings. Restart the Sigma client and server, and then test the Web Client.

Issue Unable to save periodic report to network drive when Vista is running as a service. Vista Alarm: Warning logged in B0WARLOG.TXT on node XXXXXX B0WARLOG.TXT: report >> Could not save report Reports-Report, hRes=[-2146827284] Product Line TAC Vista Environment Vista 5.x Cause When Vista Server (TACOS.exe) is running as a service, it is not functioning as part of the user desktop. This means that network map drives are not accessible under the aliases (J:\, M:\, S:\, etc). Vista Server is instead running under a specific user account name that must have access rights to the network drive and the report object must reference the full path to the network drive location. Resolution NOTE: it is recommended that the destination folder for these periodic reports be located on the local disk C;/ drive.  It can be problematic to have the destination folder located on the desktop. Open the Services MMC from Control Panel\Administrative Tools\Services. Find TACOS in the list of services. Stop it if it is running. Right click on the service and select properties. On the Log On tab check the "This Account" option and fill in a local administrator user that has access to the network location. Click Ok. Start the TACOS service. Start Vista Workstation and log in. Right click the report you are trying to save to a network drive and select properties. On the Report tab ensure that the "Save to folder:" has the full network path (ex. \\computername\directoryname). Use the browse if necessary. Click OK The next time your periodic report runs it will properly save the report to the network location.

Issue Considering changing the bCX MSTP BACnet MAC ID to an available value in the 1-127 range as indicated in the bCX web page configuration. The online Help provides the following information on the setting. BACnet MAC ID - Comm2 Identifies the MAC (Media Access Control) networking address of the controller on its MS/TP network, using integers ranging from 0 to 127. The default address is 0 and it only necessary to change this value if the value has already been assigned to another device on the network. Product Line Andover Continuum Environment bCX4040 bCX4000 b3 devices BACnet 3rd party device Cause BACnet MAC ID 0 (zero) on MSTP network already in use by third party device. Resolution Due to a limitation in the b3 devices the bCX's MSTP MAC ID should not be changed unless the bCX will only host third party devices on its MSTP (Comm2) and will NEVER be in a situation where MAC ID zero is available during a b3 learn operation. The issue is that when ID zero is made available (by changing the default in the bCX) the LEARN process done on b3s will assign ID zero to one of the b3s, because of design constraints, a b3 will not operate correctly if assigned MAC id zero. Product Support strongly recommends that if a third party device is using MAC ID zero on the MSTP, that the device be re-assigned a different ID in order to keep the bCX at its default value of MAC ID zero.

Issue XBuilder project was upgraded and OGC graphic pages were converted to TGML using the automatic conversion. The same names were used for the graphic pages, but they will not display in the web interface. Java console reports: java.io.IOException: Wrong file format feature < 0 or reature > 7  at se.tac.applet.graphics.ogc.OGCStreamHeader.load(Unknown Source)  at se.tac.applet.graphics.ogc.OGCPicture.loadPicture(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.go(Unknown Source)  at se.tac.applet.graphics.GraphicsViewer.init(Unknown Source)  at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)  at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder 5.x.x Xenta Servers Xenta 511, 527, 711, 731 Cause The graphic object was properly converted, but the graphic page is still using the old template (Graphics.html) which is designed for OGC graphics instead of the new graphics page template (TgmlGraphics.html). This causes the java to interpret a TGML graphic file as an OGC graphic file. Resolution This can be resolved two ways Manually edit the Template property of the Graphic page objects in XBuilder to be TgmlGraphics.html. Delete the graphics page in XBuilder and recreate it. When the graphic object is linked to the graphics page it will properly assign the correct template based on the type of graphics file type.

Issue A new feature is introduced in TAC Vista Workstation 5.1.7, enabling the user to identify broken and empty TGML bindings and TGML Links in TAC Vista Workstation. This feature can also list all bindings and links in TAC Vista Workstation, replacing the search function previously used to identify bindings and links in TAC Vista Workstation. Product Line TAC Vista Environment Vista 5.1.7 and above Cause Compiling a list of all bindings, or all empty or broken bindings, allows a user to quickly find and update any graphical problems cross an entire database at once. Resolution From Workstation, right click on a folder and choose "Find broken bindings." This replaces the previous method of searching for broken bindings within the Search window. Note the following object types are no longer available in the TAC Vista Workstation search function: TGML Bindings TGML Dynamics TGML Link TGML Links See TAC Vista Technical Manual Chapter 28.2 for additional information about this feature.

Issue The V395-1 is obsolete and no longer available Environment V395: 7319501000 7319505000 7319509000 7319513000 7319515000 7319519000 V321: 7312153010 7312157010 7312161010 7312165010 7312169010 TAC Forta Cause The V395 valve is obsolete and no spare parts or direct replacement valves are available. Resolution The closest suitable valve is the V321 with a Forta actuator. The "A to AB" measurements are the same, but the "A-AB centerline to B flange" is different. Double check the data sheets for more information and details. Keep in mind that V395-1 is PN25, while the V321 is PN16.

Issue PCT core and memory setup documentation does not exist Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause It is unclear what PCT core and memory settings should be configured for different kind of projects.     Resolution For optimal use, the minimum recommendation “Cores” should be limited to four (4), and have two (2) GB of “Memory” allocated Should you notice your CPU usage increase past 75%, the number of Cores can be increased as needed to help stabilize the system and maintain efficiency. Additional memory can be allocated for larger projects with many AS’s or multiple users working on the project at the same time. The amount of memory will be limited by the available memory on the machine, and the memory allocated to all the projects that are running.  

Issue Change the LED pattern on card readers Environment Continuum Site Cause How to Change the LED pattern on card readers Resolution On the ACX line of Infinet controllers and also the AC1+ modules you can change the dynamics of the reader LED. The Alternate LED pattern is selected by creating a numeric point whose name is AccessLEDPattern. When this point exists, the Alternate LED pattern will be employed by the access controller. When this point does not exist, the standard LED pattern will be employed. It should be noted that cold-starting or resetting the access controller does not delete or destroy the AccessLEDPattern.

Issue OPC Server setup for TAC Vista will not save the information when you change the user type from Windows account to TAC Vista account. Product Line TAC Vista Environment TAC Vista OPC Server 1.6.1 Cause This is a known issue that requires a specific reinstall procedure. Resolution Install version 1.6.0 of OPC Server Change to TAC Vista login in the TAC OPC setup Uninstall it Install 1.6.1 again. For more OPC Server issues please Vista OPC Server Installation and Known Issues.

Issue An ACX5740/CX9680 does not provide access events to Cyberstation 1.81. Environment Cyberstation 1.81 or earlier version SQL Server 2005  Cause The ACX 5740/CX9680 was running version 1.1xxxxx/2.1xxxxx firmware. This version of firmware is incompatible with Cyberstation versions 1.81 and earlier. Resolution The site was offered the option of upgrading the version of Cyberstation to 1.9x, or down-reving the ACX 5740/CX9680 to version 1.0xxxxx/2.0xxxxx. Flash down-reving the controller was chosen and did resolve the access event delivery issue.

Issue The LNS credits and the NL220 credits quantities do not match Product Line TAC Vista Environment NL-220 Cause Some LNS credits have been consumed while another NL220 dongle was used on the system. When you commission a device, both a NL credit and a LNS credit are consumed. When using another dongle on a given computer, (likely in “move” mode) it will consume a NL credits from it and a LNS credit from the computer. This can bee seen from the NL220 information bar. Resolution If the LNS credits are inferior, this means you are running in deficit. To fix this, you should order additional LNS credits to level up their quantity. When we deliver you credits, we send at the same time NL and LNS. This is why the dongle has to be confirmed on the computer when ordering credits and also why we highly recommend to commission devices only when the dongle is confirmed. Ordering more LNS credits is a link on how to order LNS credits.

Issue Cannot communicate with an EF1 electricity meter. Environment Modbus Electricity Meter EF1 Cause Cannot communicate with an EF1 electricity meter using Modbus. Resolution The settings need to be as follows; IC-Modbus Communication settings; Modbus RTU 9600 baud 8 Data bits Even parity 1 stop bit Fit a 120 ohm resistor across the RS 485 connections Gateway.txt entry - Point number,9,4,0,1,0x1102,0,0,0 Meter Wiring U+ - Power supply can use 7 - 24 volts dc, but tested using 12v - 15v. B connection to IC3-Modbus Terminal C2 A connection to IC3-Modbus Terminal C1 GND - Power supply 0v To review the EF1 data sheet please click HERE. To download the Windmill ComDebug software, please click HERE, or to get the latest version, register at http://www.windmill.co.uk and download from there.  

Issue Highlighted a door point and selected Schedules; I cannot modify the schedule. What is wrong? Error received: Communication with this SLI could not be established. Editing cannot be done. Product Line TAC INET Environment I/NET Seven Work Offline (Offline edit) Cause When you highlight a door point schedule, I/NET attempts to establish communication with the selected door’s SLI (Sub LAN Interface). If communication with the SLI is successful, I/NET will proceed normally. However, if I/NET cannot communicate with the SLI, you will not be able to modify the schedule assignment for the selected door.  This is the case also for the following editors: Access Initiated Control Personnel Schedules Door Schedules Doors Elevators Resolution Communication must be established with the sub LAN devices (DPU) before schedules can be edited. It is possible to do this in an offline mode as long as you have the Sub LAN Interface's (SLI) SAV file.  Refer to Offline Database Edit  for further information on Offline Edit.

Issue Every time you access a Xenta 511/527/913 you are taken to the "Server Reboot" page Environment Xenta Servers Xenta 511, 527, 913 Cause This problem is caused by some Proxy Servers that will cache the first page they find with that address which is typically the "Server Reboot" page since it is the first page found when you power up the device. Resolution To correct this, you can either clear the cache in the Proxy Server or you can configure your web browser to not use the Proxy Server for the Xenta Server address. Open Internet Options Select the Connections tab Click the LAN Setting button Click the Advanced... button Add the address of the Xenta server to the Exceptions window  

Issue Upgraded Site to Continuum 2.01, now get %N and %D in Alarm Message as seen in the message field in the snapshot below: Product Line Andover Continuum Environment Cyberstation Keywords %D %N Cause This is caused by the Enhanced Alarm Logging and Enhanced Alarm Delivery being unchecked Resolution This can be resolved by using the following steps: Close all the cyberstations Initialise the database making sure you have Enhanced Alarm Logging and Enhanced Alarm Delivery ticked as shown below:  

Issue Unable to edit Xdriver communication settings on a comm port for a 9680 or the stopbits show incorrectly as 1.5 Product Line Andover Continuum Environment 9680 Continuum 1.74 or 1.81 Webclient 1.74 or 1.81 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Under certain circumstances, there was an issue in version 1.74 and 1.81 where the comm port settings were disabled or grayed out. If the settings were not grayed out and an attempt is made to set the stopbits, it could get set incorrectly to 1.5. Resolution The issue is corrected in 1.82 and above.  The work around for versions 1.74 and 1.81 are to set the comm port from the command line. See Command examples to check controller comm port settings for Xdriver or other communication to set the parameters manually.

Issue What are the cable requirements? What is the maximum wire length? When do I add a repeater? What is the maximum number of repeaters allowed? Product Line TAC INET Environment I/NET Controller LAN, C-LAN Cause Incorrectly run controller LAN wire can cause communication issues between I/NET controllers and hosts. Resolution C-LAN should be run using: Two wire, twisted pair, shielded cable 24 AWG (0.206 mm2) or larger 30 pF/ft. or less between conductors 55 pF/ft. or less conductor to shield 80 - 150 ohm impedance The maximum controller LAN length is 25,000 feet (7,620 meters) assuming 4 repeaters are used. A repeater should be installed: To segment every 32 controllers Or if the LAN length exceeds 5,000 feet (1,524 meters). The maximum number of repeaters allowed is 4.

Issue What is DBF? Environment I/NET site Cause What is DBF? Resolution It is a Docutrend database function that allows you to extract the tenant number, key/card number, or data from one of the access control personnel database files.

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 Active Event Viewer contents and column headers are blank.   Product Line Andover Continuum Environment CyberStation Cause Windows registry corruption. Resolution Method #1 Close Continuum and use Windows System Restore to put the system back at a point where the Event Viewer were fine. Method #2 NOTE: Any customization previously done to the event viewers such as column name changes etc  will be lost when this method is used Shut down CyberStation then backup the Windows registry as a precaution Edit the Windows registry and delete HKEY_CURRENT_USER\Software\Andover Controls\Continuum\Access Event View Start CyberStation and open the event viewer which recreates the entry in the registry using default values.