Building Automation Knowledge Base

Issue Cannot do a Save Runtime DB. - getting the following error:     java.net.ConnectException: Connection refused: connect      at java.net.PlainSocketImpl.socketConnect(Native Method)     at java.net.PlainSocketImpl.doConnect(Unknown Source)     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)     at java.net.PlainSocketImpl.connect(Unknown Source)     at java.net.Socket.connect(Unknown Source)     at java.net.Socket.connect(Unknown Source)     at java.net.Socket. (Unknown Source)     at java.net.Socket. (Unknown Source)     at tridium.nre.drivers.SocketDriver$TcpSocketFactory.createSocket(SocketDriver.java:690)     at tridium.nre.drivers.SocketDriver.create(SocketDriver.java:216)     at tridium.nre.drivers.SocketDriver$ConnectThread.run(SocketDriver.java:510)   Environment Niagara R2, UNC-520, UNC-410 Cause The connection error typically occurs during a database backup when the port used by the UNC has been changed from the default port 80. Resolution If this is the case, a line must be added to the station.properties file to specify the new port value. Open the Admin Tool and log into the UNC (not the station database). Right-click on the station name that indicates "running" and select Edit > Properties. The station.properties window will open (typically indicates autoStart=true and autoRestart=true). Add a line to this file that specifies the new port. Example: If the station database was configured to use port 8080, the line would read ... httpPort=8080 Choose File > Close and save when prompted. Reboot the UNC for change to take place   You should now be able to successfully backup the database. The details of this procedure are located in the documentation (Niagara Networking and Connectivity Guide).  

Issue Unable to connect to on premise server from client. Attempting to connect using the "Management Client" results in error "Could not connect to net.tcp://localhost:42171/KeepManagementService. The connection attempt lasted for a span of 00:00:01.9950682. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:42171" Looking at the Keep by Feenics services NONE are running, an attempt to start the Keep by Feenics Management Service results in 13816 Unknown error code. Product Line EcoStruxure Access Expert Environment On premise server Cause The server has been relocated to different machine. As a result, the server's key code has been invalidated and a new key code is needed. Resolution Send license information to your local country support group so that the new server's key code can be generated.   In the server, go to the location where the license file is located and move the file to a temporary location.   Run the Feenic.Keep.Installer.msi and do a REMOVE then install the server software.   When prompted during installation enter the new key code provided by product support.   If the issue is resolved, the license file that was moved to temporary location can be deleted.

Issue Where to obtain the documentation for I/A Series G3 software. Product Line TAC IA Series Environment I/A Series G3 software and hardware Cause Documentation is provided as a part of the software package.  Resolution The current documentation for any release of the I/A Series G3 software (except for proprietary drivers) is installed with the full software installation.  The documentation can be found in the docs folder under the \Niagara\niagara-x.x.x\ installation folder. Refer to Documentation for the I/A Series G3 Schneider Electric proprietary drivers for information on the availability of the I/A Series G3 Schneider Electric (TAC) proprietary driver documentation.

Issue Replacement stuffing box for valve V222 Environment V222: 721-2254-000 DN65 721-2258-000 DN80 721-2262-000 DN100 721-2266-000 DN125 721-2270-000 DN150 Gland Service kit (Packing box, Stuffing box): DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0 Cause Replacement parts for gland service Resolution Replacement gland service kits for V222: DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0

Issue When Continuum Explorer is launched it takes a very long time to update.  Product Line Andover Continuum Environment CyberStation WebClient Continuum Explorer Cause When Continuum Explorer is launched it must populate all objects that reside at the root.  When there are a very large number of Personnel objects or other object types in the root, Continuum Explorer will be slow or unresponsive until this population process is complete. Resolution Create a Folder under the Root of Continuum Explorer and move personnel objects to this folder. Consider doing this to other objects that exist in large numbers.

