Building Automation Knowledge Base

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 There may be cases when the personnel distribution table in the ContinuumDB becomes corrupted and must be truncated. Product Line Andover Continuum Environment CyberStation Cause Table corruption issues. Resolution WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Should an issue arise in Continuum that requires a cleanup of the PersonnelDistribution table in the Continuum database follow this procedure to truncate the table and re-populate it. Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. In SQL Management Studio execute the following query. truncate table PersonnelDistribution Once the table is truncated it must be re-populated by one of the following methods... If the total number of personnel objects is reasonably small (in the hundreds) launch Continuum and bring a list view of all the personnel objects, select all then right click and perform a 'Send to controller' OR In SQL Management Studio Invoke the stored SQL procedure that initializes the PersonnelDistribution table using the query dt_DIST_Init_Personnel_Dist_Table IMPORTANT: Truncating the PersonnelDistribution table will remove all pending personnel distribution including personnel deletions; controllers could potentially continue to allow access to doors for the deleted personnel until reloaded. Conversely, removing a pending personnel distribution could potentially cause a person to be denied access at a door until a distribution is performed to the controller.

Issue Equalize Client does not work in Windows 7 64-bit with I/NET 2.42 Product Line TAC INET Environment Windows 7 64-bit I/NET 2.42 Cause It could possibly be related to the Windows Firewall settings. But typically it is due to the differences between the installed 32-bit version of SQL and the 64-bit operating system. Resolution Make sure that the Windows Firewall is not set to block the connection The SQL 2008 Express that is included on the I/NET Seven CD is a 32-bit version. If you are running a Windows 7 64-bit OS, then this involves going to the Microsoft Web Site and downloading the SQL 2008 R2 Express.  The MS site link to this is: http://www.microsoft.com/en-us/download/details.aspx?id=3743 The file you need to load is: SQLEXPR_x64_ENU.exe To verify what version of SQL 2008 is loaded on the PC: Go into DbCreate Select the “About” Option If the SQL listed here IS NOT the 64-bit version, un-install I/NET Seven and SQL 2008 Express. Do not forget in Window Explorer that there are TWO Programs Files Folders on the root directory you have to remove. If the SQL 2008 is NOT correct, then go to Step 3. If the SQL is the correct version then proceed to Step 4. NOTE: If you need to upgrade the SQL Server versions (including Service Packs) make sure you force an Upgrade (via DBCreate) to ensure the I/NET database now conforms the version of SQL installed.   Once you copy the SQL on to the PC then follow the Steps outlined in Installing I/NET Seven on a 64-bit operating system. This will guide you through loading the SQL2008 R2 Express and the I/Net Seven rev 2.42 and above. Make sure that the PC you are working on you have Windows "Local Admin" Rights On a Windows 7 64-bit PC there are two C:\Program Files\Inet Seven folders located on the root directory. One of the folders, C:\Program Files\Inet Seven, you should ONLY see three files in this folder. These are:  IEShims.dll, INetEqzCR.dll, INetEqzMerge In C:\Program Files\Inet Seven (x86), you should see all the normal I/Net Seven files and the DOC folder. Please note that the INetEqzMerge does not exist in this folder. You should NEVER copy it in this folder. You need to verify that the InetEqzMerge is listed in the Windows Services directory. If this file does exist, make sure that the properties are set to the Automatic mode. If not, set it to Automatic mode and reboot the PC. If by chance the “INetEqzMerge” does not exist in the Windows Services, you need to do the following steps to get this corrected. INetEqzMerge Fix: Load I/NET Seven CD into the PC and start Windows Explorer. Then open the CD to this location (For I/NET 2.45 or later version, they are located under CD\program files\INET Seven\INSTALL_64BIT): Click on the file shown above, this will activate the 64-bit install process again. Please note after you run this program you must reboot the PC After the reboot process, go to the Services editor and verify that the INetEqzMerge did install. Make sure that this file is in the Automatic mode. If it is not, choose the Automatic mode, and reboot the PC again. Now you can Promote the Equalized Client PC. If Manual mode is used for the promotion process, it works better than the Default mode. Also, use the IP address of the File Master instead of the PC Name.

Issue Report setup to automatically save to unique files in an output directory is not working. When ReportCmdLine.exe is used to save the report output (see Automatically Running Continuum Standard Reports) only a single file is created and overwritten each time. Product Line Andover Continuum Environment Continuum Cyberstation Continuum Report object Cause The name of the Report object being run has a period (.) in its name. Resolution Rename the Report object removing the period from its name. The Report output will now save a new file with date and time in the filename each time it is run.

Issue There are a few different stem heaters to choose from. Product Line Field Devices Environment 8800108000 8800109000 8800110000 8800112000 Stem heater Yoke heater Cause Depending on application, there are a few different stem (yoke) heaters to choose between for the Forta actuators. Resolution When Forta series actuator is used with a Venta valve, stem heater part no 8800108000 should be used when media temp is 0°C to -20°C. Note: This stem heater is not compatible with the M700 actuator.  If used with V321 DN65-100, stem heater 8800110000 should be used. If used with V222 DN65-100, stem heater 8800112000 should be used. In other applications, yoke heater part no 8800109000 for Forta should be used. Capacity for the yoke heater is: Ambient temp  down to -10°C or media temp down to -8°C  For more on stem heaters, see Stem heater for V222/V292.

