Building Automation Knowledge Base

Issue Unable to Upload or display point data on an I/NET Controller in StruxureWare Workstation Environment I/NET to StruxureWare Integration Cause The most common cause for I/NET controllers to not integrate with StruxureWare are duplicate point names or illegal characters in use Resolution In Building Operation Workstation, right click on the errant I/NET controller and select "Upload" This is expected to fail at this point Browse to the Enterprise Server Directory as displayed in Building Operation Software Administrator Look in the db/Logs folder Locate the trace log and open it using a text editor scroll to the last line of the log and look for an entry that contains inet information. If the error is caused by duplicate point names, this will be the trace log entry: 2014-01-30 20:00:25.587 [6220] nsp.pin.inet.GetAllPoints InetPlugIn::ProcessChangeSetList failed RecoverableException: d:\dev\rb-int-v140-sp1-system\source\packages\commons\components\C3Po\nsp_servers\csc\changesetmanager\source\ChangeSetTransaction.cpp(987) Error: Object_Already_Exists (0x40006), module Runtime_Db_Manager(41), moduleCode 0, dispString "~/INET Interface/0321 - SBOtester/Point1", techString "" Note the text dispString "~/INET Interface/0321 - SBOtester/Point1", techString "" This indicates that there is a point on the controller named "Point1" which is causing the error Option 1: In I/NET workstation, connect to the controller Rename the point indicated above Perform a station save and attempt to upload the controller again. If it fails a second time, repeat steps 3-10 until you have removed all illegal entries Option 2: Use RdInet to view the Save file. Click on Save Page Open the .csv file in Excel and sort the data by Name Locate the Point indicated above and notice that there will be 2 objects of the same name. In I/NET identify these 2 points. Very likely, one will not actually exist. Copy the Point that exists to the address that was indicated as a duplicate in Excel Delete the newly created point to permanently remove the object from the .sav file. Perform a station save and attempt to upload the controller again. Repeat this process if necessary.

Issue When creating a Modbus device template in XBuilder Device Editor which Modbus register data type should be used? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Modbus Register Bitmask Cause Lack of consistency between Modbus slave manufacturers there is a large number of data formats that can be selected. Each register format interprets the value differently based on byte order or purpose of the specific bits. Resolution Consult Modbus slave product documentation Use trial and error to find the correct register format. Perform communication logging to capture the raw data and compare with a known value to determine the format. As a tool to assist with these steps please consult the Definition of Modbus Registers.

Issue Which signal types can be connected to a UI on a Xenta I/O Modules? Product Line TAC Vista Environment Xenta 451A/452A, 421A/422A Cause UI is short for universal input, which means that these inputs are compatible with many different input types. Resolution Supported input signal types are: Thermistor: 1.8 KΩ at 25 °C or 10KΩ at 25 °C; Voltage: 0 to 10VDC; Current: 0 to 20mA; Digital Input. Refer to the following link about 1.8KΩ and 10KΩ thermistor compatibility: 1.8k Thermistor compatibility with Xenta controllers 10k Thermistor compatibility with Xenta controllers

Issue Are 8 byte unsigned integers (UI8) supported in Vista OPC client? Product Line TAC Vista Environment TAC Vista 5.1.X Vista OPC tool Cause Not all OPC data types (canonical data types) are supported by OPC server. UI8 variables show a question in OPC tool. If the Canonical Type column shows a question mark for the variable (or tag) then this means that Vista has been unable to identify or does not support the data type. Resolution If possible divide the OPC tag/variable into 2 x 4 byte registers. It could also be worth checking what the expected maximum value is for that register and seeing if that value will fit in a UI4 (unsigned integer 4 byte). An alternative solution, although the functionality must be checked by the engineer is to create the variable object manually and use the canonical type "string". To do this follow the steps below: Note the name of the OPC variable to be added to Vista in the OPC tool browser window. Under the OPC server object in Vista create a 'Value - String' and give it the same name as the OPC variable. Hold down shift and ctrl and right-click the string value -  select properties. Locate the Property RA and fill in the name of the folder, variable name and the data type in the following format: folder name.variable name|data type Example of OPC naming convention including data type, in TAC Vista. Click on OK and the variable should start updating after refreshing the folder. More information on OPC data types can be found in What does the "| n" mean when viewing the properties of an OPC variable in Vista workstation?.

