Building Automation Knowledge Base

Issue When opening I/NET and getting an Initialization failure error and unable to log on to start the program. Product Line TAC INET Environment I/NET Revision 2.40 and higher on Windows 7 PCs. Cause There was a security update that disabled the Named Pipes and TCP/IP that is required for SQL to run. Resolution Start , All Programs select Microsoft SQL 2005 or 2008 Expand Configuration Tools and select SQL Server Configuration Manager Select SQL Native Client Configuration and expand it then click on Client Protocols Verify that TCP/IP and Named Pipes are enabled Click on SQL Server 2005 Network Configuration and click on Protocols for MSSQLSERVER Verify that Named Pipes and TCP/IP are enabled Open up Services and verify that SQL Agent, SQL Server and SQL Browser are all running and set to automatic. Start the I/O Configuration and verify that the connection is made to the correct database Restart I/NET again and it should allow you to start the program now. For Remote Client with I/O Configuration: Repeat the above on SQL Server PC Ensure that port 50069, 1433 and 1434 are open between the PCs

Issue Use L-IP and NL220 to compose Vista LNS database. How to move the database from the engineering PC to the site PC? Environment Vista 5.X.X LNS Network NL220 Loytec L-IP Cause Due to the complexity of LNS network, it is recommended to follow the steps listed below to move the LNS database and Vista database from an engineering PC to a site PC. Otherwise, it may result controllers offline, Vista database opens extremely slow or freeze. Resolution NL220+L-IP is the most common combination for LNS network. How to move the database completed on the engineering PC to the site PC? The following steps can be followed: The software needed to be installed on site PC: Vista Server, Vista ToolPack, NL220.   A NL220 dongle is needed.  (The dongle does not need to be locked to the site PC for moving database purpose; however, it is recommended to have the dongle locked to the site PC for future maintenance purpose.)   Backup the LNS database on the engineering PC. (Select “Backup Project” in the NL220.)   Make a copy of Vista database.   Copy both backups (LNS and Vista) onto the site PC. NOTE: It is recommended to keep the paths of both databases the same. Otherwise, it may results graphic pages lost.   Specify the folder path of Vista Server on site PC to the backup database.   Add the L-IP interface in the Control Panel.   Plug the NL220 dongle onto the site PC. Open NL220, create a new project and select the interface as L-IP.   Close the project, select “Restore Project” and specify it to the backup database for NL220.   Open the NL220 project again and select the System Plug-in.   Update the LNS database to Vista Server in the System plug-in again.   Select the “Commence Communication” to start the communication.   Open TAC Vista Workstation. Then the LNS interface in the Workstation should be online. NOTE: without a NL220 dongle plugged in the site PC, TAC Vista workstation should operate normally. However, it is impossible to make any change to the LNS database.

Issue Although i2 infinet controllers were installed, when the site was built offline i1 Infinet controller objects were created. How can I change the Infinet controllers from i1 controllers to i2 controller?  Environment i1 i2 Infinet InfinityInfinetController Cause Programmer selects the wrong type of Infinet Controller objects. Upgrading from i1 Infinet controllers to i2 InfinetControllers. Resolution In Continuum 1.9 and up the Infinity controller model can be changed after the InfinityController object has been created.  Note: Some older versions of Continuum do not support all controller models.  Make sure the controller model you are installing is selectable under Controller Type in the controller editor. To upgrade to an i2 controller from an i1 Controllers Edit the controller Select the correct model number, enter the new serial number and apply. Reload the controller. Also consider any EMX Expansion modules fitted, these will need to be replaced by appropriate point count xP modules, the i2 controllers support a maximum of 2 modules.

