Building Automation Knowledge Base

Issue As of EBO 4.0.1.86 it is not possible to bind to the "Restart" property of a b3/Infinet Script program Product Line EcoStruxure Building Operation Environment Building Operation - Continuum Interface Cause Unable to bind directly to the "Restart" property of b3 or Infinet Script program. Resolution While the issue may be resolved in a future version of EBO there is a simple workaround. The workaround consists of binding via an intermediate value object.   EXAMPLE: A b3/i2 program (MasterProg) needs to run a second b3/i2 program (SlaveProg).   Create a digital value in the device (ProgReStart), Instead of binding in MasterProg directly to the Restart property of SlaveProg, bind to the value of digital value ProgReStart, then bind the value of ProgReStart to the Restart property of SlaveProg.   Here are the resulting bindings for the intermediate value object (ProgReStart)     The sequence will then be as follows: 1. When MasterProg needs to run SlaveProg, it sets its output binding (bound to the value of ProgReStart) to 1. 2. Upon a change in its value from 0 to 1, ProgReStart will then set the Restart property of SlaveProg to 1 causing it to run.   NOTES 1. Do not use Active/Inactive, it won't work, must use 1/0 instead. 2. MasterProg will need to reset ProgReStart to 0 before running SlaveProg a second time

Issue Third Party MSTP controllers are not able to be discovered. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Automation Server (AS) 3rd party controllers Cause MAC address of the Automation Server's MSTP Network was not configured properly. Under the AS > BACnet Interface > MSTP Network the MAC address is changed from the default value of 0.  Resolution Change the MSTP Network MAC address from the erroneous value back to 0 and third party controllers will be discovered properly.

Issue While using a demo license, the system is unable to connect to the Building Advisor Cloud Product Line EcoStruxure Building Advisor Environment Building Operation Enterprise Central 3.0 or later Building Operation Enterprise Server 3.0 or later Building Operation Automation Server Premium 3.0 or later Building Operation Building Advisor Portal Cause The Demo License of EBO does not contain the Cloud Connectivity feature. If the original system was registered in 2.0 and running on a demo license, once it is upgraded to 3.0 the Cloud connectivity will be lost. Resolution Enterprise Server and Enterprise Central Customers using an Enterprise Server or Enterprise Central must install a valid license to connect to the Building Adviser Cloud.   AS-P and AS-B Cloud Connectivity is only supported in versions 3.0.x or later. When running in a Stand-Alone configuration, the AS-P and AS-B do not require a separate license for Cloud Connectivity.

Issue Is it possible to print alarms automatically with SBO Workstation in matrix printer whenever there is an alarm? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause A number of sites still prefer to directly connect a Dot Matrix Printer to their BMS to automatically print off incoming alarms rather than using more modern emailing of alarms available from EBO. Resolution The following File2Printer software has been made freely available on the EcoStruxure Building Operation Community for exactly this purpose. https://community.se.com/t5/EcoStruxure-Building-Operation/File2Printer/m-p/351127#M71948

Issue Is it possible to get a XIF from Lonmaker when you have commissioned it by "upload" from device? Product Line TAC Vista Environment TAC Vista Toolpack TAC Vista Server LonMaker Cause If you don't have the XIF you can upload from the device in Lonmaker. Resolution There is no way to get the XIF from LonMaker but the system plug-in will create a new XIF when you add the device to the TAC Vista db. Refer to SNVTs, SCPTs, or Module Names are missing from Vista after device is added to database from System Plug-in. Compare XIF stored in Vista for instructions on how to locate the XIF generated by the system plugin.

Issue What date was the DMS product no longer available?  Is there supportive documentation of the announcement? Environment DMS Cause Documentation required for an end customer's request Resolution The DMS product line was no longer for sale on April 1, 2005. Click to view Announcement 05-016.

Issue Unable to access ES or AS after setting a new Domain as the default domain Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause If you set a domain as a default domain before logging in through that domain, it is possible that you do not have users set up and therefore will be locked out of the system. Resolution Open Building Operation Workstation Enter a Username and password for the Local domain or another previously functional domain Set the Domain as "Local", please note that this is case sensitive. Select the correct Server Log in Change the default domain back to Local until you have successfully logged in using the new domain.

