Building Automation Knowledge Base

Issue Unable to connect to the ENC using its IP address. The ENC Ethernet port LED's appear to indicate normal operation. Product Line TAC IA Series Environment I/A Series Enterprise Network Controller Cause The ENC DHCP function was enabled by mistake on a system that does not have a DHCP server. The ENC when booted up will try to get an IP address from a DHCP server which does not exist and the ENC may not have a valid IP address. Resolution Connect to the ENC via its serial shell and perform the following procedure. Refer to Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal for details on connecting to the ENC serial shell. 1. Connect to the ENC serial shell using Windows HyperTerminal. Allow the ENC to boot up completely and you should see output messages similar to the following.   JACE 4/5 IPL Version 6.40 ECC to stop Autobooting on-board nand james startup version 6.41 launching devc waiting for /dev/ser1 creating symlink for /dev/serconsole Welcome to QNX Neutrino 6.4 on the ppc824x(james) starting /ffs0 filesystem ETFS_FS_2048 fs-etfs-jace2048: Truncating fid 0x2f from 337920 to 316718 bytes fs-etfs-jace2048: Truncating fid 0x64 from 5488640 to 13 bytes fs-etfs-jace2048: Truncating fid 0x1ce from 4096 to 0 bytes i2c: Using 100Mhz freq divider Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:20:96:08:ee:06 media: Ethernet none status: no carrier inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- bad battery detected, A/C power test will not function MESSAGE [12:38:25 19-Jun-2013] [tid=1] niagarad: starting, baja_home=/niagara MESSAGE [12:38:25 19-Jun-2013] [tid=1] webserver: web server started [tid = 4] MESSAGE [12:38:25 19-Jun-2013] [tid=1] app registry: station registry starting MESSAGE [12:38:25 19-Jun-2013] [tid=7] engine watchdog: station TEST0817_TIM watchdog thread started [tid = 8] MESSAGE [12:38:25 19-Jun-2013] [tid=7] station: station TEST0817_TIM starting login: tac Password: [2J [H J404 System Shell ------------------------------------------------------------------------- hostid: Qnx-J404-0000-15C8-14F9 serial number: 584966 build version: 2.5.25 build date: built on 2011-04-04 16:47:24 system time: Wed Jun 19 12:38:43 STD 2013 niagara daemon port: 3011 en0: inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- 1. Update System Time 2. Update Network Settings 3. Ping Host 4. Enable/Disable Ftp 5. Enable/Disable Telnet 6. Update Platform Account 7. Reboot L. Logout   2. Select option 2 for update the network settings. 3. Press 'enter' (enter leaves the field at the original setting) for each field until the 'IP address (clear to use DHCP)' field. 4. Type in the required IP address here and press enter. This will disable the ENC DHCP function. 5. Key in the subnet mask at the next line and select 'n' when prompted to use IPv6. 6. Press enter until you are prompted to save the changes.      [2J [HJACE Network Configuration Utility Enter new value, '.' to clear the field or '' to keep existing value Hostname : Domain <> : Primary DNS Server <> : Secondary DNS Server <> : Route <192.168.10.1> : Primary IPv6 DNS Server <> : Secondary IPv6 DNS Server <> : IPv6 Route <> : NET1 Ethernet interface IP address (clear to use DHCP) <> : 192.168.1.141 Subnet mask <> : 255.255.255.0 Enable IPv6 addressing on this adapter? (Y/n) : n Confirm new configuration Hostname : localhost Domain : Default Gateway : 192.168.10.1 Primary DNS : Secondary DNS : Default IPv6 Gateway : Primary IPv6 DNS : Secondary IPv6 DNS : NET1 settings: IP Address : 192.168.1.141 Subnet Mask : 255.255.255.0 IPv6 Addressing disabled Save these settings? (Y/n) : y    7. Reboot the ENC and connect to the ENC using Workbench. 

Issue SOAP service can't be reached at http://localhost:8030/SecurityExpertSOAPService/service.svc.  HTTP Error 404 error seen when attempting to browse. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Confusion related to the indicator Windows uses to denote when features have been enabled. Instructions in the Security Expert SOAP service installation manual not sufficiently clear. For instance, the documentation shows a checkmark in the .NET framework feature but it does not show the sub-items, a checkmark here means all of the sub-items are also enabled but this is not necessarily intuitive.  When not all of the sub-items are enabled, Windows shows the check box filled with a black square but many users are interpreting this as meaning the same as a checkmark. Resolution When a feature check box shows a checkmark in the documentation, make sure to expand the feature and enable ALL of its sub-items. 

