Building Automation Knowledge Base

Issue Request for Schneider Electric version of Controlli VMBP2M Environment Controlli VMBP2M Cause Some products of Controlli are also available through Schneider Electric.  Resolution Unfortunately, no cross reference to Controlli VMBP2M is available in the Schneider Electric portfolio.

Issue Is it possible to use a TAC Xenta 1.8 kOhm thermistor on an RTD-16 Central I/O module? Product Line EcoStruxure Building Operation. Environment Building Operation I/O Module 16 Ch RTD Cause Wants to use existing modules instead of adding new modules. Resolution The RTD-16 module is designed to interface with linear resistive inputs such as PT100, PT1000. Thermistors generally have logarithmic scales, therefore it will be hard to program a correct curve function to get an acceptable sensor accuracy. Using a universal input that is made for thermistor readings will give a more accurate reading without additional programming.

Issue Adjusting the setpoint from the SXWSC3XSELXX device. Product Line EcoStruxure Building Operation Environment Building Operation SmartX Living Space Sensor. Cause SXWSC3XSELXX has plus and minus buttons that could be used for changing setpoint. Resolution Navigate in the System Tree to the Display entry for the SmartX Sensor. Go to the Button and Scene Configuration tab under Properties. Scroll down to Front Menu Button Configuration, change Button 1 function to Change temperature setpoint. Select the tab Advanced, and scroll down to the Feature Control Settings. Set Allow setpoint changes to On. Set max and min limits for the setpoint under Setpoint high limit an Setpoint low limit.   When the plus or minus button is pressed, the Setpoint will change in steps. The size of the steps depends on the difference between the Setpoint high limit and low limit, divided by 10 (when using SI units). In the example above, the difference  between the Setpoint high limit and low limit is 28-18 = 10, so the Setpoint will be changed in step of 1 degree C.  

Issue Information for User Permissions using Access Expert is needed Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Access Expert User Permissions Overview  Resolution Overview User groups and permission are set by an Administrator to manage and control what aspects of the system an operator has. There are no default user login credentials. The user group (permissions) determines what areas of the software a user can access as well as what type of actions they can execute (i.e. update, delete, etc.).   User Groups A key aspect of the Keep permissions engine is the ability to explicitly Deny a trait or option for an operator. This Deny approach allows Administrators to quickly and easily create a new Permission group like an Administrative level operator but without a specific item.   User Group Lists From the General Configuration tab, click on the Groups icon in the Administrative section. This will open a list of all the Permissions currently available in your system. Every system comes with a single System Administrator permission level and there is no limit to the number of Permissions a single system can have.   Adding User Groups To add a new Permission: Click “Add Group”. Assign a Display Name. Assign a Description. The Description should be concise but also provide enough information about the functionality this role will have. Add desired Permissions. Click "Save" or "Save & Close". ***IMPORTANT: The minimum permissions to log in are read on the Instance.   Keep Objects Begin by adding rights to the new Permission Group. Note this process starts with the first available tab at the bottom of the screen which is the Objects.   Click Add Permission – This will start the process of building out the rights for this type of operator. A full list of Object Types will be provided at the bottom of this article with the associated Linking options. Key Terms: Object Type – the type of Keep object to be assigned. Object types follow the menu structure of the Keep system such as Access Levels, Badge Design and Controllers. Selecting the All Types option will provide full access to all aspects of the Keep system. Create – Allows the user to create new objects. Read – Allows the user to read the objects. Update – Allows the user to modify existing objects. Delete – Allows the user to delete the objects. Publish – Allows the user to publish events with the object type specified. Advanced Actions - Allows the user to enable advanced actions for integrations such as HID Origo and Single-Sign On. Linking – When an object type is selected the Linking column will become active. Each object type has a unique series of possible linking traits. When Linking traits are available, the Linking window will display “…”. By clicking the “…” the operator will be presented with the full list of possible traits that can be Added or Removed by checking the available boxes. Tags – A keyword applied to a series of objects within Keep to help provide additional separation of permissions. An example: an operator can be provided with Administrative level permission but only for items with a specific keyword. Applies To – Allows the administrator to limit controls to a specific device or series of devices. When being used simply click the “…” icon and the operator will be presented with the ability to choose the devices needed by clicking the Assign Object. Multiple objects can be added. Once the Assign Object icon is pushed simply start typing in the name of the device(s) needed. Type – Allows for Granting or Denying rights for the object type in that line. The second portion of setting up a new Permissions Group is to determine the Event Types that the operator will be able to interact with. Event Types is a very dynamic list because the available options will be determined based upon the integrations deployed on your system. The Event Types section is focused on the types of messages that an operator will be able to see as well as the type of commands the operator will be able to take. Key Terms: Application – the specific service associated with an application in the system such as Mercury Controllers, Allegion Locks, Video Expert, Mobile, and LDAP. Event Types – The specific traits associated with the Application. Each Event Type will be different and the options available will be determined by the integrations deployed on your system. Tags - a keyword applied to a series of objects within Keep to help provide additional separation of permissions. An example: an operator can be provided with Administrative level permission but only for items with a specific keyword. Type - Allows for Granting or Denying rights for the object type in that line. Object Types Each object type has a unique series of possible linking traits. When Linking traits are available, the Linking window will display “…”. By clicking the “…” the operator will be presented with the full list of possible traits that can be Added or Removed by checking the available boxes.

