Building Automation Knowledge Base

Issue Since both products -- Xenta programmables and the UNC 520 -- speak LON protocol, there is some assumption that integration should be seamless.  In the case of ASCs, this is true, but Xenta programmable controllers use some forms of proprietary communication that can complicate the integration. Product Line TAC IA Series, TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B UNC-520 Niagara Tridium Cause Xenta programmables use proprietary communications for three main purposes: To communicate their online status between group members and group masters To communicate between a base unit and associated I/O modules To pass proprietary TAC Network Variables between two programmable controllers In a UNC-520, the first function would be taken over by the new network manager (Local Lon Device).  However, the second two must use Group Bindings set through a Vista compatible network management tool like LonMaker or NL220.  If the controllers are commissioned into the UNC-520, that communication will be broken and I/O modules will go offline and no network variables will pass. Resolution  It is possible to engineer a TAC Vista network as usual, using an LNS management tool to create group bindings to facilitate proprietary communications.  A UNC-520, set to non-network management mode could then be implemented on top. However, any attempt to commission the devices into the UNC-520 network will break that proprietary communication.  To prevent this scenario from occurring, the simplest method is: Do not use proprietary TAC Network Variables to pass data between controllers. Use only SNVTs which will be available to a third party LON network manager like the UNC-520 Make no SNVT bindings in a temporary LonMaker or NL220 database.  Let the UNC-520 handle all network management duties. Do not define Xenta I/O modules in the Menta Device Specification. Use only Xenta 421A, 422A, 451A and 452A I/O modules.  These have the capability to act as stand-alone LON nodes. Define the modules as LON nodes, configure them using Configuring inputs on Xenta 421A or 451A when using the controller as a stand alone Lonworks node. Bind to the inputs and outputs of the I/O modules in the UNC-520.

Issue Receiving the following error when attempting to navigate to the Xenta web interface. "TAC C503Boot/x.x.x.x not configured". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 511, 527, 555 Xenta Server 701, 721, 731 Cause Device web interface has stopped working or flash drive / hard disk has been corrupted on the Xenta Server. Resolution Attempt the following steps to resolve this problem: Try restarting the device and see if the unit comes back online, remember to wait 1-2 minutes for the unit to restart.  Check the RUN LED on the panel, if the LED is a solid green this indicates the device is running normally, and your access should be restored. If the LED is RED, solid or flashing this would indicate a problem with the device. Attempt to restore or upgrade the device to the latest firmware.    You can download the latest firmware version from the Schneider Electric Exchange. If this fails then then reference Xenta Server "Run" light is solid red with no communication via Ethernet.

Issue Problems receiving emails from Xenta 511/527 Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause Some email servers have been found to filter UTF-7 character encoding as spam. The Xenta products require this encoding to support Swedish characters, but this can be configured by manually editing some files. Resolution Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device Cycle power The device will now use UTF-8 character encoding which is more commonly used in the United States. For more troubleshooting tips, see Troubleshooting sending emails from a Xenta Server.

Issue Where are the reports of fixed issues/bugs for the various product lines located? Product Line TAC Vista, TAC INET, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, EcoStruxure Building Operation, EcoStruxure Building Expert, Access Expert, Security Expert Environment Technical Product Announcements Cause TPAs contain information of changes made per version of the different product lines. A TPA may report enhancements and/or broken functionality. Resolution Navigate to Exchange Extranet to view all TAC Vista documents tagged as TPA. The documents will be listed in reverse chronological order. Log in to view these documents. See Register for The Exchange Download Center for more information on registration.

Issue 3:15am Time Sync error in AMT Product Line TAC INET Environment I/NET site with DCU Time Sync enabled Daylight Savings Time Cause Outdated SAV file No DST observed Enabled DCU Time Sync from Host PC Resolution Make sure versions of Bin Files are up to date with current revision of I/NET across all controllers. For how to do this read How to upgrade bin and SAV files in I/NET controllers.  Make sure SAV files are backed up and current. For how to do this read How to upgrade bin and SAV files in I/NET controllers. As the host workstation synchronizes the daylight savings time settings in a controller, it will also check for the existence of a corresponding SAV file. If a SAV file for the controller is found, the host workstation processes it as follows SAV file is current If the controller's SAV file is current, the host automatically updates it with the daylight savings settings from this editor. This ensures that if you later restore the controller using this SAV file, the correct daylight savings time settings will be downloaded. SAV file is old If the controller's SAV file is out-of-date, the host does not change it. In this case, you can manually update the controller's SAV file or use the Automatic DCU Save function in order to create an up-to-date SAV file for the controller. Refer to Station Save and Restore for more information.  Beginning with I/NET revision 2.41, I/NET allows the DCU Time Sync and no observance of DST.  Work around is to remove DCU Time Sync if your time zone does not observe DST.

Issue I/A Series G3 Modbus TCP communications to random Modbus devices randomly drop offline and stop communicating with the ENC or Enterprise Network Server.  Both the modbusCore and modbusTcp modules are at version 3.6.31. Product Line TAC IA Series Environment I/A Series G3, Modbus TCP 3.6.47 and lower Cause There were a few updates to the Modbus core and TCP modules between 3.6.31 and 3.6.47. Issue 18656 corrected communication reliability when there are a large number of Modbus TCP devices under a single ModbusTcpNetwork. Issue 19897 corrected transaction ID synchronization when a retry occurred. Issue 23578 added the ability to control the maximum transactionID used for ModbusTcp (I/A Series G3 Modbus TCP communications to Siemens Moore 353 controller stops updating after a period of time after ENC/JACE reboot or station start). Resolution Download the following modules from The Exchange Download Center: modbusCore-3.6.47.1.zip modbusTcp-3.6.47.1.zip Install to the appropriate I/A Series G3 Workbench modules folder Upgrade the modules in the ENC/JACE.

Issue Time Zone Database shows +0 for all time zones when the platform date is in 2016. IA Series G3 version 3.6.407 IA Series G3 version 3.7.108 IA Series G3 version 3.8.41 Product Line TAC IA Series Environment IA Series G3 versions 3.6.407, 3.7.108, and 3.8.41 Cause This error appears when listing the contents of the Niagara Time Zone database where the Time Zone Database shows +0 for all time zones when the platform date is in 2016.  The issue is related to an error within the 3.8.41 baja and hx modules and only affects the display within the Platform view only.  The actual behavior and operation of the Time Zone remains accurate.  Prior IA Series G3 versions (e.g. 3.8.38, 3.7.106, and 3.6.406) or earlier will not exhibit this issue. Resolution Download and upgrade the baja and hx modules available in the latest consolidated patch files. baja 3.6.407.3 (or higher) and hx 3.6.407.1 (or higher) baja 3.7.108.3 (or higher) and hx 3.7.108.1 (or higher) baja 3.8.41.2 (or higher) and hx 3.8.41.1 (or higher) The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area (reference Latest consolidated patch files for I/A Series G3 maintenance builds with details).  Download and install the appropriate patch for the version.

Issue Xdriver is enabled,   Open the BCX1 editor, click "options" tag, display comm port attribute as"Xdriver comm1: 00000009", but there is no "xdriver" listed from the drop down menu when click the arrow on the right of default type of the comm port. Product Line Andover Continuum Environment BCX1-CR-X, 4.500065 Cyberstation 1.81 Cause Continuum support xdriver with BCX1-CR(BCX4040) from 1.82, any version earlier than 1.82 not support xdriver with BCX1-CR controller. Resolution Upgrade all the Cyberstation to 1.9X. To determine if a controller comm port is Xdriver enabled, refer to Determine if a controller comm port is Xdriver enabled.

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 How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 Cause Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.

Issue Error Messages: Windows - Delayed Write Failed Windows was unable to save all the data for the file D:\VISTA DB _23032011\$queues\insertevents. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Windows - Corrupt File The file or directory \VISTA DB _23032011\$queues\insertevents is corrupt and unreadable. Please run the Chkdsk utility. Product Line TAC Vista Environment TAC Vista Cause Problem with Operating System (or) Hard Disk Fault (or) Link between $queues with Vista Database. Resolution As there may be several issues that are causing this, there are three options to look at: OPTION 1: Restore the OLD TAC Vista Data Base Backup. Refer to TAC Vista Technical Manual chapter 26 for re-storing database procedure.   OPTION 2: There might be a linking problem with this folder and Vista.  Here are the steps to check if this is the problem: If the problem still exists, Check for hard disk errors. Find the $queues - folder in existing database folder ( \DB\$queues) Copy the files to an other location and delete current folder (Refer to An efficient method for deleting all queued files in the $queues folder) Recreate it with same folder names and copy back the files into $queues-folder. If the problem still exists, Check for hard disk errors.   OPTION 3: Check for hard disk errors, follow the below procedure: Go to "My Computer", Right click on Hard Disk Drive – typically - C, and Click on Properties. Go to Option "Tools" and Click on "Check Now" under "Error-Checking"

