Building Automation Knowledge Base

Issue Host conflict window always pops up, and cleaning routing table doesn't help. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause Host conflict is a normal issue happening in I/NET. It is usually caused by the duplicated host ID setting on different servers, or an engineer laptop is inserted into the network with the same host ID setting with some server. And the routing table will be messed up since all the IP related information will be recorded in the routing table and it will be distributed to all the network devices, including all the servers and NPRs. The usual solution is to clear all the routing tables on all the network devices, . Refer to How to Remove the Routing Tables in a Device or PC about how to clear the routing tables. But if the routing table is cross referred, like Server 1 adding NPR 1 and NPR 2 as reference hosts, while NPR1 adding Server 1 and NPR 2 as reference host, the routing table will never be cleaned out since when you clean the routing table for Server 1, NPR1 and NPR 2 will still try to send their wrong routing table to Server 1. Unless all the network devices are disconnected and the routing tables are cleaned one by one, or disable the 50069 port for the whole network, which is used by the communication between network devices, there is no other way to clean them out. And these two method are not applicable sometimes. Resolution If the routing table can be managed well, such kind of issue will never happen. The best practice on adding reference host and creating routing table is: On the servers: Choose one server as the master reference host. All the other servers add this server as reference host. Don't add NPR as reference host. All the NPRs can be added into the master server by clicking on the NPR button in I/NET configuration and added one by one manually. By this way, the master server can build its own routing table without impacted by other devices. And this one is the only routing table in the whole network. On NPRs. If NPR doesn't need to talk to other NPRs, like transferring indirect points, there is no need to add reference host for NPR. If indirect points are needed, just add the master server as the reference host. Then this NPR will be able to see all the other NPRs based on the routing table on the master server. If the master server is not equipped with UPS, or not always promises to be online, another master NPR can be chosen as a secondary reference host. Add this NPR as a reference host to all the servers and other NPRs. Under this scenario. if the routing table needs to be cleaned, only the master server and the secondary reference host need to be cleaned. It will be more easier to clean all the routing table and get rid of the host conflict error.

