Building Automation Knowledge Base

Issue Web Service addition Script Web Service Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add Script Web Service files and how to add to a project or site How to create values from Script Web Service Files How to add values to graphic that uses the values from Script Web Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: 1. are hardware, programming language, and operating system independent 2. Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services 3. Web Service interfaces are supported in both the AS and ES 4. Like BACnet, Lon, and Modbus, you can create a Web Service interface.      EWS Interface - EcoStruxure Web Services      Script Web Service - Generic Consume via Script      Simple XML Web Service - Rest Generic Consume via Binding Tool (Web Service addition Simple XML Web Service)      SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Sunrise and Sunset for a particular location data using Script Web Service: -Select New...Interface...Web Service...Script Web Service This first example is for a Calculation program for Results=A+B -Enter the WSDL Service and Endpoint are auto-filled Not necessarily all the time IP Cameras -Script Web Services Interface: -Script Programs can bind to the web service with the "Webservice" declaration. -When the name bound service is typed and a "." is put after it, intellisense drop down will show the available methods WSDL file is brought into the database Drop down methods become available even if the URL of the WSDL is not -The web service capabilities can be used within the code for manipulation, data gathering, or whatever else. -Script Web Services Post and Gets -Script programs can send requests directly to a web service with the SendWebRequest keyword. -The syntax requires 5 specific arguments BaseURL - URL that will be processing the message Method - Method of processing the POST and GET (dictated by URL) Headers - Defines certain parameters that are meaningful to the URL (IsMobileApp:True;IsAndroidClient:True) Content-Type - Defined by the URL Message - What is actually being sent to the URL -Script Web Services - Considerations -Bindings to a web service require a recompile -Display of captured information will get localized   Next, Create a Script Program for Calculations Here is a simple script program which defines the calc and values The below shot is the values A=12, B=3, and the Results of the calculation. Below are the binding for the Script Calc program to the Values The below shot is the binding of the Calc program to the Script Web Service The results are a calculation in which we supply value A and B and the Script Web Service performs the calculation with results of 15.   We can change the value of A to from 12 to a value of 13 which Results in 16 as shown in the shot below.

