Building Automation Knowledge Base

Issue Webclient currently unavailable Error 80070005 Check your DCOM permissions when launching webclient or webclient is currently unavailable. Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A remote reboot will not write DCOM permissions the same way a local reboot does. Other Server configurations can cause this. Resolution A webClient installation was performed using Windows Remote Desktop or some other remote access software and the reboot after the webclient install was executed using the remote software. To fix this, reboot the Webclient server directly from the server itself. There are security permissions that do not get written properly when rebooting remotely and a direct reboot corrects this problem. Start Continuum on the Webclient PC locally, not remotely. Be sure Continuum has been started on the webclient PC. Also see, Webclient unavailable error when attempting to logon which mentions making sure the Network Service is selected for the default app pool. 64-bit OS will cause this error as well. Webclient versions pre 1.94 are not supported on any 64 bit platform. If that doesn't work then a complete reinstall and reboot on the server will be required. Remote installs are typically problematic. If changes were made to .net try the following steps: Start> Run> cmd (Enter)  To get to a DOS prompt cd\Windows\microsoft.net\framework\v2.0.50727 (change directory to this folder) run the command aspnet_regiis.exe -i (It will say installing .net, this re-registers .net with IIS) Restart Windows on the webclient PC and restart Continuum

Issue Too much LON communications traffic can cause LON communications errors. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series MNL 800 Building Operation Automation Server Premium LON Network  I/A Series R2, AX, N4 Jace LON Network Cause Sending output LON SNVT values too frequently or more often than reasonably needed. Resolution There are a series of NCI (configuration) objects that control the transmission and reception of these data values on the LON network. One of four NCI objects (nciSndHeartBeatA, B, C, or D) is assigned to each NVO object in the application program. This value regulates the periodic LON transmission queuing of the NVO object values for each binding. One of four NCI  objects (nciRcvHeartBeatA, B, C, or D) is assigned to each NVI object in the application program. This value regulates the fallback timeout for each NVI object value. If a value is not received via the binding in this time period, the NVI object value will revert to its application-defined default value. In an MNL-800 controller, there are two additional NCI objects that are used to regulate the flow of data onto the LON network. The nciMinOutTime object is used to throttle the transmission of all data values queued to be sent via bindings over the LON network. This NCI object sets the transmission time interval between each NVO value being sent on the network. The important fact here is that the product of the number of bound NVO values times this interval (nciMinOutTime) must be LESS than the shortest nciSndHeartBeatX (X=A, B, C or D) interval. For example, if the Send HeartBeat is set to the default of 120 seconds and there are 60 NVO SNVTs bound from this controller, the nciMinOutTime must be set to a value of fewer than 2 seconds.  The recommendation for setting this SNVT value one half the shortest nciSntHrtBr divided by the number of NVO SNVTs bound from the controller.   The nciMinPropTm object is used to regulate the transmission queuing of changing bound NVO object values. This timer acts as a time-based filter to prevent a rapidly changing NVO value, such as a constantly changing temperature, from overwhelming the communication capacity of the LON network. Typically this value is set to a value of 1 to 5 seconds. Additional information can be found in Chapter 6 of the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). BACKGROUND: This section is provided to give the reader a basic understanding of bound LON communications, as applied to LON controllers in general. Data communications across a LON network is accomplished by using a LON Network management tool to create a binding between a device with a data source (NVO object) and one or more devices with data receivers (NVI objects) in other LON controllers. The device containing the data source will send the bound data value at a periodic rate, as defined by the associated SendHeartBeat NCI object, and whenever the value of that object changes. If the NVI object does not receive a value from the sender (bound NVO object) within a specified time period, as defined by the associated ReceiveHeartBeat NCI object, the NVI object will use a local fallback value until such time as it receives a new value via the binding.

Issue Reassigning a USB Serial Adaptor to a desired COM port Reassigning a USB to DB-9 Adaptor to a desired COM Port Product Line TAC Vista Environment Windows OS Cause It is common for newer laptops to come without DB-9 serial connections. USB to DB-9 adaptors have to be used instead. When this USB device is installed, Windows will allocate the first COM port available in the system. In most cases, this will not be COM1, which is the default port designation for both Menta and the Download Wizard. If COM10 or greater is assigned, then it cannot be used with Menta for a direct download because Menta's COM port designation drop-down list only goes to COM9. Resolution Reassign the USB to DB-9 adaptor to the desired COM port: Right-click on My Computer and select "Manage" In the left pane of the Computer Management Console, select Device Manager. This will populate the right pane with system information. Expand "Ports (COM & LPT)." There will be a list of ports in use and which device is associated to the COM port. Look for the USB to Serial Bridge (COMx). If the USB to DB-9 adaptor is not assigned to the desired COM port, right-click on it and select "Properties." From the Port Settings tab, select "Advanced." In the Advanced Settings is a drop-down menu for assigning the COM port number to this device. Select the desired COM port. If it is noted that the COM port is "(in use)," find the device using that port Reassign that device to another open port. This will free up the desired COM port for the USB to DB-9 adaptor. Changing COM port may take some time for Windows to process and put into effect. Monitor "Ports (COM & LPT)" in the Computer Management Console. This will show the reassigned COM port when the operation has finished. *it is also possible to assign to a port in use which should move the previous device to another com, however this should be used as a last resort.

