Issue Site experiencing comm issues on the Infinet or MSTP bus. Controller error logs show many 1465 (Cyclical Redundancy Check) errors. Product Line Andover Continuum Environment Infinet MSTP b3 i2 Controller error log Cause CRC errors are check sum errors. Before a packet is sent, the sending controller calculates a checksum based on the packets contents. This checksum is then appended to the packet. When the packet is delivered, the receiving controller calculates it's own checksum based on the packets contents. If the check sums do not equal, this indicates that somewhere in the delivery process the packet has been altered, usually due to bad cable or connections, controller grounding, or a bad controller transceiver. For additional information on troubleshooting the infinet or mstp bus, see Infinet and MSTP bus troubleshooting. Resolution CRC errors usually indicate poor signal integrity on the physical bus. Infiltration of "noise" on the comm cable due to the presence of high voltage conductors, radio transmissions, etc. In some cases a failed transceiver may be involved but this is generally not the case. Poor controller grounding can also contribute to this issue. Generally CRC errors call for using a scope to assess the signal integrity on a bus.

Issue How to configure the EcoStruxure BMS External Log Storage feature using PI System. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server Cause Need EBO to send selected trend logs and the event log to AVEVA PI System directly without the need for intermediate storage or specialized PI System connectors. Resolution The following video will illustrate how to: Install and configure AVEVA PI system (PI Server and PI Web API) for testing. Configure PI system settings in EBO. Configure trend logs to be written to PI system. View and organized the data in PI system Explorer. Things you need: EBO 2023 (V5.0.3) or higher with valid AVEVA PI System connection license or demo license (Enterprise Server, AS-P, AS-B or Edge Server). AVEVA PI server and PI web API with valid license (Check EBO Information Technology System Planning Guide for tested versions). For more information about PI system recommended architectures, system requirements and installation instructions, please check AVEVA documentation, PI System™ | AVEVA, OSIsoft - PI System and YouTube video published by AVEVA for detailed instructions about installing and setting up PI system Setting up a PI System Development Environment From Scratch - YouTube Note: In EBO V7.0.1 or higher, values can also be read and hosted from an AVEVA PI System, refer to: Hosting Points from AVEVA PI System

Issue Tips for Configuring HID OSDP Reader LED Colors Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert OSDP Reader Cause Additional tips for configuring OSDP Reader LED Colors Resolution The Configuring LED Colors section of AN-254 Configuring OSDP Readers in Security Expert  details the basic steps for LED configuration. This article details some additional areas of the HID reader setup and Security Expert configuration that may be useful when configuring the LED colors.   Note: The steps in this article are specific to an HID Signo RP10 Reader BLE and may not apply to other HID reader models or other brands of OSDP readers.   Upgrade the Reader firmware to the latest version. Earlier versions of the reader firmware would not correctly allow LED control. The Bluetooth option allows the configuration of the reader using the HID Reader Manager App. For detailed information see HID Reader Manager App Information Note: To use the HID Reader Manager App to configure a reader, the Security Technician or Security Installer needs to create and register an account with HID. The Reader Manager Administrator for your organization or company needs to enroll this new account using the Reader Manager Service and issue an invitation code and key authorization for this and other readers. The Security Technician can then verify the key authorization has been received in the HID Reader Manager app. Detailed instructions for all of this are included in the HID Reader Manager App Information URL listed above.   HID Reader Manager App Firmware snapshots       In the HID Reader Manager App, change the Reader Options for LED color to "Host Controlled" in 2 places. The reader must be controlled by the Security Expert controller. Credential Reader AV LED Idle Color Ensure that the firmware for the following hardware is upgraded to these versions or greater in order for LED Color Output to work. Security Expert 4.3.308.46 SP-C 2.08.1234 MRDM2 1.2.590 In Security Expert the Outputs to control the LEDs need to be manually created. Programming> Outputs> Add A pop-up asking to Invert Output will display, select 'No' when prompted Output 3 (GreenLED Port 1) Output 4 (Red LED Port 1) Output 6 (Green LED Port 2) Output 7 (Red LED Port 2)   Name the Outputs whatever is appropriate Example:  GreenLEDPortON RedLEDPortOff LED Colors The default LEDs are Blue when Idle and Green when active. As an example, the LED colors will be changed to Red when Idle and Green when Active. Color Options:   Set the colors for both Red(idle) and Green(active) in the Security Expert Output Command Window for the newly created outputs RedLEDPortOff   GreenLEDPortOn Update the modules and wait for about 15 seconds before activating the output to test. Just saving the updated command setting doesn't work, the module must be updated.   Activate the GreenLEDPort1 - the color should change to what the output was set to in the command. In this case, green. Deactivate goes back to Off (idle) Red. GreenLEDPort1 = On State RedLEDPort1 = Off State   Note: The Off state if left at the default of Blue can't be used with the On state of custom(non-default). Both Outputs must be specified in the command window for the colors to work together.   Example: If the OFF state is left at the default of blue and the color of the ON state is set in the command window and Activated, the LED color will change to what it is set to(green), but when deactivating the Off(idle) output it will not turn blue.

