Building Automation Knowledge Base

Issue A TS-58011-774 Platinum RTD sensor is wired to a DMS Microsmart MSC-MPC controller. What is the maximum and minimum offset value considered acceptable for the sensor to operate accurately? Can the maximum wire length exceed 200 feet? Environment DMS Microsmart controllers Cause A large offset of almost 6 degrees must be used to make the reading accurate with a handheld temperature calibration device. Resolution There is no maximum and minimum offset value.  However, the length of wire used should not exceed 200 feet.  The recommended wire type is Belden #9501 (AWG24).  If these two wiring requirements are met, then the offset value used will not be "large". Below is a link to the sensor's installation guide.  Review "Software Setup" starting on page 3 to understand how to calculate the amount of error introduced to the temperature reading by the installed wire.  Use the temperature/resistance table on page 5 to verify that the sensor is accurate then use an appropriate offset value to eliminate the error introduced by the sensor wire. If necessary, use SOCALC on page 4 to develop custom SCALE and OFSET values. F-24874 TS-58000 Series Platinum RTD Room Sensor Installation Guidelines

Issue Does an End-User License Agreement exist for legacy software?  (Example:  SIGNAL and TreeTech) Environment Legacy software (SIGNAL, TreeTech) Cause Required for submittal on GSA projects. The legacy software is used to perform database backups. Resolution The link below provides a single page agreement branded with Schneider Electric which can be used with legacy software. F-26731 - Schneider Electric Buildings Software End-User License Agreement It is also available for download from the Publication Zone (on iPortal).

Issue Basic test of communication port on the Carrier DataLink, as accessed by the Network 8000 SIM-CCN. Environment Carrier DataLink communication gateway to a bus with CCN controllers Network 8000 SIM-CCN (Systems Integration Module for Carrier Comfort Network) Terminal emulator, such as HyperTerminal Click here for the SIM-CCN Installation Instructions, F-26167-2. See Figure 6 for detail of the serial cable required. Cause In some cases it is necessary to verify that third-party equipment is functional, independent of the SIM-CCN. Resolution Unplug the serial cable from the SIM, leave the other end connected to the Carrier  DataLink. Set up HyperTerminal: 8 data bits, no parity, 1 stop bit, 9600 baud, no flow control. Type " RT 1 DPTCONFG",  expect a "?" prompt.  If a prompt is returned, the port on the DataLink is functional; if no prompt is returned, the port may not be functional. If necessary, change the baud rate used by the terminal emulator to 300, 1200, 2400, or 4800 bits per second and repeat the test step 3. If the test fails at all of the possible baud rates supported by the DataLink, the port may not be functional.

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 Network administrator needs a document explaining the impact of GCM NIM communications on his Ethernet network. Environment GCM-86xxx with GCM-ETH-001 network interface Cause Customer wants to know impact of adding GCMs to his Ethernet network. Resolution GCM NIM configuration information and general Ethernet networking information is in the "NIM Networking and Configuration Guide", F-25955-4.  This document is available via the Publication Zone on iPortal. Bulletin 96-42, provides answers to frequently asked questions regarding the GCM NIM communications. NOTE: This information is based on the use of firmware version 11.2T in the GCM-NIM-001 interface.

Issue My computer has USB ports, but it does not have serial or com ports. Can I use USB ports? Environment For I/NET, Host computer that either Direct Connects (cable 072) or you need to connect to a controller such as a 7798C (cable 082) Continuum, Vista, Sigma, I/A Series, Pelco, DVR, DS, Com Port, Com, PTZ Control, Serial Port, Comm, Comm Port Cause USB to Com has issues downloading or communicating with system. Resolution The generic drivers which came with your USB to Com adapter do not allow two-way communication.  Prolific driver often helps resolve this issue. Download driver HERE or for the latest driver use link below: http://www.prolific.com.tw/US/CustomerLogin.aspx    you will need to logon as GUEST  

