Issue Replacement stuffing box for valve V222 Environment V222: 721-2254-000 DN65 721-2258-000 DN80 721-2262-000 DN100 721-2266-000 DN125 721-2270-000 DN150 Gland Service kit (Packing box, Stuffing box): DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0 Cause Replacement parts for gland service Resolution Replacement gland service kits for V222: DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0

Issue Running SQL 2008 on a Windows 7 OS Product Line TAC INET Environment I/NET version 2.41 SQL 2008 Windows 7 Cause SQL 2008 and I/NET version 2.41 on a Windows 7 PC. Resolution Note: Do not install Microsoft SQL Server 2008 Express Edition on the filemaster of an equalized TAC I/NET Seven system. This database engine does not provide the replication services that are required on the filemaster. Microsoft SQL Server 2008 Express Edition is a scaled down, free edition of Microsoft SQL Server 2008, which includes the core database engine. While there are no limitations on the number of databases or users supported, it is limited to using one processor, 1 GB memory and 10 GB database files. Microsoft SQL Server 2008 Express is included on the TAC I/NET Seven installation disk in the SQLExpress folder (installation instructions are in the SQL2008 Expr Install Inst.pdf file included in the folder). Microsoft SQL Server 2008 Express Edition does not provide the replication services that are required on the filemaster. To use Microsoft SQL 2008 as the SQL engine for an equalized TAC I/NET Seven system, install Microsoft SQL Server 2008 Standard Edition on the filemaster. You can then use Microsoft SQL Server 2008 Express Edition on each equalized client. I/NET Seven supports the use of Microsoft SQL Server 2008 Express 32-bit Edition running on Windows 7 Professional 32-bit. The PC should have at least 2 gigabytes of RAM. Microsoft SQL Server 2008 32-bit (see notes 1, 2, 3, and 5   Freely Distributed with I/NET Maximum Database Size Maximum Concurrent Users Operating Systems Supported SQL Server 2008 Express (32-bit) (See note 4) Yes 10 GB Unlimited Windows 7 Professional 32-bit SQL Server 2008 Standard (32-bit) No Unlimited Unlimited Windows 7 Professional 32-bit Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, or 2008 It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. The use of Microsoft SQL Server 2005 Standard or Enterprise edition, or any edition of Microsoft SQL Server 2008 will require that the PC have at least 2 GB of RAM. Microsoft SQL Server 2005/2008 Express Edition cannot be used on a TAC I/NET Seven filemaster. Only 32-bit versions of SQL Server and Windows 7 Professional are supported.

Issue TGML function Convert Status doesn't seem to work for forced Values Environment TGML 5.1.5 or higher. Cause Vista will always identify forced values as online values. As mentioned in 5.1.7 release notes Resolution This can be scripted in other ways in TGML if it is necessary to show when a value is forced.

Issue Customer has previously purchased the WorkPlace Tech software release 4 and wants to know if there are any controllers available that can be programmed with the release 4. Environment WorkPlace Tech release 4.0 Existing MNL controllers of various releases. Cause WorkPlace Tech release 4.0 generates an error message when an existing application created for an old version of an MNL controller is downloaded into a new controller. Resolution See the section "Controller Firmware Revisions" in Chapter 1 of the WorkPlace Tech Tool 4.0 Engineering Guide for a explanation of the LON controller firmware versions.  If the controller application was programmed for use with an earlier version of the controller,  the application must be updated to the current version before the application can be downloaded into the controller.  Current production controllers contain revision 4.1 firmware.  The revision 4.1 controller model numbers are as follows:  MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F3, R3, H3 , S3 or S4), MNL-11RF3, MNL-13RF3 or MNL-VxRV3 (where x is 1, 2 or 3).    Older production controllers can be identified by the following model number series: MNL-10Rx1, MNL-20Rx1, MNL-VxRV1, MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F2, R2, H2 , S1 or S2), MNL-11RF2, MNL-13RF2 or MNL-VxRV2 To convert the application controller version, use the WorkPlace Tech "Hardware Wizard" after opening the application file. Open the Hardware Wizard. Click the [< Back] button at the bottom of the Hardware Wizard window to display the Controller Selection screen. Note that the current controller version for the application will be displayed in the box at the bottom of the window. If the old controller type is a MN V1, MN V2 or MN V3, select the [MN VAV] tab otherwise select the tab corresponding to the displayed controller type. On the controller selection page, select the model number of the new controller to be used for the application.  If the controllers are using the "Satellite" profile and the old controller was a "Satellite 1" profile, select the "Satellite 3" profile for the new controller.  Select "Satellite 4" if the old controller was a "Satellite 2" profile.  For all other controllers, select the new controller with the same profile type (Fan Coil, Heat Pump, Roof Top) as the original.  After selecting the controller profile for the replacement controller (in step 5), verify that the controller model number shown (MNL-xxxxx) matches the original controller, except for the last digit.  This is the model number of the controller that should be used for the replacement. Click the [Next] button to accept the new controller type selection then click the [Next] button to accept the controller configuration. Click the [Finish] button to exit the Hardware Wizard and apply the changes to the application. The application can then be compiled and downloaded to the new controller.

