Building Automation Knowledge Base

Issue Some customers may specify that the login screen to a Xenta Server be bypassed. Environment Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause When accessing a Xenta Server using a web browser a username and password are required by default. Resolution Configure the user you want to automatically log in to the Xenta Server Generate a certificate To avoid having the certificate error pop up every time you connect to the Xenta Server, go to XBuilder, and generate a certificate that has the same name as the IP address of the Xenta Server. Edit Slogin.html and loggedout.html Connect to the Xenta Server using FTP ftp:// XXX.XXX.XXX.XXX The Slogin.html and loggedout.html are located in the folder www/index Copy the files to your local hard drive Edit the files with, for instance, notepad and change the following Slogin.html Line 54 document.AuthForm.UserID.focus();" document.AuthForm.UserID.focus(); send(AuthForm);" Line 98 input type="text" name="UserID" value="" size="20" > input type="text" name="UserID" value="user" size="20" > Line 104 input type="password" name="PassWord" value="" size="20"> input type="password" name="PassWord" value="password" size="20"> loggedout.html Line 5 (extra line, add < symbol at beginning of line) meta http-equiv="refresh" content="2;url=/www/index/Slogin.html"> Carry out the changes Reconnect to the Xenta Server using FTP Change the names of the files that are already in the Xenta Server (Backup) Copy the files that from your hard drive to the Xenta Server  

Issue Invalid or phantom Links, Hosts and IP's in Netcon.  This symptom exists when you penetrate Network Configuration and there are Links and NPRs that you have no clue as to who they are or where they came from. Product Line TAC INET Environment I/NET NPR-2000 Xenta 527 Cause This can happen is if a laptop was used to connect to the system from a different Network or from the outside. Once connected, its IP address and any link it shares are broadcasted to the other devices like PCs and NPR’s, thus populating the table with entries that do not belong or are non-existent for this location or system. It can also happen if you install an NPR/527 or replace  one with a unit that has been used elsewhere. If that use NPR/527 is being used as a reference host, it will infect the system with every IP address and Link in its routing tables. Resolution At this point there is no way to get it out of the tables except to Telnet into all devices, remove the IP tables and rebuild them from scratch. This may be a cumbersome process depending on the amount of devices that make up the system (PCs, Laptops and NPR’s). All of these would need to be set back to 0 reference host while the cleanup is being done. To get this cleaned up, follow the steps to start a Telnet session:   Go to Start > Run and type Telnet then hit Enter. Type open at the end of the prompt, hit the space bar and then put in the IP Address of the NPR/PC and hit Enter. A logon prompt will come up, type csi and hit enter Now type LA, this lists all the entries in the table. Type delall and hit enter. This clears out all the IP’s of the other devices. This would have to be done on all the devices. Once completed, start I/NET to verify that those are gone and then start referencing other PC’s, Laptops and NPR’s to get the system back online again. Note: The proper way to use a Service/Maintenance laptop that is used for multiple customer sites is to direct connect to the NPR to see the controllers of the other links that exist at the site. However, before starting I/NET on the service/maintenance PC, open Windows Explorer, C:\Program Files\Inet Seven and delete the XXX.dat files. These get rebuilt when I/O Server restarts, it also clears out all entries in the routing tables. See .DAT files.  You may also create a different configuration profile for each site. This will also keep the tables separate.

Issue What does a network switch need to be configured as to connect to a Continuum controller? Environment Network switch CX99xx CX94xx CX92xx CX9702 B4920 BCX series controllers  Cause The configuration depends on what model of controller is being connected to the Ethernet switch. Resolution If you are connecting any of the CX99xx, CX94xx, or CX92xx models of controllers: The switch port needs to be configured as 10 Mb Half duplex. These series controllers only support a 10 Mb connection type and they do not auto detect the connection type.  If you are using any of the newer model controllers like the CX9702, B4920, or BCX series controllers  they support an auto detect connection type of 10/100 Mb connection. These newer controllers will also auto detect the mode for either full or half duplex. An additional feature on the BCX series controllers is that they will also auto detect whether the CAT5 cable being used is a Cross over cable or Straight through cable.