Issue How are the bits allocated in a 26bit Wiegand card format? Environment Access control peripherals data format Cause Although this is an openly published data format, sometimes the actual data bit format is required. Resolution The Wiegand 26 bit format consists of 24 bits of data and 2 Parity bits (Odd and Even) The 24 data bits are split between 8 bits for the Site code and 16 bits for the card number. Giving a card number range of 1 to 65535, and a site code range of 1 to 255. A spreadsheet defining the format can be downloaded here.

Issue TGML pages are slow to load in Workstation TGML objects are not responsive Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation TGML Cause The driver of the graphic card is outdated or not supported. Resolution Visit the webpage of the PC's brand and update the driver for the graphic card.

Issue Can an export file from one version of EcoStruxure Building Operation(EBO) be imported to another version of EBO?  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Export files are in general NOT backward compatible. A Script or Function Block Program that is exported from for example version 3.1.x is NOT guaranteed to import successfully into an earlier release Resolution Starting in version 3.0.x, import files exported from a later release than where they are imported will be denied. An export file from 3.1.x cannot be imported in 3.0.x. An export file from 3.0.x can however still be imported in 2.0.x, but it's not recommended, and it may fail to import successfully. In version, 3.1.x import files exported from versions older than version 1.3, will be denied. Starting in version 3.2.x, import files exported from versions older than 1.8.x will be denied.

Issue What is the procedure for upgrading firmware in an I/A Controller? Product Line TAC IA Series Environment Workplace Commissioning Tool I/A Series MNB Cause Improvements to MNB firmware require upgrades to be made periodically to the controllers. Resolution This video demonstrates how to upgrade MNB devices with the I/A Commissioning Tool.