Issue The Sigma Client reports a "HTTP connection failed" error" when an attempt is made to start it. Product Line Satchwell Sigma Environment Satchwell Sigma release 4.05 and later Cause When the Sigma Client is started, attempts are made to make a connection to the Sigma Server, this connection fails and the Client cannot be started. Resolution There are a number of reasons why this error might occur, suggestions are listed below. 1.  Windows XP operating system - ensure that service pack 3 has been installed, and that all the Windows updates have been applied. 2. Windows 7 operating system - only Ultimate and Professional are supported. 3. Sigma Client/Server software must be installed by a Windows user with "Admin" privileges. 4. Windows Firewall must either have been switched off, or has "Exceptions" configured as explained in the Sigma 4.05 SP1 release note. 5. Check that the "SigmaSVR" service has been started. If this service cannot be seen, then this is an indication that the Sigma software has not been install by an "Admin" user, and the software must be reinstalled. 6. Corruption of the Windows "User" files has taken place. Create a new Windows user with "Admin" privileges. Log on to Windows as the new user and test the Sigma Client again. 7. If using a VMware image try rebooting the image. 8. SMART is being used and has a modem connected to the PC for uploading data. Ensure that the modem is fully functional. If not, the HTTP error can be caused. This was seen at Sigma: R4   Release 3.44.14. and Smart Task Manager  3.0.2.20. Added 26-07-2012 9. This may be because a proxy server is being used, eg on school networks. Log on to your PC computer with an administrator account. Open the "Start" menu and click on "Control Panel." Double-click on the icon labeled "Internet Options." Go to the "Connections" tab at the top of the window and then click on "LAN Settings." Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Added 25-09-2012. 10. This issue was reported from a School where Sigma 4.05 SP1 had been operating correctly for several weeks. The issue was traced to the Anti-virus software Sophos, which had received an update prior to the failure. Sophos had quarantined two Sigma dll files. To correct this issue both Sophos and Sigma were uninstalled. A later version of Sophos was installed, and then Sigma was reinstalled, this corrected the problem. Added 01-08-2013 11 - Sigma software installed when connected to a wireless network. The Sigma client will only connect to the server when the wireless connection is made. Uninstall Sigma, disable the wireless, enable the network card, and then reinstall the Sigma software. Added 03-10-2013 12. DELL PC, with firewalls and antivirus disabled and no wireless card fitted. There may be a service or an application running in the background as part of the vendors Windows platform makeup.Restore the same version of Windows, but without (where possible) any of the Vendors applications. Re-install Sigma. Added 16-05-2014 13. Check the port number in c:\sigma\bin\setupsvr.exe, the default is 8080. Added 19-05-2014 14. Flexera license software has been reported as a cause for receiving this error. Flexera license software uses port 8080, (IMADMIN.EXE). Stop Flexera and retry Sigma. Changing Sigma from port 8080 to 8081 could also provide a solution. Added 27-08-2014 15. The SBO PCS (StruxureWare Building Operation Project Configuration Server) also uses port 8080.This needs to be stopped or will conflict with Sigma and produce the HTTP error. Added 02-09-2014 16. Make sure any data is backed up from the installed Sigma system. Uninstall Sigma using Add/remove programs (Win XP) or Programs and features (Win 7). Wait for the Sigma un-install process has completely finish. Delete or rename the C:\Sigma folder to.......for example Sigma1. Re-install Sigma by using a right mouse click on the "SigmaSetup.exe" file and select  A new clean Sigma folder will be created during the install. Once completed reboot the computer. Check the SIgma server is running and run up SIgma. Added 01-10-22014 17. The HTTP error can also caused if the computer name contains extended ASCII or Unicode. For example a computer named "Pást" may fail, if the computer name is changed to "Past" this may correct the HTTP problem. Added 23-11-2021 18. On SE laptops, the McAfee firewall has been updated: Go to McAfee (under hidden icons) > right click 'Quick Settings' > 'Enable Firewall Timed Groups'. This will provide a 1 hour window to run Sigma, in the McAfee pop up window. add a reason e.g. Sigma.

Issue How many objects, users, devices, etc. per device with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation Building Operation WebStation Cause How many objects per device and what are the limits of EcoStruxure Building Operation? Resolution The primary source of these details should be the Architectural Guidelines on WebHelp Topic for the version being used

Issue Device Administrator is not able to load new database version into AS-P. Error message “New database failed” Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause The new McAfee firewall policy where Local the firewall is blocking ICMP6 to the PC. The device needs to be able to "call back" to the PC. If that doesn't happen, the upgrade will not continue and stop at exactly 70%. This is seen in 3.x, EBO 2.0 does not exhibit this issue The device may be defective due to software or hardware error. Resolution   The McAfee firewall issue can be resolved by:  Temporarily disabling the local firewall Trying another PC since McAfee policy or some restriction might have caused installing 3.2 to fail. Another possible solution for this issue which we have seen working is to first install version 3.1 using DFU mode and create a new database and then upgrade to version 3.2 using IP connection.   How to cross-testing and identify if the device is defective? Use the same PC and Device Administrator to install a new DB on a different AS-Ps.  If the same PC can install a new DB on a different AS-P then the issue is not on the PC. Use another PC with the same version of Device Administrator to install a new DB on the suspecting device. If it fails to install a new DB then RMA is needed. Remember to DFU the device before installing a new DB.

Issue Certain Xenta controllers and I/O modules can accept 1.8k thermistor temperature inputs. Product Line TAC Vista Environment Xenta 121-FC Xenta 200 Xenta 300 Xenta 420A Xenta 450A Cause What is the temperature vs resistance curve of the 1.8k thermistors for Xenta 300? Resolution All Xenta controllers and I/O modules, except the Xenta 102-AX use the same 1.8k thermistor (type 1.8KA1). The following table shows details the Temperature vs. Resistance characteristics for this thermistor. Temp (°C) Minimum kΩ Nominal kΩ Maximum kΩ -50.0   60.87  63.88  67.03  -45.0   45.41  47.5   49.68  -40.0   34.23  35.68  37.2   -35.0   26.04  27.07  28.13  -30.0   19.99  20.72  21.47  -25.0   15.48  16.0   16.54  -20.0   12.09  12.46  12.84  -15.0   9.512 9.779 10.05  -10.0   7.541 7.733 7.929 -5.0   6.021 6.16  6.301 0.0   4.84  4.94  5.042 5.0   3.916 3.988 4.061 10.0   3.189 3.24  3.293 15.0   2.612 2.649 2.686 20.0   2.151 2.177 2.209 25.0   1.782 1.8   1.818 30.0   1.478 1.496 1.514 35.0   1.233 1.25  1.267 40.0   1.033 1.049 1.065 45.0   0.8698 0.8848 0.9001 50.0   0.7357 0.7497 0.7639 55.0   0.6251 0.638 0.6511 60.0   0.5334 0.5453 0.5573 65.0   0.457 0.4679 0.479 70.0   0.3931 0.4031 0.4132 75.0   0.3395 0.3485 0.3578 80.0   0.2942 0.3025 0.311 85.0   0.2559 0.2634 0.2712 90.0   0.2233 0.2302 0.2373 95.0   0.1956 0.2019 0.2083 100.0   0.1718 0.1775 0.1835 105.0   0.1514 0.1566 0.1621 110.0   0.1338 0.1386 0.1436 115.0   0.1186 0.123 0.1276 120.0   0.1054 0.1095 0.1136 125.0   0.094 0.0977 0.1015 130.0   0.084 0.0874 0.0909 135.0   0.0753 0.0784 0.0816 140.0   0.0676 0.0705 0.0735 145.0   0.0609 0.0635 0.0663 150.0   0.0549 0.0574 0.0599

Issue Troubleshooting steps for the Infinet and MSTP bus. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum SmartStruxure RS-485 Infinet BACnet MSTP Cause Methods are needed to troubleshoot the Infinet and MSTP bus Resolution This is not a comprehensive list of all methods for troubleshooting, but a starting point. The Infinit-mstp troubleshooting document is available here. NOTE If BACnet MSTP devices do not support COV subscriptions, then care must be taken when reading values (eg EBO trends or alarms) as excessive traffic can be created that overwhelms the communication bus. For example, if 30 non-COV BACnet devices have EBO alarms (or EBO change of value trends) bound to 4 objects in each controller, this will create 240 packets (reads/replies) that will be attempted every "Minimum polling Interval". This is likely to fill the MSTP bus bandwidth  

Issue Getting javax.baja.xml.XException: Error parsing value error message when attempting to add a new driver network to the I/A Series G3 station's Drivers container. Drag and Drop - drag network container from palette and drop onto the Drivers container Copy and Paste - copy network container from palette and paste into the Drivers container Drivers Manager (New selection) - wizard to add new driver Error details displayed:  com.tridium.fox.session.ServerException: javax.baja.xml.XException: Error parsing value [38:4] Environment Enterprise Network Server, ENS, ENC, JACE Cause The module associated with the driver has not been installed in the local modules folder or remote station. Resolution Enterprise Network Server Stop Workbench Copy the missing module directly into ~\modules directory for the version of I/A Series G3 being used. Restart Workbench ENC or JACE Open the platform for the ENC/JACE Install the module using the Software Manager. A station reboot may be required.

