Building Automation Knowledge Base

Issue Communications with an AS can fail due to high CPU usage and it goes offline in the ES.  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium(AS-P) Building Operation Automation Server(AS) Cause A large graphic was being edited and when saved, the AS appeared to crash, but had actually gone offline to the ES. Resolution This issue was due to the AS CPU usage, which was found to be very high and was making the AS appear to be offline to the ES, when the graphic was saved. The graphic that was being edited was accessing a large number of Universal Inputs, and these input values were changing frequently, this in turn was causing the increased CPU usage. Changing the threshold setting of a Universal Inputs. Select the properties of the universal input to be adjusted. View the configuration section and select the threshold value. Enter an appropriate value for the input being modified.  

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 Information needed about how to change the "appuser" password used by the Report Server Agent Product Line EcoStruxure Building Operation Environment Web Reports Cause There is no information available on whether the Web Reports "appuser" account password can be changed and how it's done Resolution NOTE: Refer to the following article Report Server "appuser" clarification for additional information on the appuser   The password defined for the user in the configuration file needs to match the actual password in the operating system. To change the password, do the following   Stop the WebReports Agent service Change the password defined for the "appuser" in Windows Change the password defined for the "appuser" in the WebReports Agent config file: C:\Program Files (x86)\Schneider Electric\StruxureWareReports\StruxureWare Reporting Agent\SE.WebReports.StruxureWareReportingAgent.exe.config Restart the WebReports Agent service

  Issue Schedule a meeting on a day when the site will be closed early. Steps are needed to ensure a door can be configured for 'card only' mode for the meeting. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause At times it's necessary to schedule a meeting on a day when the site will be closed early. Steps are needed to ensure a door can be configured for 'card only' mode for the meeting and then revert back to the normal schedule or extend the meeting until the end of the standard schedule. Resolution Steps to configure a door(s) with a schedule using holidays and 2 T&Ps to temporarily place the door in Card Only mode and then revert back to the standard schedule. In this example, the standard schedule Unlocks the door from 8a-5p.   Create a Holiday (Early Meeting) for the meeting date and ensure a Holiday Group Membership is selected Configure a schedule(Leave Early) for the meeting date(s) and length of the meeting. Select the Holiday Group in this example named 'Early Meeting Test' in the far right drop-down. The Holiday Group is needed for this to work. Note: The short-duration example was used while testing this multiple times a day. Configure a T&P (Early Meeting TP) to temporarily change the reader mode to 'Card Only' using the schedule (Leave Early). Select the Leave Early schedule and the 'Schedule-Became-Active' Event, the reader mode and the reader(s). The "Indefinite" duration drop-down selection worked. The other drop-down options did not work for this schedule implementation. Configure a T&P (Early Meeting Cancel) to cancel the Temporary Reader mode and revert control back to the standard schedule and to Unlock the door. Select the Leave Early schedule and the 'Schedule-Became-Inactive' Event, the reader mode and the reader(s). Extend the meeting to the end of the standard schedule if needed to keep it in card-only mode. Testing Results: At 3:55p the Leave Early meeting schedule became active and the TP changed the reader mode to card only. * Please disregard the Door held open highlights in the following snapshots At 4:00p the Leave Early meeting schedule became inactive and the TP canceled the temporary reader mode. The door Unlocked in this example after control was handed back to the standard schedule.

