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,827
  • TAC INET 1,458
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 333
  • 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:
Views
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • …
    • 156
    • 157
    • 158
    • …
    • 509
  • Next »

Repair or replace an obsolete part from the Network 8000 and DMS product lines

Issue An obsolete part from the Network 8000 and DMS product lines has failed. Is there an option to repair and/or replace it with a refurbished unit? Product Line TAC IA Series Environment NETWORK 8000 Cause Replacement parts for obsolete parts on the Network 8000 and DMS product lines. Resolution A company has been retained that can repair and/or replace several parts from both product lines. Contact information: Name: ISA Phone: 1-800-430-6013 Web: www.isa-net.com On the home page of their website, select "Energy" at the top of the screen and then click on "Parts". On the new screen, click on "Barber-Colman (Invensys)". On the subsequent screen, click on "Invensys". A list of available parts for both Network 8000 and DMS will result. Availability varies so it is best to contact them by phone.  For additional information, see Product Announcement PA-00164 Network 8000 Availability – REPAIR UPDATE.
View full article
Picard Product_Support
‎2018-09-07 02:22 AM

Labels:
  • TAC IA Series
1714 Views

TS-8XXX and TS-9XXX 1,000 Ohm Balco sensor, Celsius temperature resistance table.

Issue TS-8XXX and TS-9XXX 1,000 Ohm Balco sensor, Celsius temperature resistance table. Environment TS-8XXX TS-9XXX 1,000 Ohm Balco sensor Cause Unknown Cause Resolution Temp (°C) Ohms -40 779.0 -39 782.3 -38 785.6 -37 788.9 -36 792.3 -35 795.6 -34 799.0 -33 802.3 -32 805.7 -31 809.1 -30 812.5 -29 815.9 -28 819.3 -27 822.7 -26 826.2 -25 829.6 -24 833.1 -23 836.5 -22 840.0 -21 843.5 -20 847.0 -19 850.5 -18 854.1 -17 857.6 -16 861.1 -15 864.7 -14 868.3 -13 871.8 -12 875.4 -11 879.0 -10 882.6 -9 886.2 -8 889.9 -7 893.5 -6 897.1 -5 900.8 -4 904.5 -3 908.1 -2 911.8 -1 915.5 0 919.2 1 923.0 2 926.7 3 930.4 4 934.2 5 937.9 6 941.7 7 945.5 8 949.3 9 953.1 10 956.9 11 960.7 12 964.6 13 968.4 14 972.3 15 976.1 16 980.0 17 983.9 18 987.8 19 991.7 20 995.6 21 999.6 22 1003.5 23 1007.5 24 1011.4 25 1015.4 26 1019.4 27 1023.4 28 1027.4 29 1031.4 30 1035.4 31 1039.4 32 1043.5 33 1047.5 34 1051.6 35 1055.7 36 1059.8 37 1063.8 38 1068.0 39 1072.1 40 1076.2 41 1080.3 42 1084.5 43 1088.6 44 1092.8 45 1097.0 46 1101.2 47 1105.4 48 1109.6 49 1113.8 50 1118.0 51 1122.3 52 1126.5 53 1130.8 54 1135.1 55 1139.4 56 1143.7 57 1148.0 58 1152.3 59 1156.6 60 1160.9 61 1165.3 62 1169.6 63 1174.0 64 1178.4 65 1182.8 66 1187.2 67 1191.6 68 1196.0 69 1200.4 70 1204.9 71 1209.3 72 1213.8 73 1218.3 74 1222.7 75 1227.2 76 1231.7 77 1236.2 78 1240.8 79 1245.3 80 1249.8 81 1254.4 82 1259.0 83 1263.5 84 1268.1 85 1272.7 86 1277.3 87 1282.0 88 1286.6 89 1291.2 90 1295.9 91 1300.5 92 1305.2 93 1309.9 94 1314.6 95 1319.3 96 1324.0 97 1328.7 98 1333.4 99 1338.2 100 1342.9 101 1347.7 102 1352.5 103 1357.3 104 1362.1 105 1366.9 106 1371.7 107 1376.5 108 1381.3 109 1386.2 110 1391.0 111 1395.9 112 1400.8 113 1405.7 114 1410.6 115 1415.5 116 1420.4 117 1425.3 118 1430.3 119 1435.2 120 1440.2 121 1445.2 122 1450.1
View full article
Picard Product_Support
‎2018-09-06 02:31 PM

