Building Automation Knowledge Base

Issue When attempting to enable .NET Framework 3.5 on Windows using the DISM command mentioned in the WebReport installation guide, the attempt fails with error 1910 Command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 1910 The object exporter specified was not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Product Line EcoStruxure Building Operation Environment WebReports Cause The Windows Modules Intaller service is not operating correctly, and has to be restarted. The service is however protected, so this can not be done through the services control panel. Resolution Kill "TrustedInstaller.exe" from the Windows task manager (CTRL+SHIFT+ESC) Start the "Windows Modules Installer" service from Windows services (Start->Run->services.msc) Try again, either using the command or the SBO Reports Preparation tool.

Issue I cannot find any published instructions giving the procedure to install an updated version of one of the JAR files on my I/A Series (Niagara) system. Product Line TAC IA Series Environment I/A Series (Niagara) R2 software (any version) installed on a Windows computer Cause An updated version of one of the JAR files installed in an I/A Series (Niagara) R2 system has been published.  The updated file has been downloaded to my computer but there are no instructions on how to install it. Resolution For the purpose of this explanation of the procedure, the following steps reference an update to the "programlib" jar file for release 2.301.522.   Substitute the name of the jar file being updated and release number in the following steps. * NOTE: Before attempting to update a jar file, verify that Windows Explorer is configured to display file type extensions. (See * below for more information). The JAR file update is published, currently on the  as a .zip file containing two files.  Copy the file programLib-2.301.522c.v1.jar.emb to the \niagara\r2.301.522\emb folder. Rename the existing file  from programLib-2.301.522.v1.jar to programLib-2.301.522.v1.jar.old. Rename new file from programLib-2.301.522c.v1.jar.emb to programLib-2.301.522c.v1.jar (removing the .emb extension). Copy the file programLib-2.301.522.v1.jar.nt to the \niagara\r2.301.522\nt folder. Rename the existing file  from programLib-2.301.522.v1.jar to programLib-2.301.522.v1.jar.old. Rename new file from programLib-2.301.522c.v1.jar.nt to programLib-2.301.522c.v1.jar (removing the .nt extension). Copy the file programLib-2.301.522.v1.jar.nt  to the \niagara\r2.301.522\nre\modules folder Rename the existing file  from programLib-2.301.522.v1.jar to programLib-2.301.522.v1.jar.old. Rename new file from programLib-2.301.522c.v1.jar.emb to programLib-2.301.522c.v1.jar (removing the .nt extension). To install the new jar file into a UNC, perform the following procedure after completing steps 1 through 9, above. Start the Niagara 522 version of the Admin Tool. Open a connection to the UNC Select the "Installation" tab then click the [Installation Wizard] button. Select the "emb" folder in the "Select Distribution Directory" window then click [Install] In the "Niagara Remote Installation" window, select the "Configure Modules Only" radio button then click the [Next >] button. Verify that there is a checkmark in the "Upgrade/Add" column for the updated jar file. Click the [Next >] button to continue. Make sure that on the "Database Backup" screen that you do backup the existing database. Continue through the remaining steps and allow the upgrade to install and the station to restart.   * To properly rename the files as described in this procedure, Windows Explorer must be configured to show file type extensions.  To configure this setting or verify it, proceed as follows: Open Windows Explorer by clicking on the My Computer (or Computer) icon on the computer's desktop or by making the selection from the Windows start menu. From the Windows Explorer "Tools" menu, select "Folder Options" Select the "View" tab. Scroll down through the "Advanced Settings" list to locate the entry "Hide extensions for know file types".  Verify that this entry is unchecked. Click the [OK] button to save the change, if any, and exit the Folder Options screen.

Issue Random no response from access server invalid attempt events showing up in event view Environment Cyber 1.74 SP2 CX9900 Cause Network issues (router offline) preventing remote validation attempts from reaching the access server Resolution Make sure all routers are online. The may be an IP conflict with the controller. Disconnected the Lan cable from the controller and ping the controller IP, if there is a response then another device has that same IP.