Issue ACX5740 controllers are found to have lost configuration and programming after power loss.  Environment ACX5740 ACX5720 NCII BCX B4920 Cause Controller cannot restore data from flash memory due to the presence of corrupt or a flash backup that was saved before the controller was redeployed at another location or that has been upgraded to a different firmware version. Resolution From the controller configuration page select Clear Database Backup and commit changes to controller.  Reload the controller. Backup controller to flash to ensure that current information is backed up.

Issue Opening a pinpoint graphic from Continuum Explorer takes long time or cannot open with the error Timeout error.  Environment Continuum LAN with WSs' pointing the shared folder of the pinpoint files. Continuum SU with additional WSs' pointing the shared folder of the pinpoint files Cause It takes longer time for workstation to get connection to the shared folder on the network when the pinpoint is configured to use the ServerName\SharedFolderName (or IP_Address\SharedFolderName) instead of Mapped drive. Resolution Map the shared folder of the server to each workstation as a network drive and use the mapped drive name in the Options setting of the pinpoint editor. Also, check if the issue is related to a Windows profile. Create a new Windows Admin user and see if the slowness persists. If it doesn't then the issue is a corrupted Windows profile.

Issue The Continuum database is created with SQL Compatibility Level 80 (SQL 2000) instead of 100 (SQL 2008). Can this be changed? Environment CyberStation SQL Server Cause The Continuum database is created with a Compatibility Level of 80. This is the default level of SQL 2000. SQL 2008 has a default setting of 100 but Continuum database is still created with a Compatibility Level of 80 even using SQL 2008. Can this setting be changed?  Resolution Continuum SQL installations have always used SQL2000 Version 80 compatibility and are only tested using this configuration, SQL2005 Version 90 or SQL2008 Version 100 configurations are untested in releases up to V1.93.  Compatibility level 100 has been tested in version 1.94, and is supported.

Issue A Vista OPC client on a Windows 2008 server is not getting a OPC server on a XP online. It is possible to browse the OPC server and read values with OPC tool but it is not possible to get it online in Vista. Environment Vista 5.1.6 Windows 2008 Windows XP Cause Not sure why but after have checked the DCOM settings over and over again we found out that we had to create a Local administrator with the same password on both computers. And set up the dcom settings for that user on both computers to get it to work. The computers was in a domain but it was not possible to use a domain user from the Windows 2008 computer. It worked with domain users from a Windows XP. Resolution Create a Local administrator with the same password on both computers. Set up the dcom settings for that user on both computers. Run Vista with that user.

Issue If the license file (.plf) is lost, it is necessary to recover it for reinstall. Environment TAC Vista versions from version 3.30 to 4.50 Cause The license file is necessary for the system to run. In case of crashed PC or similar, the license file needs to be reinstalled together with its matching dongle. Resolution As long as the dongle ID or Order no. can be presented, it may be possible to regenerate the .plf license file. Please contact the Product Support Services for further assistance. Official support of Vista IV licensing has been suspended as of 1/1/2012.

Issue Is there a way, within the MNB-1000 application program, to determine if communications has been lost between an MNB-1000 and an attached MNB-1000-15 RIO module? Environment MNB-1000 with attached MNB-1000 RIO module(s) Cause The WorkPlace Commissioning tool can display the status of the RIO modules attached to the MNB-1000 but this information is not available within the MNB-1000 application program. Resolution A proposed solution is to use a UO output and a UI input on the same RIO module to allow the MNB-1000 program to monitor the RIO module.  The concept is to drive the UO, 0-20ma with a binary signal from the program. The value would be programmed to change On/Off periodically -- once a minute for example.  The value of the UI would be compared and an internal application alarm generated if the value read from the UI does not agree with the value being written to the UO.

