Building Automation Knowledge Base

Issue A Niagara R2/G3 UNC/JACE is rebooting every 15 minutes and the standard output window indicates AC Power status failed and a "Battery test failed" gets logged as well. Product Line TAC IA Series Environment I/A Series UNC, ENC or JACE chassis with Gel-cell backup battery Cause Marginal or failed battery or bad battery charging fuse Resolution The UNC automatically performs a battery load test every 15 minutes. If the voltage drops below a predefined value, the battery test indicates "battery test failed". If the voltage is higher than the predefined value, the battery test indicates "battery test passed". This message is only reported once unless the detected battery condition changes. A station alarm is generated only when the new outcome is different that the previous test. If a battery is marginal, the test may alternate between "passed" and "failed." Additionally, a bad or marginal battery has been known to cause random UNC reboots. Begin troubleshooting by checking the battery fuse (field replaceable only in the UNC-500/510 controllers), connections and voltage level.  If the battery voltage is low (less than 12 Vdc), disconnect the battery and monitor the UNC for errors or rebooting. If the errors or rebooting stops install a new battery.  After installing the new battery, measure the battery charging voltage.  The voltage reading should be between 13 and 14.5 volts DC if a good battery is connected.  If the installed battery is partially discharged, the charging voltage reading may be as low as 12.5 volts. In release 2.301.522, a change was made to how embedded controllers (UNC-410 / 500 / 510 / 520) perform the backup battery test.  Formerly, a "marginal" battery might result in continuous reboots. Now, the battery test is better coordinated with the AC power test. This prevents the scenario of repeated AC power fail shutdowns upon boot up if the battery is bad or weak.

Issue Is there a way to convert a Trane BCU (BMTW or BMTX) from BACnet/Ethernet to BACnet/IP for integrating to a Niagara R2 UNC? Product Line TAC IA Series Environment Trane BCU (BMTW or BMTX) Niagara R2 UNC Cause There are two components required to change over the BCU from BACnet/Ethernet to BACnet/IP. Resolution A special serial cable is required to download the BCU with the new configuration. Below are the pin outs to make the cable:     Access to the Tracer Summit software. Here are the steps for running the BCUconfig.exe program to change over the BCU from Ethernet to IP: Open Windows Explorer and navigate to C:\Program Files\Tracer Summit\Bin Double-click on BCUconfig.exe Enter the information and select download. Note - This is where you must have the Trane serial cable. The BCU will reset. Now change the Connection type in the Tracer Summit software to IP connection: Open the Tracer Summit software and select Connect. The Site connection Wizard will appear. Select the BACnet/IP radio button. From the Ethernet Configuration window, select the 'open on startup' check box. Select the 'Use BBMD connection' from the BACnet/IP configuration window. Specify the IP address of the BBMD BCU and the UDP port which is the BACnet port. Select Finish.

Issue Sample Plain English program to set up a door to allow for either keypad OR card validation. Environment Continuum Plain English Infinity NetController Cause Allowing the NetController to respond to a keypad as well as a card reader allows for flexibility in the security solution. Resolution How do I setup a door for keypad OR card validation Create the following InfinityProgram in the NetController for each door. Change each program to the correct door name. NOTE: If using this program, make sure that you do not have validate pin mode selected on the entry reader tab of the door editor. -------------------------------------------------------------------------------------------------- 'Looping, AutoStart Program 'Change officedoor to the name of your door Watching: IF officedoor\doorfault IS 2 THEN '0 for normal operation 2 if Fault (Tamper) detected officedoor\entrynormmode = 8 'PINMode officedoor\entrynocommmode = 8 'PINMode GOTO Counting ENDIF Counting: IF TS > 5 THEN 'Wait 5 seconds before switching back to SiteMode + CardMode officedoor\entrynormmode = 3 'SiteMode + CardMode officedoor\entrynocommmode = 3 'SiteMode + CardMode GOTO Watching ENDIF --------------------------------------------------------------------- Press the # key once, it will place the door in PINMode (8) for the 5 seconds then back to SiteMode+CardMode (3). -------------------------------------------------------------------------------------------------------- Here are the available EntryNormMode and ExitNormMode values SiteMode = 1 CardMode = 2 GeneralMode = 4 PINMode = 8 If you plan to use more than one add the two numbers together (Example: SiteMode + CardMode + PinMode = 11) ------------------------------------------------------------------------------------------------------ Here are the available DoorFault values 1 = Database of doors, areas, and personnel is not functioning normally 2 = Entry Keypad is being tampered with 4 = Exit Keypad is being tampered with 8 = Entry Card Reader is being tampered with or has failed 16 = Exit Card Reader is being tampered with or has failed --------------------------------------------------------------------------------------------------------- My Test case: I created a person with a valid card and a valid PIN. When I used the card the door would open, after relock I pressed the # and immediately entered the PIN plus the #, the door unlocked. If you have a door switch you could probably use it instead of the 5 second timer this would give you a little more control over the door so that the next person in line (with a card) would not have to wait. CyberStation (v1.52.0.20021120) NetController (v1.520010) AC1 (v22) HID ProxPro with Keypad Note: this works on an ACX(5740/5720) also IMPORTANT: The sample PE program above only sets the EntryNormMode of the door. The program needs to set also the EntryNoCommMode and possibly the EntryNodataMode. If the door is a dual reader door then the corresponding attributes on the exit side of the door must also be set.