Issue When trying to create a mirrored network variable or manually create a SNVT binding the error "Service Not Changeable" is given.  Environment Building Operation Workstation LonWorks Interface Cause If the "Changeable binding type" property of a network variable that is being bound is No, then there are only specific binding types that can be used.    To check the "Changeable binding type" property, right click on the network variable > click Properties > click on the Extended Settings tab.  Resolution Manually creating network variable bindings Make sure that the correct binding profile is chosen which complies with the device template of the controller.  Creating mirrored network variables If the "Service Not Changeable" error is given when creating a mirrored network variables, it is because the default binding profile does not comply with the network variable properties. To change the default binding profile, see WH#11229.

Issue The Sigma Client reports a "HTTP connection failed" error" when an attempt is made to start it. Product Line Satchwell Sigma Environment Satchwell Sigma release 4.05 and later Cause When the Sigma Client is started, attempts are made to make a connection to the Sigma Server, this connection fails and the Client cannot be started. Resolution There are a number of reasons why this error might occur, suggestions are listed below. 1.  Windows XP operating system - ensure that service pack 3 has been installed, and that all the Windows updates have been applied. 2. Windows 7 operating system - only Ultimate and Professional are supported. 3. Sigma Client/Server software must be installed by a Windows user with "Admin" privileges. 4. Windows Firewall must either have been switched off, or has "Exceptions" configured as explained in the Sigma 4.05 SP1 release note. 5. Check that the "SigmaSVR" service has been started. If this service cannot be seen, then this is an indication that the Sigma software has not been install by an "Admin" user, and the software must be reinstalled. 6. Corruption of the Windows "User" files has taken place. Create a new Windows user with "Admin" privileges. Log on to Windows as the new user and test the Sigma Client again. 7. If using a VMware image try rebooting the image. 8. SMART is being used and has a modem connected to the PC for uploading data. Ensure that the modem is fully functional. If not, the HTTP error can be caused. This was seen at Sigma: R4   Release 3.44.14. and Smart Task Manager  3.0.2.20. Added 26-07-2012 9. This may be because a proxy server is being used, eg on school networks. Log on to your PC computer with an administrator account. Open the "Start" menu and click on "Control Panel." Double-click on the icon labeled "Internet Options." Go to the "Connections" tab at the top of the window and then click on "LAN Settings." Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Added 25-09-2012. 10. This issue was reported from a School where Sigma 4.05 SP1 had been operating correctly for several weeks. The issue was traced to the Anti-virus software Sophos, which had received an update prior to the failure. Sophos had quarantined two Sigma dll files. To correct this issue both Sophos and Sigma were uninstalled. A later version of Sophos was installed, and then Sigma was reinstalled, this corrected the problem. Added 01-08-2013 11 - Sigma software installed when connected to a wireless network. The Sigma client will only connect to the server when the wireless connection is made. Uninstall Sigma, disable the wireless, enable the network card, and then reinstall the Sigma software. Added 03-10-2013 12. DELL PC, with firewalls and antivirus disabled and no wireless card fitted. There may be a service or an application running in the background as part of the vendors Windows platform makeup.Restore the same version of Windows, but without (where possible) any of the Vendors applications. Re-install Sigma. Added 16-05-2014 13. Check the port number in c:\sigma\bin\setupsvr.exe, the default is 8080. Added 19-05-2014 14. Flexera license software has been reported as a cause for receiving this error. Flexera license software uses port 8080, (IMADMIN.EXE). Stop Flexera and retry Sigma. Changing Sigma from port 8080 to 8081 could also provide a solution. Added 27-08-2014 15. The SBO PCS (StruxureWare Building Operation Project Configuration Server) also uses port 8080.This needs to be stopped or will conflict with Sigma and produce the HTTP error. Added 02-09-2014 16. Make sure any data is backed up from the installed Sigma system. Uninstall Sigma using Add/remove programs (Win XP) or Programs and features (Win 7). Wait for the Sigma un-install process has completely finish. Delete or rename the C:\Sigma folder to.......for example Sigma1. Re-install Sigma by using a right mouse click on the "SigmaSetup.exe" file and select  A new clean Sigma folder will be created during the install. Once completed reboot the computer. Check the SIgma server is running and run up SIgma. Added 01-10-22014 17. The HTTP error can also caused if the computer name contains extended ASCII or Unicode. For example a computer named "Pást" may fail, if the computer name is changed to "Past" this may correct the HTTP problem. Added 23-11-2021 18. On SE laptops, the McAfee firewall has been updated: Go to McAfee (under hidden icons) > right click 'Quick Settings' > 'Enable Firewall Timed Groups'. This will provide a 1 hour window to run Sigma, in the McAfee pop up window. add a reason e.g. Sigma.

