Building Automation Knowledge Base

  Issue When upgrading a MP-V from v1.xx to a later release the Box Flow reading is zero when there is a velocity pressure. Product Line EcoStruxure Building Operation Environment SmarX IP controller MP-V   Cause When a MP-V-7A or MP-V-9A is upgraded from v1.xx to v3.xx firmware. The MP-V does not control and the Box Flow reading is zero. The damper will rotate to 100% with a Velocity Pressure reading.   The Balanced k-factor and the Balance flow correction are found to be at zero:       Resolution During the upgrade process the flow data is not retained.   Before the upgrade at v1.xx, backup the flow balance data under the Flow Balance Data object,     Continue and complete the upgrade process, re-hosting the controller and downloading the objects. Finally, restore the flow data.

Issue Replacement of ARE, ARX and ARM rotary actuators Product Line Field Devices Environment Satchwell ARE1xxx Satchwell ARE2xxx Satchwell ARE7xxx Satchwell ARX1xxx Satchwell ARX2xxx Satchwell ARX7xxx Satchwell ARM1xxx Satchwell ARM2xxx Satchwell ARM7xxx Cause Obsolescence of Satchwell ARE, ARX and ARM actuators. Resolution ARE actuator                                                               Replaced by ARE1301                                                                          MD20A-24 (p/n 875 1029 000) ARE1302                                                                          MD20A-24 (p/n 875 1029 000) ARE2301                                                                          MD20A-24 (p/n 875 1029 000) ARE2302                                                                          MD20A-24 (p/n 875 1029 000) ARE2303                                                                          MD20A-24 (p/n 875 1029 000) ARE2304                                                                          MD20A-24 (p/n 875 1029 000) ARE2351                                                                          MD20A-24 (p/n 875 1029 000) ARE2352                                                                          MD10A-24 (p/n 875 1019 000) ARE2354                                                                          MD10A-24 (p/n 875 1019 000) ARE2355                                                                          MD10A-24 (p/n 875 1019 000) ARE7301                                                                          MD20A-24 (p/n 875 1029 000) ARE7303                                                                          MD20A-24 (p/n 875 1029 000)   ARX actuator                                                               Replaced by ARX1201                                                                          MD20B-24 (p/n 875 1025 000) ARX1202                                                                          MD20B-24 (p/n 875 1025 000) ARX2201                                                                          MD20B-24 (p/n 875 1025 000) ARX2202                                                                          MD20B-24 (p/n 875 1025 000) ARX2203                                                                          MD20B-24 (p/n 875 1025 000) ARX2251                                                                          MD10B-24 (p/n 875 1015 000) ARX2252                                                                          MD10B-24 (p/n 875 1015 000) ARX2253                                                                          MD10B-24 (p/n 875 1015 000) ARX7201                                                                          MD20B-24 (p/n 875 1025 000)   ARM actuator                                                             Replaced by ARM1601                                                                        MD20B-230 (p/n 875 1021 000) ARM1602                                                                        MD20B-230 (p/n 875 1021 000) ARM2601                                                                        MD20B-230 (p/n 875 1021 000) ARM2605                                                                        MD20B-230 (p/n 875 1021 000) ARM2606                                                                        MD20B-230 (p/n 875 1021 000) ARM2607                                                                        MD20B-230 (p/n 875 1021 000) ARM2651                                                                        MD20B-230 (p/n 875 1021 000) ARM2656                                                                        MD20B-230 (p/n 875 1021 000) ARM2657                                                                        MD20B-230 (p/n 875 1021 000) ARM7601                                                                        MD20B-230 (p/n 875 1021 000)   Options To fit replacement actuator to an existing MB screwed valve use linkage kit - LMD/MB (p/n 914 1071 000) To fit replacement actuator to an existing MBF flanged valve use linkage kit - LMD/MBF (p/n 914 1070 000)   If 1 end switches are required, the reference is MD-S1 (p/n 914 1060 000)  If 2 end switches are required, the reference is MD-S2 (p/n 914 1061 000)  

Issue InfinityProgram that sets the value of a local string object from the value of a remote string object frequently gets disabled. Product Line Andover Continuum Environment CyberStation CX9900 CX9702 CX9640 CX9680 ACX5720 ACX5740 i2 field devices Cause Passing string objects between controllers does not use the system's Import/Export system, strings are passed by point to point operation which can produce large amounts of traffic on the Infinet field bus. The program will disable if not properly written to account for events in the field bus that will knock controllers offline (i.e. field bus reconfigurations) Resolution Care must be taken when writing the program to 1. Fetch the string value at a reasonable interval instead of in every scan 2. Keep the program from disabling due to communication errors, bus reconfigurations etc, typically an error line (E:) is added to the problem to handle errors graciously. If possible transfer the value via a numeric point so that the I/E system is used as opposed to point to point.

Issue On a fresh install of LonMaker Turbo, inactivated, the first time trying to open a drawing you may get the error:  The object was not found (Subsystem: LNS, #6) Extensions ‘Echelon_LMW_Demo’ Environment LonMaker Vista LNS Cause If you specify a network name with trailing spaces, the LonMaker tool will report an LNS #6 error (object not found), and report an unexpected error. An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. It should be noted that this error can also occur in some implicit assignments. For example, if the network interface to be used has not been explicitly assigned to the appropriate property, LNS will continue using the network interface previously assigned to the ActiveRemoteNI or NetworkInterface property, respectively. In such a scenario, this exception could occur even though no explicit assignment has been made, indicating that an implicit assignment maps to an unavailable object. A monitor set may be created while offnet (System.MgmtMode is set to lcaOffNet); however, a monitor set cannot be opened while offnet. Furthermore, attempts to query the MonitorSet.IsOpen property will get the error "The object is not found (Subsystem: LNS, #6)" when offnet Resolution Getting the activation code and activating the install should clear the error.

Issue NSS program ID changed. Requires upgrade or revert back to old interface. (Subsystem: NS, #171)  Environment LonMaker NL220 Vista LNS Cause If you open the Network Properties dialog, change the network interface from an LNS legacy Network Interface (also called NSI) to an LNS Fast Network Interface (also called VNI), or vice versa, and at the same time change from Offnet to Onnet, the LonMaker tool will report an NS #171 error (NSS upgrade required).  Resolution Change the network interface only -- remain offnet Click OK. Re-enter the Network Properties dialog and then change from Offnet to Onnet

Issue Attempting to commission a controller in an LNS environment results in the following error: Cannot communicate with the device. (Subsystem:  NS, #26) Environment LonMaker, NL220 Cause An NS, #26 error indicates a complete failure to communicate.  Most often this will be the result of physical layer problems.  In some situations it maybe due to a failed controller. Resolution Check the obvious physical layer connections: Is the cable plugged into the laptop to connect to FT-10?  Is the router between the computer and device being commissioned online and communicating?  Are the wires terminated properly at the controller?  Is the controller powered? Are there end of line terminators fitted? Inspect the controller: Are the LEDs blinking as designed? Are you able to receive a service pin from the device? Does an MOT or NXE need to be reloaded to the device? Typical troubleshooting techniques will usually resolve an NS, #26 error once it is understood to be a complete lack of communication at the physical layer.

Issue Error number :      17040 Error description: Invalid format. (Subsystem: LNS, #40) Any tab except "Status" has some strange values. Trying to view or edit some values results in this error. Environment Xenta 102-AX Plug-in Xenta 104 Plug-in LonMaker NL220 Cause A value inside the device has been set with an invalid value.  It could be through an LNS browser, through an M/STAT or just through some glitch when setting a parameter. Resolution The device will need to be recommissioned using default values. CAUTION:  Recommissioning a device with default values will erase any user defined configuration parameters.  Record all important data for the box:  duct area, airflow setpoints, operating parameters, etc. Right-click on the device in the LNS Management tool.  In LonMaker, select Recommission. In NL220, select Repair. Choose "Manufacturer Defaults" for the initial values.  Click OK. Launch the plug-in again.  The values should now be able to be changed to the desired value.

Issue Menta Parser Error when attempting to direct download a Menta application. Warning Reference to unsupported I/O Error in COD file - Error:13 (Y=___ X=___) Product Line TAC Vista Environment Xenta Programmable Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The application may contain an I/O terminal that does not exist in the device type to which the application is being downloaded.  This error could also occur in situations where the same I/O terminal reference is used more than once in the application (this could be on the Xenta or the I/O module). Typically caused by copy/paste. Resolution It is possible to have a Menta application that looks to be error free during simulation or the generation of the XIF file, but when the application is downloaded to the controller and it is being parsed by the device it reports a warning about unsupported I/O and leaves the controller without an application. The error window that pops up when trying to perform the download directly from Menta is attempting to show where in the Menta file the error is occurring.  If you can read the point names that are highlighted it can help direct toward the invalid I/O termination.  The other option is to look in Options > I/O configuration and make sure there are no duplicates or invalid I/O terminations.  For example, a 401 doesn't have any onboard I/O so a termination of M0-K1 wouldn't be valid. Note: It is recommended that all macro libraries have non-connected outputs and constant value inputs to force the user to edit these fields.

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 When doing a LonMaker resynchronization, the operation fails on a certain subsystem or when doing a commission on a controller in Lonmaker an error is displayed: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102) Environment LonMaker 3.X Cause If re-commissioning or downloading and commissioning a controller in LonMaker fails or times out, this issue may crop up. LonMaker assigns the desired neuron ID to a temporary device while performing either of these commands, and if the operation fails, that temporary device will get stuck in the database with the same neuron ID as the controller the user was working on. A successful resynchronization will bring this "phantom device" to light where it can be deleted, but if it is the resynch that is failing, the steps below detail how to remove a neuron ID from a device in the LNS database so it can be deleted. Resolution Try to do a resynch command in LonMaker to get the temporary device to show itself on the Visio drawing. If this works, then the temporary device will show up with a randomly generated alpha numeric name on the same page as the controller you were trying the commission or download. After the resynch completes, delete the device from the page and repeat the commission or download. If the resynch operation fails with: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102), continue. Because the temporary device is in the LNS database, but not on the LonMaker Visio drawing, manual manipulation of the LNS database is required to remove this object. This is done with the LNS Object Browser. First, shut down LonMaker, then click START and chose RUN in Windows and type lnsobjectbrowser and click ok. The Startup Preferences are shown. Set the Client/Server Communication to Don’t change and the Local Network Access to Engineering Mode and then click Ok. After choosing settings in the Startup Preferences menu, the LNS Object Browser is displayed. Press F8 to take the object browser out of read only mode. Browse to the following: ObjectServer/Networks/Your_Network_Name/Systems/ Your_Network_Name/Subsystems/All/AppDevices. Note: Double-click to open each object. Within the APPDevices menu you will see the temporary device with the large alpha-numeric name. Double-click this device to get its properties in the right hand window. Double-click on the NeuronId line in the properties pane of this device and manually set the Neuron Id to 000000000000 (12 zeros) and click Ok. Exit out of the LNS Object Browser and re-open the LonMaker database. Perform another resynchronization of the database, and the suspect temporary device should now show up on the LonMaker drawing. Then, delete that device and re-attempt your work on the original controller.

Issue All Custom Types in an AS-P suddenly disappeared and it is not possible to create any new Custom Types. When trying to create a Custom Type it results in an invalid Custom Type object:   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause For an unknown reason, the Configuration database has become corrupt. Resolution Workaround 1: Do an upgrade of the AS-P to the same version which should fix this issue.   Workaround 2: Restore a backup taken before this issue appeared.

Issue How can specific users be restricted to logging into EcoStruxure Building Operation through Webstation and not through Workstation?   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause There is a requirement that specific users be restricted from logging in to EcoStruxure Building Operation through Workstation but be allowed to log in through EBO WebStation. Resolution It is not possible today to restrict users' access to Workstation or WebStation individually. There is no more information available on user permissions than what is available today in WebHelp and technical guides.  

Issue Does Continuum have an interface to the KNX/EIB protocol? Product Line Andover Continuum Environment KNX Xdriver Cause There is a need to interface to a 3rd party device/system via the KNX protocol. Resolution There is no KNX Xdriver formerly listed for download on the Schneider Electric Exchange. However a Beta KNX Xdriver has been developed for a number of select sites and can be obtained via PSS or your local Customer Care Centre (CCC) There are also third party gateways available in the market that may be able to help with this connectivity. They can provide an interface from KNX to another protocol that Continuum supports natively such as BACnet.     Schneider Electric Wiser for KNX Loytec Universal Gateway

Issue Service Containers crash and Gateways fall offline even after Containers coming back online Product Line EcoStruxure Access Expert Environment Access Expert Hosted software Cause The services crash and are offline long enough for the token to expire. Since these services don't store passwords on the machine, they require an authenticated user to reset the flag. Resolution Open the service containers within AX and untick the Authenticated box and click save.

Issue A script program uses a calculation of the difference between event marker DateTime and the current time to trigger an alarm flag. The alarm flag is initially set correctly but switches off again after 2147 seconds. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Version 3.2.2 Cause The result of the calculation Current Time - FailureTime returns a correct value until the difference exceeds 2147 seconds. At that point the calculation returns a negative value and begins counting upward toward zero. Resolution The Script program was broken.   Once the program was deleted and reimported the same script code consistently calculated an increased time differential. This behaviour is identical to a defect which was fixed in the EBO 3.0.4 release.  In that case it was the controller rather than the program that was at fault.

Issue Integration issues between EcoStruxure Building Operation and Power Monitoring Expert/Energy Expert are often complex and may require more the one PSS Team to resolve.  Investigations may begin on the BMS side but then may move quickly to the EMS team so it would be helpful at that point to gather helpful Diagnostic Data on the PME/EE system Product Line EcoStruxure Building Operation, Power Monitoring Expert, Energy Expert Environment Building Operation Enterprise Server Integration Cause Existing KB articles on EBO and PME/EE integration generally focus on troubleshooting or investigating the EBO side and little data is available in KBs for direct PME/EE investigation. Resolution EMS Support have their own structure of useful FAQs rather than KBs and in this situation there is an FAQ article which details how to extract very useful Diagnostic Date from the PME/EE Server which can be obtained before the support case is escalated to the EMS Expert Team: https://www.se.com/ww/en/faqs/FA275753/   There is also a search function where you can browse through other potentially helpful FAQ articles.

Issue How to run I/NET Seven Software as a local user Customer does not WIndows User logged in with Local Administrator rights to run I/NET Seven Software  Product Line TAC INET Environment Windows 7 Windows 10 I/NET Seven Rev 2.41 and above  Cause The IT department requires that I/NET Seven runs using a Windows "User Group" instead of the usual "Local Admin" Resolution   Define the Windows User Account Temporarily log into the PC with the desired User account using “Local Admin/Administrator” rights. Turn off the “User Account Control: (UAC) following the directions defined in this article Windows 7/10 User Account Control Settings  If this is not done then every time you try to enter an I/Net editor, using the “User” Group you will be asked to login as a “Local Admin” Change the User account back to the "User" Group I/NET Seven Feature Matrix: Review the following table showing all the editors both the “Local Administrator” and the “User” can access with their “Windows” Rights. Note: **The I/Net Editor “DbCreate Functions”. If you log into "DbCreate with the "SQL Server Authentication" then these items will be "Y". If you do not give the "Windows User" the SQL Username and Password then these items will be "NO"   User Account I/NET Seven Operation Administrator  User Install I/NET Y NO Remove I/NET Y NO Upgrade I/NET Y NO I/NET Configuration Y Y       DBCreate Functions     Create db Y Y ** Import I/Net 2X Y Y ** Verify existing db Y Y ** Remove existing db Y Y ** Backup db Y Y ** Restore db Y Y ** Import Docutrend Archive Y Y ** Upgrade db Y Y **       Seven Reports     View Y Y Run Y Y Configure Y Y Save Y Y Print Report Y Y Mount Archive Y Y View Archive Y Y Run Archive  Y Y Print Archive Report Y Y       Archive Configuration     Event Archive Configuration Y Y Run Y Y Trend Archive Configuration Y Y Run Y Y View  Y Y       I/O Server Configuration     Promote Filemaster Y NO Demote Filemaster Y NO Promote Client Y NO Demote Client Y NO  

Issue When attempting to register a system, an error page is shown indicating a server error in the /ebo application   Error Text: Runtime Error An application error occurred on the server.  The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security settings).  It could, however, be viewed by browsers running on the local server machine.  Product Line EcoStruxure Building Operation Environment WorkStation Registration Windows Server 2012 R2 and above Cause While the error message points to an error in the back end server, it is actually due to a setting on the client PC. Enhanced security configurations in Internet Explorer on Windows Server systems, is blocking required content from being run. EcoStruxure Building Operation WorkStation uses Internet Explorer as the built-in browser and is therefore affected by this. Resolution While the enhanced security measures can be disabled altogether, the resolution with the smallest impact is to add the URL of the registration portal to trusted sites in Internet Explorer. Open Internet Explorer Open Internet Options Select the Security tab Click Trusted Sites Click Sites Enter the registration portal URL: https://registration.smartstruxure.schneider-electric.com Click Add Click Close Click OK After doing so, restart WorkStation, and attempt the registration again. For more information, refer to the WebHelp topic EcoStruxure Building Operation Registration Page is not Displayed.

Issue When using a calculation method on a trend log list or trend chart with the period "Month" the timestamp is always on the 16th of each month. See the example below: Why is the time stamp always the 16th and is it possible to change the collection date Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause When doing a calculation in a trend log list or trend chart the timestamp will always be in the middle of the chosen period. Resolution This is currently not possible to change in EBO. Alternative ways of presenting the data are to use Dashboards or Notification reports

Issue Require a relay contact to close when an intercom call is being made. The relay is then wired to an information display with displays to alert personnel of the incoming call.  Product Line EcoStruxure Security Expert Environment Security Expert SX-IPI, SX-IPI-C Cause Require visual notification of incoming calls viewable by operators not currently at the monitoring desk. Resolution In the SP-IPI-C configuration settings, there are a number of options in the "Call State Trigger" setting that can be used to trigger the onboard output during certain conditions. One of these is when the intercom is making a call.  Under Security Settings, there is an option titled Alert Trigger Setting where the call state can trigger the output. Alert Trigger SettingCall State Trigger: enables the output to be triggered by the call state of the Intercom. The output triggers when the call state matches the selected state.   Enable the Call State Trigger and set the value to Calling or Ringing depending on if the SX-IPI-C is making or receiving the call. Call State Trigger Wire the output relay into the SX-IPI-C input. Register the input with Security Expert. See details starting at the Adding the Expander Setup in the Security Expert system section in the SX-IPI-C IP Intercom with Camera Installation Manual. In Security Expert, configure the input to trigger an alarm which in turn will trigger an output. Create an Event Filter and add the following event type to it. Input <ZONE_NAME> Opened Create an Alarm add the Event Filter to it. Create an Area If you want a common output that triggers when any object alarms in that area then set the Alarm Output fields on the Outputs tab. If instead, you want the output tied to the Input Type or individual Inputs then go to the next step. In your Input on the Areas and Input Types tab add your Area to Area 1 field and set the Input Type 1 to Instant. In the options enable Log to Event Buffer so we can see the activations. If a common output for all inputs of the Input Type then; On the Options (2) tab enable the Activate Control Output On Alarm and Deactivate Control Output On Restore options. On the Configuration tab set the Control Output to the output you want to trigger. Else if each input has a separate output then; On the Options (3) tab enable the Activate Input Control Output On Alarm and Deactivate Input Control Output On Restore. In each Input set the Control Output to the output you want to trigger.    

Issue Bindings made under the Infinet interface using Import/Export system (IE) stop updating. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Continuum i2920 Controller Cause Objects under the Infinet interface sometimes lose their Object IDs for reasons that are not yet fully understood. The issue has been seen during up revision of the AS-P from 1.9x to 3.x Resolution Under the Infinet interface, right-click on the Application folder of the AS-P or Infinet device and select "Resolve object ids" The system automatically re-assigns the missing ids Download applicable i2 devices