Building Automation Knowledge Base

Issue A door configured for Entry/Exit reader gets error message "cannot reload remote attribute. Error: null"  & " Cannot set remote infinity object" when reloading the door object to the controller. Environment CX9900, CX9940 and CX9680 AC1, AC1A and AC1Plus Cause Different IOU module (AC1, AC1A and AC1Plus) cannot be used to configure for entry/exit readers for a door. Resolution A door with entry/exit readers should use the same type of IOU module ( AC1 , AC1A or AC1Plus ) for entry reader and exit reader.

Issue Which actuator is suitable to replace the Forta M750 actuator? Environment Forta M750 Forta M800 Cause Since the Forta M750 is no longer available, it needs to be replaced by a suitable actuator. Resolution The Forta M750 should be replaced by the Forta M800 actuator.

Issue Need to know the rules and limitations of Continuum login user's password.  Environment Continuum Cyberstation Cause Need to know the rules and limitations of setting the password when creating Continuum login users. Resolution Continuum login passwords are used to secure the User account. A password is a case-sensitive character string that may contain letters, numbers, symbols, and spaces. Control characters, Alt-modified characters, and function keys are not allowed. Passwords can be a maximum of 16 characters. Note: When logging onto a Continuum workstation, the user must enter the alias of the User object that has been created for him (not Full Name) and a password. The alias is created when you name an object in the New dialog box. If the user fails to provide the correct alias/password combination, Continuum denies access.

Issue Get "invalid address" when reading values from a Modbus device in Vista. Environment Vista 5.1.X XBuilder Modbus Xenta 5xx / 7xx / 9xx Cause This problem can be caused by the Modbus device name and the Modbus interface name having the same name in the XBuilder project. Resolution If the Modbus device and interface have the same name change one of them to be different from the other.

Issue Digital Sentry Control Point  and Cyberstation have conflicts with both pieces of software on the same PC. Environment Cyberstation Digital Sentry Control Point Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The Cyberstation Video Integration and Digital Sentry Control Point use the same API to communicate and could cause issues. Resolution This configuration is not officially supported or tested, although we have reports that say people are doing it in the field. The reason it is not supported is because they both depend on the same DSConnex API. Installing both may introduce Windows registry issues. (causing issues with whichever application was first installed). From the field Without Control Point installed controllers were online. If only control point is installed they can view Video once Continuum is installed they can no longer view Video. Both program work independently of each other but not together, last one installed works. The configuration of having Digital Sentry Control Point and Cyberstation Video Integration installed on the same PC is not supported. The reason that it is not supported is because both products use the same API (Application Programming Interface) files in order to display video. There could also be Windows registry issues particularly if different versions of the API files are getting installed by each application.   An example from the field If only Control Point is installed the site could view video normally. Once Continuum was installed, video will no longer display in Control Point. Both programs work independently of each other, however, typically the last program that gets installed is the one that will work and the first program installed gets broken, so that video will not display.

Issue There is a limit of allowed rehosts per year. If this limit is reached and a rehost is attempted, the following error message is given: "The rehost of the fulfillment is denied by the rehost policy because max rehosts exceeded " Environment Vista 5.x Cause If the rehost is motivated and necessary, the policy can be overridden by PSS. If required, please contact PSS Malmö. Resolution Manually override rehost policy by using Administrative rights on the Licensing web.

Issue Which Continuum controllers support a terminal RS-232 interface using a terminal emulation application such as Hyper Terminal? Product Line Andover Continuum Environment HyperTerminal CX9900 CX9940 CX9200 CX9400 Cause Documentation Resolution ONLY the following range of controllers support a terminal interface. CX99xx CX92xx CX94xx Please consult Logging into CX9900 controller using HyperTerminal for additional information.

