Invite a Co-worker

Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

How can we help?

Building Automation Knowledge Base

1452 posts

Issue How to connect and configure current inputs to a UI module? Product Line EcoStruxure Building Operation Environment Building Operation I/O Module 16 Ch UI (UI-16) Building Operation I/O Module 8 Ch UI/4 Ch DO (Form C) (UI8-DO-FC-4) Building Operation I/O Module 8 Ch UI/4 Ch AO (UI8-AO-4, UI-8/AO-V-4) Building Operation MP-C, MP-V, RP-C, IP-IO Cause How are Current inputs connected and configured? Resolution To connect and configure a current input to a SmartX device no additional external resistors are required, the internal resistor in the SmartX device is automatically put into the circuit by selecting "Current Input" when creating the input object, there are no DIP switches to change as in some other products. An external Power supply will be required to provide the current in the circuit through the sensor and into the UI input. 24V DC supplies are usually used to power the sensor & provide the current drive. Further information regarding the SmartX device's internal resistor can be found in the Hardware Reference Guide. Example Circuit: The input point configuration allows you to define the top and bottom or the current scale (usually 4-20mA or 0-20mA) and the engineering units this corresponds to i.e. 0-100% or 0 - 400 DegC. The following screen shot example shows the configuration for a 4-20mA input signal represented as 0-100%

Issue Cannot change the IP address or host a Smart Controller MPX/RPX in a second EBO Server Product Line EcoStruxure Building Operation Environment IP address BACnet SmartX IP Controller MPX MP-C MP-V RPC CRS, IP-IO ECommission Tool eCT Cause 1. IP settings are saved (eg in eCommission Tool), but the IP address of the Controller does not change. (Option to change most settings is grayed out from eCT v3.x for hosted SmartX IP Controllers) 2. The Controller is already hosted by an EBO server and cannot be hosted by a second EBO server, thus data objects cannot be read. 3. Rehosting an MP device to a different EBO server Resolution 1. Changing the IP address "settings" can be done with eCommission Tool in some earlier versions but if the SmartX IP Controller is already fully hosted by an EBO Server, then a warm start from the eCommission Tool is inhibited. (Option to change most settings is grayed out from eCT v3.x for hosted SmartX IP Controllers) Without the hosting Server initiated warm start the new IP setting will not be used. If the SmartX IP Controller is not hosted then the IP address can be changed from the eCommission Tool, using the warm start option. Notes A local warm start initiated at the SmartX IP Controller(manually with the reset button) will not force the SmartX IP Controller to use these new settings. See MP Series Controller Commissioning Scenarios The IP address of a Hosted SmartX IP Controller cannot be modified from eCommission Tool A factory reset will force the SmartX IP Controller to return to AutoIP and DHCP 2. When a SmartX IP Controller is fully hosted by an EBO Server, it can be BACnet hosted by a second EBO Server, but this will only contain the standard BACnet Applications folder. This hosted BACnet Device needs to be manually created using the SmartX IP Controller instance Id. Below, it can be seen that the fully hosted SmartX IP Controller and the BACnet only hosting under ASP_22 3. When a SmartX IP Controller is configured or programmed via the hosting EBO Serving using WorkStation, some of the objects (eg. Scripts or Function Block) data is not fully contained within the SmartX IP Controller . Thus if the hosting EBO server is changed, some of the configuration data will be lost and a simple upload to the new hosting EBO Server will not upload all the data required to recreated these objects. In such a case, an export from the original hosting EBO Server should be imported into the new hosting EBO Server to ensure no data is lost.

Issue What is the unit load of a TC900 thermostat and what are the bias and termination requirements when used with a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment TC907-3A4LMA TC907-3A4DLMSA TC907-4FMSA TC907-3A4DPMSA TC907-3A4DPMSA-24 TC903-3A4LMA TC903-3A4DLMSA TC903-4FMSA TC903-3A4DPMSA TC903-3A4DPMSA-24 SmartX Server Cause Documentation does not state the RS-485 transceiver type for the TC900 range, making it unclear how many devices can exist under a SmartX servers RS-485 serial port ComA or ComB. Resolution Use the Worksheet for Configuration of RS-485 Bus with generic RS-485 devices on Webhelp to determine the appropriate Modbus configuration. The answers to the transceiver interface attributes below can be applied to complete the worksheet. Q1 Failsafe Receiver : The TC900 uses an RS-485 transceiver with an integrated idle-state failsafe receiver. Q2 Data Transmission Speed : TC900 thermostats can be configured to communicate at 4800, 9600, 19200 or 38400 bps. Q4 Isolated Interface : The TC900 does not provide an isolated RS-485 interface. Q6a Measured Resistance : With no electrical connections to the TC900, the measured resistance between the RS-485 low-side (-) signal and the communications common is 8.2K ohms. Based on this the unit load of the TC900 is 1.46 (12.000/8,200) Bias requirements and number of devices If there are only TC900 devices on the RS-485 bus then Generic RS-485 Network Device configuration 1 applies, configuration becomes very simple and no node or distance reductions are called for. The failsafe receivers can typically operate with no added bias resistors. Connect a 120 ohm termination resistor across the + and - data lines at the head end of the bus (typically at the SmartX server). Connect another 120 ohm termination resistor across the + and - data lines on the last node at the far end of the bus. Connect the shield drain wire to earth ground terminal rail in the panel with the SmartX server. This is the only ground connection of the shield for the complete cable segment. Connect the RET/Shield terminal (see the figure below) on the SmartX server to the ground rail in the panel using a 12 AWG (3.31 mm²) to 18 AWG (0.82 mm²) wire. Since the TC900 has a unit load of 1.4 the maximum number of devices that can be placed under each comm port using this configuration is 21 (31.5 / 1.46 = 21.5) Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue There is no full end to end description on how to test SNMP alarms in SmartStruxure 1.6.1 and later Product Line EcoStruxure Building Operation Environment SNMP Alarms Cause Only a guide on how to create the SNMP alarms is available, but there is no guide available on how to test them. For general information regarding SNMP traps, refer to the following Web Help links: Versions 1.6 and 1.7 SNMP Notification Properties Create SNMP Notification Wizard – SNMP Notification Page SNMP Notification View Version 1.8 and later SNMP Notification Distribution Method Create Notification Wizard - Configure SNMP Page Resolution Download and install "MIB Browser" from iReasoning Download the mib file for SmartStruxure Load the SmartStruxure mib file into the MIB Browser through "File"-->"Load MIBs", and select the SmartStruxure mib file Create a simple alarm in SmartStruxure and make it trigger on a digital point Create a SNMP notification with the following settings. To get to the conditions/filter, open (double click on it or hit enter) the SNMP notification. Only showing the properties of it will not show the filter settings. "Address" is the address of the SNMP manager that receives the SNMP notification, in this test "localhost" since the SNMP manager is installed locally. "User name" is the user name of the user on the SNMP manager that receives the notification. In filter settings, select normal and alarm state, and add "Source server = *" as a condition In the MIB browser, select "Tools"-->"Trap Receiver" Trigger the alarm in SmartStruxure An alarm will now be seen in the MIB browsers trap receiver window

Issue BACnet Multistate is showing the numeric value of the selection, instead of displaying the text associated with that selection. Product Line EcoStruxure Building Operation Environment TGML Graphic BACnet multi-state-value Cause If BACnet multi-state-value text values are required to be shown on a graphic, rather than the integer value, then the DynamicText option is needed to be used rather than DynamicValue option when creating the graphic. Resolution Below shows what happens when you use DynamicValue for a MultiState Bacnet points Below shows what happens when you use DynamicText for a MultiState Bacnet points NOTES 1. If WebStation still shows only the Integer value rather than the correct text, it may be network routing/firewall related. In this case check the WebStation graphics from different addresses and test direct to the AS and logged on via the ES to gain a better understanding of the issue 2. Graphics can be created using translation/substitution, this may be a workaround, if the network routing/firewall cannot be adjusted

Issue EcoStruxure Building Operation - Sigma logging does not work. Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Sigma logging has been transitioned to EcoStruxure Building Operation, but does not work. Resolution The Procedure is as follows; Import the log data sets from Sigma to EcoStruxure Building Operation. Highlight "Log Sets" in the system tree under the Sigma Interface and select to "Send log sets" To confirm that the controller has started logging, select the appropriate controller, and choose "Diagnostics" and "Log Set Statistics" where you can see the statistics which include the log set/object details. To upload the logging, highlight the required log set and select "Retrieve Logged values". To review the uploaded data, highlight the required log value and view it as required Once that the logging in the Sigma controllers is working correctly to EcoStruxure Building Operation, logging from the Sigma server should be disabled.

