Label: ecostruxure building operation - Building Automation Knowledge Base

Issue What mode must a LoyTec L-IP be configured to work with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Loytec L-IP Enterprise Server Cause The operating mode limits the capabilities of the LoyTec L-IP when used with an Enterprise Server Resolution Smart Switch Mode Ensure that the LoyTec L-IP is in Smart Switch mode. This is achieved by using the DIP switch settings for switch 1 and 2 in the ON position.     Reset Forwarding Tables Press the status button for at least 20 seconds. This will clear the forwarding group, the subnet/node forwarding, and the router domain table when used in smart switch mode. Important: If the L-IP is operated in smart switch mode and is moved from one location to another or if major changes to the configuration of the network are made, it is recommended to reset the L-IP forwarding tables Important: Wait at least 30 seconds after power-up of the L-IP before pressing the Status Button to ensure that the L-IP has booted properly!     For additional detail please reference the LoyTec L-IP user manual.

Issue What is the password recovery procedure for the SpaceLogic Operator Display if the password is lost? Product Line EcoStruxure Building Operation Environment SpaceLogic Operator Display Cause If losing the password for the SpaceLogic Operator Display there is no password recovery procedure available to recover it. The only option to access the device again is to do a device recovery procedure on the device. When doing a device recovery on the device everything on it, all users, configuration data, and logs will be deleted and a new firmware loaded into the device Resolution Steps to perform a device recovery procedure:   Download the device recovery file (tar.gz file) which is included in the “SpaceLogic Operator Display HMIST6400SL Firmware Package” which you can download from Schneider Electric Exchange Extract files and copy them to a USB stick (Format: FAT) a. Unpack the tar.gz  b. Two unpacks are required, then "aurora" folder should be present c. Copy whole "aurora" folder to a USB stick d. The structure on disk should be: e. aurora (folder)-FIRMWARE (folder)- AURORA.CFG-nand.img Power off OPD (Operator Display) Connect a USB-OTG cable (On-The-Go cable, USB-micro-B to USB-A) to the USB-2 port on the rear of OPD . Note: The cable is like a key, to enable device recovery. Do NOT connect USB stick to cable. Connect the USB stick to the USB-1 port on the rear of the OPD Power on OPD Device will boot to a white screen and display: Recovery Mode Loading nand.img... Writing KERNEL... Writing ROOTFS... Udisk upgrade success! (Loud beep) "Upgrade successfully, Wait to Reboot!" Power off OPD. Remove USB stick and USB-OTG cable Power on device and it will boot to the loaded firmware Firmware version is shown on startup screen.   For more details see video:  

Issue How does Modbus scattered read work? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation (1.5 and above) EcoStruxure Building Operation Modbus Cause Requirement to optimise communication over Modbus to improve performance. Resolution The following is an extract from Web Help. The complete section can be viewed at  Modbus Batch Read Function:   'Scattered read is an enhancement to the batch read function that enables multiple, non-contiguous slave device registers to be read in a single Modbus query. By using the scattered read function, you can enable the Enterprise Server or Automation Server to avoid reading a large block of contiguous registers when it is only necessary to read a few registers. Also, using scattered read avoids the multiple use of group function codes 03 (analog output holding registers) and 04 (analog input registers) in order to read non-contiguous registers. Group function codes 01 (discrete output logic coils) and 02 (discrete input contacts) are not supported for scattered read.   Scattered read is available only for supported devices, for example, Schneider Electric branch circuit power meters with split core CTs. Furthermore, the scattered read function applies only when the Enterprise Server or Automation Server is operating as the master, not as as a slave. You can enable the scattered read function in the properties of all Modbus devices. However, if a device does not support scattered read, the device is polled by the master device in the same way as if you had not enabled scattered read.'   The image below shows the properties dialogue window for a Modbus device and the corresponding setting.  The left is version 3.1 and above, the right is version 3.0 and below where it is referred to as 'Non-contiguous read'.  Refer to the Modbus TCP Device  section on Web Help for more information.     

Issue How are the 'Advanced Polling Configuration' settings under the BACnet interface to be used? Product Line EcoStruxure Building Operation Environment Enterprise Server (ES) Automation Server (AS) Cause These settings can be used to reduce traffic on the BACnet networks that can overload both the EBO server as well as the devices being polled. Resolution The settings are used to specify an amount of time (in milliseconds) that the server should wait after completing a polling cycle on the applicable BACnet network before starting the next cycle. A polling cycle is the set of point being polled on a particular network interface. For example, lets assume that the Minimum polling interval for MSTPA network has been set to 1000 ms, if you are polling 30 points on MSTP port A then the BACnet plug in will do synchronous ReadProperty requests to poll each of the 30 points one at a time. Once the 30 points are polled, (one polling cycle) the BACnet plug-in will delay 1000ms before polling the 30 points again. (next polling cycle) NOTE: The settings apply to polling ONLY and do not affect communications done via change of value (COV) To find a proper value to use, it is recommended that you start with 1000 ms and then adjust the value up or down based on polling performance. If the polled values update fast enough, increase the minimum polling interval to reduce CPU usage. If the polled values become too sluggish, reduce the minimum polling interval until performance returns to satisfactory levels. It may take some trial and error to find the optimum balance.

