Building Automation Knowledge Base

Issue LonWorks point count recommendation for the Xenta 5/7/9xx series controllers What is the device limitation on the FT-10 LonWorks channel installed on a Xenta Server Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause The load point table can be found in Vista version Release Notes on The Exchange Download Center. When Xenta 700 was released the Product Announcement had a table with the recommended number of LonWorks devices attached to Xenta 5/7/9xx. Below you can see a small revision of the recommendations. The list applies to devices which the applications in the Xenta 5/7/9xx are interchanging data with. Other devices that are completely handled by TAC Vista through the LTA port of Xenta 5/7/9xx are not included in this calculation. These devices will influence the LonWorks network performance in a similar way as if they were connected through a Xenta 911 and have to be considered. Not following the design recommendations and adding too many LonWorks devices to a single channel will cause poor Xenta Server performance. Resolution Each device uses "load points" according to the table. As a general guideline the total "load points" on the network shall stay under 100 to get a reasonable performance. In reality the e.g. intensity of the traffic also has an influence as well as, of course, the expectations on response time. Type of device Load points I/O module 5 Xenta group master 280/300/401      20 Additional Xenta 280/300/401      in the group 2 Standard LonWorks device, including Xenta 100, polled 2 Standard LonWorks device, including Xenta 100, bound 0.75 Refer to The Exchange Download Center for future releases of Vista / Xenta Release Notes containing software and updated load calculations This information is usually found in the Appendix B - Engineer Information, and look for section titled LonWorks recommendation for the Xenta 500 and 700 series

Issue Controller labelling and documentation does not describe how to connect expander modules or which modules are supported. Product Line EcoStruxure Security Expert Environment Security Expert SP-ACX SP-ACX-V2 SP-O8 SP-I16 SP-MRDM2 SP-RDM2 SP-I01 SP-IO84 SP-MI16 Cause Documentation is scheduled to be updated but due to UL certifications for some of these documents the process may take some time to complete. Resolution Expander modules are able to be connected to the SP-ACX and SP-ACX-V2 controllers. There is no restriction to the type of Expander Module, all modules are supported unless specifically stated that they are not. The Expander Module network is connected to the RS-485 port on the right-hand side of the controller just above the Digital Outputs port. This port should be labelled with N+, N-, NA, NB and is to be wired up as per the below diagram. Expander Module RS-485 port