Issue "No license for LonWorks communication" - LonMaker Recovery Folder Product Line TAC Vista Environment Echelon LonMaker Cause Vista software detects the installation of commissioning tool for the LonWorks communication license. At times LonMaker will improperly shut down and store bad data in the Lm\Db\Database name\recovery folder. This invalid data will stop the LNS server from running properly. Resolution If using LonMaker and "No License for LonWorks Communication" error message appears: Shut down Vista software Open the drawing in LonMaker If it requests the contents of the recovery folder be removed, follow those instructions. Once the contents of the recovery folder are removed, open the drawing in LonMaker Launch Vista Server, and the license problem should be gone.  Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Webpages were able to be viewed from controllers in the past but no longer work. The controller can be pinged which indicates that it is online. Product Line Andover Continuum Environment B4920 BCX 99xx Windows OS Cause If running the latest versions of Microsoft Office, there are a lot of extensions installed in the registry under accepted documents which create a very long string for a HTTP request. Resolution In a test environment, Microsoft Office suite 2007 was installed for testing. Webpages could be opened from the bcx and 9702 controllers but not from the b4920 or webpages on a 9900. The latest Microsoft Office packages added a few accepted document extensions that allow things like word docs and spreadsheets to be opened in Internet Explorer. If the extensions are removed, the docs and xls files can still be downloaded and can be opened locally instead of through the browser. The TCP streams below show the different http request. Request with latest extensions: GET / HTTP/1.1 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/xaml+xml, application/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, */* Request with default extension: GET / HTTP/1.1 Accept: */* If running the latest versions of Microsoft Office, there are a lot of extensions installed in the registry under accepted documents which creates a very long string for a HTTP request. In order to work around this, you can edit the registry. Editing of the registry should be done with extreme caution. Be sure to export a copy of your registry. Look under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Accepted Documents Then you can export all of the keys under the above location and delete all but the default key. Once this has been done, restart your browser and you should be able to open your controller's webpages.

Issue The error below occurs as soon as the Management Console is launched.  Environment Power Manager Power Monitoring Expert (PME) Management Console Cause In order for the Management Console to work properly it needs to see the correct dll files in three separate locations. If the install process of PME was not completed successfully or did not have full administrative rights while installing then some of these files may be missing.  Resolution The issue was that the Licensing.LicenseManager.resources.dll and Licensing.LicenseManager.dll was not present in all of the three following folders:     C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Web\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\ReportDataService\bin Verify that the Licensing.LicenseManager.resources.dll and Licensing.LicenseManager.dll files are present in all three of the locations below. If they are missing in any location, copy and paste the files accordingly.      C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\Web\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\bin   C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\system\ReportDataService\bin     Note: Replace "Program Files (x86)" with "Program Files" if you are working on a 32 bit computer.   

Issue How to use a digital point card with a Network 8000 MicroZone II controller. Product Line TAC IA Series Environment Network 8000 MicroZone II controller Digital Point Card Cause To use the digital input cards (DPC-3-1 & DPC-3-2) with a MicroZone II controller, it requires a custom application file. Resolution The MicroZone II controller supports two digital input cards:  DPC-3-1 & DPC-3-2. A custom application file (1-DPC3.MZ2) is required to properly read the digital input card, review technical bulletin TB01-26 for more details. (Note: The DPC-5 series cards were designed for the MNL and MNB controllers.  They are compatible with the DUI Expander Object available for both controller lines.)

Issue StatusBackup "State" system variable is not able to be manually changed and attempting to set this variable to Enabled produces a script error instead of resetting the flash circuit breaker. Product Line EcoStruxure Building Operation Environment Building Operation v1.8 and below. b3/i2 Controllers Cause Feature to reset flash circuit breaker was not implemented in the earlier versions of Building Operation Resolution A new feature to reset the flash circuit breaker was implemented in Building Operation v1.9 to address this issue. The b3 BACnet Device Memory on-line help topic shows how this is manually reset from the WorkStation in the Device menu.

Issue Transfer pressure values with units of inches of water between I/NET and LON with a 913/527/731. Environment I/NET Xenta 913/527/731 XBuilder Cause When reading pressure from LON, the value is always in metric units, Pascals, on the LON wire. When the value comes into I/NET, it will be a large, unexpected number. Resolution To read in a LON pressure value into I/NET: Create two internal points in I/NET. AO to receive the raw pressure value in Pascals AI to perform the conversion to inches of water Add a calculation to the AI to perform the conversion: P0*C0 P0 = AO created to receive the raw pressure value in Pascals C0 = 0.004 to convert value from Pascals to inches of water Set the connection object in XBuilder: From = LON SNVT_press To = AO to receive the raw pressure value The AI should be reading the correct value in units inches of water. To write a setpoint value out of I/NET to LON: Create two internal points in I/NET: AO where the user enters desired static setpoint in inches of water AO to perform the conversion to Pascals Add a calculation to the AO to perform the conversion: P0*C0 P0 = AO created to enter desired static setpoint in inches of water C0 = 249 to convert value from inches of water to Pascals Set the connection object in XBuilder: From = AO to perform the conversion To = LON SNVT_press The SNVT should be reading the correct value in desired units.

Issue When the remote I/O modules (MNB-1000-15) are powered for the first time, the status LED stays blinking red. Product Line TAC IA Series Environment I/A Series MNB 1000 -15 Cause This is a normal operation. Resolution When the associated MNB-1000 receives a database configured with remote I/O modules, it will initiate communication with the remote I/O modules. If it is successful, then the status LED with turn green.

Issue Xenta 555/731 resets when an alarm is blocked or unblocked. Environment Xenta 555, 731 XBuilder Cause If you set an alarm object to email you when the alarm is blocked or unblocked, the Xenta will send the email, and change the alarm state to blocked or unblocked, but then performs a reset. Resolution Work around for now is to not check the blocked and unblocked condition to send emails in XBuilder

Issue WorkPlace Tech Tool menu functions and toolbar icons do not respond when selected even though they are visible (not grayed out) after changes are made to the Visio Menus or Toolbars. Product Line TAC IA Series Environment I/A Series WorkPlace Tech Tool software Cause Some COM add-ins are not compatible with the WorkPlace Tech Tool software. Resolution From the Visio menu, within WorkPlace Tech, select Tools / Customize then select the Toolbars tab. Select each checked toolbar in turn, clicking the reset button for each one. Next select the Options tab and click the "Reset menu & toolbar usage data" button. If this does not correct the issue, disable the COM add-ins and delete the Visio directory cache using the procedure listed below. The procedure depends on the version of Visio and the version of Windows being used. WorkPlace Tech with Visio 2007 Open Visio 2007 Open the Tools Pull down. Select the Options. Select the Trust Center Select Add-ins. Verify that the box "Disable all Application Add-ins" is NOT checked. At the bottom of the screen, COM Add-ins is the default selection. Press GO. In the COM Add-ins box displayed, un-check the box for the ",Send to Bluetooth", and any other third party add-ins. Click OK to apply. Close Visio 2007 Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\content12.dat If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\content12.dat Open Visio 2007 and wait for the "Getting Started with Microsoft Visio" window to be displayed. Close Visio 2007. Open WorkPlace Tech, all menu items should be there. If some or all of the WorkPlace Tech Tool menu entries are still grayed out, repeat these steps, disabling all COM add-ins. Workplace Tech with Visio 2003 Open Visio 2003 Open the Tools menu. Select Options, then Security. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2003. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista or Windows 7, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\content.dat If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\content.dat Open Visio 2003 and wait for the "Choose Drawing Type" window to be displayed. Close Visio 2003 Open WPT, all menu items should be there. Workplace Tech with Visio 2002 Open Visio 2002 Open the Tools menu. Select Options, then Advanced. Un-check the box for COM add-ins. Check the box for "Enable Microsoft Visual Basic for Applications". Check the box for "Enable Automation events" Click OK to apply. Close Visio 2002. Delete the Visio Directory Cache file, as follows, depending on the version of Windows. If running Windows Vista, delete the file c:\Users\< username> \AppData\Local\Microsoft\Visio\VISIO.BIN If running Windows XP, delete the file c:\Documents and Settings\< username> \Local Settings\Application Data\Microsoft\Visio\VISIO.BIN Open Visio 2002 and wait while Visio updates its directory cache. The process is complete when the "Choose Drawing Type" window is displayed. Close Visio 2002 Open WPT, all menu items should be there.

Issue TS-59XX 1,000 ohm copper sensors resistance table Environment TS-59XX Cause Converting Resistance to Temperature to characterize the sensor. Resolution Temp (°F) Temp (°C) Ohms -40 -40 759.8 -39 -39.44 762 -38 -38.89 764.2 -37 -38.33 766.4 -36 -37.78 768.6 -35 -37.22 770.8 -34 -36.67 772.9 -33 -36.11 775.1 -32 -35.56 777.3 -31 -35 779.5 -30 -34.44 781.7 -29 -33.89 783.9 -28 -33.33 786 -27 -32.78 788.2 -26 -32.22 790.4 -25 -31.67 792.6 -24 -31.11 794.8 -23 -30.56 797 -22 -30 799.1 -21 -29.44 801.3 -20 -28.89 803.5 -19 -28.33 805.7 -18 -27.78 807.9 -17 -27.22 810.1 -16 -26.67 812.2 -15 -26.11 814.4 -14 -25.56 816.6 -13 -25 818.8 -12 -24.44 821 -11 -23.89 823.2 -10 -23.33 825.3 -9 -22.78 827.5 -8 -22.22 829.7 -7 -21.67 831.9 -6 -21.11 834.1 -5 -20.56 836.3 -4 -20 838.4 -3 -19.44 840.6 -2 -18.89 842.8 -1 -18.33 845 0 -17.78 847.2 1 -17.22 849.2 2 -16.67 851.5 3 -16.11 853.7 4 -15.56 855.9 5 -15 858.1 6 -14.44 860.3 7 -13.89 862.5 8 -13.33 864.6 9 -12.78 866.8 10 -12.22 869 11 -11.67 871.2 12 -11.11 873.4 13 -10.56 875.6 14 -10 877.7 15 -9.44 879.9 16 -8.89 882.1 17 -8.33 884.3 18 -7.78 886.5 19 -7.22 888.7 20 -6.67 890.8 21 -6.11 893 22 -5.56 895.2 23 -5 897.4 24 -4.44 899.6 25 -3.89 901.8 26 -3.33 903.9 27 -2.78 906.1 28 -2.22 908.3 29 -1.67 910.5 30 -1.11 912.7 31 -0.56 914.9 32 0 917 33 0.56 919.2 34 1.11 921.4 35 1.67 923.6 36 2.22 925.8 37 2.78 928 38 3.33 930.1 39 3.89 932.3 40 4.44 934.5 41 5 936.7 42 5.56 938.9 43 6.11 941.1 44 6.67 943.2 45 7.22 945.4 46 7.78 947.6 47 8.33 949.8 48 8.89 952 49 9.44 954.2 50 10 956.3 51 10.56 958.5 52 11.11 960.7 53 11.67 962.9 54 12.22 965.1 55 12.78 967.3 56 13.33 969.4 57 13.89 971.6 58 14.44 973.8 59 15 976 60 15.56 978.2 61 16.11 980.4 62 16.67 982.5 63 17.22 984.7 64 17.78 986.9 65 18.33 989.1 66 18.89 991.3 67 19.44 993.4 68 20 995.6 69 20.56 997.8 70 21.11 1000 71 21.67 1002.2 72 22.22 1004.4 73 22.78 1006.5 74 23.33 1008.7 75 23.89 1010.9 76 24.44 1013.1 77 25 1015.3 78 25.56 1017.5 79 26.11 1019.6 80 26.67 1021.8 81 27.22 1024 82 27.78 1026.2 83 28.33 1028.4 84 28.89 1030.6 85 29.44 1032.7 86 30 1034.9 87 30.56 1037.1 88 31.11 1039.3 89 31.67 1041.5 90 32.22 1043.7 91 32.78 1045.8 92 33.33 1048 93 33.89 1050.2 94 34.44 1052.4 95 35 1054.6 96 35.56 1056.8 97 36.11 1058.9 98 36.67 1061.1 99 37.22 1063.5 100 37.78 1065.5 101 38.33 1067.7 102 38.89 1069.9 103 39.44 1072 104 40 1074.2 105 40.56 1076.4 106 41.11 1078.6 107 41.67 1080.8 108 42.22 1083 109 42.78 1085.1 110 43.33 1087.3 111 43.89 1089.5 112 44.44 1091.7 113 45 1093.9 114 45.56 1096.1 115 46.11 1098.2 116 46.67 1100.4 117 47.22 1102.6 118 47.78 1104.8 119 48.33 1107 120 48.89 1109.2 121 49.44 1111.3 122 50 1113.5 123 50.56 1115.7 124 51.11 1117.9 125 51.67 1120.1 126 52.22 1122.3 127 52.78 1124.4 128 53.33 1126.6 129 53.89 1128.8 130 54.44 1131 131 55 1133.2 132 55.56 1135.4 133 56.11 1137.5 134 56.67 1139.7 135 57.22 1141.9 136 57.78 1144.1 137 58.33 1146.3 138 58.89 1148.5 139 59.44 1150.6 140 60 1152.8 141 60.56 1155 142 61.11 1157.2 143 61.67 1159.4 144 62.22 1161.6 145 62.78 1163.7 146 63.33 1165.9 147 63.89 1168.1 148 64.44 1170.3 149 65 1172.5 150 65.56 1174.7 151 66.11 1176.8 152 66.67 1179 153 67.22 1181.2 154 67.78 1183.4 155 68.33 1185.6 156 68.89 1187.8 157 69.44 1189.9 158 70 1192.1 159 70.56 1194.3 160 71.11 1196.5 161 71.67 1198.7 162 72.22 1200.9 163 72.78 1203 164 73.33 1205.2 165 73.89 1207.4 166 74.44 1209.6 167 75 1211.8 168 75.56 1214 169 76.11 1216.1 170 76.67 1218.3 171 77.22 1220.5 172 77.78 1222.7 173 78.33 1224.9 174 78.89 1227.1 175 79.44 1229.2 176 80 1231.4 177 80.56 1233.6 178 81.11 1235.8 179 81.67 1238 180 82.22 1240.2 181 82.78 1242.3 182 83.33 1244.5 183 83.89 1246.7 184 84.44 1248.9 185 85 1251.1 186 85.56 1253.3 187 86.11 1255.4 188 86.67 1257.6 189 87.22 1259.8 190 87.78 1262 191 88.33 1264.2 192 88.89 1266.4 193 89.44 1268.5 194 90 1270.7 195 90.56 1272.9 196 91.11 1275.1 197 91.67 1277.3 198 92.22 1279.5 199 92.78 1281.6 200 93.33 1283.8 201 93.89 1286 202 94.44 1288.2 203 95 1290.4 204 95.56 1292.6 205 96.11 1294.7 206 96.67 1296.9 207 97.22 1299.1 208 97.78 1301.3 209 98.33 1303.5 210 98.89 1305.7 211 99.44 1307.8 212 100 1310 213 100.56 1312.2 214 101.11 1314.4 215 101.67 1316.6 216 102.22 1318.8 217 102.78 1320.9 218 103.33 1323.1 219 103.89 1325.3 220 104.44 1327.5 221 105 1329.7 222 105.56 1331.9 223 106.11 1334 224 106.67 1336.2 225 107.22 1338.4 226 107.78 1340.6 227 108.33 1342.8 228 108.89 1345 229 109.44 1347.1 230 110 1348.3 231 110.56 1351.5 232 111.11 1353.7 233 111.67 1355.9 234 112.22 1358.1 235 112.78 1360.2 236 113.33 1362.4 237 113.89 1364.6 238 114.44 1366.8 239 115 1369 240 115.56 1371.2 241 116.11 1373.3 242 116.67 1375.5 243 117.22 1377.7 244 117.78 1379.9 245 118.33 1382.1 246 118.89 1384.3 247 119.44 1386.4 248 120 1388.6 249 120.56 1390.8 250 121.11 1393

Issue TS-58XX 1,000 Ohm Platinum sensors resistance table Environment TS-58XX 1,000 Ohm Platinum Cause Resistance tables are sometimes required for compatibility measures. Resolution Temp (°C) Temp (°F) Ohms -40 -40 842.7 -39 -38.2 846.7 -38 -36.4 850.6 -37 -34.6 854.6 -36 -32.8 858.5 -35 -31 862.5 -34 -29.2 866.4 -33 -27.4 870.4 -32 -25.6 874.3 -31 -23.8 878.3 -30 -22 882.2 -29 -20.2 886.1 -28 -18.4 890.1 -27 -16.6 894 -26 -14.8 898 -25 -13 901.9 -24 -11.2 905.8 -23 -9.4 909.8 -22 -7.6 913.7 -21 -5.8 917.7 -20 -4 921.6 -19 -2.2 925.5 -18 -0.4 929.5 -17 1.4 933.4 -16 3.2 937.3 -15 5 941.3 -14 6.8 945.2 -13 8.6 949.1 -12 10.4 953 -11 12.2 957 -10 14 960.9 -9 15.8 964.8 -8 17.6 968.7 -7 19.4 972.6 -6 21.2 976.5 -5 23 980.5 -4 24.8 984.4 -3 26.6 988.3 -2 28.4 992.2 -1 30.2 996.1 0 32 1000 1 33.8 1003.9 2 35.6 1007.8 3 37.4 1011.7 4 39.2 1015.6 5 41 1019.5 6 42.8 1023.4 7 44.6 1027.3 8 46.4 1031.2 9 48.2 1035.1 10 50 1039 11 51.8 1042.9 12 53.6 1046.8 13 55.4 1050.7 14 57.2 1054.6 15 59 1058.5 16 60.8 1062.3 17 62.6 1066.2 18 64.4 1070.1 19 66.2 1074 20 68 1077.9 21 69.8 1081.8 22 71.6 1085.7 23 73.4 1089.5 24 75.2 1093.4 25 77 1097.3 26 78.8 1101.2 27 80.6 1105.1 28 82.4 1108.9 29 84.2 1112.8 30 86 1116.7 31 87.8 1120.6 32 89.6 1124.4 33 91.4 1128.3 34 93.2 1132.2 35 95 1136.1 36 96.8 1139.9 37 98.6 1143.8 38 100.4 1147.7 39 102.2 1151.5 40 104 1155.4 41 105.8 1159.3 42 107.6 1163.1 43 109.4 1167 44 111.2 1170.8 45 113 1174.7 46 114.8 1178.6 47 116.6 1182.4 48 118.4 1186.3 49 120.2 1190.1 50 122 1194 51 123.8 1197.9 52 125.6 1201.7 53 127.4 1205.6 54 129.2 1209.4 55 131 1213.3 56 132.8 1217.1 57 134.6 1221 58 136.4 1224.8 59 138.2 1228.7 60 140 1232.5 61 141.8 1236.3 62 143.6 1240.2 63 145.4 1244 64 147.2 1247.8 65 149 1251.7 66 150.8 1255.5 67 152.6 1259.3 68 154.4 1263.1 69 156.2 1267 70 158 1270.8 71 159.8 1274.6 72 161.6 1278.4 73 163.4 1282.3 74 165.2 1286.1 75 167 1289.9 76 168.8 1293.7 77 170.6 1297.5 78 172.4 1301.4 79 174.2 1305.2 80 176 1309 81 177.8 1312.8 82 179.6 1316.6 83 181.4 1320.4 84 183.2 1324.2 85 185 1328.1 86 186.8 1331.9 87 188.6 1335.7 88 190.4 1339.5 89 192.2 1343.3 90 194 1347.1 91 195.8 1350.9 92 197.6 1354.7 93 199.4 1358.5 94 201.2 1362.3 95 203 1366.1 96 204.8 1369.9 97 206.6 1373.7 98 208.4 1377.5 99 210.2 1381.3 100 212 1385.1 101 213.8 1388.9 102 215.6 1392.7 103 217.4 1396.4 104 219.2 1400.2 105 221 1404 106 222.8 1407.8 107 224.6 1411.6 108 226.4 1415.3 109 228.2 1419.1 110 230 1422.9 111 231.8 1426.7 112 233.6 1430.5 113 235.4 1434.2 114 237.2 1438 115 239 1441.8 116 240.8 1445.6 117 242.6 1449.4 118 244.4 1453.1 119 246.2 1456.9 120 248 1460.7

Issue When importing an application file created or previously edited with release 3.2sp1 of WorkPlace Tech, a "Workplace Tech Tool - Visio" error window is displayed:  "Cannot find the WorkPlace Tech add-ons for Visio.  WorkPlace Tech functions will be unavailable" Product Line TAC IA Series Environment WorkPlace Tech Tool software release 5.7.4 WorkPlace Tech application file created or edited with WorkPlace Tech Tool software release 3.2sp1. Cause The Visio stencil pages referenced in the application file cannot be found in the location specified in the application file. Resolution This is not a fatal error.  It occurs because WorkPlace Tech cannot locate the Visio object stencil files referenced in the existing application drawing file.   Click the [OK] button to ignore the error message and continue with the application file upgrade.  The error message is displayed because the default location for the stencils has been moved starting with WorkPlace Tech version 5.7.4.  During the application file upgrade, the proper stencils, as specified in the original application file, will be located and attached to the application. After clicking the [OK] button, WorkPlace Tech will display a Windows message box indicating that the application must be converted to WorkPlace Tech (WPT) 5.0 format before it can be modified or downloaded.  The message ends with a prompt asking the user if they would like the application converted.  Clicking [Yes] will allow WorkPlace Tech to process the application file and convert it to the current file format.  This is the required choice if the user intends to use the imported application in the current version of the WorkPlace Tech Tool software. Clicking [No] will bypass the conversion leaving the incompatible application open in WorkPlace Tech. Clicking [Cancel] will abort the import process.

Issue These errors are internal to Echelon LonMaker and require the assistance of Echelon Technical Support. Environment LNS LonMaker Vista NL220 LonSupport@Echelon.com 1-800-258-4LON or 1-800-258-4566 Cause NS #9 lcaErrNsBadClient NS #11 lcaErrNsNoClient NS #14 lcaErrNsClientBlocked NS #16 lcaErrNsNotImplemented NS #18 lcaErrNsServiceFailure NS #20 lcaErrNsPrematureRelease NS #21 lcaErrNsRootBus NS #22 lcaErrNsRootDoesNotExist NS #23 lcaErrNsNoFreeRootTransactions NS #30 lcaErrNsEventFailure NS #32 lcaErrNsSubscriptionDblimit NS #34 lcaErrNsSegmentation NS #41 lcaErrNsDbError NS #42 lcaErrNsOutOfJournal NS #46 lcaErrNsNetworkHasInstalledNodes NS #49 lcaErrNsIntegrityError NS #55 lcaErrNsProgramDblimit NS #57 lcaErrNsNvmtDbLimit NS #61 lcaErrNsMsgError NS #62 lcaErrNsCancelError NS #71 lcaErrNsTimerRange NS #83 lcaErrNsObjectLocked NS #84 lcaErrNsInvalidContext NS #85 lcaErrNsServerNotFound NS #109 lcaErrNsStaleFileHandle NS #115 lcaErrNsManagerNotAllowed NS #126 lcaErrNsUnimplementedCategory NS #127 lcaErrNsUnimplementedProperty NS #128 lcaErrNsDisallowedInMipMode NS #129 lcaErrNsDisallowedInTxHandler NS #130 lcaErrNsNssNotInitialized NS #146 lcaErrNsInvalidErrorContext NS #151 lcaErrNsBatchOptionNotImplemented NS #152 lcaErrNsBatchNoResult NS #172 lcaErrNsEngineNotInitialized NS #189 lcaErrNs16BitUserErrorCode NS #190 lcaErrNs16BitWarningCode NS #191 lcaErrNs16BitErrorCode NS #289 lcaErrNsEngineIsSuspended NS #290 lcaErrNsNotSupportedFromRemoteClient NS #4031 lcaErrNsUpdateFuncError NI #24 lcaErrNiObsolete NI #27 lcaErrNiUnimplemented LNS #5 lcaErrUninitializedDb LNS #35 lcaErrGeneric LNS #36 lcaErrDbServer LNS #39 lcaErrWrongWriteDataSize LNS #40 lcaErrInvalidFormat LNS #54 lcaErrCantCopyLNSDirectory LNS #70 lcaErrCantRecoverReadOnlyFile LNS #71 lcaErrStringIsEmpty LNS #73 lcaErrInvalidProgramType LNS #97 lcaErrInvalidRmcObject LNS #98 lcaErrInvalidRmcServer LNS #99 lcaErrInvalidRmcClient LNS #101 lcaErrInvalidRmcMethod LNS #123 lcaErrInvalidPropChangeEvent LNS #133 lcaErrInternalErrBadExceptionCode LNS #134 lcaErrInternalErrBadHresultExceptionCode LNS #135 lcaErrInternalErrBadVNIDataServer LNS #136 lcaErrInternalErrBadNsdHandle LNS #137 lcaErrInternalErrStartTransaction DS #365 lcaErrLnsDsUnexpected DS #366 lcaErrLnsDsFailed Resolution These are internal errors and should be reported to Echelon's customer support. Contact Echelon at 1-800-258-4LON (258-4566) or LonSupport@Echelon.com.

Issue Adding a Xenta Programmable Controller to an NL220 System Product Line TAC Vista Environment NL220 Cause Commissioning a Xenta programmable controller in NL220 needs to follow a certain procedure in order to prevent various issues from occurring, such as controllers not showing online in Vista Workstation, etc. Resolution Adding a Xenta Programmable Controller to an NL220 LNS system. Preparation: Create the Menta File Install the Controller Adding the Device to the LNS database NL220:Create a Template for the device type. See NL220 Useful Functions and Shortcuts on how to create a template. NL220:Add a node using the correct device Template System plug-in: Assign Neuron ID and Menta file Add and match I/Os if applicable Bring the Device to the Vista Database System plug-in: Update TAC Network Drag controller to an existing group if desired, and delete the now empty group  Create group bindings Assign Neuron ID for the I/O modules Update the TAC Network again Check TAC Network Update Vista Database Check that your network is attached and OnNet  Download Application and Parameters Bring Vista Db online NL220: Commission and download the device (ignore I/O modules.) System plug-in: Commence Communication (if needed) NOTE:  It is very important that you Download Application and Parameters in the Vista system plug in THEN Commission the device in NL220. 

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

Issue Will public signals in TAC Xenta show up in Echelon Lonmaker? Will AI, DI, AO, DO, PVR, PVI, PVB blocks show up in Echelon Lonmaker?  Product Line TAC Vista Environment TAC Menta LonMaker or NL220 Xenta 30x, 401, 28x Cause Public signal are proprietary and can only be viewed from Schneider Electric products such as TAC Vista Workstation or EcoStruxure Building Operation. Resolution The answer to both questions is no. Only SNVTs are displayed in Echelon Lonmaker, and the SNVTs have to be added in TAC Menta and then downloaded to the TAC Xenta devices.

Issue "No license for LonWorks communication" Error when starting Workstation. Product Line TAC Vista Environment Windows 2008 Server X64 TAC Vista 5.1.5 Cause Windows Server is member of a domain. Configure the TAC Vista Server to run as a service, with a local user set as administrator to logon. Results in "No license for LonWorks communication" when starting Workstation. If starting the service with a domain user or local system, it works.  Resolution Windows Security Policy This may have something to do with UAC (User Account Control) in Windows. The user that launches TAC Vista was already as a local administrator, but it seems that a log out with the user, log in with a local user, and log back in with a domain user is necessary for some policies to be set. Licensing Registry The Vista licensing requires registry information on where to find a license file. This registry key is found in the following location: HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE If the user has not been logged in and configured to run Vista software, this key might be missing or misconfigured. Ensure that it has a proper value by launching Vista Workstation or running the TAC License Setup. Log in with the user that will run the TACOS service and run the License Server Setup application to ensure the correct file path is defined in the Registry.   Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility