Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

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…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
Options
  • My Knowledge Base Contributions
  • Subscribe
  • Bookmark
  • Invite a Friend
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.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • Andover Continuum 2,208
  • TAC Vista 2,045
  • EcoStruxure Building Operation 1,854
  • TAC IA Series 1,826
  • TAC INET 1,459
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 334
  • Satchwell MicroNet 252
  • EcoStruxure Building Expert 228
  • EcoStruxure Access Expert 150
  • CCTV 53
  • Project Configuration Tool 47
  • EcoStruxure Building Activate 17
  • EcoStruxure Building Advisor 12
  • ESMI Fire Detection 12
  • Automated Engineering Tool 5
  • EcoStruxure Building Data Platform 3
  • EcoStruxure Workplace Advisor 1
  • EcoStruxure for Retail - IMP 1
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • Cody_Failinger
    Cody_Failinger
See More Contributors
Related Products
Thumbnail of EcoStruxure™ Building Operation
Schneider Electric
EcoStruxure™ Building Operation
4
Thumbnail of SmartX IP Controllers
Schneider Electric
SmartX IP Controllers
1
Thumbnail of EcoStruxure™ Building Advisor
Schneider Electric
EcoStruxure™ Building Advisor
1

Related Forums

  • Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

Building Automation Knowledge Base

Sort by:
Date
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • …
    • 225
    • 226
    • 227
    • …
    • 509
  • Next »

Trace a connection in a WorkPlace Tech drawing when it is difficult to see the wire path

Issue How can a connection be traced in a WorkPlace Tech drawing when it is difficult to see the wire path? Product Line TAC IA Series Environment WorkPlace Tech Cause When working with objects that have numerous connection wires (perhaps an uploaded drawing), it may be difficult to see the wire routing path. The link style is too small, which may be difficult to see the wire routing path. Resolution Click on a wire to select it (green handles appear). Two clicks may be required, since the first click selects the object that the wire is from. Right click on the wire and select Format/Style. In the Line Style pull-down menu, select "Error Box" (a heavy red wire). Click OK Trace and edit the connections as needed.
View full article
Picard Product_Support
‎2018-09-07 04:44 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-03 01:07 PM

Labels:
  • TAC IA Series
997 Views

A method to export Access Events to file to then be imported into a third party system.

Issue Need to export Access Events automatically to a file format that a third party system can then import. This needs to be triggered at a set interval such as once a day. Product Line Andover Continuum Environment Continuum Access Control Cause Events can be exported from Continuum using a Listview of AccessEvents and then exporting to .CSV format file but this needs to be set up and manually run by the user. There does not appear to be an automatic method to get the same results from a listview into a file format. Resolution There is a method that can be used to export AccessEvent data to an external file without user intervention. The file format will be in HTML or XML format. A file format of XML is the obvious choice as it is usually easier for third party systems to import from an XML format. To do this, you will need to: Create a Report object with a Datasource set to "AccessEvents" or "Listview". These would then be configured with the AccessEvent attributes that you want to export. Once the desired Report is created, configure it so that it is run automatically using Windows Scheduled Events and the ReportCmdLine.exe application that is available for this purpose. See the article here for detailed steps on how to set this up.
View full article
Picard Product_Support
‎2020-11-03 10:17 AM

on ‎2020-11-03 10:17 AM

Labels:
  • Andover Continuum
1963 Views

Extending the range of the RTD-DI-16 temperature inputs