Issue When VisiSat 2.1 Build 185 on some Windows XP pro / Visio 2003 computers the following error is displayed. Internal error 0x86DB08A9 VisiSat 2.1 Build 185 Cannot find VisiSat "CustomiseUI" add-on to Visio. Some or all the files required by VisiSat are missing. You may need to re-install Visio and/or VisiSat to clear the problem. Environment CustomiseUI Add on to Microsoft Visio 2003 VisiSat 2.1 Build 185 Cause Visio 2003 does not recognise or register VisiSat 2.1 Build 185 installation CustomiseUI Resolution Open Visio 2003 (Not VisiSat) On the menu bar, under tools select options.   Select the advance tab.   Select file paths.   Delete all entries. Then select OK   Select OK.   OK the next window Visio 2003 should now close.   Run up VisiSat VisiSat should run up OK now.   If you close VisiSat and open Visio 2003 the paths should now show.   VisiSat should open correctly now. Option: If you are running on Windows 7 you could consider upgrading the Visio 2003 software to Visio 2007 or Visio 2010. If you require further assistance, please contact Product Support.

Issue Documentation for the obsolete PentaSens occupancy- and intrusion detection sensor (part no:6553002000) is requested. Environment CeTeLaB PentaSens part no 6553002000 Cause The product is obsolete from the Schneider Electric portfolio. But since it was a Class 3 product, documentation was provided by the manufacturer. Resolution You can find the CeTeLaB produced data sheet here. Also, a search on the Internet will provide more hits and further information/details on this product.

Issue Alarms are not clearing from the Active Alarm View when they Return To Normal and are Acknowledged. Environment Continuum Cyberstation Cause The "To Normal" Transition is not being sent to the recipient Workstation. Resolution Confirm that the "To Normal" transition events are configured to be sent to the recipient Workstation. In your EventNotification objects: Go to the Recipients tab. For each recipient Workstation, check the "To Normal" transition entry.

Issue How to run I/NET Seven Software as a local user Customer does not WIndows User logged in with Local Administrator rights to run I/NET Seven Software  Product Line TAC INET Environment Windows 7 Windows 10 I/NET Seven Rev 2.41 and above  Cause The IT department requires that I/NET Seven runs using a Windows "User Group" instead of the usual "Local Admin" Resolution   Define the Windows User Account Temporarily log into the PC with the desired User account using “Local Admin/Administrator” rights. Turn off the “User Account Control: (UAC) following the directions defined in this article Windows 7/10 User Account Control Settings  If this is not done then every time you try to enter an I/Net editor, using the “User” Group you will be asked to login as a “Local Admin” Change the User account back to the "User" Group I/NET Seven Feature Matrix: Review the following table showing all the editors both the “Local Administrator” and the “User” can access with their “Windows” Rights. Note: **The I/Net Editor “DbCreate Functions”. If you log into "DbCreate with the "SQL Server Authentication" then these items will be "Y". If you do not give the "Windows User" the SQL Username and Password then these items will be "NO"   User Account I/NET Seven Operation Administrator  User Install I/NET Y NO Remove I/NET Y NO Upgrade I/NET Y NO I/NET Configuration Y Y       DBCreate Functions     Create db Y Y ** Import I/Net 2X Y Y ** Verify existing db Y Y ** Remove existing db Y Y ** Backup db Y Y ** Restore db Y Y ** Import Docutrend Archive Y Y ** Upgrade db Y Y **       Seven Reports     View Y Y Run Y Y Configure Y Y Save Y Y Print Report Y Y Mount Archive Y Y View Archive Y Y Run Archive  Y Y Print Archive Report Y Y       Archive Configuration     Event Archive Configuration Y Y Run Y Y Trend Archive Configuration Y Y Run Y Y View  Y Y       I/O Server Configuration     Promote Filemaster Y NO Demote Filemaster Y NO Promote Client Y NO Demote Client Y NO  

Issue Attempting to modify the station program in a ENC on a jobsite and cannot connect to the ENC because of the License Brand Mismatch error. Environment Niagara AX WorkBench software and TAC branded ENC or I/A Series G3 Workbench and customer's third party branded AX Jace Cause I/A Series ENCs and Tridium JACEs are usually closed branded unless ordered with an open license. The branding on  the G3 / AX workbench software is always closed.  This procedure was defined by Tridium to protect the customer investment by allowing only authorized partner channel members to access the installed system at a customer site. Resolution I/A Series ENCs and  Tridium AX JACEs are normally supplied with a brand specific license that allows access only by the specific branded copy of the WorkBench software. A customer ordering a JACE or ENC can request that it be licensed as open branded.  This will allow the customer to access the JACE or ENC with their brand specific version of the Workbench software and will allow the Schneider Electric Buildings partner office to access the JACE or ENC with their TAC branded copy of Workbench.

