Label: EcoStruxure Building Operation - Building Automation Knowledge Base - Communities

Issue Are DDC Controllers Leadership in Energy and Environmental Design Certified? Environment Site wanting Green Building Council Certification Cause Are DDC Controllers Leadership in Energy and Environmental Design Certified? Resolution The USGBC does not certify particular devices or controls systems such as I/NET, Continuum, or Xentas. LEED focuses on the design of the building and not on its actual energy consumption, and therefore it has suggested that LEED buildings should be tracked to discover whether the potential energy savings from the design are being used in practice. Five basic categories make up the design points system. Totaled together, these points determine your certification level. The level of certification depends upon the total number of points. As you can see, energy and atmosphere along with indoor environmental quality factors make up half of the available basic points. Five categories for accumulating points 1. Sustainable sites.... 26 Points 2. Water efficiency ....14 Points 3. Energy and atmosphere ....35 Points 4. Materials and resources.... 10 Points 5. Indoor environmental quality.... 15 Points 6. Innovation and Operations.... 6 Points 7. Regional Priority.... 4 Points Subtotal: 100 Points LEED 2009 for Existing Buildings: Operations & Maintenance 100 base points; 6 possible Innovation in Operations and 4 Regional Priority points Certified 40–49 points Silver 50–59 points Gold 60–79 points Platinum 80 points and above The U.S. Green Building Council is a national, non-profit organization that works to “promote the design and construction of buildings that are environmentally responsible, profitable and healthy places to live and work” (USGBC Mission Statement). The USGBC created the Leadership in Energy & Environmental Design® (LEED) Green Building Rating System. LEED was fashioned to provide a standard of measurement for defining a “green” building. It takes a whole building approach that encourages and guides a collaborative, integrated design and construction process. The program evaluates and recognizes performance of your buildings in accepted green design categories—Energy & Atmosphere, Water Efficiency, Materials & Resources, Indoor Environmental Quality and Sustainable Sites. Buildings are given a certification rating based on the number of points they receive in their evaluation. The four levels of LEED certification include: Certified Level, Silver Level, Gold Level, and Platinum Level. By becoming certified, building owners are given third-party validation of their contribution environment; qualify for various state and local government incentives; contribute to the growing knowledge base; receive a LEED certification plaque and official certificate; and receive marketing exposure through the USGBC website, case studies, and media  

Issue Microsoft Visual Studio causes Just-In-Time Debugging Environment Windows Operating System Cause Visual Studio is installed on the PC and when attempting to perform a task, an error appears claiming Just-In-Time Debugging.  Resolution To disable Just-In-Time debugging: On the Tools menu, click Options. In the Options dialog box, select the Debugging folder. In the Debugging folder, select the Just-In-Time page. In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script. To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key. Click OK.

Issue How to find the MAC address / Physical Address of a computer. Product Line Andover Continuum, EcoStruxure Building Operation, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment All computers Cause The MAC address of a computer may be required when working on licensing issues. MAC stands for Media Access Control and is a unique identifier assigned to network interfaces for communications on the physical network segment. Resolution Go to the Start > Run.   Type "cmd" into the Open field. In the CMD window, type the command "ipconfig /all". Locate the connection that the computer is currently using (For this example it is the Ethernet adapter Local Area Connection). You will find the Physical Address (MAC address).

Issue Workstation Log on failure. Difficulties with Login, port settings, and Server localhost: 80 8080 443 444 and other ports Product Line EcoStruxure Building Operation Environment StruxureWare 1.2.x.xxx and higher StruxureWare Building Operation Device Administrator StruxureWare Building Operation License Administrator StruxureWare Building Operation Enterprise Server StruxureWare Building Operation Workstation Cause Logging into Workstation, since I have changed my HTTP and HTTPS port setting to avoid conflict, and error is produced when the login fails: Resolution Beginning with StruxureWare Building Operation 1.2 and forward, Workstation uses the HTTPS as the default protocol (to make communication safer).  Below is the Software Administrator screen capture. Notice HTTPS is using port 450 in this example rather than default 443 since that port is used by another program on the computer.    Now when logging into Workstation, change the Localhost to that HTTPS port number. In this case, it is Localhost:450 Note: Remember, Server field in the Login screen shot above is for the AS or ES you want to connect to. To connect to an AS, plug in directly with ethernet cable (see Ethernet port is AutoSensing (No Crossover Cable required)), and put in IP address of AS.