Issue Enterprise Server will not start due to no valid license file error: "nsp.csc.licensemanager No valid Enterprise Server license found. Terminating server." or Cannot find license file. (Error code: -1) Product Line EcoStruxure Building Operation Environment Building Operation Software Administrator Building Operation License Administrator Building Operation Workstation Cause Enterprise Server is not started and states no valid license file is found. License Server is installed on the same computer and has valid license(s). Similarly, WorkStation may not start even with a License Server installed with a valid license. If you get error -1, it means that you didn't enter the required @ before the license server address. Resolution In general, any licensed Building Operation software (Enterprise Server, WorkStation, Editors) needs to know where the license server is located. That means that the license server path needs to be entered on any PC having licensed Building Operation software installed. The "License Administrator" part of the license installer can be installed on any PC, and the license server address set using the administrator. The license server itself does not need to be installed on all PC's, but only on the PC hosting e.g. the Enterprise Server. The IP or DNS name of the PC hosting the license server is entered with an initial @, e.g. if the IP of the license server PC is 1.2.3.4 you enter @1.2.3.4 Checkpoints Remember to enter the license server address starting with a @. For example, don't use "localhost" but "@localhost". Is your evaluation license current? If not, download from EcoXpert Extranet Check that antivirus software is configured to allow the operation of the license server. (refer to SmartStruxure Workstation or editors can't get license when using firewall (errors -15 or -96)) Reboot the machine where the License Server is running. It has been observed in some cases where the error 'No valid license or Cannot find license file error' appeared after an upgrade that rebooting the machine solves the problem. Check to see if there are multiple versions of the License Server installed on the machine. If multiple versions are installed, make sure to only run the highest installed version as a Windows Service. All other License Server and License Administrator software should be uninstalled from the machine.

Issue With Script Programs in Continuum we were able to check the variable time against an integer value. Like "if time>500 then...".  In StruxureWare Building Operation time is of the type datetime, no longer an integer. Product Line EcoStruxure Building Operation Environment Script Program Cause In StruxureWare Building Operation a datetime internally is now a 64 bit number, so dates can go beyond the year 2038 which was the top limit for Continuum.  Numbers in script for StruxureWare, like in Continuum are just floats ( 32 bits ) so when trying to map a 64 bit number ( the date ) into a float it is not going to work.  You will get very erroneous readings, therefore the ban. Resolution Here are some examples of the correct StruxureWare program: Remember that for the dates, you can only compare dates to dates, not dates to numbers… In general,   you CAN do the following:       compare dates to dates                ==>   if Date1 > Date2  then     add numbers to dates                   ==>    LaterDate = LastDate + 24*3600     subtract numbers from dates         ==>    EarlierDate = LastDate - 24*3600   you CANNOT do the following   compare dates to numbers                ==>   if Date1 > 500  then

Issue The License Server does not start automatically when the server reboots. Product Line EcoStruxure Building Operation Environment Building Operation Licensing Cause The License server is attempting to start before some dependent process has started. Resolution To edit the FlexNet Service go to Control Panel > Administrative Tools > Services Right click on FlexNet Licensing Service and FlexNet Licensing Service 64  and select Properties. Change the Startup Type from Automatic to Automatic (Delayed Start)

Issue Need more than 50000 registers in a Modbus device Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Modbus specification sets a limit of 65535 as the largest register number. Resolution Enter the value into the Register number configuration property. The Modbus specification sets a limit of 65535 as the largest register number.

Issue Does the Niagara R2 Modbus driver support a 6-digit address format? Product Line TAC IA Series Environment Niagara R2 Modbus driver Cause Modbus 6 digit addressing is not supported when using modbus format in the driver. Resolution The six-digit address format and the five-digit format are just two different notations for the same thing - there is no difference in the protocol. For example, the first one thousand holding registers are normally represented as: (modbus) 40001 to 49999 -or- (decimal) 0 to 9998 -or- (hex) 0 to 270E When using modbus format in the driver, the left most digit, '4' in this example, is part of a convention that indicates the 'type' of point and, when using that convention, the point type does not have to be specified.  For example, for modbus point 40001 the '4' indicates that it is a holding register. But there are actually 64000 holding registers available and, using the common 5-digit modbus notation, it is not possible to specify more than 9999 of them. The six digit convention just moves this 'type' digit one space to the left. In this six-digit notation, the first one thousand holding registers would be 400001 to 409999. This 6-digit convention for 'modbus' formatted addressing is not supported but it is still possible to use decimal or hex notation to specify these addresses with Niagara R2. When 'modbus' formatted addresses are used, the driver subtracts 1 from the entered address, since modbus uses base 1 formatting and decimal uses base 0.  When using decimal or hex, the leading digit is dropped and subtract one from the register value and optionally convert to hex and use that as the point address. For example, to read data from register address = 422202 Drop the leading character = 22202 Subtract 1 = Decimal address 22201 or hex address 56B9

