Building Automation Knowledge Base

Issue What is a quick way to determine the IP address of a MNB-1000 that is integrated to a Niagara R2 station?  Assume only Workplace Pro is available (Workplace Commissioning Tool is not available). Environment MNB-1000 Niagara R2 UNC-410 and UNC-520 Cause None Resolution The IP address is stored in hexa-decimal format within the properties of the controller's shadow object.  A unit-conversion calculator is required to determine the IP address in decimal format (the Windows calculator can do this task). To find the IP address, Locate the shadow object of the MNB-1000 Go to its Properties, Config tab Record the first 8 digits of the hexa-decimal number displayed at the "address - MAC Address" parameter.  The last four digits are the UDP Port number and are not part of the IP address Convert to decimal Example,     C0 = 192,  A8 = 168, 01 = 1, 96 = 150 BA:C0 = 47808 (UDP Port Number) MNB-1000 IP address is 192.168.1.150

Issue Launching I/NET Access generates errors when trying to establish a connection to I/NET I/O Server. "DBase Server create failed" "I/O Server create failed" Environment TAC OPC Server for I/NET 2.10 I/NET 2.4x Cause I/NET 2.40 or higher removed certain resource files from the default installation that are required for the TAC OPC Server for I/NET to function properly. These files must be manually installed and registered. Resolution To resolve this the I/NET 2000 Backward Compatibility resource files need to be installed and registered: Browse to the Support\INET2000_Backward_Compatibility\ directory on the I/NET installation CD. Copy the DBSrv2k.exe and INetIoSrv2k.exe files to the C:\Program Files\INET Seven\ directory. Open a Windows command prompt. Navigate to the C:\Program Files\INET Seven\ directory Execute the following commands DBSrv2k.exe /regserver InetIoSrv2k.exe /regserver Start I/NET IO Server I/Net Access will not properly communicate the OPC Server and I/NET I/O Server.

Issue What is the wiring for the RS-232 A, RS-232 B, RS-485 A, RS-485 C, and 10Base-T ports on a Xenta Server? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 BACnet/IP BACnet MS/TP M-Bus C-Bus Lon Modbus Cause The wiring and pin outs for the Xenta Server hardware is detailed in chapter 2.1.2 of the TAC Xenta 500/700/911/913 Product Manual . Resolution The ports and wiring is unique for each port. RS-232 A port For serial communication it is typical to only connect the RX, TX, and Ground pins. Pin 3 4 5 Serial Cable RX TX Ground  RS 232 B port   10 Base-T port (Web connection) Note: The Xenta 913 also supports BACnet/IP and Modbus TCP/IP on this port. RS 485 A port (Modbus) Note: The Xenta 913 also supports BACnet MS/TP on this port. If two wire communication is being used then only use pins 5 and 6. Pin 5 6   + - If four wire communication is being used then all four pins will be used. Pin 5 6 7 8   TX + TX - RX + RX - RS485 C port (I/NET) This port is used for I/NET communication. Pin 19 20   + -

Issue ERROR [Current Date] [AsdNetwork_COM3] Unlicensed: /Drivers/AsdNetwork Javax.baja.license.FeatureNotLicensedException: tac_llc:tacasd Environment I/A Series G3 (Niagara) Asd Driver Cause The issue is caused by a missing certificate. Each license installed needs to have a matching certificate. Resolution Obtain TAC_LLC Certificate Install under License Manager Reboot ENC If issue persists verify the license file name is correct, i.e. TAC_LLC.license.   If it doesn't match this name exactly obtain new license file.

Issue When defining a Communication Port - Loytec the Network interface drop down is empty when the device is connected and recognized by LConfig. Product Line TAC Vista Environment Vista 4.4.0 - 4.5.0 Vista 5.x.x LoyTec NIC Cause Vista Server will only display Loytec devices connected to the computer when Vista Server is launched or started. If the NIC was connected to the computer after Vista Server was started it will not be visible until Vista Server is restarted. Resolution To populate the Network interface drop down with the currently connected devices: Shut down Vista Server Restart Vista Server If Vista is running as a service, then LConfig should function as a service also and service dependencies should be utilized to ensure that Vista Server (TACOS.exe) does not start until after LConfig.

