Building Automation Knowledge Base

Issue When air temperature falls to 30 degrees F, the output values calculated by the Enthalpy object are incorrect as compared to performing manual calculation verification or humidity measurement Environment IA Series MNL-800 controller WorkPlace Tech Tool (any version) Cause The Enthalpy object limits the allowed range of its input values so as to maintain the resolution of the values it calculates.  These range limits are set based on the temperatures typically encountered when calculating enthalpy for mixed air, return air and supply air needs in air handlers. Resolution The following limits are used when processing the Enthalpy object inputs: Dry Bulb Temperature:  32 to 120 Degrees F (0 to 48.9 Degrees C) Dewpoint Temperature: 32 to 120 Degrees F (0 to 48.9 Degrees C) Relative Humidity: 1 to 100% Barometric Pressure: 19.94 to 39.79 in-Hg (506.5 to 1010.7 mm-Hg) Input values outside the ranges listed will be processed as if they were clamped to the listed limit.  For example if the air temperature (dry bulb) was 26 degrees F, it will be processed as if the temperature were 32 degrees F.

Issue How to implement a simple Man Trap using PE Environment CyberStation CX9900 CX9680 ACX5740/20 Cause A mantrap is an access methodology with an entry door and an exit door. One door of the mantrap can not be opened until the opposite door has been closed. Mantraps are most often used to keep non-secure areas separated from secure areas and prevent unauthorized access. Resolution 'This program implements a Man Trap that allows one person at a time in the man trap. 'Once a person is in the man trap no access is allowed until the occupant leaves the 'man trap via the REX. 'The occupant is allowed to exit at either door but once they have activated the REX 'at one door they are required to leave via that door. 'If occupant stays in the trap longer than TrapMaxOccTime and alarm can be sent via ManTrapStuck 'TrapMaxOccTime and ManTrapStuck are InfinityNumeric objects in the controller. 'Program is Looping and AutoStart TRAP_READY: ManTrap_A DisRdrKpAccess = False ManTrap_B DisRdrKpAccess = False ManTrap_A OpenOnExitReqst = True ManTrap_B OpenOnExitReqst = True If ManTrap_A ValidAccess or ManTrap_B ValidAccess then Goto TRAP_OCCUPIED TRAP_OCCUPIED: ManTrap_A DisRdrKpAccess = True ManTrap_B DisRdrKpAccess = True If ManTrap_B ExitRequest then ManTrap_A OpenOnExitReqst = False Goto WAIT_EXIT_B Endif If ManTrap_A ExitRequest then ManTrap_B OpenOnExitReqst = False Goto WAIT_EXIT_A Endif WAIT_EXIT_A: If ManTrap_A DoorSwitch = Opened then Goto TRAP_READY If TS > TrapMaxOccTime then ManTrapStuck = On WAIT_EXIT_B: If ManTrap_B DoorSwitch = Opened then Goto TRAP_READY If TS > TrapMaxOccTime then ManTrapStuck = On 'Keep program from disabling due to run time errors E: If TS > 30 then Goto TRAP_READY

Issue Using a door keypad to enter command codes to carry out commands such as arm/disarm system, extend door unlock on jet way etc. Environment CX9900 with AC1Plus CX9680 with AC1Plus ACX5720 ACX5740 Cause Requirements Resolution Click here for a PDF document with instructions on how to configure the system to capture command codes using a keypad at a door.

