Building Automation Knowledge Base

Issue Is there a way to output the average of logged values contained within the I/A Series G3 history records? Environment I/A Series G3 Cause I/A Series G3 history tables contain records of values logged by the associated trend objects.  A BQL query must be used to read records from the table and perform a calculation to average the values. Resolution A program object that contains a BQL query can be used to read the records from a history table and calculate minimum, maximum, average, etc. The AX community module contains a BQL object (Trend Dynamic Analyzer) that can be assigned to a history ord and configured to a particular timeframe. A new trend with a specific number of records (rolling) can be queried by this object which in turn calculates the Count, Min, Max, Average, and Sum. The axCommunity module contains a library of useful objects for the Tridium Niagara AX platform created by AX programmers.  Download the axCommunity module from the following website - http://sourceforge.net/projects/niagaraaxcommun/. Note: Schneider Electric does not maintain and is not responsible for the content within the axCommunity module. The user should test and utilize at their discretion and risk. Copy the axCommunity.jar file into the Workbench platform (modules folder).  Install into the target platform as needed. Open the axCommunity palette and add a TrendDynamicAnalyzer object into the station. View the TrendDynamicAnalyzer property sheet and then assign the History using the History Ord Chooser. Connect an Interval Trigger if a time based refresh of the values is required. You may want to limit the values at the output if the values trended by the history can get out of range (e.g. initialization, etc.).

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 Services for assistance. Issue Require a method on how to apply individual setpoints in EBO when Users are granted access at a Security Expert  Door. Product Line EcoStruxure Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause An example of this would be to have room temperature setpoints, or other specific settings, be changed when specific Users are granted access to a room or area. One method on how to do this would be to create a separate Access Level and Access Level Output for each user. When the User with that Access Level is granted access the associated output will be enabled. Using the EWS integration, the states of these virtual outputs can then be monitored within EBO and action were taken when they change state. Resolution Perform the following steps to configure this: Create an Access Level for each User object. Create a virtual output for each User object. A virtual output is an output object that is not assigned to an output expanders physical outputs. You could create outputs on existing expanders above the maximum output channel that you will be using but it is recommended putting these virtual outputs on a completely different module address outside the range that will be used for any physical modules. Module address = 32 would be a recommended starting value. Steps would be: Under Programming | Outputs create three new outputs. Set Module Type to "Output (PX)" Set module address to "32" or greater. Set Module Output to "1", "2", "3", etc... Save the changes. For each of the Access Levels add the corresponding virtual output to the Access Levels Output tab. Access Level Outputs Ensure the Access Level has access to the Door(s) in question. Set the Time to Activate (seconds) in the Access Level | General tab to something appropriate such as 5s. The output will disable after this time period. Set the Reader Access Activates Output on the Access Level. Set Activate Access Level Output on the Reader Expander | Misc Options.    

Issue I have an I/NET Controller with a forgotten DCU password. How can I recover it? Product Line TAC INET Environment I/NET Seven Site Cause A DCU password was set on the I/NET Controller and has been forgotten. Resolution Send an email to your local support. Include a copy of the current save file for the controller in question. Support will advise you on the password. Recommendation: For future use, either remove any controller passwords or record them in a secure location where they can be retrieved easily.

Issue It is not possible to select a "Trend 10K3A1" Thermistor when configuring a central or onboard IO input point. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Automation Server (AS-P) Central IO Building operation Automation Server Bundled (AS-B) Onboard IO Cause The specific thermistor type is not available to be selected. Resolution Configure an input as a resistive Input with reliability level, electrical scale and engineering scale set to: Upper/Top: 0 Lower/Bottom: 587628 Then use a Function Block 10K3A1-Ohm-To-C sample program or Script program to convert from resistance to °C. NOTE Satchwell and Trend both use 10k3A1 Thermistors but the shunt resistance used within it will vary.

