Building Automation Knowledge Base

Issue Blank window while capturing a photo using "Logitech HD Pro Webcam C920". Product Line EcoStruxure Security Expert Environment Security Expert Cause While capturing a user photo using "Logitech HD Pro Webcam C920", it shows up as an image source (in the drop-down along with Topaz). When selected however, the screen is blank. Resolution With this webcam, you need LWS software by Logitech installed on your machine. G Hub has replaced LWS however it seems like G Hub is not currently functional with the integration. Find more information about the  "LWS280" driver HERE.  The driver can be downloaded from the attachment.

Issue Many campuses are configured with 1 BACnet Network ID number for Primary IP that is unique per building whether or not they are in the same IP subnet or multiple (with BBMDs). Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause When reviewing the Technical Reference Guide and searching "BACnet and IP Routing", it does not clearly explain the configuration and it also does not extend to multi-building systems using BBMDs. Resolution BACnet network numbers are assigned at BACnet routers, with a Range of 1-65,534 (where 65535 is reserved for broadcasts). Routed networks are assigned unique network numbers and can only have 1 router per network. Routed networks are usually BACnet MSTP, BACnet Ethernet, and Secondary IP networks. Standard practice is to have primary IP networks consisting of IP routers/devices in the same IP subnet or across multiple IP subnets joined by a BBMD and/or foreign device configuration uses the default BACnet network number 1.

Issue The Drayton Theta YBL3 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBL3 Cause The Drayton Theta YBL3 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL3 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL3 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL3 Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL3 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M7 – M1 made to M7 when YBL3 Fully Closed (24Vac) Terminal M8 – M2 made to M8 when YBL3 Fully Open (24Vac) Where external wiring is connected to YBL3 Transfer Switch Terminals M7 or M8 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here. Where external wiring is connected to YBL3 Terminal M7 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 24Vac power source Terminal S2 (Normally Closed) - connect to 24Vac device previously connected to YBL3 Terminal M7 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M8 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 24Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 24Vac device previously connected to YBL3 Terminal M8   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL3 Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL3 Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M7 – M1 made to M7 when YBL3 Fully Closed (24Vac) Terminal M8 – M2 made to M8 when YBL3 Fully Open (24Vac) Where external wiring is connected to YBL3 Transfer Switch Terminals M7 or M8 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here Where external wiring is connected to YBL3 Terminal M7 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 24Vac power source Terminal S2 (Normally Closed) - connect to 24Vac device previously connected to YBL3 Terminal M7 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M8 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 24Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 24Vac device previously connected to YBL3 Terminal M8   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL3 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue What versions of Visio are required for WorkPlace Tech? Product Line TAC IA Series Environment WorkPlace Tech Microsoft Office Visio (32-bit version only on WPT versions 5.10 and earlier ) Microsoft Office Visio (64-bit version only on WPT versions 5.11 and later) Cause Software requirement - Microsoft Office Visio must be installed on the computer before beginning the installation of WorkPlace Tech. Resolution Below is a list of the WorkPlace Tech revisions and compatible Microsoft Visio versions.  The "Pro" versions are not required.  The "standard" versions of Microsoft Visio are typically recommended.  Only the 32-bit versions of Visio are supported in WPT 5.10 and earlier and only 64-bit versions are supported in WPT 5.11 and later. WPT Visio 3.1 Visio 5 Technical Plus 3.2 2000 SP1 4.0 2000 SP1, 2002 SP1 5.0 2002 SP1, 2003 SP1 5.1 2002 SP1, 2003 SP1 5.2 2002 SP2, 2003 SP1 or SP2 5.3 2002 SP2, 2003 SP1 or SP2 5.4 2002 SP2, 2003 SP1 or SP2 5.5 2002 SP2, 2003 SP1 or SP2 5.6 2002 SP2, 2003 SP1 or SP2 5.7 2003 SP3, 2007 SP1 5.8.0 to 5.8.5 ** 2003 SP3, 2007 SP1 or SP2, 2010 SP1 5.8.6 2007 SP1 or SP2, 2010 SP1 5.8.7 2007 SP3, 2010 SP2 5.9.1 to 5.9.4 2010 SP2, 2013 SP1, 2016 5.10.0 to 5.10.4 2016, 2019, 2021 Office (Visio) 365 Subscription Plans 5.11 2019 64-bit, 2021 64-bit, Office (Visio) 365 Subscription Plans 64-bit ** Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WorkPlace Tech 5.8.0 and 5.8.1, no known issues with 5.8.2 through 5.8.5)