Issue RTD-DI-16 temperature input range is -50C to 150C, some applications require a wider range. Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation I/O Module 16 Ch RTD Cause Script program sample and guidelines needed for implementing resistance to temperature table lookup and further temperature calculation using linear interpolation. Resolution We will present two solutions, the first solution is very simple to implement but at the expense of accuracy. The second solution retains the 0.3C accuracy of the native RTD inputs. For simplicity, both solutions implement a range of -50C to 250C using the RTD Resistance electrical type to convert resistance to temperature, the program can be easily modified to implement a wider range.     SOLUTION #1 This solution simply uses the conversion settings of the RTD-Resistive input to convert from Ohms to Degrees C. Because the change in resistance is not exactly linear across the temperature range, the accuracy of the converted value varies across the range as much as +/- 4 degrees C      STEPS TO IMPLEMENT SOLUTION #1 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Change the units to degrees Celsius. Select the sensor class, in this example, we are using the pt100 sensor. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) Use values from step #4 to set the input's conversion electrical scale.  Set the engineering scale top/bottom to 250 and -50 respectively.    STEPS TO IMPLEMENT SOLUTION #2 Under the RTD-DI-16 IO module, create RTD-2W-Resistive input. Look up the resistance value in the table for -50C and  250C and set the upper/low-level reliability. (see attached R versus T table from Omega) In the Automation Server, create an Analog Value object. This object will receive the calculated temperature value from the Script program. Set the AV units to degrees C In the Automation Server create a Script program, this program will read the resistance from the input object, look up the corresponding temperature range in the table, and then using linear interpolation calculates the temperature to an accuracy of +/- 0.3C. To ensure the program when runs when necessary, configure the program's flow type for fall thru and trigger the program off of the RTD-2W-Resistive input. Bind the RTD-2W-Resistive input and the Analog Value in the Script program as Numeric Input and Numeric Output respectively.  Here is the code for the script program   'This program uses RTD temperature vs. resistance table combined with linear interpolation 'to implement RTD temperature input over the range -50C to 250C 'Program Flow Type is FallThru 'Program is triggered by the RTD resistance input. 'This program is provided as a sample for illustration purposes, it is not intended to be a complete solution 'SE PSS v1.0 101010111110 Numeric Input RTD_Raw 'the RTD Resistance input where the RTD sensor is connected Numeric Output RTD_Temp 'Analog Value that receives the calculated temperature Numeric RTD_R[31]'Resistance to Numeric RTD_T[31]'temperature table for 100 Ohms based sensor 'NOTE: Since the resistance value changes in a nearly linear way over any 10 degree section 'of the table, we can use 10 degree increments of resistance/temperature values and apply linear 'interpolation to calculate readings in between those values, this method greatly reduces the size 'of the table in the program while maintaining very good accuracy. 'Accuracy is +/-0.3C for 100 Ohms based sensors and can be improved to +/-0.03C if 1000 Ohms based sensor used. Numeric n, sLow, sHigh,sMid Line INIT 'Due to limitations in Script we will use 2 arrays to implement the resistance to temperature table. RTD_R[1]=80.31 RTD_R[2]=84.27 RTD_R[3]=88.22 RTD_R[4]=92.16 RTD_R[5]=96.09 RTD_R[6]=100 RTD_R[7]=103.9 RTD_R[8]=107.79 RTD_R[9]=111.67 RTD_R[10]=115.54 RTD_R[11]=119.4 RTD_R[12]=123.24 RTD_R[13]=127.08 RTD_R[14]=130.9 RTD_R[15]=134.71 RTD_R[16]=138.51 RTD_R[17]=142.29 RTD_R[18]=146.07 RTD_R[19]=149.83 RTD_R[20]=153.58 RTD_R[21]=157.33 RTD_R[22]=161.05 RTD_R[23]=164.77 RTD_R[24]=168.48 RTD_R[25]=172.17 RTD_R[26]=175.86 RTD_R[27]=179.53 RTD_R[28]=183.19 RTD_R[29]=186.84 RTD_R[30]=190.47 RTD_R[31]=194.1 'The temperature array could be easily omitted since once we have the first array index (n) we could easily calculate 'the corresponding temperature value, I have kept it for the purpose of simplicity. RTD_T[1]=-50 RTD_T[2]=-40 RTD_T[3]=-30 RTD_T[4]=-20 RTD_T[5]=-10 RTD_T[6]=0 RTD_T[7]=10 RTD_T[8]=20 RTD_T[9]=30 RTD_T[10]=40 RTD_T[11]=50 RTD_T[12]=60 RTD_T[13]=70 RTD_T[14]=80 RTD_T[15]=90 RTD_T[16]=100 RTD_T[17]=110 RTD_T[18]=120 RTD_T[19]=130 RTD_T[20]=140 RTD_T[21]=150 RTD_T[22]=160 RTD_T[23]=170 RTD_T[24]=180 RTD_T[25]=190 RTD_T[26]=200 RTD_T[27]=210 RTD_T[28]=220 RTD_T[29]=230 RTD_T[30]=240 RTD_T[31]=250 n=0 sLow = 1 sHigh = MaxItem(RTD_R) 'Initialize to the size of the table Line calculateTemp 'Bottom of range If RTD_Raw <= RTD_R[1] then RTD_Temp = -50.0 Stop Endif 'Top of range If RTD_Raw >= RTD_R[sHigh] then RTD_Temp = 250.0 Stop Endif 'Find the resistance input reading in the table using a binary search 'NOTE: 'In our case, what we are looking for is the lower value of the resistance range in the table that 'the input reading falls under. 'EXAMPLE if input value is 160.9 Ohms then it is in the range of RTD_R[21]=157.33 AND RTD_R[22]=161.05 'so the binary search will give us 21 While(1) If sHigh < sLow then n=sHigh 'the input value is not in the table but we now have RTD_R[n] of the range it is within break Endif 'calculate the mid point sMid = Round(sLow + (sHigh - sLow) / 2) if RTD_R[sMid] < RTD_Raw then sLow = sMid + 1 'if read value is larger then look again in upper half if RTD_R[sMid] > RTD_Raw then sHigh = sMid - 1 'if read value is smaller then look again in lower half if RTD_R[sMid] = RTD_Raw then n = sMid 'we've located the input value in the table, this is actually the exception Break endIf EndWhile 'Now, use linear interpolation to calculate the temperature If n > 0 Then RTD_Temp = (RTD_T[n+1]-RTD_T[n])*(RTD_Raw-RTD_R[n])/(RTD_R[n+1]-RTD_R[n])+RTD_T[n] Endif Stop Line E stop   NOTE: The accuracy of the temperature reading can be further improved by the use of 1000 Ohms based sensors as well as the use of 3 wire sensors so that the resistance of the leading wires can be taken into account. If 1000 Ohms based sensors are used then the resistance values in the table implemented in the Script program must be multiplied by 10
View full article
Captain AbeMeran Captain
‎2020-11-03 09:34 AM