Issue Is it possible to setup more than one custom card format in Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Custom Card Formats Cause Have a requirement for two or more custom card formats. Resolution Currently, only one Custom Format can be configured.   It is possible to add a Secondary Format to a Reader port in Reader Expanders, but only one port can be setup with a Custom Format.    However, Credential Types have now been introduced with the release of Security Expert 4.3, which largely supersedes Custom Formats going forward and allows multiple custom card formats and even QR codes where required.  Please see AN 276 Security Expert - Configuring Credential Types - Integration Guide for more information on setting up Credential Types and Maximum number of Credential Types for more info on how many can be used.

Issue A Plain English program is disabling with the error "attribute does not apply to the item". Environment CyberStation Controller Plain English Cause The controller database did not match the CyberStation SQL server database Resolution Reload the affected controllers

Issue Can the backplane, which consists of the Power Supply, Automation Server, and I/O Modules be installed in the cabinet horizontally or vertically? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation hardware installation in a cabinet with limited space. Cause Customer would prefer vertical installation rather than the typical horizontal installation. More than one Automation Server per Power Supply** Resolution What could happen if you mount the system vertically? Due to the lack of ventilation the temperature will increase, which will have negative impact on component life time. The operational temperature is defined up to +50°C. At this temperature, the horizontally mounted system will fulfill the specified lifetime of the different electrical components. In a vertically mounted system the temperature will be higher inside the modules, having negative impact on the component lifetime. Unfortunately it is not a linear relationship between temperature and lifetime - the lifetime decreases rapidly with increased temperature. Not all modules are generating the same amount of heat, and are therefore more or less sensitive to mounting direction. In my view, the most critical component is the AS. The CPU generates heat (even more important on the coming AS-P). In the AS there are also critical components that maintains power during shut-down. These component's life time is effected if the temperature becomes too hot. These components are, as stated, critical during power-down. How will this be visible to the user? During normal operation, there will be no visible effect. However, after some years when the AS goes through a power cycle, it will not restart. So, what to do if you have a cabinet with the conduits running vertically? The official answer is that the system shall be mounted horizontally. This is how the system is designed and tested. What can you do to minimize the risk you choose to take if not mounting the system horizontally? The key is operational temperature. If you are far from 50°C, then the risk is less. One thing you always should consider is to mount the PS+AS in the bottom of the cabinet horizontally, and then have the CIO modules vertically, connected via an S-Cable. This is even more important on AS-P. If you are close to 50°C operational temperature, you need to consider external cooling or at least ventilation in the cabinet in addition to mount the PS+AS horizontally.** To conclude - the system is designed for horizontal mounting and this is the only supported mounting. If you choose to mount it vertically it is at your own risk. Operational temperature is key - you need to make sure it is far from max to decrease risk. Always try to mount the PS+AS horizontally. Negative effect of not managing operational temperature is not visible short term, but can and will effect the life time of the product. **Ambient temperatures for operating should be taken into consideration. For vertical installations, ambient temperature should not exceed 35 C (95 F) and the load on the power supply should be reduced from 30 watts to 25 watts. Convective Air Cooling is used in the modules anticipating the currents of warm air being allowed to escape the confines of the module casing to be replaced by cooler air from the bottom. Since warm air normally rises, this method usually requires venting at the top and bottom of the casing to be effective. This is why horizontal installations are preferred. **One PS can supply one or more units connected to the backplane, consisting of several terminal bases connected together. At the moment you cannot connect more than one AS to the backplane though, because the backplane provides a path for communication between the connected units, and two AS cannot communicate on the backplane. StruxureWare Building Operation allocates 32 slots for the I/O Bus including the Power Supply and Automation Server. All devices can be installed on one linear section of DIN rail or they can be installed on multiple parallel sections of DIN rail by using connector cables*. Be reminded an empty position (back plane without module) will still keep a position (slot). As a general rule, there are 10 I/O modules followed by a Power Supply, then 10 I/O modules followed by a Power Supply and 8 remaining slots for I/O modules.Please keep in mind the I/O Bus backplane requires a particular order. Position 1 is always the Power Supply, Position 2 is always for the Automation Server, and then up to 30 remaining I/O devices interlaced with additional Power Supply modules.