Issue ARCnet communications failure. Environment Micronet ARCnet Router MN50-MI-RTR Daughter Board Cause Is it possible to purchase the ARCnet daughter board separately for an MN50-MI-RTR ARCnet router? Resolution Yes, the ARCnet daughter board is the MNR-C, and this can be purchased as a replacement item. To review the MNMI / ARCnet router general data sheet, please click HERE. To review the MNMI / ARCnet router "A" data sheet, please click HERE.

Issue When TAC Vista is setup as an OPC Server, Can you access the Historical Data (HDA) from TAC Vista SQL DB Product Line TAC Vista Environment TAC Vista OPC Server OPC Client Cause When TAC Vista is acting as an OPC Server and providing integration with a third party software / device, online and alarm values are all that is supported. Historical data is not supported via the OPC interface. Resolution It is not possible to access the historical data from the Vista SQL database, when using Vista's OPC Server . It may be possible to get historical data with the help of some third party OPC-HDA-Server for SQL software.  This option has not been tested, and issues related to this interface are also not supported. Click on below link to see an example of OPC-HDA Server for SQL. http://www.opcti.com/OPC-HDA-Server-for-SQL.aspx

Issue Cannot adjust the setpoint up or down on STR-250, STR-202 or M/STAT that is connected to Xenta 102-AX. Also, effective setpoint may not be changing when device goes from unoccupied to occupied modes. Product Line TAC Vista Environment Xenta 102-AX Plug-in STR-250 M/STAT STR-202 Cause This problem is most often caused by a scenario similar to the following example: A 102-AX is in cooling mode with an effective cooling setpoint of 70°F. An STR-250 stat is connected to the 102-AX and has a stat adjustment range (nviSetpoint.SCPTmaxRnge) of 6°F. This allows the occupant to adjust the setpoint ±3°F from the stat. The occupant is hot and adjusts the stat down to its minimum of 67°F. (3°F less than the cooling setpoint) The building operator decides that ±3°F is too much adjustment range and changes nviSetpoint.SCPTmaxRnge to 4°F (±2 degrees F) from the front end. The effective setpoint is still 3°F less than the cooling setpoint but now the stat cannot adjust the setpoint up or down since it steps in .1°F increments and both 66.9°F and 67.1°F are outside of the adjustment range. Since the stat adjusted setpoint offset is not a visible point and cannot be adjusted from the front end, the setpoint offset will be stuck until the stat adjustment range is expanded to include the effective setpoint and the setpoint offset is changed from the stat. Resolution To correct this problem the nviSetpoint.SCPTmaxRnge should be set high enough to include the effective setpoint. This can be done from Vista and can be found in the VAV_Controller object of the 102-AX or it can be done from the 102-AX Plug-in where it is called Stat Adjustment Range and is found on the Operating Parameters page. The setpoint should be changed at the stat to match the setpoint of the mode in which the 102-AX controller is currently operating. (eg occupied cooling setpoint) The stat adjustment range can then be returned back to its previous setting and the occupant can adjust the setpoint up or down and it will stay within the limit.

Issue When attempting to attach an Enterprise Server to a parent Enterprise Central, the error "Server name not unique" is encountered, despite the Enterprise Server having a unique name. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The error may arise due to either the server's name not being unique or one of its child servers' names not being unique. Resolution To resolve this issue, ensure that the server's name is indeed unique, and also verify that the names of the its child servers are also unique. For example, if an Enterprise server "ES1" has a child Edge server named "Edge_1" attached to Enterprise Central "EC", and another Enterprise server "ES2" also has a child Edge server named "Edge_1", it cannot be attached to "EC" until the child Edge Server is renamed to ensure uniqueness.

