Building Automation Knowledge Base

Issue Endura DVR missing the Video in I/NET Seven Rev 2.41 Product Line Pelco, TAC INET Environment I/NET Seven rev 2.41 Endura DVR Cause The Endura Workstation software that comes with the DVR (by default) is set to "Multicast". If this has not been changed, then you DO NOT have to change the three I/Net files listed below. If the Endura Workstation software was changed from the default (Multicast) setting to a "Unicast" setting. Then you WILL have to change the three I/Net files listed below. What is the Pelco definition of “Multicast” mode? By default, Endura encoders and Pelco network IP cameras are default to stream live video in Multicast mode. A common symptom of multicast routing issue is where the date and time stamp can be seen on the workspace but the video is black. This symptom is commonly associated in a layer 3 routing network where appropriate multicast routing protocol has not been enabled globally or inside the VLAN. Resolution The resolution is to modify three files that are installed with I/NET Seven rev 2.41. These three files are located in this directory on the PC – C:\Program Files\INet Seven INetAMT.exe.config INetCfg.exe.config INetW.exe.config Note: If the above three files are not in the I/Net folder, then you have not delete the previous SDK driver. You must delete the previous driver thru the "Add and Remove" option in Control Panel. Once removed then go into the I/Net CD and select the "Support" folder and manually load the new SDK Driver. Then proceed with the rest of the process in this article. Use Notepad to open each one of these files one at a time and change this setting from the "default" of "False" to "True." After making all of the changes in the three file, shut down the I/NET and IO Server ICON. Restart the I/NET again, and the Video should show up in the I/NET program

Issue How to create Elevator Access and Floor Override on Version 3 Product Line EcoStruxure Access Expert Environment Access Expert Applet Win 10 and above Cause There is no help or direction on how to perform this task. Resolution In order to do Elevator Controls, here is a link below to a video as well as some screen shots for clarification: Firstly there needs to have a Schedule, Access Level and Elevator Access created based on the application as seen on the screen shots Schedules Access Levels Elevator Access Elevator Reader Settings Elevator Floor Settings Floor Override Settings  

Issue Sporadic values in Vista or Vista Graphics show up as red X or "Invalid Value" Product Line TAC Vista Environment Vista Workstation Classic Environment Cause Vista is designed to only have one instance of Vista Server running per system.  If two Vista Servers are polling the same equipment, data will not be read correctly. Resolution Configure all machines as a Remote Workstation with the instructions below. The remote Workstation will be networked to the Vista Server you would like to remotely view. To allow for correct communication DCOM setting will also need to be set. See Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for the utility to complete this process. Shut down all Vista programs, including Vista Server Start Vista Workstation You will see this log in screen: Click on "Options" to display this screen Change "[Local Server]" to the IP address of the machine with Vista Server running Enter your username and password and select OK 

Issue A license is needed for using the Roam IO2 with ethernet Product Line Andover Continuum Environment Roam IO2 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause A license is required to use the ethernet feature with the Roam IO2 Resolution Follow the instructions for Generating a License request in the BACnet Service Tool Generating a License manual, (PDF attached). Include your contact information, PO (purchase order) and RA numbers for the RoamIO2. Send that information to Upgrades.Continuum@schneider-electric.com to process the request.

Issue How to configure Global I/O across controllers in Access Expert Product Line Access Expert Environment Access Expert Win 8.1 and above Version 3 Cause There are no guidelines on how to control points across controllers on a Version 3 instance. Resolution Setting up Global I/O utilizes Alarm Definitions and behaves similarly to Triggers and Procedures. The event source of the Alarm Definition is the Trigger for the action. The Alarm Action will act as the Procedure that occurs after the trigger has been activated. Example: In the example below, when the input on controller 1 is activated, the output on controller 2 will be pulsed. The Alarm Action of pulsing the output is set up on the Alarm Actions page and uses a Trigger and Procedure to Execute the pulsing of the output. If you are attempting to do Global I/O in Version 2, this feature is not supported. It will only work in Version 3. For this example, we are pulsing the output on Controller 2 from input on Controller 1 for a duration and we need two triggers to accomplish it. The following steps will describe how to configure them:    Step 1: Create a Trigger and Procedure for the Input on the first controller and assign the source accordingly.   Step 2. Create the Second Trigger on the Second Controller. Step 3: Create an Alarm Action to Execute this procedure and assign it accordingly. Step 4: Create the Alarm Definition. The Event Source is the object that will do the “Trigger”, the Alarm Action is the “Procedure” and the Event type is the triggering action for the Source. In this example, the filter query is setting this action to only occur when the input is activated instead of any input status change. 5. Trigger the Alarm and look at Hardware Status and Live Monitoring Window.

