Building Automation Knowledge Base

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 Upgrade warning and Error Conversion Log Analysis Additionally upgrading an AS from version 1.3 to 1.4 can create a number of unresolved or invalid references. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, ASP, ASB Building Operation Enterprise Server Building Operation Device Administrator Conversion Log Cause When upgrading using the Device Administrator various warning and errors can be seen. Errors will prevent the upgrade, but warning will still allow the upgrade to continue. Starting in version 1.4, new rules have been put in place that will invalidate some bindings that had previously been made in older versions. These rules may cause errors to be produced in the Conversion Log found in the Device Administrator. The three new rules are: Public Numeric/Signal bindings will be dropped. Multiple bindings will be restricted to one. Binding to Local Node NVIs will be dropped. For more information regarding the rule changes made in version 1.4 see Reference Guide and References beginning with 1.4.x. Resolution Instructions on how to perform the Automation Server upgrade and how to obtain the Conversion Log, see Upgrading Automation Servers from 1.3 to 1.4. Breakdown of the Conversion Log The file paths given in the Conversion Log entries will direct you to the location of the unresolved or invalid reference. Depending on the type of entry it is, it may require further action to correct the problem.   Type of entries found in the Conversion Log WARNING: ERROR: Invalid_Property_Reference (destination) (source) Explanation: Either rule 1 or 3 has been broken. If a public numeric/signal is bound programmatically to another object then it violates rule number 1. The public numeric/signal in the program must be changed to an input or output before upgrading the database. If the destination of the binding is an NVI in the Local Node then it violates rule number 3. A change to the configuration of the local node must be implemented before performing the upgrade. In many cases the substitution of an NVO for the NVI will address this issue. Explanation: This binding should not have been allowed in SmartStruxure version 1.3. In the StruxureWare Building Operation Technical Reference Guide, you will find on page 2107 that BACnet priority 6 is reserved for future use. This binding needs to be made to a different priority. WARNING: ERROR: Object_Does_Not_Exist (object). Explanation: The object that the reference is trying to bind to does not exist. In other cases the binding was already broken in the source database so it will remain broken in the target database. The binding fix can be addressed before or after the upgrade. WARNING: Property (property) bound to (property), so binding to (property) is dropped. Multiple bindings are not allowed in SmartStruxure version 1.4 and above. Explanation: The object is being written to by multiple objects and/or programs. This violates rule number 2 and is no longer accepted. After the upgrade, only one of the bindings will be left connected and all others will be dropped. This will require changes to be made to the configuration to maintain the same operation. Note: In some cases this warning can occur due to a default value of a configuration object that is mistakenly interpreted as a duplicate binding. The binding is in fact preserved by the upgrade and no further action is required. WARNING: Discarding incomplete binding for (object) -unknown source. Explanation: Due to a version 1.3 defect, the source version configuration database contains an incomplete binding error. This is not a problem but it may be a sign that someone intended for the property to be bound to something but failed to do so. Therefore, the configuration should be examined after the upgrade has been completed to insure that everything is okay. No information has been lost in the upgrade but check the configuration to rule out any errors in the source version database. WARNING: Property (property) in (object) is Unit configured but is not configurable in the new. Explanation: This property has a selected unit configured in the source version database, while in the target version configuring the unit of this property is no longer possible/meaningful. These errors should be investigated to insure that there has been no negative impact on the operation. Generally this error will not be a problem and will require no further action. WARNING: Property REF in (object) is not defined in the new system, skip REF. Explanation: The REF property prior to version 1.4 held a back-reference to an object or property that was referring to the property at hand. Starting in version 1.4 and on, the back-references are handled by other means and are no longer represented in the configuration database. This information can not be upgraded but this is not a problem and no further action is required. WARNING: Invalid value for (property) in the object, (object). The default value has been applied. Explanation: The value seen in the source version is invalid or can not be found; therefore the upgrade process sets it back to the default value. No further actions needs to be taken. WARNING: The declared instance (instance) is obsolete but contains non-default data which has been discarded. Explanation: If the instance is a SavedUserTokens or System/Remote Server warning then the warning can be ignored. No further action is required. WARNING: Property (property) in (source) is not an acceptable property type and is not configured. Explanation: This has to do with the lead reference for shadow Alarm Control Panels that cannot be properly upgraded due to changes to the type of system in version 1.4. There is logic in place that automatically sets the lead reference to the ES again. This is a warning that can be ignored. Explanation: There have been changes made to the type of system. This change prevents the hidden SynchSource property of the Time Zone setting in the source version of the database from being upgraded automatically. If the lead reference was set for Time Zone in the source database, this may have been erased and will have to be done again after the upgrade. This should be followed up manually. Explanation: The new referencing scheme expects all references to be relative so if there is a full binding path it is perceived as an error. This is not an issue and requires no action. Explanation: MatchedDevice is a hidden property that can not be seen. This warning refers to old items that have not been cleaned out. This warning can be ignored. Note: Also keep in mind that the upgrade process considers any empty link "not an acceptable Property". This error can be ignored, no changes need to be made. INFORMATION: Property "Value" in (location) is Unit configured but is not configurable, default unit is used. Explanation: This property has a configured unit that is no longer allowed to be configured in the target database, a fixed default value is used. This is unlikely to cause a problem, no further action needs to be taken.  

