Building Automation Knowledge Base

Issue What 10k Thermistor sensors are compatible with the I/A Series MNL and MNB families of controllers? Product Line TAC IA Series, Andover Continuum Environment I/A Series LON Controllers (MNL-xxxxx) I/A Series BACnet Controllers (MNB-xxxxx) Continuum 10K T3 Sensors Cause Specification information Job spec requires a specific family of sensors.  Need to know how to compare the TC curves. Resolution Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series.  NOTE: These sensors are no longer available for purchase. The TW2XAXK is the replacement Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S.Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span.   This includes the Continuum 10K T3 sensors.  The table below shows that the resistance in its normal operating range is within a few ohms of the TSMN non 11K shunted sensors.  The Continuum sensor can be used with a parallel 11K ohm resistor. The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here.  Please note that the controller may not be able to use the full temperature range shown in the table.    

Issue How to put in multiple email addresses for emailing from Email Notification Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Site with at least one ES or AS Cause A good example of when multiple email addresses are required for alarm notifications is a facilities staff. You may need critical alarms to go to several people at once to make sure they are handled in a timely fashion. Note: Consider configuring Building Operation to email a distribution list as opposed to several email addresses. That way the IT department can handle making changes without having to access the building control system. Resolution in the email address field of the Email Notification, addresses should be separated with only a semicolon. No space is permitted between the addresses. Note: This will not work from Webstation, only from Workstation. Example: user1@gmail.com;user2@gmail.com;user3@gmail.com

Issue Continuum installer throws a Error 1904, dll failed to register error during the installation process. Environment Continuum Error 1904 Failed to Write to Registry. Cause Virus protection is preventing the Continuum install from writing a .dll to the registry. Resolution Uninstall Continuum completely. Reinstall Continuum with all malware protection software disabled and using a Local Administrator user account. Check the compatibility matrix to ensure that the Windows OS you are using is compatible with the Cyberstation version

Issue MP-V Air Flow is reading zero flow despite the Velocity Pressure having a positive value. Product Line EcoStruxure Building Operation Environment MP-V-7A, MP-V-9A, RP-V-4A, RP-V-5A Variable Air Volume Data Cause The Air Flow value is an internally calculated value based on the Velocity Pressure. There are a number of values involved in that calculation that could result in no flow. Resolution Validate Variable Air Volume Data > Flow Balance Data > Rated box flow. The rated box flow defaults to 0 ft³/min in a new controller and must be replaced with the rated flow at 1.0inH₂O (provided by the box manufacturer). Compare Variable Air Volume Data > Velocity Pressure > Value to the Zero flow threshold. Any Velocity Pressure below the threshold will result in no flow. This threshold defaults to 0.008inH₂O. Check Variable Air Volume Data > Properties > Balanced k-factor and Balanced flow correction factor. If either of these values are at 0, there will be no flow. These values cannot be directly written to and are only the result of a flow balance calculation. To get them to update: Go to Variable Air Volume Data > Flow Balance Data and record all balancing data (you will need to manually re-enter it later). Set all 7 balancing values to 0 - Rated box flow, Box/Hood measured maximum/intermediate/minimum Right-click on Variable Air Volume Data and Download Re-enter the valid balancing data. The balanced k-factor should now show a value close to the rated box flow and the balanced flow correction factor should show a multiplier ideally between 0.5 and 2. If the box has not been balanced and no valid balancing data is available, leave the minimum flow readings at 0 and enter the same value into both the hood and box maximums (for example, 1000 and 1000). This will result in a balanced k-factor equal to the rated box flow and a balanced flow correction factor of 1.

