Notifications

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Building Automation Knowledge Base

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

Invite a Co-worker

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

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue Need help with programming Need help to make graphic Installation questions Forum Environment BMS Security Video Cause A great way of getting help with various application programming and graphic making is to spread knowledge between all the great technician out there. A forum exist for this and people worldwide that works with SE Solution share their knowledge here. Resolution Please enter the forum by the link below. http://community.se.com/welcome

Issue Created a BACnet digital output under the BACnet Interface in the Automation Server but the Out of service property indicates 'True' and get the error 'Property value out of range' when attempting to set the out of service to false. Product Line EcoStruxure Building Operation Environment WorkStation Automation Server - AS BACnet Interface Cause BACnet output must be associated with an IO Bus output. Resolution See Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above for instructions on setting the associated value.

Issue What are the differences between the IAC 400 and the IAC 420 controllers? Product Line Field Devices, Other, Satchwell MicroNet, Satchwell Sigma Environment IAC 400 IAC 420 Cause The IAC 400 controller is obsolete and its replacement is the IAC420. Resolution Hardware differences; The IAC 400 has 3 Temperature, 2 Analogue and 1 Digital input, where as the IAC 420 has 6 Universal inputs. Communications differences; The IAC 400 controller uses terminal 3 to earth the communications cable screening, on the IAC 420 the screening must be connected to a good earth and not terminal 3. Tables and offsets; Because the IAC 420 has different inputs that tables and offsets are changed, please review IAC Controllers - Tables and Offsets. IAC 400 Wiring details. For the full data sheet please click HERE. IAC 420 Wiring details. For the full data sheet please click HERE.

Issue When installing the TAC Vista OPC server it doesn't show up as a Windows service like it should. Product Line TAC Vista Environment TAC Vista OPC Server Cause A valid license for the TAC Vista OPC server must be installed before installing The OPC server. Resolution Uninstall the OPC software Install a valid license for the TAC Vista OPC server. Reinstall the OPC software For more OPC Server issues please see Vista OPC Server Installation and Known Issues.

Issue When a MPM is replaced on a BACnet IP network, a "Duplicate network identifier" alarm is generated Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment MPM Automation Server Cause If the BACnet name and instance number in the new controller is not exactly the same as the original MPM, the Automation Server will consider that an additional device has been installed and an alarm will be triggered stating that the new device has the same BACnet ID as an existing device. Resolution Steps to replacing a MPM to prevent the Duplicate ID alarm being triggered: When replacing the original MPM, note the BACnet name and Instance ID. Install the new MPM and enter the same BACnet name and Instance ID. Refer to BACnet device can't be discovered due to duplicate name for more information about duplicate BACnet names.

Issue Update to available documentation. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Windows 7 32/64 bit Cause Clarification of supported communication protocols and devices. Resolution Computer running Windows 7 32bit or 64bit. Visio software installed must be 32 bit version. VisiSat runs as a 32 bit application. SNP Via computers RS232 communications port. Via RS232 provided by USB to RS232 converter. Via RS232 provided by PCMCIA card to RS232 converter. Via RS232 provided by Express card to RS232 converter. IP tunneling through Xenta 555/731 AS/AS-P LAN network. Remote site connection. NCP Via computers RS232 communications port. Via RS232 provided by USB to RS232 converter. Via RS232 provided by PCMCIA card to RS232 converter. Via RS232 provided by Express card to RS232 converter. IP tunneling through LAN network. Remote site connection. ARCnet Via computers RS232 communications port connected through null modem lead to an MicroNet Interface Unit. (MN50-MI-ARC). Via PCI120U-485 PCI card (This card was made by Contemporary controls but is no longer). The card was replaced by the USB22 Series. (USB 2.0 to ARCNET adapters) These USB22 adapters do not work with VisiSat. IP tunneling through LAN network. Remote site connection. LON Not supported with Windows 7 64bit or 32bit. The latest documentation for VisiSat can be downloaded, see Download latest VisiSat Data Sheets, Engineering Guides, Installation and User Guides, and Release Notes.

Issue Use of the Plain English programming environment and general Plain English programming is covered in the Training courses, what other techniques can be used to debug a program. Product Line Andover Continuum Environment Plain English Integrated Development Environment Cause Often additional techniques are required to debug Plain English, especially when attempting to analyze, modify or fault find other peoples code. Resolution Some techniques you can use for debugging your program and isolate problems are: Add in additional line labels to the program to isolate where the program is disabling or failing, if it disables you will be able to see the "CurrentLine" it has failed on and therefore know which line of code is causing the problem. Even if a program does not disable you can use the "Stop" keyword in the program it will act as a break in the code and you can look at the values of the various variables, that should tell you what value could be at 0. Use the Watch window to show the values of the various objects, when used with the above 2 techniques it allows you to accurately trace a program flow. Temporarily create local variables as actual points and comment them out from the assignment at the top of the program, this allows you to use the Watch window to see the points values. Revert them back to local objects when debugging is complete. Ensure none of the Program size limitations as defined in Plain English program limitations on number of characters in program and line labels are exceeded.

Issue What are the limitations of Building Operation Web Services? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Version 1.3 Cause Due to the XML response rate (XML file information send to Building Operation), it has some limitations. Resolution General Guide in the Technical Reference Guide: The limit for the whole XML response is 100 kb, which includes manually created values. The limit for a string value is 10 kb, which includes manually created values. The maximum number of values created in the Web Server interface is 200. The recommended limit for XML elements in the Web Service interface is 100 The recommended number of Web Service interfaces in an Automation Server XML elements at a polling rate of 60 seconds. is 2. Additional Information: Maximum number of Web Services in an Automation Server Also refer to Architectural Guidelines for your respective version in use.

Issue Vista locks up randomly and displays application crashes. Investigating the Windows Event log shows the following errors pointing to tacldv32.dll. For more information on Windows Event Log, see Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Faulting application tacos.exe, version 0.1.0.0, faulting module tacldv32.dll, version 1.0.0.1, fault address 0x00007310 Product Line TAC Vista Environment Vista Server LNS Communication Port Large LNS network, or many smaller LNS networks Orion Stack Cause The DLL file, tacldv32.dll, is responsible for managing communications through an LNS communication port. If that is being overwhelmed with information from too many devices on the port, this DLL will crash. If the number of networks is only one and the database size is reasonable then the problem can be caused by a corrupted and non functioning LNS database.See Also Echelon LNS Utilities LNS Database Validator. Resolution If the number of networks is high then LNS communication must be managed by an Orion Stack, or NIC-852. This does not utilize tacldv32.dll and will stop the application crashes. If the number of networks is low, but the size of the networks is quite large, then it is also advisable to allow the Orion Stack to manage communication and will prevent the application crashes. If the number of networks is low and they are not very sizeable, then ensure that LNS database is working properly independently of Vista Server. If it has problems, investigate the LNS problems further, looking for any errors that can be searched on other articles. *Note that if you receive the tacldv32.dll error and are currently using an Orion Stack or NIC-852. There is a problem with the Orion Stack or NIC-852 installation or configuration. Hovering the mouse over the Communication Port objects in the TAC Vista Workstation should produce a pop-up window stating "Loytec Port". If it says "LNS Port", there will still be a need for using tacldv32.dll resource.

Issue Various issues have been observed regarding the use of the I/A Series R2 WorkPlace Pro or I/A Series G3 Graphics access. The following is a partial list of known issues caused by the Ethernet firewall built into the Trend Micro Internet Security Suite software: When attempting to install an R2 UNC license using the Admin Tool, the error "Unable to install license" is displayed. When attempting to connect to a UNC from the WorkPlace Pro tree, a "Cannot connect" error occurs. When attempting to access G3 graphics using the web browser, the user is unable to log into the station serving the graphics. When attempting to access R2 graphics using the web browser, the user is unable to display the graphics pages. When attempting to paste a .gif file to a UNC's remote library, WorkPlace Pro stops responding and must be closed with Windows Task Manager. When attempting to open a local station on the computer, using WorkPlace Pro, the Windows hourglass is displayed and the station never opens. This list will be updated as additional issues are encountered. Environment Computer running "Trend Micro Internet Security Suite" I/A Series R2 (Niagara) WorkPlace Pro software or attempting to use the computer to view I/A Series G3 (Niagara) graphics. Cause The I/A Series R2 software requires bi-directional communications over Ethernet port 80 unless the software has been user-configured to use a different Ethernet port. The Trend Micro Internet Security Software Suite has a built-in firewall that blocks incoming access to Ethernet port 80. The Trend Micro software does not allow this port to be unblocked because it considers web access to a "workstation class" computer as a security risk. Resolution The best solution to this issue is to use a different Internet Security software package on the computer that does not block the use of Ethernet port 80. One approach is to use the "Server" version of Trend Micro Internet Security instead of the "Workstation" version. Since port 80 is typically used on server systems as the IIS (Internet Information Services) access port, the Server version of the software does not block that port. The alternate solution is to configure the I/A Series R2/G3 (Niagara) software to use a different Ethernet port for HTTP communications and Web services. This change would need to be made in the R2 or G3 software installed on the computer as well as in every UNC or ENC being accessed from this computer. See New installation of the I/A Series (Niagara) R2 WorkPlace Pro software cannot connect to existing UNC for more information.

Issue Can the Text Font size be changed on Listviews, Reports, EventView, Active Alarm Window Product Line Andover Continuum Environment Continuum Cyberstation Cause Trying to change the font size Resolution Listview - Most Font attributes/styles can be changed but the Font size adjustment is greyed out EventView - Most Font attributes/styles can be changed but the Font size adjustment is greyed out ActiveAlarmWindow - Most Font attributes/styles can be changed but the Font size adjustment is greyed out Report - Text Font is not adjustable Groups - Some adjustment of Font are possible For EpiBuilder see Adding fonts to EpiBuilder or EpiDesigner

Issue "invalid data on _schedule address_" error when downloading application Environment Xenta Programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause This error can occur when the time schedule data has become corrupted in the Xenta programmable controller. Resolution To fix the controller either: Clear the MTA file by using the clear application process (see Xenta Controller Will Not Download / How to Clear the Xenta Application for more information) Download the MOT file and empty the application memory (see Instructions on how to download an .MOT file into a Xenta Programmable controller for more information).

Issue System alarm message, Physical device not defined/configured, in the alarm window. Product Line TAC Vista Environment TAC Vista (all versions) TAC Xenta programmable controllers Cause This message is displayed when there is a TAC Xenta 401/30x/28x that is attached to the physical network, but the name is not in the TAC Vista database. It is there to alert that there are unconfigured controllers on the network. Resolution Download to the controller from TAC Vista Remove the controller if it is not needed. For an alternative cause and resolution for the message, see Physical device not defined/configured.

Issue "Controller doesn't know Infinet Id" error when attempting to share data from a BCX9640 to a b3 under a BACnet BCX 4000 Product Line Andover Continuum Environment BCX9640 b3 BCX4000 Cause A program that is attempting to map a point value from a BCX 9640 to b3 under a BCX 4000 receives a program error "Controller doesn't know Infinet Id." The infinity protocol does not get routed. Resolution The BCX4000 must be upgraded to a BCX4040 by requesting this from repair. Follow Share data between standard Continuum controllers and Continuum BACnet controllers to get the best performance.

Issue CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output, but the Xenta 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. If replacing the sensors would be too costly and time consuming, this is a viable option that will allow you to drop the voltage output on the CO2 sensor using 1000 ohm resistors. Product Line TAC Vista, EcoStruxure Building Operation Environment 102-AX Cause CO2 sensors have been installed on the VAV boxes that have a 0-10 volt output but the 102-AX is limited to reading 0-5 volt output using the Universal Inputs on the controller. Resolution NOTE: It is recommended that the incorrect sensors be removed and replaced with new sensors that have the proper specifications to match the 102-AX capabilities. If the sensor replacement is not an option please follow the instructions below. Please see the image below: You will need (2) 1000 ohm (1k) resistors to complete this conversion. Wire one resistor directly to the output wire of the CO2 sensor Land that resistor to U3 on the 102-AX Jump a second resistor from U3 over to M on the 102-AX Land the other output wire from your CO2 sensor on M with the jumped resistor Also see Using a 4-20mA CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 4-20mA CO 2 sensor input on Universal Input 3.

Issue How many MSTP networks can you connect to an Automation Server (AS or AS-B)? Product Line EcoStruxure Building Operation Environment Version 1.3 and newer MSTP Network on an StruxureWare Building Operation Automation Server (AS or AS-B) BACnet MSTP Devices Cause Require 2 separate MSTP networks, either to use 2 different Baud rates or to speed up the network and split the devices across the 2 ports. Resolution You can create 2 separate MSTP networks under the BACnet interface of an AS-B or AS (version 1.3 or higher), one on Comm A the other Comm B. Each can run at different Baud rates if required. For the number of supported devices please reference, Maximum number using StruxureWare Building Operation (Scalability and Capacity). Please be aware that the listed maximum is for the Automation Server allowing you to distribute between the two comm ports.

Issue HID PIN Pad reader for I/NET Part NumberHID PIN Pad reader for I/NET Part Number Product Line TAC INET Environment I/NET Access Control Cause HID PIN Pad reader for I/NET and which part number to use? Resolution iPortal shows several PIN pad readers from HID (HID-6136CKD000214 HID-6136CKD000009) but only one works with I/NET. Here is a pdf document which helps to explain which part number works with I/NET. The 09 means the 8 bit blast which is required for compatibility. Want to use Pin Pad only without using the proxcard? The RK40 will do Prox only or Prox + Pin but not Pin only. See Essex Pin Pad Reader programming for Pin Only or for higher security Pin Only see Code-Guard Scramble Pin Pad Reader Programming.

Issue Downgrading an UNC to an earlier Niagara build Product Line TAC IA Series Environment I/A Series R2 Universal Network Controller (UNC) Cause Station is unable to run in an UNC with newer version of Niagara R2 because a 3rd party module does not have an updated JAR file Resolution The procedure to downgrade an UNC would be to use the version of WorkPlace Pro that you want the UNC to be and commission the UNC as per what you would do for a new UNC or to upgrade an UNC. The modules installed in the station should also match the Niagara version of the UNC. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330?. Refer to Procedure 4 on pages 9 and 10 of the UNC-520 Installation Instructions for details on installing the software to an UNC-520. It is important to note that newer UNCs with the newer boot flash chip requires I/A Series R2 version r2.301.527 or newer. Installing the UNC with newer boot flash chip with an I/A Series R2 version lower than r2.301.527 will make the UNC inoperable. Refer to Cannot get my I/A Series (Niagara) R2 UNC to boot after downgrading the system software to a version earlier than release 529 for details.

Issue Adding an object to an already opened Trend chart does not work correctly. Product Line EcoStruxure Building Operation Environment Webstation Open chart Adding objects Cause An AS or ES is logged into using a Webstation, and an existing Trend chart is opened. An object is then selected in the System Tree, and then using the right-hand menu, the "Open Chart" and "Add to already open chart" is selected. Values are not added to the already opened chart. This issue is caused by a Java 7 update 51 a specific fix is not available. Resolution Possible workarounds; Use an earlier version of Java. Change Java security level to Medium. Add site to the exception list For further details on "adding to the exception list", refer to Webstation graphics not working after Java updated to Java 7 update 51.

Issue Sigma Release Notes. Sigma Upgrade Information. BAS Upgrade Information. Product Line Satchwell Sigma Environment Sigma, BAS Cause Where are the release notes available from? FAQ's regarding the upgrade of BAS to Sigma. FAQ's regarding the upgrade of previous releases of Sigma to the later releases of Sigma. Resolution Sigma release notes are available from The Schneider Electric Exchange Extranet TThe Sigma 4.08 release note can be downloaded here. For upgrade information, see How to upgrade a BAS system to Sigma.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

BMS Application assistance

BACnet output point under the BACnet Interface of Automation Server indicates out of service

Differences between IAC 400 and IAC 420 controllers

After installing TAC Vista OPC server it does not show up as a Windows service

Duplicate ID alarm when replacing a MPM on BACnet IP

Supported communications options when running VisiSat software on Windows 7

Techniques to debug Plain English programs

StruxureWare for Building Operation Web Services Limitations

Vista lock-up caused by tacldv32.dll crash

"Trend Micro" Internet Security Suite causes communications issues with I/A Series R2/G3 (Niagara) software

Can the Text Font size be changed on Listviews, Reports, EventView, Active Alarm Window, Groups

"invalid data on _schedule address_" error when downloading application

System alarm message, Physical device not defined/configured

"Controller doesn't know Infinet Id" error when attempting to share data from a BCX9640 to a b3 under a BACnet BCX 4000

Using a 0-10 volt CO2 sensor with a Xenta 102-AX

Can 2 MSTP Networks be connected to the same Automation Server?

HID PIN Pad reader for I/NET Part Number

Downgrading an UNC to an earlier Niagara build

Adding an object to an already opened Trend chart does not work correctly in Webstation

Sigma release notes and BAS upgrade information

Building Automation Knowledge Base

Related Forums

This is a heading