Issue How to program a BioScrypt V-Pass-2 (Biometric) Reader in I/NET Seven. Product Line Other, TAC INET Environment I/NET Seven BioScrypt V-PASS (MV1200) Cause Assistance with configuring the BioScrypt V-PASS reader with I/NET Seven Access Control. Resolution Biometric Reader Setup Using the Bioscrypt V-pass-2 Reader The reader is: Bioscrypt V-Pass FingerPrint Reader VPASS-2 Note: The Programming software to load fingerprints on the PC comes with the reader. For the actual wiring and programming of this reader see the linked "BioScryptSetup.PDF" BioScript Setup Wiring (pigtail) Wiegand 1 - Wiegand Out Data 0 3 - Wiegand Out Data 1 6 - Wiegand GND Power using separate 24V DC Power Supply 11 - Pwr GND 13 - Pwr IN 15 - Earth Ground BioScrypt V-Pass Reader Wiegand Setup Install BioScrypt Software (VeriAdmin) on PC and setup to communicate with reader. Go to Configure > Unit Parameters Click on Wiegand Tab Check Predefined Format Pick "Standard 26 bit" Under On Success Check Alt Site Code & Enter Arbitrary Value (usually 3 digits) RECORD VALUE this is the Site Code Under Wiegand I/O Check Enable Input Check Enable Output Select Always Output (regardless of Input Source) Enroll Individual in VeriAdmin Enroll Individual RECORD ID – this is Individual Number NOTES: The index number is to assigned to ID number to record each individual finger (0-9 is for all 10 fingerprints). I/NET will only be sent the ID number in the Wiegand String. Schedule does not matter. You have selected Always Output (regardless of Input Source). One will do all the door scheduling in I/NET. Enroll Individual in I/NET Create new Tenant called “BioReaders” If site is using Wiegand Card and NOT Large Numbers (Dipswitch 7 OFF) Enter Site Code (recorded from above) as the Tenant ID When enrolling the individual in the new tenant, use the ID recorded from above as the Individual Number and Decimal Card Number.   If site is using Wiegand Cards and Large Numbers (Dipswitch 7 ON) or if using Idiscs (set Dipswitch 7 ON for only DPUs with BioScrypt, even if they have Idisc also) Leave default Tenant Code. Use 26BHEXCAL.xls and enter Site Code and Individual ID recorded from above and it will generate the HEX Card Number. When enrolling the individual, enter the Hex Card Number as generated. I/NET Door Configuration Make sure door is setup as Wiegand 26 Configuration as Implemented DPU 7920 Door 08 was setup as BioScrypt V-Pass MV1200 Door 09 was setup for Idisc Door Lock was wired to both relays in series (so both had to be energized to unlock the door). Door 08 (BioScrypt) was given a schedule of 24/7 and assigned to all individuals in new tenant. Door 09 (Idisc) had the original schedule assigned to site personnel. This schedule is the one that will deny access according to schedule. Other Configurations This can be used as a single reader for the door (with schedules in I/NET) or as implemented above with any combination of reader compatible with I/NET.

Issue MPM rebooting with message in the log like: MASTER_MAN (id= 9) 361893.721> FAULT: core_watch.c:333; code:0; time:2017-02-13 15:34:25; Message:Task ID 38:Lua_User_PGs expired at 361886.5; Top Of Stack:0x000000F3 0x20D4BE7C 0x71B73B76 0x0000007A 0x00000000 0x60000013 0x60000013 0x00000000 0x2084D224 0x08080808 0x09090909 0x10101010 0x11111111 0x00000015 0x2006FD91 0x2006FD91 0x20D48D3C 0x20062159 0x00000000 0x00000000 0x20EE8248 0x20D48D3C 0x00000000 0x00000000 0x22D50000 0x00000000 0x20D1E8E4 0x000007D0 0x00000000 0x2084D238 0x00000000 0x00000000 ; Product Line EcoStruxure Building Expert Environment MPM Cause This is an error in one of the PG object (user written Lua script) possibly an infinite loop. Resolution Disable or delete 1 by 1 your Lua PG's to identify the PG with the issue.