Issue How to read and understand the accuracy and repeatability on CO2 sensors. The sensors shows 380 ppm, is it defect? Product Line Field Devices Environment CO2 Sensors Cause Accuracy +- 30ppm +-2% of measured value Repeatability +- 20ppm +-1% of measured value Resolution   Accuracy The accuracy of a unit is defined as the tolerance between the actual absolute gas concentration and the measured value. For example, if a unit has a specified accuracy of ±30ppm, this implies that the displayed value will be within 30 parts‐per‐million of the actual gas concentration under standard ambient operating conditions. If the gas concentration in a room is 400ppm, then the sensor is operating within rated parameters if it reads anywhere between 370ppm and 430ppm on average.   Repeatability Repeatability is closely related to precision. Repeatability is defined as the variance in measured values of a known, unchanging gas sample upon repeat measurements. To put it another way repeatability is the range of acceptable values the sensor will read, relevant to a previous measurement, when measuring a gas, independent of the actual gas concentration.  For example, if the gas concentration in a room is 400ppm and the sensor has a rated repeatability of ±10ppm, then if originally the sensor reads 420ppm, upon future measurements the sensor will read between 410ppm and 430ppm.  Repeatability is generally specified as having a tighter tolerance than accuracy. Even if a sensor is reading a value that is slightly high when compared to the actual gas concentration, it is likely that it will read close to the same slightly higher value upon repeat measurements.   How to understand the accuracy and repeatability Accuracy +- 30ppm +-2% of measured value Repeatability +- 20ppm +-1% of measured value Accuracy at 400ppm:                     Min =  – (30 + 400*0.02) = -38                     Max = + (30 + 400*0.02) = 38 Repeatability at 400pm:                     Min = - (20 + 400*0.01) = -24                     Max = (20+400*0.01) = 24   This means that in a 400ppm environment, the sensor output can vary between                     400-38-24 = 328 ppm                     400+38+24 = 462 ppm Finally, based on the explanation given above, 380ppm would still be in spec. However, another reason could be that the calibration was done in an environment that was not the “purest” and by doing so, an offset was created on the 400-baseline explaining why values below 400ppm are reported.   As said 380ppm is still in spec but the customer could try to recalibrate the CO2 sensor to see if it changes anything.

