Building Automation Knowledge Base

Issue Cross Reference of Obsolete Field Devices to Current Schneider Electric Field Devices. Environment Field device replacement Cause Unknown replacement for obsolete field device part number Resolution There is an Online Cross Reference Guide located on our Schneider Electric Buildings Website. Enter the old part number into the field for part to cross reference & click on the search button not the ENTER key. The ENTER Key clears the part number entry. The Manufacturer's name is not required for a product search. Contact Product Support when no cross reference is found for additional help.

Issue What to check when viewing your Xenta 555 webpages and finding areas/pages grayed out, For example the Time Schedule page. Environment Xenta 555 Cause Xenta 555 firmware must match the correct version of Xbuilder.   Resolution Xenta firmware Xbuilder Software version 5.00 5.00 5.01 5.01 5.02 5.02 5.03 5.03 5.10 5.10 5.11 5.11 5.12 5.12 5.13 5.13 For example: If your Xenta 555 is running firmware version 5.1.1 and your project is Xbuilder version 5.0.3. Install Xbuilder 5.1.1 Open your project in Xbuilder 5.1.1 Your project will be upgraded. Then upload project to the Xenta 555.

Issue A Niagara R2 / MicroSmart integration is creating IbsMs invalid condition and receive message entries in the Standard Output Window. Here is an example: ***IbsMs receive message: 454130433130464631433543 ***IbsMS invalid condition received: 28 Environment Niagara R2 MicroSmart Cause When the points are learned into the UNC station, it is in a specific order and the station records this information for making requests. If that order is changed in the MicroSmart, then the mismatch occurs. Resolution The mismatch occurs specifically when a record number is reused (i.e. a point is deleted and a new point created) and the point types are different. For example, an Analog Output point is deleted and a Start/Stop point is created – with the Start/Stop point being assigned the record number that was previously used by the Analog Output point. The UNC is expecting an analog point for that record number but is getting a response from a different point type. There are two choices to fix this situation: The controller is to be re-learned. Unfortunately, this will result in lost links and the need to go back and re-link all bindings done with this controller's database. Re-load the MicroSmart controllers with the original database so that it matches the learned database in the station. To find the offending controller(s), turn on de-bug and see if that will provide pointers to the controller(s) creating the error message. When done, make sure to turn off de-bug as it will create a large amount of entries in the Standard Output Window.

Issue The MNB-1000 mounting base, manufactured before January 2009, does it comply with the UL 864 standard? Environment MNB-BASE-1000 UL 864 Cause Information on MNB-1000 compliant with the UL 864 standard. Resolution The MNB-BASE-1000 has electronics on it that cannot be used for smoke control if it has a manufactured date prior to receiving UL 864 certification (January 2009).

Issue Opening java or TGML graphics is very slow or they don't open at all. You may also have various java error popups. Environment TGML Graphics Cause The Java applet is limited to the amount of memory it is allowed to use. This will also limit how much memory java or TGML graphics are allowed to use, and can slow the rendering. Resolution It is possible to expand the amount of memory the Java applet has access to, and that seems to help in some cases. To increase this memory, do the following: Open the Control Panel in Windows and double click on "Java" Click the tab "Java" In "Java Applet Runtime Settings", choose "View" Find the most recent Java version runtime line (1.6.0_11) and double click on the "Java Runtime Parameters" box and add "-Xmx300m". This sets the Java maximum heap size to 300 MB. For some unknown reason, some computers with large amounts of installed memory are limited to how much memory they can assign to their Java VM. If you experience problems, just reduce the "300" to some smaller number (like 250, 200, 150, etc). However some computers have no problems setting the value to "1000". This procedure must be done to each computer individually. Also, remember to close all Internet Explorer windows for the changes to take affect.