Issue When a Sigma animation is created, the object assigned and the graphic is run, the animations do not move or rotate. Product Line Satchwell Sigma Environment Sigma Graphics Animations Cause A Sigma animation has been used (for a BAS Legacy animation see BAS Legacy Animations are not moving in Sigma Graphics). Resolution Identify the animation file in c:\sigma\data\graphics\animations\ and open with Microsoft Paint and note the no. of frames across and no. of rows. Open the properties page of the animation. Change the Frames Across and Num Frames (rows x frames across) to that seen in MS Paint. Change the Width and Height by sizing the image in the preview window so that only 1 animation is visible e.g. 1 fan. Change the Horz Pitch and Vert Pitch so that the animation moves completely to the next animation in 1 step. Example: fan animated 4.bmp will be Frames Across = 4 Num Frames = 8 Start Col = 1 Start Row = 1 Width = 267 Height = 267 Horz Pitch = 267 Vert Pitch = 267

Issue The MNB-Vx (MNB-V1, MNB-V2) controllers are shown as replaced by the MNB-Vx-2 (MNB-V1-2, MNB-V2-2) on iPortal.  What is the difference? Environment MNB-V1 (-2) MNB-V2 (-2) Cause Production change Resolution There are no functional differences between the MNB-V2 and the MNB-V2-2 controllers. The part number was changed to allow tracking of an internal manufacturing change in the actuator part of the assembly.

Issue Valves V354 and V355 requires a specific type of actuator. Environment V354 (7315425000) V355 (7315529000) M52L (8522320000) EM52L (8522221000) EM52L-4 (8522210000) MC52A (8532221010) Cause Due to the design of the V354 and V355 valves, a specific type of actuator is necessary. Resolution MC52A, part no. 8532221010, is designed for use as a replacement actuator. It is delivered together with an adapter to fit the V354 valve.

Issue Vista central time chart and TAC Xenta Server  time chart - what happens when communication between Vista server and TAC Xenta Server is lost When is TAC Xenta Server time chart updated from Central time chart? Central time chart overwritten from TAC XBuilder Environment TAC Xenta 731, TAC Xenta 721, TAC Xenta 711, TAC Xenta 701, TAC Xenta 511. TAC Xenta 527, TAC Xenta 555 TAC XBuilder  TAC Vista Cause The Xenta Server only knows about its own time objects that is defined in XBuilder (or TSCHI in Menta). There are no synch between the central chart and the local time object. If you download the project from XBuilder, times defined from the central chart will be overwritten. To avoid this you have to perform a Get from Target before download, or you have to open the central time chart again and click ok to update the local time object once again. Resolution When you change a time in a central time schedule the change gets written down to the TAC Xenta Server time object the same way as a manual update. After the correct time has been set in the TAC Xenta Server time object,  from the central time chart,  the controller will operate using these times until it gets new information. It does not matter if the connection to the TAC Vista Server is lost. To perform get from target: In TAC XBuilder go to Project > Get from target Select "Get online changes" Click OK

Issue Upgrading 4.05 sites to Sigma 4.06 Environment Upgrade 4.05 SEB Cause Overview on upgrading Sigma 4.05 versions to Sigma 4.06 Resolution General Overview of the upgrade process. This overview is for background information only; ensure that, when upgrading, the instructions in sections 6.2.4 to 6.2.8 of the release note are followed. This release provides upgrade utilities which, when run, detect the release at which configuration data was created and selectively convert it as required. The main utilities are: SgiConvert: Converts .SGI graphics and associated files to the original version of the .SWC format. SigUpgrade: Converts all data (including graphical and tolerances) to the current release format. It must be run after graphics have converted from early .DRW (BAS) and .SGI (earlier Sigma) formats. It examines Also available is the Graphics Optimisation Tool which converts BMP files to JPG files and amends file name references in associated graphics. This tool should only be used in specific circumstances. See section 4.4.3. Revised Web Optimisation Tool for details. In addition any old BAS Graphics can be imported using a DrwSwcCnvrt utility. During the upgrade it is necessary to shutdown all clients of the server. The point at which this is done must be chosen to suit site circumstances and to minimise downtime. When Releases 4.00 and later is uninstalled, all data files are left intact (unlike earlier releases). The Standard Client software release and the Web ActiveX Client software release must both match the release of the server software. Do not allow clients and servers at different releases to attempt connection during the upgrade process. This applies for both Standard Clients and Web ActiveX Clients. If Remote Alarm Manager is used to read alarm data from Sigma, Remote Alarm Manager 2.0 must be used.