on ‎2020-11-03 09:34 AM

Labels:
  • EcoStruxure Building Operation
3263 Views

ADI FSCO Panel Integration

Issue ADI FSCO Panel Integration Product Line TAC Vista Environment ADI FSCO Panel Xenta 913 Cause Integration to an ADI Fire/Smoke Control Panel. Resolution This document details the process for integrating an ADI FSCO Panel (www.adipanel.com) with a TAC Xenta 913 through the ModBus serial interface. Comm Settings In XBuilder, right click the "RS232-485 A" Serial Port, add a ModBus Slave interface. The comm settings necessary are shown below:   The ADI FSCO Panels speak RS232. The 913's baud rate is adjustable in XBuilder from 300 to 19200. The panel's baud rate is adjustable via DIP switches from 2400 to 19200. There is no right or wrong speed, they just need to match. Parity is even, 7 data bits, 1 stop bit, and ASCII framing mode. On the ModBus serial line slave, right click and add a device. If it has not been created yet, you will need to create a device template first. The device requires a ModBus address. With an ADI FSCO Panel, this address is always 1. Physical Connections The RS232 port is an RJ45 port on the left front of the 913 labeled “A.” If you are creating your own patch cable to tie into the ADI FSCO Panel, the pin-out is as follows:   1 - White Orange 2 - Orange 3 - White Green – TXD 4 - Blue – RXD 5 - White Blue – GROUND 6 - Green 7 - White Brown 8 - Brown     TXD ties to the ADI FSCO Panel on the terminal block labeled "IN." RXD ties to "OUT" and GROUND ties to "GND." Signal Connections When populating connection objects between an ADI FSCO Panel and a Vista database, the best option is to use a Multi-Connection Object. Right click on the root folder in the System pane of XBuilder and select New > Object > Multi-Connection Object. The Multi-Connection Object can be populated by dragging and dropping points from the ADI Device Template and Menta. The Send Option in the Connection Manager lets you select either Periodically, Write on change, or Write initially and on change. Choose to write initially and on change. Each point also has a designated Period. Just because a point is not set to update periodically does not mean the period ceases to have any effect. If too many points are on the same period, it can overwhelm the 913. So regardless of the Send Option, the Period (s) should be staggered. Set the first 20 points to 10 seconds, the next 20 points to 11 seconds (for example – in reality, just avoid having hundreds of points at the same period.) When finished populating all data fields of the Connection Manager, hit the Validate button on the bottom left corner and make sure there are no errors. Menta Programming Menta files that accept data from an ADI FSCO Panel do so through PVBs and PVRs. These come default with the "Backup" option selected. This is used to store the value in non-volatile memory on power loss. When using a PVR for a setpoint, this is a good thing. However, when something is constantly writing a value to this public variable, and it in turn is constantly writing values to flash memory, it can cause the controller to lock up and stop working. You must de-select the "Backup" option from any PVBs or PVRs in a Menta file that are accepting data from a connection object in a 913. Disclaimer This document is intended to address some of the most common (and most commonly overlooked) settings when integrating with an ADI FSCO Panel through a serial ModBus connection. Contact ADI for product information and to ensure that the correct FSCO Panel is ordered to facilitate this type of integration. No guarantee can be made that changes to the physical configuration, communication settings, or software format have not been made, so always check with your ADI sales representative first.
View full article
Picard Product_Support
‎2018-09-07 02:10 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-03 06:28 AM

