Building Automation Knowledge Base

Issue How to add another TAC Vista server node into an existing server in TAC Workstation. Product Line TAC Vista Environment Vista Workstation Cause Multi-sever Vista system is the system which has more than one Vista Server in the network. One Vista Server will be assigned as the master and the rest will be assigned as slaves. The order of setting multi-sever system is very important in order to make the system work properly. Common mistakes are: Vista servers have different versions. Adding slave computers before adding the master computer. Using same names of Vista servers. Using dynamic IP address. Vista Server object names are the same. All folders and objects found at the root level of the servers must be changed to unique names before merging the databases. Resolution Before doing that, please back up all TAV Vista databases on all computers. All computers should run the same version of TAC Vista. Also make sure all your IP networks are functioning. In addition, all Vista Servers need to be the same version. (eg. Vista 5.1.3 server will not be able to communicate Vista 5.1.4 server when they are noded together.) All computers’ TAC Vista Servers need to have different names. The server name can be checked by opening your TAC Vista Server. By default, Server name is the computer name. If the sever name needs to be changed, please following the steps listed below: Go to TAC Vista Server Setup Go to Vista Database tab Under “Rename Vista Server to” text field, type the new name Click ok and start the Vista Server to make sure the name has been changed Choose one computer to be the Master and the rest of the computers will be Slaves. Start by shutting down all instances of TAC Vista Sever and TAC Vista Workstations. Add Slave Servers into the Master Server. Start the Master TAC Vista Sever, and then start its TAC Vista Workstation. Right click on the Vista Server object. Select New>Object>Node. Type $LAN.SlaveServerName. If the Slave Server name is different from its computer name, change the IP/DNS address in the property window. (Note: this step requires a static IP address) Right click on the Slave Server Node and select Properties. Type in the IP address in the IP address/DNS name field. Repeat steps a-e for any additional Slave Servers. Leave the Master Server on, and start the Slave Server. Follow steps 4 a-e for adding Master Server into Slave Server but use the Master Server’s server name and IP address this time. Then, right click on the TAC Server object in Slave Server computer, select Properties. Under the General tab, change the Network Master to the Master Server name. Then click OK. If you have multiple Slave Servers, add the Master Server into each of them. Shut down all instances of TAC Vista Workstation and TAC Vista Server. Restart the Master Server’s TAC Vista Server and its TAC Workstation first. Then start the Slave Servers’ TAC Vista Server and their TAC Workstation. You should be able to view the Slave Servers under Master Server. Note: Master Server can view all Slave Servers’ projects, and each Slave Server can view Master Server’s project. However, each Slave Server cannot see other Slave Servers unless you node Slave Servers to each other. Any change made in Slave Server’s TAC Workstation will be reflected in the Master Server’s TAC Workstation. Vice versa also works.

Issue After migrating a TAC Vista export containing TAC Xenta IO modules to SBO, some or all TAC Xenta IO modules are missing the neuron ID's Environment Migration TAC Xenta IO module Cause During the migration, the TAC Xenta IO modules are matched on their name. If the name in TAC Vista differs from the actual name in the associated Menta file, the match can't be made and the properties on the IO modules can not be set. Example of this scenario In TAC Vista   In TAC Menta Resolution 1. Edit the Menta application through TAC Vista Workstation 2. Rename the IO modules in Menta 3. Save to Vista 4. Device gets dirty and need download - download to get rid of the dirty mark 5. Export database in through TAC Vista Workstation 6. Convert to SBO using the Conversion Tool

Issue If only Cyberstation was installed, but Webclient is needed will installing Webclient over the top work? Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause At times a Webclient install is needed but a Cyberstation installation was done. Resolution Trying to install over the top will not install the needed web components. The recommended installation of Webclient when Cyberstation has been installed first is as follows: Uninstall Cyberstation Reboot Install Webclient Run the following command after the install to re-register .NET framework with IIS. C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i​

Issue Can not enter the unlock code in WorkPlace Tech Purchasing Software, the “Unlock” button is grayed out. Environment WorkPlace Tech Tool software, release 5.7 or newer Cause WorkPlace Tech Purchasing Program was not properly closed after the codes were generated.  The Purchase program was closed using the “X” button, not the “Done” button.  Registry and file information does not get saved to the computer when the purchase program is closed using the “X” button. Resolution Re-run the purchasing program and select the same options. This time close the purchasing program using the "Done” button, not the “X” button.

Issue Trying to add B3 controllers to BCX and they are not coming online. Product Line Andover Continuum Environment BCX 4040 Continuum 1.9X B3XXX  controllers Cause BacNet wiring can not be in a star configuration. There can not be more than two terminating 120 Ohm resistors. Resolution The Bus must be wired in series with end line 120 Ohm resistors. Install a B-Link if the bus path cannot be wired in series. Please see the BacNet Technical Reference manual for wiring examples.