Issue How many Video Servers can be used with CyberStation? Environment CyberStation Cause The answer to this question depends on the revision of CyberStation that is being used. Below is a list of CyberStation revisions and what quantity of Video Servers they support. Resolution CyberStation Revision   Quantity of Video Servers Below Revision 1.60   0 Revision 1.60 to 1.71   10 Revision 1.73 to 1.74 w/o SP2   50 Revision 1.74 SP2 to 1.82   100 Revision 1.90 and above   unlimited

Issue The MNB-300 mounting base, manufactured before January 2009, does it comply with the UL 864 standard? Environment MNB-300 mounting base UL 864 Cause Information on MNB-300 compliant with the UL 864 standard. Resolution The MNB-BASE-300 has electronics on it that cannot be used for smoke control if it has a manufactured date prior to receiving UL 864 certification (January 2009).

Issue If you have a double address on an SCU 1284, and the operation of the LEDs are wrong after you installed I/NET Seven rev 2.21 what do you do? Environment I/NET Seven rev 2.21 SCU 1284 Cause I/NET Site Resolution If you had set a double address in the SCU 1284, the operation of the LEDs are wrong. Both LED (Green and Red) are active permanently no matter what you set in the Door Editor(Anode/Cathode), the LED will just flash once when the door is operated. If the SCU is set to single address, the LED will work correctly. The equipment setting that will cause this issue is having a 7798C with BIN file Rev 1.08 and SCU1284 with BIN Rev 3.25. To correct this issue requires you to only change the BIN file in the 7798C from rev 1.08 back to Rev 1.06. This 1.06 Bin file is from the I/NET Seven rev 2.16 release. Please note the SCU1284 LED issue DOES NOT exist in the following BIN files in the I/NET Seven rev 2.21 release. 7798B Bin is OK 7793 Bin is OK SCU1284 Bin(3.25) is OK

Issue Transfer pressure values with units of inches of water between I/NET and LON with a 913/527/731. Environment I/NET Xenta 913/527/731 XBuilder Cause When reading pressure from LON, the value is always in metric units, Pascals, on the LON wire. When the value comes into I/NET, it will be a large, unexpected number. Resolution To read in a LON pressure value into I/NET: Create two internal points in I/NET. AO to receive the raw pressure value in Pascals AI to perform the conversion to inches of water Add a calculation to the AI to perform the conversion: P0*C0 P0 = AO created to receive the raw pressure value in Pascals C0 = 0.004 to convert value from Pascals to inches of water Set the connection object in XBuilder: From = LON SNVT_press To = AO to receive the raw pressure value The AI should be reading the correct value in units inches of water. To write a setpoint value out of I/NET to LON: Create two internal points in I/NET: AO where the user enters desired static setpoint in inches of water AO to perform the conversion to Pascals Add a calculation to the AO to perform the conversion: P0*C0 P0 = AO created to enter desired static setpoint in inches of water C0 = 249 to convert value from inches of water to Pascals Set the connection object in XBuilder: From = AO to perform the conversion To = LON SNVT_press The SNVT should be reading the correct value in desired units.

Issue What version of Workplace Tech supports Microsoft Visio 2007? Environment Workplace Tech Microsoft Visio 2007 Cause Need WorkPlace Tech to function with Microsoft Visio 2007     Resolution WorkPlace Tech 5.7 supports Microsoft Office Visio 2007, Service Pack 1, and Microsoft Vista Business, Ultimate and Enterprise. WorkPlace Tech 5.7 continues to support Microsoft Office Visio 2003, Service Pack 3, and Microsoft Windows XP, Service Pack 2. Although this release may function with Microsoft Visio 2002, Service Pack 2, and Microsoft Windows 2000, Service Pack 4, this combination has not been tested, and will not be supported by Product Support Services. For further information, review the "Release Notes / Getting Started" document for 5.7.

