Building Automation Knowledge Base

Issue Incorrect image name is displayed in the download window. The IC-UNIFACT image is displayed in the download window instead of the IC-SNP image where Unifact URC1201/2201 controllers are installed on site. Environment Sigma IC and IC3 controllers Cause The site has Unifact 1201/2201 controllers integrated to an IC3-SNP, when the image is to be downloaded, the image file that is displayed is for an IC3-Unifact. Resolution IACs and Unifact 1201/2201 controllers use the IC SNP. Unifact Pro controllers use the IC UNIFACT. In this example the controller sub type was configured as IC UNIFACT when the correct setup should be an IC SNP. Only the specific image file will be displayed in the download window as determined by the controller version set in the controller setup.  1. Select the correct IC in System Setup > Network and Devices > Controllers as shown below and save. 2. Goto System Diagnostics > Options > Download Files. The correct image will appear.

Issue Are the following SNVTs supported in Vista 5.1.6? SNVT_Amp_ac SNVT_Count_32 SNVT_Volt_ac Environment Xenta X5XX, X7XX, X9XX with firmware 5.1.6 Cause The SNVTs  SNVT_Amp_ac, SNVT_Count_32 and SNVT_Volt_ac are not included in the Xenta 5.1.6 firmware. They will be included in 5.1.7. There is however a workaround available in 5.1.6  Resolution Locate the SNVTtype.def file in the Xenta server. Connect to the Xenta server using an FTP client and locate the SNVTtype.def file under configdb/Lon/SNVTTYPE.def. Copy the file to your PC and make a backup copy Edit the file with a suitable text editor (notepad, notepad2 etc) -Locate the SNVT_amp definition -Add the following lines after SNVT_amp definition (see screenshot below): //---// amp_ac 139 2 1   INTEGER,,2,0,65535,1,0 //---// Repeat the process with the other 2 SNVTs - SNVT_count_32: Add the following lines after SNVT_count definition: //---// count_32 183 4 1 INTEGER,,7,-2147483648,2147483647,1,0,raw //---// - SNVT_volt_ac: Add the following lines after SNVT_volt definition: //---// volt_ac 138 2 1   INTEGER,,2,0,65535,1,0 //---// Replace the SNVTType.def file in the Xenta server using the FTP client.

Issue Official Product Announcement on the Discontinuation of Micronet 2000 and Network 8000 (PA_00152). Environment Micronet 2000 Network 8000 Cause Components for manufacturer no longer available. Resolution The following products will no longer be available after December 31, 2011:  

Issue Airflow reading from Xenta 102-AX is jumping around and will not stabilize or is 0. Environment Vista Xenta 102-AX Plug-in LonMaker, NL-220 Cause For a variety reasons parameters may get changed in a Xenta 102-AX adversely affecting the controller's performance. Resolution Ensure that all of the parameters that affect the airflow reading are set properly. In some cases it may be best to restore the default parameters. Parameters that should be checked may be found through the Xenta 102-AX plug-in or through Vista but are grouped below how they are found in the plug-in starting with Unit Parameters: Unit Parameters Duct Area Ensure that the duct area is set properly for the box size. If a formula was used to determine the duct area from duct diameter verify that it yielded the correct result. For square or rectangular ducts use the following formula: For round ducts use the following formula: Pickup Factor The pickup factor is sometimes known as the K factor and is determined by examining the airflow curve diagram provided by the box manufacturer. It can often times be found on the box itself or in the manufacturer's literature. If the manufacturer's specs cannot be obtained use the default pickup factor, which is 2951.6. Box Constant The box constant is a product of the pickup factor and the duct area. It is sometimes available from the box manufacturer. If the manufacturer's data cannot be obtained use the default value, which is 1588.5. Note that the box constant will be changed from default if a CBC, or, calibrate box constant is performed. Airflow Parameters Velocity Pressure Gain The default settings here are 10 / 10 and are changed when a calibration is performed. If these numbers factor out to be very far from one you may want to reset them to their defaults and investigate if something went wrong with the calibration. For example these values may read 2957 / 3054 but since that factors out to 0.968 which is only about 3% off from one. However, if these numbers were 2957 / 6043 this would be a clear indicator that there was something wrong. Velocity Pressure Offset The default value here should be zero and considering that sensor is nominally set up for a 0-1" scale numbers greater than +0.1 or less than -0.1 should be cause to investigate further for mistakes during the calibration process.