Issue 3:15am Time Sync error in AMT Product Line TAC INET Environment I/NET site with DCU Time Sync enabled Daylight Savings Time Cause Outdated SAV file No DST observed Enabled DCU Time Sync from Host PC Resolution Make sure versions of Bin Files are up to date with current revision of I/NET across all controllers. For how to do this read How to upgrade bin and SAV files in I/NET controllers.  Make sure SAV files are backed up and current. For how to do this read How to upgrade bin and SAV files in I/NET controllers. As the host workstation synchronizes the daylight savings time settings in a controller, it will also check for the existence of a corresponding SAV file. If a SAV file for the controller is found, the host workstation processes it as follows SAV file is current If the controller's SAV file is current, the host automatically updates it with the daylight savings settings from this editor. This ensures that if you later restore the controller using this SAV file, the correct daylight savings time settings will be downloaded. SAV file is old If the controller's SAV file is out-of-date, the host does not change it. In this case, you can manually update the controller's SAV file or use the Automatic DCU Save function in order to create an up-to-date SAV file for the controller. Refer to Station Save and Restore for more information.  Beginning with I/NET revision 2.41, I/NET allows the DCU Time Sync and no observance of DST.  Work around is to remove DCU Time Sync if your time zone does not observe DST.

Issue Both comm ports can be enabled for RTU, but is this a recommended configuration? Product Line Andover Continuum Environment Continuum 9900 9940 9680 9640 5740 5720 Xdriver Cause 2 port can be enabled for RTU Xdriver on a netcontroller, but is this a recommended configuration or will this be too much of a strain on the Controller? Resolution According to the Xdriver developers, it is NOT advisable to use 2 Modbus RTU Xdrivers on the same Controller  The Modbus RTU Xdriver is the only 'poll on demand' type xdriver and this dual configuration has the potential of holding the CPU for longer and could cause the polling to become irregular. It is recommended to add an additional Controller to handle the additional devices and points required. Also see BCX Controller can use Comm 1, Comm2, or both ports for Modbus RTU X-Driver Can two comm ports be enabled when using the RTU Xdriver?

Issue The card reader beeps continually when connected to the door controller with the Sounder cable connected. Product Line TAC INET Environment I/NET Cause There may be several causes for this situation: The door which this reader belongs to isn't configured. The polarity setting of the reader beeper isn't correct. This reader port is damaged due to certain cause. Resolution The following steps need to be followed: For cause 1, configure the door and reader in Door parameter. For cause 2, click "Sounder" button in the Door parameter window and change the "Polarity" setting correctly. Usually change from "High" to "Low". For cause 3, send the door controller to repair. For how to set up a beeper in I/NET, refer to How to use the Beeper of the Card Reader in I/NET.

Issue Recommended method for replacing an MR-VAV-AX controller. Where to get ASC Parameters for the new device. Environment I/NET software all versions MR-VAV-AX controller Cause An MR-VAV-AX needs to be replaced on an existing VAV box. Resolution The ideal way to change an MR-VAV-AX or similar would be to use an airflow hood to calibrate when the device must be changed. However, if no airflow hood is available, see the options below: Obtain the ASC parameters of the existing MR before removing the device from service. Re-use the original settings. If these values cannot be recovered, then ask the customer for the original drawings or T&B reports on the device in an effort to properly establish correct duct diameter and total airflow. Rarely is this information readily available at the time of the change. Without such info, an estimation will have to be made. A rule of thumb is: 250 CFM per diffuser and an eyeball estimate of the duct diameter The pickup factor is left at factory default (3) or compared to other similar devices and an average of other pickup factors is used. For setting CHF, base it on the above estimate of 250 CFM per diffuser and make sure that the box just reaches 100% damper at the maximum airflow it is physically capable of at the AHU's normal static CLF is an estimate based on the use of the space and the temperature needs of the occupants. CLF is about 10% of the CHF.