Issue Need to perform autosensing on an ethernet port but do not have a cross over cable. Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET, TAC Vista Environment Ethernet connection to an Automation Server Xenta device ACX BCX Auto-Sensing, Auto Sensing direct connect Auto uplink and trade Universal Cable Recognition Cause Need to direct connect with a straight through or normal patch cable from a computer or laptop to the AS, Xenta, BCX, ACX  Resolution Since 1998, the distinction between uplink and normal ports and manual selector switches on older hubs and switches are obsolete. If one or both of two connected devices has the automatic MDI/MDI-X configuration feature there is no need for crossover cables. Now you can plug your laptop right into the Ethernet port of the device with just a regular patch cable. 

Issue Problems with the speed a script was appearing to run. How to adjust the Variable Connector. Environment StruxureWare Building Operation site with BACnet or LON  Cause Definition of a variable connector Problems with the speed a script was appearing to run Resolution Definition Variable connectors The SmartStruxure system has a base philosophy where different objects and properties are connected using bindings. Bindings do not usually cause any significant load to the system, but in some cases the bindings need to be driven by an external object called a variable connector. The user does not create variable connectors. The system creates variable connectors either when there is no obvious direction of the binding (analog value to analog value, for example) or when passing data between protocols (LonWorks to BACnet or LonWorks to Modbus). Due to load caused by the variable connectors, limit the number of variable connectors according to the variable connectors table above. It is possible to increase this number, but close monitoring of CPU load and memory consumption is needed. Release 1.4 Anticipated removal of Variable Connectors and replaced with a Binding Table. Variable Connectors cannot be removed. The maximum number of variable connectors is (Used when the binding has no obvious direction or when passing data between protocols) Enterprise Server: No practical limit known Automation Server:500 There are 'variable connector' objects in the system folder underneath the server that have a polling time associated with them and these are applied to both incoming and outgoing script variables. They default to 10 seconds polling time so regardless of the setting of a script cycle time it is subject to these polling times. Note: The default value of 10 seconds polling time for values regardless of BACnet, LON or otherwise.  Variable Connectors are automatically created when the bound values themselves are of a kind that lack the logic needed for polling. Editing the binding (by clicking the pencil icon next to the binding list path) indicates that there is a variable connector associated with the binding.   Below is a screen capture for Variable Connector Settings. Transfer Value Click the Force value button and enter the value that you want to force onto the binding. Type Select how the binding is updated. Periodic polling updates the destination value at regular intervals. Change of value updates the destination value only when the source value changes, and only when the change is significant enough. Interval Select the number of seconds between updates. Propagation delta for value changes Enter how much the source value must change to trigger an update of the destination value. Retransmit interval(s) Enter the number of seconds between forced updates. In most cases, you bind a source value to a destination property that is an input variable in a program. The binding is direct, and the input variable actively reads the source value during every execution cycle of the program.However, not all bindings have a destination property that is an input variable in a program. When you create a binding, with a destination property that cannot read or poll the source value, StruxureWare creates a variable connector. Most bindings do not need variable connectors, but when they do, StruxureWare creates them automatically. There are basically three things you can do with a variable connector: Configure polling method Configure polling rate Force the bound value In a direct binding, you do not need to concern yourself with the polling of a bound value. There will be a program execution cycle involved that manages polling. With a variable connector you can configure the default polling settings in the properties of the variable connector. For more information, see Configuring a Variable Connector . Also, in a direct binding, you may be able to force the bound value in the destination property. With a variable connector, you force the bound value in the properties of the variable connector. Variable connectors and their properties are accessible from the Control Panel. There is a Variable Connectors list in the System folder of each server. Variable connectors are also accessible from the Binding point list. LonWorks network variables and configuration properties can be bound to each other in LonWorks bindings. They can also be bound to most points in StruxureWare, such as programs, graphics, alarms, and trend logs, but then StruxureWare bindings is used, not LonWorks bindings.

