Building Automation Knowledge Base

Issue Does the MPM have an internal power source to maintain the clock during an extended loss of power? Environment MPM Cause Clock maintenance during a loss of power Resolution The MPM has a Lithium battery that will keep the system clock online/accurate during a power loss. The battery life is very high, however leaving the MPM unplugged for many months will eventually wear out the battery. Units manufactured after week 13 2016 have a super capacitor rather than a battery. The capacitor has a charge time of approximately 5 minutes after which it will provide backup for the RTC for approx. 48 hours

Issue A method of offline database engineering is needed for SmartStruxure.  Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Project Configuration Server (PCS) Cause System integrator wants to engineering expansions and new automation to the site offline. What is the procedure if the client already has the ES and AS devices onsite, but wants to engineer offsite? If not can we only add one AS per project then restore / deploy just the AS and how is point referencing managed on bindings to the original site server? Resolution Beginning with the release 1.5 version of Project Configuration Server(PCS) is a 'deploy once' version, meaning that it allows you to make the first configuration offline. It is a full deployment meaning it may only be the ES or AS or the ES with AS connected. There are no partial deployments with bindings intact with existing servers. For deployment to include bindings between the ES and AS or other devices, they must be added to the initial deployment, which will overwrite existing configuration. Note: the 64 AS limit is a performance issue. 64 fully loaded AS in a project takes a long time to open. Once a server in the PCS project is deployed on site, you cannot deploy it again without manually erasing the database in the online server using the Device Administrator or uninstall and re-install the Enterprise server. Consider the following scenario where an office wishes to use the PCS on a project with staged installation and an ES with 15 AS: Create the ES and all 15 AS in my project. You may not have the project’s communication information because none of the final IP addresses are available. So put them in with 192.168.1.x Configure all of what is needed in 5 of the AS (AS1 – AS5). Configure all of the IO and other objects in another 5 AS (AS6 – AS10) Do nothing with the last 5 AS (AS11-AS15). Create some read references in some of my programs in AS1-AS5 that are referencing objects from AS6 – AS15. Create extended trends and alarms categories at the ES. Create alarms in AS1 - AS5 that use the alarm categories. Go to the site and deploy AS 1 to AS5 (after modifying the communication parameters for those 5 so that you can bring them on line.) The alarm categories will be deployed to the AS in spite of the fact that the PCS would have had them configured as lead and shadows from the ES, which was not deployed. However, there would likely be an offline alarm generated because there was no ES and there might also be a lead/shadow alarm. The alarms will be correctly configured, however, and operational. The references to the objects from AS6 – AS15 will appear as unresolved in the AS1-AS5 reference managers. Go back to the office and finish everything needed in AS6 – AS10 Create graphics at the ES referencing objects from all 15 AS. Create trend charts showing log data from all AS. Create users, domains, workspaces, etc. Go back to the site and adjust the communication parameters for all the remaining 10 AS and for the ES Deploy AS6 - AS10 and the ES. Initially, the AS1-AS5 have empty/wrong communication settings to the ES. It requires a manual “Repair Com-settings” from the user logged on to ES (at the site). When the Com-settings are ok, then the bindings from AS1- AS5 to AS6-AS10 will be resolved after a few minutes. When the Communication settings in AS1-AS5 for the ES are correct, the synchronization for lead/shadow relationships starts updating the alarm categories that we discussed in step 8a. The graphics in the ES will have resolved bindings for objects from AS1 – AS10, but unresolved bindings from AS11-AS15. In fact, they will be resolved to AS1-AS5 even if you haven't corrected the Com-settings in AS1-AS5. The ES knows all the AS. Go back to the office and finish up my work on AS11-AS15. Part of this process is the creation of programs that reference objects in AS1 – AS10. Go to the site and deploy AS11 – AS15. All of the read references to objects from AS1 – AS10 will automatically fix up once the Com-settings for the ES in AS11-AS15 are correct. It might, however,  take a few minutes. All of the references in the ES graphics for AS will be operational.   Further information can be found on Building Operation WebHelp.

