Building Automation Knowledge Base

Issue Some b3 system variables have been renamed in StruxureWare as have some of the special labels. Environment StruxureWare WorkStation b3 BACnet devices Cause System design Resolution When programming the b3 devices care should be taken to use the StruxureWare Building Operation name of system variables and special labels to avoid compiler errors. All system variables that in Continuum have the prefix ACC in the name have been re-named to remove the prefix so that ACCStatusBackup is StatusBackup and ACCStatusFlash is StatusFlash. Also all value labels that in Continuum have the prefix ACC have been re-named to remove the prefix so that ACCBackupNeeded is BackupNeeded and ACCBackupNow is BackupNow.

Issue What are the pull up resistors on the universal inputs used for? Environment IOU modules i2 devices b3 devices Cause Information on the pull up resistors selection switch. Resolution The pull up resistors on the inputs are used to configure the input impedance, for example on the 810 series i2/b3 field controllers the input impedance can be 30.1K ohms referenced to 10.000 V or 10 M ohms referenced to ground with the input reference resistor switch set to OUT Pull up resistors are configured via the DIP switch located in the general area of the inputs, each small switch corresponds to the input with the same number. If an input is either a thermistor or a digital input, switch its input reference resistor switch to IN. (switch ON) If you require that the input be high impedance (10 M ohms), set its input reference resistor switch to OUT. (switch OFF)

Issue Average space temperature on TAC Xenta 120 devices. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Xenta 121-FC TAC Xenta 121-HP Cause TAC Xenta 121 is able to average space temperatures from multiple sensors. For example, it could average two room units, or one room unit and one Lon sensor. It is possible to average up to three different Lon sensors. Resolution Bind a valid temperature SNVT value to the input nviSpaceTemp. The TAC Xenta 120 device will calculate the average between the bound input and the physical sensor.

Issue Function Blocks as object controller Environment StruxureWare Building Operation FB Program at site Cause When commissioning the local node with a LNS tools (NL220), one cannot see the functional blocks as object controller in the LNS tool, but rather have all the SNVT in the static node. Is it normal? The problem is, if one has a lot of SNVT, it is not clear. Resolution Functional blocks created do not have a functional block index to be able to present them correctly. All Functional blocks have same index causing the presentation issue mentioned above.

Issue Binding SNVT to AS-L  Environment StruxureWare Building Operation AS-L site Cause About the SNVT, when one binds a SNVT from the AS-L to the LNS network (nvo in AS-L), the AS-L doesn't propagate the value on the LON network. But, when binding a SNVT from the LNS to AS-L (nvi in AS-L) and when one changes the value, the AS-L receives it well and then can use the value in AS-L. Resolution The problem is that we “own the world” that is StruxureWare Building Operation owns the AS and Local Node, so we don’t know that we need to propagate something to someone. This really falls under design issues. A local node is typically only available for LNS network management tools and front ends. It seems this is not the design of the device to be used in another LNS network management tool since StruxureWare Building Operation and the AS-L is a LNS network management tool. Using two different tools complicates systems greatly since there should be only one.

Issue AS-L Loses LON Configuration Environment StruxureWare Building Operation LON environment Cause After commissioning the local node with a LNS tool and if one switches off the power supply of the AS-L, the local node loses the LON configuration and it return in factory configuration 'Domain 18 Subnet 1 node 254'. Now you can just change the domain.  Resolution It seems the local node updates the domain if the domain is updated from LNS. So if you do a Local Node commission than the LNS will not work and if you commission it from LNS local node is not going to update the domain. This really falls under design issues. A local node is typically only available for LNS network management tools and front ends. It seems it is not the design of the device to be used in another LNS network management tool since StruxureWare Building Operation and the AS-L is a LNS network management tool. Using two different tools complicates systems greatly since there should be only one.

Issue Using the RD and TD LEDs to help commission and Fault finding a Modbus RTU Continuum Xdriver Using the RX and TX LEDs to help commission and Fault finding a Modbus RTU AS, AS-P, AS-B Product Line Building Operation Automation Server Premium Continuum bCX4040 (BACnet) Environment Continuum Automation server Cause How to use the TD RD(TX RX) LEDs to help commission or check an installation Resolution Continuum The Comm Port LEDs on a net controller can be helpful when first setting up or fault finding an Xdriver (ModbusRTU) Every time the net controller transmits the TD LED will flash and every time another device on the bus transmits (such that the net controller can receive it) the RD LED will flash. Thus if Xdriver seems not to be working correctly this is often the first thing to check A simple check with Modbus RTU would be to stop any automatic polling on the network, then manually refresh a modbus point and watch for a single Transmit (TD) followed by a Receive (RD). SmartStruxure The Comm Port LEDs on an AS controller can be helpful when first setting up or fault finding ModbusRTU Every time the AS transmits the TX LED will flash and every time another device on the bus transmits (such that the AS can receive it) the RX LED will flash. A simple check with Modbus RTU is to create only a  single device (or inhibit polling to all but one device) and watch for a single Transmit (TX) followed by a Receive (RX). Modbus Simulation Another useful technique when commissioning or troubleshooting with Modbus is to simulation software on a PC (with RS232/485 convertor for RTU if required). A Slave device or the Master node can be simulated eg ModSim, ModScan, ModbusSlave, ModbusPoll, Mod_RSsim

