Building Automation Knowledge Base

Issue When EBO servers (ES & AS) no more need to keep the unnecessary TrendLog objects, the obsolete objects need to be deleted from EBO servers, and their log data need to be removed from the Extended Log Storage (PostgreSQL/TimescaleDB) server as well.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server External Log Storage PostgreSQL (pgAdmin 4) TimescaleDB  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 for assistance. Cause Deleting the obsolete TrendLog objects from EBO servers does not remove the old log data of the obsolete TrendLogs left in the PostgreSQL/TimescaleDB database. Resolution Once the obsolete TrendLog objects are deleted from EBO servers, their log data are no longer saved in the PostgreSQL/TimescaleDB. The next task is removing the old log data left in the PostgreSQL/TimescaleDB database.   1. As always, backup current EB & AS’s databases from EBO workstation.   2. As always, backup the current PostgreSQL/TimescaleDB database and save to a safe location. Backup the “ebo_db” from the PostgreSQL/TimescaleDB server using the pgAdmin 4 (refer to https://www.pgadmin.org/docs/pgadmin4/development/backup_dialog.html , or refer to page 8 “Backup” section of the “EBO External Log Storage Installer.pdf” document for detail).  3.Remove the obsolete TrendLog from the PostgreSQL/TimescaleDB database (the “ebo_db”). Method_1: Delete the EBO TrendLog object from ES & AS’s & TimescaleDB using EBO workstation. (1) From the EBO workstation, expand the folder (location) of the TrendLog object, and delete the TrendLog object. (2) From the EBO workstation, go to the TimescaleDB folder (/Server 1/System/External Log Storage/TimescaleDB/Trend /Logs/Tree View), and delete the Trendlog object from PostgreSQL/TimescaleDB database. (3) Verify the TrendLog disappears from both the EBO and the PostgreSQL/Timescale DB.   Method_2: If the above Method1 takes a long time to complete, you can delete the TrendLog objects from PostgreSQL/TimescaleDB database directly.  (1) From the EBO workstation, expand the folder (location) of the TrendLog object, and delete the TrendLog object. (Same as item (1) of the above Method_1) (2) From the PostgreSQL/TimescaleDB server, run the pgAdmin 4, select the “ebo_db”, open the “Query Tool”, and execute the below scripts: Find the ID of the obsolete TrendLog from the trend_meta table. Select Externallogid, source from trend_meta where sources like '%TrendLog Name or Path%' Remove the TrendLog from the 2 tables using the above found Externallogid as below. Delete from trend_data where externallogid = 1234567890 Delete from trend_meta where externallogid = 1234567890 (3) Verify the TrendLog disappears from both the EBO and the PostgreSQL/Timescale DB.  

Issue The I/A Series G3 Platform Software Manager indicates "Not Available Locally" when connected to the remote platform (ENC or JACE). Environment I/A Series G3 - All versions Cause Upon start of Workbench, the modules residing in the local Workbench module folder are scanned by the software.  During this process, new and/or updated modules are copied and saved into the local software database.  "Not Available Locally" indicates the associated module is missing from the local Workbench software database.  The following example finds the Installed Version of tacMs at TAC 3.4.64.4 with the Available Version missing with the comment "Not Available Locally." Resolution There are two methods to correct this issue. Method 1:  Copy the module directly into ~\modules directory. This makes the module(s) available in your Workbench environment, and also available to install in other remote platforms.  When the installer runs, the module(s) are also copied into your software database, available for installation. This is the typical choice. Method 2:  Copy the module into your ~\sw\inbox directory (or, use the equivalent “Software Import” feature in the Software Manager). In this case, the module(s) are not used in your Workbench environment, but are available in your software database for installation in remote platforms. If the module is invalid or corrupt, the software manager will generate and place the module in the "failed_imports" folder (e.g. unable to read the manifest files, class files, etc.).  Verify the module is valid. Reference the Niagara AX Platform Guide - Software Manager for additional details.

Issue An alarm goes on and off several times in a short amount of time. Each time the alarm condition clears and reasserts itself, by default, another email will be sent. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation SMTP alarms Cause Every time an alarm goes off, the email notification checks its parameter and, if true, sends an email. Resolution Filter the email notification by "count." Set it to "from 0 to 1" and you will only get a email on the first alarm (count).

Issue Can TAC BACnet (Viconics) thermostats have identical names or device ids within sub networks using their default names? Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconic BACnet Thermostats BACnet BCX B4 MSTP Cause Viconic stats need a unique address and unique name across the entire BACnet network. Resolution BACnet Viconics thermostats must have a unique name and device id across the entire BACnet network. The BACnet data link layer has two key parameters: the device object name and the device object ID. The device object name must be unique from any other BACnet device object name on the BACnet network (i.e. not just the MS/TP sub-network). Typically this question comes up because a thermostat will not come online. Run an acctrace during the Find and you will probably see a duplicate MAC address. Once you have given unique names and comm addresses to each of the thermostats on the entire BACnet network, these devices should communicate and come online properly. Each of the Viconic stats are given a unique name that includes the address (once it has been made unique) To change the communication address: Hold down the menu button until the option for menu comes up Answer the questions for the various options and eventually you will be brought to change comm address. Change Comm address, select Yes and then use the up or down arrows to give this MSTP Viconic stat a unique address. There is a Configuration Tool to access and edit the name and device id unique naming scheme. Click here for ViconicsConfigurationTool.zip. Installing and using the Viconics Configuration Tool on a Windows Laptop  You will need a serial adapter connection to tie into the MSTP bus that the thermostat(s) are connected to Select the Viconics folder > ViconicsConfigurationTool.zip You can install this ZIP file in any directory you wish, but the bacdocm.ini file must be installed on your C:\Windows directory. Use the bacdocm.ini file to configure your network settings at the Configurator Tool level. You can set the MAC address of your tool, the baud rate of your connection (max 38400 - limited by the RS-232 to RS485 port and Windows) etc. The "Our Device Instance" value represents the MAC address of the tool which must be unique on the MSTP network. Also the "MaxMaster" value must be set to a higher value than the highest MAC value on the MSTP network. You can edit this INI file to modify your settings OR you can modify the settings by going though the BACdoor Configuration Tool. Once you launch the Configuration Tool, you'll notice a white applet appearing at the right bottom of your screen. That is the BACdoor MSTP sniffer that actually looks for devices and objects. If you click on that icon, and select the "Configure" tab, a configuration window will be displayed. Select the baud rate at which you want to communicate with your device. This BACdoor configuration does the same thing as changing the BACDOCM.ini file (if properly located in C\Windows). Launch the Configurator Tool application. It automatically looks for devices on that network (at the baud rate set in the bacdocm.ini file or in the BACdoor Configuration window). If no device is detected an error message will pop-up after 1-2 minutes. All discovered devices will show up in the "Device List" you have to "Connect to device" in order to list all the objects of that device. After you changed the Baud Rate, you have to click on the "Apply changes" button. Don't forget that the max speed of this tool is 38400. For the first connection, you need to power cycle the thermostat (if it was running at 76800 previously) so that it auto-detects the 38.4 network. Once you set it to 76.8, you can not connect to that thermostat with the tool because of that 38.4 limitation. Also this tool does not support Read Multiple Property so it reads every property of every object one at a time. In its default mode of operation, the device will automatically match its baud rate to the baud rate of the network. Automatic baud rate detection will occur when the MS/TP communication port is initialized (on power up). If the network speed is changed, the device will keep listening at the previously detected speed for 10 minutes before resuming auto-bauding. Re-powering the devices will force right away auto-bauding. SE7xxx series requires the tool. The SE8xxx series does not as access is available through the menu on the device.

Issue Programming or points in the AS can not be bound to control LCM blocks. Product Line EcoStruxure Building Operation Environment AS Network 8000 interface Cause The AS Network 8000 interface replicates the function of a GCM and a GCM's blocks are not able to link directly to LCM blocks. Resolution The AS Network 8000 interface replicates the function of a GCM. As such the LCM blocks in the AS can be monitored, manually commanded and bound to share within the AS, but cannot be bound to AS points or logic for control. This is as it would be with an actual GCM and the LCM's connected to it. As with the GCM, the SGCM block is available in the AS and can be used to send data in the AS to the LCM for use in the LCM's logic. The LCM must contain the RGCM block and the use of the data received is determined in the LCM logic.

Issue Alarms cannot be created in a BACnet b3 controller because the fields are grayed out. Product Line Andover Continuum Environment Continuum Cyberstation b3 BACnet MS/TP controllers Cause Alarms are created differently in a BACnet controller than with an Infinet controller.  These fields are grayed out since they are not used for alarm creation in a BACnet controller. Resolution There are instructions in the BACnet section in the Continuum help for creating an event notification and then mapping the point and the event notification within an alarm enrolment. For an example see AlarmCreatingAndConfiguring BACnet.doc

Issue Do the universal inputs (UI) of the MNB-1000 support pulse inputs? Product Line TAC IA Series Environment MNB-1000 Cause Attempting to wire a pulse input to a UI on the MNB-1000 can cause issues. Resolution The UI inputs of the MNB-1000 do not support pulse inputs and can not be used for this purpose.  The digital inputs (DI) of a MNB-1000 do support pulse inputs. Pulse Input Rate Minimum rate of 1 pulse per 4 minutes Maximum rate of 10 pulses per second  

Issue Is it possible to have a link on a GxPage to run an executable file to launch an external application outside of the web browser? Product Line TAC IA Series Environment I/A Series R2 graphics Firefox web browser 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. Cause To launch an external application via a link on graphics page in a web browser. Resolution It is not possible to launch an external application from an I/A Series R2 GxPage. Two suggested workarounds are as follows. Create a hyperlink on a GxPage that links to a standard HTML web page. There would be a link to run a script on the standard HTML page to launch the external application. If the site graphics has a HTML tree created, create a new link in the tree which will run a script to launch an external application. * Take note that the HTML web page with the script link has to reside on the same computer as the external application. As an example the following script and procedure which will launch an external application in a Firefox web browser. In this case, the script will launch Windows notepad.exe. This method has been provided as a workaround but you should use and troubleshoot any information given below at your own discretion. Example of a script to launch an Notepad in Firefox: Right Click on this link and select "Save target as" to download this script as a text file We also need to configure Firefox to allow Java script to run. Run Firefox and type in 'about:Config' at the address field. Set the 'signed.applets.codebase_principle_support' to true. Be careful not to make any other changes. NOTE: This script and browser configuration may or may not work in other web browsers. Further changes may be required for this functionality in any other web browser other than Firefox.

Issue Edit > Host Computer > Software Restore results in pop-up error "No entries in data base" Product Line TAC INET Environment I/NET Seven host Cause The network configuration does not have any entries saved in the database. Resolution Go to Edit > Host Computer > Network Configuration In the Link Summary window, find the correct Link. If the Cnf column has a plus sign (+) in it, then this link is not saved. If the correct link is not shown, reference Error: "No Entries in Database" for more information. Highlight the correct link and press "Save" With the correct link highlighted, click "Penetrate" Any controller with a + in the Cnf column has not been saved. Click "Save All" Hit "Close" on the Station Summary and "Close" on the Link Summary. There are now entries in your database. The software restores should now show the correct options. For instructions on performing a software restore, see How to upgrade bin and SAV files in I/NET controllers

Issue Battery power on an MN50-RTC is low and needs to be replaced. Product Line Satchwell MicroNet Environment Controller PCB Power supply Timeclock Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Low power in battery Resolution The replacement battery is a standard CR1632 3 volt 125mAh Updated January 2014. The MicroNet 50 series range MN350,450,550,650 LCD and Touchscreen have been withdrawn from sale. Currently no direct replacement is offered.

Issue All setpoints are lost after a power outage and the function block programs revert back to initial value. Environment Menta Function Block Editor Menta Editor Xenta 280/300/400 Controllers Cause A Menta, Menta Editor, or Function Block Editor program with configurable setpoints will be lost if the default programming settings are used and there is a power loss. Resolution Backup feature in function blocks Menta and Menta Editor When the Backup check box is selected, the current value of the block output and internal states in the RAM are used when the device makes a warm start. Otherwise, the block output and internal states are reset to their initial values (same as for a cold start) at a warm start if the Backup box is not checked. If a power outage lasts longer than the power failure protection time for the device and the RAM contents are lost, the restart is a cold start. All blocks will be rest to their initial states regardless of the Backup option. The RAM working member that includes current values will last for 72 hours without power. Function Block Editor When the Backup check box is selected, the current value of the block output and internal states in the RAM are used when the device makes a warm start. If a power failure occurs, all important variables are automatically saved to the flash memory before complete shutdown. When power returns, this data retention function ensures that the Automation Server can continue to run with the correct set of values.

Issue Unable to get modbus to communicate with the automation server and LC&D GR2400 lighting controller. Environment Modbus Automation server LC&D GR2400 SmartStruxure Solution 1.5 Cause The LC&D GR2400 lighting controller will ONLY allow 1 stop bit in it's modbus communication. Normally the stop bit setting in a modbus slave device is an "at least number", meaning the GR2400 should except 1 or more stop bits, but it does not. The problem comes from the automation server by  default sends the 1 stop bit and addition "guard bits" for modbus communication. The guard bit setting was not available in versions prior to 1.5 and by default the automation server would send 3 stop bits causing the modbus communication to fail with the GR2400lighting controller. Resolution In SmartStruxure 1.5 right click on the Modbus Master Network and select properties. Click the advanced tab:         3. Here you see the guard bit setting. This value should be a 0 if the automation server is to ONLY send 1 stop bit. If this number is left at default the automation server will add the number of guard bits to the user       setting of stop bits. By default that makes 3 stop bits from the Automation Server. To properly communicate to the GR2400 the guard bit setting should be a 0 and the user selected stop bit should be a 1 in order to ONLY send 1 stop bit.

Issue taclogdata_log.ldf file is too big Environment SQL 2005   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. Cause Fail to perform frequent SQL DB maintenance   Resolution To Shrink the LOG file (.ldf) follow the procedure. Connect to taclogdata.mdf using SQL server management studio. Run the following command: dbcc shrinkfile (taclogdata_log,100,truncateonly)   This will reduce the size (taclogdata_log.ldf) to 100 mb. Note : You can get the logical file name for the log by running the following select statement: (select * from sysfiles) The following are the query results: 1          1          6400    -1         6400    2          0          taclogdata         c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata.mdf   2          0          2624    268435456      1280    66        0          taclogdata_log  c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata_log.LDF   If the database has the truncate log checkpoint turned off, then the transaction log file will be shrink to the target size only when the transaction log is backed up. OR If the truncate log on checkpoint is turned on then go to Enterprise Manager - all tasks - and click "truncate log". This will shrink the file down to the target size and will release all the unused space to the Operating System.

Issue Vista 5.1 license is not working.  Trying to launch Vista components results in error:  lc_checkout failed: Cannot checkout an uncounted license within a Windows Terminal Services guest session. Environment Vista 5 Terminal Services Virtual Machine VM Cause There is a special feature needed in the license which allows the use of Terminal Services. Resolution You must download the 14 day Demo TS Evaluation License on The Exchange Download Center. *note that Terminal Services are only supported in Vista 5

Issue Creating a bacnet schedule to control a 3rd party device generates the error:  “Bacnet operation rejected generated in response to a confirmed request apdu in which the service choice field specifies an unknown or unsupported service”  Environment Continuum 3rd party bacnet device Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The bacnet error occurs when dynamic creating of schedules is not supported in the 3rd party device and the packet gets rejected. Resolution An ethereal capture from the Cyberstation will show the packet getting rejected. A work around for this is to use a BCX to create the schedule and communicate to the 3rd party device.

Issue Date and time gets incorrect periodically in TAC Xenta Programmable controllers Time stamp in alarm list is incorrect Time stamp in alarm list is wrong  Vista Server local time and the local time in all Xenta controllers in the network go out of synch.   All local time settings are correct in TAC Xenta Environment TAC Xenta 30x/401/28x Cause The time in a TAC Xenta can be changed by TAC Vista TAC OP, note that a change of the time in one controller is broadcasted to the whole network. TAC Xenta group master will broadcast the time to it's group every 24 hours A Xenta Server (Xenta7xx, Xenta5xx, Xenta 913) Menta, this only affects the controller Menta is connected to. Most likely, the problem is a Xenta Server in the network that has the wrong time. It can be enough that a Xenta server is connected to the network, it does not have to be configured in this network.. Resolution Log in to Xenta server from the web interface. Go to Configuration-time If the date and time is incorrect set the correct date and time. Click on time synchronization, the lonworks time synchronization should only be set to enable  if this is a Xenta Server in TAC Vista or if this is a site that does not have TAC Vista on it and it is the only source to sync the time to.

Issue When starting the Vista Server, the splash screen displays the current state of the startup.  It gets to the "Trend Log Initialization" screen and then hangs. Product Line TAC Vista Environment Vista Server Cause Queued files in the $queues folder in the Vista database are being written to the SQL database.  If the queued files folder has grown very large, it can take a very long time (hours) to write this data to SQL.  If the connection to the SQL database has been broken, then it will take an infinite amount of time. Resolution Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. Allow time for the files to write the SQL Start Vista Server. Insure that TAC DSS Writer Service is running. When it gets to trend log initialization, leave the PC alone and allow time for the files to write to the SQL server.  If the size of the $queues folders are shrinking, then the process is working and after enough time, the server will start. Note: If you have cleared the $queues folder but it still hangs on trend log initialization, still allow plenty of time for the server to come up. There is a good chance that the Xenta controllers are passing all of their trend logs over to the SQL server. This could take hours or even overnight to complete. Delete the queued files If the data is not of dire importance, delete all the files inside both of the $queues folder.  For an efficient method for deleting many queued files, see An efficient method for deleting all queued files in the $queues folder. Check the SQL connection Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Remove TRL files This can also occur if the database has been upgraded from a lower versions, and still has information in the TRL files in the database. Stop the server Locate all TRL files in the $thisfil folder Delete any TRL file over 32Kb. Start the server again.

Issue An STR-104 can be used to monitor space temperature with a Xenta programmable controller. If a zone override is also required, the most straight-forward solution is to wire the override button to a digital input on the same controller. However, if those wires were not installed, or sufficient inputs are not available on the controller, the override button can be sent via the temperature sensor wires. Environment STR-104 Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause If enough wires were not run, or sufficient inputs are not available on the controller, the override button can be sent via the temperature sensor wires. Resolution The override signal sent via temperature sensor wires is accomplished by shorting the temperature sensor reading to ground. The Menta application senses this short and interprets it as a zone override. On the STR-104, short terminals 12 to 14 (Therm to Switch) On the STR-104, short terminals 11 to 15 (M to MX) Terminals 11 and 12 on the STR-104 go to M and B1 on a Xenta programmable (for example). Download this Menta macro for use in the programmable Menta application. While the button is pressed, the temperature will jump to a failed-shorted value of 300+ °F.  The attached Menta app will read in this jump, filter it out from a failed sensor, and enable an override for an adjustable duration.

Issue What TTS-SD-LED and TTS-SD-LCD Smart Sensors are available? Environment TTS-SD-LED Series • TTS-SD-LED-1 • TTS-SD-LED-B-1 TTS-SD-LCD-Series • TTS-SD-LCD-1 • TTS-SD-LCD-4-2 • TTS-SD-LCD-B-1 • TTS-SD-LCD-C-1-10P • TTS-SD-INFBUF Cause Some products in this range have become obsolete due to the discontinuation of some key components. Resolution Full details are on the attached Product Announcement PA-00171 TTS-SD-LED-1 Discontinued TTS-SD-LED-B-1 Discontinued TTS-SD-LCD-1 Modified TTS-SD-LCD-4-2 Modified TTS-SD-LCD-B-1 Replaced by TTS-SD-LCD-1 TTS-SD-LCD-C-1-10P Discontinued TTS-SD-INFBUF Discontinued

Issue StruxureWare Building Operation Extended trend logs have an incorrect unit associated with the measured value. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3.x 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. Cause It is possible to create extended trend logs by selecting multiple trend logs and using the right click option to create extended trend logs. The software incorrectly associates all of the created trend logs with the first trend log object's associated unit even if the other trend logs in the selection use different units. Resolution The cause of the problem is resolved in a forthcoming release (1.4.0) however if the system is in the state currently additional steps must be taken. The method to resolve this problem depends on the need to maintain the existing extended trend log data or not. 1. Accept loss of data Delete the extended trend logs that have incorrect units and create each extended trend log individually and avoid multiple selections. 2. Avoid loss of data Export the trend logs in StruxureWare Workstation. Modify the export file and edit the unit value for the Extended trend log The unit will need to be validated with another export that contains an object of the correct unit type. Example of Units % - 0x200001 F - 0x280003 no unit - 0x10001 inH20 - 0x230005 ppm - 0x200002 kW - 0x3210001 Import the modified file and when it detects a naming conflict allow it to rename the Trend log with a "2" notification. Stop the data collection on the original trend logs and once the retention levels of the new trend logs meets your site requirements delete the old trend logs with the incorrect data. Please be aware this issue could impact meter reports from WebReports detailed in Energy Reports not working in 1.3 and earlier