Building Automation Knowledge Base

Issue How to interpret a M-Bus point details in a VX communication log such as External Temp [C] {1:0:0}. Environment Xenta Server 913 Cause The  External Temp [C] {1:0:0} message is providing important information about the point. External Temp = Field Type [C] = Unit {1 = Storage # :0: = Sub-Unit 0} = Tariff # Resolution Use the details of the communication log message to correct configuration problems in the device editor. MVAL External Temp [C] {1:0:0} value not required This message provides device details that a point exists, but the Device Editor is not looking for it. !MVAL External Temp [C] {2:0:0} =not received A point is expected but was not found.

Issue Vykon Tenant Billing invoice and report end dates are limited to year 2010 Environment I/A Series R2 (all versions), VTBS, Vykon Tenant Billing Cause None Resolution vtbs-2.301.532d.v1 resolves the year limitation. The year is now selectable beyond 2010. Caution: Always backup station database before performing any upgrade.

Issue Vykon Tenant Billing fails to reliably generate invoices for overrides that operate through midnight. Environment I/A Series R2 (all versions), VTBS, Vykon Tenant Billing Cause None Resolution vtbs-2.301.532d.v1 resolves the year limitation. The year is now selectable beyond 2010.   Caution: Always backup station database before performing any upgrade.

Issue Stat Replacements for I/NET controllers Environment I/NET Cause S/STAT and I/STAT are unavailable for purchase. Resolution The S/STAT has been replaced with the STR202 (User Manual for STR202) The I/STAT has been replaced with the STR250 (User Manual for STR250)

Issue SQL Host not passing data to Xenta 527 Web Server Product Line TAC INET, TAC Vista Environment I/NET 527 Web Server Cause When defining the Host for the primary SQL server, you have options of 1-250. When using a Web Server to send this information to a Vista System you must define the primary SQL server with a Host number less than 63. Resolution In I/NET configuration, define the primary SQL server's Host number between 1 and 63 Restart the I/O server Connect to each Xenta 527 Web Server on site and modify change the SQL Host # to the host number assigned in step 1 Restart each 527

Issue SQL Equalization Failure on Non-English Systems Environment I/NET File Equalization Client Computer Cause There is a collation mismatch that was caused during the SQL installation. Resolution Go to the Client PC Demote the client PC to Standalone Create a Temporary Folder on the C Drive, for example C:\Equalization Run the SQL Express install file Wait for the installation shell to start, but do not hit NEXT Browse to your C: Drive and look for a temporary folder with a current time stamp. This will likely have a name made of random numbers and letters Open this folder and copy the contents to your temporary folder. You may need to copy each file manual as a file beginning in $ will not copy.  You do not need this file. Cancel out of the SQL Express installation program Open the Command Prompt Browse to the temporary folder you copied files to Type in the following exactly, but replace *** with the sa password for your system This doesn't make any sense to me, any time the text on a link passes the end of the line the line is supposed to wrap to the next line setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SAPWD=*** /SQLSYSADMINACCOUNTS=Administrator /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS   This will run a limited version of the SQL installation.  Follow the instructions as prompted Re-promote the PC to Equalized client. Manually delete the temporary folder you created in step 3

Issue Vista reports running on EXCEL 2010 do not save the date format correctly. Environment Microsoft EXCEL 2010 Vista 5.1.5 and below Cause Excel 2010 is not supported on Vista 5.1.5 and below Resolution To get the date and time format to work correctly with Vista uninstall Excel 2010 and install Excel 2007. The other option is to upgrade to Vista 5.1.7 which supports Excel 2010 A possible  workaround  is to insert your trends into the Work Area of the report. That is the area to the right of the main page. Then you can copy this information to the main page and format the cells on the main page.    

Issue Need to re-license I/A Workplace Tech, have already used 3 of the 365 day licenses. Is there a way to add another one?   Environment I/A Series WorkPlace Tech Tool Software  Cause Renewal license limitation. Resolution Use the file WPTLExtractor.exe. This exe file allows for up to (15) - 365 days license renewals. Review TPA-RKFD-09-0025 for additional information.

Issue Xenta 102-B nviManOverride allows for flow or percentage overrides. But since this controller is intended to be used along with a Belimo flow controller/actuator, how do these modes of operation differ? Environment Xenta 102-B Cause Flow control is not actually an option for this controller. Flow values will be interpreted as desired percentages of airflow. Resolution nviManOverride.state = HVO_PERCENT, nviManOverride.percent = 35% The controller fixes the Airflow output (Y1) at 35% (3.5V) nviManOverride.state= HVO_FLOW_VALUE All of the flow values are actually being treated as percentages ... there is no way to set it to a desired flow. (nviManOverride.flow X nciNomFlow / 100) is limited to 0-100% and sent to the Airflow output (Y1). Emergency Override can override these setting, as can setting the controller to slave mode (the overrides would have to be performed on the master controller in that setting). The way to release these states is to set the nviManOverride.state to any value other than HVO_PERCENT or HVO_FLOW_VALUE. Those are the only two values accounted for in the logic.

Issue The GCMA-135-2 circuit board for the ASD repeater needs to be replaced but the item is not available for purchase. Environment RPTR-WIRE product, GCMA-152-2 circuit board Cause Unit needs to be replaced. Resolution The GCMA-135-2 circuit board used in the RPTR-WIRE ASD repeater is not available as a field replaceable part.  Purchase as an assembled unit using part number RPTR-WIRE.

Issue BACnet MS/TP Bus Communication Troubleshooting Checklist Product Line TAC IA Series Environment I/A Series BACnet controllers (MNB-70, MNB-V1, MNB-V2, MNB-300, MNB-1000) on an MS/TP bus. Cause BACnet MS/TP Bus Communication Troubleshooting Checklist Resolution This checklist provides several settings/configurations to review when faced with a communication problem at the controller level. The content was compiled from different resources, summarized, and laid out in an easy-to-use manner so as to provide a quick-reference document. Power Each controller requires 24 VAC from a Class 2 transformer. See the Installation Instructions for each controller, and the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Read-Only Flag Use the WorkPlace Tech Commissioning Tool (WPTCT) to check “Device Properties” of the controller. If the status is “Operational, Read-Only”, the input voltage to the controller may be too low. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Power Supply Wiring”. Due to the short duration of the low-voltage condition required to set the flag, it is unlikely that you will see it when measuring the input voltage with a digital meter, so check the “Device Properties”, and correct the problem as noted on page 28 of the guide, (reduce transformer loading, reduce wire length between transformer and controller, and /or use wire with higher current rating). Diagnostic LEDs The MNB controllers have onboard diagnostic LEDs that are useful in troubleshooting. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 3, “Communications Hardware Checkout”, Table: “LED Indications”, for a detailed description of the behavior of the LEDs and their diagnostic uses. Topology It is very helpful to draw the topology of the bus when you start troubleshooting. If there are no repeaters on the bus, the topology must be a daisy-chain, with no tees or stars. MS/TP network wiring to MN-Sx sensors must be run to the sensor, then to the next controller on the bus, in a daisy-chain; no tees or spurs are allowed. Maximum length of a wire segment is 4000 feet. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “MicroNet MS/TP Network Wiring”, for details on Communications wiring. Repeaters B-LINK-AC-S, Andover Controls MS/TP Repeater B-LINK-AC-F-S, Andover Controls MS/TP Repeater Fiber See the MicroNet BACnet Smoke Control Systems Manual, F-27419, for details on the use of these wire and fiber repeaters with MNB controllers. See F-27419, Chapter 5, “Approved MS/TP Repeaters”, including the wiring example. Maximum Number of Devices The maximum number of MNB controllers depends on the cable used, and the Baud Rate. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types”. The MNB controllers are quarter-load devices, so a maximum of 128 or less are allowed on an MS/TP trunk, depending on the cable used. Addressing Avoid duplicate addresses. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7, Chapter 1, “Required Configuration”, CAUTION: “Duplicate addresses on an MS/TP network trunk will result in erratic behavior, lost tokens, and disrupted communication. There is no software tool that will identify duplicate addresses on an MS/TP network trunk. Typically, if two controllers are set to the same address, one of the controllers will appear to be missing from the list, and the address shared by the two controllers will intermittently come and go from the list.” Biasing As a requirement of EIA-485 (formerly RS-485) bus topology, an MS/TP network must have a minimum of one set, and a maximum of two sets, of bias resistors in place. The MNB-300, MNB-1000, UNC-520, and ENC-520 have jumpers to enable or disable the bias resistors. See bulletin TB06-09, “RS-485 Bias Resistors and the UNC-520-2 / ENC-520-2”, page 3, for a photo of the bias jumpers on a UNC-520-2. Terminators A 120-Ohm End-of -Line (EOL) resistor is required across the “MS/TP +” and “MS/TP -” terminals at each controller at the end of a wire segment. The MNB-1000 and MNB-300 are equipped with a jumper-selectable end-of-line (EOL) termination resistor. The default position for the EOL jumper is “EOL termination not present.” See the MicroNet BACnet Smoke Control Systems Manual, F-27419, Chapter 5, “Approved MS/TP Repeaters”, Figure titled “UL 864 Listed MS/TP Repeater and Isolation”, Note 4, for an important exception, requiring external EOL for the MNB-300 and MNB-1000, when used on a bus with an approved repeater. If a UNC-520-2, ENC-520, MNB-V1 or MNB-V2 is installed at the end of the trunk, install a discrete 120 Ohm EOL resistor, part number EMSC-546, or equivalent. Cable Use of the proper cable is critical to the communications performance of the networked controllers. See the MicroNet BACnet Wiring, Networking, and Best Practices Guide, F-27360-7,Chapter 1, Table, “Approved Cable Types” for a list of recommended cable types. As shown in the table, cable selection affects both the maximum number of controllers allowed on the trunk, and the maximum baud rate. WorkPlace Tech Interface The MNB-ROAM-IA is the recommended communications converter for connecting WorkPlaceTech, including the WPT Commissioning and Flow Balance Tools, to an MS/TP trunk. It is supported in versions 5.7.1 and later. A converter that had been recommended earlier, the B & B Electronics model USOPTL4, was found not to operate reliably at speeds above 38.4 K baud. (See Direct MS-TP Connection with B & B Electronics Converters (Revised) - TB08-02-02 for details). The MNB-ROAM-IA supports Bluetooth wireless connection between WorkPlace Tech suite and the MS/TP network, for distances up to about 40 feet. One external Bluetooth adapter has been tested and approved - the Belkin USB adapter. (See Supported models of Bluetooth adapters with WorkPlace Tech for details). A problem we have seen with some MNB-ROAM-IAs is when trying to add Bluetooth device, the Bluetooth Wizard identifies it as "Serial Port Device, Unknown: Major(0), Minor(0)" instead of "tac-RoamIA:xxxxxxxx" where xxxxxxx is the serial number. There is no way for WPT to use the ROAM-IA if the computer can’t pair with it. Currently, there is no known solution, other than replacing the device. Divide and Conquer This is a strategy for dividing a bus into smaller sections in order to isolate a controller or section of bus that might be causing communication problems. The general idea is to divide the bus in half, and see if communications are possible from one end to the other end. If not, divide each half again, and continue until the problem(s) are found. Reference Documents F-27360 TAC I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide F-27358 TAC I/A Series MicroNet BACnet Workplace Commissioning Tool and Flow Balance Tool User’s Guide F-27456 TAC I/A Series MicroNet BACnet MNB-70 Zone Controller Installation Instructions F-27345 TAC I/A Series MicroNet BACnet MNB-300 Unitary Controller Installation Instructions F-27346 TAC I/A Series MicroNet BACnet MNB-V1, MNB-V2 VAV Controller Installation Instructions F-27347 TAC I/A Series MicroNet BACnet MNB-1000 Controller Installation Instructions F-27419 TAC I/A Series MicroNet BACnet Smoke Control Systems Manual

Issue What controller models have full-wave and which have half-wave rectifier type power supplies? Environment All Controllers Cause What controller models have full-wave and which have half-wave rectifier type power supplies? Resolution   Updates Product Rectifier Type       Full  Half Built-in     Wave Wave Isolation   CC-8102-024 X   X   CC-8104   X     CC-8111-024 X   X   CC-8118 X   X   CC-8155   X     CP-25xx   X     CP-8142-024 X   X   CP-8161-333   X     CP-8161-701   X     CP-8261-333   X     CP-8261-702   X     CP-8301 X   X   CP-8301-024 X   X   CP-8391-913 X   X   CP-8511-024   X     CP-8511-102   X     CP-8511-103   X     CP-8513   X     CP-8552   X     PP-2000 Series   X     PP-8121   X     PP-8311-120 X   X   PP-8311-024   X     PP-8516   X     PP-8616   X     PP-8621   X     T155 Series X       T158 Series X       T167 Series X       T168 Series X       TC97-MHP   X X   TC97-S   X X   TC97-SHP   X X   TC-98-M   X X   TC-98-MHP   X X   TC-98-S   X X   TSP7xxx         TSP-8111       08.03.06 VER-PHx-07-S   X   08.03.06 VER-PHx-08-S   X   08.03.06 VER-PHx-09-S   X               i2/b3865   X     i2/b3866   X     i2/b3865-S   X     i2/b3866-S   X     i2/b3865-WL   X     i2/b3866-WL   X               i2/b3885   X     i2/b3885-WL   X               i2/b3867   X     i2/b3867-S   X     i2/b3867-WL   X               i2/b3865-V   X     i2/b3866-V   X     i2/b3885-V   X     i2/b3865-V-WL   X     i2/b3866-V-WL   X     i2/b3885-V-WL   X               i2/b3887   X     i2/b3887-WL   X               i2/b3887-L-115 X   X   i2/b3887-L-115-C X   X   i2/b3887-L-230 X   X   i2/b3887-L-230-C X   X   i2/b3887-L-115-WL X   X   i2/b3887-L-115-C-WL X   X   i2/b3887-L-230-WL X   X   i2/b3887-L-230-C-WL X   X             i2/b3850 X   X   i2/b3851 X   X   i2/b3853 X   X   i2/b3850-S X   X   i2/b3851-S X   X   i2/b3853-S X   X   i2/b3850-WL X   X   i2/b3851-WL X   X   i2/b3853-WL X   X             i2/b3800   X     i2/b3800-S   X     i2/b3800-WL   X               i2/b3804   X     i2/b3804-S   X     i2/b3804-WL   X               i2/b3810   X     i2/b3810-WL   X               i2/b3814    X     i2/b3814-WL   X               i2/b3608   X     i2/b3624   X     i2/b3608-S   X     i2/b3624-S   X     i2/b3608-WL   X     i2/b3624-WL   X               i2/b3920 X   X   b4920 X   X   i2/b3920-D X   X   b4920-D X   X   i2/b3920-S X   X   b4920-S X   X   i2/b3920-WL X   X   b4920-WL X   X   i2/b3920-D-WL X   X   b4920-D-WL X   X             bCX1 Family   X               NetController I   DC Input               NetController II   X               CMX9924  X   X             ACX-2   X               CX9702 X   X             I2200AC X   X   I2210AC X   X   B-LINK-AC X   X   BLINK-F-AC X   X

Issue i2 controllers randomly go offline then back online 10 minutes later. During this period of showing as offline, all points under the i2 controller can be viewed. Environment Continuum i2xxx Controllers Netcontroller II (CX9680) Cause After an i2 controller goes offline on a noisy Infinet, the Netcontroller II can miss receiving the reconfig of the i2 controller coming back online. It fails to see the i2 controller come back online but still continues passing requests down to it and receiving responses. After 10 minutes of not receiving the token, the i2 controller announces that it is on the bus. At this point the Netcontroller II gets the controller online message and the network reconfigures again bringing in this controller to the token pass. Resolution This has been fixed in a new build of the Netcontroller II v2.100031 which can be found at the link below. Netcontroller II v2.100031

Issue DCom or other error message seen when running CyberStation Extended logging errors may be seen Error connecting to database may be seen, but CyberStation still runs up Alarms not getting to Active Alarm window Environment Continuum Cause An unspecified PC error, or Continuum Workstation error has occurred such that the CyberStation does not connect to the database correctly. This may be a sign of a more serious fault with the PC (hard disk, RAM fault, CyberStation installation error) but this would require further investigation. Resolution 1. If possible re initialize the database (all CyberStations need to be shut down before this is started. For a LAN install use "Server" or for a single User install use "Stand Alone") 2. Re initialize the workstation (first close the CyberStation), then test by running the CyberStation

Issue Analog outputs only put out 4 milliamps.  If you override them on they will put out 20 milliamps.  Should I send this controller in for repair? Environment Continuum Analog Output Cause When the controllers output HOA switch is in the AUTO position an output value of 20mA is indicated but the actual signal produced by the output is 4mA.  When the HOA is in the On position the output potentiometer can be adjusted to produce a 20mA signal. Resolution Move the controller with the analog output issue to another location, or remove all analog output connections to determine if the behavior caused by the field device wiring.

Issue Compressor will not activate blocking the cooling or heating of the Xenta 121-HP. Environment Xenta 121-HP Cause A compressor temperature lockout exists in the Xenta 121-HP application. The lockout has a minimum and maximum temperature the source signal must be between for the compressor to activate. The source signal changes depending on whether the application uses a air source or a water source. Air Source - nviOutdoorTemp Water Source - nviSourceTemp Resolution Ensure that the source temperature signal is between the compressor lockout minimum and maximum.

Issue Continuum 1.62: Personnel objects are losing their template associations Environment Continuum CyberStation Personnel Templates Cause Personnel objects are losing their template associations Resolution Install all Continuum 1.62 service packs.

Issue Using an End-User Dongle to license XBuilder or Menta when Vista Server is not installed Environment Vista 5.1.7 and older XBuilder Windows XP Menta Cause License may not be able to install due to previous license file conflicts. Resolution Install or re-install the TAC License Program found on Exchange Select Start>All Programs>Schneider Electric>TAC Tools>LMTools (or Start>All Programs>TAC>TAC Tools>LMTools Click on the Start/Stop/Reread Tab Click on "Start Server" Click on "ReRead License File" Close LMTools and Start XBuilder If the option is available, it is preferred to host the license to a MAC address instead of a dongle ID.

Issue How to display the currently configured access level for all User objects without having to open each User individually. (logon security groups) Environment Continuum Cyberstation Cause Want to see the access level for all User objects at the same time but unfortunately this attribute is not viewable in a ListView of all User objects. Resolution The Users access level is viewable as the KeyRings attribute in the text "dump" file of the User objects. Select and Right-click the User objects you want to dump to file. Select "Send To -> Text File..." and provide a file name. In the resulting dump file you will see that the KeyRings attribute shows the enabled groups in binary encoded hexadecimal. Group1 corresponds to bit1, Group2 to bit2 and so on; the KeyRings value is the hexadecimal representation of this binary value.

Issue What is the pin configuration for Modbus RTU when using a 9 pin comm port on a BCX controller. Environment BCX Modbus RTU Cause Connecting a BCX or CX controller to a Modbus RTU device. Resolution RS232 connection for a 9 pin BCX comm port.   BCX Comm 1 (9 Pin)            RJ 45 Connector @ Modbus device Pin 1 CXD        -->                 Pin 1 DTR Pin 7 RTS        -->                 Pin 2 CTS  Pin 4 DTR        -->                 Pin 3 CXD Pin 8 CTS        -->                 Pin 4 RTS Pin 5 GND       -->                 Pin 5 GND Pin 3 TD           -->                 Pin 6 RD Pin 6 DSR        -->                 Pin 7 DSR Pin 2 RD           -->                 Pin 8 TD