Issue Problems encountered when changing Data Types(Elec Type) with Bacnet Points and using programs to perform COV's on those points Environment bCX Controller CyberStation Cause Data type (elec type) is changed without sending to the bacnet side will create issue. Resolution Changing the Data Type (Elec Type) of a point on the fly can cause issues. Once a point is created on the infinity side and sent to the data base on the bacnet side and a point is referenced from one or the other and a data type (elec type) is changed without sending to the bacnet side can cause issues. One of the issues is that data could quit updating. Another issue and one that is more noticeable is that if a COV subscription is created from one of the points through a program, the program could disable for one and or the data would not be correct or updated. To get an understanding of what goes on under the hood. Lets create a scenario that is a typical setup to see what is really going on. ------------------------------- I have a BCX with a B3 controller and have a point in the bcx named bcxPoint (binary data type). I have a point in the B3 named localPoint(binary data type) and a program named MirrorPrg. localPoint = myNet\MyBCX\bcxPoint Save this program and send to database on the bacnet side. Open the bcxPoint on the infinity side... change the value from 1 to 0 and back and forth while watching the value update on the bacnet side's localPoint. All is well and works as expected. Now change the data type on the bcxPoint to Analog and apply. Change the point form 1 to 0 and back and forth, notice that the point on the B3 localPoint on the bacnet side is not updating. But check the program and it is still running.(But not working) Depending if you have other points in a program that sent a COV notification your program can disable. But for our test, we'll force a COV subscription by adding a blank line to the program and saving, notice the program disables. NOTE: the program will appear to still to be running until a COV notification is sent. This caveat if you think about it makes sense. We subscribe to a COV list, but one of the data types changes without being sent to the bacnet side. On a larger scale lets say you have multiple points in the mirrorPrg and the program disables, not good. In order to correct the issue we described above, we can set the BCX's bcxPoint back to a binary type and perform a send to database on the bacnet side. Open up the program and add a line and then save which recompiles and puts out a new COV subscription. Don't forget to enable the program. The above is a workaround in case you get into trouble. But if you have many points you have changed, I would suggest deleting the controller from the bacnet side and then reloading the controller and the performing a find new bacnet devices. This will ensure that you have all data types straightened out. But to be on the safe side, if you are going to be changing data types of points, I would suggest deleting the point on the infinity side and perform a send to database on the bacnet side. This will get rid of all instances of the point. Then create the point with the correct data type and perform a send to database on the bacnet side and make sure you check all programs referencing the point.

Issue When saving a Plain English program, Continuum shows error messages and cannot save the PE program. 'Error: Unable to lock an object because it is already locked', or 'Unable to find an object in the database' Environment Continuum system Plain English program Cause FiringOrder attribute of the controller (or the workstation) is editlocked PE is not registered in the FiringOrder attribute of the controller (or the workstation). Resolution When saving a PE program, Continuum gets error of 'Error: Unable to lock an object because it is already locked' followed by 'Error Text Undefined [TBD 0xc2ff1410]'. This happens when the FiringOrder attribute of the controller (or the workstation) is editlocked. Unlocking the FiringOrder (Set CXName\FiringOrder Editlock = False) will fix the problem. When saving a PE program, Continuum gets error of 'Unable to find an object in the database'. This happens when the PE is not registered in the FiringOrder attribute of the controller (or the workstation). In order to Verify, open the program in the PE editor, right click inside the program, select the Firing Order, check if the program is listed on the Member List page. In order to fix the issue, verify the FiringOrder Editlock is false (ie, print CXName FiringOrder Editlock), export the PE program to a dump file, delete the PE program, import the dump file of the PE program back to the controller (or, create a new program and copy the source code from the dump file.). 