Issue Is there a limitation to the size the database can be on a Single User system in Continuum? Product Line Andover Continuum Environment Single User Continuum system MSDE database Cause Microsoft has put a limitation in the size of the MSDE database. Once you hit this limitation your Single User Continuum system will not operate properly. Resolution The size limitation is 2 Gb. It may be possible to recover after hitting this limit by removing un-needed log entries from the database, but this is not always a guarantee you will be able to recover the database. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation. From this point you can remove any unwanted logs and shrink the database. Then you can back up the database and restore it back to the Single User system. Another way to recover from this is to back up the database, if you can, and restore it to standard SQL installation and convert the Single User system to a LAN installation. Finally if all the above do not work for your system you will have to restore from the last known good backup of the database. See Microsoft Database size Limitations and Continuum for SQL Express information.

Issue Set extra DCOM Settings when TAC Vista Server and Remote Work Station in Workgroup. Environment TAC Vista Server Remote Workstation Cause Cannot access TAC Vista Server from Remote Workstation, even though DCOM's set properly (in Workgroup). Resolution When using Remote Workstation and TAC Vista Server in same Workgroup and completing the DCOM settings based on the TAC Vista Installation Manual (04-00001-xx) and you still cannot access the TAC Vista Server PC, try the settings in the attached the document. Click here to download. Also refer these articles for more information: Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET Error: The RPC server is unavailable. Connecting from a TAC Vista Remote Workstation says "Ensure that TAC Vista Server is started" error, even though DCOM is set correctly Necessary Accounts for DCOM and Firewall Security Settings

Issue Need to use a Xenta I/O module on another channel from the base device Product Line TAC Vista Environment Xenta I/O Modules Xenta Programmable Controllers LON Channels Cause Using traditional I/O modules you are not allowed to span channels when placing your base unit and I/O modules. Resolution Use the 421A/422A or 451A/452A models. You can span channels by using SNVT based communication rather then Xenta group communication. You will be required to bind the values to the base unit. See Configuring inputs on Xenta 421A or 451A when using the controller as a stand alone Lonworks node for more information on configuring the Xenta I/O modules for stand alone operation.  

Issue How to disable credential access on Doors at different controllers using a single variable. Product Line Andover Continuum Environment Continuum Access Control Cause Require a method of securing multiple Doors at the same time. Resolution The best way to secure a number of Doors from a single variable is to use the Door Force Lock Schedule attribute in the Door object. This is accomplished by adding a numeric to the attribute on the Options tab of the Door object; IMPORTANT: The attribute name Door Force Lock is misleading, it DOES NOT lock the door in any way, all it does is disable credential access at the door. For Area/Door Lockdown refer to the linked KB article And also on the Entry Reader or Exit Reader tabs, ticking the checkbox under either Normal and/or Comm Fail for Door Forced Lock Schedule. Setting this Door Force Lock Schedule field to a local or remote InfinityNumeric point will provide the following conditions: When the Numeric is on, access is permitted to all personnel by card swipe and/or keypad entry. (Allow use of the door.) When the Numeric is off, card reader and keypad access are denied to all personnel. (No Access) You could have this numeric located in a central controller and all the rest of the controllers reference this numeric from the Door objects. No other points or plain English is required. If you want to ensure that the updates are received, you can force the IE entry for this numeric to update on a regular interval, see Use just one schedule to control doors or access to areas across different controllers that discusses how to accomplish this.  

Issue How to do alarm escalation in Continuum? Product Line Andover Continuum Environment PEAlmFunction, PERtnFunction Cyberstation Alarm Workstation PE function Cause The customer requires the ability to time how long an alarm is active, and based on its status (acknowledged-unacknowledged), escalate the active alarm, by email or other means. Should the alarm be acknowledged in time, the escalation does not occur. Resolution One method is to use the PEAlmFunction and PERtnFunction in a Workstation Program to capture the various alarm conditions off the alarm stack to trigger the activity that you want. As an example, the PEAlmFunction could be used to initiate a timer for the alarm by recording the time of the alarm and the alarm point. The PERtnFunction is then used to clear this recorded information if the alarm is acknowledged. A Workstation program is then used to constantly monitor this alarm information and comparing the recorded alarm time to the current time, if this is above the escalation time then a numeric is set to trigger another alarm that is then escalated. For details on how to configure the PEAlmFunction and PERtnFunction, consult Can Plain English interact with the Continuum Alarm Engine?

Issue When accessing Webstation through Internet Explorer, receive the error “8000401A. Code:-2147467238” Product Line TAC Vista Environment Vista Server 5.x and Webstation. Internet Explorer Windows 7 Cause Improper DCOM settings. ASP.NET not installed Incorrect Remote work station License used Resolution Set DCOM settings as per Vista Installation Manual (04-00001-04) Section 3.6. ASP.NET Start - Controlpanel- Programs - Turn windows feature on or off Navigate to Internet Information Services - Word Wide Web Services - Application Development Feature Make sure ASP.Net are checked, if not install it.Try webstation again. Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET is a link to a tool that can assist with setting DCOM and ASP.NET   Ensure correct Webstation licenses are installed.  Below are the options available.   0-008-8270-1      "Vista 5.1 Web station 1 CAL - One concurrent user license for Web station 5" 0-008-8271-1      "Vista 5.1 Web station 3 CAL - Three concurrent user licenses for Web station 5" 0-008-8272-1      "Vista 5.1 Web station 6 CAL- Six concurrent user licenses for Web station 5" 0-008-8273-1      "Vista 5.1 Web station 12 CAL- Twelve concurrent user licenses for Web station 5" 0-008-8274-1      "Vista 5.1 Web station Unlimited- License for unlimited users for Web station 5"

Issue Where to obtain the documentation for I/A Series G3 software. Product Line TAC IA Series Environment I/A Series G3 software and hardware Cause Documentation is provided as a part of the software package.  Resolution The current documentation for any release of the I/A Series G3 software (except for proprietary drivers) is installed with the full software installation.  The documentation can be found in the docs folder under the \Niagara\niagara-x.x.x\ installation folder. Refer to Documentation for the I/A Series G3 Schneider Electric proprietary drivers for information on the availability of the I/A Series G3 Schneider Electric (TAC) proprietary driver documentation.

Issue LonWorks Device is Offline in Vista, but Online in LonMaker. For Xenta Programmable devices refer to Xenta Programmable Device is Offline in Vista but Online in LonMaker. Product Line TAC Vista Environment LonMaker, NL220 Vista Workstation LonWorks Device Cause If the Vista database has some LonWorks devices that are not communicating, one cause could be due to changes in the system such as moving controllers to a new channel for example. Updating the Vista database with the system plug-in might not fully overwrite all the node properties causing the device not to communicate in Vista Workstation even though it is communicating in the LNS database. Resolution Delete the LonWorks device from the TAC Network in the System plug-in. "Update Vista Database" in the System plug-in to remove the device or devices from Vista Workstation. "Update TAC Network" to add the devices back to the TAC Network. "Update Vista Database" again to add the devices back to the Vista database.

Issue Database initialization completes with errors Product Line Andover Continuum Environment Cyberstation installation Cause When running database initialization you will need full access to all of the database. Otherwise you may see errors similar to the following: Installation Error! <[Microsoft][ODBC SQL Server Driver][SQL Server]The SELECT permission was denied on the object 'syscategories', database 'msdb', schema 'dbo'.> Installation Error! <[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot drop the procedure 'dt_IsColumnDifferent', because it does not exist or you do not have permission.>   Resolution Ensure that the Andover97 account has DBO privilege to the ContinuumDB, if not run the "Change DB Owner" query to restore Andover97 as the DBO, see Unable to Initialize Continuum Database following installing no SQL instance.   The above errors relate to setting up the SQL Server Agent Jobs that are held in the MSDB part of the database. Check that Andover97 does have the user mapping to this part of the database as per the following screenshot:     Also ensure your Windows User account has the required Administrator privileges to allow full access to the SQL database and its files.

Issue Video of DigitalSentry system can't be seen in I/NET. Alarm of Endura system, for example Motion Detection or Video Server Offline can't be shown in AMT. Product Line Pelco, TAC INET Environment I/NET 2.41 Cause The possible cause is that when installing SarixSDK of I/NET 2.41, there will be an error: Error 1904. Module C:\Program Files\Pelco\Common Files\IntegralPelco4600 dll fail to register. HRESULT-2147220473. Resolution The possible resolution is to uninstall the SarixSDK, delete the Pelco folder in Program Files folder and reinstall the SarixSDK. The error should disappear during the installation. And then video and alarm should be able to appear in I/NET. For more issue about video that can't be seen in I/NET, refer to Video in Endura/Digital Sentry System Can't be Shown in I/NET.