Building Automation Knowledge Base

Issue Where can I get information and documents on the Building Analytics service? Environment Building Analytics Cause Information and documentation is required on this product. Resolution Available documentation is available on the Download Center A diagram of network architectures can be seen Here.

Issue Feature overview and tested platforms, operating systems, databases, and web browsers for AX/G3 version 3.8. Product Line TAC IA Series Environment Niagara AX / G3 3.8 Cause Field inquiries Resolution View the PDF files below.  They were obtained from Niagara-Central.com.  Feature Overview Test Summary Windows 8.1 is also supported (not listed in the Test Summary).

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 Under rare circumstances, resetting your Manager to its factory defaults may be necessary.  For example, if you have forgotten your Manager's IP address, or if you are experiencing login problems.  Environment SmartStruxure Lite Web Browser SmartStruxure Lite MPM Cause All SmartStruxure Lite™ Managers are equipped with a bootloader, accessible via a special IP address that lets you access several Manager firmware functions, among them, a factory reset.  Resolution WARNING: Restoring your Manager to factory settings should only be performed as a last resort; doing so will erase all its objects and devices, requiring you to reconfigure your Manager from scratch. Accessing the Bootloader As its name suggests, you access the bootloader at boot time, i.e., when you power up your Manager. To perform a factory reset: 1. Disconnect electrical power from your Manager by unplugging its power connector or unplugging its power supply from the AC outlet. 2. Ensure that your computer's TCP/IP settings are on the same subnet as the bootloader IP address:10.50.80.X.     IMPORTANT: Upon restarting your Manager, you will have only a brief interval–approximately 5 seconds–during which you will be able to access the bootloader. As such, we recommend that you perform the following steps 3.  Open your browser and type the following IP address into the address bar, but do not click the browser's Go icon or press any  key on your keyboard: 10.50.80.2 4. Reconnect your Manager's electrical power. 5. Within approximately 5 seconds, click your browser's Go icon or press the key to navigate to the  bootloader's IP address.  The bootloader screen displays.    6. In the Restore factory defaults area, click Submit. The Manager begins restoring its settings to the factory defaults. When completed, a success message displays.  7. Restart your Manager by clicking the Submit button in the Restart system area. 8. You may now log in to the Manager using its restored IP address: 10.50.80.3. If you cannot connect successfully to the bootloader using the above steps, chances are you are not navigating to the bootloader's URL within the defined 5-second window.       As an aid, some users may find it useful to do the following:      Open a command window and type the following: ping 10.50.80.2     As soon as you see a ping reply, return to your browser window and press the key to navigate to the address previously entered into the address bar.   Restoring your Manager to Factory Settings download as PDF.

Issue Clarification on documentation which does not indicate the addition of an xPDI8 and an xPDO4 being a valid combination to add to a b3 or i2 controller.   Environment xP modules xPDI8 xPDO4 Cause An addition to a existing i2 controller with an expansion port requires (4) more digital outputs and (8) more digital inputs. However, the documentation does not list the combination of the xPDO4 and xPDI8 as valid. Resolution That combination of expansion modules is not a tested, valid combination. The only tested combinations are those in the attached pages from the i2 Technical Reference

Issue Integration of the Rayleigh Instruments CT-2EA kilowatt-hour meter with the Xenta 5xx\Xenta7xx Xenta 913 and Modbus RTU Environment Xenta 511, 527, 55, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Rayleigh Instruments CT-2EA kilowatt-hour meter Cause Disclaimer:  This device template is intended to provide a starting point for an integrator and is not meant to be a mandatory points list for your integration project. Product Support Services has written this device template in an effort to give our customers a solid example of how to develop a device template for the above product.  The integrator will be responsible for any additions or modifications to this device template.   Please report any problems with this template to Product Support, via the Contact link at the top of this page. Resolution Please use the following dev file as a starting point and a guide to the integration.  This .dev file contains all of the registers in the device published by the manufacturer.  If any other data is required please see the latest Rayleigh Instruments documentation to make the necessary changes.   To use these files in XBuilder please follow these steps: 1.  Extract the .dev file from the .zip file in the link above and place it in a convenient location on your harddrive. 2.  In XBuilder, right-click on the Modbus Master device and choose 'Add Device'. 3.  Browse to the extracted dev file and choose 'Open'. 4.  Rename the newly added device to a unique name within the Modbus Master network.

Issue WorkPlace Tech revision 5.7.7 installed on a Windows Server 2003, 64-bit machine, receives the following error: Environment WorkPlace Tech Tool version 5.7.7 Windows 2003 Server, 32 bit or 64-bit Windows 2008 Server, 32 bit or 64 bit (multiple processors) Cause WorkPlace Tech Tool (WPT) is not supported on computers with Windows Server operating systems, nor on computers with 64-bit operating systems. Resolution Install on an approved hardware platform, per the Installation Instructions.

Issue During download or commission of a TAC Xenta programmable controller, WorkStation crashes with the following error message "A problem has occurred in this application" Click here to view the full error message Product Line EcoStruxure Building Operation Environment Building Operation WorkStation v. 1.7 or earlier TAC Vista Transition Cause During the transition from TAC Vista to SmartStruxure, it is possible that some information is imported with content that is not possible to introduce in the system with the normal engineering tools. If the neuron ID of a TAC Xenta IO module is not valid according to SmartStruxure, it will usually not be allowed to initiate the download process, but as the value has been introduced by the migration tool, this is possible. Here is an example of an invalid neuron ID entered for the IO module, and "Commission" being enabled Resolution Enter a valid neuron ID for the IO module before downloading, or remove the IO module from the Menta program. Note that this is fixed in SBO 1.8.1 and later versions.

Issue TC series thermostats which one support Modbus protocol? TC series thermostats which one support time schedules? Environment TC100 (TC103) TC300 (TC303, TC353) TC500 (TC503, TC553) Cause Due to different TC thermostats models support different features, customers need to double check the selection guide to make sure the selected model can support all features which are required. Resolution Click here  to view a matrix which contains all TC series thermostats and their supported features. Additional information can be found on the Buildings Business Extranet website (Products > Field Devices Asia Pacific > Thermostats).

Issue Is it possible to view web pages from an Xenta server using an iPhone or Android telephone? Environment Xenta Server 5.1.X Xenta 511, 527, 711, 731 Apple iPhone, iPad or Android smart phone mobile app Cause An increasing demand from customers to be able to monitor a site via a smart phone web browser. Resolution Whilst there are no official apps for iPhone or android smart phones, it is possible to create some static HTML pages which can be viewed in a smart phone web browser. There does however appear to be some restrictions is some web browsers, so try a number of different web browsers before determining if a web page works or not. The steps below outline how to create a simple variables page that can be viewed with a smart phone. An example is also attached as well as 2 copies of the HTML page that needs to be edited to increase the number of variables on the page. 1. Create a new Xbuilder project with the desired controller. 2. Create the folder structure for mobile users. a. Add a folder to the tree structure and name it "Mobile pages" or another appropriate name. b. Right-click on the page and select New\Page\HTML Variable Page. c. Select the tmpl1form.html template when prompted. d. 5 variables will be created in the folder under the HTML page. These are called SignalTag_1 - SignalTag_5. e. If more variables are required, right-click on the folder and select New\Object\Signal. Rename the signal "SignalTag_X" (in the example project SignalTag_6). f. Rename the variable page if required. g. Connect the signal tags to the appropriate signals e.g. LON/Modbus etc. 3. Generate the project. 4. Locate the Xbuilder project in windows explorer. Note the folder structure! 5. Locate the HTML variable page created under Project Name\Target Image\www\info\your folder name\your folder name\ 6. Edit the HTML variable  page that was created in Xbuilder (either notepad.exe or Microsoft front page or another appropriate HTML editor). The editing is to connect the extra variables created. In this example SignalTag_6 a. Locate the TAC_validateForm function at row 39. The original file contains 5 signals (as per the template): 'memsignal.4' to 'memsignal.8' Copy the complete text for one of the signals eg. for a boolean signal ,'memsignal.8','b','RinRange0:1' and then paste the text just before the closing bracket for the function. Rename the signal to memsignal.9 (or whatever the next number in the sequence is). b. Locate the paragraph tr bordercolor = "#000000# that contains the signal memsignal.8. c. Copy the entire paragraph and paste it in the document between the /tr of the previous paragraph and the tr bordercolor of the memsignal.8 paragraph. d. Remove the line containing "input type="submit" name="Submit" value="Submit" from the paragraph containing memsignal.8 e. Add the text: " " f. In the last paragraph containing "input type="Submit"...", change the memsignal.8 text to memsignal.9 and select the correct data type. Save the changes. 7. Copy the edited HTML page from ...\TAC XBuilder Projects\PSS Smart Phone\TargetImage\www\info\PSS Mobile Friendly Site\Mobile Pages to ...\TAC XBuilder Projects\PSS Smart Phone\UserTargetImage\www\info\PSS Mobile Friendly Site\Mobile Pages This creates the folder structure in the Xenta server when downloading the project. a. Download the project to the Xenta server (select "All files" when downloading). b. Browsing the Xenta server should result in a page similar to that shown below. 8. Configure a mobile user and grant the appropriate access levels. a. In the web interface go to Configuration\User Administration\User Administration and create a new user similar to the example below. b. Configure the user's access so they can only access the mobile folder and the pages contained within. 9. Log in with the newly created user and check that the view is similar to that shown below. The values should be able to be updated and submitted using the submit button. This is a very simple example, but this can easily be built upon with a little knowledge of HTML programming. For example, the home page can be adapted by using FTP to retrieve the intro731.html (or introXXX.html if you're using another Xenta server). Open the file and edit the following paragraph: You'll see that the text has been changed to "Mobile users, click here" and referred to a page PSS_HVAC/Mobile.html. This mobile.html page can be created and saved in the correct folder under user target image.  Link to Xbuilder project and before and after variables page.

Issue How to add Templates to new Personnel using the Personnel Import Utility. Environment Continuum Personnel Import Utility Access Control Cause It can be unclear as to how to add a Template to new Personnel when creating them from CSV file using the Personnel Import Utility (PIU). Resolution You will need to add the Template field to your attribute mapping list on the configuration tab and modify the XSL file to also include the RefTemplate field.   1. In the PIU attribute list, map the Template data source attribute to the RefTemplate Continuum personnel attribute.   2. Open the CSVToContinuumTransformation.xsl file (or the transformation file you will be using), search for the " " tag and at the tail end of this add the RefTemplate attribute as shown below.   3. Select the CSV file to import and press the Preview button then go to the Transformed Data Tab and you should see the RefTemplate field populated if everything was correct.   4. Upon importing the CS file you should then see the new Personnel with your defined RefTemplate assigned.   Here is a sample transformation and CSV import file

Issue In firmware 2.19.1, the MPM Modbus Generic Driver feature has been introduced with little to no explanation on how to use it Product Line EcoStruxure Building Expert Environment Multi Purpose Manager (MPM) Cause Sample CSV file not available on MPM Resolution In order to establish communication with a modbus device, a CSV (comma separated values) file of a certain format must be uploaded to the GMC1 object. Once uploaded the file will be visible in the drop-down list.   Requirements and Limitations Only holding registers are supported at this time (Modbus function codes 3 and 16) The CSV file mast be renamed Modbus_[label].csv where label is the name of the device or a label to help identification (e.g. Modbus_SE8000.csv) Write only registers are not supported It is not possible to use a more than 32 bits variable in write mode It is not possible to leave a blank column in CSV register configuration file except the last column It is not possible to create a continuous register table using different variable types   The CSV file must have the following format: modbus_addr,register_type,label,access,factor,unit Download example here (The text file can be viewed in a text editor but its extension must renamed to csv before uploading it to the MPM) modbus_addr: modbus register address (Decimal number between 1 and 65535) register_type: "uint" (UI16) "int" (SI16) "float" (F32) "ulong" (UI32) "int64" (SI64) "uint64" (UI64) label: name for this register, this will also be used to populate the associated object in the MPM Alphanumeric value between 1 and 32 characters. No special characters (comma, simple quotes, double quotes,%,&,@,#, etc.) access: read or read_write. read will only poll register based on driver availability (30 seconds typical) read_write will monitor for a change of value of the associated point, which will then generate a write event to the device with this new value factor: multiplier / gain Float number, typical between 0.001 and 65535. Typical use are factors of 10: (1,10,100, etc) This factor is multiplied when reading and is divided when writing.     unit: BACnet unit, used for the object units in the MPM. Number from the following list: 169 ampere square meters 3 Amperes 167 amperes per meter 168 amperes per square meter 55 bars 20 BTUs 50 btus per hour 117 btus per pound 24 btus per pound dry air 179 candelas 180 candelas per square meter 118 centimeters 60 centimeters of mercury 57 centimeters of water 79 cubic feet 84 cubic feet per minute 142 cubic feet per second 80 cubic meters 135 cubic meters per hour 165 cubic meters per minute 85 cubic meters per second 105 currency1 114 currency10 106 currency2 107 currency3 108 currency4 109 currency5 110 currency6 111 currency7 112 currency8 113 currency9 25 cycles per hour 26 cycles per minute 70 days 65 degree days celsius 66 degree days fahrenheit 90 degrees angular 62 degrees celsius 91 degrees celsius per hour 92 degrees celsius per minute 64 degrees fahrenheit 93 degrees fahrenheit per hour 94 degrees fahrenheit per minute 63 degrees kelvin 181 degrees kelvin per hour 182 degrees kelvin per minute 14 Degrees Phase 120 delta degrees fahrenheit 121 delta degrees kelvin 170 farads 33 feet 77 feet per minute 76 feet per second 38 foot candles 28 grams of water per kilogram dry air 155 grams per minute 154 grams per second 133 hectopascals 171 henrys 27 hertz 51 horsepower 71 hours 158 hundredths seconds 81 imperial gallons 86 imperial gallons per minute 32 inches 61 inches of mercury 58 inches of water 183 joule seconds 16 Joules 127 joules per degree kelvin 128 joules per kilogram degree kelvin 23 Joules/Kilogram Dry Air 147 kilo btus 157 kilo btus per hour 39 kilograms 186 kilograms per cubic meter 44 kilograms per hour 43 kilograms per minute 42 kilograms per second 129 kilohertz 122 kiloohms 17 Kilojoules 151 kilojoules per degree kelvin 125 kilojoules per kilogram 149 kilojoules per kilogram dry air 75 kilometers per hour 54 kilopascals 9 Kilovolt Amperes 12 Kilovolt Amperes Reactive 19 Kilowatt Hours 48 kilowatts 6 KVs 138 kw hours per square foot 137 kw hours per square meter 82 liters 136 liters per hour 88 liters per minute 87 liters per second 36 lumens 37 luxes 148 mega btus 130 megahertz 126 megajoules 152 megajoules per degree kelvin 150 megajoules per kilogram dry air 140 megajoules per square foot 139 megajoules per square meter 10 Megavolt Amperes 13 Megavolt Amperes Reactive 146 megawatt hours 49 megawatts 123 megohms 31 meters 164 meters per hour 163 meters per minute 74 meters per second 166 meters per second per second 78 miles per hour 2 Milliamperes 134 millibars 30 millimeters 59 millimeters of mercury 162 millimeters per minute 161 millimeters per second 145 milliohms 159 milliseconds 124 millivolts 132 milliwatts 72 minutes 68 months 7 MVs 153 newton 160 newton meters 187 newton seconds 188 newtons per meter 95 no units 172 ohm meters 4 Ohms 97 parts per billion 96 parts per million 53 pascals 131 per hour 100 per minute 101 per second 98 percent 143 percent obscuration per foot 144 percent obscuration per meter 99 percent per second 29 percent relative humidity 56 pounds force per square inch 40 pounds mass 46 pounds mass per hour 45 pounds mass per minute 119 pounds mass per second 15 Power Factor 102 psi per degree fahrenheit 103 radians 184 radians per second 104 revolutions per minute 73 seconds 173 siemens 174 siemens per meter 116 square centimeters 1 Square Feet 115 square inches 0 Square Meters 185 square meters per newton 175 teslas 21 Therms 22 Ton Hours 41 tons 156 tons per hour 52 tons refrigeration 83 us gallons 89 us gallons per minute 8 Volt Amperes 11 Volt Amperes Reactive 5 Volts 176 volts per degree kelvin 177 volts per meter 18 Watt Hours 47 watts 189 watts per meter per degree kelvin 34 watts per square foot 35 watts per square meter 141 watts per square meter degree kelvin 178 webers 69 weeks 67 years

Issue The calectro smoke detektor has too long pipe to fit Environment Calectro Smoke detektor Venturi pipe Cause The Venturi pipe is long, but also possible to cut Resolution You can cut the Venturi pipe to size but you must only cut it from the end that does not have the sleeve. See Installation instruction for more information.  

Issue The documentation on The Exchange differs from the documentation included in the packaging. Neither document shows the full capabilities or wiring options of the transmitter. Environment STO300 Cause The supplier recently changed the PCB and as a result, all of the 300 model plantroom type sensors now offer dual outputs (current and voltage). Since the part number designation is for current only the documentation included in the packaging only shows this configuration. To further complicate matters the specification and installation materials on The Exchange have not been updated to reflect the changes at this time Resolution The installation instructions included in the product packaging should always be referred to when installing these transmitters. The latest installation instructions can be downloaded here. If the new 0-10VDC output feature is required please follow the diagram below for wiring and DIP switch configuration.

Issue Some sensors such as the SCR110-H CO2 produce a noisy signal even when wired according to the documented instructions. The following is a trend chart of the unfiltered raw signal from the sensor. Environment Automation Server Continuum controllers TAC Xenta Cause Noisy signal is typically caused by common ground wiring of AC power. Resolution SOLUTION #1 Signal noise can usually be eliminated by using an isolated transformer to power the sensor separately as opposed to using a common transformer that powers up several pieces of equipment. SOLUTION #2 For sensors that support  AC and DC input voltage, signal noise can usually be eliminated by using DC instead of AC power source to power the sensor. SOLUTION #3 Implement a Slew Rate to filter out the noise. As of version 1.7.1, StruxureWare Building Operation does not have a built-in slew rate functionality. Nevertheless, a custom slew rate can be implemented using Script programming. See HowToDebounceANoisySensorSignal.pdf SOLUTION #4 Add a filter (FILT) in a Function Block program after the signal input Description: The function block is a discrete time first order software filter. The filter time constant is specified in seconds with the Time Const parameter. The initial block output value is zero. The filter algorithm is y(k) = y(k-1) + 1 / 1+T/h (u(k)-y(k-1)) where y(k) and u(k) are the filtered and unfiltered values at time k, respectively,h is the sampling interval (i.e. the application program cycle time), and T is the filter time constant. If the time constant is less than or equal to zero, no filtering is done. To obtain a good filter function, the time constant should be set significantly greater than the application program cycle time. This filter algorithm is based on a straightforward backward difference approximation of the continuous time derivative operator. SOLUTION #5 Ensure you are not using older versions of the IO Firmware. As detailed in TPA-SBO-17-0006.00 the firmware should be at least V2.015 in the modules and is available on the Download Center.

Issue There are new versions of Continuum Reports, Archiver, Elevator Control, etc. that were updated by the Center of Excellence development team. These applications need to be upgraded prior to using Continuum 2.0 SP1 for sites that use these applications because of new memory mapping. Environment Windows 7 Windows Server 2008 Continuum Cause Continuum 2.0 SP1 uses a new memory mapping scheme that allows for better use of large memory addressing. The Continuum Add-on applications needed to be updated in order to work properly, so each of the applications has a new version. Installers need to know which versions to update. Resolution Below is a list of Continuum Add-on applications and versions needed to work properly with Continuum 2.0 SP1. Prior to installing Continuum 2.0 SP1, you need to upgrade certain Continuum Add-on Applications with new versions. It is recommended that you be prepared to rollback to Continuum 2.0 should critical applications fail to operate after the upgrade to SP1. You can download new versions of the following Add-on Applications from The Exchange at this URL: https://ecobuilding.schneider-electric.com Search on 'continuumreports' and locate the application.   Add-on Application 2.0 SP1 Compatible Version Access Groups 2.5.1 BioScrypt 4G V-Station Integration 1.12.1 CFR Extended Log Archiver CFR Access Event Archiver CFR Alarm Event Archiver CFR Activity Event Archiver Continuum Reports 23.0e Cogent MiY Integration 1.8.1 DVTel 6.x Video Integration 2.3.2 Elevator Control V2.6.6 2.6.7 EZ-GuardTour 1.2 EZ-Trap 1.9 Genetec Omnicast 4.8 Video Integration 1.1.1 Genetec Security Center 5.2 Video Integration 1.2.1 Personnel Data Importer Continuum Reports 23.0e Salient Video Integration 1.3.1 Stentofon Integration 1.8 Video Inquire 1.9.1   Customer-Specific Custom Applications Contact COE.Support@Buildings.Schneider-Electric.com for upgrades for the following customer-specific custom applications:   AckAlarm Area Templates PIM CADS DVTel Alarming Continuum-Excel Elevator Control V3.x Elevator Control V4.x Elevator - EasyLobby Integration Extended Log Exporter PIM 2.0 ScanShell Scanner Interface Surgard Integration Vicon Video Integration xTra    Legacy Applications Contact COE.Support@Buildings.Schneider-Electric.com for upgrades for the following legacy applications:   Area PIM Door PIM Elevator Control V2.4 Elevator Control V2.5 Unlisted Application       Download a pdf copy of this list click the following link:  Continuum Add-On Application version list

Issue In versions of Cyberstation prior to 2.0 there was no way to determine if a valid attempt had been processed by the access engine in the controller before granting access to the door. This limitation made it impossible to implement custom access control sequences such as 'Two-Man Rule' or 'Man Trap' sequence unless the door was configured WITHOUT a door switch. Not having a door switch configured in the door made the implementation awkward as well as less secure, since the status of the door (Closed/Open) could not be determined. Product Line Andover Continuum Environment CyberStation ACX57xx controller CX9680 controller Cause Door 'Valid Attempt' flag not available before has been added to Continuum in Cyberstation 2.0, ACX57xx 1.100042 and CX9680 2.100042 Both the new version of Cyberstation as well as the new version of the controller firmware are required to get the new functionality. Resolution In order to improve the physical access control functionality in Continuum a new flag has been added to the door object. The name of the new flag is 'ValidAttempt' The value of 'ValidAttempt' is set to true when the access engine has processed a credential presented at the door (card or card & PIN) and has determined the credential can be granted access to the door. The value of the 'ValidAttempt' flag is reset to false after one scan. HOW IS 'ValidAttempt' DIFFERENT FROM 'ValidAccess'? When a door is configured with a door switch 'ValidAttempt' is set to true immediately after the access engine validates the credentials, determines that they are valid and  grants access by unlocking the door, the 'ValidAccess' flag will remain FALSE until the person gains access by opening the door as detected via the door switch. Click HERE to see a sample program demonstrating the use of the new 'Valid Attempt' functionality. In this example a bank has specified that access to the bank's vault must follow these rules: Not one is to be allowed alone in the vault. Access to the vault is by two people at a time, no more than two people are allowed in the vault. Vault's door must be configured with door switch in order to alarm on forced entry as well as door ajar.

Issue BACnet Schedule does not change the Digital Value when the Value attribute of the DV is bound to the Schedule Environment StruxureWare Building Operation BACnet controller B3xxx series. Cause When a user creates the BACnet Schedule object in the b3 controller, if the Default_Value attribute of the BACnet Schedule in the b3 is not configured, the schedule's default value is left as "NULL".   And later on, when the Schedule turns to True, it sets the bound DV value to Active. But when the Schedule turns to False, it tries to change the bound DV value to NULL (as it is the default value of the schedule),  which fails as it is not allowed to set the DV value to NULL.  As a result, the bound DV value cannot be changed and it keeps its previous value "Active" without being able to change it any longer. Resolution Set the Default Value attribute of the BACnet Schedule object from NULL to False as below: - Right click the BACnet Schedule object in the b3 controller and select the Properties. - In the Basic tab of the Properties window, scroll down all the way to the bottom and locate the Default Value attribute. - Click the setup icon on the right side of the attribute, it pops the Default Value window. - Uncheck the Null checkbox and confirm the Value now shows False. - Click OK from the attribute window, verify the Default value is False now, click OK from the Properties window.

Issue Allowing write access from BACnet Product Line TAC IA Series Environment I/A Series G3 BACnet Integration Cause By default, the BACnet driver provides external BACnet (client) devices "read access" to all exposed (exported to BACnet) objects in the station. Access depends on a station user named "BACnet." If this user does not already exist in the station, the Bacnet driver automatically creates it, upon startup. The BACnet user is initially created without any permissions. Resolution See below which is extracted from the Niagara Ax BACnet Guide: To allow any external writes (from BACnet) to properties of exported components, including invoking commands (actions), you must assign the BACnet user the necessary permissions to those components. For example, to allow an invoked "Active" action from BACnet to an exported BooleanWritable, in addition to making it "BACnet Writable" at priority level 8 when exporting, you must configure the station’s BACnet user to have operator write permissions on that BooleanWritable, at a minimum. Or, if an exported NumericWritable has an alarm extension, and you want to permit external BACnet writes to its "alarm limit" values, configure the BACnet user to have admin write permissions on the exported NumericWritable. In either example, to allow an external BACnet write to a property like "Out Of Service" or "Notify Type," you must give the BACnet user admin write permissions on the BACnet export descriptors. For details about station user security, see "About Security" in the User Guide. Note: BACnet user permissions also apply to writes of any exported files and histories. Also, note that while a password for the BACnet user is technically not needed (for external BACnet access), you should assign one anyway, because of the write permissions typically assigned. Make it a "non-blank" password, and guard this password carefully.

Issue How to modify a single trend sample value in Reports Server. Product Line EcoStruxure Building Operation Environment SQL  Reports Server Cause In some cases the user may wish to edit a single value from a trend log stored within the Reports Server Resolution Log into the Reports Server PC Copy the 2 Queries below into separate Queries in SQL Management Studio. - Click Here to download both queries. Open these Queries in SQL Management Studio Open Workstation Browse the Extended Trend Log you wish to change a value on Copy the Path from workstation Open the Query GetInfo in SQL Management Studio and paste the path to the @myLog parameter in the query. Remember to enter the data between the single quotes. In Workstation, open a Trend Log list. Browse to the Time stamp for the value you wish to change Type that time between the single quotes for the parameter @thisTime. Format the data as shown Year-Month-Day Hour:Min:Second Set the @oneSecondLater parameter to one second in time later than the @thisTime parameter Execute the Query or press F5 The Result should be a single row showing 3 columns Open the Query UpdateDb in SQL Managment Studio Set the @DateTimeStamp by Coping the result of the GetInfo query and pasting it between the single quotes. Set the @thisParentID and the @OriginalFloatValue parameters by copying the data in the same manner. Type the desired new value between the single quotes of the @newFloatValue parameter. Press F5 to execute the Query Re-Run the get info Query to verify the change Query 1 - GetInfo Declare @myLog nvarchar(1024) Declare @thisTime datetime2(3) Declare @oneSecondLater datetime2(3) SET @myLog = '' SET @thisTime = '' SET @oneSecondLater = ''   SELECT sampledata.DateTimeStamp, sampledata.ParentID, sampledata.floatvalue from dbo.tblogtimevalues as sampledata join dbo.tbLoggedEntities as logs on sampledata.ParentID = logs.ID   WHERE logs.Path = @myLog AND sampledata.DateTimeStamp between @thisTime and @oneSecondLater Query 2 - UpdateDb Declare @thisDateTimeStamp datetime2(3) Declare @thisParentID int Declare @OriginalFloatValue float Declare @newFloatValue float   Set @thisDateTimeStamp = '' Set @thisParentID = '' Set @OriginalFloatValue = '' Set @newFloatValue = ''   UPDATE dbo.tbLogTimeValues  Set FloatVALUE=@newFloatValue,OdometerValue=@newFloatValue  WHERE DateTimeStamp = @thisDateTimeStamp AND ParentID = @thisParentID

Issue From Continuum version 1.94 when you enable the Operator text when acknowledging alarms prompt, the messages will not save Environment Continuum Alarm acknowledgement Windows  Cause This was caused by a defect in the software which includes version 1.94 to version 2.0  Defect #368 = Alarms - Operator text entered before ACKing an alarm, is not stored in regions other than US. Resolution There is now a hotfix which corrects this issue which you must apply after you have Continuum 1.94 SP1 This hotfix has also been applied and tested successfully on version 2.0  Please download this file and replace the file as instructed in the READ ME.txt document