Issue Enterprise Server does not start when computer is started/rebooted or shuts down right after starting it StruxureWare Building Operation Software Administrator log shows the following error: nsp.NspServer The server has made too many unsuccessful attempts to start... Product Line EcoStruxure Building Operation Environment Software Administrator Enterprise Server Cause StruxureWare Building Operation is prohibiting the Enterprise Server from starting up because the ES has exceeded the number of startup retries defined in server_startup.properties. When the server_startup.properties file is opened in a text editor, the first line indicates a startup failure. NspServer.Startup.Service.Status: fail Resolution Windows XP: This is caused by a dependency, set in the registry, on the service netprofm (Network List Service), which exists on Windows Vista and later, but not on Windows XP. The error has been verified on a new installation of Windows XP. Steps 1 and 2 below help to resolve this on the XP operating system. Windows 7 and Windows Server 2008 R2 including Virtual: Start ES manually from the Software Administrator. If this fails, the log in the Software Administrator explains why. Start the ES manually from the Services listed in Services (Start, My Computer, right-click, Manage, Services click the + to find Services) find StruxureWare Enterprise Server Go to the Software Administrator and modify the HTTP, HTTPS, and TCP ports to available ports. (suggested: 81, 444, & 4444). The number of startup retries is defined in the following file: 1.2.0 and below : C:\Program Files\Schneider Electric\StruxureWare X.X\Enterprise Server\etc\server_startup.properties 1.3.0                  : C:\Program Files\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\etc\server_startup.properties 1.4.1 and above : C:\ProgramData\Schneider Electric StruxureWare\Building Operation X.X\Enterprise Server\db\etc\server_startup.properties Increasing this threshold in server_startup.properties will allow the Enterprise Server to have a better chance of achieving a successful startup. server_startup.properties -- Original settings NspServer.Startup.Service.Status: fail NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 2 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 2 server_startup.properties -- Threshold increase to 10 retries. NspServer.Startup.Service.Status: success NspServer.Startup.Service.Status.NbrOfConsecutiveFails: 0 NspServer.Startup.Service.Status.QuitRetryAfterNbrOfConsecutiveFails: 10   Last option, and please go through all the previous steps mentioned before attempting: Open regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Building Operation X.X Enterprise Server. Open the DependOnService and remove the first line (netprofm) and then reboot. The ES will now start automatically.     Alternative Workarounds Go to Computer Management by right clicking on Computer and going to Manage. In Computer Management, go to Services and Application > Services > Building Operation X.X Enterprise Server. Right click on Building Operation X.X Enterprise Server and go to properties. The two different settings that can be changed so that the Enterprise Server starts automatically as a service after a reboot are as follows. Under the General tab, change the Startup type from Automatic to Automatic (Delayed Start). Or under the Recovery tab, change the Restart service after to a value of 3 or more minutes.

Issue Is there a way to copy the setup parameters from one Xenta 102-AX VAV controller to another? Environment Xenta 102-AX NL220 Cause To assist in commissioning of many Xenta 102-AX controllers with similar configurations, parameters can be copied between controllers. Resolution Locate the controller you want to copy the parameters from. Right click on the controller and select "Copy configuration values to memory" Locate the controller you want to paste the parameters into. Right click on the controller and select "Paste configuration value(s) from memory" Then modify the parameters for that specific 102-AX as normal.

Issue Attempts to make changes to LonMaker drawing results in error message that write access is not available. Environment LonMaker 3.1 Cause When the drawing is opened write access was not granted. By default write access is enabled, but it can be turned off when multiple users are accessing the same drawing file. Resolution When opening the network ensure that the "Show all network options dialogs" checkbox is checked. When you reach the Username prompt screen ensure that the "Write Access" field is checked and then complete opening the drawing.

Issue When using a HyperLink in Vista WebStation graphic page the error message "This content cannot be display in a frame" is shown. Clicking the link to open this content in a new window will properly display the web page. Environment Vista WebStation 5.x.x Cause Newer web browsers support a HTTP header flag named X-Frame-Options which allows the remote web server to block display of its content within a web page frame. This is a security measure to stop "click jacking". Internet Explore 8, Internet Explorer 9 will display the error message Google Chrome will ignore the hyperlink. Resolution Instead of linking directly to the web page link to the folder that contains the Hyperlink object and then clicking on the hyperlink object will open the web page in a new window if the target property is empty or "_blank". Another alternative is simply click the "Open this content in a new window" link.