Issue Is there a document that gives the suggested controller to I/O device (field hardware) wiring information?  Wire Gauge, Type of Wire, etc. Environment I/A Series controllers and field hardware Cause Customer wants a document that provides Schneider-Electric's recommendation on controller field wiring. Resolution For the MNB family of controllers, refer to the MicroNet BACnet Wiring, Networking and Best Practices Guide, F-27360. For the MNL family of controllers, refer to the I/A Series MicroNet System Engineering Guide, F-26507. For the Network-8000 family of controllers, refer to the Network 8000 Hardware Installation Practices guide, F-23061. The Network 8000 Hardware Installation Practices guide is also a good guide for field device wiring for use with any family of controllers.

Issue Public time sync Servers for the United States Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment IP Level Devices USA Cause Time synchronization is required for accurate alarming and reporting Resolution Here is a web site referencing several US based Time Sync NTP Servers. http://tf.nist.gov/tf-cgi/servers.cgi

Issue Xenta Server installation on a LON network Environment LNS Network Cause Installing a Xenta Server on a LON network Resolution The Xenta Server can be installed anywhere along the LON channel as long as the terminators are located at each physical end of the wire. The server will function the same as any other LON node.

Issue Does TAC plug-ins work with NLStart? Environment TAC Plug-ins NLStart Cause NLStart is a non LNS based binding tool for small networks from Newron systems. Since the tool is not LNS based out plug ins will not work Resolution You can not use NLStart and TAC plug ins

Issue Drayton DC 2000/2100 and 3000 controller series. Environment Drayton DC 2000 2100 3000 Cause Are replacements available for the Drayton DC 2000/2100 and 3000 controller series? Resolution The Drayton DC 2000/2100 and 3000 controller series are obsolete, and there are no direct replacements for these controllers.

Issue Need to interface Continuum system with 3rd party BACnet Ethernet devices on the network. Environment Continuum BCX4040 Cause Continuum with bCX BACnet IP devices need to share data with BACnet Ethernet device on the network. Resolution Set one of the bCX on the network to be enabled for the BACnet Ethernet in bCX configuration webpage, and set the same value for the BACnet Network ID - Ethernet with the other Ethernet devices. Enabling this option on a BCX allows the BCX to communicate both Bacnet IP AND Bacnet Ethernet, it does not turn off Bacnet IP.

Issue Actuator M44 is no longer available (withdrawn in 2000) and needs a replacement. Environment M44 M9B EM9 Forta Cause Depending on application, since the M44 was used for both rotating and sliding valves, a few different replacement actuators could be used. Resolution For valves with rotating stem, (TRV, VTRA, VTRE and STMG), actuators M9/EM9 can be used. For valves with linear moving stems the TAC Forta series actuator is used.

Issue A schedule was created in the ENC and imported into the ENS, but it can not be edited in the ENS Environment Niagara G3 all versions, ENS, ENC-520, ENC-410 Cause The imported schedule becomes the slave of the original (master) schedule. Only the master schedule can be edited. The slave schedule can not be edited. Resolution If the schedule is to be edited in the ENS, then the schedule must first be created in the ENS and then imported into the ENC.

Issue After installing WorkPlace Tech 5.8 the Hardware wizard cannot be accessed. Environment I/A Series WorkPlace Tech Cause Earlier versions of WPT 5.7.4, 5.7.5, 5.7.6 and 5.7.7 when uninstalled leave behind files that can cause such an issue. Resolution The simplest solution is to uninstall WPT58 and re-install it.  The uninstall of WPT58 will remove the extraneous files so the next install will function properly.

Issue How long can the power to AS be interrupted Product Line EcoStruxure Building Operation Environment PS Power Supply Automation Server Cause Question regarding the AS and the power supply module. If the power is interrupted from the 24VAC power supply for say, 100 milliseconds, will the power to the AS be interrupted? There is a cold cap in the PS, and how long does it maintain power supplied to the AS? What about the RTC?   Resolution The power to the AS will be interrupted if there is a 100mS main power fail. The AS will then save the server cache. When the power returns the AS will make a restart that will take approx. 2 minutes. The AS Power supply fully complies with the IEC 61000-4-11 standard and can withstand voltage dips, with a 20mS dip and a 0% residual voltage.  The Power-fail process: When the AS loses power the super-cap keeps the AS alive for 15 seconds. 10 seconds of it dedicated to power-fail process to flush all the data that that are currently in the RAM to the SD card(That data can be anything with any value they have before power-fail). When power comes back that data is retained and are stored in appropriate place on the SD card. Real-Time-Clock(RTC) is maintained when the AS loses power by a dedicated capacitor which backs up the RTC chip for a minimum of 30 days in the absence of power since there is no battery in the AS.