Issue Sigma Transition issues upon Data Import the Sigma Server fails Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Sigma Building Operation Enterprise Server Cause Sigma server fails when an EBO data import is initiated. Resolution It is important that the Sigma Database is checked with the Doctor utility (found in SigmaX) before a Sigma transition into EBO is undertaken. Longtext - Longtext file contains 'mandarin' type characters - probably from previous BAS/Sigma upgrades. If the file contains these, then Longtext has probably not been used in the past or currently. Delete File, it will self re-create. Shorttext - Shorttext contains an incorrectly formatted entry. Find entry and correct. To find, delete 1 -250, if it continues to fails, the entry in question will be in the range 251 to 500 and keep halving until the entry is found. Index A errors - index contains a looping segment, where the page references itself. Correct index as necessary. Index A errors - page is referenced more than once, i.e. the index page can be opened via two (or more) routes. Correct Index as necessary. Note: the Index should be checked with SigmaX before a transition. Object corruption - open object in Sigma, if it fails to open, then correct by whatever means that is required. Note, Sigma server will fail at a point during the Data Import. Log Sets - Fail to import log sets. To find, in Sigma, locate the logset.rec in the c:\sigma\data\server...folder file, take a copy. In Sigma, delete 50% of the log sets and try the import again. If it fails, delete another 50% and repeat. Or if it succeeds, then the issue may lie in the 50% of log sets originally deleted, re-instate these using the copied logset.rec file and try again by deleting the other 50% and so forth.

Issue Clarity is needed on the new License Inheritance feature which is has come into EBO from 3.x Product Line EcoStruxure Building Operation. Environment Building Operation Enterprise Server Building Operation Automation Server (AS-P, AS-B) Cause The evolving Licensing Model of EBO has offered the option of Embedded Licenses in AS, such as SNMP Licenses, since EBO 2.x. The concept of Inheriting Licenses from an ES into an AS is a new option which can be used from EBO 3.1 onward, although the original embedded AS License option still remains, but what does this actually mean? Resolution In EBO 3.1, SNMP Licences may be inherited from an ES into any AS. For an EBO system with 1 x ES and 10 x AS, the ES would only require 1 x SXWSWSNMP00001. In EBO 3.2 SNMP and TimescaleDB. Licences may be inherited from an ES into any AS in the same manner.

Issue How fast does the software run in an AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Cause Knowledge about application cycle time is important when designing project solutions. Resolution Both Function Block and Script programs run at a speed defined by the specific time task they are linked to, the available tasks are: Task 1 - 100mS Task 2 - 500mS Task 3 - 1 Second Task 4 - 5 Seconds Task 5 - 10 Seconds Programs that are not cyclic or time based can be run from a main or executive sequencing program. The AS cycle speeds are comparable to other Building control systems, but the power of the AS allows many more programs to be run in parallel at higher speeds. See also the WebHelp topic Application Scheduler for more information.

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix. Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, OTHER, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue Missing LNS plugins for EcoStruxure Buildings Operation Workstation Product Line EcoStruxure Buildings Operation Environment Building Operation Workstation Cause Plugins for EcoStruxure Buildings Operation are not included in these releases. Resolution Download the TAC Vista 5.1.9 tool pack and this will install the 100 series controller plugin and Z-Builder programming tool. Once this is installed EBO will be able to access these plugin when used with Open LNS. Download the TAC Vista 5.1.9 Toolpack - Software from Exchange Extranet. Direct Download also provided.

Issue What are the basics steps when setting up the Engage Mobile application to use it for the first time? Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) Cause The Engage mobile application enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. Resolution Below are the basic steps when setting up the Engage Mobile application to use it for the first time: First create and configure the Occupant App Menu object. Make sure Bluetooth is enabled for the RP-C. Download the Engage mobile application and connect to the RP-C Available on App Store and Google Play To see details for every step please see video:

Issue The Local Variables Pane in the Script Editor is not displaying local variables or arrays. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Local Variables Pane can only be used in debug mode, i.e. when pressing Start and then either Step or trace (Trace On) through the script. When the Script Editor is not in debug mode the Local Variables Pane is empty. Note that the debugger is not available at all when editing scripts in the RP-C or MP-X, or when using Script Event Programs. Resolution Click Start in the Debug tool list at the top of the Script Editor (or press F5) to start debugging. The local variables will now be visible in the Local Variables pane. If you have arrays you can expand them by clicking the plus sign. Next use the Step button (or press F10) to step through the program. The values of the local variables will change as the script is executed line by line. ClickTrace On to automatically step through the program. ClickTrace Off to stop the automatic stepping. For troubleshooting purposes, values can also be updated directly by editing the entry in the Value column in the Local Variables pane.

