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
    • …
    • 144
    • 145
    • 146
    • …
    • 509
  • Next »

L-IP Firmware Upgrade.

Issue Upgrading Loytec L-IP to the latest firmware or checking current firmware version. Environment Loytec L-IP Vista Network Interface Cause UL 864 v.9 for Smoke Control requires at least version 5.04 firmware in all system L-IP's. Resolution Verifying L-IP Firmware Version via Console Connection To use the serial interface, the DB9 console connector of the L-IP can be connected to the RS-232 port of a PC. The L-IP-3ECTB and L-IP-33ECTB use a standard null-modem-cable must be used to connect the L-IP’s DB9console connector to the RS-232 port of the PC. The PC will communicate with the L-IP using a HyperTerminal program with the communication settings set to 38,400 bps / 8 data bits / no parity / 1 stop bit / no handshake. The L-IP displays the console menu shown in Figure 1 upon a successful HyperTerminal connection initiated by a “enter” keystroke or power cycle of the L-IP: LOYTEC electronics GmbH www.loytec.com L-IP Configuration Menu ======================= [1] Show device information [2] Serial firmware upgrade [3] System configuration [4] EIA-709 configuration [5] IP configuration [6] EIA-852 device configuration [7] EIA-852 server configuration [8] Reset configuration (factory defaults) [9] Device statistics [0] Reset device Please choose: Figure 1: L-IP main menu. Select Option 1 to Show device information  This menu item shows information about the L-IP and the current firmware version. The output should look like what is shown in Figure 2. Product information =================== Product code: L-IP-3ECT Firmware: L-IP Primary image Version: 5.0.5 Build date: Fri Mar 18 10:41:29 2005 Serial number: 002304-80000000E73C Free memory: 557K,57K System temp: 33.3C Supply volt: 12.0V Unique Node IDs =============== Port 1: 80 00 00 00 E7 3C EIA852: 80 00 00 00 F7 92 Figure 2: Device information. (For UL 864 v9: If the Firmware Version does not reflect a Version 5.0.4 or Version 5.0.5, you must update the firmware to an approved version in the next steps. If the L-IP contains an approved version, further action is not required.) L-IP Firmware Upgrade To download the firmware via the console connected the L-IP to the RS-232 port of a PC via its console interface as outlined above. Download the lswitch_lipxxx.zip located at www.loytec.com to the PC. Install the LOYTEC serial upgrade tool (LSU Tool) by double clicking LSU_2_0_1setup.exe. Double click on the lswitch_lip_xxx.dlc file. This will start the LSU Tool and load the firmware image referenced in the . lswitch_lip_xxx.dlc file. The start window of the LSU tool is shown in Figure 3. *note that the lswitch_lip_xxx.dlc file and the lswitch_lip_xxx.dl file must be stored in the same folder. Figure 3: LSU Serial Upgrade Tool in idle mode. If the L-IP is not connected to COM1 you can change the port to COM1, 2, 3, or 4. Press “Download” to start the download. A progress bar as shown in Figure 4 can be seen. Figure 4: Progress bar during firmware download. If the upgrade is successful the following window appears (Figure 5). Figure 5: Successful firmware upgrade. Exit the LSU Tool. Reconnect through HyperTerminal connection and  initiate the console by a “enter” keystroke or power cycle of the L-IP. At the console main menu, select option [1] Show device information, and press Enter. This will bring up the current device information as shown in Figure 2, for verification that the firmware version has updated successfully.
View full article
Picard Product_Support
‎2018-09-07 06:43 AM

Labels:
  • Field Devices
  • TAC Vista
1823 Views

Where do I find our BACnet controllers BACnet PICS? (Protocol Implementation Conformance Statement)

Issue  Where do I find our BACnet controllers BACnet PICS? (Protocol Implementation Conformance Statement) Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment All BACnet controllers Cause Alternative locations to find BACnet PICS for our controllers. Resolution PICS documentation can be found on The Exchange Download Center and BACnet International website.
View full article
Picard Product_Support
‎2018-09-07 07:47 AM

Last Updated: Janeway PeterEdvik Janeway ‎2019-11-07 06:20 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • TAC IA Series
1896 Views

Vista Database Sizing and SQL Server Selection

Issue How do you determine how large a database will grow when using Vista? Which version of Microsoft SQL Server is needed? Product Line TAC Vista Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of trend logs and events should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called SQL Server Express. The size limitations are 4 and 10 gigabytes for Microsoft SQL Server 2005 Express and Microsoft SQL Server 2008 Express respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption, data loss, or inaccessible data. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Vista database, to determine which version of SQL should be used. The Vista database estimating spreadsheet takes into consideration 2 main areas: Trend Logs- total amount of logs, intervals and the number of days to retain Events- total amount of access events. The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate which version of SQL Server is needed This spreadsheet can be downloaded by clicking on the following link: Click Here Update: In Vista 5.1.7, there is a Trend Log Calculation Tool included (under Schneider Electric-Tools)
View full article
Picard Product_Support
‎2018-09-07 08:03 AM

Labels:
  • TAC Vista
1862 Views

N4 ASD (tacAsd) driver setup basics.

Issue Provides additional setup information for the N4 ASD (tacAsd) driver implementation. Product Line TAC IA Series Environment I/A Series N4 Jace 8000/9000 I/A Series N4 ASD driver Cause Configuration Guidelines Resolution N4 ASD (tacAsd) driver setup basics ...  Monitor properties Ping Enabled = true Ping Frequency = 5m change to 1m Alarm On Failure = true Startup Alarm Delay = 5m The baud rate sync properties are the mechanism that synchronizes the baud rates for the ASD bus. Upon reset, ASD devices initialize to 1200 baud, and it is this mechanism that locates those devices and sets the baud rate to 19.2K or 9.6K (if PEMs are used on the bus). These values are part of the ASD specification and should not be changed. Last Time Sync is the last time a successful sync occurred Baud Rate Sync Time = 1m Baud Rate Set Timeout = 0.2s Baud Rate Set Repeat = 1 Baud Rate Change Millis = 800 Total Devices indicates the total number of devices active. Total Down indicates the total number of down devices. Scan Time indicates the total time to poll through the list of devices. The ASD communications protocol is designed to exchange most data between the host (Jace) and device with one transaction. This means that typical data (e.g. EMS, etc.) is written to the device as part of the request and response data (e.g. Window, Output, Diagnostics, etc.) in one transaction. In this case, the scan time is 6.9 seconds for 33 devices or approximately 4.5 devices per second. Tuning Policies (Default Policy) Min Write Time = 0 Max Write Time = 0 Write On Start = false Write On Up = false Write On Enabled = false Stale Time = 0 Note: The stale time actually involves the proxy point objects. The polling mechanism still continues and the internal point information is still updated. The driver does not implement the interaction between the point updates and proxy point stale. The values should be left at their default settings. Poll Scheduler Poll Enabled = true Fast Rate = 5s (defaults to 1s) Normal Rate = 10s (defaults to 5s) Slow Rate = 30s (defaults to 30s) Typically set the Normal Rate based upon the rules specified in the R2 documentation or (Normal Rate seconds = Number of devices / 3.5). For example, a network with 33 devices would be set to (33 / 3.5 = 10 seconds). As indicated earlier, the driver inherits the basic driver properties and mechanisms. N4 implements a complex poll scheduling mechanism that automatically determines and continually adjusts the poll list to achieve the most efficient polling. Retry Count The retry is only used in the event that a response from an ASD device is not received.  This value defaults to 1 and can be increased if needed to a maximum of 3 if devices are unable to respond to the initial message and one subsequent retry,  Devices that do not respond to the initial message may indicate a potential issue with the ASD bus. Response Timeout This is the amount of time the driver will wait for a response to a request before retrying the request.  This value defaults to 2 seconds and should not be changed. Inter Message Delay This value defaults to 0 seconds.  Change to an initial value of 0.020 seconds.  This may need to be increased (typically 0.050 to 0.075 seconds) if the ASD bus includes one or more ASD bus repeaters (RPTR-WIRE or RPTR-FIBER).
View full article
Picard Product_Support
‎2018-09-06 02:00 PM

Last Updated: Guinan RandyDavis Guinan ‎2025-07-17 12:05 PM

Labels:
  • TAC IA Series
1848 Views

After upgrading the WorkPlace Tech Tool software to 5.7.x from an earlier version, and installing a new 365 day expiring license, the "License Expired" message is still...

Issue A version of the WorkPlace Tech Tool software prior to version 5.7 had previously been installed on the computer and licensed with an expiring license.  The WPT software was updated to version 5.7.x.  When the previous expiring license was about to expire, the next expiring license renewal was requested.  However, when the previous expiring license did expire, the new one also expired. Environment Initial WIBS/WPT license on computer created by installation of any version Wonderware for Intelligent Buildings Software (WIBs) or any version prior to 5.7 of the WorkPlace Tech Tool software (WPT). New version (5.7.x or later) of the WorkPlace Tech Tool software installed on same computer. Cause New license request was incorrectly generated using the WIBSPurchase ("Purchase WIB Software" icon) program instead of using the "Purchase WorkPlace Tech Software" icon on the computer desktop. Resolution Use the "Purchase WorkPlace Tech Software" icon on the computer desktop to request any license updates for version 5.7.x and newer of the WorkPlace Tech Tool software.
View full article
Picard Product_Support
‎2018-09-06 01:58 PM

Labels:
  • TAC IA Series
1830 Views

SBO is not supporting enumerated values.

Issue Binding to Security Expert values through EWS results in "Type does not exist" error when attempting to save a binding. Environment SmartStruxure Security Expert Cause The value being bound was coming through and mistakenly being created by SBO as an enumerated value which is not supported. The value is actually an integer. Resolution A hotfix has been created to resolve this in SBO 1.9.1.6700.   There is also a workaround that works for previous versions of SBO.   If you update (configure) the value type of the EWS ValueItem property Value with the system.pt.Int32 it will work to do bindings.   1. Open the propertydialog of the EWS ValueItem and click the configuration button of the Value property.    2. Check the Type checkbox which already contains the value type system.pt.Int32. 3. Press Ok and save the change in the dialogproperty. 4. Now it's ok to do bindings with this Value.
View full article
Picard Product_Support
‎2018-09-10 12:50 PM

Labels:
  • EcoStruxure Building Operation
  • EcoStruxure Security Expert
1841 Views

In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default.

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.
View full article
Picard Product_Support
‎2018-09-07 02:32 PM

Last Updated: Guinan RandyDavis Guinan ‎2023-03-23 08:14 AM

Labels:
  • TAC IA Series
1825 Views

Vista crashes when integrating with an Integral DVR

Issue When integrating a Integral DVR system Vista crashes Video does not work in Vista CCTV video loss in Vista Product Line Pelco, TAC Vista Environment Vista 5.1.3 Vista Integral DVR SDK v6.6.1.57 Integral DVR SDK v7.0.8 Cause Vista uses the same SDK as Controlpoint uses for an Integral DVR system, this mainly means that Vista SDK needs to be at the same versions as Controlpoint's SDK. A good example of this would be that Vista 5.1.3 use SDK v6.6.1.57 and Integral Digital sentry 7 use a newer version of SDK that is not compatible with SDK v6.6.1.57, a integration of this system then causes Vista to crash. An integration with Vista 5.1.3 would need Integral Digital Sentry 4.1/4.2. Please reference Vista Video Compatibility for more information. Vista 5.1.5 has SDK 7.0.8.0 and it appears that HD support was not included prior to SDK7.0.24.0 Resolution Make sure you have the correct version of Integral Digital version versus Vista version.     5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0   Integral Digital Sentry 4.1/4.2 X X X X X X           Integral Digital Sentry 7 X X    
View full article
Picard Product_Support
‎2018-09-07 10:25 PM

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

Labels:
  • CCTV
  • TAC Vista
1823 Views

ProView for LON configuration wizard installation and use with Niagara G3 and N4

Issue Provide the information required to support ProView for LON with Niagara G3 and N4 Product Line TAC IA Series Environment I/A Series G3 (3.5.34 or higher) I/A Series Niagara N4 (4.1.27.20 or higher) ProView for LON (MNL-PROV-WAL) Cause Required files for configuring the ProView for LON display with G3 and N4. Resolution Support for ProView for LON with I/A Series G3 and N4 requires the download and installation of the Distech Controls EC-NET-AX Support Package and EC-Display Configuration files.  Those files are available for download from The Exchange Download Center. Download the following files. BCS Distech Controls EC-Display Configuration v3.4.369 Setup.zip Distech Controls EC-NET AX Support Pack v4.4.17198.1 Setup.zip Unzip the files and run the executables to install the Distech Controls EC-NET-AX Support Package and Distech Controls EC-Display Configuration files. Follow the instructions to install the version(s) required. Install the Distech distribution file into the ENC (if required) using the platform distribution installer. The distribution file will be located in the Distech Controls Files directory added to G3 or N4 during the installation process. Open the distechControls palette (LonWorks - Services container) and add the LonWorksWizardService to the Services. Open the Drivers - ConfigurableControllers container and add the EcDis210 device object to the LonNetwork. Commission the ProView device using the LON Device Manager. Right-click on the EcDis210 and select Views - Ec Dis Wizard to test the wizard connection and launch the display wizard.
View full article
Picard Product_Support
‎2018-09-07 11:01 PM

Last Updated: Guinan RandyDavis Guinan ‎2023-02-23 12:17 PM

Labels:
  • TAC IA Series
1821 Views

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

Issue Satchwell ALM series Linear Actuator requires replacement. Environment Satchwell ALM series Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF Series Plug and Seat Valve Body.    Satchwell ALM series Linear Actuators. Cause Obsolescence of Satchwell ALM series Linear Actuator. Resolution Replace Satchwell ALM series Linear Actuator with MV15B-230 Linear Actuator and Linkage Kit and wire as follows :- ALM = MV15B-230 + L7SV (880-0126-000) Linkage Kit. Actuator wiring :- ALM Terminal Number 1  =  MV15B-230 Terminal Number Y2  ALM Terminal Number 2  =  MV15B-230 Terminal Number Y1  ALM Terminal Number 3  =  MV15B-230 Terminal Number N N.B. ALM power consumption  =  4.5 VA          MV15B-230 power consumption  =  12 VA operating and 15 VA Transformer sizing Should the Satchwell ALM series Actuator include a wired Auxiliary Switch (ALA1211) then the following Accessory should also be installed on the MV15B-230 Actuator as appropriate and should be wired as follows :- S2 - MV15B = Two independent 250 volt 10 amp / 3 amp rated SPDT Auxiliary End Point Switches. Auxiliary Switch wiring :- ALA1211 Terminal S1  =  S2 - MV15B Switch 1 Terminal C ALA1211 Terminal S2  =  S2 - MV15B Switch 1 Terminal B ALA1211 Terminal S3  =  S2 - MV15B Switch 1 Terminal A ALA1211 Terminal S4  =  S2 - MV15B Switch 2 Terminal C ALA1211 Terminal S5  =  S2 - MV15B Switch 2 Terminal B ALA1211 Terminal S6  =  S2 - MV15B Switch 2 Terminal A   Please check the latest catalog for current equipment.  
View full article
Picard Product_Support
‎2018-09-07 11:13 PM

on ‎2018-09-07 11:13 PM

Labels:
  • Field Devices
1842 Views

VX logging is not available in the Xenta 5xx/7xx Series running System Program version 5.15

Issue The VX logging functionality is not included in the 5.15 release. It is functioning in prior and later releases. Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause VX functionality was not included with the 5.15 release. Resolution Use a version other than 5.15 where the VX log is included.
View full article
Picard Product_Support
‎2018-09-06 01:51 PM

Last Updated: Janeway Jonas_Brissman Janeway ‎2025-04-04 06:13 AM

Labels:
  • TAC Vista
1846 Views

Sigma - Installing Web Graphics across a network.

Issue Sigma Web Graphics must be installed as an Administrator, but most users do not have these rights. Environment Sigma Sigma Web Server Cause As most network users do not have Admin rights, there is a need to install Sigma Web Graphics across the network. Resolution The following text has been provided by the Sigma programmers and should be understood by the IT professionals. First you need to create a response (answer) file Then play back the response (answer) file  in silent mode To review the InstallShield Setup Parameters.pdf, please Click Here.
View full article
Picard Product_Support
‎2018-09-09 05:19 PM

Labels:
  • Satchwell BAS & Sigma
1810 Views

TAC Menta Advanced Memory Usage: BPR Size Calculator

Issue In TAC Menta, under Options > Memory Usage > Advanced, there is a BPR size calculator.  What is a Network Neighbourhood (BPR file) and what does this calculation mean? Product Line TAC Vista Environment TAC Menta Xenta 281 Xenta 301 Xenta 401 Cause The total amount of memory consumed in a programmable controller includes Application and Application Files Parameters Work Area Number of Objects FBD (COD file) OP Menu Tree (BIN file) National Character Set (CHR file) Network Neighbourhood (BPR or Blueprint file) Trend Log Definitions (XLG file) Resolution The BPR is the blueprint file. It contains:  The TAC Xenta network name All TAC Xenta group names The TAC Xenta's own group's members' names The TAC Xenta's own I/O modules' info The BPR is unique for every single TAC Xenta device. This information is created by Vista and included with the TAC Menta images just before download of the Xenta. So this file is not saved anywhere as a separate file. The information is downloaded and does consume memory inside the TAC Xenta controller, however, so the BPR calculator is included to approximate how much room might be required to store the network descriptions for this specific TAC Xenta device. Where memory is close to filling the controller, it can provide more accurate estimates of which applications will fit into the controller.
View full article
Picard Product_Support
‎2018-09-06 01:50 PM

Labels:
  • TAC Vista
1856 Views

Using BACnet Multistate points within Continuum

Issue Using BACnet Multistate points within Continuum Environment Continuum BACnet Cause Can't use Multistate points values to trigger graphics or other objects Resolution A third Party Multistate BACnet object needs to be mapped to a Continuum Infinity Numeric before it can be read as number. A third Party Multistate BACnet object may be read as State 1, State 2, state 3 or On, Off, -On or other values These should be either mapped to Infinity Strings or Numerical to be displayed or measures as required. eg. ContinuumNum = BACnetFullPath\PointName (if a number is required) Then a ContinuumString can be set based on the ContinuumNum value if the text read from the third party point requires modifying. Other MultiState Bacnet Notes When setting the value of a third party Multistate Bacnet Objects eg "Heat", "Cool", "Auto", "Off", try using an integer ie WriteProperty(Bacnet Object, 4, 1) rather than WriteProperty(Bacnet Object, Heat, 1) Note: Some 3rd party bacnet devices default their multi-state values to 0 instead of 1. Cyberstation will not accept a default value of 0. Get the 3rd party vendor to set the default to 1 if possible.
View full article
Picard Product_Support
‎2018-09-06 01:47 PM

Labels:
  • Andover Continuum
1874 Views

Can external inputs (momentary switches or other momentary device such as a proximity detector) of LO-2 be configured as a regular inputs of the LO-2 module, and can it be used a...

Issue Wants to have LO-2 with external momentary input switch works with schedule object of Continuum. Such as, when the input is ON and the schedule is ON then the PE program turns the lighting output to ON. Environment NetController(CX99xx & CX9680) IOU module (LO-2) Cause LO-2 provides 2 inputs (the 2 Class II Low Voltage override inputs) for direct control of lighting relays but no input signals are not available on LO-2 or NetController.  Resolution Use other input IOU modules such as UI8 or DI8 for the lighting control switch input, and create a PE program to check the input together with the schedule numeric value before turning the lighting control output value to ON or OFF.
View full article
Picard Product_Support
‎2018-09-06 01:46 PM

Labels:
  • Andover Continuum
1876 Views

Force Xenta Server to write Modbus register with multi register function code (10 hex - 16 dec)

Issue Modbus slave device only supports function code 10 hex/16 dec for writing of holding registers. Environment Xenta 913 Xenta 701/711/721/731 Xenta 511/527 Cause In system program 5.1.4 a trigger was added to the Xenta Server software that enables the device to use only the Multi-Register function code. This command is executed from the console port or from the VXI web shell command webpage. VX M 1 = Enable Multi-Register write VX M 0 = Disable Multi-Register write VX M = Display current status of the trigger Note: This setting is persistent on the unit until the firmware has been reloaded. If the unit is upgraded the setting will need to be reapplied. Resolution Log In to the webpage of the Xenta Server Access the Utilities\Target System\VXI Web Shell Commands webpage. Issue a "VX M" command to display the current status. Issue a "VX M 1" to enable the multi register write command option. Some of the Xenta Servers with recent Modbus support do not have the VXI web shell commands web page and the console will need to be used instead. The VXI web shell commands web page should be available in firmware 5.1.6.
View full article
Picard Product_Support
‎2018-09-06 01:47 PM

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

Will Continuum communicate with a third party system?

Issue What X Drivers are available? Environment All Continuum controllers that support X Drivers (XDrivers) 3rd Party interfaces Cause How to find out what standard X Drivers are available to integrate with Continuum controllers. Resolution The Third Party Communicates Interface and Protocol Brochure can be found on The Exchange Download Center that lists all available X Drivers and product compatibility. Also all of these listed drivers are available for download from The Exchange Download Center here for use on X Driver enabled controllers. Should a new driver development be required, or other special interface; then you can contact the team that develop X Drivers: Adam.Summers@Schneider-Electric.com You will need to provide protocol details if you require a quotation.
View full article
Picard Product_Support
‎2018-09-10 06:23 PM

Labels:
  • Andover Continuum
1817 Views

Can not enter the unlock code in WorkPlace Tech Purchasing Software, the "Unlock" button is grayed out.

Issue Can not enter the unlock code in WorkPlace Tech Purchasing Software, the “Unlock” button is grayed out. Environment WorkPlace Tech Tool software, release 5.7 or newer Cause WorkPlace Tech Purchasing Program was not properly closed after the codes were generated.  The Purchase program was closed using the “X” button, not the “Done” button.  Registry and file information does not get saved to the computer when the purchase program is closed using the “X” button. Resolution Re-run the purchasing program and select the same options. This time close the purchasing program using the "Done” button, not the “X” button.
View full article
Picard Product_Support
‎2018-09-06 01:43 PM

Labels:
  • TAC IA Series
1853 Views

Replacement of Satchwell "AMS" or "AMSH" (high torque) series Spring Return Rotary Actuator

Issue Satchwell "AMS" and "AMSH" series Spring Return Rotary Actuator requires replacement by S-E M700 Spring Return Linear Actuator due to obsolescence. Product Line Field Devices Environment Satchwell "AMS" series Spring Return Rotary Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body. Satchwell "AMSH" series Spring Return Rotary Actuator installed on Satchwell MZF or VZF series 125mm and 150mm Plug and Seat Valve Body. N.B. Where a Satchwell "AMS" series Spring Return Rotary Actuator is installed on a Satchwell VV Butterfly Valve Body then NO simple Actuator replacement is available. See Replacement of Satchwell V V series Butterfly Valve Body Cause Obsolescence of Satchwell AMS and AMSH series Spring Return Rotary Actuator. Resolution The new actuator is 24Vac and the control signal will need to be converted from 230Vac to 24Vac, this could be achieved by a transformer and 2 off 230Vac relays. The old signals switch the coils of the relays. The relay contacts switch 24Vac to the new actuator. Replace Satchwell AMS or AMSH series Spring Return Rotary Actuator with S-E M700 Spring Return Linear Actuator and Linkage Kit: AMS = M700 + L7SV (880-0126-000) Linkage Kit. N.B. M700 is available with two different spring return actions M700 - SRSU (880-0430-000) = Spring Return Spring Up          ( M700 - SRSU will CLOSE a Satchwell Valve.) M700 - SRSD (880-0440-000) = Spring Return Spring Down     ( M700 - SRSD will OPEN a Satchwell Valve.) Should the Satchwell AMS series Actuator include a wired Auxiliary Switch then the following S-E M700 Actuator specifications which include 2 independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches should be considered as appropriate: M700 - S2 - SRSU (880-0431-000) M700 - S2 - SRSD (880-0441-000) Alternatively Auxiliary Switch Pack S2 (880-0104-000) - Two independent 24 volt 4 amp AC-1 rated SPDT Auxiliary End Point Switches may be purchased separately permitting local installation. Particular care should be taken when selecting a TAC Forta M700 Spring Return Actuator to replace an existing Satchwell AMS Spring Return Actuator. Please refer to Replacement of Satchwell "AL..S" series Spring Return Linear Actuator. Please check the latest catalog for current equipment.
View full article
Picard Product_Support
‎2018-09-10 12:04 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-10 02:03 AM