Issue A UNC was upgraded from version 431 to 5xx and polled GCM objects update more slowly.  What settings can be reviewed to ensure they are set at recommended values? Environment Niagara R2 UNC-520 (all revisions) Cause The older revision of the UNC and the age of the installation could play a role in the station settings, for the GCMCommService, not being set at recommended values. Resolution Appendix B of the Niagara Network 8000 Serial Driver Engineering Guide (F-27070) reviews the recommended settings of the GCMCommService.  Below is Figure 48 illustrating the General - Config tab of the GCMCommService properties with the required changes from Technical Bulletin 03_03:     Below is Figure 52 illustrating the Poll - Config tab of the GCM object.  Use a cycleTime of 0 ms to synchronize the GCM's Poll Cycle with that of the GCMCommService.  It is best to use the same cycleTimes for both the GCMCommService and the GCM object itself.

Issue Cannot see third-party LON devices when using the I/A Series Lon Device Manager to find and learn the devices on the LON Network.  The third party devices are known to be defined with a specific Lonworks Domain address. When using the I/A Series R2 (Niagara) WorkPlace Pro to commission LON controllers with specific a Lonworks Domain address, configure the Local LON device to match the Domain Length, Domain ID, and Subnet ID programmed in the third-party device. Environment I/A Series R2 (Niagara) WorkPlace Pro UNC 520 Third party LON controllers Cause When a third-party network management tool is used to define and configure / commission a LON network, the commissioning tool frequently uses specified domain address instead of the default "zero-length" domain address.  When using the I/A Series (Niagara) R2 WorkPlace Pro to learn a previously commissioned network, Workplace Pro will not be able to discover the LON devices until it has been configured to match the domain address of the network. Resolution Perform the following steps using WorkPlace Pro to configure the LON interface of the UNC and to learn the LON network. Open the Netmgmt page for the Local Lon Device then set the domain length and domainId to match the domain address of the device.  Apply the changes.  (See example here). Open the Properties page for the LocalLonDevice and select the Engineering tab.  Set the subnetId to match the subnet address of the devices.  (See example here). Recommission the Local Lon Device. Use the Lonworks Device Manager to find and learn the devices on the LON network.

Issue Documentation on the MSC-P-1500 Series Microsmart controller. Environment Microsmart controller MSC-P-1500 Cause Obsolete controller Resolution Click here to view the installation instructions on the MSC-P1500.

Issue How to set the Network 8000 MicroZone II (MZ2) back to its factory-default settings? Environment Network 8000 MicroZone II (MZ2) Cause Need to set the Network 8000 MicroZone II (MZ2) back to its factory-default settings Resolution See Technical Bulletin 95-08 for a detailed procedure. Revised 12/22/2011

Issue What is the part number for the battery in a Network 8000 GCM? Environment Network 8000 GCM-84000 series, GCM-86000 series, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK. Network 8000 LCMs. Cause Need to replace a discharged  battery in a GCM or an LCM. Resolution The part number for the replacement battery is E17-129. NOTE:  The E17-131 is a functional replacement for the E17-129 which is now obsolete.  The E17-131 can be found on iPortal   For a GCM-86000 series, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK, replace the battery according to F-25895, GCM-861X0 Series Global Control Module Installation Instructions, "Battery", "To Enable Battery", "To Replace Battery", and "Checkout" sections. For a GCM-84000 series or an LCM, replace the battery according to F-23116, "LCM / GCM Battery Installation Instructions".

Issue A DMS installation has nine controllers communicating properly.  However, only eight of them are listed as Microsmart controllers.  The ninth is identified in OPRIF as a "SAI" controller.  The DMS points for the SAI controller are updating with no issues.  How can its database be saved? Environment DMS (all revisions) Cause n/a Resolution The SAI controller was one of the first generation controllers developed for use with the DMS product line. It is referred to as a Slave AI Module. The old part number is N604-003 which may appear on a sticker somewhere on the controller itself. It takes six analog inputs. These controllers were installed with revision 8 firmware. On the printed circuit board, there will be an IC labeled with 8.x. The key to this controller is that it is NOT smart. It does not take a database. The Analog Input points MUST be created in the DMS. That's why it shows up as one of nine controllers but does not show up as a Microsmart controller.  There's no need to back up its database since it doesn't take one. Click here to view a figure of the Slave AI (SAI) Module.  

Issue Documentation on the MSC-V-400 Microsmart controller. Environment Microsmart controller MSC-V-400 Cause n/a Resolution Click here to view a datasheet on the MSC-V-400.

Issue Is the I/A Series R2 software compatible with a specific version of Windows? Product Line TAC IA Series Environment I/A Series (Niagara) R2 software Windows 32-bit operating system Cause Only specific releases of the I/A Series R2 software have been certified compliant with specific versions of the Microsoft Windows software.  Resolution The following chart details the version compatibility between the releases of the I/A Series R2 software and the various 32-bit versions of the Microsoft Windows Operating System software.  NOTE: I/A Series R2 software cannot be installed directly in any 64-bit version of the Microsoft Windows Operating System. Virtual platforms such as VMware Server 2 or Microsoft Virtual Server 2008 are not supported in R2.   R2 522 R2 527 R2 529 R2 532 R2 535 R2Tunnel Clients TunnelAX Clients  VAS 2.50 VAS 3.92                     Windows XP Professional (SP3) (32-bit) Y Y Y Y Y Y Y Y Y Windows XP Professional (SP3) (64-bit) N N N N N N N N N                     Windows Vista Business / Enterprise / Ultimate  (SP2) (32-bit) N Y Y Y Y Y N N N Windows Vista Business / Enterprise / Ultimate  (64-bit) N N N N N N N N N                     Windows Server 2003 Standard  / Enterprise (SP2) (32-bit) Y Y Y Y Y Y N N N Windows Server 2003 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N Windows Server 2003 R2 Standard  / Enterprise (SP2) (32-bit) Y Y Y Y Y Y N N N Windows Server 2003 R2 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N                     Windows Server 2008 Standard  / Enterprise (SP2) (32-bit) N N N N N N N N N Windows Server 2008 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N Windows Server 2008 R2 Standard  / Enterprise (SP2) (32-bit) N N N N N N N N N Windows Server 2008 R2 Standard  / Enterprise (SP2) (64-bit) N N N N N N N N N                      Windows Server 2012 (All Versions 32-bit & 64-bit) N N N N N N N N N  Windows Server 2012 R2 (All Versions 32-bit & 64-bit) N N N N N N N N N                     Windows 7 Professional / Enterprise / Ultimate (32-bit) N N Y* Y* Y* Y* Y* N N Windows 7 Professional / Enterprise / Ultimate (32-bit) (XP-Mode) N N Y* Y* Y* Y* Y N N Windows 7 Professional / Enterprise / Ultimate (64-bit) N N N N N N N N N Windows 7 Professional / Enterprise / Ultimate (64-bit) (XP-Mode) N N Y* Y* Y* Y* N N N                     VMWare Server (all versions) N N N N N N N N N Microsoft Virtual Server (all versions) N N N N N N N N N                     Microsoft SQL Server 2000 Y Y Y Y Y         Microsoft SQL Server 2005 N Y Y Y Y         Microsoft SQL Server 2008 N N N N N         Microsoft SQL Server 2008 R2 N N N N N         * Refer to PA-00163 for Windows 7 Support Info. NOTE: When selecting a computer on which to install the I/A Series R2 software, select one that meets or exceeds the recommended hardware for the selected operating system. For the larger Schneider Electric BMS offering please refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation

Issue A new MicroNet VAV controller has been installed under a MicroNet Microsmart Integrator (MN-MSI).  How is real-time data obtained from and how are commands sent to the new VAV controller? Environment MN-FLO3x MN-MSI DMS-35, -350A, -3500 Cause The MN-MSI is an obsolete product and no documentation is available for it. Resolution To integrate the new MicroNet VAV controller with a MN-MSI, create a Mode Control point Type 26 in the MN-MSI using the programming tool called DMS Operator Interface (also called PS-OPRIF or just OPRIF). Use this file to learn and program the Type 26 Mode Control point.  It is a complete chapter from the MN-MSI documentation.

Issue A mothballed government building is being put back into use.  It uses a DMS-35 with some Microsmart controllers for building automation and control.  What does the DMS-35 look like and what are its dimensions?  The customer wants to install power and communications to it.  The connectors for these cables are missing.  What do they look like? Environment DMS-35 Cause n/a Resolution Digital photos of a DMS-35 are provided. Scanned images of the obsolete installation guideline (portions thereof) are provided.

Issue Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Environment I/A Series G3, Modbus, Modicon, Schneider Electric PowerLogic PM800 Series Power Meters Cause Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Resolution As a workaround, the Modbus proxy points can be configured to poll the register as four integers and convert or combine the four integers to a single unsigned 64-bit value.  NOTE: that all four registers will need to be polled in a single message.  The following are two examples that can be used to read and convert unsigned 64-bit values.  The first example converts a Modicon power value with data type UINT64.  The second example converts a Schneider Electric PowerLogic P800 Series Power Meter with data type MOD10. Example 1 (Modicon UINT64):  The memory map below indicates the Total KWh+ value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 0500h. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the Modicon address 301280 (0500h) would be configured as follows. NumericPoint1 > Data Address (Address Format Hex, Address 500, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Hex, Address 501, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Hex, Address 502, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Hex, Address 503, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Hex 500, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple UINT64 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 65536.0 Multiply1 = 4294967296.0 Multiply2 = 281474976710656.0   The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToUINT64 program object can be copied into a station database. Example 2 (PowerLogic P800 Series Power Meter MOD10):  The memory map below indicates the Energy (Real Out) value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 1708. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the address 1708 would be configured as follows. NumericPoint1 > Data Address (Address Format Decimal, Address 1708, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Decimal, Address 1709, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Decimal, Address 1710, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Decimal, Address 1711, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Decimal 1708, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple MOD10 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 10000.0 Multiply1 = 100000000.0 Multiply2 = 1000000000000.0 The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToMOD10 program object can be copied into a station database.

Issue Modbus device integration to I/A Series R2 requires encode and decode of integer type registers to bytes. In this particular case, the Modbus device is a Patterson-Kelly ENVI boiler where the HIGH byte and LOW byte of a standard Modbus integer represent individual values.  However, the solution can be applied to other devices as required. Environment I/A Series R2, Modbus Cause Application - integration of Modbus into I/A Series R2 Resolution The attached R2 program objects can be used to encode or decode values as required. ModbusIntToBytes - Program will take the input integer value and decode to individual byte values as float status type values. ModbusBytesToInt - Program will take individual float status type values and encode bytes to a Modbus integer. Download ModbusIntBytePgms zip file ...

Issue  Unable to find or learn devices under Niagara. Environment R2 or G3 Niagara Cause Unable to find or learn devices under Niagara.  The LON device or devices may be configured to a different domain length.  Resolution To find devices under a different domain length download procedure click here

Issue Outside dimensions of the enclosure for the MNB-1000? Part Number MNB-1000-ENC. Environment Plant Controller, MNB-1000 Enclosure for the Plant Controller, MNB-1000-ENC Cause Need to determine mounting clearances. Resolution Outside dimensions are 12" wide x 11 1/4" high x 2 5/8" deep. See the figure below, from the MNB-1000 Installation Instructions, F-27347-3. (Figure 3, p.3.)   Click here for a link to F-27347.