Issue Steps for Troubleshooting Readers Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Readers are offline or not returning the correct card data Resolution Common Issues Issue Solution My reader is not returning any data when I present a card Check to make sure the technology card you are using matches the requirements of the card reader. A prox card will not work on an iClass reader. Check the Reader wiring to confirm CLK and DATA on wired correctly. Check that the Reader addressing matches the reader port. Check the power being supplied to the reader. Multiclass readers cannot be powered off S2 (green boards). They require an external power supply. Bluetooth readers cannot be powered off the S2 (green) boards. The power required by the Bluetooth readers is directly related to the range at which the Bluetooth readers are programmed to work. My reader is returning different results every time I swipe my card. Check the power to the reader. If the reader requires more power than the board can provide, use a dedicated power supply. My reader is returning the correct number of bits but the encoded card information is incorrect. Check to make sure your CLK and DATA wires are not switched. If the CLK and DATA wires are switched the 0's and 1's will be inverted causing the card number reported to be wrong.  My reader is returning the correct number of bits but the raw HEX data is all 0's.  This is most often caused by a bad reader or a bad port on the Mercury board. Check the reader wiring and power first, then try the reader on a different port.    My EP1501 uses the Reader 1 port for my SIO, how do I utilize the on-board reader? The on-board reader for the EP1501 is placed on the internal port and is physically placed on Reader 2 (TB3); it should still be addressed as reader address '0' in Feenics. I wired my reader to Reader 1 on the board, what's my reader address? All reader addresses are -1 from the physical port the reader is wired to. Reader wired into Reader 1 is address 0. I don't understand what to set my offline access method to. No Change: Reader access will remain in the 'Online Access Method'. Facility Code Only: Only the facility code is required to receive and access granted event. Unlock: The reader will unlock during its offline state. Lock Down: The reader will be locked down during its offline state. OSDP Reader goes offline when I select 'Secure Channel'. From the top menu bar select 'Start Linking Mode'. The OSDP reader will come back online. Please Note: The OSDP reader must be new or never have been configured for Secure Channel previously. If it was previously configured for Secure Channel it will need to be reset with a config card. My Engage NDE/LE lock is showing a Magnetic Tamper Follow the manufacturers instructions to calibrate the door sensor. My reader is posting "Access Granted - Not Used" events. This can happen for two reasons. First, the cardholder badged at the door but never opened the door to enter. Second, the door does not have a door contact wired at the door and one is programmed into the system. Since there is no device telling the system if the door was used, the system reports no door use. My reader is posting "Access Denied" events immediately after "Access Granted" events. Whenever troubleshooting event data always be sure to expand the event message to learn more. If the event is returning data is without a card read following the first access event, it suggests there may be power coming back into the comms, or are sending feedback into the comms loop. You can test this by Does removing the load (pull the output/strike) oof the terminal render the same results? Is there any change when placing the reader directly onto the Mercury board? A thorough investigation of the power wiring on the board will help isolate the location of the issue. My reader is posting "Access Denied - Incomplete Card or PIN Sequence" The Card and PIN reader mode requires a valid PIN sequence followed by a valid card read. The Incomplete Card or PIN Sequence can occur Only the card was presented to the reader. Only the PIN Code was entered at the reader. The card was presented before the PIN code was entered. Keep in mind, if someone enters a random PIN sequence at a reader and happens to guess a valid PIN but does not present a card, this event will show. The reader is producing an "Unidentified Person on Site" event. This event is produced when a controller grants access at a reader to a cardholder that is on the controller database, but that is not currently within the Feenics Database. This can happen if a controller missed an event when a person was deleted from the database. The system will delete this card from the controller after this event. The next step is to identify the person and remove them from the building. The reader is posting "Access Denied - Invalid Facility Code" but showing the correct Facility Code in the expanded event data. This can occur if the Card Format programmed with the appropriate Facility Code on the controller does not have the correct parity bits for the card being used. The Mercury Service checks the Card number, the Facility Code, and the parity bits in that order. Due to this, when creating a card format, the parity bit is often the last part of the Card Format to be checked. Access Denied - Card/Pin Not Found The User does not have access to the door. Add the User to the door through an Access Level    

Issue Unable to bring interfaces(downstream devices) online, showing as unknown Product Line EcoStruxure Access Expert Environment Access Expert in Cloud or On-Premise SSC (Security System Controller) Downstream controllers Cause Offline interfaces can occur under a number of circumstances, below are the most common reasons. The controller is not yet active. Once all interfaces, readers, and I/O have been added, it’s important to remember set the device as active. Interfaces were added to the controller after it was made active. The controller requires a reboot to download the correct configuration. Dipswitches and addressing on the board may be incorrect Check Wiring  Resolution Go through the following steps to get interfaces online Set the device as active (Go go back to the controller page ) Reboot the controller (containing the interface) Check that the DIP switch settings are correct on the controller (see the Mercury hardware manual) Switches 1-5 on an interface module set the address in binary, this means 32 addresses are available (0-31). Users must set the correct address inside Access Expert that matches the DIP switch value. Switches 6 & 7 set the Baud rate, both on for default 38400. Switch 8 should be off to disable AES key encryption. (Communication is instead encrypted over TLS 1.2) Note: The orientation of the DIP switches may be upside down compared to some labels on other connectors, so it's easy to have everything inverted. On this MR52 board, the On label on the connector is DOWN. These dip switches are configured for address 0, baud rate 38400, and no encryption. Check wiring Ensure that the panels are wired correctly. Verify your RS485 communication and refer to the hardware installation guides Verify End of Line Termination Verify End of line termination jumpers are set, refer to hardware installation guides

Issue When a remote I/O module goes offline the JACE will show an "NA" for the analog inputs but the binary inputs from a remote I/O module still show maintain their last value. Product Line TAC IA Series Environment I/A Series MNB 1000-15 I/A Series JACE Cause The BIs from a remote I/O module that is offline are going to an "NA" status if viewed from WorkPlace Tech.  At the JACE an "NA" received from a BI object will be interpreted as a "fault" and the object will show its last value and turn orange to indicate it is in fault. Resolution When a Remote I/O module is off-line its AI and BI outputs will show as NA in WorkPlace Tech. At the JACE an "NA" received from a BI object will be interpreted as a "fault" and the object will show its last value and turn orange.  The BI can be set up to annunciate an alarm based on the fault condition in the JACE if necessary.