Issue Depicting the differences between Bacnet points and Central IO points. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and lower Cause Explanation of difference in points Resolution Creating Central IO points When you create inputs and outputs in a non-BACnet SmartStruxure system, you simply create the inputs and outputs and then provide programming to control the Requested value. Trends, alarms and graphics would monitor the value property. In a BACnet SmartStruxure system, the inputs and outputs are created under the IO Module in the same way; however an additional point is created in the Application folder under the BACnet Interface Device. On the property page of that point is a field designating the “Associated Value”. You should browse to the appropriate CIO point and select it. At this point all monitoring, display and control of the object should be accomplished with the BACnet point. (It is also possible to make the link between the associated value and the IO value by using the binding tool.) There is no other binding necessary to make the link between the CIO point and the BACnet “proxy” that is created in the application folder. For SmartStruxure versions prior to 1.4 please see the attached document for some implications and proper method of operation for using the IO associated value property: PSS Building Operation Attachment 14040rev2.pdf For SmartStruxure 1.4 and above see Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above.

Issue Communication issues between the Enterprise Server and Automation Servers result in an offline status of the AS. More information is required on how this status is detected.  Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause An AS behaves as if it is online yet shows up as offline in Workstation.  Resolution As of 1.5.0.10001 there is a new model for detecting online / offline servers. Prior to 1.5.0.10001 When a communication error was detected the Automation Server was marked as offline. As of 1.5.0.10001 and Newer An immediate DetectOnline call is scheduled. Only after three failed DetectOnline with an interval of one second we consider the  server to be offline. When offline an alarm is generated.and set the offline status as normal, and also go back to one minute interval for online detection. In 1.5.0.10001 the number of retries and interval is possible to set in server.properties. From 1.6.0 this is configurable from WorkStation. *** Server Communication folder is hidden in more recent versions of SBO See Also: How BACnet b3 controllers are established as being Online / Offline How the communication status of BACnet devices are verified

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 Time synchronisation is often an issue on large BMS installations. A central time signal is normally required to make sure all controllers, terminals or workstations have the correct time. If there is no internet connection available then the time has to be synchronised from a central source. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Sigma Continuum Vista SmartStruxure Windows XP Windows 7 Server 2003 Server 2008 R2 Cause No internet connection available to synchronise the system time. Resolution Important The methods below contain steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. If using Windows XP, please use the following link - http://support.microsoft.com/kb/314054 If using Server or Windows 7 OS, please use the following link - http://support.microsoft.com/kb/816042 This has been tested for Time updates to an AS by simply using the PC IP address as the primary NTP Time Server. If the firewall is turned on you also need to make sure UDP 123 is open. Please note that Windows will add a dispersion to the time that may cause issues with time synchronization, please see Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for details.