Issue After updating Java, webstation doesn't show graphics. The window is blank/white. If the error you get is "Error. Click for details" and not a blank window, please refer to Webstation graphics not working after Java updated to Java 7 update 51. Product Line EcoStruxure Building Operation, TAC Vista Environment Java Webstation Cause There's an issue with Java and Webstation in SmartStruxure 1.5 when using panels. There's a hotfix available (1.5.0.2307) correcting this issue. Either Contact Product Support for this hotfix or download it on The Exchange Download Center. If panels are not used or the SmartStruxure version is lower than 1.5 or you are working with another product line such as TAC Vista, this article might help. This issue is usually only seen when updating an existing Java installation. If no version of Java has been installed previously, the issues doesn't seem to appear. According to Sun, there's an issue with the deployment.properties file. Read this article for further information. Resolution First try to install the newest version of Java. Version 1.7u67 has just been released, and is supposed to solve the issue. If you are using a x64 operating system, make sure you install both the x86 and the x64 version of Java in order to support both 32 bit and 64 bit browsers installed. If that doesn't work, try the procedure below. 1: Make sure all browsers are closed 2: Uninstall all Java versions 3: Make a copy of the file C:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\security\exception.sites (replace user_name with the profile name of the user logged into Windows) 4: Delete the folder C:\Users\%username%\AppData\LocalLow\Sun (replace user_name with the profile name of the user logged into Windows) 5: Install the latest version of Java (https://java.com/en/download/manual.jsp) - if you are using a x64 operating system, make sure you install both the x86 and the x64 version 6: Verify that you have the latest Java version and that you don't have older versions using the Java uninstall applet: https://java.com/en/download/uninstallapplet.jsp 7: Move the exception.sites file back into C:\Users\user_name\AppData\LocalLow\Sun\Java\Deployment\security (replace user_name with the profile name of the user logged into Windows) - if the directory doesn't exist, make the directories missing to complete the path 8: Try viewing TGML graphics again

Issue Is it possible to 'hot swap' IO modules? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation I/O Modules Cause Some critical applications require 24-hour operation. Resolution The I/O modules allow hot-connection of terminal bases and hot-swapping of the modules to their bases. This design ensures continuous power and communication during service operations.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Download Service fails to start after an upgrade to v.4.2.251 Product Line EcoStruxure Security Expert Environment Security Expert Server v4.2.251 Cause Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.30501; (VC++ 2013 Redist v12.0.0.30501.0) is not installed. This package is a pre-requisite to installing Security Expert v4.2.251. It was needed for extending the Suprema integration but did not get added to the installer for that version. This is now packed with the Security Expert installer. Resolution There are two options to resolve this; 1. [Preferred Option] Install the current release of Security Expert. This required package is now included in all new versions of the Security Expert installation file. 2. Install the package from Microsoft before installing Security Expert 4.2.251. Locate the file on the Microsoft site https://www.microsoft.com/en-nz/download/details.aspx?id=40784. Download and install vcredist_x86.exe, the 32 bit version (because Security Expert is a 32 bit application), before performing the upgrade.

Issue Workstation Pro License fails to allow running of v2.0 or v3.x EcoStruxure WorkStation following an upgrade Product Line EcoStruxure Building Operation Environment WorkStation Licensing Cause Workstation Pro License SXWSWWORK00002 (SW-STATION-PRO-0) is the same for v1.x and v2.x, so that WorkStation Pro should continue to operate after an upgrade. However, there was a License upgrade/change at v1.7 (from v1 to v2) and if the License was registered before this the version remains at v1 and this will not run v2.x WorkStation Resolution The WorkStation Pro License needs to be returned, then re-installed using the online Licensing system.   Before License is returned   After license is returned  The process to return a license can be found in Webhelp.

Issue Managing the address table in a Lonworks device Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment I/A Series MNL TAC Xenta Third-party LON devices Building Operation Automation Server Cause A LonWorks device contains an Address Table which will hold a maximum of 15 addresses. Once this table is full, all bindings will only be able to use the broadcast setting which is not desirable. A Xenta 200,300 or 400 controller will have its first 2 address tables used with TAG 0 and TAG 1 binding. This leaves only 13 addresses for user bindings not the 15 addresses like other LonWorks devices. Resolution ​When you create a binding in LonWorks, you decide its behavior by selecting a binding profile. You either select a binding profile, or you use the default profile. There are basically three types of binding profiles: Acknowledged profiles Unacknowledged profiles Broadcast profiles Using an Acknowledged profile will consume one of the 15 available address table addresses on both the sending and the receiving device. The Unacknowledged profiles will only use one Address on the sending device's address table. Broadcast binds do not use an address but are not recommended. Use an acknowledged binding profile when the sending device should receive an acknowledgment from the receiving device indicating that the value of the bound variable was successfully sent. Binding profile Transmit timer Retry count Acknowledged Profile 96 ms 3 Acknowledged, Tx tmr 256, 3 retries 256 ms 3 Acknowledged, Tx tmr 256, 5 retries 256 ms 5 Acknowledged, Tx tmr 1024, 5 retries 1024 ms 5 Be careful of creating large, acknowledged fan-out bindings because they generate a lot of traffic, especially if the device of one of the recipients is offline.  Use an unacknowledged binding profile when the sending device should not receive an acknowledgment from the receiving device. Use this type when the value being sent is not critical and is of low importance to the control logic. Binding profile Repeat timer Repeat count Unacknowledged Profile   0 Unacknowledged Repeated Profile 48 ms 3 Unacknowledged Repeated, 5 repeats 48 ms 5 Use a broadcast profile when you do not want to use up an entry in the address table. The device address table has 15 available entries for bindings but the first entry is a reserved broadcast entry that all broadcast bindings can share. Binding profile Repeat timer Repeat count Broadcast Profile   0 Broadcast Profile, 5 repeats 48 ms 5 If no binding profile is selected, a default profile is used: Point-to-point bindings use the Acknowledged profile as default. Fan-out bindings use the Unacknowledged Repeated profile as default. Building Operation uses the broadcast profile as default when the device address table has run out of entries. If a point-to-point binding is changed to a fan-out binding, the binding profile is automatically updated to an Unacknowledged Repeated profile. If a fan-out binding is changed to a point-to-point binding, the binding profile is automatically updated to an Acknowledged profile.  This and other information about lon bindings is available on the online help guide Using a Lon Binding in StruxureWare Building Operation More information on the different tables used by each LON device

Issue Allowing write access from BACnet Product Line TAC IA Series Environment I/A Series G3 BACnet Integration Cause By default, the BACnet driver provides external BACnet (client) devices "read access" to all exposed (exported to BACnet) objects in the station. Access depends on a station user named "BACnet." If this user does not already exist in the station, the Bacnet driver automatically creates it, upon startup. The BACnet user is initially created without any permissions. Resolution See below which is extracted from the Niagara Ax BACnet Guide: To allow any external writes (from BACnet) to properties of exported components, including invoking commands (actions), you must assign the BACnet user the necessary permissions to those components. For example, to allow an invoked "Active" action from BACnet to an exported BooleanWritable, in addition to making it "BACnet Writable" at priority level 8 when exporting, you must configure the station’s BACnet user to have operator write permissions on that BooleanWritable, at a minimum. Or, if an exported NumericWritable has an alarm extension, and you want to permit external BACnet writes to its "alarm limit" values, configure the BACnet user to have admin write permissions on the exported NumericWritable. In either example, to allow an external BACnet write to a property like "Out Of Service" or "Notify Type," you must give the BACnet user admin write permissions on the BACnet export descriptors. For details about station user security, see "About Security" in the User Guide. Note: BACnet user permissions also apply to writes of any exported files and histories. Also, note that while a password for the BACnet user is technically not needed (for external BACnet access), you should assign one anyway, because of the write permissions typically assigned. Make it a "non-blank" password, and guard this password carefully.

Issue Seeing 0x00001427 Bad RTC chip errors in controller error log along with controller warm start errors. Controller error log contains entries similar to below.    01/01/1989 00:01:10.33 0x00001427       0x04070400       0x02028922       0x00000001       0x0000000                 HardwareErr__ Bad RTC chip 04/16/2011 09:47:24.93 0x00030000       0x00216500       0x00105c62       0x00000000       0x00000000                Warm start 01/01/1989 00:00:00.94 0x00001427       0x00201900       0x0011edba      0x00000001       0x00000000                 HardwareErr__ Bad RTC chip Environment Continuum Controllers Cause The error is a time related error but may not indicate that there is a physical problem with the controllers Real Time Clock (RTC). This can be due to an issue occuring on startup of a controller where there may be requests for time from COV updates. If that request comes in prior to the RTC clock coming up, it can post this error. The COV code will post this error and then try again later.  Resolution If this error occurs after a restart of the controller then this is more than likely a benign error and can be ignored. However, if it occurs when the controller hasn’t just restarted then it could be an actual fault with the RTC chip and may need to be returned for repair.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue How can I clone an MPM? How can I upload config.db to an MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Unable to upload config.db to an MPM Resolution An MPM can be cloned from Building Expert by exporting default.db from one MPM and importing it to another (using the "Export Database" and "import Database" buttons) Note: Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. If it is necessary to clone the system configuration objects as well, refer to the procedure below: This procedure show you how to upload the Database to an MPM. To download a backup of the database, refer to MPM database information. Power up the MPM and ensure either its IP address can be pinged or Building Expert is accessible. In address bar of browser, enter 10.50.80.3/test.html. (assuming IP address of MPM is set to default) In Remote Path field of File Upload section, enter config.db. Click Browse and Navigate to the backup config.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Note: Uploading the config.db file first does not cause the MPM to reboot; which is why it is uploaded first On Browser, click to return to previous page. In Remote Path field of File Upload section, enter default.db. Click Browse and Navigate to the backup default.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. Note: MPM must not powered off during this time In address bar, enter 10.50.80.3 to connect to Building Expert and validate Database upgrade is correct.

Issue What does it mean when a TAC controller is said to have a Universal Input? Environment Xenta Programmable Controllers Xenta I/O modules Cause Universal typically means all types; however, this definition does not apply to TAC Xenta controllers. Resolution With respect to TAC Xenta controllers, the term "Universal" means more than one type of input. It is important that the project planner review the data sheet to determine the exact definition for "Universal" as it applies to any TAC Xenta device.

Issue What is a MIP? Environment I/NET site Cause What is a MIP board? Resolution The Memory Interface Processor (MIP) is a plug-in module that provides significant functional and speed enhancements to TAC products. It provides increased processor performance and enables 96 K of on-board RAM for I/NET-related processing. The MIP is installed by removing the process and other memory chip(s). (The MIP is not designed to be used with all or our products!) Refer to TCON101 and TCON123.

Issue Unable to login to AS directly when using Domain user. It is possible to login to AS directly with "Local" Domain and to the ES with same Domain. Receive error "Can not continue because server is offline or temporarily unavailable" even though ES is online. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Domain Cause AS is unable to communicate with the ES to properly authenticate the Domain user.  If the ES is picking up a WiFi IP address instead of the LAN IP address, this can be the cause. All other communications can still function correctly with the ES but the issue occurs when the AS tries to connect directly to query the Domain, it will be using the wrong IP address. Resolution Changed the order of NIC''s in Windows so that the Local Area Connection was first, confirmed the ES had the correct IP address, confirmed the AS saw the change, and was then able to login to the AS directly using the Domain user. See How to set the Enterprise Server IP address for details on how to ensure you are using the correct IP address.  Another thing to look out for is that you are using the correct port number for the ES communications as seen from the AS.

Issue Using Xenta Controllers with a Tridium Jace Product Line TAC Vista, TAC IA Series Environment Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Tridium AX / N4 Jace Cause By default, the Tridium Jace acts as a network manager which will disrupt controller addresses, SNVT bindings, and Group bindings previously set up in LonMaker. Resolution  To disable this feature provide these steps to a Tridium Integrator: Use Niagara WorkBench Connect to Jace Under the Services Folder, find "LonNetwork" Go to  "Local Lon Device" Set the "External Config" property to "true" Hit "Save"  

Issue Modbus XDriver for BCX1-9640/4040 (ModbusRTU_bCX_xxxxxxx.xdr) on comm2 for RS-485 does not work even when the comm2 port says that the driver is installed, no errors and the comm parameters match the Modbus protocol device (ie, 19.2k, n, 8, -). Product Line Andover Continuum Environment bCX1-9640/4040 Controller Modbus XDriver Cause Check the Communication Configuration Point (Function Code 99) of the XDriver. Resolution Function Code 99 is used to select between RS-485 and RS-232 when using a bCX1-9640/4040 controller with Modbus XDriver installed in Comm2 port. Unlike the Modbus XDriver for CX ModbusRTU_2xxxxxx.xdr), the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) requires user to set correct value to the FileNumber attribute of Function Code 99 (Communication Configuration Point ). If the FileNumber attribute of the Communication Configuration Point is not set to "1", the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) uses the default value, which is "0". When the FileNumber attribute is set to "0", the Modbus XDriver for BCX1-96404040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-232. When the FileNumber attribute is set to "1", the Modbus XDriver for BCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-485. For detailed information, refer to the Modbus RTU XDriver User Guide on page15: Function Code 99 – Communication Configuration Point.