Issue When the remote I/O modules (MNB-1000-15) are powered for the first time, the status LED stays blinking red. Product Line TAC IA Series Environment I/A Series MNB 1000 -15 Cause This is a normal operation. Resolution When the associated MNB-1000 receives a database configured with remote I/O modules, it will initiate communication with the remote I/O modules. If it is successful, then the status LED with turn green.

Issue Following an attempt to update firmware, some MNB MS/TP controllers appear to be in a locked-up condition (ie: the status LED is red and blinking). Product Line TAC IA Series Environment I/A Series MNB controllers Cause The device was interrupted before completing the update, which cause the controller to be in bootloader mode. Resolution To perform a successful firmware update it is imperative that once the update has been initiated it must not be interrupted until complete. A successful firmware upgrade must be completed to get the controller out of bootloader mode. However, in most cases when this issue occurs the unit is no longer displayed in the WorkPlace Commissioning Tool device list.  Therefore it cannot be selected for an upgrade. To get the unit to show up in the list, it must be added as an MS/TP slave. This is done under the WorkPlace Commissioning Tool menu selection: File – add MS/TP Slave. The network number and the controller's MS/TP physical address must be known. Once defined as a slave it will appear in the list and can be selected for a firmware upgrade. Note: If a controller shows up in MS/TP slave mode and indicates it contains the latest firmware it will be necessary to downgrade it to the previous firmware version to recover the unit and then upgrade to the latest firmware.  To downgrade the firmware in an MSTP device open its Device Properties, go to the Firmware tab and click on "Update firmware".  On the Update Firmware window check the box next to "Check here to preview or modify the updates to be applied and click "next".  On the Update Details window click on the change button and a window with available firmware versions for that controller will be displayed.  Select the "bin" file for the previous firmware revision and click on the Open button.  Now click on the Start Update button to perform the firmware downgrade.  If successful the controller will show up in the WPCT device list and can be upgraded to the latest firmware. If suspect communications are what caused the update failure, it must be remedied prior to attempting another update. Once a successful firmware update has been completed the unit will boot normally.  The status LED will be green and it will appear in the Device list.

Issue The MNB-70 firmware upgrade displays version v1.130 during the upgrade process when upgrading to v1.430   The firmware included with WorkPlace Tech 5.8.5 will display the correct filename (MNBU70-01430.bin) however the version will indicate v1.130 within the WorkPlace Tech Commissioning Tool. The firmware included with the MNB Series v1.430 Firmware Pack extractor will display an incorrect filename (MNBU70-01130.bin) as well as indicate v1.130 within the WorkPlace Tech Commissioning Tool. Product Line TAC IA Series Environment I/A Series MNB 70 I/A Series WorkPlace Tech 5.8.5 I/A MNB Series v1.430 Firmware Pack extractor Cause An incorrect version of firmware for the I/A Series MNB-70 controller has been included with the WorkPlace Tech 5.8.5 distribution and the MNB Series v1.430 Firmware Pack extractor both released in mid-July 2013. Resolution Replace the existing MNB-70 firmware file with an updated version: Locate and delete the existing MNB-70 firmware files (where applicable): MNBU70-01130.bin MNBU70-01430.bin The firmware files are typically located … Windows XP \Documents and Settings\All Users\Application Data\WorkPlace Tech\Firmware Windows 7 \Program Data\WorkPlace Tech\Firmware Download the updated MNB Series v1.430.A Firmware Pack extractor from The Exchange Download Center: MNB Series v1.430.A Firmware Pack - BTL Compliant.exe Execute the extractor and the files will be extracted to the firmware directory for use with the WorkPlace Tech Commissioning Tool.

Issue After importing a new template into AET, the different folders and objects are all different colors. What does each color represent? Product Line EcoStruxure Building Operation Environment AET Folder View Cause Each color indicates a different status for the object. Some must be resolved before proceeding and others are information only. Resolution Below is the list of the different status colors and their meanings:  Red – Duplicated object. This must be corrected. Green – Existing folder. Orange – Folder with duplicated object below. Black – New object or folder. Blue – Existing object in EcoStruxure system tree Brown – Device that will be created automatically by AET Light Blue – Empty IO Channel