Issue Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. Product Line TAC INET Environment Windows XP, Windows Vista OS, with SQL 2000, 2003 and 2005. Cause Functionality of the host pc and the database seems to be inconsistent. Resolution Option 1: Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy INetDb.mdf and INetDb_log.ldf to an alternate locations (located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Restart all SQL Services. Launch DBCreate and remove the existing I/NET Seven Database. Create a new I/NET Seven Database. Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy the saved INetDb.mdf and INetDb_log.ldf over the newly created files. Restart all SQL Services. Launch DBCreate and attempt a backup. Option 2 (If Option 1 does not work) Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy INetDb.mdf and INetDb_log.ldf to an alternate locations (located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Uninstall and Reinstall I/NET Seven. Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy the saved INetDb.mdf and INetDb_log.ldf over the newly created files. Restart all SQL Services. Launch DBCreate and attempt a backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue When I/NET is running under Windows 7, there will be a display issue about alignment. The font size has been changed to smaller - 100%, but still no use.  Product Line EcoStruxure Building Operation, TAC INET Environment Windows 7 Cause Be sure to try I/NET Seven Windows fields not aligning correctly on workstation's display to change the font size first to see whether it can help. If not, continue to the next information. I/NET used the default MS Sans Serif font to display everything. But something has changed in Windows 7 about the font display.  Research showed that many users with high resolution monitors (particularly LCD flat screens) were running the monitors at lower resolutions than the native resolution of the screen. This was usually because at the native resolution, the fonts were becoming too small to read, so the users would decrease the resolution. Windows includes a facility to increase font and window sizes while keeping the screen at the native resolution.  This is a much better method of increasing the font size as it can produce much smoother images by using many more, smaller pixels. The really significant issue is, unlike CRT monitors, flat-panel LCD monitors have a fixed pixel size, or "resolution", and that when users change to a lower resolution (in order to increase text size) the system has to re-sample the lower-resolution display image into its fixed resolution causing a significant degradation in display quality: not just text looks worse, everything looks worse. A change was made for Windows 7, to set the screen resolution to the monitor's native resolution and if the screen is over a certain resolution to default the font size 120 DPI (dots per inch). This is approximately 125% of normal 96 DPI (100%). When the system defaults to 125% DPI it also adjusts the MS Sans Serif font to be bigger.  If the user then decides to set the DPI back to 100%, then TrueType fonts, which are scalable, adjust as expected. But the bitmap MS Sans Serif font does not: it remains at the larger size, hence this issue. This problem does not occur if Windows 7 keeps DPI at 100% when it is first installed. So anyway, when the default font size is Medium - 125% instead of smaller - 100%, probably the solution below is needed to solve it. Resolution Go to the Registry Editor, and find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts. Find the entry MS Sans Serif 8,10,12,14,18,24. The original value is set to SSERIFF.FON on a system which started at 125% DPI. Set to SSERIFE.FON on a system which started at 100% DPI.  Notice that one character of the file name changes from F to E. Restart the computer, and make sure the font size is set to smaller - 100%. Refer to I/NET Seven Windows fields not aligning correctly on workstation's display about how to set font size. Then it should go back to work.

Issue Alarms generated from Sigma controllers are not received at the Sigma server. Product Line Satchwell Sigma Environment Sigma software - All versions Controller firmware - All versions Cause The controller generates the alarm correctly, but is unable to send the alarm to the Sigma server. This can be seen by using the "Comms Stats" request from the Sigma server. The screen shot below indicates that the "Alarm buffers" have 21 alarms waiting for transmission. Resolution To identify the cause of the problem, carry out the following steps. Perform a "Comms Stats" request of the controller from the Sigma server, to establish that an alarm has been generated. Confirm that the Client configuration has been correctly set up by referring to Alarms are not displayed in the Sigma local or remote client Alarm Manager window. Confirm that the Sigma server has been correctly configured in "System Setup / Networks and Devices". Confirm that the Sigma server IP Address matches the address set in "Network Connections" Upload an object with an alarm programmed from the controller, and check that the routing page has no references to "T" present. (T was used in the BAS2800+, but is not in Sigma). Confirm with the IT department that there are no network issues.

Issue Alarms being generated in I/Net are not showing up on the Enterprise Server. Product Line EcoStruxure Building Operation, TAC INET Environment SmartStruxure Integration with I/Net Alarms Cause Alarms generated in I/Net are not populating on the Alarms Window on the ES, all masking are set on both the AMT Configuration and Host Masks. When the point goes into Alarm, it populates the Alarm Window type, whether it is Priority or Critical with said point address. However, it does not show up on the Alarms page because the bin files on the controller needs to be updated to the latest version of software and all points need to be saved prior to integrating with SmartStruxure. Resolution When integrating with SmartStruxure, all controllers are supposed to be updated with the latest version of software as well as sav files, per Resetting a 7793 Controller and PCU (Applies to 7793, 7716, 7728, 7756). Once completed, recheck the points by putting them in Test mode so that they can generate the Alarm condition and it should show up in the ES Alarm now.

Issue No Messages Received in AMT from specific Link or Site Product Line TAC INET Environment I/NET Seven Xenta 527-NPR Xenta 527 Web Server NPR2000 Cause There are many causes outlined in AMT not receiving Data which show reason why AMT may not be receiving data. In some cases the issues is not due to programmatic issues but network Errors. I/NET uses UDP port 50069 to broadcast data from NPRs and Xenta 527s to any listening host device. While this does give the flexibility to have multiple hosts receive the same packet, it prevents the proof of delivery that a TCP packet provides. You can read more about UDP at this link. http://en.wikipedia.org/wiki/User_Datagram_Protocol Resolution  To prove a network error, use the following methods: Verify everything listed in AMT not receiving Data If feasible, repeat those steps above direct connected to the Xenta 527 via crossover cable. Ensure Window Firewall is disabled on the local PC when performing this task. Once you have a PC that will receive Messages while direct connected, re-connect the 527 to the network and use the same PC to connect to try to 527 over the network. If AMT works or fails based on being on or off of the network, then this is a networking issue. The PC, Domain Server, or Internet Service provider are all capable of blocking I/NET communication. This can be done by either blocking traffic going out of the PC(s) to the NPR/527(s), or it can block traffic from the NPR/527(s) to the PC. On a PC Windows Firewall these are referred to as outbound rule and inbound rule respectively. Please note the following conditions when certain parts of the network traffic are blocked. Traffic Blocked on traffic from NPR to PC Traffic Blocked on Traffic from PC to NPR Both Blocked You can connect to controllers in I/NET, values will update and you can control points You cannot connect to controllers in I/NET, values will not update and you cannot control points You cannot connect to controllers in I/NET, values will not update and you cannot control points AMT does not receive data from the blocked Link or Site AMT does not receive data AMT does not receive data   To Correct a PC Windows Firewall Issue: You will be able to prove a windows firewall issue by turning off the PC firewall for a few minutes and testing AMT. If traffic resumes, this is the cause. Open Windows Control Panel If needed, change "View By" from Category to Small Icons Click on Windows Firewall Select Advanced Settings Click on Inbound Rules Click on New Rule in the Actions Pane Select Program and click Next Browse to the InetIoSrv.exe application on your PC. Click Next Select the Action to Allow the connection and click Next   Set the Rule to apply to all locations. Click Next Name the Program and Click Finish. AMT Should begin to receive data. If not, repeat step 1 to verify this is a PC firewall issue and contact Product Support for additional assistance. If the data is being blocked by the network and not the PC Firewall: Contact your network administrator and explain that the Xenta 527 or NPR 2000 must be able to broadcast UDP data on UDP port 50069. This path must be open on every hop between the device and the PC. Verify that both the PC and device are on the same Windows Domain. Typically, UDP traffic will not travel outside of the Domain. If you are unable to get network blocked removed, you may be forced to put all I/NET devices and PC's on a single subnet.

Issue The TGML page is dynamic but looks static. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista StruxureWare Interface Cause In the Release Note, page 30 says: It is possible to navigate to a TAC Vista Webstation TGML Graphic through a link in a SmartStruxure TGML Graphic. To achieve this connection a link object is created in the SmartStruxure TGML Graphic which is linked to a SmartStruxure hyperlink object that holds the TAC Vista Webstation TGML Graphic page address. Example of a hyperlink objects address in SmartStruxure that is linked to a TGML Graphic in TAC Vista: HTTP://ip_address/webstation/LoginPage.aspx?page=TgmlGraphicsPage.aspx?objectId=3074949137 Note: This will always require a login by a valid TAC Vista user, even if the TAC Vista Webstation auto login feature has been activated. Resolution The example link above is referring to a static page. For example, if the TGML page is dynamic, you will see the following in the copied link (see bold). HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 You can also read the following in the release note: In order to determine the TAC Vista Webstation URL for a TAC Vista Webstation TGML Graphic the following TAC Vista Web Setting configuration must be in place: Optimized TGML Loading is deactivated Folders pane is set to Standard HTML With these settings it is possible to right-click a TGML object in the folders pane and select "Copy Shortcut." This will copy the TAC Vista Webstation URL to the clipboard and it can then be pasted into a SmartStruxure hyperlink object address field. After the shortcut has been pasted, it will have to be modified in order for the TAC Vista TGML Graphic to be displayed properly in SmartStruxure. The modification is marked with bold in the example below: Copied: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 Modified: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 If the link you copied was a dynamic TGML the link will look like: HTTP://ip_address/webstation/TgmldynamicGraphicsPage.aspx?objectId=3074949137 and should be modified as this HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 Also reference the TAC Vista Webstation Graphics Links and SmartStruxure Integration tool on the Community.

Issue When Remote Alarm Manager attempts to initialise the GSM modem it fails during reset command. Modem will reset correctly if the same commands are sent from a terminal emulation program. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista RAM Sigma Ram MicroNet RAM BAS RAM GSM Modem Cause The result codes from the modem are not returned in the format expected by Remote Alarm Manager Resolution The Mobile Equipment Errors setting (AT+CMEE) sets the format that error responses from the modem are returned in, the possible formats are: 0 disable result code and use ERROR instead 1 enable result code and use numeric values 2 enable result code and use verbose values The GSM driver in Remote Alarm Manager expects to see these results in numeric format. To Check and set the format do the following: Using a Terminal Emulation Program such as Hyperterminal connect to the modem Enter the command AT+CMEE? to show the current setting Enter AT+CMEE=1 Enter AT&W to store the current settings to non volatile memory. Disconnect Hyperterminal and test with Remote Alarm Manager.

Issue Both comm ports can be enabled for RTU, but is this a recommended configuration? Product Line Andover Continuum Environment Continuum 9900 9940 9680 9640 5740 5720 Xdriver Cause 2 port can be enabled for RTU Xdriver on a netcontroller, but is this a recommended configuration or will this be too much of a strain on the Controller? Resolution According to the Xdriver developers, it is NOT advisable to use 2 Modbus RTU Xdrivers on the same Controller  The Modbus RTU Xdriver is the only 'poll on demand' type xdriver and this dual configuration has the potential of holding the CPU for longer and could cause the polling to become irregular. It is recommended to add an additional Controller to handle the additional devices and points required. Also see BCX Controller can use Comm 1, Comm2, or both ports for Modbus RTU X-Driver Can two comm ports be enabled when using the RTU Xdriver?

Issue This is a guideline to do air balance settings (airflow calibration) on a VAV ASC using a I/STAT or M/STAT. Product Line TAC INET Environment MR-VAV-AX MR-VAV-X1 MR-VAV-X2 Cause The air balance company needs a procedure to properly set up the MR-VAV-AX products for the air balance settings. Resolution Understand the cooling setpoint is 75°F, and the heating setpoint is 70°F. This information is important in knowing which state the system is trying to control. While in the PP mode of the I/STAT, it is important to verify the setpoint is 75°F. This allows Test & Balance to set the temperature to: 77°F for maximum cooling 72°F for minimum cooling with no fan 68°F for heating mode - minimum primary airflow with fan To verify the current setpoint, use the Select key and scroll up to Set Temp. The I/STAT will display the current setpoint. For testing purposes as described in Step 1, if the temperature setpoint is not 75°F, press the + or - key to raise or lower the setpoint to 75°F. In order to enter the Service Mode, press the Service key. Enter the I/STAT password 183. Press the + or - key to see the left most digit change accordingly. Press the + key to scroll to 1 and press Enter. The cursor on the I/STAT will move to the center digit. Press the - key to 8 and press Enter. Now the cursor will move to the right most digit. Press the + key to 3 and press Enter. You are now in the Service Mode. While in the Service Mode, the Service key is the escape key and the Enter key will allow the controller to accept your desired changes. The first step in the calibration process is to make sure the controller is at the Factory Calibration Setting (FCS). Press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press the Select keys to scroll to FCS, press Enter. The I/STAT will display NO. Press the + key to change the display to YES and press Enter. Press the Service key to back up one screen. To verify duct diameter (dd) press the Select key and scroll to Unit Parameters (UP). The I/STAT will display the current duct diameter as 10.0 (default of 10 inches) unless the value has already been changed. Press the + or - key to raise or lower the value, and the Select keys to move between the right most and center digit. Sample: 8 inch box is displayed as "08.0" Press the Enter key to allow the changes to take place. Press the Service key to back up one screen. To verify Cooling Low Flow (CLF) and Cooling High Flow (CHF) setpoints, press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press Enter, the I/STAT will display the current value. Note that CFM is displayed as KCFM, for example 0.50 = 500 CFM. If the values are correct, press Enter. If the values need to be changed, use the + and - keys to change the values and the Select keys to move the cursor from the left most digit to the right most digit. Once you have the desired value displayed, press Enter. The I/STAT is now displaying CLF. Press the Select keys to scroll to CHF and press Enter. If the values are correct, press Enter. If the values need to be changed, use the +, -, and Select keys to change the CHF to the desired value then press Enter. CHF is displayed on the I/STAT. Press the Select keys to scroll down to Calibrate Primary Low (CPL), press Enter. The VAV controller will modulate the damper to maintain its design CLF. The I/STAT is currently displaying the CFM the controller is reading. Note that during this process, the CFM value may go to -0.1, 0.0, etc.; the controller is calibrating itself to the 100% actual closed position. Once the CFM comes within 10% of the CLF setpoint, the ON/OFF LED will turn on. While the LED is on, the controller is not modulating the damper and the controller has the damper in a fixed position for approximately 60 to 90 seconds. (Do not attempt to enter any values at this point. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CLF.) Once the airflow has stabilized and the I/STAT is displaying the CLF CFM, measure the airflow and input the actual value (do this as soon as possible because once the + or - key has been pressed, it freezes the damper into a fixed position to allow enough time to enter the actual value and to minimize chances of the actual CFM changing), into the I/STAT using the +, -, Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT will display Calibrate Primary High (CPH), press Enter. The VAV controller will modulate the damper to maintain its design CHF. Again, once the CFM comes within 10% of the CHF setpoint the controller's ON/OFF LED will come on and the controller will perform as described in Step 9. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CHF. Once the airflow has stabilized and the I/STAT is displaying the CHF CFM, measure the airflow and input the actual value (again, do this as soon as possible) into the I/STAT using the +, -, and Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT should be displaying CLF. Once the low and highs have been calibrated, press the Service key. Press the Select key to scroll to Operational Parameters (oP), press Enter. Press the Select key again to scroll to Prove Performance (PP). This mode will place the program's Room Temperature in a test state. The I/STAT display will toggle between the current CFM and the room temperature. This step will allow the balance engineer to verify proper operation of the VAV controller to maintain the design maximum and minimum airflow. Press the + and - keys to increase or decrease the room temperature in order to manipulate the system to control between cooling and heating as described in Step 1. Once the VAV has controlled the damper to design minimum CFM, the balance engineer can adjust the fan (if applicable) to design airflow. Important: If at any time during the calibration process, (not during Prove Performance (PP)) a mistake is made, make sure that the controller is reset back to the Factory Calibrated Settings (FCS), (see Step 4) and restart the calibration process. Also, if the VAV box does not control the CFM within the maximum allowable percentage, normally within 10%, go back to Step 4 and restart the calibration process. For further information see the following: TCON126 (Micro Regulator Controllers and I/STAT) TCON147 (ASC MR-VAV-AX) TCON155 (ASC MR-VAV-X1) TCON165 (ASC MR-VAV-X2) Go to TCON Number and Title Cross Reference (with links) and download the TCONS above.

Issue How can multiple licenses work simultaneously in Vista 5? Product Line TAC Vista Environment Vista 5 Licensing LMTools Cause Licenses may have been purchased separately and either contain different features, or additional seats. The license server can read multiple licenses and serve them up appropriately. Resolution Option 1 - Use multiple .lic files Since the filenames are the same for all .lic files sent via schneider-electric.flexnetoperations.com, you must first rename the files Put them in the License Files folder Make sure the license server is pointing to that folder (not an individual file) Reboot or Stop/Start/Reread license server using the LMTools utility. Option 2 - Merge into one .lic file Complete instructions in Manually Consolidating License Files Open each license file using a text editor. Cut and paste the "Features" into one of the files (Do not copy the file "header") Place this file in the License Files folder Reboot or Stop/Start/Reread license server using the LMTools utility.

Issue It may be desirable to change the default name of an NPR as it appears in I/NET (ie XentaXB2435) to something more descriptive. Product Line TAC INET Environment I/NET I/O Server Config Xenta 527, Xenta 527-NPR, Xenta 731, Xenta 913 Cause I/NET generates a unique default name for each NPR. While the default name differentiates the NPRs it may be helpful to have a descriptive and relevant name for each NPR. Resolution Open the I/NET IO Server Config. Select the IP Port connection of the NPR to be changed and select Modify to open the Configuration Profile. Click on NP Routers to open the NetPlus Routers Summary. Select the router that you want to change and click Modify to open the NetPlus Router Configuration. Enter a new name for the NetPlus Router and click OK. The NPR will now re-initialize and will have the new name. If you are still having issues, see How to change the name of a 527 Link or DLA site.

Issue If a customer's Vista PC crashes, how is the software recovered, and is it necessary purchase all software again? Product Line TAC Vista Environment TAC Vista Cause If a PC with Vista software installed crashes, all software needs to be reinstalled, and if necessary a rehost of licenses is required. The rehost procedure is covered in Rehosting a Vista 5 License on the FlexNet License Server. Resolution The TAC Vista 5.x software itself is free and available for download from The Exchange Download Center. If the software licenses are purchased once, they are still available and no repurchase is necessary. If licenses were locked to a hardware dongle, just reinstall the license file(s) again when installation is completed.    If licenses were locked to a Host ID and Host ID is changed due to configuration changes on PC, you need to login to https://schneider-electric.flexnetoperations.com and rehost the licenses to the new Host ID.

Issue Is it possible to limit the number of Vista workstation instances that can be opened on a PC? Product Line TAC Vista Environment TAC Vista 5.1.X Cause On a site with a number of workstation and workstation remote it is possible that all licenses will be checked out by one user on one PC, if multiple instances are running, leaving no licenses available for other users in the network. Resolution It is possible to use a license options file to reserve licenses for specific users. In this way it is possible to guarantee that a license will be available for each user. There is also an option to set the maximum number of licenses a user can use. Click on the following link to open Controlling distribution of license modules in Vista 5which contains a link to the FlexNet Licensing User Guide.

Issue Sigma and BAS - Out of Range value displayed on an AI point when configured as a 0-10V input. Product Line Other, Satchwell Sigma Environment Sigma BAS Cause If a 0-10V analogue input rises to above 10Vdc then the point default value is displayed. Resolution There are several ways to prevent this happening as follows: Follow the example in SHD100 / SHD101 - Humidity Sensors can give a DC voltage signal of greater than 10 Volts using a resistor and lookup table. Or use a Zener diode fitted as per the diagram. Note the maximum input will be the rating of the Zener diode e.g if the Zener diode rating is 9.1V then any voltage from the device higher 9.1V will be pulled back down to 9.1V. Zener diodes are available with fixed voltages, the nearest to 10V is 9.1V. The Zener diode can be fitted at the sensor end (normally slightly easier) or at the controller. The upper limit of the normal operating range of the sensor needs to be below 9.1V. Note: normally a resistor is fitted when using a Zener diode, but because the impedance of the sensor is high, the current will be small, hence the resistor is not used.  Or use a diode, this will work to where the maximum input rises to 10.6V. The diode needs to be fitted in series with the device BMS signal. A diode will drop 0.6V across it, therefore in this case a revised lookup table needs to be created. e.g 10V in will be 9.4V out and so forth. Or in the case of feedback from an actuator, the output to the actuator can be restricted to a value e.g 9.5V, this will then restrict the feedback signal. Care must be taken with this method if the actuator is connected to a valve then the performance of the valve and the system it is connected to will be slightly reduced.

Issue Steps to setup a NIC-IP for Vista Product Line TAC Vista Environment NIC-IP Cause Setting UP a NIC-IP Resolution 1. Download and install the latest NIC software. Here is a link to this site 2. Start the LConfig application. This is located in the LOYTEC Network Interfaces menu. 3. Select the NIC-IP/RNI tab. 4. Select the Assignment & Configure button. 5. The next popup screen will search for the NIC-IP. If your NIC-IP is powered up and plugged in to the network it should appear in this list. 6. Select the NIC-IP and then select the Configure button. 7. Setup the IP address, IP Netmask, IP Gateway and DNS servers if required. Select the OK and the device will write the new configuration to the NIC-IP 8. Take note of the Assignment and change if required. Press OK and the Assignment & Configure screen will close. 9 In the LConfig application select the Device from drop down list that matches the notes assignment from step 8. 10. Press the Test Device/Serial Number button to check for the correct setup of the NIC-IP. The return screen should look like this. 11.Close the LConfig application by selecting the OK button. 12. Start the Vista server and log into Vista workstation 13. Under the Vista server object add a new Device-communications Port - Loytec 14. Select the properties of the new Communication port and select the Network interface from the dropdown list. this should be the same interface noted in step 8. 15. You can the add Lonworks networks under the NIC-IP device.    If your NIC-IP does not appear in the dropdown list, Configuring Loytec NIC in Vista discusses this related issue.  

Issue How to check the amount of used memory in a TAC Menta/TAC Xenta application. Product Line TAC Vista Environment TAC Menta Xenta 281 Xenta 301 Xenta 401 Cause When programming applications for TAC Xenta, you may want to be able to check the size of your application, to verify that it can be downloaded to the device. Resolution To be able to check how much memory an application is using, the application needs to generated. In TAC Menta, edit mode: Select Option, Simulate to enter Simulate mode. In Simulate Mode, select Commands, Generate, to generate the application. To be able to check the Memory usage, you have to return to Edit mode, Select Options, Edit. Now you can check the Memory usage by selecting Options, Memory Usage... As this calculation is done on your PC, and not in the device, and that the memory in the TAC Xenta device is dynamic allocated, it is a recommendation to have at least 10% free memory in each category to avoid future problems. For more information about the Advanced button, please see TAC Menta Advanced Memory Usage: BPR Size Calculator.

Issue XIF and Device Resource files for the Schneider Electric SE7000 Series Room Controllers Product Line EcoStruxure Building Expert, Field Devices, TAC IA Series Environment SE7000 Series Room Controller Cause In order to commission Schneider Electric SE7000 Series Room Controllers into an LNS system, the XIF is required. Resolution LonWorks External Interface Files (XIF) SE72_73_PIR.XIF (80:00:10:55:00:04:04:20) SE76_PIR.XIF (80:00:10:55:00:04:04:21) SE76RH_PIR.XIF (80:00:10:55:00:04:04:22) Device Resource File for XIFs listed above. For Datasheets for the SE7000 Series Controllers, see Where to find datasheets and information on the SE7000/SE8000 series room controllers.

Issue Has the AC256 Xdriver been qualified or modified to work on any second generation controllers (NC2, bCX)? Product Line Andover Continuum Environment bCx9640 CX9680 Xdriver AC256 LA-1 Cause With the obsolescence of the NetC (CX99xx), will the AC256 Xdriver be updated to work with NC2 and/or bCX controllers? Resolution There are no plans to upgrade the AC256 Xdriver for the NC2 and/or bCX. One option, if a site only has AC256 IOU boards, is to use the NC2 and the LA-1 LBus Adapter module or the NC2 with built in LBus support (on comm4 or comm1 with an RS232-to-RS422 converter) to communicate over the LBus with Plain English programming in the NC2. Note: If you configure the controller for Lbus (using the LA-1 or directly to comm1 or comm4) you cannot use Continuum IO modules on that controller. For further information on X Driver compatibility and how to request new drivers/ upgrades, please see Will Continuum communicate with a third party system?

Issue It is not possible to make any configurations or calibrations within a Xenta controller that will reflect on the STR-150. Product Line TAC Vista Environment STR-150 Vista Xenta 121 Xenta 104-A Cause Communication between any Xenta controller and STR-150 is only one-way. The STR-150 can communicate to the controller but the controller cannot communicate back to the STR-150. Resolution Any parameters that can be changed on the STR-150 must be changed at the stat itself. Complete information on the various available parameters can be found in STR-150 Manual Configuration. It is not possible to perform a calibration on the STR-150 stat in a way that will affect the readout of the STR-150 in a version prior to 1.4. The Xenta 104-A can have the space temperature calibrated within the application by changing nciTempOffset. However, when a version prior to 1.4 of the STR-150  is used with the Xenta 121 the space temperature cannot be calibrated. For more information see STR-150 Calibration Feature.