Issue When there are multiple displays, and the script editor is in the right window, the autocomplete popup window goes off-screen. *note* this only happens in full screen Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The issue depends on which way you assign the two monitors in the Windows settings or how you have the monitor cables hooked in the docking station/laptop. Resolution Swap the physical monitor plugs on the PC or docking station, allowing Windows to recognize your monitors synchronously from left to right Go into your Windows monitor settings and drag each screen to its proper position and hit apply.

Issue When SmartStruxure and TAC Vista is installed on the same PC, the license system for one of the products doesn't work properly and you get no license. Product Line EcoStruxure Building Operation, TAC Vista Environment Flexera license system Cause SmartStruxure and TAC Vista uses the same license system vendor and also the same vendor daemon. That causes a conflict, and a special configuration is needed. Resolution To move a TAC Vista license to the EcoStruxure Building Operation(EBO) license server See video: Or follow the steps below: Disable TAC Vista's license server and host the TAC Vista licenses in the SBO license server. Stop and disable the service "TACLicenseServer". This is done through "services" (Start-->run-->services.msc) on the PC. Make sure the correct license setup is made for TAC Vista. Refer to No license after reboot when TAC Vista Server (TACOS) runs as a service for further explanation. Create a folder for the TAC Vista licenses as a subfolder in the SBO license server installation folder. Give it the name "licenses" and place all TAC Vista customer licenses here. Do not place demo licenses in this folder. Open the SBO license server web page (http://localhost:8888) preferably with Chrome or FireFox Click on "Administration" Sign in using "admin" as user name. If you have logged in before, use the password you have defined. If not, enter "admin" as password and create a password as indicated in step 6a and 6b. If it is the first time you log in, enter a new password and click "Save". If it is the first time you log in, now click "OK". Click on "Vendor Daemon Configuration" Click on "Administer" Click the field "License File or Directory" and enter the folder name "licenses" on a new line. Scroll down and click "Save" Restart the SBO license service (Building Operation 1.6 License Server) Additional notes If your TAC Vista license is locked to a dongle, you need to replace the SBO vendor daemon file (taclic.exe) with the on from the license server hotfix produced for TAC Vista 5.1.9. Please contact Product Support Services for assistance and refer to this article.

Issue Modbus write command setup and timing Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P, AS-B) Building Operation Enterprise Server (ES) Cause The Modbus value keeps being sent to a Modbus register (when write code 06 or 16 used) Resolution Control of the write timing is via the binding to the Modbus point within the Modbus network. If the Communication type is set to "Periodic" then the value will be sent based on the Period Communication Interval. If the Communication Type is set to "Change of Value" then the value will only be written when the value changes by this amount. The Re-transmit Interval should also be considered, as the register will also be written to based on this timing value, regardless as to whether it has changed or not. This value may need to be increased if the value should not be re transmitted apart from when the value changes. Up to v1.3 v1.4 and later Some Modbus devices get over these sort of issues by having a mode that can be set so that re-transmission of the same value is ignored, as the example below NOTE Block (Batch, Multiple) Writes are not supported (correct as 2020 01 01 and up to v3.1) Although they are used to write to 32, 48 & 64 bit Register types (so "Write Multiple Registers" packets will be seen when writing to 32, 48 or 64 bit registers)

Issue Poor communications, communications failure or packet being corrupted Product Line Andover Continuum,EcoStruxure Building Expert,EcoStruxure Building Operation,Satchwell MicroNet,Satchwell Sigma,TAC INET,TAC Vista Environment Communications networks, BACnet MSTP, LON FT10, Infinet, Modbus RTU, Ethernet EMC (Electromagnetic compatibility) VSD Variable Speed Drive, VFD Variable Frequency Drive, Inverter Drive Cause Electrical Interference from Inverter (variable speed drives or VSD) Radiated or Induced RFI (Radio Frequency Interference) Resolution A VSD has the potential to create a large amount of electrical noise, to avoid causing issues it is vital they are installed as the manufacturer's instructions. (Other devices also have this potential) Our systems are often used to control VSDs on fan motors, so if poor communications is found during the commissioning process, then try stopping all the fans in the area then re-testing the communications. A recent example was seen where LON FT10 communication was working ok until some VSDs were started, at this point LON devices and Object went offline intermittently. When all the VSDs were stopped the communication become completely stable. It was then possible to find which VSD was causing the problem and correct the VSD installation. In this case a LON analyzer would also have helped diagnose the issue.

Issue BACnet devices not found but are visible in other third party BACnet applications An update may cause devices to go offline Product Line EcoStruxure Building Operation Environment BACnet IP Network Building Operation EnterpriseServer Building Operation Automation Server (AS, AS-P, AS-B) Cause According to BACnet routing rules, each BACnet Device should have a unique BACnet Instance ID and each BACnet Network should have a unique BACnet Network ID When a BACnet interface is created on an EBO Server, a BACnet IP network is created with default Network ID of 1. This is a local Network address and in not published on the network, it is therefore not a problem if this is duplicated with other EBO Servers. On many site this will remain at 1 for multiple EBO servers with no problems. If a third party BACnet device uses a published Network ID that is identical to the EBO local Network ID, then it will be ignored. There will be a "Duplicate of local network" System Alarm and line similar to below in the trace log "nsp.pin.BACnet Device <device name>claims to be router to Network #1234 but that is a local network (BACnetMain)" Resolution If the EBO Server is not finding a BACnet device on a different network type (via BACnet routing like MSTP or virtual IP) then it could be the Network ID is identical to the local EBO Server Network ID. If this is the case, then simply change the EBO local Network ID and retest. BACnet Devices on the same IP network, including those on different IP subnets and linked via BBMD or Foreign Devices are not BACnet routed and therefore will not have this issue (no BACnet Network ID route is involved) Some earlier versions of EBO did not ignore these duplicate Network IDs, thus when up grading some devices could go offline. The workaround would be the same. The correction to the BACnet operation occurred in v1.9.3 and v2.0.2

Issue Living Space Sensore goes offline after upgrading SmartX Controller firmware from 2.0x to 3.01 or later Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) v3.01 or later Building Operation SmartX Living Space Sensor Cause Living Space Sensor RJ-45 connector is plugged into Room Bus port on RPC. Resolution Move RJ-45 connector from Room Bus port to Sensor Bus port.

Issue Timestamps in Script programs are different by an amount equal to the UTC offset of the workstation's timezone settings. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B) Building Operation WorkStation Script editor Cause Take the following program as an example: Datetime Output TimeOut, TimeOut2 TimeOut = StrToDate ("1/17/2012 15:00") TimeOut2 = StrToDate ("1/17/2012 3:00 PM") In StruxureWare Building Operation, the values will read: "1/17/2012 9:00:00 AM" (in this example, the UTC offset is set for -6). In servers, all time values are stored in UTC, then the offset is applied by the client. When it receives a value from a Script program, it stores the value as UTC, then the offset for the selected timezone is applied. Resolution There are two workarounds: On the Workstation PC, set the PC's time to UTC Write code in the Script program to adjust the time values to UTC. Also see the example code below to help understand operation Datetime Output dtOut1 Datetime Output dtOut2 String Output str1 dtOut1 = Date 'Local time; displays with added UTCOffset dtOut2 = Date - UTCOffset 'Local time, adjusted by the UTCOffset, displays properly Print Date to str1 'Local time String value displays properly (UTCOffset system variable was added in v2.0)

Starting your topic is just steps away!

Join Exchange for free and get unlimited access to our global community of experts.

Invite a Co-worker

Invitation Sent

Building Automation Knowledge Base

Configuring a Current Input

SmartX IP Controller MPX/RPC IP address settings and BACnet hosting

TC900 Modbus bias, termination and number of devices

Testing SNMP alarms

BACnet Multistate not shown correctly on graphics

Sigma Transition to EcoStruxure Building Operation - Sigma Logging operation

Sigma Transition Issues

AS Licence Inheritance from ES in EBO 3.x

Automation Server software cycle time

Installation Guidelines for Electromagnetic Compatibility (EMC)

LNS plugins for SmartStruxure are not included in the release.

Configuring the Engage Mobile app

Local Variables Pane in Script Editor is not displaying local variables

Autocomplete window is off screen in Script Editor

SmartStruxure license and TAC Vista license on the same PC

Modbus write command setup and timing

Poor data communications, communications failure or packet being corrupted

BACnet devices not found but are visible in other applications

Living Space Sensor goes offline when upgrade RP-C firmware

Timestamps vary by the UTC offset in scripts based on WS timezone

Support

FAQ

About

Invite a Co-worker

Invitation Sent

Building Automation Knowledge Base

Support

FAQ

About

Starting your topic is just steps away!

Connect with Peers & Experts

Get Support in Our Knowledge Base

Ask Questions. Give Solutions