Issue Initialization errors when starting I/NET Seven 2.42 or higher Error: "You must install an instance of SQL 2008R2 (64bit) before completing the INET install" Product Line TAC INET Environment I/NET Seven 2.42 Windows Server 2008 64-bit Windows 7 64-bit SQL 2008 64-bit Windows 8 Cause I/NET 64-bit requires specific installation process in order to function on a 64-bit PC Resolution Installing SQL Download SQL2008 R2 Express 64 bit (SQLEXPR_x64_ENU.exe) from this location: http://www.microsoft.com/en-us/download/details.aspx?id=30438 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 or higher installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install I/NET Seven 2.42 or higher Install I/NET Seven 2.42 or higher using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET NOTE: If error occurs during SQL installation stating invoke or begin invoke failed, follow instructions at this link: http://support.microsoft.com/kb/975055 UPDATE: SQL2008 SP1 prevents the invoke failed error. It can be installed with the same instructions as above. Download it at this link: http://www.microsoft.com/en-us/download/details.aspx?id=25052

Issue Is there a quick reference I can search to find out what features are included in a particular license When manually adding my Product during offline embedded license workflow, how do I know which Features is included and in what quantity?  Product Line EcoStruxure Building Operation Environment Building Operation EBO 2022 v4.03 and lower  Embedded Offline Licensing Offline Activation of Licenses Workflow Cause Currently, no information lists features for each Product name listed in the Part Number Summary for EBO 2022.  A documentation defect (QC 49762) has been raised, which should resolve this.  This article has been created to assist somewhat during this process while waiting for this to be corrected.  The recommendation, if possible, is to perform license activation online to avoid having to enter this detail.   Resolution Important Note: This information is no longer valid for EBO 2022 (Maintenance Release 4.0.4) and EBO 2023 and greater.  The details below are still provided for reference only and are not needed for these later versions.   Attached are two documents that provide version 3.0 and 4.0 License details.  The documents contain all searchable details, including: Product Name Features Part Numbers     Additional details required for Device Administrator "Feature Name" offline entry:   SpaceLogic Server license details Feature Name (seen in Device Admin) License name (seen in Features document) Description / Comments Automation Server server.as.base   SmartDrivers smartdriver.license   SNMP Notifications server.alarms.snmp   Personal Dashboard client.dashboard   TimescaleDB server.timescale   MQTT Publish/Subscribe server.mqtt.rw Enables EBO, as MQTT Client, to publish data on an MQTT Broker and to subscribe to the same data. Serial Modbus server.modbus.rtu Allows SmartX server serial communication - Modbus RTU Serial MS/TP server.bacnet.mstp Allows SmartX server serial communication - MSTP ES Connection server.connect.to.es Allows SmartX server to be hosted by an Enterprise Server Server I/O server.io Allows SmartX server to use IO Field Devices server.device.as Allows SmartX server to host one field device SAML Authentication server.as.auth.saml   Zoning client.zoning Enables use of zoning tools BACnet IP server.bacnet.ip Allows SmartX Server to communicate using BACnet IP Software Assurance software.assurance         Feature Name (Automatically included with bundle licenses)   client.webstation Allows Webstation to log on to an AS   server.cloud.customer Cloud connectivity - Checked by Cloud SMS (Production)   server.as.scalable Included in the license that allows SpaceLogic servers upgrades. i.e. Standalone to Standard etc.   Example: Product Name: ASP-NL Bundle upgrade - Full to ASP Full    Search the document for the product name in the attached document. In this case, the version 4 document.  Below is the result seen in the document: From this, the associated Features and Quantity are shown. In Device Administrator, then add the respective features and quantities when adding the product manually to the Entitlement. Use the above table to correlate between Feature Name and License Name. The example shown below:  

Issue How to change the STR-150 temperature display, setpoint adjustment range, etc. Product Line TAC Vista Environment STR-150 STR Sensor Cause The communication between the STR-150 and the TAC Xenta 121/122 device is one way, space temperature and setpoints are sent from the sensor to the controller. Therefore some STR-150 functions (for example, the setpoint adjustment) can not be configured though Zbuilder, but needs to be done manually in the STR 150 device. Resolution Buttons on the thermostat: Increase Button Decrease Button Bypass button Fan button Wrench symbol   Steps of changing the STR-150 configuration are listed below: Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0 In P0, hold down the bypass button and push the fan button three times to enter configuration mode. NOTE: the wrench symbol is lit when the STR-150 is in configuration mode.   In configuration mode: Press the fan button repeatedly until reaches desired parameters (refer to the configuration table below). NOTE: the two digits farthest to the left on the display show the parameters, while the two digits farthest to the right show the value Use increase button or decrease button to change the value.   Exit configuration mode: Push the fan and bypass button simultaneously for 2 seconds. Or, the timeout will exit configuration mode if idle.   Configuration Options: Parameter Function Value/Range Default value P0 Software Version - - P1 °C or °F temperature display 1=°C, 2=°F 1=°C P2 Reference temperature (Reftemp) 15-30°C / 60-90°F 22°C / 72°F P3 Setpoint or room temp. 1=Setpt, 2=Room 1=Setpt P4 Timeout 5-90 seconds 10 seconds P5 Fan Settings 0=No fan 1=On/Off fan 2=Two-speed fan 3=Three-speed fan 3=Three-speed fan P6 Room temperature and setpoint display resolution 0.1 or 0.5 °C 0.2 or 1.0 °F 0.5 °C or 0.2 °F P7 Max adjustable setpoint span above or below Reftemp (P2). +/- 0 - +/- 5°C +/- 0 - +/- 10°F +/- 3° or +/- 6°F P8 Bypass button and occupancy indication When = 2, no bypass command is sent  to the controller 1= Symbol on, off Or flashing 2=Symbol always off Default 1=on, off Or flashing P9 Setpoint as Absolute or Offset value 1=Absolute 2=Offset 1=Absolute   Click here to read STR-150 user's manual.

Issue MNL-V1RVx, MNL-V2RVx and MNL-V1RVx-2, MNL-V2RVx-2 differences Environment I/A Series Micronet LON VAV controllers Cause Part number MNL-V1RVx has been replaced with MNL-V1RVx-2 and part number MNL-V2RVx has been replaced with MNL-V2RVx-2.  The datasheet F-26365 indicates the parts as MNL-V1RVx and MNL-V2RVx.  Resolution The MNL-VxRVx and the MNL-VxRVx-2 are functionally the same. The '-2' was added to the part number to indicate an enhancement to the VAV actuator assembly to reduce the operation noise level of the actuator. 

Issue Where are example Plain English programs and functions stored for typical BMS applications? Product Line Andover Continuum Environment Plain English (PE) Functions and programs. ACSM, PID, Optimiser, ISM, First Aid. Standards Bacnet Optimiser Cause It is always easier to write your Plain English programs starting from documented examples rather than a blank page. What is available? Resolution The following link is to a .zip file containing various BMS standard modules originally developed by the UK Application engineers for Infinity SX8000 and were known as the Infinity Standard Modules (ISM's), they were then updated to Andover Controls Standard Modules (ACSM's) for Continuum. These modules are example functions or building blocks that can by used globally by application engineers to provide the control and monitoring appropriate for your own buildings. Link: Click here. In addition to these functions other examples are in the online help for the corresponding Plain English keywords, and other applications can be found on the Forums; see Sample PE functions and programs for further details. For Smart Sensor examples see Example programs for Smart Sensors TTS-SD-LCD-1 and TTS-SD-LED-1 for details. For example Security programs see the Download Center link, Click Here.

Issue Some BACnet devices advertise support for services such as RPM, COV, etc but malfunction when the service is used. An example of such a device is the Johnson Controls TEC2627VVT which advertises support for RPM but fails to upload its objects when SBO uses RPM to get the object list. Product Line EcoStruxure Building Operation Environment BACnet Automation Server Enterprise Server Cause Some BACnet devices with inconsistent protocol implementation cannot process BACnet services such as RPM, COV, etc. Resolution Feature Supported in Version <no-rpm/> 1.8.1 and higher <no-cov/> 1.8.1.23701 and higher <ignore-unhosted-devices/> 3.2.3.9005 and higher (*)   Users can create a rule under the BACnet interface to configure SBO not to use the service. Some rules are global, while others can be for specific BACnet devices. For particular BACnet devices, they are specified by 'Vendor Identifier' and 'Model Name,' which need to match exactly as shown in that device's Properties - Advanced Tab.   Ensure you have installed the version that supports the feature you want to change. Setup file using the no-rpm rule. Use a text editor like 'Notepad' to create a text file or download the same file below. Enter the device's vendor ID (5)  and model name (TEC2627VVT) followed by the rule (no-rpm) using the format seen in the screenshot below. Save the file to the desired location on the PC with a name aiding later identification. Under the BACnet interface, create a new 'Document' object in the 'Application' folder. NOTE: The object MUST be named 'service_blacklist' in all lowercase. Click 'Next,' import the text file created in step 1, and save the 'Document' object. Restart the Server  Once the device is on the block list, SBO will not send 'readPropertyMultiple' requests to the device using only individual 'readProperty' requests. Add the service_blacklist to the EBO Server. Add the no-cov tag if you would like to block that service for this device:  Extended for multiple devices from different vendors simultaneously using this example for reference.   One can add a global rule using this syntax to ignore unhosted devices. * NOTE: It is recommended to remove <ignore-unhosted-devices/> after upgrading to EBO 4.0/2022 and higher because this feature is supported in the BACnet Interface Properties and BACnet Device Discovery view. Device Discovery for BACnet Controllers and IO Modules (se.com)  Once the Server has restarted, check the trace.log file and search for service_blacklist, there should be entries similar to this. 

Issue Is the I2/B3 865/866/885 UL 916 Listed Environment  I2/B3 865/866/885 Cause  I2/B3 865/866/885 UL 916 Listed Resolution Yes the  I2/B3 865/866/885 are UL 916 Listed Download the complete list of UL916 listed products.

Issue BACnet device can't be discovered but instead shows up under the 'Unconfigured devices' in the server's hardware folder. Product Line EcoStruxure Building Operation Environment WorkStation Enterprise Server - ES Automation Server - AS Cause A BACnet device name must be unique. Devices with duplicate BACnet names can't be discovered. In the screen shot below a device by the name AbesbCX already exists under Network1, when performing a device discovery on Network1 a second device with the same name is found, Since StruxureWare already has a device with the same name it adds the device to the list of unconfigurable devices. NOTE: “The <<N>> means the device was discovered on a directly connected network (such as the local IP network, or a directly connected MSTP bus).  The 2 indicates it was “port” 2, (port numbers are really an internal detail) The server's Trace Log shows the following information, which includes the device's ID. The entry gives the reason as duplicate device name. Resolution 1.8.1 and above BACnet device name duplication is allowed, the duplicates will still land in the unconfigured folder and the system alarm will be generated BUT you can drag the duplicate device from the unconfigured folder to the desired network. When finished, manually delete the device from the unconfigured/non-conformant folder. Alternatively, you can also  warm start the server to force the unconfigured/non-conformant devices list to be updated. Note that the devices with duplicate names will still stay in the unconfigured/non-conformant folder until the name conflict is resolved. 1.7.2 and below A workaround is to create the device manually and specify a BACnet name during the create process. When manually creating the device you need to know the Device ID, you can get the id from the information in the trace log as shown above. SmartStruxure will send a message to the device to change its name to the specified BACnet name. The entry in the unconfigured devices folder should automatically update after a few minutes, you can also re-start the server to force the unconfigured devices list to be updated, the entry for AbesBCX should be gone now that the devices has been manually configured.

Issue How to create custom reports in Building Operation WebReports Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Custom reports are typically created by modifying another report and then saving these changes. Typically used are the factory-supplied reports as the base for a new report then enter the filtering criteria that are required to be used in the new report. Assign a unique name to the custom report and save the new report as a dashboard or prompted report.  There may be a need to create a report not based on any of the standard reports provided in these Report Packs, this article covers this process. Resolution To create a non-factory-supplied report within WebReports it is necessary to use an editor.  Since WebReports use Microsoft Reporting Services it is recommended to download the Microsoft SQL Server 2008 R2 Report Builder 3.0 or MS MSQL Server 2012 Report Builder.  This is a free tool provided by Microsoft that provides an intuitive report authoring environment for business and power users. This download provides a stand-alone installer for Report Builder 3.0.  Please note that Product Support does NOT provide support for Report Builder.  After downloading and installing the Report Builder application, the steps are as follows:  Each of these steps is also located on the Building Management System WebHelp site, a link for each of these steps is provided for additional reference and guidance. Start Report Builder and create a new blank report, see Creating a Basic Report for the steps.  After Creating the report create a data source that connects this report to StruxureWareReportsDB, see Creating a Data Source for these steps Then create the Data set, so add to the report which tables, views, stored procedures, and fields from the StruxureWareReportsDB are required to use in your report, see Creating a Dataset for these steps. This data can then be added to the custom report as required.  See Setting Up a Report for an example of setting up a report. See Adding an Image to a Report  on how to add images to the report  The new report now must be deployed to the Reports Server where it can be accessible to WebReports. To complete this procedure use SQL Server Reporting Services Report Manager. See Deploying a New Report to the Reports Server to view these steps in detail.  Finally, the report must be synchronized in WebReports to be deployed and therefore appear in the WebReports Reports Tree. Use WebReports with a Web browser to complete this procedure.  See Synchronizing WebReports with a New Report for the steps to complete this. Once all these steps have been completed successfully the new Report should be visible in the tree - the placement of these reports will depend on where they have been uploaded in step 5 above.  See the image below:

Issue Datacard ID Works gives an ODBC error. Examples shown below: Microsoft SQL Server Login Connection failed: SQLState: '01000' SQL Server Error: 53 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState: '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. Data Source Error Data source name not found and no default driver specified State:IM002,Native:0,Origin:[Microsoft][ODBC Driver Manager] Product Line TAC INET Environment I/NET Seven all versions Datacard ID Works video badging software Cause The "IDWorksView" driver uses a ODBC Connection to allow the ID Works Software to communicate to the I/NET SQL Database. If for some reason this ODBC gets corrupted, you will get an error anytime you try to run the ID Works software. Resolution Go to Start > Control Panel > Administrative Tools Select Data Sources (ODBC) Select the System DSN tab Highlight Seven ODBC SQL Server in the list and hit the Configure button Make sure the settings are as follows: Name: Seven ODBC Description: ODBC Connection for I/NET Seven Server: (local) Hit Next Before you actually login to this window, choose the Client Configuration button and make sure these settings are correct. Network libraries: TCP/IP Connection parameters: Dynamically determine port Note that the InetThirdParty password changed in I/NET Seven rev 2.4X to PassInetDb3p_SE. If you try to use this in this process it will fail on you. Instead of using the InetThirdParty and the password here, use the Username and Password that you use for the DbCreateEditor. Then select the Next button. Verify the settings below, then hit Next: Change the default database to: InetDb Verify the settings below, then hit Finish Perform translation for character data

Issue While attempting to activate a purchased license, the entitlement ID shows that it is valid, but there is no available licenses that can be activated, or less available than listed on the entitlement certificate. The entitlement ID or certificate is lost. Unable to return the license in order to activate it on another PC Getting "This Operation is not applicable for Trusted Fulfillments" Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In order to activate a SmartStruxure license, it must be available and unused. If a license is already in use, it needs to be returned before it can be activated. Note that all handling of licenses are to be carried out using the License Administrator. Licenses are not returned or rehosted as it was done for TAC Vista. Resolution Refer to WebHelp article #6687 for instructions on how to return a license If you are unable activate a license because you don't have the entitlement ID or certificate, note the activation ID before you return the license, and send that to Product Support Services in order to get the associated entitlement ID Launch the License Administrator Go to the Diagnostics tab and click the refresh icon in the top left corner. The entry in the list that is labeled Entitlement ID is actually the Activation ID. In the case that the computer has crashed or you are unable to successfully return the license on your own, contact Product Support Services providing the following details: A copy of the entitlement certificate The site name An elaborate explanation of why you are not able to return the license yourself

Issue BAS is obsolete how can it be upgraded to Sigma? Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ V2.9 Satchwell Sigma Cause BAS is obsolete but there is a defined path to upgrade the system to Sigma Resolution Upgrading must start from BAS2800+ v2.9 when upgrading to the latest version of Sigma.  Sigma not only allows for more features but also future proofs the system. Upgrade procedure can be found here Migration document (Sales support) can be found here Any BAS versions before BAS2800 + V2.9 please contact Product Support with the details.   The Sigma system is now out of its support period, consideration should be given to transitioning or upgrading to SpaceLogic - EcoStruxure Building Operation.

Issue How to change the IP address of the Automation Server and ensure proper communication. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Building Operation Device Administrator Building Operation Workstation Cause At times the IP address information for an Automation Server must be changed after being added to an Enterprise Server to accommodate changes in IP network design, correction of incorrect data, or any other reason. Changing the IP address needs to be done in the proper method to avoid artifacts and confusion after the change. Resolution To avoid complications, follow this process to modify the IP address of an Automation Server that is already communicating with an Enterprise Server. In the Building Operation Device Administrator connect the AS controller via USB or IP.  WebHelp Topic Connect to SmartX Servers Right-click on the AS and select Network Settings Modify the IP address settings to the new values Additionally, this can be changed through PuTTY with the "setip" command. Power Cycle the Automation Server (If a power cycle is not completed the AS will still have invalid data for network settings despite the physical network interface running with the new settings) Start Building Operation Workstation and log in to the Enterprise Server Select the Enterprise Server and open the Communication Tab Highlight the Automation Server that needs to be changed and modify the address field for the IP address of the device. (The Communications settings tab is enabled by selecting the Show/Hide tick icon). Click the Save button The Enterprise Server should now automatically establish communication with the AS, but if you want to speed this process you can right-click the Enterprise Server and select the "Advanced\Repair Server Communication" option. IMPORTANT: As of 1.41 if the IP address is changed on a server that is configured with a BACnet interface, the IP address and possibly the broadcast address of the IP Network under the BACnet interface must be updated manually. (see below)

Issue One of the following error messages are displayed. Internal server error Server already part of a system Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Server Cause Version Mismatch: The Automation Server is either not the same version as the Enterprise Server or it is still connected to a different Enterprise Server. If the Automation Server is still connected to another Enterprise Server then it must be detached before it can be added underneath a new Enterprise Server. User Permissions: In some instances, the User Permissions "System Address" is not added to the user account that is attempting to add the server.    Resolution If you are given an error that states "Domain: Internal Server Error" then you need to download the same version of firmware to the AS that is installed on the ES. Resolution #1: Detach the Automation Server Log in to the Automation Server.   In the system tree pane, right-click on the automation server and go to Advanced > Detach server.   The Disconnect Automation Server window will open; click yes.   The Automation Server is now detached and can be added to an Enterprise Server. Resolution #2: Verify User Permissions Check a current backup using the SBO xbk Analyzer and verify the number of servers listed under Reports>Servers Log on using the default admin account and see if these servers exist. Detach the server(s), as described above. If the secondary user still requires permission to add and see ALL servers: Go to the user and select the Permissions tab Ensure the ES path is selected Click on the Add System button (identified with the arrow) Enable all options to allow read/write, create etc.  Save these changes and log off and back on with this user to see the changes. This user should now be able to add/see ALL servers.

Issue Every item shown in the Objects window of the TGML editor can be considered a Node. In the figure shown below, this relatively simple TGML page has 14 nodes. Nodes are hierarchical with parent and children nodes. One important concept when scripting in TGML is finding the desired node. Examples of this are: Changing the color of a rectangle when a bound signal is offline Writing a new value to a text box every time the database value updates Opening a new page when the user left clicks on a component Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation TAC Vista TGML Graphics Editor Cause Within a script, there are two functions that will pinpoint a specific node, but have very different applications. These are: getTarget() getCurrentTarget() An example function of how to use these functions is: function click(evt){ target = evt.getTarget(); } Resolution getTarget() - returns where an event is coming from getCurrentTarget() - returns the parent of the script Both examples below chart the differences between the two functions using the screen capture below. If the bind object in the figure above changes its value, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Bind Component B Bind Rectangle C Bind Bind If the user clicks on the rectangle in the figure above, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Rectangle Component B Rectangle Rectangle C N/A N/A Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue A more in-depth description of each of the Direct Digital Control (DDC) modules in I/NET Product Line TAC INET Environment I/NET DDC DCUs, PCUs, MRs Two Position Module (2POS) PID Controller (PID) Float Module (FLT) Reset Module DDC Hi/Lo Module (HI/LO) Relay Module (Single Pole Double Throw Relay) Calc Module Cause DDC is a system that measures a variable, compares the variable with a known value to determine the error, processes the error using a specific software algorithm, and then produces an output to modify the controlled variable. Resolution Most of these modules are discussed in both TCON 083 or  TCON 299 System Operator Guide for more details. (The System Operator Guide is installed by default on your I/NET Host Workstation) DDC Two Position Module (2POS) This module is used where the final control element is in either one state or another opposite state (ON/OFF, OPEN/SHUT). This type of control will commonly be used for simple heating or cooling systems, starting and stopping motors, controlling water sprays for humidification, etc. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC PID Controller (PID) In Proportional (P), Proportional + Integral (PI), and Proportional + Integral + Derivative (PID) control, the control element moves linearly to a position that is proportional to the deviation and the rate of deviation of the controlled process variable from a prescribed setpoint. This type of control, in any of its three modes, or combinations thereof, is commonly used for the control of modulating valves, vanes or modulating motors where a proportional output control point is used. The proportional output control point may be either an analog output (voltage, current, resistance) or a pulse width output where the duration of the pulse is proportional to the error variation. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Float Module (FLT) Traditionally, floating control actuates a control device when the error, i.e. the difference between the controlled process variable and the setpoint, exceeds a deadband and maintains the control until the error is within the deadband. The floating controller is based on the same principle however it has been enhanced to include PID control without the requirement for analog output or pulse width position feedback. The output of this controller may be directed toward either a pair of variable pulse width discrete outputs to control a bi-directional drive motor or dual EP value arrangement which is generally described as a "pressure-vent" controller. This type of control is commonly used for the same applications as the PID controller where positive feedback is either unnecessary or economically unsound. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Reset Module (RESET) Reset is used to develop a setpoint output in an inversely or directly proportional relationship to one or two analog inputs and one or two operator-specific reset schedules. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Hi/Lo Module (HI/LO) This module is used to provide the highest and/or lowest value from two or more measured variables, most commonly temperatures. HI/LO can be cascaded to accommodate virtually any number of inputs of similar nature. Typically the lowest space temperature would be the most logical to use to directly reset the heating water setpoint. The HI/LO modules provide the control engineer with a convenient alternative method for making the selection. The HI/LO modules may also be used as an OR/NOR selector by using the state(s) of various monitored discrete points. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Relay Module (Single Pole Double Throw Relay) This module provides a mechanism for selecting one of two values or states based on conditions within the controlled environment. The actions of the relay are controlled by one discrete input and control which of two input states or values is directed to the output. The inputs and output may be either discrete or analog. The actions of this relay are analogous to its electric/electronic counterpart in its simplest form. This module is available in our PCUs and DCUs; and you can customize it for your needs.  DDC Calc Module This module functions similarly to calculations added to a point through the calculation extension editor. This module is only available in Micro Regulators (MR). It is not available in Application Specific Controllers (ASC).