Issue What hardware platform can be used to replace the I/A Series R2 UNC-600 or UNC-610? Product Line TAC IA Series Environment I/A Series R2 UNC-600 UNC-610 Cause The I/A Series R2 UNC-600 and UNC-610 are obsolete and can no longer be repaired. Resolution The JACE-NXT (TRD-NXT-R2) can be considered the replacement for a UNC-6xx. The JACE-NXT includes (2) 10/100 Mb Ethernet ports and (1) RS-232 port, one isolated RS-485 port, one FTT-10A LonWorks interface, four USB ports, a 250 GB hard drive and includes a Windows XP Embedded operating system. Similar to the UNC-610 the JACE-NXT supports LonWorks and BACnet Ethernet / BACnet IP. Legacy driver support includes GCM, ASD, and DMS. Note: The JACE-NXT will not directly support BACnet MSTP or MicroSmart devices. The JACE-NXT requires installation of R2 Release 2.301.532 or higher. TRD-NXT-UI (Web Browser Support) TRD-NXT-UPS (Optional UPS - includes UPS unit and battery)

Issue Continuum entries in the windows application events occasionally shows error related to the database connection. A database fault warning state was detected and cleared. This is an indication that the connection to the Continuum database was lost for a moment. "wuaueng.dll (46108) SUS20ClientDataStore: The database engine stopped the instance (0)". "wuaueng.dll (46108) SUS20ClientDataStore: The database engine started a new instance (0)."   Environment CyberStation Windows Event Viewer SQL Server Cause Informational entries in the windows application event viewer frequently refer to Continuum reporting a database fault warning. The warning may or may not be accompanied with other information such as: ClientDataStore: The database engine stopped the instance (0) ClientDataStore: The database engine started a new instance (0) These events can occur in the ordinary operation of the SQL Server environment, or they may be associated with errors. Resolution If a 'stopped' instance warning is immediately followed by a 'restarted' instance warning and not associated with an error then the event took place in the context of ordinary operation of the SQL server and can be ignored. If on the other hand there is an error reported such as ‘The database instance ran out of disk space.’ then corrective action will be required.

Issue The damper position value sometimes displays as "NA" Product Line I/A Series Environment I/A Series MNB VAV Cause The VAVActuator object in the controller's database has its position initialization mode set to 0 which means it will initialize the position value at its earliest opportunity following a reset. Therefore, the position will display as "NA" until the controller reaches the full open or full closed position Resolution The VAVActuator object in the controller's database has three options for the position initialization mode following a reset. If having the position display NA for a time following a reset is not desirable the position initialization mode can be set to force the controller to go open or closed following a reset and then it will display a value for the position following a reset. The following table is extracted from the WorkPlace Tech 5.x Engineering Guide Supplement. Set the Initialization Mode to 1 or 2 (in the VAVActuator object properties) and download the application. 

Issue Cannot upgrade CyberStation key. Environment CyberStation Cause Received key activation code from Repair Dept. to add an option to CyberStation. After entering the activation code into the KeyWriter application, getting the error "Invalid Key Activation Code: Please try again..."    Resolution There is a KeyWriter application for the Continuum Reports Add-On Software and a different one for activation codes from the Repair Dept..  Use ...\Program Files\Continuum\CyberKeyWriter2.exe for the codes from the Repair Dept.

Issue Connecting Modbus RS-485 to a CX9200 Comm4 will not operate correctly. Environment Modbus RTU XDriver Serial port XDriver Cause Different ports support different electrical standards. Resolution Comm1 and Comm2 of a CX9200 has RS-485 ports and can be used directly with the Modbus RTU XDriver. As a first generation controller it requires the 1st Generation driver. Second Generation X Drivers are only for the second generation controllers (bCX1, NC2 &ACX) The comm ports also have RS-232 ports that can be used and using an external RS-232 to RS-485 converter they can support an RS-485 network. On Comm 4 it has 2 ports they are RS-232 and RS-422 which is sometimes referred to as "4 wire RS-485". But this is not the regular 2 wire RS-485. The difference between regular RS-485 and RS-422 (4 Wire RS-485) is half and full duplex. The RS-422 with + and - connected is not a true RS-485 2 wire as the transmitted data will also be received by the transmitting controller (feedback). Regular RS-485 will turn off its receiver when it is transmitting.