Last Updated: Administrator CraigEl Administrator ‎2019-06-03 06:53 PM

Labels:
  • Field Devices
1770 Views

Replacement of TAC VG211, VG222 and VG321 series Valve Bodies by S-E.VGS211F 15 and 100CS series Valve Bodies due to obsolescence.

Issue Obsolescence of TAC VG211, VG222, and VG321 series Valve Bodies. Product Line Field Devices Environment TAC VG211, VG222, and VG321 series Valve Body installations. Cause Obsolescence of TAC VG211, VG222, and VG321 series Valve Bodies. Resolution Replace TAC VG211 series Valve Body with S-E.VGS211F 15 – 100CS series Valve Body. It should be noted that a number of anomalies appear in the current issue of the Data Sheet describing the VGS211F 15 - 100CS range of 2-port Valve Bodies. The VGS211F 15-100CS Data Sheet includes two tables of information. A discrepancy appears in respect of the Kv value stated for the 50mm size Valve Body. The table of information on Page 1 of the Data Sheet displays a Kv value of 38 The table of information on Page 2 of the Data Sheet displays a Kv value of 40 The correct Kv value is 40 The type designation stated in the Data Sheet for this Valve Body is also incorrect. The type designation for this Valve Body should read VGS211F-50CS 40M SD00 Arrangements are currently in hand to correct these anomalies. NB The table on Page 1 of the earlier VG211 Data Sheet displayed a Kv value of 38 This value was also incorrect. The Kv value should have read 40 The VG222, VG222 and VG321 are no longer available, as it is replaced with the following: VG222 Valves will have the family name VG221F VG321 Valves will have the family name VG311F Please find the Product Announcement PA-00085 with the information.
View full article
Picard Product_Support
‎2018-09-07 05:06 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-04 08:52 AM

Labels:
  • Field Devices
1739 Views

Alarms are not displayed in the Sigma local or remote client Alarm Manager window

Issue Alarms being generated on the Sigma system are not displayed in the Sigma local, or remote client Alarm Manager window. Product Line Satchwell Sigma Environment Sigma 4.04 or later Cause The Sigma local, or remote clients have not been correctly configured in the Sigma server. Resolution Confirm that the Sigma client has been selected to receive alarms. Open the Sigma System Setup and from the tree structure select "Clients". Identify and select the required client , confirm that the correct Sigma server is selected from the list of servers shown.   Select Controllers from the tree structure, then choose "Routesets". For each routeset make sure that the client has been selected.   If changes have been made to the routesets, download them to all of the Sigma controllers.
View full article
Picard Product_Support
‎2018-09-07 03:04 AM

Last Updated: Administrator DavidFisher Administrator ‎2020-11-04 08:59 AM

Labels:
  • Satchwell BAS & Sigma
1711 Views

Square D Altivar 61 with BACnet card. Found drives coming on and offline on BACnet Bus. The literature stated the baud rate could be up to 76.8 k.

Issue Square D Altivar 61 with BACnet card. Found drives coming on and offline on BACnet Bus. The literature stated the baud rate could be up to 76.8 k. Environment Square D Altivar 61 with BACnet card Cause Communication card would not communicate above 19.2k baud rate. Resolution Change the baud rate of the network below 19.2k.
View full article
Picard Product_Support
‎2018-09-06 02:29 PM

Last Updated: Sisko DavidChild Sisko ‎2021-02-01 01:48 AM

Labels:
  • Field Devices
1722 Views

"No license for LonWorks communication" error message in Classic Network

