Building Automation Knowledge Base

Issue How long will a UNC-520 hold the date & time if AC power and the backup battery are disconnected? How long will a UNC-520 hold the date & time if AC power is disconnected but the backup battery remains connected? Environment UNC-520 Universal Network Controller Cause UNC-520 provide real-time clock and need to maintain the information during power failures. Resolution Approximately one hour. This is done by a 1200 µF 10 Vdc capacitor that backs up the real-time clock chip. Over one month.

Issue ZBuilder will not open on certain commissioned Xenta 121s in Lonmaker. It will open on others in the same network. Environment ZBuilder LonMaker Cause Incorrect or corrupted configuration parameters prevent the ZBuilder plug-in from opening on specific Xenta 121s. Resolution Right-click on the device in LonMaker and choose Browse Take a screen capture of the various settings that will need to be re-entered Re-commission the Xenta 121 controller with default values (this will erase any configurations that have been made) ZBuilder will now work correctly. Re-enter any previously configured parameters

Issue What is the switching level resistance for a digital input to be seen as 1 in a Xenta 411/412 I/O modules Environment Xenta 411/12 Cause Integrating third party devices with Xenta 411/412 I/O modules. Resolution The switching level resistance for a digital input to be seen as 1 in a Xenta 411/12 is around 2000ohm

Issue Can individual terminals be purchased for the MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx controller? Environment MNL controllers; MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx Cause Replacement parts ... Resolution The individual terminals are not setup in the system for purchase.  The MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx controller base assemblies are available for purchase under the following part numbers (MNL-BASE-100, MNL-BASE-150, MNL-BASE-200).

Issue Requested Clients window shows a remote client as being off-line. Environment Sigma Clients Remote Requested Clients Off-line Cause Sigma defect 3174 - The remote client status as shown in the "Registered Clients" window, may be incorrect. This is caused by the remote client being started before the local client.. Resolution This issue has been corrected in Sigma release 4.05 SEB, upgrade the site to this release or later. If an upgrade is not possible then Shut down Sigma and re-start the local client first.

