Building Automation Knowledge Base

Issue The last 4 inputs on a SCU1280 unit are not working properly. Product Line TAC INET Environment SCU 1200, SCU 1280, SCU 1284 Cause The controller is in single address mode.  Resolution The last 4 inputs are activated by making the SCU1280 a 2 station (dual address) unit. Try turning on Dip Switch 6 and see if these inputs start working.   For more information, see SCU dip switch 6 for dual station addressing. 

Issue Does TAC Vista Support MySQL Server? Product Line TAC Vista Environment TAC Vista MySQL Cause User may wish to integrate TAC Vista with a MySQL installation for access to data or reporting. Resolution TAC Vista can not support MySQL Server. It only supports various types of Microsoft SQL Servers. For details, please refer to the compatibility matrix which is available on Exchange Extranet, or refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation.

Issue Steps to remove I/NET Seven software and SQL database from a stand-alone PC, then install a later version of I/NET Seven Product Line TAC INET Environment I/NET site Cause Need to replace existing I/NET software on a computer. Resolution Remove I/NET Seven and MSDE using the Add & Remove Programs utility in Windows Control Panel. Go to Windows Explorer and delete the I/NET Seven and SQL Microsoft Server folders. Go to the Icon called “My Computer” / Manager / Local Users / User / and delete the file called “INMProxy”. Empty the Windows Recycle Bin before beginning the new install. Check compatibility by using Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue Does Continuum support Windows Server 2012? If not, are there plans for supporting this in a future release? Product Line Andover Continuum Environment Continuum Windows Server 2012 Windows 8 Cause Unsure of the roadmap for support for Windows 8 and Windows Server 2012. Resolution The current version of Continuum (v1.94) only supports up to Microsoft Server 2008 R2 (SP1). The next release of Continuum may support MS Server 2012 if that is the OS commonly available at the time the product is qualified. Update from Marketing "Today the support for Windows 8 and Windows Server 2012 is under investigation both from Technology and Market/IT adoption perspective; hence at this moment no timeline nor any commitment for its support can be provided" This won't be addressed until the OS becomes adopted more by the general market. For details on supported Operating Systems for Continuum, consult the Compatibility Matrix link found in Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue Can the Continuum OPC Server be configured to run as a service to enable the application to start without a user having to log on to the relevant machine? Product Line Andover Continuum Environment Continuum OPC Server Cause Need to have OPC Server running without requiring a user to logon to Windows to start the application. Resolution The OPC Server can not be run as a service. It can only be run as an application which will require a user to logon to Windows and start the application.  See OPC Server further information on OPC Server.

Issue When adding a workstation to be used for security can I use a SEC version of the software even though other workstations have Integrated (INT) security keys for HVAC parts of the system? Product Line Andover Continuum Environment Continuum Workstation and Web Client all versions Security Key Dongle Cause Mixing Security key options on different workstations could have undesired effects. Resolution It is not recommended to mix the security key options on different workstations, Continuum uses the Security levels to determine exactly what information a User can see or change. So any system user should be able to log onto any workstation in the system and see the same information. All Keys should also support the same I/O point count and Cyberstation version to operate correctly. An exception to this may be the badging option -B that may only be required on certain workstations. See What are the different options on the CyberStation security key? for a full list of options.

Issue A numeric has been created and has its Setpoint attribute = true.  Its value is being calculated and set by a Plain English program.  When the controller is reloaded the numeric assumes a different value than expected. Product Line Andover Continuum Environment All controller CX ACX BCX b3 i2 Cause The setpoint attribute is designed to restore the point value that is stored in the ContinuumDB.  The database does not know when changes are made to the points value by a Plain English program since this occurs at the controller level and not at the database level.   Resolution The setpoint attribute is not designed to restore last calculated value to a point on reload of a controller. Note: For a possible workaround to this involving Plain English programming see How to save array information to a Database so that values are not lost when reloaded.

Issue Is serial tunneling, using XPSI to Network 8000 controllers, possible through an Automation Server? Environment Automation Servers (all revisions) Cause Remote connectivity to Network 8000 controllers in a building is a desired feature Resolution There is no serial tunneling with XPSI available from Schneider-Electric. The Communities website may offer an option:  https://community.se.com/message/19507?commentID=19507?sr=search&searchId=b7102b14-5f13-4971-8a5d-ef0a0e591271&searchIndex=2#comment-19507

Issue Sometimes it is required to gather a trace log between the I/Net USB adapter and the AS or AS-P it is connected to for deeper troubleshooting investigation.  Product Line EcoStruxure Building Operation Environment Automation Server  Automation Server Premium  Workstation  Cause The I/Net adapter trace log may be requested by Product Support to help identify problem experienced in the field.  Resolution How to collect the I/Net interface adapter trace log In the Workstation System Tree, go to System > Modules > Trace > Loggers > nsp > nsp.pin > nsp.pin.inet-nsp.pin.inet.IoPort Right click on nsp.pin.inet.IoPort and go to properties. Under the Basic tab > Settings > Level, set the Level to Trace. Click OK.  Let the system run for the desired amount of time (usually 10-15 minutes). To collect the log, in the system tree go to System > Modules > Trace > TraceSettings Right click on TraceSettings and select Trace Settings and then Get trace log. Finally go back to System > Modules > Trace > Loggers > nsp > nsp.pin > nsp.pin.inet-nsp.pin.inet.IoPort, right click on nsp.pin.inet.IoPort and go to properties.  In properties under the Basic tab, change the Level back to Information.    Parse the Trace Log You can use the TAC INET LANMon Decoder tool found on the Community site. 

Issue Adding a Xenta Programmable Controller to an NL220 System Product Line TAC Vista Environment NL220 Cause Commissioning a Xenta programmable controller in NL220 needs to follow a certain procedure in order to prevent various issues from occurring, such as controllers not showing online in Vista Workstation, etc. Resolution Adding a Xenta Programmable Controller to an NL220 LNS system. Preparation: Create the Menta File Install the Controller Adding the Device to the LNS database NL220:Create a Template for the device type. See NL220 Useful Functions and Shortcuts on how to create a template. NL220:Add a node using the correct device Template System plug-in: Assign Neuron ID and Menta file Add and match I/Os if applicable Bring the Device to the Vista Database System plug-in: Update TAC Network Drag controller to an existing group if desired, and delete the now empty group  Create group bindings Assign Neuron ID for the I/O modules Update the TAC Network again Check TAC Network Update Vista Database Check that your network is attached and OnNet  Download Application and Parameters Bring Vista Db online NL220: Commission and download the device (ignore I/O modules.) System plug-in: Commence Communication (if needed) NOTE:  It is very important that you Download Application and Parameters in the Vista system plug in THEN Commission the device in NL220. 

Issue When using the LOYTEC NIC709-USB100 LON Interface every time an attempt is made to connect to an MNL controller via WorkPlace Tech 5.X it gives an error "installing device driver" and causes the PC to lock up. Product Line TAC IA Series Environment WorkPlace Tech 5.x Loytec NIC709-USB LON interface Cause WorkPlace Tech 5.x is not compatible with Loytec LON interfaces. Resolution Only Echelon LON interfaces are supported in WorkPlace Tech 5.x due to it utilizing the Echelon Open LDV driver. The WorkPlace Tech installation instructions notes the following as part of the hardware requirements:- Echelon™ LonTalk™ adapter card, WPA-LON-x. Since many newer notebook computers do not have a PCMCIA card slot and therefore must use a USB LON interface an Echelon U10 USB interface (75010R) can be utilized. Also see Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for an adaptor that can be used to convert PCMCIA to Express card.

Issue What LAN is at the top of the I/NET structure? Product Line TAC INET Environment I/NET Site Cause What LAN is at the top of the I/NET structure? Resolution The Ethernet LAN is at the top of the I/NET structure and can be used to connect multiple host workstations, via TCP/IP (TCON 209, 1-3). Refer to Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication for further information.

Issue There are two sets of terminals on the Xenta Repeater that are labeled identically. Product Line TAC Vista Environment Vista Lon Network Cause The duplicate power supply and communications terminals are internally connected. Resolution The power supply and communication connections can be made either to the upper or the lower terminals as they are internally connected. The extra set of terminals is strictly for convenience purposes. One segment of the Lon network should be connected to the COM1 terminals and the other segment should be connected to the COM2 terminals. The only other wiring required is to connect the Xenta Repeater to a 24V power supply. Wiring Example #1 This is the most traditional wiring schematic used with a Xenta repeater. Segment #1 comes into COM1 and is the end-of-line for a bus topology. A terminator is placed at the repeater. Segment #2 continues on out of COM2, and represents the beginning-of-line for the next segment, thus is also terminated at the repeater. Wiring Example #2 This example is actually the same as Example #1, but is showing that the upper or lower terminals can be used for convenience, as they have electrical connectivity from top to bottom. Wiring Example #3 Example #3 shows Segment 1 coming into COM1 on top and carrying on out of COM1 on bottom. This segment does not get terminated at the repeater because it is not the end of line for this segment. However, COM2 does represent the beginning-of-line for the second segment, and is therefore terminated at the repeater.     For more information on how the Xenta Repeater works see the following article: The Xenta Repeater provides signal restoration and conditioning on LON networks.

Issue Recovering from a Failed 1.4 upgrade. Product Line EcoStruxure Building Operation Environment StruxureWare Device Administrator Cause The upgrade to 1.4 requires special planning and site specific preparation. Before Upgrading you should always review the release notes with an eye for site specific implications. Please read these articles when performing an upgrade to 1.4: Reference Guide and References beginning with 1.4.x Contains detailed information about the changes to Reference Management in 1.4. Upgrading Automation Servers from 1.3 to 1.4 Contains the process for upgrading an Automation Server to 1.4 Resolution The following offers 2 scenarios for correcting issues post upgrade. Scenario 1 In this Scenario, the user will use the built in repair tools added in 1.4. These tools help the user fix issues that are typically fixed prior to upgrading. Please see Reference Guide and References beginning with 1.4.x for a complete description of the changes to the Reference Management in 1.4 In StruxureWare Workstation, browse to the Control Panel and click on "Reference Manager" Note the list of References with errors. Right Click on each item and click "Edit Bindings". Re-Bind any questionable item using the new rules for Reference management. Scenario 2 In this Scenario, the user will downgrade the system to 1.3. This is not a preferable solution, but may be required in specific instances. Please note, that in order to downgrade, you must have a valid backup of the ES and every AS from prior to the 1.4 upgrade. If you do not have a valid 1.3 backup, you will need to use Scenario 1. You will also need to be able to apply any service packs or hotfixes previously used. Validate that you have a 1.3 backup of the AS and every ES by going to C:/ProgramData/Schneider Electric StruxureWare/Building Operation 1.3/Enterprise Server/db_backup. If the Backups are present and the date and time stamps are acceptable, then copy these to another location, to ensure they are not lost. You can either install 1.3 on a second PC or install on the same PC. For this example, we are installing 1.3 parallel to the 1.4 upgrade. Stop the 1.4 enterprise server before proceeding. As you install each piece of software you will be informed that the installation will be done parallel to the current version. The exception to this is the License Server. You can have only one license server installation of any build on the same PC. After you have installed all of the 1.3 Software, Install any Service Packs or Hotfixes that had previously been installed on site. When you are finished, the Start Menu will show the parallel installations of StruxureWare. Open Device Administrator Connect to the AS or all AS Click Upgrade and select "New database" Click OK There is no point to attempt to upgrade the database to 1.3 as any problems will be converted back as well. Log into each Automation Server separately, right click on the server in the system tree, and click Restore. Import the backup set you have from prior to the 1.4 upgrade. Note that Red text indicates that your current build does not match the build used for that backup. At this point, you system will be back at 1.3, and should be running as it was before the upgrade, or at the very least, it will be at a manageable level. Use the links above to correct any Reference issues before proceeding with the 1.4 upgrade.

Issue How to change the name of a 527 Link or DLA site Product Line TAC INET Environment I/NET Seven XBuilder Xenta 527 Cause In some versions of I/NET changing the name of a Link name through the I/NET Configuration tool will not work on a Xenta 527. Also, You cannot configure the Name of Link through XBuilder, this must be done as show below. Resolution Before you begin, follow the instructions in How to change the name of a NetPlus Router (NPR) in I/NET. If this fails, or you are performing an initial configuration via XBuilder, use the process below. Connect to the Xenta 527 via a web browser Expand the Configuration folder Expand the Network folder Click on TCP/IP Change the Host Name to the desired link name.

Issue Will the TE200AD24 sensor from Greystone Energy work with a MNB controller? See the datasheet. Product Line TAC IA Series Environment MNB controllers Cause Retrofitting an existing 3rd party control system with a MNB controller Resolution Any 10k thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the MNL/MNB controllers. An 11k shunt resistor wired in parallel with the sensor (1/8 watt, +/- 0.1% tolerance) is also required. See What 10k Thermistor sensors are compatible with the I/A Series MNL and MNB families of controllers? The inputs only take a 10k resistive load. So, for the setpoint slider, use a 10k linear pot. The datasheet says the AP model comes with a 20-30k pot and that you’ll have to call for other values. The 5 Vdc source required is not available on the MNB-300. It is available on the MNB-1000

Issue The door strike will not energize upon pressing door release switch. Product Line TAC INET Environment I/NET DPU SCU Cause Multiple Possible Causes - Programming Error Wiring Error Determine Cause Have someone watch the DPU or SCU while you press the exit button.  You should see an LED light come on beside the Lock relay.  If you do, then you have a wiring issue. If you do not, then you have programming issue. Resolution If you have a Wiring Error Do not assume that because it worked before the wiring is correct Check the voltage on the lock power supply Consult the appropriate TCON to determine that the wiring for the exit button is correct Disconnect the wiring from the DPU/SCU and use a continuity meter to ensure that the exit button is functional. Hard wire the strike to remain unlocked and check that the door can be opened. (if not, repair door hardware) If you have a programming Error Connect to the correct controller Select Edit > Controller > Doors Modify the affected door Ensure that the Door Strike Parameter is set to "Both" Ensure that the Door Release switch is set to either Normally Open or Normally closed Ensure that the Strike Duration is long enough to allow a user to press the exit button and still have time to exit the door. Click OK Select Edit > Summary > Controller Ensure that no door points are in manual control Consult the appropriate TCON to ensure no internal points are taking up needed point addresses. Re-test the door.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue SP-C Controllers randomly going offline / online.  Restarting the controller resolves the issue for a short period of time. SP-C Controller ports showing TIME_WAIT when a netstat command is run. Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause Under normal conditions an SP-C needs to update the Security Expert Server with new data. During this time the IP Socket of the SP-C is in a Waiting State, refusing to communicate to anyone else while waiting for an opportunity to upload. Once the controllers data has been uploaded to the server however the controller releases the IP Socket and it is open again to new communication. In an extremely small number of cases the SP-C controller goes into this waiting state as usual but then never comes out of that state, holding onto the IP Socket forever and blocking any further communication until the controller is power reset. This only affects a very small percentage of SP-C controllers running Microsoft Windows CE OS Version 16. Resolution In these extremely rare cases the first step is to identify if the affected controllers are indeed running OS Version16.  For SP-C Firmware builds before 2.08.921 Log into the controllers configuration web page. Browse to the Configuration tab. Check the OS Version field at the bottom of the page. For SP-C Firmware build 2.08.921 and above the OS is now shown in a different location.   Once it is clear, that the OS is version 16, Product Support can be contacted to arrange to upgrade the controller OS to Version 20 (or greater) as is found in SP-C controllers shipping now. As this is a high risk procedure and can result in complete failure of the controller if anything goes wrong there are two options for upgrading the OS. Install the affected controller on a test bench with remote access for Product Support to remote in to and perform the update. Have the controller sent back to the factory to be updated and returned to site. Both options will require replacing the controller with temporary stock while the upgrade is being performed.

Issue Xenta 102-ES configuration and wiring for 2 position (on / off) heating actuators or other digital heating control Product Line TAC Vista Environment Vista Xenta 102-ES Cause Wiring for 2 position heating control on the Xenta 102-ES is different than increase / decrease type actuators. Resolution The Xenta 102-ES documentation refers to two position heating control as thermal actuators, thermo or TAO and can be somewhat confusing. The same info applies whether using a two position hot water valve, any on / off type electrical heat (such as baseboard heaters or electric heating strips. Here's what you need to know: If using only one stage of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin or if configuring from Vista Workstation or the OP set nciAppOptions bit 5 to 1 and leave bit 6 as 0.   From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used.   If using two stages of heat: Select Thermo for Primary Heating in the Xenta 102-ES plugin and select Enable for Secondary Heating. If configuring the device from Vista Workstation or the OP set nciAppOptions bit 5 and bit 6 to 1. From the Xenta 102-ES plugin choose either Normally Closed (NC) or Normally Open (NO) from the box in between the Primary and Secondary Heating fields. Additionally, this can be configured from Vista Workstation or the OP by setting nciAppOptions bit 11 to 0 for normally closed (NC) operation or set bit 11 to 1 for normally open (NO) operation. Both terminals V3 and V4 will be switched when the first stage of heat is activated. These terminals operate in parallel in this configuration and either one can be used. Only terminal V6 will be switched for second stage of heat. Note: The triac outputs of the Xenta 102-ES are ground sourcing and should be wired accordingly. See Digital outputs (V) on most Xenta 100 series controllers are ground sourcing (voltage sinking) for additional information.

Issue MSDE to Full SQL Product Line TAC INET Environment I/NET Seven site Cause Need to Move db from MSDE to Full SQL Resolution Below are the steps to move from your MSDE to a full SQL instance: Make sure your version of I/NET supports Full SQL (check ReadMeSeven.txt file located on the Install CD) Backup all controllers (HVAC and Security) to database Backup MSDE database using DBCreate (Start, Programs, I/NET, DbCreate Utility) If running I/NET as a service, unregserver to stop the service (Running I/NET Seven as a service on Windows) If applicable, demote Equalized Clients(EQ) to StandAlone then demote FileMaster(FM) to Standalone Using Microsoft SQL Management Studio Express create an instance database for INETSeven which I have explained how to do in step 7 In SQL Management Studio Express right click on Databases and select New Database and be sure to name specifically INETdb Using I/NET DbCreate Utility when the login screen appears, connect to the SQL Server (Computer Name Required) you want to use which has full SQL Create a blank I/NET SQL database with proper login credentials Still from DBCreate Utility, restore the database from previous step which is a good backup Re-install I/NET over the top of the existing install so that the StandAlone will use this instance of SQL Have the proper security key information When the install gets to the SQL, select the instance from the SQL database created in step 9 Complete the installation Suggested reboot if necessary and start I/NET Restore SAV files (which is the database, see How to upgrade bin and SAV files in I/NET controllers) to the controllers in the I/NET network so everything is in sync with the db