Issue The functionality of the different tools and/or software does not operate as expected. Issues can appear related to controller functionality or possibly issues with how the standard programs work.  Product Line EcoStruxure Building Operation Environment Automated Engineering Tool (AET) Project Configuration Tool (PCT) EcoStruxure Building Operation (EBO) Cause When the latest versions of software and firmware are not being used, previously identified issues can cause problems with downloads or the operation of controllers. In other situations, it is possible that the proper steps or tools are not being used correctly. This could require further instruction and information.  Resolution In most situations, the troubleshooting steps below will address a majority of issues encountered while working with the AET and the standard applications. EBO software and SmartX firmware being used should be at the latest version Between updates and fixes to the software/firmware, you should be using the latest versions found on the Exchange.  AET software should be up to date Between updates and fixes, make sure you are using the latest version of the AET software which can be found on the Exchange.  AET templates should be up to date You can reference the AET Quick Help - Downloading AET Templates video or the SmartVAV: Software Engineering Process document for further direction.  Understanding the proper way to use the Automated Engineering Tool There exist a number of AET Quick Help Videos available on the Community to help with AET user skills. If there are any topics not covered in a video that you are searching for, be sure to leave a post with the new video idea.

Issue The ServerPack installation process does fail to complete on a new PCT installation PCT presents the following error. : 'beee::vm_module::VirtualBox::make_disk_multiattach' due to: 'VBoxManage.exe: error: Cannot change the type of medium 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\docker.vmdk' because it is attached to 1 virtual machines VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The VBoxHardening.Log (\\Users\John Boehmer\VirtualBox VMs\NoteTEst\Logs) is flagging dll flags that are incorrectly signed. supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll [lacks WinVerifyTrust] If an attempt is made to create a virtual instance in VBox the machine fails to run with the following error. Resolution Uninstall all non-essential software applications from the host machine.  In this case, PCT was being installed on a brand new Hewlett Packard PC that had a variety of HP security software.  In some cases, other non-essential applications may need to be uninstalled as well. Once the software was uninstalled PCT was reinstalled over the top of the existing installation. Virtual machines created in VBox could then be started and PCT began to function normally.

Issue When adding Server Packages to a new PCT install, the installation process does not complete.    Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Some security policy is interfering with the PCT installation process. The VirtualBoxDisclamer.log shows the following error     Could not add PCTService to BUILTIN\Administrators.   The lack of the PCTService could be responsible for a range of issues including the failure to install Server Packages. Resolution To learn what is preventing the creation of the PCTService, try manually adding the user to the Administrators group to see what errors might be presented.  Open Windows event log and look for errors that occurred during the same timeframe noted above. 

Issue PCT fails to open, presenting four 'could not connect' error messages.   Product Line EcoStruxure Building Operation Environment Project Configuration Tool Windows 10 version 1909 Windows 10 version 2004 Cause The cause maybe a firewall, scripts or group policy not allowing PCT to install correctly. Resolution First: check the VirtualBox Host-Only Network has the correct IP address. This can be found under: Control Panel\Network and Internet\Network Connections\VirtualBox Host-Only Network #?\Properties\Internet Protocol Version 4 (TCP/IPv4).   Raise a case with your region's IT2929 (UK = 020 7660 2747), requesting IT install the patch to correct the issue. IT2929 have a knowledge base article on the IT2929 system to help their representatives with this issue (KB0014074).   IT2929 will advise you to take a backup of your PCT projects, uninstall PCT and Oracle VM VirtualBox. IT2929 will then install the patch. Re-boot the laptop. Install PCT and Oracle VM VirtualBox (run as administrator). Restore your PCT projects. Re-boot the computer. If PCT still does not work after this, update the CCC case you have or create a new case with Product Support, providing your IT2929 KSR number is you do not have a case.