Issue How do points map from a i2 controller and the xP expansion modules to Infinity SX8000? Environment Using Continuum i2 controllers and xP modules on SX8000 Infinity systems. Cause The I/O channels on expansion modules are different from Infinity to Continuum. Resolution You can add an i2 controller to your Infinet networks on Infinity and it will co-exist with the other Infinity controllers. The controller will be seen as a equivalent infinity controller i.e. a i2850 will be seen as a TCX850. Also you will not be able to use any of the additional features that a i2 controller has like the flash memory or the smart sensor connection. For Expansion modules you could however use the xP modules (not including the xP display) the attached spreadsheet that shows how the i2 controllers I/O channels will be seen by the Infinity Controller. Download the spreadsheet here.  

Issue Enterprise Network Server station failed. Attempts to start the station resulted in the following error messages. ERROR [15:32:36 04-Jul-12 SGT][sys] Cannot load station java.io.EOFException    at javax.baja.xml.XParser.read(XParser.java:753)    at javax.baja.xml.XParser.parseText(XParser.java:621)    at javax.baja.xml.XParser.next(XParser.java:268)    at javax.baja.io.BogDecoder.decodeDocument(BogDecoder.java:164)    at javax.baja.io.BogDecoder.decodeDocument(BogDecoder.java:152)    at com.tridium.sys.station.Station.loadStation(Station.java:128)    at com.tridium.sys.station.Station.bootStation(Station.java:78)    at com.tridium.sys.station.Station.main(Station.java:978)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)    at java.lang.reflect.Method.invoke(Unknown Source)    at com.tridium.sys.Nre.runClass(Nre.java:224)    at com.tridium.sys.Nre.main(Nre.java:149) App Failed   Environment I/A Series G3 Cause The station's config.bog appears to be corrupted. The reason for this is unknown at this time. Resolution Restore the station database with the latest copy of a known good backup.

Issue The System License Information screen has a lot of useful data on the status of licenses in the EBO system. Is there a way to export or screenshot the entire System License Information page? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Cause Unable to save or export the System License Information screen Resolution There is no option to print or export the Control Panel System license Information screen. It is possible to get a reasonably close facsimile by viewing the LicenseStatus item in System>LicenseManager and adding columns for Required Licenses, Checked Out Licenses, Installed Licenses, Available Licenses, and License Violation.   This can then be Exported in XLSX format for future reference or if required by Product Support  

Issue Seeing multiple losses of functionality starting to occur, such as controllers going offline, browsing with the client being slow, reports failing to run and events not being logged. Product Line EcoStruxure Security Expert Environment Security Expert SQL Server 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. Cause In SQL Server the SecurityExpertEvents database has a very large LOG file ( hundreds of gigabytes) resulting in degraded performance in SQL and Security Expert.   The Recovery model of the SecurityExpertEvents database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size. Recovery model fullRecovery model full New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution Reduce the size of the log file and prevent it from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpertEvents database from Full to Simple in SQL Server Management Studio. To do this, right-click on the SecurityExpertEvents database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery model simpleRecovery model simple Right-click on the SecurityExpertEvents database and select Tasks > Shrink > Files Shrink filesShrink files In the Shrink File - SecurityExpertEvents window, change the File type to Log. Shrink log fileShrink log file Click OK Repeat steps 2-5 for the SecurityExpert database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue There is mention of the Modbus integration service in Security Expert manuals and release notes but no application note explaining what features are supported or how to configure the integration. Product Line EcoStruxure Security Expert Environment Security Expert controller Modbus integration Cause The Modbus integration in Security Expert is currently not supported by the Offer. The current Modbus integration has known issues and is being rewritten. There is no further information on when this will be completed or what devices this will be supported in. Resolution If the Modbus integration is required, the local solution category management team should be contacted to have this requirement properly prioritized and to get updates on any new Modbus integration work.

  Issue Site upgraded SmartX IP Controller from 2.00.03.1203 to  v3.02.03.02109. When the upgrade was completed, they attached the SmartX room sensor to the controller.  The sensor appeared to update but the screen display was distorted.             Product Line EcoStruxure Building Operation Environment • Building Operation Multi-purpose VAV • Building Operation SmartX Living Space Sensor • Building Operation Workstation   Cause With a blank database, an MP-V with firmware V2.00.03.1203, when the sensor is connected the screen is distorted, but  after upgrading the MP- V to firmware V3.02.03.02103 , the screen display shows up with no issues Something is breaking for the site when attempting to go from 2.0.3.1203 to 3.2.3.02103 Resolution Upgrade the firmware to a higher version (ex 4.x). After the MP-V is upgraded, the sensor will upgrade automatically which takes about 10 to 15 minutes and the status will be operational. The screen will then display properly.

