Building Automation Knowledge Base

Issue Identify between the various dongles used by Vista 2k, Vista 4 and Vista 5 License systems. Product Line TAC Vista Environment Vista 3.3x (Vista 2000) Vista 4.x.x Vista 5.x.x Cause Licensing and dongle technology used by Schneider Electric Vista has changed as new revisions were released. The manufacturer of Vista dongles is Aladdin which causes the designs and colors to lead to confusion over which dongle works with which version of Vista. Resolution Visual inspection and some software tools can be used to differentiate between the various Vista dongles. The Dongle Reset Utility for Vista 4 can be used to determine whether the dongle is for End User or In House use. The getTACHLInfo.exe program which is installed with Vista 5 and the License Server can be used to determine whether a Vista 5 dongle is End User or In House. Vista 4 End User Dongle A Vista 4 End User dongle is only functional when an associated license file (PLF) is installed on a computer that was generated for the PSU ID of the dongle. This dongle can either be USB or LPT in size. If the dongle is LPT it is typically white in color. If the dongle is USB the color is typically blue. When viewing the dongle through the Dongle Reset Utility it will report the type of dongle as Enduser PSU and show the PSU ID. Vista 4 In House Dongle A Vista 4 In House dongle, commonly referred to as an Engineering Dongle, activates the Engineering license files which grants a branch or partner access to the majority of Vista licenses. This type of dongle is not intended for use on customer sites outside of commissioning and maintenance work. Custom licenses can be generated for In House dongles, but it is not common. This dongle can either be USB or LPT in size. If the dongle is LPT it is typically white in color. If the dongle is USB the color is typically blue. When viewing the dongle through the Dongle Reset Utility it will report the type of dongle as TAC Vista IV Inhouse PSU and show the PSU ID. Vista 5 End User Dongle part number 000857510 A Vista 5 End User dongle is only functional when an associated license file (LIC) is installed on a License Server that was generated for the Host ID of the dongle. Vista 5 End User dongles only come as USB dongles and are typically purple in color. When using the getTACHLInfo.exe command the dongle will indicate that it is Enduser and provide the dongle ID. Instructions can be found in Find a Vista 5 dongle ID. Vista 5 In House Dongle - Part Number - 000885000 A Vista 5 In House dongle, commonly referred to as Engineering or Maintenance dongle, grants a branch or partner access to the majority of Vista licenses. This type of dongle is not intended for use on customer sites outside of commissioning and maintenance work. Custom licenses can be generated for In House dongles, but it is not common. Vista 5 In House dongles only come as USB dongles and are typically black in color. When using the getTACHLInfo.exe command the dongle will indicate that it is Engineer and provide the dongle ID. Side by Side Comparison Dongles side by side for size comparison:

Issue Unable to send alarm generated emails via the Yahoo’s SMTP server in I/A Series G3. The following error messages are displayed in the console output window when attempting to send a mail via Yahoo’s SMTP server. javax.mail.MessagingException: Could not connect to SMTP host: smtp.mail.yahoo.com, port: 465; Caused by: java.net.ConnectException: Connection refused: connect Product Line TAC I/A Series Environment Niagara G3 ENS ENC-520 ENC-410 Cause An incorrect STMP hostname was used in the “Hostname” of the OutgoingAccount. The correct Yahoo outgoing mail address, “smtp.mail.yahoo.com”, must be entered for in the OutgoingAccount “Hostname”. Resolution Procedure and properties settings required when using the Yahoo SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.mail.yahoo.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@yahoo.com (works without the “@yahoo.com” as well) Password: Your Yahoo account password Enabled: true Use SSL: true (Yahoo requires SSL) Transport: Smtp Use Authentication: true (Yahoo requires authentication when sending out emails) Reply to: example@yahoo.com (“The Reply To” must contain a valid Yahoo account) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue Check Windows Add/Remove programs and see if MSXML 6 SP2 is installed.  Installation of MSXML 6 Service Pack 2 (KB954459) failed because a higher version already exists on the machine. To proceed, uninstall the higher version and then run MSXML 6 Service Pack 2 (KB954459) Setup again. Product Line Andover Continuum Environment XP SP3 SQL Express 2005 XML Cause When SQL Server Setup tries to install MSXML 6.0 SP2, it detects that the version of MSXML 6.0 that is described in Knowledge Base article 954459 is already installed on the computer. Therefore, the validation process indicates that the current version of MSXML 6.0 should not be replaced. This stops the installation of both MSXML 6.0 and SQL Server 2005. Resolution See Microsoft's Support KB article for more information. MS offers a work around to this issue in their KB article as follows: Download MSMXL fix from the following Microsoft website: http://download.microsoft.com/download/E/3/F/E3F51FFB-505D-480E-9F67-0DD3A9680DEE/MSXMLFix.EXE Extract the fix, and then copy the MSXML6.MSP file and the MSXML_FIX.VBS file to the same folder. Run cscript MSXML_FIX.VBS. Once the fix is run, try installing SQL Express again. For alternative solutions see Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) and Error when installing SQL 2005 Express on a machine that had previously had MSDE installed

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 The new program interface does not match the previously defined program interface. (Subsystem: NS, #59) Product Line TAC Vista Environment LonMaker 3.1 LNS Version <3.2 Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 104-A Square D Altivar 61 Xenta 102-AX Cause The steps defined in this article only relate to the NS #59 error when it is received on an attempt to commission a controller in an LNS environment. It does not cover when this error is shown as a result of a download attempt in the TAC Vista System Plug-in. For information on the download error, see NS Errors #59, #64, #51 in a row on download attempt through System Plug-In. The new program interface does not match the previously defined program interface; i.e., the number of network variables, message tags, or the structure of self identification data is inconsistent even though the Program IDs match. This generally happens when a newer firmware of a controller is introduced that uses the same SNVT inputs and outputs as the old controller, and therefore shares a device template even though something below the surface may be different. Resolution The appropriate resolution to the NS, #59 error depends on the LNS version and type of controller that is failing to commission. Select from the categories below which best describes the situation. LNS Version <3.2 Check the existing Version of LNS. Open the Echelon® LonMaker™ Design Manager Right-click on the title bar of the Design Manager and select "About Echelon LonMaker..." In the About Echelon® LonMaker™ Design Manager Professional Edition window, look under Additional Information.   If the LNS Version is below 3.2, then upgrading the LNS to 3.2 or later (also referred to as LNS Turbo, not to be confused with LonMaker Turbo) may fix the error. The later LNS versions are less sensitive to program interfaces not matching. Navigate to Echelon Downloads. You will need an Echelon ID and password. It is free to create a New User Account if you do not already have one. In the drop-down menu, select Search for software in the Network Tools category. Before you install LonMaker Integration Tool 3.1 Service Pack 3 Update 3, you must have already installed LonMaker Integration Tool 3.2 Service Pack 3 Update 1. Download both Update 1 and Update 3, or just Update 3 depending on the situation. Note: If you upgrade to LNS Turbo, you will no longer be able to restore databases from a non-Turbo LNS PC. There is backwards compatibility with old databases, but no "forward" compatibility for older PCs to open newer networks. If you cannot install the LNS update, proceed to the following solutions organized by controller type. Xenta Programmables (follow steps below) Xenta 28X, 30X, 401(:B) You get this error when two controllers share a device template (XIF file) if one has a system program version (.MOT) below 3.5 and the other has a system program version above 3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and its own template. Open the application from the System Plug-in by right clicking on the controller and selecting Configure>Edit. To give the application a new XIF, either add a dummy SNVT or go to Device Configuration and uncheck the box for "XIF header generated according to LonMark standard." Go to Options>Simulate (F12), select Commands>Generate. Options>Edit (F12) and save the application to the hard drive by selecting File>Save as. In the System Plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and Vista Database. If you are asked to resynchronize, do so. Download Applications and Parameters. Commission in LonMaker. Another cause of the error for a Xenta programmable is if the system program version (.MOT) is newer than the version of Vista System Plug-In being used. For example, if visiting a 4.2.5 Vista site and attempting to add a much newer 3.8 firmware Xenta programmable. It will fail on attempts to commission. The firmware must be downgraded to a version that is compatible with the older Vista system. See Download an .MOT file into a Xenta Programmable controller for information on loading a different .MOT file. Xenta 104-A (follow steps below) If there are TAC Xenta 104-A v1.10 (or older) commissioned in an LNS database, it is not possible to add a TAC Xenta 104-A v1.20 or newer in the same database. Nor is it possible to do a replace. This is due to a change of size of the SNVT declaration area residing in the device memory. For the same Program ID, LNS requires this size to be identical as previously commissioned devices. Download NXE v1.20A from The Exchange Download Center. This is an NXE file which should be used to upgrade v1.20 to be able to coexist with v1.10. (It is not possible to upgrade 1.10 to 1.20/1.2A, due to memory configuration.) The download of v1.2A to the device is selected in the “New device wizard” in LonMaker. Check the “Load application image” and browse in the NXE as the image file. Note : The same process must be performed while dealing with the 104-A v1.21. In addition to the same issues above, v1.20A will not be compatible with v1.21. For more information on the Xenta 104-A firmware versions see Xenta 104-A firmware version compatibility. Square D Altivar 61 (choose an option below) Square D Altivar 61 drives have undergone a similar update of the firmware. Newer LON drives cannot reside concurrently on a network with older drives. A new NXE must be loaded into the newer drives so they can coexist with the older drives. This NXE file is on the Product Support SharePoint, or can be obtained by contacting Square D drive support directly at drive.products.support@schneider-electric.com. Xenta 102-AX Two Xenta 102-AXs, one that is hardware version 1, and one that is hardware version 2, cannot co-exist on the same LNS network. Whichever one is commissioned first will work fine, the second will result in an NS, #59 error.

Issue When using the Modbus RTU and Modbus IP XDrivers it is important to determine which controller and port can support the electrical standards used by the 3rd party device. Product Line Andover Continuum Environment Continuum Netcontroller II and bCX1 controllers that have been XDriver enabled. XDriver, Modbus RTU, IP, Infilink, Infilink200, B-Link. RS-232, RS-485 JBUS Cause Controller ports and 3rd party devices come in various electrical standards (RS-232, RS-485, RS-422), which ports support the various standards? Resolution There are two Continuum Modbus XDrivers: Modbus RTU: This allows the connection of 3rd party Modbus RTU slaves via the serial data RS-232, RS-485 or RS-422 electrical standards. RS-232 is a point to point connection to 1 device, RS-485 & RS-422 support a bus topology for connection of multiple 3rd party devices. The Continuum controller will be the Modbus RTU Master and will poll the 3rd party device that must be a slave. The bCX1-CR controllers have 2 ports that can be configured for Modbus: Comm1 RS-232 Comm2 RS-232 or RS-485 port The Netcontroller II controllers support: Comm1 - RS-232 or RS-485 Comm2 - RS-485 Comm3 - RS-232 Comm4 - RS-422 The ACX57xx controllers support: Comm1 - RS-485 Notes An Infilink200 or B-Link may be used to convert RS-232 to RS-485 if required. The J Bus protocol is a subset of the Modbus protocol and so the Modbus XDriver is used for J Bus Systems. Modbus IP: The bCX1, ACX57xx and the Netcontroller II all support the Modbus IP protocol that connect via the Ethernet IP connection. This XDriver can be configured to support either Client or Server modes. Although the communication is physically via the Ethernet port, one of the Serial ports is required to be X Driver enabled to load the software, this serial port is then no longer available for other purposes. This XDriver requires Ethernet X Driver support to be enabled on the port. NOTE Netcontroller II and bCX1 can have an XDriver ENABLED on more than a one Comms port, however only one IP XDriver should be INSTALLED on each controller, also only one Modbus RTU XDriver should be INSTALLED on each controller. It is possible to INSTALL a Modbus RTU and a Modbus TCP/IP XDriver on a single controller, but it would be very easy to overload the controller, so this setup is only suitable for smaller networks. (note the difference between enabling XDriver support and Installing an XDriver) See Articles Can multiple Modbus TCP/IP XDrivers be installed on a single 2nd Generation NetController? and BCX Controller can use Comm 1, Comm2, or both ports for Modbus RTU X-Driver  

Issue Can I remove the permanent override feature or limit the maximum override duration from the station or an individual point in I/A Series G3? Environment I/A Series G3 Cause Can I remove the permanent override feature or limit the maximum override duration from the station or an individual point in I/A Series G3? Resolution Starting in version 3.4.51, the permanent override can be removed globally from the station by adding a facet to the SysInfo facets property on the root of the station. Add a new BRelTime value to the SysInfo facets and assign it the name "maxOverrideDuration." This enables a station global limit on the duration for any control point. The value of this BRelTime should be the MAX duration allowed. A value of zero means that 'Permanent' is allowed. A non-zero value limits the custom to a maximum time value.  Note that 'Permanent' is the default if no "maxOverrideDuration" facet is found. Starting in version 3.5.25, the feature was enhanced to allow specifying the max duration on an individual control point basis. Follow the same procedure as defined above but add a new BRelTime value to the individual point's facet. Example: Right click on the station's Config container and select View - Property Sheet. Click on the Sys Info >> to open the Config Facets dialog box. Select + to add a facet. Click inside the Key area and enter the new key name maxOverrideDuration. Click on the Type drop down and select RelTime. Click on the Value ... and enter the desired time. Select OK

Issue What are the sourcing and sinking specifications of the analog voltage outputs on the different controllers? Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 XP IO modules Cause Sourcing and sinking refer to the ability of a DC circuit to PUSH or PULL a direct current through the circuit. Resolution Voltage Sourcing In a controller's voltage sourcing output, the output provides a voltage source that PUSHES a direct current through the load as indicated in the illustration below. The current flows from the output's positive (V/+) terminal through the load to the output's negative terminal (-/ RTN). Current Sinking In the illustration below, a controller's voltage output is sinking a current from the load. Note the voltage source in the load's circuit which is at 15 VDC. Because current always flows from positive to negative, the voltage coming from the controller's output (0 - 10 VDC) will ALWAYS be more negative than the load's source of 15VDC, thus a current will flow from the load's voltage source through the controller's output circuit to reach the negative (RTN) side of the output's circuit. The lower the voltage coming out of the controller's output the more negative it will be as compared to the load's voltage source, thus the output will be sinking the most current when it has a value of 0 volts. It is extremely important when using a controller's voltage output in a way that will make it sink current to know the maximum amount of current the output will be sinking and to ensure it does not exceed the current sinking capacity of the controller's output. The following table shows the sourcing and sinking capabilities of the voltage outputs of the different controllers. CONTROLLER VOLTAGE SOURCING CURRENT SINKING COMMENT i2/b3 814 Voltage output 0-10 V @5 ma max 1 ma max Exceeding the 1 mA sink limit will cause the IO readings to be incorrect. ie, inputs may read 999.99

Issue Need to send Continuum alarm messages to email addresses  Product Line Andover Continuum Environment Continuum Cyberstation Cause Alarm delivery required to remote users via email.  Resolution Please note this resolution is applicable to all versions of Continuum Cyberstattion and requires Microsoft Exchange or Outlook to send emails.  However, CyberStation version 2.xx does not necessarily require Microsoft Exchange or Outlook to send emails for alarm notifications. Instead, it is possible to configure an SMTP server on the network and use it to send alarm email notifications directly to the intended recipient.  Please refer to SMTP Email Alarm Configuration in Continuum 2.00 to 2.03    Here are some requirements for forwarding Continuum workstation alarm events via email and paging: The Continuum workstations that have been designated primary and backup email and/or page handlers must have an email client such as Microsoft Exchange or Outlook. The email client application must communicate with an existing email server application, such as MS Exchange Server. The primary or backup email/paging workstation must be running Continuum at the time an alarm is generated. Each EventNotification object associated with the alarms that you wish to email or page must have its own email distribution list in the personal address book of the client email application using a specified naming convention as outlined in the table below. This email distribution list must be stored in the first address book shown in the list of available address books in the email client application. For example, if you create an EventNotification distribution list in the Personal Address Book in Microsoft Outlook, then the Personal Address Book must be the first one showing in the address list dropdown box when you open the Address Book.   How to Create an EventNotification Distribution List Note: The following steps are based on Microsoft Outlook. Other mail applications may have different menu names and choices but the general procedure is the same. Step Action 1 Open the Address Book for the email account on the Continuum workstation that will be providing the email/paging services. Your toolbar may have a button for this. If not, use the Address Book option of the Tools menu. 2 Select New Entry from the Address Book File menu. 3 Select the entry type Personal Distribution List and put this entry in the Personal Address Book. 4 In the Name field enter a name for the distribution list using the following format: For E-mail: ACC.name For Paging: ACC.page.name where name is the name of the EventNotification. 5 Add members (the email addresses or pager and service numbers of those to whom the notification of the alarm will be sent) to your personal distribution lists. 6 Set address book options so that the address book where your personal distribution lists are stored is the first one to be searched when sending emails or pages.

Issue Internet Explorer on Windows Server 2008 (R2) gets "Incorrect User or Password, please try again" or "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" when logon to the Webclient server. Product Line Andover Continuum Environment Webclient 2.0 Windows Server 2008 / 2008R2 Internet Explorer 9, 10, 11 Cause Internet Explorer security issue and the compatibility issue. Resolution Change the setting of the IE 11 on Server2008 as below: When Webclient logon from IE gets error "Incorrect User or Password, please try again": Set the Webclient server a Trusted site : From IE menu, select Tools -> Internet Options -> Security tab -> select the Trusted sites and click the Sites button -> add the Webclient to the Trusted Sites list. When Webclient logon from IE gets error "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" : Set the Compatibility View: From IE menu, select Tools -> Cmpatibility View settings -> add the Webclient name or IP address to the Compatibility View list. Also refer to:  Do we support 64-bit Internet Explorer for use with WebClient? HTTP Error 500.21 Internal Server Error logging into WebClient. or ASP.NET setup custom has stopped working when trying to register .NET 2 using aspnet_regiis.exe Invalid user name or password dialog when logging into webclient with acc that works in Continuum Error: "Unable to load the .Net control for this page." when trying to open a schedule or trend log in WebClient

Issue No Communications when directly connecting to a MicroNet Controller. Product Line Satchwell MicroNet Environment MicroNet controller (MN300, MN440, MN500, MN620 or MN350, MN450, MN550, MN650) using VisiSat Cause Controller subnet setting incorrect. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Go to the VisiSat server on the taskbar by the clock.      Drop down the Network menu Then select restart. This will reset the controller subnet setting to 1 Now the Visisat server should be able to connect to the controller.  

Issue Replacing an older style 400 I/O with 400A series hardware, the Digital Inputs need changed to reflect the newer style of Universal Input. Product Line TAC Vista Environment Xenta 400 I/O Xenta 421, 422, 451, 452 Xenta 421A, 422A, 451A, 452A LonMaker Replace Cause Hardware changes in the Xenta 400 "A" series I/O will not function as a replacement to a non-"A" series without additional changes to Menta and LonMaker. Resolution Part 1- Changes needed within Menta Open the controller’s application (a Menta file). For ES projects, this file should be stored within C:\TAC\Vista\Applications. Note the I/O module that needs to be replaced. A list of I/O modules can be found under the Options menu on the Device Specification page:   Find and record all input points on the I/O module to be replaced. This list is found in the I/O Configuration Table under the Options menu. For example, write the "Name" and "Bound To" address for every point referencing M2.   After you have noted all of the addresses for input points on the I/O module that will be replaced, you can edit the device type for the I/O module to reflect the new type (421A or 451A). Making this change WILL remove all DI mappings (421: X1-X4) and all thermistor mappings (451: B1-B4) affected by the change in module type.   Double-Click on each DI block from the 421 (X#) or on each AI thermistor input block from the 451 (B#) that you are updating to a 421A or 451A.   The following window will appear. Click the Bind button.   Update Menta FOR 421A POINTS: The controller’s DI points are now UI points. Select the Terminal Ref based on the old mapping: X1-U1, X2-U2, X3-U3, X4-U4 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. FOR 451A POINTS: The controller’s thermistor inputs (B#) are now additional Universal Inputs. Select the Terminal Ref based on the old mapping: B1-U5, B2-U6, B3-U7, B4-U8 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. **Repeat step 7 for all affected points on the I/O module you’ve updated. Repeat steps 2-7 for every I/O module that needs to be replaced by a 421A or a 451A. PART II - Integration Within LonMaker locate the controllers that you want to change out for a 421A or 451A   Right click on them one by one, a click "Delete."   Open the Vista System Plug-In. Right click on the controller in which you want to change the .MTA application. Click "Configure."   Click "Browse," and locate the updated .MTA file you saved   Click "NO" when asked if you want to remove the devices   Click "Add and Match"   Click "Apply"   Re-Synchronize LonMaker   Your controllers should now be 421As or 451As

Issue Error Getting IIS object: IIS://LocalHost/W3SVC/1/Root/webclient. Automation error Invalid syntax when installing webclient Environment Webclient Windows XP Windows 7 Cause IIS must be installed prior to webclient or the webclient applications cannot be created Resolution 1. Install IIS prior to the webclient install (See the installation guide section Pre-installation Microsoft Tasks) 2. If IIS is already installed, run the following command from a DOS prompt (Start>Run>cmd) CD\ + enter Cd \Windows\Microsoft.net\Framework\v2.0.50727> aspnet_regiis.exe -i + enter Reboot the PC and reinstall webclient Windows 7: Ensure that all the specific IIS components are selected according to the webclient installation guide See the section Configuring IIS for Windows Vista and Windows 7. There are specific components that must be selected in order for the webclient applications to work properly. If a component was missed, select it, then restart IIS and Continuum.

Issue What is the part number for a flying lead temp sensor for Continuum? Environment Measuring air temperature in fan coil applications or exhaust ducts Cause On site or inability to find the HVAC Sensor Catalogue Resolution STD550 The 550 is intended for measuring air temperature in fan coil applications or exhaust ducts. The sensor, which are made of stainless steel, is delivered with a 2m (6.5 ft.) cable, PVC sheathed overall. Mounting details such as screw and clamp are included with the product. Description Duct Temperature Sensor STD550 Order Code 5123058400 Part Number STD550 For Continuum Systems   HVAC Sensor Catalog in pdf format

Issue After the successful installation of Continuum 1.9x, users are receiving a DCOM Permission error when logging on to Continuum webClient. The error is intermittent. Product Line Andover Continuum Environment Microsoft Server 2008 Standard Microsoft Windows 7 Continuum 1.9x and 2.0 Continuum webClient Server Remote Desktop Cause When a remote desktop connection is made on Windows 7 or Windows 2008 Server the console occasionally gets locked. It stays locked until the local session is restored with a logon. Resolution Create a .bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console **************************************************************************************** Place this file on the desktop of the Continuum webClient Server system. When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be run "As an Administrator." This will disconnect the session and restore the console.

Issue Satchwell VZF 2-Port Flanged Valve Body requires replacement. Environment Satchwell 2-Port Plug and Seat Flanged Valve Body VZF1727                                VZF 1727 VZF1777                                VZF 1777 VZF1852                                VZF 1852 VZF1902                                VZF 1902 VZF1954                                VZF 1954 Cause Obsolescence of Satchwell VZF 2-Port Flanged Valve Body Resolution A number of alternative S-E 2-Port Flanged Valve Bodies are available to replace existing Satchwell VZF 2-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E VG221F 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L9TVG Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the VG221F 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E V222 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L8TV Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the V222 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2-port Flanged Valve Body  Similarly, the centre line to bottom of third port dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2port Flanged Valve Body  As a result alterations to the pipework connected to the VZF 2-port Flanged Valve Body will be required. Details of the Satchwell VZF 2-port Flanged Valve Body may be viewed here. Details of the S-E VG221F 2 port Flanged Valve Body may be viewed here. Details of the S-E V222 2-port Flanged Valve Body may be viewed here. Details of the S-E L9TVG Linkage Kit may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue Do IP settings go to defaults when flashing from 4040 to 9640? Product Line Andover Continuum Environment bCX9640 bCX4040 Cause Have a need to flash a controller from bCX4040 to bCX9640 over a remote connection access. Do not want to have to go to the site to reset IP settings.  Resolution Using CyberStation v1.93 a bCX4040 was flashed to a bCX 9640 and it did NOT lose its IP info. Notes: At the end of the upgrade an error was received: “The uprev could not communicate with the specified controller”. From the webpage it was noted that the IP address had not changed and the upgrade was successful. It did not come back online in CyberStation. From the webpage, resetting it still did not bring it back online in CyberStation. Changing the model number in CyberStation to bCX9640 (from bCX4040) to bring it back online was not an option. The flash upgrade had reset the ACCNetID to 1. The 4040 was then deleted (Bacnet side first then Infinity side) and a new 9640 was created. The proper ACCNetID was set up in the webpage and the changes committed. It was then online in CyberStation. Bottom line – IP address never changed. ACCNetID did. The controller never had to be touched during this process so remotely doing this is expected to work. This was only tested using the latest firmware and CyberStation v1.93. Of course, the best way to do this is on the bench not on a live system. Please be aware that the model flash change will cause node count and/or xdriver upgrades to be reset if they were added as post-factory-shipment upgrades (via the Repair Dept) since these upgrade UPD files are model specific. See Node or XDriver Upgrade of BCX Inf (9640) to BCX BACnet (4040) or reverse. Also see Update b3 or i2 OS, changing (converting) a controller, BACnet to Infinet or Infinet to BACnet .

Issue "You need to enable JavaScript in your web browser to be able to use Building Operation" message is displayed in the browser window when accessing EBO WebStation using the URL "https://<IP>/login/login.html" Product Line EcoStruxure Building Operation Environment Building Operation Webstation 5.0.3 and later Cause In order to bypass automatic guest account login, some sites have used https://<IP>/login/login.html as a direct URL to the login page. In EBO 5.0.3 this direct URL has been changed to "https://<IP>/login.html" to allow PCT 2.0 to operate correctly. Resolution Use the new "https://<IP>/login.html" URL to bypass automatic guest account login and update any saved browser bookmarks.

Issue What are the replacement battery part numbers? Product Line Andover Continuum Environment Continuum and Infinity controllers i2, b3, CX, bCX1 SCX920, LCX810, LCX800, TCX850 Cause Replacement part numbers required. Resolution All the i2/b3 controller battery types are covered on pages 48/49 of the b3 Controller Technical Reference The CX9200, CX9400, and CX9900 all use 2 off: 12V 6.5A lead acid gel cells, Part number: 01-2100-423 The Part number for the bCX1 battery is: BCX1-BAT-KIT The Part number for the ACX57xx battery is: ACX2-BAT-KIT The Part number for the NC2 battery is: NC2-BAT-KIT For the older Infinity Controllers: SCX920, LCX810, LCX800, TCX850 – ½ AA 3.6V 850mA-Hr  e.g. LS14250

Issue Customer are running an ES with version 3.2.3 sending emails through SMTP server using TLS protocol. After site is upgraded to version 4.0.3, emails are not sent and the following error is shown in the ES: "SSL routines: tls_process server_certificate:certificate verify failed. Email service failed to connect to SMTP Server." In version 6.0.3, the following error is also displayed in the ES: "error:16000069:STORE routines::unregistered scheme" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server version 4.0.1 and later Building Operation Automation Server Premium (AS-P) version 4.0.1 and later   Cause The following is stated in the EBO version 4.0.1 release notes: "Certificate validation for SMTP When choosing TLS as encryption method (i.e. encryption of all traffic) for SMTP, then the certificate will be validated from EBO 4.0. If a corresponding CA-certificate isn’t present in the server, then a system alarm is generated. See more in “CA Certificate Management” ( also in section 2.17.5) how to import CA Certificate." Resolution In EBO version 4.0.1 and later a valid certificate needs to be installed if alarms should be sent when using TLS protocol in the communication to the SMTP server.