Building Automation Knowledge Base

Issue RM3601 / XRM3201 Wiring connection details. Environment RM3601 3601 XRM3201 3201 Actuators Wiring connection details Cause Actuator wiring details. Resolution The RM3601 actuator is a 230 volt actuator, its connection details are as follows; Terminal 1 - Connection for open signal (230V live) Terminal 2 - Connection for close signal. (230V live) Terminal 3 - Connection for Neutral. Terminal 1T - Transfer connection, passes 230V to other devices when actuator is open. Terminal 2T - Transfer connection, passes 230V to other devices when actuator is closed. The XRM3201 actuator is a 24 volt actuator, its connection details are as follows; Terminal 1 - Connection for open signal (24 volts) Terminal 2 - Connection for close signal. (24 volts) Terminal 3 - Connection for zero volt. Terminal 1T - Transfer connection, passes 24V to other devices when actuator is open. Terminal 2T - Transfer connection, passes 24V to other devices when actuator is closed. To review the data sheet please select HERE.

Issue In an R2 (Niagara) station with BACnet, getting errors in Standard Output Window, "Transport lockup detected!" and multiple "TException E_QUEUE_FULL {BClient}". Environment I/A Series R2 (Niagara) UNC station with BACnet service. Cause Queue sizes in BACnet Service are too small. See the BACnet Integration Reference, Chapter 6, "Configuring BACnetService Properties", "Engineering", Figure 6.4, and section titled "Message Queue Properties" for further details. Resolution Increase all three of the queue sizes(transportQueue, serverQueueSize, clientQueueSize) , from the default values of 16, up to 90.   Monitor the Standard Output Window for errors, and increase the queue sizes in increments of 50, up to 500. It may be necessary to reboot the station in order for the changes to take effect, because the changes are being made to a service.

Issue Access Expert V2 configured MR52 Interface with inputs and outputs showing as Not attached (See snapshot) Product Line EcoStruxure Access Expert Environment V2 SSC MR52 Interface Cause The MR52 interface was previously configured with elevator controls but now has been detached in some manner. Resolution Remove the configured elevator references on each input and output individually and resave the point. Delete and re-add the points and configure the I/O as needed.  V3 works differently then V2. V3 allows for a more granular configuration so that the I/O selection just allows for the specific elevator other I/O selections. In V3 the assignments doesn't need to be released, only reselected.

Issue WebPinpoint crashes on "Failed to call piLiveData>GetLiveData(). AccdataServices has an error" on both WebServer and Client PCs. Product Line Andover Continuum Environment WebClient IIS WebPinpoint Pinpoint  Cause The asp_net account does not have permission to access the ILiveData interface. ILivedata is an internal engine that WPinpoint uses for polling points values.   Resolution In Workstation Preferences on the Web Server, increase the value of WPinPoint Continuous Polling Rate until  from crashes no longer occur.  If this is for a Windows Server 2008, Windows 7 or Windows Vista, make sure the web.config file has been edited. See also Error: "DNWacserverFactory/WACServerFactory.soap" when accessing Webclient 1.9x Pinpoint.

Issue When using a HyperLink in Vista WebStation graphic page the error message "This content cannot be display in a frame" is shown. Clicking the link to open this content in a new window will properly display the web page. Environment Vista WebStation 5.x.x Cause Newer web browsers support a HTTP header flag named X-Frame-Options which allows the remote web server to block display of its content within a web page frame. This is a security measure to stop "click jacking". Internet Explore 8, Internet Explorer 9 will display the error message Google Chrome will ignore the hyperlink. Resolution Instead of linking directly to the web page link to the folder that contains the Hyperlink object and then clicking on the hyperlink object will open the web page in a new window if the target property is empty or "_blank". Another alternative is simply click the "Open this content in a new window" link.

Issue I/A Series Integration to BACnet PTP protocol Environment I/A Series R2 I/A Series G3 Cause Supported I/A Series BACnet integrations are only BACnet Ethernet, BACnet IP and BACnet MS/TP protocols. There is no driver for integration to BACnet PTP devices. Resolution Schneider Electric solution: Using the TAC Xenta 913 LonWorks Gateway - The Xenta 913 is able to connect to a BACnet PTP half router. Data can be mapped to LonWorks or BACnet IP which are standard protocols in I/A Series. Knowledge of the Xenta 913 and TAC XBuilder is required to configure the Xenta 913. Third party solution: Use a 3rd party BACnet PTP to BACnet IP, BACnet Ethernet or LonWorks gateway. A company which has the gateways for this is Field Server Technologies. See there BACnet FieldServer Drivers here.

