Notifications

Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Replacement for Drayton A703 Immersion Temperature Sensor by S-E STP600D Product Line Field Devices Environment Drayton A703 Immersion Temperature Sensor installation. Cause Obsolescence of Drayton A703 Immersion Temperature Sensor Resolution 1. Replace Drayton A703 Immersion Temperature Sensor with S-E STP600D The S-E STP600D provides the same functionality as the Drayton A703, differing only in its appearance and dimensions. The S-E STP600D Terminals are not polarised. N.B. It should be noted that the S-E STP600D is not supplied with a compatible Pocket. If it is not possible to utilise the existing Drayton Pocket, then a 100mm S-E Pocket (9121041000-Brass or 9121051000-Stainless Steel) should be selected as appropriate and in order to comply with the system requirements. There is a intentional gap between the top of the pocket, and the sensor housing, to ensure the probe tip touches the end of the pocket.

Issue Configuring LON tunneling in Niagara G3 Product Line TAC IA Series Environment Niagara G3 Cause See below to watch a video document (vdoc) explaining the process to configure Lon tunneling in Niagara G3. Resolution The purpose of this video is to show you how to configure Lon Tunneling in G3. It's already assumed that there is a LON network that has been installed, commissioned, and discovered in the G3 ENC.

Issue SNVT_flow will not display correctly in Imperial units on a TGML graphic on a Xenta Server Product Line TAC Vista Environment Xenta Servers version 5.1.1 or earlier Xenta 511, 527, 711, 731 Cause SNVT_flow will only display on TGML graphics as liters per second regardless of what unit the signal in Xbuilder is configured for when sent to the graphic page. This is a bug and has been reported. Resolution This has been corrected in version 5.1.2. Upgrading to 5.1.2 or later will resolve this issue. If upgrading is not an option, the conversion can be done in a script element of the TGML graphic page. This LS to CFM Snippet can be used to modify a numeric or text presentation object.

Issue What Niagara R2 UNC license features are shown with BACnet MSTP? Product Line TAC IA Series Environment Niagara R2 UNC BACnet MSTP Cause The Niagara R2 UNC checked in the license.properties file, and if the line BACnetMSTP trunk is absent, the default is 1. Resolution Each UNC-520 is licensed for LonWorks and BACnet IP / BACnet Ethernet as a standard feature. Even though the license defaults with the number of BACnet/MSTP trunks = 1, the user must purchase an IA-DRV-MST-P for each BACnet/MSTP trunk required. The BACnetMSTP feature will be added to the license.

Issue SNVT_press_p will not display correctly in Imperial units on a TGML graphic on a Xenta Server Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 711, 731 Cause There is a bug with the TGML graphic editor that causes a SNVT_press_p to only display in the SI units of pascals. Resolution Until this issue is corrected you can manually convert the value on the graphic page using a JavaScript. This Pascal to H2O Snippet can be used to modify a numeric or text presentation object.

Issue After upgrade of Xbuilder or opening a project built on another computer generating the project causes a "File not found:" error message. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder Cause Find the alarm or event page that is causing this problem and view the reference field to identify the cause of the problem. XBuilder was upgraded and the xmle files from the previous version are no longer present. XBuilder installation directory was on a different drive on the computer the project was last used on. Resolution In Xbuilder, right click on all the Alarm and Event pages, select Change reference, and browse in the new path to the referenced file.

Issue Getting "invalid status error 503" when trying to access a Niagara R2 UNC station remotely Product Line TAC IA Series Environment Remote I/A Series R2 station Cause Issue is due to large number of UNCs on site, and / or high browser traffic. Resolution This is an issue seen from time to time on sites that either have many UNCs present or see lots of browser traffic. Check the system.properties file. There is a line that reads: webServer.threadPoolSize=15 . This is the number of web server threads that can be opened to the UNC station. Each station to station connection takes up one thread, as does a web browser connection. I believe the JDE takes up three threads when it connects to the UNC station. If the UNC station runs out of available threads you will see the "503" error. Change that number to 25 or 30 and reboot the UNC. If the problem persists, then change this line to false: ie.activex.activation=true

Issue Echelon now has an easier way to check the status of your LonMaker License. Determine the status of your credits in seconds. Product Line TAC Vista Environment LonMaker 3.1 LonMaker 3.2 (Turbo) LNS Cause Determine corrupted credits/licensing issues without the old method of using the command prompt. This will do the same thing with a click of a button. Resolution The tool will diagnose the license status and give you the solution you need to follow to fix the problem. Download here: Echelon License Diagnostic Utility Save or run Choose LonMaker credits Copy to clipboard and email to Echelon if corrupted credits are shown. Screen shot of invalid LonMaker license: This error occurs if the license file you specified is not located in the application directory. To resolve this, you will need to reboot your PC and log in as a user with Administrative privilege. Next, make sure the files listed below are located in the C:\Windows\LNS Licenses folder. Note that the "LNS Licenses" folder is a hidden one; therefore, in Windows Explorer, go to Tools - Folder Options..., and in the View tab, select "Show hidden files and folders." Now uncheck the "Hide protected operating system files (Recommended)" option.

Issue 3 State Event Sequence to control certain Access Control Doors Product Line TAC INET Environment I/NET site Cause Three State control requirement Resolution When using the Door Points ("08" & "09") with event sequences, the following actions will occur: A “Start” command is equal to the “Secure Mode” of the door A “Stop” command is equal to the “Unlock Mode” of the door A “Lock Door” command is equal to the “Lock Mode” of the door

Issue How do I properly acknowledge and purge a "Force Door" alarm in AMT. Product Line TAC INET Environment I/NET Access Control Cause The return to normal condition (Door Normal) "Message Type" must have the same "Message Type" as the alarm cause (Forced Door). This is the same condition as for DOTL (Door Open Too Long) alarms. For I/NET to clear both these alarms. the Message Types must match within the Door editor. Resolution You have to properly configure the Door editor before you can properly remove this from AMT. In order to acknowledge and purge a "Force Door" alarm you must have the "Force Door" entry set to "Alarm." The "Door Normal" should also be set to "Alarm."

Issue Can I use the Xenta 527 on an old I/NET 2000 system? Product Line TAC INET Environment I/NET 2000 Cause Adding a Xenta 527 to an I/NET 2000 network. Resolution Yes you can, provided you set the Xenta 527 up to be compatible with I/NET 2000. With the Xenta programming cable (P/N 3-781-0128-0) inserted in port "B" of the Xenta 527, go into Windows Hyper-Terminal and make the following changes for the Xenta 527 to operate in an Inet 2000 program. Please be aware that I/NET 2000 is no longer a supported product and this mode should be used at your own risk.

Issue USB Prox enrollment reader for I/NET Seven Environment I/NET Seven Cause I/NET supports the use on an Enrollment reader via the Hosts PC Serial port, most PC's no longer have serial ports. One solution is to use a USB supported reader which can be sourced by the supplier listed in the resolution Resolution The USB enrollment reader is made by RF Ideas. It is very easy to program for use in the I/NET Seven System. After you program certain steps it becomes a "Plug and Play" device at the job site. To set up this USB reader please consult this whitepaper.

Issue The "Transactions Individual" report in Seven Reports does not sort the transactions by Date and Time. Product Line TAC INET Environment I/NET Seven Seven Reports Cause The "Transactions Individual" report is not sorted by Date and Time Resolution The "Transactions Individual" report is not sorted by Date and Time for a reason. I was determined by TAC, that the customer needs to design the method by which they want this report to be presented. This White Paper will define how to go about setting the Sort process by the Date and Time Option. Start Seven Reports and open the “Transactions Individuals” report Once the report is fully developed on the screen. Choose the “Design” tab In any of the blank white area do a “Right Mouse” Click In the “Popup” window selects the “Report” Option In the next “Popup” window selects the “Sort Records…” Option In the next “Popup” window you need scroll the left window unit you find the “RptEvents.DateTime” Option. Then Select the “Add” button the place the “RptEvent.DateTime” Option in the right window. After you do Step 6 this is what you will see in the right window You need to highlight the “RptEvent.DateTime” function. Then select either “Ascending” or “Descending” sort order. In the “Ascending Mode” the “Oldest Date” is on the top of the list and the most “Recent Date” is at the bottom of the list. In the “Descending Mode” the most “Recent Date” is on the top of the list and the “Oldest Date” is at the bottom of the list. I selected the “Descending” Mode as the way I wanted to sort the Date and Times. You also need to select the “OK” button to finish the setup process. You need to close out of this report. Select “Yes” button to save the changes you made in the “Canned” report. Remember to rename you newly created report to something other than the Original “Canned” report name.

Issue Error message: "Failed to run DcuXml.exe" when importing I/NET .sav files into XBuilder Product Line TAC INET, TAC Vista Environment XBuilder 1.6.0 Cause When XBuilder imports I/NET save files, it does a simple batch of all of the save files for the import process. It creates a path for the import into XBuilder. A typical path might look like this: C:\TAC XBuilder Projects\MyProjectName\Files\INET\dcu0102,dcu0103,dcu0104 This example shows the import of 3 I/NET save files with a character length of 72 for the batch process. This process is limited to 2048 characters. Importing 15-20 save files will cause a crash. Resolution To squeeze a few more save files into XBuilder, shrink that path as much as possible. For example: Rename the default "TAC XBuilder Projects" folder to something shorter. Rename the project to something shorter. Move .sav files to another location, even temporarily to the C:\ drive root to eliminate extra path data. Example: C:\XBPrj\MyPrj\Files\INET\dcu0102.sav. This path shrinks the directory at the front end to allow for more save files on the backend.

Issue Importing I/NET 2000 Graphics into I/NET Seven Product Line TAC INET Environment I/NET Seven Cause Have you upgraded from I/NET 2000 to I/NET Seven and the graphics at the site has either stopped working, don’t come up with the correct back ground or bitmaps and the size is all wrong? Resolution There are a few things that you need to verify after the upgrade. Verify that the path for both symbols and bitmaps that was used in I/Net 2000 is the same for I/NET Seven. If this is not done then the pages when opened in I/Net Seven would come up with a blank background or without a bitmap and or symbols. To find the original path (if unknown): Open the Graphics Editor Select File> Open to edit the graphics page Select View > Page Properties In the Backdrop area (shown below) is the original path of the background bitmap. If you only have a few graphics then you can edit and modify this for each of the graphic pages Alternatively make sure all the bitmaps used are still located in the path defined here. All folders with Bitmaps and Symbols are all the same, even if you have to create a new I/Net 2000 folder on the new PC. If you were using 800 X 600 on the original pages, then you’d have to change the resolution on the new PC to the same. If this is not done, then the pages will show smaller and the points would be distorted.

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 Elements in Sigma Graphics within EBO are not displaying correctly when its bound object commands the element to display or not to display. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause The issue arises on a machine that has a Windows Language Pack e.g. Norwegian Bokmål installed where the decimal separator uses a comma (,) rather than a dot (.). In the example, using the EBO Graphics Editor, it can be seen that the decimal separator in 0,5 is a comma in the 'condition' command, other commands are also effected e.g. Bitmap, Alarm etc; Resolution When a Sigma graphic Data Import is undertaken the decimal separator dot (.) used by the Sigma machine is replaced by a comma (,). On the Sigma server machine using Registry Editor. Registry Edit can be run by typing RegEdit in the Windows search box on the Task Bar. 1. Goto > Computer\HKEY_USERS\S-1-5-18\Control Panel\International\ 2. Locate sDecimal. 3. sDecimal will be set to a comma (,). Change to a dot (.). 4. Re-import the Sigma graphics using the Graphics Data Import in EBO. 5. Select a graphic and edit using the EBO Graphics Editor, select an element and check that a .(dot) is used. Finally, check operation by changing object states on the graphics and the respective element changes state too. Note: This will be auto checked and be incorporated into the Sigma Transition Tool in the future.

Issue Modbus (or other 3rd party communications protocol) not displaying correct value even though coefficients (gain and offset) have been defined Product Line TAC Vista Environment XBuilder Device Template Cause The Xenta 913/731 uses an abnormal equation when applying the coefficient in device templates for 3rd party interfaces: y=m(x+b) Traditionally, the slope-intercept form is used when applying a coefficient: y =mx+b This means that the gain in the coefficient is applied after the offset rather than before it. Resolution If you have the information that fits a traditional slope-intercept form and need to apply a coefficient in a XBuilder device template then use the following as your variables where m and b are from the slope-intercept form equation: Gain: m Offset: b/m The following is an example of one manufacturer's specifications for its Modbus values and how to correctly enter them into the device template: For a temperature sensor reading that is being sent as a Modbus point a certain manufacturer specifies that to correct the raw value the following should be used: Gain = 0.1 Offset = -40 However, the manufacturer assumes the standard slope-intercept form will be used, so entering the data without any adjustments would cause the value to be converted incorrectly in the Xenta Server. For example, if the temperature was 80 °F then the raw Modbus value would be 1200 and the Xenta Server would apply the coefficient as y=0.1(1200+(-40)), simplified as y=120-4. This means the Xenta Server would return a value of 116 °F instead of 80 °F. In order to fix this the offset should be multiplied by the gain in order to compensate for the difference in how the Xenta Server utilizes the coefficient compared to how the 3 rd party manufacturer intended it to be used. So the following would be used: Gain = 0.1 Offset = (-40)*0.1 or -400 Now, with a temperature of 80 °F the raw Modbus value will still be 1200 and the Xenta Server will apply the coefficient as y=0.1(1200+(-400)), simplified as y=120-40. The Xenta Server now returns the correct value of 80 °F.

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 Downloading new NXE or APB files using NL220 Product Line TAC Vista Environment NL220 Cause Downloading new or old firmware versions into application specific controllers. Resolution Before performing this update, make a backup of the NL220 project. In case something happens and the configuration parameters are lost, there will be something to reference. Go to extranet and download the latest NXE and APB files. In NL220, right click on the controller to be upgraded and go to Network > Upload configurations. This will update the database with the current configuration in the controller. Next, right click on the controller again and go to Network > Replace. A box will open that is titled Commissioning a node. The option "Upload configuration from old node if present" should be checked. This will insure that the values in database are current with the controller. Under Configuration download, "Download all known database values" needs to be selected. This will download the configuration parameters back into the controller once the update is complete. Finally under Template, "Download a program to the node" should be checked. The file that was downloaded off of extranet earlier can now be browsed in. Note: The option ‘Keep current configuration on node’ is misleading. By selecting this option it will not download parameters to the node. So when you download the new APB file, the controller will retain the configuration parameters found in the APB file not what was originally on the node. Click Continue

Issue ZBuilder allows for configuration of heating and cooling setpoints as well as PI gain and terminal load deadbands. However, sometimes these parameters can mask the actual activation and deactivation temperature points for heating and cooling outputs. Product Line TAC Vista Environment Xenta 121 ZBuilder Cause Figuring out where a Xenta 121 will turn on stages of heating or cooling can be a bit confusing, especially in °F. If you're not careful, you could have the heat operating until the space temp crosses the cooling setpoint at which point, the unit will switch to cooling and turn on the cooling stage(s). Resolution Click here to open a spreadsheet that will calculate the proportional bands and the activation points of the heating and cooling stages. Select the tab that describes the cooling/heating application set in ZBuilder Enter the temperature setpoints, gain and hysteresis settings and the value of nviSetpoint if it is being used. Ensure that cooling/heating bands are not inverted or overlapping to ensure proper operation of the Xenta 121.

Issue TGML Graphic does not display. Shows only a red X Xenta Server TGML Graphics not updating following XBuilder download Miscellaneous Java error messages Product Line TAC Vista Environment Xenta 511, 527, 711, 731 TGML graphics XBuilder Cause Dynamic TGML graphics are rendered in the web browser using a Java applet. Java on the PC will store applets and graphics in its cache for faster load times. This can sometimes be problematic as changes are being made -- either to the graphic source files or the firmware version of the Xenta Server. Resolution Clear the Java cache before loading the page again: Open the Java Control Panel If viewing a Java page, the icon for the control panel will be in the task bar of the PC. Double click it. Otherwise, go to Start > Control Panel > Java. On the first tab, General, see the third box item, Temporary Internet Files. Click Settings... Click Delete Files... Select both "Applications and Applets" and "Trace and Log Files". Click OK, and exit the Java Control Panel Reload the graphic.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Replacement for Drayton A703 Immersion Temperature Sensor by S-E STP600D

Configuring LON tunneling in Niagara G3

SNVT_flow will not display correctly in Imperial units on a TGML graphic on a Xenta Server

What Niagara R2 UNC license features are shown with BACnet MSTP?

SNVT_press_p will not display correctly in Imperial units on a TGML graphic on a Xenta Server

After upgrading the XBuilder program, you may get "File not found" error message when generating the project.

Getting "invalid status error 503" when trying to access a Niagara R2 UNC station remotely

Use Echelon License Diagnostic Utility to check the status of LonMaker credits

3 State Event Sequence to control certain Access Control Doors

Acknowledge and purge a "Force Door" alarm in AMT

Use a Xenta 527 on an old I/NET 2000 system

USB Prox enrollment reader for I/NET Seven

The "Transactions Individual" report in Seven Reports does not sort the transactions by Date and Time.

Error message: "Failed to run DcuXml.exe" when importing I/NET .sav files into XBuilder

Importing I/NET 2000 Graphics into I/NET Seven

Imported Sigma Graphics not working after transition into EBO

Defining Coefficients (Gain and Offset) in XBuilder Device Templates

Downloading new NXE or APB files using NL220

Calculating heating and cooling operations on a Xenta 121

Xenta Server TGML Graphic issues resolved by clearing the PC's Java Cache

Building Automation Knowledge Base

Related Forums

Welcome!