Building Automation Knowledge Base

Issue Failing communications from a MicroNet View front end. Environment MicroNet View communicating to a MicroNet ARCnet or NCP  LAN. Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position.  Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Place switches 1 to 4 to ON for compatibility with NCP/ARCNET I/O- Server (MicroNet View versions 1.0 and later). Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue Failing communications when Xenta 555/731, VisiSat, StruxureWare Building Operations automation server/enterprise server connected to MicroNet ARCnet system through an MNMi. Product Line Satchwell MicroNet, TAC Vista, EcoStruxure Building Operation Environment Xenta 555 or Xenta 731 communicating to a MicroNet ARCnet LAN VisiSat communicating to a MicroNet ARCnet LAN StruxureWare Building Operations automation server/enterprise server communicating to a MicroNet ARCnet LAN Cause MicroNet Mi bit switches not set correctly. Resolution Cold Starting a MicroNet Mi Caution: The cold start procedure clears all configuration data from the non-volatile EEPROM of the device and reloads default settings. A cold start is performed using bit switch S1, as shown in the following diagram. To perform a cold start: Energise the device and verify that the RUN LED flashes at about once per second. Unplug any connections to 9 pin plug 3 and 9 pin plug 4. Set all switches to the off position. Place bit switch 8 in ON position and then return to OFF position. You will not see anything change. Place only switch 1 in the ON position. The remaining switches must be in the OFF position. Place bit switch 8 in ON position and then return to OFF position. You should see the RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, then the RUN LED should flash at about once per second. Switch 1 only must be ON for direct connection to Xenta 555. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. See data sheet DS10217A for more information.

Issue Personnel.csv file fails to import into Continuum No error message is shown Product Line Andover Continuum Environment Continuum access control Keywords: CSV, Import, cardholder, personnel Cause CSV file gets modified by MS excel such that the import fails During the process of manually changing and saving a personnel.csv file within MS excel, a number of commas are added to the first line (corresponding to the number of column fields in the CSV) Resolution Use notepad or similar to delete commas before importing into Continuum as Microsoft Excel does not show up any trailing commas This will NOT import correctly Personnel,,,,, Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 This will import correctly Personnel Name,FirstName,LastName,CardNumber,CardType,SiteCode Smith_Fred,Fred,Smith,10,Infinity_37,3701 For more information on CSV imports Click Here For an example .csv file for testing Click Here Note: If importing X Driver points using a .csv file the comm port attribute "Port" must always be defined before the X Driver parameters Param1, Param2 etc. The Port must contain the full path e.g. "Network1\CXName\Comm1" Example X Driver Numeric: InfinityNumeric Name,Alias,Format,Description,Port,Param1,Param2,Param3,Param4 XDRPoint1,XDRPoint1,##,First X Driver Point,Network1\CX1\comm4,1,3,10001,1

Issue How do you determine how large a database will grow when using Vista? Which version of Microsoft SQL Server is needed? Product Line TAC Vista Environment Windows XP Windows Vista Windows Server 2003 Windows Server 2008 SQL Express SQL Server Standard SQL Server Enterprise Cause A database will grow based on the number of objects and logging requirements for a project. Estimating how much a database will grow over time based on the number of trend logs and events should be done to determine which Microsoft Database solution is needed for the site. Microsoft has placed database size limitations on the free versions of their database engines called SQL Server Express. The size limitations are 4 and 10 gigabytes for Microsoft SQL Server 2005 Express and Microsoft SQL Server 2008 Express respectively. If this size limitation is exceeded, it can produce unwanted results including database corruption, data loss, or inaccessible data. If the estimated size of a database over time exceeds these limitations then a full Microsoft SQL version must be implemented. Resolution An Excel spreadsheet has been developed to help evaluate the size of a Vista database, to determine which version of SQL should be used. The Vista database estimating spreadsheet takes into consideration 2 main areas: Trend Logs- total amount of logs, intervals and the number of days to retain Events- total amount of access events. The number of data logs, extended log intervals, number of days to retain data and other estimation information can be inserted into the spreadsheet. The sheet will calculate the information and do the following: Estimate the space required for that object type and the sum of all object types Indicate which version of SQL Server is needed This spreadsheet can be downloaded by clicking on the following link: Click Here Update: In Vista 5.1.7, there is a Trend Log Calculation Tool included (under Schneider Electric-Tools)

Issue Addressing issues with M-Bus metering application because it is unclear what Storage# or Tariff# to use in Xbuilder. Environment Xenta 913 5.x.x Xbuilder 5.x.x Cause Manufacturers of meters which utilize the M-Bus protocol may not specify the Storage# or Tariff# needed by Xbuilder. They may instead include DIF or DIFE information regarding their meter points. These codes correspond to the M-Bus protocol and indicate the Storage# and Tariff# of the data. Resolution Use the M-Bus DIF calculator to parse the data type, Storage#, and Tariff# of the data point. This spreadsheet should be sufficient for the majority of applications, but some exceptions apply. The hexadecimal codes for the data point must be provided by the manufacturer for the calculator to be useful.

