Building Automation Knowledge Base

Issue How can it be determined if a new Niagara G3 ENC or new Niagara R2 UNC has the new boot flash? Environment Niagara G3 ENC Niagara R2 UNC Cause Determine boot flash version. Resolution The best way to determine if the controller has the new or old boot flash is to compare the serial number on the printed circuit board with the numbers listed below: UNC New Boot Flash (requires 529) UNC-410:Serial number 36218 or greater, shipped 6/16/10 UNC-520:Serial number 36184 or greater, shipped 6/16/10 ENC New Boot Flash ENC-410:Serial number 263187 or greater, shipped 5/18/10 ENC-520:Serial number 263122 or greater, shipped 5/13/10 If the serial number was removed or is not legible, contact Product Support Services for assistance. There is additional information available that will assist in determining the new and old boot flash.

Issue Vista Webstation crops printouts when set to scale to fit on the page Environment Vista Webstation Internet Explorer Cause Automatic scaling, or scale to fit, is not properly sizing the print job. Resolution If you are not getting a complete printout of the trend log, or have portions of it cropped off at the edge of the page, scale the print size manually rather than using a scale to fit feature.

Issue Users are finding it difficult to locate the settings for Password Expiry on EBO Accounts Product Line EcoStruxure Building Operation Environment EcoStruxure 1.7.1 and later Cause When the standard Administrators User Group is examined (of which the admin account is a member), the Password Expiry, Change Password and Auto Logoff settings cannot be altered.  Everything is greyed out.   Even if a new User Group is created,  while Passwords Change permissions and Automatic Logoff settings can now be adjusted, the Password Expiry is still not available. Resolution For Password Expiry settings select: Control Panel / Security Settings / Password Policy.    All Password options including Password Expiry can be adjusted here and will apply to all users rather than a single User or Group

Issue Vista Server - "Comm port not configured" error message Environment Vista Workstation LonMaker Cause While reviewing the EMS if mouse over a point you get a "comm port not configured" error message and points appear offline. This isn't a Vista Server issue however its an LNS issue resulting in the lonmaker protocol not working correctly. Resolution Open LonMaker You should receive a "recovery - global" error message. Close LonMaker  Proceed to the following path on the clients computer. C:\Lm\Db\projectname\recovery Find the "objects.dat" file. This file should disappear when Vista and LonMaker aren't running. Shutdown Vista Server and LonMaker and see if the file disappears. If it doesn't then this file has been corrupted and needs to be deleted. Once you delete the file open LonMaker and verify the error message is gone. Once verified, start Vista Server and check communication and the "comm port not configured error message should be gone as well.

Issue In Niagara G3, how can an objects value be displayed in a graphic and not its status? Environment Niagara G3 Cause Default BoundLabel properties of the object are set to display the value and status. It must be adjusted to display only the value. Resolution In the BoundLabel properties of the object, the default text format is %.% This displays the value and the status of the object. To display just the object's value, edit the format to %out.value% The object will then display only the present value in the graphic.

Issue In Niagara G3, how can a Boolean object's "False" condition be made to disappear? Environment Niagara G3 Boolean Object Cause BoundLabel properties must be adjusted for the desired operation. Resolution In the BoundLabel properties of the object, right-click on the "visible" field, and choose "Animate" In the Animate window, click on the drop-down for the "Converter Type", and choose "I Boolean to Simple" Click the drop-down for the "False Value", and select "false" Click OK to close the Animate window Click OK to close the BoundLabel properties window Save the graphic Now, when the object has a value of "false," it will not be visible in the graphic.

Issue What is Remote Client with I/O in the Workstation Type in the I/O Server? Product Line TAC INET Environment I/Net Seven version 2.4x with need for Remote Client configuration using a Remote SQL Server. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.4x  Resolution The new option of Remote Client with I/O for the Workstation Type begins with 2.4x version of I/Net Seven. This option is for a SQL Server which is not located on the Filemaster or Standalone but rather a separate Server. The Remote Client with I/O must be running for other standard Remote Clients to get the features such as AMT, Trends, and Network Functions. Network Functions can be found in I/Net on the pull down menu Edit/Host Computer/Network Functions. The configuration is in the I/O Server under the current profile and can be found in the Workstation Options.  HINT: Exit the I/O Server (and I/net) and select Start/Programs/I/Net/I/Net Configuration to be able to setup the Remote Client. Remote Client is not show unless you exit I/O Server. Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Remote Client with I/O. I/Net version 2.4x Remote Client with I/O Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Filemaster, Equalized Client, or Remote Client. I/Net version 2.4x Filemaster, Equalized Client, or Remote Client Suggestions for further info: To install the SQL, go to Installing I/NET Seven on a 64-bit operating system. For more on how to set up that Remote Client with I/O to use that SQL database, see Unable to connect Remote Client to Standalone Server. 