Issue How do I calculate the pulse constant for an MNL-800 BI object configured for pulse input? The Pulse Constant is a user entered pulse scaling value used by the pulse algorithm for calculating the output based on a pulses per second frequency. The range of the Pulse Constant value is 0.1 to 1000. Environment MNL-800 Cause How do I calculate the pulse constant for an MNL-800 BI object configured for pulse input? Resolution Calculating the pulse constant requires the value to first be scaled to the equivalent pulse rate in seconds. Two examples are shown below. The first example represents a water meter that provides a pulse that represents cubic feet per minutes. The meter generates one pulse per minute that represents a rate of 10 cubic feet per minute. The pulse constant calculates on a per second basis so the first step is to determine what one pulse represents as a rate per second. 1 pulse per minute / 60 seconds = 0.0166666 rate per second Next, divide this value into the desired output when this pulse rate occurs. In this case, the rate value is 10 so the pulse constant is equal to 10 / 0.01666666 or 600. The second example represents an electric meter that provides a pulse that represents KW. The meter generates one pulse every 0.5 second that represents a rate of 15 KW. The meter will pulse twice every second (1 second / 0.5 second). The pulse constant is calculated by multiplying the rate value by 2 or a pulse constant of 30. A meter pulsing twice per second will generate an output of 30 KW. Reference the WorkPlace Tech Tool Engineering Guide - Binary Input object (F-26580) for more details.

Issue Most of the xDriver points provide bit (binary) information in a word(integer) point in order to save register address. In order to interpret/decrypt the bit information out of the word(integer) value, PE programming is required. Environment Net Controller (CX99xx, CX96xx) bCX controller (bCX4040) ACX5740/5720 Cause Bit information is displayed as a number in the controller when read in to.  Need to have PE function to decrypt the number in to each bit information. Resolution Create InfinityProgram in the Controller as below; ' = = = = = = = = = Numeric locNum1 Numeric nBit0, nBit1, nBit2, nBit3, nBit4, nBit5, nBit6, nBit7, Numeric nBit8, nBit9, nBit10, nBit11, nBit12, nBit13, nBit14, nBit15 Line ReadAndSet   locNum1 = CIAlarms ' Read the xDriver point and set to local point.   Goto AAA Line AAA   ' Decrypt each bit information from the locally mirrored point.   nBit0 = (locNum1 bitand 2 ^ 0) > 0     nBit1 = (locNum1 bitand 2 ^ 1) > 0    nBit2 = (locNum1 bitand 2 ^ 2) > 0  . . . . .    nBit15 = (locNum1 bitand 2 ^ 15) > 0    Goto BBB Line BBB   ' Do something here for each nBit0~nBit15 such as below   ' If nBit0 then   ' set InverterTempAlarm = On   'Set the global point to ON   ' Else   ' set InverterTempAlarm = Off   'Set the global point to OFF   ' Endif   . . . . . .    Goto CCC Line CCC   ' Wait for 15 seconds and send to the first line to read the xDriver point again.   If TS < 15 then Goto CCC   Goto ReadAndSet Line E   If TS < 30 then Goto E   Goto ReadAndSet ' = = = = = = = = =

Issue What is the format of the SNMP alarm traps and where can I obtain the MIB's Product Line Andover Continuum Environment Netcontroller II CX9680, bCX1 & ACX57xx with SNMP alarming enabled. Cause Documentation on the SNMP Alarming is required. Resolution The Configuration guide for SNMP Alarming can be downloaded from The Exchange Download Center, link: Andover Continuum v1.9 SNMP Configuration Guide This will detail how the SNMP alarming is configured and operates. The SNMP Alarming sends the same alarm messages as shown in the Continuum alarm viewer out to the third party system via SNMP traps. The format of the traps is defined by Management Information Blocks (MIB's) these can also be downloaded from The Exchange Download Center, click on the following link: SNMP MIBs There is no facility to change these formats within the controllers or Continuum