Labels:
  • TAC Vista
1616 Views

Adjust the size of the wire sheet in Niagara G3 Workbench

Issue In Niagara G3 Workbench, how can the size of the wire sheet be adjusted? Product Line TAC IA Series Environment Niagara G3 Workbench Cause Locating the settings to configure the Wire Sheet width and height to increase or decrease the view. Resolution Wire Sheet maximum size limits Starting in NiagaraAX-3.6, you can limit the size of the wire sheet by setting size of the wire sheet in the Options dialog box. From the workbench main menu, select Tools > Options to open the dialog box. Then select the Wire Sheet option and enter a desired maximum value in the Max Width and Max Height fields, as shown, below. Click the OK button to complete the setting change. If you decrease the maximum wire sheet size, objects are repositioned to stay within the view, after the size change. Note: You may need to refresh the wire sheet view to see the changes in wire sheet size and object repositioning. Also, the wire sheet borders may not be visible until you zoom out in the wire sheet view.  
View full article
Picard Product_Support
‎2018-09-07 02:12 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-03 06:26 AM

Labels:
  • TAC IA Series
1462 Views

WorkPlace Tech monitor tags disappear in an open application with no error message

Issue In WorkPlace Tech, monitor tags can not be placed into the open application. They disappear and there is no error message. Product Line TAC IA Series Environment WorkPlace Tech Cause A layer being turned off in error and need to configure the layer setting to Visible. Resolution Below are steps to resolve the issue: Close WorkPlace Tech. Using Windows Explorer locate the VSD file, right click it, and clear the read-only and archive flags.   Open the drawing in Visio. Select "Customize" from the "Tools" drop-down menu. Highlight "Menu Bar" on the Toolbars tab of the Customize window and pick "Reset". Close the Customize window. Select "Drawing Explorer Window" from the "View" dropdown.   Expand Foreground Pages - Device Definition - Layers. Right-click RealTimes and enable Visible.   Close the "Drawing Explorer Window". Save and close the file. Insert monitor tags will now work.
View full article
Picard Product_Support
‎2018-09-07 02:12 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-03 06:25 AM

Labels:
  • TAC IA Series
1188 Views

Migrate from custom installed Microsoft SQL Server 2000 to custom installed Microsoft SQL Server 2005