Issue Users who clean-dist or factory restore JACE-8000 to Niagara version 4.1 risk losing the serial ports.   Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Cause Due to an old defect (fixed in Niagara 4.2 update 2; 4.2.36.38), a programmable device that controls the serial port may be left in an erased state during firmware programming. If this happens, serial ports (COM ports) will be missing when viewing the Serial Port Service under Platform Services in a station. This continues to be an issue for customers who routinely clean-dist or factory reset to Niagara 4.1 on upgrade scenarios. It is not necessary to clean-dist or factory reset when upgrading JACE-8000. If you are advised to do so, it is recommended that you use the 4.9u1 clean dist rather than the 4.1 version one, to avoid being affected by the old defect.  Resolution When the JACE-8000 is loaded with Niagara 4.14u2 (or newer) the issue will be automatically detected and fixed on boot. However, when a serial expansion module has been erased, the software cannot distinguish between an RS-232 expansion module versus an RS-485 expansion module. The following messaging will appear in serial shell (and system logs) when the JACE is booting (it will continue booting):   Starting USB-0 and USB-1 Host controllers... Started USB-0 and USB-1 Host controllers get_ctrlperms: ctrlperms set to 644 Check for usb firmware updates Re-creating firmware info file in /etc/usb ERROR: Expansion module info file /etc/usb/350130901TF9S81 is empty, cannot reprogram or start serial ports        1) To populate the info file with path to appropriate firmware, execute one of following at console command line:               For RS-485 expansion module: echo "/sys/images/usb/vid03eb/pid2425/Tridium485-2_r01" > /etc/usb/350130901TF9S81               For RS-232 expansion module: echo "/sys/images/usb/vid03eb/pid2404/Tridium232_r01" > /etc/usb/350130901TF9S81        2) Reboot to reprogram Check for usb firmware updates done   To fix the issue, download and start PuTTY. In PuTTY Configuration, select the radio button labeled Serial under Connection type. In the text field under Serial line enter COM3 (or whatever the port number is) and enter 115200 in the text field under Speed. Press the Open button to connect. You will need the same VCP driver that is noted in Preparing for new JACE commissioning  and JACE-8000 Backup and Restore Guide. Sign in to the JACE serial shell. At the prompt type 'sh' to exit the menu and enter serial shell prompt (shell prompt is $ dollar sign). Copy the correct command from the serial shell instructions. To copy with PuTTY, click and drag over the text. When you lift the mouse button, the text will be in the clipboard. To paste the text, you simply right-click. In the instructions above, 350130901TF9S81 is serial number of a programmable device that controls the serial port. Your serial number will be different. But if that was your serial number, and the erased device was an RS-485 expansion module, then the command to enter would be:    echo "/sys/images/usb/vid03eb/pid2425/Tridium485-2_r01" > /etc/usb/350130901TF9S81   And if it was an RS-232 expansion, then the command to enter would be:    echo "/sys/images/usb/vid03eb/pid2404/Tridium232_r01" > /etc/usb/350130901TF9S81   The file name and path may change in newer versions of Niagara. Therefore, copy from the instructions given in the serial shell output (do not copy the command from this Knowledge Base Article). Press the enter key after the command has been pasted correctly. Then send shutdown to warm-boot the JACE-8000, or just cycle power.  Observe the following output on the next boot:   Starting USB-0 and USB-1 Host controllers... Started USB-0 and USB-1 Host controllers get_ctrlperms: ctrlperms set to 644 Check for usb firmware updates Reprogramming usb device: 1.2 350130901TF9S81... loaded 350130901TF9S81 with /sys/images/usb/vid03eb/pid2404/Tridium232-1_r07.bin Reprogramming usb device done: 1.2 350130901TF9S81 Expansion boards have been reprogrammed - rebooting... exiting usbinit, shutdown requested   The JACE will boot one more time, and then it will operate normally.  Please refere to this additonal article for more help.   Jace 8000 Serial Port Issues 

Issue Receive API error codes while trying to connect my API to BDP. Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Receive the following Error codes: 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 500 Internal Server Error Resolution 400 Bad Request The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing) 401 Unauthorized Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response 403 Forbidden The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server 404 Not Found The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web 500 Internal Server Error The server has encountered a situation it does not know how to handle   Successful responses 200 OK The request succeeded. The result meaning of "success" depends on the HTTP method: GET: The resource has been fetched and transmitted in the message body HEAD: The representation headers are included in the response without any message body PUT or POST: The resource describing the result of the action is transmitted in the message body TRACE: The message body contains the request message as received by the server 201 Created The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests. 202 Accepted The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.

Issue EBO acts as a BACnet server and a BACnet client send SubscribeCOVProperty to get value updates of specific property of a BACnet object, ex. present value, but EBO respond with "NOT_COV_PROPERTY".   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Specified property does not support COV notifications. Resolution EBO only supports SubscribeCOVProperty (DS-COVP-B) for the following properties and object types: Status_Flags: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop, Trend Log Event_State, Reliability, Out_Of_Service: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop When a client attempts to use SubscribeCOVProperty for another property not listed above, the appropriate response is 'Not COV Property', as specified in BACnet standard. When getting this response from EBO, the client is expected to automatically use another method to acquire the property value (either via COV subscription or polling). If the client is attempting to read Present_Value, then using SubscribeCOV would be the preferred mechanism.

Issue How can thousands of unacknowledged alarms and exceptions be deleted quickly in SIGNAL? Environment SIGNAL (all versions) Cause Months of unacknowledged alarms and exceptions were allowed to accumulate. Resolution The files containing all the alarms and exceptions are located in the SIGNAL\ALARM and SIGNAL\EXCEPT folders respectively. Shutdown SIGNAL (all programs).  In the ALARM folder, delete the alarm_a.dat, alarm_u.dat, and alarm_l.num files. In the EXCEPT folder, delete the excep_a.dat, except_u.dat, and excep_l.num files. Reboot the computer.

Issue When trying to browse for Areas to assign to the Area Inside Door and Area Outside Door fields in Door records, not all Areas are shown or available to be selected. Product Line EcoStruxure Security Expert Environment Security Expert Cause The Programming Mode selector is set to "Local" which is the default value. This will only show objects that are already attached to the controller this record resides in.   Programming Mode Resolution Change the Programming Mode to "Global" which will now show all Area records, including those unassigned or assigned to other controllers.   Programming Mode Global

Issue What is the b2 and i2 Controller Object Format property used for? Product Line EcoStruxure Building Operation Environment Continuum Conversion i2 Controller objects b3 controller objects Cause i2 and b3 Controller objects include a a Format field for objects created using the Continuum Conversion tool. What is this used for and how does the value effect the operation?     Resolution These Format values are propagated through the Continuum Conversion Tool for reference only and have no impact on operation in EBO. The values cannot be modified. In EBO there are two ways to configure numeric display formats. -In WorkStation property pane and watch window, the number of decimals displayed to the right of the decimal point is inherited from the WorkStation PC's regional settings. This setting applies to all values displayed in WorkStation except for values in graphics. -In graphics, the number decimals displayed to the right of the decimal point is configured value-by-value in the Graphics Editor.   The format value is not stored in an EBO export and if objects are manually created, then standard formats are used for the type of object created .

Issue Since the ZS106 is obsolete, a replacement is requested. Environment ZS106 - 007309220 STR106 - 004600500 Cause Replacement for obsolete product. Resolution The STR106 wall module, part no 004600500, is replacing the obsolete zone sensor ZS106.

Issue What is the Analog to Digital Output resolution of the MNB controllers? Environment MNB Controllers Cause Analog to Digital conversion resolution. Resolution The MNB BACnet controllers have 12-bit resolution on the inputs and 8-bit resolution on the analog outputs.

Issue When ordering an MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx controller, is the controller base included? Environment MNL controllers; MNL-10Rxx, MNL-15Rxx, or MNL-20Rxx Cause The web pages on iPortal do not described whether or not the base is included. Resolution The base is included when ordering any of these MNL controllers.

Issue Slide stat or temperature offset values are incorrect when using a ETR-1xx sensor with Xenta 100 or Xenta programmable controllers. Environment ETR-1xx Xenta 100 Xenta 280, 300, 4xx Cause Similar to the STR-1xx line of sensors, there is a jumper that must be set depending on the controller the sensors is being connected to. This jumper removes or adds an extra resistor to the temperature offset value. Resolution Set the Jumper position according to the type of controller the sensor is connected to: Controller Jumper Position Xenta 100 J1 Xenta Programmable J2