Issue R2, UNC-520-2 is Displaying “Authentication mismatch” error message for a MNL-800 controller.  How can this error be corrected?    Environment R2, UNC-520 Cause An “Authentication mismatch” error means that the authentication set in the in the LonWorksService does not match what is set in the MNL-800’s shadow object.  One is set to “True” and the other is set to “False”.  They should both be the same.  Authentication is rarely used due to the high overhead associated with its use, so we normally recommend it not be used. Because of this, “Authenticate” should be set to “False” in the properties of both the LonWorksService and MNL-800 shadow object. This error message applies to the MNL shadow objects as well.   Resolution To verify if Authenticate is set to true in the property of the LonWorksService: - Open the Properties of the LonWorksService and click on the Netmgmt tab. The Authenticate property may be set to “True” and grayed out. To verify if Authenticate is set to true in the property of the DynamicDevice: - Open the Properties of the DynamicDevice shadow object and click on the Engineering. The Authenticate property may be set to “True” and grayed out. To verify if Authenticate is set to true in the property a MNL controller: - Open the Properties of the MNL shadow object and click on the General tab and Engineering tab. The Authenticate property may be set to “True” and grayed out.   Steps to set “Authenticate” to “False”: 1. Disable Authentication using Command from the LonWorksService Property view       1. In WorkPlace Pro (WPP), open the station LonWorksService       2. Highlight the shadow objects that needs to be changed to “True” (or simply highlight all of them)       3. Select “Commands” from the WPP menu at top of page       4. Select “disAuth” from dropdown menu and select “Yes”              Note: An error may be displayed stating that the action failed even though it was successful. 2. Recommission each Lon device (if it fails to commission, reset the device then try again) 3. Rebind all affected bindings  

Issue What I/A Series BACnet hardware (MNB) is officially UL 864 listed? Environment MNB UL 864 Cause Many consulting engineers would like documented proof that the hardware within a smoke control system is UL 864 tested and approved. Resolution The Schneider Electric MicroNet BACnet UL 864 case file, outlining exactly what I/A Series BACnet hardware is approved for UL 864 systems can be obtained at: www.UL.com Navigate to the bottom of the home page under Useful links and click on Online Certifications Directory Find the UL File Number field and type s5381 The Schneider Electric MNB file will show up and click the link UUKL.S5381 under the link to file column. This will show you all of the I/A Series hardware that is UL 864 certified, and can be installed in an official smoke control system. Also refer to the I/A Series MicroNet BACnet Smoke Control Systems Manual (F-27419) for further information related UL 864 Smoke Control applications.

Issue When using RS-232 port to download Menta program, the neuron ID of I/O modules can't be downloaded. When downloading Menta program to Xenta 280/300 (with /N/P) through RS-232 port, the LED besides Service Pin flashes red. When plug OP onto the controller, only “No Answer” shows. Environment Vista 5 Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta I/O modules Cause The network configuration can't be downloaded through RS-232 port. Resolution When downloading Menta program to Xenta 280/300 (with /N/P) through RS-232 port in Vista 5, the normal method can't download the network configuration information to the controller, such like the blueprint, the neuron ID of controller and I/O modules. Then the following steps can be followed: Create the Xenta 280/300 controller in the Workstation. The LTA interface can be the Xenta Server, Loytec port or Echelon Port. It does not matter. Assign the Menta file to the Xenta 280/300 controller. Also manually type the neuron IDs of the controller and I/O modules in the Workstation. Right click on the Xenta controller and click “Edit” to open the Menta interface. Press F12 and “Online” button to download the Menta program into Xenta 280/300 controller. The controller or I/O modules should work fine now.

Issue 7770, 7771, 797, 7801 TAP replacement needed with existing system. Product Line TAC INET Environment Existing TAC I/NET Seven environment Cause The 7771 was the first generation ICI that the 7797 platform replaced. The 7771 was built on the old 7801 tap hardware where was the 7798 was built on the 7790 MRI platform. Neither of which are supported or available to purchase anymore. System upgrade for more capabilities or capacity, or hardware failure Resolution For the 7801 tap hardware, the Xenta 527 would be a suggested choice for replacement. For the remaining TAPs, the Xenta 913 would be a direct replacement. The TAC Xenta 913 is a cost-effective way to integrate a large variety of products into a TAC network. The TAC Xenta 913 supports the most commonly-used open protocols, like Modbus, BACnet and LonWorks. It also supports some manufacturer-specific protocols, like I/NET and Clipsal C-bus. The TAC Xenta 913 acts as a gateway and transfers data point values from one network to another. Configuration is carried out using the TAC XBuilder programming tool. For more info including the documentation, manuals, and datasheets, visit the Schneider Electric Extranet at the following link, which guide you to the replacement for the ICI. TAC Vista > Technical Documentation > Specifications Sheets  