Issue The user installed the PCT on a machine and after running it, the following error pops up: “VM Module INITIALIZING_ Failed to refresh versions”     Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause An installed and enabled antivirus may have corrupted the PCT installation. Resolution By verifying the PCT Virtual Box logs, we can see the folloiwng error:    ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={xxxx-xxxx-xxxxx-xxxx-xxxx} aComponent={MachineWrap} aText={The virtual machine 'Project Name' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)}, preserve=false aResultDetail=0   This indicates that the antivirus may have corrupted the PCT installation if it remained enabled during the installation. Now the PCT cannot communicate with the Virtual Machine. To resolve this, users will need to re-install the PCT while the antivirus has been disabled temporarily.

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 During the installation of the EBO package, an error is displayed about PCT_temp.vbox already in existence.   ERROR_(3), UNABLE_TO_EXECUTE__COMMAND(99), reason=VBo xManage.exe: error: Machine settings file Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Leftover folder/file from previously failed installation Resolution Close PCT if running Take note of the folder/file that the error refers to, in this case "C:\Users\sesaxxxxxx\.VirtualBox\PCT_temp\PCT_temp.vbox Make a backup of the folder/file as a precaution (in case it has to be put back) Delete the folder or file, in this case, delete the PCT_temp folder Re-launch PCT and attempt to install the EBO package once again

Issue Can not logon with the Mobile App Building Operation Technician Tool.  Logon screen appears but app closes after selecting Logon No objects are displaying in my Custom View folder or other locations  Can not view or acknowledge alarms My alarm display colors as set in Workstation are not displaying correctly in the mobile app  Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool 1.0.0 / 1.1.0 Building Operation Enterprise Server and SmartX Server 1.9.3 and below Cause May be various cause that are not allowing the Mobile App to connect to the server (Enterprise or Automation Servers), including EcoStruxure Web Services (EWS) Configuration Setting, folder names, User permissions and Alarm configuration.  Please review the different options below for assistance. Resolution Please note: Mobile experience to be replaced with EcoStruxure™Building Operation v2.0 WebStation For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool   When logging into the Technician Tool it times out This has been seen before and was caused by the Windows Firewall. If you are able to ping back and forth between the enterprise server and iPad/iPhone, then it may be a firewall issue. You can either shut down the Windows Firewall or use Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port to set up firewall rules.  Unable to connect to server or "Contact  technical support" message given When logging in to the Technician Tool, specify the HTTPS port in the SERVER field (EX: 192.168.10.20:446).   The mobile app uses the feature from Building Operation StruxureWare call EcoStruxure Web Services, as such a majority of issues can stem from this setting.  If you are having issues logging into the Enterprise Server or Automation Server using the Technician Tool check the following: Software installed on both the Enterprise and Automation Servers must be 1.3.0.938 or later? Ensure the EWS Server Configuration settings are enabled in the server. As a minimum Serve Value and Serve Alarm must be set to true Browse allows object to browsed if not set, no objects will be displayed Ensure the user has sufficient permission to log in and MUST be member of the default domain Values are not displaying in the Custom View folder or other locations Custom View folder must be located in the root directory of the Enterprise Server Check the EWS Configuration settings and ensure Browse is set to true - refer to item 2.2 above. In the EWS Configuration there is a tab labeled "Filter Hardware Folder"; Filters can be assigned By Path or By Object, check that the nominated folder or object has been filtered. Can not view or acknowledge alarms In the EWS Configuration settings ensure that the Alarm Acknowledge setting is set to true. Also check that the Alarm has no additional 'Enforcement', such as Cause / Action - these alarms can only be acknowledge through Workstation. My alarm display colors as set in Workstation are not displaying correctly in the mobile app Unfortunately the Alarm colors are hard coded within the Mobile App - this feature may be provided in a future release.  Date for this is currently unknown.

Issue Where can I find information on EWS? 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 SmartConnector Cause Documentation required Resolution Documents can be downloaded from The Exchange Download Center - EcoStruxure Web Services EcoStruxure Web Services Specification can be found at: SmartConnector Server

Issue Incorrect settings in the BCX will prevent BACnet communication. Product Line Andover Continuum, TAC INET, TAC Vista Environment BACnet MSTP BACnet IP BCX Xenta 913 Cause Because the Xenta 913 has a limitation of 127 addresses, the default BACnet Address will most likely be out of range. Resolution The BCX4040 must be addressed properly to allow BACnet communication to the Xenta 913. The setting can be changed on the BCX's Controller Configuration page by accessing the controller via IP address to its web interface. On this page, you will see a setting for BACnet Network ID Comm2 which is the device's BACnet address. This number must be unique on the BACnet Network and must range from 0-127.   To Enable BACnet IP communication: Modify the BACnet Ethernet settings from the web interface. Set the BACnet Ethernet Enabled to Yes Set the BACnet Network ID Ethernet. This is the device's BACnet address. This number must be unique on the BACnet Network. The BACnet Device Id is by default the last 7 characters of the BCX serial number and must be unique to all devices in the Continuum network. Many people try to set the BACnet Device Id field to represent a BACnet address but this is not correct. This setting does not affect the Xenta 913 in any way.