Issue Controller Error Logs - How to gather Continuum Controller error logs if requested by Product Support for troubleshooting. Product Line Andover Continuum Environment BCX CX  CMX 9680 9900 i2 b3 9702 Controller Error Log Gerry Log Cause Troubleshooting controllers often time requires obtaining an error log from the controller Resolution The controller error logs contain useful diagnostic information when it is necessary to troubleshoot a controller or system problem. Much of what is logged are normal system operations that may assist an engineer in diagnosing a problem in the field. To get the error logs from various controllers follow the procedures below: NetControllers - 99xx  Dumb terminal in using HyperTerminal Sign into the NetController Press V then E and press Enter over the NetController you are attached to Press F2 Hit Alt + Print screen and paste into a Word doc Arrow down to single space or Ctrl+D to page down Hit Alt + Print screen and paste into a Word doc Repeat this process until you are at the end of the errors (up to 200) F4 Exits the error log See the CX Controllers Programmer’s Guide for all terminal keystrokes Email the file to Product Support Services   BCX/i2/B3 Controllers CX9680/ACX5720/ACX5740/9702 Controllers Note: You can not retrieve errors from NetController I (CX9900) using this tool Controller Error Log Tool Navigate to C:\Program Files\Continuum Double click on ControllerErrorLogTool.exe to open (This will do an install the first time) Note: The ErrorLogTool.exe is an older version of this utility and will work, but gives less information and does not contain the error lookup feature. Enter in the BCX or master CX IP Transport type = UDP or TCP depending on controller configuration CX Enode ID = AccNetId from the main CX editor Select Continuum in the Mode area, top right If the controller is a field device then enter the following: CX infinet port = Select the one you want to report on Infinet Node ID = port number of the i2 device you want the error log out of Once all the above required entries have been made: Click Get Log and the page will populate with any errors Once this runs, select SaveAs and name the file Email the file to Product Support Services Suppliment - To gather error logs from Continuum controllers transisioned to StuxureWare please see How to pull the error log from a b3 or Infinet controller in SmartStruxure.

Issue Unable to connect to a BCX configuration page Product Line Andover Continuum Environment Continuum BCX9640 and 4040 Cause 404 Page not found error accessing the configuration page using the controller IP in a browser Resolution Note: This document is for troubleshooting help, it is not a comprehensive BCX setup guide. Please refer to the BCX1 Technical Reference for detailed setup instructions.   Using a LAN or a cross-over cable? If the BCX is on a LAN and was working before, remove the LAN cable from the BCX and try to ping the BCX. If you get a response then you have a duplicate IP. Same subnet? Make sure DHCP is disabled on your computer. Use a straight-through or cross-over cable to access the BCX directly. Has this cable been used successfully before? Reset the BCX to the default IP. The button is under the cover, top right. Be sure to hold down the IP reset button for about 20 seconds Is the controller in bootloader mode? This can be seen by observing the CPU light flashing rapidly, approximately two times a second (2 Hz at 50% duty). Flashing the application through Cyberstation may fix this and enable you to get back into the controller. Even though access to the config page is not available, the update OS button in Continuum using the controller's Network setting and ACCNet ID may be accessible to perform a firmware upgrade. Ping the IP from a DOS prompt, can the BCX be pinged? Ex. Ping 169.254.1.1 Use Ipconfig /all to see your PCs network settings. The best case scenario is to be on the same subnet or connect directly. Are there multiple NIC cards on the PC? (Ex. Ethernet and wireless on a laptop) Disable the wireless adapter or other adapters. Continuum does not support a multiple NIC card configuration. Run Wireshark to get a capture between the BCX and The PC. Remove power from the BCX and reapply power. When the BCX starts it sends a gratuitous ARP that will indicate the IP address within the BCX. It may be a different IP than expected. Did the issue of not accessing the web page happen after a power outage? Is the CPU light flashing amber and it was flashing green before and no one has flashed the controller? Is the CPU light solid amber? If so, contact support for assistance.