Issue The Xenta 102-AX can be set to NIGHT_PURGE mode using the plug-in or VAV_Controller.nviApplicMode.  The documentation does not state what this mode does. Environment Xenta 102-AX Cause The Xenta 102-AX Product Manual enumerates all of the possible modes for the controller, but does not go into detail about night purge or any of the other modes. Resolution NIGHT_PURGE mode will: Set the unit mode (nvoUnitStatus.MODE) to HVAC_NIGHT_PURGE Set the airflow setpoint (nvoFlowControlPt) to Cooling Maximum (SCPTmaxFlow) The Xenta 102-AX will enter NIGHT_PURGE mode automatically when the unit is UNOCCUPIED and the terminal load is 100%. NIGHT_PURGE mode will end and return to the active nviApplicMode when the terminal load reaches 0% or below. Note:  Heating outputs are not disabled in this mode. If the Xenta 102-AX is in night purge mode when it goes occupied it will be stuck in that mode. The box will not come out of night purge until the terminal load reaches 0% just as when it is unoccupied

Issue When binding Output points in the script editor to the desired outputs, the bindings are not working. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation All Versions Automation Server Central I/O Modules Cause When bindings to the output points the incorrect attribute is being used. Resolution Open binding editor for the desired program. In the right hand pane, choose the desired output to be bound. Expand the point and select Requested Value. Drag the Requested Value to the desired output in the program. Save settings.

Issue What are the PinOuts for the RS-232 Connection of the older 1st Generation CX controllers to connect through Hyper terminal. Product Line Andover Continuum Environment Hyper Terminal Continuum CX Gen 1 CX9900 Continuum CX Gen 1 CX9940 Continuum CX Gen 1 CX9400 Continuum CX Gen 1 CX9410 Continuum CX Gen 1 CX9200 Cause Need to direct connect to a first-generation controller to configure its IP address and ACC Net ID. Resolution The Hyper Terminal cable needs to have the below pinouts. RJ Connector - - - - - - - - - - - - - 9 Pin RS-232 PC Controller Comm3 Pin 1 - DTR - - - - - - - - - - - - - Pin 6 - DSR Pin 2 - CTS - - - - - - - - - - - - - Pin 7 - RTS Pin 3 - CXD - - - - - - - - - - - - - Pin 1 - CXD Pin 4 - RTS - - - - - - - - - - - - - Pin 8 - CTS Pin 5 - GND - - - - - - - - - - - - - Pin 5 - GND Pin 6 - RD - - - - - - - - - - - - - Pin 3 - TD Pin 7 - DSR - - - - - - - - - - - - - - Pin 4 - DSR Pin 8 - TD - - - - - - - - - - - - - - Pin 2 - RD On the RJ connector for the controller's comm3, Pin 1 is the furthest to the left with the insert clip facing away from you and the gold teeth facing you (download drawing). For the CX9200 and CMX controllers download the pinouts here. Download Command Terminal Reference Guide here

Issue The nvoEffectSetPt is different than the nviSetPoint The nvoEffectSetPt is different than the cooling or heating setpoint (SCPTsetPnts) Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The nvoEffectSetPt is calculated according to nviSetPoint, cooling or heating setpoints (SCPTsetPnts), nviStPointOffset, and thermostat offset. Resolution The nvoEffectSetPt is a SNVT network output in Xenta 102-AX and represents the current effective setpoint that the controller is utilizing in its control loop. nvoEffectSetPt can be configured to display in two different manners: Actual and Normalized. (As defined bynciVAVselctcCntl.oP.ESS (UCPTvavSelection)) Actual nvoEffectSetPt displays the setpoint that corresponds to the currently active application mode of the controller (occupied cooling, unoccupied cooling, standby cooling, occupied heating, unoccupied heating, and standby heating). Normalized nvoEffectSetPt displays the average of the cooling and heating setpoints for the currently active occupancy mode (occupied, unoccupied, standby). NOTE: Whether nvoEffectSetPt is set to Actual or Normalized only affects how the effective setpoint is displayed and does not affect how the application operates. The 102-AX application utilizes the setpoint that corresponds to the currently active mode (occupied cooling setpoint, etc.). In addition, the thermostat adjustment of the setpoint will not appear in any SNVT in Xenta 102-AX controller. This offset is captured in the Xenta 102-AX's memory, and although it is not displayed, it is utilized into the nvoEffectSetPt calculation. Also note that the below scenarios only apply to the occupied and standby modes since the unoccupied setpoints are unaffected by nviStPointOffset, nviSetPoint or by the thermostat offset. Scenario 1: nviSetpoint is unused 1.1 Actual nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the sum of one(1) of the four setpoints (occupied cooling, standby cooling, occupied heating and standby heating) plus the offsets (nviStPointOffset and thermostat offset). 1.2 Normalized nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the average of heating and cooling setpoints ( 1/2(Occupied Cooling Setpoint + Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint + Standby Heating Setpoint) ) plus the offsets (nviStPointOffset and thermostat offset).   Scenario 2: nviSetpoint is used 2.1 Actual nvoEffectSetPt calculation: In cooling mode, the nvoEffectSetPt is the nviSetPoint plus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint -Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ),  plus the offsets (nviStPointOffset and thermostat offset). In heating mode, the nvoEffectSetPt is the nviSetPoint minus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint - Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ), then plus the offsets (nviStPointOffset and thermostat offset). 2.2 Normalized nvoEffectSetPt calculation In this scenario, whether the application is in the cooling mode or the heating mode, the nvoEffectiveSetPt is the sum of the nviSetPoint and the offsets (nviStPointOffset and thermostat Offset). Therefore, when nviSetPoint is used and nvoEffectSetPt is to Normalized, the actual heating and cooling SCPT setpoints do not matter; only the difference between them is significant. For example, setting occupied cooling and heating setpoints to be 75°F (24°C) and 65 °F (18°C) will give the same resulting nvoEffectiveSetPt as setting occupied cooling and heating to be 45°F (7°C) and 35°F (1°C).   Example Occupied Cooling = 72°F (22°C), Occupied Heating = 68°F (20°C), nviSetPoint = 75°F (24°C), assuming the nviStPointOffset and thermostat offset are zero. nvoEffectSetPt in Occupied Cooling or Heating Mode   Scenario 1.1 Scenario 1.2 Scenario 2.1 Scenario 2.2 Cooling Mode 72°F (22°C) 70°F (21°C) 77°F (25°C) 75°F (24°C) Heating Mode 68°F (20°C) 70°F (21°C) 73°F (23°C) 75°F (24°C)

