Building Automation Knowledge Base

Issue After the successful installation of Continuum 1.9x, users are receiving a DCOM Permission error when logging on to Continuum webClient. The error is intermittent. Product Line Andover Continuum Environment Microsoft Server 2008 Standard Microsoft Windows 7 Continuum 1.9x and 2.0 Continuum webClient Server Remote Desktop Cause When a remote desktop connection is made on Windows 7 or Windows 2008 Server the console occasionally gets locked. It stays locked until the local session is restored with a logon. Resolution Create a .bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console **************************************************************************************** Place this file on the desktop of the Continuum webClient Server system. When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be run "As an Administrator." This will disconnect the session and restore the console.

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 After successfully setting up KIOSK mode to automatically login in to WebStation another user wants to login through WebStation on the same PC. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Cause The GUEST account login URL used with KIOSK mode retains the last user logged in and the WebStation menu bars have been removed so that user cannot "logout". Any subsequent attempts to access the WebStation using the same browser result in being automatically logged in under the GUEST account. Resolution The "KIOSK" link that you create will login automatically with the GUEST account as long as the GUEST account has already been created in the ES/AS. This then must set the "last credentials" in IE for that website and any subsequent connections to that server, even to the direct login URL, result in automatically being logged in with those last credentials. One of the two options below should work to disable GUEST login depending on where your ES is located. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port while Building Operation Workstation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation Workstation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. To be prompted for a login: Disconnect the ES/AS with one of the options above. Then try to connect to the server page at "http:/localhost:444" (or your specific URL:Port). This results in a "this page can't be displayed" (or similar) message. Then start the service, or reconnect cable, and again attempt to connect to "http:/localhost:444". You should be presented with the login page. Do not try to open up the "KIOSK" URL or else this will again login with the GUEST account and you'll be back to square one. The next time you use the "KIOSK" URL it will automatically login with the GUEST account and this will again be used for subsequent logins until the above steps are repeated. Note1: This could result in loss of data while the Enterprise Server is stopped. Note2: Also see StruxureWare Building Operation Workstation Auto Login feature locked if encountering this issue with a Workstation.

Issue The upgrade fails, and you may get the following error message: Warning Error: Could not create remote directory. Product Line TAC Vista Environment TAC Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause To upgrade the Xenta Server system software to version 5.1.3 and later, Xenta Server HW 2.0 or later is required (otherwise the upgrade will fail). All Xenta 700 have HW 2.0 or later. In some cases the file system of the Xenta Server can be corrupt, which prevents the upgrade software to connect to the device.   Resolution First of all, try to do the upgrade a second time. If the upgrade still fails, please do the following: Check if you can ping the device and that port 80 or 443 aren't blocked. If the above is ok, format the device from the console by typing "format". (Warning: All data will be lost!) Install the system software again. If it still fails, replace the Xenta Server. Please note that If the Xenta Server is HW 1.1 or earlier you can only upgrade to version 5.1.2 or earlier. If you have to upgrade to 5.1.3 or above you need to replace the Xenta Server to a unit that has HW 2.X. (See also Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller)

Issue No Communications when directly connecting to a MicroNet Controller. Product Line Satchwell MicroNet Environment MicroNet controller (MN300, MN440, MN500, MN620 or MN350, MN450, MN550, MN650) using VisiSat Cause Controller subnet setting incorrect. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Go to the VisiSat server on the taskbar by the clock.      Drop down the Network menu Then select restart. This will reset the controller subnet setting to 1 Now the Visisat server should be able to connect to the controller.  

Issue TAC Xenta Server webpage does not work smoothly. A typical example is when you try to change a value. The small dialog that should pop up to change a value might pop up and immediately disappear. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment TAC Xenta Severs Xenta 511, 527, 701, 711, 721, 731, 913 TAC Vista 5 Webstation Cause Using unsupported version of Java may cause various issues. For example, Xenta server webpage does not display smoothly, time schedule does not show up or can not be edited, etc. Resolution Below is the Java compatibility matrix of TAC Vista 5.   5.1.9 5.1.8 5.1.7 5.1.6 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Java 1.5 update 06               X X X X X X X Java 1.6 update 11           X X               Java 1.6 update 17            X 1                 Java 1.6 update 20 X X X X X                   Java 1.7 update 51 X                           1  TAC Xenta Server 5XX/7XX/913 SP1. Log into The Exchange and then click here to download the full Vista Compatibility Matrix. To uninstall an unsupported version of Java and install the supported version, refer to Xenta Server webpage automatically logs out while waiting for Java to load.