Issue Unable to find the latest firmware for ADv3 in EcoXpert Extranet Product Line EcoStruxure Building Operation Environment Advanced Display v3 (ADv3) Cause The firmware is not publicly posted since the process to load the firmware should not be attempted without guidance from Product Support. Resolution All customers must to open a support case to receive fixes or enhancements.

Issue How to setup and use the Plain English Alarm function?   Product Line Andover Continuum   Environment PEAlmFunction, PERtnFunction CyberStation Alarm Workstation PE function Cause Manual configuration is required to create the Plain English alarm function and set certain registry keys.   Resolution As a function of Continuum CyberStation Alarm Engine, user written Plain English functions are automatically invoked at a workstation when an alarm occurs when an alarm is acknowledged when a return-to-normal condition occurs. The user optionally specifies the names of those functions in the Windows registry, and they will be called appropriately. Registry keys used for calling Plain English Alarm function PEAlmFunction : The name of the user-defined PE Alarm Function. (Ex. “AlmProcess”) PERtnfunction : The name of the user-defined PE Return-to-Normal Function. (Ex. ”AlmProcess”) Example of the Plain English Alarm function is as follows: Arg 1 A ' Network AliasName(16) Arg 2 B ' Controller AliasName(16) Arg 3 C ' Infinet Controller AliasName(16) Arg 4 D ' Object name(32) Arg 5 E ' Object AliasName(16) Arg 6 F ' Object Description(32) Arg 7 G ' Object Value(Numeric) Arg 8 H ' Alarm State(3) ALM,RTN,ACK Arg 9 I ' Graphic Object AliasName(16) Arg 10 J ' Alarm Enrollment Alarm Message(String) Arg 11 K ' Alarm Enrollment AliasName(16) Arg 12 L ' EventNotification AliasName(16) Arg 13 M ' EventNotification Priority (Numeric 1~255) Arg 14 N ' TimeStamp(16) Arg 15 O 'Logging Flag (1~255) ' String 1 Q String 80 AlmDir, Fnam File AlmF ' If M < 100 then AlmDir = "C:\" Q = chr(96) Fnam = NumToStr(random(Second)) OpenFile(AlmDir ; Fnam ; ".alm", WriteOnly, AlmF) Print L ;", " ; K ; ", " ; A , B , C , D , ", " ; G to AlmF CloseFile(AlmF) Endif Return Success Create the following registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls \Continuum\Settings: PEAckFunction (REG_SZ) PEAlmFunction (REG_SZ) PERtnFunction (REG_SZ) PEMaxBufferedAlarms (REG_DWORD) PEPopAlarm (REG_DWORD) Set PEAlmFunction to “AlmProcess” Set PERtnFunction to “RtnProcess” Restart Continuum. Create PE programs in the workstation called AlmProcess, and RtnProcess with source code similar to the example function. Files will be created in the specified directory containing the alarm and return to normal information.

Issue A new Automation Server won't load in Device Administrator versions earlier than EBO 2022. A "Failed to process USB connection event for DevicePath:\\?" error is shown when adding the device.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server AS-P with Secure Boot Building Operation Automation Server AS-B Scalable Cause Secure Boot/Scalable Automation Server hardware is not supported in EBO versions prior to EBO 2022. Resolution It is not possible to install EBO versions prior to EBO 2022 in Secure Boot/Scalable Automation Server hardware. Verify the Automation Server part number to ensure it is a non-scalable/non-secure boot version. Refer to the Part Number and Hardware and Software Matrix for a list of parts numbers and their associated EBO version compatibility.