Issue Vista IV Remote Workstation pulling the Workstation license from the server PC shows the error "The object involved has disconnected from its clients." If the alarm is acknowledged, Remote Workstation does not work. Restarting the Remote Workstation restores functionality. Environment Vista IV Remote Workstation Aladdin Privilege Administrator 2.01 Remote license hosting Cause The Aladdin Privilege Administrator 2.01 licensing tool that comes with Vista IV did not handle remote licensing of Workstation very well. If trying to read the Workstation license from the server at the remote PC, it occasionally will time out and result in this error. Resolution Install a Workstation license/dongle on the remote PC. This will prevent it from trying to read a license from the server PC and resolve the issue.

Issue Aside from the firmware chip, are the SIM-YORK and GCM-86000 the same circuit board? Environment Network 8000 GCM-86000 series controllers Network 8000 SIM-YORK Cause For in-house programming purposes, a GCM-86000 is available but access to the specific SIM block used with York chillers is not available in the GCM's firmware. Resolution The SIM-YORK and the GCM-86000 are functionally equivalent circuit boards.  The only difference is the firmware.  Swapping firmware with these two controllers is all that's needed to change them into the other.

Issue Getting modbus devices to communicate to Continuum may require some trial and error. Product Line Andover Continuum Environment Continuum Modbus RTU, ModbusRTU Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Manufacturers of modbus devices may have an offset for their register values and addressing these values requires trial an error. Resolution This article was created as a starting point. There are a lot of tools and methods to get values from modbus devices communicating. This resolution discusses some important concepts as well methods for trying to bring values in. The Modbus RTU protocol is a Master/Slave style of protocol. The Andover Controls CX will be the master on the Modbus RTU network. There can be only one (1) master at a time on the Network. The Slave number is always set in the third party device. This could be either a hardware setting such as dip switches or a software setting. Modbus-IDA (also known as Modbus.org) has set the limit that the slave address can be between 1 and 247. Address 0 is allocated as a broadcast message. The Andover Controls x-driver can support addresses in the range of 0-255. The third party manufacturer should be able to tell you what the expected function codes are for the points that you are interested in. Modbus.org has defined the function codes in a very loose manner and leaves it up to individual interpretation. Andover controls supports the following standard function codes: 1-8 15,16. Since when you request information from a Modbus RTU device you receive the exact value that is in the register Andover Controls has provided some special function codes that will help to convert some of the common engineering values into usable values. The listing in the x-driver documentation shows the special function code, what is expected from the third party and the equivalent function code that is truly sent to the device. For instance if a point is a Intel float and resides in the 40,000 range then function code 245 would be used in the Andover Controls x-driver. This will still send out a function code 3 in the Modbus message but the x-driver will take the value sent in from the third party device and convert it into a usable float. Most confusion occurs when talking about the data registers, (also known as addresses or channels). Modbus.org has the following statements about the addresses in the protocol document. All data addresses in Modbus messages are referenced to zero. The first occurrence of a data item is addressed as item number zero. For example: The coil known as ‘coil 1’ in a programmable controller is addressed as coil 0000 in the data address field of a Modbus message. Coil 127 decimal is addressed as coil 007E hex (126 decimal). Holding register 40001 is addressed as register 0000 in the data address field of the message. The function code field already specifies a ‘holding register’ operation. Therefore the ‘4XXXX’ reference is implicit. Holding register 40108 is addressed as register 006B hex (107 decimal). Register number also known as address. When setting the start channel number parameter on the x-driver tab the x-driver is expecting the exact decimal address that you are looking to obtain. For instance: if a device shows a listing for the first point to occur at 40,001 then the start channel number is typically 0. This can be confusing since some manufacturers have decided to have 40,001 as being 1 and not zero while others manufacturer have decided that 40,001 is 0. There are two ways of determining how the manufacturer has started the numbering system for the device if it is not documented: Method 1 is a trial and error method. Where you set the value to minus 1 of the register address, the actual register address and plus 1 of the register address and see which one you a response from. Method 2 uses a third party software to poll all the points to see what addresses are populated. There are many shareware Modbus RTU software packages on the Web. One such program is called ModScan32 by Win-Tech. www.win-tech.com Number of channels. The least amount of channels that will be requested is 1 so number of channels should always be 1 or greater. If the data is stored in multiple channels then you will need to set the number of channels equal to the number of registers. If you are not using a special function code you will need to set up a separate numeric with a manual log with the number of entries equal to the number of channels. When you poll for the value of the channels the data will then be stored in the manual log of this second numeric. The first element of the log will be the first channel that is requested. For instance if a value is stored in registers 40,000 through 40,003 then the start channel number will be set to 0 and the number of channels would be 4. Another numeric with a manual log of 4 would be created and linked in the x-driver numeric by placing the name of the new numeric in the annex point parameter. Once the x-driver point is polled the returning information will be stored in the annex point. The manual log of the annex point will contain the data for the 40,000 register in location 1. The data for each subsequent register location will be in the next manual log location. I.E. annexpoint[4] will contain the data for register 40,003 The Modbus RTU x-driver is a poll on demand x-driver. What this means to the user is that either a Plain English (PE) program, graphic or editing the x-driver numeric will cause a poll to occur. It is best to mirror the x-driver point and use PE to poll the x-driver points. A simple program would loop through and perform a simple line of mirroredpoint = x-driverpoint. This will avoid multiple polls to the same point tying up more CX resources then necessary. Then you can use the mirrored point in programs and graphics. If you try to get values from a slave device that is offline (not responding) the x-driver will poll each point three times before it moves on to the next point. This will cause the CX scan time to rise to seconds instead of tenths of a second. It is helpful to have a single x-driver point in the third party slave device that will return a known value, (Product ID or serial number for example). This can be used to avoid running the scan time of the CX up if the slave device can not communicate. Inside of the polling program try to poll for the value of this point. If the value does not come back then skip the polling for the rest of the points for this slave device. This point can also be used as an alarm for the offline device as well. For example: 1: If ProductID1 = 15 then Mirroredpoint1 = x-driverpoint1 Goto 2 else Goto 2 endif 2: If ProductID2 = 15 then Mirroredpoint2 = x-driverpoint2 Goto 1 else Goto 1 endif Some data may come back as a value when you need only a bit of information. In this case you will need to use the Bitand operator in PE to extract the exact bit that you are looking for. As seen below the PE code will take an alarm point from a Liebert AC unit and break out the individual bits of information. AC9_Alarm1 = x_ac9alarm1 'setting the mirrored point AC9_CommFail = AC9_Alarm1 bitand 1 'extracting bit 1 AC9_LocalOff = AC9_Alarm1 bitand 2 'extracting bit 2 AC9_RemoteOff = AC9_Alarm1 bitand 4 'extracting bit 3 AC9_HiHeadPrs1 = AC9_Alarm1 bitand 8 'extracting bit 4 AC9_HiHeadPrs2 = AC9_Alarm1 bitand 16 'extracting bit 5 AC9_LossAirFlow = AC9_Alarm1 bitand 32 'extracting bit 6 AC9_StbyGlycolOn = AC9_Alarm1 bitand 64 'extracting bit 7 AC9_LiquidDet = AC9_Alarm1 bitand 128 'extracting bit 8 AC9_ChangeFltr = AC9_Alarm1 bitand 256 'extracting bit 9 AC9_HighTemp = AC9_Alarm1 bitand 512 'extracting bit 10 AC9_LowTemp = AC9_Alarm1 bitand 1024 'extracting bit 11