Issue Information is needed about the Access Expert Kone Elevator Integration Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Kona Elevator integration information  Resolution Overview: Destination Dispatch is a licensed feature for Access Expert and used when customers are modernizing their elevator systems or deploying newer ones which do not utilize the relay-based approach for floor control and selection. Within Access Expert, 3 different elevator platforms are supported which include Otis, Kone and ThyssenKrupp. For this document, we will focus on a KONE deployment. It is important to note that a single Access Expert can support multiple integrations at the same time. The KONE integration supports up to 128 total floors of control. When using front and rear entry points within the elevator cabs), each entry point is considered to a separate destination. This means a 32- story building using front and rear entry points will result in 64 individual destinations.   A KONE protocol was created so that the LP controllers can manage access for the KONE Elevator Group Controller. Mercury will support configuration for Destination Operation Panels (DOPs), Car Operation Panels (COPs), and turnstiles. This feature is supported on the LP4502, and EP4502. The support for KONE Elevators was added in firmware 1.25.5.   Prerequisites: 1. Access Expert System 2. KONE Destination Dispatch License - FN-DEST-KONERS 3. Appropriate Reader Licenses 4. AX-LP4502 5. Coordination with the Elevator Contractor A KONE Elevator Destination Dispatching System mode was created within Access Expert so that the LP4502 intelligent controller can inform a KONE DEC (Destination Entry Computer, E.g. touch screen or keypad) allowed and authorized floors for a cardholder. This feature is only supported on the LP4502.   Controller Page 1. On the LP4502 controller page, navigate to the "Destination Dispatch" Tab. 2. Select Kone. 3. Enable "Has front and rear floors" if your Kone setup has front and rear floors. Make sure to take into consideration this flag when assigning elevator floors access. It is also recommended to consider the door when creating names. Examples like 2F or 2R are beneficial to system operators. 4. Set the Maximum Cabin Configurations. This is the number of Kone Cabin Access configurations that can be stored on the controller. 5. Press Save. 6. From the "Add Downstream" dropdown, select Kone KGC under the network port. 7. Enter the Display Name to be applied to be used.  8. Enter the KONE primary KGC IP address and Port. 9. Leave 2005 as the default port number. Press Save 10. Repeat steps 6 to 8 for the Backup KGC. 11. Issue a "Push Controller Database" command.   Reader Page Once the Interface Controller has been saved, add/Navigate to a reader attached to the Controller, and move to the elevator tab. The Reader does not reside on the KONE KGC downstream. The KGC downstream is only used to configure the controller with the Primary/Backup KGCs. The readers must be on the regular Mercury downstream modules or attached to the LP4502. Because of this, the actual reader setup is similar to a regular door/elevator deployment with the addition of new settings on the Elevator Tab. Once the Elevator Type is set to Destination Dispatch, a series of settings will be enabled and displayed. You will be presented with a WARNING Message when the Elevator Type is selected. This message is normal and you should select YES. 1. On the reader page, navigate to the "Elevator" tab. 2. Select "Kone Destination Dispatching" as the Elevator Type. 3. Select the Kone Operation Type. Please note that Kone does not support mixing Remote Call Giving Interface (RCGIF or turnstiles) with Destination Operation Panel (DOP) and/or Car Operation Panel (COP). Only one is supported at a time. 4. Depending on the Operation Type, specify the fields. 5. If desired, select an Override Elevator Access Level. This will allow a set of floors to be public during defined schedules. 6. Press Save. Kone Cabin Access Page 1. Navigate to "Access Configuration" on the Main Ribbon bar. 2. Go to "Kone Cabin Access". 3. Click on "Add Kone Cabin Access". 4. Enter a Display Name. 5. Enter the allowed cabins (up to 255). You can use the following formats to enter values: 1-10,15,16. 6. Press Save. Person Page Once the reader has been saved navigate to the person(s) who you want to grant access to the destination dispatch and select the new destination dispatch tab at the bottom of the page this will take you to a new Destination dispatch tab. To add an Elevator user setting, simply select the elevator type you wish to grant access to and click the add button. You will be prompted to select a controller. If there are no active LP4502 elevator controllers, then the dropdown will be empty meaning the user needs to add a valid controller. 1. On the person page, navigate to the "Destination Dispatch Settings" tab. 2. On the "Kone Settings" tab, click on "Add Kone Setting". 3. Select the Kone controller and press OK. 4. Enter the Default Floor. 5. Enter the Default Floor Side. 6. Select a Cabin Access 7. Select the Kone Elevator flags to be applied to the person. 8. Press Save.  *Users must configure the Instance Settings to reflect the correct number of floors. The Cab used will be sent by the Kone system to Keep on an 'Access Granted' and displayed in event data. Masks Kone has Global and Specific Masks that are used when setting schedules. These can be set and cleared by right-clicking on the controller and selecting the appropriate option. Setting the Global Mask opens the Global Mask Configuration window. To add a floor configuration, click the "Add Floor Configuration" button, then select the desired floors. From there the options for each floor can be selected by setting the appropriate flags for the floor. Click "OK" to save the changes. Other Information: Each Elevator Manufacturer has specific settings, commands or fields when deploying the Destination Dispatch integration. The following are specific to KONE: Supported Reader Types: 1. Destination Operation Panel (DOP) – Destination operation panels are located outside of the elevator car. Each of these will be configured as a separate reader. 2. Car Operation Panel (COP) – Destination operation panels are located inside the elevator cab. Each of these will be configured as a separate reader. 3. Turnstile (RCGIF) – Turnstiles are half-height sensor barrier solutions designed for public and commercial buildings and airports. Each turnstile will be configured as a reader and must use a Mercury reader port.

