Building Automation Knowledge Base

Issue General questions and best practices for RS-485 protocol including cable length and terminating resistors Product Line Andover Continuum, EcoStruxure Building Operation Environment MSTP Cause Understanding best practices for installing, cabling, and terminating RS-485 networks can avoid a lot of problems with communication and hours of troubleshooting communication problems. Resolution MS/TP MS/TP stands for Master Slave Token Passing. Each device on the link is considered the master when it has the token. If it does not have immediate need to use the token, it is required to pass the token along to the next device. This is the token passing part. All devices on the link which do not currently have the token are regarded as slaves, and are expected to listen to any messages the current master may have for it. Because all devices take turns being master, the link is effectively peer to peer. Electrically, MS/TP adheres to standard RS-485, physically wired using two-conductor shielded twisted pair cable. RS-485 Cable Specifications Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Velocity of propagation: 78% Capacitance: <12.5 pF/ft between conductors and <22 pF/ft between the conductor connected to ground and the next conductor. Topology Daisy chain bus topology. Star topology can be achieved using Infilink/B-Link repeaters. Maximum Cable Length Cable lengths of up to 4000 ft (1220m) daisy chained from controller to controller on one arm of a star are supported. After 4000 ft (1220m), a signal repeater (b-Link) is required to add more nodes to the network or further extend the cabling. Using a b-Link fiber repeater allows you to extend the length of RS-485 with fiber optic cable, recommended for running cable between buildings and through noisy environments. Maximum Number of Devices TAC's MS/TP RS-485 supports a maximum of 127 nodes overall. Each controller represents a single node on the network. RS-485 Termination The MS/TP field bus requires a 120 ohm terminator resistor at both ends of a daisy chain segment. The following diagram illustrates the connection of the terminator: Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue Can the red crosses (that indicate that a signal is offline) in Vista or SmartStruxure Workstation/Webstation be disabled? Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure TGML Graphics (Workstation, Webstation) Vista TGML Graphics (Workstation 5.X, Webstation 5.X) Cause When a signal which is bound to an object in a TGML graphic is offline, this is indicated by a red cross when viewing the graphic in Vista or SmartStruxure Workstation or Webstation. Resolution This can easily be disabled in TGML by adding a script to the OnSignalChange event: function signal(evt){   evt.preventDefault(); }  Note, this script will only disable the red X when a point is offline. This does not address any issue that might cause points to be offline. A short video is available on this process, to review, please see SmartStruxure - Graphics - Removing Red Crosses.mp4.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue An Energy Expert system is being moved to a new server and/or the virtual image is being upgraded. The historical records held in the SQL database of the Power Monitoring Expert (PME) system need to be backed up and properly restored on to the new server. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Power Monitoring Expert (PME) Enterprise Server Cause The system administrator has deemed it necessary to upgrade the Windows server that the Energy Expert system is installed on for security and/or resource reasons. Resolution It is important to remember that an Energy Expert installation is really just two Schneider Electric offers, EcoStruxure Building Operation and Power Monitoring Expert, installed together and set up to pass information back and forth. This means that appropriate steps must be followed for each system to backup the historical data and properly restore it on the new server. For more detail regarding how the system is laid out, please see the Difference between EcoStruxure Energy Expert (Power Manager) and Power Monitoring Expert (PME). Steps to move an Energy Expert database Backup the Power Monitoring Expert (PME) SQL database, dashboards and reports. The Configuration Manager tool available on the Exchange can be used to back all of these items up automatically. Run the tool on the existing server and it will create a zip file to be used later on when restoring to the new server. See Migrating a PME 8.0 System to a New Server for more information. The Schneider Electric Technical FAQs website also contains many other helpful troubleshooting articles for PME including different versions of the product. Return the Energy Expert license(s) from the Floating License manager in order to move them to the new server. For more information see Video: Licensing Guide for Power Monitoring Expert (PME) 8.x and 7.2.x and ENM 8.3.x. If moving the Enterprise Server, make a historical backup of the EcoStruxure Building Operation (EBO) ES from the existing server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES for more information. If the Enterprise Server and other EBO licenses are installed on the existing server, then they may need to be returned as well so they can be moved to the new server. See Removing a Local License or Returning a Network License for more information. Next the ETL project files must be retrieved and saved so they can be moved to the new server (if using architecture 1 in the Energy Expert offer). Go to the file location below and save all ETL project files that are needed on the new server. C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs If moving the Enterprise Server, install the EBO software on the new server, rehost the EBO licenses, and restore the EBO server backup(s). See Restoring the EcoStruxure BMS Server for more information. Install the Energy Expert software (the software includes PME, ETL and the integration utility). The information on how to download the Energy Expert software can be found on the Exchange. Once the software has been installed, the Energy Expert license can be hosted to the new server in the Floating License manager. Next, install the PME Configuration Manager tool on the new server. The zip file from step 1 can be loaded using this tool to restore the SQL database, PME dashboards and PME reports. Add the previously saved ETL project files to the same location on the new server C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs Since the server has changed, the configuration settings must be updated in the ETL projects to reflect the new server name. The settings in the EWS interface on the EBO server will also need to be updated as well. Note: It may be easier to delete the existing EWS interface in EBO and then use the integration utility to create a new XML import file to simply rebuild the interface.

Issue Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 SP1 Cause Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Resolution Setup of the NIC852 network interface for the ES is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.9 L-IP router setup is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.10   Here are some additional points not covered in the Reference Guide: To use the NIC852 as a network interface for the ES, you must configure the Loytec LConfig software to run as a service.  See Not able to get Service pin from LON devices connected with Loytec NIC from ES for more details. The L-IPs must be used in Smart Switch mode in StruxureWare.  There are two Smart Switch modes: 1.  Smart Switch Mode 2.  Smart Switch mode with No Subnet Broadcast Flooding. Only use the first of these modes.  This should be the default, out of the box.  See the L-IP User Manual for details of the DIP switch positions for each mode. The ES version 1.3 can host up to 100 Xenta devices + 100 LON devices in total. These can be divided across 5 logical networks (different domains). It is possible to have multiple L-IPs in the same network if needed - but the limit of 100+100 is per ES, not per network or L-IP. Loytec recommend that in Smart Switch mode an IP channel should have no more than 10 L-IPs and packet rates no more than 500 packets/s. If additional Xenta/LON devices are needed you can add them to one or more AS, below the ES. Observe the standard Lonworks guidelines when creating your network topology e.g. maximum number of devices per network segment, maximum length of runs for the chosen cable type.  Group your devices so that network traffic across channels is minimized. StruxureWare is unaware of your physical network topology - it just sees it as one big channel.  It will reserve a different subnet for each Xenta group you create, starting at subnet 253, but each Lonworks device you create will just be assigned the next available subnet/node address, starting at subnet 254 node 1.  This means that devices with the same subnet address will most likely appear on multiple physical channels. The Loytec L-IP in Smart Switch Mode can still provide effective routing in this situation as it builds its routing table based on the physical location of subnet/node addresses, not just subnets.  Other manufacturers' routers, even in learning mode, may not be so forgiving.

Issue What are the intervals for Trends when using StruxureWare Building Operations Product Line EcoStruxure Building Operation Environment Enterprise Server or Automation Server Cause Questions regarding what the interval in time is for trending Resolution Intervals can be in Days, Hours, Minutes, Seconds, and Milliseconds. . Trend logs can be of different types and used for different purposes. All logs in StruxureWare use circular storage. The interval trend log collects data at a specific time interval. Each logged value is stored as a record in the trend log. Use this trend log when the logging interval is less than 1 hour. You create interval trend logs using WorkStation or WebStation. In WorkStation, you configure the properties of the interval trend log to meet the specific needs of your site. The interval trend log does not record the values between the intervals. An interval log checks the monitored value at each interval and records the new value if it differs from the previously recorded value by more than the delta. Delta is the difference between the current variable value and the last log value. To log a variable according to the time interval, use a delta of zero. You use an extended trend log to transfer records from a trend log. An extended trend log can be connected to a trend log or connected in a series to another extended trend log. Only one extended trend log can be connected to a trend log. You create and configure extended trend logs using WorkStation. The extended trend log is often saved on a higher server level with more storage capacity than the server of an ordinary trend log. This extra storage capacity enables the server to store more records before it overwrites old ones. The extended trend log can be viewed in a trend log list or a trend chart. Trend log lists and records can be exported in two different formats: CSV (Comma separated values) is a standard file format for digital storage of data structured in a table of lists form. The CSV format can be used by Excel and in databases such as SQL. XML (Extensible Markup Language) is a standard file format for structured data and can be use with a lot of different tools. One last suggestion is the number of records, depending on how many records you want to store is important. For example: a single one minute interval Trend Log, and for 66 day, that would be 99,792 records. The maximum is 100,000 on an AS, so take this into account when configuring. This is why Extended Trend Logging is important. Check out Maximum number using StruxureWare Building Operation (Scalability and Capacity) for information on trends and extended trendlogs.

Issue During the installation of Workstation on a PC that didn't previously had any SmartStruxure software installed, you can get the message: "Failed to install XXXX redist, error: 3010" Product Line EcoStruxure Building Operation Environment Workstation Cause One of the build in Microsoft Visual C++ Redistributeable (VCRedist) installers (2008, 2010, 2012) is failing for some reason. Resolution Restart the PC and start the installer again Note: There is a similar issue but with error 1603, if you get this please see Getting the error "Failed to install XXXX redist, error: 1603" during installation.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue While upgrading a database from 1.7.1 to 1.8.1 that has already been prepared, the upgrade log states that a MAP file is missing (similar to one shown below), and the upgrade is cancelled and reports "Database upgrade failed!" MAP file is required for upgrading the type public.lon2.devicetemplates.pidxxxxxxxxxxxxxxxx but none could be found Product Line EcoStruxure Building Operation Environment Upgrade LonWorks Pre-upgrade add-on Observed in version 1.7.1 and 1.7.2 Cause At some point in a previous version of StruxureWare Building Operation, the import of a device template has gone wrong in the sense, that the XIF has been imported and parsed correctly, but stored incorrectly. That means that we have cases where the actual content of the XIF stored in the database, can either be another completely different XIF, or even in some cases just random files. The issue can be verified by performing a "Content Analysis" using the "SBO xbk Analyzer" version 1.0.9 and above. You'll get a message like this: Error in XIF file: Mismatching program ID (SBO: 90001347000604A0 - XIF: 90:00:13:47:00:06:04:3C) This means that Building Operation has a device template with PID 90:00:13:47:00:06:04:A0 but that the actual file this device template points to is 90:00:13:47:00:06:04:3C Resolution A hotfix has been produced to allow replacing the wrong XIF with the correct one. With the following procedure you can manually fix the issue if you don't have the hotfix: Firstly ensure you have run the Pre-Lonworks upgrade configuration and try the upgrade again. Check if the template is in use by searching the specific template while logged in directly to the server Once the device has been identified, proceed with the following steps: Record Neuron ID(s) - this is required since the Export Process does not retain this information. Export device(s) If you have multiple devices you can Export the folder containing these devices, it is not critical to export the devices individually. Delete device(s) remembering to keep references. Import latest XIF for device From WorkStation select: File > LonWorks > Device Template Browse in the correct XIF. Import exported device(s) in step 2 Commission device(s) Run the Pre-Lonworks upgrade configuration The database should now successfully upgrade.

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

Issue The built in logs for troubleshooting communications from SmartStruxure ES/AS to SmartStruxure ES/AS remove the need for network captures for SmartStruxure communications. However, SmartStruxure to BACnet continues to be ideal for traditional means of network captures. The most common capture method is Wireshark when dealing with BACnet device to BACnet device communication. Product Line EcoStruxure Building Operation Environment SmartStruxure BACnet ES AS Cause The need to troubleshoot communications issues from device to device whether this is ES to AS or vice versa. The need to troubleshoot BACnet communications Resolution Network captures are beneficial in troubleshooting the following cases: Connection issues between SmartStruxure client and AS/ES. If customers complain their client cannot connect to an AS/ES, a capture run from the client PC can be very useful. However, SmartStruxure uses TCP/HTTP and the payload is not easy to decode. There are no Wireshark decoders to help out, but the good news is that there is in communication logging built in to SmartStruxure that can replace the need for network captures. (See Error logs from the Enterprise Server for ES and see Error logs from an Automation Server and Enterprise Server for AS) Communication Status problems between servers and controllers (for example BACnet controllers). The location of where the captures is taken can be very important. The best place to capture is at a switch directly connected to the controller. This may be difficult because it will require putting a “dumb” hub between the switch and the controller or finding a port mirroring switch. When you are not receiving BACnet alarms when expected. When you are not receiving COV notifications when expected When a trendlog is trending external point To evaluate the health of a network. ARP broadcast traffic can flood networks and can create connectivity problems on BACnet/IP networks. If this is the case then a customer can take action by segmenting their BMS to a VLAN. Performance problems on graphics where a large number of the point displayed are BACnet MS/TP bus performance is poor or MS/TP device is offline Using a USB RS-485 adapter can permit the capture of packets on an MS/TP bus. Wireshark can then be used to decode the packet captures. This can show token passing problems as well as traffic loads. Also check out the BACnet-Capturing MS/TP Traffic Quick-Help video on the Exchange.

Issue What is the difference between a Numeric Input, Numeric Output and Numeric Public within a script program. Is using a Numeric Public a less efficient choice (as opposed to using a Numeric Input or Numeric Output) that will generate negative overhead in the AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Workstation b3 and Infinet controllers Cause Want to determine best practices when choosing numeric types during script programming. Resolution Numeric Input is a read only numeric (from the point of view of the script program) that accepts a binding. Numeric Output is a write only numeric (from the point of view of the script program) that accepts a binding. Numeric Public is both read and write (from the point of view of the script program). Numeric Public also accepts a binding. (A Numeric Public can be bound to both a Graphic and a Value Object to allow overriding of values from a Graphic. See SBO Script Public.zip for an example) When choosing the numeric type in a script program there is no overhead cost difference between using one of these numeric types vs the others. Also check out the Script Programming - Writing the Script Program Quick-Help video on the Exchange. NOTE b3 and Infinet Controller scripts do not support "Numeric Public", but "Numeric Output", in these controller scripts, can be used in a similar way to "Numeric Public" The Bound value is read by the script as well as being written to.

Issue The FlexNet console shows the following error Vendor daemon down: taclic No such feature or vendor does not exist: taclic Product Line EcoStruxure Building Operation Environment License Server FlexNet TACLIC Cause The taclic vendor daemon which serves the SmartStruxure licenses is down. This indicates that the vendor daemon either does not exist, or that another application using the same vendor daemon executable is present on the PC. You can run one or more FlexNet license servers with different vendor daemons, but a given vendor daemon can only be run once at a time on the PC. The SmartStruxure Building Operation vendor daemon is called taclic.exe. This can be seen as a process in the Windows Task Manager. Resolution 1. Make the SmartStruxure license server is properly installed 2. Follow SmartStruxure license and TAC Vista license on the same PC if both TAC Vista and SmartStruxure Building Operation is installed on the same PC.

Issue When trying to log on to an ES or AS using HTTPS, you get "No connection to server" or it takes a long time. Using HTTP it works fine. Version 1.6.0 and below you get "No connection to server" Version 1.6.1 and above you get in but it takes an extra 25 seconds compared to normal Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Workstation Cause The most common reason for this is that the port used for HTTPS is changed in the Software Administrator, and not added in Workstation when logging on. For a solution to that, please check Workstation Log on failure due to unidentified port. A more rare reason for this has been identified on sites with strict network policies or no connection to the internet. The reason this is happening is because an application using SSL or TLS (e.g. OpenSSL) is regularly checking for certificate revocation. That can normally only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang or fail to use SSL. For a deep explanation of certificate revocation check and the base of this article, read Citrix' article: Slow Web Interface\MMC console? CRL explained. The issue can be confirmed using Fiddler. Here is an example on how to identify the issue.: Another way to check it, is to enter the URL used to retrieve the list on the PC having the issue: http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab?baa88d4bbbfc38e4 When trying to access that URL from a PC having this issue, you should get "HTTP Error 502 Bad gateway". Resolution Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl Copy the two files to the PC having the issue Open a command prompt and navigate to the folder where the files are located Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

Issue Interfacing M-Bus meters to Modbus. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma Environment Sigma IC3-Modbus Mbus Modbus Kampstrup Heat Meter Multical 601 Cause Multical 601 M-Bus meters are required to be interfaced with the BMS. Resolution A M-Bus/Modbus converter (RS-485, RS-232 or TCP) and configuration software are required. The converter  and software are available from SyxthSense or similar suppliers. Using the converter and software setup the M-Bus/Modbus system without the BMS system connected. The M-Bus/Modbus converter will automatically assign the M-Bus registers as Modbus registers. From the software note the tables and registers used. Create the Modbus registers as required for the BMS system used. For Sigma - Create the gateway.txt, connect and configure the IC3-Modbus. A sample of the gateway.txt can be downloaded here: MultiCal Modbus Gateway.zip. For further M-Bus information see M-Bus Protocol Information. 

Issue When using the Modbus RTU X Driver on RS-485 what cable type should be used and what maximum distance would it give? Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RS-485 XDriver. bCX1, NC2 AS Cause Recommended cable type required. Resolution The Modbus RTU is a standard RS-485 network and you can use the same networking rules as per the Infinet network. As long as the baud rates are set the same you can even use an Infilink 200 or a B Link to act as a repeater. Unless the Third Party device manufacturer specifies different requirements the Belden 9182 or a similar cable that matches the Infinet specification would be suitable, again as per Infinet rules this would typically allow a maximum end to end distance of 1200 Meters. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue How do I change the Baud Rate of a field bus (either Infinet or Bacnet MSTP) if there is either an Infilink or B-link on the network? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet BACnet Cause The Infilink and B-link must have their baud rate set manually. Resolution All Infinet or Bacnet B3 controllers autobaud on initial startup or when the fieldbus commport is changed from the parent controller's commport editor. The Infilink and B-link must have their baud rate set manually. The proper procedure to change the fieldbus baud rate is to first go to the commport editor and change the fieldbus baud rate. At this point a message is sent to all field bus controllers to change their baud rate. They will all change immediately, however the Infilink and B-link have not yet changed, so the bus will now be in a confused state and there will be offline issues. The next step is to go to the Infilink or B-link repeater and manually change the baud rate to the new setting. At this point the network should work normally, however if the procedure is not followed there may be network issues where you have some controllers that are running at different baud rates causing the network to be totally shut down. If this is the case the way to resolve the issue is to make sure the Infilink or B-link repeater is set to the desired baud rate and power down or reset those controllers on the network so that they will all synch up to the correct Baud Rate upon power up. ** Changing many controllers A method that may help when needing to change the baud rate of many controllers is to bypass the b-link Connect segment 1 of the b-link directly to the BCX comm port and change the baud rate Reconnect the B-link and verify the controllers are now online, repeat the baud change if necessary. Repeat this process for each segment You may still have some isolated controllers that need to be powered off/on. Related: BACnet bCX MSTP network loses communication when a b-Link is added or removed

Issue What is the unit load of a TC300 thermostat and what are the bias and termination requirements when used with a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment TC303-3A2LM TC303-3A4LM TC303-3A2DLMS TC303-3A4DLMS SmartX Server Cause Documentation does not state the RS-485 transceiver type for the TC300 range, making it unclear how many devices can exist under a SmartX servers RS-485 serial port ComA or ComB. Resolution The answers to the transceiver interface attributes below can be applied with to the Worksheet for Configuration of RS-485 Bus with generic RS-485 devices on Webhelp Q1 Failsafe Receiver The TC300 does not use an RS-485 transceiver with an integrated idle-state failsafe receiver. Q2 Data Transmission Speed TC300 thermostats manufactured from November 2018 onward can be configured to communicate at 9600 or 4800 bps. TC-300 thermostats manufactured before this date can only communicate at 4800 bps. Q4 Isolated Interface The TC300 does not provide an isolated RS-485 interface. Q6a Measured Resistance With no electrical connections to the TC300, the measured resistance between the RS-485 low-side (-) signal and the communications common is 10K ohms. Based on this the unit load of the TC300 is 1.2 (12.000/10,000) Bias requirements and number of devices If the length of the RS-485 bus is less than 150M (500ft) then Generic RS-485 Device Configuration 3 from Webhelp can be applied. Using this configuration the recommended 3300 bias resistors present a unit load of 3.6 (12,000 / 3,300). The SmartX server adds 0.5UL. The remaining node budget is calculated as: 32 - 3.6 - 0.5 = 27.9UL. Since the TC300 has a unit load of 1.2 the maximum number of devices that can be placed under each comm port using this configuration is 27.9 / 1.2 = 23.25 If the length of the RS-485 bus is greater than 150M (500ft) then Generic RS-485 Device Configuration 7 from Webhelp can be applied. Using this configuration the dual end-point bias configuration presents a unit load of 24UL (12,000 / (1,000 / 2) = 24). The SmartX server adds 0.5UL. The remaining node budget is calculated as: 32 - 24 - 0.5 = 7.5UL. Since the TC300 has a unit load of 1.2 the maximum number of devices that can be placed under each comm port using this configuration is 7.5 / 1.2 = 6.25 Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.  h

Issue Once the occupied cooling and heating setpoints are written from a BMS, the user is not able to change the setpoint from the room controller Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Series Room controller Viconics branding VT8000 Series Multi Purpose Manager (MPM) BACnet Cause By default, the occupied setpoint value is written to Room Controller with priority level 16 by the BACnet front end. Attempting to change the setpoint locally using the up and down arrows on the SE8000 Room controller will not be allowed since the Room controller uses the relinquish value internally (priority 17) which will be automatically overwritten by the BACnet front-end. Resolution The work around is to release the BACnet front-end control over the BACnet object using a LUA4RC script. The script can be uploaded using one of the following two methods: 1 - Uploader Tool A USB cable is required to upload the script. The uploader tool can be downloaded from the Exchange Download Script Download Uploader Tool   2 - BACnet The script can also be directly uploaded via BACnet using the "Description" field as shown in the image below if (ME.AV92 == 6 or ME.AV92 == 7) then ME.AV39_PV[16] =nil ME.AV39_PV[10] =nil ME.AV40_PV[16] =nil ME.AV40_PV[10] = nil ME.AV92_PV[17] =0 end Where, ME.AV92 is the Keyboard value ME.AV39 is the Occupied Heating Setpoint ME.AV40 is the Occupied Cooling Setpoint Using this method, the script can be uploaded to multiple SE8000 Room Controllers by following the steps in Bulk Lua4RC upload via BACnet (Mass upload) For more information about Lua4RC, refer to the Lua4RC Programming Guide

Issue The ETL job configuration tool freezes when running the load sources task under the mappings tab. Product Line EcoStruxure Building Operation Environment Extract Transform Load Administration Tool (ETL) Power Manager for SmartStruxure EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause The ETL default HTTP query size is set to 10 which in some cases can impact the performance of the tool. Resolution Make sure that you read through Energy Expert (Power Manager for SmartStruxure): Best Practices. This article will provide a lot of tips to avoid issues or improve system performance. ETL locks up while loading sources Adjust the HTTP query size to a higher value. This will reduce the number of queries between ETL and the SBO Server. Close ETL. Go to the location where ETL is installed. The default path is C:\Program Files\Schneider Electric\ETL X.X (SBO to PME). Under the Jobs folder there is a project file named "JOB_ETLProjectName.xml". Open this XML file with a text editor. Search for the setting called "ContainerQueryBatchSize". It is set to 10 by default, change it to 100 and save the job. Open the ETL user interface again and try running the Load Sources task. The folder count at the bottom of the screen will increase slower then before because each call is gathering ten times as much data. Note: If the ETL tool locks up again with the query size set to 100, try other values until it is able to complete the task such as 50, 25, etc. ETL takes a very long time to load sources When dealing with very large systems it can take hours for ETL to search through the entire database for all trends. To help reduce the searching time filters can be created to restrict what is exposed to EWS. Go to the System folder EcoStruxure Web Services > EWS Server Configuration. Click on the Filter Hardware Folder tab. Under the "Filter Hardware Folder by Path" section, click on the green addition symbol. In the pop up window, name the path filter and click create. Select the newly created filter path and click on the edit symbol. Enter the path of the folder or item in the database that you want to exclude from EWS. Click Okay. Note: All filter paths created here will NOT be searched by the ETL tool. Save changes. Once the ETL tool has loaded sources and the project has been created, the EWS filters may be removed.

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 What is the unit load (UL) of the SpaceLogic SP90 PIBCV Actuators that will help me to calculate how many SP90 PIBCV Actuators can be added on ComA and ComB of a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic SP90 PIBCV Actuator SmartX Server Cause Require the Unit Load (UL) of the SpaceLogic SP90 PIBCV Actuator to calculate the number of actuators allowed on the RS-485 network.  Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SpaceLogic SP90 PIBCV Actuator range uses the SN65HVD1780DR transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/10 UL. In addition, there are no local bias resistors and therefore the 1/10 UL of the transceiver would be the total UL presented to the bus by the SpaceLogic SLP Room Unit. Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus SN65HVD1780DR 0.1 Yes None None 0.1 No Based on the above the total number of devices can be calculated as 32/0.1 = 320. The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore a SmartX Server is limited to 127 devices per com port (254 total per Server) so this should effectively be the limiting factor. However, the documentation recommends using only up to 64 devices with the same RS-485 transceiver, or 32 devices with different RS-485 transceivers.   Since the SpaceLogic SP90 PIBCV Actuator does not have an isolated RS-485 interface it conforms to Generic RS-485 Network Device Configuration 1 in EBO Webhelp.  A network consisting of only SpaceLogic SP90 PIBCV Actuators should only require a 120-ohm termination resistor at each end of the bus and not require any bias resistors. Also, check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.