Issue How to retain an AccessEvent history of visitor names when using a generic pool of visitor access cards? (personnel)  Environment Continuum Cyberstation Cause Need to record a history of access events for visitor cards with the visitor name and the card number assigned to them at the time. Resolution Using the Personnel Manager. Setup a Personnel Profile for Visitors with default areas assigned. For example, use the existing "Visitor" profile. Setup a Personnel Profile for Visitors with no areas assigned. For example create a new one called "Visitor No Access". This will allow just the required distributions to be sent down to access controllers when they are required. Create a new personnel object for each visitor assigning a dummy card number to them with the "Visitor No Access" profile you created in step 1. Save the object. Issue a temporary card for that personnel with the "Issue Tmp Card" button; using one of your visitor cards and add area access by using the "Reset Access Rights" button to assign the "Visitor" profile created in step 1. After applying the changes to the Personnel object they will then distribute access down to the controllers. When the card comes back, restore the original dummy permanent card with the Restore Tmp Card" button and reset the access rights back to "Visitor No Access"; freeing up the visitor card to be used again. Save the object.   This will provide you with an AccessEvent audit trail of the visitor card number and the personnel name associated with it at the time it was being used.

Issue Disable FTP (File Transfer Protocol) in all X5/7/9xx controllers Environment Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 Cause In some high security project installations, local IT groups require that FTP (File Transfer Protocol) be disabled on all devices within their network. Resolution FTP into the Xenta 5/7/9xx controller by typing FTP://x.x.x.x (where x.x.x.x is the IP address of the controller) in the Windows Explorer address bar. Login with the root username and root password. Browse to the sys/system/ftp.cfg file and copy it to the desktop of the local machine. Open the ftp.cfg file with notepad on the local machine. Set the FTPMaxUsers="4" line to FTPMaxUsers="0" and save the file. Copy the file back to the FTP session on the controller and paste / replace it over the existing file. Logout of the FTP Session Cold start the controller Now the Xenta 5/7/9xx controller will not have FTP access. If there is a need to re-enable FTP please follow this steps on the Xenta 511, 527, 555, 701, 711, 721, 731, & 913 Login into the controller via the web interface with the root level username and password. Navigate to Configuration > Servers > FTP Server Set the Max. number of users back to a valid number of 1-5 and click save. Cold start the controller. If FTP needs to be re-enabled on the Xenta 527-NPR the only option will be to reload the system program. This is because the 527-NPR does not have a full web configuration interface like all other Xenta 5/7/9xx controllers to set the number of users.   Update note: In later versions of the Xenta Server, FTP is disabled by default (the number of users are set to 0). If you still can't login to FTP, try to format the controller, reload the system program and try it again. Then it should work now.