Issue The EWS interface in the SBO system tree shows as online but when browsing to the hardware folder all that shows up is the class folders, no objects are loaded.   When reviewing the settings in Security Expert EWS Manager.exe a prompt showing "Please set the password" is shown before loading the main configuration window.   You can then see that the Operator Password field is blank and that subsequent attempts to set this and save seem to work but when closing and re-opening the Configuration Manager that the password is not saved. Product Line EcoStruxure Building Operation, Security Expert Environment Security Expert Cause The current language for non-Unicode programs is set to a value other than English. In one specific case this was set to Chinese (Simplified,PRC). Resolution In the Region and Language settings for Windows go to the Administrative tab and select Change system locale... Set this to English, save and reboot the machine. The Operator Password should now be able to be set in the EWS Configuration Manager and EWS connection established.

Issue Getting the following error message when attempting to open a Niagara R2 Enterprise Server station: ERROR: Cannot open web server socket. [ServerLoop.run] java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(Unknown Source) at java.net.ServerSocket.bind(Unknown Source) at java.net.ServerSocket.(Unknown Source) at tridium.nre.drivers.SocketDriver$TcpSocketFactory.createServerSocket(SocketDriver.java:681) at tridium.nre.drivers.SocketDriver.createServer(SocketDriver.java:203) at tridium.foundation.net.TWebServer$ServerLoop.run(TWebServer.java:754) at java.lang.Thread.run(Unknown Source) Product Line TAC IA Series Environment Niagara R2 Enterprise Server all version Cause Windows IIS is enabled on Enterprise Server PC. IIS and WorkPlace Pro (station database) have a conflict issue related to Port 80. By default, IIS connects and utilizes Port 80 when installed and running. This directly conflicts with an Enterprise Server’s station database running on the PC which also uses Port 80 by default. Resolution Most times, users do not require IIS on the Enterprise Server or WorkPlace Pro PC so IIS is disabled. If IIS is required, users typically change the port used by the station's database to another port (e.g. 8080, etc.). If this change is made, all other settings that access this IP for the station (address table entries, web browser pages, etc.) must append the port number to the IP address (e.g. 192.168.1.142:8080). Disable the IIS if not required by some other application on the Enterprise Server PC. Select Start and open the Control Panel Double-click add remove program Click on “Add/Remove Windows Components on left side on screen Scroll down and deselect Internet Information Services in the Components window Click next and Finish The Enterprise Server station can now be opened. Note:  On Windows 7 host computer, the World Wide Publishing Service may be linked to IIS.  Go to 'Services' in Windows 7 and modify its startup to 'Manual' so that it does not start automatically.  If IIS is needed on the Enterprise Server PC, then change the port used by the Enterprise Server. Open WorkPlace Pro Admin Tool and stop the Enterprise Server Open the Enterprise Server offline Right-click on the Enterprise Server station and open its Properties sheet Click on the Config tab Change httpPort to the desired port number and click Apply Right-click on the Enterprise Server and Save Close the Enterprise Server station Open Admin Tool and start the Enterprise Server station  Once the station starts you should now be able to access it. Please note that the port number must now be included in the station's address when accessing the Enterprise Server.