Issue Time Synchronization in Cyberstation  Product Line Andover Continuum, EcoStruxure Building Operation Environment Multiple Cyberstation Workstations Cause Security or HVAC and want to have exact time stamp from two or more Cyberstation workstations Resolution Continuum uses the Workstation time for events and transactions which are recorded in the database. Time Synchronization with the Server is not critical since they have internal time logs with the SQL database.  Time Synchronization with the Cyberstations so they have the exact time stamp on events and transactions is done by synchronizing the Windows workstation time to either a Network Time Server (NTS) (see Public time sync Servers for the United States) or by a third party software or device. Recommended is the Windows time which automatically synchronizes with the Domain Controller when logging in. If the computer(s) is not on a domain, double click on the clock in the lower right hand corner. This opens up the time settings and has a third tab as shown in image below: Select to synchronize with the Static IP Address of a primary workstation which can be seen by this computer. Visit Google and search for "Synchronize the time with Windows Time service" for your operating system If Internet access is not available, there are 3rd party USB and PCI devices available which synchronize with the Atomic Clock via radio frequency. Check your local listing to see if available.

Issue Changing a value from a WebStation. Environment Web Changing a value Changed value returns to its original value Cause The value appears to have been changed correctly, but when the page is refreshed, or changed and returned to, the original value is shown. Resolution There are two ways to change a value as shown below; 1 - Using the edit option. -  Select "Edit" which is located on the right-hand side of the current value.   The "Edit" box is displayed.     Enter the required value and select "OK". Now go to the lower right-hand side of the window and select "Apply".   2 - Typing over the current value -  Wipe over the current value to highlight it, and enter required value. Now go to the lower right-hand side of the window and select "Apply".  

Issue EcoStruxure Building Operation WorkPlace Tech Editor Supported Microsoft Visio Versions The following error context is encountered when trying to run WorkPlace Tech Editor to edit a program: WorkPlace Tech Editor returned errorClass not registered 0x80040154 REGDB_E_CLASSNOTREG Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation WorkPlace Tech Editor I/A Series MNL, MNB Controllers (MNB - from SBO v1.8.1 and newer) Cause Only the 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. The error is seen when a 64-bit version of Microsoft Visio 2010 is installed. Resolution Currently, only 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. SBO 1.5, 1.6, 1.7 Microsoft Office Visio 2010 SP1, 2007 SP2, 2003 SBO 1.8 Microsoft Office Visio 2010 SP1 (32-bit), 2007 SP2, 2003 SBO 1.9, EBO 2.0, 3.0 Microsoft Office Visio 2016 (32-bit), 2013 (32-bit), 2010 SP1 (32-bit)

Issue Telnet does not come enabled on Windows 7 PCs Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 OS Cause This feature does not come enabled in Windows 7. Resolution Click on the Start Icon and type Programs in the Search Window Click on Programs and Features Click on Turn Windows features on or off When the window becomes populated, check the box for Telnet Client   Click on Ok to apply change, exit Programs and Features window Type Telnet at the prompt and start your session

Issue Interfacing M-Bus meters to Modbus. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma Environment Sigma IC3-Modbus Mbus Modbus Kampstrup Heat Meter Multical 601 Cause Multical 601 M-Bus meters are required to be interfaced with the BMS. Resolution A M-Bus/Modbus converter (RS-485, RS-232 or TCP) and configuration software are required. The converter  and software are available from SyxthSense or similar suppliers. Using the converter and software setup the M-Bus/Modbus system without the BMS system connected. The M-Bus/Modbus converter will automatically assign the M-Bus registers as Modbus registers. From the software note the tables and registers used. Create the Modbus registers as required for the BMS system used. For Sigma - Create the gateway.txt, connect and configure the IC3-Modbus. A sample of the gateway.txt can be downloaded here: MultiCal Modbus Gateway.zip. For further M-Bus information see M-Bus Protocol Information. 

Issue Binding a PVR module in the Function Block Program directly to a "Value" object? Environment Function Block Program FBP PVR module Cause The PVR module is not available to bind in the binding window. Resolution To enable the PVR module to be bound, it must first be made "Public", this is selected when editing the module.     Having saved the Function Block Program, the PVR module can now be bound in the normal way.  