Issue Modbus XDriver for BCX1-9640/4040 (ModbusRTU_bCX_xxxxxxx.xdr) on comm2 for RS-485 does not work even when the comm2 port says that the driver is installed, no errors and the comm parameters match the Modbus protocol device (ie, 19.2k, n, 8, -). Product Line Andover Continuum Environment bCX1-9640/4040 Controller Modbus XDriver Cause Check the Communication Configuration Point (Function Code 99) of the XDriver. Resolution Function Code 99 is used to select between RS-485 and RS-232 when using a bCX1-9640/4040 controller with Modbus XDriver installed in Comm2 port. Unlike the Modbus XDriver for CX ModbusRTU_2xxxxxx.xdr), the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) requires user to set correct value to the FileNumber attribute of Function Code 99 (Communication Configuration Point ). If the FileNumber attribute of the Communication Configuration Point is not set to "1", the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) uses the default value, which is "0". When the FileNumber attribute is set to "0", the Modbus XDriver for BCX1-96404040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-232. When the FileNumber attribute is set to "1", the Modbus XDriver for BCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-485. For detailed information, refer to the Modbus RTU XDriver User Guide on page15: Function Code 99 – Communication Configuration Point.

Issue A PCI I/O board added to allow a parallel port for a security key is not recognized by the key. Environment Continuum Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause The default setup for the Sentinel driver does not configure the PCI port Resolution After adding a PCI I/O board to allow a parallel key, the security key is not recognized. Even if a printer works on this parallel port and another machine reads the key perfectly, the security key does not work. Uninstalling and reinstalling the Sentinel driver does not make a difference. The Sentinel driver needs to be configured to allow the parallel port to be accessed via the PCI bus. By default, only the ISA and USB port types are shown. Follow these steps to add the port for the installed PCI board: From the Control Panel, double-click the System icon to open the System Properties page. Click the Hardware tab and then the Device Manager Button to open the Device Manager. Click the + sign next to Ports (COM & LPT) to expand the tree. Double-click on PCI Card (LPT1) to open the property sheet for the PCI adapter. Click on the Resources tab to see the resources used by the adapter. Under Resource Settings, make note of the first number in the range of the first line. Ex. I/O Range 0378-0374 (the number to make note of is 0378) Next, Start the driver configuration utility, SetupSysDriver.exe. It is usually located at C:\Program Files\Rainbow Technologies\Sentinel System Driver Click the "Configure Driver" button, then click the "Add" button. Enter the I/O address of the PCI parallel port adapter into the "Bus Address" field. Ex. 0378. For Port type select PCIbus and Click on OK It will show that a User Created port has been added at address 0378. The Sentinel System Driver should now be configured to use the Parallel PCI adapter.

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 How can the true/false output from a Boolean object (i.e. Tstat) be changed to a numeric 0 or 100 in Niagara G3? Environment Niagara G3 Cause Represent a boolean on/off value with a numeric that can be used to drive other logic. Resolution Open the kitControl palette under the Util folder Use an object called NumericSwitch Link the output of the Boolean object into the InSwitch property of the NumericSwitch In the properties of the NumericSwitch object, set the "in true" value to 100 and "in false" value to 0 (or vice versa if reverse acting). The output of the NumericSwitch will be a numeric type.

Issue Setting up the override value to show the damper feedback on an i2/B3 866-v Product Line Andover Continuum, EcoStruxure Building Operation Environment i2/B3 866-V Plain English Script Cause Activate the damper position feature in the 866-V. Resolution SBO: See this video on creating a program that calculates damper feedback position.  Also reference the article How to show damper feedback for an i2/b3 866-V which describes what needs to be done to show damper position and calibrate the damper. Sample objects, code and images showing configuration are supplied.   Continuum: There is a description in the 866-V installation manual on how to activate the damper position feature, but there are some additional pieces of information that this article has been created to address. This was initially to just get the feature working as mentioned in the next section below. Getting the damper feedback operational: Once the end stops are determined initially during the Learn process, the controller can then determine the position of the damper. Create a PE program to set the DamperOutput LCDState = Disabled and back to Enabled in the next line. This will run through its stroke to determine the end stops. ‘Example program named "damperstate" Fall thru, auto start ‘a 2 line program to initialize the stops Line 1 Set damper LCDstate to disabled goto 2 Line 2 Set damper LCDstate to enabled stop To run from the command line Run damperstate Note that the Feedback will not start working until the Damper has gone full stroke in both directions. This will take several minutes. Set the damper point to on or –on depending on the position so it will move Print Damper OverrideValue from a command line or display it on a listview of the damper output after adding the overridevalue column Self Calibration - The LCDState toggle actually activates the "self calibrate" process. It doesn't just enable the feature. It is necessary to know this because you will need to activate the self calibration again whenever the damper is manually moved using the red actuator clutch release button. Using the clutch can cause the damper position to be reported incorrectly. Periodic re-calibration should be as a part of normal procedure for the controller. Once the clutch is used, the damper position will still report, but the value may be incorrect. Re-calibrate recommendation- Use a PE program that recalibrates the damper (i.e. LCDState as mentioned in Section A) on manual command by the service technician on a power cycle or at the end of an occupancy period. Note: For controlling the Damper motor output create an Infinity Output point of type Triac on Channel 1. It can then be opened / Closed like any other Triac output with the use of On, -On or Off commands