Issue DC2000 series Optimiser / Compensator Controller requires resetting to default values due to exposure to electrical corruption. Product Line Field Devices Environment DC2000 series Optimiser / Compensator Controller installed to control Variable Temperature Mixing Valve, Boiler/s, Pumps etc. Cause DC2000 series Optimiser / Compensator Controller has been exposed to electrical corruption. Resolution DC2000 series Optimiser / Compensator Controller may be reset to default values as follows :-  Isolate power to Controller. Open Door of Controller. Locate PCB on rear of Controller Door. Locate pair of Steel Pins (marked PL1) on PCB. Link out pair of Steel Pins for 10 seconds approx. Remove Link. Close Door of Controller. Reinstate power to Controller. Re-programme Controller. Re-programming procedure for the DC2000 series Optimiser / Compensator Controller may be viewed here. Should the above reset to default values procedure fail to enable the DC2000 series Optimiser / Compensator Controller to be re-programmed then replacement of the Controller may need to be considered. POSSIBLE REPLACEMENT The most common control application to which theDC2000 series Optimiser / Compensator Controller may be applied comprises the following combination of inputs and outputs.  Outside Air Temperature Sensor Inside Air Temperature Sensor Compensated Heating Temperature Sensor Variable Temperature Heating Circuit Valve Actuator Boiler/s (2 maximum) H W S On/Off output (independent) Should such inputs and outputs be confirmed then the DC1100 Optimiser / Compensator may be installed in place of the DC2000 series Optimiser / Compensator Controller. Details of the DC1100 Optimiser / Compensator Controller may be viewed here. Drayton A7xx series Sensors connected to the DC2000 Optimiser / Compensator Controller are compatible with the DC1100 Optimiser / Compensator Controller and may therefore be retained. N.B. It should be noted that where a DC2000 series Optimiser / Compensator Controller is included in an installation of a more complex nature then an alternative solution utilizing different products may need to be considered In such installations not only will the DC2000 series Optimiser / Compensator Controller need to be replaced but its associated Sensors will also need to be replaced. Resolutions to such installations may best be determined following a review of the control system installed by a member of the local Schneider Electric

Issue When starting the station, an error message is displayed in the Application Director window reporting a series of javax.baja.sys errors.  The errors are of the format: javax.baja.sys.ModuleException: Cannot resolve dependency xxxxx-Tridium-3.y.zz -> xxxxxx-Tridium-3.a.bb javax.baja.sys.ModuleIncompatibleException: yyyyy-Tridium-3.y.zz Environment I/A Series G3 installation, any versions Cause The modules reported in the first exception line are incompatible with each other. Resolution This issue is usually caused by installing an incompatible version of one of the modules used by the ENS station.  Delete the folder \niagara\niagara-3.x.xx\sw folder (where 3.x.xx is the G3 release number) Reinstall the required 3.x.xx version of the G3 software. Copy any additional required modules to the modules folder. Open the workbench and run the Software Manager to rebuild the "sw" folder. Restart the ENS station.

Issue Reloading a BCX4040 causes it to appear offline. Environment bCX4040 Cause After a reload, a bCX is offline.  Resolution Dump bCX to text file. Delete bCX from CyberStation. Clear database backup via controller webpage. Add back the bCX in CyberStation and performed a Teach. In global BACnet Preferences (Cyber icon in Windows tray), add BBMD information and run Teach in the BBMD Registration editor.  Import the dump file from Step 1. Perform a successful reload.

Issue AC256 Master controller repeatedly displays Test Mode. Environment AC256+ AC8+ Cause LED card is not plugged into the CIU board. Resolution In order for an AC256 Plus master controller to pass its system startup test, the indicator light panel must be plugged into the CIU board.

Issue Where is the information on LVIS Display/Screen Environment Lon Bacnet Loytec LVIS L-VIS L-VIS Touch Panel for BACnet networks   Cause Information on Loytec L-VIS Resolution The L-VIS from Loytec uses bacnet MSTP or LON. See Product Announcement - LonWorks and BACnet Touch Panels release for more information. All support for this product is via Loytec

Issue Unless the correct format is used when defining a dongle as locking property in https://schneider-electric.flexnetoperations.com web site when activating license, the license will not work. Product Line TAC Vista Environment Vista 5.x Cause Defining a dongle as locking property in schneider-electric.flexnetoperations.com web site when activating license. Resolution It is important that the format is entered in the following format: TAC_HL_ID=1234567890. If the "TAC_HL_ID=" part is not entered, it will not work, and you will need to rehost the licenses again, this time using the correct format as stated above. Complete instructions can be found in Rehosting a Vista 5 License on the FlexNet License Server.

Issue No events in Vista No events in SQL $Queue grows in size Product Line TAC Vista Environment Vista DSSWriterService SQL Database Cause DSSWriterService is responsible to transfer log data and event's from TAC Vista queues into the SQL Database, it is crucial that this process has enough authority else no logs or events will be written. Resolution To change the user that handles DSSWriterService: Click on Start - Settings - Control Panel Open Administrative Tool and execute Services In the list to the right, (Services), locate TAC DSS Writer Services Right-click the TAC DSS Writer Services and choose properties Click on tab Log On Use Local System account or under "This account" specify a user with the correct authority Restart the Service and check the $queue folder. If folder insertevents and insertlogvalues are empty or just have a few files that are being removed the DSS Writer is working and has a connection with SQL. NOTE: After Vista 5.1.7 the Queue folders have been reworked and there are additional folders under insertevents and insertlogvalues. You will have to navigate under them to find the Event/log files.

Issue There are a few different stem heaters to choose from. Product Line Field Devices Environment 8800108000 8800109000 8800110000 8800112000 Stem heater Yoke heater Cause Depending on application, there are a few different stem (yoke) heaters to choose between for the Forta actuators. Resolution When Forta series actuator is used with a Venta valve, stem heater part no 8800108000 should be used when media temp is 0°C to -20°C. Note: This stem heater is not compatible with the M700 actuator.  If used with V321 DN65-100, stem heater 8800110000 should be used. If used with V222 DN65-100, stem heater 8800112000 should be used. In other applications, yoke heater part no 8800109000 for Forta should be used. Capacity for the yoke heater is: Ambient temp  down to -10°C or media temp down to -8°C  For more on stem heaters, see Stem heater for V222/V292.

Issue What is required to configure controllers to use the wireless network adaptors? Environment Wireless Infinet CX 9680 (Netcontroller II) bCX 9640 (bCX1-INF) i2xxx controllers Wireless MSTP bCX 4040 (bCX1-BACnet) b3xxx controllers Cause Require more information on how to enable Continuum controller subnet to use wireless communications instead of wired communications. Resolution To setup and enable wireless Infinet or MSTP networks, you will require two things: 1. Firmware There is separate Wireless Firmware that needs to be loaded into the i2xxx and b3xxx controllers to enable wireless communications. The Netcontroller II or bCX1 controller do not have a separate wireless version of the Firmware. FW -> Ecobuildings   2. Wireless Adapters You will need to attach wireless adapters to each controller including the master and change the commport to wireless mode. (Note: bCX or NC2 controllers only; wireless has not been enabled in the ACX57xx controllers at this time.) For further information see the Wireless documentation at the link on ExchangeOnline below. Ecobuildings

Issue MSDE to Full SQL Product Line TAC INET Environment I/NET Seven site Cause Need to Move db from MSDE to Full SQL Resolution Below are the steps to move from your MSDE to a full SQL instance: Make sure your version of I/NET supports Full SQL (check ReadMeSeven.txt file located on the Install CD) Backup all controllers (HVAC and Security) to database Backup MSDE database using DBCreate (Start, Programs, I/NET, DbCreate Utility) If running I/NET as a service, unregserver to stop the service (Running I/NET Seven as a service on Windows) If applicable, demote Equalized Clients(EQ) to StandAlone then demote FileMaster(FM) to Standalone Using Microsoft SQL Management Studio Express create an instance database for INETSeven which I have explained how to do in step 7 In SQL Management Studio Express right click on Databases and select New Database and be sure to name specifically INETdb Using I/NET DbCreate Utility when the login screen appears, connect to the SQL Server (Computer Name Required) you want to use which has full SQL Create a blank I/NET SQL database with proper login credentials Still from DBCreate Utility, restore the database from previous step which is a good backup Re-install I/NET over the top of the existing install so that the StandAlone will use this instance of SQL Have the proper security key information When the install gets to the SQL, select the instance from the SQL database created in step 9 Complete the installation Suggested reboot if necessary and start I/NET Restore SAV files (which is the database, see How to upgrade bin and SAV files in I/NET controllers) to the controllers in the I/NET network so everything is in sync with the db

Issue How can I create a list view that will show only user activity where the user has deleted an object from the database? Environment CyberStation ListView Action Code Cause Need to research what items have been deleted from Continuum by others. Resolution Create a listview. On the General Tab configure the fields as follows. Class: Activity Event Filter: Today Path Type: AllPaths On the Columns Tab add the following columns TimeStamp UserName NodeName EventObjectId Description Action Code On the Qualifier Tab use the Query Wizard to configure the following attribute filter. Attribute: Action Code Operator: Is Value: 2

Issue Device Template for trane Uc800 Product Line TAC Vista Environment Xbuilder Xenta Server MODBUS Cause Device Template Required Resolution Here is a MODBUS device Template for a TRANE UC800

Issue When running a listview on the alarm log it appears there are instances where the alarm was acknowledged before the timestamp. How can this happen? Product Line Andover Continuum Environment Time Sync Cause This issue can occur if  the Continuum system is not properly time synchronized. In order to properly sync the system time, it's helpful to understand where the various alarm time attributes are set: TimeStamp comes from the controller's time TimeofLog comes from the SQL Server's time TimeofAck comes from the Acknowledging CyberStation's time Resolution Make sure all the components of the system are properly time synchronized. Methods of synchronizing server and workstation times may vary based on the workstation operating system and if your network is using active directory. Refer to the network administrator to verify if time sync is being done, and under what conditions (logon only and/or a schedule) and how often. If Continuum is on an isolated network refer to http://support.microsoft.com and search on network time synchronization to learn about the different options for the particular network configuration. As for the workstation-to-controller time sync, Time sync controllers to workstations includes a program to which will sync the workstation time to the controllers. TimeOfLog and TimeStamp columns in an Alarm or AccessEvent listview are different covers a couple of conditions where the TimeStamp and TimeofLog may vary considerably. Periodically, verify that all the components are in sync.

Issue Vista only supports EXCEL reports. Environment Vista 4 and 5 Cause Vista reports only supports EXCEL format as a standard installation. Resolution A PDF printer can be installed and set to auto save as a PDF file. Vista can then print the report to the PDF printer which will save the file as a PDF. To set this up you need to first install the PDF printer. PDFCreator is one printer option that can be set to auto save functionality. Here is a link to download this software. http://www.pdfforge.org/ Once installed you configure the auto save option Then in Vista setup the report to print to the PDFCreator The setup the Report Periodical to print the report This will then save the report as a PDF in the folder defined in the PDFCreator setup.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue The list of visitors has become very large on the VMS front page Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause By default, visitor users are not deleted automatically from the system Resolution 1. In The Security Expert client, go to Visitor | Template | General Tab. Select the template you want to edit. 2. Scroll down and expand the Configuration section. In the Checkout mode, select 'delete user'. 3. Click Save.

Issue UNC station is frequently rebooting on its own and occasionally reports "Station Watchdog Timeout" in the error log. Environment I/A Series UNC 510 or UNC-520 Cause System Monitor task is causing the UNC to reboot. Typically this is caused by incorrect information in the drivers.properties file of the UNC. Resolution This issue can be corrected by editing the drivers.properties file in the UNC. To edit this file, Log into the UNC using the Admin tool. Select the Installation tab the select [Edit drivers.properties].  The file will be displayed in the text editor. Look for a line that reads sysmon.enable=true If the line is present, edit the line changing so that it reads sysmon.enable=false If the line is NOT present, add the line sysmon.enable=false at the end of the file. Select Save from the File menu to save the changes. Select Close from the File menu to close the editor. After editing the file, the station must be restarted to allow the change to take effect.

Issue Transfer SNVT (network variables) between lon devices in a TAC Vista Classic scenario. Can't bind in classic network; how to send SNVTs from one lon device to another? Environment TAC Vista Classic scenario LonWorks devices Cause If you are using TAC Vista in a classic scenario, no real SNVT bindings can be made. Resolution Use object transfer to send the values. Note that the server have to be running for the values to be transferred. For more info on how to set up object transfer, see Chapter 14 in the TAC Vista Technical Manual.