Issue While attempting to activate a purchased license, the entitlement ID shows that it is valid, but there is no available licenses that can be activated, or less available than listed on the entitlement certificate. The entitlement ID or certificate is lost. Unable to return the license in order to activate it on another PC Getting "This Operation is not applicable for Trusted Fulfillments" Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In order to activate a SmartStruxure license, it must be available and unused. If a license is already in use, it needs to be returned before it can be activated. Note that all handling of licenses are to be carried out using the License Administrator. Licenses are not returned or rehosted as it was done for TAC Vista. Resolution Refer to WebHelp article #6687 for instructions on how to return a license If you are unable activate a license because you don't have the entitlement ID or certificate, note the activation ID before you return the license, and send that to Product Support Services in order to get the associated entitlement ID Launch the License Administrator Go to the Diagnostics tab and click the refresh icon in the top left corner. The entry in the list that is labeled Entitlement ID is actually the Activation ID. In the case that the computer has crashed or you are unable to successfully return the license on your own, contact Product Support Services providing the following details: A copy of the entitlement certificate The site name An elaborate explanation of why you are not able to return the license yourself

Issue Trouble synchronizing the time of the Automation Server or Enterprise Server to a NTP server or between each other. Product Line EcoStruxure Building Operation Environment Automation Server(s) combined with Enterprise Servers AS-P, AS-B Cause The AS and the ES do not synchronize time to each other, they must use an external server or be manually configured.  Trouble synchronizing the time of the AS to other AS or ES. Resolution First see Setting up a Local / Internal NTP Server for setting the Enterprise Server up as a time server. The information below is mainly concerned with synchronizing the time setting but not the actual time. Release 1.2.0 and higher - Setting Time - Until the time is set, b3 data will not update in the Watch Window. - Until the time is set, BACnet COV will not be functional. - Automation Server time does not synchronize directly with the Enterprise Server. Instead, all servers can synchronize to the same accessible time server. -To adjust the Automation Server time, time zone, and DST, you have to access the Automation Server through a WorkStation. Overview The Enterprise Server gets the time from the computer it is installed on. In order to check what Network Time Protocol (NTP) server the computer is using, go to Control Panel > Date and Time and click on the Internet Time tab. Here you can click on Change settings... to see which NTP server is being used. To insure that the ES is in sync with the AS controllers, you will want to use the same NTP server for both. For Time Servers in your area visit the NTP.Servers Web. Automation servers Date and Time can only be configured to look at an NTP server or set manually. The NTP time sync on the Automation Server up to version 1.2 is adaptive. The AS will gradually change the time and eventually get fully in sync with the NTP server's time. If the time server is a URL, such as time.nist.gov, then it is critical that at least a Primary DNS is set for each Automation Server, and possibly a Secondary DNS. Without a DNS, the Automation Server will be unable to resolve the URL to an IP address. (note that the DNS addresses are set using Device Administrator by right-clicking the AS and selecting Network settings. Starting in version 1.3 the time in the AS will be set directly to what is provided by the NTP server. The time displayed in Workstation will reflect the time zone of the local computer that Workstation is installed on. All events and alarms will be automatically modified to match the time of the workstation that was used to log into the server. The "Server time" will represent the date and time of this server adjusted  to client local time zone, while the fields below "Server time" represent the settings of the Automation Server. The same applies to a Xenta controller underneath an Automation Server, the time in the controller will reflect the client's local time zone. See example images below.   How to synchronize date and time settings on multiple Automation Servers IMPORTANT:  As stated above, only the time settings are synchronized via the Lead/Shadow configuration, the time itself IS NOT synchronized via the Lead/Shadow but rather by all servers synchronizing with the configured timer server.  The synchronizing of multiple Automation servers can be done with a lead/shadow relationship. You define the primary and secondary network time server settings for connected shadow Automation servers on the Enterprise server. Setting up the Primary and secondary time servers in the ES only passes those configuration settings to the AS controllers, it does not send the actual time and date value. In the ES Workstation, go to the Tools menu > Control Panel. In the Server box, select the Enterprise server that you want to synchronize the Automation server time settings with. Then click "Network time and time zones". Under the Enterprise Server Date &Time tab > Network time synchronization on shadow Automation Servers > Click Enable. In the "Primary time server" field, type the address of the NTP server that you want to synchronize the shadow Automation Servers clocks with. In the "Secondary time server" field, type the address to the time server that you want to synchronize shadow Automation Servers clocks with if the primary time server is not available. Click Save. In the Search box in the top right corner of the Workstation, type "Date and Time" and click Search for the date and time object on all connected servers in your Building Operation system. In the Search view, select the servers with the time and date you want to synchronize with the Enterprise Server time server settings. Click the Show/Hide Property Grid button.  Click the Time tab. In the "Lead object" field browse to (Enterprise Server Name) > System > Time Settings > Date and Time. Click Save. You may need to stop and start the Enterprise server to get the configuration settings to pass down to the shadow Automation servers. Note: In order to set up synchronization of the time zone settings follow steps 7 through 10 with the following exceptions. Set the ES time zone On step 7, search for "Time Zone" instead. Click on the "Zone Info" tab on step 9 instead. Browse to (Enterprise Server Name) > System > Time Settings > Time Zone on step 9.    Tip/Trick -  to see the time of your ES as well as multiple AS controllers: Drag the Server Time, which can be found in the Properties of the server > Basics tab > Status Information as shown below. Click where it says Server time and drag to the Watch window as shown below. It is the AS who is initiating the synchronization so make sure the AS have the correct IP address to the ES and if a firewall exist that the ports is open so the AS can connect to the ES. Make sure the correct IP address is specified in the communication tab for the ES.