Issue Are B-link or Infilink repeaters required every 32 nodes on an RS-485 bus when using i2 or b3 controllers? Infinet 1 controller had this requirement Environment Continuum Cause Infinity version 1 controllers required a repeater every 32 nodes. i2/b3 controllers do not have this same node count requirement. Resolution If you are going to be using i2/b3s with no 3rd party bacnet controllers on the segment, it’s less than 4000ft with approved cable, the runs are totally daisy chained without any "Y's" or "T's" in the network runs, then no Infilink/B-link repeaters are needed. The reason for this is that Continuum uses 1/10th load transceivers allowing the full 127 nodes to be used. If you are mixing b3s with 3rd party non-Andover controllers or mixing infinity version 1 infinet controllers with i2s, then you will need a repeater every 32 nodes and every 4000ft. If the distance exceeds 4000 ft, you will need a repeater.

Issue Performing Load Sources in the EcoStruxure ETL tool causes errors with the following headers:   There was no endpoint listening at http://localhost:8080/EcoStruxure/DataExchange that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. The HTTP request is unauthorized with client authentication scheme 'Digest'. The authentication header received from the server was 'Digest realm="ews@SxWBM",qop="auth",nonce="AEEE5A9347E49ECADC753B5AA17EECE0",OPAQUE="5B4718"'. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Enterprise Server Automation Server Cause The EBO EWS Extract Task settings are incorrect in regards to the EcoStruxure ES or AS that it is trying to access.    There was no endpoint listening at... This error is due to the use of the incorrect port numbers in the EWS Web Service URL.   The HTTP request is unauthorized with client authentication scheme 'Digest'... This error is due to the use of the incorrect admin Username and/or Password.  Resolution The settings of EBO EWS Extract Task need to be verified and corrected.    Click on the Tasks tab in the ETL tool and select the "EWS Extract Task". The extract task settings will be displayed on the right side of the screen.                                                                               Verify that the port number in Web Service URL address corresponds to the port number being used by the ES or AS  Verify that a valid Username and Password has been entered into the EWS Web Service User Name and Web Service Password fields. 

Issue Alarm Forward and Log settings with enhanced alarm logging causes unnecessary network traffic Product Line Andover Continuum Environment Continuum Workstation Cause There has been some confusion about whether to select forwarding and logging on the recipient editor located within the eventnotification editor. Resolution In 1.5 and later versions of Continuum, a new alarm engine was introduced. To use the new alarming engine, select the enhanced alarming check box located in the database initialization editor. The enhanced alarming feature will perform both the forwarding and logging of an alarm. If the enhanced alarming feature IS SELECTED, then the forwarding and logging of a specific PC will not need to be checked ***. If enhanced alarming IS NOT SELECTED, then you will need to specify a forwarding and logging workstation. **IMPORTANT: Intrinsic alarms of type Controller Status, Fault Status and Logon Status still need their corresponding Event Enrollment object configured for logging and/or forwarding as before. If enhanced alarming, forwarding and logging are selected, there will be no duplication of alarms, but will cause unnecessary traffic on the network. If all three are selected and are on a very busy network, you may experience workstations appearing as offline. This can be intermittent depending on the amount of network traffic generated on your site. To check the settings of your enhanced alarming features, open up the database initialization editor and select either the server or stand alone button to view your settings. If your setting is not selected and you want to use the new alarming engine then select the feature. Make sure you restart ALL workstations when you change this feature. In 1.7 and later versions of continuum there is also an enhanced alarm delivery selection. This selection uses Microsoft's Messaging Queuing Service to deliver alarms. This feature allows multiple workstations to share the load of delivery of alarms to the recipients of an eventnotification. Thus reducing the work load of just one workstation to handle the delivery. The enhanced alarm delivery feature, will be best utilized when working with multiple workstations.

