Building Automation Knowledge Base

Issue After a power reset, bCX1 comes back online with its comm2 set to a different baud rate than before it went offline, no longer communicating with the connected b3 MSTP controllers. Environment bCX4000 bCX4040 bCX9640 CX9680 CX9900 Cause Controller comes back from power fail and does not have the correct baudrate set which results in loss of communications to all field controllers. Resolution 4.500076 should correct this issue. If not get the controller error log and see if the controller is cold starting. On those controllers that have come back from power fail and have their comm port set to 9600, you can try setting the defaultbaud attribute of that comm port to the desired speed. For this to be saved to the controllers EEPROM you will need to do this from the command line, see the syntax for this below. (replace baud19200 with your desired baudrate) comm2 defaultbaud = baud19200   Or   Write a PE program to detect the baud condition and change the baud to the desired rate

Issue In EBO BACnet device discovery, how is the BACnet MAC address defined? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause A BACnet device is uniquely identified by a network number and a MAC address. Resolution BACnet MS/TP A BACnet MS/TP device supports device MAC addresses in the range 0-127 for masters and 0-254 for slaves. Device MAC addresses are often configured using DIP switches or a configuration tool.   BACnet/IP MAC addresses for BACnet/IP devices are a combination of the IP address and BACnet/IP UDP Port expressed in hexadecimal notation. For example, if a BACnet/IP device is configured with an IP address of 192.168.1.5 and a UDP port of 47808 then:   IP address expressed in hexadecimal is 192 = C0, 168 = A8, 1 = 01, 5 = 05 UDP port expressed in hexadecimal is 47808 = BAC0   Therefore the MAC address will be, C0:A8:01:05:BA:C0   BACnet/SC BACnet/SC nodes are identified by their 6-octet virtual MAC (VMAC) address in form of a IEEE EUI-48 identifier which is randomly generated. A BACnet/SC device attempts to resolve its own VMAC in the network. If it detects another device is already using this VMAC, it will generate a new Random-48 VMAC address and try again.

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 for assistance. Issue In Niagara Enterprise Server versions older than N4.9, the Niagara Service fails to start. Typically the service successfully starts when the 'plat installdaemon' is executed. Product Line TAC IA Series Environment I/A Series N4 Enterprise Server (earlier than N4.9) Cause The Niagara daemon fails to restart automatically after a server reboot Resolution For older Niagara versions, these are two workarounds that may work in some cases:   Option 1:  Go to Start > Run > and type regedit  Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control  With the control folder selected, right click in the pane on the right and select new DWORD Value  Name the new DWORD: ServicesPipeTimeout  Right-click ServicesPipeTimeout, and then click Modify  Click Decimal, type '180000', and then click OK  Restart the computer Option 2: Create a Task Scheduler task that calls the command "net", with the arguments "start niagara" five minutes after boot.   Alternative Solution (reported to work on Niagara older than 4.7): There are two solutions to implement in the Niagara Service. Before performing the settings below you must first have NiagaraD successfully installed. After the computer has rebooted, manually install NiagaraD using 'Plat installdaemon'. Once the service is installed implement the two configurations below. Open Windows 'Services' and then double-click the 'Niagara' service to open the Niagara Service Properties window . You can select to delay the start of the Niagara Service which helps give Windows time to initialize before the service attempts to start. Set the recovery options on the 'Recovery' tab. It is recommended to set all three 'failure' options to 'Restart the Service'

Issue System changes made to a Security Expert server can cause the license to fail. Product Line EcoStruxure Security Expert Environment Security Expert licensing Cause When the SSN license is activated on the Security Expert server a hardware footprint of the server system is created and stored with the license activation. This ties the license to that specific machine, if the hardware footprint changes in the future this will break the license activation.   There may be additional system changes that trigger this but the ones we are aware of that will break the licensed hardware footprint are the following: A change of the Security Expert servers computer name. Normally when we see this the installer is attempting to activate/update the license from a Security Expert client machine instead of the Security Expert server machine. A change in the Network Interface Cards. Changing from a wired to wifi connection can potentially do this. If the server is installed on a virtual machine ensure that the Network Interface Card is assigned a static MAC address. Other hardware changes such as changing Hard Drives, CPU, Memory, Operating System or Motherboards. Resolution If the hardware footprint has changed, breaking the license activation, the SSN will need to be reset and an activation added. Contact your local support to add a registration to the license and clear the hardware profile. The installer will then do a License Update from the Security Expert server to re-activate the SSN.

