Building Automation Knowledge Base

Issue Unable to connect to a Niagara R2 UNC-520.  The IP address was incorrectly set.  How can the IP address be found and changed if there's no access via the Ethernet port? Environment UNC-520 or UNC-410 Cause Incorrect entry of the IP Address or subnet mask can cause the UNC appear unresponsive to the WorkPlace Pro software. Resolution There are two methods available to determine the IP and subnet mask entered into the UNC. The first method requires having access to the computer used to change the IP address.  Look at the file "ipchanges.txt" located in the "\Niagara\r2.301.522\nre\user" folder. It will contain the date, time, user name, original IP, new IP, and controller name (i.e. 9:54 16-Dec-2008 CST: tac 10.159.34.123 -> 10.1.146.128 on J404-29764). The second method requires the use of a terminal program, a UNCC-405 to adapt RS232 to RJ45, and a CBL-RJ45 cable (a standard ethernet cable no longer than seven feet will do).  The HyperTerminal program is used to directly connect to a UNC-520 to verify and to make changes to its IP address in order to make it accessible.  HyperTerminal makes it possible to view the UNC's configuration and execute commands. The steps needed to directly connect to a UNC-520 using HyperTerminal are listed in chapter 2 of the Niagara Networking & Connectivity Guide.  After connecting to the UNC, use the procedure "Determining an IP address of a JACE-4/5" in the section "Determining Network Settings" of Chapter 3 of the same manual to display or change the IP address or subnet mask.  Failure to enter the subnet mask properly can prevent the UNC from being seen by WorkPlace Pro.

Issue Are MNB controllers RoHS compliant? Environment MNB controllers Cause Restrict dangerous substances commonly used in electronic and electronic equipment. Resolution All controller final assemblies will be RoHS compliant by the end of the 1st quarter of 2010.

Issue How can two Niagara G3 stations run simultaneously on a computer? Product Line TAC IA Series Environment Niagara G3 PC Cause To run two stations simultaneously on a PC, you must set up two ports to be different: The http port and the Fox port. Resolution Open the second station offline via My File System – Sys Home - Stations. Go to Services – Web Services – Properties – Http Port. Change it from 80 to 8080. In the offline station, go to Drivers – Niagara Network – Properties. Expand the Fox Service and change the Port to 1912. Be sure to save the changes and the bog file. Go to Platform – Application Director. Start the second station that you just edited offline. You should see the new ports under "Details."  Go to File - Open Station. Enter the IP address, but change the port to 1912. You should now be able to go to the Niagara Network and discover one station from the other on the same IP.

Issue How to display the degrees symbol (°) in WorkPlace Tech. Product Line TAC IA Series Environment WorkPlace Tech Cause Helpful to add a suffix for temperature engineering units. Instead of typing "degrees" or "deg". Resolution In the Constant Object properties (double click or right click - Set Value), click in the Suffix Text field.    Desktop PC: If you have a desktop PC with a full keyboard, press and hold the Alt key and type the number 248 on the numeric keypad. Note: The number keys above the keyboard will not work. Notebook PC: The numeric keypad on a notebook PC is overlaid on the letter keys (M, J, K, L, U, I, O, 7, 8, 9), and requires that the Fn key is held down while using this secondary purpose. The Fn key may be colored blue to match the number keypad keys. Press and hold both the Alt and Fn keys and type the number 248 (KU8). Release the Alt key (and Fn key on the laptop). A small circle ° (the symbol for degrees) should appear. Type an upper case F for Fahrenheit or C for Celsius. Click OK.   Other ASCII symbols are defined at asciitable.com or lookuptables.com.

Issue Problems adding i2 or b3 controllers to systems and causing the network to go down or devices to not learn on. Product Line Andover Continuum Environment i2 Controller b3 Controller Cause Duplicate ID's,  incorrect baud rates or faulty controller Resolution Infinet and BACnet field controllers have the capability to autobaud and auto correct duplicate ID's on a network. They do this by listening to the network on powerup and determining what Baud Rate and currently operating controller ID's are on the network. If an existing controller is on the network and the newly added controller has the same ID assigned, the new controller will zero out its own ID so as not to cause a network problem with duplicate ID's. Then learning or manually commissioning the controller will give it a unique ID. It is therefore critical that when adding a controller to a network, that the controller is connected to the network before the controller is powered up.  Failure to do so could cause network problems such as duplicate ID's or conflicting baud rates which could bring the network down. If the new controller causes these types of problems it is recommended to power down the suspect controller(s) and re-power them to eliminate these issues.  Run acctrace when the learn is being done and there will be an indication of what is happening.  Send a controller error log to PSS.   If nothing else works even with a clean database then replace the Master and if that works send the controller in to repair.

Issue Troubleshooting sending email alarms from a Vista Server Mail error 1 – MAIL client needs to be configured first Mail error 2 – Couldn’t connect to server. Error:0  Mail error 2 – Couldn’t connect to server. Error:10022 Mail error 2 – Couldn’t connect to server. Error:10061 Mail error 3 – Couldn’t send message. Response:550 Mail error 3 – Couldn’t send message. Response:503 Unable to relay Product Line TAC Vista Environment SMTP Server Vista Server Workstation Cause There are many reasons why an emailed alarm from a Vista Server wouldn't reach the desired destination inbox.  This document walks through the most common settings and networking issues and how to overcome them. Resolution Vista can be configured to send out alarms via email.  Typically, following the instructions found in the TAC Vista Technical Manual will result in successful delivery of email alarms.  However, there are some factors that can hinder these email messages.  This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Vista alarms to email out is to configure the Server Setup.  Reference Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any).  If no SMTP server or login information has been provided, contact an IT professional at the customer’s site to obtain this information. Once Vista Server Setup is correctly configured you must restart the Vista Server. After the Server has been stopped and restarted, set up an Alarm Control Object and an Alarm Receiver – Email.  The steps for this can be found in Chapter 18 Alarm Processing in the TAC Vista Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses.  Then the distribution list can be edited and maintained by the IT staff without ever having to access Vista. If everything is set up correctly, test the email alarm receiver by forcing an alarm condition.  The alarm should show up in the Vista Alarm Queue as well as at the alarm receiver’s designated inbox.  If the email does not arrive as expected, proceed to the next section of this document titled “Check Vista for Alarms/Errors.” Check Vista for Alarms/Errors If emails are not showing up when expected, the first place to begin the investigation is in Vista Workstation’s Alarm Queue.  There are helpful messages that may appear based on some criteria.  The Alarms will all come from $EE_Mess object under the Vista Server.  Sort the Alarm Queue by Last Change if the alarm just happened, or by Object ID to find the $EE_Mess alarms. Server-$EE_Mess Mail error 1 – MAIL client needs to be configured first Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10022 Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10061 Figure 1.  Vista Alarm Queue Mail Errors There are three possible errors that can be seen in the Vista Alarm Queue.  They should occur within a few seconds of the alarm if there is an error connecting to the SMTP server.  If the alarms are acknowledged or disabled, they may not show up in the Vista Alarm Queue.  The other place to look for them is under the Vista database folder on the hard drive.  Inside the database structure there is a folder called $log.  Inside this folder should be a file called b0warlog.txt.  Open this file and scroll to the time/date where the alarm occurred.  If an error occurred, the same text that appears in the Alarm Queue will appear in the error log in a slightly different format.  An example: Mon Aug 17 08:16:26 2009 alrdisp >> Error from SMTPSendMail: Mail error 1 – Mail client needs to be configured first Three possible alarm conditions are discussed here: Mail error 1 – MAIL client needs to be configured first This error refers to the TAC Vista Server Setup.  Refer back to Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  If the server is setup correctly, be sure that the server has been restarted since the last change.  Changes in Server Setup will not take effect until the next time server is run. Mail error 2 – Couldn’t connect to server.  Error:0 Unknown cause. Mail error 2 – Couldn’t connect to server.  Error:10022 This error means that the SMTP server is unreachable.  If using a DNS name for the SMTP server, double check the spelling.  If everything looks correct, move to section of this document titled “Check SMTP Server Connectivity” and follow the steps described there. Mail error 2 – Couldn’t connect to server.  Error:10061 This error means that the SMTP server has been reached, but Vista was not allowed access to the server.  Double check the authentication username and password.  Re-enter the password to ensure it is correct (only dots are shown for privacy).  There are three different authentication modes to choose from: CRAM MD5 – (Safest) Password is coded with Message Digest 5. AUTH LOGIN – (Standard) Password coded with base64 method. LOGIN PLAIN – Password is sent uncoded. If the correct authentication mode has not been provided, it may require trying all three until the mail error clears.  If all three result in an error, contact an IT professional to be provided with a valid username and password.  Use the section of this document titled “Contacting an IT Professional” for a template to request this information. Mail error 3 – Couldn’t send message.  Response:550 Unknown user Unknown cause. Mail error 3 – Couldn’t send message.  Response:503 Must have sender and recipient first. Unknown cause.  If no errors occur in the Vista Alarm Queue or in the Vista alarm log text document, refer to the section of this document titled “Vista Indicates No Errors” for more troubleshooting techniques. For troubleshooting unknown errors, read Troubleshooting sending emails using WireShark. Unable to relay If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Go to Vista Server settings At the email tab set proper authentication (Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established.  In this example, the provided SMTP server is “smtp.ACME.com.”  Pinging is the lowest level of internet communication.  A successful ping will not guarantee communication with an IP device, but a failed ping will guarantee no communication.  Open a new DOS command prompt (Start > Programs > Accessories > Command Prompt).  Ping the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 2.  Failed Ping Example In Figure 2, a request to ping the SMTP server has failed.  Check that the computer where Vista Server resides has internet connectivity (Start > Settings > Network Connections).  Make sure the connection status is Connected, navigate to an internet website, or ping a known IP address.  If those fail, check the computer’s IP settings.  Figure 3.  TCP/IP Properties - Obtain IP Automatically If the computer is set to obtain an IP address automatically make sure that an IP address has been assigned.  Figure 4.  Local Area Connection Status If no IP address has been defined, then the DHCP server is not available and the computer is not connected a network.  Check the physical connections and contact an IT professional to determine why the DHCP server is not assigning the PC an IP address. If the TCP/IP properties are configured to use a static IP address (which is common in applications where WebStation or ScreenMate are employed), then the DNS server address must also be defined if a DNS SMTP server is used.  Figure 5.  TCP/IP Properties - Static IP If DNS is causing problems, it is possible to bypass this by using the IP address for the SMTP server as opposed to the DNS name. Look back to Figure 2 to obtain the SMTP server’s resolved IP address.  In this example, the IP is 10.10.10.10.  Figure 6.  Using IP Address of SMTP Server When everything is set correctly, try to ping the SMTP server again.  This time, it should go through successfully, which is an indication that most of the basic settings are correct – but should not be viewed as indication that email messages will successfully be delivered by the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 7.  Successful Ping Example In Figure 7, the ping has returned four successful results.  This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating.  It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 8.  Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 9.  Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220.  Type the word “helo” and press enter.  The SMTP server should again respond but this time with a line starting with 250.  Exit the telnet session by typing “quit” and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 10.  Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Vista Server.  That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled “Vista Indicates No Errors.” Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below) Figure 11. Enable Telnet Client. Vista Indicates No Errors If no errors show up in either the Vista Alarm Queue or the $log folder, then Vista has successfully contacted a valid SMTP server.  Review Chapter 18 Alarm Processing in the TAC Vista Technical Manual.  Make sure that the alarm is using the correct Alarm Handler that is assigned the correct Alarm Receiver that has the correct valid email addresses defined. If the alarms are set up correctly, the focus should now shift to troubleshooting the SMTP server itself.  Assistance from an IT professional will be helpful at this stage.  Things to check include: Check the incoming/outgoing messages from the SMTP server.  See if the messages from Vista are arriving but not being sent out.  Many companies will set up an “allowed” list that will only pass emails from recognized IP addresses, and all else is filtered as spam.  Make sure the Vista Server’s IP address is listed on the acceptable list. Ask what port the SMTP communication is using.  Port 25 is typically used for SMTP communication, but some companies will change this for security purposes.  Request that port 25 be opened for SMTP communication from the Vista Server.  If this is not an option, the port can be changed manually using registry settings.  See the section of this document titled “Changing the default SMTP Port” for instructions. Look at the selected Text encoding in the Vista Server Setup.  Unicode (UTF-8) is the most common in America and Europe.  If encoding is set to UTF-7, some SMTP servers will filter the messages out as spam. Some companies will block all POP messages on the network.  This will disable the ability to use external SMTP servers.  Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the Default SMTP Port Vista defaults to using Port 25 for all SMTP communication.  This is the standard port for SMTP and is typically used by SMTP servers.  However, because it is so well known as the SMTP port, some companies prefer to change this as a security measure.  Request that port 25 be made available to the Vista Server.  Unfortunately, sometimes this is just not possible because of security procedures.  If a different port is required, it is possible to manually change the port by navigating through registry keys. Open up the Registry Editor on the Vista Server PC (Start > Run… > regedit).  Navigate to: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > TAC AB > TAC Vista > 5.1.2 > SMTP Depending on the version of Vista, the path may change slightly.  If a 64-bit operating system is being used, the path will be: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > TAC AB > TAC Vista > 5.1.5 > SMTP Navigate until the SMTP folder is located.  Inside the SMTP folder, the SMTP settings that were set with Vista Server Setup can be viewed.  There is also an additional registry key defining the port.  Figure 12.  SMTP Registry Settings If there is no registry key for Port, create one.  Right click in the key view window, but not on an existing key.  Select New > DWORD Value.  Name the new value “Port.” Double-click the Port registry key to edit.  Radio buttons convert the value from hexadecimal to decimal.  Ports are typically described in decimal values.  Switch to decimal, enter the required port number, and click OK. Figure 13.  Editing Port Registry Key Verify that the value had changed in the registry.  Vista should now be sending out SMTP communication on the required port. Contacting an IT Professional If you need help contacting the customer’s IT department to gather and share the correct data, use the document attached in Appendix A:  IT Request for Information.  A completed example is shown in Appendix B:  Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice.  It is also subject to change with versions of TAC Vista.  If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable):   Password (if applicable):   Text encoding (if filtered):   To distribution list (if any):   Required TCP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses):   From name:   From email address:   From IP address:   Desired TCP port: 25 Appendix B:  Sample IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable): emailuser Password (if applicable): password123 Text encoding (if filtered): UTF-8 To distribution list (if any): facilities_staff@thebuilding.com Required TCP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses): facilities_staff@thebuilding.com From name: Vista Server From email address: vista @server.com From IP address: 10.10.10.20 Desired TCP port: 25

Issue Existing documentation for showing damper feedback and provide damper calibration is applicable only for Continuum and the same steps will not work in SmartStruxure. Product Line EcoStruxure Building Operation Environment SmartStruxure i2866-V b3866-V Cause Damper feedback and calibration for these controllers do not work the same in SmartStruxure as they do in Continuum. Resolution The correct damper feedback can be shown, but will require a script program to correctly calculate this and then write this back to an Analog_Value. Unfortunately, it is not possible to bind directly to the "LCD State" attribute to be able to toggle this (and the damper calibration feature) from within a Script Program. For now, toggle this attribute of the Damper Output manually from "enabled" to "disabled" and back. This will set the damper to drive closed fully, then open fully, then to about 75%. After this is calibrated properly the "Override Value" attribute in the Damper Output will update with likely a very large and strange-looking number. To convert this to something usable, multiply this value by 100 to give a percentage open value. See Zip file with XML code and screenshots of the configuration with notes. Either import supplied XML file into b3866-v or create below objects: Create DamperOutput as a multistate output. Assign to channel 1. Create DamperPos AnalogValue. Create Script Program Damper_Position and input code as shown in image. This will be a looping program. Bind DamperOverrideValue to the OverrideValue attribute of the Damper Output and DamperPosition to the DamperPos AnalogValue we created earlier. See image for details. After the points and program is created and the damper calibrated, you should see the DamperPos AnalogValue update with a live representation of the current Damper Position.

Issue In the Xenta Servers, it is possible to set the communication port to RS232 or RS485. In EBO this is not possible on the Automation Server (AS) Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server  Xenta 500 Xenta 700 Xenta 900 Cause The AS serial ports are RS-485, not RS-232. Resolution There are two solutions to consider when Xenta is using an RS-232 connection: If the connected device also has a RS-485 connection switch to that. (Optionally replace the device with one that has RS-485.) Use a RS-232/RS-485 converter. The converter must have automatic data direction detection and control on the RS-485 side, since our Automation Server devices have no RTS signal (to enable the transmitter) available externally.

Issue Vista to I/NET Integration Tips Product Line TAC INET, TAC Vista Environment I2V Integration I/NET XBuilder Xenta 913 Xenta 527 Cause An input in I/NET can only be controlled from an outside source if it is in "Test" or "Manual," so outputs must be used. Resolution When integrating with an I/NET system using a Xenta 5/7/9xx, all I/NET points must be defined as either AO or DO, regardless of the direction of information flow. To get data from an I/NET system (into Lon, BACnet, or Modbus) use the AO attribute "value" or DO attribute "value." To get data into an I/NET system (from Lon, BACnet or Modbus) use the AO attribute "value" or DO attribute "control."

Issue TS-8XXX and TS-9XXX 1,1000 Ohm Balco sensor, Fahrenheit resistance table. Product Line Field Devices Environment Field devices Balco temperature sensors Cause Reference for integration and calibration Resolution Download spreadsheet file of chart below.     Temp (°F) Resistance (Ohms) Temp (°F) Resistance (Ohms) Temp (°F) Resistance (Ohms) -50 760.816 50 956.9 150 1185.2 -49 762.6 51 959 151 1187.7 -48 764.4 52 961.2 152 1190.1 -47 766.2 53 963.3 153 1192.6 -46 768 54 965.4 154 1195 -45 769.9 55 967.6 155 1197.5 -44 771.7 56 969.7 156 1199.9 -43 773.5 57 971.8 157 1202.4 -42 775.3 58 974 158 1204.9 -41 777.1 59 976.1 159 1207.3 -40 779 60 978.3 160 1209.8 -39 780.8 61 980.5 161 1212.3 -38 782.6 62 982.6 162 1214.8 -37 784.5 63 984.8 163 1217.3 -36 786.3 64 986.9 164 1219.7 -35 788.2 65 989.1 165 1222.2 -34 790 66 991.3 166 1224.7 -33 791.9 67 993.5 167 1227.2 -32 793.7 68 995.6 168 1229.7 -31 795.6 69 997.8 169 1232.2 -30 797.5 70 1000 170 1234.7 -29 799.3 71 1002.2 171 1237.3 -28 801.2 72 1004.4 172 1239.8 -27 803.1 73 1006.6 173 1242.3 -26 804.9 74 1008.8 174 1244.8 -25 806.8 75 1011 175 1247.3 -24 808.7 76 1013.2 176 1249.8 -23 810.6 77 1015.4 177 1252.4 -22 812.5 78 1017.6 178 1254.9 -21 814.4 79 1019.8 179 1257.4 -20 816.3 80 1022 180 1260 -19 818.2 81 1024.2 181 1262.5 -18 820.1 82 1026.5 182 1265.1 -17 822 83 1028.7 183 1267.6 -16 823.9 84 1030.9 184 1270.2 -15 825.8 85 1033.2 185 1272.7 -14 827.7 86 1035.4 186 1275.3 -13 829.6 87 1037.6 187 1277.8 -12 831.5 88 1039.9 188 1280.4 -11 833.5 89 1042.1 189 1283 -10 835.4 90 1044.4 190 1285.6 -9 837.3 91 1046.6 191 1288.1 -8 839.3 92 1048.9 192 1290.7 -7 841.2 93 1051.1 193 1293.3 -6 843.1 94 1053.4 194 1295.9 -5 845.1 95 1055.7 195 1298.5 -4 847 96 1057.9 196 1301 -3 849 97 1060.2 197 1303.6 -2 850.9 98 1062.5 198 1306.2 -1 852.9 99 1064.8 199 1308.8 0 854.8 100 1067 200 1311.4 1 856.8 101 1069.3 201 1314 2 858.8 102 1071.6 202 1316.7 3 860.7 103 1073.9 203 1319.3 4 862.7 104 1076.2 204 1321.9 5 864.7 105 1078.5 205 1324.5 6 866.7 106 1080.8 206 1327.1 7 868.6 107 1083.1 207 1329.8 8 870.6 108 1085.4 208 1332.4 9 872.6 109 1087.7 209 1335 10 874.6 110 1090 210 1337.7 11 876.6 111 1092.3 211 1340.3 12 878.6 112 1094.7 212 1342.9 13 880.6 113 1097 213 1345.6 14 882.6 114 1099.3 214 1348.2 15 884.6 115 1101.6 215 1350.9 16 886.6 116 1104 216 1353.5 17 888.6 117 1106.3 217 1356.2 18 890.7 118 1108.7 218 1358.9 19 892.7 119 1111 219 1361.5 20 894.7 120 1113.3 220 1364.2 21 896.7 121 1115.7 221 1366.9 22 898.8 122 1118 222 1369.5 23 900.8 123 1120.4 223 1372.2 24 902.8 124 1122.8 224 1374.9 25 904.9 125 1125.1 225 1377.6 26 906.9 126 1127.5 226 1380.3 27 909 127 1129.9 227 1382.9 28 911 128 1132.2 228 1385.6 29 913.1 129 1134.6 229 1388.3 30 915.1 130 1137 230 1391 31 917.2 131 1139.4 231 1393.7 32 919.2 132 1141.7 232 1396.4 33 921.3 133 1144.1 233 1399.2 34 923.4 134 1146.5 234 1401.9 35 925.4 135 1148.9 235 1404.6 36 927.5 136 1151.3 236 1407.3 37 929.6 137 1153.7 237 1410 38 931.7 138 1156.1 238 1412.8 39 933.8 139 1158.5 239 1415.5 40 935.9 140 1160.9 240 1418.2 41 937.9 141 1163.4 241 1421 42 940 142 1165.8 242 1423.7 43 942.1 143 1168.2 243 1426.4 44 944.2 144 1170.6 244 1429.2 45 946.3 145 1173 245 1431.9 46 948.5 146 1175.5 246 1434.7 47 950.6 147 1177.9 247 1437.4 48 952.7 148 1180.3 248 1440.2 49 954.8 149 1182.8 249 1443         250 1445.7

Issue TS-57XX-85X and TS-67XX-85X 10K thermistor with 11 K shunt resistance table Environment Unknown Environment Cause Unknown Cause Resolution Temp (°C) Temp (°F) Ohms (11K shunt)   -40.0°     -40.0°   10,517   -39.0°     -38.2°   10,489   -38.0°     -36.4°   10,460   -37.0°     -34.6°   10,430   -36.0°     -32.8°   10,397   -35.0°     -31.0°   10,364   -34.0°     -29.2°   10,329   -33.0°     -27.4°   10,292   -32.0°     -25.6°   10,254   -31.0°     -23.8°   10,214   -30.0°     -22.0°   10,172   -29.0°     -20.2°   10,129   -28.0°     -18.4°   10,084   -27.0°     -16.6°   10,037   -26.0°     -14.8°   9,988   -25.0°     -13.0°   9,938   -24.0°     -11.2°   9,885   -23.0°     -9.4°   9,830   -22.0°     -7.6°   9,773   -21.0°     -5.8°   9,715   -20.0°     -4.0°   9,654   -19.0°     -2.2°   9,592   -18.0°     -0.4°   9,527   -17.0°     1.4°   9,460   -16.0°     3.2°   9,391   -15.0°     5.0°   9,320   -14.0°     6.8°   9,247   -13.0°     8.6°   9,171   -12.0°     10.4°   9,094   -11.0°     12.2°   9,015   -10.0°     14.0°   8,933   -9.0°     15.8°   8,850   -8.0°     17.6°   8,764   -7.0°     19.4°   8,677   -6.0°     21.2°   8,587   -5.0°     23.0°   8,495   -4.0°     24.8°   8,402   -3.0°     26.6°   8,307   -2.0°     28.4°   8,210   -1.0°     30.2°   8,111   0.0°     32.0°   8,012   1.0°     33.8°   7,910   2.0°     35.6°   7,807   3.0°     37.4°   7,702   4.0°     39.2°   7,595   5.0°     41.0°   7,489   6.0°     42.8°   7,380   7.0°     44.6°   7,270   8.0°     46.4°   7,160   9.0°     48.2°   7,048   10.0°     50.0°   6,937   11.0°     51.8°   6,825   12.0°     53.6°   6,711   13.0°     55.4°   6,597   14.0°     57.2°   6,483   15.0°     59.0°   6,369   16.0°     60.8°   6,255   17.0°     62.6°   6,141   18.0°     64.4°   6,027   19.0°     66.2°   5,912   20.0°     68.0°   5,798   21.0°     69.8°   5,686   22.0°     71.6°   5,572   23.0°     73.4°   5,460   24.0°     75.2°   5,348   25.0°     77.0°   5,238   26.0°     78.8°   5,127   27.0°     80.6°   5,018   28.0°     82.4°   4,909   29.0°     84.2°   4,802   30.0°     86.0°   4,696   31.0°     87.8°   4,591   32.0°     89.6°   4,487   33.0°     91.4°   4,385   34.0°     93.2°   4,284   35.0°     95.0°   4,184   36.0°     96.8°   4,086   37.0°     98.6°   3,989   38.0°     100.4°   3,894   39.0°     102.2°   3,800   40.0°     104.0°   3,707   41.0°     105.8°   3,617   42.0°     107.6°   3,528   43.0°     109.4°   3,441   44.0°     111.2°   3,355   45.0°     113.0°   3,271   46.0°     114.8°   3,189   47.0°     116.6°   3,107   48.0°     118.4°   3,028   49.0°     120.2°   2,951   50.0°     122.0°   2,875   51.0°     123.8°   2,801   52.0°     125.6°   2,729   53.0°     127.4°   2,658   54.0°     129.2°   2,588   55.0°     131.0°   2,521   56.0°     132.8°   2,455   57.0°     134.6°   2,390   58.0°     136.4°   2,327   59.0°     138.2°   2,266   60.0°     140.0°   2,206   61.0°     141.8°   2,148   62.0°     143.6°   2,091   63.0°     145.4°   2,036   64.0°     147.2°   1,982   65.0°     149.0°   1,929   66.0°     150.8°   1,878   67.0°     152.6°   1,827   68.0°     154.4°   1,779   69.0°     156.2°   1,732   70.0°     158.0°   1,685   71.0°     159.8°   1,640   72.0°     161.6°   1,597   73.0°     163.4°   1,554   74.0°     165.2°   1,513   75.0°     167.0°   1,472   76.0°     168.8°   1,433   77.0°     170.6°   1,395   78.0°     172.4°   1,359   79.0°     174.2°   1,322   80.0°     176.0°   1,287   81.0°     177.8°   1,253   82.0°     179.6°   1,220   83.0°     181.4°   1,188   84.0°     183.2°   1,157   85.0°     185.0°   1,126   86.0°     186.8°   1,097   87.0°     188.6°   1,068   88.0°     190.4°   1,040   89.0°     192.2°   1,013   90.0°     194.0°   987   91.0°     195.8°   961   92.0°     197.6°   936   93.0°     199.4°   912   94.0°     201.2°   888   95.0°     203.0°   865   96.0°     204.8°   843   97.0°     206.6°   821   98.0°     208.4°   800   99.0°     210.2°   780   100.0°     212.0°   760   101.0°     213.8°   741   102.0°     215.6°   722   103.0°     217.4°   704   104.0°     219.2°   686   105.0°     221.0°   669   106.0°     222.8°   652   107.0°     224.6°   636   108.0°     226.4°   620   109.0°     228.2°   605   110.0°     230.0°   590   111.0°     231.8°   576   112.0°     233.6°   561   113.0°     235.4°   548   114.0°     237.2°   534   115.0°     239.0°   521   116.0°     240.8°   509   117.0°     242.6°   496   118.0°     244.4°   484   119.0°     246.2°   473   120.0°     248.0°   462   121.0°     249.8°   451

Issue What is difference between valve rangeability and turndown ratio? Product Line Field Devices Environment Valves Cause Definition of the terms helps explain the flow outcomes. Resolution Rangeability - maximum controllable flow divided by minimum controllable flow Turndown ratio - normal maximum system flow divided by minimum controllable flow.   Rangeability is the inherent characteristic of the valve and turndown ratio is the installed characteristic.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Slow reading/writing of log values and events might be caused by a fragmented index in the SQL database. Product Line TAC Vista Environment Vista Server SQL log/event data SQL Server 2005, 2008 Microsoft SQL Server Management Studio Express Cause If the SQL database has become fragmented in its index, these scripts can be run in SQL query software (e.g. Microsoft SQL Server Management Studio Express). Downloaded this software for free at: http://www.microsoft.com/downloads/details.aspx?FamilyID=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en Resolution Warning: Always take backups of the system prior to performing maintenance on the database. Run the following SQL query: SELECT * FROM sys.dm_db_index_physical_stats (DB_ID(N'taclogdata'), OBJECT_ID(N'TrendLogValue'), NULL, NULL , 'DETAILED') WHERE index_level = 0 order by index_id Look at "avg_fragmentation_in_percent" Or DBCC SHOWCONTIG Look at Logical scan fragmentation If the database is fragmented, e.g more than 50% run this script to defrag the index: USE TACLOGDATA DBCC INDEXDEFRAG('taclogdata','TrendLogValue') Or USE TACLOGDATA DBCC DBREINDEX('TrendLogValue')

Issue Exporting/Importing Configuration Profiles and need to copy CCTV configuration from one machine to another. Product Line TAC INET Environment I/NET Seven Cause When Configuration Profiles are created on one PC and the user wants to copy it onto another PC, there is no easy way to do this even through the SQL database. To accomplish this the user would have to first, Export and then Import the configuration files from the registry. Likewise when setting up a second standalone machine to use the same CCTV interface or similar Host masking settings can take some time. This process will allow you to transfer everything configured under the profile setting to a new machine. Resolution The following step describes how to do this: Caution • Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on your computer. • To open Registry Editor, click Start, click Run, type regedit, and then click OK. • You can use a text editor like Notepad to work with the registry files you create by exporting. • You can save registry files in the Windows format, or as text files. Registry files are saved with .reg extensions, and text files are saved with .txt extensions. • In Windows Explorer, double-clicking a file with the .reg extension imports the file into the computer's registry. To import a registry hive just double click it from Windows Explorer. Open the Registry Editor On the File menu, click Export. In File name, enter a name for the registry file. Under Export range, do one of the following: To back up the entire registry, click All. To back up only a particular branch of the registry tree, click Selected branch and enter the name of the branch you want to export. Click Save. HOST MASK information To share host mask configurations between PCs, browse to C:\I/NET SEVEN DATA and copy the .dat files relevant to the configuration profile

Issue What is the contact information for Barber Colman Dyna group? What is the contact information for Barber Colman Aerospace division? What is the contact information for Barber Colman Industrial Instruments division? Environment Barber Colman Cause The old Barber Colman Dyna group is now a part of Woodward Governor. The old Barber Colman Aerospace division is now a part of the GE Aerospace. The old Barber Colman Industrial Instruments is now part of Eurotherm, an Invensys company. Resolution Barber Colman Dyna group is now Woodward Governor. They can be reached at 800-543-5811 Barber Colman Aerospace division is now GE Aerospace. They can be reached at 815-637-3500 Barber Colman Industrial Instruments is Eurotherm, an Invensys company. They can be reached at 815-637-3222 or 815-637-3404 for tech support.

Issue How can the Niagara G3 ENC platform be accessed if the user name and password have been forgotten? Environment Niagara G3 ENC Cause Forgot username and password for the Niagara G3 ENC. Resolution To connect via the serial port of the ENC you will need a UNCC-405, an Ethernet cable 7' or less, and Hyperterminal (or another terminal program). In the upper right corner of the ENC-520 is a block of four pins marked J4 Mode. Using one of the bias jumpers from the board, temporarily short the front two pins. Using the UNCC-405 and short Ethernet cable connect the laptop to serial port one of the ENC. Open HyperTerminal and configure a connection as 57600, 8, none, 1, no flow control. Reboot the ENC. When this appears: "Press ESC to restore factory default username and password...", go ahead and press the ESC key. Enter "y" when prompted to force the platform user name and password back to "tac" and "niagara". After using WorkBench to verify the user and password have been changed, remove the jumper and disconnect the serial connection.

Issue A Niagara R2 / BACnet integration station, running on a computer, can interfere with the WorkPlace Commissioning Tool. Environment WorkPlace Tech  Commissioning Tool (WPT CT), any revision I/A series R2 / BACnet integration station running on the same pc as the WPT CT Cause Communications port or driver conflict between WorkPlace Tech  Commissioning Tool  and the I/A series R2 / BACnet integration station. Resolution A Niagara R2 / BACnet integration station can interfere with the WorkPlace Commissioning Tool (WPCT), by disrupting communications between the WPCT and MNB controllers. One symptom of this interference is that while the WPCT can find some or all of the MNB controllers, their property sheets will not be fully populated with data. In such a case, the WPCT might be displaying data from a default template, rather than live data from the controller. As a best practice, check to be sure that the General tab of the device's Properties sheet is populated before going to any other tab. If the Firmware and Application fields of the General tab have not filled in, then the tool is not communicating with the controller, and the other tabs will contain default data, not current values from the controller. To insure that a Niagara R2 station is not running in the background on the computer follow these steps: Go to the Computer Management by right-clicking on My Computer Select Manage from the pull-down menu. Go to Services and Applications, then Services. Stop the Niagara service. Typically, the Niagara service will be configured to start automatically when the computer is rebooted.

Issue The Wonderware Temporary License is out of date. How can a new one be obtained? Environment WonderWare Cause Since Schneider Electric (Rockford) is no longer a Wonderware OEM software distributor, demo licenses can no longer be provided. Resolution The 30-day temporary Wonderware demo mode license is available to the Wonderware SI selling the Wonderware software.

Issue Can you cap the A port or B port of a mixing or diverting valve to change the valve to a two way (straight through) valve? Product Line Field Devices Environment VB-9313 series Cause Capping A port or B port of a mixing or diverting valve to change the valve to a two way (straight through) valve Resolution Schneider Electric does not recommend this modification for the VB-9313 series, because the valves are not equal percentage and therefore will not provide good control. The valve performs as a linear valve when both ports are utilized. These curves are not additive. Total flow is determined with both ports contributing. The valve will perform as a quick acting valve if the B port is plugged and a nominally linear valve if the A port is plugged. Additional problems that can occur are: Insufficient force to close off. Two way valves usually require high actuator forces to provide close off. Valves are not designed to be tight seating. Valves are rated ANSI III therefore flow leakage through the controlled coil can be expected. Flow direction through the valve can not be reversed. Flow must oppose the plug when closing. Flow aiding the plug may create hammer by causing the plug to overcome the actuator force and slam against the seat. When converted to a two way control valve for a variable flow system, 3-way valves tend to be extremely over-sized creating poor process control. After considering the pros and cons of making this type of modification, you may choose to proceed with this modification. The performance penalties should be less in chilled water applications and higher in hot water application.

Issue What is pneumatic actuator spring range shift and how can it be eliminated? Product Line Field Devices Environment Pneumatic Actuator Cause Spring range shift is an inherent feature of all spring return pneumatic actuators without positive positioners. The nominal published spring range of a pneumatic actuator without a positive positioner is the air pressure required to fully stroke the actuator WITH NO EXTERNAL LOAD. In the extend direction against an opposing load as provided by a damper or a valve, the supply air pressure must be increased above the spring range of the actuator to overcome the spring and the opposing force. In the retract direction against an opposing load as provided by a damper or a valve, the supply air pressure must be decreased below the spring range of the actuator so that the spring can overcome the air pressure and the opposing force. Under constant load conditions, the range of the actuator is offset by the amount of air pressure required to provide close-off of the damper or the valve. Resolution When is "Spring Range Shift" a concern? It is a concern when two or more pneumatic controlled devices should be sequenced from one pneumatic signal without an overlap. An example would be a normally open heating valve and a normally closed cooling valve being sequenced from a direct acting thermostat, In this example the spring range of the normally open valve will shift upward and the normally closed valve will shift downward which means the two valves may overlap. Another area of concern is that pneumatic control signal provides proper pressure span to operate the control device and provide "tight" close-off of damper or valve. Examples of limited pressure change would be: pneumatic controllers maximum output which is limited by main air pressure; the low pressure output capability of a pneumatic controller; and electronic to pressure transducer which can have a limited output such as 3 to 15 psig.   What can be done to overcome "Spring Range Shift" when sequencing devices? Sequencing can be accomplished in a pneumatic system by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment (2378-501) or controllers with separate outputs for each actuator. Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning. This is the ideal way to provide precision sequencing, since variable loading on the actuator will not effect the sequencing. Biased start ratio relays may be used to provide a method of sequencing by amplifying or shifting the pneumatic signal. For applications involving sequencing a pressure to electric (P.E.) switch with a pneumatic actuator, the P.E. can often be adjusted to operate outside the operating range of the actuator. Sometimes larger actuators will help the sequencing problem. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper and therefore reduces control signal change required to control the actuator. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, adjusting the start points can help prevent sequencing problems. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Sequencing problems can be eliminated by providing controllers with separate outputs for each actuator and do the sequencing in the controller. What can be done to increase the close-off of a damper or valve actuator due to limited or insufficient pneumatic control pressure to the control device? Proper control and close-off of the control device can be accomplished by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment ( 2378-501). Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning (0 to main air pressure to the actuator). Biased start ratio relay provide a method of amplifying or shifting the pneumatic signal. Selecting larger actuators will increase close-off pressure. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, proper adjustment of the start points will increase close-off. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Provide electronic to pneumatic transducers with sufficient input span to obtain maximum or sufficient pneumatic output.