Issue Migrate from custom installed Microsoft SQL Server 2000 to custom installed Microsoft SQL Server 2005 Product Line TAC Vista Environment Microsoft SQL Server 2000 Microsoft SQL Server 2005 Cause When you upgrade from Vista 4.3.0 - 4.5.0 to Vista 5.x you can continue to use the SQL Server 2000, but as the security and performance is better in SQL Server 2005, you would want to upgrade. There are some things that are important before you upgrade. You should of course take a backup, but there are also some other things you should have in mind. If you want to have the same instance name on the SQL Server 2005 as you have on the SQL Server 2000, you must have two different PCs. The SQL Server 2000 should be SP4 The SQL Server 2005 should be SP2 The SQL Server 2005 should be minimum “Standard” version Resolution Always remember to update from TAC Vista 4.5.0 to TAC Vista 5. This means that you have to update to TAC Vista 4.5.0 if you are currently running eg. TAC Vista 4.4.1. Procedure Upgrade TAC Vista to 5.x, and have it connect to the existing database on SQL Server 2000. Check the existing SQL setup in TAC Vista Server Setup. Uninstall TAC Vista 4.5.0. Restart the PC. Install TAC Vista 5. In the installation procedure, type in the SQL credentials you checked earlier. Stop TAC Vista Server and DSS Writer. To view installed services go to Start > Run > services.msc. If TACOS is running as a service, stop it in the services and set it to disabled. Stop the “TAC DSS Writer service” and set it to disabled. Assure that the SQL Server Agent is started on both the SQL Server 2000 and the SQL Server 2005. This can be checked in Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager. Start the “SQL Server Management” on the PC where SQL Server 2005 is installed. This is the management tool that comes with SQL Server 2005 Connect to both the SQL Server 2000 and SQL Server 2005. The connect button is located in the upper left corner. Login using either windows or SQL authentication. Right click the Vista log database on the SQL Server 2000, select all tasks and copy. Follow the instructions in the wizard, and copy the database to the SQL 2005 Server (VERY slow process). Configure TAC Vista to connect to the copied database on the SQL Server 2005 Go to the SQL setup in TAC Vista Server Setup and have it connect to the DB on the SQL 2005 Server in stead of the SQL 2000 Server. Start the DSS Writer Go to Start > Run > services.msc Set the “TAC DSS Writer service” to automatic and start it. Start TAC Vista If TACOS is installed as a service, set it to automatic and start it. Otherwise, just start the TACOS application.
View full article
Picard Product_Support
‎2018-09-07 02:30 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-03 06:22 AM

Labels:
  • TAC Vista
1423 Views

Using the 913 as a NPR in I/NET

Issue Can the Xenta 913 be used as a NPR in I/NET? Will the Xenta 913 transfer (via Connection Objects) from one I/NET link to another? Product Line TAC INET Environment I/NET Seven Xenta 913 Cause Although the Xenta 913 appears in the I/NET network configuration and parameters appears the same as a NPR not all functions are possible.  Refer to the resolution to below for supported communications: Resolution Even though the 913 has some basic NPR functionality to I/NET it does not function 100% as a NPR like the 527 or 731 does. The 913 will not pass any AMT information to a host, nor will it pass global indirect points from link to link. It is recommended to only use the 527 or 731 as an NPR to an I/NET system.   Click the picture above to open this image in PDF format. It should also be noted that provided the Xenta 913 is connected on the TCPIP network it is possible to create connection objects across I/NET links.  The Xenta must be part of the I/NET network, that is add the reference host to the Xenta 913 configuration then all links will be available to the device.
View full article
Picard Product_Support
‎2018-09-07 02:17 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-03 06:20 AM

Labels:
  • TAC INET
1256 Views

How to reset the Mobile Application account password

Issue Mobile Application account login is not working or the password has been lost. Product Line Security Expert Environment Security Expert Mobile Application (SX-MOB-IF) Cause Login is not working or the account password has been lost. Resolution The Mobile Application account password must be reset by the account holder. The only way this can be done is through the online form which sends an email with a reset link URL. On the login page of the Security Expert Mobile Application, select the Forgot your password link at the bottom of the page. Then type in the email address of your account and press the Send Reset Link button. An email will be delivered with a URL where the accounts password can be changed. Mobile App Password Reset   This process is by design, Mobile Application accounts are not able to be reset from the backend or deleted. You must be able to receive these emails to be able to manage the Mobile Application account. Check spam filters if the emails are being blocked. If a password reset email is not being received then a new account will need to be created using a different email address.
View full article
Guinan AdamSteele Guinan
‎2020-11-02 10:18 PM

on ‎2020-11-02 10:18 PM

Labels:
  • EcoStruxure Security Expert
1268 Views