Issue Need to be able to read and write to a point. Environment StruxureWare Building Operation Workstation ES AS Cause Need to be able to read and write to a point. Resolution Declare the point as Output and bind it. Outputs can be read and written.

Issue Updating firmware from StruxureWare Building Operation and the still be usable with other BMS such as Continuum, I/A Series, I/NET, Sigma, and Vista Environment Site with more than one Building Management System  Cause Implications of updating firmware on a controller from the StruxureWare Building Operation side and still compatible with existing Resolution For the controllers available on the StruxureWare Building Operation network that have been configured, take precaution when updating the firmware and still expect compatibility with other systems. For example, at a Continuum site, with a b3 and the option to update of firmware from StruxureWare Building Operation, there are a couple of things to keep in mind. When selecting the b3, and the Update Firmware, it will ask you for the *.udp file. This can be downloaded from the extranet. The thing to keep in mind here is if you are using this controller in conjunction with Continuum, then pay particular attention to the Compatibility Matrix and the firmware which is compatible with the version of Continuum you are running. Updating a firmware that is not in line with the version of Continuum will create problems for the site. So when selecting the firmware *.udp, be sure of which firmware file you are selecting. The operating system in the b3 controller is no different between StruxureWare Building Operation and Continuum. The PE code may be different though, so he should be able to learn these controllers into Continuum as long as they have their user memory cleared out.  

Issue Audible alarms and the DefaultAlarmView vs. new workspace with new alarmview Environment StruxureWare Building Operation site Cause Audible alarms and alarmview, Using the predefined alarmview we get the audible alert for this alarm. Create a new workspace with an alarmpane with a self defined alarmview we do not get the audible alert. Steps to reproduce problem: I created a digital value and one alarm connected with this digital value. I the settings of this alarm I checked the box audible. Then created a new alarmview without any filter. I created a new workspace (named ws01) with a system tree and one alarmpane. For the alarmpane I selected my created alarmview. Selected the workspace Engineering and triggered the alarm. Expected result: Alarm is in the alarmview Audible alarm This works Then logout of the workstation and login again. Now using the workspace ws01: trigger the alarm Expected: Alarm is in the alarmview Audible alarm Actual result: Alarm is in the alarmview No audible alarm.   Resolution Audible alert, works only in the DefaultAlarmView. Expected fix to be in 1.3 release of StruxureWare Building Operation. Work-around: None known

Issue WorkPlace Tech version 5.7.2 menus do not appear when the StruxureWare Building Operation workstation is installed on the same computer. Environment Computer with both WorkPlace Tech version 5.7.2 and StruxureWare Building Operation workstation installed. Cause WorkPlace Tech 5.8.2 and later support coexistence with SmartStruxure. Resolution Install WorkPlace Tech 5.8.2 or later. The proper procedure for performing this upgrade is: Uninstall StruxureWare Building Operation Install the latest version of the WorkPlace Tech Tool software. Reinstall Building Operation.

Issue Can we integrate 3rd party LON devices Environment StruxureWare Building Operation AS or Enterprise Server Cause Integrating third part LON devices allows the system to take full advantage of the open protocol. Resolution We currently support 3rd party Lon devices in Version 1.0 and 1.1, but some large devices are too big to be configured in quantities according to specifications. No major change regarding this is scheduled until earliest 1.4. In 1.3 we will change the numbers that we support to configure but this will mainly be runtime improvements. Some devices can only be configured with Lonmaker which is an extra step during the engineering process.

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

Issue Which products have been independently assessed by the BACnet International BTL labs? Environment BACnet approvals BACnet Building Controller (B-BC) BACnet Advanced Application Controller (B-AAC) BACnet Application Specific Controller (B-ASC) Other BACnet Device (B-Oth)  Cause The Continuum & I/A Datasheets define that the products are BTL approved, but where can more information be obtained? Resolution Go to the independent BACnet International BACnet Testing Laboratories web site and select Schneider Electric, This shows all of our BACnet approved products and will answer many typical BACnet related questions. See link:  http://www.bacnetinternational.net/btl/

Issue How long can the power to AS be interrupted Product Line EcoStruxure Building Operation Environment PS Power Supply Automation Server Cause Question regarding the AS and the power supply module. If the power is interrupted from the 24VAC power supply for say, 100 milliseconds, will the power to the AS be interrupted? There is a cold cap in the PS, and how long does it maintain power supplied to the AS? What about the RTC?   Resolution The power to the AS will be interrupted if there is a 100mS main power fail. The AS will then save the server cache. When the power returns the AS will make a restart that will take approx. 2 minutes. The AS Power supply fully complies with the IEC 61000-4-11 standard and can withstand voltage dips, with a 20mS dip and a 0% residual voltage.  The Power-fail process: When the AS loses power the super-cap keeps the AS alive for 15 seconds. 10 seconds of it dedicated to power-fail process to flush all the data that that are currently in the RAM to the SD card(That data can be anything with any value they have before power-fail). When power comes back that data is retained and are stored in appropriate place on the SD card. Real-Time-Clock(RTC) is maintained when the AS loses power by a dedicated capacitor which backs up the RTC chip for a minimum of 30 days in the absence of power since there is no battery in the AS.    

Issue When any LON device is power cycled the nvi values will change to invalid / null / last changed / default value.   Environment LON Devices Cause Using the device for the first time or after re-flashing the firmware. Power cycling the device. Resolution If nvi has any binding it receives the value from source nvo. If nvi does not have the binding then manually set the value. If nvi is a multistate SNVT it returns to default value.

Issue The reports installation completes without error but Reporting Agent service never gets installed. Without the Reporting Agent service, reports will not collect data and the WebReports login page will not load in a browser. Environment StruxureWare Building Operation WebReports, version 1.1 Cause Error in installation files Resolution The workaround for this issue is as follows: Ensure that in Windows, the Folder Options are configured to show hidden files, file extensions, and protected operating system files. Open Windows Explorer, navigate to the C:\Program Files\Schneider Electric\StruxureWareReports\StruxureWare Reporting Agent directory, and edit StruxureWareReportingAgentInstall.bat. Remove the "%1\" from the first two lines so that it simply reads: installutil.exe SE.WebReports.StruxureWareReportingAgent.exe regedit /s StruxureWareReportingAgent.reg pause   Save the file and exit. Edit the config file, SE.WebReports.StruxureWareReportingAgent.exe.config. Find the section with the following line: Note: They will appear without the "." after the "<" <.add key="uid" value="appuser"> Copy & paste the above line just below it , then edit the copied line so that it reads: <.add key="ServiceName" value="StruxureWare Reporting Agent"> When finished, the two lines should read: <.add key="uid" value="appuser"> <.add key="ServiceName" value="StruxureWare Reporting Agent">   Save the config file and exit. Run the batch file StruxureWareReportingAgentInstall.bat.

Issue Linux source code is public source Environment StruxureWare Building Operation AS Cause Provide source code for AS Linux operating system. Resolution Software License Notices This product contains code that is covered by the GNU General Public License (GPL). In accordance with the GPL, you may request the relevant code for up to three years from the date of original purchase of this product. The code will be supplied on CD free of charge, though there will be a small fee to cover the cost of the CD, plus shipping and handling. For further information on the GNU GPL licenses, please visit http://www.gnu.org/licenses and, for the complete GPL texts, http://www.gnu.org/licenses/gpl-2.0.txt and http://www.gnu.org/licenses/gpl-3.0.html To request a CD copy, please e-mail us at info@buildings.schneider-electric.com

Issue Can an AS or ES also send a SNVT to the bound device, even though the value itself hasn't been updated? Environment AS or ES with bound SNVT to send Cause Just to be clear, a TAC Xenta will send out a bound SNVT's value if it has been updated or by period. For the AS or ES, can it also send a SNVT to the bound device, even though the value itself hasn't been updated? Example: a SNVT_switch that is 100,1... it then writes 100,1 again. Will the SNVT be send again, as it's actually updated, even though the value hasn't changed?  Resolution For devices it shall be send again in StruxureWare Building Operation 1.0 or 1.1. In StruxureWare Building Operation 1.3 is going to be send always.

Issue Support for LON "File based CPT products" Environment LON CP CPT SCPT UCPT Cause Downloads / Uploads to the Roombox LON, and other "File based CPT products" fail. Resolution The Roombox controller uses the File based CPT's, and StruxureWare Building Operation does not support this, this means that uploads / downloads will always fail. SCPT is an acronym for Standard Configuration Parameter (Types). UCPT is an acronym for Used (defined) Configuration Parameter (Types). CPT is an acronym for Configuration Parameters (Types). (Both SCPT and UCPT).   In the LonWorks technology it’s possible for the Vendor of the device, to implement these variables in three ways: As NV's (network variables) As “DMA type variables”, (meaning they just reside in the devices flash memory at known addresses) As “File Type” variables, (meaning they are located inside a logical file in the device)   StruxureWare Building Operation can handle type 1 and 2 above. But not type 3 at the current release (1.5)..   There is a fairly easy way to determine this, which is from the device’s XIF file. If the XIF file contains these variables, (or at least the two first), then the SCPT's / UCPT's in this device ARE implemented as File type variables, and StruxureWare Building Operation can’t handle them. nviFileReq nvoFileStat nviFilePos Most of the devices having this, are using Loytec’s chip, so typically this can be: Lvis, Linx and many gateways from Loytec., but there are other products to. These devices are not easily commission in StruxureWare Building Operation. However Product Support Services can assist you to edit the XIF file, so that the device can be commissioned. Note - The SCPT's / UCPT's will be removed from the device, so these will not be visible (and of course not changeable) from StruxureWare Building Operation. Access to NV's will be as normal.