Issue When using the "Commission and Download" command in Vista Workstation the controller being downloaded is failing with a "Completion Event Failure" and has multiple "Waiting for unit to restart" error messages. Product Line TAC Vista Environment Vista Server/Workstation Classic Network Cause The controller being downloaded and presenting with this error message typically has been functioning and communicating on the network and an application update is being downloaded. The unit is busy responding to other communication (TAC network variables, Xenta group communication, etc) and can not devote full attention to the application download. By setting the neuron status to unconfigured, the controller can focus only on the application download. Resolution Right click on the Xenta programmable controller and select Advanced Operation > Neuron Unconfigured. Right click on the Xenta programmable controller and select Commission and Download. It is unnecessary to set the Neuron status back to Configured because this is part of the Commission and Download process. Similar steps are available for a LNS network and are discussed in "Completion event failure" and/or "Waiting for device to restart" errors when downloading a previously commissioned controller.

Issue How can a Viconics BACnet thermostat instance number be changed with Niagara G3? Product Line TAC IA Series Environment Niagara G3, ENS, ENC-520 Cause The device Default Device ID is set to: 7x000+MAC address. The MAC address being the current Mac address of the BACnet device. Example, when a VT7300C5018B thermostat with a MAC address of 7 is connected to a network, its default Device ID will be 73007. There will be Device ID conflicts when the same Viconics model is used on multiple MS/TP networks and uses the same identical MAC address. Resolution How can the instance number be changed in a Viconics BACnet thermostat? lists how to change the Device ID (instance number) via the Viconics thermostat. However, it only allows for change of the MAC address portion of the Device ID. When changing the MAC address portion of the instance number is not enough, Niagara G3 can be used to change the entire instance number. The steps to change the Viconics thermostat instance number are as follows: Open (double-click) the BACnetNetwork Under the Database window, highlight the Viconics stat you want to change the instance number Click on the DeviceID button at bottom of screen and click yes Highlight the DeviceID number and change it to the desired number and click OK This screen show the device number it is being changed from to the device number it is being changed to – click OK If the change was successful, you should get a pop up stating: "Successfully changed remote device ObjectID!"

Issue The customer (or others) have performed Ethernet penetration tests and some controllers have reset Product Line Andover Continuum Environment Ethernet Controllers Netcontroller Cause Some earlier versions of firmware include vulnerabilities to broadcast storms or DOS attacks. Resolution The following firmware versions have fixes that relate to resetting of controllers due to unusual Ethernet Activity. Those shown are not always the latest version and it is best practice to use the latest firmware available on all sites. The following controller versions and above: bCX 4040 (BACnet) bCX1-INF 9640 v1.200025 Netcontroller CX99xx v1.5300026 Netcontroller NC2 CX9680 v2.100035 ACX57xx v1.100037 CX9702 v1.200036 All firmware compatible with Continuum v1.90 and later. Previous versions not shown, but all the information required is available from the firmware release notes See Continuum controllers go offline during a broadcast storm

Issue Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server Shadow Schedule in the ES syncs successfully to Lead Schedule in the AS Lead and Shadow Schedules in different AS are syncing successfully Product Line EcoStruxure Building Operation Environment SmartStruxure 1.x Cause Traffic is blocked by Windows Firewall.  Resolution Disable Windows Firewall. Disabling the firewall may not be possible due to security concerns, Exceptions can be added to Windows Firewall for ports that are used by SmartStruxure. Refer to Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port for details. If this doesn't work, please refer to Shadow Schedule in AS isn't synchronized with the Lead Schedule in ES.

Issue The demo license used to access the OPC server configuration must be removed from the license Files folder in the new Flexnet License Server for the service to start. Upgrade to a Vista 5.1.8 will not allow access to the OPC Server Configuration. Product Line TAC Vista Environment Vista 5.1.8 using 3rd Party OPC where Vista is a client Cause Vista.OPCTool = Allows accessing the OPC Server for configuration Vista.Server.OPCClient license= Allows a connection to get the configured OPC points into Vista. Systems engineered to use 3rd Party OPC Server may only contain a Client license for connectivity, using the Demo for the initial configuration and servicing of the OPC Server. In Vista 5.1.8, the  Flexnet License Software  will not allow a Demo license to be present in conjunction with a Site License. This is corrected in Vista 5.1.9. More information can be found in License troubleshooting in Vista 5.1.8 or greater. Resolution Purchase the Vista.OPCTool to add to the existing Site License file. Best practice is to have a separate folder for your demo licenses, and reference the physical path to that folder. See below:  WSDKHE9781;C:\Program Files (x86)\Schneider Electric\License Files Demo

Issue When using the LPA through an Automation Server (AS) as described in Using Loytec LPA with SmartStruxure AS, only traffic to and from the AS is captured. Product Line EcoStruxure Building Operation Environment LPA Automation Server Cause Due to a hardware limitation in the AS, it's not possible to capture all traffic on the segment Resolution Connect the LPA to the segment using a NIC-USB100 or similar

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.