Issue Unable to login to AS directly when using Domain user. It is possible to login to AS directly with "Local" Domain and to the ES with same Domain. Receive error "Can not continue because server is offline or temporarily unavailable" even though ES is online. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Domain Cause AS is unable to communicate with the ES to properly authenticate the Domain user.  If the ES is picking up a WiFi IP address instead of the LAN IP address, this can be the cause. All other communications can still function correctly with the ES but the issue occurs when the AS tries to connect directly to query the Domain, it will be using the wrong IP address. Resolution Changed the order of NIC''s in Windows so that the Local Area Connection was first, confirmed the ES had the correct IP address, confirmed the AS saw the change, and was then able to login to the AS directly using the Domain user. See How to set the Enterprise Server IP address for details on how to ensure you are using the correct IP address.  Another thing to look out for is that you are using the correct port number for the ES communications as seen from the AS.

Issue When restoring database, an error will show up, saying that version is incompatible with this server. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause This is usually caused by restoring new SQL database to older version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Microsoft doesn't like to do this. Resolution There is build number matrix for each SQL server version:     RTM (Gold, no SP) SP1 SP2 SP3 SP4 SQL Server 2012 11.00.2100.60 11.00.3000       SQL Server 2008 R2 10.50.1600.1 10.50.2500 10.50.4000     SQL Server 2008 10.00.1600.22 10.00.2531 10.00.4000 10.00.5500   SQL Server 2005 9.00.1399.06 9.00.2047 9.00.3042 9.00.4035 9.00.5000 So check the build number in the error message and download the corresponding version of SQL to restore and be used for I/NET.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue Downloading a Xenta Programmable controller under a SmartStruxure Automation Server LON channel fails with message: "Application Download Failure." Viewing error details, the Progress view window shows "Wrong device version." Product Line EcoStruxure Building Operation Environment Automation Server LON channel Xenta Programmable Controllers Cause Right click on the Xenta controller in StruxureWare Building Operation Workstation. Go to the Xenta tab. Check the Software version. If this is below 3.6, then the controller's .MOT file is out of date and must be updated. Resolution The controller's software version must be at least 3.6 to be compatible with SmartStruxure. Use the Download Wizard to load an updated .MOT file into the controller. See Download an .MOT file into a Xenta Programmable controller for further instructions.

Issue When the EWS interface is created, the Status show "online". However, after clicking on the Hardware > EcoStruxure Web Service > SSLite, the Status will go offline. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause Make sure the SOAP Endpoint field says "ews" and not "EWS". Lua program is a case sensitive program. Resolution Change the SOAP Endpoint field to "ews". For firmware version support in EWS, see Firmware versions to support EcoStruxure Web Services (EWS) in SmartStruxure Lite MPM Controllers.

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 There is a need for Xenta I/O modules to be added as standalone devices on a Lon network. Product Line EcoStruxure Building Operation Environment Xenta I/O modules Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Cause The Building Operation ES/AS structure allows I/O modules to operate without a Xenta programmable base unit. Resolution The following Xenta I/O modules can be added directly once the Lon interface and network have been created: I/O Module DI DI status DO DO override UI TI AO AO override Xenta 421A  - - 5 - 4* - - - Xenta 422A - 4** 5 5 4* - - - Xenta 451A - - - - 8* - 2 - Xenta 452A - 8** - - 8* - 2 2                   * - DI, 0–10 V DC or 0–20 mA, 1.8/10 kohm TI         ** - Status indication only when the corresponding universal inputs (UI) are being used as digital inputs. Once the I/O module is set up for SNVT communication the green LED will flash once every 10 seconds. For more information see Configuring Xenta I/O module inputs when used as stand-alone Lonworks devices.