Issue How to estimate the disk space required to accommodate a given Security Expert installation. Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Security Expert databases will grow in size depending on the configuration and logging requirements. Therefore, estimating how much a database will grow over time should be done to determine which Microsoft Database solution and hard drive requirements. Resolution The Installation Guide does have some hardware recommendations under the System Requirements section, and these should be used as a baseline for allowing appropriate database storage. 10 controllers w/ 16 modules each - 40GB More than 10 controllers w/ any number of modules each - 100GB. The configuration database (SecurityExpert) is relatively small and will typically not grow much. The events database (SecurityExpertEvents) is what logs all events and alarms, and it will grow over time, rapidly depending on what is being logged and how often. There are many variables in play from one site to another. The space required for a standard Security Expert Database is dependent on, but not exclusive to: The amount of Inputs/Outputs/Readers you have with Log Events enabled. The amount of traffic through the site. The number of Expanders and other Records. The frequency of backups and purging of events from the SecurityExpertEvents database. As a guideline, we can broadly calculate storage requirements based on the size of each event being logged. Typically this will be 564 bytes per event. If you have 2000 Events per day, here is the calculation for how many MB will be used per day: 564 B x 2000 = 1128000 B = 1.07 MB per day If those events that are being logged are alarms as well, then this total would be doubled. Another way to calculate this is to take what a typical usage requirement would be for a site or monitor a live site over a week/month to calculate the sites' average usage and extrapolate that to fit. For example, a site with 130 doors being used 8 hours a day and with door openings and closings 10 times an hour would equate to just under 1GB a month. Please note these are very rough guesses; individual sites might be busier/quieter. Performing regular SecurityExpertEvents database backups and purges will ensure that the database size does not get too large for the installation. For instructions, see the System Backups section in the Installation Guide and AN 279 Security Expert Differential Backups.

Issue Valid Users are randomly unable to gain access when presenting at a Suprema biometric reader. Sometimes they are able to gain access but others they are not and see user denied events in the events window. User denied entry by entry mode error door mode is not correctly programmed using invalid reading device User Denied Event Product Line EcoStruxure Security Expert Environment Security Expert Suprema BioEntry W2 fingerprint reader Cause The sensitivity settings in the Suprema software are too sensitive resulting in missed fingerprint reads. Resolution Reducing the fingerprint sensitivity from the default setting of 7 to a setting of 5 may allow fingerprints to be read more reliably.   The sequence used to authenticate the User can also result in more frequent read failures. Presenting a valid card then an invalid (or bad read) fingerprint and then presenting the card again,  the sequence starts all over again and will result in a user denied event. If the user presents the correct finger (after presenting the wrong finger) or tries the same finger again within the configured timeframe they will be granted access.

Issue Webstation closes by itself Environment Webstation  Internet Explorer 9 32bit Cause Vista webstation and TGML do have some compatibility issues with Internet Explorer 32 bit that can cause the webstation to log out itself or even close down when login in. Also a Internet Explorer 32 bit needs to have Java 32 bit installed. On a 64 bit machine if you want to run 32 bit make sure the Java 32 bit client is installed. A normal error to see when those happen is:  --- A fatal error has been detected by the Java Runtime Environment: EXCEPTION_ACCESS_VIOLATION (0xc0000005) --- Resolution Following workarounds have been confirmed to help.  Enable the compatibility view in Internet Explorer 9 Upgrade to Internet Explorer 10  Make sure you have Java 32 bit installed.  Use Internet Explorer 64 bit

Issue TAC Vista to SmartStruxure Interface does not connect in non-English Operation System Environment TAC Vista SmartStruxure Solution TAC Vista SmartStruxure Interface 1.0 TAC Vista 5.1.8 non-English Operation System Cause The Format setting to non-English will cause this issue. Resolution In the Windows Control Panel, select Region and Language. On the formats tab change the format to English. Click Apply. Vista 5.1.9 will fix this. For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure.

Issue Even though the curve block is set to range between 0-100, the block just stays at a fixed output somewhere in the curve output range. Product Line TAC Vista Environment Vista Workstation Cause The curve requires the first entry of the X value to be the lowest value, and then the subsequent values to be larger than the previous X entry. Resolution Adjust the order of the XY entries on the curve block so the first entry in the X will be the lowest value. Example of Incorrect Curve Here is an example of a Curve that will not work. Note the first X entry is -2 and the last X entry is -6.  Example of Correct Curve To correct this curve, -6 is the lower number, so this should be the first X entry. Here is an example of the curve that has the correct X entry order.

Issue RP-C address dial is difficult to see in poor light Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RP-C) Cause The controller modbus address setting dial is difficult to see in poor light conditions. Resolution By default, the dial is set to address '1' (there is a small arrow on the cross head dial) and the dial is numbered 1....9,0 clockwise.

Issue Xdriver is enabled,   Open the BCX1 editor, click "options" tag, display comm port attribute as"Xdriver comm1: 00000009", but there is no "xdriver" listed from the drop down menu when click the arrow on the right of default type of the comm port. Product Line Andover Continuum Environment BCX1-CR-X, 4.500065 Cyberstation 1.81 Cause Continuum support xdriver with BCX1-CR(BCX4040) from 1.82, any version earlier than 1.82 not support xdriver with BCX1-CR controller. Resolution Upgrade all the Cyberstation to 1.9X. To determine if a controller comm port is Xdriver enabled, refer to Determine if a controller comm port is Xdriver enabled.

Issue Troubleshooting 4417 DEVICE_ERR_NOADDR_I2C errors seen in Controller's Error Log. Environment Continuum Controllers Cause 0x00004417 0x00002100 0x021046e2 0x00080002 0x000000200x00004417 0x00002100 0x021046e2 0x00080002 0x00000020 "DEVICE_ERR_NOADDR_I2C" errors are related to the internal bus to the peripherals and RealTimeClock.   DEVICE_ERR_NOADDR_I2C       (no address response)      “DEVICE_ERR_NOADDR_I2C” errors are not I2 errors they are I2C errors. These errors are related to the internal bus to the peripherals (like an onboard RealTimeClock or the expansion bus (modules)).   There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module. Resolution Possible causes can be:   1. A defect with the onboard RealTimeClock. Check for 4417 errors followed by TimeSync errors and/or indications that the time clock is not stable similar to the following error lines.   01/01/1989 00:00:00.00 0x00004417 DEVICE_ERR_NOADDR_I2C (no address response) 01/01/1989 00:00:00.00 0x00010000 Clock change   2. An issue with the expansion bus modules. There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module.

Issue I have an Andover system that I need help with... Can you assist me with my Andover Continuum systems? I have an Andover alarm panel that got wiped out; what is the default IP address? Environment Andover Continuum Cause Phone number and email are not available online. Resolution To contact Schneider Electric for Andover Continuum system support, please visit the Contact Product Support page.

Issue How to bring an MPM-VA online over ZigBee to communicate with the ZigBee Coordinator (which is also the MPM you have your IP interface with). Environment MPM, MPM-VA, ZigBee Cause Cannot figure out how to get the MPM-VA to communicate over ZigBee to the Coordinator. Resolution Use web interface on the bench to set up ZigBee Pro Extended Configuration on the "remote MPM-VA" to match the Coordinator's Channel, PAN ID, Extended Network ID, Stack Profile, Security Profile and Trust Center Link. Save settings and save database to flash. You can now disconnect the IP connection to the remote MPM-VA. Re-discover controllers from the Coordinator MPM. It will appear as a "peer" below the coordinator, i.e., it will not be "under it" like a Room Controller (stat) or TE2.  

Issue What camera conditions does Continuum support being shown as a Continuum alarm? Product Line Andover Continuum, Pelco Environment Continuum v2.0 Pelco Video Server Digital Sentry Endura Cause Available documentation is a bit bare on specifically what camera conditions can be monitored / setup to be displayed as alarms in Continuum. Resolution According to the latest Video Compatibility Matrix, only the following video alarms are supported: Video server online/offline Camera video loss (cable connection loss only, not covering of camera lens) Motion detection (per camera) Note: Video loss and motion alarm functionality are not supported on DVX and DVXi Video Servers.

Issue When SE7000/SE8000 Series Room Controllers are bound to the MPM via ZigBee, "Effective Occupancy" does not follow "Occupancy Command" if the COV box is checked. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment SSL MPM SSL SE8000 SSL SE7000 Cause Data type mismatch Resolution Uncheck the COV box for Effective Occupancy

Issue After configuring a BACnet Schedule in a BCX or a b3 controller, it goes into Fault with its Reliability field showing "ConfigurationError". Environment CyberStation WebClient BCX40xx b3 BACnet Schedule Object Cause Configuration of BACnet schedule Incorrect point type used to configure BACnet schedule Resolution For each object type within BACnet (input, numeric, trendlog, etc.) each object property identifier (property) has an associated data type.  A list of data types for the each property can be found in Chapter 12 of the BACnet spec under the section for each object type.  The correct data type to configure in the schedule is determined by the Object property that is being controlled by the schedule object.  When using a schedule to control the value of a BinaryInput, BinaryOutput and BinaryValue objects, the Data Type that should be used is Enumerated. When using a schedule to control the value of a AnalogInput, AnalogOutput and AnalogValue objects, the Data Type that should be used is Real. When using a schedule to control the value of a MultiStateInput, MultiStateOutput and MultiStateValue objects, the Data Type that should be used is Unsigned Integer The Schedule object can be tricky to configure, however. There are several properties (Weekly_Schedule, Exception_Schedule, Schedule_Default) that must contain the same data type for all events. Since Enumerated is the “default” data type, the user may need to manually remove any existing events with the Enumerated type and replace them with the desired data type. If while configuring the schedule a message similar to the one above is displayed and accepted  all the events MUST be deleted otherwise a configuration error will result.