Issue A site backup is not available. Product Line Satchwell BAS2800+ Environment Backup No Index Uploading Cause The site is stand alone and the backup is not available. Resolution To recover the site data carry out the following; Use the Pocket Terminal application to review the outstation node configuration. Setup the BAS2800+ terminal to match the configuration observed from the node. Using the BAS2800+ System Diagnostics; Select the outstation number and then from the options menu, select "Transfer Files" Select to transfer PNTFLE.REC from the outstation, to C:\BAS\Data\osn??\PNTFLE.REC Shutdown BAS2800+ Locate and run the "No Index" utility. Run the utility to create the index Restart BAS2800+ and confirm that the points are available and can be displayed. Please note the "No Index" utility cannot name the index segments, this will need to be done by hand. Link to download the No Index utility

Issue A duress input is only triggering duress alarm events and not the return to normal events after the duress input is reset. The point going into alarm is seen on the Monitoring | Status page when viewing all alarms but the return to normal events are not being displayed. Product Line EcoStruxure Security Expert Environment Security Expert Cause The problem is due to how the Event Filter and Event Report are configured. Resolution Check to see that the Event Filter includes all of the Event Types that should come through as shown alarms. In the example this would be at least "Input Opened" and "Input Closed" under the "All Input Events" folder.   Event Filter: Create an Event filter and include the correct Event Types that you wish to report on.   Event Report: Add the Event Filter you configured in step 1. To show those Alarms, create/modify a Status Page under Monitoring | Setup > Status Page Editor, set the Type to Event Windows and add the Event Report from step 2 above to the Record field.

Issue Is there anything that will convert AC256 drum programs to Continuum Plain English programs? Environment Cyberstation Plain English Cause When doing an AC256 to Continuum upgrade, is there a utility to convert drum programs to Continuum Plain English. Resolution Various partners and branches have written their own utility. Product Support does not distribute or support any of these. The results of most are underwhelming - PE code that looks "drum-ish" and often involves enough clean up that is better when PE is done from scratch. Alternatively, a request for improved or other utilities can be made on the Exchange Community.  

Issue When using the UI-8-10V for 0-10V analog input, the ElecValue of the input shows the half of the actually applied voltage. Product Line Andover Continuum Environment NetController: CX9900 , CX9940 , CX9680 IOU: UI8-10V (UI-8-10V) Cause UI8's 10V dip switch functions as the voltage divider. Resolution As the UI8's 10V dip switch functions as the voltage divider, it halves the 10V input voltage into 5V and uses it as the measured input. So, the ElecValue of the input shows the half of the actual input voltage. Note: When the input is configured for 10V operation, the input impedance is 4.4kΩs. Therefore, the sensor used would have to be able to source as much as 2.3mA. If input impedance is an issue for the sensor, then select the 5V input switch setting and use external resistors as detailed in How to use a 0-10V Sensor on a controller with 5V inputs.

Issue General Continuum instability is followed by the following error when viewing Graphic panels. "Pinpoint: Failed to call pILiveData->GetLiveData(). ACDataServices has an error." Product Line Andover Continuum Environment Continuum Cyberstation Cause Continuum has become unstable due to modules not starting up properly. This can be evidenced by looking at the Windows Application Event Logs for "Send Email" errors when alarms occur. This may then be followed by Continuum applications starting to crash and post errors. Resolution Remove "email" and "page" entries in Event Notifications if there has not been an Email client installed and configured to email alarms. Set Windows virtual memory settings to 4096. Ensure time synchronization between Cyber and CX. In Continuum General preferences set the Time Interval Between Requests to 100 (default is 30). Set COV increment for noncritical points to non-zero numbers (default is 0). Upgrade to 2.03. If already at 2.03, a reinstall of Continuum may be necessary or at least the pre-requisite 'Visual C++ 2005 redistributable'. Also refer to: Crash of ACCDataServices on start-up or run 