Issue How do I change the Baud Rate of a field bus (either Infinet or Bacnet MSTP) if there is either an Infilink or B-link on the network? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet BACnet Cause The Infilink and B-link must have their baud rate set manually. Resolution All Infinet or Bacnet B3 controllers autobaud on initial startup or when the fieldbus commport is changed from the parent controller's commport editor. The Infilink and B-link must have their baud rate set manually. The proper procedure to change the fieldbus baud rate is to first go to the commport editor and change the fieldbus baud rate. At this point a message is sent to all field bus controllers to change their baud rate. They will all change immediately, however the Infilink and B-link have not yet changed, so the bus will now be in a confused state and there will be offline issues. The next step is to go to the Infilink or B-link repeater and manually change the baud rate to the new setting. At this point the network should work normally, however if the procedure is not followed there may be network issues where you have some controllers that are running at different baud rates causing the network to be totally shut down. If this is the case the way to resolve the issue is to make sure the Infilink or B-link repeater is set to the desired baud rate and power down or reset those controllers on the network so that they will all synch up to the correct Baud Rate upon power up. ** Changing many controllers A method that may help when needing to change the baud rate of many controllers is to bypass the b-link Connect segment 1 of the b-link directly to the BCX comm port and change the baud rate Reconnect the B-link and verify the controllers are now online, repeat the baud change if necessary. Repeat this process for each segment You may still have some isolated controllers that need to be powered off/on. Related: BACnet bCX MSTP network loses communication when a b-Link is added or removed

Issue MNL-800 LON SNVT Programming Standards Environment Workplace Tech Tool software (any version) MNL-800 controller application Cause Problems occasionally arise as a result of improper LON SNVT programming and configuration in the MN-800 device application.  These issues include problems with the re-commissioning of the updated controller and potential network variable mismatch situations. Resolution  The following standards will prevent these problems from occurring. Network variables MUST be manually indexed. This prevents issues with the network variables becoming renumbered when application programming changes are made. (See NOTE 1) Change the application "Program ID" any time network variables are added or removed from an application.  To change the "Program ID" use the WPT Hardware Wizard,  (See NOTE 2) Select Hardware Wizard from Application Menu Click [Next] in MicroNet Setup Wizard screen Change the displayed program ID by entering a different program ID or adding a suffix letter/number. Maximum length is 8 characters. Click [Finish] to save the changed program ID and exit the MicroNet Setup Wizard.  In addition, one method of minimizing the need to repeatedly change the "Program ID" as the application is developed and debugged is to add a few extra common SNVT input and output definitions when first creating the application, leaving them unconnected to the application program.  If one of these SVNTs is needed, it is available in the LON network image (XIF file) and it is not necessary to change the "Program ID". If the MNL-800 controller has firmware version 2.0 (or later) installed, the standard nci network variables do not have to be indexed as the highest numbered SNVTs in the application.  It is perfectly acceptable to number them as the first 17 indexed SNVTs. Note that there are 17 standard network variables (12 nci, 2 nvo & 1 nvi), not just ten nci SNVTs. SNVT variable names should be limited to 16 characters or less.  Longer names are accepted by the WorkPlace Tech programming tool but the names will automatically be truncated by the LON Network Management tool when commissioning the controller. In addition, when programming the MNL-800 applications with the WorkPlace Tech Tool version 5.0, or later, it is not necessary to put each MNL-800 application in a separate project. NOTE 1: If using the WorkPlace Tech Tool version 5.8 or above, you can use the "Object Indexer" to automatically number all the network variables for you.  This tool also includes functions for detecting duplicate SNVT index numbers and for detecting gaps in the assigned index numbers. NOTE 2: If using the WorkPlace Tech Tool version 5.8 or above, you can set an option in the Hardware Wizard to automatically generate a new ProgramID and reindex the network variables when compiling the application.  Please be aware that this automatic generation of the ProgramID will require the Echelon network image for this device to be updated in any Echelon compatible network management tool.  Please refer to the documentation for the network management tool to determine what actions will be required. For example, if Niagara was used to manage the LON network, then the old shadow will need to be deleted, a new one added, and the device points rediscovered and the device re-commissioned.  

Issue Input scaling issues with the use of 0 to 5 Vdc and 0 (or 4) to 20 Milliamp transducers on a MNB controller. Environment MNB Series Controller application program using Analog Input voltage or current inputs. Cause The resolution of the Analog Input object value is determined by the maximum value that can be processed. If the scaled input range is less than 163.84, the output resolution is 0.01 If the scaled input range is greater than 163.84, the output is an integer value. Resolution When programming the Analog Input object in the WorkPlace Tech Tool, it is important to properly configure the input range and scaled value range for this object. If configured for a 0 to 5 VDC input, the sensor properties must be configured as follows: Input Sensor Type (Type): 5 - Volts Input Low Value (LInput): 0 Scaled Low Value (LScale): 0 Input High Value (HInput): 5 Scaled High Value (HScale): (value, up to 16383, corresponding to 5 volt input) See note below. If configured for a 0 to 20 milliamp or 4 to 20 milliamp input, the sensor properties must be configured as follows: Input Sensor Type (Type): 4 - Milliamp Input Low Value (LInput): 0 or 4 (depending on transducer) Scaled Low Value (LScale): 0 (value corresponding to LInput sensed value) Input High Value (HInput): 20 Scaled High Value (HScale): (value, up to 16383, corresponding to 20 milliamp input) See note below. NOTE: The HScale value should be set to give an output value for the Analog Input object that corresponds to the maximum temperature, flow, cfm, etc. that the sensor is measuring. The resolution of the value processed by this object must be taken into account when setting the HScale value because the input to output scaling and precision depends on this scaling constant. If the HScale value is less than 163.83, the input resolution is two decimal places and if greater than 163.83, integer resolution. An example of where this scale range is critical would be the use of a 0 to 5 volt air pressure transducer measuring an air pressure of 0 to 2 InWC. If the HScale is set to 2, the output would only resolve to 0.01. If the HScale value were set to 2000, the output would be in thousandths of an InWC, giving you an effective resolution of 0.001. Since this value is one thousand times the actual measured pressure, this 1000x scale factor would also have to be taken into account in any use of that value within the application.

Issue Is a certain version of Technician Tool Mobile Application compatible with all versions of StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool Automation Server Enterprise Server Cause The Technician Tool will always be backwards compatible, meaning that the latest version of the tool will work with any version of SBO. Older versions of the Technician Tool may not work with a newer version of SBO. Resolution Please note: Mobile experience to be replaced with EcoStruxure™ Building Operation v2.0 WebStation. For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool Always use the latest version of Technician Tool Mobile Application when possible, as that will work with all SBO versions.

Issue There appears to be a low battery on the control board. How can the NiCAD Battery be tested on the controller to see if it needs to be changed? Product Line TAC INET Environment I/NET Seven Cause Possible low battery on control board. Resolution There are some checks you can make regarding the battery condition. The battery has a design life of 7 years and sometimes lasts much longer. With power applied to a controller for at least 72 hours, take a DMM and measure the DC voltage across the battery. It should be in the neighborhood of 4.2-4.3 vDC. Remove power from the controller board and take the same measurement again. The beginning voltage should still be between 4.1-4.3 vDC and should start slowly tapering off (a tenth of a volt over a period of minutes would be normal). When the battery voltage reaches 3.6 vDC this is the threshold at which the battery can sustain the RAM memory. Any voltage below this value will subject the RAM memory to loss of data (+ - a tenth or two). If the initial voltage with power applied to the controller is less than 4.0 vDC after 72 hours, the battery may need replacing. If the battery voltage drops rapidly after power is removed from the controller, the battery needs replacing. If the controller memory inexplicably gets lost (not counting power surges, brownouts, etc.) and a station restore is needed, the battery may need replacing. Normally the above-mentioned tests will show that the battery has lost its storage capacity. The TAC part number for the White NiCAD battery that is on most of the I/Net Controllers is 01-2100-545. These batteries can no longer be ordered through the Customer Care department. For further battery info please reference Replacement I/NET Controller NICAD Battery info.