Issue Can a digital clock be used to replace an analog clock on a SVT4201? Environment SVT SVT4201 SVT4251 Cause Can a digital clock be used to replace an analog clock on a SVT4201? Resolution A digital clock cannot replace an analog clock in a SVT4201, because the SVT4201 and SVT4251 have a slight difference in components used.

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 Access Expert SSC and Mercury controllers require firmware updates Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause SSC and Mercury controller firmware needs to be updated for a fix or feature change Resolution Overview Mercury Controllers operate based on their firmware version and programmed configuration within Keep. It is necessary to update the Mercury firmware on occasion to ensure the most recent features, bug fixes and security upgrades are on the Mercury panel.    Updating Firmware Mercury controllers can be updated using the Keep by Feenics software. Before updating the controller, confirm the controller is powered on and connected to a Keep by Feenics instance. It is important to have a stable internet connection throughout the entire firmware update process. The duration of the firmware update will depend on the network bandwidth but typically will take between 5 to 10 minutes for a complete update. Users can issue multiple firmware updates to different intelligent controllers at the same time, but not downstream devices.   Updating the Firmware on a Controller To update the firmware on a controller: Open the controller page.  Beside the Version field, click on the "Update Firmware" button. Open the Live Monitoring window and set the priority to 0. In the Live Monitor, you will see the "Downloading Firmware Event". Once the controller has completed the firmware update, it will reboot.  After, close and re-open the controller page to see the updated firmware version. EP Controller Firmware The EP Series controller's current version is 1.29.1.633 and was released on 2020/01/31. Due to the controllers being End of Life, no new versions of firmware will be released for the EP series controllers.   On-Premise Deployments Note: On-Premise Deployments are no longer supported. All sites will convert to hosted. The previous process to upgrade firmware for On-premise deployments (servers managed on-site): They can have their firmware updated out of band by placing the latest Mercury CRC files in the appropriate directory. Once the files are in place users can proceed with the update steps outlined in this article. The default directory for firmware files can be found at C:\Program Files (x86)\Feenics\Mercury Service\MercuryFirmware. 

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 Bringing a MicroNet LON controller/network into EcoStruxure Building Operation Product Line Satchwell MicroNet Environment Satchwell MicroNet MNN-30-100 Satchwell MicroNet MNN-44-100 Satchwell MicroNet MNN-50-100 Satchwell MicroNet MNN-62-100 Satchwell MicroNet MNL-C Cause Satchwell MicroNet 100 series LON networks are not supported in EcoStruxure Building Operation as a MicroNet LON network Resolution From the introduction of the MicroNet 50 series range in 2008, the MicroNet 100 series controllers with LON cards has no longer been supported and the MicroNet LON network is not supported in EcoStruxure Building Operation. Workaround: The MicroNet 100 series LON controllers can be bound to a standard LON network, using a third party network management tool such as LonMaker®  for Windows®  from Echelon. The complete MicroNet LON network could then be brought into an AS-P as a standard LON network. If this is not possible, the supported option to bring the MicroNet 100 series controllers into an AS-P or Enterprise server (ES) would be to remove the LON cards, from the MicroNet 100 series controllers and convert them to use an NCP network. The top two pairs of pins of the auxiliary card plug, would need the jumpers restored. The LON network cabling may need to be changed for a RS 484 compatible type, such as Belden 8762 or equivalent. The controller’s program would need to be re-configured for NCP using VisiSat. Then the MicroNet controller network can be imported into the AS-P, under a MicroNet NCP interface. If the LON network contains MicroNet LON touchscreens, these cannot be converted to NCP and would need to be removed from the NCP network.   The MicroNet 100 series data sheets are available here https://community.se.com/t5/Building-Automation-Knowledge/MicroNet-100-series-controller-MLi-s-and-Data-sheets/ta-p/6784   VisiSat 2.1 Build 196 – Software is available here https://ecoxpert.se.com/search?documentUUID=c93346a7-9d82-48e7-9b54-a866ac75bb71&title=VisiSat%202.1%20Build%20196%20-%20Software   VisiSat Release 2.1.196 Service Pack 1 https://ecoxpert.se.com/search?documentUUID=fd2e9849-1ffe-4c10-b3a6-5f27bac91870&title=VisiSat%20Release%202.1.196%20Service%20Pack%201%20(2.1.200)%20-%20Software   VisiSat Release 2.1.196 Service Pack 2 https://ecoxpert.se.com/search?documentUUID=839c09d2-400d-4434-8b1e-97f339545034&title=VisiSat%20Release%202.1.196%20Service%20Pack%202%20(2.1.201)%20-%20Software

