Building Automation Knowledge Base

Issue Various problems with converted TGML graphics Bindings of the I/NET objects within Building Operations have wrong and / or illegal point address. Environment I/NET integration with SmartStruxure Cause Improper preparation before converting graphics may cause nuisance issues. Resolution Ensure the following is done when converting a sites I/NET graphics to TGML Before converting the graphics to TGML Ensure all save files are current Ensure the I/NET network configuration is current Before importing the graphics to StruxureWare Ensure that all affected controllers are imported.  Do not change any names or descriptions before importing graphics Upload any controller which indicates it is required. This will ensure that point names for graphic bindings are correct. In the INET Interface path box, enter the path to where the INET interface is located in WorkStation. This setting affects the bindings that get defined for objects in the resulting TGML file(s). If you accepted the default name when you created the I/NET interface in WorkStation, this path is typically /Server 1/INET Interface/.  Make sure this matches the installed system details.   Click Here to get more detail from the Online Web Help. Check out the I/Net Transition: Graphics Conversion video on the Community website.

Issue Even though the correct settings are defined in Device Administrator, the Automation Server will appear red indicating that it is not possible to connect to it. Product Line EcoStruxure Building Operation Environment AS Device Administrator Cause Some special characters are not supported in some positions before version 1.6.0. For example, the password admi$n would work in Workstation, but not in Device Administrator. The password admin$ would however work. Furthermore, after 3 login attempts the account will be blocked. Resolution Change the admin password to something simple like "admin" or "password" Reboot the AS, or wait 30 minutes Connect with Device Administrator

Issue How many messages are buffered on a Door Controller 7910A and 7920 DPU? Product Line TAC INET Environment I/NET Seven Door Controllers: DPU 7910A, DPU 7920, and SCU 1284 Cause Even though every device in the system contains a message queue, only a few of the devices will successfully buffer the queued messages for later distribution. All controllers and Taps distribute messages out of their RS485 port even with the absence of any LAN communication. This is due to the fact that there is no requirement for an acknowledgment to be received at the generating device. The RS485 LAN is for both solicited and unsolicited message traffic. The only devices that perform extended buffering are the ones that directly communicate to polling devices such as the 7801 Taps, 7803 Taps, 7804 Taps, and all DPUs/SCUs. The MRs, ASCs, and UCs do not generate messages; messages relating to these devices are generated by the relevant MRI, MCI, etc. Resolution Refer to the Database Caching in the Door Controller Chapter 9-11 in TCON 300-05/17 for full details. For the 7910A and 7920 see the following details:  Controller software before v.2.20 = 100 messages Controller software for 2.20 and later = based on the number of resident individuals (see table below).

Issue Get "service not implemented" message when downloading Menta application from Vista. Environment TAC Vista 5.1.X Menta application downloaded via Vista Cause A programming error in the Menta application has occurred. Resolution Check the Menta application - start with the last added block and check for calculation errors etc, e.g. Division by 0 in a calculation.

Issue Multiple issues caused by changing the link after discovering devices. Duplicate entries of MCU devices under a sub LAN interface Deleting duplicate MCUs causes MCU devices to be removed from I/NET Environment Automation Server integrated to I/NET Cause Changing the link address of the I/NET Interface should not be done after devices are discovered. If you must change the link address, do so before you have added devices to the I/NET interface. Resolution Option 1 -  Remove all controllers from the I/NET interface. Change the link to the correct setting Re-discover the devices Option 2 - Determine whether the AS or the I/NET controller has the correct information. (This will require I/NET software) If the AS is more correct, perform a download to the controller if the I/NET controller is more correct, perform an upload to the AS

Issue A computer was installed with version 3.5.34 of Tridium's Vykon-branded Niagara AX and Schneider-Electric's TAC-branded Niagara G3.  An error appeared indicating that the core distribution files were missing. Environment Niagara G3 Workbench Cause The sw directory was missing under the 3.5.34 directory. Resolution Un-install both versions and re-install just one of them. The Vykon-branded and TAC-branded licenses files can be kept in a separate directory and swapped in-and-out as required.