Issue Unable to connect to a G3 ENC or JACE after attempting to downgrade or install a station. One of several different errors may be displayed in the serial shell console output.  The following are examples: Could not find library libcpp.so.3 Could not find library libcpp.so.4 Error occurred during initialization of VM - Java/Lang/ No Class Def found error: Java/Lang/object Product Line TAC I/A Series Environment I/A Series G3 ENC and JACE (all revisions), ENC-410, ENC-520, TRD-T-645, TRD-T-603, TRD-RB-645, TRD-RB-603, TRD-J-600E, TRD-T-700 Cause The issue is caused by downgrading the ENC / JACE without following the procedure to first install the clean distribution file. In addition, the ENC/JACE will fail if a station is copied into the ENC/JACE without first installing the OS and NRE software using the Workbench Commissioning Wizard. Note: With G3 release 3.3 and newer, the procedure for downgrading an ENC/JACE is included in the Niagara AX Platform Guide - Downgrading a JACE (Clean Dist). Resolution Tools needed: Null Modem Cable Serial Terminal (e.g. HyperTerminal or TeraTerm) Jumper Obtaining the files required to recover the ENC NOTE: If recovery of a Jace-700 is required, please contact Product Support for the recovery file. Download the appropriate OS image and gz file zip file for the ENC/JACE from the Exchange website - https://ecobuilding.schneider-electric.com ENC-410.zip ENC-410-1 standard memory - etfs512 ENC-410-EM.zip ENC-410-1 extended memory - etfs2048 ENC-520.zip ENC-520-2 standard memory - etfs512 ENC-520-EM.zip ENC-520-2 extended memory - etfs2048 NPM6E.zip JACE603/645, TRD-RB-603/645, JACE600E Note: The files used in the following procedure MUST correctly match the ENC/JACE hardware platform, otherwise permanent damage to the unit may occur. The serial shell can be used to determine the file system requirements (standard or extended memory). To find the exact image needed for an ENC (JACE 2/4/5) execute the following while connected to the unit with serial shell: Log into the unit's menu system using the platform username and password. Type sh to exit the menu system and enter the shell mode. At the # prompt, (type: cat sys/info/fs) and enter This will return the file system type of etfs512 or etfs2048. Extract the OS image and gz files from the downloaded zip to a suitable directory on the local computer (e.g. local hard drive such as: c:\temp). Enable ftp: By default, the ftp port is disabled on every ENC/JACE as shipped from the factory.  Enable the ftp as follows. Set the jumper on the ENC to serial shell mode and connect the null modem cable between the PC and the ENC/JACE. Connect to the ENC using the Serial Terminal program and the following port settings: Baud rate 57600 bps (Note: JACE-603/645 baud rate is 115200) 8 data bits, 1 stop bit, no parity After logging in to the menu system from the serial shell, do the following to enable ftp: Select option 4 from the menu Enter the port number (Normally 21). (type: 21) Press the Enter key to confirm the change Note: Leave the serial shell connection open while performing the next steps. FTP the OS image and gz files On the local system, open a command prompt window and change the directory to the location where the OS image and gz files were extracted (c:\temp). Connect to the ENC via ftp and put the OS image in the /tmp directory entering the following from the command line: Create a ftp connection to the ENC by typing: ftp and enter Type the username and password for the platform when prompted Change directory to /tmp (type: cd tmp) and enter Change to binary mode (type: bin) and enter Download the image to the ENC by using the put command. The image name must exactly match the image extracted from the downloaded zip file. ENC-410-1 standard memory (type: put york-etfs512.image) and enter ENC-410-1 extended memory (type: put york-etfs2048.image) and enter ENC-520-1 standard memory (type: put james-etfs512.image) and enter ENC-520-1 extended memory (type: put james-etfs2048.image) and enter JACE-600E, 603, 645 extended memory (type: put npm6xx-etfs2048.image) and enter Download the gz file to the ENC by using the put command. The name must exactly match the image extracted from the downloaded zip file. Change directory to the root (type: cd ../..) and enter Change directory to /ffs0/zip (type: cd ffs0/zip) and enter Download the gz file (type: put clean.tar.gz) and enter Exit ftp (type: quit) and enter Execute OS image update Return to the serial shell connection Type sh to exit the menu system and enter the shell mode At the # prompt, type: osupdate and enter After a short delay the # prompt will return. Shutdown to reboot the ENC (type: shutdown) and press enter. The ENC/JACE will reboot, install the clean distribution image and perform one additional reboot automatically. The ENC/JACE should now be recovered and allow connection to the platform. Connect and use the Workbench Commissioning Wizard to install the version of G3 required.

