Building Automation Knowledge Base

Issue Lost/Forgot/Modify the SysAdmin SQL default password created during the installation of TAC Vista 5.X.X in typical mode. Product Line TAC INET, TAC Vista Environment TAC Vista 5.x.x SQL 2005 Express Microsoft SQL Server Management Studio Express: (http://www.microsoft.com/download/en/details.aspx?id=8961) Local Admin rights Required. Cause Procedure if SQL Password is Lost/ Forgotten or Modification required. Resolution When you click on Microsoft SQL Server Management Studio Express, it will open the below page and require you to choose the way you want to log in: either by “Windows Authentication” or “SQL Server Authentication”. If you want to log in using Windows Authentication, choose this option and go in. (It uses the Windows login credentials). If you want to log in using SQL Server Authentication, choose this option and enter Login and password. If you want to change this Login and Password: Enter using the Windows Authentication Choose Security > Logins > Select the login ID Right click and go to Properties Change the password and re-login using the new password. Below is an example where the password for the login 'sa' has been changed:

Issue I/A Series R2 Enterprise Server and I/A Series G3 Enterprise Network Server redundancy solution Environment I/A Series R2 and I/A Series G3 Cause Continuous uptime is required for I/A Series system and data. Resolution The recommended software for I/A Series redundancy is from Stratus Technologies (http://www.stratus.com/). Contact your local Stratus Technologies office or distributor / partner for details. Also refer TVDA document 'everRun Mx with SE Building Management Systems'.   Frequently asked questions: What does Stratus Technologies solutions do? It delivers simple, affordable, continuous uptime for any Windows application running on unmodified, industry-standard server hardware. This high availability solution protects applications, data, and operating systems from faults, failures, and dropped network connections. How does it work? Stratus software synchronizes two standard Windows servers and creates a virtual application environment that runs on both of them simultaneously. If one server fails, the Windows application continues to operate uninterrupted using the other server with no failover, transaction rollback, or other complex procedure. Are there any special I/A Series licensing requirements? The Stratus solution requires a single I/A Series license only. Only one copy of the Enterprise Server / Enterprise Network Server is required. There are no special properties or license requirements. Which Marathon product should be used? All Stratus products can be used. The particular Stratus product will be determined by the end-user hardware and performance requirements. Are there any special properties that need to be set up in the Enterprise Server / Enterprise Network Server when using the Stratus product? The installation of I/A Series (R2 or G3) is no different than installing the product on a standard Microsoft Windows platform. Keep in mind; if the Microsoft Windows platform is running IIS, then either IIS or the Enterprise Server / Enterprise Network Server will have to run on something other than port 80. Both applications cannot utilize the same port.

Issue The controller displays dashes instead of showing the expected temperatures. Environment CSC CSC5252 CSC5352 Temperatures are not displayed. Dashes displayed Cause Controller has the incorrect sensor type selected, or has not correctly cold started. Resolution If none of the sensors display the correct temperature, then reloading the controller defaults, is the way forward. To reload the controller defaults and to re-initialise the controller, carry out the following; Switch off the power to the controller. Press and hold in the controller enter key. Switch on the power to the controller, whilst continuing to hold the enter key in. Release the enter key after 3-4 seconds. The sensor temperatures will now be displayed correctly. To access the controller data sheet, please click HERE.

Issue Unable to control Door output on SP-C when configured as onboard Reader Expander. Manual control of the Door outputs work but the Reader Expander will not control the Door outputs when a valid card is read. Product Line EcoStruxure Security Expert Environment Security Expert SP-C Cause The Controller was not registered as a Reader Expander. This is not done automatically for you when configuring the Controller through the wizard and needs to be done manually to be able to use the onboard readers. Resolution 1. Go to Sites > Controllers and on the Configuration tab select the address to Register as Reader Expander and the configuration of the Onboard Reader Lock Outputs. 2. Update modules and download. Note: In later Security Expert versions, it will say "Controller Relay 3/4 outputs" under "Onboard Reader Lock Outputs".  

Issue Weather information provided through the weather module in I/A Series G3 is no longer updating. Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server ENC-410 ENC-520 Cause The National Weather Service hosts the data service used by the Niagara weather module's default provider, the "NWS Weather Provider". At some point during the week of September 26th, the National Weather Service moved the location of their forecasted weather conditions service.  No advanced warning of the change was provided. The error message encountered may include: WARNING [10:04:20 30-Sep-11 EDT][weather] Updating forecast failed for WeatherReport javax.baja.sys.BajaException: 404 Not Found at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java) at com.tridium.weather.nws.NwsForecastReader.getForecast(NwsForecastReader.java) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java) at javax.baja.sys.BComponent.doInvoke(BComponent.java) at javax.baja.util.Invocation.run(Invocation.java) at javax.baja.util.Worker.process(Worker.java) at javax.baja.util.Worker$Processor.run(Worker.java) at java.lang.Thread.run(Thread.java:823) Resolution The weather service has been updated in patched weather modules to use the new data service location.  A number of other enhancements have also been made to better detect this situation and attempt to automatically resolve the issue by better following the 'HTTP Moved Permanently' error response messages. This may help reduce the impact of future unannounced National Weather Service data service changes. Although some users may wish to work around this problem by making changes to hidden fields on the weather provider, this is not recommended because it leaves stations exposed problems resulting from future data feed changes. forecast server: graphical.weather.gov forecast path: /xml/sample_products/browser_interface/ndfdBrowserClientByDay.php The NWS has also deprecated the current condition feeds previous retrieved from the www.nws.noaa.gov servers. These are now being replaced by feeds made available at www.weather.gov.  The new patched weather module will automatically use the feeds at the new location. As a temporary workaround, the Nws Weather Provider's hidden slot "conditions server" can be modified with the new value "www.weather.gov". It is recommended that weather service users upgrade to the most recent weather module for their release.  The modules can be downloaded from The Exchange Download Center. weather-3.4.67.3 or higher weather-3.5.39.5 or higher weather-3.6.37.4 or higher

Issue Controller crashes during reload. Error log shows illegal instruction. 0xbadd0004 0x00002000 0x01802174 0x40102000 0x085be4d8 Reset (illegal instruction) Environment All CX controllers Cause Incompatible XDriver loaded. Continuum controllers can be either first or second generation. The XDriver used must be matched with the controller generation.   First generation controllers are 92xx, 94xx, 99xx Second generation controllers are 9702, 9640, 4xxx, 9680, and 57xx Resolution Load the appropriate XDriver in the controller. If upgrading a controller such as going from a 9200 to a 9680, review the Third Party Interface Data Sheet to locate the re-compiled second generation Xdriver. NOTE: Not all XDrivers have been made available for second generation controllers, if the Xdriver is not available check with the third party vendor to see if a standard ModBus or BACnet plug in/upgrade is available for the device.

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. 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. One way conversion: Conversion of b4920 to b3920 is not reversible, once the b4920 controller has been converted to b3920 device, it cannot be converted back to b4920. Issue A b3920 device has failed in the field and the only available replacement at hand is a b4920 Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum b4920 Cause The b4920 is a Continuum BACnet router its hardware is almost identical to that of the b3920 device, the only difference is the Ethernet port in the b4920, which is not populated in the b3920. When a b3920 must be replaced, and the only available replacement is a b4920, use the steps outlined in this article to convert the b4920 to a b3920. Resolution Before starting the procedure, you need the following items: The b4920 device to be converted. The serial number of the b4920 device to be converted. Continuum Cyberstation with b4920 to be converted, configured, and online. (***) A RoamIO2 and BACnet Service Tool A special firmware b4920 application upgrade file provided by Product Support A b3920 bootloader file provided by Product Support Steps to convert b4920 into b3920 Contact Product Support and request the b4920 to b3920 conversion files. You will be provided with an application file (e.g. b4920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd). From Continuum Workstation, take note of the baud rate of the MSTP operating under the b4920 (In Comm1 settings) From Continuum Cyberstation, edit the b4920 controller object and take note of the BACnet Device ID and the controller Serial Number, typically they will be the same but this is not always the case. In the "General" tab, click 'Update OS' and send the Application file provided by PSS. Please note that once the application file has been sent and the controller re-starts, its MSTP will shut down and RoamIO2 is required to re-start the MSTP for operation as a b3920, the reason for this is Continuum uses mac id 0 (zero) for router controllers such as the b4920 and the bCX4040, in Continuum, b3 devices are not allowed to use mac id 0. Disconnect the Ethernet cable from the b4920, the Ethernet port is now unusable. Connect the RoamIO2 directly to the b4920's Service Port then cycle power to the b4920. Start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from b4940 to a b3920 causes the now b3920 device to come up with an unknown baud rate and an invalid (for b3s) mac id 0, so now need to find out the baud rate the converted b3920 is using From the "View" menu, select "RoamIO2 Properties and take note of the MAC ID the RoamIO2 is using   From the 'Tools' menu, select 'Set b3 baud rate' and set it to Baud9600, and click apply    From the 'Tools' menu, select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC ID ( DO NOT ENTER ZERO NOR THE MAC ID IN USE BY ROAMIO2), then click on 'Apply'   If you get the message below, repeat the steps above for the next baud rate... when you have found the correct baud, you will see the message below after setting the MAC ID   Once the baud and MAC id have been set successfully, the device will automatically pop up in the tree, but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right-click on the device, then select 'Update OS' and send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, click 'Done' button to dismiss, select the device, right-click and select 'Cold start device', and click 'Yes' on the confirmation window   You should now be able to commission the converted device as a b3920, either as a new device or as a replacement device, following the steps for replacing a b3 device. (those steps are not in the scope of this procedure) *** b4920 controllers are not easily defaulted to factory settings. If one gets an old b4920 from the shelf, use the steps below to find out the controller's current IP address and ACCNetId which are needed to put the controller online in Continuum. IP ADDRESS Upon start-up the b4920 sends a gratuitous ARP, use Wireshark to connect directly to b4920 controller using a crossover Ethernet cable, restart the controller, and inspect the gratuitous ARP to determine the IP address configured in the b4920 ACCNetID Once you have the IP address, use the attached utility tool to discover the ACCNetID of the b4920. Unzip the attached file and use the Windows Command Line to execute FindEnodeID.exe as seen below  

Issue DHCP server is required to assign addressing to IP devices Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series Jace 8000 I/A Series ScheniderMPx Modules Building Operation Multi-purpose VAV  Building Operation Multi-purpose Controller Building Operation Room Controller (RPC) 24 V Building Operation IP-IO Cause When working with the SchneiderMPx modules for engineering Spacelogic devices, the Jace can be used as a DHCP server for the field devices. Resolution This video discusses how to; - Configure the second IP network port for DHCP server use - Add an additional IP Port to the Jace station  

Issue The port range used by the Project Configuration Tool is unclear Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The ports used by PCT are located in different documents Resolution • TCP on port 4444 (fixed) • HTTP on port 80 (default) • HTTPS on port 443 (default) • Server port 9091 (default) • Server port 9090 (default) • Engineering port 32768-61000

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 The EGWW sensor is obsolete and needs to be replaced. Environment  EGWW: EGWW 120 Cu 5122720000 EGWW 120 St 5122720010 STP100: 5123102010 5123104010 5123106010 5123108010 5123110010 5123112010 5123114010 Cause Obsolete sensor needs to be replaced. Resolution There is no direct replacement, as the old EGWW had 2 sensor elements and was designed to be used with controllers like TA 219WB (Data sheet here). Also, the EGWW was designed to be mounted directly into the pipe work using a well, and not using a pocket as with the STP100. If only one sensor element is required by the application, the STP100 series sensor is recommended. However, please note that the EGWW well was 120mm or 220mm (see data sheet here), while the STP100 sensor probe and pockets are available in 50, 100, 150, 200, 250, 300 and 400 mm lengths. For more information and details on the STP100 and its different configurations, please see data sheet here. If the 2 sensor configuration is required, you will have to install 2 parallel sensors.  

Issue After installed I/NET, DBCreate will never pop up to create a new database, which will cause I/NET never launches. Backup and Restore button are greyed out when opening DBCreate, which also will cause I/NET fails to launch. When restoring database, an error will show up, saying that version is incompatible with this server. When restoring the database, an access deny error will show up. Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause SQL default instance is not created correctly. SQL2005 BCM is not installed correctly if SQL2008 is used, or there is a database version mismatch for I/NET. This is usually caused by restoring new SQL database to old version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Windows permissions are not enough to do the restoring Functionality of the host pc and the database seems to be inconsistent. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution If you are using I/NET 2.4x, and already have a named SQL instance on the computer (for example, TAC Vista 5.1.7 or higher has been installed, with a named instance installed called TACVista), I/NET may fail to recognize it, while also fail to create a default instance. Similar kind of warning will pop up during the I/NET installation: Under this condition, use your current SQL server installer or browse to /SQLExpress folder of I/NET installation CD, to manually create a new default instance. You can refer to the guide within the /SQLExpress folder about how to create it. As long as the default instance is created, DBCreate will pop up immediately and a new database can be created. If 64 bit Operation System is used, refer to Installing I/NET Seven on a 64-bit operating system for the detailed guide. Also refer to Installation guidelines for installing I/NET and Vista on the same PC for more details about installing I/NET and TAC Vista on one computer. If SQL 2008 or SQL 2008 R2 is used, be sure to follow the correct steps about how to install them: I/NET Seven with SQL 2008: I/NET Seven with SQL 2008 Installing I/NET Seven on a 64-bit operating system: Installing I/NET Seven 2.42 or higher on a 64-bit operating system If SQL 2008 is installed correctly, please refer to Data Base maintenance before performing an upgradeto perform a forced upgrade for the database. Refer to Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate: Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate Refer to DBCreate backup access denied using Windows Server 2008 R2 Standard and Microsoft SQL 2008 R2: DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2. Refer to Unable to Create a backup in DBCreate: Unable to Create a backup in DBCreate. Refer to Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached: Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached.

Issue Users login to EBO using Windows Authentication via the Workstation client encounters the error "User account not associated with a group. Contact your administrator".  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server - SXWSWESXX00001 Building Operation Enterprise Central - SXWSWECXX00005 Building Operation Workstation - SXWSWWORK00002 Cause The "Local System account" used to run the "Building Operation Enterprise Server" service does not have sufficient permissions for EBO/Active Directory integration. One function call from EBO to the Active Directory fails when EBO tries to fetch the groups for the user logging in. Resolution The service account used to run the "Building Operation Enterprise Server" service must be able to read the token-groups-global-and-universal (TGGAU) attribute. The IT department or the Active Directory administrator needs to grant this explicit access to the service account by adding the service account to the built-in group in Active Directory called "Windows Authorization Access Group". For more details regarding the TGGAU attribute, see this article from Microsoft Support, Some Applications and APIs Require Access to Authorization Information.

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 Security Expert Installation steps for separate SQL, SX application Server, and Client for use with Windows Authentication and Active Directory Product Line Security Expert Environment Microsoft SQL Server Microsoft Windows10 Security Expert Server and Client  Cause Access Denied error appears when attempting to log into Security Expert with Windows Authentication with a multiple PC Security Expert Installation Resolution Important considerations when connecting Security Expert to an external SQL Server: Machines should be on the same network and Domain. When you install Security Expert, reference the SQL database in this form:  Machine Name\SQL Instance Name The Windows user account doing the installation must have admin rights on both machines. The windows login you're using to install on the Security Expert machine has to have admin privileges to alter the SQL Database on the remote machine. The easiest way to do this is to use the same account to set up all machines. Different accounts can be used, but the accounts have to have privileges added to the SQL Database manually. (Not covered in this document)   Assumptions: Active Directory server has a domain user that can be used to install the applications on all machines. Licenses cover all machines Security Expert users are set up to use Windows Authentication (snapshots at the end of the document) If the SQL server ever had Security Expert Installed on it, uninstall Security Expert and reboot. If the Security Expert application server had SQL on it, uninstall SQL, reboot and reinstall Security Expert without local SQL. If the Client PC had Server components installed, uninstall Security Expert, reboot and install the client only.   Perform the SQL Server Installation onto a separate Server per the Security Expert Installation Instructions Security Expert Application Server/Client installation (No SQL) If this box is selected, the install may fail because the service has not been installed yet. With this option selected, the install will finish and then the service can be configured later. 3. Change the database server to NOT be localhost\SecurityExpert Use machinenameofSQLServer\SecurityExpert (Ex. SECEXPERTVM\SecurityExpert) 4. Select Windows Authentication Complete the installation.   5. Open Windows Services on the Security Expert Application Server (Run> services.msc) Right-click on Security Expert Data Service> Properties Select the Log On tab Deselect Login As Local System Account Select This account and then click browse to search for the domain admin user   Start the service. Security Expert Data Service, Security Expert Event Service, and Security Expert Update should all start   Client only setup - Ensure the Server option is deselected In the following dialog select Custom   7. Select the drop-down next to Server> then select “This feature will not be available” Complete the installation   A successful login with the domain admin account using Windows Authentication from the Security Expert machine and also the client PC should work.   From the Client PC – Security Expert application server = 10.169.90.170 From the Security Expert Server/Client SecurityExpertSV.exe.config (Server) – This file did not have to be changed    SecurityExpert.exe.config (Client) - This file did not have to be changed   Note: There may be circumstances where these files do need to be configured. See LL https://community.se.com/t5/Knowledge-Base/Security-Expert-Error-Server-Has-Rejected-Client-Credentials/ta-p/698   Domain Tab example set up in Security Expert for Active Directory Windows Authentication   Operator Example setup in Security Expert for Windows Authentication   Global Support Lab Testing SX Application Server (Windows10 1803) SQL Server – Server 2012 R2 with SQL 2016 SP1 (VM) SX Client – Window 8.1 Pro

Issue Application Director output window and LON proxy point indicates fault: java.lang.ClassCastException: javax.baja.sys.BDouble ERROR [14:56:22 20-Aug-14 EDT][lon1] Could not decode nv update data Misc9:nvoSpaceTemp java.lang.ClassCastException: javax.baja.sys.BDouble    at javax.baja.lonworks.londata.LonFacetsUtil.makeLonQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.LonFacetsUtil.getQualifiers(LonFacetsUtil.java)    at javax.baja.lonworks.londata.BLonData.primitiveFromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromInputStream(BLonData.java)    at javax.baja.lonworks.londata.BLonData.fromNetBytes(BLonData.java)    at javax.baja.lonworks.BNetworkVariable.receiveUpdate(BNetworkVariable.java)    at com.tridium.lonworks.NvManager.receiveLonMessage(NvManager.java)    at com.tridium.lonworks.loncomm.NLonComm.routeToNvListener(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonComm.receiveLonMessage(NLonComm.java)    at com.tridium.lonworks.loncomm.NLonLinkLayer$AppBufferReceive.run(NLonLinkLayer.java)    at java.lang.Thread.run(Unknown Source) Environment I/A Series G3 (all versions) Cause This error is related to a mismatch between the lonworks module running on the ENC/JACE versus the version being used within the Workbench modules folder.  A different version of Workbench and/or lonworks module is being used to engineer the ENC/JACE. Resolution Review the versions between the Workbench and ENC/JACE and match the versions.

Issue It is not possible to bind a point in a Function Block program to the RelinquishDefault property of a BACnet Multistate value in an SE8000 controller. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation(SBO) 1.6.1 SE-8000 series Room Controller Cause In some circumstances the user may wish to change the value from both the HMI in SE8000 and from a Function block program in SBO, and in this case the RelinquishDefault property must be used. Resolution A possible workaround is to use a LUA script in the SE8000 controller. Idea 1: Write a LUA script that will check if the Priority array (ex. priority 16) value has changed for the list of points that the user wants to modify. If there is an entry in the Priority array, have the LUA script copy that value to Relinquish_default, then relinquish the corresponding priority array entry. Idea 2: There are 6 LUA "scratchpad" BACnet AVs that the user can write too. When the LUA script sees a change in those AVs, it can copy the value to a specific AV's relinquish default. For example, scratchpad AV25 can be used to "shadow" a setpoint. So when AV25 changes, the LUA script will copy the present value of AV25 into the Relinquish_default of whatever the Setpoint's AV is. Example of the LUA script in the SE8000 controller for the above: If value AV25 is bigger than 0, the value of AV25 is written on AV39 Relinquish_default property (priority17) and then AV25 is set to 0. if ME.AV25 > 0 then ME.AV39_Present_Value[17] = (ME.AV25/10); end ME.AV25 = 0 LUA programming guide for SE8000 Room controllers

Issue Difference in Triggered time and Timestamp Product Line EcoStruxure Building Operation Environment SBO Alarm view Cause In alarm view there, there are two timefields: "triggered time" and "time stamp." Resolution The Timestamp is the time at which the most recent state change occurred to the alarm. It is when the AS or ES received/detected the state and logged the alarm. The Triggered time is the first occurrence of this alarm. It could be when the alarm was originally detected, before possibly going in/ out of alarm several times. It could also be the time stamp when detected by a field controller. Triggered Time Stamp behavior also clarifies a few things on when they are updated.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown. The SSN is invalid for this installation. Product Line EcoStruxure Security Expert Environment Security Expert Cause Wrong SSN being used. The SSN being used is different to what was used when Security Expert was initially installed. Resolution Uninstall Security Expert and re-install using the correct SSN. Backup the SecurityExpert and SecurityExpertEvents databases and copy the resulting backup files somewhere safe. Manual backups can be initiated from the Global > Global Settings menu. Select the directory location and press backup now. Uninstall Security Expert from Windows Add or Remove Programs. Search for "Security Expert" to filter the results. Install Security Expert from available installation files. When asked for the license make sure to use the correct SSN.

Issue MQTT client from an AS-P cannot establish communication with the Mosquitto broker installed on the machine that hosts the Enterprise Server (ES). At the same time, the MQTT client from the ES was online with the Mosquitto broker. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server IoT messaging MQTT (Messaging Queuing Telemetry Transport) Cause In version 1.6.x and earlier from the Mosquitto broker, the option - allow_anonymous [ true | false ] from the configuration setup (e.g. mosquitto.conf — the configuration file for mosquitto) of the broker was defaulted to  true  unless there were other security options set.   In recent versions of the broker, the option allow_anonymous defaults to  false - Unless no listeners are defined in the configuration file, in which case it set to  true  - but connections are only allowed from the local machine if external connections are required; specific port listeners need to be set. Resolution To configure the MQTT Mosquitto broker for insecure communication with an EBO server, follow these steps.  Download the Mosquitto broker latest version from the Eclipse website and install it on the host machine. Locate the mosquitto.conf file in the  Mosquitto installation folder (Default: C:\Program Files\mosquitto). Edit the mosquitto.conf file with a text editor application (e.g. Notepad, Notepad++). Setting up the  allow_anonymous configuration as true and the listeners to the desired communication ports (e.g. 1883: This is the default MQTT port. 1883 is defined at IANA as MQTT over TCP. 8883: This is the default MQTT port for MQTT over TLS.)   Check the Video attached, which includes the basic configuration of the mosquitto.conf file.   

Issue Using AOL as email provider the following error messages comes every two days: 2014-06-12 15:11:06 E-mail was NOT sent: 521 5.2.1 MUST COMPLETE IMAGE PUZZLE BEFORE SENDING. PLEASE GOTO http://challenge.aol.com/spam.html Product Line EcoStruxure Building Expert Environment SmartStruxure Lite MPM AOL Cause This is AOL trying to stop people using its email service to generate spam, you are now required to periodically enter a series of numbers or letters from a web page in addition to normal username and password authentication. Resolution See AOL help to understand the issue further. This post on the internet also notes the issue and unfortunately this is something that AOL has added and is not under our control.