Issue I/A Series R2 and G3 MIB files Environment I/A Series R2 SNMP integration I/A Series G3 SNMP integration Cause A Management Information Base (MIB) describes a database of objects that can be monitored by a network management system. SNMP uses standardized MIB formats that allow any SNMP tool to monitor any device defined by a MIB. The Tridium MIB defines the information that can be exposed for a I/A Series Niagara station running the SnmpService. The third party system is having trouble reading the SNMP traps from I/A Series using the MIB file that was sent to them. Resolution Ensure that the correct MIB file is used. Starting in I/A Series R2 version 2.301.528 and above, a new TridiumR2-MIB was created that is supported by R2 Snmp stations. This was created because of the need to differentiate Tridium MIB object identifiers between R2 and G3. I/A Series G3 versions 3.4 and earlier uses TridiumR3-MIB.my MIB file. To view this file in WorkBench, go to 'File' > 'Open' > 'Open Ord' (or shortcut Ctrl + L) and key in 'local:|module://snmp/tridiumMib/TridiumR3-MIB.my'. Starting from I/A Series G3 versions 3.5 and above, there is a Workbench function (right-click menu on the local SNMP device) to create a MIB. See 'About locally generated MIBs' on page 3-17 to 3-21 of the Niagara Ax 3.5 SNMP Driver Guide.

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 Large data base log file causes Continuum to run very slow and/or crash. Environment SU CyberStation MS SQL Express Cause When Continuum starts and attempts to connect to the DB it takes too long due to the size of the log file (14GB in the case covered by this article) Resolution Shrink the database. Go to http://technet.microsoft.com/en-us/library/ms190757.aspx for steps from Microsoft to shrink the database files.

Issue Unable to run the  Database Initialization application. Receive error stating that "You must have NT local administrator access...". Even after logging in as a local administrator the same error occurs. Environment Continuum Cyberstation Windows Server 2008 Domain Cause The instances of this that have been reported all seem to be where there has been an upgrade to or new installation of Windows Server 2008 where the system is part of a Domain. It is not entirely understood at this time but something to do with the Domain policies being pushed down to the Workstations is causing problems.   Resolution Until the cause can be properly identified, a workaround that has worked in most cases has been to create/setup a local Administrator account and then run Database Initialization as an Administrator. Shut down all Cyberstations. Right-click Database Initialization and select "Run as... Administrator". With the EUR domain in the UK the following has been found - XP                 - "Right click" on the "Database Initialization shortcut" and “Run As” use local admin - Windows 7 - "Shift" & "Right click" on the "Database Initialization shortcut" and “Run as a different user”, use local admin

  Issue Schedule a meeting on a day when the site will be closed early. Steps are needed to ensure a door can be configured for 'card only' mode for the meeting. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause At times it's necessary to schedule a meeting on a day when the site will be closed early. Steps are needed to ensure a door can be configured for 'card only' mode for the meeting and then revert back to the normal schedule or extend the meeting until the end of the standard schedule. Resolution Steps to configure a door(s) with a schedule using holidays and 2 T&Ps to temporarily place the door in Card Only mode and then revert back to the standard schedule. In this example, the standard schedule Unlocks the door from 8a-5p.   Create a Holiday (Early Meeting) for the meeting date and ensure a Holiday Group Membership is selected Configure a schedule(Leave Early) for the meeting date(s) and length of the meeting. Select the Holiday Group in this example named 'Early Meeting Test' in the far right drop-down. The Holiday Group is needed for this to work. Note: The short-duration example was used while testing this multiple times a day. Configure a T&P (Early Meeting TP) to temporarily change the reader mode to 'Card Only' using the schedule (Leave Early). Select the Leave Early schedule and the 'Schedule-Became-Active' Event, the reader mode and the reader(s). The "Indefinite" duration drop-down selection worked. The other drop-down options did not work for this schedule implementation. Configure a T&P (Early Meeting Cancel) to cancel the Temporary Reader mode and revert control back to the standard schedule and to Unlock the door. Select the Leave Early schedule and the 'Schedule-Became-Inactive' Event, the reader mode and the reader(s). Extend the meeting to the end of the standard schedule if needed to keep it in card-only mode. Testing Results: At 3:55p the Leave Early meeting schedule became active and the TP changed the reader mode to card only. * Please disregard the Door held open highlights in the following snapshots At 4:00p the Leave Early meeting schedule became inactive and the TP canceled the temporary reader mode. The door Unlocked in this example after control was handed back to the standard schedule.