Issue When trying to view values in a Classic Network, "[No license for LonWorks communication]" message shows up in the Value tab and the alarm window. Product Line TAC Vista Environment Vista Classic Network Cause Though you are using Classic network, it's still using LON standards. You still need the license for TAC Vista Server. If the Server license is missing or invalid, you will get this kind of message. Resolution Check your license file and make sure you have the server license included. The server license should look something like listed below:  INCREMENT Vista.Server taclic 5.1 permanent 1 ISSUER=TAC \ If you do not have the line above, it means you do not have the proper license for TAC Vista server. Thus, you get the error message saying "No license for LonWorks communication."  The solution is to purchase the TAC Vista Server license, or use the demo license or an engineering dongle. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility
View full article
Picard Product_Support
‎2018-09-07 03:32 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-09 07:11 PM

Labels:
  • TAC Vista
1718 Views

Error: LNS #25 lcaErrDatabase "Database error. (Subsystem: LNS, #25)[DB#-2506]"

Issue "Database error. (Subsystem: LNS, #25)[DB#-2506]" After clicking OK there may be another error: "The global database is not open. (Subsystem: LNS, #64)". When the Echelon LonMaker Design Manager opened, there is nothing in the Database Name field. Product Line TAC Vista Environment LonMaker Vista LNS Cause This error can occur when ports that the LNS Database is trying to use are already being used by other applications. The ports in question are 6001 and 6002. Resolution To check which application is using these ports, use the following DOS command: netstat -bn Once you know which application is using ports 6001 and 6002, shut that application down and relaunch LonMaker or your LNS-based application. For further information refer to Echelon Support article kb481
View full article
Picard Product_Support
‎2018-09-07 03:42 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-14 10:47 PM

Labels:
  • TAC Vista
1701 Views

DVR incorporated with I/NET Seven and Pelco Integral or Digital Sentry

Issue DVR incorporated with I/NET Seven and Pelco Integral or Digital Sentry Product Line Pelco, TAC INET Environment I/Net Seven Pelco Integral or Digital Sentry DVR CCTV Cause Send back a Integral DVR and it comes back as a Digital Sentry or confusion revisions of I/NET Seven and Pelco Integral of Digital Sentry Resolution This chart to clarifies which versions of I/NET Seven are compatible with which Pelco DVRs: For the latest products (after 2.31 revision) please visit Software and Firmware compatibility matrix for older versions of the traditional product lines which has the most recent Pelco compatibility.
View full article
Picard Product_Support
‎2018-09-07 03:41 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-09 08:38 PM

Labels:
  • CCTV
  • TAC INET
1727 Views

Having set Link Addressing in a Sigma DNN3 can no longer communicate to the DNN3 and Link Addressing does not work.

Issue Set-up the Link Addressing using the Pocket Terminal (LA +) for port 1 via the DNN3 service port and set port 2 on the DNN3 to be Serial PPP.  Can't communicate to the DNN3 from the Sigma server and global data is not being passed between the two VLAN's. Environment Multiple Sigma controllers across at least two Ethernet VLAN's.  DNN3's (version 1.h) connected to each VLAN. Each DNN3 is connected to the VLAN via port 1 and port 2 is configured as a 'virtual' serial PPP port but not connected to a device. Cause No routing information (static routes) entered into the DNN3's.   Although Link Addressing can be correctly configured the DNN3 devices also need to know where to transmit the point to point global data, that is the router device for the local Ethernet VLAN or default gateway. By having two ports configured on the DNN3 network routing messages RIP will be enabled and broadcast and will advertise the port 2 address as a potential but false route off the network, therefore RIP must also be disabled.  Resolution Using Pocket Terminal or Windows Hyperterminal enter a default Static Route to the DNN3 via its service port.  Use the generic entry 0.0.0.0/0 for the destination sub-LAN and mask.  For example; SR+ 0.0.0.0/0 192.168.1.253   1      (Where 192.168.1.253 is the default gateway and 1 is the DNN port number). RIP must also be disabled on the DNN3 port 1.  For example; RIPD 1
View full article
Picard Product_Support
‎2018-09-06 02:19 PM

on ‎2018-09-06 02:19 PM

Labels:
  • Satchwell BAS & Sigma
1735 Views

Error 1001 when installing Cyberstation or Webclient

Issue Receive error 1001 when installing Cyberstation or Webclient Environment Continuum Cyberstation Webclient 1.9x Windows XP SP3 Windows Server 2003 Windows Server 2008 Windows Vista Cause Windows application viewer is full Resolution Clear the Windows application event view log. See the following link or the lettered steps below. Open Event Viewer (Start>Run>Eventvwr or Go to Administrative Tools>Open Event Viewer) In the console tree, click the log you want to clear. On the Action menu, click Clear all Events. Click Yes to save the log before clearing it. Click No to permanently discard the current event records and start recording new events. Install Continuum
View full article
Picard Product_Support
‎2018-09-07 08:25 AM

Labels:
  • Andover Continuum
1744 Views

Error "Continuum is already running" while trying to start Continuum or C0663 error

Issue Error "Continuum is already running" while trying to start Continuum. Environment Continuum 1.91 Windows XPsp3 Cause Continuum was not gracefully shut down, which left some services running. Resolution Reboot PC which will terminate all services or use Continuumprocesses.exe in the Continuum folder If this is an upgrade ensure that the database has been updated prior to starting Cyber with the transferred database Make sure the Workstation initialization was completed prior to starting Cyber.
View full article
Picard Product_Support
‎2018-09-06 02:18 PM

Labels:
  • Andover Continuum
1717 Views

Ethernet connection speeds for Sigma controllers

Issue Which Ethernet port speeds are supported by Sigma controllers? Product Line Satchwell Sigma Environment Sigma controllers Ethernet New Hardware. ARM 7(S-696, S-x96CPU-AE, S-796, S-x796CPU-AE, S-DNN3, S-DNN3-DT, S-632-E, S-632-AE and S-IC3's) Old Hardware V53  (S-ETH, S-496, S-596, S-532, S-DNN and S-IC's) Cause The newer ARM-7 controller hardware supports more Ethernet connection speeds than the older V53 controller hardware. Resolution Most Ethernet hubs or switches autoscan to find the best connection speed.  For Sigma device hardware types, the supported Ethernet speeds are as follows: ARM-7 (New hardware): 100Base-T (and supports port auto-scanning on connection) 100M Half Duplex 10M full/half duplex V53 (Old hardware): 10Base-T (does not support port auto-scanning) 10M half Duplex Additionally, for direct connections to a Sigma controller: ARM-7 Ethernet connection supports both straight and cross-over Ethernet cables. V53 hardware only supports cross-over cables.
View full article
Picard Product_Support
‎2018-09-06 02:14 PM

Last Updated: Administrator CraigEl Administrator ‎2023-11-13 06:04 PM

Labels:
  • Satchwell BAS & Sigma
1789 Views

Alarms not showing up in the alarms list

Issue Alarms not showing up in the alarm list. Environment TAC Vista Workstation TAC Vista Server Cause The alarm could be disabled. The alarm might have priority 0 (info). There might be a filter in place in the alarm list. Resolution The alarm could be disabled, in workstation go to View > Disabled alarms to see the list and enable again. The alarm might have priority 0 (info). No Alarms with priority 0 is shown in the alarm list. There might be a filter in place in the alarm list, in the alarm view you are using right click and select filter to check this. A good practice is to set the "Date and Time" tab settings to reflect "Tripped " and "Last change" to show all alarms. This is done by checking the four checkboxes for "First alarm" and "Last alarm" allowing all alarms to be viewed.  
View full article
Picard Product_Support
‎2018-09-06 02:14 PM

Labels:
  • TAC Vista
1711 Views

Alarm delivery server window popping up

Issue Alarm delivery server window popping up Environment Continuum Cyberstation 1.91 Cause Alarm delivery server window popping up Resolution Updated OS and applied all the current updates. The issue resolved after the updates
View full article
Picard Product_Support
‎2018-09-06 02:08 PM

Labels:
  • Andover Continuum
1722 Views

Replacement of Satchwell ALM series Linear Actuator by S-E MV15B-230 Linear Actuator due to obsolescence. (Actuator Selection)

Issue Satchwell ALM series Linear Actuator requires replacement. Environment Satchwell ALM series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF Series Plug and Seat Valve Body. Actuator type :- ALM series Cause Obsolescence of Satchwell ALM series Linear Actuator. Resolution Replace Satchwell ALM series Linear Actuator with MV15B-230 Linear Actuator and Linkage Kit :-  ALM = MV15B-230 + L7SV (880-0126-000) Linkage Kit N.B.  Should the Satchwell ALM series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the MV15B-230 Actuator as appropriate :-  S2 – MV15B = Two independent 250 volt 10 amp / 3 amp rated SPDT Auxiliary End Point Switches.
View full article
Picard Product_Support
‎2018-09-06 02:06 PM

on ‎2018-09-06 02:06 PM

Labels:
  • Field Devices
1739 Views

The difference between NL220I and NL220M dongles

Issue What is the difference between the NL220I and NL220M dongle. Product Line Other, TAC Vista Environment Newron NL220 Cause There are two types of NL220 dongles, (install) and M(maintenance).  Each type have their own specific functionality.  The correct dongle should be selected to avoid issues at a later time. Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case. Resolution Newron NL220 functionality.   Administration (Engineering) mode will allow the following (NL220I): Creating a project Adding network infrastructure devices Adding LonWorks devices – application specific devices as well as programmable devices Installing and commissioning network infrastructure devices Installing and commissioning LonWorks devices Creating SNVT and tag bindings Configuring devices using the generic browser and device specific plug-ins Managing devices Deleting devices Replacing devices Maintenance mode will allow the following (NL220M): Configuring existing devices using the generic browser and device specific plug-ins Managing devices Replacing devices   Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case.
View full article
Picard Product_Support
‎2018-09-06 02:06 PM

Labels:
  • TAC Vista
1751 Views

Replacement of Satchwell AR Series 1 or AR Series 2 Rotary Actuator by S-E MD Series Rotary Actuator due to obsolescence. (Actuator Wiring)