Issue Infinity schedule randomly fails to turn on occupancy flag for a given day. Environment Cyberstation All IP level Infinity Controllers All i2 Infinet devices Cause Empty Holiday schedule can cause schedule issues, if you have not entered any events in your holiday schedule you need to add and inactive event at mid-night, adding this event does not have any effect in terms of changing the value of the schedule but solves a series of potential issues caused by the holiday schedule having no events at all in its event list. Resolution Add one event to Holiday schedule as follows: 12:00:00 AM - Inactive

Issue Can I send live data over SNMP? How many trap pages can I define? Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731 Cause All Xenta Servers (except Xenta 913 and Xenta 527-NPR) have a built in SNMP agent. However, the SNMP protocol in them cannot handle sending live data over SNMP. It can only send alarms along with specific fields of those alarms.   Resolution The Xenta Server supports SNMP version 1 and SNMP Traps. It can only be used to send SNMP and not to receive. The first step to setting up SNMP is to create alarms in XBuilder and link the points to the alarms that are to be monitored. Then, the filters used by the SNMP traps should be defined. This is done using SNMP trap pages. SNMP Trap Page The SNMP trap page is where you define a set of rules in Xbuilder of when to send a trap to the SNMP manager. This includes severity of the alarm or a wildcard string based on the address of the point.  In XBuilder you can create up to 10 SNMP trap pages, which will give you possibilities to define 10 different alarm filters. An SNMP trap page is created by right-clicking a folder in the System pane of XBuilder and then selecting New > Page > SNMP Trap Page. (It is recommended that a separate folder be created for SNMP trap pages and that this folder be restricted to only system administrators.) Once the SNMP trap page has been created it is then configured by right-clicking on the SNMP trap page object and selecting SetupSNMP Trap Filter.   SNMP Field Configuration The SNMP field configuration is where you define what 8 pieces of data will be sent to the SNMP manager (due to the UDP limit of 8 fields). That data consists of things like date/time, type, address, priority, description, etc. The SNMP field configuration is accessed by clicking on the Tools menu and selecting SNMP Field Configuration.     For more information on SNMP in Xenta Servers please see the TAC Xenta Server - TAC Networks Technical Manual, section 16. Note: SNMP is only supported by Xenta Server devices and is not supported by TAC Vista.  