Issue Opening and running a Seven Report that uses the Calendar to define the date range feature for data after entering the values, and nothing happens. It does not pull up any data. Business Objects error is seen in the Calendar picker.  Product Line TAC INET Environment I/NET Seven revision 2.31 and higher. Seven Reports (Crystal Reports) Cause Crystal Reports has not been set up correctly on the host PC. An additional file has to be installed to handle scripts in Seven Reports. This file can be found under >Support>Sevenreport/CR_XI/PostCRSetup on the INET CD.  A read me is also located there to assist with the installation procedure: Resolution To resolve this issue, the following steps need to be implemented: Close I/NET and I/O Server Open up Windows Explorer and select the original CD Open up the Support Folder and expand it Select the CR-XI folder and run the SetupCrystalReportsXI.exe Once completed, go back into the folder again and run the Post CRSetup.exe Once this is completed, restart I/Net and I/O Servers again Open up Seven Reports again and run the associated report

Issue When using Microsoft Vista and IE 8, the calendar picker pops up a window but does not show the calendar. Product Line TAC INET Environment I/NET Seven 2.40 Microsoft Vista Internet Explorer 8 Cause Security of Internet Explorer Resolution Go to the Internet Options, Security Tab, and disable the protected mode for the Internet.

Issue Crystal Reports with I/NET 2.41 and higher Design tab is no longer available (missing) within SevenReports. Can no longer edit Crystal (Seven) Reports Product Line TAC INET Environment SevenReports (Crystal Reports) with I/NET 2.41 and higher Cause I/NET will no longer have the "Crystal Reports" Modify and Design license after May 2012. After 2.41 you must buy a separate CD for this function. Upgrades are not affected by this change. Any SAP Crystal Reports licenses used at existing installations will remain active after an upgrade. Resolution RDC version will no longer be supplied on the I/Net CD.   The NON_RDC version will still allow reports to be Viewed and Printed, as always. Modifying a "Canned" report or designing a "New" report will be impossible unless the new RDC version is installed.   This removal of the Crystal report function will start with I/Net Seven rev 2.41A and beyond.   To receive the Crystal Reports application files and license certificate, the SEVEN-REPORTS-RDC part will need to be ordered in addition to the standard I/NET SEVEN software part for each workstation requiring SAP Crystal Reports. Refer to Unable to install the RDC version for additional information and a copy of the necessary software for upgrading and installing this software.   Upgrades (from I/NET Seven Version 2.21 and above) are unaffected by this change. Any SAP Crystal Reports licenses in use at existing installations will still be active after an upgrade as long as you perform an upgrade of the existing I/NET installation.  If you perform a clean install, so you have uninstalled the previous version of I/NET, you will lose this licensing.      

Issue Unable to install the RDR version of the software.  Unable to find the RDC version of Seven Reports Product Line TAC INET Environment I/NET version 2.40 and above. Cause The Seven Report file gets installed automatically for the NORDC and blocks the RDC install. Resolution To resolve this, the Seven Reports NORDC has to be removed, and the RDC has to be installed. To accomplish this, the following steps should be followed. Open up the Add/Remove Programs Go to Seven Reports NORDC and select Uninstall Now explore the RDC CD and find the SetupCrystalReportsXI_RDC.exe file Download the attached 7zip file Run the PostCRSetup.exe Once completed, open up Seven Reports, and the ability to Modify reports should be available.