Issue Battery replacement for V53 processor card and 532 controller. Environment V53 532 Controller Cause The battery supplied with the V53 processor board is dead and need replacement. Resolution The battery supplied with the V53 processor card and 532 controllers is rated at 70mAh. Specification V53-BAT provides a battery rated at 150mAH. The circuitry on both the V53 processor card and 532 controllers can handle this higher rated battery.

Issue UI-4 Expansion module will not work with i2 controller. Points cannot be controlled. Environment UI-4 Expansion modules i2 Controller Cause The firmware of the controller is less than what is required. The compatibility matrix indicates that to use the ui-4 expansion module that the firmware must be at version 3.3x. Resolution Uprev the firmware to version 3.3x. Read through Technical Bulletin #1361 to ensure that the bootloader flash is at the correct version. 

Issue Error 5295  or invalid attribute when applying installing an xdriver Environment xdriver Cause Clicking apply prior to installing the driver will present the 5295 error. Resolution One of the following should resolve this: Make sure that you click "Apply" prior to checking the driver .  Do not map a drive to the server, place the driver on a local Cyber and do not place any spaces in the path. Ensure that the correct driver is being used.  Set the commport to xdriver, install the driver then apply. If you hit apply before you install the driver you will get the 5295 error

Issue Error when commissioning a Xenta 5/7/9xx indicates an out-dated or mismatched XIF (device template). Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) on a Xenta 5/7/9xx LON device   If this error occurs on any other device besides a Xenta 5/7/9xx, please reference Program IDs do not match. There is an incorrect or out-of-date program version. (Subsystem: NS, #38) for resolution. Product Line TAC Vista Environment LonMaker 3.X Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Cause The Program ID inside the controller does not match the Program ID specified for that controller inside the LNS environment resulting in a Program ID mismatch. Program IDs are unique identifiers created for use in device templates and are based on the XIF. Resolution Resolve the Program ID mismatch by making the Program ID in the controller match that in the LNS environment. Download the controller using XBuilder. Send project to target. Generate the latest XIF for the XBuilder project. In the Network Pane, right-click on the root (TAC_Xenta_511 in this example) Select Generate XIF File   Find the new XIF that has been generated in the XBuilder Project directory: targetimage\configdb\lon\TAC_Xenta_511.xif Default XBuilder locations XBuilder 5.1.3 and prior: C:\Documents and Settings\All Users\Application Data\TAC\TAC XBuilder Projects XBuilder 5.1.4 and later: C:\Documents and Settings\All Users\Application Data\Schneider Electric\TAC XBuilder Projects Windows 7: C:\ProgramData\Schneider Electric\TAC XBuilder Projects A good practice is to view details of the folder to confirm the time stamp of the XIF file. It should match the time that the file was generated in XBuilder. This file will be selected later, so another good practice is to rename the file to something more meaningful -- the name does not matter. "WebServer.xif" may be easier to find later and confirm it is the correct file. It is also perfectly acceptable to move this file to a new location -- Device Files of your overall project, for example. That can also help in later steps, especially if the default XBuilder Project location is used. In LonMaker, right-click on the device, and choose "Replace" (Not in System Plug-In)   Browse to the newly generated XIF file. Give the new device template a name. Select Finish. Commission the Xenta 5/7/9xx into the network. The Program IDs now match and the error is cleared.

Issue Installation of a key on SQL server is not required Environment Continuum SQL Server Cause   Do I need a Continuum security key on my server? Resolution Installation of a key on SQL server is not required. For each Continuum workstation that accesses the database located on the server you will need a key for each Continuum workstation.

Issue Question on what to set the virtual memory to on a Continuum Workstation PC Product Line Andover Continuum Environment Windows XP Cause Question on what to set the virtual memory to on a Continuum Workstation PC Resolution Virtual Memory Requirements The virtual memory "Initial size (MB)" setting on your workstation PC should be set to a minimum of 1 GB. To make this change: Go to Start, Settings, Control Panel. In the Control Panel, double click System. The System Properties menu, shown on the next page, appears. Click the Advanced tab and click Settings in the Performance box. The Performance Options menu appears. Click the Advanced tab. In the Virtual Memory box, click on Change. When the Virtual Memory dialog appears, fill in the desired paging file memory size (initial and Maximum). Click OK as you back out of the dialogs.

Issue This typically happens after upgrading Continuum on a workstation that uses add-on reporting. When attempting to run the reports this error pops up. Environment Continuum Environment with reporting requirements Cause ODBC settings altered on the upgrade.   Note: No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the “Reset_Password.bat” batch file to re-enter the default Continuum DB password.   Note: No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the “Reset_Password.bat” batch file to re-enter the default Continuum DB password. Resolution   The password needs to be re-entered. No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the C:\Program Files\Continuum_Reports\Reset_Password.bat batch file to re-enter the default Continuum DB password. (i.e. Andover97)

Issue MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." Environment Continuum loaded on a Microsoft Operating System computer Cause MSMQ has become corrupt on this PC. Resolution Continuum cannot be installed on XP HOME(XP Professional only) Verify that the msmq service is started Go to Add/Remove programs > Add/Remove Windows Components does not give the option of installing Message Queuing. Go to a DOS Prompt and change your directory to C:\Program Files\Continuum\Install (cd \Program Files\Continuum\Install) Run the batch file Runafterreboot.bat (This will reinstall the Continuum version of MSMQ. NOTE: Most recent versions of CyberStation RunAfterReboot.bat has been renamed InstallMSMQ.bat Run the batch file and re-boot the machine then run Continuum ** In some cases Windows Add/Remove programs may not completely remove MSMQ and a utility like Revo Uninstaller may be helpful in getting a clean uninstall, so that a reinstall is successful.

Issue RAM can generate an interface alarm after Sigma has been upgraded to release 4.05. Environment All Windows supported versions. Cause Prior to Sigma release 4.05, the Alarm manager (Alarmcli.exe) was monitored by the Remote Alarm Manager. Sigma 4.05 no longer has this file, and therefore the Remote Alarm Manager produces an interface alarm because it is unable to see the Alarm Client running. Resolution When using Sigma 4.05, start the Remote Alarm Manager services and open the Console. Select the configuration tab, and then choose “Interfaces”, now select “Sigma (R4) RAMServer”. Go to the “Applications” option and deselect “Sigma Alarm Manager (alarmcli.exe)”.

Issue The Remote Alarm Manager is unable to send Sigma Longtext messages as part of the RAM message. Environment All supported Windows platforms. Cause Prior to Sigma release 4.05, Long Text messages were stored individually in the Sigma\Data\LongText folder. Sigma 4.05 introduces a new combined format of record (LongText.rec) and a storage location in the Sigma\Data folder. The Remote Alarm Manager does not recognise the file. Resolution Upgrading an existing Sigma site to Sigma 4.05 with RAM installed, and where RAM is required to use Sigma Long Text messages. Upgrade the Sigma system and retain the Sigma\Data\LongText folder.   Adding a new Long Text message Create the new message using the Sigma 4.05 Long Text editor. Copy the message and create a new message called Ltxt???.txt under Sigma\Data\LongText,   Configuring a Sigma 4.05 system where RAM is to be installed, and where RAM is required to use Sigma Long Text messages. Creating a Long Text message Create the new message using the Sigma 4.05 Long Text editor. Create a new folder Sigma\Data\LongText. Copy the message and create a new message called Ltxt???.txt under Sigma\Data\LongText, where ??? is a unique number.

Issue When trying to right click on the Xenta object in LonMaker to get the Plug-in option, it is not in the dropdown list. Unable to open plug-in for Xenta 100 series devices Environment Xenta 100 Plug-in LonMaker NL220 Xenta 101-VF, Xenta 102-ES, Xenta 102-B, Xenta 102-VF, Xenta 102-EF, Xenta 103, Xenta 104-A, Xenta 110 Cause If the option to launch a plug-in is not available, it may be because the plug-in is not installed and/or registered.  Plug-ins for most Xenta 100 devices are accessed through the function block, right-clicking on the controller will not bring up the correct menu. Most LON plug-ins are launched by right-clicking on the function block, not the controller.  The exception to this rule is the Xenta 102-AX, which requires you to right-click on the controller. Resolution Ensure the correct version of the plug-in you are trying to launch is installed and registered. Navigate to LonMaker > Network Properties > Plug-in Registration > Already Registered. If not, Register. In general, Xenta ASCs require you to right-click on the function block and select Plug-Ins to launch the plug-in. Note: It may be necessary to first add a function block in LonMaker, even if SNVT bindings are not required.

Issue Error displayed: Enhanced Alarm Delivery "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ. The system will now shutdown."   Product Line Andover Continuum Environment Windows OS Cause The issue is that MSMQ is not installed on the machine or the installation is corrupted. MSMQ is a windows component that needs to be installed for enhanced alarm delivery. Resolution Install MSMQ from the Windows Control Panel > Add/Remove programs or Add/Remove Windows Components Reinstall Continuum NOTE: There have been instances where uninstalling MSMQ from Add/Remove Windows Components then allowing Continuum to install MSMQ resulted in a successful installation of the MSMQ.

Issue It is not possible to access graphics in a Xenta 5/7xx from a smart phone mobile app. Environment Xenta 511, 527, 711, 731 Smart Phones: Apple iPhone, iPad, Android Cause Graphics in a Xenta 5/7xx webserver render in the web environment using Java.  There is not currently a smart phone in the market that is works with Java applets. Resolution There is currently no supported mobile solution for viewing graphics in a Xenta web server.