Issue After an install of webclient 1.80/1.81 on Windows Server 2003 you receive the following error opening webpinpoint graphics: Could not find pin file at specified URL. Please contact your system administrator. Environment webpinpoint 1.80/1.81 Cause .PIN and .EMF file extensions have not been registered in the IIS MIME Types (for webClient Pinpoint graphics). Also, an IP conflict with another PC can cause this.   Resolution Webpinpoint is installed properly when first opening a graphic, you can browse to the NewGraphicsFiles folder through Internet Explorer and the web folder tab in Cyberstation pinpoint options resolves properly without Red Xs. To fix this, follow the instructions on Pg 32 in the Webclient 1.80/1.81 Installation Guide as follows Registering File Extensions for Server 2003 after IIS Installation: If you have a Windows Server 2003 system, you must also register the .PIN and .EMF file extensions in the IIS MIME Types (for webClient Pinpoint graphics). After IIS installation, follow this procedure: From the Control Panel, double click and open Administrative Tools. The Administrative Tools dialog appears. Double click and open Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager dialog appears. In the tree, right click on the machine name, and select Properties from the popup menu. Click the MIME Types button. The MIME Types dialog appears. Click the NEW button. The MIME Types dialog appears with 2 empty fields In the Extension field, enter: .pin and in the MIME type field, enter: pinfiles/plain. Click Ok Click the NEW button again, but in the Extension field, enter: .emf and in the MIME type field, enter: image/emf Click OK three times back through the dialogs. Restart your machine and open webpinpoint