Issue When clicking on the Right Click Menu for I/NET Converted TGML Graphic on remote SmartStruxure Workstation, nothing happens even though I/NET has already been installed on this computer and I/O server has been registered as service. Environment SmartStruxure I/NET Seven 2.44a through to 2.48 Remote Workstation Cause On a 32 bit OS and a 64 bit OS machine, the I/NET Converted TGML Graphic are different because I/NET default software installation path is different: 32 bit OS: C:\Program Files\INET Seven\ 64 bit OS: C:\Program Files (x86) \INET Seven\ Since the Right Click Menu calls the I/NET program, if the graphic is converted on 64 bit OS machine on the Server, it will not work on the Client machine with 32 bit OS. And vice versa. Resolution NOTE: This right click menu option will only function when the graphics page is located on an Enterprise Server where a copy of I/NET is installed on the local Workstation. This feature provides access to graphic functions run using the installed I/NET software so will not work when that software is not locally available. It is therefore not available when using WebStation or when viewing graphics located within a SmartX Server. From I/NET version 2.49, this right click menu option will be removed from this editor and NO LONGER be available. there are mixed versions of 32 bit OS and 64 bit OS between ES and Remote Workstation, the I/NET graphics need to be converted on 64 bit OS machine. And then follow the steps below: 1. Manually create C:\Program Files (x86)\INET Seven\ folder on 32 bit OS machine. 2. Uninstall I/NET and reinstall it under the folder created instead of default one. Then the Right Click Menu should work now.

Issue PE Script editor crashes when a WebService is declared in a script program in 1.5 Environment Workstation Cause Product defect. Resolution Ask PSS for SE.SBO.WS-1.5.0.1703-Hotfix

Issue Since the IP address scheme for the site had been changed, trying to start a Webclient session results in 400 bad request error in the browser session. There are no issues when accessing Webclient on the Webserver. Environment WebClient IIS Cause Default Website in IIS is configured with the old IP address. Resolution Set the new IP address in the Properties of the Default Website. Then stop and restart IIS.

Issue In SmartStruxure version 1.5, when editing a graphic or program while having the bindings view open adding, deleting or renaming binds, the bindings view doesn't update with the changes when the change is saved. Manually refreshing the view doesn't update the view either. You need to close the view and open it again. Environment SmartStruxure version 1.5 Workstation Cause This is a bug already reported to Product Support Resolution For the time being there's no fix for this. You need to close and reopen the bindings view after having made changes to the graphic or program.

Issue JACE-645-R2 will not learn BACnet devices on its MSTP trunk and is spewing out the following message in the Application Director. devctl rx frame failed: No error java.lang.RuntimeException: mstp rcv failed at tridium.nre.qnx.mstp.QnxMstpDriver.rcvFrameJNI(Native Method) at tridium.nre.qnx.mstp.QnxMstpDriver.access$0(QnxMstpDriver.java) at tridium.nre.qnx.mstp.QnxMstpDriver$MstpTrunkListener.run(QnxMstpDriver.java:287) at java.lang.Thread.run(Unknown Source) Environment G3 version 3.8.37 Cause Issue with the platform drivers in G3 (3.8.37) that interface with R2. Resolution Install a clean distribution using 3.6.47 and commission with 3.6.406.

Issue ALARM blocks can be added to an SBO Function Block application, but it is not possible to set delay, priority or alarm text parameters from within the Function Block Editor.  Also, the preceding block is assigned an auto-generated name and public status, if it did not already have a name. Environment SBO 1.5.0 and earlier. Function Block Editor Cause When an alarm block is added to a Function Block program an alarm object is automatically created in the SBO System Tree, below the FB program object.  By default, the alarm object is not visible until the filter 'Show non-presentation objects' is set The public block preceding the alarm block is required so that the alarm object in the System Tree can have a Monitored Variable reference.  The 'Function Block Editor and Menta Editor Difference Guide 04-15010-01' states that 'The function block programs still need the ALARM blocks, but the blocks only serve as inputs and outputs to the alarm functions..'.  This is misleading as you do not need to explicitly create an external alarm object - all the usual alarm properties are available in the automatically generated alarm object, once it is made visible. Resolution Set the System Tree filter to 'Show non-presentation objects'.  Then set the required alarm properties in the displayed alarm object below the FB program object.

Issue Not able to discover the MNB controllers on the MSTP trunk of an AS. However, all MNB controllers on the same AS trunk are discovered in WorkPlace Tech Commissioning Tool. Environment SmartStruxure, AS Cause The negative lead of the MS/TP AS network was shorted to ground. Resolution Examine all MS/TP wiring and correct any grounding issue.