Error 28001 - sa password complexity error when installing TAC Vista 5

Issue Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) Windows Event log reveals the following error:   Product: Microsoft SQL Server 2005 Express Edition -- Error 28001. The sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online. Product Line TAC Vista Environment Vista Server Microsoft SQL Server 2005 Express Edition Windows Server 2003 Cause When installing TAC Vista 5 on a 2003 Server you can get an error if the group policy require a certain complexity on the sa password. Resolution One possibility is to edit the group policy Go to Start > Run and type gpedit.msc In the Local Group Policy Editor, navigate to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Account Policies > Password Policy Set Password must meet complexity requirements to Disabled.     The other option is to install the SQL 2005 Express SP3 yourself. It is downloadable from Microsoft. Remove the checkmark in "Hide Advanced Configuration" Set the instance to TACVISTA. Use the "custom" option in TAC Vista Server setup, and select the local SQL server.
View full article
Picard Product_Support
‎2018-09-07 02:09 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 08:48 AM

Labels:
  • TAC Vista
2173 Views

I/NET SubLAN communication best practices

Issue How do the 7793 and 7798 handle retries?  Improving I/NET sublan communications Excessive MCU Lost messages in AMT Command Error messages in AMT Product Line TAC INET Environment I/NET sublan 7793, 7798 Cause If there are issues on the physical layer of the network, this will effect the reliability of I/NET communications. However, these risks can be lessened with some best practices. Resolution Best Practices and Troubleshooting measures to improve sublan communications: Ground the 24V line coming into MRs and ASCs Connect ground to the earth ground terminal of DPUs and SCUs. Bond the shield of the LAN cable all the way through the network, not landing it on any controller anywhere and then tie it to earth ground in one location. (see diagram)   SubLAN Communication Explained: The first packet to any sublan device goes out on the primary channel, terminals 1 and 2 of the sublan connector on the 93/98. If the device doesn't respond in time, a second packet is sent out on the alternate channel, terminals 4 and 5. If there is still no reply, a third packet goes out on the primary Finally, if there is still no reply, that device is marked as lost which generates an "MCU Lost" message. Optional Configuration for only using Terminals 1 and 2:  If you are using only Terminals 1 and 2 you could be missing 33% of it's retry capacity. If you follow wiring guides and best practices the device will answer on the first packet every time, however if you have not followed the guide all it takes is a little noise to make the retries necessary. If you are unable to use a loop configuration, or want to avoid the extra potential for noise and EMI, in stall a jumper on the sublan connector from terminal 1 to 4 and from terminal 2 to 5 The allows you to get the extra retry, without the extra cable This will also function if you have some controllers on channel A and some on Channel B The SLI doesn’t have to be at the end of line on sublan communication  
View full article
Picard Product_Support
‎2018-09-07 02:41 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 06:33 AM

Labels:
  • TAC INET
1796 Views

Sunrise/Sunset does not function correctly in I/NET Seven rev 2.16

Issue Sunrise/Sunset does function correctly in I/NET Seven rev 2.16 Sunrise/Sunset workaround in I/NET Seven 2.16 Product Line TAC INET Environment I/NET Seven rev 2.16 Cause Currently there are some issues with Sunrise and Sunset working correctly in I/NET Seven rev 2.16. The follow steps are given as a work around to solve these issues. Resolution There are two different ways to make this work correctly: Add some starts between the Sunrise and Sunset. It is important that these starts do not have any days of the week defined.   Use a Cycle between the Sunrise and Sunset. It is important that this Cycle does not have any days of the week defined.  
View full article
Picard Product_Support
‎2018-09-07 02:01 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 06:31 AM

Labels:
  • TAC INET
1488 Views

%D and %N on the FeedBack tab of an AlarmEnrollment is not filling in Name or Description of point

Issue Using the %D and %N on the FeedBack tab of an AlarmEnrollment and it is not filling in the Name or Description of a point. Product Line Andover Continuum Environment Continuum Cyberstation Alarm View Cause Enhanced Alarm Logging has not been enabled. Resolution Make sure that you have selected Enhanced Alarm Logging on the Database Initialization screen. This is a requirement to use %D and %N in AlarmEnrollments.  
View full article
Picard Product_Support
‎2018-09-07 02:00 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 06:29 AM