Issue How to perform the activation of an embedded demo license Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause The embedded demo License is a temporary license used for demonstration purposes, training, site engineering, when waiting on a permanent license order, or license support. This license file has a .Bin extension and can be downloaded from the EcoStruxure Exchange ( ecoxpert.se.com ) and is valid for a limited time (3 months). Resolution This video will demonstrate where to download, and how to activate an embedded demo license on an Automation Server using the Device Administrator.

Issue Internal counter stops counting. Product Line EcoStruxure Building Operation Environment Script Function Block Counter 167777216 Cause When this script is used it stops counting at 16777216. Numeric Output CountOut   Main: CountOut = 16777100 goto Counter Counter: CountOut = CountOut + 1   Resolution This issue was identified in the early days of Continuum and is regarded as a limitation, not a defect. Explanation - Internally the Script handles all numbers as IEEE754 single precision floats, which means that 16777216 is handled as 1.6777216E7. Adding 1 to 16777216 is unrecognizable in that representation. Using an IEEE754 converter at https://www.h-schmidt.net/FloatConverter/IEEE754.html, one can see that 16777216 and 16777217 have the same binary representation. The point at which the counter will stop, will depend upon the value being added each time, so adding 0.9 will count to a different number than adding 1. The counting range can be extended by two or more variables as shown below. Numeric Output CountOut Numeric CountOut1 Numeric CountOut2   Main: CountOut1 = 16777100 goto Counter1   Counter1: CountOut1 = CountOut1 + 1 CountOut = CountOut1 if CountOut1 = 16777216 then goto Counter2   Counter2: CountOut2 = CountOut2 + 1 CountOut = CountOut1 + CountOut2  

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 User of EcoStruxure Building Operation WorkStation used the "Remember me on this computer" option and logged into an account that does not have account rights to logout. Product Line EcoStruxure Building Operation Environment WorkStation Cause A situation such as this could happen either due to inattention of the user or because of planned system design (Kiosk with Building Operation WorkStation logged into a read only account). However it might be necessary due to maintenance to adjust the login option. In the absence of a kiosk situation, it is recommended to always leave the ability for a user to logout by only hiding the toolbar instead of disabling it. Resolution The solution can differ depending on the installation or usage scenario. User has access to log off option Once logged into Building Operation WorkStation use the log off option to return to the login prompt Uncheck the "Remember me on this computer" option. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port Building Operation WorkStation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation WorkStation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. This could result in loss of data while the Enterprise Server is stopped. Delete the Building Operation WorkStation configuration file (named either SBO.ClientUserProfile.bin or TAC.ClientUserProfile.bin for older versions) stored in the computer application data. Deletion of this file will result in loss of custom settings such as column widths and similar customizations.

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 After successfully setting up KIOSK mode to automatically login in to WebStation another user wants to login through WebStation on the same PC. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Cause The GUEST account login URL used with KIOSK mode retains the last user logged in and the WebStation menu bars have been removed so that user cannot "logout". Any subsequent attempts to access the WebStation using the same browser result in being automatically logged in under the GUEST account. Resolution The "KIOSK" link that you create will login automatically with the GUEST account as long as the GUEST account has already been created in the ES/AS. This then must set the "last credentials" in IE for that website and any subsequent connections to that server, even to the direct login URL, result in automatically being logged in with those last credentials. One of the two options below should work to disable GUEST login depending on where your ES is located. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port while Building Operation Workstation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation Workstation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. To be prompted for a login: Disconnect the ES/AS with one of the options above. Then try to connect to the server page at "http:/localhost:444" (or your specific URL:Port). This results in a "this page can't be displayed" (or similar) message. Then start the service, or reconnect cable, and again attempt to connect to "http:/localhost:444". You should be presented with the login page. Do not try to open up the "KIOSK" URL or else this will again login with the GUEST account and you'll be back to square one. The next time you use the "KIOSK" URL it will automatically login with the GUEST account and this will again be used for subsequent logins until the above steps are repeated. Note1: This could result in loss of data while the Enterprise Server is stopped. Note2: Also see StruxureWare Building Operation Workstation Auto Login feature locked if encountering this issue with a Workstation.