Issue After updating the computers Java version to Java 7 update 51, graphics are not displayed when using Webstation. Then a security warning is displayed. Missing required Permissions manifest attribute in main jar: http://xxx.xxx.xxx.xxx:/com.SE.webstation.Main/applet/applet-1.4.1.68.jar If you don't see the error above, but just get a blank window, please refer to Webstation graphics not working after updating to Java 7 Update 65. Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC Vista Environment Webstation Cause From Java 7 Update 51 and onwards, Java has enhanced the security model to make user system less vulnerable to the external exploits. The new version of Java does not allow users to run the applications that are not signed (Unsigned), Self signed (not signed by trusted authority) and the applications that are missing permission attributes. Risks involved in running each kind of applications: Unsigned applications An application without a certificate (i.e. unsigned apps), or missing application Name and Publisher information are blocked by default. Running this kind of application is potentially unsafe and present higher level of risk. Self signed application (Certificate not from trusted authority) An application with self-signed certificate is blocked by default. Applications of this type present the highest level of risk because publisher is not identified and the application may be granted access to personal data on your computer. Jar file missing Permission Attribute Permissions Attribute verifies that the application requests the permission level that developer specified. If this attribute is not present, it might be possible for an attacker to exploit a user by re-deploying an application that is signed with original certificate and running the application at a different privilege level. Resolution As a workaround, the user can use Exception Site list feature to run the applications blocked by security settings. By adding the URL of the blocked application to the Exception Site list allows it to run with some warnings. Steps to Add URL to the Exception Site list: In control panel go to the Java Control Panel Click on the Security tab Click on the Edit Site List button Enter your site details (This example http://www.SBO-Site.com) Click the Add in the Exception Site List window. Select continue Repeat the process until all the sites AS/ES have been added. Then select OK to complete and OK on the next window to exit the Java control panel. Next time you use Webstation to access the AS/ES you will be asked if you want to run the application. Tick the box so this is not displayed again. Then select Run. The graphics should now be displayed. You will need to repeat this process on any computer you which to use Webstation on.

Issue Internet Explorer on Windows Server 2008 (R2) gets "Incorrect User or Password, please try again" or "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" when logon to the Webclient server. Product Line Andover Continuum Environment Webclient 2.0 Windows Server 2008 / 2008R2 Internet Explorer 9, 10, 11 Cause Internet Explorer security issue and the compatibility issue. Resolution Change the setting of the IE 11 on Server2008 as below: When Webclient logon from IE gets error "Incorrect User or Password, please try again": Set the Webclient server a Trusted site : From IE menu, select Tools -> Internet Options -> Security tab -> select the Trusted sites and click the Sites button -> add the Webclient to the Trusted Sites list. When Webclient logon from IE gets error "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" : Set the Compatibility View: From IE menu, select Tools -> Cmpatibility View settings -> add the Webclient name or IP address to the Compatibility View list. Also refer to:  Do we support 64-bit Internet Explorer for use with WebClient? HTTP Error 500.21 Internal Server Error logging into WebClient. or ASP.NET setup custom has stopped working when trying to register .NET 2 using aspnet_regiis.exe Invalid user name or password dialog when logging into webclient with acc that works in Continuum Error: "Unable to load the .Net control for this page." when trying to open a schedule or trend log in WebClient

Issue If more than 3 Operators are created in Security Expert, the License page of the Thick Client will show more Licenses in use than the maximum three (3) clients provided with the standard SX-SRVR License. To see what the site is using, select About > License and scroll down to the Feature: Web Operators. As shown below, there are four web operators active out of the three (4/3) allowed. Product Line EcoStruxure Security Expert Environment Licensing Cause A Web Operator is defined as any Operator who can log onto the Security Expert Server using a browser.                           In the example shown below there are four Operators: admin 2nd Operator 3rd Operator 4th Operator The system allows each to log in successfully: The License option SX-WEB-OPR enables 'x' number of browser connections depending on customer needs and should effectively ensure that the correct number of Operators are purchased. However, the feature is currently in development and is not yet enforcing limits on the number of web operator connections.  This allows the number of connections to exceed the maximum limit (I.e.4/3) for the time being. Resolution Note: The Operator does NOT even need to be logged on for the count to register 4/3, the fact that 4 operators have been created is enough. The restriction of operators via Web Client could be enabled/enforced at any time in the next release of the software, so it is strongly advised to purchase the correct number of Licenses required at the time of installation, to prevent a loss of user connectivity going forward.