Labels:
  • Field Devices
1841 Views

How does controller part number relate to the controller type

Issue How does controller part number relate to the controller type Environment Continuum 1.7 onwards for bCX Continuum 1.74SP2 onwards for NC2 Cause Require details on Controller type, these detail are available in the Operation and Technical Reference Guide Resolution Part Number Type NC2  9680 bCX1-R-?? 4000 bCX1-CR-??? 4040 bCX1-CR-???-INF 9640 The actual type can be confirmed by logging on to the controller web page Full details from relevant guide CX9680 NetController II with optional Network Security code linked with firmware, although the code may not be activated at run-time. This option provides secure, encrypted communication between the controller and a workstation. CX9681 NetController II without optional Network Security code linked with firmware. bCX4000 BACnet Router and BBMD only .. bCX1-R-64 = 64 MS/TP Nodes No xP module support No PE Driver support BACnet/IP, BACnet/Ethernet bCX4040 BACnet controller with MS/TP Bus xP expansion bus for up to 2 I/O modules + 1 Display module 1 MS/TP port and 1 RS232 port BACnet limitations are indicated by the bCX1 part number, and include: .. bCX1-CR-0 = 0 MS/TP Nodes .. bCX1-CR-8 = 8 MS/TPNodes .. bCX1-CR-32 = 32 MS/TP Nodes .. bCX1-CR-64 = 64 MS/TPNodes .. bCX1-CR-127 = 127 MS/TP Nodes .. bCX1-CR-0-SA = 0 MS/TP Nodes w/SMNP Alarming .. bCX1-CR-8-SA = 8 MS/TP Nodes w/SNMP Alarming .. bCX1-CR-32-SA = 32 MS/TP Nodes w/SMNP Alarming .. bCX1-CR-64-SA = 64 MS/TPNodes w/SMNP Alarming .. bCX1-CR-127-SA = 127 MS/TP Nodes w/SMNP Alarming bCX9640 Full function controller with Infinet Bus xP expansion bus for up to 2 I/O modules + 1 Display module, 1 Infinet and 1 RS232 port Infinet bus limitations are indicated by the bCX1 part number, and include: .. bCX1-CR-0-INF = 0 Infinet Nodes .. bCX1-CR-8-INF = 8 Infinet Nodes .. bCX1-CR-32-INF = 32 Infinet Nodes .. bCX1-CR-64-INF = 64 Infinet Nodes .. bCX1-CR-127-INF = 127 Infinet Nodes .. bCX1-CR-0-INF-SA = 0 Infinet Nodes w/SMNP Alarming .. bCX1-CR-8-INF-SA = 8 Infinet Nodes w/SNMP Alarming .. bCX1-CR-32-INF-SA = 32 Infinet Nodes w/SNMP Alarming .. bCX1-CR-64-INF-SA = 64 Infinet Nodes w/SNMP Alarming .. bCX1-CR-127-INF-SA = 127 Infinet Nodes w/SNMP Alarming The bCX can have XDrivers on comm1, comm2 or both ( add -X1, -X2 or -X12)
View full article
Picard Product_Support
‎2018-09-06 01:40 PM

Labels:
  • Andover Continuum
1881 Views
  • « Previous
    • 1
    • …
    • 144
    • 145
    • 146
    • …
    • 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