Building Automation Knowledge Base

Issue SmartStruxure with BACnet interface, points from BACnet devices are displayed in a graphic, list view etc, initially everything works fine and the point's value updates normally but after sometime of operation (days or weeks) the value stops updating. Value maybe shown as 0.00 or ... or with a green circle or red X that indicates a bad variable. Environment Automation Server Enterprise Server BACnet interface B3 Third party BACnet devices Cause Software defect in version 1.3 (including SP1) and below. Resolution Please note that if 1.3 SP1 has not been applied it MUST be applied before installing the hot fix. Contact Technical Support to obtain hot fix 1.3.0.11403 Provide site details Apply the hotfix

Issue There are new versions of Continuum Reports, Archiver, Elevator Control, etc. that were updated by the Center of Excellence development team. These applications need to be upgraded prior to using Continuum 2.0 SP1 for sites that use these applications because of new memory mapping. Environment Windows 7 Windows Server 2008 Continuum Cause Continuum 2.0 SP1 uses a new memory mapping scheme that allows for better use of large memory addressing. The Continuum Add-on applications needed to be updated in order to work properly, so each of the applications has a new version. Installers need to know which versions to update. Resolution Below is a list of Continuum Add-on applications and versions needed to work properly with Continuum 2.0 SP1. Prior to installing Continuum 2.0 SP1, you need to upgrade certain Continuum Add-on Applications with new versions. It is recommended that you be prepared to rollback to Continuum 2.0 should critical applications fail to operate after the upgrade to SP1. You can download new versions of the following Add-on Applications from The Exchange at this URL: https://ecobuilding.schneider-electric.com Search on 'continuumreports' and locate the application.   Add-on Application 2.0 SP1 Compatible Version Access Groups 2.5.1 BioScrypt 4G V-Station Integration 1.12.1 CFR Extended Log Archiver CFR Access Event Archiver CFR Alarm Event Archiver CFR Activity Event Archiver Continuum Reports 23.0e Cogent MiY Integration 1.8.1 DVTel 6.x Video Integration 2.3.2 Elevator Control V2.6.6 2.6.7 EZ-GuardTour 1.2 EZ-Trap 1.9 Genetec Omnicast 4.8 Video Integration 1.1.1 Genetec Security Center 5.2 Video Integration 1.2.1 Personnel Data Importer Continuum Reports 23.0e Salient Video Integration 1.3.1 Stentofon Integration 1.8 Video Inquire 1.9.1   Customer-Specific Custom Applications Contact COE.Support@Buildings.Schneider-Electric.com for upgrades for the following customer-specific custom applications:   AckAlarm Area Templates PIM CADS DVTel Alarming Continuum-Excel Elevator Control V3.x Elevator Control V4.x Elevator - EasyLobby Integration Extended Log Exporter PIM 2.0 ScanShell Scanner Interface Surgard Integration Vicon Video Integration xTra    Legacy Applications Contact COE.Support@Buildings.Schneider-Electric.com for upgrades for the following legacy applications:   Area PIM Door PIM Elevator Control V2.4 Elevator Control V2.5 Unlisted Application       Download a pdf copy of this list click the following link:  Continuum Add-On Application version list

Issue Can't see the Xenta Server Menta  program online in the browser Menta program is working but it is not possible to view it online All other viewers work correctly Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta Cause One reason could be that there are texts (comments) in the Menta application that does not have any font specified. Resolution Edit the Menta file form Xbuilder Find any comment/texts Double click to edit Click on font Select a font and save Download the Xbuilder project again

Issue ID Works 5.1 badge printing error and I/NET Seven rev 1.16B. Product Line TAC INET Environment ID Works 5.1 I/NET Seven rev 1.16B Cause Attempt to save or print a badge in ID Works 5.1, the following error occurs:   Data Source Error A cursor with the name 'SQL_CUR06B8F1D0' already exists. State:37000,Native:16915,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] Resolution In order to correct this issue, contact Schneider Electric Product Support and ask for the “I/NET Seven 1.16B/IDW 5.1” patch. We will e-mail this patch to you. A better solution is to upgrade to I/NET Seven Rev. 1.17, which includes the patch in the software.

Issue Device driver open failure Echelon LonMaker Failed to open network interface device. (Subsystem: NI, #39) Environment LNS LonMaker Vista Cause NI error #39 is a network interface error. It indicates that the network interface driver failed to open the network interface. For the i.LON 10 or i.LON 100, this error occurs when the LonWorks Interfaces driver configuration on your computer does not match the network interface settings in your i.LON 10 or i.LON 100. Improperly seated PCMCIA PCC-10 LON Adapter. Can happen with some regularity when using a NIC852 and going onnet through LNS Server.  Subsequent attempts are usually successful Resolution If the LON Adapter is not properly inserted, you should try removing it and plugging it back in, or by using a second card temporarily and then switching back to the original card. If unsuccessful... To correct the error, open the LonWorks Interfaces Control Panel program and verify that the port setting, authentication key, hostname, and DNS suffix match the settings in your i.LON 10 or i.LON 100. To open LonWorks Interfaces, click Start, click Control Panel, double-click LonWorks Interfaces, and then click the RNI tab. Please reference the i.LON 10 or i.LON 100 user guides or online help for instructions in modifying the configuration of an RNI. When opening your network, make sure you select the correct network interface. For an i.LON 10 or i.LON 100 RNI, the name that you select in the LonMaker tool must match the name that you see on the LonWorks Interfaces RNI tab. Echelon Support KB515 .

Issue Access Control Doc-to-Dif Report on an older I/NET system Product Line TAC INET Environment I/NET site Cause How to perform an Access Control Doc-to-Dif Report Resolution Take a look at Tech Tip G071, which describes the process.

Issue When editing a TGML error A generic error occurred in GDI+ appears Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista StruxureWare Building Operation TGML Graphic editor Cause This issue occurs after you install security update 3045171. You experience a crash when you use Windows GDI+ to create text outline-based path objects on a computer that is running Windows 7 Service Pack 1 (SP1) or an earlier version of Windows. Resolution Download the patch below from Microsoft https://support.microsoft.com/en-us/kb/3065979 It has been noted that this patch do not solves all the issues, if you still have issues with other applications uninstall the security update KB3045171.

Issue AVUE 5304, AVUE 5354, AVUE 5305 or AVUE 5355 Light Duty Actuator does not respond to changes in control signal. Environment AVUE 5304 or AVUE 5354 Light Duty Actuator installed on VZX or MZX Valve Body.. AVUE 5305 or AVUE 5355 Light Duty Actuator installed on Satchwell VEU, MEU or FEU Unit Valve Body.. Cause AVUE 5304, AVUE 5354, AVUE 5305 or AVUE 5355 Light Duty Actuator may not respond to changes in control signal due to self stroking / auto stroking procedure failing to occur when originally installed, or due to manual override having been undertaken without subsequent reset procedure having been applied. Resolution 1.  Check that 0v of 0-10v dc control signal and 0v of 24v ac power supply originate from same source. 2.  Undertake Manual Override Reset. The Manual Override Reset Button is located on the underside of the AVUE Actuator. The purpose of the Manual Override Reset Button is to cause the Actuator to self reference. A reset is required only in the following circumstances. A.  If the Manual Override Access screw on the top of the Actuator has been operated when the Actuator is powered up. B.  If it is necessary to re-align the Actuator to a point of self reference during periods of system maintenance. N.B. The AVUE is designed to reset automatically on restoration of power following a power failure.  It should be noted that it will take approximately 85 seconds (AVUE 5305 and AVUE 5355) or 110 seconds (AVUE 5304 and AVUE 5354) for the self reference procedure to be completed. 

Issue Echelon LON interface card installed in computer is not recognized by the LonWorks Plug and Play utility nor by the I/A Series software installed on the computer. Environment LON interface card PC Cause This problem is caused by not installing the Echelon driver for the PCLTA-10 / PCLTA-20 / PCLTA-21 / PCC-10 card before installing the card into the computer. Resolution Steps 14-20 of this procedure can be used to test the PCC-10 lon card and driver if the proper driver is believed to be installed.     Before attempting to reinstall the driver, verify that this Echelon file is available:  "OpenLDV340.exe", "153-0117-01C.zip" or "PCLTA21 Win2k XP.exe". If the .zip version is available, extract the .exe file from that .zip file, to the desktop.   To correct the problem and install the proper driver, use the following procedure. Open the Windows Control Panel and select SYSTEM then select the hardware tab. Select the Device Manager button. Check to see if the Echelon card is already installed -- look for the entry "Lonworks Network Interface" and click on that entry to open it then select the "Lonworks xxxx Network Interface" choice that was just displayed. (then continue with step 5 below.) If the Lonworks Network Interface was not shown, look for an entry with a yellow question mark -- a Lonworks entry so marked should be found. Select that entry. Right click on the Lonworks entry just selected and select "Uninstall…". Follow the prompts to uninstall the driver. Shut down Windows and power down the computer then remove the Echelon card from the computer. Power up the computer. Log into the computer using an account with full administrative rights. Run the Lonworks driver application file ("OpenLDV340.exe", "153-0117-01C.zip" or "PCLTA21 Win2k XP.exe") that was downloaded and extracted. This installs the driver into Windows. After the installation completes, close the prompt indicating that a reboot is required then shut down Windows and power down the computer. Reinstall the LON interface card. Power up the computer and log into Windows. The system will indicate that new hardware has been installed and will attempt to locate a driver for the new hardware. Allow the system to install the card driver. When the hardware installation wizard finishes, it may indicate that the computer must be restarted before attempting to use the new hardware. If so prompted, shut down windows and restart the computer, logging in again as an administrative user. Open the Windows Control Panel and select (double click) the "Lonworks Plug 'n Play" entry. Verify that the device selected is LON1. If not already selected, specify the NSIxxx application in the NI Application selection box. Click the "Diagnostics" button. Click the "Reset" button then click the "Restart" button. Click "Yes" to reset the card to its boot state. Click the "Test" button and verify that no errors are indicated. Click the "OK" button to leave the Diagnostics screen then click "OK" on the Lonworks Plug 'n Play screen to save the configuration information and exit the utility. The Echelon LON Interface Card is now ready to use.

Issue When upgrading to 1.4, the reference system will be changed to follow newer more strict rules. Product Line EcoStruxure Building Operation Environment Device Administrator Cause With the release of 1.4, StruxureWare now has a tighter control on bindings. This is to prevent users from creating bindings which hinder system communication. When a system is upgraded from 1.3, to 1.4 any bindings that do not follow the new rule set will be dropped. Here are the 3 major items for this new rule set. See Reference Guide and References beginning with 1.4.x for a full explanation. Public Signal bindings will be dropped Multiple bindings will be restricted to one Bindings to Local Node NVIs will be dropped during the upgrade. Resolution To upgrade the Automation Servers, follow these steps: NOTE: You will need to have a copy of Workstation at 1.3 in order to make changes to the Automation Server during the upgrade process. Use 1.4 Workstation after you have completed Perform a Manual Backup of the Automation Server. This backup must include historic data. Ensure that a copy of that backup is saved to an external disk as a recovery option. Open Device Administrator 1.4 Connect to and Select an Automation Server Click Upgrade Device. Please Read the warning in this pop up message. This will upgrade the most recent backup of the Automation Server. Any changes to the system made since the last backup will be lost at the end of this process. Note that the yellow Progress bar means that you MUST review warning in the conversion log. If the progress bar is Yellow or Red, proceeding may result in irreversible system changes. Click "Open" under the conversion log column. This is very difficult to read in Notepad. Perform a Save as .txt and open this file in either Word Pad or NotePad++ for easier reading Notice the Change in display when the information is viewed in WordPad Use the notes from Reference Guide and References beginning with 1.4.x and the conversion log analysis from AS Conversion Log Analysis to make sure that all objects with WARNINGS meet the new rules. This will require making changes to the system via workstation. Repeat steps 1-8 until you are happy with the conversion log. Please note, that you must perform a new backup to get an updated log. Click on "Download updated database to devices" Click Okay in the pop up Wait for the Installation to finish successfully. If any errors occur, be sure to get a screen shot and contact Product Support Note: If the upgrade doesn't complete correctly on one of the AS, cycle power on the AS, go back to the previous version and perform the upgrade again.

Issue How can a workspace be created that can see only a single graphic page at a time. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Workstation Cause While more complex workspaces can be created a kiosk or graphic page style interface could be the perfect workspace for the occasional user or touch screen style kiosk in a communal area. Resolution To create a workspace of this style it is important to use the Work Area Window instead of a Graphic pane since the Graphic pane will not fill the window area and has to be linked to a side of the workspace area. Open the StruxureWare Control Panel Select Account Management Click Add under Workspaces Specify the name of the Workspace ("Kiosk" for example) Click Next Click Add in the Content Window Highlight Work Area Window and  click Next Specify your initial path to be the default graphic you want to be presented such as a home page. Click Create Define what user interface options you want to restrict such as the history bar, toolbar, or address bar (Address bar for example can allow access to other parts of the database unless you restrict it with access rights or user permissions) Click Create Select your newly created workspace from the drop down menu and select  User Account groups Add the user account group you want to use this workspace to the right hand column. The graphic page only workspace should now be accessible or configured as the default workspace for a user both in Building Operation Workstation or Webstation.

Issue When troubleshooting SMTP email issues it is oftentimes handy to send a test email directly from Windows in order to narrow down the part of the system with the problem. Product Line Andover Continuum, EcoStruxure Building Operation Environment Windows Continuum SmartStruxure Cause Troubleshooting technique. Resolution Simple way to test SMTP email for testing purposes. Make sure telnet is turned ON in Windows. (If not, go to Control Panel > Programs > Turn Windows Features On or Off > turn ON the Telnet Client.) Open a command prompt and type telnet domain name (or IP address) and port. telnet 10.169.9.10 25​ Type HELO and identify the sending system helo MyPCName​ Type mail from: followed by an email address mail from: user@tac.com​ Type rcpt to: followed by destination address. (NOTE: must be an email account in the mail server) rcpt to: user@3indq.com​ Type data then ENTER key Type a message Type . (period) then ENTER to end NOTE: Type slowly and if you mistype something hit enter and after the error re-type the line. Using backup space appears to work but it doesn't. NOTE: Make sure Telnet server is installed on the SMTP server. Make sure Telnet service is enabled/running on the SMTP server

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 Clarification on how to wire Form A and Form K Triac outputs on i285-V / b3865-V controllers. Environment i2865-V b3865-V i2866-V b3866-V i2865-V-S b3865-V-S i2866-V-S b3866-V-S Cause Had issues in the past with blown Triac outputs due to wiring, need to confirm how they are properly wired for Form A and Form K Triac outputs. Resolution As per 30-3001-810 i2 b3 865-866 Controller Installation Instructions (see page 5), you can configure your Triac so they switch the 24VAC (hot) or the GND (ground), but all Triac outputs must be configured the same. The difference between the Form A and the Form K is that the Form A is two digital outputs using a single triac each while the Form K is a single tristate output using both physical triacs for the one (logical) output. The Form A Triac outputs can be configured as either a hot or ground switch but the Form K must be configured as a ground switch (TRIAC REF tied to GND, Load to 24VAC).

Issue After creating a new station using the "New Station Wizard" in Niagara G3 Workbench, it fails to copy into the ENC using the "Station Copier". This error message appears: "The local station database file config.bog is currently in use, and cannot be copied". Environment Niagara G3 Workbench Cause It's because a "Save Bog" was not done. Resolution Go back to Workbench and open the station, make a change and do a "Save Bog". The station should now copy without issue.

Issue When trying to reload a B3867 controller or add log arrays to existing points, a memory error is encountered. Product Line Andover Continuum Environment Continuum 1.xxx B3867 Cause A memory allocation defect that was found in the -V versions of the controller was fixed in drop 51 of the -V firmware. The same issue was resolved in drop 64, but was not listed in the release notes. Resolution Update the B3867 version to the drop 64 rev.

Issue A Niagara G3 jace-6 has been operational in a building for more than two months with no reported problems.  End customer reported no updates to related graphics screens.  The jace-6 stopped responding on both of its ethernet ports.  A serial shell connection displayed the following information: IPL for NPM 6-E (PPC440EP) v4.00-6.32 ECC Press to stop autoboot... Autobooting... npm6xx startup version 7.00-6.41 Welcome to QNX Neutrino 6.4 on the NPM 6xx (ppc440) Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:01:f0:8e:5f:70 media: Ethernet none full-duplex status: active inet 143.83.31.10 netmask 0xffffff00 broadcast 143.83.31.255 inet6 fe80::201:f0ff:fe8e:5f70%en0 prefixlen 64 tentative scopeid 0x2 ------------------------------------------------------------------------- NPM6-E with T2023 JACE-2 Base Board detected SRAM mounted successfully at /sramopt LON interface detected # # An unexpected error has been detected by HotSpot Virtual Machine: # # SIGILL (0x4) at pc=0xfe4a26dc, pid=1773598, tid=1 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_34-b28 mixed mode, sharing) # Problematic frame: # Memory fault   Environment Niagara G3 jace-600, jace-600E, jace-700 Cause Internal memory issue Resolution The jace-6 cannot be repaired with a reported memory fault.  Replace it.

Issue A Niagara R2/G3 UNC/JACE is rebooting every 15 minutes and the standard output window indicates AC Power status failed and a "Battery test failed" gets logged as well. Product Line TAC IA Series Environment I/A Series UNC, ENC or JACE chassis with Gel-cell backup battery Cause Marginal or failed battery or bad battery charging fuse Resolution The UNC automatically performs a battery load test every 15 minutes. If the voltage drops below a predefined value, the battery test indicates "battery test failed". If the voltage is higher than the predefined value, the battery test indicates "battery test passed". This message is only reported once unless the detected battery condition changes. A station alarm is generated only when the new outcome is different that the previous test. If a battery is marginal, the test may alternate between "passed" and "failed." Additionally, a bad or marginal battery has been known to cause random UNC reboots. Begin troubleshooting by checking the battery fuse (field replaceable only in the UNC-500/510 controllers), connections and voltage level.  If the battery voltage is low (less than 12 Vdc), disconnect the battery and monitor the UNC for errors or rebooting. If the errors or rebooting stops install a new battery.  After installing the new battery, measure the battery charging voltage.  The voltage reading should be between 13 and 14.5 volts DC if a good battery is connected.  If the installed battery is partially discharged, the charging voltage reading may be as low as 12.5 volts. In release 2.301.522, a change was made to how embedded controllers (UNC-410 / 500 / 510 / 520) perform the backup battery test.  Formerly, a "marginal" battery might result in continuous reboots. Now, the battery test is better coordinated with the AC power test. This prevents the scenario of repeated AC power fail shutdowns upon boot up if the battery is bad or weak.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121, which does not have a D1 input. Product Line TAC Vista Environment Xenta 121 STR-150 Cause The correct terminal for the mode input from the STR-121 is labeled differently on the Xenta 121 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 121 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 6   The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 121. When the Xenta 121 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained inIs it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue Where Sigma utilizes the site Ethernet network, and that the network consists of multiple subnets, or is using Sigma DNN's with ARCnet or ethernet secondary LANs. Global object values are not received at the receiving controller when it is on a different subnet to the sending controller. Product Line Sigma Environment Ethernet networks containing subnets. Cause Global Values not being passed from controller to controller on different subnets. General advice on the configuration of Link Addressing. Resolution PIB 05 105 Link Addressing explains how to configure Link Addressing on a Sigma system utilizing a customers Ethernet network,