Issue Can other fonts be added to EpiDesigner EpiBuilder? Product Line Andover Continuum Environment EpiBuilder EpiDesigner Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause The method to add fonts to EpiDesigner is needed to use alternate fonts. Resolution Download or install the font that is needed to a folder on Windows Unzip if necessary and then drag and drop the font file(s) into the windows fonts folder and they should automatically install. Here are some Windows instructions for installing manually. https://support.microsoft.com/en-in/help/314960/how-to-install-or-remove-a-font-in-windows After installing the fonts you can open a layout in EpiDesigner and select the newly added font.

Issue How do the Wake Up Time and Redundant Transmission settings affect the operation of the SED-THSU5045 thermostat? Environment SED-THSU5045 Enocean Cause The function of the Wake-Up interval and the Redundant Transmission switches is not described in the documentation that comes with the sensor.   Resolution DIP Switch 1 and 2 control the Wake-up Interval (in seconds) OFF OFF No cycling wake up ON OFF 1 OFF ON 10 ON ON 100 DIP Switch 2 and 3 control the Redundant Transmissions (in frequency of tx) OFF OFF Every wake up ON OFF 7 to 14 wake ups OFF ON 70 to 140 wake ups ON ON Never   The idea is that the stat will wake up when the wake-up interval is elapsed and verify if the temperature has changed by more than approximately 1°F. If it did, it will send a transmission, if not it will go back to sleep until the next interval. The second setting (redundant transmission) will govern how often the stat will send a value, even if the temperature has not changed (as some kind of ping or keepalive).

Issue Integrated NPR Dial on a Xenta 527 (Web) failed to connect Environment I/Net Site with Integrated NPR Dial Cause There is a current issue with Xenta 527 (Web) and the Firmware load of 5.1.9-15 at the present time. This release will not support the Modem connection. This issue has been given to Engineering for Repair. Resolution The "Work Around" is to go back a Firmware release. For the time being, until the 5.1.9-15 is fixed, load 5.1.8-10 in the Xenta 527 (Web) and the Modem will work in this load.

Issue Configuring a Smart Sensor in a B3 controller in StruxureWare Building Operation using a simple script program to display temperature. The temperature does not display in the Smart Sensor LCD. Environment Automation Server with B3 controllers Cause SmartStruxure 1.4 attaches a _AV, _BI, etc. to the BACnet name Resolution Remove the _AV, _BI, etc. from the LCDDisplay BACnet name Download the controller again The display functions as suggested

Issue When you drag and drop and Xenta programmable controller in to a new folder it remains in the existing Xenta group. Environment SmartStruxure 1.5 Cause The drag and drop feature is not designed to make new Xenta Group bindings. The controller will be moved but remain in the existing Xenta Group membership. Resolution Two options exist to move a controller into a different Xenta Group  Make a new Xenta Group, save the existing Menta application out of the database and then delete the device.  Add a new folder then add the Xenta device into that folder and select the previously saved Menta file.  A new Xenta Group will now be created .  Select the controller you wish to move, using right mouse click, select Copy. In the new location use the right mouse click Paste Special command.  When finished delete the original controller.

Issue What type of sensor element is used in the STR300? Environment STR300 Cause The HVAC European+Sensors+Catalogue.pdf on the Extranet, as well as the datasheet for the STR300 Series says that the sensor element is PT100 Class B. Resolution The actual sensor element for the STR300 that are made today is NTC Thermistor 10 kOhm. The output from the STR300 is 4-20 mA.   The documentation will be updated shortly.