Issue This is a guideline to do air balance settings (airflow calibration) on a VAV ASC using a I/STAT or M/STAT. Product Line TAC INET Environment MR-VAV-AX MR-VAV-X1 MR-VAV-X2 Cause The air balance company needs a procedure to properly set up the MR-VAV-AX products for the air balance settings. Resolution Understand the cooling setpoint is 75°F, and the heating setpoint is 70°F. This information is important in knowing which state the system is trying to control. While in the PP mode of the I/STAT, it is important to verify the setpoint is 75°F. This allows Test & Balance to set the temperature to: 77°F for maximum cooling 72°F for minimum cooling with no fan 68°F for heating mode - minimum primary airflow with fan To verify the current setpoint, use the Select key and scroll up to Set Temp. The I/STAT will display the current setpoint. For testing purposes as described in Step 1, if the temperature setpoint is not 75°F, press the + or - key to raise or lower the setpoint to 75°F. In order to enter the Service Mode, press the Service key. Enter the I/STAT password 183. Press the + or - key to see the left most digit change accordingly. Press the + key to scroll to 1 and press Enter. The cursor on the I/STAT will move to the center digit. Press the - key to 8 and press Enter. Now the cursor will move to the right most digit. Press the + key to 3 and press Enter. You are now in the Service Mode. While in the Service Mode, the Service key is the escape key and the Enter key will allow the controller to accept your desired changes. The first step in the calibration process is to make sure the controller is at the Factory Calibration Setting (FCS). Press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press the Select keys to scroll to FCS, press Enter. The I/STAT will display NO. Press the + key to change the display to YES and press Enter. Press the Service key to back up one screen. To verify duct diameter (dd) press the Select key and scroll to Unit Parameters (UP). The I/STAT will display the current duct diameter as 10.0 (default of 10 inches) unless the value has already been changed. Press the + or - key to raise or lower the value, and the Select keys to move between the right most and center digit. Sample: 8 inch box is displayed as "08.0" Press the Enter key to allow the changes to take place. Press the Service key to back up one screen. To verify Cooling Low Flow (CLF) and Cooling High Flow (CHF) setpoints, press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press Enter, the I/STAT will display the current value. Note that CFM is displayed as KCFM, for example 0.50 = 500 CFM. If the values are correct, press Enter. If the values need to be changed, use the + and - keys to change the values and the Select keys to move the cursor from the left most digit to the right most digit. Once you have the desired value displayed, press Enter. The I/STAT is now displaying CLF. Press the Select keys to scroll to CHF and press Enter. If the values are correct, press Enter. If the values need to be changed, use the +, -, and Select keys to change the CHF to the desired value then press Enter. CHF is displayed on the I/STAT. Press the Select keys to scroll down to Calibrate Primary Low (CPL), press Enter. The VAV controller will modulate the damper to maintain its design CLF. The I/STAT is currently displaying the CFM the controller is reading. Note that during this process, the CFM value may go to -0.1, 0.0, etc.; the controller is calibrating itself to the 100% actual closed position. Once the CFM comes within 10% of the CLF setpoint, the ON/OFF LED will turn on. While the LED is on, the controller is not modulating the damper and the controller has the damper in a fixed position for approximately 60 to 90 seconds. (Do not attempt to enter any values at this point. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CLF.) Once the airflow has stabilized and the I/STAT is displaying the CLF CFM, measure the airflow and input the actual value (do this as soon as possible because once the + or - key has been pressed, it freezes the damper into a fixed position to allow enough time to enter the actual value and to minimize chances of the actual CFM changing), into the I/STAT using the +, -, Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT will display Calibrate Primary High (CPH), press Enter. The VAV controller will modulate the damper to maintain its design CHF. Again, once the CFM comes within 10% of the CHF setpoint the controller's ON/OFF LED will come on and the controller will perform as described in Step 9. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CHF. Once the airflow has stabilized and the I/STAT is displaying the CHF CFM, measure the airflow and input the actual value (again, do this as soon as possible) into the I/STAT using the +, -, and Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT should be displaying CLF. Once the low and highs have been calibrated, press the Service key. Press the Select key to scroll to Operational Parameters (oP), press Enter. Press the Select key again to scroll to Prove Performance (PP). This mode will place the program's Room Temperature in a test state. The I/STAT display will toggle between the current CFM and the room temperature. This step will allow the balance engineer to verify proper operation of the VAV controller to maintain the design maximum and minimum airflow. Press the + and - keys to increase or decrease the room temperature in order to manipulate the system to control between cooling and heating as described in Step 1. Once the VAV has controlled the damper to design minimum CFM, the balance engineer can adjust the fan (if applicable) to design airflow. Important: If at any time during the calibration process, (not during Prove Performance (PP)) a mistake is made, make sure that the controller is reset back to the Factory Calibrated Settings (FCS), (see Step 4) and restart the calibration process. Also, if the VAV box does not control the CFM within the maximum allowable percentage, normally within 10%, go back to Step 4 and restart the calibration process. For further information see the following: TCON126 (Micro Regulator Controllers and I/STAT) TCON147 (ASC MR-VAV-AX) TCON155 (ASC MR-VAV-X1) TCON165 (ASC MR-VAV-X2) Go to TCON Number and Title Cross Reference (with links) and download the TCONS above.

Issue When a NCII 9680 starts up what determines which mode is used, as it does not have an ACCRestartMode system variable as per the bCX1. Environment Netcontroller II CX9680 NC2, NCII Cause Clarification of the way a Netcontroller II starts up is required. Resolution It is only the BACnet bCX1 controllers that allow you to manually set the ACCRestartMode. The NCII however still can do the 3 different start up modes (Warm, Cool or Cold) but it will depend on the situation. When the controller powers up it will try to do a warm start, if the battery is plugged in (it is shipped disconnected) and the internal RAM checksum is valid it will continue the programs from where they were prior to power fail. Also all data and logging will be retained. If the RAM is not valid the controller attempts a Cool start, if you have a valid Flash backup (see Sys Var' ACCStatusBackup) then it will copy over the data from Flash to RAM and all Auto start programs will start up from their first line. If there is no valid RAM or Flash backup the controller will be empty and do a cold start.

Issue VisiSat 2.1 Build 185/196 Cannot find VisiSat “CustomiseUI” add-on to Visio. Environment Internal error 0x86DB08A9 VisiSat CustomiseUI Visio VisiSat 2.1 Build 185 VisiSat 2.1 Build 196 Cause Visio 2003 does not recognise or register VisiSat 2.1 Build 185/196 installation CustomiseUI. Some or all the files required by VisiSat are missing. You may need to re-install Visio and/or VisiSat to clear the problem. Resolution When VisiSat 2.1 Build 185/196 on some Windows XP pro / Visio 2003 computers the following error is displayed. Carry out the following; which should fix the problem. Open Visio 2003 (Not VisiSat) On the menu bar, under tools select options. Select the advance tab. Select file paths. Delete all entries. Then select OK Select OK. OK the next window Visio 2003 should now close. Run up VisiSat VisiSat should run up OK now. If you close VisiSat and open Visio 2003 the paths should now show. VisiSat should open correctly now. Options: Most of the enhancements in VisiSat 2.1 build 185/196 are to incorporate StruxureWare functionality. If you are running VisiSat on Windows XP with Visio 2003, then consideration could be given to using VisiSat 2.1 build 148 instead. If you are running on Windows 7 you could consider upgrading the Visio 2003 software to Visio 2007 or Visio 2010. Click here to download VisiSat 2.1 Build 148. (Direct link) (files size is 42 meg). (your original VisiSat registration form (version 2.0/2.1 only), provides proof of purchase and will be required when unlocking this VisiSat version. If you require further assistance, please contact Product Support.

Issue Using the correct URL to launch webclient and there is only white space Product Line Andover Continuum Environment Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause ActiveX controls were not installed from the Server onto the browser PC. Certain versions of browser (IE8) disable unsigned activex controls which we use for webclient Resolution It is possible that if this is happening on a domain that there is a group policy in place restricting access. Try the browser on the webClient PC or a laptop directly connected to the webClient PC. Check the compatibility matrix to see if the version of your browsers are supported with that version of webClient. Ensure the Activex controls were installed Turn Off Pop-up blocker.  Internet Explorer> Tools>Turn Off Pop-up blocker Internet Explorer> Tools> Internet Options> Security> Select the correct Zone (i.e. Internet, Local, trusted). Click Custom Level button Select Enable for Automatic prompting for ActiveX controls Select Enable or Prompt for Download signed ActiveX controls Select Enable or Prompt for Download unsigned ActiveX controls Click OK, OK Close Internet Explorer and try again. If it is still not working, clear the cache (http://support.microsoft.com/kb/260897) and try again. If the PC is 64 bit and the webclient version is not 1.94 and above, that could also cause this. In extreme cases removing and reinstalling .net, IIS and webclient may be necessary. Verify that the version of SQL Server is compliant with the version of Continuum that is being used. Ex. SQL Server 2000 with SP3 (instead of SP4) isn't compatible with webclient 1.93 Check Removal of MS KB2858725 Dot Net 4.5.1 causes issues with Web Servers IIS Functions related to .Net 4.5 Reinstall webclient Lastly, a reformat of the hard drive an complete reinstall. Note: If the white space happens in just the personnel area and this is 1.74 remove .net version greater than version 2 In IE 9 and IE10 use compatibility mode IE11 is not currently not supported in a 1.94 SP1 ** Webclient 2.0 new alarmview is blocked by IE setting "Block pop-ups" ** If you receive "Internet Explorer blocked a popup from webClient IIS" after logging into webclient then turn of the pop-up blocker for this or all sites. Open Internet Explorer > Tools > Pop-up Blocker > Turn off Pop-up Blocker

Issue When closing Continuum 1.9x SU (SQL 2005 Express engine on a stand alone workstation),  it shows MFC error message of ACCDataServices and the Windows Event Log shows AlmUtil.dll error message. Environment Continuum SU 1.82 and higher version. Cause There are 3 Windows Schedule Tasks which are created during the DBInitialization->Creation of the Continuum SU workstation. Some possible causes are: If these Schedule Tasks are missing The Windows Schedule Tasks cannot be executed due to that fact that the current login userID is different than the one setup for the Schedule Tasks The password is not correct Resolution Manually create these 3 Schedule Tasks in the SU Cyberstation Alternatively: Uninstall SQL engine, Continuum Reboot the Workstation Reinstall Continuum SU, create a new DB from DB Initialization. Verify these 3 Schedule Tasks are created as below: CS_Distn CS_hrly CS_Minute

Issue Replacement stuffing box for valve V222 Environment V222: 721-2254-000 DN65 721-2258-000 DN80 721-2262-000 DN100 721-2266-000 DN125 721-2270-000 DN150 Gland Service kit (Packing box, Stuffing box): DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0 Cause Replacement parts for gland service Resolution Replacement gland service kits for V222: DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0

Issue How to delay the intrinsic controller status alarms to accommodate controllers that are sporadically going offline for short periods of time due to known network problems. Environment Continuum BACnet Controllers bCX1 b3xxx Cause Need to delay controller offline messages to accommodate slow network communications or remote controllers. Resolution The intrinsic alarm for the controller status will trigger when the controller does not respond to communications from the within the probe time and would not be suitable for this delay. The only way to delay a controller offline alarm for an amount of time after the controller goes offline, is to monitor the controller offline status from the workstation with a program, toggle a variable that then has an AlarmEnrollment attached. This AlarmEnrollment would then have a Time Delay configured. See the attached sample screenshot below showing the program in the Workstation, the AlarmEnrollment, and the Active Alarm View showing the time delay between the intrinsic alarm and the new AlarmEnrollment with a delay configured. Example

Issue To assist locating data sheets if you do not have access to the Schneider Electric Buildings Business Extranet and other company storage areas. Product Line Satchwell MicroNet Environment Unifact Pro Data sheet NCP Palm Cause To assist customers that do not have access to our internet or partner websites Resolution Click here to download the MLi for the Unifact Pro Controller. Click here to download the data sheets for Unifact Pro Controller. Click here to download the NCP Palm Engineering Guide.

Issue When Continuum Explorer is launched it takes a very long time to update.  Product Line Andover Continuum Environment CyberStation WebClient Continuum Explorer Cause When Continuum Explorer is launched it must populate all objects that reside at the root.  When there are a very large number of Personnel objects or other object types in the root, Continuum Explorer will be slow or unresponsive until this population process is complete. Resolution Create a Folder under the Root of Continuum Explorer and move personnel objects to this folder. Consider doing this to other objects that exist in large numbers.

Issue Script programs in b3 controllers will not autostart after reboot of the controller Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation AS-B Cause The program is not configured to autostart in StruxureWare Building Operation. Resolution In the Properties of the program object, ensure that the Autostart field is set to True. For further information on these properties please refer to Webhelp

Issue What is the best method for calibrating a thermistor? Product Line Andover Continuum Environment All CX controller All i2 devices All b3 devices Input Temperature sensors Thermistors Cause There is no documentation that details how to calibrate a Continuum sensor. Resolution There is no requirement to calibrate a Continuum Thermistor sensor, Thermistors are factory trimmed to provide an accurate temperature / resistance curve to within the tolerances defined in the datasheet. One exception to this could be if the connecting cable was of excessive length to add additional impedance to the circuit, in this situation the input point conversion line could be used to subtract an offset: Enter "ElecValue - x" where x is a factor to compensate for the cable impedance. See How to add an offset to a sensor reading for further information