Issue Communications failure due to transaction timeout when reloading b3 device. b3's version number as seen from the Infinity side reads 0.0000 Product Line Andover Continuum Environment CyberStation bCX4040 b3 Cause A b3 BACnet controller is found to exist in the BACnet folder under an MSTP Network which is different from the Network specified in the bCX's comm2 Port. Resolution Delete the MSTP network under the BACnet folder and perform a 'Find new BACnet devices'.  A new MSTP network should be created with the right network ID.

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document 

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue How to connect to the Jace 8000 system shell Product Line TAC IA Series Environment I/A Series Jace 8000 Cause Multiple diagnostic and low-level configuration processes need to be performed directly connected to the Jace 8000 in the system shell of the device. Resolution Connect the USB cable between the controller’s Debug port and the USB port you are using on your PC   On your PC, start your terminal emulation software. For example to start PuTTY from the Windows Start menu, this is typically Programs > PuTTY → PuTTY. PuTTy can be downloaded at no cost if you do not already have it on your PC. In the tree in the PuTTY Configuration dialog, expand Connection and click Serial. Set the “Serial line to connect to” for your PC’s (USB) COM port to use. For example, COM3. NOTE: You can examine Ports in Windows Device Manager to determine which serial port is in use on the PC. If you don't see the Jace in the COM ports, you will need to install the driver which can be Downloaded from FTDI.  It is also attached to this document below for Win10. Set the “Configure the serial line” fields as follows: • Speed (baud): 115200 • Data bits: 8 • Stop bits: 1 • Parity: None • Flow control: None In the tree in the PuTTY Configuration dialog, click Session and then click/select the “Connection type” as Serial NOTE: (Optional) You can save this configuration to reuse (load) in future PuTTY to JACE serial sessions. To do this, type in a connection name in the “Saved Sessions” field (for example, “JACE- 8000-S”), and click Save. When you start PuTTY again to serially connect to the JACE, select this name and click Load. At the bottom of the PuTTY Configuration dialog, click Enter. At the login prompt, enter a platform user name, and at the password prompt, the platform password. a. If prompted for system passphrase, enter the platform’s system passphrase. If login is successful, the TITAN System Shell menu appears. When finished making platform changes from the system shell, do the following: • If no changes or reboot is not necessary, simply type L to Logout. • If changes require rebooting, select the Reboot option. Type “y” at the “Are you sure you want to reboot [y/n]” prompt, and press Enter. Shutdown-related text appears in the terminal (PuTTY) window. Click the Close control (upper right corner) in the terminal session (PuTTY) window. Click OK in the “PuTTY Exit Confirmation” popup dialog. Unplug the USB connector from the JACE’s Debug port. This procedure is simply how to connect using USB serial port for system shell.  More information about functions available once connected can be found in other Knowledge Base articles and in the Jace 8000 Install and Startup Guide

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.

Issue How to bind BACnet Objects with Priority Levels Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation BACnet MPX, RPC, MPC Cause Servers (ES, AS) and other native devices (MPX, RPC) have slightly differing binding options. EcoStruxure Building Operation BACnet binding offers many options and the information below gives an example of how it can be achieved, it is not the only method. Resolution When binding between BACnet objects in EcoStruxure Building Operation (either external or within the device) it is usually better to utilize the BACnet Priority based control, often this facility is not fully exploited. Object Force and Overrides will use set priorities as in the BACnet Interface setting for the site (see System/Interface Manager/BACnet), the defaults are below. The example below shows a simple bind from a BACnet Schedule-value to a BACnet Binary-value Priority 16 (or other priority as required, as binding at Priority 16 can interfere with simple manual overrides). A BACnet datetime_value has no Priority array, so if you bind, for example, from a "BACnet Schedule Next transition" to "BACnet datetime_value Value" the bind to a Priority cannot be achieved, as below. In addition, the MPX & RPC have some constraints that Servers do not have. If you bind "Transfer Value to" an Object Value Property (rather than a Priority) then further bindings "Transfer Value to" binding to a Priority is inhibited. The screenshot below shows the error that is seen. This promotes using Priorities to control BACnet Objects.

Issue How to configure Custom 37-Bit as well as Infinity 37-Bit Card Format Product Line Access Expert Environment Access Expert Server 2012 and Above Version 2 Version 3 Hosted  Premise Cause When configuring Custom 37-Bit as well as Infinity 37-Bit Card Formats, the settings are different based on the Facility Code, Card Length and Card Formats. The HEX code generated in Live Monitoring can be deciphered to get the correct set of values required to make this work for your application. If you are unable to do so, please contact PSS and open a ticket so that they can help. Resolution The following settings on the screen shots show how to configure Custom, HID Formats and Infinity 37-Bit Formats, please pay attention to the one that will work for your specific application: Open and log on to the respective Access Expert Instance Select the tab Access Configuration to create a new Card Format Name the format accordingly in the description field, this can be used for Infinity 37-Bit if so desired Add the card range by clicking on the page Icon on the Number Range There is a Standard, HID Managed 37-Bit (not Infinity 37) in the drop down in the Card Format Presets This can be used by default but if you have a Custom 37-Bit Format and the Facility Code is known, however the Start Bit and Length will be different. An Infinity 3 Bit Format will use the Parity Bits Create the new format per the screen shots and configure accordingly. Once complete, click on Save or Save and Close, reboot the controller.

Issue When logging into the web server of a Xenta controller using Mozilla Firefox 4 an error message is shown stating that the website is using an invalid security certificate.  When logging into Xenta server using Firefox 4 a certificate error is displayed as displayed below: The complete error screen reads as follows: This Connection is Untrusted You have asked Firefox to connect securely to 192.168.1.152, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Get me out of here! Technical Details (IP Address of Xenta) uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for (IP Address of Xenta) (Error code: sec_error_ca_cert_invalid) I Understand the Risks If you understand what's going on, you can tell Firefox to start trusting this site's identification. Even if you trust the site, this error could mean that someone is tampering with your connection. Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification. Add Exception... How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Mozilla Firefox 4 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Firefox 4) cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution There are two possible resolutions: Install the self-signed certificate using the following steps: Expand the "I Understand the Risks" bullet then click the "Add Exception" button. Firefox will automatically retrieve the certificate from the Xenta server. Make sure to check "Permanently store this exception" and then click "Confirm Security Exception" The certificate is now installed and the warning screen will no longer show up when logging into the server. It may be necessary to restart Firefox for the changes to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Firefox is uninstalled then reinstalled. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate. Purchase a certificate issued by a Certificate Authority (CA): These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. Please see TAC Xenta Server - TAC Networks - Technical Manual for more information. See "There is a problem with this website's security certificate." when logging in to Xenta web server using Internet Explorer 8 for information on installing certificates into Internet Explorer.

Issue Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly requires replacement. Environment Stand alone Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly M 1201 Actuator 2-port Valve Body Cause Obsolescence of Satchwell “M 1201” forming part of combined Actuator / 2-port Valve Body assembly. Resolution There is no direct replacement for the "M 1201" Actuator and as a result both the "M 1201" Actuator and the 2-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly with Schneider Electric MD10B-230 Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B-230 Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. Satchwell MB series 3-port Rotary Shoe Valve Body may be converted for use as a 2-port Zone Valve by means of the installation of a plumber’s plug in Port 3 Install plumber's plug in Port 3 of MB series 3-port Rotary Shoe Valve Body. Tighten plumber's plug sufficiently to ensure PN 10 rating of Valve Body is not compromised. It is possible that the "M 1201" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B-230 Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.

Issue What are the differences between the IAC 400 and the IAC 420 controllers? Product Line Field Devices, Other, Satchwell MicroNet, Satchwell Sigma   Environment IAC 400 IAC 420 Cause The IAC 400 controller is obsolete and its replacement is the IAC420. Resolution Hardware differences; The IAC 400 has 3 Temperature, 2 Analogue and 1 Digital input, where as the IAC 420 has 6 Universal inputs. Communications differences; The IAC 400 controller uses terminal 3 to earth the communications cable screening, on the IAC 420 the screening must be connected to a good earth and not terminal 3. Tables and offsets; Because the IAC 420 has different inputs that tables and offsets are changed, please review IAC Controllers - Tables and Offsets. IAC 400 Wiring details. For the full data sheet please click HERE.   IAC 420 Wiring details. For the full data sheet please click HERE.

Issue "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 Alarm "cannot verify lead object" appears even though AS is online. Product Line EcoStruxure Building Operation Environment StruxureWare Alarm Queue Cause The AS is unable to communicate with the ES. The ES may be able to communicate with the AS allowing the user to view and control the AS, but Value Binds will not work. This type of error can also occur as a result of multiple networks being accessed by the same PC.  It is important that if you are using multiple networks that the ES be configured with the IP address for the correct network. Resolution Ensure that no Firewalls are blocking configured ES and AS ports Ensure all devices are on the same Windows Domain In workstation, select the Enterprise server's Communication Tab and verify that the IP address listed for the ES matches the ES PC IP address. Right click on the ES and select Advanced > Repair Server Communication For more information see Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port

Issue How to create a proper XLSX/Excel template under Alarm Triggered Notification of EcoStruxure Building Workstation, in order to receive the Multi trend logs report in the XLSX/Excel format. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation Cause Additional information is needed to create a template for presenting multi-trend log information in Excel XLSX format.    Resolution Below screenshot shows where users can select the Report format and XLSX template.   The multi trend log containing four Interval Trend Logs 1 to 4 with their time stamp is shown as below as an example   In order to get the XLSX multi trend log report in XLSX/Excel format upon receiving a trigger, the following XLSX template needs to be used containing two rows: The first header row contains the column headers from the trend log. The second row include the <Multi Log List> command   Here is final report in Excel/XLSX format:  

Issue Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Controllers: ENC-410-1 ENC-410-1-N ENC-520-2 ENC-520-2-N Cause There maybe a need to access the ENC via its serial port if the IP address of the ENC is unknown or for troubleshooting purposes when the ENC's Ethernet port is not functioning. Resolution Hardware required for connection to ENC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors. RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430). A functioning COM port on your computer. A 2-pin jumper for connection to the ENC's 'Mode' connector. Refer to the Installations Instructions for ENC-410 (pages 10 & 11) or ENC-520 (pages 10 & 11) for details on the cable and adapter.  Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC also refers to these pin outs. Connection to ENC's serial system shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the ENC’s RS-232 port and the RS-232 COM port you are using on your computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to ENC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port you are using on your computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 57600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Click OK. On the ENC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 7 of the ENC-410 or ENC-520 Installation Instructions for position of the Mode connector. With your HyperTerminal session active and configured to log to a file, remove power from the ENC, let it cycle down, then reapply power.  The easiest way to power cycle the ENC is to unplug the 6-pin power plug from the circuit board, wait 15 seconds and plug it back in.  After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... Do not press any key, wait for the login prompt. If you did press a key to stop auto-boot, select option 1. At the login prompt, enter the platform user name, and at the password prompt, the platform password. The default user name is 'tac' and password is 'niagara'. The system shell menu should now appear. You should able to see the IP address of the ENC now. When finished using the serial system shell, do the following: Remove the 2-pin jumper from the Mode connector of the ENC. From the system shell menu, select the Reboot option. Type 'y' at the 'Are you sure you want to reboot [y/n]' prompt, and press Enter. Shutdown-related text appears in the HyperTerminal window, and then the connection is dropped. Press the Disconnect button on the HyperTerminal tool bar. Exit from the HyperTerminal application, selecting to Save if you wish to reuse this HyperTerminal setup for future connection to an ENC. If you are troubleshooting the ENC, send the HyperTerminal start up messages to Product Support for analysis.

Issue When running TAC Vista in a Network environment, there are several ways of setting up the license system. Sometimes, TAC Vista nodes (Vista users) "steal" license modules for each other. Environment Vista in network Flexnet license Cause When various TAC Vista systems are pointed to the same license server, one server can take or "steal" e.g. an OPC Client license which another server should use. Resolution For a complete explanation about the license system and how to setup the system and control licenses, refer to this video. A useful tool to use is the Options file, with the .opt file extension. Located in the License files folder, its easily monitored in a text editor, and could be used for Reserving or Excluding license modules for other TAC Vista nodes. Other features available for the Options file can be found in the Flexnet Licensing End User Guide. 1: Make a file called taclic.opt and place it in the same directory as the license files. 2: Edit the file with notepad and make the reservations you need. The syntax for each line in the file is "command amount feature HOST host". The feature names can be seen in the license files. Here is an example on how to reserve an OPC Client license for a PC called "BMS_SERVER_1" RESERVE 1 Vista.Server.OPCClient HOST BMS_SERVER_1 3: Restart the license server.