Building Automation Knowledge Base

Issue The extended trend log contains approximately 50% of the configured storage capacity. For example, only 250 entries are in the Trend log view even though the ETL is configured for 500 entries.   After the ETL runs long enough to fill up the 500 entry capacity, ONLY 250 entries are shown in a Trend log list view. (see below)   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause An extended trend log (ETL) includes an equal number of internal entries hidden from view; these entries are overhead incurred in the operation of the ETL. For example, each time a transfer takes place, an internal entry is added. Depending on the specifics of the configuration (i.e., Maximum Transfer Interval), the percentage of internal entries for a given ETL relative to its full size varies. From EBO 3.2.3, the internal entries of an ETL are hidden, and no information is provided to give any visibility into how much storage is being used by internal entries. Resolution The solution is to increase the size of the ETL to ensure there is enough storage capacity for data and overhead. Typically, the size must be doubled (in this case, 1000) in the particular ETL to make sure 500 entries of data can be stored.  Although these transfer events are hidden, it is possible to identify these events by adding the Sequence number column in the trend log list.  It is also possible to decrease the overhead amount stored in the ETL by increasing the "Maximum transfer interval" in the ETL properties, as shown in the screenshots.  Here it can be seen that by increasing the Maximum transfer interval to 1 hour for an interval log of 5 minutes that ONLY 1 'overhead' record (sequence # 565) is added per 10 entries.   Using this or a similar setting will allow to reduce the storage requirement of the ETL.

Issue Field Bus controller shows its version number as 0.000000. Learn controllers from comm port is very slow and fails when reloading the controller. Updating the firmware will not fix this problem. Product Line Andover Continuum Environment Cyberstation 1.74 above i2 controllers B3 controllers Cause There are many reasons that will cause the i2 and B3 controllers show their version number as 0.0000000 Wireless network enabled or Multi-Network card enabled on the machine. Database snatched from Flash RAM after power-cycle does not match to the Continuum Database Some controllers with special firmware (Such as B38XX-V with 4.501043) have points referenced by other controllers, this will make the source controller buffer to be full after more than 20 hours Unknown application software installed on the CyberStation PC B-Link fault will also cause this problem Resolution Exit Continuum CyberStation, then ensure only a single network card is enabled Fix the problem caused by database mismatching: Create a new database and bring the master controller online, Do learn from the commport and bring the field controllers online Click the "Reset" button on the Runtime tag after opening the controller editor. Do database initialization and connect the original database to see if the version number is correct or not. If not, skip to item 4. If yes, do SendToController and then BackUpToFlash Update the controllers to the latest version. Rebuild the CyberStation PC. Only have the Windows operating system and Continuum CyberStation installed. Skip over B-Link and connect Field bus to BCX1 comm2 directly to verify B-LINK has some fault, and then replace it with new one, if required

Issue Access denied and/or insufficient access errors reloading CX9680 or ACX2 (5720/5740) The above typically happens following an uprev of the controller FW to a different version. Product Line Andover Continuum Environment CyberStation CX9680 ACX5720 ACX5740 Cause RAM Memory issue due to the difference between the two builds, this problem will be addressed in future releases of the FW A similar warning can be seen if an XDriver is not correctly loaded. (Xdr may be referred to in the Distribution Properties page) Resolution Remove the battery Power down the controller, wait 5 minutes to make sure RAM is fully erased. Power up and reload the controller once it is online. Or reload the XDriver correctly first

Issue Require details on where to find the Pelco VideoXpert integration package and which versions are supported with Security Expert as the information cannot be found on the Scheider Electric EcoXpert Extranet. Product Line EcoStruxure Security Expert Environment Security Expert Pelco VideoXpert Cause Pelco now supports the VideoXpert integration with Security Expert directly. Resolution All information can be found on Pelco's  partners website, this includes: Security Expert VideoXpert Integration User Guide Security Expert VideoXpert Integration Download Installer Access Control OpsCenter Plugin Information on required licenses A contact form for further support

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 Procedure for converting a bCX9640 to a CX9680 (NC2) Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 (NC2) Cause Documentation Resolution This article provides some guidelines for converting a bCX9640 to a CX9680 in the field. As of version 1.94 CyberStation does not automatically convert a bCX9640 to a CX9680, such conversion while complex and error prone can be done manually.   DISCLAIMER: Be aware that due to the differences between the two models not everything can be converted; certain items may have to be re-created from scratch in the new CX9680 controller. DIFFERENCES BETWEEN BCX9640 AND CX9680   Feature bCX9640 CX9680 1 System Variables 47 65 2 Comm Ports 2 4 3 IO Expansion Modules IOU Modules 4 Infinet 1 2 5 Access Control No Yes 6 UPS Support No Yes 7 Display Module Support Yes No   Procedure: Make sure you have a recent backup of the SQL ContinuumDB as a precaution. From CyberStation send the bCX including children to a text file, the dump file can be later used for reference. Take note of the bCX9640’s name, AccNetID and network settings. Put the CyberStation in offline edit mode and delete the bCX9640 then create the CX9680 using the exact Name, ACCNetId and network settings as the deleted bCX. After creating the new controller object it will come online, at this point you are still communicating with the bCX9640 hardware. In the ‘Send to Database’ options make sure to select ‘Save attached objects and controllers’ then select the new controller in the Continuum explorer and perform a ‘Sent to database’, depending on how many Infinet devices you have this make take a while. When the send to database operation has completed you are ready to remove the bCX9680 hardware and connect the CX9680 hardware. After disconnecting the bCX from the network commission the CX9680 hardware with the same AccNetID and network settings as the bCX it is replacing. When the new hardware comes online reload it from Continuum making sure you don’t reload the Infinet devices (Reload attached objects but not attached controllers)   At this point you have converted the bCX9640 to a CX9680, the next steps in the process is fixing the items that do not convert properly due to the differences between the two controllers. LCD Display Configuration If the bCX has an display module attached all configuration related to the display module must be removed as the CX9680 does not support it. Fixing IO If the bCX had IO then appropriate IOU modules must be configured in the CX9680. In some cases points may have to be moved to a different IOU. For example if you were using a xPBD4 (which has both inputs and outputs) then you’ll have to put the inputs and outputs on different IOU modules as there is not an IOU module that is the equivalent of the xPBD4. Fixing References Any references in programs/functions to objects that do not exist in the CX9680 must be manually removed/fixed. For example the CX9680 does not have some system variables supported in the bCX such as all the system variables related to the display module (ACCLCDBeeper etc) Other items that need partial or complete manual fixing include… Alarms, links will convert ok, but references to Graphics, Program, Video may be have to be re-assigned. Extended logging   Use the dump file created on step #2 for reference when manually re-entering lost configuration.   Article as a document: Procedure For Converting a bCX9640 to a CX9680

Issue When a Zigbee device is imported to EBO there is a lot of different configuration settings for the device, like the below settings for the Wiser Radiator Thermostat: How do I know what the different settings do? Do we have any documentation explaining that?  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Room Controller (RPC) Cause The different objects under the Zigbee device like "Thermostat" and "Power Configuration" is coming from something called clusters and a cluster is defined in the "Zigbee Cluster Library Specification". For example the "Remote sensing" attribute for the "Thermostat"   Look like this in the "Zigbee Cluster Library Specification" When joining a Zigbee device it will specify what cluster it support and that information is what will be used when building the import file which is imported to EBO. Resolution EBO doesn't know anything about the functionality of the Zigbee device. Instead it gets information from the device what clusters it supports, and will make sure the correct objects and attributes for the different clusters are created in EBO so it is possible to set all configuration parameters in the device. So to know what the different settings actually do in the device please contact the manufacturer of the device.

Issue RP-C-16B-230V Transformer 24Vac output Product Line EcoStruxure Building Operation Environment SmartLogic SmartX IP Controller RPC-16B-230V Cause More details about the internal transformer power supply required. Resolution The voltage regulation of the transformer is around 15%, thus if the "230Vac supply" is towards it's upper tolerance (230Vac +10%, 253Vac) the no load voltage of the "24Vac output" can be about 30Vac. If the RPC power supply is 230Vac, then the no load voltage of the 24Vac output will be around 28Vac With the 224Vac output" half loaded, the voltage is around 26.5Vac With the "24Vac output" fully loaded the voltage is around 24Vac See SpaceLogic - Hardware Reference Guide

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 for assistance. Issue Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In Project Configuration Tool, in the Project view, select the project you want to export. On the Header toolbar, click the Export project button or right-click on the project and select "Export". On the Export selected project(s) dialog box, in the Folder box, browse to the folder on your hard drive where you want to save the exported project. Click OK. TIP: You can select multiple projects and export all of them at once. Note: In order to be more future proof, there is a new export/import format of PCT projects starting in PCT v1.3.2 with exports having an extension of '.pct_export'.  Projects exported at an earlier version have an extension of '.ppb' and they must be converted to '.pct_export' files before import into PCT v1.3.2.    Please refer to point 2.1 in the release notes.   Also prior to PCT v1.3.2 the project had to be stopped before export was possible.  In PCT v1.3.2 the project has to be running before it can be exported.    

Issue In the field it can be advantageous to flash an i2 to a b3 or a b3 to an i2 Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet controllers BACnet controllers i2xx/i28xx-V b3xx/b28xx-V Cause Flashing controllers in the field can save time Resolution If the controllers are i28xx-V or b38xx-V then these can be flashed back and forth in the field.  Please refer to Update b3 or i2 OS which also contains information on converting a bCX4040 to/from bCX9640 Refer to Conversion of Continuum devices from i2 to b3 and vice-versa in the field for non -V models If the i2/b3 controller is NOT included in the above (any other type of controller) then it cannot be flashed in the field, it will need to be sent to repair to change from an Infinet to BACnet or BACnet to Infinet.  If you attempt to flash this way in the field it can cause the controller to become a non-functioning controller.

Issue System was running fine with EBO version 3.2.3 and Active Directory (AD) integration. But after upgrading to EBO version 2022 no AD user could login to the ES. The Workstation Error when trying to login is: User_Not_Associated_With_A_Group And the error message seen in the ES trace log is: WinES\server\nsp_servers\csc\accountaccess\source\AccountAccess.cpp(486) Workstation Error: User_Not_Associated_With_A_Group (0xc002a) in module Account_Access(28).  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause The Windows AD integration performance in EBO was improved in version 2022 by storing and comparing the SID for the AD-groups. During the upgrade from version 3.2.3 to EBO 2022 all EBO groups should have been updated with an AD-connected group SID. This was not done as the AD server was offline when doing the upgrade of the ES. Resolution If turning on the below property in the properties the old way used in EBO version 3.2.3 of matching groups during logon will be used: In the "ES.properties" file usually placed in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\etc\config add and save: NspServer.Windows.Group.MatchByName = true   To utilize the AD performance improvement in EBO 2022 re-connect the AD group to their respective EBO group. This is done by changing the "Windows group name" property in the EBO group to anything else or an empty string and then change it back to its proper value, i.e. the AD group name. Doing so should correctly populate the hidden "External SID" property for the EBO groups that is missing as the upgrade was done with no connection to the AD server.  

Issue How can I streamline badge creation in Security Expert? Product Line EcoExpert Security Expert Environment Security Expert Server Security Expert Client   Cause There is no "Import/Export badge" feature available in Security Expert (unlike in Episuite/Continuum) Resolution This video demonstrates how to streamline badge creation in Security Expert.     Badge templates are normally provided by the customer.  They should be provided in bitmap (.bmp) or portable graphics format (.png) format. JPEG image format does not work well for resizing.     A new template can also be drawn though this is time-consuming.      Blank template from client 1. In Security Expert Client menu, go to Users--> Card Template Editor   Add and name new template, 2. Add blank template as image, go to right side Properties-->Images   Add blank template Adjust image to fit blue outline   3. Add dynamic user fields, go to right side Properties-->User Fields   Add and name fields ONE AT A TIME by dragging out items on to plan (drag one at a time to avoid confusion)     4. Name and place dynamic user fields over-top of blank template layout (Photo, Name, Dept, etc.)   Stretch, Align and Center Fields for uniform finish         5. Save template   6. Preview badge In Security Expert, go to Users--> Users-->Photo tab   Select a user:   Photo ID: Card template(drop-down menu)--> Choose your newly created template Hit the preview button Note: Do not choose Print & Read if no USB card reader is attached; this will cause an error and shut down Security Expert   Print Preview:

Issue How can the reports list sort order be changed and saved so that reports are always displayed in a specific order.  Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Reports are printed in order of Database ID by default. There is a need to have this changed to a custom sorting order.  Resolution This video demonstrates how to create, configure and save report layouts in Security Expert.         1. Create your report      In Security Expert Client menu, go to Reports --> Setup--> User Add and name the new report Choose a Report Type and give your Report a Title (this will appear at the header of your report) Skip sorting properties Save your report 2. Add Columns to your report With your new report highlighted, go to the "Columns" tab Click Add to add desired columns for your report Save your report 3. Configure your report: Return to the "General" tab and click "Edit in report view" as seen below   Filtering: right-click the column you want to filter and select filter editor  Add your desired filters   Apply to view changes and OK to close the editor Sorting: right-click the column(s) you want to sort Click Save Report Filter to save your changes   Note: 1. You can clear custom sorting of the report table by:: Right-click tab and hit clear sorting Click Save Report Filter 2. You can also filter multiple columns: Right-click the columns Sort primary column (Dept, Access Level, Region) Sort secondary columns Click Save Report Filter

Issue What are the recommendations/limitations around using RDM2 and mRDM2 Reader Expander Modules on SP-ACX and SP-AC1 controllers? Product Line Security Expert Environment SP-ACX SP-AC1 RDM Expander Modules Cause The number of RDM2 and mRDM2 modules which can/should be used on an SP-C/SP-C-Web is well documented, but it is not so clear what limitations exist when using these modules on other SP Controllers. Resolution While SP-ACXs and SP-AC1s have not historically supported SP_RDM2 modules in the past, it is now supported going forward, as detailed in Architectural Guide Lines Security Expert - 4.3.322 available on The Exchange.    This will also receive an official 'new feature' announcement for Security Expert 2023 when it is released later this year.  (Assume controller firmware of 2.08.1320 minimum)   Legacy Continuum AC1 Modules and Security Expert RDM modules have to be used on separate ports and care must be taken when adding new RDM modules as this runs the risk of overtasking the controller, especially when approaching maximum door limits.  SP-ACXs and SP-AC1s are primarily designed as transitional controllers to allow Continuum ACXs and Continuum NetControllers to be transitioned smoothly into a new Security Expert system.   

Issue As per RFC 4510 The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. Do EBO servers support LDAP protocol? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Need to know if EBO supports LDAP protocol. Resolution EBO doesn't support LDAP protocol. EcoStruxure Windows based BMS servers (Enterprise Server/ Enterprise Central) support integerationto Windows Active directory. The Active Directory integration is not using LDAP directly, but the NetLogon service on the Windows OS that ES/EC is running on.  This connection enables inherited user account groups from the Windows Active Directory to EcoStruxure Building Operation software, and allows users to log on to WorkStation with their Windows user accounts. Refer to: Windows Active Directory User Groups and Integrating Windows Active Directory user accounts with EcoStruxure - Communities For EBO 2022 or higher, Authentication using SAML 2.0 is also supported (Edge Server, AS-P, AS-B, ES and EC) . This enables configuring WebStation to use single sign on (SSO) using Federated Authentication, refer to: Federated Authentication. SAML Authentication feature requires license.

Issue SLP Sensor Modbus RTU issue when used with RPC or AS Communication errors are seen during normal Values are updated very slowly, can take up to two minutes to populate/update the 15 objects within the SLP.   Product Line EcoStruxure Building Operation Environment Modbus RTU RPC Modbus Automation Server + Premium  SLP SpaceLogic Sensors LSA_APP_REV2.03.19 and REV2.05.21 Cause Once the Modbus communication is set up between RPC (or AS) and the SLP,  although the values updates fairly regularly, multiple communication errors are also seen The SLP read speed needs to regulated to prevent overwhelming it The SLP Modbus transmission voltage is less than the AS Resolution Use with RP-C SLP struggles to respond to every request from the RP-C, changing the baud rate to 9600/19200 and increasing the "Silence characters" in the interface to 255 (maximum possible) should stabilize the communications.  The character spacing cannot be adjusted enough in the RP-C to allow communication at 38400 or 76800 Use with AS/AS-P  Adjust the “Poll point delay” in the Modbus Interface to 80ms The Silence characters and Transmit guard bits may also need to be increased Baud rate up to 38400 has been tested.  

Issue Are there any redundancy options for Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Stratus everRun Cause Need to provide redundancy for the Security Expert Server. Resolution There are a couple of options for providing server redundancy that can be used with Security Expert. The first option would be to use a downtime prevention product such as Stratus everRun as a hot standby solution. The second option is having a secondary Security Expert server as a cold standby server, if the primary server fails/needs to be taken offline the Security Expert services on the cold standby server can be started to take over. This option is largely manual, there is no automatic switching between two servers with this configuration. There are also a number of considerations to take into account with this option: In this scenario the controllers would be programmed with 2 x event server IP addresses for the primary and cold standby server as a result only 1 server/set of Security Expert services must be running at a time, having both running and therefore the controller having 2 x valid paths back to 2 x different servers concurrently will cause issues with the upload of events, online status and downloads A suitable system/process would need to be put in place to ensure the databases are restored from the primary to the cold standby server There will be 2 different Security Expert servers running which will require 2 separate Security Expert Server license with the same feature set enabled on both Considerations will need to be made with regards to the name of the machine to ensure the Download and Event servers can run, either the machines must have the same name or the name of the server needs to be renamed when required to the name of the cold stand by server An operator would need to verify the state of programmable functions and services. If the primary server failed during the middle of the download when the cold standby server is up and completes a full download some functions/services may require manual starting.

Issue Can Enterprise Servers inherit licenses from a parent Enterprise Central? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Need to know if Enterprise Central Licenses can be inherited by an Enterprise Server, and then, in turn by Automation Servers. Resolution An Enterprise Server cannot inherit its licenses from a parent Enterprise Central. Licenses can only be inherited from an Enterprise Server by the attached automation servers. Refer to WebHelp article Inherited Licenses and Knowledge Base article SmartX Server License Inheritance in EBO 3.x.

Warning This article describes a feature that is not standard functionality within the Product Line.  It has been provided to allow customers the option to use this requirement.  Pay particular attention to the Prerequisites of the required programming. Issue Customer requires the functionality for Individuals  to double badge (present their credentials twice) to gain access. Product Line TAC INET Environment Access Control Cause Customer application requirement Resolution Prerequisites: LIMITATIONS: As this is not a standard access control feature within I/NET, it uses custom programming, which therefore reduces/limits the standard features within I/NET The description provided below must be set for ALL individuals with access to the door that requires double badging.  It does NOT cater to custom individual use.  It may be possible to provide additional programming to achieve this, but this is not detailed in this article. Door Automatic Time Schedules (ATS), if applied, can be overridden if the door reader is badged during the scheduled operation.  The functionality of this feature uses event-driven programming, which in its nature is single-shot programming and therefore relies on the following:  Requires reliable communication between SLI/MCI (779x) and the SCU (Door Controller).  The door reads from the SCU must be received by the SLI/MCI to activate the badge/read occurrence. Requires SLI/MCI (779x) CPU loading below 65%. LAN Load of this controller should be below 2%; anything above this can cause the operation to fail/be inconsistent.  Removes the standalone capability of the Door controller (SCU) POINTS The points required for each door that requires this functionality are Door Reader (Internal DO door point as required in I/NET)  Door Strike (External DO Point) must be programmed within the controller Door Intermediate (Internal DO Point). :: Scan Rate 1 second Door Read Count (Internal AO Point). :: Scan Rate 1 second I/NET Controller Summary Note: The address order, as shown in the screenshot above, is important for the overall operation.   That is Read Count must be at a lower address than all other points.  Next the Intermediate point.  The Strike and Reader addresses are fixed by I/NET but must be at a HIGHER address than the Read count and Intermediate points.    DOOR Intercard Interval (sec) should be set as low as possible.  This allows the card to be present within this time setting (minimum is 1 second) Door strike: Configuration of the door/reader must have this set to either. None: When a valid read is received, no action is sent to the strike Exit: Only when an Exit read to Request to exit (REX) is received by the door does it activate the strike.  Strike duration (sec): Should be set 1 second above the scan rate of the Intermediate / Read Count points above.  In this case, it is set to 2 seconds.  Note: this does not have any bearing on how long the strike remains "unlocked" Door editor Programming DOOR No additional programming is required for the door apart from the details provided in the above prerequisites.  ACCESS INITIATED CONTROL (AIC) Add an AIC that will trigger the Intermediate point on a "valid" reader entry for the nominated door. Select the Target point (DR1 Intermediate) Select either Use all individuals in the range which will trigger this action for all individuals.  Note: If selected Individuals are needed to activate this feature, then additional programming is required and not detailed in this article.    Select Reader entry to START the target point  Select which Doors are to trigger this action Access Initiated Control editor POINTS From the screenshots below, it can be seen that: Point DR1 Read Count has two extensions: Calculation (C)  Operation: The result of this calculation is displayed on the DR1 Read Count point.  The calculation adds the value of itself (P0) DR1 Read Count and point (P1) DR1 Intermediate point (where 0=OFF 1=ON), the result of which is then multiplied by the NOT (~) the value of (P2) Door Strike (where sec = 0 Unlk = 1). Result: DR1 Read Count is incremented by one on each valid read.  The counter is reset (zeroed) when the Door Strike is energized.        Event Definition (EV)   Operation: When the point DR1 Read Count crosses the value 1 (the value of 2 represents the double (2) badge), Sequence/Action #1 is triggered.  From the above Event Definition (EV), this runs Sequence/Action Num 1, which is shown below:  Operation: When triggered by the (EV) above, the Door Strike is immediately "Stop"  (Unlocked); after a 5-second delay, the Door Strike is "Start" (secured). Note: The delay of 5 seconds on line #2 determines how long the strike remains in the unlocked state.  Modifying this value will shorten or extend the unlocked state.     Point DR1 Intermediate has only one extension: Calculation (C)  SUMMARY OPERATION A valid card read is presented to the reader; this triggers AIC to turn point DR1 Intermediate to ON. This increments DR1 Read Count by 1 to the value of 1 via its Calculation (C) extension The additional card read repeats Steps 1 and 2 above;  DR1 Read Count value increments to a value of 2. Event Defintin (EV) high-value crossing (>1) triggers Event Sequence #1 Event Sequence #1 unlocks Door Strike 1 and, after a 5-second delay, relocks (secures) Door Strike 1 point. This relock (secure) of Door Strike 1 zeros the DR1 Read Count value via its Calculation (C) extension.  ATTACHMENTS - for reference showing the above details  I/NET Controller SAV file (DCU0201.zip) Backup InetDb (SQL.bak).  (InetDb_DoubleBadge.zip)  

Issue When WebReports is installed, two users called "appuser" are created. One is a local Windows user, and one is a SQL user. Product Line EcoStruxure Building Operation Environment WebReports User accounts Cause These users are or have been needed by WebReports Resolution EBO version 2.0 and above: the Windows user account "appuser" is no longer required to operate WebReports.  It is only a requirement during installation. SBO/EBO version 1.8 and above:  In SQL, the "appuser" user account has been removed as it's not essential for the Web Reports to operate correctly. In these versions, if an upgrade from an earlier version is performed and this user account is still present, it can be safely deleted /disabled.     In all other versions: The local Windows user account ([PC_NAME]\appuser) is used for importing report packs (RDL files) and synchronizing between WebReports and Microsoft Reporting Services.   For more information about this account, refer to SmartStruxure WebReports Installation Errors (1001 while importing report pack). To change the password for this Windows user, refer to Changing Report Server "appuser" password.    

Issue Moving from Webreports going to Postgres/TimescaleDB instead, leaves us without a reporting engine. SSRS can supposedly utilise a PostgreSQL database, but SSRS is a licensed part of MSSQL. Product Line EcoStruxure Building Operation Environment Building Operation Timescale Database Cause From EcoStruxure Building Operation version 4.0 (2022) the Building Operation Report Server is no longer supported. Instead, we support PostgreSQL/TimescaleDB, using Dashboards and Excel from within EBO, to make reports, using Notification reports to start Excel and reports. Resolution EBO 3.2 introduced Enhanced Reporting, based on the current feature Notifications in combination with Notification Report Template, which also supports report data such as Alarms, Groups, Multi Log list, Relative events and Users. The Notification result can also be presented in XLSX format and converted to PDF with signing capabilities. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there.   EBO 2023 introduced External Log Storage support for Microsoft SQL Server in addition to PostgreSQL/TimescaleDB   Information  and examples of Enhanced Reporting and Dashboards can be found in EBO Webhelp, My LearningLink and the Automation Experts Community.   NOTIFICATION REPORTS : EBO Webhelp: Notification Reports  Community: Reporting in EcoStruxure Building Operation 3.2 Community: Reports showcase - share your reports! Community: Get more data out of the system with Notifications! EcoXpert Extranet Video: Community Video : Fusion Fridays - Session 20 Community: Change Control and Enhanced Reporting Lab Guides Community: Example Report Templates  Community: Forced Values Report Example My LearningLink: EcoStruxure Building: Enhanced Reporting and Dashboards 3.2 My Learning Link: EBO 2022: Enhanced Reporting and Dashboards   DASHBOARDS : EBO Webhelp: How Dashboards Work EcoXpert Extranet Video: Dashboards EcoStruxure Building Operation 3.0 - Informational Video Community: What Custom Types have to do with Dashboards Community: Public vs Personal Dashboards Community: Graphics in Dashboards [Advanced] Community: Dashboards: Share your screenshots! EcoXpert Extranet: PA-00701 EcoStruxure™ Building Operation 3.0 Captures the Spotlight