Issue DC2000 series Optimiser / Compensator Controller requires replacement due to obsolescence. Product Line Field Devices Environment DC2000 series Optimiser / Compensator Controller installed to control Variable Temperature Mixing Valve, Boiler/s, Pumps etc. Cause Obsolescence of DC2000 series Optimiser / Compensator Controller. Resolution OVERVIEW DC2000 series Optimiser / Compensator Controllers are flexible with regard to the number and type of electrical inputs and outputs to which they may be connected, enabling the Controller to be applied to a wide range of control applications.  Overview details of the DC2000 Optimiser / Compensator Controller may be viewed here.    INSTALLATION AND COMMISSIONING In view of the numerous control applications to which the DC2000 series Optimiser / Compensator Controller may be applied, numerous wiring connection variations will also apply. Please therefore check the number of inputs and outputs connected to the DC2000 series Optimiser / Compensator Controller installed before proceeding, as this will assist in determining the suitability of the possible replacement Controller suggested below. Installation and Commissioning details of the DC2000 series Optimiser / Compensator Controller may be viewed here. POSSIBLE REPLACEMENT The most common control application to which theDC2000 series Optimiser / Compensator Controller may be applied comprises the following combination of inputs and outputs.  Outside Air Temperature Sensor Inside Air Temperature Sensor Compensated Heating Temperature Sensor Variable Temperature Heating Circuit Valve Actuator Boiler/s (2 maximum) H W S On/Off output (independent) Should such inputs and outputs be confirmed then the DC1100 Optimiser / Compensator may be installed in place of the DC2000 series Optimiser / Compensator Controller. Details of the DC1100 Optimiser / Compensator Controller may be viewed here. Drayton A7xx series Sensors connected to the DC2000 Optimiser / Compensator Controller are compatible with the DC1100 Optimiser / Compensator Controller and may therefore be retained. N.B. It should be noted that where a DC2000 series Optimiser / Compensator Controller is included in an installation of a more complex nature then an alternative solution utilizing different products may need to be considered. In such installations not only will the DC2000 series Optimiser / Compensator Controller need to be replaced but its associated Sensors will also need to be replaced. Resolutions to such installations may best be determined following a review of the control system installed by a member of the local Schneider Electric office.

Issue What I/A Series G3 driver can be used to directly interface a McQuay MicroTech OPM with Microtech legacy controllers to the ENC-520? Environment I/A Series G3, ENC-520 Cause The existing system includes McQuay legacy products (e.g MicroTech 1 controllers) communicating to a MicroTech OPM (Open Protocol Master) panel.  The system does not support open protocols such as BACnet or LonWorks. Resolution The McQuay driver communicates to the MicroTech legacy devices through the McQuay OPM.  The driver is compatible with I/A Series G3 versions 3.4 and higher.  The part number through Schneider Electric is ENC-DRV-MCQ. Click here to download the Niagara McQuay Driver Guide.

Issue Using Apollo engineering software and receive an error 'Login failed for user 'Andover97'. Environment Apollo v3.1 Continuum Cause The wrong user credentials are used, Apollo is expecting a standard password. This authentication can fail if the password is different to the default or if SQL is set to for case sensitive passwords.   Resolution It is possible to rectify by performing the following using the Apollo software. 1. Select the option 'Change Database' under the 'Edit' menu. 2. Select 'Non Standard Logon' and try different user name and password combinations, clicking 'Test' to check if the login works. It should be one of the following combinations unless the Continuum SQL install master password has been changed. (removed due to public access) *Try each variation of the default username and password with uppercase first letter and lowercase first letters. 3. When the test in step 2 works, click on the 'Change Database' button to set the new database. Unfortunately this is not saved and it will need to be re-entered each time Apollo is started.  

Issue When specifying the configuration of the SE7300 you can choose between "50" and "55" in step 5 of the part number. Product Line EcoStruxure Building Expert, Field Devices Environment SE7300 Cause Different options of configuration when defining the part no for the SE7300 Resolution The difference is that the "50" option is PIR Ready, but PIR cover of unit is not included. Option "55" is with the PIR cover already mounted upon delivery. 

Issue When using the LOYTEC NIC709-USB100 LON Interface every time an attempt is made to connect to an MNL controller via WorkPlace Tech 5.X it gives an error "installing device driver" and causes the PC to lock up. Product Line TAC IA Series Environment WorkPlace Tech 5.x Loytec NIC709-USB LON interface Cause WorkPlace Tech 5.x is not compatible with Loytec LON interfaces. Resolution Only Echelon LON interfaces are supported in WorkPlace Tech 5.x due to it utilizing the Echelon Open LDV driver. The WorkPlace Tech installation instructions notes the following as part of the hardware requirements:- Echelon™ LonTalk™ adapter card, WPA-LON-x. Since many newer notebook computers do not have a PCMCIA card slot and therefore must use a USB LON interface an Echelon U10 USB interface (75010R) can be utilized. Also see Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for an adaptor that can be used to convert PCMCIA to Express card.

Issue Require manuals, datasheets, install guides or sales information for Field Devices. Product Line Field Devices Environment European Field Devices, U.S. Field Devices IPortal, USiportal, Extranet Datasheets, Specification, manual, sources of information Cause Where to obtain field device data? Resolution Field Device information for your part of the world can be accessed from the Exchange Extranet: Field Devices. When you logon to the site it will allow access to products available for your location. U.S. Products can also be easily found using the search in iPortal. Catalog information can be obtained via the following Valve, Actuator, Sensor, Field Device, Peripheral, HVAC Control Devices Datasheets and Catalogues, Selection Tool. Note: The Extranet links above are for Schneider Electric personnel or approved partners, if you do not have a logon account please contact your local Schneider Electric office for information. For pricing information please contact you local Order Entry or sales contact.

Issue Can a Remote Client run I/NET Reports (SevenReports) from the I/NET Seven Server's SQL database? Product Line TAC INET Environment I/NET Seven SevenReports Cause In a Remote Client configuration, the local SQL database is not used and is typically blank.  To enable the local SevenReports engine to connect to the I/NET Server the ODBC data source must be configured to successfully connect to this server workstation.  Resolution To download more detail instructions please Click Here Remote Client: The following procedures describe how to configure the local I/NET Seven ODBC data source to communicate with the SQL server on another I/NET Seven workstation. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools) In the ODBC Data Source Administrator editor, click the System DNS tab, highlight the Seven ODBC data source, and click Configure.... In the DSN Configuration editor, use the Server field to specify the name of the I/NET Seven workstation and SQL Server instance that will be used as the server for this workstation. Click Next and enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be passinetdb3p_SE. Click Next two more times and then click Finish. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration. Click the Test Data Source... button to test the connection. Click OK to close the Test Results window. Click OK to close the DSN Configuration editor. Click OK to close the ODBC Data Source Administrator editor. Third-Party Applications Use the following procedures to create a new ODBC data source on a PC that is not running I/NET Seven. The purpose of this task is to allow local third-party applications to communicate with I/NET Seven running on another PC. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools) In the ODBC Data Source Administrator editor, click the System DNS tab and click Add.... In the resulting window, scroll through the list and highlight the driver appropriate for the version of SQL Server installed on your PC:  - For MSDE/SQL Server 2000, select SQL Server. - For SQL Server 2005, select SQL Native Client. - For SQL Server 2008, select SQL Native Client 10. Click the Finish button. In the DSN Configuration editor, make the following settings:  - Define the data source Name as “Seven ODBC”.  - Define the Description as “ODBC Connection for I/NET Seven”.  - Use the Server field to specify the name of the I/NET Seven workstation that will be used as the SQL server for applications on this PC. Click Next and make the following settings:  - Select the With SQL Server authentication using a login ID and password entered by the user option. - Near the bottom of the editor, enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be PassInetDb3p_SE. Click Next two more times and then click Finish. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration. Click the Test Data Source... button to test the connection. Click OK to close the Test Results window. Click OK to close the DSN Configuration editor. Verify that the new ODBC data source has been added to the list of System Data Sources. Click OK to close the ODBC Data Source Administrator editor. More detailed information is also available on Extranet in TCON301 Chapter 2 - ODBC Driver Interface section.

Issue The MNB-Vx (MNB-V1, MNB-V2) controllers are shown as replaced by the MNB-Vx-2 (MNB-V1-2, MNB-V2-2) on iPortal.  What is the difference? Environment MNB-V1 (-2) MNB-V2 (-2) Cause Production change Resolution There are no functional differences between the MNB-V2 and the MNB-V2-2 controllers. The part number was changed to allow tracking of an internal manufacturing change in the actuator part of the assembly.

Issue Webstation Displays the error: The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access when attempting access. Product Line TAC Vista Environment Vista Webstation ASP .NET Cause Incorrect setting in ASP and .NET Resolution Please run the DCOM Config 1.0.3.0.exe utility located in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET.