Building Automation Knowledge Base

Issue ES connect to 3rd party BACnet devices in StruxureWare Building Operation Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with Enterprise Server. Connection to BACnet devices such as ACX. Cause Desire to use ES rather than AS Resolution As of StruxureWare Building Operation 1.1 the ACX with BACnet I/P xDriver with the ES, we can see the points, load them into the BACnet interface, and view them in tgml. The BACnet IP xDriver and User Guide is available on The Exchange Download Center. The following screen captures are from the ACX where a simple Infinity Numeric is setup called ACXdevice:   Next the xDriver for the ACX is loaded and setup as Server with the following settings: (Note the IP Address references the IP of the ACX controller)   Next a simple Numeric is setup called BacTest1 with the following settings: (Note the IP Address is left blank)   Next another Numeric is created called CocaCola1 with the following settings:   Next from the Enterprise Server, a 'Find New BACnet devices' is done to find the ACX and the two Numerics created:  

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network with integration of the FOI or Fiber Optic Interface  Cause How the Fiber Optic Interface (FOI) fits into an I/NET site. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN and the integration of Fiber Optic or FOI. The FOI Spec sheet is available here, as well as TCON087. Click the image below to download as a PDF document.  

Issue Upgrading a Xenta 102-AX to v 2.16 Product Line TAC Vista Environment Xenta 102-AX LonMaker NL220 Cause Firmware upgrade Resolution The following instructions will describe the firmware upgrade process for three different LNS environments: LonMaker 3.1, LonMaker Turbo 3.2, and NL220. The NXE, APB, and XIF files for upgrading the 102-AX are now available on The Exchange Download Center. Preparation   Always remember to make backups before beginning this process. Record the Neuron IDs for all Xenta 102-AXs that will be receiving the upgrade. If you do not record the Neuron IDs ahead of time, you will have to press the service pin on every controller being upgraded. A list of all Neuron IDs can be obtained in one of the following ways: Through TAC Vista Server Open TAC Vista Server Click on Reports > LonWorks Networks, Survey   This process will open a .txt document which lists all controller names and Neuron IDs in the Vista database. Through Echelon LNS Utilities Navigate to Start > Programs > Echelon LNS Utilities > LNS Report Generator Select the LNS Network   Hit Generate   This will generate a .csv file in the designated location with controller names and Neuron IDs. This can be viewed using Microsoft Excel. Through NL220 Choose either Subsystem or Channel view Depending on the view, right click either on the Subsystem or the Channel Select Print > Print list of nodes Select Export   Choose desired file format Hit OK If changes have been made to the configurations of the 102-AXs through any means other than the LNS plug-in (I/STAT, M/STAT, Vista Workstation) these parameters will first need to be uploaded to the LNS database. If this step is skipped, then any configurations made this way will be erased during the upgrade. In LonMaker 3.1 Right click on a device Select Resynch CPs... Repeat for each 102-AX In LonMaker Turbo 3.2 Right click on a device Select Commissioning > Resynch CPs... Repeat for each 102-AX In NL220 Right click on a device Select Copy configuration values in memory Repeat for each 102-AX Download the NXE and XIF files for version 2.16 from The Exchange Download Center. Please note that during the upgrade process, the 102-AX will not function properly. In a multiple LIP or router database the dummy database can be created on a notebook PC. This allows for a local FT10 connection to the Lon network after the router. The existing network topology is not needed on the dummy database in this case.   Performing the Upgrade in LonMaker 3.1 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device *Note: The network has to represent the topology of the physical connection to the FT-10 channel Check Commission Device box, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Specify channel. Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the box for Load Application Image. Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property Values to Current values in device. This is an important step. If you do not set to current values in device, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in LonMaker Turbo 3.2 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device Check Commission Device box, specify channel, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the boxes for "Load application image" and "Update firmware in device to match application image." Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property (CP) Values to "Application image file." Set the Device Specific CPs to "Preserve device values." This is an important step. If you do not preserve device values, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Commissioning > Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in NL220 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch NL220 Log in and create a New project. Do not register any plug-ins. In SmartChannel, set the new network to be Attached. Under the Device Templates tab, right-click and select New Device Template. Create the New Device Template from interface file. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit OK.   On the Channel tab, right-click and select New node on Name the device and choose Create node from a device template. Select the newly created 2.16 device template. Uncheck Set all configurations to manufacturer's default.   Right-click on the new device and select Install (network > commission in newer versions). Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you are going to service pin the controller, do it now.   Right-click the device and select Download program. Choose Upgrade system version. You will receive a warning stating that upgrading the system image can leave the device in a bad state and break communication. You should only use this option if you are sure of what you are doing. Confirm, Yes, you want to continue. Configuration download should be set to Keep current configuration on node.     Allow approximately 50 seconds for the application image to finish loading. To upgrade the next 102-AX, right click on the device and select Network > Replace. Repeat these steps for each 102-AX in the system.