Issue The editing of Sigma objects is not working correctly on a Windows 7 PC. Environment Sigma Objects Editing Windows 7 Object File 0 Bytes Cause This was caused by a mis-configuration of the Sigma server on the Windows 7 PC, which had been set as a remote client. Resolution The original fault was described as shown below. On the newly upgraded Sigma 4.04 to 4.05 SEB system, I have encountered some problems regarding Object Editing. When finishing editing, it takes a long time for the download to finish and afterwards the object file shows that it is zero bytes. If I try to edit without uploading and downloading the same happens. The issue was traced to the configuration of the Sigma server which is set in C:\Sigma|Bin\SetupSvr.exe. This had been set for a remote Sigma client. Local Sigma client. (Client is running on the same PC as the Sigma server). Running SetupSvr.exe produces the following window. The window shows the configuration set for a newly installed system, which is assumed to be a local Sigma client. Remote Sigma client. (Client is running on a different PC to that of the Sigma server). Running SetupSvr.exe produces the following window. If the tick in the "This Computer" selection is removed, then the configuration is ready for use with a remote Sigma client. In the screen shot below, the IP address of the Sigma server has been entered, but PC names can also be used.

Issue How are two 4-20 mA loop-powered sensors wired into a MNL-200? Environment MNL controllers with at least two UI inputs (MNL-100, MNL-150, MNL-200, MNL-800) Cause n/a Resolution The image below provides a basic (but accurate) diagram of two loop-powered sensors and how they are wired with a power supply and a MNL controller.

Issue The Xenta 104-A plug-in limits the temperature value input between 0°F and 18°F. It is not possible to input a negative value. Environment Xenta 104-A Plug-In Lonmaker 3.1 or Lonmaker 3.2 NL220 Cause The Xenta 104-A plug-in limits the temperature value input between 0°F and 18°F. It is not possible to input a negative value. Resolution In Vista follow these steps: Navigate to the Xenta 104-A controller. Browse down to the Node Object function block and find the nciSpaceTempOfst SCPT. Type in the designed space temp offset parameter from the default 32°F value. For example, if a -1°F offset is needed a value of 31 will need to be entered. If a +1°F offset is needed a 33 will need to be entered. 32°F represents zero offset.

Issue The Xenta 104-A plug-in limits the temperature value input between 32°F and 104°F. Environment Xenta 104-A Plug-In Lonmaker 3.1 or Lonmaker 3.2 NL220 Cause The Xenta 104-A plug-in limits the temperature value input between 32°F and 104°F. Resolution In Vista follow these steps: Navigate to the Xenta 104-A controller. Browse down to the 8030 function block and find the nciDischAirMax SCPT. Type in the designed high discharge air temp value.

Issue How to set a Xenta 102-AX back to factory default values.  Environment Xenta 102-AX Vista LonMaker NL220 Factory Default Cause Unwanted changes can be reset back to factory values. Resolution To reset a Xenta 102-AX back to factory defaults, recommission the device and select Source of CP Values to default.

Issue The engine is in the process of converting a database. Internal. NS#165 error occurs when the user is attempting to delete a portion of the LNS database. For example, the error will occur when doing group bindings because the first step in the automated group binding process is to delete the old bindings. The error will also occur when deleting a controller, snvt, bindings, etc, out of the LNS database. Environment Lonmaker 3.2 NL220 Cause All instances of this error have been reported after upgrading an LNS 3.1 system to 3.2, and the upgrade process somehow does not finish. This has been reproduced in NL220 as well. Resolution Send your LNS database to Echelon for analysis at support@echelon.com.

Issue What is the best way to implement the GMT/BST changeover on Sigma? Environment Sigma Time Date Daylight saving Summer Winter GMT BST Cause Correct implementation of the process. Resolution The recommended procedure is as follows; Set all Sigma server PC's to "Automatically adjust the clock for daylight saving changes", this is achieved in the Date and Time properties. Set up the Sigma Scheduler with a schedule or schedules to retime the controller/s. We suggest that you do not retime all controller/s at once, but do a section at a time, see below. Server retimed at 02:00 Controllers retimed at 02:02 (Schedule 1) Controllers retimed at 02:12 (Schedule 2) Controllers retimed at 02:22 (Schedule 3) ETC. This allows time for any logging to returned to the server, before the next retime occurs. The schedules are configured as shown below.  Firstly the action is created, notice that a range of controllers is chosen. The second part is to associate the action with the schedule.

Issue Understanding the meaning of the Diagnostic LED's located on UNC devices. Environment Sigma Devices Controllers UNC DNN DNN3 496 532 596 632 696 796 Cause The Diagnostic LED's provide the user with a clear understanding of the controllers present state. Resolution The LED chart below provides a clear understanding of the controller state, and allows an easy diagnostics.  