Issue VisiSat 2.1 Build 196 Service Pack 1 provides the five following corrections: In the ARCnet debug Excel spreadsheet, the property editor can now be run. (Defect 1633) Exporting points to MNView or XBuilder, now allow up to 32 characters for the name and up to 50 characters for the description. (Defect 1706) In StruxureWare Building Operation WorkStation, MicroNet Interfaces can no longer be exported/imported. All MicroNet engineering should be done in VisiSat first and then imported into StruxureWare. (Defect 1765) Newly created blank points lists can now be saved without production an error message. (Defect 1784) Exports to StruxureWare no longer produce Memory leaks. (Defect 1808) Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment VisiSat 2.1 build 196 StruxureWare Building Operation Version 1.4 Onwards Cause Correction of five known defects. Resolution This Service Pack should only be added to VisiSat 2.1.196 Note: When installed, the VisiSat 2.1 Build version/build number increases to 2.1.200. (due to one of the files in 'Program Files'). VisiSat will still show as Build 2.1.196 in Control Panel - Programs - Programs and Features - Uninstall or change program. Installing VisiSat Service Pack 1 =============================== Shutdown VisiSat and the VisiSat-Server. Run "VisiSat 2.1.196 Service Pack 1.exe". Extract to VisiSat installation root drive. (or extract to another location and move the Satchwell folder, created when extracted to the root of the C: drive). To the question 'Would you like to replace the existing file', select 'Yes to All' Restart VisiSat. Download VisiSat 2.1 Build 196 Service Pack 1. See VisiSat version 2.1 Build 196 service pack 2 where information on VisiSat 2.1 Build 196 Service Pack 2 can be found and the service pack downloaded.

Issue When connecting to a Web Service, the connection is not established and the error "403 forbidden" is shown. A Web Service goes offline after having worked previously and the error "403 forbidden" is shown. Product Line EcoStruxure Building Operation Environment Web Service Generic Consume Cause The generic consume Web Service client in SmartStruxure doesn't have a user agent header defined. Some Web Service providers will not or no longer allow that, and denies the request when it comes from SmartStruxure. If the same URL is entered in a browser, the page is shown. The cause of this issue can also be that the Web Service is being polled too often. Resolution Until it is made possible to define a customer user-agent header, you need to use another application to relay the Web Service request. This can for instance be "SBO - Web Service through a Proxy and JSON conversion" from the Exchange Community.

Issue When adding a Simple XML Web Service interface in to SmartStruxure, the following error message is given.  Product Line EcoStruxure Building Operation Environment SmartStruxure Workstation SmartStruxure Web Service Interface Enterprise Server  Automation Server Automation Server Premium  Cause The (403) Forbidden error means that the destination of the XML address being used is denying access.  Resolution Follow these steps:   Verify that the XML address can be reached in a normal web browser.  Contact the provider of the XML web service to gather more information on their requirements.    Note: Some providers require a username and password to acquire their information. In other cases they may require that the HTTP request contain an user-agent header. For example, weather.gov requires the HTTP header and will block any request without it. SmartStruxure does not currently support the HTTP user-agent header. You can check out the Community post SBO - Web Service through a Proxy, JSON and Image conversion as a possible workaround for these situations. 

Issue What is the firmware version that supports EcoStruxure Web Services in SmartStruxure Lite MPM Controllers? Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SmartStruxure 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause SmartStruxure Lite controllers have two variants of firmware depending on the sales channel: Schneider Electric Can2go Resolution EcoStruxure Web Services are only available in Schneider Electric firmware versions and full EWS support is planned for firmware version 2.7.0 SmartStruxure Lite shows offline in StruxureWare Building Operation

Issue Waveforms for PS, AS, and I/O modules Product Line EcoStruxure Building Operation Environment SmartStruxure Site Cause Loss of power and UPS for the StruxureWare Building Operation and SmartStruxure product lines. Should you design a site with Stepped Approximation or Pure Sine Wave? Resolution Concerning the UPS, and in particular the APC UPS 650, this is a good UPS, but the problem is that it would still interrupt the power for enough time to reset the AS. The AS has a 100mS capacity. AS Power supply interruption or failure has a bit more information would be beneficial to read through. A good UPS would be one that is Online or sometimes referred to as Double Online. This means that the power is not interrupted. The APC UPS line that has this is the SmartUPS and the base model is the old 1000XLI. This model may or may not be available in every country, but there would be a comparable model available. APC has been replacing the 1000XLI with various models, but all have the capability to go directly to battery, then back to power once the power is restored (assuming that there is a backup generator or the main power is restored) before the battery is pulled down. The Automation Server is powered from one or several PS-24V units. They have and peak voltage rectification on the input and the voltage waveform should not be an issue as long as the peak voltage is similar to that of a sine wave. If the input voltage is increasing with a very high dV/dt there may be high input current peaks. Those peaks may but not necessarily be reduced by the 230/24V transformer.   Key Concept: Look for a model with the Topology of Line Interactive and the Waveform Type of Sine wave. Picture is simply for example but not required:

Issue Echelon Node Utility with Loytec NIC-USB Network Interface Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Microsoft Windows 7 32-bit Echelon Node Utility 2.04 Echelon OpenLDV 4.0 Loytec NIC-USB network interface Loytec NIC driver version 4.1.3 Cause There is a need to run Echelon Node Utility using Loytec network interfaces. Resolution The easiest way to accomplish this, is to use the NodeUtil Launcher. This program scans the registry for known interfaces. It was created by an active Community member. * Do take note Schneider Electric Product Support does not provide support for the NodeUtil Launcher - for support please write the developer of the tool. Below are two methods to manually achieve this if you don't want to use the tool. Here are 2 methods to run Node Utility using Loytec NIC-USB network interface. Method 1 involves accessing the Windows registry to check the path name of the Loytec network interface. We are not modifying any entries in the registry but as always, we should be careful when we access the Windows registry. Using Windows registry incorrectly can cause serious problems that may require you to reinstall Windows. Method 2 will configure the Loytec NIC-USB to use LON1. If you have used an Echelon LonWorks interface as LON1, you will need to detach it before you can use this method. Method 1 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity Run Windows registry editor (Start > Run > regedit). Navigate to the path HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\DeviceDrivers. The interfaces will be shown here. Look for the interface with '_LDV'. Run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil using the command nodeutil -D"". See example below. Method 2 Run Loytec LConfig tool. With the Loytec NIC-USB network interface connected, go to the 'USB' tab and test the connectivity. Click on the 'Advanced' button. Check the option 'LON1 Support for device' and select the appropriate device in the drop down list. You will need to reboot the computer for this to take effect. Once the computer has restarted, run Windows Command Prompt and navigate to the Node Utility software directory (whichever directory you have put Node Utility) and run NodeUtil. Node Utility should now run.

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 Is there support for the C-Bus protocol in StruxureWare Building Operation? How can we integrate C-Bus into StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0, 1.1 and 1.2. Cause Requirement to integrate C-Bus protocol into StruxureWare Building Operation, Automation Server or Enterprise Server. Clipsal C-Bus integrated service provide two gateways (BACnet / OPC), that may provide a suitable integration option. Resolution StruxureWare Building Operation does not directly support the C-Bus protocol at this point. Currently Schneider Electric Buildings integration with the C-Bus protocol is typically through the Xenta 913 (See Tip and tricks for communication between Xenta 913 and C-Bus on how this is achieved). When Interfacing the Xenta 913 to the Building Operation offerings you must create connection objects to and from the C-Bus objects via SNVTs, which need to be separately created within the Xenta 913 XBuilder project. Once these SNVTs are exposed, then the Xenta 913 can be added on the LonWorks network allowing the unit to be discovered as a LonWorks device (i.e. only acting as a third party LonWorks device). There are also two offerings provide by the Clipsal Integrated Services division that can be integrated with Building Operation, these are:   1. C-Bus BACnet Gateway (5000BACnet) The C-Bus BACnet Gateway is an embedded device that provides a field bridge between Clipsal C-Bus lighting control systems and the BACnet open protocol. The C-Bus BACnet Gateway provides 255 group addresses from a single application address. The C-Bus BACnet gateway supports the reading and writing of BACnet objects between C-Bus and BACnet and is supplied pre-configured from the (Clipsal) factory. Below is the link to detail of the C-Bus BACnet Gateway (5000BACnet) https://www.clipsal.com/Trade/Support/Software   2. C-Bus OPC Server For larger C-Bus systems (i.e. >255 group addresses) then the C-Bus OPC Server provides a gateway for C-Bus and the OPC Data Access protocols. Current releases of Building Operation does not support OPC, so you will require either an OPC to BACnet or OPC to LonWorks application which can be purchased through third party vendors. SCADA Engine is the preferred Clipsal BACnet OPC Client solution used. http://www.scadaengine.com/ Even though this solution is focused on BACnet, it may also be possible for a similar solution using LonWorks. Below is the link to detail of the C-Bus OPC Server https://www.clipsal.com/Trade/Support/Software There are additional requirements for each of these options that may need to be considered, it is best to discuss these directly with your regional Clipsal representative.