Building Automation Knowledge Base

Issue What do the error codes mean on the SCX920 LCD display? Environment Infinet SCX920 SCX900 Cause What do the error codes mean on the SCX920 LCD display? Resolution See the attached 1995 INETGUID.pdf starting on page 4 for the LCD error code listing and troubleshooting tips. 

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 When running TAC Vista in a Network environment, there are several ways of setting up the license system. Sometimes, TAC Vista nodes (Vista users) "steal" license modules for each other. Environment Vista in network Flexnet license Cause When various TAC Vista systems are pointed to the same license server, one server can take or "steal" e.g. an OPC Client license which another server should use. Resolution For a complete explanation about the license system and how to setup the system and control licenses, refer to this video. A useful tool to use is the Options file, with the .opt file extension. Located in the License files folder, its easily monitored in a text editor, and could be used for Reserving or Excluding license modules for other TAC Vista nodes. Other features available for the Options file can be found in the Flexnet Licensing End User Guide. 1: Make a file called taclic.opt and place it in the same directory as the license files. 2: Edit the file with notepad and make the reservations you need. The syntax for each line in the file is "command amount feature HOST host". The feature names can be seen in the license files. Here is an example on how to reserve an OPC Client license for a PC called "BMS_SERVER_1" RESERVE 1 Vista.Server.OPCClient HOST BMS_SERVER_1 3: Restart the license server.

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 Changes to the Set Space Temperature do not work. Environment DC1100 DC1400 Controller Compensator Optimiser Setpoint Cause The pump overrun is timing down and will not allow the controller to act normally until it is complete. Resolution If the "Set Space Temperature" value is modified, then after the rotary switch is returned to "Auto", the user must wait until the Pump Overrun function has timed out. Where adjustments are generally being made, it is recommended that the Pump Overrun setting is set to 1 minute until  testing has been completed, after which it should be return to its required setting. To change the Pump Overrun setting carry out the following: Turn the rotary switch to "Setup". Select "System Menus" then "Alter Settings", and then enter the password of 0112. Select "Compensator", then "Set-up Menu", and then "Pump Overrun". Note the current value then change it to 1. On completion of the tests return the setting to its correct value. For the DC1100 data sheet, click here. For the DC1400 data sheet, click here.

Issue Integrate a Datacard (ID Works) Video Badging system together with an existing I/NET Seven system. Environment I/NET Seven ID Works Video Badging software version 6.5 All Windows version that are supported in the current I/NET Version of 2.42 and below Cause I/NET Seven and ID Works need to work as an integrated system. Resolution The attached White paper defines the necessary steps required to modify the ID Works to operate in the I/NET system. Note: if using 64bit OS such as Windows 7, a patch is required which makes ID Works 64bit. It is available from the 3rd party vendor. http://www.datacard.com/id-software-support-and-upgrades/id-works-identification-software

Issue Example Menta Programming using a STR as Setpoint adjustment to an Xenta I/O Module Environment Adjustable 10k Thermostats Menta STR-102 STR-103 STR-104 STR-105 STR-106 STR-107 STR-201 STR-202 STR-203 Cause Interfacing a STR to Xenta I/O Resolution Program an Analog Input to a Universal Input of an I/O Module Click on the HFB above to download this .MTA file.   The Expression Block is taking the hard coded -9 to 9 input and making it adjustable from the front end.   In simulation with a Calibrated Range of 5 the following setpoint results are produced: Analog In -9 -8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 Setpoint -2.5 -2.2 -1.9 -1.6 -1.3 -1.1 -0.8 -0.5 -0.2 0 0.2 0.5 0.8 1.1 1.3 1.6 1.9 2.2 2.5 Note: This example is for a non-linear input, with a setpoint adjust of +/-9. For a metric calculation, use a setpoint adjust of +/-5  and change the calculation in the expression block to A*B/10.  

Issue Testing operation of a CSC1701 compensator. Environment CSC 1701 Compensator Climatronic Cause Help with testing controller operation. Resolution The controller operation can be tested as follows; 1 - Testing the actuator operation. This is achieved using the controller +/- settings. Select + and the actuator will drive fully open. Select - and the actuator will drive fully closed. 2 - Testing the sensors. Isolate the power to the controller, and detach the controller front from the base. For each of the sensors disconnect one sensor wire. Using a multi meter measure the resistance between the disconnected wire and the sensor terminal with the wire still connected, this should give you a resistance reading. Refer to the resistance chart to confirm the temperature reading. Because of age the accuracy may not be perfect. Repeat for all sensors. 3 - Controller operation. With the sensors reconnected and the controller powered again, set the controller to "Day mode and Auto". Confirm that for the current outside temperature, the compensated flow water temperature is correct. To download the controller data sheet please click HERE. To download the sensor resistance charts please click HERE.

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 Site requirement that all card holders' records be kept disabled and are only enabled when card holders enter the building. Environment CyberStation CX9900 CX9702 CX9680 ACX5740 ACX5720 ACX781 Cause Not known cause Resolution Click here to see sample PE programs that implement the use case.

Issue Boiler plant is not operating. Environment DC1100 DC1400 Compensator Plant Off Day Economy Cause Controller is in a Day Economy mode. Resolution The DC1100 / DC1400 has a mode known as "Day Economy, this will prevent the plant from working. The controller display will show "Day Economy", its operation is as follows. Day Economy Day economy will allow the system to turn the heating off during an occupation period if the space temperature is at or above the Space Setpoint and the outside temperature is within 4 degrees of the Space Setpoint. When the heating is switched off by day economy, pump run-on will commence. If during a day economy period the space temperature drops more than 1 degree below setpoint or the outside temperature is no longer within 4 degrees of the Space Setpoint then the heating will switch back on. The Day Economy function can be disabled though the controller menu system. For further details please select the data sheet HERE.

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 Clarification on dip switch six and station addressing for the SCU1200, SCU1280, or SCU1284 Product Line TAC INET Environment I/NET Seven with Access Control using an SCU SCU1200, SCU1280, or SCU1284 Cause Clarification on SCU and dip switch settings being open, enabled for dual or single station addressing (2 or 4 doors) Resolution If the Device Type is SCU1200, SCU1280, or SCU1284: set the Number of points to either 1 or 2. Choose 1 if the SCU is configured to operate in the “single-address” mode (DIP switch S1-6 = OFF). Choose 2 if the SCU is configured to operate in the “double-address” mode (DIP switch S1-6 = ON). In order to control more than two doors, the SCU1284 must be configured to operate in the double-address mode. Though the TCON312 shows the dip switches for 1-6, there is still a bit of clarity which can be provided on how that looks on an actual SCU. The example from the TCON is shown here: And this is a photo below of an SCU which is setup as 0101 with dual addressing since Dip Switch 6 is in Dual Address mode shown in the picture below. When penetrating down to it using Edit, Host Computer, Network Configuration, SCU 1284 is shown with 2 Points with door addresses: 010108 Door1 010109 Door2 010208 Door3 010209 Door4 After checking MCU Configuration, I added the points in the Network configuration. The main point here is that Dip Switch 6 is up on the Open side of the Switch bar shown in red which is the dual point and 4 door configuration.   Note: Concerning the numbering scheme for addressing the SCU, it is important to number your SCUs with an address then skip the next number so in the event you dual addressing for four doors, the second address is available. Don't use addresses 28, 29,30, and 31 as those are reserved for the Remote Arming Terminal.  Overlooking this can result in future headaches of moving SCUs around in the addressing scheme which is never recommended. Example for a site containing 4 SCU door controllers: SCUa address 2, SCUb Address 4, SCUc Address 6, SCUd Address 8.  Another example configuration: One reader inputs to READER1 and READER2? Here is that wiring example. In order to use more than the first eight inputs on the SCU, you must configure the SCU as a double-address controller. When you enable the double-address mode (DIP switch S1-6 = ON), inputs 1 through 8 are monitored on the selected subLAN address (i.e., the primary address) and inputs 9 through 12 are monitored on the next consecutive subLAN address (i.e., the secondary address). The input points are defined in the I/NET host using two separate SCU controller assignments, the first providing eight input point definitions and the second providing 4 input point definitions. The SCU’s outputs are also divided across two LAN addresses when the SCU is operating in the double-address mode. The first four outputs are assigned to bit offsets 00 through 03 on the SCU’s primary address. The last four outputs are assigned to bit offsets 00 through 03 on the SCU’s secondary address.

Issue Xenta controllers are 1 hour ahead of PC  time. All controllers and PC are in the same timezone and have the same daylight offset time. Environment Windows XP Service Pack 1 and 2 Cause Windows daylight times are incorrect for the current dates. The PC time is in normal time not Daylight time even though the update daylight saving automatically is selected. Resolution Install windows update KB955839. This updates the daylight dates in windows. Click here to download this update

Issue How to bring SX8000 objects to Continuum when upgrading. Environment Infinity SX8000 Continuum CyberStation Debug document Cause Upgrading from legacy Infinity SX8000 system to Continuum Resolution See Infinity to Continuum upgrade for information on how to convert Infinity SX8000 objects to Continuum.

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 Configuration and understanding 32 bit values. Environment Sigma IC3 Modbus 32 Bit values Cause Correct configuration when reading the 32 bit value.   Resolution Below is a list of the actions carried when attempting to interface an IC3-Modbus to a third party Modbus device. The device instructions were not clear, and therefore this process was worked through. The gateway.txt  had been configured as had been suggested, but an error messages indicating the function code 4 was not allowed was received.  Modified the gateway.txt to use function code 3 which corrected the function code error, but now the register address still caused an error. Changed the gateway.txt string to 304,3,3,0xC652,1,1,0,0,0 and this eliminated the address errors, but did not return the correct value. Changed gateway entry string to 304,3,3,0xC652,1,0x0202,0,0,0 which is 32 bit unsigned value data not swapped. This still returned an incorrect value. Changed gateway entry string to 304,3,3,0xC652,1,0x1202,0,0,0 which is 32 bit unsigned value data swapped. This returned the correct value. For a copy of the Gateway.txt file click HERE.

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.