Issue Time schedule in Menta on Xenta 731 using a Central Time Chart not becoming active. Environment Xenta 731 Menta TSCHI Central Time Chart Cause Even though a Central Time schedule on the server level can be created with an event that spans 2 days (23:00 to 01:00), the TSCHI block in Menta does not process the day change and will not activate the schedule. Resolution The Java schedule does not allow creation of these schedules. 2 separate events would be required to work across 2 days (should you need a schedule to be active across midnight). For example, running a schedule from 6pm to 2am you would need 2 separate events: one from 6pm (18:00) to 12-midnight (00:00) and one from 12-midnight(00:00) to 2am (02:00).

Issue When using a Niagara R2 Enterprise Server with a "Remote Printer Recipient" on a large network with many printers, the Enterprise Server can take several minutes to complete its station startup following a reset. Environment Niagara R2 Enterprise Server Network printers Cause This situation is possible due to the remote printer recipient object that is attempting to populate its network printer recipient list. This would not be noticeable unless there are hundreds of printers on the network. This is how the remote printer recipient is designed to function. Resolution Possible workarounds for very large jobs affected by this would be to: Re-configure the customer's network so there are not so many networked printers Define local printers (or map network printers as local printers) in order to use the Local Printer Recipient Use the Vykon Alarm client to send alarms to network printers. Be advised printers other than dot matrix types will print one alarm per page.

Issue Defining a device name for each Network 8000 Microflo II controller is possible when it is configured under a GCM.  When defining it via a Niagara R2 UNC station, using the ASD driver, it is not possible. Environment Niagara R2 UNC station Network 8000 Microflo II controller Cause Not a supported feature in the ASD driver. Resolution Due to the maturity of the Microflo II product this is a feature that will not be incorporated into the ASD driver.

Issue Niagara R2 GCM driver version 2.304.522 may generate errors when uploading VEO information. Environment Niagara R2 GCM driver version 2.304.522 Cause This error is generated if there are attributes in VEO## list but there is no LABEL block associated with this VEO. Resolution There is a CreateVeoGxPages button located on the Block List Manager screen. This feature is intended to upload the GCM's View/Edit/Override information and generate the appropriate display screens. This function uploads the VEO information successfully, however it may fail to complete the process and generate a "NullPointerException".  To work around this error, create LABEL blocks in the GCM for each VEO used. Make sure to properly name each LABEL block starting with VEO and ending with 01 to 10. It is also possible a "ClassNotFoundException" will be generated during this upload process. This error is caused by the attribute types found in the VEOs uploaded. The GCM driver can only handle AV and DV types in the list. Any other types in the list will cause this error. To eliminate the error all non AV or DV attributes must be removed from the VEO attribute list(s) in the GCM.

Issue Configuration of BACnet Alarming from 3rd party BACnet IP Device that does not support Dynamic Device Binding. (i.e Notifier Fire Panel and etc.) Environment 3rd Party BACnet IP device Notifier Fire Panel Cause When 3rd party BACnet IP device (i.e. Notifier fire panel) supports Dynamic Object Binding, as Continuum WS supports Dynamic Device Binding only, the alarm recipient device (i.e. alarm recipient Continuum WS) needs to be set up in a different way to provide Static Binding information to the 3rd party device as below in order to get the alarm delivered to Continuum WS from the 3rd party BACnet IP device. Resolution Open the editor of the EventNotification in the 3rd party IP device from BACnet View. Go to Delivery tab, click Add Recipient button, or double click the existing recipient WS. Check "BACnet Address" checkbox, and uncheck "Guarantee Delivery" checkbox. Type NetNumber:MACAddress manually as below and save. ** The NetNumber is the BacNet Number from 3rd party device's perspective. The netnumber is 0 by default for most devices but need to consult with the device vendor to get the correct NetNumber. NetNumber of 65535 can be used for broadcasting. ** The MACAddress is the WS's IP address in Hex+BAC0 at the end. For example, Continuum WS IP address is 10.11.12.13, the MACAddress should be 0a0b0c0dBAC0. ** The value for the attribute is 0:0a0b0c0dBAC0. (It can be set to 65535:0a0b0c0dBAC0 for Broadcasting)

Issue When trying to install Niagara R2 version 2.301.330, the process halts and reports that Java Virtual Machine (JVM) is not installed. What version of JVM is required? Environment Niagara R2 version 2.301.330 Cause All Niagara R2 versions prior to 2.301.514 require Microsoft's Java Virtual Machine.     Resolution All revisions of Niagara R2 prior to 2.301.514 require Microsoft's JVM. To confirm if it is installed, open a Command Prompt window and type "jview" then press Enter. This command will display the current version of Microsoft's JVM (or that it is not installed). Download and install Java_Virtual_Machine_for_WinXP.exe. All revisions of Niagara R2 starting with 2.301.514 and beyond require Sun's JVM. To confirm if it is installed, open a Command Prompt window and type "java -version" then press Enter. Visit http://www.java.com regularly to keep the JVM updated. The Microsoft and Sun JVMs can co-exist on the same Niagara host computer.

Issue What is required to transfer your MicroNet View license to a new computer? Environment MicroNet View PC Cause Transfer MicroNet View license from existing PC to the new PC. Resolution On the existing computer: Close MicroNet View and all associated programs. Go to the folder “C:\MicroNet\Binary\VCommon\License” Copy the “WWSUITE.LIC” file off the computer. Go to the C:\MicroNet\Projects folder copy your Micronet View project off the computer. Remove the MicroNet View dongle and the I/O server dongle from the old computers parallel port. On the new computer: Install MicroNet View on the new computer; if it is running Windows XP you must install the Hasp dongle driver from the Hasp folder of the MicroNet View installation CD. Plug the two dongles into the parallel port of the new computer. (The computers parallel port must be a manufacturer’s standard parallel port, additionally added parallel port cards do not allow the dongles to be recognized). Copy the “WWSUITE.LIC” license file onto the new computer under the “C:\MicroNet\Binary\VCommon\License” folder. Copy your Micronet View project onto the computer under the folder “C:\MicroNet\Projects”. Re-boot the computer. Open the MicroNet View project manager (C:\MicroNet\Binary\Project\MNProject.exe). From the menu select ”Find and register a project” Find your project, highlight your project, and press OK. You should now be able to run your MicroNet View project on the new computer now.  

Issue How to load the Pocket I/A 4.1 software on a handheld device (PDA) Environment Handheld device (PDA) Pocket I/A 4.1 software Cause An Installation manual for the current version of the Pocket I/A software is not available. Resolution Use the following procedure to install the software:   Open ActiveSync on the computer and establish a connection to the Pocket-PC device.  It is not necessary to create a partnership when making this connection. Copy the CAB file and paste it somewhere on your handheld device, the Storage Card is a recommended location. After copying the file to the device, disconnect it from the computer. Open Pocket-PC's File Explorer, located into the Programs. Browse the storage card or the location used to copy the CAB. Select and run it, and a window will appear, which asks to choose a location to install the program. It can be the Device or the Storage Card, so select either and click below on Install. The process after that is fully automated and after the installation is complete it will show a confirmation screen. Refer to the help file installed with the Pocket I/A software for information on using the program.

Issue When to use ERIE Replacement motors 30-158-A,B,D,T,U instead of 30-118-A,B,D,T,U? Environment ERIE Replacement motors 30-158-A,B,D,T,U ERIE Replacement motors 30-118-A,B,D,T,U Cause Find the correct replacement part for the AH/AG Actuator. Resolution Use 30-158-A,B,D,T,U if AH/AG Actuator was made after January of 2003.

Issue When filtering, column sorting or column selecting is made inside an Alarm or Event Viewer, the changes are not saved when the viewer is closed. Environment Vista Workstation Cause Changes made to the current view are considered temporary. Only changes made to the properties of the Alarm or Event Viewer are stored permanently in the database. Resolution To make your changes persistent, do the filtering, column sorting or column selecting by right clicking the Alarm or Event viewer object and select properties.