Issue Provide the information required to support ProView for LON with Niagara G3 and N4 Product Line TAC IA Series Environment I/A Series G3 (3.5.34 or higher) I/A Series Niagara N4 (4.1.27.20 or higher) ProView for LON (MNL-PROV-WAL) Cause Required files for configuring the ProView for LON display with G3 and N4. Resolution Support for ProView for LON with I/A Series G3 and N4 requires the download and installation of the Distech Controls EC-NET-AX Support Package and EC-Display Configuration files.  Those files are available for download from The Exchange Download Center. Download the following files. BCS Distech Controls EC-Display Configuration v3.4.369 Setup.zip Distech Controls EC-NET AX Support Pack v4.4.17198.1 Setup.zip Unzip the files and run the executables to install the Distech Controls EC-NET-AX Support Package and Distech Controls EC-Display Configuration files. Follow the instructions to install the version(s) required. Install the Distech distribution file into the ENC (if required) using the platform distribution installer. The distribution file will be located in the Distech Controls Files directory added to G3 or N4 during the installation process. Open the distechControls palette (LonWorks - Services container) and add the LonWorksWizardService to the Services. Open the Drivers - ConfigurableControllers container and add the EcDis210 device object to the LonNetwork. Commission the ProView device using the LON Device Manager. Right-click on the EcDis210 and select Views - Ec Dis Wizard to test the wizard connection and launch the display wizard.

Issue Using the same power supply (transformer) for a Xenta 527 and a 7798 I/Site LAN comes down and there is no communication to any other devices. Environment Xenta 527 7798 I/Site 7798C 7798B Cause This is because it has blown the RS-232 expansion board on the 7798 I/Site due to a voltage overload The Xenta 527 must be powered with either half wave AC Power or DC power.  (Half wave power connects earth ground 1 leg of the AC power to the controller.) The 7798B and the 7798C can use either full way power or DC power. It is recommended to use a separate power supply for each device Resolution If required you can power the 7798C and the Xenta 527 on the same DC power supply, provided all devices are properly grounded.  This is not recommended as each devices specifies a separate power supply. To correctly wire these devices follow these instructions. You will need to send your damaged 7798 in for repair Add a second transformer or power supply to power the 7798 controller Ensure that the Xenta 527 is properly grounded. Please reference TCON190 (page 15)  for the 7798B or TCON311 (page 9)  for the 7798C wiring diagrams.  Reference this cut sheet for the Xenta 527 which shows that G0 must be grounded.

Issue Where can I find plugins for a Xenta 102-ES? Product Line TAC Vista Environment Xenta 102-ES Cause Need to find the plugins for a Xenta 102-ES Resolution The plugins for Xenta 102-ES can be found together with the Toolpack.

Issue Following an upgrade or import of a graphic the canvas size becomes extremely large. Environment Cyberstation V1.94 Pinpoint Cause A defect in V1.94 has been found and corrected by a hotfix. Resolution Hotfix for Pinpoint issues 1.94 SP1 resolves this issue (TPA-BOST-12-0001.00). This should be installed on all workstations on the site.

Issue Performing database maintenance with Vista 4.5.0 Product Line TAC Vista Environment Vista 4.5.0 SQL Server Cause It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database. Resolution Vista has a means of backing up databases on a Vista Server.  It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database.  The Vista database probably won’t grow very much after the initial engineering activity but the event and trend log database grows as events are received in Vista.  In many installations maintaining an archive of event data is required so that is another reason for backing up the database.  This paper presents a way to accomplish the backing up of the Event and Trend database and creating an archive file. Before the backup process can be implemented it is first necessary to have a good estimate of the Event and Trend Log traffic anticipated for the installation.  In the Vista 4.3.0 Technical Product Information (TPI), Ref No: C88-1-D43, there is section entitled Strategies for Calculating and Controlling Database Size.  On page 5 the method for determining database size is explained and used in the following example: Right clicking on the $Backup_LDB object in the Server View brings up this dialog.   Note that this example has an Event and Trend database that has reached 1121 (MB) in size.  The default Size Alarm Limit is shown to be 1640 and if the database grows past that size, Vista may not operate reliably. The TPI states on page 4 that events contain on average 2Kb of data.  Combining that value with the expected traffic provides a reasonable estimate of the database expansion rate.  If the installation traffic estimate is 4000 Events and Trend samples per day, the database expands at the rate of 8Mb per day.  If the installation traffic estimate is 10,000, the database expands at the rate of 20Mb per day. A conservative approach would limit the size of the active database to half of the alarm limit.  That means the backup process must be done so that the size does not get to 820Mb.  At 10000 Events and Trend samples per day that value would be reached every 41 days.  Vista is designed to allow Event driven backup operations and the closest choice it offers to the 41 days is once a month so that is what will be chosen. The configuration of backup is done in Vista Workstation by opening the Properties of the Workstation object in the tree.  The first step is to select a location for the backup files to be saved.  In the example shown below it is the folder outlined in red.   The “Max number of files” limits the number of backups that are retained by Vista on the hard drive.  The number chosen here was two (2).  The procedure that is described further down will actually move backup files to new directories which could be a network drive or a CD/DVD rom.  (The latter option requires operator action so it might not be the most desirable especially since backups are usually done at off times when an operator might not be available)  Next the event that is to trigger the backup must be defined.  The configuration of when the backup is done is set on the Log Backup tab of the Vista Server Properties dialog.  In the example shown below the backup is scheduled to occur on the first of every month at 12:40AM. The selection of Event object is made from the options made available by the browse button.     The browse selection brings up the Select dialog from which the selection of Event type and properties is done.  In the following example the selection is Monthly.   Right clicking on the $Event_LDB object opens the properties dialog box to configure the Event_Month object.  The final configuration option is what to do with older records.  Vista will remove Events from the database if you so desire.  The removal does not shrink the database but does make space available for new events to be written without expanding the size of the database.  This is the key to keeping the database from exceeding the Alarm Limit. The Event Log tab provides a way to delete old records from the database.  In the example shown below records older than 30 Days will be deleted after the backup that was done be the Event_Month object has been completed.  This means that each month the backup should have the most recent 30 days of Events and Trend samples.   The final step that can be taken is to also copy the backup file to a server that is backed up or to a CD/DVD Rom. This operation creates an archive in which Event and Trend data is stored.  Windows task scheduler can be used to run a cmd at some time after the backup operation was scheduled.  For the above example schedule it to run a 1:00am on 1 st of each month.  If backing up to a network drive create a folder such as shown below.  J:\Engineering\Vista Event Log BU.  In order for the task scheduler to run it is necessary to setup a user account on the pc that is not related to any actual user.  I added a user to the User group named, vista xcopy dbmgr.  This will be the user account used by the task scheduler.  The Vista backup folder must have modify/write permissions for this user and the folder into which the backup is going to be copied must have Full control.   The command line for this example is shown below: C:\WINDOWS\SYSTEM32\xcopy.exe "C:\Program Files\TAC\TAC Vista 4.5.0\Db2\$bkp" "J:\Vista Event Log BU" /M The Windows task scheduler is configured in the Control Panel, Scheduled Tasks as shown below:   In the Run as: box enter the name of the new User created described above: vista (xcopy dbmgr) Schedule the task to run on the first of each month at 1:00AM.   The backup files can be restored to a Vista Server that is not performing actual site monitoring.  This method is only way the “archived” event and trend data can be viewed as of Vista revision 4.5.0.

Issue Can Pelco's Control Point Software run on the same PC as I/NET Seven Software? Product Line Pelco, TAC INET Environment All Windows OS I/NET Seven Software Pelco Control Point Software Cause The two software packages are not compatible with each other. Resolution Pelco's client software cannot be installed on the same PC that is running TAC I/NET Seven. See TCON 301 - Chapter 6.

Issue What is the part number for the velocity sensor (0-1.3") transducer that is connected to the VAV-UC? Environment I/NET Site Cause What is the part number for the velocity sensor (0-1.3") transducer that is connected to the VAV-UC? Resolution CFM velocity pressure transducer input 0-1.3" W.C part number is 603500-0002. Refer to TCON 069 for more details

Issue PSI / XPSI Revision 4.0 will not tunnel, nor will it connect via modem. Product Line TAC IA Series Environment PSI / XPSI Revision 4.0 Cause Not supported in this release. Resolution Upgrade to PSI / XPSI Revision 4.1, which the file PSIv4.10.zip is available for download on The Exchange Download Center. Click here to see the Release Notes included in the zip file.

Issue Site has installed and "Tuned" a few PIDs and Float (FLT) modules in the controller but is not able to tune the last module added. What may be wrong? (History – Tuning) Environment I/NET Site Cause Due to the memory required for the tuning function, there is a limit of four modules that can be contained in the history record of each controller. Resolution If an additional module is needed, an old one must be deleted first. For more information refer to the System Operator Guide or TCON 083.

Issue Do all b3 and i2 Controllers support  all PE commands Environment b3 i2 Controllers String Trig Cause Some PE commands can not be used on some b3 or i2 controllers Resolution The following Plain English system functions are not supported in the i2885, i2885-V, and i2887(L) controllers: (b3885,b3885-V, and b3887(L) controllers) ACOS, ARCCOSINE, ARCSINE, ARCTANGENT, ARCTANGENT2, ASC, ASIN, ATAN, ATAN2, CEILING, CHR, CLOSELIST, COS, COSINE, EXP, EXPONENTIAL, FACT, FACTORIAL, FIRST, FLOOR, GETOBJECT, LAST, LEFT, LEN, LENGTH, LN, LOG, MID, NUM_TO_STR, OPENLIST RANDOM, RIGHT, RND, ROUND, SD, SEARCH, SIN, SINE, STANDARD_DEVIATION, STR_TO_DATE, STR_TO_NUM, STR_TO_TIME, STRINGFILL TAB, TAN, TANGENT, VAL See - b3 technical data - i2 technical data - PE Programming guide

Issue A 7700 and a 7740 are running DDC modules in I/NET 2000. Both DCUs have EPROMs (Non-MIPed). A "P-only" PID does not work. Environment I/NET 2000 Non-mipped EPROM Proportional-only PID control Cause P-Only mode is not available in the EPROM versions of the 7700 and 7740 DCUs. Resolution Use MIPs in these controllers to get this feature. Refer to TCON 206 or TCON 237, Direct Digital Control for more information.

Issue Overall Tap Configuration Environment I/NET Seven Site Cause Need information on Tap Configuration Resolution When you update parameters in a Tap, the changes will take effect when you disconnect from the Tap. If the changes are made to a shared dial Tap, the changes will take effect when the last connected host disconnects from the Tap. Use the following steps to configure a Tap. Refer to TCON300, I/NET Seven Technical Reference Guide, for a description of Tap configuration parameters. Select Edit Tap Host (or Link, or LAN) from the main menu. The system displays the Host Tap Configuration editor. The Link Tap and LAN Tap configuration editors are similar. This procedure describes the differences. Assign a Tap Name to the Host, Link, or LAN tap (up to 16 characters). On site Taps, use the spindial to choose a LAN Address (0 to 63) to identify the tap address on the controller LAN. The LAN Address field applies only to site taps. Depending on the type of tap, do one of the following: On host and LAN taps use the spindial to choose a LAN Speed. On link taps use the spindial to choose a Speed. On dial taps choose a Tap speaker setting from the drop-down list (Off, Auto, or On). Use the Firmware Status parameters for information purposes only. These parameters show the current revision number and revision date. These fields are display only, you cannot edit them. Use the Distribution Parameters fields to specify distribution group number, message priority, and the message mask. Note: When utilizing dual Tap functions (site Tap and LAN Tap) in a 7716, 7718, 7728, or 7793 (configured as -03 or -06), the values entered under "Distribution Parameters" in one Tap editor are used by all Tap editors emulated within the same DCU. Only one set of "Control Parameters" have been provided in each DCU. Select the Distribution Group number (1–4) to match the distribution group of the host PCs to which you want the Tap to send messages. Set the Message Mask to match the mask(s) of the host PCs to which you want the Tap to send messages. Set the Message Priority to None, Routine, Priority, or Critical. The Percent Full field is for AD/AA LAN Taps only. It specifies the number of messages that will be stored in the LAN/Site Tap’s RAM, as a percent of the total available memory, before the Tap calls the host PC. This is a deferred dialing parameter for "Priority" alarms. The Time Interval field is for AD/AA LAN Taps only. It specifies the time interval that must transpire following a "priority" alarm before the LAN/Site Tap calls the host PC. This is a deferred dialing parameter for "Priority" alarms.

Issue Users or engineers may be unsure of how to obtain the Smart Connector itself, as they are not generally available for download from the Exchange Download Center or the Smart Connector Forum on the Community. Product Line EcoStruxure Building Operation Environment SBO/EBO and general integration projects SXWSWSCDL100001 Cause Smart Connectors are not freely available and will require a license obtaining in order to download and use them. As Smart Connectors can be developed by a number of teams around the world that are not part of R&D, these teams will define the costs and requirements for using their software. Resolution A Product Announcement PA-00546 is available that details the concept and use of Smart Connectors. To order the Smart Connector Framework for a project, use part number: SXWSWSCDL100001  Then go to the Smart Connector Server licensing portal to obtain your required license for the specific Smart Connector you require. The URL for the License Portal is: https://www.smartconnectorserver.com/ A login is required for this portal which can can be obtained through the "Sign Up" button. Once logged in the user may browse through the available Smart Connectors and request to download a license. For support information on Smart Connectors, see the article "Support route for Smart Connector Framework issues".

Issue Online Messages on an SLI Environment I/NET site Cause Messages coming from the Sub Lan Interface (SLI) Resolution A door controller (DPU) has a limited amount of memory space available for storing individual records and messages. "Resident in DPU" individual records are given priority in storage: they are never discarded. Transient (non-resident) individual records and messages are stored on a space-available basis. If a communication outage between the SLI and the door controller causes the door controller's memory capacity to be reached, older records must be discarded as new messages continue to be generated. All records are discarded on a first-in, first-out (FIFO) basis, so that the remaining records are the most recent ones. A "DPU queue ovflw" message will also be generated to warn that data was lost. Records are discarded in the following order: Transient individuals. Messages. If there are no more transient individuals to discard, routine messages will be lost. When communications between the SLI and the door controller are restored, the contents of the door controller's queue (including the "DPU queue ovflw" message) will be delivered, freeing memory in the door controller. The SLI continually requests messages from its door controllers. Retrieved messages are queued within the SLI until they can be sent to appropriate host workstation(s). When the SLI queue is full, it will continue to accept messages from door controllers (i.e., the SLI will not cause its door controllers to discard messages). With its memory queue full, the SLI will discard older messages as newer messages are received. This ensures that the remaining records are the most recent ones. A "DCU queue ovflw" message will be generated to warn that data was lost. When communications between the SLI and the host PC are restored, the contents of the SLI's queue (including the "DCU queue ovflw" message) will be delivered, freeing memory in the SLI. There is also a TPA-DALL-09-0001.00 that was written on this issue.

Issue If there is an online selection tool for all the HVAC sensors (room temperature sensors, duct pressure sensors, etc.) Environment All Schneider Electric Buildings product lines Cause Since Schneider Electric manufactures a huge amount of sensors for different product lines. Sometimes it takes a bit of time to search for the right sensor. Therefore, Schneider Electric developed an online selection tool to help customer pick the right sensors. Resolution Click here to go direct to the online HVAC sensors selection tool. Select the desired features of the sensor. All sensors match the requirements will be displayed on the right. Datasheets can be accessed by clicking on the image or the part number. NOTE: the listed sensors may not be available in some region. Please contact the local sales or Support team to confirm the information.

Issue Product Line Update As previously communicated in 2007, there are several important product availability measures occurring at the close of 2008 that impact the NETWORK 8000, MicroNet 2000, and SIGNAL. Environment SIGNAL SIGNAL XP NETWORK 8000 MicroNet 2000 Cause Manufacturability related to low volume, last time buy issues with components, and technology support circumstances Resolution The following product groups will no longer be available for purchase after December 31, 2008 Global Control Modules and Assemblies (GCM-84000 Series) Local Control Modules and Assemblies (LCMs) MICROFLO II Lighting Interface Module (LIM) SIGNAL Schneider Electric will honor all product warranties and will continue to offer repair services and provide Product Support for these products. The GCM-86000 series along with the Network Interface Modules (NIMs), MICROZONE II, PEM, and MicroNet 2000 controllers will continue to be available for sale. Table 1 provides a full list of the part numbers no longer available after December 31, 2008. Click here to review PA-45.

Issue The software is no longer distributed on a CD.  Customer wants to install and license the software on his computer. Environment TreeTech 3.1 Network 8000 GCMs DMS panels Cause None. Resolution Download the software "TreeTech-3.1.exe" on The Exchange Download Center. Install the software by running the downloaded program file and following the displayed prompts. Run the "Purchase WIBs" program from the computer desktop.  This icon and program will be automatically installed on the computer if it does not already exist. Click the [Purchase] button to start the program. Fill out the Field Office and Customer Information parts of the form.  Make sure to fill in your purchase order number in the indicated field. The installer should also fill in his email address for emailed return of the installation codes. From the "Package List" section of the form, select the TR-TECH software and required drivers, selecting each from the list and clicking the [Add to Order] button. To request the license for the base TreeTech software, select TR-TECH. To request a license for using serial communications between TreeTech and Network-8000 GCMs or DMS panels, select IOS-SRL. To request a license for using Ethernet communications between TreeTech and Network-8000 GCM-86xxx series panels, select IOS-NW8-ETH. To request a license for using Ethernet communications between TreeTech and DMS-3500 panels, select IOS-DMS-ETH.  NOTE: At least one communications driver must be selected. After completing the form, click the [Accept Order] button and save the order form to a text file.  Click the [Done] button to save the requested license options to the computer and click the [Done] button on the WIB Purchase screen to exit the program. Email the saved license form to IASeries.WIB_Order@schneider-electric.com.  The requested unlock codes will be emailed to the address specified on the form after the order has been entered and processed.  Allow two business days for processing.  While waiting for the unlock codes, the software can be used with the automatically installed demo mode license.  The demo mode license is valid for 30 days from the time the first WIB software product is installed on the computer. When the purchased license unlock codes have been received, they must be installed using the [Unlock] function of the "Purchase WIBs" program.  After opening the program and  clicking the [Unlock] button, select one of the requested license products, enter the corresponding unlock code and click [Generate License].  This process licenses the software onto the computer and removes the product from the displayed list.  Repeat this process for each additional product license shown on the screen.  Each provided unlock code will be used only once.

Issue Obix stops polling data randomly Environment G3 Niagara Cause The niagara Obix driver jar has recently been updated to address this issue. Resolution Go to The Exchange Download Center and download the latest niagara Obix driver jar file 3.6.47.9

Issue How to interface OTIS Elevator HLI with Security Expert. Product Line Security Expert Environment Security Expert v4.2.194.7 or higher SX-ELV-HLI-OT license to enable the integration OTIS OTIS Compass V2 OTIS OTIS Compass V3 Cause Information required on how to interface OTIS Elevator HLI with Security Expert. Resolution Requirements Security Expert (v4.2.194.7 or higher). SX-ELV-HLI-OT license to enable the integration.   This interface will work with OTIS Compass V2 and OTIS Compass V3. Detailed information on how to configure this integration can be found in the application note below.   Security Expert OTIS HLI Integration

Issue Is an Xdriver (X-Driver) needed for OPC integration? Product Line Andover Continuum Environment Continuum CX(99xx) Cause OPC server requirements Resolution An Xdriver is not needed to operate the OPC Server. Link to OPC Server Datasheet Link to OPC Server Software