Issue Satchwell AR Series 1 or AR Series 2 Rotary Actuator requires replacement Environment Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Satchwell ARE ARM & ARX Series 1 and Series 2 Rotary Actuators Cause Obsolescence of Satchwell AR Series 1 or AR Series 2 Rotary Actuators Resolution Replace Satchwell AR Series 1 or AR Series 2 Rotary Actuators with appropriate S-E MD Series Rotary Actuators and wire as follows: Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies ARE ARE Series 1 & 2 Wire Colour BLUE  =  MD10A-24 or MD20A-24 Wire Number 2 ARE Series 1 & 2 Wire Colour RED  =  MD10A-24 or MD20A-24  Wire Number 3 ARE Series 1 & 2 Wire Colour BLACK  =  MD10A-24 or MD20A-24  Wire Number 1 ARE Series 2        Wire Colour WHITE  =  MD10A-24 or MD20A-24  Wire Number 5  ARX ARX Series 1 & 2 Wire Colour RED  =  MD10B-24 or MD20B-24 Wire Number 3 ARX Series 1 & 2 Wire Colour BLUE  =  MD10B-24 or MD20B-24  Wire Number 2 ARX Series 1 & 2 Wire Colour BLACK =  MD10B-24 or MD20B-24  Wire Number 1  ARM – UP TO MARCH 2006 ARM Series 1 & 2 Wire Colour RED  =  MD10B-230 or MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLUE  =  MD10B-230 or MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLACK  =  MD10B-23 or MD20B-230 Wire Number 1  ARM – SINCE MARCH 2006 ARM Series 1 & 2 Wire Colour BROWN  =  MD10B-230 or MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLACK  =  MD10B-230 or MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLUE  =  MD10B-230 or MD20B-230 Wire Number 1  Note: Should the Satchwell AR Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the S-E MD Actuator as follows: MD – S1  One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch  AR COMMON Wire Colour ORANGE  =  MD-S1 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S1 N/O contact Wire Number S3      AR N/C contact Wire Colour WHITE  =  MD-S1 N/C contact Wire Number S2  MD – S2  Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches  AR COMMON Wire Colour ORANGE  =  MD-S2 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S2 N/C contact Wire Number S2  AR COMMON Wire Colour BLACK  =  MD-S2 COMMON Wire Number S4 AR N/O contact Wire Colour RED  =  MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Colour BLUE  =  MD-S2 N/C contact Wire Number S5   Satchwell AR Series 1 or AR Series 2 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE ARE Series 1 & 2 Wire Colour BLUE  =  MD20A-24 Wire Number 2 ARE Series 1 & 2 Wire Colour RED  =  MD20A-24 Wire Number 3 ARE Series 1 & 2 Wire Colour BLACK  =  MD20A-24 Wire Number 1 ARE Series 2        Wire Colour WHITE  =  MD20A-24 Wire Number 5  ARX ARX Series 1 & 2 Wire Colour RED  =  MD20B-24 Wire Number 3 ARX Series 1 & 2 Wire Colour BLUE  =  MD20B-24 Wire Number 2 ARX Series 1 & 2 Wire Colour BLACK =  MD20B-24 Wire Number 1  ARM – UP TO MARCH 2006 ARM Series 1 & 2 Wire Colour RED  =  MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLUE  =  MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLACK  =  MD20B-230 Wire Number 1  ARM – SINCE MARCH 2006 ARM Series 1 & 2 Wire Colour BROWN  =  MD20B-230 Wire Number 3 ARM Series 1 & 2 Wire Colour BLACK  =  MD20B-230 Wire Number 2 ARM Series 1 & 2 Wire Colour BLUE  =  MD20B-230 Wire Number 1  Note: Should the Satchwell AR Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the S-E MD Actuator as follows: MD – S1  One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch  AR COMMON Wire Colour ORANGE  =  MD-S1 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S1 N/C contact Wire Number S2  MD – S2  Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches  AR COMMON Wire Colour ORANGE  =  MD-S2 COMMON Wire Number S1 AR N/O contact Wire Colour BROWN  =  MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Colour WHITE  =  MD-S2 N/C contact Wire Number S2  AR COMMON Wire Colour BLACK  =  MD-S2 COMMON Wire Number S4 AR N/O contact Wire Colour RED  =  MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Colour BLUE  =  MD-S2 N/C contact Wire Number S5
View full article
Picard Product_Support
‎2018-09-06 02:01 PM

on ‎2018-09-06 02:01 PM

Labels:
  • Field Devices
1770 Views

I/NET physical layer issues

Issue I/NET Physical Layer Issues, Lan Reconfigure, and/or Controllers going on or offline 1 at a time. Product Line TAC INET Environment I/NET Cause Physical Layer Issue Resolution Some or all of the following may indicate a physical layer issue. Abnormally large number of Lan Reconfigure messages Controllers going offline individually or in groups and sometimes all together Large numbers of Station Lost/Restore Messages Frequent problems connecting to controllers and data interruption To Troubleshoot a suspected Physical Layer error: Determine if this is a Controller LAN layer issue by direct connection to the Controller LAN using a tap.  If you continue to experience the same errors, as while connected via TCP/IP then the issue is on the Controller LAN Verify that you are using the correct wire gage (22 or 24) and that you controller LAN is less than 4000 feet for 24 AWG and less than 5000 feet for 22 AWG. Verify shield drain wire. Shield drain wire continuity must be maintained as the LAN cable passes through each controller. Shield drain wires from each controller LAN cable must be twisted together, insulated, and tied back such that wires do not come in contact with ground or any conductive surface within a controller. Shield drain wire must be directly connected to Electrical Service Earth Ground at only one end of the cable. The issue at this point can either be a wiring fault or a controller that is broken. Disconnect all controllers from the controller LAN by removing the LAN terminal strip from each controller Reconnect each controller one at a time and watch for the original errors. During this process a LAN Reconfigure is expected each time a device comes online While at each controller watch for any frayed wire, unusual/unneeded splices and if needed re-seat each wire into the terminal block When a controller is brought online and the error returns, examine that leg of the LAN wire for shorts or replace that section of wire Replace the suspect controller with a different device to ensure that the controller is not the source of the problem. (On critical systems you can plug in a spare controller at the location for testing without taking the existing controller offline) Typically if a controller is causing the error it will display alarms or LAN reconfigure on it's LEDs. Consult the TCON for the specific controller for more details (TCON Cross Reference available in TCON Number and Title Cross Reference (with links)). If it is not feasible to replace long sections of wire, or if it is determine that the controller LAN exceeds the specified length, then you may want to consider using Distributed Link Architecture.
View full article
Picard Product_Support
‎2018-09-07 02:09 PM

Last Updated: Administrator CraigEl Administrator ‎2022-08-09 05:09 AM

Labels:
  • TAC INET
1725 Views

"Error getting root folder name" when launching Personnel Manager

Issue Personnel Manager displays "Error getting root folder name" when launching. Product Line Andover Continuum Environment CyberStation Personnel Manager (PIM) Cause At boot time, Personnel Manager queries the ContinuumDB to find the Root container by ID using the following SQL query: SELECT uiname FROM Dictionary WHERE objectidhi = 0 AND objectidlo = 536870913  "Error getting root folder name" will be generated if PIM is unable to access the ContinuumDB or can not find the root object for any other reason. Resolution The User account control slider on a Windows 7 PC will need to be moved all the way to the bottom. Check/resolve for database connectivity errors. Make sure Firewall settings are not preventing the PIM from getting to the SQL server. If the problem persists try the following:   Check to see if Badgemanager.exe is starting. If not then a perform clean uninstall of EpiBuilder with the following steps: From Add/Remove programs (Programs and Features in Windows 7) Uninstall Run Regedit (Start > Run > regedit) Get a registry back by Right clicking on HKey_Local_Machine\Software\ImageWare Systems\EpiBuilder  and select Export and save the selected branch to a file location. This can be used to restore the registry key if necessary. Windows 7: HKey_Local_Machine\Software\WoW6432Mode\ImageWare Systems\EpiBuilder Right Click the same registry branch from step c and select Delete Reboot the PC Reinstall EpiBuilder by going to My Computer or Windows explorer, double click on C:\Program Files\Continuum\EpiBuilder\SDK\InstallEpiBuilder.bat Note: This runs very quickly Start Cyber and open a badge in Personnel Manager If using a VBScript File to redirect communication between principal DB server to mirror DB server, coding may need to be updated. Example: x32 vs x64 bit coding differences For x32: strRegName = "HKLM\Software\Andover Controls\Continuum\Primary Database\Server" strRegData = WshShell.RegRead(strRegName) For x64: strRegName = "HKLM\Software\Wow6432Node\Andover Controls\Continuum\Primary Database\Server" strRegData = WshShell.RegRead(strRegName)
View full article
Picard Product_Support
‎2018-09-06 01:55 PM

Last Updated: Administrator DavidFisher Administrator ‎2019-08-30 08:42 AM

Labels:
  • Andover Continuum
1720 Views

Duplicate Card Numbers in Access Expert

Issue When adding a duplicate card into Access Expert, an error is generated. Environment Access Expert Hosted Instance (cloud) Premise Windows Server 2012 SQL 2012 R2 Version 2 Version 3 Cause Existing customers who may have multiple Tenants using multiple card formats and Facility Codes run into the the problem where there are duplicate cards that may have been ordered or handled differently. In Access Expert, when the card is added an error shows up indicating that the card is already assigned and cannot be added to another person. Card offsets can be introduced in order to ensure no overlapping card number values. Resolution In order to resolve this issue, the following steps need to be followed: 1. Create a new Card Format using the same Tenant Information 2. Add a card number offset, which is added to the original value. ie. a Card Offset of 1000 would make card 100 read as 10100.   3. Save and Close 4. Reboot the controller
View full article
Picard Product_Support
‎2018-09-10 10:46 AM

Labels:
  • EcoStruxure Access Expert
1760 Views
  • « Previous
    • 1
    • …
    • 156
    • 157
    • 158
    • …
    • 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