Issue A BACnet Schedule is working but not changing the point it is controlling   Product Line Andover Continuum   Environment CyberStation Schedules BACnet command priority Cause A BACnet Schedule will by default, write to a BACnet point at a certain command priority level.  However if that BACnet point is also being commanded by a higher command priority then the present value of the point will not change according to the Schedule.   Resolution Example: A BACnet Binary value is created and the operator wishes to set the value to Off. If the value is set by a Manual Operator then by default this will command the point to Off at command priority 10. If a Schedule is then created and the point is attached to that Schedule, because a Schedule's default priority is 16, at the configured time, when the Schedule tries to change the point to On it can only command that point at command priority 16 The point itself always obeys the highest command priority which in this case is command priority 10 so the value stays Off.   To correct the above scenario there are two main options: Edit the Command Priority Tab of the BACnet Point and perform a Relinquish at command priority 10 to clear out that command, at which point the BACnet object will then defer to the next highest command priority (which in this case would be command priority 16) Edit the Schedule and change the command priority on the Schedule configuration page to an appropriately higher priority such as command priority 10.     NB. In cases where a point is written to at the same command priority as another object then the point will be controlled by whichever object wrote last...

Issue The reconfiguration of the log database (run from TAC Vista Server Setup) times out. Configuring the settings, for the first time after upgrading Vista, on the SQL server tab of TAC Vista Server Setup an then clicking on apply makes the following message appear: "Log database found but needs to be reconfigured. Reconfigure Log database?". After clicking yes the reconfiguring process starts, but times out. The message states the following:  Lock request time out period exceeded. (Microsoft SQL Server, Error: 1222) Environment TAC Vista 5.1.X SQL server  Cause The SQL server is busy. When a reconfigure of the database layout (or schema) is done, all connections to the database must be stopped to prevent corruption of data. If a number of applications/clients are trying to write data to the database, the request to lock the database will time out. Resolution Close the open connections to the database and try again. Generally speaking this shouldn't occur with just Vista running. It is when 3rd party clients access the SQL data directly that this problem can occur. To help identify the problem, the Activity monitor in SQL server management studio can be used.

Issue Automation Server CPU Specifications Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Basic Cause Automation Server Family CPU specifications are required for projects requirements and specifications. Resolution There are three Automation Server models, each with unique CPU specifications:   Automation Server (AS): The Automation Server (AS) has been withdrawn from sale. CPU: ATMEL AT91RM9200, ARM9 core microcontroller. Processor: ARM920T. CPU Clock Speed: 160 MHz. Automation Server Premium (AS-P): CPU: STMicroelectronics SPEAr1380, ARM Cortex-A9 dual-core microcontroller. Processor: ARM Cortex-A9. CPU Clock Speed: 500 MHz. Automation Server Bundled (AS-B): CPU: STMicroelectronics SPEAr320S, ARM926 core microcontroller. Processor: ARM926. CPU Clock Speed: 333 MHz.

Issue Can not save the Diagnostic Files from IP Controller using Building Commission Share button Product Line EcoStruxure Building Operation Environment Building Commission Cause By default, the only apps you can share are Mail and OneNote for Windows. Neither allows you to save a file to the Windows File System. Resolution Install Clipboard by Justin Chase via MS Store or link.  In Building Commission, navigate to the controller -> Device Settings -> Diagnostics Files Select either Device Report, Error Log, or Crash Report Click Share icon in the upper right corner.  Select Clipboard icon.  Click Copy button  Right-click Paste on the desktop or in File Explorer folder.