Issue Trying to download a Xenta programmable controller through System Plug-In fails.  Errors shown are default LNS type errors shown as: (Subsystem: NS, #59). Click okay and the next error appears (Subsystem: NS, #64). Click okay and the next error appears (Subsystem: NS, #51). Product Line TAC Vista Environment TAC System Plug-In Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The steps defined in this article only relate to the NS #59 error when it is received on an attempt to download a controller through the TAC Vista System Plug-In.  It does not cover when this error is shown as a result of a commission attempt in an LNS environment.  For the commissioning error, please see The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). The cause of this particular set of errors is unknown at this time, but has been witnessed a number of times.  Various troubleshooting techniques have resolved the issue. The best course of action is to try each of these methods in the order of least to most disruptive. As new techniques and procedures are discovered, they will be documented here. Resolution Remove the controller from the Vista database In the Vista System Plug-In, locate the offending controller in the right-hand TAC Pane Right click and delete the controller Update the Vista database Locate the controller in the left-hand LNS Pane Drag and drop it back into the TAC Pane Update the Vista database Attempt the download again.  Remove the controller from the LNS database In LonMaker or NL220, locate the offending controller Right click and delete the controller In the Vista System Plug-In, locate the controller (which now has a red X over it) Right click and delete the controller Update the Vista database Add the controller back to the LNS database In the Vista System Plug-In, locate the controller in the left-hand LNS Pane Drag and drop it back into the TAC Pane Update the Vista database Attempt the download again Replace the controller Physically replace the controller This should be performed in conjunction with the steps listed above for removing the controller from the LNS database.

Issue When a Xenta 121-FC changes from heating to cooling the fan output  turns off for 5-10 seconds. Product Line TAC Vista Environment 121-FC controller Cause The firmware version has been enhanced and this was a enhancement that has been implemented. Resolution Upgrade your 121-FC to version 1.25 (or above). Download the upgrade files from The Exchange Download Center: Xenta 121-FC Firmware Files (NXE/APB/XIF) See Downloading new NXE or APB files using Lonmaker for instructions on how to download the application to the controller using LonMaker.

Issue MSDE to Full SQL database Product Line TAC INET Environment I/NET site currently using MSDE and wanting to convert to Full SQL database Cause The size of a site may have grown beyond the limits imposed by the existing SQL database.  The site may want more information available in the database thus pushing beyond the size of the current database limits. SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL: For information on your current SQL compatibility Resolution Here is a list of articles which may be useful with installations of I/NET: Installing I/NET Seven on a 64-bit operating system Equalize Client in Windows 7 64-bit with I/NET 2.42 or higher SQL 2008 and Windows 7 SQL 2008 Install Tips Installing 2008 SQL R2 Express for 2.42 Also: The Windows 7 HAS to be the professional version to work with I/NET. The Home Edition will not work. Assuming the site is using File Equalization it requires FULL SQL 2005 on the 32Bit and Full SQL 2008 R2 on the 64Bit on the File Master. The other PCs can have the express version of SQL, but the Express has to be the same version. If database size is expected to get above 4Gig, then full SQL would be needed on the FileMaster as well as each Equalized Client There is really no way to make a comprehensive list of every single step required at every site. Site knowledge is key but this list may be beneficial. It is assumed the site has a Filemaster (FM) and several Equalized Clients (EQ). Make a backup of db, then make a second backup. Copy those onto another location for safekeeping. Make sure all firmware at site is at correct revision Save archive information on each computer Make note of each pc for I/O configuration information Bring each EQ computer to a stand alone state including Filemaster Make backup of each pc’s db and archive info, graphics pages, etc for safe keeping Discover what database is on each EQ and FM. I assume the FM has MSDE, which all the others would have as well. From FM uninstall I/NET Remove all the I/NET folders from FM Remove SQL on FM Install Full SQL on FM Install I/NET and use Full SQL instance on FM Create blank database on FM Check that db from SQL Management Studio Express Restore db from backup on FM Repeat steps 8 – 13 on each of the StandAlones except using SQL Express In I/O configuration, point each StandAlone at FM which makes them EQs Setup your archiving config for site Go through each link in Network Configuration and check for communication Go to AMT and check messages

Issue Various problems with converted TGML graphics Bindings of the I/NET objects within Building Operations have wrong and / or illegal point address. Environment I/NET integration with SmartStruxure Cause Improper preparation before converting graphics may cause nuisance issues. Resolution Ensure the following is done when converting a sites I/NET graphics to TGML Before converting the graphics to TGML Ensure all save files are current Ensure the I/NET network configuration is current Before importing the graphics to StruxureWare Ensure that all affected controllers are imported.  Do not change any names or descriptions before importing graphics Upload any controller which indicates it is required. This will ensure that point names for graphic bindings are correct. In the INET Interface path box, enter the path to where the INET interface is located in WorkStation. This setting affects the bindings that get defined for objects in the resulting TGML file(s). If you accepted the default name when you created the I/NET interface in WorkStation, this path is typically /Server 1/INET Interface/.  Make sure this matches the installed system details.   Click Here to get more detail from the Online Web Help. Check out the I/Net Transition: Graphics Conversion video on the Community website.

Issue Periodically a computer with Vista 4.5 will start generating the message "Failed to Read Event From Event Log Database" when opening Vista Workstation. Error: "Event Receiver Failed - Could not retrieve any events from the event log". Product Line TAC Vista Environment Vista IV Vista Workstation Windows Server 2003 Windows XP Cause Vista IV uses 2 users, TACA and TACM (appended with an underscore followed by the PC name e.g. "TACA_PCname"), to manage its SQL connection. Certain Automatic IT security procedures will either remove these users or revoke their administrator privileges. Resolution Option 1 Reinstall Vista. This will be required if the users TACA and TACM no longer exist. Option 2 Modify User rights for accounts TACA and TACM. This is only possible if the local user accounts have not been deleted. To do this you will need to follow the following steps: Log in as an Administrator Go to the control panel and look for the program User Accounts (also called User Profiles)   Find the User TACM Select Properties In the Group Membership tab, add the user TACM to the administrator group Option 3 Upgrade to Vista 5 For either Option 1 or Option 2, you will need to contact the site IT department to ensure that this issue will not come up again. Event Receiver Failed - Could not retrieve any events from the event log may also be of interest.

Issue NPR Connectivity over the Internet Product Line TAC INET Environment I/NET NetPlus Router (NPR) Series 2000 Cause In most cases when communication occurs over the Internet, firewalls are in place to block non typical ports.  I/NET utilizes Ports 50069 (set by default).  These ports usually need to be configured within routers to allow I/NET to communicate correctly. Resolution Receiving messages from one I/NET System to another over the Internet through an NPR that is behind a Firewall. In order to accomplish this there are several steps that need to be done. Configure the NPR with a static IP Address. Set the Host Masking to send and receive messages (this will not be available when directly connected). Remove the NPR from behind the firewall and connect outside the firewall. Connected directly to the Internet. Set the Host Masking so that it can receive messages. Once communications have been established, You can now replace the NPR back behind the firewall. Also refer to Which ports must be open on a commercial router in order to communicate with an NPR over a WAN? which discusses ports utilized by I/NET. For cases where you are using the Xenta Server 527 NetPlus Router (NPR) refer to TCP/IP Ports used by the I/NET system: UDP Port Settings.

Issue Get error "Local TAC Vista server not started . Cannot reserve graphic object" when trying to edit a OGC graphic from TAC Vista Workstation. Can not start OGC editor from within TAC Vista Workstation Product Line TAC Vista Environment Windows Server 2008 Windows Server 2008R2 Windows 7 TAC Vista Server running as a Service Cause When using Windows 2008/7 the following legacy tools can not be used when TAC Vista Server runs as a service: TA Draw, TA Main, Database Generator, LIST.EXE, IPCL Editor, Test Client and UPGRFILE.EXE. For more restrictions for Windows 2008 and Windows 2007 see the release TPA-VSTA-11-0002.01 for TAC Vista 5.1.5. Resolution Run TAC Vista Server as an application.  Refer to Registering/Unregistering TAC Vista Server as a Windows service for registering/unregistering Vista Server as a service.

Issue What are the product certifications? Product Line EcoStruxure Building Operation Environment SmartStruxure for Buildings AS ES Cause Standards documentation required. Resolution Click here for the CE Declaration of Conformity Click Here for the WSPCert For  BACnet BTL Testing see the PICs statements or the BTL Website: http://www.bacnetinternational.net/btl/ For UL and Country of Origin certification, please refer to PSS for this.

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 for assistance. Issue How can duplicate Handle errors be fixed? Product Line Andover Continuum Environment All versions of Continuum CX, i2 and infinet Controllers Cause An SQL database gives every object a unique handle that is used internally to reference that object. If Continuum requests a value from an Input point that has handle 1234, but that controller has handle 1234 for example as a TimeDate point, then problems will ensue. Every object in the DB has a unique handle. This includes all classes: points, programs, graphics, reports, schedules, etc. Duplicate handles can be caused on sites where engineers use multiple databases during commissioning on new panels (maybe a Single User on their laptop), It can also be caused by importing dump files with handles created from other databases, or just from database corruption on the server from failures etc. It can also be caused by the use of an Infinity LSX280 see Handle mismatch issues. Resolution Usually reloading the controller will re-sync the controller and all of its object handles back to the site database. If the DB has become corrupted, run the analyzer and try to fixup (Clean) any issues You may even have to manually delete the offending objects, running the Import Export Fixup utility (See How to run the Import/Export Fixup Utility) Follow this with a controller reload Worst case would be to revert to a backup DB if it is found to be corrupt. To avoid issues altogether, it is best to engineer a project all from a single DB and take care when importing dump files.

Issue When trying to add an automation server underneath an enterprise server the following error is given. Product Line EcoStruxure Building Operation Environment Workstation  Automation Server Cause Something has been left behind in the automation server that causes a conflict. Resolution Reformat the automation server by performing a New database download. Create a backup of the automation server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES. Launch Device Administrator and add the automation server. Select the automation server and click on the Upgrade Device button in the top left corner.  In the Upgrade device window, choose "New database" in the Type of upgrade field. Click OK. Once the download is complete, log into the automation server and restore the database. See How to restore a StruxureWare Building Operation server backup set. Now add the automation server underneath the enterprise server.

Issue Database maintenance has been keeping the event and extendedlog tables trim and someone decides they want to see data from a period of time that has been truncated from the Database. Environment Continuum Cyberstation SQL Server ActivityEvent AlarmEvent ErrorEvent ExtendedLog Cause Table truncation scripts have removed the events that a report is to be populated with. Resolution We can run reports on user activity and access event activity going back only as far as the information that is stored in the Continuum Database. This information is stored in specific tables that are normally truncated on a regular basis. The amount of time this information is saved for may be different for each installation.  (See articles Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table and How to setup automatic table truncation on Single-User SQL Express systems on how this is setup on a single-user system.) However, there is one possibility to being able to provide this information. If there has been a vigilant database maintenance schedule maintained and there have been periodic backups of the ContinuumDB, then the information stored in those backups can be retrieved and reports can be run. This would require a setup of a separate Continuum system (SQL Server and Cyberstation) that is able to have these backed up Databases restored to it. Restore each backed up copy of the ContinuumDB Run the required reports against this offline version of the Database. Do this one Database at a time until all the required data has been gathered.  

Issue How to integrate I/NET with Pelco Analog Matrix in order to implement some features, such as: Switch specific camera image to specific monitor. Switch specific camera to specific preset and display it on specific monitor. Product Line TAC INET Environment I/NET Pelco CCTV system Pelco Matrix Cause In some projects there is demand for access control system to integrate with analog CCTV system to do the alarm interaction. I/NET can integrate with Pelco CCTV system with ASCII code communication. Resolution I/NET communicates with Pelco analog CCTV system through ASCII code. There are two kinds of communication port for Pelco matrix, which are RS232 and RS485/422. For RS232 port for matrix, an RS232 to RS 232 cable is needed. If there are no COM ports for computer, an USB to RS232 converter is needed. For RS485/422 port for matrix, an RS232 to RS485/RS422 converter or USB to RS485/422 converter is needed. Connect the I/NET server to Pelco matrix through this converter, and the steps below should be followed: Open the I/O Configuration of I/NET, and choose the port for text output port and baud rate for the port communicating. In the AMT, choose Edit--->Text Library, and click Add. Choose a point for alarm interaction, and the status of the point to activate the interaction: alarm, acknowledge, return to normal (RTN) and acknowledged/return to normal (RTN). In the text area, enter the ASCII code for matrix. For the two applications of the alarm interaction, different ASCII code should used: 1Ma1#a, which means switching 1# camera image to 1# monitor 1Ma7#a1\\a, which means switching 7# camera to 1# preset and display it on 1# monitor. Here "\a" is an escape sequences for I/NET, so we need one more "\". Then the integration with I/NET and Pelco CCTV system is finished. When the specific point goes into alarm, then the specific camera can be switched to specific preset and displayed on specific monitor. For more applications of the integration with Pelco analog matrix, refer to the documentation for the Pelco ASCII Protocol Manual. And for more information about how to set text output in I/NET, refer to Text Output through RS-232 Port in I/NET.

Issue Controller regularly warmstarts or resets every 5 minutes. The site was upgraded from a BAS system Product Line Satchwell Sigma Environment Sigma Controller 1 warm start BAS Wireshark Cause In Sigma each device (server, controller and DNN) must be unique, in BAS this was not the case as terminal and outstations could share the same number. The resetting controller is receiving requests for files or alarm data that was previously routed to a BAS terminal, the Sigma controller does not handle the data and resets/warmstarts.  The previous BAS terminal number would have been the same as the controller number, typically T1 and OSN1.  When upgraded to Sigma the BAS terminal number would have been changed to a new designation but some of the system configuration has not been updated correctly. Resolution Alarm routing:  Check that all the alarm routing in the object files (R1, R2, R3, and R4) are set correctly.  Some systems use single destinations such as T1, if this is found and the destination number matches a controller number then this must be changed. (See Node reset messages are received at regular time intervals after a BAS 2800+ to Sigma upgrade) To search for possible incorrect routing destinations use the latest Sigview utility and search for any alarm routing that matches a controller number. Note: Typically device number 1 is the issue, but this may not be the case in all situations and another device number may have been duplicated. Operlist.txt Files: Check that all the operlist.txt files have been modified to the latest version and none contain the older BAS format. For example the wrong entries are; 1 C:\Bas\Data\OSN2\ROUTESET.REC    ROUTESET.REC 1 C:\Bas\Data\OSN2\LOOKOSN.REC     LOOKOSN.REC 1 C:\Bas\Data\OSN2\PNTFLE.REC      PNTFLE.REC With Sigma can be; ;This is a dummy OPERLIST.TXT   (Note: CRLF (Carriage Return & Line Feed) after the line) The dummy operlist.txt file will be created automatically by Sigma if the existing operlist.txt file is deleted from the server and then a download to the controller is performed. Default/Backup server number: Using the Diagnostics - View Comms Stats, check that all the controllers on the system do not have the default or backup server number configured the same as a controller number. Logging Servers: Using the Diagnostics - View Logging Servers, check that no logging data sets have been created with a server number matching an existing controller number. Wireshark Trace: If neither of the above help then it may be possible to look at the Ethernet data packets being received by the controller (obviously will not work if the controller is on an ARCnet LAN).    Set up a laptop with Wireshark (see Using WireShark to analyse communications on an Ethernet network) with an Ethernet hub at the controller. Run the trace until a reset/warmstart is observed at the controller Save the trace and email to Product Support or add and apply the following filter to show only those data packets being sent to the controller: ip.dst==192.168.2.1   (Change the IP Address to match that used by the controller) Look for packets that appear to come from another controller (source IP address).  For example below shows a request for the Lookosn.rec file on controller 1 (fault with operlist.txt file).

Issue DBCreate unable to run after installation. If installing I/NET on new PCs or upgrading to 2.42 and DBCreate does not start after selecting it from Programs > I/NET > DBCreate. Product Line TAC INET Environment SQL 2008 Server 2008 Windows 7 Windows XP Cause The SQL Browser needs to be enabled in the Services to get it to run. Resolution Run the SQL 2005 Backward Compatibility 64-bit option or 32-bit based on the OS. Restart I/NET Configuration Editor Modify the active profile and click on the Connections button. Verify that the database shown is the correct one that is being connected to and click on the okay button. Start I/NET again and verify that you can login and start the program again. See Initialization Error when starting I/NET for information that may also be helpful.

Issue In earlier releases of continuum Pre Windows 7, The Badge software would attach to the cameras and import a photo directly to the Badge without any additional cost. Canon's SDK for the Powershot cameras is not compatible with Windows 7 Canon's SDK for the EOS line of cameras is compatible with Windows 7 but requires  a license in order to import photos directly into the badge. Product Line Andover Continuum Environment Windows 7 Continuum 1.94 Cause There are a limited selection of cameras that are supported and qualified with Epi Canon's SDK for the Powershot cameras is not compatible with Windows 7 Canon's SDK for the EOS line of cameras is compatible with Windows 7 Resolution See related article, An Epibuilder Plugin is necessary for some badging devices to work. Camera (Face) Options: Canon EOS Camera (high end cost / higher functionality) Tested on Windows XP Pro SP 3 & Windows 7 Pro Models currently tested: EOS Rebel XS and EOS Rebel T3 Interfaces through the EPI Canon EOS capture plug-in license

Issue Vista reports fail to save to the server when they are being edited from a remote workstation. Product Line TAC Vista Environment Vista Microsoft Excel Cause When setting up remote workstations on a LAN or WAN, there are certain steps that must be taken. If the proper DCOM settings are not set up on every remote workstation as well as the computer that runs Vista server, there can be authority issues. Vista reports can be created but will not allow values or trends to be saved into the report. In some cases this has generated the error "The RPC Server is unavailable" as seen in Error: The RPC server is unavailable. Resolution On ALL remote workstations and the main server: Run DCOM Config 1.0.2.2.exe found in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Either select Server-Workstation or Server-Workstation-Webstation. On the main server that will be used to run Vista Workstation: Run > dcomcnfg Expand Component Services Open Computers Right-click My Computer and choose properties Go to COM Security pane For Access Permissions and Launch and Activation Permissions choose to edit both Edit Limits... and Edit Default... Add users Anonymous and Everyone with Remote Access Go back to Component Services and open My Computer Open DCOM Config Browse for OPCEnum right-click and choose properties Go to Security pane Change the three options to Launch and Activation Permissions   -Use Default Access Permissions                        -Use Default Configuration Permissions                -Customize Choose Edit > add Anonymous and Everyone with Remote Access Go back to DCOM Config and browse for TACOS right-click and choose properties Go to Security pane Change the three options to Launch and Activation Permissions  -User Default Access Permissions                       -User Default Configuration Permissions               -Customize Choose Edit > add Anonymous and Everyone with Remote Access