Sign In Help
Schneider Electric
HelpSign In
Schneider Electric Exchange
  • Home
  • Collaborate
  • Develop
  • Shop
Home Collaborate Develop Shop Log in or Register Help

Invite a Co-worker

Send a co-worker an invite to the Exchange 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
  • Home
  • Collaborate
  • Exchange Community
  • :
  • Knowledge Center
  • :
  • Building Automation Knowledge Base
Community Menu
  • Forums
    • By Topic
        • EcoStruxure IT
          • EcoStruxure IT forum
        • Industrial Automation
          • Industry Automation and Control Forum
          • Alliance System Integrators Forum
          • Machine Solutions in the Digital Transformation
          • EcoStruxure Automation Expert / IEC 61499 Forum
          • Industrial Edge Computing Forum
          • Level and Pressure Instrumentation Forum
          • Modicon User Group
          • PLC Club Indonesia
          • SEE Automation Club Forum
          • Fabrika ve Makina Otomasyonu Çözümleri
          • Форум по промышленной автоматизации СНГ
        • SCADA & Telemetry Solutions
          • Geo SCADA Expert Forum
          • SCADA and Telemetry Devices Forum
        • Power Distribution IEC
          • Power Distribution and Digital
          • Power Standards & Regulations
          • Paneelbouw & Energie Distributie
        • Power Distribution Softwares
          • EcoStruxure Power Design Forum
          • SEE Electrical Building+ Forum
          • LayoutFAST User Group Forum
        • Solutions for your Business
          • Solutions for Food & Beverage Forum
          • Solutions for Healthcare Forum
    • By Segment
        • Food & Beverage
          • Solutions for Food & Beverage Forum
        • Healthcare
          • Solutions for Healthcare Forum
      • EcoStruxure IT
        • EcoStruxure IT forum
      • Industrial Automation
        • Industry Automation and Control Forum
        • Alliance System Integrators Forum
        • Machine Solutions in the Digital Transformation
        • EcoStruxure Automation Expert / IEC 61499 Forum
        • Industrial Edge Computing Forum
        • Level and Pressure Instrumentation Forum
        • Modicon User Group
        • PLC Club Indonesia
        • SEE Automation Club Forum
        • Fabrika ve Makina Otomasyonu Çözümleri
        • Форум по промышленной автоматизации СНГ
      • SCADA & Telemetry Solutions
        • Geo SCADA Expert Forum
        • SCADA and Telemetry Devices Forum
      • Power Distribution IEC
        • Power Distribution and Digital
        • Power Standards & Regulations
        • Paneelbouw & Energie Distributie
      • Power Distribution Softwares
        • EcoStruxure Power Design Forum
        • SEE Electrical Building+ Forum
        • LayoutFAST User Group Forum
      • Solutions for your Business
        • Solutions for Food & Beverage Forum
        • Solutions for Healthcare Forum
      • Food & Beverage
        • Solutions for Food & Beverage Forum
      • Healthcare
        • Solutions for Healthcare Forum
  • Blogs
    • By Topic
        • Industrial Automation
          • Industrial Edge Computing Blog
          • Industry 4.0 Blog
          • Industrie du Futur France
        • SCADA & Telemetry Solutions
          • SCADA and Telemetry Blog
        • Power Distribution IEC
          • Power Events & Webinars
          • Power Foundations Blog
        • Power Distribution NEMA
          • NEMA Power Foundations Blog
        • Power Distribution Softwares
          • EcoStruxure Power Design Blog
          • SEE Electrical Building+ Blog
        • Solutions for your Business
          • Solutions for Food & Beverage Blog
          • Solutions for Healthcare Blog
          • Solutions for Retail Blog
        • Community experts & publishers
          • Publishers Community
    • By Segment
        • Food & Beverage
          • Solutions for Food & Beverage Blog
        • Healthcare
          • Solutions for Healthcare Blog
        • Retail
          • Solutions for Retail Blog
      • Industrial Automation
        • Industrial Edge Computing Blog
        • Industry 4.0 Blog
        • Industrie du Futur France
      • SCADA & Telemetry Solutions
        • SCADA and Telemetry Blog
      • Power Distribution IEC
        • Power Events & Webinars
        • Power Foundations Blog
      • Power Distribution NEMA
        • NEMA Power Foundations Blog
      • Power Distribution Softwares
        • EcoStruxure Power Design Blog
        • SEE Electrical Building+ Blog
      • Solutions for your Business
        • Solutions for Food & Beverage Blog
        • Solutions for Healthcare Blog
        • Solutions for Retail Blog
      • Community experts & publishers
        • Publishers Community
      • Food & Beverage
        • Solutions for Food & Beverage Blog
      • Healthcare
        • Solutions for Healthcare Blog
      • Retail
        • Solutions for Retail Blog
  • Ideas
        • Industrial Automation
          • Modicon Ideas & new features
        • SCADA & Telemetry Solutions
          • Geo SCADA Expert Ideas
          • SCADA and Telemetry Devices Ideas
  • Knowledge Center
    • Building Automation Knowledge Base
    • Industrial Automation How-to videos
    • Ask Exchange
    • Digital E-books
    • Success Stories Corner
    • Power Talks
  • Events & Webinars
  • Support
    • User Guide
    • Leaderboard
    • Releases Notes
How can we help?
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: 
49470members
Join Now
242767posts
Join Now

Building Automation Knowledge Base

  • « Previous
    • 1
    • 2
    • 3
    • …
    • 73
  • Next »
1451 posts
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 73
  • Next »
Sort by:
Date
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Subscribe to RSS Feed
  • Invite a Friend
  • Print Knowledge Base
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 73
  • Next »
Showing articles with label TAC INET. Show all articles

Changing from the "Small Numbers" format to the "Large Number" Format

Issue You need to change from the Small Number Format to Large Number Format (Hex) Product Line TAC I/NET Environment I/NET Seven Cause The system is limited to a maximum number of access cards of 32,000.  If a larger number is required then I/NET must be configured to used large card numbers.  Resolution To convert I/NET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Weigand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can be used to determine the Decimal number of the first card in the system (Card #970 Facility code 199) is Decimal number 13042634 depending on which card format is been used. This number will become the source number in the Key card table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the Inet Seven Access Control editor.  This table will be removed after running the provide SQL Script  At this point shut down Inet Seven and run the attached SQL Script. Then once the script runs then restart Inet and look in the individual’s editor and you will see what is shown below. Start I/NET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify that a Hex number and the decimal number in the Individual editor In order to have large numbers working on a site DipSw #7 has to be turned ON for the 7920 DPU's. For the SCU1284 in the door editor at the top center of that editor, there is a check box "Card Translation" you have to check that box for large numbers to work in the SCU's. You will have to do an SLI “SAV” because that is where the Card numbers are now stored and then do an SLI restore. Followed by a DPU restore to all of the door controllers.  
View full article
Picard Product_Support
Thursday

Last Updated: Janeway RobertAndriolo Janeway Thursday

Labels:
  • TAC INET
707 Views

Temperature Sensor Resistance Charts

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 here. The devices covered are Schneider-Electric's range including Andover, TAC and Satchwell and other manufacturers temperature sensors. All are detailed below. For the standard thermistor, tables click here, where the INET, I/A, and BALCO resistance tables are detailed. This is the chart for the Precon Thermistors - ACCTemp 10K Type III thermistor also known as the 10K4A1 Thermistor. For EcoStruxure I/O Module universal inputs, the type of thermistor bead is classed as a: "10k Type I (Continuum)" 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 include: 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 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, and 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 can be found here. Please note that the controller may not be able to use the full temperature range shown in the table.  
View full article
Picard Product_Support
‎2020-12-02 06:46 AM

on ‎2020-12-02 06:46 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • Field Devices
  • Satchwell MicroNet
  • Satchwell Sigma
  • TAC IA Series
  • TAC INET
  • TAC Vista
6853 Views

AMT not receiving Data

Issue AMT has stopped receiving data AMT is not receiving data A new link added to a system, is not sending messages or transactions Product Line TAC INET Environment I/NET Cause AMT can stop receiving data for several reasons. Connection between Remote Client with I/O and SQL is broken AMT is Paused Communication to the device is not functioning AMT Masking is not set correctly Host Masking is not set correctly Point Masking is not set correctly Door Editor Masking is not Set The software has frozen I/NET has reached its maximum online event size and FIFO is not working (very rare) Other Resolution Connection between Remote Client with I/O and SQL PC is broken. Check that no other I/NET PCs are connected to the SQL database. This may include an instance of I/NET installed on the SQL PC Restart the I/Net Remote Client with I/O to re-establish the connection with the SQL Server Wait several minutes for data to update. If this fails, ensure that there are no firewalls or communication failures between the 2 PCs. If using I/NET v2.42 there have been instances where this version does not pass events to the SQL Server.  This is fixed in v2.43 or greater. AMT is paused Right-click anywhere in an open Alarm/Transaction/Message window The bottom choice is either "Pause" or "Resume" If it is "Resume" click on that and AMT function will be restored Communication to the device is not functioning Minimize AMT and open I/NET Connect to the controller Select Summary>Controller If you see values and get no error messages this is not the issue If you cannot see values or get a "No Entries in Database" error, determine why communication is down AMT Masking is not set correctly In AMT Select Edit>Configuration Note the current settings, take a screen shot and save it if possible For troubleshooting purposes, select all of the check boxes under "Messages/Alarm" Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Host Masking is not set correctly (TCP/IP only) Right-click on the I/O server and select Configure Modify the Active Profile On the bottom of the screen click on "Host Masks" Select any NPR or 527 Note the current settings Check all boxes Click okay Repeat 4-7 for all NPR or 527 devices Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Point Masking not set correctly Connect to a controller that you expect to receive messages from Select Edit>Controller>Resident I/O Modify a point you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Messages and Alarms Click okay Go to the controller summary and attempt to trigger a message or alarm Door Editor Masking is not Set Connect to a controller that you expect to receive messages from Select Edit>Controller>Doors Modify a door you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Transactions and Alarms Click okay Attempt to trigger a message or alarm The software has frozen Restart the I/O server If this does not work restart the computer I/NET has reached its maximum online event size and FIFO is not working (very rare) Right Click on the I/O server and select Archive Configuration Enable Archiving if it is not enabled Increase the size of the maximum online events Restart the I/O server Trigger an Alarm or Event in I/NET Verify AMT  Other troubleshooting steps Force a Lan to reconfigure by changing the station address of the Xenta 527, then changing it back If AMT still will not function Repeat the above processes using an Event window with no filter.  It is possible messages are being received, just not to the open Window Close all open AMT windows Select System>New>Event Window Click Okay This opens an Event Window which will display all data coming into AMT Repeat the above troubleshooting processes The Controller LAN is having communication issues Cycle power on one of the Controllers on the Controller Lan to force a Lan Reconfigure Other solutions for this issue have been documented in these articles: No door transactions coming into AMT: Quick Poll is not enabled.  Typically applies to older sites. Transactions not Updating AMT Window using direct connect: For Direct Connect systems No Transactions or controller Events in AMT: Reliable Tap AMT messages stop after re-installing I/NET: Applies to recently upgraded sites.
View full article
Picard Product_Support
‎2020-11-30 08:00 AM

on ‎2020-11-30 08:00 AM

Labels:
  • TAC INET
1214 Views

SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, 2008, or 2008 2. It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 
View full article
Picard Product_Support
‎2018-09-07 03:29 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-19 11:32 AM

Labels:
  • TAC INET
1156 Views

Calibrating Airflow on a Xenta 102-AX (or MR-VAV-AX) using the M/STAT

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.
View full article
Picard Product_Support
‎2018-09-07 07:09 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-19 07:17 AM

Labels:
  • EcoStruxure Building Operation
  • TAC INET
  • TAC Vista
1206 Views

Remote Client with I/O in the Workstation Type of the I/O Server 2.4 and later

Issue What is Remote Client with I/O in the Workstation Type in the I/O Server? Product Line TAC INET Environment I/Net Seven version 2.4x with need for Remote Client configuration using a Remote SQL Server. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.4x  Resolution The new option of Remote Client with I/O for the Workstation Type begins with 2.4x version of I/Net Seven. This option is for a SQL Server which is not located on the Filemaster or Standalone but rather a separate Server. The Remote Client with I/O must be running for other standard Remote Clients to get the features such as AMT, Trends, and Network Functions. Network Functions can be found in I/Net on the pull down menu Edit/Host Computer/Network Functions. The configuration is in the I/O Server under the current profile and can be found in the Workstation Options.  HINT: Exit the I/O Server (and I/net) and select Start/Programs/I/Net/I/Net Configuration to be able to setup the Remote Client. Remote Client is not show unless you exit I/O Server. Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Remote Client with I/O. I/Net version 2.4x Remote Client with I/O Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Filemaster, Equalized Client, or Remote Client. I/Net version 2.4x Filemaster, Equalized Client, or Remote Client Suggestions for further info: To install the SQL, go to Installing I/NET Seven on a 64-bit operating system. For more on how to set up that Remote Client with I/O to use that SQL database, see Unable to connect Remote Client to Standalone Server. 
View full article
Picard Product_Support
‎2018-09-07 07:06 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-17 11:06 AM

Labels:
  • TAC INET
1140 Views

Device connected to 24VAC begins to smoke due to power input from transformer not being wired correctly

Issue Power to devices are Full Wave or Half Wave. Device is connected to 24VAC and begins to smoke because the voltage power input from transformer is not wired correctly. Product Line TAC INET, TAC Vista Environment Devices such as a Xenta Router or a controller which is powered by an external 24VAC transformer. Cause Devices such as a Xenta Router or control board is connected to 24VAC and begins to smoke because the power input from transformer is not correct. Resolution Download Full Wave Half Wave.pdf which illustrates the transformer to device wiring configuration. PoE is not supported for any of the Ethernet ports on I/NET devices.  
View full article
Picard Product_Support
‎2018-09-07 03:16 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-17 06:37 AM

Labels:
  • TAC INET
  • TAC Vista
649 Views

Dip Switch 7, Card Translation checkbox settings required depending on Card Number, MIP on the DPU

Issue Configuration help for doors on a 1284, 7920, or 7910 Setting up Access Control on an SCU or DPU Can’t remember if Dip Switch 7 is up for the Card Number equals Individual Number without a MIP on the DPU or was that Card Translation Checked box the issue Environment I/NET Seven Access Control SCU 1284, DPU 7920, DPU 7910 Cause Configuration errors or failure to remember how to properly configure the door editor Resolution SCU 1284 Yes → Large Number Format Yes → In Door Editor, CHECK Using Card Translation     ↓No   ↓No             Card Number equals individual scheme Yes → In Door Editor, UNcheck Using Card Translation     7920 Yes → MIP Board Yes → Using Large Numbers Yes → In Door Editor, CHECK Using Card Translation ↓No   ↓No   ↓No             In Door Editor, UNcheck Using Card Translation         EPROM Yes → Large number format Yes → Dip Switch 7 on         ↓No             Card Number = Individual Number Yes → Dip Switch 7 off 7910 Yes → EPROM Yes → Large number format Yes → Dip Switch 7 on         ↓No             Card Number = Individual Number Yes → Dip Switch 7 off
View full article
Picard Product_Support
‎2018-09-07 09:35 PM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-11 06:14 AM

Labels:
  • TAC INET
594 Views

Fiber Optic Interface, Ethernet, C-LAN, and Sub-LAN communication.

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network with integration of the FOI or Fiber Optic Interface  Cause How the Fiber Optic Interface (FOI) fits into an I/NET site. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN and the integration of Fiber Optic or FOI. The FOI Spec sheet is available here, as well as TCON087. Click the image below to download as a PDF document.  
View full article
Picard Product_Support
‎2018-09-07 03:43 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-06 06:48 AM

Labels:
  • TAC INET
876 Views

Troubleshooting sending emails from a Xenta Server

Issue Troubleshooting sending email alarms from a Xenta Server. Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 511:B, 527, 701, 711, 721 and 731 XBuilder SMTP Server Cause There are many reasons why an emailed alarm from a Xenta Server wouldn't reach the desired destination inbox. This document walks through the most common settings and networking issues and how to overcome them. Resolution Some Xenta Servers can be configured to send out alarms via email – 511, 511:B, 527, 701, 711, 721 and 731. Typically, following the instructions found in the TAC Vista Xenta Server – Web Server Technical Manual will result in successful delivery of email alarms. However, there are some factors that can hinder these email messages. This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Xenta alarms to email out is to properly configure the XBuilder project. Reference Chapter 5.2 Configuring the TAC Xenta Server for Email Forwarding in the TAC Vista Xenta Server – Web Server Technical Manual. Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any). If no SMTP server or login information has been provided, contact an IT professional at the customer's site to obtain this information. Alternately, for testing and demo purposes, Schneider Electric's SMTP server can be used – smtpservice.buildings.schneider-electric.com (port 25 or port 2525). If using Schneider Electric's SMTP server, set the Authentication to "TAC." Once the Xenta Server is correctly configured, set up Alarm Receivers in the XBuilder project. The steps for this can be found in Chapter 4.3 Configuring Receiver Groups in the TAC Vista Xenta Server – Web Server Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses. Then the distribution list can be edited and maintained by the IT staff without ever having to access XBuilder projects or Xenta Servers. If everything is set up correctly, test the email capability by logging into the web interface of the Xenta Server and navigating to Utilities > Tools > Communication Tests. Enter a test email destination and hit "Test" as shown in Figure 1.  Figure 1. Test Send E-mail Message If the email arrives as expected, then the SMTP settings are all correct. A final test of the alarm receivers and alarm properties can be accomplished by forcing an alarm condition. If the email does not arrive as expected, check the following possible errors, or proceed directly to the next section of this document titled "Check SMTP Connectivity." Could not send the e-mail, error in mail configuration If this error results from sending a test email, then the settings in XBuilder need to be revisited and verified. Failed deliver e-mail, connection couldn't be established, check e-mail address If the test results in this error, proceed to the next section of this document titled "Check SMTP Server Connectivity." Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established. In this example, the provided SMTP server is "smtp.ACME.com." Xenta Servers have a built in test function for determining the status of some of the defined devices. Log into the web interface and navigate to Utilities > Tools > Communication Tests.  Figure 2. Communication Tests From this screen, the connection between the Xenta Server and any of the defined gateways and servers can be verified. Select the radio button for Mail server 1 (SMTP) and hit test. Some possible results of the test are: ‘Mail server 1 (SMTP)’ is on-line If the mail server is online, but the test email still is not delivered, then the cause is most likely the authentication credentials of the Xenta Server. Check with an IT professional to verify the login account name and password that have been provided. Check that it has been correctly entered as described in the section of this document titled "Check SMTP Server Settings." If all of this is set up correctly and verified, proceed to the section of the document titled "Xenta Server Indicates No Errors." ‘Mail server 1 (SMTP)’ is off-line If the mail server is offline, then no communication exists. Make sure the SMTP server settings are correct. Refer to the section of this document titled "Check SMTP Server Settings." Also check the TCP/IP settings as described in the section of this document titled "Check TCP/IP Settings." If the SMTP server is outside the network, ensure that the default gateway is defined and test its availability with a communication test as shown in Figure 2. Lastly, connect to the network using a laptop and attempt to ping the SMTP server. If it is unavailable, contact an IT professional for assistance. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 3. Failed Ping Example C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 4. Successful Ping Example In Figure 4, the ping has returned four successful results. This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating. It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 5. Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 6. Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220. Type the word "helo" and press enter. The SMTP server should again respond but this time with a line starting with 250. Exit the telnet session by typing "quit" and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 7. Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Xenta Server. That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled "Xenta Server Indicates No Errors." Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below)  Figure 8. Enable Telnet Client. Failed convert dns-name into ip-number If using DNS names for the SMTP server instead of IP addresses, a DNS server must be defined. A DNS server is responsible for resolving DNS names to IP addresses. Make sure the DNS server is online with a communication test as shown in Figure 2. To bypass any problems with DNS, enter the SMTP server IP address instead. This can be obtained by pinging the server as shown in Figure 3. Check SMTP Server Settings The SMTP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > SMTP.  Figure 9. SMTP Settings The fields shown in Figure 9 for "Outgoing mail server port" are not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and below, it is not possible to alter the default SMTP port. It is hard-coded at 25. The Primary SMTP will be provided by the site's IT staff. If authentication is required, then an account name and password must be provided by the IT staff. If the SMTP server is available, but no emails are being sent out, the authentication parameters need to be checked. Any further investigation at that point will require contacting an IT professional for assistance. Refer to the section of this document titled "Xenta Server Indicates No Errors" for some troubleshooting questions to pose. Also refer to "Contacting an IT Professional" for documents to use to facilitate these conversations. If no SMTP server has been provided, then Schneider Electric's SMTP server can be used. To use Schneider Electric's SMTP server for testing or temporary purposes, enter "smtpservice.buildings.schneider-electric.com" into the outgoing mail server. Mail server ports 25 and 2525 are available. Authentication is set to "TAC." This does not require an account name or password. This method is only recommended for testing purposes. Schneider Electric makes no guarantees as to the availability of the SMTP server. To ensure the email alarms are being delivered as promised, use an SMTP server with some guarantee of up time. Even if an SMTP server has been provided, consider defining Schneider Electric's SMTP server as a secondary server. It is not always a viable solution due to some network security settings and availability, but may increase the overall success rate of your email delivery by providing some redundancy. Check TCP/IP Settings The TCP/IP settings can be viewed and changed either in the XBuilder project, or live via the server's web interface. If you are troubleshooting live on a site, it is probably faster and easier to use the web interface. If settings are changed live, be sure to update the XBuilder project at some point to avoid the settings being erased by a download. Navigate in the web interface to Configuration > Network > TCP/IP.  Figure 10. TCP/IP Settings The most important items to check on this screen are Default gateway and DNS server. If the default gateway is not properly defined, then external SMTP servers will be unavailable. If the DNS server is not properly defined, then SMTP servers defined by DNS names will be unresolved. Either enter a valid DNS server, or manually resolve the IP address by pinging the server as shown in Figure 3. If using Schneider Electric's SMTP server, DNS must be defined. Xenta Server Indicates No Errors If the test email was sent, but not received, and no errors were recorded, the focus should now shift to troubleshooting the SMTP server itself. Assistance from an IT professional will be helpful at this stage. Things to check include: Check the incoming/outgoing messages from the SMTP server. See if the messages from the Xenta Server are arriving but not being sent out. Many companies will set up an "allowed" list that will only pass emails from recognized IP addresses, and all else is filtered as spam. Make sure the Xenta Server's IP address is listed on the acceptable list. Ask what port the SMTP communication is using. Port 25 is typically used for SMTP communication, but some companies will change this for security purposes. Request that port 25 be opened for SMTP communication from the Vista Server. If this is not an option, the port can be changed in XBuilder/System Program versions 5.1.3 and later. See the section of this document titled "Changing the default SMTP Port" for instructions. Xenta Servers are hard-coded to use UTF-7 encoding. They require this encoding to support Swedish characters. UTF-8 is the most common encoding in America and Europe. Some networks may filter UTF-7 messages as spam. While this is not readily configurable, it can be manually changed by editing some files. Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device and then cycle the power. The device will now use UTF-8 character encoding which is more commonly used in the United States. Remember that reloading the system program will erase these changes. Some companies will block all POP messages on the network. This will disable the ability to use external SMTP servers. Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the default SMTP Port Changing the default SMTP port is not available in XBuilder/System Program versions prior to 5.1.3. In versions 5.1.2 and before, the only options are to request for the IT department to allow use of port 25, or upgrade to version 5.1.3 or later. If you are using XBuilder/System Program version 5.1.3 or later, adjusting the default SMTP Port can be done through the web interface as shown in Figure 9. It can also be adjusted in XBuilder as shown in Figure 6.  Figure 11. Changing the SMTP Port in XBuilder Contacting an IT Professional If you need help contacting the customer's IT department to gather and share the correct data, use the document attached in Appendix A: IT Request for Information. A completed example is shown in Appendix B: Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice. It is also subject to change with versions of TAC Xenta Servers. If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication required (choose one): Yes No Account name (if applicable):   Password (if applicable):   To distribution list (if any):   Required UDP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses):   Unit e-mail address:   From IP address:   Desired UDP port:   Appendix B: Sample IT Request for Information The TAC building automation system installed on your site has the capability to email facilities personnel in certain situations. Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system. TAC Xenta Servers use standard Simple Mail Transfer Protocol (SMTP) for these messages. An SMTP server must be provided in order for these messages to be delivered. The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication required (choose one): Yes No Account name (if applicable): emailuser Password (if applicable): password123 To distribution list (if any): facilities_staff@thebuilding.com Required UDP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: To distribution list (or email addresses): facilities_staff@thebuilding.com Unit e-mail address: xenta@server.com From IP address: 10.10.10.20 Desired UDP port: 25
View full article
Picard Product_Support
‎2018-09-07 02:38 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-04 07:12 AM

Labels:
  • TAC INET
  • TAC Vista
1643 Views

Seven Reports Error "CRPaige library CRPaig80.DLL cannot be found"

Issue Seven Reports Error "CRPaige library CRPaig80.DLL cannot be found". Product Line TAC INET Environment I/NET site with Windows OS Cause Missing CRPaig80.DLL error message Resolution CRPaig80.DLL can be found on the original I/NET Seven installation CD (cd-drive:\program files\inet seven). Copy CRPaig80.DLL to the root I/NET Seven folder (c:\program files\inet seven). Click Here to download a zipped copy of the CRPaig80.DLL
View full article
Picard Product_Support
‎2018-09-07 02:12 AM

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

Labels:
  • TAC INET
916 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
558 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
794 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
851 Views

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

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.  
View full article
Picard Product_Support
‎2018-09-07 01:29 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-29 07:29 AM

Labels:
  • Satchwell MicroNet
  • TAC INET
  • TAC Vista
511 Views

3 State Event Sequence to control certain Access Control Doors

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
View full article
Picard Product_Support
‎2018-09-06 02:46 PM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-28 11:34 AM

Labels:
  • TAC INET
657 Views

Acknowledge and purge a "Force Door" alarm in AMT

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."  
View full article
Picard Product_Support
‎2018-09-06 02:45 PM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-28 11:32 AM

Labels:
  • TAC INET
715 Views

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

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.  
View full article
Picard Product_Support
‎2018-09-07 04:03 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-28 11:31 AM

Labels:
  • TAC INET
816 Views

USB Prox enrollment reader for I/NET Seven

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.
View full article
Picard Product_Support
‎2018-09-07 01:52 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-28 11:27 AM

Labels:
  • TAC INET
611 Views

How to find the Facility Code and Card Number

Issue Can I take a 26 bit Wiegand Hexadecimal Card Number format and find out what the Facility Code and Card Number are? Product Line TAC INET Environment 26 bit Wiegand Hexadecimal Card Cause Need to discover the Facility Code and Card Numbers Resolution Yes you can do this. This document will show you the process on how to determine these values: 26 Bit Wiegand Format Also see Conversion from I/NET hexadecimal code to Continuum Facility/Card Number for an Excel utility to perform this conversion.
View full article
Picard Product_Support
‎2018-09-07 04:02 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-10-28 11:24 AM

Labels:
  • TAC INET
4073 Views
  • « Previous
    • 1
    • 2
    • 3
    • …
    • 73
  • Next »
Labels
  • Access Expert 81
  • Andover Continuum 2,167
  • Automated Engineering Tool 3
  • CCTV 53
  • EcoStruxure Building Expert 216
  • EcoStruxure Building Operation 1,465
  • EcoStruxure Workplace Advisor 1
  • Field Devices 690
  • OTHER 197
  • Pelco 1
  • Project Configuration Tool 19
  • Satchwell MicroNet 251
  • Satchwell Sigma 448
  • Security Expert 186
  • TAC IA Series 1,778
  • TAC INET 1,451
  • TAC Vista 2,040
  • « Previous
  • Next »
Support

Have a question? Please contact us with details, and we will respond.

Contact Us
FAQ

Look through existing questions to find popular answers.

Learn More
About

Want to know more about Exchange and its possibilities?

Learn More

Full access is just steps away!

Join Exchange for FREE and get unlimited access to our global community of experts.

Connect with Peers & Experts

Discuss challenges in energy and automation with 30,000+ experts and peers.

Get Support in Our Knowledge Base

Find answers in 10,000+ support articles to help solve your product and business challenges.

Ask Questions. Give Solutions

Find peer based solutions to your questions. Provide answers for fellow community members!

Register today for FREE

Register Now

Already have an account?Log in

About Us FAQ Terms & Conditions Privacy Notice Change your cookie settings
©2020, Schneider Electric