Building Automation Knowledge Base

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

Issue Master / Slave schedules not working Product Line TAC IA Series Environment I/A series R2 Niagara Cause When Master / Slave schedules not functioning properly the most common cause is an issue with the Address books. Another issue that can cause this is the firewall application on the Enterprise Server computer. Resolution To confirm it is an Address book issue conduct the following test: Create an AO object in the Master device (typically the Enterprise Server) and the Slave device (typically the UNC).  Link the output of the AO in the Master device to the input of the AO in the Slave device.  Link the output of the AO in the Slave device to the input of the AO in the Master device.  When viewing the AO's at each station in the WorkspaceEditor there should be little boxes on both sides of each AO indicating both devices can send and receive data.  If an Address book issue exists there will be a box missing at one device or the other.  To correct this issue: Reboot which ever station only shows one box by its AO.  If the issue persists go to step 2. Clear the address book entries in the device that has the AO with both boxes (this is usually the UNC) and reboot the device.  When the station comes back up carefully re-enter the Address book data and then check each AO to make sure both have two boxes.  Typically this will resolve the issue, but until both AO's have boxes on both sides the issue is not resolved.  It may be necessary to clear and redefine the address book a second time or clear and redefine the address books in both devices to pass this test.  Once the AO test is successful the Master / Slave scheduling will link and function as expected. Ensure that ports 80 and 3011 are added as exceptions in the firewall application. Refer to Which antivirus software is compatible with Niagara R2 and G3? for details.

Issue Will I/NET access control work with retina, palm or fingerprint readers? Product Line TAC INET Environment I/NET 2000 I/NET Seven Cause Access controls can use different forms of identifying individual users. Newer readers can scan retinas, palms, and finger prints. Resolution I/NET will work with bio scanners, provided they send a data string of the supported Wiegand bit rate for the version and firmware of I/NET in use, and it is in the order expected. Refer to BioScrypt V-Pass-2 (Biometric) Reader in I/NET Seven for an example or contact Product Support for more details.

Issue After configuring an I/NET workstation to connect as a Remote Client the I/NET Configuration profile editor does not start. INetCfg.exe appears in the Windows Task manager processes but no application user interface (GUI) is displayed. Product Line TAC INET Environment I/NET Seven 2.13 and above configured as Remote Client Cause I/NET Configuration profile editor attempts to connect to its active profile database server, if this is not active it will sit and wait for the database server to become active before displaying the I/NET Configuration Profiles user interface (GUI). Resolution It is possible to change the default (or active) profile, provided you have more than one configuration profile.  This is achieved by changing the following settings in the registry. If you only have one profile on your I/NET workstation, you could export a known working profile from another I/NET workstation.  Refer to the following Exporting/Importing Configuration Profiles for the procedure to do this. Ensure that the INetCfg.exe application is not running in the processes, if it is then use the Windows Task Manager to check and end the process before proceeding with the following steps: From the Windows Start menu select RUN Enter in the command regedit Locate the Registry Key > HKEY_LOCAL_MACHINE> SOFTWARE> CSI - Control Systems International> I/Net 2000> Configurations> In this container (Configurations) there is String named "Active" this should display the name of the active profile been used by I/NET. Edit this string to another profile that exists, typically the initial profile called "Config1" is the safest. Close the Registry Editor Run up I/NET Configuration – the profile editor should now start and display the Active configuration you selected above. Modify the profile you wish to use Ensure that the Database Server name is now local to your machine name or is online. If not you can edit this my selecting the Connection Button within the profile.  Make any necessary changes required to the profile Select OK. Ensure the profile you modified is now made active Close the I/NET Configuration Profiles editor and I/NET is now ready to run.

Issue What is LANMon and how do I use it? Product Line TAC INET Environment I/NET Controller LAN 78010 Model TAP Cause Further analysis is required to establish physical layer (LAN) issues, which may include some of the following: 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 It is strongly recommended that you look at these issues prior to using LANMon.  Refer to I/NET Physical Layer Issues for rectification and recommendations of these Physical Layer Issues. Another form of analysis is to look at your Processor and LAN loading for each of your controller LAN devices.  Refer to I/NET Configuration Status parameters: Processor Loading and LAN Loading (Percentages (%)) for further information on this. Resolution LANMon 3.0 is a utility program used to perform communications capture and analysis functions on the I/NET controller network. The LANMon utility consists of a firmware program which is executed on a 78010 Tap and a .EXE program which is run on a PC. The Tap running the LANMon firmware connects to the RS485 I/NET controller LAN and listens to the communications traffic on the LAN. The Tap receives and translates the communications to a continuous ASCII stream of data which it sends to the LANMon PC using the RS232 channel. Download TCON301 which describes the installation, configuration and operation of LANMon. Click here to download the LANMon application. EPROM is available through either your logistic channels (Australia Only) or alternatively refer to Using the LANMON 3 tool with a 78010 TAP with a MIP01 board attached on how to use a MIP01 to achieve the same function. After capturing your LANMon files, you can then send your captured files to Product Support for further analysis if required or use Decoding LANMON 3 errors to assist in decoding the capture. Below is an image showing the basic LANMon equipment:

Issue "PSU device driver failed, It may be missing or disabled!” error or “An External installation failed : Hasp" error error when attempting to install Privilege Administrator. Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Incompatibility with Windows Server 2003 Resolution Uninstall any previous installation attempts (Please see How to uninstall Privilege Administrator 2.01 software for instructions on uninstalling the software) Download HDD32.zip from Exchange Online located at Previous Vista Software \ TAC Vista IV License System Unzip and run HDD32.exe Install Privilege Administrator again. Only Vista version 4.20 and later is supported for use in Windows 2003 Server. Please observe that HDD32 may also solve some problems when installing Privilege License on Windows XP Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue New laptops do not support hardware for Echelon PCC-10 cards Product Line TAC Vista Environment Laptop Computers without PC Card slots or with ExpressCard Slots Cause Some new Laptops do not come with a PC Card slot or have an ExpressCard Slot that does not fit the PCC-10 card Resolution If the PC does not have a PC or express card slot then use NIC-709 USB Lon Talk adaptor. These are available from Loytec. See the procedure for changing from a PCC-10 LTA to a NIC-709 LTA. If the PC has a express card slot, see Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for a solution.

Issue  All time schedules on site did not start. What is the difference between "Global Special Day Broadcast" and "Special Day Broadcast" in the Network Functions? Product Line TAC INET Environment I/NET Seven 2.xx and greater Cause Special days are incorrectly configured in the controllers special day calendar as permanent, or are not re-entered each year. Resolution There are two types of broadcast settings available under the Network Functions, Special Day Broadcast option in I/NET. Using the 'Special Day' broadcast setup in the Network Functions allows only a single temporary 'special day' entry to be sent to selected controllers saved in your network configuration (Netcon). Using the "Global" special day broadcast the entire special days calendar to the selected controllers in your network configuration (Netcon).  The entries in this calendar can be selected as either temporary or permanent. Refer to TCON299 TAC I/NET Seven Operator Guide 5/10 Chapter 2-34 (Network Functions – Special Day Broadcast) available on your installed I/NET workstation or from the Download Center). Also refer to Time Schedules through Special Days Button.

Issue Do we support the DoubleTake redundancy solution with Continuum? Product Line Andover Continuum Environment Continuum DoubleTake Cause This product used to be available from Andover Controls, is it still available for purchase and support today? Resolution The DoubleTake redundancy solution is no longer supported for use with Continuum. This third-party product (with some additional in-house custom software) has not been supported for quite some time now and there has not been any new development work done on our side of the solution (Failover Manager) for over 10 years. Marathon (AKA EverRun) is the only Disaster Recovery / Redundancy solution we currently support. Also see What are the solutions available for database fail over redundant Continuum system.  

Issue Xenta 102-AX version 2.14 and prior will not honor nviSpaceTemp unless it is bound with a true SNVT binding. This can be an issue in a Vista classic scenario using a Xenta Server to do the connection in XBuilder. Product Line TAC Vista Environment Xenta 102-AX version 2.14 or prior Vista Classic Network Cause The Xenta 102-AX version 2.14 and prior requires a true SNVT binding on nviSpaceTemp from an LNS Management software (LonMaker, NL220). The controller does a check to see if there is a true bound value on the nviSpaceTemp and if it does not exist, it reverts to the hard-wired room temperature sensor. When using the Xenta 700, Xenta 500, or Xenta 900 the controller simply connects the desired temp value to nviSpacetemp via a connection object. This is not a true LNS binding and the controller WILL NOT honor the connected value. Resolution Upgrade the firmware of the Xenta 102-AX to version 2.16 or later. Firmware 2.16 allows the use connection objects in XBuilder to send a value to the nviSpaceTemp SNVT of a 102-AX. Download the latest Xenta 102-AX firmware Instructions on upgrading the firmware are located here: Upgrading a Xenta 102-AX to version 2.16 or later.

Issue To communicate directly with a laptop to a DMS Microsmart controller requires an interface adapter. The model number of the adapter is MSC-LIM. It is obsolete. Does it have a replacement? Product Line TAC IA Series Environment DMS Microsmart revision 10 and 11 Cause Obsolete part Resolution There is no replacement for the MSC-LIM, but there is a repair option. See Repair or replace an obsolete part from the Network 8000 and DMS product lines.

Issue In some projects there is demand for time synchronization for I/NET system. Unlike other Xenta Servers, Xenta 527 NPR does not have an entry for setting up an NTP server on the webpage of the controller. Product Line TAC INET Environment Xenta 527 NPR Cause Xenta 527 NPR is just the IP router for I/NET system. So the web page of it is simpler than the one of other Xenta servers. Resolution We can set the NTP server for Xenta 527 NPR through HyperTerminal. Refer to Connecting a serial cable to a Xenta 5/7/9xx controller for how to use HyperTerminal to configure Xenta 527 NPR. After entering Xenta 527 NPR by typing username and password, type the command "time_date". Then type "timesynch" command. There will be several options for it: Set whether to let Xenta 527 NPR act as NTP server. For this parameter, just leave default. Assign the IP address of the NTP server. Set the refresh interval. After these parameters are set, restart the controller. After the refresh time passed, it will synchronize the time with the NTP server.  

Issue Error: "Event Receiver Failed - Could not retrieve any events from the event log" Product Line TAC Vista Environment Replacement PC running Vista 4.5 Vista IV Cause This is typical of a <4.5 Vista installation where the original PC running Vista Server has failed. The replacement PC name has not been changed to match the original PC name. It could occur from a name change of the PC or Vista Server after TAC Vista installation. This can be the result of a failed installation of the TAC Vista Config which creates communication issues between SQL and Vista. Resolution Reinstall Vista making sure the PC has the proper name and follows the correct naming convention before you start installing. This will create new users including the proper PC name on the PC and in the SQL server. If the installation continues to fail, send Product Support all error messages along with a copy of the Windows Event Log. Failed to Read Event From Event Log Database - Vista IV may also be of interest.