Labels:
  • Andover Continuum
1240 Views

Database size is growing rapidly, SQL Database Recovery Modes Explained

Issue LDF file of a database is growing rapidly. SQL Database Recovery Modes Explained Product Line Andover Continuum Environment Continuum  SQL Server Cause Recovery Mode setting could allow all transactions to be logged. Resolution The Full Recovery Mode basically logs all transactions successfully, failed, table creations, columns created etc... When the Continuum database is created, there are no additional tables added or columns added unless there is an update to the database to a different version. Some sites will require Full Recovery Mode but for most sites, we only need to know when an error occurs when updating or altering rows occurs and Simple Recovery Mode will log those. The Continuum Databases are created with Simple Recovery Mode. It is up to the individual site whether they need Full Recovery Mode. Most sites run with the default Simple Recovery Mode since there is no need to log every successful transaction but only want to catch the transactions that have an error. The Recovery Mode is especially important if your site is a single-user setup. Single user databases are limited in size and if you fill-up the .LDF log file, you can exceed Microsoft's database limitations in a short period of time. As for Enterprise versions of SQL for Continuum Lan systems, you'll need to watch your available disk space. Check what the Recovery Mode is set to by using SQL Server Management Studio Express, right-click your ContinuumDB and select properties, go to the Options tab, and check the Recovery model. See the image below for details.   Furthermore, if you have selected Full Recovery Mode in the past and now have a large unwanted .Ldf file that is causing you issues, then selecting Simple Recovery Mode at this point will also truncate your original Log file down to a more usable size retrospectively.  (Although it may take a few hours before you see any changes).
View full article
Picard Product_Support
‎2018-09-07 01:59 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 06:27 AM

Labels:
  • Andover Continuum
1941 Views

Unable to open Trend Log automatic activation start time calendar

Issue When creating a trend log in TAC XBuilder it is possible to choose automatic activation. If the automatic option is chosen you can browse in a start time for the trend log using a calendar. It is not possible to open this calendar. Product Line TAC Vista Environment XBuilder Trend Logs Cause TAC XBuilder is using Microsoft's ActiveX Calendar Control file (mscal.ocx) this is normally installed when you install Microsoft Office Professional (i.e. a version including Access) or when you install Microsoft Access. If mscal.ocx is not installed on the computer it is not possible to open the calendar. Resolution The file mscal.ocx should be in the folder \\windows\system or \\windows\system32.  If not, please follow the steps below to install the mscal.ocx file. Click here to download the file. Store the file at \\windows\system or \\windows\system32 go to Start->Run and type cmd to open the command window type "regsvr32.exe mscal.ocx" Now the calendar should be able to edit in Xbuilder.
View full article
Picard Product_Support
‎2018-09-07 02:02 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 06:26 AM

Labels:
  • TAC Vista
1081 Views

"Error HRESULT E_FAIL has been returned from a call to a COM component" when saving a TGML graphic

Issue Unable to save a TGML graphic in a Vista database. Save error Error HRESULT E_FAIL has been returned from a call to a COM component. Product Line TAC Vista Environment Vista 5 Workstation TGML Graphic Editor Cause This message occurs when saving a graphic to a folder that has a "/" in the name. Resolution Change the name of the folder to not include a "/"
View full article
Picard Product_Support
‎2018-09-07 02:02 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 06:24 AM

Labels:
  • TAC Vista
1507 Views

Determine the current year in a Menta file

Issue Determine the current year in a Menta file. Product Line TAC Vista Environment Menta Cause Menta has built in Simple Blocks for weekday, date, month, minute and second, but does not have a "YEAR" block to tell the program the current year. Resolution Please use the attached Menta macro block. This code will take the current year and transition to the next year at midnight on December 31st. ***Please note*** The SHR block named "Year" has to have the current year put in it before downloading this code. YEAR_CALC.MTA  
View full article
Picard Product_Support
‎2018-09-07 02:01 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-02 06:23 AM

Labels:
  • TAC Vista
1301 Views

