Building Automation Knowledge Base

Issue When using multiple .lic files, Vista Licensing Server can  have issues reading all the files. If the license features were not purchased on the same Entitlement, manually consolidating the licenses into one file will be necessary. Product Line TAC Vista Environment Licensing FlexLM Vista Cause Multiple licenses not read which results in purchased features not unlocking. Resolution   Open the .lic files in Notepad, Wordpad or text editor of your choice. Verify that each license to be consolidated are entitled to the same MAC address or Dongle.  Line 2 of the files should all have matching "Server This_host xxxxxxxxxxxx" Chose one of the files to become the "Master" Copy and paste the "INCREMENT" contents of the files at the end of the "Master" The final result will be a file with one "Header" and listing all of the features below.

Issue Errors occur when trying to open up graphics in Vista Workstation similar to these: Microsoft .NET Framework Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. A generic error occurred in GDI+. TAC Vista Workstation Encountered an improper argument. Environment Windows 7 Windows XP Vista TGML Cause Installing Windows XP on a machine that came pre-installed with Windows 7 has been observed to cause this problem. Resolution Computers that are sold with Windows 7 pre-installed typically have hardware that is optimized for Windows 7 and often experience a variety of problems when they are re-imaged to Windows XP. The best solution is to re-install Windows 7. TAC Vista 5.1.4 and newer is compatible with Windows 7 as well as some third-party LNS network tools (check manufacturer's websites for more information). Windows 7 Professional, Ultimate and Enterprise can run programs using "XP Mode". XP Mode is a separate download available for free from Microsoft's website.

Issue Individuals added via Datacard ID Works are not getting access to doors Product Line TAC INET Environment I/NET ID Works Cause I/NET uses audit trail messaging to ensure that ID Works data is broadcast out to the site. Resolution Open AMT Select Edit>Configuration Note the Group 1 Masking Settings Open I/NET Select Access>Options Select Group 1 for Audit Trail Messaging Ensure that the masking for Audit Trail is set the same as the AMT Configuration Select Edit>Host Computer>Network Configuration Choose the Link that is connected to the Video Badging PC Verify the Host Number Set up Automatic DPU Restore Function. 's means of communication, then make sure that the Host Masking is set to match the AMT Masking for Group 1 If you are still having issues make sure you are using the correct ID Works Template The Templates are available on the I/NET CD in the Support Folder If you are using your own template ensure you have these required fields: IndividualId TenantName GroupName RecType TempStart TempStop TempStartDate TempStartTime TempStopDate TempStopTime IssueLevel

Issue Saving station information within the I/A Series R2 Niagara Application Tunneling dialog window generates the following error: Windows Shell Common Dll has stopped working. This occurs when attempting to configure and use the tunnel client on a Windows 7 32-bit operating system. Environment I/A Series R2, LON Tunnel Client, Serial Tunnel Client Cause I/A Series R2 Tunnel Client dll file compatibility and Windows 7 operating systems. Resolution Configure the Niagara Application Tunneling dialog box with the station information as required. For the serial tunnel, select a valid COM port and enter the host address, username, and password.  For the LON tunnel, select a valid LON port and enter the host address, username, and password. NOTE: The tunnel client must be configured for Silent Mode. Select OK to save the data. Following dialog box is displayed indicating Windows is checking for a solution to the problem. The workaround involves selecting Cancel prior to the Windows timeout notifying the user to Close Program. Selecting cancel prior to the Close Program timeout saves the station information within the Application Tunnel.

Issue Adding a device through the System Plug-in results in missing SNVTs, SCPTs, or Module/Functional Block Names in the Vista database. Environment Vista 5.x.x Cause The XIF file is either incorrect or parsed improperly. Resolution Right click on the device and select properties. Click on the XIF file tab. View the XIF file name (this can be found in the $thisfil directory of the Vista database) and either browse in a renamed copy of the existing file or an independent copy of the file by clicking the ... button. Click Ok Log out of Workstation Log into Workstation to see the changes. Note: For a change to be detected the filename or location of the file must be different.

Issue The software is no longer distributed on a CD.  Customer wants to install and license the software on his computer. Environment TreeTech 3.1 Network 8000 GCMs DMS panels Cause None. Resolution Download the software "TreeTech-3.1.exe" on The Exchange Download Center. Install the software by running the downloaded program file and following the displayed prompts. Run the "Purchase WIBs" program from the computer desktop.  This icon and program will be automatically installed on the computer if it does not already exist. Click the [Purchase] button to start the program. Fill out the Field Office and Customer Information parts of the form.  Make sure to fill in your purchase order number in the indicated field. The installer should also fill in his email address for emailed return of the installation codes. From the "Package List" section of the form, select the TR-TECH software and required drivers, selecting each from the list and clicking the [Add to Order] button. To request the license for the base TreeTech software, select TR-TECH. To request a license for using serial communications between TreeTech and Network-8000 GCMs or DMS panels, select IOS-SRL. To request a license for using Ethernet communications between TreeTech and Network-8000 GCM-86xxx series panels, select IOS-NW8-ETH. To request a license for using Ethernet communications between TreeTech and DMS-3500 panels, select IOS-DMS-ETH.  NOTE: At least one communications driver must be selected. After completing the form, click the [Accept Order] button and save the order form to a text file.  Click the [Done] button to save the requested license options to the computer and click the [Done] button on the WIB Purchase screen to exit the program. Email the saved license form to IASeries.WIB_Order@schneider-electric.com.  The requested unlock codes will be emailed to the address specified on the form after the order has been entered and processed.  Allow two business days for processing.  While waiting for the unlock codes, the software can be used with the automatically installed demo mode license.  The demo mode license is valid for 30 days from the time the first WIB software product is installed on the computer. When the purchased license unlock codes have been received, they must be installed using the [Unlock] function of the "Purchase WIBs" program.  After opening the program and  clicking the [Unlock] button, select one of the requested license products, enter the corresponding unlock code and click [Generate License].  This process licenses the software onto the computer and removes the product from the displayed list.  Repeat this process for each additional product license shown on the screen.  Each provided unlock code will be used only once.

Issue Adding a new logging database and making it current. Environment BAS 2800+ BAS2800+ Logging Database Cause Creating a new database Resolution From the System Manager carry out the following. Open DataView and select Data / logging Databases. The screen will show you the existing databases. Choose “Add” and enter the name you require. Select to “make Current” the new database. The database will now store any new data returning to the Terminal.

Issue How to register LonTalk Protocol Analyzer Software Product Line EcoStruxure Building Operation, TAC Vista Environment Vista LPA Cause The LonTalk Protocol Analyzer software is a tool for LonWorks network troubleshooting. There are two kinds of LPA license. Some customers may be confused about it. Resolution To use the LPA, you need to purchase the software license. There are 4 kinds of LPA license. Refer to this page for further explanation. LPA-SW: This license is bound to NIC709-USB.  Need to use specific NIC709-USB to be the network interface of the software. LPA-IP-SW: This license is bound to NIC852. Need to use specific NIC852 to be the network interface of the software. LPA-IP: Same as the above, but includes a dongle.   The steps of registration for the current version of LPA using the current NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec's Website. Open the LPA program Click on "Help->Register Product"   Enter the Registration Code in the product package, and click Add.   The steps of registration for previous versions of LPA using the previous NIC driver is the following: Install the drive for the LOYTEC Network Interface. Refer to Loytec Website. Open the LConfig program.   Click Register / Activate to open the registration window. Enter the Registration Code in the product package, and click Add. Then the registration is finished. Open the LPA software to test whether the license works fine.

Issue When downloading an XBuilder project (Send to Target) a window pops up with three send options: Send all project and language files Send all project files Send modified project files What is the difference between each of these and when is it appropriate to use each one? Environment XBuilder Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause Knowing what each option does and when it's best to use each one can save a lot of time in troubleshooting integrations and general operations of a Xenta Server. Resolution Send all project and language files This option is very rarely used. The only time it is necessary to send language files is when the display language inside the Xenta Server is being changed (e.g. from English to Polish).   Send all project files If there was a default operation to always use, it would be send all project files. It will always perform the desired operation. However, it always prompts a reboot of the Xenta Server. Communication with the Xenta unit will be interrupted for ~2 minutes while the reboot occurs. If a lot of quick changes are being tested, this can add unnecessary time to the task. However, the reboot is sometimes desired. Especially when making small changes to integration device templates, a reboot will ensure the changes take immediate effect. In general, if a change has been made to the Network pane in XBuilder, all project files should be sent.   Send modified project files Send modified project files when minor changes to the System pane have been made. Adding a values page, editing a time object, deleting a graphic page. These are all changes that can be sent with only modified project files. This will not reboot the unit and will allow for faster editing of the project.

Issue Step by step instructions for installing and configuring a Loytec NIC852 dongle, also known as an Orion Stack. Environment Vista LNS Network Echelon LonMaker Cause A single Vista server can handle communications to about four "average" sized LNS Networks. Very large networks or many LNS ports in a single server may result in a degradation of communication reliability. An Orion Stack changes the way Vista communicates with the LNS Server and allows up to 28 LNS Ports to be added. Resolution NOTE: If LonWorks Interfaces was previously configured as your Network Interface you must delete the computers IP address from the IP-852 tab before you continue. Insert NIC852 Dongle into USB slot on Front-End computer.  This dongle must be plugged in at all times for the Orion Stack to work. Use the Loytec CD to install the necessary software to use the dongle such as hardware drivers and the LConfig interface Make sure that the latest drivers are installed for the NIC Interface.  The latest drivers can be found at:  http://www.loytec.com/index.php?option=com_docman&task=cat_view&gid=116&Itemid=25 When properly installed, the Loytec symbol should appear on the bottom right corner of the Windows Toolbar.   Right-clicking on the symbol will allow you to easily access the LConfig interface.  Click on LConfig to configure the NIC852 (Orion Stack) Using the LConfig interface, navigate to the NIC852 tab and check the box next to enable the device.  The transceiver should most likely be set to IP-10L and the number of LNS Applications should be selected (aka, the number of LNS databases) Click CNIP configuration to set up the IP addresses for the Device (aka..The Front-End Computer IP address) and the Config. Server’s IP address.  * Don’t forget to enter the Device Name (aka Computer Name).  Click “Ok” twice and the device should be configured.  Test it before closing out. With the NIC852 configured, open Lonmaker and open the first drawing directory with “Show all network options dialogs” checked. When the Network opens, click ‘Next’ to configure the Network Interface.  Check the box next to ‘Network Attached’ and select the first NIC_852 entry.  Click next to let the network configure.  Go through the rest of the windows by clicking ‘Next”, save the drawing, and exit. The network interface for each LNS can also be chosen by going to Lonmaker > Network Properties in the Visio drawing and utilizing the Network Interface tab. Next, set the Communication Port for the TAC Network to look for a Loytec device.  To do, this open ‘TAC Vista System Plug-In’ which can be found at Lonmaker > System Plug-in > TAC Vista System Plug-In.  In this window, right-click the Network (top of the controller tree under the TAC Network) and click “Settings.” When the ‘TAC Network Settings’ window opens, under the Network tab select “Communication Port-Loytec” and click OK.  The TAC Network will have to be updated after this.  Repeat Steps 6-10 for each LNS database.  Remember to select a different Network Interface each time. After configuring the NIC for each LNS Database.  The Orion Stack should be properly setup.  * Note:  It is a good idea to note that an Orion Stack is installed on the main graphics page for the site to keep other potential users informed, like remote support engineers.

Issue The "Host Mask" "NP Routers" "Advanced IP" and "CCTV" Buttons are grayed out in I/O Server Editor Product Line TAC INET Environment I/NET Seven rev 2.40 and 2.40A through current release Windows 7 32-bit Cause Issue 1. There is an issue in Windows 7 and running I/NET Seven 2.40 or 2.40A in the Service Mode. Please note this is unique to Windows 7 Only. This does not occur in Windows XP Pro. Issue 2. When editing the Configuration Profile, "Host Mask" "NP Routers" "Advanced IP" and "CCTV"  are not available Resolution Issue 1. There are two solutions to this issue: Leave the site at I/NET Seven rev 2.40 or 2.40A and change the operation from Service Mode back to Application Mode. Upgrade the site to I/NET Seven rev 2.41. With this load the operation can return to Service Mode. Issue 2. When I/NET I/O server is not running, or you select Start/Programs/I/NET/Configuration Profile the configuration profile is like the screen shot below.  Starting I/NET starts the I/O Server which is visible on the tool bar by the clock. Right clicking offers the below menu: Select Configure from this menu and modify the active profile enables the Host Masking, NPR Routers, Advanced IP, and CCTV.

Issue Endura DVR missing the Video in I/NET Seven Rev 2.41 Product Line Pelco, TAC INET Environment I/NET Seven rev 2.41 Endura DVR Cause The Endura Workstation software that comes with the DVR (by default) is set to "Multicast". If this has not been changed, then you DO NOT have to change the three I/Net files listed below. If the Endura Workstation software was changed from the default (Multicast) setting to a "Unicast" setting. Then you WILL have to change the three I/Net files listed below. What is the Pelco definition of “Multicast” mode? By default, Endura encoders and Pelco network IP cameras are default to stream live video in Multicast mode. A common symptom of multicast routing issue is where the date and time stamp can be seen on the workspace but the video is black. This symptom is commonly associated in a layer 3 routing network where appropriate multicast routing protocol has not been enabled globally or inside the VLAN. Resolution The resolution is to modify three files that are installed with I/NET Seven rev 2.41. These three files are located in this directory on the PC – C:\Program Files\INet Seven INetAMT.exe.config INetCfg.exe.config INetW.exe.config Note: If the above three files are not in the I/Net folder, then you have not delete the previous SDK driver. You must delete the previous driver thru the "Add and Remove" option in Control Panel. Once removed then go into the I/Net CD and select the "Support" folder and manually load the new SDK Driver. Then proceed with the rest of the process in this article. Use Notepad to open each one of these files one at a time and change this setting from the "default" of "False" to "True." After making all of the changes in the three file, shut down the I/NET and IO Server ICON. Restart the I/NET again, and the Video should show up in the I/NET program

Issue Opening an MTA file in Menta causes an "The device type is not supported" error message. Environment Menta 5.x.x XBuilder 5.x.x Cause The Menta file is for a Xenta 700 controller and cannot be opened in stand alone Menta which only supports the Xenta 280, 300, and 400 series of programmable controllers. Resolution Import the MTA file into an Xbuilder project's Menta Library in order to edit or view the MTA file.

Issue When attempting to start the programme an error indicating that the communications port is already open, is generated. Environment BAS 2800+ BAS2800+ Sigma Visisat Comms port open Comm 1 Cause The communications port is already being used by another programme. Resolution One of the most common programmes to cause this issue is Microsoft Active Sync, if this is found to be installed, either disable it or remove it if the programme is no longer required. The screen shot below shows the Active Sync connection settings window.   Ether change the Serial port number or de-select it. If Active Sync is not the problem, then disabling communications port 1 in the system Bios, may cause the programme to generate an error when it starts up. Once the programme is identified it can be disabled. The System Bios is accessed during start-up by pressing the F2 function key. You should then follow the on-screen instructions.

Issue How are devices added or removed from the monitored list? Environment Sigma 4.05 4.05 SEB Device Monitor Adding Removing Cause Confusion over how devices are added or removed. Resolution To add devices to, or remove devices from, the monitored list is achieved as follows: Enter Sigma "System Setup" and select "Networks and Devices". Select the "Zone Name" and choose the "Device Monitor" tab. The  screen shot below shows the devices being monitored, this list is formed from the DeviceCNF.rec file. To prevent a device from being polled, tick the appropriate "Omit" box. To add devices select the "Add" button, complete the device name and IP address.

Issue Adding a "Short Form Edit" command to a User Menu. Environment BAS 2800+ BAS2800+ Short Form Edit User Menus Cause This option is not available by default. Resolution The add this option select "System Setup / User Menus" Select to create a "New Command" Complete command details as shown below. Having created this command add it to the required menus.

Issue The G3 icon for "Start, All Programs, Enterprise Network Server 3.x., Install Platform Daemon" is missing. How to locate and run the file? Environment I/A Series G3 Workbench, all builds Cause The I/A Series G3 icons that were automatically installed in the pc Start menu are missing. Resolution 1. On the drive where I/A Series G3 Niagara is installed, go to C:\niagara\niagara-3.n.nn\bin\plat.exe installdaemon. 2. Double click on the file plat.exe to run the executable file.  

Issue Receive PARSER IO ERROR 13 when direct serial downloading a Xenta 401 controller. Environment Menta Xenta Cause Physical IO points in a Xenta 280 or Xenta 300 menta application are assigned to M0-X1, M0-U2, etc, and when these physical IO points are copied to a Xenta 401 or Xenta 401:B menta application M0 does not exist. Because these points were copied into the menta application and not created within that application or imported as a library file, simulation mode will not check this IO terminal error. This situation will show itself by failed downloads in the system plug-in, and PARSER IO ERROR 13 when direct serial downloading. Resolution In Menta select Options>IO Configuration Table. Click the "bound to" column to sort by physical IO within the menta file. Look for points with the M0 reference similar to the screen shot below. Set these points to the proper physical IO terminal for the application.  

Issue IC or Gateway returning default values. Modbus, SNP, Unifact. Environment Sigma IC's and IC3's, BAS PIU's. Modbus SNP Unifact Cause In Sigma the following is displayed: Note the default value displayed will be the default value set within the object. Resolution There are a number of causes: Ensure that no additional spaces have been inserted. Select all of the gateway.txt with the cursor to reveal any extra spaces. Separators within the input and output fields should be a comma (,). User comments e.g. "Temperature Sensor", "Setpoint" at the end of a input or output line are commented out using a semicolon (;). In some gateway.txt the IC/PIU communications need to be set e.g. Modbus. Make sure these match the 3rd party's network. In the Modbus IC, ensure the gateway.txt is set to modbus or crompton as required. To simplify the problem solving process: Use one gateway.txt entry and one connected controller on the 3rd party's network Disconnect the remainder Choose a mapped point in the 3rd party controller with a known value. Once working, the remainder of the controllers can be added along with the points to be mapped.

Issue After Vista system commissioning finished. Site engineers need to move Vista database from engineer laptops to site PC. Sometimes Vista database export & import needed. Engineers found some time schedule or setpoint (PVI / PVR / PVB) returned to initial value, not the value they changed during the commissioning progress or customer defined later. Environment Vista Menta Cause Vista may not save customer changes to the Menta file sometimes. Therefore, when exporting the menta file, those forced by operator values may not be carried along with. Resolution To save the latest setting of time schedule object or setpoint object in Vista database before export the database, make sure following steps have done. Right click on the Xenta controller and select "Edit" Input "username" and "password" after the Menta application window comes up. In the Menta application, click "Vista Database", select "Save", Make sure following window is displayed. If not, try making some modification in Menta, such as move a wire or block. Then click "Vista Database >Save" Repeat step 1 to 4 for those Xenta controllers which need export. In Vista Workstation, click "File > Database > Export" to export the desired networks / Xenta Servers / Devices. Copy the ZIP file to target PC, and Import the contents to the final system.