Building Automation Knowledge Base

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 When attempting to edit a graphic on an SBO/EBO ES or AS the Graphics Editor, Function Block Editor or Script Editor reports it has lost connection. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Cause A second instance of the workstation is running on the same computer The firewall is blocking the connection. The password was recently changed during the same session Workstation is connected via HTTPS but there is no valid certificate Resolution Solution 1 If using Remote Desktop (RDP) to access the SBO/EBO ES remotely, a second instance of the workstation could be initiated. Close the workstation on both the remote connection and at the SBO/EBO ES. Then open the workstation either at the SBO/EBO ES or via remote connection, not both.   Solution 2 Check if the firewall has been enabled while logged in to the SBO/EBO ES or AS, and disable the firewall Here is an example for McAfee   Solution 3 Make sure the network information (such as gateway) for the PC is entered correctly.   Solution 4 If you just changed the password of the logged in user, log out and in again   Solution 5 Workstation is connected via HTTPS but there is no valid certificate. Ensure that certificates are installed and trusted on the workstation/server so that no certificate warnings are received or use HTTP to connect to the server.   Solution 6 Update the Certificate Revocation List as described in First time a TGML graphic is opened after logging in it takes a long time for the graphic to load.

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 Documentation on the MSC-MPC Microsmart controller and its associated modules. Product Line TAC I/A Series Environment Microsmart controller MSC-MPC MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO Cause Obsolete controller Resolution Click here to view the installation instructions on the MSC-MPC. Click each associated module part number below to view its installation instructions: MPC-4AO MPC-8AI MPC-2PO MPC-SSR MPC-4CO

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 How to setup and configure External Log Storage in EcoStruxure Building Operation (EBO) when using Microsoft SQL Server as external log storage. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Enterprise Server Building Operation Enterprise Central Cause You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature. The External Log Storage feature uses an external database administered by either a combination of TimescaleDB and PostgreSQL software, or Microsoft SQL server. Resolution Please see the below video demonstrating how to: Create a database and user account in Microsoft SQL (MSSQL) Server using Microsoft Server Management Studio. Configure the External Log storage connection between EBO and MSSQL server in EBO. Also please note the following: In the video the "Host address" in EBO is set to the IP address or DNS name\SQLserver instance like this: localhost\SQLEXPRESS. If the SQL server is not located on the same computer as the EBO server only use the IP address or DNS name and no instance on "Host address". The video demonstrates using the version 5 script when configuring the database in the MSSQL server, search External Log Storage - MSSQL Installation Script  to download the appropriate EBO version script. For the example query to manage user permissions download User Rights Script or see attached script.txt. If using MSSQL Express rather than the full MSSQL version it may be necessary to consult External log storage not working with SQL Server Express.    

Issue ISO 9001 certificate for Schneider Electric Buildings Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices,Other, TAC INET, TAC Vista Environment Management Certification Certificate for the Design and Manufacture of Building Management System Controllers, Devices and Electronic Systems Cause ISO9001 certificates are sometimes requested for different projects. Resolution Download the ISO 9001:2015 certificate here.

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 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 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 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 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 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 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 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 Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver. Product Line Andover Continuum Environment Modbus Protocol Cause Definition of number of nodes and points allowed using Modbus TCP/IP or RTU xdriver according to the modbus protocol. Resolution The maximum number of nodes is 254. The address range for points is 1 through to 65535. The number of addresses is limited by the controller memory. We have had ~6000 points but please note the Modbus is a polled protocol so the more points you have the longer the poll rate.   Specific Modbus RTU Details Our Modbus RTU XDriver supports the node range from 0-255. According to the Modbus specification, the node range is from 0 – 255, with 0 being the master, 1-247 being the slaves, and 248-255 being reserved addresses. After 32 nodes (1 master + 31 slaves), you may need RS-485 repeaters to ensure proper communications. This depends on a number of different items, including if the RS485 transceivers are full or quarter load. You can find the Modbus serial standard at the link below for further details. http://www.modbus.org/docs/Modbus_over_serial_line_V1.pdf

Issue Getting modbus devices to communicate to Continuum may require some trial and error. Product Line Andover Continuum Environment Continuum Modbus RTU, ModbusRTU Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Manufacturers of modbus devices may have an offset for their register values and addressing these values requires trial an error. Resolution This article was created as a starting point. There are a lot of tools and methods to get values from modbus devices communicating. This resolution discusses some important concepts as well methods for trying to bring values in. The Modbus RTU protocol is a Master/Slave style of protocol. The Andover Controls CX will be the master on the Modbus RTU network. There can be only one (1) master at a time on the Network. The Slave number is always set in the third party device. This could be either a hardware setting such as dip switches or a software setting. Modbus-IDA (also known as Modbus.org) has set the limit that the slave address can be between 1 and 247. Address 0 is allocated as a broadcast message. The Andover Controls x-driver can support addresses in the range of 0-255. The third party manufacturer should be able to tell you what the expected function codes are for the points that you are interested in. Modbus.org has defined the function codes in a very loose manner and leaves it up to individual interpretation. Andover controls supports the following standard function codes: 1-8 15,16. Since when you request information from a Modbus RTU device you receive the exact value that is in the register Andover Controls has provided some special function codes that will help to convert some of the common engineering values into usable values. The listing in the x-driver documentation shows the special function code, what is expected from the third party and the equivalent function code that is truly sent to the device. For instance if a point is a Intel float and resides in the 40,000 range then function code 245 would be used in the Andover Controls x-driver. This will still send out a function code 3 in the Modbus message but the x-driver will take the value sent in from the third party device and convert it into a usable float. Most confusion occurs when talking about the data registers, (also known as addresses or channels). Modbus.org has the following statements about the addresses in the protocol document. All data addresses in Modbus messages are referenced to zero. The first occurrence of a data item is addressed as item number zero. For example: The coil known as ‘coil 1’ in a programmable controller is addressed as coil 0000 in the data address field of a Modbus message. Coil 127 decimal is addressed as coil 007E hex (126 decimal). Holding register 40001 is addressed as register 0000 in the data address field of the message. The function code field already specifies a ‘holding register’ operation. Therefore the ‘4XXXX’ reference is implicit. Holding register 40108 is addressed as register 006B hex (107 decimal). Register number also known as address. When setting the start channel number parameter on the x-driver tab the x-driver is expecting the exact decimal address that you are looking to obtain. For instance: if a device shows a listing for the first point to occur at 40,001 then the start channel number is typically 0. This can be confusing since some manufacturers have decided to have 40,001 as being 1 and not zero while others manufacturer have decided that 40,001 is 0. There are two ways of determining how the manufacturer has started the numbering system for the device if it is not documented: Method 1 is a trial and error method. Where you set the value to minus 1 of the register address, the actual register address and plus 1 of the register address and see which one you a response from. Method 2 uses a third party software to poll all the points to see what addresses are populated. There are many shareware Modbus RTU software packages on the Web. One such program is called ModScan32 by Win-Tech. www.win-tech.com Number of channels. The least amount of channels that will be requested is 1 so number of channels should always be 1 or greater. If the data is stored in multiple channels then you will need to set the number of channels equal to the number of registers. If you are not using a special function code you will need to set up a separate numeric with a manual log with the number of entries equal to the number of channels. When you poll for the value of the channels the data will then be stored in the manual log of this second numeric. The first element of the log will be the first channel that is requested. For instance if a value is stored in registers 40,000 through 40,003 then the start channel number will be set to 0 and the number of channels would be 4. Another numeric with a manual log of 4 would be created and linked in the x-driver numeric by placing the name of the new numeric in the annex point parameter. Once the x-driver point is polled the returning information will be stored in the annex point. The manual log of the annex point will contain the data for the 40,000 register in location 1. The data for each subsequent register location will be in the next manual log location. I.E. annexpoint[4] will contain the data for register 40,003 The Modbus RTU x-driver is a poll on demand x-driver. What this means to the user is that either a Plain English (PE) program, graphic or editing the x-driver numeric will cause a poll to occur. It is best to mirror the x-driver point and use PE to poll the x-driver points. A simple program would loop through and perform a simple line of mirroredpoint = x-driverpoint. This will avoid multiple polls to the same point tying up more CX resources then necessary. Then you can use the mirrored point in programs and graphics. If you try to get values from a slave device that is offline (not responding) the x-driver will poll each point three times before it moves on to the next point. This will cause the CX scan time to rise to seconds instead of tenths of a second. It is helpful to have a single x-driver point in the third party slave device that will return a known value, (Product ID or serial number for example). This can be used to avoid running the scan time of the CX up if the slave device can not communicate. Inside of the polling program try to poll for the value of this point. If the value does not come back then skip the polling for the rest of the points for this slave device. This point can also be used as an alarm for the offline device as well. For example: 1: If ProductID1 = 15 then Mirroredpoint1 = x-driverpoint1 Goto 2 else Goto 2 endif 2: If ProductID2 = 15 then Mirroredpoint2 = x-driverpoint2 Goto 1 else Goto 1 endif Some data may come back as a value when you need only a bit of information. In this case you will need to use the Bitand operator in PE to extract the exact bit that you are looking for. As seen below the PE code will take an alarm point from a Liebert AC unit and break out the individual bits of information. AC9_Alarm1 = x_ac9alarm1 'setting the mirrored point AC9_CommFail = AC9_Alarm1 bitand 1 'extracting bit 1 AC9_LocalOff = AC9_Alarm1 bitand 2 'extracting bit 2 AC9_RemoteOff = AC9_Alarm1 bitand 4 'extracting bit 3 AC9_HiHeadPrs1 = AC9_Alarm1 bitand 8 'extracting bit 4 AC9_HiHeadPrs2 = AC9_Alarm1 bitand 16 'extracting bit 5 AC9_LossAirFlow = AC9_Alarm1 bitand 32 'extracting bit 6 AC9_StbyGlycolOn = AC9_Alarm1 bitand 64 'extracting bit 7 AC9_LiquidDet = AC9_Alarm1 bitand 128 'extracting bit 8 AC9_ChangeFltr = AC9_Alarm1 bitand 256 'extracting bit 9 AC9_HighTemp = AC9_Alarm1 bitand 512 'extracting bit 10 AC9_LowTemp = AC9_Alarm1 bitand 1024 'extracting bit 11

Issue Satchwell MZF 3-Port Flanged Valve Body requires replacement. Product Line Field Devices Environment Satchwell 3-Port Plug and Seat Flanged Valve Body MZF MZF3729 MZF3779 MZF3854 MZF3904 MZF3958 Cause Obsolescence of Satchwell MZF 3-Port Flanged Valve Body Resolution A number of alternative Schneider Electric 3-Port Flanged Valve Bodies are available to replace existing Satchwell MZF 3-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E VG311F 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L9TVG Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the VG311F 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E V321 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L8TV Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the V321 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body Similarly, the centre line to bottom of third port dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body As a result alterations to the pipework connected to the MZF 3-Port Flanged Valve Body will be required. Details of the Satchwell MZF 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric VG311F 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric V321 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric L9TVG Linkage Kit may be viewed here. Details of the Schneider Electric L8TV Linkage Kit may be viewed here. 

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 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.