Issue Unable to see EWS objects/points under an EcoStruxure Web Services interface Product Line EcoStruxure Building Operation Environment EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause An EWS License may be needed to allow your ES/AS to use EcoStruxure Web Services Resolution Purchase and install an EWS License if required.     Note: The EWS option is NOT required when using EWS to integrate between two Schneider Electric systems or services. Refer to PA-00349 for details.   This includes the new Smart Connector by Schneider Electric which does not require an EWS License but does require a Smart Connector License as usual

Issue How to transfer EBO 2022 or higher data to Azure IoT hub via MQTT protocol Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to configure EBO MQTT interface and Azure IoT Hub, so EBO can  send MQTT messages to Azure MQTT IOT Hub. Resolution The following video will illustrate how to: Create Azure IoT hub and IoT device using Azure Portal Create IoT interface and Azure MQTT client in EBO Configure the MQTT connection Create and configure a data group Test the connection Things you need: EBO 2022 or later with valid MQTT license or demo license (Enterprise Server, AS-P or AS-B) valid Azure Subscription with possibility to use free account during testing. For each Azure subscription one IoT hub in the free tier can be created, refer to IoT Hub | Microsoft Azure Visual studio code to be used to test the connection between EBO and Azure IoT hub, can be download from: Visual Studio Code

Issue Automation / Enterprise Server configuration very slow Attempting to make any configuration changes in the AS such as creating a new point/value or modifying existing objects is extremely slow. Note: This applies to the ES as well although less of a problem since the ES has better resources than the AS. CPU usage as seen in the Status Information of the server is very high. (above 80%) Question marks are shown on many objects in the application folder of third party BACnet devices that have been uploaded to the AS Enterprise Server takes a long time to startup (15 minutes) before allowing users to log on with Workstation.  Deleting the BACnet Interface allows log on with 2 - 3 minutes on a restart. Product Line EcoStruxure Building Operation Environment Automation Server Enterprise Server BACnet Cause Uploaded BACnet devices contain unresolved references to notification class object(s) Resolution Ask for SE.SBO.ES-AS-1.5.0.1501-Hotfix. (SE.SBO.WS-1.4.1.16001-Hotfix for 1.4.1, there is no hot fix for versions before 1.4.1) After applying the hot fix the server should become responsive. The unresolved references can typically be cleaned up by creating a BACnet Notification object in the application folder of the third party BACnet device proxy that reside in SBO and manually setting the Instance ID to 0 (zero) NOTE: Cases have been seen where multiple notification class objects must be created using instance IDs 0,1,2,3,4 in order to clean up all the unresolved references. A few minutes after the notification class object with the proper instance ID is created the question marks should disappear from the icons and created notification class object will show up in the intrinsic alarm property as seen below.   If creating the notification class objects with the above instance IDs does not resolve all the references a backup of the server can be provided to PSS, a PSS/R&D engineer can look directly at the database to determine the proper instance IDs the unresolved references are looking for.

Issue Configuration of multiple BACnet BBMD's over several subnets Product Line Andover Continuum, EcoStruxure Building Operation Environment Bacnet BBMD Cause Bacnet Broadcast communication through IP router Resolution Configuration of multiple BBMD's over several subnets: INCORRECT METHOD For example if there are 4 subnets on the same B/IP (BACnet IP Network): Subnet 1: Workstation setup as a BBMD with an entry in the Broadcast Distribution Table for each BCX Subnet 2: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 3: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 4: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. The BCX's do not reference any points from each other. Since there is no data sharing between the BBMD's, one might think that in each BCX's Broadcast Distribution Table that there would only be a need to add one entry for the Workstations BBMD. Sounds like with this setup we'll reduce traffic by only adding the one entry in each BCX's BBMD Broadcast Distribution Table. The above scenario could in fact slow down a network and cause unnecessary traffic.   The supported method is that every BBMD on a B/IP network have the same routing tables(better known as the Broadcast Distribution Table) as in the below configuration. CORRECT METHOD For example there are 4 subnets on the same B/IP (BACnet IP Network). Subnet 1: WS BBMD with an entry in the Broadcast Distribution Table for itself and all BCX's setup as BBMD on the same B/IP. Subnet 2: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 3: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 4: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. The entry below can be found in the BACnet Standards 2004:   J.4.3 BBMD Concept Each IP subnet that is part of a B/IP network comprised of two or more subnets shall have one, and only one, BBMD. Each BBMD shall possess a table called a Broadcast Distribution Table (BDT) which shall be the same in every BBMD in a given B/IP network.

Issue When configuring a BBMD what is the Broadcast Distribution Mask and what are the valid settings for the field. Continuum EcoStruxure Building Operation Product Line EcoStruxure Building Operation, Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution When configuring a BBMD the BACnet protocol defines two methods of propagating the broadcasts messages to other networks. The two methods are referred to as One-Hop also known as a Directed Broadcast and Two-Hop.   Note: In this article the subnet mask is shown using Classless Inter-Domain Routing(CIDR) notation. An IPV4 address is 32 bits long, CIDR notation defines the number of bits used for the subnet mask. The most commonly used are: /8 or 255.0.0.0 /16 or 255.255.0.0 /24 or 255.255.255.0 /32 or 255.255.255.255 One-Hop With the One-Hop method the local BBMD transfers the message directly to the remote devices via the remote router. In this case the IP routers have to support the transfer of IP broadcast messages to remote IP subnets Figure 1 Figure 1 above illustrates the one-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a message directly to the broadcast address of the 192.168.1.0/24 subnet, it is then up to Router2 to send the directed broadcast to all devices on the subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks. (i.e a bCX hosting an MSTP network on COMM2)   Two-Hop With the Two-Hop procedure a BBMD device transfers broadcast messages to a further BBMD in the remote IP subnet, which then distributes the messages in its local network as IP broadcast messages for its IP subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks.(i.e a bCX hosting an MSTP network on COMM2) Figure 2 Figure 2  above illustrates the two-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a unicast message to each BBMD device on its table, it is then up to each BBMD device on each subnet to send a broadcast that will be heard by all devices on the subnet. Which distribution mask should be used? As mentioned earlier, in order for the one-hop method to work, the router on the remote subnet MUST be configured to process incoming messages sent to the broadcast IP address, the two-hop method on the other hand is guaranteed to work, so when in doubt use the two-hop method. Most sites use two-hop distribution for the reason stated above,, the only obvious disadvantage of the two-hop method is that it is a little more verbose than the one-hop method since the message appears twice on the subnet, once as a unicast sent to the BBMD device and then again as a broadcast sent by the BBMD device. In Building Operation and Continuum the distribution mask defaults to the two-hop method (/32 or 255.255.255.255) How to configure the distribution mask For one-hop enter the subnet mask of the remote network in the distribution mask, the system will apply the mask to the IP address to obtain the broadcast address for the remote network. For two-hop enter 255.255.255.255, this tells the system not to do a direct broadcast and instead do a unicast to the remote BBMD device. Sample distribution mask In the BBMD table of a bCX shown in the screen shot above, BDT #1 and #3 use the two-hop method while BDT entry #2 uses the one-hop method.

Issue The 6 character PIN for the SmartXKiosk has been forgotten so the user cannot exit Kiosk mode Note the PIN is case sensitive Product Line EcoStruxure Building Operation Environment SmartXKiosk Advanced Display v1 and v2 SmartX Controller Cause The 6 character PIN for the SmartXKiosk has been forgotten or lost and the user cannot locate it. Resolution In order to reset your SmartXKiosk PIN, follow the steps below:   In the SmartXKiosk application, click on Exit Kiosk Mode in the bottom right corner of the screen. In the Exit Kiosk Mode window, click on Forgot PIN?. An 8 character Session ID will be generated.  Take note of this Session ID.  Open a ticket with Support to request a SmartXKiosk PIN reset and provide them with the Session ID. Once Support sends you back the Recovery PIN, click Continue on the Session ID window. In the next window fill in the Session ID from step 2. and the Recovery PIN that Support have provided. Click Continue. You can now reset your PIN. Enter your new 6-digit PIN number and confirm it before clicking Submit. The PIN is case sensitive. It must be exactly 6 characters, otherwise an error will occur.  Important Note : The Session ID generated and the Recovery PIN provided to you by Support will expire at midnight on the day that the session ID was generated.  

Issue There is a need to know if Continuum and/or EcoStruxure BACnet support NAT. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum EcoStruxure BACnet BBMD NAT Cause Many sites use NAT for security purposes.  Resolution NAT traversal is not supported in BBMD implementations (Continuum or EcoStruxure). It is an optional feature that has not been implemented. Requests to add this feature should be directed to Product Marketing to include on the backlog for prioritization. Related Continuum article: Can Continuum operate over a NAT Ethernet connection? Ashrae information: here

Issue SmartStruxure comes preloaded with LonMark's resource files. It is not documented what version of the LonMark Resource Files are build into each version of SmartStruxure. Product Line EcoStruxure Building Operation Environment LonWorks LonMark Cause This is missing from the documentation Resolution SmartStruxure Version Resource Files Version 1.2 13.02 1.3 13.02 1.4 13.12 1.5 14.00 1.6 and later 14.00

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open Port 443 (HTTPS) for  the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is: https://schneider-electric.flexnetoperations.com If the site of the old server has issues with the non secure communications or the communications forwarding between the previous and the new server, there is a tool available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used, port 80 is no longer required and HTTP is redirected to HTTPS.

Issue An application will not open in WorkPlace Tech Editor with the following error:   WorkPlace Tech Editor returned errorOperation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))   Product Line EcoStruxure Building Operation Environment Building Operation Workstation (WorkPlace Tech Editor) Visio 2013, 2016, and 2019   Cause Visio crash causes the Add-In for WorkPlace Tech Editors fluent ribbon to become disabled Resolution To re-enable the WorkPlace Tech Editor fluent ribbon bar, perform the following steps: Open Visio.  NOTE: Open Visio, not WorkPlace Tech Editor Select Options from the File menu. From the menu in the Visio Options window, select Add-ins At the bottom of the window, you will see a field that says 'Manage:' with a selection box after it, select 'Disabled Items' and then click the [Go] button. In the 'Disabled Items' window, select 'SE.WorkStation.IA.VisioRibbon' then click the [Enable] button. Close the open Visio windows and sub-windows. After closing Visio, the WorkPlace Tech Editor fluent ribbon bar will be available in WorkPlace Tech Editor

Issue Too much LON communications traffic can cause LON communications errors. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series MNL 800 Building Operation Automation Server Premium LON Network  I/A Series R2, AX, N4 Jace LON Network Cause Sending output LON SNVT values too frequently or more often than reasonably needed. Resolution There are a series of NCI (configuration) objects that control the transmission and reception of these data values on the LON network. One of four NCI objects (nciSndHeartBeatA, B, C, or D) is assigned to each NVO object in the application program. This value regulates the periodic LON transmission queuing of the NVO object values for each binding. One of four NCI  objects (nciRcvHeartBeatA, B, C, or D) is assigned to each NVI object in the application program. This value regulates the fallback timeout for each NVI object value. If a value is not received via the binding in this time period, the NVI object value will revert to its application-defined default value. In an MNL-800 controller, there are two additional NCI objects that are used to regulate the flow of data onto the LON network. The nciMinOutTime object is used to throttle the transmission of all data values queued to be sent via bindings over the LON network. This NCI object sets the transmission time interval between each NVO value being sent on the network. The important fact here is that the product of the number of bound NVO values times this interval (nciMinOutTime) must be LESS than the shortest nciSndHeartBeatX (X=A, B, C or D) interval. For example, if the Send HeartBeat is set to the default of 120 seconds and there are 60 NVO SNVTs bound from this controller, the nciMinOutTime must be set to a value of fewer than 2 seconds.  The recommendation for setting this SNVT value one half the shortest nciSntHrtBr divided by the number of NVO SNVTs bound from the controller.   The nciMinPropTm object is used to regulate the transmission queuing of changing bound NVO object values. This timer acts as a time-based filter to prevent a rapidly changing NVO value, such as a constantly changing temperature, from overwhelming the communication capacity of the LON network. Typically this value is set to a value of 1 to 5 seconds. Additional information can be found in Chapter 6 of the WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). BACKGROUND: This section is provided to give the reader a basic understanding of bound LON communications, as applied to LON controllers in general. Data communications across a LON network is accomplished by using a LON Network management tool to create a binding between a device with a data source (NVO object) and one or more devices with data receivers (NVI objects) in other LON controllers. The device containing the data source will send the bound data value at a periodic rate, as defined by the associated SendHeartBeat NCI object, and whenever the value of that object changes. If the NVI object does not receive a value from the sender (bound NVO object) within a specified time period, as defined by the associated ReceiveHeartBeat NCI object, the NVI object will use a local fallback value until such time as it receives a new value via the binding.

Issue How to search for points, names, or descriptions in EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The EcoStruxure Building Operation search feature can be performed on an entire database or on individual controllers / folders. This can help reduce the amount of time it takes to locate multiple points when creating mirrored points. Resolution How to search for specific names in EcoStruxure Building Operation Right click on the folder, object, or controller you would like to search in and click "Search. Note: When the search is narrowed down to specific areas of the database it will be able to complete the search faster than performing a full database search." In the search field type in the name that you are looking for. In this example the search is for snvt*. This will locate all points underneath the controller that begin with snvt in the point name. After a few seconds, depending on the size of the search area, the results will be displayed in the window to the right. In order to filter the search further, you can set different search parameters under the search field.