Issue Is Webstation compatible with iOS or Android for use on tablets or smartphones? Product Line TAC Vista  Environment TAC Webstation 5.1.7 and earlier versions. Cause Today many technicians use iPad, tablets, or mobile phones in their daily work and would like to access the buildings running Webstation on these devices.  Resolution Unfortunately today it does not work well to run Webstation on iOs or Android. The problem is viewing TGML graphics. They will not load correctly.

Issue Infinet to MP or RP controller communications Product Line EcoStruxure Building Operation Environment Infinet Controller i2 i1 SmartX IP RPC RP-C, MPC, MP-C, MPV, MP-V Controller Cause The power cycle and bandwidth requirements need to be considered when setting the parameters for Infinet to MP/RP communication Resolution First ensure a good understanding of "Infinet Under the hood" article. A direct binding can easily be made between an Infinet controller object like an Analog Value and an MP/RP Controller object like an Analog Value. The whole communication path is not BACnet so a "Value transfer settings" window can be opened that controls part of the EBO communication process. This default configuration (Infinet to MP/RP) will usually result in the Infinet Value being collected every 10 seconds, this value will then only only be written to the MP/RP when the value changes. To ensure the value is correct following a power cycle either enable Guaranteed transfer and set to 1 minute, or use the retailed level on the MP/RP object   If there is a listview, graphic or watch window containing the Infinet Object, this causes the value to be collected every 500mS, as seen in the screenshot below   If the Infinet Object is "exported", (see "Infinet under the hood" for details) then the communication can be much more efficient as the values are only sent when there is a change (greater than the object threshold for analog inputs).   If the communication is from the MP/RP Object to the Infinet controller Object, then a BACnet COV subscription will be set up by the EBO server to the MP/RP Controller, this will be renewed if either is reset/power cycled. It needs to be remembered that the "Value Transfer settings" is an EBO property and in this case the communication is controlled by the EBO Server with Infinet in one direction and BACnet in the other. So the communication to the MP'/RP controllers will either be a write or a COV subscription from the EBO Server.

Issue Making connections in Xbuilder for graphics, connection objects, alarms, Menta programs, or trends can be tedious due to the organization and tree structure of the System pane window. Do logical units in the system pane have to be used when making bindings? Environment Xbuilder 5.0.2 - 5.1.x Cause Both logical and physical objects can be linked (though some unit issues might cause one method to be preferable to another) to graphics, alarms, connection objects, Menta programs, and  trends. With the use of the Filter View the system and network pane can be presented in a single window filtered to only display objects which work together. Use of the Filter View will provide a user friendly connection process that avoids the need for users to scroll up and down the system pane to drag and drop signals. The filter view toolbar also provides the ability to fix the view and connect objects without having to drag and drop them into the system pane. The Filter View is only available in Xbuilder version 5.0.2 or higher. Resolution Highlight the object you want to make a connection with in the System Pane. Select the Filter View tab in the middle pane. Select the signal from the combined list of System and Network panes. Use the Connect button on the Filter View toolbar to finish the connection.

Issue An error was detected while attempting to set an attribute in a remote Infinity object Infinity Controller error: No response from I/O module Environment 99xx 9680 Continuum Cause FTT-10 IOU modules are not compatible with RS-485 Netcontrollers RS-485 IOU modules are not compatible with FTT-10 Netcontrollers Resolution There are a few ways to determine what bus topology type was built into a IOU module or Netcontroller  Take a look at the original purchase order which will indicate the type Look at the inside cover of the IOU module(s) and in the model description RS-485 or FTT-10 may be indicated Inside the cover of the Netcontroller and the IOU module there is a black component on the circuit board that has Echelon FTT-10 on it near the comm bus connector if it is FTT-10 Get the serial number of each of the IOU modules and the Netcontrollers and let Product Support know what they are, PSS can cross reference the number to determine the topology scheme from when it was manufactured If this isn't the issue then try the IOU with only that IOU connect in a different part of the IOU bus or by itself on the Netcontroller Under the cover RS-485 version - CX9900 Netcontroller 1   Under the cover FTT10 version - CX9900 Netcontroller 1

Issue How to connect 2-10 Vdc position output signal of an actuator to an analog input of LON or BACnet controllers. Controller’s Analog Inputs are limited to 0-5 Vdc input. Environment WorkPlace Tech I/A Series Lon (MNL) controllers I/A Series BACnet (MNB) controllers Cause Controller’s Analog Inputs are limited to 0-5 Vdc input. Resolution See the WorkPlace Tech Tool Engineering Guide (F-27254-3) Analog Input object discussion (page 129) for reference. Setting up a 2 to 10 VDC feedback voltage divider, use a 120 K (120,000) Ohm in series with a 100 K (100,000) Ohm resistor; connect the UI across the 100K Ohm resistor. As long as the signal never exceed 10 VDC, the voltage across the 100 K Ohm will never exceed 5.0 VDC. Based on the above test results, 10Vdc [actuator output] = 4.545 Vdc [after voltage divider] 2 Vdc [actuator output] = .909 Vdc [after voltage divider] Set-up the Analog Input Object Linput= 0.909 Vdc LScale= 0 Hinput= 4.545 Vdc HScale= 100 Your values maybe different based on the resistor accuracy.

Issue The TAC I/A Series G3 ASD Driver Installation and Configuration Guide, F-27522, does not describe the Send Group object. Environment I/A Series G3 (Niagara) station containing the ASD driver I/A Series Network 8000 ASD controllers ; MicroZone II, MicroFlo II, LIM, or PEM1 PSI / XPSI to edit database in the ASD controller. Cause Setup not documented. Resolution Basic setup procedure: Verify the configuration of the ASD controller, using PSI: ASD device, Edit, device, Setup, Group # RGRP:n block, where n matches the Group Number in step 1 Edit the G3 station using the Workbench, as follows: In the ENC station, AsdNetwork, Groups (AsdGroup Device); verify Enabled = True verify status = OK  SendGroup object under the Groups. Verify Device Type matches the controller type ( Mz2, Mf2, Lim, or Pem) Verify Group Number is the same as in Steps #1 & #2 above. Set Mbx Input = true;  by either setting Mbx Input Default = true, or by connecting a Boolean Writeable to the Mbx Input

Issue Polling data from one Xenta Server to another can be accomplished over IP by importing XBuilder Projects. This will only bring over data points that reside in the Network Pane of the XBuilder Project.  If points are being calculated in a Menta object, for example, they would not be available following an import. Product Line TAC Vista Environment XBuilder Xenta Server 701, 711, 721, 731 Fixing Write Over IP Cause Importing another projects network brings over only data points that reside in the Network Pane of the XBuilder Project. In order to avoid a write over IP situation, data from the System pane sometimes needs to be browsed into the other controller's project. Resolution Expand the Network pane beneath the Xenta 700 and find the Variables folder. Right click on the Variables folder and select New Variable (if desired, choose New Folder to organize the points that need to be sent over IP). Create a variable for each point that needs to be imported into the receiving Xenta Server. Drag and drop Variables onto the Menta object outputs to associate them   Note: Only Menta object Outputs allow for this drag-and-drop functionality.  If they are public signals, then either: Add an RO, IO, BO point on the output of the signal Use a connection object in XBuilder to transfer the value to the Network Pane variable. In the receiving controller's XBuilder project, right-click on the IP Backbone and select New > Other Projects Network.  Now the Menta object variables are available.

Issue How to monitor if an HOA switch in an I/O module for a Xenta Server is set to something other than auto. How to tell if an I/O signal is hardware (HW) overridden/forced Environment Xenta Server (731, 721, 711, 701) Cause Some I/O modules have switches that can be used to manually force/override the outputs. It could be important to know what signals are forced. Resolution In XBuilder, each physical I/O that has a manual switch also has a signal for it.     This can be used to monitor the switch.

Issue After configuring a BACnet Schedule in a BCX or a b3 controller, it goes into Fault with its Reliability field showing "ConfigurationError". Environment CyberStation WebClient BCX40xx b3 BACnet Schedule Object Cause Configuration of BACnet schedule Incorrect point type used to configure BACnet schedule Resolution For each object type within BACnet (input, numeric, trendlog, etc.) each object property identifier (property) has an associated data type.  A list of data types for the each property can be found in Chapter 12 of the BACnet spec under the section for each object type.  The correct data type to configure in the schedule is determined by the Object property that is being controlled by the schedule object.  When using a schedule to control the value of a BinaryInput, BinaryOutput and BinaryValue objects, the Data Type that should be used is Enumerated. When using a schedule to control the value of a AnalogInput, AnalogOutput and AnalogValue objects, the Data Type that should be used is Real. When using a schedule to control the value of a MultiStateInput, MultiStateOutput and MultiStateValue objects, the Data Type that should be used is Unsigned Integer The Schedule object can be tricky to configure, however. There are several properties (Weekly_Schedule, Exception_Schedule, Schedule_Default) that must contain the same data type for all events. Since Enumerated is the “default” data type, the user may need to manually remove any existing events with the Enumerated type and replace them with the desired data type. If while configuring the schedule a message similar to the one above is displayed and accepted  all the events MUST be deleted otherwise a configuration error will result.

Issue Loytec (LTA, lon port) offline in TAC Vista when running TACOS as a service Environment TAC Vista running as Service Loytec NIC device Lconfig/NIC legacy driver Cause For TAC Vista to use the legacy driver, it must be running before Vista starts. When running TACOS as a service, by default, it will start prior to the legacy driver and the LTA port will show offline. For this reason, the legacy driver must also run as a service.  Dependencies on the Vista Server service must also be configured to ensure that the legacy drivers starts first. Resolution First make sure that the legacy driver is set up to run as a service Open Lconfig and click on advanced. Select "run as service" and click ok.   Reboot computer From the  start menu, select run, and type regedit Go to  HKEY_LOCAL_MACHIN\SYSTEM\ControlSet001\Services\TACOS\ Double click on depend on service Type in LoytecSrv on a new line.   Reboot computer.

Issue Replacing the original Satchwell 24 volt actuator, (ALX, XRM or similar) with the current Schneider Electric version. Environment Actuator is connected to a CXT 4604 controller. Cause The CXT 4604 controller internal transformer has a limited VA rating, this is insufficient to supply some new 24 volt actuators. Resolution To overcome this situation an external transformer with a suitable VA rating must be added to the system, please see drawing below.  This drawing shows the controller being connected to a M800, but this configuration will apply generally if other SE actuators such as, M700 or MV15B-24 are used.

Issue Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC. Product Line TAC IA Series Environment Niagara R2 UNC-520 Niagara G3 ENC-520 Cause Pinout diagram for wiring Resolution This image details two pinout configurations:  Null Modem and Straight-through.  The Null Modem version is available for purchase using part number UNCC-405.  The Straight-through version is not available for purchase. This image is also part of the UNC-520 Installation Instructions (F-27391)

Issue TAC Vista Web Settings > Preferences > Login and Logout > Automatic Logout (An inactive user is automatically logged out after a specified period of time) Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Set the logout time to less than 5 minutes Set the logout time to more than 30 minutes. Customize the logout time to something other than specified intervals.  Environment Vista 5.1.5 Webstation TAC Vista Web Settings Cause Selection for automatic logout time is restricted to 5, 10, 15, 20, or 30 minutes. Resolution Navigate to C:\Inetpub\wwwroot\TACVistaWeb515 Open the file web.config. Use, for example, Notepad2 (Do not use wordpad as it formats the file differently) Search for "sessionState" Change the "Timeout" for the SessionState to the desired logout time in minutes Save the file 

Issue Get warning (error) "The Min and Max values for the "in" signal are out of bounds in regard to this "to" signal" when generating Xbuilder project Environment TAC Xbuilder Cause This warning refers to min and max values of signals in a connection object not matching. Resolution This is just a warning that there is a possibility that the receiver can't handle some of the values that can be sent. No action is required.

Issue Menta Crashes in Simulation Mode. Environment Menta Vista Cause Improper use of Menta objects can cause Menta to crash in Simulation mode. It is possible to cut a HFDI from inside a HFB and paste it onto the root level of the Menta drawing. Resolution If a Menta Object is used in a manner that is not normal, such as a HFDI (Hierarchical Function block Digital Input) used outside of a HFB (Hierarchical Function Block), Menta may crash when entering Simulation Mode (hotkey=F12). The best way to troubleshoot this type of issue is to systematically delete portions of the Menta file then try to enter simulation mode. If you successfully can enter simulation mode, the deleted piece was causing the crash. You can typically narrow the cause down to the object causing the issue.