Issue Plug-in 'TACOSSysPin.Document' launch failure. Unspecified error Product Line TAC Vista Environment LonMaker 3.X TAC Vista System Plug-in Cause An unspecified error in the launching of the TAC Vista System Plug-in is either caused by a faulty installation or registration of the plug-in.   Resolution Check under Start > Settings > Control Panel > Add or Remove Programs. Look for TAC ToolPack 5.X.X. Make sure the version number 5.X.X matches the current Vista installation. If it does not, uninstall the current version of the ToolPack and install the correct version. If it is the correct version, proceed. Check the plug-in registration. In LonMaker go to LonMaker > Network Properties > Plug-in Registration. Look for TAC Vista System Plug-In (Version 5.X.X) Make sure the version number 5.X.X matches the current Vista installation. If it does not, unregister the current version of the Plug-in and register the correct version. If everything appears to be installed and registered correctly, but the error persists, uninstall and reinstall the correct ToolPack. Reboot the PC, reregister the plug-in, and try to launch it again.

Issue Are the Network 8000, DMS, and Signal manuals available in an electronic format? Environment Network 8000 DMS Signal Cause Option to view Network 8000, DMS, and Signal manuals in electronic format. Resolution The Network 8000, DMS, and Signal manuals are available from the Publication Zone via iPortal. They are, also, available on a CD. The "Legacy zip" link downloads and extract the files, if running the program from a computer or creating the CD. When running the program from a computer, launch "index.html" located in the extracted bin folder. Email legacy product documentation requests to be added to the Legacy CD, to Product Support.

Issue   Plug-in 'TACXenta102AXPlugin.LNSPlugInAPI' launch failure. Can't show non-modal form when modal form is displayed Product Line TAC Vista Environment LonMaker 3.X TAC Xenta 102-AX Plug-In Cause This error appears when launching the TAC Xenta 102-AX Plug-in if there is another instance of the plug-in already running. The first instance of the plug-in was never fully launched (it is still stuck in modal form). This can happen by not acknowledging the Configuration Parameters Synchronization window, sending it to the back, getting tired of waiting for the plug-in to launch, and killing the application. Resolution Minimize every window on the screen. Find the errant Configuration Parameters Synchronization window as seen below:   Select Skip If the application was terminated through Task Manager, acknowledge the failure to connect. If the application is still waiting, the plug-in for the original VAV will launch. If you do not wish to view this plug-in, close it once it opens. Try to launch the plug-in again on the desired VAV. It should now launch.

Issue What is the recommended method to upgrade a Niagara R2 station to a newer version? Product Line TAC IA Series Environment I/A Series Niagara R2 Cause Unsure how to upgrade station databases. Resolution The published upgrade procedure is provided in F-27334. Below is a modified method that also works. Doing station upgrades on the server first is preferred. If there are any errors, they can be addressed without operational interruptions. Using the existing version of WorkPlace Pro (WPP), backup ALL of the UNC and Server databases into XML format. Methods of backing up and converting databases. Open the Enterprise server in WorkPlace Pro. Double click the station name. Select "Commands" and "Backup XML to save the server in XML. Then select "Backup Subordinate XML" to pull all of the UNC databases as XML into the server stations folder.   If not on site but the UNC and Server databases are available, use the DB Admin tab of the Admin tool to convert the databases locally to XML. Now install the newer Niagara revision onto the Server. Copy the stations containing the XML files to the desired WPP revision station folder. Enable and open the new revision of WPP. Use the Admin Tool to convert locally all of the stations from XML to DB. (If there are any errors, they can be addressed without affecting the running installation.) After all the databases have successfully converted to DB, convert them to SNS. (This saves time later if the UNCs need reloading) Use the Enterprise Server to upgrade the UNC. During the upgrade process of the UNC it will ask to backup the database. If the database had upgraded with no issue in the previous step, enter the username and password to proceed with this backup. This will backup the station, upgrade the UNC, and then upgrade and reinstall the station. The previous station upgrade will be needed only if there is an issue. If after following this procedure the station still fails to start, contact Product Support Services.

Issue Alarms being generated on the Sigma system are not displayed in the Sigma local, or remote client Alarm Manager window. Product Line Satchwell Sigma Environment Sigma 4.04 or later Cause The Sigma local, or remote clients have not been correctly configured in the Sigma server. Resolution Confirm that the Sigma client has been selected to receive alarms. Open the Sigma System Setup and from the tree structure select "Clients". Identify and select the required client , confirm that the correct Sigma server is selected from the list of servers shown.   Select Controllers from the tree structure, then choose "Routesets". For each routeset make sure that the client has been selected.   If changes have been made to the routesets, download them to all of the Sigma controllers.

Issue TAC TRV-S series Butterfly Valve Body requires replacement. Product Line Field Devices Environment TAC TRV-S series Butterfly Valve Body installations. Cause Obsolescence of TAC TRV-S series Butterfly Valve Body. Resolution Replace TAC TRV-S series Butterfly Valve Body with S-E VF208W series Butterfly Valve Body. Replace TAC MB15 / MB30 Actuator with S-E MF20 / MF40 series Actuator as appropriate. It should be noted that where a TAC TRV-S series Butterfly Valve Body is to be replaced by a S-E VF208W series Butterfly Valve Body the TAC Actuator fitted to the TAC TRV-S Butterfly Valve Body will not be suitable for reuse on the S-E VF208W.Buttterfly Valve Body. TAC TRV-S series Butterfly Valves utilise TAC MB15 / MB30 series Actuators. TAC MB15 / MB30 Actuators are not suitable for use on S-E VF208W series Butterfly Valve Bodies. S-E VF208W series Butterfly Valve Bodies utilise S-E MF20 / MF40 series Actuators. S-E MF20 / MF40 series Actuators are suitable for use on TAC TRV-S series Butterfly Valve Bodies, but then no linkage kit should be mounted. MF20 datasheet MF40 datasheet  

Issue Obsolescence of TAC VG211, VG222, and VG321 series Valve Bodies. Product Line Field Devices Environment TAC VG211, VG222, and VG321 series Valve Body installations. Cause Obsolescence of TAC VG211, VG222, and VG321 series Valve Bodies. Resolution Replace TAC VG211 series Valve Body with S-E.VGS211F 15 – 100CS series Valve Body. It should be noted that a number of anomalies appear in the current issue of the Data Sheet describing the VGS211F 15 - 100CS range of 2-port Valve Bodies. The VGS211F 15-100CS Data Sheet includes two tables of information. A discrepancy appears in respect of the Kv value stated for the 50mm size Valve Body. The table of information on Page 1 of the Data Sheet displays a Kv value of 38 The table of information on Page 2 of the Data Sheet displays a Kv value of 40 The correct Kv value is 40 The type designation stated in the Data Sheet for this Valve Body is also incorrect. The type designation for this Valve Body should read VGS211F-50CS 40M SD00 Arrangements are currently in hand to correct these anomalies. NB The table on Page 1 of the earlier VG211 Data Sheet displayed a Kv value of 38 This value was also incorrect. The Kv value should have read 40 The VG222, VG222 and VG321 are no longer available, as it is replaced with the following: VG222 Valves will have the family name VG221F VG321 Valves will have the family name VG311F Please find the Product Announcement PA-00085 with the information.

Issue The Momentary Start / Stop (SS) object in a MNB controller is not working. The OutStrt output property remains ON and does not pulse off. Product Line TAC IA Series Environment MNB controllers Cause Application programming Resolution The OnPulse input property is set higher than the required minimum of 2 seconds.  In order for the logical outputs to work (OutStrt & OutStp), physical hardware tags must be assigned to the physical outputs (AddrStrt & AddrStp).  This is required when using the Momentary SS object in any MNB controller. The following logic can be used in place of the Momentary SS object to generate an equivalent OnPulse.  

Issue Not getting any alarms from Xenta 30x/40x/28x on the network. Have to perform alarm refresh to get alarms Product Line TAC Vista Environment TAC Vista XBuilder Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 400, 401, 401:B Cause Xenta will only send alarms if it gets a heart beat from TAC Vista. If it for some reason does not get it or get it from the wrong server no alarms will get in to the alarm list. Xenta Servers can also send out the heartbeat on the network if a "stand alone" Xenta server is doing this the alarms will be sent to it instead. Resolution Open properties of the Lonworks Network object and click on the  "Communication Timers" tab. Make sure that “Heartbeat Active” is checked. If there are any Xenta 5xx/7xx on the network open the XBuilder for it and make sure that the option Alarm Server is set to disabled.   Download the XBuilder project again