Error 'Failed to connect to server' reported from Data Import in Sigma Interface

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 When Data Import is used in the Sigma Interface, the Data Importer fails to connect with the Sigma server. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Building Operation Workstation Sigma Cause Sigma requires the correct release of Sigma software to be installed as well as the Sigma Transition Tool. Installing the Sigma Transition Tool onto a Sigma server machine can mask the true version of Sigma server and client installed. Resolution The release of Sigma client and server that is to be transitioned into EBO should be Sigma 4.08 (build 3.46.nnn) before the Sigma Transition Tool is installed. However installing the Sigma Transition Tool will overwrite the Sigma version in the Sigma application and in the Sigma splash window when launched.   To check the true version: 1. Go to Windows Explorer and locate the directory c:\sigma\bin. 2. Identify SigOp.exe (or other files) and hover over or right click and open 'Properties' and the tab 'Details',  3. The version number should be at least 3.46.57     If the version identified is below e.g. 3.45.nnn, then Sigma needs to be upgraded to the correct release. The Sigma Transition Tool will need to be uninstalled first, the Sigma upgraded and the Transition Tool reinstalled.   When complete, rerun the Sigma Data Import in EBO.   Note: Remote Sigma clients that are connected to the Sigma server will also need to be upgraded.
View full article
Sisko DavidChild Sisko
‎2020-11-02 01:11 AM

on ‎2020-11-02 01:11 AM

Labels:
  • EcoStruxure Building Operation
  • Satchwell BAS & Sigma
1193 Views

How to identify a WorkPlace Tech application as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x

Issue How can a WorkPlace Tech application be identified as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x? Product Line TAC IA Series Environment WorkPlace Tech Cause Jobsite with an installed base of MNL or MNB controllers but the version of WorkPlace Tech used is not known. Resolution NOTE: Do not allow the application to be converted, if so prompted. Open the application file in an appropriate version of Visio. (WorkPlace Tech not needed). While holding down the left-shift key, right click on the background of the application and select "Show ShapeSheet", holding the left-shift key down until the ShapeSheet window is displayed. Verify that the text table window that is opened shows the file name followed by "". If not, close the shapesheet window and repeat step 2. The left-shift key must be held down until the ShapeSheet table is displayed. Look for the "User-defined Cells" table in the displayed information and verify that an entry named "User.wptVersion" is shown. This field will show the version of WorkPlace Tech that created the application. If either the "User-defined Cells" section or the "User.wptVersion" field are not displayed in the shape sheet, the application was created / edited with a version of Workplace Tech prior to version 3.2sp1. Close Visio. Respond by clicking NO if Visio prompts to save the document. In Visio 2010, the ShapeSheet is located on the Developer tab, which is not displayed by default. To show the Developer tab, do the following: Click the File tab. Under Help, click Options. Click Customize Ribbon. Under Customize the Ribbon, select the Developer check box. To open the ShapeSheet, do the following: On the Developer tab, in the Shape Design group, click the arrow below Show ShapeSheet and then do one of the following: To open the ShapeSheet for a selected shape, click Shape. To open the ShapeSheet for the active page, click Page. To open the ShapeSheet for the entire drawing, click Document.  
View full article
Picard Product_Support
‎2018-09-07 01:57 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-30 10:56 AM

Labels:
  • TAC IA Series
1198 Views

Get log information out of a Niagara R2 Enterprise Server station and into Excel

Issue Is there an easier way to get log information out of a Niagara R2 Enterprise Server station other than by using a web browser, saving the data, and importing it to Excel? Product Line TAC IA Series Environment I/A Series R2 (Niagara) station with logs. Cause Tech tip. Resolution There is no easier way to get log information than to use a web browser, save the data, and import to Excel. However, by default, a query to the archived log limits the number of records to 2500. This limit can be changed by adding $limit=xxxx.  Note:  Attempting to query a large number of records (> 7500) may cause the process to fail due to timeouts. A review of the cloudscape2excel document provides some details.
View full article
Picard Product_Support
‎2018-09-07 03:09 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-30 10:52 AM

Labels:
  • TAC IA Series
1693 Views
  • « Previous
    • 1
    • …
    • 225
    • 226
    • 227
    • …
    • 509
  • Next »
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

Welcome!

Welcome to your new personalized space.

of