Issue Not able to select the Find New BACnet Device option in the BACnet folder, to bring new devices online. Environment BACnet Cause Not able to bring online new BACnet devices. Resolution The "Find New BACnet Devices" option should be selected by right clicking on the Root folder. You can not perform this operation from under the BACnet Devices folder.

Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV property  0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

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 for assistance. Issue How to bring a BACnet controller online after restoring a backup Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause Customers may want to take a backup from a site and use it on other setups. If there would be any BACnet controller under the Backup, they may need to know the process of hosting the BACnet controllers under the restored backup on the physical BACnet controllers.   Resolution This video will demonstrate how to bring a BACnet controller online after restoring a backup. NOTE After matching up the Device ID of the BACnet controller under the restored server and the Object ID of the physical BACnet controller, if the hosting status shows “Not hosted”, users need to perform a "Repair Hosting". Please refer to Repair Hosting a BACnet/IP controller 

Issue DC1100 or DC1400 not accepting 0112 passcode to clear alarms or to alter settings. Environment DC1100 DC1400 Cause When the passcode 0112 is used to clear alarms or to alter settings, the code is not accepted. Resolution The controller will require coldstarting. 1. Using the setup menu and view settings, make a note of the settings of the controller. 2. Coldstart the controller by turning the power off, hold down the enter and exit buttons, power on and then release the buttons. The controller should re-initialise and will return to its default settings. 3. Reprogramme the controller with time and date, heating and HWS schedules, and any other parameter required in the set up menu. e.g. no of boilers, HWS linked etc. 

Issue Unwanted hardware and other alarms received at Enterprise Server Product Line Satchwell BAS & Sigma, EcoStruxure Building Operation Environment EcoStruxure Building Operation Sigma Release 4_08 (Build 3_46_57) Cause Unwanted Sigma hardware and other alarms received at Enterprise Server. Resolution Navigate through the “Sigma interface”, to the controller (OSN) that the alarms need to be disabled from. Select the controller’s property (basic tab), Device monitoring can be enabled or disabled.     If you need to disable the alarms for multiple controllers, this can be done by multi selecting the required controllers, opening the property panel and change the setting there.  

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue Need to replace an AVUE, AVUX or AVUM Mark 5 Actuator Product Line Field Devices Environment AVUE5305 AVUE5355 AVUE5304 AVUE5354 AVUX5202 AVUM5601 Cause Need to find a replacement for the obsolete AVUE, AVUX or AVUM Mark 5 actuator, that will allow the valve to be retained. Resolution The AVU* Mark 5 range of actuators can be replaced from the MZ300S range. AVUE5305 replace with MZ300S-24M AVUE5355 replace with MZ300S-24M AVUE5304 replace with MZ300S-24M AVUE5354 replace with MZ300S-24M AVUX5202 replace with MZ300S-24F AVUM5601 replace with MZ300S-230F The AVUE, AVUX, AVUM Mk 5 Datasheet is attached   MZ300S Specification sheet   MZ300S-24M Installation Instructions MZ300S-24F Installation Instructions   MZ300S-230F Installation Instructions

Warning   Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Using sensors, other than the D?T range in a Sigma controller Product Line Satchwell Sigma Environment Sigma Release 4_05-SEB (Build 3_43_18) Sigma Release 4_05-SP2 (Build 3_42_48) Sigma Release 4_06 (Build 3_44_14) Sigma Release 4_06 SP1 (Build 3_44_16) Sigma Release 4_07 (Build 3_45_48) Sigma Release 4_07-SP1 (Build 3_45_51) Sigma Release 4_07-SP2 (Build 3_45_58) Sigma Release 4_08 (Build 3_46_57) Cause Using 10k Type 2 and type 3 Thermistor causes hardware alarm Resolution The lookup value for a Sigma resistance input is calculated as a percentage of a 2 volt signal (that's what is measured at the A/D convertor). If using a sensor other than a standard D?T range sensor, a calculation needs to made, to obtain the value to be entered in the input column (a % of 2 volts) of the look up table.   The calculation is as follows: - ( 10^6 * R1 )      /4000 ( 14700 + R1 ) Where R1 = resistance of the input 14700 =resistor on AI card The circuit shown below is a typical example of an AI channel for a resistance input.     It is suggested to put a 10K resistor in parallel therefore, the resulting circuit resistance can never be higher than 10K.   Attached is information for both the 10K type 2 and 10K type 3 sensors. Column C is the raw sensor resistance. Column D is the controller input resistance with a 10K shunt resistor connected. Column E and F example of the look up table.

Issue Unable to establish communication between the enterprise and automation servers through the TCP Port 4444. Values are not being passed between the enterprise to the automation servers or between automation server to automation server. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Workstation Cause Windows Firewall is not allowing inbound or outbound information from passing through the TCP port 4444. Resolution First download and run TCP View. With TCP View running, sort the list by the Local Port and find all devices that are talking on port 4444. If the automation servers are in a state of LISTENING then rules must be created to allow communication. Copy the file path of SE.EnterpriseServer.exe in order to create the rules. This can be found by right clicking on one of the SE.EnterpriseServer.exe process > Process Properties... (C:\Program Files\Schneider Electric\StruxureWare 1.2\Enterprise Server\bin\SE.EnterpriseServer.exe) If the automation servers are in the state of ESTABLISHED, then take a look at Binding between ES and AS or two AS shows Unresolved and "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 for more troubleshooting help.   Change Windows Firewall Settings to Allow Programs Go to Start > Control Panel. Click on Windows Firewall. Click on "Allow a program or feature through Windows Firewall" on the left hand side of the window. Find "StruxureWare Building Operation" in the list of programs and make sure Home/Work and Public networks are selected.  Note: If you do not have permission rights to make changes in this area of Windows, move on to the next section where you can set up inbound and outbound firewall rules.   Creating Inbound and Outbound Windows Firewall Rules Go to Start > Control Panel.  Click on Windows Firewall. Click "Advanced settings" on the left side of the window. Select Inbound Rules on the left side of the window and then click New Rule... on the right side of the window. On the first screen of the New Rule Wizard, choose Program. Click Next. In "This program path:" either browse to SE.EnterpriseServer.exe or paste the file path that was copied earlier from the TCP View into the box. Click Next. Select the option to "Allow the connection". Click Next. Leave Domain, Private, and Public checked unless otherwise desired. Click Next. Name the rule StruxureWare. Click Finish. Select Outbound Rules on the left side of the window and then click New Rule... on the right side of the window. Follow steps 5 through 9 to create the Outbound Rule. Note that the SBO Firewall Config tool on the community can be used to automatically create the required firewall rules.

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 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 Is there an I/A Series G3 object that calculates sunrise and sunset? Environment I/A Series G3 (versions 3.5.xx and higher) Cause Requires calculated sunrise and sunset times for automatic control of lighting, etc. Resolution The SunPosition object can be used to calculate a wide variety of sun metrics. Calculations are based upon a provided longitude, latitude, and date time.  The SunPosition object can be found in the I/A Series G3 weather module. Note:  The use of the SunPosition object does not require that the ENC, JACE, or Enterprise Server have Internet access, nor that it be located within the United States. The data provided is generated within the station using mathematical calculations based upon the current date, time, and a location provided in degrees longitude and latitude. The following data is available as output slots of the object: Day Length Sunrise time Sunset time Astronomical noon Astronomical midnight Current sun elevation Maximum sun elevation (at solar noon) Minimum sun elevation (at solar midnight) Current sun Declination Current sun Azimuth Current sun Right Ascension

Issue  EBO can have license violation bar without a known reason. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause License enforcement is the process of checking whether a software application has a valid license available to it at runtime. If you do not have enough licenses, a license violation occurs. This is accomplished by a license violation bar in WorkStation and WebStation.   Firstly, the license violation will be yellow, and it can be hidden for 8 hours. You can use Hide to hide the License Violation bar for 7 days. After 7 days, the Hide function is disabled. After 30 days, the bar turns red. Resolution Below information can be collected to help in troubleshooting: Refer to the document Part Number Summary and Hardware Software Matrix for software and features that need licenses and note that some feature licenses can be inherited from parent server to child servers. Get a screenshot of the License information page in the control panel, make sure to have all content in license information page are shown in the screenshots, ex child servers' status. It can tell which feature needs a license or which child server needs a license, refer to License Information Get the License Diagnostics, and entitlement certificates to make sure that required licenses are activated. Install the latest CP/hotfix to make sure that the system is not affected by one of the known license related defects, Make sure that all EBO servers have correct date and time, incorrect date and time can cause license violation, as explained in: Incorrect Automation Server date and time leads to license violation - Schneider Electric Community Check Known issues community. Get screenshots for the following: In ES, "System/LicenseManager/LicenseStatus/ConnectedASLicenseStatus" will show all connected Automation Servers. Show the license violation tab to know which Automation Server has violation as Automation Server may have violation although license information doesn't show that, ex. if the "Change Control" feature is enabled in an Automation server and ES doesn't have a license for it. For parent server and any server that has violation, search in folder "/System/LicenseManager/LicenseStatus". In the object name, write "*" and add columns License Violation, Checked Out License, Available Licenses, Required Licenses, and Installed Licenses. Export the results to XLSX. Check license Metadata for the parent server and any servers have license violation, search in folder "/System/LicenseManager/LicensingMetadata". In object name, write "*" and add columns FeatureVersion, FatureName, ProductVersion, EntitlmentID and Activation ID. Export the results to XLSX.   Get screenshot from FlexNet Publisher web interface, localhost:8888, concurrent tab. Make sure all features are shown in the screenshot, and the entire webpage can be saved instead of taking screenshots. If the server has just started, wait for some minutes till all data is collected.   Collect the logs and configuration files listed below: Log files located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\logs Configuration file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\conf Using EBO WorkStation, go to module, '/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.licensemanager", set trace level to debug, reproduce the issue, if possible. Collect the server logs, then set the module trace level back to "information", refer to Collect logs from an Automation Server - Communities and Collect logs from the Enterprise Server and Enterprise Central - Communities.

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 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 When adding License Entitlements via Device Administrator using the online method. After clicking activate, a "Communication failed" message is displayed:   Could not establish contact with License Server using SmartX Server Followed by a "License Operation Failed" message:   Add entitlement failed. License Server is offline. Error code: 41 Error message: CURL error: Product Line EcoStruxure Building Operation Environment Device Administrator Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause When activating a SmartX Server license online, the SmartX server will try to connect to the license activation server to activate the license. If it cannot resolve the license activation server site name and connect, it will show up as offline. Resolution Make sure that the SmartX Server DNS is properly configured in the AS-P.  In Device Administrator select the Ethernet 1 Configuration tab. Check the Primary, Secondary, and Tertiary DNS settings If unsure of the correct DNS address, enter the Google DNS address of 8.8.8.8 or 8.8.4.4. The example below shows a local router address as the Primary DNS and Google DNS as the Secondary and Tertiary DNS.   To confirm that the SmartX Server can resolve the license activation server address Open a Console session on the SmartX Server in Device Administrator. Enter the command: ping schneider-electric.flexnetoperations.com If the DNS is correctly set in the SmartX Server, the result should look similar to that shown below: Note: Ensure that the ASP is fully connected to the Internet in order to perform Online Embedded License Activation. You need to be connected to the Automation Server using IP (Not via USB) to activate the embedded license.

Issue Is there any adaptive tuning in the flow control loop that drives the MP-V or RP-V damper loop that will be negatively impacted by extended periods of non-zero box flow setpoints when the associated AHU is disabled (i.e. no pressure at VAV so the damper will open fully and the flow control loop will saturate). Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV EasyLogic RP-V Cause No information on the internal Variable Air Volume Data object Resolution Airflow control in the MP and RP VAV controllers is not impacted by extended periods of non-zero box flow setpoints when the associated AHU is disabled. The damper is actuated by a single-speed motor with three states (open, close, hold), and to avoid windup or saturation effects, the flow control algorithm is not a PID loop. There is no need to link the AHU enable to the MP or RP flow control logic.