Issue Trying to find all BACnet devices under a bCX by right clicking the device in the Continuum Explorer and selecting 'Find BACnet Device', no error is received but no devices are found even though there are BACnet devices on the bCX's MSTP port. Furthermore, a Wireshark capture shows who-Is message was qualified with bCX's device id. (example, who-Is, 2587214-2587214) Environment Cyberstation bCX4040 b3s Cause When a 'Find BACnet Device' is issued from a specific bCX device, Cyberstation direct the who-Is message to the particular device. Resolution To find all BACnet devices right click the root folder and select 'Find BACnet Device' from the root.

Issue Microsoft Visual C++ Runtime Library Error After you install I/NET on a computer containing Microsoft Office XP or one of the Office XP programs, you may receive one of the following error messages: Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSDMN.EXE abnormal program termination Microsoft Visual C++ Runtime Library Runtime Error! Program:.. C:\PROGRAM FILES\COMMON FILES\SYSTEM\MOSEARCH\BIN\MOSEARCH.EXE abnormal program termination Environment XP computers containing Microsoft Office or other loaded programs, one of which may be I/NET  Cause This behavior occurs if a program (not necessarily I/NET) conflicts with the Mosdmn.exe and Mosearch.exe files or with video settings, antivirus or 3rd party programs conflicting with your operating system. Resolution The Mosdmn.exe and Mosearch.exe files are part of the "Support for fast searching" feature in Office XP. This feature is similar to the Find Fast feature in Microsoft Office 2000. Fast searching uses the Indexing Service in Office XP to create a catalog of Office files on your computer's hard disk. To resolve this issue, use the following methods, as needed, in the order presented. Method 1: Clean Boot with Only MoSearch The Mosearch.exe (Microsoft Office Search Service) and Mosdmn.exe (Microsoft Office 10 Search Filter Daemon) Startup items may be conflicting with some other program (or programs) running in the background. Therefore, clean boot your computer with only MoSearch selected on the Startup menu to determine whether this program is the source of the conflict. To do this, follow these steps:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the General tab, click Selective startup. 4. On the Startup tab, click to clear all check boxes except for MoSearch. 5. Click OK, and then click Yes when you are prompted to restart the computer. 6. If the error message can be reproduced, repeat the preceding steps. In step 3, also click to clear the Process System.ini file and Process Win.ini file check boxes.   If the error message cannot be reproduced, this indicates that MoSearch is conflicting with some other program or programs running in the background. Follow these steps to locate the conflicting program:   1. Click Start, and then click Run. 2. In the Open box, type msconfig.exe, and then click OK. 3. On the Startup tab, click to select one of the check boxes. 4. Click OK, and then click Yes when you are prompted to restart the computer. 5. If the preceding steps reproduce the error message, the last item added to the Startup menu is causing the conflict. If the error message is not reproduced, repeat these steps until all Startup menu check boxes are selected. 6. If all the Startup menu check boxes are selected and the error message is still not reproduced, start Msconfig again, and then click to select the Process System.ini file and Process Win.ini file check boxes.   Restart the computer. You may need to install a clean version of I/NET depending on your computer setup.   This is the solution for the Microsoft Visual C++ Runtime Library error with XP Office. Other solutions may entail removal or reconfigure of video drivers, antivirus programs, or other 3rd party programs conflicting with your operating system.

Issue Attempting to commission a Niagara G3 ENC-520 and an error indicates the nre core distribution files cannot be found on the local computer. The distribution files are typically installed under the Niagara directory in \sw\3.5.34 (or other version number) Environment Niagara G3 all versions Cause The distribution files were not installed on the computer as the checkbox for "This instance of TAC I/A Series Enterprise Network Server will be used as an installation tool" was disabled (or NOT checked) during the installation process. Resolution Re-install the Niagara G3 software version with the checkbox (described above) enabled.