Issue What kind of controller can be used to get values from a Modbus device into TAC Vista? For example, getting data from a Modbus meter into a BMS system running Vista. Product Line TAC Vista Environment TAC Vista TAC Xbuilder TAC Xenta server 731/913 Cause TAC Vista can not talk Modbus directly so you need to use a gateway controller. Resolution Xenta firmware version 5.1.4 and earlier only two controllers had Modbus communication capabilities: Xenta Server 731  For details see TAC Xenta 711/731 Web Server and Controller Xenta Server 913 For details see TAC Xenta 913 LonWorks Gateway Starting with Xenta firmware version 5.1.5, all Xenta Servers are now capable of communicating on a Modbus network both via TCP/IP and RS-485.  This includes Xenta 511, 527, 701, 711, 721, 731, 913. Note: Older Xenta Server devices built before firmware 5.1.5 have the capability of using Modbus over RS-485 once they have been upgraded even though the terminals are not labeled on the device. For information on how to wire these devices to reference a newer Xenta Server that does have the RS-485 A terminals labeled or see Xenta Server wiring and pinouts.

Issue During installation of the Keeps software an exception is thrown in ExtentPlaceholderCreator. Environment Keeps On Premise Cause Microsoft SQL Server issue. Problem has been seen with MS SQL SERVER EXPRESS 2012 SP3 Resolution Edit the 'c:\Websites\Feenics\'web.config' file and insert the text below at the exact location shown in the screen shot below. --INSERT THIS TEXT <dependentAssembly> <assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" /> <bindingRedirect oldVersion="1.0.0.0-11.0.0.0" newVersion="10.0.0.0" /> </dependentAssembly> --END OF INSERT TEXT                                                    

Issue Cannot bring Reader Expander online. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controller Security Expert Door Expansion Cause Module addressing has not been configured or is incorrect. Resolution Check the following:   1. Controller (SP_C) Module addressing is correct. When creating the controller for the first time you will need to register it as a Reader Expander to be able to use it's reader ports. Go to the Configuration tab  of the controller and set "Register as Reader Expander" to 1 and the Lock Outputs to the default "Controller PGM 3/4 outputs" setting.     2. Reader Expander Module address. A new module from the factory will default to an id of 254, this will need to be changed. If you only have the controller and one expander module then the SP-C will be id=1 so make the second expander id=2.     3. Health status. Check the Health status of your controller to see if anything shows up there.     4. Update. Update your modules to download changes, review the health status again.

Issue Where Sigma utilizes the site Ethernet network, and that the network consists of multiple subnets, or is using Sigma DNN's with ARCnet or ethernet secondary LANs. Global object values are not received at the receiving controller when it is on a different subnet to the sending controller. Product Line Sigma Environment Ethernet networks containing subnets. Cause Global Values not being passed from controller to controller on different subnets. General advice on the configuration of Link Addressing. Resolution PIB 05 105 Link Addressing explains how to configure Link Addressing on a Sigma system utilizing a customers Ethernet network,

Issue Failing communications when Xenta 555/731, VisiSat, StruxureWare Building Operations automation server/enterprise server connected to MicroNet ARCnet system through an MNMi. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN StruxureWare Building Operations automation server/enterprise server communicating to a MicroNet ARCnet LAN Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position. Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Switch 1 only must be ON for direct connection to Xenta 555. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers under an existing LNC-100, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the LNC. Product Line TAC IA Series Environment I/A Series R2 (Niagara) WorkPlace Pro I/A Series Network 8000 LNC-100 Cause When a third-party network management tool is used to define and commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Click here to see this procedure including screen captures. If the LNC-100 is already communicating to existing controllers on the LON trunk, document the Domain0, Subnet0, and Node0 addressing in either the SYS:SIM or SYS:SIM2 blocks. You don't need to change the existing address in order to add new LON controllers. If you will be using Niagara to commission the new LON controllers, set up the LonWorks Service so that the Local LON device is on the same Domain and Subnet as the LNC-100. Set the Domain length and Domain ID; go to the Properties of the LonWorksService, Netmgmt tab, Engineering tab, domainId, length, domainId. For example, if the SYS:SIM block in the LNC-100 has "DOMAIN0=0D, SUBNET0=01,NODE0=120,..." then in the UNC, it should be domain length = 1 (byte), and domainId = 0D. Apply the changes. Set the Niagara subnetNodeId properties: subnetId = 01, nodeId = 127. The subnet matches SUBNET0 in the SYS:SIM block. Leave the Node ID set to 127 Apply the changes Recommission the Local Lon Device. (Remember to disconnect the LNC-100 from the trunk before commissioning!) With the new controllers connected to the LON trunk, go to the Lonworks service, Lon Device Manager, and run the “find” command; the new controllers should be added to the list of nodes. You can use the Lonworks Utilities, command = identify, SubCommand = service pin to be sure you have the correct node. Then commission the new nodes. Note: Should the LNC-100 be accidentally commissioned, refer to Network 8000 LNC-100 cannot communicate to LON devices under it but can be accessed with WorkPlace Tech or a LON commissioning tool.