Issue Add a receiver group to a Xenta server alarm in Xbuilder Environment TAC Xbuilder Cause Easiest way to add a alarm receiver group to an alarm. So that an e-mail is sent when the alarm is triggered Resolution Drag and drop the alarm receiver object on top of the alarm.

Issue When backup to flash is automatically disabled by the system due to exceeding the flash circuit breaker write limit, no system alarm is sent to make the system's operator aware  Product Line EcoStruxure Building Operation Environment Continuum i2920 Controller Cause Implementation of Continuum Infinet integration in EcoStruxure Building Operation did not include this feature. Resolution As a workaround, a user-created alarm can be used instead of the system alarm. Here is a sample implementation of this workaround:   Under the Infinet Interface create an Alarm, in this example, we are using an 'Expression' alarm Here is the algorithm used as an expression for the alarm Value = BackupDisabld In the i2 device, edit the 'StatusBackup' system variable and attach the alarm above in the Alarm Configuration tab. Make sure to tick the 'Enabled' box to engage the alarm.   The alarm will be sent when the flash circuit breaker trips which in the i2 device takes place after 10,000 backups To resume backups the feature must be manually re-enabled from Workstation by right-clicking the device and selecting DEVICE->ENABLE BACKUP TO FLASH

Issue How will SQL logging be affected if a trend log's parameters are changed?  Environment Vista 5.1.X Cause A customer may wish to log values from another point, eg if an energy meter has been changed, or may wish to change the frequency with which the point is logged. Resolution The simplest answer to this question is that if a change affects the log, the message "Log database will be emptied" will be displayed giving the user the opportunity to cancel the action. Depending on the type of trend log being used, the check box "Keep trend log values when changing log point" can be checked and this will allow the log point to be changed - all other parameters must remain the same. It is not possible to change the log interval without emptying the log database for the point as a number of calculations are carried out when displaying log data in a client, that require the points to be logged at a regular interval.

Issue Require details on how to configure duress events from Doors and Keypads to be registered and displayed as alarms. Product Line EcoStruxure Security Expert Environment Security Expert Cause Door and Keypad duress trouble inputs are not configured to trigger alarms when activated. Resolution Use an Event Filter to filter for specific Trouble Input events and then setup an Alarm to use that Event Filter. Configure an Event Filter for duress events by creating an event filter with the Event Type: Trouble Input<TROUBLE_ZONE_NAME>Opened If you need an alarm for when the duress trouble input is closed then also add: Trouble Input<TROUBLE_ZONE_NAME>Closed Event Types Then on the Records Tab add the specific Trouble Input(s): User Duress Code Door Duress Record Filter Create a new Alarm record under Events | Alarms. Add this Event Filter, created in step 1, to the Alarm.

Issue When the Vista export file is converted using the Vista conversion to an EBO Server the Xenta devices are created with an empty application. Product Line TAC Vista, EcoStruxure Building Operation Environment Vista Conversion tool Cause The user name that was used to log into Vista Database to run the Database export does not have full access to the Xenta devices Function Block Program. Resolution Log in with the System user that has full access to the Vista Database and export the database for the conversion tool to use.

Issue On an existing trend log, the calculation type can be set to the “Meter Consumption”, but this does not generate any log records. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause The “Set initial meter” under the “Meter Info” tab has been set to false when the trend log was initially created. Resolution The following image demonstrates the issue. The “Is meter log” is false because in the trend log creation process the “Set initial meter” has been set to false. This causes the “Meter Consumption” calculation type does not generate any log records. To resolve this: Create another Trend log with the “Set initial meter” set to true Or Right-click on an existing trend log (with “Is meter log” = false), press manage meter, configure the required settings, and then press save. This will change the “Is meter log” to true  Now, if the calculation type is set to “Meter Consumption” on the trend log, the log records are getting populated.

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 SigmaX checks prior to transition into EBO Product Line Satchwell Sigma Environment SigmaX Cause Programmable Object checks required prior to transitioning Sigma to EBO. Resolution Programmable Object checks steps to be taken to check a Sigma database is free of more than one type of RETURN statement is used prior to a transition to EcoStruxure Building Operation (EBO). This video will demonstrate how to use SigmaX to find and create a report of any Programmable Objects that are using more than one type of RETURN statement. This video with SigmaX is the third of three videos, the first SigmaX Quick Help Video will check for Database Errors and the second video will check for Duplicated Names.     When launching the SigmaX application, see the Knowledge Base articles for Side by Side errors and errors regarding missing SigmaX files should they occur.

Issue Xenta 301XT/N/P is not available Environment Vista Xenta Cause Xenta 301XT/N/P is a Xenta unit made for the US market where some facilities needed some extra range of temperature. The XT stands for Extended Temperature. Resolution This unit is obsolete now and can no longer be ordered.

Issue Not all changes in a Notes file are saved. If opening and edit a Notes file, save and then continue writing only the changes before the save will be changed. Environment Vista 5.1.x Cause The Notes file will only be saved once then you need to close it and open it again. Resolution When editing a Notes file only save once then close the file. If you need to write some more close the file and open it again.

Issue The Sigma object associated with the first entry in the Gateway.txt file of an S-IC3-SNP integration controller when displayed in the Sigma System Manager, always shows its default value. Environment Sigma S-IC3-SNP Cause There is an issue with the way that the S-IC3-SNP processes the object mapping file (gateway.txt) file, please note that this issue does not affect the earlier S-IC-SNP Resolution TPA-LOND-08-0011.00 provides a workaround for this issue, the work around involves adding a dummy line to the Gateway.txt file, this then allows the first object to be displayed normally.

Issue When configuring reports there is no option to select the report to be exported once a month. Product Line EcoStruxure Security Expert Environment Security Expert Cause There isn't an option to have a  report run only once a month. Resolution A workaround for this would be to select a single day of the week for it to run. This would reduce the frequency of the reports to once a week, then to have the operator check the export folder once a month for that months report.   Browse to the Event Report you want to export. Under File Export tab select the Enable File Export checkbox. Set the Time field to the time of day you want to run your report. Set the Export Directory to the folder you want to save your report export files to. Under Days to Export select one day of the week. Under Period select Last Month. Each time this report is run the same file will be overwritten, so when setting the report period to "Last Month" it will export the last months events from when it is run. Once a month the Operator would then select the file in the report folder which will have the last months events in it. The filename of the report is "EventReport" followed by that Event Reports Database ID number.