Building Automation Knowledge Base

Issue MNL-V1RVx, MNL-V2RVx and MNL-V1RVx-2, MNL-V2RVx-2 differences Environment I/A Series Micronet LON VAV controllers Cause Part number MNL-V1RVx has been replaced with MNL-V1RVx-2 and part number MNL-V2RVx has been replaced with MNL-V2RVx-2.  The datasheet F-26365 indicates the parts as MNL-V1RVx and MNL-V2RVx.  Resolution The MNL-VxRVx and the MNL-VxRVx-2 are functionally the same. The '-2' was added to the part number to indicate an enhancement to the VAV actuator assembly to reduce the operation noise level of the actuator. 

Issue Replacing a 230 volt Satchwell mains actuator. Environment Satchwell MZxxx Valve Mains Actuator Cause Old Satchwell actuator is obsolete. Resolution The replacement mains actuator will be the MV15B-230 spec - 880-0460-000 for datasheet please click HERE. To fit the MV15B-230 actuator to a Satchwell MZxxx valve a L7SV linkage is required. spec 880-0126-000

Issue Replacement Environment Current replacement. Cause Obsoletion of device Resolution The is no direct replacement for the DRT 3801, DRT3851 Sensors with fan switches. The sensor and setpoint can be replaced using a New Part No. STR612/004604700 The fan switches would need to be replaced using a four position switch. Click here to view the DRT3801/DRT3851 data sheet.

Issue Replacement of obsolete actuator Environment Valve actuator replacement Cause Obsolete Valve actuator Resolution The current replacement for the AVUX 2-201 actuator is the AVUX 5-202 Click here to view the data sheet for the AVUX 2-202. Click here to view the data sheet for the AVUX 5-202. .

Issue The address of the IAC touch screen will reset to default (65) on Sundays when time broadcast is used Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Building Operation Enterprise Server Building Operation Automation Server MicroNet transition IAC touch screen Cause When the time broadcast on an AS or ES MicroNet interface the address of the touch screen will reset Instead of broadcasting the day number as a 7, the day number is sent as a 0. The IAC touch screen does not understand day 0, resulting in the touch screen resetting to defaults. No other days are affected. When the touch screen resets, the touch screen's address is also reset and defaults to address 65. Unless the touch screen was originally configured as address 65, the controllers on the SubLAN of the touch screen will not be available, until the correct address is entered into the touch screen. Resolution A hotfix is available from Product Support for SBO version 1.7.1.12604 This correction has been included in SBO 1.8 and later releases. Earlier SBO version will need to be upgraded to SBO 1.7.1 with the hotfix applied or upgrade to version 1.8 when available

Issue A Siemens  power meter with a Modbus TCP/IP interface will not allow setting of the Device ID - only the IP parameters. Continuum Modbus TCP/IP Xdriver Remote Device Status Point (aka Comms Point] does not work if the Device ID is set to 0.   Environment Modbus TCP/IP Xdriver Cause Continuum Xdriver Modbus TCP/IP Remote Device Status Point does not work if the Device ID is set to 0.   Resolution Set the Device ID = 1 when configuring the Modbus TCP/IP Xdriver Comms Point For more information refer to page 12 of the Modbus TCP/IP Xdriver User Guide linked here.

Issue Created new Alarm Enrollment, attach to point and put point in alarm but no alarm is received and the points alarm value does not show the point is going in alarm. No problem when using an existing Alarm Enrollment created in the past when the total number of Alarm Enrollment objects was much less. Environment CyberStation CX9900 CX9640 CX9702 CX9680 ACX5720 ACX5740 Cause Controller's handle id limit on Alarm Enrollment objects has been exceeded. Resolution Click here to download this article as a PDF: Continuum Alarm Enrollment Handle ID Limits Continuum Alarm Enrollment Handle Ids Limit. (Note the information presented here applies only to non BACnet alarms) In Continuum there is a limit on the number of Alarm Enrollment objects that can be sent to the controller, the limit is 4000. Unlike the BACnet alarms, the Continuum alarm enrollments are meant to be re-usable, the system was designed for the Alarm Enrollment to be reused hence the limit, when the system is used as designed is very unlikely if not impossible to exceed the 4000 Alarm Enrollment objects limit. There have been cases where this limit has been exceeded due to site requirements that do not conform to the Continuum design, further more as of version 1.94 Continuum does not provided any feedback when the limit is exceeded, the alarm simply won’t work since the controller does not accept the alarm enrollment objects sent by the CyberStation. Guidelines to avoid exceeding the alarm enrollment handle id limit. Re-use, re-use, re-use. The Continuum system was designed for the Alarm Enrollments to be reused. If for some reason the number of alarm enrollment object is approaching the limit, do not delete Alarm Enrollment objects, if you have an alarm enrollment that is no longer needed rename it and re-purpose it instead of deleting it and creating a new one, the reason for this is that the handle ids once assigned are never re-assigned, so if you delete an alarm enrollment its handle id is lost forever. How to clean up if the limit is ever exceeded. If there are any Alarm Enrollment objects with handle ids out of range in the database they should be deleted to avoid confusion but before they are deleted all links to the enrollments have to be identified and the links removed. To find any links to alarm enrollment objects with id out of range run the following query against the ContinuumDB Select * from EventEnroll where AlarmRefLo > 562041735 If you get any results look at the uiName column, the uiName will consist of the point’s number and the AlarmEnrollment’s name separated by a period. Example: Num1.TempTooHigh Now From the Continuum explorer, find the point named ‘Num1’ that has a link to ‘TempTooHigh’ and remove the link. After all the links have been removed run the following query to find all the Alarm Enrollment objects with handle ids out of range. Select * from AlarmEnroll where ObjectIdLo > 562041735 Note the name in the uiName column, from the Continuum explorer delete the AlarmEnrollment objects.

Issue End connection kits needs to be ordered separately, specified depending on application Environment VZ208E VZ308E VZ408E VZ208C VZ308C VZ408C Cause The end connection kits needs to be ordered separately.  Resolution 1 (one) kit / port  on valve is required, i.e. a VZ208 needs 2 kits, and VZ408 needs 4 kits. See data sheet for details. 

Issue When logging into SIGNAL, a pop-up error appears: Path not found. Error, Btrieve #915.  A local or shared drive cannot be found.  Correct the problem and try again. Environment SIGNAL Cause The SIGNAL.INI file located in the WINDOWS folder contains folder paths that no longer exist or were changed. Resolution Replace this file with a copy containing the default directories. The file can come from a database backup, another installation of SIGNAL, or from the link available in the previous line above.

Issue What is the I/A Series product suite? What I/A Series devices will be connected to or talking on my network? Does I/A Series support DHCP, DNS, and dynamic DNS? Which software protocols and RFCs (Request for Comments) does I/A Series support? I use Netscape Navigator as a browser, are there any ActiveX compatibility issues that I need to be concerned with? How do I back up this device? What LAN network management tools do I use to manage these devices? When does a UNC controller communicate with the Enterprise Server and vice versa? What does a system of UNCs and a Enterprise Server do to my network traffic and bandwidth? How do I access an UNC or Enterprise Server over the Internet? Can I access the entire I/A Series network if only the Enterprise Server is exposed to the Internet? How will I/A Series tie in to my security policy? How is the UNC protected from viruses? How do I protect someone from hacking into my I/A Series system? How do I set up / use a VPN? How does your system work with firewalls and proxy servers? What firewalls does your system work with? What LAN network management tools do I use to manage these devices? “I use Netscape Navigator as a browser, are there any ActiveX® compatibility issues that I need to be concerned with?” “I use Netscape Navigator as a browser, are there any ActiveX® compatibility issues that I need to be concerned with?” “Which software protocols and RFCs (Request for Comments) does TAC I/A Series support?“Which software protocols and RFCs (Request for Comments) does TAC I/A “I use Netscape Navigator as a browser, are there any ActiveX® compatibility issues that I need to be concerned with?” Series support?”“Which software protocols and RFCs (Request for Comments) does TAC I/A Series sup Environment I/A Series R2 Cause Frequently asked IT related questions for I/A Series R2. Resolution There is a document 'F-27407-4 IT Manager’s Frequently Asked Questions' that answers common IT related questions on the I/A Series R2 system. This document can be downloaded here. Frequently Asked Questions

Issue On an upgrade or other circumstances, the Continuum.mnu points to C:\program Files instead of C:\program files (x86) on a 64 bit PC. Product Line Andover Continuum Environment Windows 7 64 bit Windows 2008 64 bit Cause On an upgrade or other circumstances, the Continuum.mnu file points to C:\program Files instead of C:\program files (x86) and doesn't find the files being used. Resolution Under certain circumstances the Continuum.mnu file doesn't point to the correct folder. All of the buttons in the file point to C:\program Files instead of  C:\program files (x86). Use the following file to copy to each of the PCs that the menus are not working. The path of the Continuum.mnu is c:\program files\continuum\userprofile\continuum.mnu . This can be changed per Cyber by editing the Workstation in Cyberstation then clicking the preferences tab. The path for the entry can be edited. The Continuum.mnu that can be download from the web site has the default  (x86) paths in it. Continuum x86 Mnu file download Make a copy of the existing Continuum.mnu (Copy of Continuum.mnu) Delete the existing Continuum.mnu Download the file from the link above to the C:\Program Files (x86)\Continuum\UserProfile\continuum.mnu Restart cyber *** The path within the Continuum.mnu files must be correct and the path to the Continuum.mnu must reference the .mnu file with the path that you need

Issue What type of SIM is a Type 40? Environment Network 8000 Cause Service call to an older installation of Network 8000 product Resolution Type 40 is a SIM-TRANE. Click here for the SIM-TRANE Integration Manual.

Issue When using WPT 4.0 to upload controller databases, the system may display the following error message at the end of the upload process: Environment WorkPlace Tech version 4.0 Cause This error will occur whenever an Upload is performed under the following circumstances: 1. Any time the WPT project path is changed from the factory default such that it references a  drive path other than "C:", and the project is opened from that location. 2. Any time a project is opened through the use of the "Browse" function, and that project is located on a drive other than "C:"   Resolution See the attached Technical Alert TA04-05 for complete details.

Issue The documentation only describes mounting on curved pipe. Environment STP100 STP101 STP120 STP200 STP201 STP300 STP501 STP600 Cause In some applications, mounting the sensor on a straight pipe is necessary Resolution A description drawing is available here. The installation should be beveled against flow direction and the diameter should not be bigger than half of the diameter of the pipe.

Issue Documentation for KLR-E AC Room Controllers / Thermostats Environment AC Room Controllers Thermostats Cause Documentation for KLR-E type thermostats. Resolution KLR-E Thermostats are manufactured by EBERLE (Invensys) and available from Schneider Electric in Europe. Click here to download KLR-E documentation in French Click here to download KLR-E documentation in English/German

Issue CZU1201 replacement Environment CZU1201 Cause The CZU1201 requires replacement, but the controller had a exposed setpoint adjust dial on its fascia, the replacement CZU4201 does not. Resolution Replace the CZU1201 with the CZU4201 and a STR612 setpoint adjust unit, Wire to terminals 9 and 10 on the controller, set the internal setpoint on the controller to 10'C. CZU1201 datasheet click here. CZU4201 datasheet click here. STR612 datasheet click here.

Issue It is possible to use Thermistor Inputs in Xenta 281 Environment Xenta 281 Thermistor Inputs Cause The Xenta 281 does not have any special thermistor inputs. Resolution Yes, it is possible to use the Xenta 281 Universal Inputs for Thermistor Inputs. Click HERE to see the procedure.

Issue The TAC 200 OTP is obsolete, and the available documentation may be hard to find. Environment TAC 200 OTP 2001005000 Cause Documentation for obsolete products may be hard to find. Resolution All available documentation is available here

Issue Identifying the non-MicroSmart controllers in a DMS system. Environment DMS Cause Old installation of DMS with controllers not identified in any Niagara DMS/MicroSmart integration literature Resolution Controllers that were manufactured prior to revision 9.X do not have MicroSmart capability. These controllers are accessed through DMS programming only. It should be noted that it is not possible to add MicroSmart capability to these controllers. The controller model numbers are: Slave CO/CI Module N604-002, N604-012 Slave AI Module N604-003 Slave Pneumatic Motherboard N604-004 Slave AO Module N604-016, N604-017 General Purpose Slave Module N604-021, N604-025 The controllers listed above can reside on the same trunk with MicroSmart controllers that are revision 9.2, 10.X or 11.X. The only requirements are that the Slave controllers must have revision 9.0 firmware installed and the trunk must be a 2 wire design (not 4 wire). For more information about non-Microsmart controllers, review Tech Tip #350-95-03

Issue On December 13, 2012, the certificate verifying the authenticity of the Schneider Electric I/A Series G3 Workbench Applet (wbapplet) expired. Users will see the following error in their browser when accessing a station that is using a version of the wbapplet.jar with an expired code signing certificate: Environment Niagara G3 Cause When accessing an I/A Series G3 station through a web browser using a WbWebProfile, the web browser runs Workbench within a Java applet. To enhance security, this applet is 'signed' using a code signing certificate. This ensures that the applet has come from a reliable source and can be trusted to run with the proper permissions. Certificates used to sign applets are issued by a Certificate Authority (CA). Each code signing certificate issued by a CA has an established expiration date, with the maximum expiration being two years. Once this expiration date has passed, continuing to use a Java applet with an invalid certificate will result in warning messages within the browser. The applet will only be allowed to run after the user has acknowledged the warning and granted approval. Resolution An updated certificate is available in the new wbapplet.jar, available from The Exchange Download Center. This file will need to be added to the Enterprise Network Server, as well as on any ENCs that will be accessed from a browser. This file is for all released versions of TAC I/A Series G3 and is valid until March 30, 2015. Download wbapplet_March_2015.zip. Extract the wbapplet jar file  Click and Download The WbApplet Installation Guide. Note: Updated WbApplet files are available as part of upcoming Niagara 3.5 and 3.6 maintenance builds, as well as being from the Source website. In 3.7, wbapplet.jar is integral to the web.jar and contains an up to date certificate.;