Issue Step-by-step instructions for calibrating Space Temperature sensor on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating temperature in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution  Step 1: Connect M/STAT Plug the M/STAT into the jack on the thermostat.  The initial display shows the set temperature.  Step 2: Enter Password Press the Service button.  This prompts you to enter the service mode password.  Default password is 183.  Use the +/- keys to set each digit and the enter key to submit.  If the password is incorrect, the display will blink.  Step 3: Operational Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed.  Hit the select button down until Operational Parameters (oP) is displayed.  Press enter.  Step 4: Calibrate Space Sensor Hit the select button until Calibrate Space Sensor (CSS) is displayed.  Press enter to view the current value.    Step 5: Enter Actual Value Use the +/- keys to change the value beginning with the tenths of degrees.  Press select to change to the degree and ten degree digits.  When the display matches the Actual Value, press enter.  Step 6: Escape Service Mode Press the service key to escape out of the menu.  If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT.  Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue How do you determine how large a database will grow when using Continuum? How do you know if a Stand Alone or LAN install should be used? Which version of Microsoft SQL Server is needed? Product Line Andover Continuum Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 MSDE SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of controllers, points and logging should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called MSDE and SQL Server Express. The size limitations are 2 and 4 gigabytes respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Continuum database, to determine if a Stand Alone or LAN is needed and which version of SQL should be used. The Continuum database estimating spreadsheet takes into consideration 6 main areas: Extended Logs- total amount of logs, intervals and the number of days to retain  Access Events- total amount of access events and the number of days to retain Alarm Events- total number of alarms and the number of days to retain Error Events- total number of Cyberstation errors and the number of days to retain Activity Events- total number of Activity events of all Continuum users and the number of days to retain Continuum Database objects- Total number of Netcontrollers, Infinet, BCXs , mstp controllers, total number of inputs, outputs and numerics. Any of the objects not mentioned above. Consider all objects not mentioned above The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate if a Stand Alone or LAN system is needed Indicate which version of SQL Server is needed Download the Continuum Database Size Estimation Tool.

Issue Configuration instructions for setting up a communications VX Log in the Xenta 5/7/9xx for communications troubleshooting. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 VXI Cause Configuration instructions for setting up a communications log in the Xenta 5/7/9xx for communications troubleshooting. Obtaining the communications log for a Modbus or BACnet network is crucial in finding communications errors, or other unforeseen problems with integrating to third party devices. Resolution Step by step instructions for creating the communication log for troubleshooting or for data analysis: Log In to the Xenta 5/7/9xx controller and navigate to the Utilities Folder:   Click on the Target System Folder and choose VXI Web Shell Commands:   The command line should appear with VX populated in the command line:   Logging to file in the Xenta controller will first need to be enabled to by typing VX L 1 and press submit:   VXI Web Shell Commands should return a messing indicating logging has been enabled for 1 hour:   After logging has been enabled, the verbosity will need to be set in order to capture each layer of communications on the wire. In the command line type VX V 9 and press submit:   VXI Web Shell Commands should return a messing indicating the verbosity has been set to 9 and what messages you will see with this verbosity level :   Let the communications log run for 5-10 minutes. Create as many changes on the 3rd party wire as possible to get various data changes to and from the Xenta Server.   In the command line type VX O and press submit:   This command will output the communications log the Xenta Server has collected. Highlight this entire output log and copy, then paste it into notepad for archiving or emailing:   To set the communication logging back to default type "vx V 1" or power cycle the Xenta Controller. To stop the logging to file, type "vx L".   For TCP/IP logging you can only monitor one client at a time: Complete Steps 1- 8 above Enter "vx d" This will display a list of the TCP available devices Enter vx d # where # is the number corresponding to the deice you wish to monitor To view the log, follow steps 9 and 10 above