Issue  The bCX and b3 controllers are BACnet compliant, why do they not support all defined BACnet object types? Environment Continuum BACnet 3rd Party BACnet Device Cause Misunderstanding of what BACnet compliant means and/or misinterpretation of BACnet Product Information Conformance Statement (PICS). Resolution BACnet compliant devices are not required to support all of the defined object types. However, if an object is supported it must comply with the standard object model for that object type. This includes a number of required as well as optional properties. The PICS for a BACnet device is used to define what LAN options the device supports as well as supported objects and optional properties (it’s implied that the required properties are supported and these may or may not be shown in the PICS). In our current products, we do not support some optional objects such as Life Safety Point and Life Safety Zone, this is clearly stated by the omission of  these objects in our device PICS. Looking at our bCX1-CR as an example, we support 19 of the optional standard BACnet object types. The list of those objects below was taken from our device PICS located here.

Issue When trying to connect XPSI version 4.1 to a MicroZone II, using a B&B Electronics converter, model USOPTL4, an error is received: "No communications adapter found. Comm error = -5". Online XPSI functions may be grayed-out and not available: Environment XPSI version 4.1 USB / RS-485 adapter, B&B Electronics model USOPTL4 Network 8000 MicroZone II controller Cause One cause of the error appears to be closing the XPSI Site Group window: Resolution Leave the Site Group window open. Edit the Site setup. In the following example, the site is named "B&B converter to MZ2". To communicate to a stand-alone MicroZone II, the Network Number and GCM Number do not matter, they can be left at their default values. The "Connection Type" should be set to PSI HOST   The "Port" should be set to match the hardware port assigned to the B&B converter when installing its drivers. It will be named " RS-485 Isolated Port (COMx)". COM3 in the following example. Note the Universal Serial Bus Controllers, Model USOPTL4. Once the site is configured, access the controller: Enter the user name and password for the MicroZone II on the MicroZone II PSI Main Window:   In the "Functions" menu, use the arrow keys to move the cursor to "Device Number", and press "Enter". Type in the address of the controller, which is set by its DIP switch. The MZ2 is set to address = 1 in the example: While XPSI is connecting to the MZ2, the TD and RD LEDs on the model USOPTL4 should blink.  The  yellow (RX) and green (TX) LEDs on the MicroZone II should also blink. When XPSI is connected to the controller, the Main Window will display the device number. In the example, MZ II # 001 is connected: When finished accessing the MicroZone II, logoff and select "Disconnect" from the Access menu. This will properly shut down XPSI and the drivers for the B&B converter.

Issue Alarm archiving at release 4.5 SEB. Environment Sigma Alarms Archiving AlarmLog.rec Cause The alarm archiving mechanism is unclear. Resolution Sigma 4.05 SEB includes a mechanism for archiving alarms on basis of a number of conditions. User Settings. The user is able to set the following "Alarm File Sizes".  Current (Max). this is the maximum number of alarm records * 1000. Archive (20 - 50) %. this is the percentage of the "Current (Max)" record setting that will be archived.  These setting are located in the "System Setup" / "General" / "Archive Sizes" as shown below. Automatic Alarm Archiving. The Sigma alarm archiving process is an automatic function that will operate to the requirements of the settings above. When an archive takes place a low level alarm message is produced to advise the user, it does not require acknowledgement as it is only for information. Archive alarm files are stored in the C:\Sigma\Data\ArchivedAlarms folder using a sequence reference number. Timed Alarm Archiving. These Schedules are located in the "System Setup" / "General" / "Scheduled Actions", and the first step is to create an "Action", as shown below.  Next create either a "Daily" or a "Once Only" schedule. The alarms will now be archived on a regular basis as dictated by the above schedule. Please note that the archive will still follow the configuration setup up in "Archive Sizes".

Issue I/A Series (Niagara) R2 station, needs a LON shadow object for a Square D Altivar 21 with Program ID 80:00:13:3C:0A:0A:04:50.  The closest match is Atv21, with Program ID 80:00:13:3C:0A:0A:30. Environment I/A Series (Niagara) R2 station in a UNC with a LON trunk, build 532, 529, or 522 Square D drive, Altivar 212, with LON card, Program ID 80:00:13:3C:0A:0A:04:50. Cause Square D Altivar 212 with a new LON profile and XIF file, program ID 80:00:13:3C:0A:0A:04:50 Resolution Download a new jar file: lonSquareD-2.303.532a.zip, which includes a shadow object named Atv212, manufacturer Id = TA_Control, and Program ID  = 80:00:13:3C:0A:0A:04:50. LonUtilities Manager after the jar file has been installed: