Building Automation Knowledge Base

Issue When deploying ES/AS, it will go through for a while until the end. Then it will show failed, and the cause is communication error. Environment SmartStruxure PCS Cause 1. First check whether there is any real network issue, like router setting, fireware or anti-virus software. If it is confirmed that the network is good, check whether the date/time setting match the current ones. 2. If both are checked for the first point, the cause is there is a defect for PCS when the project contains BACNet interface and objects. Resolution 1. Change the date/time to current ones. 2. If it doesn't work, contact PSS to ask for hotfix: R1.5.0.7201.

Issue Changing a Sigma value from a graphic. Environment Object Override Graphic Slider Cause From an imported or transitioned Satchwell Sigma graphic it is possible to override an object value, from a StruxureWare Building Operation Trackbar graphic, it is not. Resolution Sigma's objects are unusual, in that they are not writable. To change their value you have to force them, (or manually override them in Sigma terms).  This means that the standard "Trackbar" component that comes with StruxureWare Building Operation, will not work with Sigma. To manually override the Sigma object, the existing "Trackbar" can be modified to call "setForce" on the object .  This is what legacy Sigma normally does if you have a slider on a graphic, and move the slider. It sets the object to a manual override state. The standard "Trackbar" component can be changed to make it work with Sigma objects. To do this, the "setForce" line was added to the function "setCurrentValue",  setForce(fullName, true);  return setValue(fullName, value);  Note:-  As with legacy Sigma, StruxureWare Building Operation Transitioned Sigma only supports changing certain values.  For example:- You can't make a graphic change the alarm high limit. You can't make it change the configuration value "Fixed value".  The modified "Trackbar in the StruxureWare Building Operation graphic must be bound to the "Value" property, just like it would have been in legacy Sigma.  It is not valid to bind it to the configuration value. To download a copy of the modified "Trackbar", please click HERE.

Issue When trying to log into SBO Workstation receive the following error: Invalid returned data from license server system. (Error code: -12) Product Line EcoStruxure Building Operation Environment Workstation Enterprise Server Cause This error has been caused when a Workstation license is present but no Enterprise Server license is present. Resolution An Enterprise Server license must be purchased and added. Please see EcoStruxure Building Operation License types for license options and part numbers.

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 Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue Programming an 8-Bit HID or Indala Prox/Pin Pad reader Environment I/Net Site with Access Control Cause There is a requirement to supply an 8-Bit Prox/Pin Pad reader at a site. How do I program this reader? Resolution Attached is a PDF File that guides you through the setup if this type of reader in an I/Net Seven system. Click here to download.

Issue At times it is necessary to monitor an external variable to trigger action in SmartStuxure Lite Environment Smart Struxure Lite Smart Struxure Continuum AS MPM Windows 7 Windows Server 2008 Cause Need the ability to trigger actions from an external variable to run a lua script Resolution Use a lua script in your MPM that copies the value of ME.PG#_ENABLE.value to an Analog/binary value. This value can then be seen from the AS or BCX through bacnet and you can have the AS or BCX do different functions depending on that value

Issue What bit formats are accepted by the Security Expert Controller (SP-C) for communicating with third-party card reader with pin? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controller Cause When using pin pad readers with the Security Expert Controller there are only a few supported bit formats.  Resolution Only these following formats are support and tested with Security Expert at this time: 26 Bit (Site 0) ARK-501 4 Bit 4 Bit Parity 4 Bit Buf 4 Bit Buf & Par 36 Bit (IEI S0)

Issue What HID Corporate 1000 card formats are supported by Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controller Security Expert Smart Card Reader Cause Information about HID Corporate 1000 card formats is needed to configure the card readers correctly. The existing documentation does not mention this. Resolution HID Corporate 1000 35-bit format has been validated with Security Expert. To use this go to Expanders | Reader Expanders | Reader 1 and set the Reader 1 Format setting to HID Corp 1000 as shown below. Other HID Corporate 1000 formats may work however they have not been validated. If the format specification is known, it is possible to program the cards in a custom format. As an example, below are the custom format settings used for the HID Corporate 1000 48-bit format cards. Go to the Custom Reader Format tab of your controller and enter the following values. HID Corporate 1000 48-bit format 1 HID Corporate 1000 48-bit format 2 If the format is different from the above two examples or is not known, please provide support with the site code, card number and raw data output for Any Bit RAW card reads from at least three different cards to help determine the format. Refer to article Show raw card data of a badged card in Security Expert for further details on this.

Issue Information concerning Linux releases used within the Automation Server.   Product Line EcoStruxure Building Operation Environment Linux Operating System (OS) Building Operation Automation Server Building Operation Automation Server Premium Cause Questions concerning Linux releases used within the Automation Server. Resolution AS versions to 1.4.1 run Linux kernel 2.6.25.1 AS versions 1.5 to 2.0.2 run Linux kernel 3.0.101 AS-P versions 1.7 to 2.0.2 run Linux kernel 3.5.0-lsp-3.3.1 For questions concerning what type of Linux...i.e. Red Hat, Ubuntu, openSUSE - There is no linux distribution in the automation server just vanilla linux kernel. For further reading, download some documentation about the kernel from their website www.kernel.org  

Issue Is R2 or G3 compatible with JAVA 8? Product Line TAC IA Series Environment R2 G3 Cause Oracle released Java 8 Resolution At the time of the creation of this article (February 17, 2015) no versions of R2  have been tested with Java 8 and therefore Java 8 is not supported until further notice.  As of March 15, 2015, Tridium has now tested the latest maintenance builds of G3 releases 3.6, 3.7 and 3.8 and found that they appear to work properly with Java 8 update 31.

Issue When adding MNL controller in Workstation for Projects, it will show up an error: Object type is not supported. Environment SmartStruxure 1.5 Workstation for Project PCS MNL controller Cause When using the Project Configuration Server, you cannot create MNL LonWorks devices and applications. Accordingly, the WorkPlace Tech Editor option does not display in the Control Panel. Resolution MNL LonWorks devices can be added in an Enterprise Server or Automation Server after deploying a project to one of these servers.

Issue A site physical access is configured as follows... Upon arriving at the site, the employee must check-in at a gate where a main biometric reader at a VIRTUAL door is configured with entry/exit readers for Check-in and Check-out. This 'Registration' reader is not controlling access to any physical door, the Registration door in Continuum has zero for door relay channel but IT IS configured with entry/exit readers so the Continuum access control panel can detect the check-in/check-out transactions. Once the employee has checked in, he can continue on to the building where he must then present his physical access credentials at a physical door to gain access into the building. The site requirement is that the employee can not be given access to the building until they have checked-in at the Registration reader at the gate, also, access to the building must be removed upon the employee checking-out at the gate when leaving the site. The doors in the buildings are configured with entry reader ONLY, so entry/egress anti-passback cannot be used. Product Line Andover Continuum Environment CyberStation ACX2 NC2 NC1 9702 Cause Documentation Resolution Since this must be done on a per employee basis, an InfinityNumeric is created per employee and assigned as the area schedule in the personnel object for the areas that are in the building. A specific convention is used for the name of the numerics (Key_XXXXX) where XXXXX is the card number assigned to the employee. A PE program monitors the registration door at the gate, when en employee arrives and checks-in the program finds the appropriate employee key numeric and turns it ON to grant access to the areas in the building, conversely, when the employee leaves, the program finds the right key and turns it to OFF to deny access. PROGRAM SAMPLE IMPORTANT: PE PROGRAM IS PROVIDED HERE AS PROOF OF CONCEPT ONLY AND IS NOT INTENDED TO BE TAKEN AS A COMPLETE TESTED SOLUTION. 'This program controls access to the building on a per employee basis 'The area schedule numeric for the employee is turned ON when the employee 'reports at the entrance reader (GIVE EMPLOYEE THE KEY) and OFF when the 'employee reports his departure at the exit reader. (TAKE THE KEY FROM THE EMPLOYEE) 'ASSUMPTIONS '1. All cards have the same site code 'AUTO START 'LOOPING Numeric Direction, DEBUG String theKey Line INIT DEBUG = 1 'SET THIS TO 1 FOR DEBUG HELP Goto WAIT_FOR_ACCESS Line WAIT_FOR_ACCESS theKey = "Key_" 'RESET KEY NAME 'WAIT FOR A VALID ACCESS AT THE LOBBY If Lobby ValidAccess then Goto GET_DIRECTION Line GET_DIRECTION 'DETERMINE IF ENTRY OR EGRESS If Lobby TimeEntered > Lobby TimeExited then Goto ENTRY Else Goto EXIT Line ENTRY theKey = theKey ; Lobby EntryLastCard 'FIND THE KEY FOR THIS CARD getname(theKey) = On 'GIVE THE EMPLOYEE THE KEY Goto WAIT_FOR_ACCESS Line EXIT theKey = theKey ; Lobby ExitLastCard 'FIND THE KEY FOR THIS CARD getname(theKey) = Off 'TAKE THE KEY FROM THE EMPLOYEE, NO KEY NO ACCESS Goto WAIT_FOR_ACCESS Line E If DEBUG then Print "Hit the error line" to Debug_STR If TS > 0 then Goto WAIT_FOR_ACCESS

Issue When trying to upgrade a database to version 1.5 or 1.6 the upgrade fails Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause There can be various reasons for the upgrade failing. At this moment there are two known issues: Issue with specific LonWorks devices such as the T-Stat T7300 Too complex or long list of email addresses in notification objects Resolution Solution for issue 1: Issue with specific LonWorks devices such as the T-Stat T7300 Contact Product Support and ask for hotfix 1.5.0.4801 Solution for issue 2: Too complex or long list of email addresses in notification objects Make a search for all email address objects searching for "EmailAddress" - You can import this search object to do it. Copy all rows to this Excel sheet Check the "Count" column - it counts the characters in the "Property value" column. There's no exact max character count as it also depends on complexity of the addresses, but a good indicator is if the count is over 270. In SmartStruxure, delete the content of the objects having more than 270 characters. Carry out the upgrade (if the upgrade fails, go back to step 3 and delete the content of all objects where the count is 260) After upgrading copy the property content from the Excel sheet back to SmartStruxure

Issue When schedules, reports, trend logs, loops or any calendars are loaded, Internet Explorer is rejecting the control and will not host it. IE will then throw a "Cannot Create .net Editor" error. Product Line Andover Continuum Environment .Net 4.51 Continuum webClient Server Internet Explorer Cause Microsoft has stopped allowing IE to host controls from .net 2.0 and 1.1 by default. Resolution In order for these controls you must do the following on all of your client machines: Note: Always make a copy of the registry on the machine before making any modifications Open regedit Update the .NetFramework key as follows: On an x86 Operating System Add a DWORD attribute with the name EnableIEHosting to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework Set the value to 1 On an x64 Operating System Add a DWORD attribute with the name EnableIEHosting to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework Set the value to 1 Reboot the computer At this point you should be able to start WebClient and run the .net editors without any problems. The following Microsoft Article discusses this issue: Application Compatibility in the .NET Framework.

Issue @TriggeredTimeStamp does not always report the last time an object transitioned to an off-normal state. Environment Alarms Substitution Codes Event Notifications. Cause Both the Normal and the Reset alarm states represent conditions where the alarmed object has assumed an acceptable value and is not in alarm Reset = The object has returned to a normal state but the return to normal notification has not been acknowledged. Normal = The object has returned to a normal state and the return to normal notification has been acknowledged. The TriggeredTimeStamp value is updated only when the object transitions from a Reset Alarm State to an Alarm Alarm state. The TriggeredTimeStamp value is not updated when the object transitions from an Alarm Alarm State to a Reset Alarm state. If an object goes into alarm and that alarm event is never again acknowleged, the Triggered Time Stamp will continue to reflect that initial alarm transition time regardless of how many times the object goes into and out of an alarm state. Resolution In order to get the Triggered Time Stamp to update, the notification must be acknowleged so that the alarm can return to a Normal state (rather than Alarm State = Reset) before it transitions to Alarm. 

Issue In the past there was no way to calibrate the space temperature from a STR-150 when used with a Xenta 121 FC/HP.  Environment STR-150 Xenta 104A Xenta 120 Xenta Programmables Cause Any calibration applied to the temperature of a STR-150 had to be done downstream of the stat in the controller. In the past when the STR-150 room stat was wired up to a Xenta 121 there was no way to calibrate the space temperature as the Xenta 121 FC/HP had no kind of Temp Offset in the controller. Resolution Starting with version 1.4 (released September 2013) of the STR-150, there is a calibration feature built into the stat. This feature allows the calibration to be applied before the temperature is sent down to the controller (Example: Xenta 121 controller). Below you can find out how to check the version number of the stat and how to perform the calibration. There is not a way to upgrade older versions of the STR-150 to 1.4 or greater. Checking the STR-150 version number The version number of the stat can be found as parameter P0. View version: Push the fan and bypass button simultaneously for 2 seconds to display P0. The version number will be displayed here. Using the STR-150 Calibration Feature Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0.   In P0, hold down the bypass button and push the fan button three times to enter configuration mode. Note: the wrench symbol is lit when the STR-150 is in configuration mode.   In Configuration Mode: Press the fan button repeatedly until you reach parameter F0. Note: The two digits farthest to the left on the display show the parameter, while the two digits farthest to the right show the value.   Use the increase or decrease button to adjust the value. The offset scale ranges from 0-99 which corresponds to -5.0 to +4.9 degrees. If the STR-150 is setup for degrees C, then the offset is exact. If the STR-150 is setup for degrees F, then the offset is recalculated to a corresponding value.   Exit Configuration Mode: Push the fan and bypass button simultaneously for 2 seconds or allow the idle timeout to exit configuration mode on its own.

Issue An offline edit in PCS deploys successfully. When viewed in Workstation, the Automation Server is online, but all b3s are offline. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.50 PCS AS 1.5 BACnet interface Cause The b3s have a BACnet Device ID which is different from that assigned to b3s in PCS. The BACnet device ID can not be modified in PCS after it has been assigned. Resolution It is best to modify the BACnet Device ID in Continuum: Use a BCX4040. Connect with b3 devices one by one or together Bring b3s online in Continuum Workstation Modify the BACnet Device ID for each b3 to the BACnet Device ID assigned in PCS Go back to SBO Workstation. b3s should be online.

Issue Trend log values from two or more M-bus meters under a Xenta Server are intermittently mixed up, also when viewing a trend log page in the Xenta Server's web interface. Values from meter 1 are (sometimes) logged in meter 2's trend log and/or vice versa. Environment Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 M-bus meter Cause When secondary addressing is used for the meters, there is an extra telegram sent from the Xenta Server before asking for the actual values/data. The M-bus meters then replies to this telegram so that the Xenta Server knows which secondary address belongs to which meter. In some cases (only seen with a few meters) these addresses seems to be intermittently mixed up and this will cause the issue described above.  Resolution Use primary addressing for the M-bus meters.

Issue Replaced a Niagara R2 UNC with a Jace-645 embedded with R2.  LON communications was stable at first but now it is intermittent.  Environment Niagara G3 - AX version 3.6.47 or higher Niagara R2 version 535 Cause The intermittent LON communications issue was identified and a supporting jar file in R2-535 needs to be upgraded. Resolution Replace the lonworks jar file with this updated version:   lonworks-2.301.535c

Issue Setting up Visual Verification to track who has gained access to a door using Access Expert Product Line Access Expert Environment Access Expert v3 Cause Verification of access is a common feature request in access control integrations. The following steps show how to enable and access this feature within the Access Expert v3 product. Resolution Open and connect to the instance with the required credentials Select the Access Control Tab and click on the Visual Verification button Click on the Assign Reader button to Add the respective readers and click OK The Visual Verification Window opens up with the readers that were selected from the previous step on the right side of the screen. Select the necessary readers that will be used for the verification.                    Once someone scans a card on any of the selected readers, their saved image will then be displayed    *Note* If this Window is closed the configuration for Visual Verification will be lost and will need to be recreated