Warning 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 Services for assistance. Issue What is the best way to upgrade Continuum Single User system from 1.5x to 1.9x? Product Line Andover Continuum Environment Continuum 1.5x, 1.5, V1.5 Continuum 1.6x, 1.6, V1.6 Continuum 1.9x, 1.9, V1.9 SQL Server Cause Continuum Upgrade from older versions of Continuum. Resolution First upgrade to 1.74, then upgrade from 1.74 to 1.9x.    PART I - Preparation: Acquire all software necessary to bring the workstations into compliance with 1.9x platform requirements. For each Cyberstation machine, make a record of the following Workstation name Folder name Device Node ID Network ID. From https://ecobuilding.schneider-electric.com Download Cyberstation 1.74 Download Cyberstation 1.9x Download Microsoft SQL Server Management Studio Express Run Continuum Analyzer and resolve any issues.  An upgrade should not be done until the analyzer test report is clean. IMPORTANT - Make a backup of the Continuum database just prior to upgrading. PART II - Upgrade Workstation 1 (Database server PC) Uninstall 1.5x or 1.6x Shut down the Cyberstation applications on all workstations. Power down the workstations that are not running SQL and leave off until Part III Backup the contents of C:\Program Files\Continuum\UserProfile by copying contents to a flash drive or another folder. Backup the contents of the graphics file directory to a flash drive or another folder. Delete C:\Program Files\Continuum Uninstall SQL from Workstation 1 (DB server) Install 1.74 Install Continuum 1.74  (SQL 2000 SP4 will be installed automatically as part of the install) Run Database Initialization Create new database Initialize workstation using information from Part I. Launch Continuum to test that Cyberstation startup normally. Shut down Continuum Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Restore database backup from PART I Run Database Initialization. Update Continuum DB Update Workstation using information form Part I Launch continuum and verify that everything looks normal. Verify the integrity of the database by running Continuum Analyzer and correct any database issues before proceeding.. Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Backup Database – name file so that it is clearly 1.74 Uninstall 1.74 Uninstall Continuum Delete C:\Program Files\Continuum Uninstall SQL from Workstation 1 Install 1.9x Install all platform software necessary to bring the workstation into compliance with Continuum 1.9x requirements. Install Continuum 1.9x - (SQL Express will be installed automatically as part of the install) Run Continuum Database Initialization Create new database Update workstation with information from Part I. Launch Continuum to test that Cyberstation startup normally Shut down Continuum Run Microsoft SQL Server Management Studio Express Navigate to ContinuumDB and Right Click Restore 1.74 database backup. Run Continuum Database Initialization Update database Update workstation with information from Part I. Launch Continuum and verify that everything looks good. Run Continuum Analyzer and verify the integrity of the database. Backup Database PART III - Upgrade Workstation 2 and 3 Install all platform software necessary to bring the workstation into compliance with Continuum 1.9x requirements. Backup the contents of C:\Program Files\Continuum\UserProfile by copying contents to a flash drive or another folder. Uninstall Continuum from Workstation  Delete C:\Program Files\Continuum Install Continuum 1.9x Run DB Initialization and update database and workstation. Launch Continuum and verify that all looks well. Backup Database

Issue What is the default IP address for BCX, ACX57xx, CX9702 & Netcontroller II? Product Line Andover Continuum Environment Controller Netcontroller II (9680) BCX ACX57xx CX9702 Cause Default IP address for BCX, ACX57xx, CX9702 & Netcontroller II Resolution The default for all these controller types is: IP address: 169.254.1.1 Subnet: 255.255.0.0 Gateway: 169.254.0.0

Issue How to view user login/logout information in TAC Vista Workstation Environment TAC Vista Workstation Cause User login/logout information is captured in the events log. Event viewer can be filtered for displaying just the login information. Resolution Sign in TAC Vista Workstation as an administrator. Open the Event Viewer.   Use event filter to filter out unnecessary information Open Event Filter window, and select “General” tab. Under “Type”, leave “Commands” to be checked and uncheck everything else. Under “Object type”, Type “Vista Server” After the filtering, the event viewer will only display user login, user logout, server start up information. Additional Information: Viewing only the login/logout information: In the Event Filter window, select “Event Specific” tab Under “Command”, type “LOGIN” or “LOGOUT   Viewing specific user login/logout information In the Event Filter window, select “General” tab Under “User”, type the user name NOTE: if the user is in a user group, need to include the user group name also. For example, user SYSTEM is also in the SYSTEM MANAGER group, need to type “SYSTEM (User Profile SYSTEM)” in "User" textbox.

Issue The Runtime tab of an Infinet controller editor shows the maximum number of 255 for both the Infinet Error Count (InfinetErrCount) and Reconfigs.  What is the command to reset them to 0? Product Line Andover Continuum Environment Infinet controller NetController (CX9200, CX9400, Cx9702, CX99xx) NetController II (CX9680) bCX9640 Cause Having an unstable Infinet can cause both Infinet errors and Reconfigs to occur.  An engineer may want to reset the Infinet Error Count (InfinetErrCount) and Reconfigs to 0 and check how fast they both reoccur. Resolution Either execute the command from the Command Line of Continuum Explorer or create an InfinityProgram in the CX controller to reset them as below: *   Set Comm2 Reconfigs = 0 *   Set InfnetCtrlName InfinetErrCount = 0                NB  Make sure the whole path is specified!!