Issue What versions of Sigma does RAM Remote Alarm Manager work with? Environment Sigma RAM Cause RAM does not work with S-150 or S-400. Resolution RAM Remote Alarm Manager will only work with S-FULL. The site will need to be upgraded with S-UPG to the full version. 

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 How to combine multiple Continuum DBs into one DB Product Line Andover Continuum Environment Continuum Cyberstation Cause Multiple Continuum site databases need to be combined into a single site database Resolution Guideline for combining Multiple sites to one Database Executing this procedure requires a technician who thoroughly understands Continuum and how it works with SQL Server. This procedure does not encompass BACnet controllers. There is a multitude of decisions related to efficiencies and site preferences that are not documented here. The following procedure is intended for use as a guideline for combining multiple databases. This work must be done offline on a development database and validated on a test bench before Note:Before proceeding with this procedure you must do the following. Backup the Continuum database in SQL. Backup all the files and folder structure under New Graphic Files. Note that these files may be on the SQL Server or elsewhere on a mapped drive. Back all Cyberstation Profiles. Steps 1 – 11 must be done before any of the site exports are done. Preparation All sites must have the same revision software and CX firmware. NO EXCEPTIONS! Make sure that all the Alarm Enrollments and Event Notifications have unique names between all sites as these will wind up together in a single database. Make sure that all the Graphics in the Root directory have unique names between all sites. Make sure each Schedules in the Root directory has a unique name across all sites. Make sure each Custom ListViews in the Root directory has a unique name across all sites. Make sure each Groups in the Root directory has a unique name across all sites. Make sure each Reports in the Root directory has a unique name across all sites. Once steps 1-5 are completed, export each class in the root individually. Import files from step 6 into the new site The Local Site name on all the sites that will be combined must be named LocalSite. All workstations must have unique names and ACC IDs between the sites. All CX, ACX and BCX controllers must have unique names and ACC IDs between the sites. Note: The safest way to do steps 9 & 10 is to create a new controller in offline mode with the changed ID, then drag and drop copy from the original controller to the new controller. Panels, reports, and programs then must be edited to bind to the new controller. Another way to merge the panel, reports, and programs that are in the root is to copy all the panels, programs, and reports to their corresponding controller then export the controller. Doing this will keep all the bindings linked. Then once the controller is imported into the merged database they can be copied back up to the root. All Commports on all controllers and workstations must be named Comm1, Comm2, etc… Each site must have the default “ACC” user and password. All graphic files (.pin) under the New Graphic Files folder must have unique names between the sites. Merging the databases Install a standard multi-user Continuum system being sure to size the database big enough to accept all the other databases combined into one database.  After a clean installation is done, shut down the new workstation and the SQL server. Copy the empty database files to an area where they won’t get corrupted. Do a complete site export from each of the sites that will be combined. Back up all the Graphic files (.Pin) files from the site so that they can be transferred to the new server. Copy all the backed up Graphic files (.Pin) from each site onto a New Graphics Files folder in the location of choice. Note these files can reside on the SQL server or elsewhere on a mapped drive. Import each of the site text exports from the old systems into the new system. After each import check to make sure that each import went cleanly. Check all the Graphics, Programs, Alarm Enrollments, and Event Notifications to make sure that all the links were made during the import process.

Issue Can Satchsize the valve sizing software be used with Windows 7? Environment Valve sizing Satchsize Cause Customer wishes to use Satchsize on Windows 7. Resolution Satchsize is no longer available and is not supported with Windows 7, but a new program is available. TAC Valve 1.8 UK can be downloaded from the Buildings Business Extranet. Once installed please use the help files installed with the program.

Issue Sometimes the availability count for license features are displayed as double the actual available count for Entitlements. The problem has no functional effect on the system other than that the visual indication of the feature count is wrong. Issue seen in Entitlement View - Features inside a License Product are doubled. Issue seen in Server View. -The issue can be seen temporarily during activation on the server line. -The number of features inside the License Products available for activation under the server are doubled permanently. Server line view after activation. - After the license product has been activated the features on the server are shown correctly. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Secure Boot Building Operation Automation Server Bundled (AS-B) Scalable Cause AS-P Classic and AS-B Classic licenses are NOT affected. None of the Windows licenses are affected.   EBO releases affected: All EBO versions up to and including 4.0.3. The EBO systems that are already running licenses are Not affected. Customers that for any reason reinstall an Entitlement in DA will be affected by the issue. EBO 5.0.1 Resolution This issue is planed to be resolved in the following EBO versions: EBO 4.0.4 EBO 5.0.2

Issue Importing Security Expert controllers' serial numbers will break the import process and result in only creating default templates for the controllers. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Data Sync Service Cause Security Expert controllers' serial numbers are displayed in hexadecimal. However, in the SQL database they are  stored as decimal values. So the Data Sync Service is expecting a decimal integer and is instead receiving a string.  Resolution Convert the serial numbers in the .CSV import file from hexadecimal to decimal. This can be done in excel using the  "HEX2DEC" function. E.g. if the controller serial number is "ABCDEF12", it must be converted to decimal value "2882400018" before importing to Security Expert.