Issue When trying to download a b3866 device, receive an Untranslated BACnet Error. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (AS, AS-P, AS-B) BACnet b3 or Infinet i2 Controller Cause Infinet ID 0 or duplicate Infinet Id Resolution Export the objects in the controller. Delete the b3866 (or other b3 or i2) controller. Re-learn the controller. Manually assigned the Infinet ID to the next one available. Software reset the b3/i2. Download the b3/i2. Back up to flash. Import the objects. Download the b3./i2. Back up to flash.

Issue Spare Satchwell valve gland kit & grease, reconditioned 'O' rings and lug nuts options. Satchwell packing kits, Satchwell gland kits, Satchwell stuffing glands. Product Line Field Devices Environment Satchwell valve Gland kits Packing kits Stuffing Gland Part Numbers: 0617-9-410, 0617-9-411, 0617-9-412, 0617-9-413 0618-9-210, 0618-9-510, 0618-9-511, 0618-9-512 0623-9-201 0626-9-203, 0626-9-204, 0626-9-310, 0626-9-311, 0626-9-312, 0626-9-313 0667-9-201 Cause Spare item part numbers Resolution   Valve(size) Part No Description Stock 1/2"…..1" 0626-9-313 LUG NUT AVAILABLE   0626-9-312 LUG NUT AVAILABLE   0617-9-410 RECON KIT "O" RINGS & TOOL AVAILABLE MB 1 1/4" 0617-9-411   AVAILABLE MB 1 1/2" 0617-9-412   TOOL AVAILABLE MB 2" 0617-9-413   AVAILABLE MBF 65mm 0618-9-510   AVAILABLE MBF 80mm 0618-9-511   AVAILABLE MBF 100mm 0618-9-512 RECON KIT "O" RINGS AVAILABLE MEU, FEU & VEU 0623-9-201 REPLACEMENT GLAND KIT & GREASE OBSOLETE MJF 0626-9-203 REPLACEMENT GLAND KIT & GREASE AVAILABLE MZ 1"..2" series 3       VJF       VSF 15..25mm       VZ 0.5" .. 2" series 1 & 2               MZX 0.5" .. 2" 0626-9-204 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZX 0.5" .. 2"               MZ 0.5" .. 2" series 1 0626-9-310 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZ 1" .. 2" series 1               MZF 65 .. 150mm 0626-9-311 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZF 65 .. 150mm series 1               VSF 32 .. 50mm 0667-9-201 REPLACEMENT GLAND KIT & GREASE AVAILABLE VV 0618-9-210 RECONDITIONING KIT AVAILABLE Download the drawing for the MB 0617-9-410 (0.5" to 1") Download the drawing for the MBF 0618-9-511 (80mm) Download the drawing for the MZX 0626-9-204 Download the drawing for the VZ/MZ 0626-9-310

Issue Do IP settings go to defaults when flashing from 4040 to 9640? Product Line Andover Continuum Environment bCX9640 bCX4040 Cause Have a need to flash a controller from bCX4040 to bCX9640 over a remote connection access. Do not want to have to go to the site to reset IP settings.  Resolution Using CyberStation v1.93 a bCX4040 was flashed to a bCX 9640 and it did NOT lose its IP info. Notes: At the end of the upgrade an error was received: “The uprev could not communicate with the specified controller”. From the webpage it was noted that the IP address had not changed and the upgrade was successful. It did not come back online in CyberStation. From the webpage, resetting it still did not bring it back online in CyberStation. Changing the model number in CyberStation to bCX9640 (from bCX4040) to bring it back online was not an option. The flash upgrade had reset the ACCNetID to 1. The 4040 was then deleted (Bacnet side first then Infinity side) and a new 9640 was created. The proper ACCNetID was set up in the webpage and the changes committed. It was then online in CyberStation. Bottom line – IP address never changed. ACCNetID did. The controller never had to be touched during this process so remotely doing this is expected to work. This was only tested using the latest firmware and CyberStation v1.93. Of course, the best way to do this is on the bench not on a live system. Please be aware that the model flash change will cause node count and/or xdriver upgrades to be reset if they were added as post-factory-shipment upgrades (via the Repair Dept) since these upgrade UPD files are model specific. See Node or XDriver Upgrade of BCX Inf (9640) to BCX BACnet (4040) or reverse. Also see Update b3 or i2 OS, changing (converting) a controller, BACnet to Infinet or Infinet to BACnet .

Issue Seeing "An Object_Identifier has been specified for an object that does not exist in the object database of the addressed BACnet device", when trying to open a BACnet Device in Continuum Product Line Andover Continuum Environment bCX 4040 BACnet Cause When trying to send a controller's obejcts to the Database on the BACnet side the following messages are seen in the Distribution Properties window. 10/10/2013 12:50:07 PM The operation 'Save to Database' is finished. 10/10/2013 12:50:07 PM Unable to save objects to the database from Id:36922175.           An Object_Identifier has been specified for an object that does not exist in the object database of the addressed BACnet device. 10/10/2013 12:50:07 PM The operation 'Save to Database' is starting.   In the case of the affected controller being a bCX, all b3's underneath the bCX are able to be seen and their objects opened, but a user is unable to open any of the objects in the bCX itself on the BACnet side of the Continuum system tree.  Some/all objects are either not located in the BACnet side of the bCX Device or they have been malformed as they were initially created. Resolution The Device needs to be removed and re-discovered Delete the BACnet side of the bCX Device. Perform a "Find new BACnet Devices" from the Root. Then "Send to Database" on the BACnet side to upload all of the BACnet objects back into the Database.  

Issue The value of an exported Infinet point is not updated in some or all of the subscribing controllers. Product Line EcoStruxure Building Operation, Andover Continuum Environment Building Operation Automation Server Continuum i2 Controller Cause The subscribing controller is offline or inaccessible when the IE update is broadcast. Resolution The main disadvantage with the Continuum Import/Export (IE) system is that, in certain cases, it is possible that the updated value may not reach one or more of the subscribers due to various reasons such as network or controller down problems, excessive traffic on the network, etc. This is not of big concern when the point is of an analog type that changes frequently such as a temperature input since the point will update again when the temperature changes in a matter of seconds or minutes at the most.  For binary values though, a missing update is a big concern. Consider an occupancy schedule point that turns ON at 08:00 and off at 17:00.  If a subscriber misses the 08:00 update the zones under control by the subscriber will be unoccupied the entire day. The Point’s Refresh Attribute. Continuum points have a ‘Refresh’ attribute that is used to force the IE system to send a new updated value, setting the refresh attribute to true forces the Infinity controller to export the point’s value regardless of whether it has changed or not. It is IMPERATIVE that a PE program periodically refreshes binary points that are exported in Infinity controllers such as i2 devices. In the schedule example described above, a program* can be added to the Infinet controller that hosts the exported point.  This program should be triggered by the minute system variable and coded as follows: *make sure the program is of the type Infinet Script Program This will ensure that any subscribers to the schedule OCC flag won’t go more than a minute with a stale value of the point. Refreshing points that reside under the Infinet interface of the Automation Server (EBO 3.1 and greater) If the point to be refreshed resides under the Infinet interface of the AS-P then there are some differences in the way the refresh is accomplished. The program will be of the type Script Program. The point will have a REFRESH property, you bind to the refresh property in the Script Program instead of the point's value. The most important difference is that while in the i2 device the export takes places when you set the value of the refresh property to true, in the Automation Server the export takes place when the value of the refresh flag is toggled, regardless of the value (true or false) Below is an example of a Script Program refreshing some value objects that reside at the Automation Server under the Infinet interface The statement DigValue1 = (DigValue1 = false) is just a very efficient way to toggle the value of the refresh property, it is equivalent to saying.... If DigValue1 = false then set it to true and if DigValue1 = true then set it to false. Things to consider when refreshing exported points. Do not refresh points at a fast rate as this will cause unnecessary traffic on the Infinet field bus, refresh rates of one minute or more are strongly recommended. For the same reason, when refreshing many points, the operation should be staggered to avoid flooding the Infinet bus with an avalanche of IE traffic at the same instant.

Issue What binding methods can be used and how is the data transferred when binding objects between two b3  or Infinet controllers? Product Line EcoStruxure Building Operation Environment Automation Server, AS, ASP, ASB BACnet b3 Infinet controllers i2 Cause When binding objects between b3(infinet) devices/controllers, the type of Objects being bound will effect the properties of the binding. Resolution When binding between two Controllers, several methods can be used: Value/Point to Value/Point - The data goes via the Automation Server and the speed/rate is set in the Transfer Window, thus more bandwidth used and communication is lost if the Automation Server fails. Script to Value/Point - The data goes direct using BACnet COV subscriptions, thus less bandwidth is used. NOTE - The BACnet b3 and Infinet controllers, have no facility for direct binding of Value/Point to Value/Point, thus if a direct binding is made within the same controller, an EBO binding will be created. This will cause data packets on the MSTP or Infinet network. This should usually be avoided, as it can easily overwhelm the network. Bindings should usually be made from scripts. See Infinet under the hood for more details on Infinet setup

Issue DC1100 / DC1400 Displays two horizontal black lines when powered up. Product Line Field Device Environment DC1100 / DC1400 Discrete Controller. Cause Cold Start has not been performed. Cold Start has been performed incorrectly. Mains borne corruption has affected processor. Resolution Carry out Cold Start: Isolate Controller power supply. Press and hold down "Enter" and "Exit" buttons. Keep "Enter" and " Exit" buttons depressed while restoring power. Display should show "Self Test" and "Initiating System Variables" Release "Enter" and "Exit" buttons. Controller may then be programmed in accordance with Data Sheet instructions.   Or, if the controller is non-recoverable, the DC1100 and DC1400 units are now obsolete. However, there are several 3rd party companies offering refurbished units, these can be found by using a browser and searching e.g. DC1100 repairs.    

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 Need program example of Macro Block for Function Block program. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Macro Block Library is intended as an example and may need to be adjusted to the actual application. Resolution A Macro Block Library is included in the installation of the Function Block Editor. Inside the Function Block Editor, right click in an empty space and select Load Macro. If you do not see the Macro Block Library directly, please navigate to  C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 3.1\WorkStation\Function Block Editor Here, you can select Macro Library Function block to find different Macro Blocks:                  Macro Block Library Macro Block Library for TAC Xenta series Macro Block Library Xenta700 Macro Block Library For TAC Xenta 700 series Macro Library Function Block Macro Block Library For Function Block Editor Process Models Process Models Library For TAC Xenta series Process Models Function Block Process Models Library For Function Block Editor Process Models Xenta700 Process Models Library For TAC Xenta 700 series User Library Reserved location for user made Macro Block The first three folders in the list above (Macro Block Library, Macro Block Library Xenta700 and Macro Library Function Block) each contain the following sub folder structure: Air handling Control Function Calculation Common Efficiency Energy Psychrometric Heating Control Function Miscellaneous Function SNVT Timers The other four folders contain macro blocks without any sub folder structure, i.e. they are located directly in the folders.

Issue Use of the Building Operation Script editor and general Script programming is covered in the Training courses and technical reference guide, what other techniques can be used to debug a program? Product Line EcoStruxure Building Operation Environment  Building Operation Script editor. Cause Often additional techniques are required to debug Script programs, especially when attempting to analyze, modify or fault find other people's code. Resolution Some techniques you can use for debugging your program and isolating problems are: Add in additional line labels to the program to isolate where the program is disabling or failing, if it disables you will be able to see the "CurrentLine" it has failed on and therefore know which line of code is causing the problem. Use the Trace feature to step through a program and monitor the binding variables, stepping through each line of code to ensure the values are all set as expected. Even if a program does not disable you can use the "Stop" keyword in the program, it will act as a break in the code and you can look at the values of the various variables, this may be a useful alternative to the Trace feature. Use the Watch window and the Binding Variables window to show the values of the various objects, when used with the above two techniques it allows you to accurately trace a program flow. Ensure all of the code used is compatible with the Script programming rules and that Continuum Plain English programs are not just used without conversion. Check the Plain English and Script Difference Guide. For programs in an i2 or b3 controller, ensure none of the Program size limitations are exceeded, see Plain English program limitations on number of characters in program and line labels.