Issue Edit a Schedule to make changes Environment StruxureWare Building Operation site Cause Desire to have similarity to the Vista "View All Events" feature Resolution Once an exception in a schedule has been made, the only way to edit that exception being a normal exception or being a calendar, is to actually find a day where exception is active, and then open properties. With WebStation 1.1 we only support Single date exceptions but with release 1.2, we have enhanced with date range and calculated events.

Issue StruxureWare Building Operation uses the old PI-Modbus-300 protocol Environment StruxureWare Building Operation using Modbus protocol Cause Does StruxureWare Building Operation use the MODICON protocol with the reference PI-MBus-300? Resolution Modicon was purchased by Groupe Schneider (which eventually became Schneider Electric) in 1996, way before Schneider Electric bought TAC. The PI that referred to is just a prefix of the technical document describing the Modbus communication protocol. The 300 is the version of the protocol. StruxureWare Building Operation supports a subset of the Modbus protocol. StruxureWare Building Operation does not support all Functions defined by the document specified. Modicon is still the only one that does.

Issue Screen captures for setting up the BACnet BBMD and BBDT BACnet Broadcast Management Device BACnet Broadcast Device Table Product Line EcoStruxure Building Operation Environment Enterprise Server which is using a BBMD (BACnet Broadcast Management Device) for another subnet Cause BBMD and BBDT clarification BACnet Broadcast Management Device BACnet Broadcast Device Table Resolution The BACnet Testing Laboratory listing assures compatibility with 3rd party BACnet devices that are also BTL listed. The BBMD functionality is part of BTL testing if the feature is claimed on the PICS. The BBMD feature has been tested for compliance and compatibility with 3rd party devices. The BBMD is only needed when communicating to BACnet devices on another IP segment (across IP routers). You only need 1 BBMD per subnet (VLAN). Each BBMD will multicast the mapped BBMD within it's own subnet. The only way to pass BACnet packets from one subnet to another is through a BBMD (BACnet Broadcast Management Device). Look at a BBMD as a BACnet router that functions just like an IP Router would but only for BACnet messages. Key Concept: *How many BBMDs can you create with SmartStruxure? Answer: the BBMD table is for distributing the packets as unicast. This tells the acting BBMD who to forward the message to in the BACnet Virtual Link Control layer. This is not to be confused with the article Maximum number using StruxureWare Building Operation (Scalability and Capacity). BBMDs are for distributing packets among subnets at the IP level (not MSTP)  Please find the following screen captures which show the BBMD registration to an Continuum bCX. The BBMD must be in both subnets. In this first screen capture below, we are viewing a Continuum workstation, and configuring it as the BBMD. It will serve as the BBMD for this Subnet. For StruxureWare Building Operation, the BBMD is created on the IP Network of the ES with the IP of the ES.  In this second screen capture below, I am using an Enterprise Server (ES) in the StruxureWare Building Operation software to configure this BBMD. It will serve as the BBMD for this subnet which is a different subnet than the previous screen capture and the Continuum workstation. Next below is the BBMD BDT for the other BBDTs from other subnets.  In this third screen capture, we are again in the ES and configuring the Broadcast Device Table, which refers to the first screen capture of the Continuum workstation. You can see the IP address here is referring to 10.158.64.254.  It is assumed that the IP port number remains the same 47,808 which is the BACnet default If you are creating a BDT entry in a master table type the broadcast distribution mask of the BBMD on the subnet. This configuration happens to be same mask for the subnet. After completing and saving your configuration. Right click on your ES BBMD and select Learn BDT Table. Type the IP address of the BBMD for the BDT you just created. Again, it is assumed BACnet 47,808 is the port (default) Right click on your ES BBMD and select Teach from the menu. The properties of the BBMD has a Teach Status which should change from None to Success. Lastly a 'Discover New BACnet Devices' is run which bring in available devices via the BBMD. In this last screen capture below, highlight the ES or AS-B then on the available tabs List View Device Discovery Date &  Time Communication Properties, select Device Discovery and device type: BACnet devices. 

Issue StruxureWare Building Operation AS status data Environment StruxureWare Building Operation AS Automation Server Cause AS Information program such as CpuUsage, MemUsage, ProductID, Partnumber, Serial, SWversion, and much more. Resolution The attached file can be imported into a AS (with any or the releases 1.1.x  through the current release 1.5.x). It will create two graphics that supply a wealth of operational information. Screenshots are shown below:   After import into your AS, look for System View folder. Open to view the two ProgramInfo and SystemInfo tabs. Please note that you can also see the CPU% and memory usage of the AS by using Building Operation Workstation, highlight the AS, go to the Properties tab and in Basic, the stats are listed.

Issue Configured Loytec LConfig application as a service but still do not get communication from the LonWorks Network. Not able to get Service pin from LON devices connected with Loytec NIC from Enterprise Server Product Line EcoStruxure Building Operation Environment Enterprise Server 1.1 Loytec NIC852 (LConfig Tool) Windows 7 Cause LConfig tool version is too old. The LConfig tool, even if set to start as a service, also still needs to start before the Enterprise Server (ES), otherwise the Enterprise Server fails to establish its connection with the LonWorks interface. For information on how to set LConfig to run as a service refer to Not able to get Service pin from LON devices connected with Loytec NIC from ES. Resolution To rectify the cause 1, click here to verify if the LConfig version is the most recent one. If not please download the most recent NIC - LOYTEC Network Interface Software. To rectify the cause 2, you must set the Loytec (LConfig) application service to be a dependency of the Enterprise Server (ES), to do this follow these instructions: Using RegEdit (or similar) edit the Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\StruxureWare 1.1 Enterprise Server NOTE: For SmartStruxure version 1.3 and above, go to path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Building Operation 1.3 Enterprise Server Locate and edit the DependOnService string Add the text LoytecSrv (service name for the LConfig application). Close the editor and reboot the PC Note: When running the LConfig as a service the LConfig Tool is not available from the System Tray and must be started from the program shortcut, located under Start > Programs> LOYTEC Network Interfaces> LConfig As a quick visual check, to see if configured correctly, you can perform a LonWorks Device Discovery on your Enterprise Server, this will show the NIC which has been defined with a red box (see image below). If these are all blue then you will not be able to receive any communications from your devices. Also remember if using the Loytec LIP devices that these should be configured in Smart Mode.

Issue COVNotification messages in BACnet captures. Product Line EcoStruxure Building Operation Environment BACnet IP network BACnet MSTP network BACnet networks with controllers that support COV (Change of Value) Cause COV increment is an attribute that is available in several BACnet points that is settable and when this attribute COV Increment is left at a setting of zero can cause COVNotification messages appearing as broadcast storms creating un-necessary network traffic. Resolution It is suggested to set the value of the COV increment attribute to something other than the default zero or to a value that is pertinent to the point in question. The COVNotification services are uni-cast messages and can have a many to one relationship depending on how may clients are subscribing to the point. Example: Jobsite has a BACnet OAT (outside air temp) input point with the COV increment of zero. The OAT point is added to the watch window or a binding to a graphic or program. The OAT is changing ridiculously fast due to wind and intermittent clouds. The value is changing by 1/1000 of a degree and each COV (change of value) message is delivered out to any object that is referencing the point. But does the value need to display or do we care if the point changes by 1/1000 of a degree. Let's say that the sites requirement only needs value changes of 2 degrees or more. The COV increment can be set to 2.0 and now the UnconfirmedCOVnotification message would only be sent if the OAT changed by 2 degrees or greater. This alone would reduce 100's if not 1000's of network packets. Imagine a jobsite with the above scenario and 100 different points all with the COV increment of zero. Setting the COV increment to something other than the default of zero is one of many ways to improve BACnet communications and reduce what may appear as broadcast storms on the network.