Issue LON bindings stop updating in a Niagara R2 UNC station. The following message also appears in the standard output window: MESSAGE: Unmatched LonWorks response received! [LonCommReceive.run] The LON bindings are re-bound but the problem re-occurs. Product Line TAC IA Series Environment  Niagara R2 UNC Cause This message indicates that a LON controller is sending a message to the UNC's subnet/node address that the UNC cannot match to its LON database. This happens when a controller has not had its binding table updated. Resolution Make sure the UNC is the only LON network management tool used on the associated controllers. Compare the UNC's LON database information to the data actually held in the associated controllers. Right click on the LonWorks Service and select Lon Utilities Manager. Leave the "device" to 'localLonDevice' and set the "Command" to 'reports' and the "SubCommand" to 'verify.' The resulting output will show any mismatches in the various tables. To correct, re-commission the localLonDevice, re-commission all other devices (which clears their tables), and then re-bind all listed bindings. Re-run a 'reports' > 'verify' to ensure all devices are up and running on the network.

Issue What is the Actual SCU Power Requirement and Battery Life expectancy Environment I/NET site with Access Control Cause SCU Power Requirement information SCU Battery Life information Resolution The current power ratings listed in TCON312 & TCON313 are the indicate maximum power consumption for Agency markings and recommended transformer sizing. All of the SCU models all have the same supply circuits. All three models can deliver up to approx 1.2 amps of 13.6V, and .2A of 5V, along with the onboard 3.3V logic load. The SCU1200 and SCU1280 provide two terminal blocks (TB4 & TB5) which can deliver 13.6V and 5V power out to miscellaneous sensor/detector loads. The SCU1200 and SCU1280 also support an external a lead acid battery backup. When this battery is discharged, application of AC power can call for maximum power from the 13.6V supply with the onboard supply limiting 13.6V to the battery and external load to currents up to approx 1.2 amps. Even if you are not using the external power for sensor/detector power, the battery can pull maximum power during recharge. If you are NOT using an external battery backup, and you are NOT using the external 13.6v connection (on TB4 & TB5), and you are NOT using the external 5V connection (on TB4 & TB5), then you could assume a reduced 24VAC power consumption as follows. For the SCU1200, the 24VAC power input would be approximately .1A (2.4VA). For the SCU1280, the 24VAC power input would vary from about .1A with no relays on, up to approx .3A (7.2VA) with all 8 relay outputs energized. SCU Battery information: SCU1284 NiMh Battery Life The Varta battery datasheet lists the life expectancy for trickle charge applications (which is what the SCU uses) as 6 years (at temp of 20C) and 3 years (at temp of 45C) So in typical access control environment we should be around 25C so around the 6 year expectation would be appropriate. Also, the end of life is frequently interpreted as reaching ½ capacity on a NiMh battery, so it still has memory retention, even at end of life. 

Issue Configuring LON tunneling in Niagara G3 Product Line TAC IA Series Environment Niagara G3 Cause See below to watch a video document (vdoc) explaining the process to configure Lon tunneling in Niagara G3. Resolution The purpose of this video is to show you how to configure Lon Tunneling in G3. It's already assumed that there is a LON network that has been installed, commissioned, and discovered in the G3 ENC.  

Issue When using the RJ10 OP port for Lonworks communication the TAC Xenta 200, 300, or 401 controllers fails completely.  Product Line TAC Vista Environment Xenta 281 Xenta 301 Xenta 401 Xenta OP Vista server Cause When theRJ10 OP port on a TAC Xenta 200,300 or 401 controller is used to access the Lonworks network the controller can be easily damaged if the 24VAC power is shorted or grounded accidently.  The OP port on these controllers have four pins. Two of them are the Lonworks network and the other two are 24VAC to power the OP panel, If the two 24VAC wires (most left pins on the TAC Xenta 280, 300 and 401) are shorted the embedded fuse in the controller may be blown and the controller will not be able to be used. Resolution In most cases the controllers internal fuse has blown and will require replacement. The repair of this will be dependent on location and type of controller.  Please contact the repairs department if repair is possible.   Recommendation: If this type of connection is to used, then ensure that the two 24VAC wires are very well separated from each other.

Issue Blank screens seen when starting WorkStation, Device Administrator, License Administrator and Software Administrator Product Line EcoStruxure Building Operation Environment Windows 10 Cause Graphics Card Driver Issue In this case there was a "Intel(R) HD Graphics 4600" graphics card (this is the Intel Core i7-4790 CPU built-in graphics card) and there was a dedicated "NVIDIA GeForce GT 630" graphics card which was in the end also the culprit because it was the one with the outdated graphics driver, the Intel one didn't required an update. Resolution Update Display Drivers Fix for Windows 10 Professional Version 1803 below Start Computer Management Go to Display adaptors and update driver  Search online for drivers  Verify with second run after driver update if newest driver is installed 

Issue The controller installation guides detail how to display the values in Water Column (WC), but how can this be displayed in metric units? Product Line Andover Continuum Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885, i2885-V, i2850 &i2853 ) BACnet controllers (b3865 & b3865-V, b3866 & b3866-V , b3885, b3885-V, b3850 & b3853) Cause A conversion to metric units (Pascals) is needed. Resolution i28xx type of Infinet Controller has 0-2" WC (Water Column) range which corresponds to 0-2V so the input value can be read directly in WC. The 850 has a single airflow sensor on channel 8 The 853 has two airflow sensors on inputs 7 and 8 For 865, 866, and 885 the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 500 The i28xx-V type of Infinet Controller has 0-1" WC (Water Column) range. For 865-V, 866-V and 885-V, the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 250  For controlling the Damper motor output Create an Infinity Output point of type Triac on Channel 1 It can then be opened/closed like any other Triac output with the use of On, -On or Off commands. Also see Setting up the override value to show the damper feedback on an i2/B3 866-V for details on reading the damper feedback on the i2/b3886-V.

Issue DHCP for MPMs Environment StruxureWare Lite site with MPM Cause Can DHCP be used for network settings or does the IP address need to be static Resolution The MPM's do not support DHCP, only static IP addressing. It is planned to have DHCP on the new MPM platform that is in development. There are no dates or firm roadmaps available, but DHCP is one of the desired features of that new product line. The DHCP support is planned in the future generation of controllers which means a completely new hardware platform. This would not be a firmware upgrade on the current generation of products. To get to the IP address settings,  Then input the static IP address for the MPM

Issue What do the HVAC, SEC, and INT options on the Continuum Security Key provide access to? Product Line Andover Continuum Environment Continuum Security Key Continuum Cyberstation Cause Unsure as to what restrictions these various Security Key Options place on the activity that can be performed and what can be viewed within Continuum. Resolution HVAC - Provides access to HVAC specific objects such as viewing BACnet controllers, creating BACnet objects and polling for new BACnet Devices. SEC - Provides access to viewing and creating Security specific objects such as Door, Area, and Personnel objects. INT - Provides access to all of the above. This key will be able to view/create both HVAC and Security related objects. Any Workstation with a SEC key will not be able to view any BACnet Devices or objects in the database and any with an HVAC key will not be able to view Security related objects in the database. For more information see Different options on the CyberStation security key.

Issue Can Workplace Tech (version 5.7 or later) be installed so that a user with only normal user rights can use the program? Product Line TAC IA Series Environment MicroSoft Windows XP MicroSoft Windows 7 Visio 2003, 2007 WorkPlace Tech Tool software version 5.7.x or newer Cause Some sites do not allow users to have unlimited administrative rights on their computers due to security concerns.  These restricted users need to be able to use the WorkPlace Tech Tool software. Resolution NOTE: This was tested in Windows OS and Visio versions defined in the "Environment" only.  The later versions of Visio and, consequently, Workplace Tech use a ribbon COM Add-In for navigation that does not work correctly using the methods described here.   All versions of WorkPlace Tech must be installed by a user with Administrative rights on the local computer.  This would include the following users: Local computer administrator Windows Domain user with administrative rights Windows Domain user with user domain rights that have been given "Local Administrative" rights After the administrator has installed a revision 5.7 (or newer) version of WorkPlace Tech, ANY user on the computer will be able to run the software.

Issue Alarms cannot be created in a BACnet b3 controller because the fields are grayed out. Product Line Andover Continuum Environment Continuum Cyberstation b3 BACnet MS/TP controllers Cause Alarms are created differently in a BACnet controller than with an Infinet controller.  These fields are grayed out since they are not used for alarm creation in a BACnet controller. Resolution There are instructions in the BACnet section in the Continuum help for creating an event notification and then mapping the point and the event notification within an alarm enrolment. For an example see AlarmCreatingAndConfiguring BACnet.doc

Issue The Xenta 913 can only be used for both Modbus and BACnet at the same time if they are being used on separate ports or are both on the IP port. BACnet and Modbus can not both be used on the RS-485 A port at the same time. Environment Xenta 913 XBuilder BACnet Modbus   Cause Only the Ethernet 10 Base-T port on a Xenta 913 may have more than one interface at a time. Resolution The Xenta 913 may interface with BACnet and Modbus at the same time only if: The RS-485 A port is being used for Modbus and the Ethernet 10 Base-T port is being used for BACnet The RS-485 A port is being used for BACnet and the Ethernet 10 Base-T port is being used for  Modbus The Ethernet 10 Base-T port is being used for both BACnet and Modbus and the RS-485 A port is either unused or is being used for only BACnet or Modbus but not both The Xenta 913 may not interface with both BACnet and Modbus if they are both connected to the RS-485 A port.

Issue Why is "B" shown in the Concurrent license feature list in the License Server Interface (http://localhost:8888) Dashboard?   Product Line EcoStruxure Building Operation Environment Building Operation License Server Cause The Flexera framework requires at least 1 licensed feature to be present when installing a license server for it to start correctly. In this phase there aren't any licensed features so a dummy feature is created. Resolution It can be ignored as it is just a dummy license used for the installation.

Issue Values sent from a Xenta 121 FC/HP controller via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the Xenta 121 shows a value, but the inbound SNVT on the receiving controller is invalid or a default value. Product Line TAC Vista Environment  Vista NL220 LonMaker ZBuilder Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All Xenta 121 controllers come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution In order to adjust the send or receive heartbeat of a Xenta 121 controller, follow these steps: Right click on the controller and go to PlugIns > TAC ZBuilder Plug-In. In ZBuilder, click on the Configuration tab and go to LON > Node. Here the Send heartbeat and Receive heartbeat can be changed. The following nvo values will require the Send heartbeat be set to a value greater than zero in order to communicate with another controller using a SNVT binding. nvoSpaceTemp nvoUnitStatus nvoHeatPrimary nvoHeatSecondary nvoCoolPrimary nvoEffectOccup nvoTerminalLoad nvoEffectSetpt nvoFanSpeed nvoEnergyHoldOff nvoOccSensor nvoRawDOStatus   The following nvi values will default to invalid if they do not receive an update within a specified period of time. For most applications this should be left at zero. If the application must actively poll a SNVT then the receive heartbeat can be set to a value greater than zero. nviApplicMode nviSetPtOffset nviEnergyHoldOff nviFanProof nviOccSensor nviSpaceRH nviOutdoorRH nviSpaceIAQ nviOutdoorTemp nviSourceTemp nviAuxHeatEnable nviSourceFlow nviComprEnable

Issue Unable to connect Continuum I/O's to Access Expert Product Line Access Expert Environment Win 8.1 and above on Version 3 Cause The Continuum Integration has only been configured to bring in the AC-1 and AC-1 Plus door controllers as sub-devices. Resolution There is no resolution, but the Continuum I/O's are simply not compatible with Access Expert. Use Mercury 16 In/Out boards for applications that require these types of devices.