Issue There isn't enough documentation on how to disable the different connection protocols. I.e. TLS or SSH. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Cause Increase the security of the system. Resolution SSL Communication Security Settings: You can edit SSL configuration in WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. SSLv1,v2,v3 are all implicitly disabled. In EBO 2022 (4.0) or higher, TLS 1.3 is available and used as default when logging on with WebStation and for server-server communication with HTTPS. TLS 1.0 and TLS 1.1 are by default disabled but can be enabled in Control Panel. WorkStation is using TLS 1.2, disabling it would prevent logging on to WorkStation. In WorkStation, the only valid protocols are shown when you hover the mouse over disabled protocols. See below.   SSH Port: Port used for communication with Device Administrator can be disabled or changed so that the automation server communicates on another port using SSH. It is also possible to disable all SSH communication. SSH communication settings are available in Automation Server Properties – Network Tab, as shown below. Refer to Disabling Port 22 on SmartX Server and Adding an Additional SSH Port for a SmartX Server .  For more Security guidelines,  refer to EcoStruxure Building Management - System Hardening Guide, Security Overview, and Information Technology System Planning Guide 

Issue When a MicroNet 100 series LON controller is upgraded to a MicroNet 50 series LON controller, reference in/out objects and the bindings to the LON SNVT bindings are lost. Product Line Satchwell MicroNet Environment VisiSat Software version 2.1 Builds 137, 148, 148 SP1, 185 and 196. Cause The upgrade process removes various items/objects from the original scheme. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- The upgrade process removes various items/objects from the original bubbleland scheme. See MicroNet 100 to 50 series upgrade precautions.pdf to view more detailed information.

Issue How Permissions works in EBO Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Software Permissions are used to control user activities in a software application. For example, permissions can be setup to manage the type of data and commands the user has permission to within a workspace, panel, or domain. Resolution EBO software permissions comprise path permissions and command permissions. Path Permission: Path permissions give a user or user account group basic permissions to the objects defined in a path. The permission level set on a path applies to all sub levels unless you set a new permission level for a sub level. Command Permission: To make the system even more flexible and useful, you can assign a user account group with special command permissions. Use the command permission to control exceptions from path permissions that allow or deny actions on specific commands. Command permissions will not restrict a user from specific properties of a given window. They function to remove items from Action or Right Click menus. EBO uses the following basic rules to interpret software permission priorities: The path permission settings of lower branches overrule the settings of higher branches within a user account group For example, a user account group has the Read permission to the path /Trend_Logs and Full Access permission to the subbranch /Trend_Charts. Users in the user account group have permission to modify the objects in the /Trend_Charts but can only view the objects in the superior /Trend_Logs. If the path /System has the permission level Read, and the subbranch /Alarms has the permission level Full Access, the users in the group have full access to the objects in the /Alarms path. The highest permission rule wins between user account groups. For example, if a user has inherited the permission to accept an alarm from one group, this overrules settings from other groups that deny the user the permission to acknowledge alarms. The software permissions for a single user account overrule the permissions of any inherited user account group permissions. The path permission rules also apply to the basic commands Create, Copy, Paste, Cut, Move, Rename, and Delete. For example, you only need the Read path permission level to copy an object but you need the Full Access path permission level to paste an object. See the table for more details.       Download Software Permission.pdf, the detailed guide about how permission works in EcoStruxure Building Operation (Formerly known as SmartStruxure) and how to make it work.  Check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.

Issue How do I read unsigned 8-bit (byte) values from a Modbus holding register and represent the analog value in Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In this case, the Modbus holding register is a 16-bit unsigned value that is used by the Modbus device to represent two individual 8-bit values.  The 16-bit unsigned value is an integer with a range of 0 to 65,535 and needs to be converted into two analog values. Resolution Use a Building Operation Modbus Analog Input Point for each value required.  Each object will be configured to read the same Modbus register address with the bitmask value applied before evaluating the value to determine the output. For example: Read Modbus holding register 40001 which is a 16-bit unsigned value and decode as two analog values. Under the Modbus device object - create a Modbus Register Group Under the Modbus Register Group - create two Modbus Analog Input Points Configure each point as follows: Modbus Analog Input Point 40001 (AI-HighByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 8 through 15 Modbus Digital Input Point 40001 (AI-LowByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 0 through 7 Additional information can be found in the Building Operation Technical Reference Guide - Modbus Point Configuration (Bitmask) or WebHelp at Point and Value Configuration

Issue A license violation alarm is shown in the alarm viewer even though the system has all licenses necessary. The alarm returns to normal without any action from the operator. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Enterprise Server / Central contacts the License Server installed on the computer to determine what licenses are available. The License Server will then contact the "Trusted Storage" on the computer which is created when activating the licenses and ask how many licenses are available. The issue comes when the "Trusted Storage" creates some metadata once a day.  The metadata is a file created showing which licenses are used at that moment.  This is not currently used but could be by a third-party client who is interested in the license information for the system.  When the "Trusted Storage" creates the metadata it will be busy and not answer the License Server.  This is when the license violation alarm will be activated.  The alarm will return to normal after the "Trusted Storage" has finished creating the metadata. Resolution An investigation is ongoing. This issue has been fixed in EBO 2022. Please refer to License Violation Alarm 

Issue Clicking on a URL in Workstation gives the error message "Navigation to the webpage was canceled". Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The website owner has added additional code to prevent their webpage from being displayed in a 3rd party application e.g. EBO. However, the webpage can be viewed in a web browser e.g. IE, Chrome or Firefox. This additional measure makes use of a feature called X-Frame-Options and is used to prevent 'clickjacking' and prevents embedding in other websites. In 2009 Internet Explorer 8 introduced a new HTTP header X-Frame-Options which offered partial protection against clickjacking and was shortly after adopted by other browsers (Safari, Firefox, Chrome and Opera). The header, when set by the website owner, declares its preferred framing policy: values of DENY, SAMEORIGIN, or ALLOW-FROM origin will prevent any framing, framing by external sites, or allow framing only by the specified site, respectively. See Mozilla article for further information. Resolution If a web site implements the usage of X-Frame-Options to limit which other web sites it can be embedded into, there is nothing to be done about that. It is the providers' decision, and cannot be circumvented. In Building Operation release 1.9 and later, there are two global policy settings used to protect Building Operation presented web content, so it is resilient against clickjacking. Option 1 - Enable external content to be embedded in WebStation This option must be selected to permit another web page to be rendered in a WebStation <frame> or <iframe>. To protect against clickjacking for all use cases, this option should be turned off. Option 2 - Enable WebStation to be embedded in another site This option permits Building Operation web pages to be rendered in a <frame> or <iframe> from the local server. If this option is selected with option 1, then there is no protection against clickjacking. The most secure and recommended configuration is when both options are turned off. However, when an application requires embedded web content, one or both these options can be turned on. Since this is a global policy, these settings will affect all embedded content. If only some content is required to be embedded then there is no solution or workaround within EBO unless the website owner can remove or change this feature.

Issue EcoStruxure Building Operation allows using a period embedded in the name of an object (i.e My.AnalogValue) and  the name of a binding variable in the Script program cannot contain a period.     In the Script program all the periods in the binding variable names have to be changed to a different character such as the underscore (_).   This in turn causes a problem for a programmer that has created many objects using the period in the names as it is now NOT possible to use the default name matching binding template. Product Line EcoStruxure Building Operation Environment Script Programs Enterprise Server Automation Server Cause Script programs do not allow a period '.' in binding variable names because the period has special functionality in the Script compiler. Resolution Create a new path matching binding template or edit an existing one to map the underscore to the period.     Here is a second example:   Name of point/value contains embedded '.' as well as spaces      This is what the binding variable would look like in the Script program   and here is the Path Matching Template

Issue Continuum Graphics (Pinpoint): How do point updates take place and how can I change the update interval and polling speed? Is it different for BACnet points? Product Line Andover Continuum Environment Pinpoint Graphics Bacnet Cause How do point updates take place and how can I change the update interval and polling speed? Resolution In Cyberstation V1.71 and greater, the graphics polling engine was significantly changed. Prior to this change, the Pinpoint application would poll the points within its graphic file directly. If several graphics were open, each graphic would perform its own polling, This engine also applied to Web.client. Each control on the graphic had a separate selection where you could set the polling rate on a per-point basis on the miscellaneous tab of each control. This was the only method to adjust the point polling interval. The main reason for the graphic engine change was for Web.Client graphics. Slow networks, multiple browsers accessing the same graphics, and slow browser machines could make Web.Client graphics unacceptably slow.   The current method to get data into graphics involves a separate graphics polling engine per workstation. When one or more graphics are opened on a workstation or a Web.Client IIS server, the graphics register the points into the polling engine on that workstation. The polling engine then begins updating the values and sends the data to the Pinpoint/web.pinpoint clients. After initially sending all the data values to the graphic, it then only sends the data that has changed since the last update in an XML document format. If several graphics are requesting the same point values, the data is only polled once for all the Pinpoint clients on that workstation or Web.Client. Efficiency was also achieved by registering the points in the polling engine which allowed the polling engine to decrease the number of data requests by 50% to retrieve the same data.   There are now additional settings to adjust the polling rates in a graphic. #11 General preferences "Time interval between requests" This is a global setting and affects all workstations. By default, all polled points which are in the polling queue are sequentially updated at a continuous rate with a default delay between requests of 30 milliseconds. It is often recommended to set this to 100ms (Additional considerations below  under Multiple Cyberstation graphics performance)   General Preferences are accessed by Right Clicking on the Continuum icon in the Windows system tray and selecting General Preferences     There are also a pair of settings in the workstation preferences: #24 Pinpoint active polling rate #25 Pinpoint inactive polling rate These settings are for each workstation individually and do not affect the polling rates of the polling engine, but merely determine how often the graphic requests data updates from the polling engine based on whether a panel is or is not the active window. Typically these settings can be left at their defaults R&D has indicated that #24 is not used as Pinpoint always uses the inactive polling rate whether the window is active or not. Therefore, adjust #25 "Pinpoint inactive polling rate".  It is recommended to set this to keep this at the default of 250ms.   Cyberstation Preferences are accessed by Right Clicking on one of the Cyberstations while logged into Continuum and selecting Edit   Multiple Cyberstation graphics performance Several workstations may be configured to display graphics that are pointing to the same controllers and the controllers being polled may be on a large Infinet or MSTP network. In this case, the controllers could be overwhelmed by simultaneous data requests from the different workstations, slowing down controller scans, the whole field bus and overall system performance. R&D indicates that when multiple Cyberstation Graphics are used there is some randomness as to how the polling requests are accomplished. If graphic or system performance is an issue, it is suggested that another 30 Milliseconds is added to the general preferences "Time interval between requests" (#11) and then measure system performance and add additional time if needed up to 500ms.   When using this setting it is necessary to consider how many Cybersations would be running simultaneous graphics. For example:4 workstations polling graphics simultaneously with "x" number of points in it for 1 Netcontroller could have about 20 requests per second (determined via Wireshark capture at the NC NIC) 30 ms per X 4 Cyber =120ms added In this case, the recommendation was to set the "Time interval between requests" value to 250ms for performance   Note: Individual millisecond settings in each point do not effect polling for the point. They are not used.   BACnet points Bacnet points can be managed differently. Continuum BACnet points can either be polled the same way that Standard continuum points are polled or by using a COV. Standard polling is done by using the point objects from the "Infinity" side of the object tree. If you want to use COV for the point updates which is much more efficient, you should use the "BACnet Points" in the graphic, from the BACnet side of the object tree. The polling engine will then subscribe for COV updates to the respective controllers. When the graphic is closed the polling engine will unsubscribe the COVs. Third-Party BACnet controllers have an additional method to adjust the poll frequency. If the third-party BACnet controller supports COV subscriptions, Cyberstation will subscribe to these points as COV's like the Continuum BACnet controllers however, if the devices do not support COV's their points will be polled. Since many third-party BACnet controllers cannot withstand frequent data requests, there are two additional settings on the BACnet device object editor. The settings are on the Details tab on third-party BACnet controllers only. 1. Max # of Async requests The max # Async requests specify how many requests we should send before we get a reply to the data request, or how many requests can I queue. Typically this should be set to 1. 2. Request interval in ms  The request interval setting will depend on the device. Does it use Ethernet or MSTP network architecture? Are you running "Enhanced MSTP"? How many third-party devices are on the mstp network that cannot run enhanced MSTP? Typically it would be safe to set this in the 1000 to 5000 ms range based on desired data update rates and the controller's capability to handle the polling.

Issue Unable to connect to a BCX configuration page Product Line Andover Continuum Environment Continuum BCX9640 and 4040 Cause 404 Page not found error accessing the configuration page using the controller IP in a browser Resolution Note: This document is for troubleshooting help, it is not a comprehensive BCX setup guide. Please refer to the BCX1 Technical Reference for detailed setup instructions.   Using a LAN or a cross-over cable? If the BCX is on a LAN and was working before, remove the LAN cable from the BCX and try to ping the BCX. If you get a response then you have a duplicate IP. Same subnet? Make sure DHCP is disabled on your computer. Use a straight-through or cross-over cable to access the BCX directly. Has this cable been used successfully before? Reset the BCX to the default IP. The button is under the cover, top right. Be sure to hold down the IP reset button for about 20 seconds Is the controller in bootloader mode? This can be seen by observing the CPU light flashing rapidly, approximately two times a second (2 Hz at 50% duty). Flashing the application through Cyberstation may fix this and enable you to get back into the controller. Even though access to the config page is not available, the update OS button in Continuum using the controller's Network setting and ACCNet ID may be accessible to perform a firmware upgrade. Ping the IP from a DOS prompt, can the BCX be pinged? Ex. Ping 169.254.1.1 Use Ipconfig /all to see your PCs network settings. The best case scenario is to be on the same subnet or connect directly. Are there multiple NIC cards on the PC? (Ex. Ethernet and wireless on a laptop) Disable the wireless adapter or other adapters. Continuum does not support a multiple NIC card configuration. Run Wireshark to get a capture between the BCX and The PC. Remove power from the BCX and reapply power. When the BCX starts it sends a gratuitous ARP that will indicate the IP address within the BCX. It may be a different IP than expected. Did the issue of not accessing the web page happen after a power outage? Is the CPU light flashing amber and it was flashing green before and no one has flashed the controller? Is the CPU light solid amber? If so, contact support for assistance.

Issue Can Newron NL220 or Echelon LonMaker systems run on a 64-bit operating system? Product Line TAC Vista Environment Windows 7 64-bit Windows Server 2008 64-bit LNS Newron NL220 4.5.12 Echelon  Lonmaker Turbo SR4 Cause Support is  provided for Newron NL220 4.5.13 on 64-bit operating systems. Lonmaker SR4 does provide some support for 64-bit systems. Resolution The current supported operating systems for this environment are as follows: Newron NL220 4.5.12 Windows NT Windows 2000 Windows 2003 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 (32-bit)   Newron NL220 4.5.13 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 32-bit and 64-bit Server 2003 32-bit and 64-bit Server 2008 32-bit and 64-Bit http://www.newron-system.com/index.php?Page=soft&Traite=download&Prod=nl220te (Account needed to view this document) Lonmaker Turbo SR4 32-bit version of Windows 7, Server 2008, Windows Server 2003 R2 with MSXML 6.0 Windows Vista with Service Pack (SP) 1, or Windows XP with SP3.  http://www.echelon.com/support/documentation/datashts/370xx-324_LonMakerTurbo_SR4.pdf 64-bit versions For 64-bit operating systems, please refer to Echelon's Software Compatibility List for restrictions and approved configurations: http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0339-01A   Lonmaker 3.1.3            32-bit version of Windows 98. Windows 2000. Windows XP. http://www.echelon.com/Support/documentation/datashts/370x0.pdf

Issue Cannot bring controller online in Continuum even though all settings are correct. Unable to browse to that controllers configuration webpage but can ping the controller. CPU LED blinking approximately two times a second (2 Hz at 50% duty). Product Line Andover Continuum Environment bCX40xx bCX96xx b3xxx i2xxx Cause The controller is in bootloader mode and has lost its application program. Resolution If the bCX is in bootloader mode, with the CPU LED blinking approximately two times a second (2 Hz at 50% duty), then there are a couple things you can try to do to get the controller back online before sending it back for repair. Basically it has lost its application program and dropped into bootloader mode. Try to uprev the controller with its application firmware to see if that will bring it back online. Attempt to uprev (Update OS) the controller from its device object in Continuum even though it may not show as online. Alternatively uprev the controller using the RoamIO to send the application firmware to the controller. If neither of these options work the controller must be returned to be repaired through your normal RA procedure for your region. (this option may no longer be available, due to the age of the controller) Note: An error code including 6818(hex) (c2026818 has been seen) or 26648(dec) during an attempted download or on a graphic. Example1: Example 2: See a Quick time movie to indicate CPU light modes for controllers that shows the various stages of the CPU LED blink rate.

Issue How can the format of a custom card be determined/understood Product Line Andover Continuum Environment Access Control AC1 AC1Plus ACX Cause The format of access cards is unknown. Resolution The document Understanding custom card formats in Continuum describes how to determine the custom format of proximity cards.  

Issue TAC EM 5 Actuator requires replacement. Product Line Field Devices Environment EM 5 EM5C EM5 Actuator Cause TAC EM 5 Actuator requires replacement Resolution The TAC EM5 Actuator is totally obsolete and no direct replacement is currently available. Details of the TAC EM5 Actuator can be found in EM5 OBSOLETE.tmp.pdf. The TAC EM5 Actuator was capable of use in control systems having alternative electrical wiring connections.   Alternative 1 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA DC positioning signal. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. Details of the S-E MD10A-24 Actuator may be viewed in MD10A S-E.pdf. N.B. The S-E MD10A-24 should be checked for electrical compatibility with other control system devices that it is to be integrated with. It is unlikely that it will be mechanically compatible with the other control system devices such as the Control Valve Body. Arrangements may therefore need to be made for the design and manufacture of a suitable Linkage Kit.   Alternative 2 Actuator electrical connections comprising 24 Vac power supply and 2-10 Vdc / 4-20 mA positioning signal with 16 Vdc output. In instances where the positioning signal is 2-10 Vdc, the TAC EM5 Actuator may be replaced by the S-E MD10A-24. It should be noted however that no 16 Vdc output is available from the S-E MD10A-24 and none can be connected. A 16 Vdc power supply should therefore be installed to provide power to any external Controllers or Auxiliary Units.

Issue When using the Modbus RTU X Driver on RS-485 what cable type should be used and what maximum distance would it give? Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RS-485 XDriver. bCX1, NC2 AS Cause Recommended cable type required. Resolution The Modbus RTU is a standard RS-485 network and you can use the same networking rules as per the Infinet network. As long as the baud rates are set the same you can even use an Infilink 200 or a B Link to act as a repeater. Unless the Third Party device manufacturer specifies different requirements the Belden 9182 or a similar cable that matches the Infinet specification would be suitable, again as per Infinet rules this would typically allow a maximum end to end distance of 1200 Meters. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue What are the proper configurations in the network Poll Service to balance the BACnet packet traffic for better data handling? Product Line TAC IA Series Environment I/A Series Enterprise Server I/A Series ENC and Jace 8000 Cause Improperly defined poll rates, and poll groups in the Poll Service. Resolution This video demonstrates the Poll Service configurations in a Jace (MS/TP and IP) and an Enterprise Server (IP)   About Polling  Polling Statistics  Polling Rate Tuning  About Polling Components   

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue For various reasons, it may be necessary at times to change a b3's Device ID (Object ID) to avoid a duplicate. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) BACnet Cause There is little or no formal documentation on steps to change the Device ID of an existing B3 controller. Resolution As seen in the screenshot below, once a b3 is added to the network, its Device ID, EBO Object ID, can not be changed.  The reason for this is that the Device ID references the device and objects contained within it.  Once the ID is changed, such references will become orphans. To successfully give the b3 a different Instance/Device ID the b3 must be deleted from the MSTP Network in the Building Operation database and recreated   Write down the b3's Serial Number, MAC Address, Model, and BACnet Name before deleting it. Right-click and Export all BACnet Objects within the b3's Application Folder to file (.xml) Delete the b3 from under the MSTP network. Re-create the b3 manually using its S/N, MAC, Model, Name, etc but enter the new Device ID Commission/Download the b3 to get the new ID to take effect Import the File (.xml) exported in step 2 back into the newly created b3's Application Folder Commission/Download the controller again Important: References to the old Device ID will no longer work and must be re-created.