Building Automation Knowledge Base

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 Is there any limitation for the number of local program variables that can be declared in a script program located in ExoStruxure BMS servers or BACnet/IP controllers?   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 Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) 24 V Cause A script program has a lot of variables declared. Resolution There are no hard limits imposed by the script compiler. for the number of local program variables. The limits are performance and device resources. The bigger a program is, the more memory and processor bandwidth it will consume and the longer it will take to execute. 

Issue The sequence numbers for Alarm Events are changing daily for all active alarms in the system. This can be a problem for applications using sequence number as alarm identifier. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server. Building Operation Automation Server Premium Cause Every night there is a cleanup in the alarm table and alarms can then get new sequence numbers. Every night historic updates with old time stamps are removed in the alarm table.   When this cleanup takes place, there is a reorganization of sequence numbers of current alarms. They all get a new sequence number.   The new sequence numbers are always higher than the latest sequence number before the cleanup. Resolution Do not use alarm sequence number for alarm identifier, use triggered time stamp instead.

Issue Not possible to get a Xenta Server / 911 online in TAC Vista. It is possible to ping it and connect to it via a Web browser using ports 443, 80, and Port 1068 is open, but it is not possible to get online in Vista. Product Line TAC Vista Server Environment TAC Vista TAC Xenta 911 TAC Xenta Server Cause The problem, in this case, was that another Vista server was connected to the Xenta Server / 911.  This could have been from a technician or the customer who started Vista with this database loaded and had the device online in their Database. The Xenta Server / 911 will only communicate with one Vista Server at a time and will close the connection if another Vista tries to communicate with it.    Using Wireshark it is possible to monitor this scenario as shown below:  Packet number 57439: Vista is trying to establish communication with the Xenta Server or 911( sending an SYN). Packet number 57440: The Xenta sends an acknowledgment on the SYN from Vista, but with the window size set to zero, this is because the Xenta can't buffer information as a computer does. Packet number 57441: Vista  sends an acknowledgment on the message from the Xenta Packet number 57448: The Xenta sets the correct window size. Packet number 57449: Vista starts to communicate Packet number 57452: The Xenta closes the communication to the Vista server  Resolution Ensure only one Vista server is started when the Xenta server / 911 is included in the database.

Issue TAC Vista database export/import. Description texts are missing when the .zip file is imported. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation Export/Import Cause Changes to the object description text fields made in TAC Vista Workstation are not automatically saved in the .mta file. Resolution To make sure that the description texts will be included in a database export (physical structure only): Edit the Xenta application with text description fields added or modified through Workstation. Save the Xenta application to the database. If you do this, the description text will be written in the .mta file and will be included in a database export.

Issue There is no information on how to create and prepare signed certificates for import in Building Operation. PEM file format has to be used. If another format is used or the certificate files are not correct, you get a message like this when importing SAXParseException: Reference to invalid character number in line X column Y Product Line EcoStruxure Building Operation Environment Certificates Cause There is no information on how to create signed certificates in Building Operation. Resolution Make sure that when preparing the pfx file that the full chain of trust is included in the pfx file. You have various options when preparing a pfx certificate export file, and the private keys and chain of trust are options that must be selected. Otherwise, you won't extract the intermediate certificate or the private key if not included. Complete a Certificate Request and then request a certificate in PEM format in a .pfx file "container".  Extract the CA certificate, Intermediate certificate, and private key using the following OpenSSL commands. After executing each command, enter the password if prompted. Make sure you reference the right pfx file. Below filename.pfx is used as an example Make sure you enter the commands manually and do not copy/paste from this article Download OpenSSL tool here or use OpenSSL installed with EBO  openssl pkcs12 -in filename.pfx -out host.pem -nodes -clcerts -nokeys openssl pkcs12 -in filename.pfx -out inter.pem -nodes -cacerts -nokeys openssl pkcs12 -in filename.pfx -out privkey.prv -nodes -nocerts The three files produced must then be parsed of any characters that aren't in the part of the certificate/key and in PEM format (or PRV if private key) - basically all the characters before "-----Begin Certificate-----" or after "-----End Certificate-----". Ensure each file ends with a blank line and that a blank line separates each section. This can be done in any text editor; however, this example uses Notepad++ with the "Show All Characters" button selected.  Import the files into SBO using the certificate manager in the Control panel. File type conversion If the host and intermediate certificate are in crt, cer or der format, you can convert them to pem format using the following method/command: openssl x509 -outform der -in certificate.cer -out certificate.der openssl x509 -inform der -in certificate.der -out certificate.pem Replace "certificate.cer" with the name of your file Determining certificate file type To determine which filetype a given certificate file has (PEM, DER, or pkcs12/pfx), you can use the following commands (replace "cert.crt" with the name of your file). A valid output will confirm the file type. PEM openssl x509 -in cert.crt -text DER openssl x509 -in cert.crt -inform DER -text pkcs12/pfx openssl pkcs12 -in cert.crt -info

Issue How can a webpage be integrated into Vista graphic pages for a seamless transition between a graphic page and a 3rd party website such as: Static information, such as a site webpage Device webpage (power meters, sensor, etc. Product Line TAC Vista Environment Vista Server 5.x.x Cause The Hyperlink database object in Vista can store a URL address. By linking to this Hyperlink object with a standard link in a Vista graphic page, standard components can be used and support common graphic pages for different sites and reusability. Note:  More complicated integration can be accomplished with javascript, but this requires custom components such as accessing web services such as weather.com data for actual display on your graphic page. Resolution Create a Hyperlink object in the Vista database for each page you want to make available. Use a link in the TGML graphic page to access this Hyperlink object. Clicking the link on your graphic page will display the webpage in the Vista Workstation window. Target Property The target property can be configured for Webstation display to control the window or frame the link is opened in. The options _top, _self, and _parent will be ignored in WebStation and treated as _blank, which will open a new tab or frame depending on your browser settings. If you specify a target frame you must match the exact syntax of the WebStation frame names from the following list: TAC_WebStation_header TAC_WebStation_left TAC_WebStation_contents TAC_WebStation_footer

Issue In many situations, customers need to integrate more than one LNS database into a single Vista database. Product Line TAC Vista Environment Vista LNS LonMaker NL220 TAC Vista System Plug-In Cause This is very common in retrofit situations where a new LonMaker or NL220 database is created for the new section of the building. Still, the existing system was programmed in a completely separate LonMaker or NL220 database. This is common for multi-building systems like school districts that expand and add schools or buildings over time and integrate into one Vista database. Resolution Some general rules must be followed when integrating multiple LNS databases into one Vista database. These rules are: You can not integrate more than 4 LNS networks to 1 Vista database when doing straight LNS server-to-Vista server communication. NOTE: If more than four networks are needed, the system must utilize the Loytec NIC852 key and the Orion stack. When using the Orion stack and 1 Loytec NIC852 key will expand Vista's capability to 8 LNS networks simultaneously. If more than 8 LNS databases are needed, then multiple Loytec NIC852 keys are needed. Vista can only communicate to 4 Loytec NIC852 keys simultaneously for a maximum of 32 LNS databases per Vista server. It is recommended never to use more than seven ports on the NIC852 for serviceability reasons, with Lonmaker or NL220 truly giving the system a 28-network limitation. The Menta file paths from the site or engineering PC will be stored within the path structure of the System Plug-In. If these files are not in the exact same path on the Vista server that the LNS database is being integrated to, all.MTA files will have to be browsed for every controller. It is recommended to save all Menta files from the engineering Vista database to a folder on the machine to ensure they are the most current files. Then copy that menta files directory to the new Vista server to ensure the System Plug-In will search and copy the same path when transferring the network to the vista database. Every LNS database integrated into the Vista server must have a unique domain ID. See the instructions and screenshots below. The screenshots and instructions below detail how to build one Vista database with two LonMaker databases. The first database will be called NETWORK1, and the second database will be called NETWORK2. Please follow these instructions: Restore and open the LonMaker database NETWORK1 on the machine running the Vista server database into which the LNS system will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties. Set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK1 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name.  LNS_Network Name is good practice. In the example below, it is LNS_NETWORK1. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK1 is the LNS port, and NETWORK1 is the physical LNS database.   The steps to add the second LNS database are almost identical except for steps 2 and 4  above. Follow these instructions to integrate NETWORK2 into the Vista database. Restore and open the LonMaker database NETWORK2 on the machine running the Vista server database into which the LNS database will be integrated. The Vista server must be running and logged in to continue with the next instruction.   From the Visio menu bar, choose LonMaker and Network Properties and set the Domain ID to a unique number within the Vista database. Systems sharing the same LNS server communicating to one Vista server must have unique Domain ID numbers.   In the NETWORK2 LonMaker database, open the TAC Vista System Plug-In and choose the toolbar menu item TAC Network, then choose settings. Click the browse button next to the Operator unit object: and browse to the local Vista server object running on the machine. The Operator unit object: entry to change to the Vista server object name currently running on the local machine.   In the TAC Network Settings menu, the Vista communication port should be set to Communication Port - LNS, and the Vista communication port name should be unique to the LNS network name. In the example below, it is LNS_NETWORK2. LNS_Network Name is good practice. Click Apply, then OK, and close to close the TAC Network Settings window.   In the TAC Vista System Plug-In, click the Update TAC Network Icon.    Next, click the Check TAC Network Icon. Check for any errors or warnings in the output pane.   Then finally, click the Update Vista Database icon. This process will copy all of the Xenta groups, Lonworks groups, .MTA files, and .XIF files to the Vista database.   Once the Vista database has successfully updated, open Vista Workstation, and the LNS port should be created along with the physical LNS network. In the screenshot below LNS_NETWORK2 is the LNS port, and NETWORK2 is the physical LNS database. As network 2 does not use the default Domain length of 1 and Id of 11 and uses a Domain length of 1 ID 12, any operator panel used in this system will need this domain setup to work this network.  You can adjust the OP Domain setting as described in the following article, "No Answer" on an OP when connecting to a Xenta 280/300/400

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue There is an alarm showing after adding a downstream controller Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Instructions needed to eliminate the power failure and  tamper alarms showing on newly added downstream devices Resolution When adding downstream devices, for example, An MR50, MR52 or MR16In/Out to an SSC, EP1501 or EP1502 controller, an alarm may show in the hardware tree. To get the controller out of this state, the following steps need to be taken: a. Locate the terminal block(TB) on the panel which contains the connections for CT (Cabinet Tamper) and BA (Power Fault) Note: You may need to consult the specific controller documentation since the TB#  with these connections are different on each board. It will look similar to the following: b. Remove the connector Cut two small pieces of wire, one for each Alarm Use the 2 wires to jumper each connection (CT and BA) to create a closed circuit. This assumes these contacts are not being used for their usual purpose. No resistors are required Place the connector back on the board The downstream devices no longer show alarms for the respective addresses.

Issue .MTA file not updated .MTA file does not show the correct value when exported/imported The Menta project does not have the correct value when imported into a new database Product Line TAC Vista Environment Vista Menta Xenta OP Cause The upload/download parameter does not save any changes in values to the .MTA file. It only saves it to the device and Vista database. This means that if you export a project and import it to a new database the .MTA file will contain the initial values chosen when you last saved the Menta project. To get the values saved to the .MTA file, you need to edit the Menta project and save it again. However, to trigger the save correctly, you need to change the project. For example, add a comment or move a block, then hit save. Resolution  Below is the correct way to edit a project in a new database.  On the client PC, start by doing an upload parameter; this ensures that the values stored in the Xenta are present in the Vista database. Edit the Menta project(s) and add a comment (This can be a comment like "John brings the project home to make some changes") now the project can be saved, and all new values will be stored in the .MTA file.  Export the database/project Import the database/project to the new PC Make the desired changes Edit the Menta project(s) and add a comment (This can be a comment like "John has made the following changes ....") now the project can be saved, and all new values will be stored in the .MTA file. Export the database/project Import the database/project into the client's PC Now make a download parameter; this ensures the Xenta will get updated with the changes you have made.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 What steps are needed to configure and add Mercury Intelligent IP Controllers to Access Expert Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Instruction steps are needed to configure and add Mercury Intelligent IP Controllers to Access Expert Resolution Overview Intelligent Controllers synchronize with Access Expert in real time, but all access decisions are made locally and independently from the server. This means that the processing of events, actions, and alarms remains local and functional even if network connectivity is lost. Configuring a Controller for IP Client Power the controller with an external power supply or by PoE and connect the controller via Ethernet cable to the network. Make sure all DIP switches are set to the off position. Enter the IP address of the controller in the web address bar of Microsoft Edge or Internet Explorer. Set DIP switch 1 to the ON position to leverage the default username and password. Log into the controller within 5 minutes of setting DIP switch 1 to the ON position with these default credentials. Username: admin Password: password From the menu located at the left of the configuration manager page, click on the ‘Network’ button to visit the network settings page Ensure ‘Use the following DNS server address is checked and enter 8.8.8.8. This is a Google DNS server. We recommend utilizing this to maintain the best operation. Click on the Accept button in the ‘Network Settings’ page to save changes. Navigate to the menu and select the ‘Host Comm’ to open the page. Ensure the Primary Host Port is configured as follows. It should be noted the Alternate Host Port must be disabled: Communication Address: 0. Use IPv6: Unchecked. Connection Type: IP Client. Data Security: TLS if Available. Host IP/Host Name: connect.feenics.com. Port Number: 3001. Connection Mode: Continuous. Retry Interval: 20sec Click on the ‘Accept’ button in the ‘Host communication’ page to save changes. Navigate once again to the menu and select ‘Apply Settings’ to open the page. Click ‘Apply setting, Reboot’ (located at the top of the page). If a warning page appears, check both the ‘I understand' and 'wish to proceed’ boxes. Click 'Yes' to apply the changes and allow the controller to reboot. Adding Controllers to Access Expert Controllers are added to Feenics from the Hardware Provisioning tab. When adding a controller, you will need to select the controller type from the drop-down list. If the controller you are trying to add does not match one of the types listed, Access Expert does not support it. When adding a controller, a name must be given to identify the controller and the UNIQUE MAC address of the controller. The MAC address is used to identify the controller within the Feenics system. Duplicate MAC addresses will not be allowed.   When adding a controller, the MAC address is optional. If no MAC address is provided, the controller will be marked as disabled upon save. The controller can only be enabled by providing a valid MAC address.    Steps to add an IP Controller to Access Expert Select the ‘Hardware Provisioning’ Tab Click “Add Controller” and select your device type Enter a Display Name Enter the MAC Address in the correct format: “XX:XX:XX:XX:XX:XX” Select the time zone (This sets the Controller Time) (OPTIONAL) Assign Card Formats as needed (Can be added later) (OPTIONAL) Add Custom EOL Tables 8. Click “Save” or “Save & Close” The Port configurations will be grayed out initially until you commission Interfaces and Downstream Devices. At that point, the port configuration section will automatically be configured. Baud Rate is configurable but all devices on the bus must share a baud rate. ***Important Note: It is important to choose the correct controller type when adding a new controller.  

Issue How do you determine which version of Access Expert being used Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Unsure which version of Access Expert is installed Resolution When opening Access Expert new users may not know what version they are currently running. The following differences can help to identify the version being used.   Version 2: Uses a url e.g. http://seba.accessxpert.com The Hardware tree is on the left pane when selected Only five tabs on the header Icons are larger on screen No Folder View  Version 3: Uses an app that needs to be installed The hardware tree is on the right Seven tabs on the header depending on the license Icons are much smaller Folder view when enabled  These are just a few of the differences that are visible to help determine which version is being used.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 Instructions needed to perform a Factory Reset for Upstream Mercury Controllers Product Line EcoStruxure Access Expert Environment Access Expert software Hosted V3 Cause Instruction steps are needed to reset Upstream Mercury controllers to Factory Default settings Resolution Bulk Erase Configuration Memory: The bulk erase function can be used for the following purposes: Erase all configuration and cardholder database (sanitize board) Update OEM default parameters after OEM code has been changed Recover from database corruption causing the board to continuously reboot   Bulk Erase Steps (Factory Reset): Do not remove power during steps 1-8   Set S1 DIP switches to: 1 & 2 "ON", 3 & 4 "OFF" (see DIP switch location and diagram below) Apply power to the board Watch for LEDs 1 & 2 and 3 & 4 to alternately flash at a 0.5 second rate Within 10 seconds of powering up, change switches 1 or 2 to "OFF". If these switches are not changed, the board will power up using the OEM default communication parameters LED 2 will flash indicating that the configuration memory is being erased Full memory erase takes up to 60 seconds When complete, only LEDs 1 & 4 will flash for 8 seconds The board will reboot 8 seconds after LEDs 1 & 4 stop flashing (no LEDs are on during this time)  All other switch settings are unassigned and reserved for future use. Factory Default Communication Parameters: Network: static IP address: 192.168.0.251 Subnet Mask: 255.255.0.0 Default Gateway: 192.168.0.1 DNS Server: 192.168.0.1 Host port: IP server, no encryption, port 3001, communication address: 0

Issue How to set up a controller for Elevator Controls. Product Line EcoStruxure Access Expert Environment Win Server 2012 and above Cause Steps to configure Elevator Controls from the beginning. Resolution To achieve this the following steps need to be followed: Open Access Expert Click on the main controller (SSC) Add interface - MR16 Out Set the address of the interface (dip-switches 1-5 on the panel) Add Reader interface and name accordingly (Elv Flr 1) for example Select the Elevator Tab and make the appropriate selections Go to the Elevator Tab Associate the MR16 Out (Floor Relays) Set Floor Relays (1 through 16) Create an Elevator Access Level - this would be used for floors that have access to this level An Elevator Override Access Level can be created as well if an Unlock Schedule is required Create the Door Group and assign the necessary  reader or readers Go to General Configuration and select the System Settings Select the Hardware Tab On the Elevator settings, change the Elevator Relay  Time and Elevator Push Button times from 1 to 5 seconds Once configured, select the elevator reader, right click and choose the Pulse option to test the relays If correct, the assigned readers will Pulse Assign users to the Elevator individually or through the User List.   Note: Please keep in mind that if there are multiple readers for multiple floors, it is best that a reader be associated with its own MR16 Out, it is best practice as the relays cannot be shared between the readers. Meaning that if Reader 1 uses relays 1-8 the second reader would not be able to use 9-16 on that same MR 16 Out. It would need its own MR16 out for those floors. Note 2: When creating Elevators in Access Expert, the outputs used on the MR16Out should not be added as an Output once defined in the Reader. These are automatically assigned, if they are added then the Floor selections will not function properly. 

Issue Valid cards are being denied access at doors with "Read Raw" events seen in the Status Page. Read Raw Data Read Raw Data Events Read Raw Credential Data Read Raw Credential Data Events Product Line EcoStruxure Security Expert Environment Security Expert Cause The credential being supplied to the doors reader can be read but is not able to be matched to a valid User in that controller. There could be a couple of reasons for this: Pending downloads have not yet gone through to the respective controller The User in question does not have access to any of the Doors in that controller. Resolution Wait for downloads to complete or manually perform a download to send any pending User updates down to the controller. If the User is supposed to have access to the door they are badging at then confirm they have been assigned an Access Level that includes that door. To hide the events refer to Do Not Display Read Raw Data Message. To display a different message for the event refer to  Add Users to a Controller so all Card Events are Associated.

Issue When using Project Configuration Tool (PCT) in Server mode and connecting from a remote PCT client, it is not possible to transfer backups or exports. The transfer gets stuck, and a complete reboot is required to start using the project again. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause In the "Settings for Project Configuration Tool" the Notification and Listening port defaults to 0. Port 0 means that PCT will ask the OS for an available port. But if network policies prevent PCT from communicating using that port, PCT cannot detect that.  Resolution In "Settings for Project Configuration Tool" Change the port number for the Notification port and Listening port to a port that is available to use.

Issue In TAC Vista, we had a function for the OGC graphics called standard graphic. Do we have something similar in Building Operation? Product Line EcoStuxure Building Operation Environment Building Operation 2.0 and above Graphics  Cause All graphics connected to the standard graphic in TAC Vista changed if the standard graphic was changed. This is a very useful function when having many similar graphics.    In Building Operation, a new object was implemented in version 1.8 labeled shared Graphics, Custom Types superseded this in version 2.0, and this function is similar to shared Graphics but not identical. Resolution There is no direct function like this in Building Operation.  Custom Types is the only similar feature available in the currently supported versions of Building Operation. Additional information can be viewed in the online help topic Custom Types Overview.  

Issue How to configure two room sensors in ZBuilder. Product Line EcoStruxure Building Operation Environment ZBuilder Cause It is possible to configure TAC Xenta 121 or TAC Xenta 122 to use two room sensors via the ZBuilder tool. Resolution In Zbuilder, under the tab Configuration, under Room unit, select the type of sensor you are going to use. Select the tab I/O Setup,  Right click on the sensor and select Duplicate. Move the sensors to the input you are going to use.   At the end of this session you will be able to: Configure TAC Xenta 121/122 to use two room sensors. Understand that the nvoSpaceTemp value is calculated as average value of the two sensors. Understand that it is not possible to see the actual value of a single sensor when using two sensors.    

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 Read Raw Data events for valid cards without access are shown but do not identify the User or indicate the door is not allowed Product Line EcoStruxure Security Expert Environment Security Expert Cause If a User does not have an access level for at least one object on an SP-C controller then the user record is not downloaded to the controller.  Therefore, when the user swipes their card at a reader for a door on the controller a Read Raw Data message is received. Resolution This resolution requires creating an access level so the information about doors any users do not have access to are downloaded to the controller.  This will then display an indication that the door is not allowed.   Create an Access Level and give it a name, in this example it is called Door Not Allowed Access Level.  Select the Outputs tab for the access level and add at least one output from each of the controllers that contain the doors where the Read Raw Data event occurs.  It does not matter which output as it will not be used for any control.  Adding the output means the access level will be download to that controller. Navigate to Users and select the user(s) that require an indication that the door is not allowed rather than a Read Raw Data event.  Add the access level, e.g. Door Not Allowed Access Level, to the users.  Save the newly added option.   As can be seen in the image below, in comparison to the same sequence of events shown in the Issue section, the Read Raw Data event is replaced by a Door Not Allowed event.  The User is also identified. Note: The Read Raw Data event will still occur for any User that does not have the access level applied (or any cards that are not in the system).