Issue Converting the Velocity Pressure measured by the pressure sensor to Flow velocity (CFM) Product Line Andover Continuum,TAC INET,TAC Vista Environment Air flow measurement / balancing Cause Requirement for converting the velocity pressure to flow velocity (CFM) Resolution To calculate Air Flow in Cubic Feet per Minute (CFM), determine the Flow Velocity in feet per minute, then multiply this figure by the Duct Cross Sectional Area. Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A)   Determining Flow Velocity The easiest way to determine Flow Velocity is to measure the Velocity Pressure in the duct with a Pitot Tube Assembly connected to a differential pressure sensor. The Pitot Tube Assembly includes a Static Pressure Probe and a Total Pressure Probe. A Total Pressure Probe, aligned into the airflow, senses the duct velocity pressure and the static pressure, which equals the total pressure. A Static Pressure Probe aligned at a right angle to the airflow senses only the static pressure. The difference between the total pressure reading and the static pressure reading is the Velocity Pressure. If you connect the Total Pressure Probe to the HIGH port on a differential pressure sensor and the Static Pressure Probe to the LOW port on the differential pressure sensor, then the sensor’s output will be the Velocity Pressure, as shown in the figures below. The Flow Velocity is then determined with the following equation: V = 4005 x Sqrt(ΔP) V = Flow Velocity in feet per minute. Sqrt() = Square root of the number in the parenthesis. ΔP = The Velocity Pressure measured by the pressure sensor Example: Measuring a Velocity Pressure of .75” W.C. equals a Flow Velocity of 3,468 Ft/Min. V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min   Determining Duct Cross Sectional Area After obtaining the Flow Velocity from the previous procedure, that figure is now multiplied by the Duct Cross Sectional Area to determine the Air Flow in CFM. There are two different equations for determining the Duct Cross Sectional Area, one for round ducts and one for square or rectangular ducts. The equation for a round duct is: A = π x r 2 A = Duct Cross Sectional Area π = 3.14159 r = radius of duct in feet The equation for square or rectangular ducts is: A = X x Y A = Duct Cross Sectional Area X = Duct height in feet Y = Duct width in feet. Example: An 18” diameter round duct has a Duct Cross Sectional Area of 1.77 Ft 2 A = π x r 2 or A = 3.14158 x .5625 18” diameter is 1.5 feet, therefore the radius is .75 feet • r 2 = 0.752 = 0.5265 • π = 3.14159 A = 3.14159 x 0.5625 = 1.77 Ft 2   Determining Air Flow in CFM After obtaining the Flow Velocity and the Duct Cross Sectional Area from the previous two procedures, the Air Flow in CFM is determined by multiplying the two: Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Example An 18” diameter round duct with a Velocity Pressure of .75” W.C. has an Air Flow of 6,128 CFM The Flow Velocity is 3,468 Ft/Min. V = 4005 x Sqrt(ΔP) V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min The Duct Cross Sectional Area is 1.65 Ft 2 A = π x r 2 π = 3.14159 • r 2 = 0.752 = 0.5625 Duct Cross Sectional Area (A) = 3.14159 x 0.5625 = 1.77 Ft 2 The Air Flow in CFM is 6,128 Ft 3 /Min Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Air Flow in CFM (Q) = 3,468 Ft/Min x 1.77 Ft2 = 6,128 CFM

Issue Inovonics Wireless Interface problem Product Line Andover Continuum,TAC Vista Environment Inovonics FA7403 receiver Inovonics EN4000 Universal Serial Receiver Cause Inovonics provides an interface to access wireless temperature sensors. The FA7403 receiver can be used to interface with Xenta equipment or Continuum equipment, however these interfaces use different protocols. Resolution The Xenta equipment requires a hexadecimal protocol which corresponds to the FA7403 receiver. The Continuum equipment requires an ASCII protocol which corresponds to the FA7403-ASC receiver. If you have the wrong receiver for the equipment you are trying to interface with then contact Product Support for steps to reconfigure this device. Note: Inovonics EN4000 Universal Serial Receiver**, REPLACES FA7403