Issue How to set up a Mantrap Product Line TAC INET Environment I/NET Access Control Site Interlocked Doors Person Trap Anti-Passback (APB) Cause What is a mantrap? A mantrap is a security device that monitors and controls two or more interlocking doors to a small room that separates a non-secured area from a secured area. These interlocking doors allow only one door to be open at any time. What are interlocking doors? “Interlocking doors” is a security term used to describe how two or more doors are interfaced with each other and locked. Doors that are interlocked cannot be opened at the same time. Either door can be unlocked and opened as long as the other door is locked and closed and no other alarm condition exists. What types of locations require a mantrap? Mantraps are used at high-value or critical security areas where only authorized persons are allowed to enter. Typical areas include sensitive data processing areas, cash handling areas, critical research labs, security control rooms, and automated airline passenger entry portals. Why would my company consider a mantrap? Typically, security personnel are posted in high-security locations to control access into the area. An automatic mantrap used in this same location would control the access to the area, allowing security personnel resources to be available for other tasks. What is the difference between a mantrap and an interlocking door control system? Regarding controlling two doors within a vestibule, “mantrap” and “interlocking door controller” can be used interchangeably. Once the number of doors controlled by a single controller exceeds two, then the term interlocking door controller should be used. Resolution I/NET has three ways to do a mantrap: Event sequences and calculations -- limit to 5-7 SCUs per 7798C due to system loading Use a "standalone" third-party device that is wired to the door and is not attached to I/NET at all Use the interlock wiring diagram that uses relay logic to function. This is also part of the I/NET System. I/NET Seven allows configuring a door to have both an entry and an exit reader and uses the selection of Anti-pass back/Anti-tailgate to set up Zones or areas with stricter control over access. However, even with the Anti-pass back option set to Hard, which denies access to successive reads at the same reader, it does not prevent multiple persons from entering and exiting together, and it does not provide real-time accounting for the number of people in a Zone. Besides having a guard at the door, the usual method of implementing Zones does not prevent violations.   The example below presents some thoughts about improving the Zone's security in an I/NET Seven system. There needs to be a way to restrict the number of people gaining access to the door. There needs to be a way to keep up with how many people are in the Zone. One method to accomplish the first goal is to use a two-door egress system, as is often used in jails and similar security setups. For a medium security setup where the intent is not to prevent people from leaving, only one door needs a card reader. Such a design is illustrated below: Notes: Electric strike normally energized. Low walls or fences. The area should be small enough to limit how many people or things are in it at one time. Gate with normally de-energized bolt. The gate could swing both ways, so one would only have to push it to open it. It should have a spring to close it. The door “a” would have both an Entry and Exit reader, so an Anti-pass back/Anti-tailgate can be implemented. The strike on the door “a” would normally be energized and opened by a valid reader transaction.   The bolt on the gate would be normally de-energized, allowing the gate to open freely. When the strike on the door “a” is de-energized, the bolt on the gate would be energized, preventing the gate from opening. This is designed to allow only one person to simultaneously move into or out of the Zone.   An added level of security would be accomplished by mounting IR emitter/receiver pairs along the low wall or fence at regular intervals. A person would interrupt the light at a limited number of receivers, so if more than expected are interrupted, it would violate one person at a time, and necessary action could be taken.   If material needed to be moved through the door, the gated area could be made large enough to allow for a dolly or whatever might be needed. A different access level would be provided to those who are moving material, thus preventing the alarm for too many people going through the door.   This approach would restrict movement into and out of the Zone, and the example given in the AIC note could be implemented to allow real-time monitoring of occupancy levels in the Zone.   Design thoughts:   To calculate whether more than one person is in the gated area, sum the number of receivers that are detecting and compare it to a minimum, e.g., four of six must be detecting if only one person is in the area. If material is in the gated area, generate an alarm if an authorized card is not read. Use the alarm delay for the point to give an individual time to make a card read before sounding the alarm. The AIC scheme described in the AIC note would have to be duplicated for the material mover individuals to change the calculation of a person in the gated area. For material movers, the detection would be (sum of detectors < minimum), whereas for regular individuals, the detection would be (sum of detectors > minimum). Remember, the SLI connected to this door can have only 64 AIC’s and this door now has used 2 of them. Use an inter-card delay long enough to let the person exit the gated area before another card can be read. For personnel safety, there must be a way to de-energize the strike. One method would be to mount an emergency exit button located far enough away from the door so a single person could not reach it and a second emergency exit button on the outside of the Zone so someone could keep the strike de-energized until everyone is evacuated. Most codes probably require that all strikes be de-energized in case of smoke or similar emergency to provide another fail-safe.   Here is a pdf document which explains the setup using an SCU Click here to download third-party ManTrap information.