Issue Is it possible to download the Xenta 511 firmware to a Xenta 511-B? Environment TAC Xenta 511-B version 5.1.7 Cause The 511-B version became obsolete in Vista version 5.1.5 as all Xenta servers got support for Modbus and the B stands for Modbus support. After version 5.1.5 it is only one firmware for the 511 and that is possible to download also to a 511-B.   Resolution The 511-B version became obsolete in Vista version 5.1.5 as all Xenta servers got support for Modbus and the B stands for Modbus support. After version 5.1.5 it is only one firmware for the 511 and that is possible to download also to a 511-B.  

Issue Issues with Operator username/password which can arise when restoring an SP-C-Web Database.   Product Line EcoStruxure Security Expert   Environment SP-C-Web   Cause The SP-C-Webs Database Restore process is different from the Security Expert Client/Server.   Resolution SP-C-Webs are unlike the Security Expert Client/Server model in that the SP-C-Web contains its own on-board controller database This controller database can be backup by the customer and then restored onto another SP-C-Web by a field or support engineer However, issues can arise when trying to access that restored SP-C-Web customer database using the customers own provided Operator username/password

Issue Modbus integration to Data Industrial Series 3050 BTU monitor Environment I/A Series G3 ENC-520 Modbus Asynchronous (Async) driver Cause Required to read the values in the BTU monitor via Modbus Async. Resolution The below Modbus registers table is provided by the BTU monitor manufacturer. Here are the basic procedures and settings in an ENC for this integration. Add a ModbusAsyncNetwork to the station database.   In the ModbusAsyncNetwork properties, configure the Serial Port Config. Port Name: COMX (where X is the COM port number of the ENC used for this integration). Baud Rate: As per baud rate setting in the Modbus device. We recommend the baud rate of 9600 as this appears to work best with this device. Data Bits: 8 Stop Bits: 1 Parity: None Flow Control Mode: No   Other properties of the ModbusAsyncNetwork to be left at its default values.   Add a new Modbus Async Device to the ModbusAsyncNetwork. The device address is as per address set in the BTU monitor device.   Leave all properties in the Modbus Async Device object as their default values.   Go to the Points folder of the Modbus Async Device and add the required Modbus objects. Configure the properties of each object as per the following. Address Format: Decimal Address: Refer to the table above. If reading register 30002, use 2 as the address. Reg Type: Input Data Type: Long   Set the Facets for the object  

Issue Search widget graphics can't find graphic pages created under child servers.    Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause Currently, in EBO 2023, the dynamic search widget will only find graphic pages created on the server the user is logged into on WebStation. The dashboard search widget is not related to the native EBO search object and cannot search child servers. Resolution EBO 2024 (V6) or higher: From 6.0.1 it is possible to include TGML widgets from sub servers (all servers must have EBO version 6.0.1). Note that this functionality is only supported when you use HTTPS as the protocol between the servers, which is the default protocol in 6.0.1.   EBO 2023 (V5) or lower: If graphic pages are located under child servers, they need to be added to the dashboard manually.  Refer to: Adding a Graphic to a Dashboard

Issue Running Bomgar Remote Support Client from Linux for support from Product Support Services Product Line EcoStruxure Building Operation Environment Building Operation Edge Server - Standard Cause Bomgar session downloads Bomgar-scc-[long string of characters].desktop file and need to run to connect with a Product Support Services agent. Resolution The file needs to be granted permission to execute and then run. Open browser on Linux OS for website: https://seconnect.se.com  Enter the 7-digit Session Key and press SUBMIT button. After saving the client to the Downloads folder, right-click on the bomgar-scc-[long string of characters].desktop file, then click Properties.  Click on the Permissions tab, then check the checkbox next to Execute to Allow executing file as program.  Open Terminal, then type "sh " (without quotes and not forgetting a space), then drag the file to the Terminal window, then press Enter. The full command will look similar to this image.  Once the executable runs, this image will appear on the screen as the full session begins.  Click Allow to let the agent view and control your computer.