Building Automation Knowledge Base

Issue I/A Series R2 OBIX Driver part number Product Line TAC IA Series Environment I/A Series R2 Enterprise Server I/A Series R2 UNC Cause In order for an I/A Series R2 Enterprise Server or UNC to function as an OBIX server, the Enterprise Server or UNC needs to be licensed for it. This is required for integration to I/A Series G3. Refer to Configure oBIX to integrate a Niagara R2 station and a Niagara G3 station. Resolution Part number: IA-DRV-OBIX This is the part number required for each Enterprise Server / UNC that needs to function as an OBIX server.   *Update - I/A Series R2 has been discontinued. As of January 1, 2015, the part number IA-DRV-OBIX will no longer be available for purchase. 

Issue Error while creating the Continuum DataBase in 64-bit Operating System. SQL Server Installation Package cannot be opened. Microsoft SQL Server 2005 Setup SQL Server 2005 Setup cannot continue because the installation package could not be opened. The installation package has a missing file, or you are running a 32-bit only Setup program on a 64-bit computer. To continue, verify the SQL Server 2005 package you are running is supported on WOW64. If you are certain that you are running a supported SQL Server 2005 package, and you continue to see this message, contact the application vendor. Product Line Andover Continuum Environment Continuum 1.93 and below 32-bit Operating Systems Cause Continuum 1.93 and below versions do not support in 64-bit Operating Systems. Resolution Install Continuum in a supported Operating System. Read and follow the Continuum compatibility matrix before installing.   Download the Andover Continuum Compatibility from Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue When saving program changes adding new data sharing points an error is displayed; Infinity controller error: The controller has reached its BACnet binding limit. Product Line Andover Continuum Environment Continuum Cyberstation Cause The controller has reached its known devices limit and is rejecting any further target devices from being added. The known device limits are 255 for bCX controllers and 32 for b3 controllers. See Limit of how many devices a Bacnet controller can know about (Known devices)  for more details. Resolution Make a change in the controllers to reduce this number of known controllers by modifying how much data is shared and/or reduce the number of Workstations that alarms are delivered to. Once this is done then restart the controller for the known devices table to be rebuilt.

Issue Can a BACnet Automation Server and b3's be programmed offsite with temporary IP addresses? Are there any considerations to be made when moving the system to site and configuring with new IP addresses for the Enterprise Server and Automation Server? Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server b3xxx Controllers Cause Do not have complete IP address details for the new project but need to start programming the controllers in the office. Not sure if there will there be any issues when moving this to site. Resolution You can do this programming with a temporary IP address for the AS and then when you get to site Change the AS IP address to whatever is required. See Changing IP address of Automation Server that explains how to change the AS IP address.

Issue A network of GCM-86000s with EtherNet NIMs does not have bi-directional communications between all GCM/ NIMs. It is a shared network with routers. Some symptoms reported include: A GCM/ NIM may be able to send to some GCM/ NIMs, but not to others. A GCM/ NIM may be able to receive data from some GCM/NIMs, but not from others. A GCM/ NIM may be able to send to a GCM/NIM, but not receive data from that GCM/NIM. You might be able to "ping" all GCM/NIMs on the network, and ACCESS all of them from the GCM menu, but still have issues as in 1-3 above. Product Line TAC IA Series Environment GCM-86000 series (including LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK) EtherNet NIM (GCM-ETH-001) Shared (customer's) EtherNet LAN with routers Cause In the NIM block of one or more of the affected GCM/ NIMs, the IP Multicast address (IPMLT) is set incorrectly. In the following example, the NIM block parameters were taken from a network of four GCM/NIMs, experiencing all four of the issues noted above.     GCM#1 GCM#2 GCM#3 GCM#4   5.4A 5.3A 5.4A 5.4A   11.2T 11.2T 11.2T 11.2T PNLIP 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 RTRIP 010.020.000.001 010.020.000.001 010.020.000.001 010.020.000.001 DIRSV 010.020.000.028 010.020.000.028 010.020.000.028 010.020.000.028 ETHML 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 IPMLT 010.020.000.019 010.020.000.019 010.020.000.019 010.120.000.019 IPSUB 255.255.000.000 255.255.000.000 255.255.000.000 255.255.000.000 UDPPT 1235 1235 1235 1235 Resolution On a shared network with routers, the IP Multicast address (IPMLT) should be the same as the Panel IP address (PNLIP); IPMLT = PNLIP. Using the appropriate FLASH clear procedure, and set the NIM block parameters so that IPMLT = PNLIP. In the example below, make the changes to the IPMLT as high-lighted in yellow.   GCM#1 GCM#2 GCM#3 GCM#4 GCM Rev. 5.4A 5.3A 5.4A 5.4A NIM Rev. 11.2T 11.2T 11.2T 11.2T PNLIP 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 RTRIP 010.020.000.001 010.020.000.001 010.020.000.001 010.020.000.001 DIRSV 010.020.000.028 010.020.000.028 010.020.000.028 010.020.000.028 ETHML 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 01.20.96.01.00.00 IPMLT 010.020.000.028 010.020.000.019 010.020.004.008 010.020.004.009 IPSUB 255.255.000.000 255.255.000.000 255.255.000.000 255.255.000.000 UDPPT 1235 1235 1235 1235 See the Nim Networking and Configuration Guide, F-25955-4, Chapter 2, "GCM Shared Network Address Guidelines (Routed Network)" for details. For EtherNet NIMs with firmware revisions 11.2P or 11.2T, see "Special NIM Address Switch Functions" for the REVISED FLASH clear procedure. For EtherNet NIMs with firmware revisions 11.1F or earlier, see "Flash clear" procedure for GCM Ethernet NIMs (GCM-ETH-001) with firmware prior to revision 11.2P.

Issue TGML Graphic Alert: ReferenceError: "test" is not defined. (cmd#16) Product Line TAC Vista Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML has used a variable that has not been defined. Resolution Determine which script tag is generating the error. When did the error occur? When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 16 of the code. The variable name is in quotes.  In this example, find where a variable named "test" was used. Verify that the variable has been declared and defined prior to being used. Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue I/NET Seven running on a Windows 7 computer that has an issue with fields not aligning as shown below: Product Line TAC INET Environment I/NET Seven Cause This is caused by increasing the text size of the workstations display from the default setting of 100%.  It will occur on any Operating System not just Windows 7. Resolution Make sure the Display settings Text setting is at the "Default setting (100%)".  If it's any larger then it will distort the text and editor titles will be miss aligned with the text displayed in the summary / editors.  You change this as follows: Windows 7:  From the Control Panel: - Select Appearance and Personalization Under the heading Display select “Make text and other items larger or smaller” Change setting is set to Smaller – 100% (default). You will then need to log off and then back in for these changes to take affect. If this does not resolve the issue, refer to Windows Alignment Issue for I/NET display. Windows XP / Server 2003: From Control Panel: Double-click on Display Select the Settings tab (top right) Click on the Advanced tab Within the Display section select the "Normal size (96 DPI)" from the DPI setting drop down box. A restart of the workstation may be required to apply these changes.

Issue It is not possible to extract a Menta file directly from a Xenta programmable. If a backup of the Menta file, or a backup of the Vista database is not available, there is no way to extract the program from the controller. "File object contain no actual MTA file" when trying to open a Menta file. Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Going out to a job site without a database backup, or a backup of the Menta applications (.MTA), leaves no way to view the Menta that is running in a Xenta programmable controller. Resolution Options are: Find a backup of the .MTA Menta application that has been downloaded previously into the controller. Find a backup of the Vista database.  Menta files are stored in the Vista database for each programmable controller. To extract a Menta file from a Vista database, the preferred method is described in Get all MTA files saved from a Vista Database. To extract the files one at a time, right-click on the controller and select Edit. Connecting to a live controller, it is possible to view all public values inside the controller and to extract a .COD code file.  Unfortunately, these cannot be used to create a .MTA to view the logic.

Issue OP is plugged into Xenta base unit, or wired up using terminal strip on the back, but the screen is still blank. Product Line TAC Vista Environment Xenta OP Xenta programmable controller Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Xenta 100 series ASC Cause Either power is not properly being applied to the OP, or the contrast on the LCD has been adjusted all the way down making the menu invisible. For troubleshooting connectivity issues please see the following articles: Xenta programmable controllers: "No Answer" on an OP when connecting to a Xenta 280/300/400 Xenta 100 series ASCs: Use a Xenta OP with a Xenta 100 controller Resolution Check OP port connection Check power connections on terminals 3 and 4 Make sure the contrast hasn't been adjusted all the way down

Issue On which LANs can you place an FOI ring? Product Line TAC INET Environment I/NET Site Cause On which LANs can you place an FOI ring? Resolution A Fiber Optic Interface can be placed on: Host Controller Sub-LAN See Fiber Optic Interface, Ethernet, C-LAN, and Sub-LAN communication for further information.

Issue When installing Cyberstation V1.93 with a Single User Security Key fitted the following message may be displayed when starting the install: The current version of Continuum is setup to use a database that is not on this computer, but the security key is Single User and does not allow remote databases There is an option to continue installation. Product Line Andover Continuum Environment Cyberstation V1.93 Cause The Workstation has previously been configured to operate as a LAN workstation connecting to a database on a separate server. Resolution Select the continue option, Cyberstation V1.93 should then install correctly, run the database initialization and the Workstation initialization, then you should be able to start up Cyberstation. By re-installing all of the files will be updated and the system will then operate as a single user as required. Also see How to identify what is enabled on a Continuum Security Key to check that the Security Key does have the configuration as expected.

Issue Video in Endura/Digital Sentry system can't be shown in I/NET Cameras can not be learned from Video Server Product Line TAC INET Environment I/NET Endura Digital Sentry Internet Explorer Cause The possible cause of it may be the proxy setting in IE browser. Resolution Cancel the proxy setting in IE browser. Type the IP address of the camera or encoder in IE browser. If the video displays in IE browser, it should work in I/NET now. For more issues about video that can't be seen in I/NET, refer to Video or Alarm of Video System can't be seen in I/NET.

Issue What is the data format for the OPC and ModBUS options in the ModBMS software? Product Line Satchwell Sigma Environment ModBUS Slave OPC Server ModBMS OPC DA AE OPC XML Cause Supported Data formats Resolution The supported data formats are listed in the configuration and release note for the ModBMS software. See ModBMS Release Note 3.2.pdf. OPC XML is not supported by ModBMS (see IC GEN OPC and XML-DA data type)

Issue A red exclamation mark is seen with a discovered MNB controller icon in WorkPlace Commissioning Tool Product Line TAC IA Series Environment I/A Series WorkPlace Commissioning Tool I/A Series Micronet BACnet controller (MNB) Cause The WorkPlace Commissioning Tool has lost communications with the BACnet device Resolution Resolve the BACnet communications issue. Refer to BACnet MS/TP Bus Communication Troubleshooting Checklist. Refer to the table below which is extracted from the IA Series MicroNet BACnet WorkPlace Commissioning Tool and Flow Balance Tool Users Guide. Icon and Type Applicable Devices Meaning Remote I/O Warning MNB-1000 A remote I/O module connected to the MNB-1000 controller is in a state other than "online and configured" (status code 0x03). Lost Communication All Devices The Tool is no longer able to communicate with the device. Operation in Progress All MNB-xxxx Devices Device is in the midst of an operation. For example, the device may be undergoing a firmware upgrade, or an MNB-Vx VAV Controller may be performing a Check Rotation.

Issue On larger databases it is time intensive to resynchronize the drawing by creating group binding from the System Plug-in. Is it possible to manually set the TAC group binding on a Xenta Server controller to enable LACnet communication? Product Line TAC Vista Environment LonMaker Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause The TAC group binding can be created manually by editing the group binding properties. Resolution First identify what group ID is the TAC group bindings. Use Verifying Xenta Group Bindings in an LNS system as a guide to identify the group number of the TAC group binding. Follow these steps to manually create the TAC group binding in a Xenta Server: Create the Xenta Server in LonMaker and commission it. Drop a Virtual Function Block for the Xenta Server Drop a msg_out shape on to the Virtual Function Block of the Xenta Server and select tag_0. Find a Virtual Function Block for one of the Xenta programmable controllers.   a. Right click on the tag_0 reference shape and select properties.   b. Expand the connection details and then highlight the source signal in the Hub window. c. Click the Target pane. d. Click the "Add FB/SNs.." and add the Xenta Server Virtual Function Block. e. Select the tag_0 under the Xenta Server Virtual Function Block. f. Click the "Add" button. g. Click the "OK" button. The Xenta Server now has the TAC group binding created.

Issue When adding doors to Tenant or change the number of individuals in Tenant editor, there is always an error that the change can not be saved. Product Line TAC INET Environment I/NET Cause The maximum individuals for one door in DPU7920 with DPU48K and SCU 1284 with firmware newer than 3.24 is 64000. Resolution Try to decrease the individual number for the door within 64000. Do not forget the Tenant disabled. The individual number of disabled Tenant for a door is also inclusive in this 64000. Refer to Door selection is not possible in Tenant editor for more details about the individual number limit for the door controller.

Issue When Upgrading I/NET Seven that is currently running older rev of software to version 2.40, while doing equalization, an issue arises when the editor for the site and key information does not come up. It skips right over that and comes up with the SQL log in and password. Once this is entered, it proceeds to upgrade but when I/NET is started it gives an Initialization Failure. Product Line TAC INET Environment I/NET Seven revisions 2.XX and higher but below 2.40 Cause An existing instance of SQL was present there which prevented the software from completely installing. Resolution Uninstall and reinstall of the system as described in Procedure for uninstalling I/NET Seven on a stand-alone host. Once these are completed, then restart again. Verify connectivity to the system. Re promote the Filemaster of Server, verify that the snapshot is created and the database is intact. Repromote the clients and verify that they are all communicating and that Equalization is in fact working again.

Issue Unable to set up Automatic DPU Restore on a local Host PC as the option is grayed out. Product Line TAC INET Environment I/Net version 2.XX and above Cause When the system is using the Server/Remote Client application the changes can only be done from the PC or Server. Resolution To resolve this issue the Automatic DPU Restore needs to be enabled at the Host PC or server so that the PC that is making the changes will automatically download them to the necessary DPUs. For more information see Automatic DPU Restore.

Issue How to display humidity level or CO2 level on a STR350/STR351? What type of sensor can display humidity or CO2 level? Product Line TAC Vista Environment STR 350 SHR 100 Cause All Schneider Electric made humidity sensors and CO2 sensors do not have display. In order to display the value locally, need to wire the sensor to a STR 350, and configure the STR 350 for display. Resolution Wire humidity sensor or CO2 sensor to STR 351 or STR 351's AUX. input channels. Following STR 350/351 manually setup without plug-in (nciOption1 and nciOption2) to add the STR 350 or STR351 into the network. Change nciOption2 bit 6-8 according to the sensor type. Note: If using a plug in or adding the STR 35X in XBuilder, can simply follow the configuration guide. Set nciOption2 bit 9 to a value of 1. This allows the humidity or CO2 to be displayed on the STR.

Issue Global and indirect points are very useful and are usually a mandatory part of most application programs. It is seen that in the event of a LAN failure or any failure of the indirect point being updated, the indirect point will be flagged as "Old Data." When this occurs any process using the indirect point as a variable, say, calculation extension, event extension will freeze at the last status/value before the old data on the indirect point was detected. Even though other parameters are still valid, the calculation and the event extensions will remain frozen, and some occasion remain in this state even when the old data is cleared from the source. Any subsequent process that uses the calculation or event definition will also be frozen. Any PID DDC Modules, Floating DDC Modules and 2 Position DDC Modules that uses the indirect point that has been flagged as "old data" will force those DDC modules to "Fail Safe" mode. Product Line TAC INET Environment ALL I/NET Software and controller LAN (CLAN) based controllers Cause LAN failure or any failure of the indirect point being updated. Resolution There are various tools available within I/NET to filter "old data" from subsequent control processes.  These include: Filtering by Calculation AVG operator function (including point types AI, DI and DO) Filtering by Direct Digital Control (DDC) Modules using either the Relay or HiLo modules Click Here to download a document which details these methods. For further details and recommendations when using Global and Indirect points, refer to the following I/NET Global and Indirect Points Overview and Recommendations.