Issue How to configure search object to display SpaceLogic controllers IP settings "Changes pending" in the search's list view Product Line EcoStruxure Building Operation Environment Space Logic IP controllers  Cause Confusion when attempting to find the appropriate type to include in the search  Resolution The IP settings "Changes pending" property is not a property of the device but rather a property of the IP Network Port as seen in the screen shot below  

Issue Users may need to display the current date as a formatted object within Sigma. Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause Sigma does not natively format date objects for display. A programmable point must be configured to represent the date in a readable format. Resolution Option 1: Display Day and Month (Format: dd.mm ) Use the following programmable logic: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo / 100.000 30 YFlo = FLOAT ( DAY ) 40 RETURN VIA TEXT 449 VALUE XFlo + YFlo  Shorttext Format: %2.2f → Displays as 17.07 Date:%2.2f → Displays as Date:17.07 Option 2: Display Day, Month, and Year (Format: ddmmyy ) Use the following programmable logic: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo * 100.000 30 YFlo = FLOAT ( DAY ) 40 YFlo = YFlo * 10000.0 50 ZFlo = FLOAT ( YEAR ) 60 RETURN VIA TEXT 449 VALUE XFlo + YFlo + ZFlo   Shorttext Format: Date:%2.0f → Displays as Date:170712 Notes Ensure the correct formatting is applied in the Shorttext field to match the desired output.

Issue Controller Error Log shows error code 5128. Environment Error Log Error Code NetController BCX ACX Cause An Infinity Controller is dropping offline. Resolution Controller error code 5128 (0x00001408) is an indication that the controllers network comm buffer is out of memory.  Normally the network transceiver will shut down when this happens to protect the controller.  This is generally an indication that the controllers comm buffer is being overtaxed.  This can happen when there is a data storm present on the network. 

Issue Standard Applications for I/A Series Micronet BACnet (MNB) controllers Product Line I/A Series Environment I/A Series WorkPlace Tech 5.x and above I/A Series MNB controllers Cause A library of standard pre-engineered applications for MNB controllers is available. These can be modified and used as a reference for creating MNB applications. Resolution The library of standard applications can be downloaded from Exchange Extranet. Below is a list of the applications available for downloads.  DUI Application Stencil Operation Guide Application Objects Visio Stencil (Includes DUI_App) Applications - BACnet Zone, VAV, and Unitary Applications using SP and SPP Momentary Start/Stop Object Application Operation Guide Application - BACnet Zone Controller Applications Application - BACnet VAV Box Applications Application - BACnet Unitary Applications Stencil - Application Stencils Application - VAV_Staged_Heat.vst Application - FC_1DX_1EH.vst Application - FC_1PropCL_1PropHT.vst Application - FC_2Pipe_2PosHC_wCO.vst Application - All BACnet Unitary Applications.zip Application - All BACnet VAV Box Applications.zip Application - VAV_Cooling_Only.vst Application - VAV_Floating_Heat.vst Application - AHU_HeatPump.vst Application - VAV_Parallel_Fan_Staged_Heat.vst Application - VAV_Parallel_Fan_Floating_Heat.vst

  Issue PCT v1.3.3.75 fail to start SmartX server in versions 1.8.x and 1.9.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Defect, user can create SmartX server v1.8.x and 1.9.x but the servers can't start properly. Resolution Uninstall PCT v1.3.3.75 Install PCT v1.3.2.110 (Download), (Client Installer) Install server packages 1.8.x and 1.9.x

Issue Using CARD + BIOMETRIC credentials at an integrated Suprema reader for user access. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Reader Cause Security Expert does not support CARD + BIOMETRIC credentials being read at the integrated Suprema reader. Only BIOMETRIC credentials are supported to be read at the Suprema reader. Resolution For situations where CARD and BIOMETRIC credentials are required to authenticate users a supported solution is to install a Security Expert reader in conjunction with a Suprema reader at the door. The Security Expert reader will read the Security Expert Mifare/DESFire tags, compare this to the credentials configured in Security Expert user and then wait for the proper biometric to be provided before allowing access through the door.

Issue 3rd Party RS485 to Ethernet or other connection types are available. Will they work with Infinet? Product Line Andover Continuum Environment Infinet networks Infilink 200, Infilink 210 Cause Sometimes existing cabling is available on a site, using this could reduce install costs. Resolution Third party converters and extenders are not supported on Infinet networks. It is not possible to use most 3rd party devices as the latency (delay) times will be too long for the protocol to operate correctly. This will include: RS485 - Ethernet converters RS485 Tied line Modems Any other type of Modem Any GSM packet modems Other RF devices

Issue All of the nodes are yellow and when they are clicked on the error below is displayed even though the database is attached to the network (OnNet), the network interface is on the correct channel, and the network interface passed all applicable tests. Environment NL220 Cause When the nodes appear yellow, this means that the LNS database has been corrupted. Resolution It can be attempted to repair the database using the Echelon LNS Database Validator. Follow these steps. If NL220 is still running, shut it down. Go to the Start menu > All Programs > Echelon LNS Utilities > LNS Database Validator. Select the corrupt database in the "Network to Validate" drop down box. Check the box next to Repair Database. Now click on the button called Validate.   If these steps do not repair the database, send the LNS database backup to Echelon support to see if they can correct the problem.

Issue The EBO license is activated on a virtual machine, need to make sure that it will not get damaged. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Scenarios leading to broken Trusted Storage (license damage), when license is activated on a Virtual Machine. In some cases, the License Administrator can be used to repair the license, and in other cases, product supported will need to be contacted. Resolution FlexNet documentation explains how licensing in virtual machines works, what causes license damage, and how to avoid license damage. Make sure that documentation is related to the FNP version (FlexNet publisher) used by installed EBO, ex. EBO V4.0.2 uses version 2021 (11.18.1) and EBO V5.0.2 uses FNP V2022 R3 (11.19.2).  You can also check the FNP version by checking the properties, details of lmadmin.exe file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Binding elements for licenses activated on a virtual machine: FlexNet publisher documentation lists three binding elements for virtual machines, all of which are deal breakers: MAC address, UUID, and Generation ID, refer to Binding in a Virtual Environment (revenera.com)  Scenarios that can cause license damage (Trusted-Storage Breakage): In the attached FlexNet White Paper: Understanding Virtualization Features in FlexNet Publisher, Page 9, details binding variables and which scenarios can change each binding element. Page 11 in the same white paper, Recovering from a Binding Break in TS, explains common scenarios leading to broken TS and if a license can be repaired.  WebHelp article EcoStruxure Building Operation Software License Repair, explains other reasons for license damage, for physical or virtual machine.  Please contact your local support if the License Administrator can't repair the license. Best Practices to avoid Trusted-Storage Breakage: To minimize license damage, follow the below steps before making changes to the bindings elements or moving EBO to a new VM. Make a backup of EBO, Backing Up EcoStruxure BMS Servers Manually Return all licenses, Returning an EcoStruxure Building Operation Software License. Verify that all licenses have been returned for all used Entitlements by logging in to https://licensing.se.com. Perform your operation. Activate the licenses again, Activating EcoStruxure Building Operation Software Licenses. FlexNet lists best practices that can also be followed to avoid trusted storage breakage: Best Practices (revenera.com)

Issue System memory usage stays high after exporting projects in PCT (Project configuration tool) Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause The exporting process increases memory usage but is still withheld by the project after the process finishes.   Resolution Close the project exported.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP server from the virtual machine. Resolution To change the Notification Address in the "Setup for use with remote server" to "localhost". 1. Select "Setup for use with remote server" after PCT start. 2. Update the "Notification address" to localhost