Label: TAC Vista - Building Automation Knowledge Base - Communities

Issue Need to capture steps taken to reproduce a problem or a solution Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Cause A series of screen captures will help to demonstrate the steps needed to reproduce a problem or a solution. You can use this tool to capture the steps you take as a problem occurs and send the output to someone so they can see a screenshot of each step. Resolution In Windows click on the Start menu button  Type "PSR" Windows 7 Windows 7 Windows 10, 2012, 2016 Windows 10, 2012, 2016 Open the Problem Steps Recorder Windows 7 Windows 7 Windows 10. 2012, 2016 Windows 10. 2012, 2016 Click Start Perform the desired tasks Click Stop Choose a location to save the file output The .zip file will contain a .mht file which can be opened in a web browser The screenshots will appear in order  This will be followed by a detailed output of keystrokes and mouse movements. For additional information please refer to Microsoft webpage on this topic: Record steps to reproduce a problem 

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell T range is now known as STR600, STP660, STD600, STO600 10K3A1 with shunt Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding the INET, IA and Balco, the document Thermistor Types Tables (Veris Industries) is available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue Troubleshooting LON Network communications. Product Line EcoStruxure Building Operation, TAC Vista, TAC IA Series Environment Xenta Controllers MNL I/A Controllers EcoStruxure Building Operation AS-P LPA Protocol Analyzer Cause Intermittent communication failures, high bandwidth, error packages, noise on the line -- these can be difficult to pin down and identify. Resolution These two documents produced by Loytec are invaluable resources in troubleshooting a LON network.  The first deals with common causes of noise on LON Wires.  The second details what to do once you've procured an LPA protocol analyzer -- how to use it and interpret data. LON Network Training Network Troubleshooting White Paper For a Vista system, also see Actions for reducing Bandwidth in a Vista network. For an EcoStruxure Building Operation system, also see Bandwidth Throttling.    If an LPA protocol analyzer is not available there is also an option to log the Lon communication to and from the ES, AS-P, or AS-B. To do that you change the debug level from "Information" to "Trace" for: /Automation Server/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon/nsp.pin.lon.comm After the investigation make sure to set the debug level back to "Information" again. For debugging assistance a Tool called SBO Lon Decoder can be used.

Issue The License Server is not working and may show Vendor Daemon Down errors. The LMadmin log shows the error. LicenseEngine (taclic) exited with status 28 Product Line TAC Vista EcoStruxure Building Operation Environment Vista Building Operation Enterprise Server License server Cause Data Execution Prevention (DEP) is activated. Antivirus or other software can scan/use the port used by the vendor daemon. If the time drifts over two minutes and a time synch occurred, the vendor daemon can stop. https://support.citrix.com/article/CTX137111 Resolution First, check that DEP is not activated. Make sure that there is no antivirus program that has portscan activated Make sure there is no other software that uses the same port as the vendor daemon Make sure that the time does not drift too much, if the time drifts two or more minutes and then a resynch occurs the vendor daemon can stop This is more likely on VMware where time synch can occur from either the domain or VMware tool. Check Windows event log (Security) for time synch messages. NOTE: It can also appear just by stopping the server manually.

Issue Need a link to provide an easy way of uploading one or more files to Global Expert Technical Support - Digital Buildings - Asia Pacific Region on Box. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Schneider Electric "Asia Pacific" Box server folder Cause Many email services have a limit on the size of attachments. In many cases, large files must be sent to Support so that the support engineer can investigate a reported issue. Resolution Using the following Box link will allow the upload of case files associated with your support ticket. Please note that you must have an open support ticket with Support before uploading a file. Files uploaded without a reference to a support ticket without previous approval will be deleted.  

Issue .xif file not available for download. Product Line Field Devices, Other, TAC Vista Environment MF20-24M 1M54 00 MF20-24L actuator Cause When configuring the MF20-24L in LonWorks, .xif file is necessary.  Resolution All necessary files for LON connectivity are available here: lon_actuator_v3.0 (1).zip

Issue What are the setup requirements for a L-switch on a classic network Environment Loytec L-Switch Cause What is the best way to setup a L-switch in a Vista classic network. Resolution The best option for a L-Switch on a classic network is in the Smart Switch Mode. In this mode the L-Switch decides based on the destination address of the message, which port(s) the message will be forwarded to. This functionality isolates network traffic. The dip switch settings for this setup are shown here.  Here is a link to the Loytec manual for the wiring configurations.

Issue Where can I get information and documents on the Building Analytics service? Environment Building Analytics Cause Information and documentation is required on this product. Resolution Available documentation is available on the Download Center A diagram of network architectures can be seen Here.

Issue Integration of the Rayleigh Instruments CT-2EA kilowatt-hour meter with the Xenta 5xx\Xenta7xx Xenta 913 and Modbus RTU Environment Xenta 511, 527, 55, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Rayleigh Instruments CT-2EA kilowatt-hour meter Cause Disclaimer:  This device template is intended to provide a starting point for an integrator and is not meant to be a mandatory points list for your integration project. Product Support Services has written this device template in an effort to give our customers a solid example of how to develop a device template for the above product.  The integrator will be responsible for any additions or modifications to this device template.   Please report any problems with this template to Product Support, via the Contact link at the top of this page. Resolution Please use the following dev file as a starting point and a guide to the integration.  This .dev file contains all of the registers in the device published by the manufacturer.  If any other data is required please see the latest Rayleigh Instruments documentation to make the necessary changes.   To use these files in XBuilder please follow these steps: 1.  Extract the .dev file from the .zip file in the link above and place it in a convenient location on your harddrive. 2.  In XBuilder, right-click on the Modbus Master device and choose 'Add Device'. 3.  Browse to the extracted dev file and choose 'Open'. 4.  Rename the newly added device to a unique name within the Modbus Master network.

Issue Integration of the Carlo Gavazzi EM21 Power Meter with the Xenta 5xx\Xenta7xx Xenta 913 and Modbus RTU Environment Xenta 511, 527, 55, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Carlo Gavazzi EM21 Power Meter Cause Disclaimer:  This device template is intended to provide a starting point for an integrator and is not meant to be a mandatory points list for your integration project. Product Support Services has written this device template in an effort to give our customers a solid example of how to develop a device template for the above product.  The integrator will be responsible for any additions or modifications to this device template.   Please report any problems with this template to Product Support, via the Contact link at the top of this page. Resolution Please use the following dev file as a starting point and a guide to the integration.  This .dev file contains a subset of the registers in the device that PSS considers will be of most use to the integration process.  If any other data is required please see the latest Carlo Gavazzi documentation to make the necessary changes.   To use these files in XBuilder please follow these steps: 1.  Extract the .dev file from the .zip file in the link above and place it in a convenient location on your harddrive. 2.  In XBuilder, right-click on the Modbus Master device and choose 'Add Device'. 3.  Browse to the extracted dev file and choose 'Open'. 4.  Rename the newly added device to a unique name within the Modbus Master network.

Issue What are the limitations of the Xenta 527 when used with TAC Vista and I/NET. What do I need to consider when integrating I/NET with TAC Vista. Product Line TAC INET, TAC Vista Environment TAC I/NET TAC Vista 5.1.6 and above TAC XBuilder TAC Xenta Server 527 5.1.6 and above I2V Cause Integrating I/NET into Vista. Resolution Below are a few considerations associated with the Xenta 527 Server that may assist when integrating existing I/NET systems with TAC Vista: As in all case the latest versions of both hardware and software should be used on any integration project. The attached datasheet indicates that the TAC Xenta 527 Web Server has been tested with up to 1000 I/NET points, if you require to integrate more points than this it is then recommended to add additional Xenta Servers to cater for this.  You may also consider segregating your I/NET System to improve performance. Currently it is not possible to pick and choose which points are imported into the XBuilder project, it can only be limited to which SAV file (or controller) is imported . Note: Each I/NET point type, as shown below, creates the following number of TAC Vista objects - these include; Alarm, State, Value, Control, Test, Manual, Alarm_ack etc, and vary according to the point type used. I/NET Point Type Number of TAC Vista Objects created DO 14 AO 11 AI 10 PI 10 DI 11 DA 11     The impact to consider here is the time it takes when adding or modifying your Xbuilder Project. This usually means that importing a large number of SAV files will cause the Vista server to get extremely busy creating / importing all of these objects.  It is best to let the process complete before selecting any other window.  Note that the total number of objects created during the import of the I/NET points is not counted as part of the 'tested' 1000 point limit stated in the above datasheet. This is a separate consideration. Network performance can be affected when a large number of connection objects are in use (so direct transfers between I/NET and Vista). There is no documented limitation, but the recommendation is not to exceed 300 connection objects per Xenta 527 Server.  For information on what the effects a connection object on the I/NET controller LAN has and how to calculate this, refer to Connection Objects in Xenta Server effect on I/NET system. Engineering of any I/NET feature apart from Point Control, Trends, Time Schedule and Alarm Configuration can only be done using the I/NET Host Tool or via an I/NET workstation.  Access to these features are via the Xenta 527 web server feature, so pages appear as HTML pages within TAC Vista, this will have a different look and feel to both Vista and I/NET users.   Other Knowledge Base Articles as listed below are also available to assist on integrating I/NET and Vista: Unit conversions when integrating LON to I/NET Vista to I/NET Integration Tips    Decoding the I/NET signal "flags" attribute Viewing I/NET Point Names in Vista Workstation instead of Addresses User Defined Units on I2V integration were accidentally set incorrectly SQL Host not passing data to Xenta 527 Web Server

Issue Is it possible to view web pages from an Xenta server using an iPhone or Android telephone? Environment Xenta Server 5.1.X Xenta 511, 527, 711, 731 Apple iPhone, iPad or Android smart phone mobile app Cause An increasing demand from customers to be able to monitor a site via a smart phone web browser. Resolution Whilst there are no official apps for iPhone or android smart phones, it is possible to create some static HTML pages which can be viewed in a smart phone web browser. There does however appear to be some restrictions is some web browsers, so try a number of different web browsers before determining if a web page works or not. The steps below outline how to create a simple variables page that can be viewed with a smart phone. An example is also attached as well as 2 copies of the HTML page that needs to be edited to increase the number of variables on the page. 1. Create a new Xbuilder project with the desired controller. 2. Create the folder structure for mobile users. a. Add a folder to the tree structure and name it "Mobile pages" or another appropriate name. b. Right-click on the page and select New\Page\HTML Variable Page. c. Select the tmpl1form.html template when prompted. d. 5 variables will be created in the folder under the HTML page. These are called SignalTag_1 - SignalTag_5. e. If more variables are required, right-click on the folder and select New\Object\Signal. Rename the signal "SignalTag_X" (in the example project SignalTag_6). f. Rename the variable page if required. g. Connect the signal tags to the appropriate signals e.g. LON/Modbus etc. 3. Generate the project. 4. Locate the Xbuilder project in windows explorer. Note the folder structure! 5. Locate the HTML variable page created under Project Name\Target Image\www\info\your folder name\your folder name\ 6. Edit the HTML variable  page that was created in Xbuilder (either notepad.exe or Microsoft front page or another appropriate HTML editor). The editing is to connect the extra variables created. In this example SignalTag_6 a. Locate the TAC_validateForm function at row 39. The original file contains 5 signals (as per the template): 'memsignal.4' to 'memsignal.8' Copy the complete text for one of the signals eg. for a boolean signal ,'memsignal.8','b','RinRange0:1' and then paste the text just before the closing bracket for the function. Rename the signal to memsignal.9 (or whatever the next number in the sequence is). b. Locate the paragraph tr bordercolor = "#000000# that contains the signal memsignal.8. c. Copy the entire paragraph and paste it in the document between the /tr of the previous paragraph and the tr bordercolor of the memsignal.8 paragraph. d. Remove the line containing "input type="submit" name="Submit" value="Submit" from the paragraph containing memsignal.8 e. Add the text: " " f. In the last paragraph containing "input type="Submit"...", change the memsignal.8 text to memsignal.9 and select the correct data type. Save the changes. 7. Copy the edited HTML page from ...\TAC XBuilder Projects\PSS Smart Phone\TargetImage\www\info\PSS Mobile Friendly Site\Mobile Pages to ...\TAC XBuilder Projects\PSS Smart Phone\UserTargetImage\www\info\PSS Mobile Friendly Site\Mobile Pages This creates the folder structure in the Xenta server when downloading the project. a. Download the project to the Xenta server (select "All files" when downloading). b. Browsing the Xenta server should result in a page similar to that shown below. 8. Configure a mobile user and grant the appropriate access levels. a. In the web interface go to Configuration\User Administration\User Administration and create a new user similar to the example below. b. Configure the user's access so they can only access the mobile folder and the pages contained within. 9. Log in with the newly created user and check that the view is similar to that shown below. The values should be able to be updated and submitted using the submit button. This is a very simple example, but this can easily be built upon with a little knowledge of HTML programming. For example, the home page can be adapted by using FTP to retrieve the intro731.html (or introXXX.html if you're using another Xenta server). Open the file and edit the following paragraph: You'll see that the text has been changed to "Mobile users, click here" and referred to a page PSS_HVAC/Mobile.html. This mobile.html page can be created and saved in the correct folder under user target image.  Link to Xbuilder project and before and after variables page.

Issue Some sensors such as the SCR110-H CO2 produce a noisy signal even when wired according to the documented instructions. The following is a trend chart of the unfiltered raw signal from the sensor. Environment Automation Server Continuum controllers TAC Xenta Cause Noisy signal is typically caused by common ground wiring of AC power. Resolution SOLUTION #1 Signal noise can usually be eliminated by using an isolated transformer to power the sensor separately as opposed to using a common transformer that powers up several pieces of equipment. SOLUTION #2 For sensors that support  AC and DC input voltage, signal noise can usually be eliminated by using DC instead of AC power source to power the sensor. SOLUTION #3 Implement a Slew Rate to filter out the noise. As of version 1.7.1, StruxureWare Building Operation does not have a built-in slew rate functionality. Nevertheless, a custom slew rate can be implemented using Script programming. See HowToDebounceANoisySensorSignal.pdf SOLUTION #4 Add a filter (FILT) in a Function Block program after the signal input Description: The function block is a discrete time first order software filter. The filter time constant is specified in seconds with the Time Const parameter. The initial block output value is zero. The filter algorithm is y(k) = y(k-1) + 1 / 1+T/h (u(k)-y(k-1)) where y(k) and u(k) are the filtered and unfiltered values at time k, respectively,h is the sampling interval (i.e. the application program cycle time), and T is the filter time constant. If the time constant is less than or equal to zero, no filtering is done. To obtain a good filter function, the time constant should be set significantly greater than the application program cycle time. This filter algorithm is based on a straightforward backward difference approximation of the continuous time derivative operator. SOLUTION #5 Ensure you are not using older versions of the IO Firmware. As detailed in TPA-SBO-17-0006.00 the firmware should be at least V2.015 in the modules and is available on the Download Center.

Issue Web pages opened in TAC Vista Workstation is shown in compatibility view. That might have unwanted impact on some web pages. Environment TAC Vista Workstation Cause By default TAC Vista Workstation will use the newest version of Internet Explorer installed on the PC, but enable compatibility view. That might have unwanted impact on some web pages. Resolution Add a registry entry to define what version of Internet Explorer you want TAC Vista Workstation to use. 1. Navigate to the following registry key:        32 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION]        64 bit OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION] 2. Add a new DWORD (32 bit) value 3. Give it the name "TACVistaExplorer.exe" 4. Give it the decimal value 11000 to set Workstation to use IE11 This ZIP file contains registry imports that will set the browser used to IE9, IE10 or IE11

Issue What NEMA or IP rating is a specific product? Environment All devices Cause Is a product protected against water and access by foreign objects? Resolution The Degrees Of Protection document details both the IP rating and NEMA Enclosure charts. The IP rating is made up of 2 digits, the first is the level of protection to foreign objects, the second is the level of protection to water. If a product does not specify any rating for water ingress in it's datasheet then the the second digit will be 0. The first digit relates to the size of a foreign object that can be inserted into the product. Typically many Buildings products will not allow the insertion of a finger (12.5mm approx' 1/2") and offer no water protection, so they would be rated as IP20, however it would be IP10 should they have holes of up to 50mm (approx' 2").

Issue Webstation static graphic viewer no longer works in Chrome, FireFox or on smart phones. The "Loading..." image never goes away. Environment Webstation Cause The file "xmlHttpImageLoader.js" located in "C:\inetpub\wwwroot\TACVistaWeb519\Modules\Graphics\ImageLoader" (519 being the version of TAC Vista installed) uses the name "status" for a variable in the script. This variable name is a reserved word. The name is actually not a reserved JavaScript word, but a reserved Windows word: http://www.w3schools.com/js/js_reserved.asp Resolution As only Internet Explorer is supported, this is not going to be fixed. There is however a workaround that will enable viewing graphics in static mode. 1. Rename the file C:\inetpub\wwwroot\TACVistaWeb519\Modules\Graphics\ImageLoader\xmlHttpImageLoader.js 2. Paste this corrected file to the same location

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue There is no clear guidance on how to handle the SNMP settings for TAC Xenta Servers Product Line TAC Vista Environment TAC Xenta Server TAC XBuilder SNMP Cause Previously the SNMP feature has not been widely used and has not been a security concern. There are two types or flavors of SNMP. One is for browsing a device to get information about it (SNMP Agent), and the other is to automatically send alarms from a given device to a central alarm system (SNMP Alarm Trap). Now according to reports from the field, IT departments are starting to get concerned about the SNMP feature in Xenta Servers. A general overview of how SNMP can be used maliciously for intrusion can be studied here. Normally the IT department requests that: The default community string is changed SNMP is disabled Here is an example of what you see when you browse a Xenta Server (having the correct Xenta Server mib file) using a SNMP browser such as "MIB Browser" from iReasoning Here is an example of alarms received from a Xenta Server via SNMP Resolution All (or most) SNMP settings are changed through TAC XBuilder First step is to change the default community name. If the community name is either "private" or "public" (the latter is default), it can be browsed without knowing the name. You simply change the name in "Community Name" and "Trap Community Name". Download all project files to the Xenta Server afterwards. Now when you try to browse the Xenta Server from the SNMP agent without first defining the community name, you will not be able to retrieve data. Next, we can disable the SNMP Alarm Trap. Download all project files to the Xenta Server afterwards. After that, alarms will not be sent to the IP address configured. Following here are advanced steps to change the ports used for SNMP (161 and 162) If the settings described above are not enough, we can change the port number used for SNMP. This is however a little more complicated. You need to connect to the Xenta Server using FTP (Note that the FTP access may be disabled, refer to Disable FTP in the Xenta 5/7/9xx Controllers if unsure how to enable this), and fetch the following file: /sys/system/snmp.cfg Open the file in Notepad Change the two port number as below - you can choose other port numbers, but it is crucial that they are not the same as any other ports used by the Xenta Server. Upload the changed file to the same location on the Xenta Server Download the project from TAC XBuilder, choosing to download all files You now get this message Here you must click "Target system" or the changed settings are overwritten Note that the port numbers defined in XBuilder have not changed yet Save the project and close XBuilder Open the project again You will now see that the port numbers have the value you defined in the file earlier Now when you try browsing the Xenta Server with a SNMP tool, you can no longer connect on the default port 161

Issue Java 8 is only supported together with TAC Vista 5.1.9 Environment Webstation Xenta Server web Cause The current version was developed and tested together with Java version 7, but not Java version 8 as Java 8 was released subsequently After the latest update of Java (Javav 8u31) SSLv3 has been disabled by default in Java. If updating to that version of Java, the Xenta Server web (graphics and schedules) will not work, as the Xenta Server relies on SSLv3. Resolution Making the proper configurations has enabled a number of sites to use Java 8 with the TAC Vista product range. Java 8 is supported for TAC Vista 5.1.9 according to TPA-VSTA-15-0000.03 Refer to this video for settings required: Download video - View on YouTube   The proper settings in Java are: [1] Install the newest version of Java. If you are working on a 64 bit operating system, it's crucial that you install both the x86 and the x64 versions: https://java.com/en/download/manual.jsp [2] Make sure all older versions are removed: https://java.com/en/download/uninstallapplet.jsp [3] Make sure Java is enabled in your browser: https://java.com/en/download/help/enable_browser.xml [4] Add all addresses to the site exception list in the "Security" tab. Both http and https addresses are needed for Xenta Servers. If a special port is used (not 80 for http and 443 for https), the port needs to be entered, e.g. http://IP_ADDRESS:81 if port 81 is used for HTTP communication. [5] Click "Restore Security Prompts" in the "Security" tab. [6] In some cases you might need to add the IP address of the PC or Xenta Server to trusted sites in Internet Explorer   TAC Xenta Server web uses SSLv3 for Java if high security is set in XBuilder. The workaround for SSLv3 being disabled in Java 8u31 and above is: (read Java's own release note) [1] Edit the following two files: C:\Program Files (x86)\Java\jre1.8.0_31\lib\security\java.security C:\Program Files\Java\jre1.8.0_31\lib\security\java.security [2] Scroll down to the last line where it says: jdk.tls.disabledAlgorithms=SSLv3 In both files, comment that line so it says: #jdk.tls.disabledAlgorithms=SSLv3 [3] Edit the file: C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\deployment.properties [4] Add the following line: deployment.security.SSLv3=true

Issue When a XIF file contains NCI's (SCPT's and UCPT's) default values (NVVAL) must be described in the XIF file. In some cases if NCI's are present, but some or all NVVAL initializers are missing commissioning the device will fail. For information regarding NCI's that are part of a FILE definition, please refer to Understanding the FILE part of a XIF file. Product Line EcoStruxure Building Operation, TAC Vista Environment LonWorks XIF Cause When commissioning a device default values to configuration variables must be assigned. If the tool (TAC Vista, SmartStruxure, LonMaker, NL220) does not know what default value to assign, it can cause an error. Resolution Make sure all NCI's have proper initializers defined. Read XIF file - NVVAL initializers.pdf guide as reference. Here is an example of a NVVAL section: VAR nciHrtBtRcv 2 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,48; 107 * 1 4 0 2 0 0 VAR nciHrtBtSnd 3 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,49; 107 * 1 4 0 2 0 0 VAR nciLocation 4 0 0 0 1 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,0\x80,17; 36 * 1 4 0 31 0 0 VAR nciDeviceName 5 0 0 0 0 1 63 0 0 1 0 1 0 1 0 0 1 "&1,0,6\x80,3; 36 * 1 4 0 31 0 0 NVVAL #VAR nciHrtBtRcv \x00,\x00 #VAR nciHrtBtSnd \x00,\x00 #VAR nciLocation = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00 #VAR nciDeviceName = empty string \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00, \x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00,\x00

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.