Issue The MNB-Vx appears in the Workplace Commissioning Tool in a read-only mode. After downloading a MNB-Vx controller, an error window appears stating "The download was completed but the application was invalid. The device is now running the factory default application". Product Line TAC IA Series Environment MNB-Vx Workplace Commissioning Tool Cause This condition is related to improper AC power provided to the MNB controller. Typically, when AC power drops below 20 Vac, the controller will fall back to a factory-installed application and switch to read-only mode in the Workplace Commissioning Tool. Resolution Fix the AC power supply so that it is within specifications for the MNB controller. Do a hardware reset using the dip switches to get it out of read only mode. Try the download again.

Issue Bind to more than 13 unique LON devices without running out of address table entries Product Line TAC Vista Environment LonMaker NL220 LNS Cause Using a broadcast SNVT binding type will save on address table slots by only consuming one slot per receiving subnet instead of one per receiving controller.  This will increase network bandwidth, but allows one-to-one bindings to many controllers in the same subnet.  Xenta programmable SNVT output limits would be the only limiting factor. Resolution Open the Network Variable Connection tool by right clicking on a function block in LonMaker and selecting Connect. Set the Connection Attribute to Repeated to use this as a starting point. Hit the Properties button.    On the Connection Details window, select New. Give the New Connection Description a name. "Broadcast" is a good description.    Hit the Advanced button for this connection type.    Set the Use Broadcast setting to Yes.   Try binding some outputs with this new connection type and it will reduce the number of address table slots consumed.

Issue Troubleshooting sending email alarms from a Xenta Server. Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 XBuilder SMTP Server Cause There are many reasons why an emailed alarm from a Xenta 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 Some Xenta Servers can be configured to send out alarms via email – 511, 511:B, 527, 701, 711, 721 and 731. Typically, following the instructions found in the TAC Vista Xenta Server – Web Server 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 Xenta alarms to email out is to properly configure the XBuilder project. Reference Chapter 5.2 Configuring the TAC Xenta Server for Email Forwarding in the TAC Vista Xenta Server – Web Server 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. Alternately, for testing and demo purposes, Schneider Electric's SMTP server can be used – smtpservice.buildings.schneider-electric.com (port 25 or port 2525). If using Schneider Electric's SMTP server, set the Authentication to "TAC." Once the Xenta Server is correctly configured, set up Alarm Receivers in the XBuilder project. The steps for this can be found in Chapter 4.3 Configuring Receiver Groups in the TAC Vista Xenta Server – Web Server 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 XBuilder projects or Xenta Servers. If everything is set up correctly, test the email capability by logging into the web interface of the Xenta Server and navigating to Utilities > Tools > Communication Tests. Enter a test email destination and hit "Test" as shown in Figure 1.  Figure 1. Test Send E-mail Message If the email arrives as expected, then the SMTP settings are all correct. A final test of the alarm receivers and alarm properties can be accomplished by forcing an alarm condition. If the email does not arrive as expected, check the following possible errors, or proceed directly to the next section of this document titled "Check SMTP Connectivity." Could not send the e-mail, error in mail configuration If this error results from sending a test email, then the settings in XBuilder need to be revisited and verified. Failed deliver e-mail, connection couldn't be established, check e-mail address If the test results in this error, proceed to the next section of this document titled "Check SMTP Server Connectivity." 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." Xenta Servers have a built in test function for determining the status of some of the defined devices. Log into the web interface and navigate to Utilities > Tools > Communication Tests.  Figure 2. Communication Tests From this screen, the connection between the Xenta Server and any of the defined gateways and servers can be verified. Select the radio button for Mail server 1 (SMTP) and hit test. Some possible results of the test are: ‘Mail server 1 (SMTP)’ is on-line If the mail server is online, but the test email still is not delivered, then the cause is most likely the authentication credentials of the Xenta Server. Check with an IT professional to verify the login account name and password that have been provided. Check that it has been correctly entered as described in the section of this document titled "Check SMTP Server Settings." If all of this is set up correctly and verified, proceed to the section of the document titled "Xenta Server Indicates No Errors." ‘Mail server 1 (SMTP)’ is off-line If the mail server is offline, then no communication exists. Make sure the SMTP server settings are correct. Refer to the section of this document titled "Check SMTP Server Settings." Also check the TCP/IP settings as described in the section of this document titled "Check TCP/IP Settings." If the SMTP server is outside the network, ensure that the default gateway is defined and test its availability with a communication test as shown in Figure 2. Lastly, connect to the network using a laptop and attempt to ping the SMTP server. If it is unavailable, contact an IT professional for assistance. 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 3. Failed Ping Example 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 4. Successful Ping Example In Figure 4, 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 5. 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 6. 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 7. 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 Xenta 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 "Xenta Server 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 8. Enable Telnet Client. Failed convert dns-name into ip-number If using DNS names for the SMTP server instead of IP addresses, a DNS server must be defined. A DNS server is responsible for resolving DNS names to IP addresses. Make sure the DNS server is online with a communication test as shown in Figure 2. To bypass any problems with DNS, enter the SMTP server IP address instead. This can be obtained by pinging the server as shown in Figure 3. Check SMTP Server Settings The SMTP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > SMTP.  Figure 9. SMTP Settings The fields shown in Figure 9 for "Outgoing mail server port" are not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and below, it is not possible to alter the default SMTP port. It is hard-coded at 25. The Primary SMTP will be provided by the site's IT staff. If authentication is required, then an account name and password must be provided by the IT staff. If the SMTP server is available, but no emails are being sent out, the authentication parameters need to be checked. Any further investigation at that point will require contacting an IT professional for assistance. Refer to the section of this document titled "Xenta Server Indicates No Errors" for some troubleshooting questions to pose. Also refer to "Contacting an IT Professional" for documents to use to facilitate these conversations. If no SMTP server has been provided, then Schneider Electric's SMTP server can be used. To use Schneider Electric's SMTP server for testing or temporary purposes, enter "smtpservice.buildings.schneider-electric.com" into the outgoing mail server. Mail server ports 25 and 2525 are available. Authentication is set to "TAC." This does not require an account name or password. This method is only recommended for testing purposes. Schneider Electric makes no guarantees as to the availability of the SMTP server. To ensure the email alarms are being delivered as promised, use an SMTP server with some guarantee of up time. Even if an SMTP server has been provided, consider defining Schneider Electric's SMTP server as a secondary server. It is not always a viable solution due to some network security settings and availability, but may increase the overall success rate of your email delivery by providing some redundancy. Check TCP/IP Settings The TCP/IP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > TCP/IP.  Figure 10. TCP/IP Settings The most important items to check on this screen are Default gateway and DNS server. If the default gateway is not properly defined, then external SMTP servers will be unavailable. If the DNS server is not properly defined, then SMTP servers defined by DNS names will be unresolved. Either enter a valid DNS server, or manually resolve the IP address by pinging the server as shown in Figure 3. If using Schneider Electric's SMTP server, DNS must be defined. Xenta Server Indicates No Errors If the test email was sent, but not received, and no errors were recorded, 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 the Xenta Server 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 Xenta 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 in XBuilder/System Program versions 5.1.3 and later. See the section of this document titled "Changing the default SMTP Port" for instructions. Xenta Servers are hard-coded to use UTF-7 encoding. They require this encoding to support Swedish characters. UTF-8 is the most common encoding in America and Europe. Some networks may filter UTF-7 messages as spam. While this is not readily configurable, it can be manually changed by editing some files. Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device and then cycle the power. The device will now use UTF-8 character encoding which is more commonly used in the United States. Remember that reloading the system program will erase these changes. 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 Changing the default SMTP port is not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and before, the only options are to request for the IT department to allow use of port 25, or upgrade to version 5.1.3 or later. If you are using XBuilder/System Program version 5.1.3 or later, adjusting the default SMTP Port can be done through the web interface as shown in Figure 9. It can also be adjusted in XBuilder as shown in Figure 6.  Figure 11. Changing the SMTP Port in XBuilder 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 Xenta Servers. If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC 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 Xenta Servers use 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 required (choose one): Yes No Account name (if applicable):   Password (if applicable):   To distribution list (if any):   Required UDP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses):   Unit e-mail address:   From IP address:   Desired UDP port:   Appendix B: Sample IT Request for Information The TAC 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 Xenta Servers use 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 required (choose one): Yes No Account name (if applicable): emailuser Password (if applicable): password123 To distribution list (if any): facilities_staff@thebuilding.com Required UDP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses): facilities_staff@thebuilding.com Unit e-mail address: xenta@server.com From IP address: 10.10.10.20 Desired UDP port: 25

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 When creating a localized SEBA naming convention EBO displays local characters as a question mark (?) Product Line EcoStruxure Building Operation Environment Building Operation WorkStation version 3.2 (and later)  Cause The CSV file used is in ANSI format and EBO requires UTF-8 format Resolution Ensure the file is saved in "CSV UTF-8" format rather than generic "CSV".      

Issue Seven Reports Error "CRPaige library CRPaig80.DLL cannot be found". Product Line TAC INET Environment I/NET site with Windows OS Cause Missing CRPaig80.DLL error message Resolution CRPaig80.DLL can be found on the original I/NET Seven installation CD (cd-drive:\program files\inet seven). Copy CRPaig80.DLL to the root I/NET Seven folder (c:\program files\inet seven). Click Here to download a zipped copy of the CRPaig80.DLL

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 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.