Issue Configuring the Xenta 102-AX to accept a 4-20mA CO₂ sensor input on Universal Input 3. A negative value is required on the CO₂ offset value, but it is not possible to enter a negative value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX 4-20mA output CO₂ sensor Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input. The best option is to always buy a CO₂ sensor that is compatible. However, if 4-20mA CO₂ sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20mA CO₂ sensor with a 0-2000ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to CO₂ Sensor Wire a 250Ω resistor across U3 and M. This converts the 4-20mA signal to 1-5V. In Vista Workstation, navigate to the 102-AX > UnivIn3_Sense. Open SCPToffsetCO2. This value needs to be -500, but negative values cannot be entered. To get around this: Change Value to 0 Change Scaling > Offset to 500. This alters the display of the offset value. Click OK. Open SCPToffsetCO2 a second time. The value is still 0, but it is being displayed as 500, due to the scaling offset. Change the value to 0 (because of the offset, 0 represents -500). Click OK Open SCPTgain. Set multiplier to 2444 Set divisor to 1000 Click OK. This value comes from 2000 (range of sensor) + 500 (offset) / 1023 Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid). Also see Using a 0-10 volt CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 0-10 volt CO₂ sensor input on Universal Input 3.

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 Unable to reload entire database using "Send to Controller" option. The error "Not enough memory" is seen in Distribution View when trying to reload some objects. Product Line Andover Continuum Environment Continuum b3 Series Controllers i2 Series Controllers Cause Data is corrupt in controller Database or individual points such as Infinity Programs have become corrupt and are unable to be reloaded to the controller. Resolution Clear the database in the controller and retry a "Send to Controller" as follows: Open the Device object of the i2 or b3 controller. Go to the "Runtime" tab. Press the "Reset" button to reset the controller and clear its memory. Retry "Send to Controller".

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 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 Wants to know the correct termination specification for each different I/O modules and different IOU networks. Environment NC1 - CX9900, CX9940 NC2 - CX9680 IOU modules Cause Different type of terminations are required for different type of I/O modules (ACC-LON and FTT-10A) and different topologies (Bus topology, Free topology and Doubly terminated Bus topology). Resolution ACC-LON  requires two 120 ohm resistors at both ends of the bus. One between pin 1&2 of the I/O module on the NetController side and the other one between pin 1&2 of the I/O module at the last node of the bus. FTT-10A Free topology requires one 52.3 ohm resistor between pin 1&2 at any place on the bus. FTT-10A Doubly terminated bus topology requires two 105 ohm resistors.  One between pin 1&2 of the I/O module on the NetController side and the other one between pin 1&2 of the I/O module at the last node of the bus.

Issue After successfully downloading a Menta application directly through the serial connection, the pop-up window below is displayed:  tam32 No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network! Product Line TAC Vista Environment Directly connected Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The blueprint is also called an .NDB (network database) file.  It contains network information that allows the controller to communicate to other controllers or I/O modules.  When downloading a Menta application directly, this warning is displayed as a reminder that that necessary network information has not been included in the application-only download. Resolution If the controller is running stand-alone and no networked communication is required, then no further action is required.  The message is only a warning alerting the user to the fact that the NDB file has not been included in the download. If the controller needs network variables and I/O module communication, follow the direct download (most often done only for troubleshooting purposes) with a download from the front end Vista Workstation for classic networks Vista System Plug-In for LNS networks If no front end exists, but network communication is still required (most often for I/O modules), lonTool32 is a suitable work around for those rare instances.  See Using lontool32 to download a stand-alone controller.

Issue What OPC options does sigma support? Environment Sigma OPC DA AE ModBMS IC-GEN-OPC IC GEN OPC Cause Requested details Resolution There are two options available; 1. OPC Server:  ModBMS software available from Product Support London. This supports up to 5000 OPC DA tags and OPC AE events.  See release note for details 2. OPC Client:  IC GEN OPC software mimics a Sigma controller and is loaded onto the same PC as the OPC Server. This supports up to 1000 OPC DA tags only.  See datasheet for details.

Issue Suggested configuration for Xenta 121, STR-150 in single occupancy zones (Hotel Operation): Single setpoint display for ease of use for hotel guests Erasing setpoint offsets between guests automatically on transition from unoccupied to occupied Disable fan overrides Product Line TAC Vista Environment Hotel rooms Xenta 121, ZBuilder STR-150 Cause A hotel room is a unique application of the Xenta 121 and must be tailored to fit the temporary residents and be as easy to use and understand via an STR-150 as possible to reduce the amount of calls to the on-call maintenance department. Resolution The important thing to remember is that the Xenta 121 and STR-150 do not have duplex communication capabilities. Communication is one way from the stat to the controller. There is no capability for the controller to override/control the stat display. Because of this, it will be very important to standardize setpoints between the stat, the controller, and system-wide. Set Up the STR-150 Refer to the STR-150 User’s Manual for additional information. Push the fan and bypass buttons simultaneously for 2 seconds to enter P0. In P0, hold down the bypass button and push the fan button three times. The wrench symbol is lit when the STR-150 is in configuration mode. Parameter Function Value/Range Set Value P0 Software Version - - P1 °C or °F temperature display 1=°C, 2=°F 2 P2 Reference temperature (Reftemp) 15-30°C / 60-90°F 72 1 P3 Setpoint or room temp. as default 1=Setpt, 2=Room 1 P4 Timeout 5-90 seconds 10 P5 Fan settings 0= No fan 1= On/Off fan 2= Two-speed fan 3= Three-speed fan 0 2 P6 Room temperature and setpoint display resolution 0.1 or 0.5°C 0.2 or 1.0°F 0.2 P7 Max adjustable setpoint span above or below Reftemp (P2). ±0 - ±5°C ±0 - ±10°F 10 P8 Bypass button and occupancy indication When = 2, no bypass command is sent to the controller 1= Symbol on, off or flashing 2= Symbol always off 2 1 Reference temperature should equal the average of the Xenta 121 occupied heating and cooling setpoints. Assuming 70°F heating and 74°F cooling for this example. 2 There is no way to give only AUTO/ON override control to hotel guests, so fan override capabilities should be disabled. Wire STR-150 to Xenta 121 STR-150 Xenta 121 Mode 11 Y1 5 Data 12 X1 7 M 13 M 6 Set Up the Xenta 121 - ZBuilder Connected devices > Room unit Select STR-150 and Check the box for "Activate STR-150 reset offset function." Engineering TAC Xenta 120 Manual Chapter 9.1.2 states: There is a so-called hotel reset function for room unit STR-150. When activated, an 'old' offset value is not taken into account when going from Unoccupied to Occupied until the Offset is changed (probably by a new hotel guest). Control > Setpoints Center all control setpoints around reference temperature of the STR-150. In this example, the reference temperature is 72°F, so cooling and heating setpoints have been centered around that. Setpoint calculation mode is set to method A which preserves symmetry around a base setpoint, but since these setpoints are already symmetrical, that is not of great importance. Expose normalize setpoint is important for the hotel staff to see the same setpoint as the stat is displaying to the hotel guest. Operation STR-150 defaults to reference temperature as setpoint 72°F. Xenta 121 uses default setpoints. In cooling maintaining 74°F. If the stat is set to display setpoint by default, the customer will only see the setpoint and won't be aware of the 2-degree dead band offset. Hotel guest decides 72°F is too hot and lowers the setpoint on the stat to 70°F. Xenta 121 interprets this as a -2°F offset on setpoints and now maintains 68°F heating/72°F cooling. Guest checks out and the room is set to unoccupied. Stat continues to display 70°F but the larger unoccupied dead band actually controls to set default of 80°F for cooling. Next guest checks in and the room is set to occupied. Stat continues to display 70°F but the Xenta 121 has erased the offset from its calculation and maintains 74°F. Guest feels this is too warm and lowers the stat from 70°F to 69.8°F. A new offset of -2.2°F is sent to the Xenta 121 which now controls the cooling setpoint to 71.8°F. The guest believes they have lowered their setpoint by 0.2°F  but in reality have effectively lowered it 2.2°F. As soon as they make a change to the setpoint, they resume control of the offsets.

Issue Sigma server fails when a Data Import is initiated during a Sigma transition Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Sigma Building Operation Enterprise Server Cause Sigma server fails when an EBO data import is initiated. Resolution It is important that the Sigma Database is checked with the Doctor utility (found in SigmaX) before a Sigma transition into EBO is undertaken. Longtext - Longtext file contains 'mandarin' type characters - probably from previous BAS/Sigma upgrades. If the file contains these, then Longtext has probably not been used in the past or not used currently. Delete the file (located c:\sigma\data), it will self re-create. Shorttext - Shorttext contains an incorrectly formatted entry. Find entry and correct. To find, delete 1 -250, if it continues to fails, the entry in question will be in the range 251 to 500 and keep halving until the entry is found. Index A errors - index contains a looping segment, where the page references itself. Correct index as necessary using SigmaX - Doctor. Index A errors - page is referenced more than once, i.e. the index page can be opened via two (or more) routes. Correct Index as necessary using SigmaX - Doctor. Note: the Index should be checked with SigmaX before a transition. Object corruption - open object in Sigma, if it fails to open, then correct by whatever means that is required, Sigma server will fail at a point during the Data Import. Log Sets - Fail to import log sets. To find, in Sigma, locate the logset.rec in the c:\sigma\data\server...folder file, take a copy. In Sigma, delete 50% of the log sets and try the import again. If it fails, delete another 50% and repeat. Or if it succeeds, then the issue may lie in the 50% of log sets originally deleted, re-instate these using the copied logset.rec file and try again by deleting the other 50% and so forth.

Issue Niagara G3 (NiagaraAx) Open NiCS (Niagara Compatibility Statement) Environment Niagara G3 (NiagaraAx) Cause NiCS attributes: Niagara G3 (NiagaraAx) licenses has brandId="TAC". A station's ability to accept NiagaraAx data from another NiagaraAx station depends on the accept.station.in="*" field in its license. A station's ability to share NiagaraAx data with another NiagaraAx station depend on the accept.station.out="*" field in its license. A station's ability to allow a copy of WorkBench to connect to it and engineer the station depends on the accept.wb.in="*" field in its license. A copy of WorkBench's ability to connect to a NiagaraAx station to engineer it depends on the accept.wb.out="*" field in its license. (Where "*" is the brandId) 'Open' licenses may be required when there is a need to: Allow sharing of a station's NiagaraAx data to another station which has a different brandId in its license. Accept NiagaraAx data from another station which has a different brandId in its license. Allow a WorkBench connection from a copy of WorkBench that has a different brandId in its license. Allow a copy of WorkBench to connect to a station which has a different brandId in its license. Resolution Niagara G3 open NiCS licenses have the following: “accept.station.in="*”; “accept.station.out="*”and “accept.wb.in="*”and “accept.wb.out="*”. The "*" is a wildcard designation to allow all brandIds. You can specify new licenses to have open NiCS by selecting the 'Request open NiCS (Niagara Compatibility Statement)' checkbox in the I/A Series G3 license request forms. You will need to purchase the part IA-LIC-CHG for each existing Niagara G3 that needs to have an open NiCS. 

Issue Can the DUIC-5P-12V digital point card be used on a MNL-200? Product Line TAC IA Series Environment IA Series MNL-200 Cause Integration of multiple status inputs Resolution The DUIC-5P-12V will function with the MNL-200 controller.  Do not use the BACnet DUI_Application.  Use the WorkPlace Tech's DUI Expander object instead.  Also, remove the JP1 jumper on the DUIC-5P-12V board.

Issue Selecting the appropriate IO system on a Continuum Net Controller (NC1 or NC2) Product Line Andover Continuum Environment CX9900 CX9940 CX9680 Cause Controller configuration Resolution Continuum Net Controllers can support three different IO systems, ACC-LON, LonMark XDriver and the legacy LBus. Only one IO system can be selected, the controller must be re-started after the selection is made. The document Selecting IO system in Continuum NetController has instructions on selecting the desired IO system for the controller.

Issue This tool will help calculate the required M&B conversion coefficient for a given analog value in I/NET. Product Line TAC INET Environment All I/NET Controllers I/NET Resident Point Editor Cause Need to calculate an I/NET Conversion Coefficient (M&B) for a special sensor Resolution Click here to download an Excel spreadsheet that has several functions for calculating the correct M&B.