Issue Review of Windows event log, product event logs, or error windows during operation provides an error code number that is unreadable. Environment Microsoft Windows Cause Microsoft uses a standard list of error codes which programs can access. The display of these errors is typically in a decimal or hexadecimal format. Resolution Use the Windows Error Codes spreadsheet which allows the user to enter the code as either Hexadecimal or Decimal format and provide the text description for the error code. Use the error code description to further diagnose the problems being experienced. Guidance on whether a code is Hexadecimal or Decimal: 0x00000001 - Hexadecimal -214000000 - Decimal

Issue Issues being experienced can vary, here are some examples: The digital clock gains a minute every few seconds. The code (0112) when entered to accept alarms, is not accepted. Environment DC1100 controller DC1400 controller Cause The unit has not been correctly cold-started after first being powered on. Resolution The DC1100 / DC1400 controllers must be correctly cold-started after first powering up, this ensures that the default configuration is correctly installed. Cold-start the controller using the following process: Turn off the power to the controller. Press and hold in the ENTER and EXIT keys. Power up the controller whilst continuing to press the ENTER and EXIT keys. Release the ENTER and EXIT keys. The controller will now go through a self test programme and load its defaults. To review the DC1100 / DC1400 controller overview, select here To review the DC1100 controller general data sheet, select here To review the DC1100 controller installation, wiring and Commissioning information select here To review the DC1400 controller general data sheet, select here To review the DC1400 controller installation, wiring and Commissioning information select here

Issue The IC-GEN OPC server does not communicate with a third party OPC client across Ethernet. Environment Sigma IC-GEN OPC (all versions) Cause The IC-GEN OPC only supports a local IP address configured in the gateway.txt file. Resolution The IC-GEN OPC server can only be connected to third party OPC clients located on the same PC. For more information see Release Note, click here An example using an EIB I/O server, click here

Issue How can a schedule be added to a personnel records particular area? Environment Continuum 1.xx Cause Adding a schedule a one area in a personnel objects areas list. Resolution This link explains step by step how to add a schedule to a personnel objects area.

Issue How do you set up the VisiSat server for MicroNet or IAC controllers? Environment VisiSat server settings Cause Assistance for correct configuration. Resolution LIB-4-485 is a RS-232 to RS-485 converter to be used with VisiSat for communicating to MicroNet NCP Controllers or Satchnet controllers without the need for a MNMI or MIU respectively. The LIB-4-485 is powered from the communications port of your PC and no external power is required, providing the PC port adheres to the RS-232 specification (we have used successfully with Dell PC’s). The connection to the LAN are:-  TD (A) – To negative (-) communications terminal of controller. TD (B) – To positive (+) communications terminal of controller. GND – Screen connected at LIB card only and not at controller.   VisiSat requires the following settings to be configured in the VisiSat Server. The Server is found minimized next to the clock in the system tray. At the bottom right corner of your desktop, double click the server icon to show the VisiSat Server client. Select settings from the Network Menu Option. The Configure Network Settings window will be displayed as below. Select ‘Serial Port’ as the Transport type, and click the Configure button. 1. The configuration for use with MicroNet controllers needs to be as detailed below. 2. The configuration for use with IAC controllers needs to be as detailed below. Once the correct selection has been made click OK. VisiSat is then ready to use with selected controllers.   The VisiSat Engineering guide contains additional information regarding the VisiSat server Click here to download or view the VisiSat Engineering manual.  

Issue Instructions and programming example for using nviEmergCmd to control the damper on the Xenta 102-AX Environment Xenta 102-AX Menta Cause In some situations it is necessary to have the Xenta 102-AX damper open to 100% for smoke control, or other sequence of operations specific tasks. There are different emergency modes which all perform a different function. Resolution The damper position on the 102-AX can be controlled to 100% or to 0% by using the SNVT input nviEmergCmd. Please see the attached Menta file as a programming example. The enumeration breakdown and controller actions of nviEmergCmd are as follows: 0 = Emerg Normal - Normal operation of the controller without any emergency command. 1 = EmergPressurize  - 102-AX will control to its max cooling CFM setpoint. 2 = EmergDepressurize - 102-AX will control its damper to 0% and shut off all other outputs. 3 = EmergPurge - 102-AX will control the damper to 100% 4 = EmergShutdown - 102-AX will pause control on the damper and disable all other outputs. 5 = EmergNull - Null SNVT value NOTE: Any value change on nviEmergCmd will initiate a damper resynchronization. This will cause the controller to fully close its damper, fully close any floating control outputs, and disable any other hardwired outputs for their full stroke time (throttling range).

Issue Access denied pop up messages occur at the end of a Continuum or Webclient installation MFC error Environment Continuum Webclient Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause At the end of the Continuum or Webclient install an attempt is made to register a number of files and access is being denied. Resolution Reinstall Continuum or Webclient as a local Administrator with Anti Virus and any Firewalls disabled Download AccessDeniedReg.zip and follow the instructions in the RegInstructions.txt to run a batch file to register the files. Note: The workstation may require a reboot after running the batch file.

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

Issue TGML graphic do not work Graphics are displayed OK but no values are displayed (crossed out in red) Webstation ports usage No values in webstation Environment Vista Webstation Internet Explorer Cause When the graphic are working but no values are shown it most likely because webstation do not have access to create subscription with TACOS. The function Rendering cache are meant to handle this Subscription Rendering cache are a function that can be changed under "TAC Vista web setting" and it need to be associated with a user that have read write access to the system. Another reason for this issue, can be that the Windows user "ISUR" that is the one used when accessing Webstation ("Anonymous" in Windows terms) for some reason doesn't have the appropriate user rights on the PC Resolution [Option 1 - rendering cache user] For a normal installation you can reach the function by Start - program - Schneider Electric - Tac Vista webapplication (Depending on what version are installed) Click the tab "Performance" Add a  user that have read/write access in Tacos In TAC Vista Web Settings 5.1.8 this Rendering Cache and Security setting is under Graphics>TGML Viewer   [Option 2 - "Anonymous" access user (IUSR)] Open the IIS manager through Control Panel - Administrative tools Edit the properties for "Webstation" In directory security, define a local user on the PC with high user rights NOTE: Also make sure port 80 is open in firewalls/routers, since this port is used to transfer HTTP data. For HTTPS port 443 is used. See attached "Webstation port usage"

Issue When using the IC_LON Plug-in an error is reported indicating that the SNVT is not supported. Unknown SNVT Type:  92 Environment Sigma IC-LON Version 1.E Cause The Sigma IC3-LON corresponds with version 11 of the LONMARK Resource files. Not all SNVT types are supported. Resolution Not all SNVT types are supported, please confirm which SNVT’s are supported by viewing the IC3-LON release note.

Issue "Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681". Environment Continuum v1.74 SP2 NetController II Cause Trying to create new NetController II device object with a "Controller Type" of "9681". "A Guide to Version 1.74 Support for NetController II and ACX 57xx" states that there is only one NetController model, the CX 9680. Please ignore references to the 9681. Resolution Create the Netcontroller II as  a Controller Type "9680" as stated on page 15 in document number 30-3001-1001 "A Guide to Version 1.74 Support for NetController II and ACX 57xx".

Issue I/NET uses a different "large number" hexadecimal format to represent individual cards.  To convert to a Continuum system, these must be decoded into Facility Codes and Card Numbers. Product Line Andover Continuum, TAC INET Environment I/NET Seven Security converted to Continuum Cause Different representations of individuals in the two systems. Resolution Download the "ZIP" file here conversion Excel spreadsheet. Press the "Clear Values" button to zero out the inputs. Select the correct format between the four options: 26-Bit Wiegand 32-Bit Wiegand Format (CSI) 35-Bit Wiegand Format 37-Bit Wiegand Format Enter the hexadecimal value and the Facility Code and Card Number will populate automatically.

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network Cause A better understanding of the I/NET network architecture and communication components can help to avoid the need to troubleshoot issues later. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others including resistor termination. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN Wiring Specifications are available here as a PDF document. Selecting the link Network Definition CLAN SubLAN downloads and opens the pdf document shown below.

Issue How should I engineer my BACnet project? What are some of the pitfalls and what is best practice? What work can be done offline in the office prior to going to the jobsite and what has to be completed when online on site? Product Line Andover Continuum Environment Continuum BACnet systems Cause There are multiple ways to engineer a system. Often project timescales do not allow for all of the engineering to start after the system goes live on site.  Resolution Engineering Continuum BACnet Systems V5.pdf is designed to provide guidance for the Sales and engineering teams when designing a BACnet system. It details how to engineer some of project tasks offline and what must be done at the job site. Then a Hints and Tips section gives further assistance with links to other helpful articles.

Issue Controller repeatedly cold starting Environment V53 Processor Boards, Image 5s Cause The controller has been working satisfactorily for a period of several months and then begins to coldstart. Upon coldstarting only part of the pntfle.rec is taken and another coldstart is initiated. Resolution Check the controller with pocket terminal that the controller has the correct default gateway address (GW). If no gateway address is required then this should be set to 0.0.0.0. See PIB: 050803_3+Sigma+V53+Processor+Card+_+Initial+Set_up.pdf Download the latest image release 6a (for UNC632/496/596 and DNN) and switch the image so that it is the active version.