Building Automation Knowledge Base

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

Issue During installation and commissioning of a MNL-800, a component labeled MFC21 on the backplane was damaged. Is it necessary to replace the backplane? It seems like the MNL-800 is still completely functional.  It's reading all of its inputs and the program logic is controlling the outputs accordingly. Environment MNL-800 Cause The issue is typically a ground loop between full-wave and half-wave devices or power supplies connected to the UIs and / or AOs.  MFC21 is a Multi-function Ceramic protection capacitor / varistor component connected between the internal +15 VDC and earth ground (not common).  This and the other 28 varistors on the base board provide various forms of protection.  MFCs have burned out in situations that contain one or more transformers and a combination of full-wave / half-wave devices. Connections (common) between these devices can cause undesired ground loops (especially where transmitters are involved). It may also be related to how the transformers are wired (e.g. 24H / 24G or one side tied to earth ground).  The MNL-800 is a full-wave power supply device. Resolution Review the power wiring of all connected I/O. Replacing the backplane is ideal because it will provide proper protection for the next voltage spike. Without a functional MFC21, the logic card may get damaged.

Issue The Enterprise Network Server is licensed for 3 subordinates but when trying to add one it faults with the message "exceeded device limit of three"? Environment G3 Enterprise Network Sever Cause If stations had been added to the Niagara Network in the Enterprise Network Server and then deleted the subordinate count in the license does not reset. Resolution Restart the station and the subordinate count in the license will be reset to the correct number and allow the addition of more stations if the limit has not been reached.

Issue A Niagara R2 / ASD integration has two ASD services but serial tunneling only works with one service. Environment Niagara 522 or higher Cause Both services cannot support tunneling simultaneously. Resolution Enable tunneling on one ASD service at a time.  Leaving both services enabled for tunneling will only allow the first ASD service to allow a tunnel connection.  A station restart may be required.

Issue Error message displayed when booting the Network 8000 HOST computer indicating that the DOS file system cannot be initialized or a message displayed indicating that QDOS file is busy.  If these type of messages are displayed while the HOST system is booting, the DOS applications including PSI will not be available from within the HOST system. Product Line Other, TAC IA Series Environment Network 8000 HOST Software versions 6.x or 7.x Cause During bootup, the HOST software initialization checks for the presence of a PC-DOS partition on the computer's hard drive. If this PC-DOS partition is found, the command files needed to access PC-DOS are created or modified based on the partition number containing the PC-DOS operating system.  If the system is physically rebooted by power cycling or a power fail occurs, one or both of the PC-DOS control files may be left in an unusable state. Resolution The following steps can be used to correct this issue. Exit the Host by entering a q at the Host Login. At the QNX Login enter superman for both user and password. At the $ prompt enter the following four commands, pressing the Enter key at the end of each command: chattr /cmds/start_dfs s=-b chattr /net_8000_cmds/mount_xdos s=-b frel / cmds/start_dfs frel /net_8000_cmds/mount_xdo Re-boot the HOST

Issue Specifying engineer wants to know the input impedance of the voltage inputs on the MNL-10Rxx / 15Rxx / 20Rxx controllers.  This information is not in the data sheet. Environment MNL-10Rxx controller MNL-15Rxx controller MNL-20Rxx controller Cause Job specification requirement Resolution The minimum input impedance for a MNL-10Rxx /-15Rxx / -20Rxx  UI configured as a voltage type input is 20K ohms.

Issue Prior to installing an older MNB-1000 (sitting in the office unused), the firmware was updated to the most recent release.  Right at the completion of the upgrade, an 'Error 15' occurred.  However, a power cycle of the controller seemed to reset it.  The firmware revision was correct.  A database was installed successfully and the controller communicated with the WorkPlace Commissioning Tool. What does 'Error 15' signify and is it enough of a concern to not install it on a jobsite? Environment MNB controllers WorkPlace Commissioning Tool Cause Error 15 indicates that WorkPlace Commissioning Tool could not determine if the controller restarted. Resolution Since a connection was possible after the firmware upgrade and a power cycle, then the MNB-1000 is fine to continue to use.

Issue A jobsite consists of several (independent) buildings each installed with a UNC-520. They are not networked together (i.e. standalone) and each one has a different projectID.  The customer would like to use Workplace Pro to do some occasional changes and scheduled database backups.  Can a copy of Workplace Pro be purchased / provided without the need to purchase the Enterprise Server as well? Environment Niagara R2 Cause Unusual jobsite configuration with several standalone UNC-520 controllers and no Enterprise Server. Resolution Workplace Pro can only be purchased along with the Enterprise Server software.  It cannot be purchased in any other configuration. Perhaps an arrangement can be made with the local Schneider-Electric branch or I/A partner for temporary usage of a pc with Workplace Pro.

Issue What is a quick way to read a dynamic value from LNSDDE server? Environment InVue Cause Trying to confirm if the value of a snvt is updating and reading accurately - without using InVue. Resolution LNSDDE server and Microsoft Excel are both DDE compatible. Open a new sheet or book in Excel. Find the snvt in LNSDDE and copy / paste the link into one of the cells in Excel.  After hitting enter, the cell will display the dynamic value of the selected snvt. This is a good way to troubleshoot the LON programming and controller communication from the field all the way back to the server - without adding InVue programming to the troubleshooting process.

Issue How many points per driver can an Enterprise Network Server (ENS) be licensed for? Environment I/A Series G3 ENS Drivers ENS-BAC-NET ENS-BAC-CL ENS-MOD ENS-MOD-SL ENS-OPC ENS-SNMP Cause Each of the ENS base drivers includes support for 500 points. Additional blocks of 500 points each can be added to the license.  Resolution In terms of licensing, there isn't a limit to the number of points each driver can be licensed for. However, the actual number of points used will be dependent on the computer's resources (CPU, memory etc.). 

Issue Existing site with a MSC-NC and several MicroSmart controllers no longer communicates.   The user cannot view real-time data.  The MSC-NC is proven defective.  Can a UNC-520 be used in place of the MSC-NC?  There are two, separate MicroSmart trunks connected to the MSC-NC. Environment DMS Niagara R2 Cause Product failure and obsolescence Resolution Remove the MSC-NC and replace it with the UNC-520 running a station with two MicroSmart Services - one per physical controller trunk.

Issue Does Schneider Electric support the Niagara Andover Infinity Driver? Environment Niagara Infinity Driver Infinet Drivers Cause Unable to get Andover Infinity Driver working. Resolution The Andover Infinity Driver was created by and for Tridium.  Schneider Electric do not sell nor support this driver and all enquiries should be referred to Tridium.

Issue How does the controller-resident schedule work in a Revision 11.x MicroSmart controller? Environment MicroSmart controllers revision 11.x and 10.x Cause Main DMS panel and/or NC panel were removed. Resolution With the loss of schedule control from the DMS or NC, each controller has two built-in schedules numbered 1 and 2. The Start/Stop point requiring a schedule can be assigned either one of these schedules followed by a letter A or letter B. Letter A stands for 'always' and letter B for 'backup'. With no DMS or NC present, enter the schedule as 1/A or 2/A.  Assign 'off' and 'on' times as required. Remove any reference to a DMS or NC schedule number (i.e. set it to a value of 00). 

Issue Analog inputs on a MicroSmart controller are all reading a negative value. Environment MicroSmart controllers (all versions) Cause Hardware issue or sensor failure Resolution If the connected sensor is a RTD, a negative reading reflects an electrical short somewhere between the controller and the sensor.  Note that a high positive reading reflects an electrical open circuit. If the connected sensor is a 4-20 mA device, it typically reads a high positive value which reflects an electrical open circuit.

Issue The drop down menu to select WorkPlace Tech help manuals does not function in Internet Explorer 11. Environment WorkPlace Tech 5.8.6 Internet Explorer 11 Cause Internet Explorer changes how they handle compatibility mode for websites and webpage used to access the help files requires updating in a new version of WorkPlace Tech. Resolution Use one of the following options to access the help files Access them directly by going to the folder they are stored. On a Windows 7 (64 bit) operating system this is C:\Program Files (x86)\WorkPlace Tech\Help by default. Modify the index.htm, BACnet.htm, LON.htm, search.htm, Sensors.htm, and Software.htm files found in the C:\Program Files (x86)\WorkPlace Tech\Help\bin directory. Add the following line in front of the first "meta http-equiv=" line:   <meta content="IE=EmulateIE8" http-equiv="X-UA-Compatible" />   <meta content="IE-EmulateIE8" http-equiv="X-UA-Compatible" />

Issue Is the Niagara G3 Andover Infinity driver compatible with the NetController II (Model CX 9680)? Environment Niagara G3 any version Cause Site has a trunk of NetController II controllers Resolution The driver was never tested with the NetController II.

Issue On a DMS jobsite, Operator Interface (OPRIF) does not display the MicroSmart controllers on the screen.  There are a dozen controllers and they are confirmed as communicating to the DMS but they do not appear in the controller list in OPRIF. Environment OPRIF DMS MicroSmart Cause In OPRIF, the MicroSmart controller list displays 32 controllers per screen and it reserves spaces even if that controller address does not exist on the jobsite. If the controller addresses begin with number 33, then the first screen will appear as blank.  However, the second screen will list controllers 33 to 65. Resolution Use the Page Down and Page Up buttons to move back and forth between controller lists 1-32 and 33-65.

Issue An "Invalid Pointer" error message is displayed when attempting to open an existing project in the WorkPlace Tech Tool software. Environment WorkPlace Tech Tool release 5.x.x Cause The WorkPlace Tech Tool project database file (project-name.wtp) is missing or is corrupted. Resolution Use the WorkPlace Tech Tool software to recreate the project and reassociate the applications with the project. Navigate to the project folder using Windows Explorer. If the a .wtp project database file is present, rename the file, by adding .save to the end of the existing .wtp file name, for example, rename My_Project.wtp to My_Project.wtp.save Close Windows Explorer. Open WorkPlace Tech but do not open the project. Under the WPT Project Menu, select New Specify the name of the project. Use the same name as the existing project folder. Using my example from step 2, you would create the project named My_Project In the displayed "Add Application to Project From..." window, select the "Unassigned File" tab. All existing applications for that project will appear in the list. Select them all by holding down the [Ctrl] key on your keyboard and clicking on each file shown in the list. Click the [OK] button at the bottom of the window to add all the selected applications to the newly created project. Exit from the Workplace Tech Tool software. When you reopen this project, all applications should be shown and any of them should open properly.

Issue The thermostat appears to be in OFF mode and can't be cycled through the modes as indicated by the manufacturer's directions.   Environment Venstar T2700, VST2700 thermostats for red-wire control connected physically to a controller Cause It seems that the polarity of the dry contact was set to the default Normally Open (NO) state. Using the Venstar EZ-Programmer to apply the correct settings for use with an occupancy point did not overwrite the polarity of the Venstar's dry contact, but did overwrite the Dry Contact Operation. Also, by wiring everything up first, we did not power up the thermostat to change the mode before it got the closed dry contact command from the BAS. So when we did power everything up, the dry contact was closed, but the thermostat understood that this was an "unoccupied" command since it was still set to NO. Even though the security settings allowed the mode to be changed, when Dry Contact Operation is enabled, the mode can only be changed in occupied mode. When the thermostat goes unoccupied, it stays in whatever mode it was in previously, and controls to the unoccupied setpoints. By not realizing that the EZ Programmer didn't overwrite the polarity, we assumed the dry contact operation and polarity were correct and a closed dry contact would enable the occupied mode.   Resolution This issue can be resolved by powering up the thermostat before connecting the dry contact relay and changing the mode to "auto". If already wired, make sure the dry contact polarity is set to Normally Closed (NC) and Dry Contact Operation is "Yes". Then the modes can be cycled while occupied. < acc0432manualrev1.pdf="" manuals="" support="" www.venstar.com="">

Issue SmartStruxure with I/A Series Micronet BACnet (MNB) controllers Environment SmartStruxure version 1.4 and earlier I/A Series Micronet BACnet (MNB) controllers Cause Need to know if it is possible to use MNB controllers with SmartStruxure.  Resolution I/A Series MNB controllers can be integrated into SmartStruxure as 3rd party BACnet devices. For more information on SmartStruxure with MNB controllers, download document MNB BACnet Support within a StruxureWare Building Operation System Solution Guide.