Issue Netcontroller power supply is not working as expected. Environment NC1 NC2 CX9900 CX9680 PS120 UPS Cause Problems with Netcontroller power supply. Resolution UPS not working Replace failed 5 Amp pico fuse (located on PC board adjacent to the UPS cable connector) UPS cable or connector has failed or is defective. Insufficient UPS battery capacity is attached to the UPS connector.  UPS requires two 12 VDC batteries). UPS Batteries are not sufficiently charged or have failed. No Power to NetController 3 Amp Slow-Blow fuse has failed.  (located on PC board adjacent to 120 volt power connector). Power switch is shut off. Insufficient supply voltage. General Mode switch is in the wrong position (See manual) Click here to download the PS manual

Issue AVUE 5304, AVUE 5354, AVUE 5305 or AVUE 5355 Light Duty Actuator does not respond to changes in control signal. Environment AVUE 5304 or AVUE 5354 Light Duty Actuator installed on VZX or MZX Valve Body.. AVUE 5305 or AVUE 5355 Light Duty Actuator installed on Satchwell VEU, MEU or FEU Unit Valve Body.. Cause AVUE 5304, AVUE 5354, AVUE 5305 or AVUE 5355 Light Duty Actuator may not respond to changes in control signal due to self stroking / auto stroking procedure failing to occur when originally installed, or due to manual override having been undertaken without subsequent reset procedure having been applied. Resolution 1.  Check that 0v of 0-10v dc control signal and 0v of 24v ac power supply originate from same source. 2.  Undertake Manual Override Reset. The Manual Override Reset Button is located on the underside of the AVUE Actuator. The purpose of the Manual Override Reset Button is to cause the Actuator to self reference. A reset is required only in the following circumstances. A.  If the Manual Override Access screw on the top of the Actuator has been operated when the Actuator is powered up. B.  If it is necessary to re-align the Actuator to a point of self reference during periods of system maintenance. N.B. The AVUE is designed to reset automatically on restoration of power following a power failure.  It should be noted that it will take approximately 85 seconds (AVUE 5305 and AVUE 5355) or 110 seconds (AVUE 5304 and AVUE 5354) for the self reference procedure to be completed. 

Issue Error message when starting SigmaX, says "Failed to Create Object", once accepted SigmaX works correctly. Product Line Satchwell Sigma Environment Sigma SigmaX Tools Utilities Cause Sigma Graphics has not correctly registered in the system registry. Resolution This issue is rectified as detailed below. 1 - Close SigmaX if running. 2 - Start the Sigma server and client. 3 - Open the Sigma graphics editor, and either open an existing graphic, or start a new one. 4 - Modify the graphic and then save the changes. 5 - Shutdown the Sigma client and server, Start SigmaX and confirm its operation.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121, which does not have a D1 input. Product Line TAC Vista Environment Xenta 121 STR-150 Cause The correct terminal for the mode input from the STR-121 is labeled differently on the Xenta 121 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 121 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 6   The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 121. When the Xenta 121 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained inIs it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue Dumping or reloading a NetController using HyperTerminal. Environment Windows HyperTerminal CX9900 CX9400 CX9200 Command Terminal Configuration Guide Infinity and Continuum Window Interface Cause Not known cause. Resolution Click here for instructions on using HyperTerminal to dump or reload controller.  For full details on using the Window interface as used on Infinity and 1st Generation Continuum controllers, you can download the Command Terminal Reference Guide.

Issue What are the new features that are available in the 3.xx firmware version of the DPU. Should we upgrade to the latest EPROM revision for the DPU 7910A / 7920A If we do not upgrade the EPROM will I/NET work properly. 7910 / 7920 DPU Transactions not showing up in AMT - including Disabled / Deny Entry Sel / Deny Entry Schd (Schedule) 7910 / 7920 DPU Door Editor changes not downloaded to controller. Editor changes revert back to None. Product Line TAC INET Environment I/NET Seven DPU 7910A / 7920A 2.23 and above. Cause The recommendation is to always upgrade to the latest revision. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the DPU. The recommendation is too always upgrade to the latest revision to enable all of I/NET's features and fixes included in these revisions. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. If you have any additional concerns then please contact Product Support. Below are the New Features introduced in firmware revision 3.00: This release contains changes to support a real time clock and the ability to report messages with seconds. The DPU now supports generating an alarm for a card read of a card that has been disabled. The DPU now supports the use of User defined PIN numbers. The DPU now supports soft and graced APB. The DPU has been modified to handle the new user defined Duress scheme. The DPU now has the capability of generating a Reader Tamper Alarm by configuring a two bit DA at bit offset 4 for door 1 and 5 for door 2. Click Here to review the changes for EPROM firmware revisions 2.23 through to 3.04 for both the DPU 7910A and DPU 7920A. For SCU range of controllers refer to I/NET Security Control Unit (SCU) firmware releases. 

Issue The controller does not follow the programmed on/off times. Product Line Field Devices Environment CSC 5252 5352 Discrete Compensators Cause The flow temperature sensor has failed and is causing the controller to remain on. Resolution As part of it's "Out of Hours" operation, the controller will monitor the flow temperature and if it falls below 5'C, the controller will act to remove the risk of frost by starting the pump and opening the control valve. For a full description of this function, please refer to the CSC User Guide.

Issue How to run the Import/Export Fixup Utility Product Line Andover Continuum Environment CyberStation Import Export Fixup Utility, I/E Fixup, IEFixup, IE,ImpExpFixupUtil.exe CX Controller, i2 Controller, Infinet Controller Cause Points not updating or alarms not coming in have resulted in PSS asking for the import export fixup utility to be run. Resolution Note: Before performing the steps listed below, make sure a database backup has been performed. Navigate to the \Continuum directory. The Import Export Fixup Utility is located here The filename is ImpExpFixupUtil.exe. Double-click it. It runs in a DOS window and when complete, creates a file in the format IEFixuptimestamp.log. In some cases the log file will open; in others it will be saved to the \Continuum directory.

Issue Can old generation temperature sensors or new generation temperature sensors be used on CXR, CXT, CZT, CSC5252, CSC5352 ? Environment CXR CXT CZT CSC CSC5252 CSC5352 CSC 5252 CSC 5352 Cause Can old generation sensors or new generation sensors be used on CXR, CXT, CZT, CSC5252, CSC5352? Resolution Existing old generation sensors can be used on the current range of discrete controller, however they CANNOT be used/mixed with new generation sensors. Note, when replacing sensors or upgrading a controller to the current version, terminal numbers are different between old generation and new generation sensors, see the datasheet for terminal numbers. For the CXT datasheet click here. For the CXR datasheet click here. For the CZT datasheet click here. For the CSC5252 or 5352 datasheet click here.

Issue Need to purchase and replace the battery for the IAC-TS and IAC-600. Product Line Satchwell MicroNet Environment IAC-600 IAC-TS Cause The battery has failed and requires replacement. Resolution The battery is a lithium crystal SNAPHAT M4T28-BR12SH1 These are available from RS Components. The RS Components stock number is 189-1239. Manufacturer name: STMicroelectronics Manufacturer's part number: M4T28-BR12SH1 Specifications Category Detachable Lithium Power Source Maximum Operating Temperature 70°C Minimum Operating Temperature 0°C Mounting Through Hole Pin Count 4 Product Height 8mm Product Length 21.84mm Product Width 18.03mm Supplier Package SNAPHAT   Documentation M4T28-BR12SH M4T32-BR12SH TIMEKEEPER SNAPHAT (battery and crystal) Data Sheet.pdf Statement of conformity.pdf

Issue Modbus values are not not working reliably and are not updating as expected. Product Line Andover Continuum, TAC INET, TAC Vista Environment Xenta controllers 511, 527, 701, 711, 721, 731 and 913 Cause The amount of Modbus points being polled is excessive for the controller. Resolution The product data sheets indicates no limit to the Modbus points but only 31 Modbus devices over RS-485. With a practical install, a limit of 300-400 Modbus points per Xenta server  would be applicable. If you exceed this level, communications become slower than acceptable. Network performance can be affected when a large number of connection objects are in use ( direct transfers between Modbus and other protocols). There is no documented limitation, but the recommendation is not to exceed 300 connection objects per Xenta Server. Connection polling period should also be considered with a large amount of connection objects.