Issue I have created a project in the Project Configuration Server (PCS) on my computer. Now I would like to move this to the customers computer how do I do that?  Environment StruxureWare Building Operation 1.5 and later versions. Cause You move a project database from an off-site computer to a customer site computer, when a project cannot be deployed from an off-site computer. Resolution On the source computer, in WorkStation for Projects, ensure that the project is backed up. For more information, see Checking the Backup Status of a Server . Close WorkStation for Projects. Wait 5 minutes to ensure that the project is closed. A project closes 5 minutes after the last user has logged off.    When multiple users are working with the Project Configuration Server, make sure a stop of the Project Configuration Server Windows service does not negatively affect your projects before closing.   In Software Administrator, in the Project Configuration Server tab, copy the path of the Projects folder. In Windows Explorer, in the Address box, paste the path of the Projects folder. Move the individual project folder to a USB drive or to another appropriate media. On the target computer, in Software Administrator, in the Project Configuration Server tab, copy the path of the Projects folder. In Windows Explorer, in the Address box, paste the path of the Projects folder. Move the individual project folder from the USB drive to the Projects folder. The project can now be opened in WorkStation for Projects on the target computer Make sure that the versions on both PCS servers is the same.

Issue A new license file was provided for a UNC so that it could communicate with other UNCs at a jobsite.  The UNC was a spare unit being used in the office for testing.  When trying to install the new license with Workplace Pro, a pop-up error appears immediately indicating:  Unable to install license. Environment UNC (all versions and models) Cause Re-licensing a test UNC Resolution Use the summary tab in admin tool to ensure there is enough free file space.  If not, open the remote library and delete unnecessary files. The free file space number will increment after a few seconds (no need for a reboot). Now, install the new license.

Issue How to determine which MNL controllers (profile and version number) are integrated to a Niagara R2 or G3 station. Environment Niagara R2 lonSiebe jar file Cause Quick reference Resolution Use the LonWorks Device Manager and cross-reference the listed MNL controllers to the table below: siebe                         MNLRF103                             SIEBE                          80:0:16:50:14:4:4:1      siebe                         MNLRF2                                  SIEBE                          80:0:16:50:14:4:4:2  (version 2)    siebe                         MNLRF3                                  SIEBE                           80:0:16:50:14:4:4:3   (version 3) siebe                         MNLRH103                             SIEBE                           80:0:16:50:33:4:4:1      siebe                         MNLRH2                                  SIEBE                           80:0:16:50:33:4:4:2     (version 2) siebe                         MNLRH3                                  SIEBE                           80:0:16:50:33:4:4:3      (version 3) siebe                         MNLRR103                             SIEBE                           80:0:16:50:1e:4:4:1      siebe                         MNLRR2                                  SIEBE                           80:0:16:50:1e:4:4:2    (version 2)  siebe                         MNLRR3                                  SIEBE                           80:0:16:50:1e:4:4:3      (version 3) siebe                         MNLRS1                                  SIEBE                           80:0:16:50:1e:4:4:10     (satellite 1) siebe                         MNLRS2                                  SIEBE                           80:0:16:50:1e:4:4:11     (satellite 2) siebe                         MNLRS3                                  SIEBE                           80:0:16:50:1e:4:4:12     (satellite 3) siebe                         MNLRS4                                  SIEBE                           80:0:16:50:1e:4:4:13     (satellite 4) siebe                         MNLRV2                                  SIEBE                           80:0:16:50:a:4:4:9       (version 2) siebe                         MNLRV3                                  SIEBE                           80:0:16:50:a:4:4:a       (version 3) siebe                         MNOTPVA3                             SIEBE                           80:0:16:50:a:4:4:8       siebe                         SiebePEC                               SIEBE                           80:0:16:50:1e:4:4:0      

Issue Sigma 4.08 - Sigma server does not start, and an error message may be produced. Environment Sigma 4.08 Build 3.46.57 SigmsSvr.exe Cause Upgraded to Sigma 4.08 from Sigma 4.04 and the Sigma service SigmaSvr.exe would not run. Resolution This issue is caused by a valid licensing method not being available on the Sigma server. Sigma 4.08 (Build 3.46.57) can be licensed by one of the following methods; A valid Sigma dongle. A copy of StruxureWare Building Operation license Administrator software and valid license has been installed.

Issue Does the MNB-1000-15 Remote I/O Module supports pulse inputs? Environment I/A Series MNB-1000-15 Remote I/O Module Cause How to use the MNB-1000-15 remote I/O module universal inputs to read pulse inputs. Resolution Standard pulse input is supported on the MNB-1000-15 universal inputs (UI1 to UI6).  Minimum Rate 1 pulse per 4 minutes   Maximum Rate 1 pulse per second Minimum Rate 1 pulse per 4 minutes. Maximum Rate 1 pulse per second.