Issue It is unclear how to unlock a door from a graphic. Product Line EcoStruxure Access Expert Environment V2   Hosted Instance & Premise Install See Premise Installs on Windows OS for supported Windows OS Cause In order to unlock a door from a graphic, the door reader must first be added to that graphic. Resolution To add a door reader to a graphic, do the following: From the “General Configuration” tab navigate to “Floorplans” and select the correct floorplan, then go to the hardware tab. Add the appropriate reader by clicking the green +, then drag it to the correct location on the floorplan graphic. Save the change to the floorplan graphic. From the “Access Control” tab navigate back to the newly updated floor plan. Now you can right-click on the reader and select “Unlock”. This will unlock the corresponding door.

Issue ENC is licensed for ASD but gets error "Unlicensed: javax.baja.license.FeatureNotLicensedException: tac_llc:tacasd" when attempting to access the ASD Network property sheet. Environment I/A Series G3, ENC-520 with TAC-LLC license installed. Cause When displaying the I/A Series G3 Platform details via the Platform Administration screen in the Workbench, the display shows the following for licensing: Licenses Tridium.license (Tridium 3.6 - never expires) TAC_LLC.license (TAC_LLC 3.6 - never expires) Certificates Tridium.certificate (Tridium - never expires) This information shows that the Tridium and TAC_LLC licenses have been installed but only the Tridium certificate. The TAC_LLC license will not be recognized unless the TAC_LLC.certificate is also installed (as shown in the following platform details display. Licenses   Tridium.license (Tridium 3.6 - never expires)   TAC_LLC.license (TAC_LLC 3.6 - never expires) Certificates   Tridium.certificate (Tridium - never expires)  TAC_LLC.certificate (TAC_LLC - never expires) Resolution There are two ways to resolve this issue. If you have previously installed the TAC_LLC.certificate in any other version of the G3 software, you can import that certificate into the version you are currently running. Open Workbench and connect to the subject ENC. Open the Platform then select License Manager. In the License Manager, select [Import] under the certificate section of the window. Browse to the "certificates" folder under any other G3 installation folder and locate the TAC_LLC.certificate file.  If the file is not found, check the "certificates" folder of another G3 folder.  Click on the TAC_LLC.certificate file name then click [OK]. The certificate will automatically be copied and installed.   If public ethernet connectivity is available or the certificate is not found, download the TAC_LLC certificate from The Exchange Download Center. Use Workbench to import the downloaded file.

Issue Crystal Reports with I/NET 2.41 and higher Design tab is no longer available (missing) within SevenReports. Can no longer edit Crystal (Seven) Reports Product Line TAC INET Environment SevenReports (Crystal Reports) with I/NET 2.41 and higher Cause I/NET will no longer have the "Crystal Reports" Modify and Design license after May 2012. After 2.41 you must buy a separate CD for this function. Upgrades are not affected by this change. Any SAP Crystal Reports licenses used at existing installations will remain active after an upgrade. Resolution RDC version will no longer be supplied on the I/Net CD.   The NON_RDC version will still allow reports to be Viewed and Printed, as always. Modifying a "Canned" report or designing a "New" report will be impossible unless the new RDC version is installed.   This removal of the Crystal report function will start with I/Net Seven rev 2.41A and beyond.   To receive the Crystal Reports application files and license certificate, the SEVEN-REPORTS-RDC part will need to be ordered in addition to the standard I/NET SEVEN software part for each workstation requiring SAP Crystal Reports. Refer to Unable to install the RDC version for additional information and a copy of the necessary software for upgrading and installing this software.   Upgrades (from I/NET Seven Version 2.21 and above) are unaffected by this change. Any SAP Crystal Reports licenses in use at existing installations will still be active after an upgrade as long as you perform an upgrade of the existing I/NET installation.  If you perform a clean install, so you have uninstalled the previous version of I/NET, you will lose this licensing.      

Issue The I/Net Seven Help button goes to Windows Help instead of I/Net Help Product Line TAC INET Environment I/Net Seven Software versions 2.40, 2.40A, 2.41, 2.42 and above. Windows 7 (32Bit & 64 Bit), Server 2008R2 (32 Bit), Server 2008R2 (64 Bit)       Note: In Windows 10 (64 Bit) the Online Function was removed by Micrsoft Cause There are some Windows Downloads, from the Microsoft Web site, that needs to be manually installed on the PC.    Resolution Go to TCON Number and Title Cross Reference (with links) and download TCON 298 (Dated 4/12) Chapter 1, Page 2 see the note in the middle of that page for the required windows download to solve this issue. Also if you look in the readme.txt file in any of the I/Net 2.4X release you will see this comment: 9. If installing I/NET on Windows 7, Windows Server 2008R2 or Windows Server 2008R2 64 bit the following must be done to allow I/NET online help to work.  I/NET Seven's online help is a 32-bit ".hlp" file. In order to view I/NET Seven online help on Windows Vista, Windows 7 or Windows Server 2008, you must first download "WinHlp32.exe" from Microsoft and install it on your workstation. Note: there are different downloads for 32 bit and 64 bit OS's WinHlp32 downloads.   Links to download WinHlp32.exe: Windows 8.1 : http://www.microsoft.com/en-US/download/details.aspx?id=40899 Windows 8 : http://www.microsoft.com/en-US/download/details.aspx?id=35449 Windows 7 : http://www.microsoft.com/en-US/download/details.aspx?id=91 Windows Server 2008 : http://www.microsoft.com/en-US/download/details.aspx?id=19771 Windows Server 2008 R2 : http://www.microsoft.com/en-US/download/details.aspx?id=4424 Windows Vista : http://www.microsoft.com/en-US/download/details.aspx?id=5143

Issue Does Continuum have an interface to the KNX/EIB protocol? Product Line Andover Continuum Environment KNX Xdriver Cause There is a need to interface to a 3rd party device/system via the KNX protocol. Resolution There is no KNX Xdriver formerly listed for download on the Schneider Electric Exchange. However a Beta KNX Xdriver has been developed for a number of select sites and can be obtained via PSS or your local Customer Care Centre (CCC) There are also third party gateways available in the market that may be able to help with this connectivity. They can provide an interface from KNX to another protocol that Continuum supports natively such as BACnet.     Schneider Electric Wiser for KNX Loytec Universal Gateway

Issue Information is needed to set up the APC Xdriver modbus UPS integration with Continuum Product Line Andover Continuum Environment Continuum Windows XP  Windows 7 Windows Server 2003 Windows Server 2008 Cause There are a number of APC devices that support modbus and information is needed to get values into Continuum Resolution The following document, APCConfigExample.zip, is provided as an example and will not address every type of APC device. See Helpful Modbus register Information for helpful information on bring in modbus values.  

Issue How to have visibility into what a controller sees in its list of peer controllers and Cyberstations following a tech. Product Line Andover Continuum Environment All CX controllers Cause Documentation Resolution If controller is 9900 you can perform a "dump controller" from Hyper Terminal and see the list of peer controllers and CyberStations the controller has been taught. For Second Generation Continuum controllers that do not have a terminal interface you can put a program in the controller to get information about the list. (You can use the program in the 9900 as well.) Click HERE to see a sample PE program. IMPORTANT UPDATE: If the site has more than just a few (3-5) controllers comment out the line in the program that gets the controller names. Also, comment out the line that gets the security flag if there are first generation (9900, 9640) controllers involved.

Issue TAC Xenta I/O modules that are added as LonWorks units in TAC Vista, are converted to Xenta I/O modules belonging to a Xenta Base unit (SlaveSpeak devices) in EcoStruxure Building Operation, after conversion using TAC Vista Conversion Tool. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista Server TAC Vista Conversion tool Xenta Xenta I/O-modules Cause In TAC Vista, the Xenta I/O modules are normally located on the same subnet as the Xenta Base unit, and belong to the Xenta Base unit, communicating as SlaveSpeak devices. If a Xenta I/O module is located on another subnet than the Xenta base unit, it could instead be added as a LonWorks Unit in Vista, and therefore communicating via LonWorks bindings to the Xenta base unit using SNVTs. Vista Conversion Tool does not handle this configuration. In the conversion tool, all Xenta I/O modules are expected to be connected directly to a Xenta base unit, located on the same Subnet, and are therefore always treated as SlaveSpeak devices. Resolution After running the Vista Conversion tool, you have to re-build the LonWorks Bindings between the Xenta I/O module and the Xenta Base unit manually in EBO, as the Conversion Tool does not handle the actual configuration setup.

Issue "Controller doesn't know Infinet Id" error when attempting to share data from a BCX9640 to a b3 under a BACnet BCX 4000 Product Line Andover Continuum Environment BCX9640 b3 BCX4000 Cause A program that is attempting to map a point value from a BCX 9640 to b3 under a BCX 4000 receives a program error "Controller doesn't know Infinet Id." The infinity protocol does not get routed. Resolution The BCX4000 must be upgraded to a BCX4040 by requesting this from repair. Follow Share data between standard Continuum controllers and Continuum BACnet controllers to get the best performance.

Issue User names and passwords are not accepted by the AS's. Environment Domain Password Users Cause A new Domain was configured on the ES, this configuration was then exported, the export was then imported to each AS. Resolution Note;- By importing and exporting copies of the Domain, Domains that are not related to each other, are created, which is unlikely to be the operational intent. Exporting/Importing will duplicate user accounts etc. Having multiple accounts with the same name (potentially with different passwords) throughout the system can lead to an overly complex and un-manageable configuration. To create a new Domain configuration, carry out the following. Add the Automation Servers (AS) to the Enterprise Server (ES) in the normal way. With the Workstation connected to the ES, select "Control Panel" and "Domains"     "Add" a new Domain, giving it a suitable name, and then select the AS's that will share this Domain with the ES.       Now Create the Domain. At this stage, if the AS's are reviewed, the New Domain can be seen, (Note - Nothing is shown in the Domain folder on an AS).                           If required, you can choose to set the new Domain as the default Domain,  this is achieved by right-hand mouse clicking on the Domain and selecting the option. This must be done on each Server.                                       Confirm that the ES IP address is correct in all servers.     Finally create the User Groups, Users, and Workspaces required for this Domain. Log off the Workstation, and restart  the ES. Once the ES has restarted, log back on using the new Domain information.   Log on to an AS using the new Domain information.     

Issue Having difficulties determining which firmware/hardware version supports which feature. Some of main questions are: Is an SE8000 compatible with an MPM's firmware Can zigbee NYCE sensors be paired with MPMs Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SE8xxx Room controller SE8000 Series SER8300, SE8300, SE8350, SE8600 Ex. Viconics branding VT8000 Series Cause Firmware versions are frequently updated to introduce new features Resolution   Room Controller Firmware Zigbee-Module Application MPM's Firmware Comments Lua4RC 1.0.7 N/A 2.13.4 and up A script must be uploaded via BACnet or USB cable in order to view the "LUA" Menu. ZigBee NYCE Sensors 1.0.6/1.0.7 051 - 0131R05 and up 2.13.4 and up   SE8650   1.2.0 051 - 0131R06 and up 2.17 and up   SE8600   1.0.7 051 - 0131R05 and up 2.13.4 and up   SE8300/ SER8300 1.0.7 051 - 0131R02 and up 2.12.4 and up No label on ZigBee Module 1.0.6 051 - 0131R02 and up 2.7.2 and up No label on ZigBee Module

Issue Do 3rd party BACnet MSTP devices count as nodes on a BCX controller that is node limited? Environment BCX controller Third-party BACnet MSTP devices Cause Knowing the information will ensure there is not more node than the BCX controller specifies. Resolution Yes they do count as nodes. If you do go over the node count you will see operational problems with the BCX BACnet controller. The BCX controller will scan lock when it tries to perform a time sync to the MSTP network. Modbus nodes communicating via xDriver are not part of the node count.

Issue Wiring detail for using the B&B Electronics model USOPTL4 converter with PSI / XPSI Revision 4.1 Product Line TAC IA Series Environment PSI (Personal System Interface) Revision 4.1 XPSI (Xtended Personal System Interface) Revision 4.1 B&B Electronics USOPTL4 converter Cause PSI / XPSI Revision 4.1 does not work with the Patton Electronics RS-232 / RS-485 converter, model 2089-bc, that was widely used with earlier versions of PSI (rev. 3.13) and XPSI (rev. 2.0). Resolution One converter recommended for use with PSI / XPSI Revision 4.1 is the B&B Electronics model USOPTL4. To connect directly to the RJ-12 jack on an ASD device, or on a stat: Cut the RJ-12 plug off one end of an RJ-12 cable. Connect Black and Yellow wires and tape back. Connect the Green wire to the RDB(+) on the screw terminal of the USOPTL4. Connect the Red wire to the RDA (-) on the screw terminal of the USOPTL4. All four switches of the DIP switch on the USOPTL4 must be in the ON position to allow it to work properly on the ASD bus.

Issue Key for the standard Door Control Graphic Product Line Andover Continuum Environment Door Control Graphic PinPoint Cause Require a key for the standard Door Control Graphic Resolution

Issue Is there a way to use points in I/NET Seven to calculate the "Heat Index"? Product Line TAC INET Environment I/NET Cause Desire to use Heat Index information Resolution You can determine the "Heat Index" within I/NET Seven. The only External points required are the following: Outside Air Temperature sensor Outside Air Relative Humidity sensor Please see the attached Word doc that shows the Calculations involved: