Issue Check the host and intermediate certificates with a CA certificate to verify the authentication chain before importing them into EBO servers. Product Line EcoStruxure Building Operation Environment Enterprise Central Enterprise Server Automation Server Edge Server Cause Certificates are provided and can be assigned incorrectly or to the incorrect server; therefore, they do not function as expected. Resolution Verify you have the following: Host certificate in PEM file format Intermediate Certificates in one pem file, not including Certificate Authority (CA) cert CA Certificate where Issuer and Subject Name are the same, indicating it is self-signed. OpenSSL is installed on the computer with the files. Use OpenSSL installed with EBO or install as mentioned in Ensuring the SSL Host Certificate and key file are a matching pair Use this command:  openssl verify -CAfile ca.pem -untrusted intermediate.pem server.pem​ The explanation of the command is as follows: openssl verify: This initiates the certificate verification process. -CAfile ca.pem: Specifies the path to the PEM file containing the trusted CA (Certificate Authority) certificate. -untrusted intermediate.pem: Indicates the path to the PEM file containing the intermediate certificates. They are marked as untrusted because the system does not directly trust them, but their validity will be checked against the CA certificate. server.pem: Specifies the path to the PEM file containing the host server certificate you want to verify. The expected responses are:  server.pem: OK: Verification successful, indicating the server certificate is valid and its chain of trust is established. Error messages: If any errors occur during verification, they'll be displayed in the output. Common errors include certificate expiration, invalid signatures, or missing intermediate certificates Additional information: Ensure the file paths are correct and the certificates are in PEM format Ensure the host and intermediate certificates are installed on the server device and the CA Certificate on the client device. If you encounter issues, double-check the validity of the file permissions and certificates. For more detailed output, add the -verbose option to the command. To check expiration dates, use  openssl x509 -in server.pem -noout -dates

Issue IO Module properties show Firmware version 0.000. The module is online but no values can be read/written to/from the IO module. Product Line EcoStruxure Building Operation Environment IO Modules Automation Server Premium Building Operation Workstation Cause This can be caused by a module mismatch where the module configured in Workstation is not the same type as the physical module.  The module is shown as configured and online, but upon closer inspection of the I/O modules properties the "Module Type Mismatch" property is set to true. Resolution Double-check the module type shown under "Model Name" and correct it to match the module type printed on the IO module.  If there are not any points configured on the module then simply delete and recreate the module with the correct type.  However, if points are configured and bound and need to be retained follow the process below:- Change the module ID of the affected module configured in workstation to NULL to release the module id Create a new module with the correct type and assign the module id released in step 1 Drag the points over from the incorrect module to the new module Check the points are working as expected (the new module must support the point type) Delete the old module as it is not required Additionally, modules with a 'V' variant, such as the AO-8/AO-V-8 and UI-8.AO4/UI8.AO-V-4,  are different module types and one cannot directly replace the other.  Doing so will generate a module type mismatch.

Issue When installing PCT 2 the following error is seen: Error: System.Management.Automation.CommandNotFoundException: The term 'Get-VM' is not recognized as a name of a cmdlet, function,script file, or executable program. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause The Hyper-V Module for Windows PowerShell is not installed. Resolution Follow these steps in Windows 10 to install the Hyper-V Module for Windows PowerShell: Right-click on the Start button and click Programs and Features. In the Programs and Features dialog, click Turn Windows features on or off In the Windows Features dialog, check the box for Hyper-V Module for Windows PowerShell and click OK. The dialog will signal completion and the module will be installed.

  Issue How can system alarms be configured so that electronic signatures are required? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause Alarm Decoration rules are required to configure change control/electronic signatures for system alarms. Resolution Use the Alarm Decoration filters to apply/override settings for alarms. Create an Alarm Decoration Rule under ~/System/Alarm Control Panel/Alarm Decoration   Select the Alarm Decoration rule that filters on all System Alarms or the specific ones, select to override electric signature, and set it to True.    

Issue SLP BACnet Setpoint limits Product Line EcoStruxure Building Operation, Andover Continuum, Field Devices Environment SpaceLogic SLP Series Cause The BACnet Object "Temperature Setpoint" includes properties Minimum and Maximum values These can be used to limit the setpoint, however the values are not saved in non volatile memory, thus the value revert to default after a power cycle (0 and 50 degC). The Setpoint object needs to be manually downloaded from EBO following a power cycle to set these properties. These properties cannot be written to individually. Thus changing these properties is unlikely to be good practice. Resolution A script program can be used to set limits to the Temperature Setpoint. Example below Note the "Value transfer settings" need changing to "Transfer value each time..." as below

Issue The toolbar icons in PCT 2.0 are jumbled. They seems to be stacked on top of each other, making it hard to use the toolbar. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause Issue with the font used by PCT Resolution Follow these steps to resolve the problem: In Windows, navigate to Settings, then Font Settings, and search for "Material Icons". Select Material Icons, then choose Uninstall. Confirm by clicking Uninstall. Close all browser windows used to access PCT, then reopen and browse to PCT again. The toolbar icons should now display correctly.

Issue An error pop-up is encountered when trying to use WorkPlace Tech Editor (WPTE) ERROR: WorkPlace Tech Editor does not function using Visio 2000. A supported a supported version of Visio must be installed for WorkPlace Tech Editor or Monitor to function properly. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2013, 2016, 2019 Cause The Visio installed is corrupted or not updated to the required version. Resolution Procedure for doing the repair required for the WPTE to function Ensure that the Visio installed is approved for the version of WPTE you are using by reading the EBO release notes. Confirm that Visio if licensed and activated, and not using a temporary license Install any required Security Upgrades  Perform an Online Repair, not the Quick Repair, as illustrated  The picture above shows doing this repair to the installed Office.  Perform this on the installed Visio as well. It is important to search the installed applications to make sure no 64-bit Office products are installed.  Smartware Studio 360/Design 360 installs a 64-bit Microsoft Access DB application by ignoring the 32-bit/64-bit version check.  This can cause the fluent ribbon for WorkPlace Tech to fail and if the Online Repair is done, it can force all Office applications to be removed from the PC. 

Issue The network card is not working on the PC.  Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series TAC I/NET, TAC Vista Environment PC Network Interface Card Cause Require a method to test the network card. Resolution Assuming you have the correct protocols loaded:- Open up a command prompt and type ‘ipconfig’(1) then press enter to get a list of the available network cards. Find the specific network card by name (2) Record the IP Address (3) assigned to the card, e.g. 192.168.5.90 If the card is unplugged (4) connect a network cable and start back at step 1 If the network card does not appear in Device Manager check the drivers are correctly installed for the card and when installed correctly start back at step 1. If the network card still does not appear it could be disabled.  In Network Connections right click the adaptor and select Enable (5) and start back at step 1. After these steps if the network card still does not appear when running ipconfig it is most likely damaged. If/when an IP Address is successfully obtained open a Command Prompt and type ping followed by the IP Address of the card, for example ping 192.168.5.90 (1). A functioning card will respond with 4 successfully replies (2) and the associated statistics (3) As additional information a good first step would be to "ping 127.0.0.1". This will not test a network card but indicates that the TCP/IP protocol is installed and functioning on the host PC.

Issue Script advise for xPDisplay on a b3/i2 controller Product Line EcoStruxure Building Operation Environment i2 and b3 Controller xP Display Cause The xP Display was designed when only Continuum was available (before EBO) and there was no documentation for EBO. Scripts need to be used to control the xP Display Binding to Object LCDAnswerString directly via "String Input" or "String Output" in a script program Then doing a check  If LCDAnswerString <> ""  then causes the script to disable with errors. "" = Null Resolution A simple way around this is to do the script check on another (manually created) string that is bound to the object LCDAnswerString Thus the following will work:  Numeric Input LCDKeyStroke       'bind to LCDKeyStroke    - this can also be used to set to zero. eg. LCDKeyStroke = 0 String Input LCDAnswerStrCopy   'bind eg LCDAnswerStrCopy  - use this to read the LCDAnswerString value String Output LCDAnswerString    'LCDAnswerString  - use this to set to Null eg. LCDAnswerString = "" Numeric Output AAA Line Wait4Value If LCDAnswerStrCopy <> "" then  'check if a value has been input    AAA = minimum(maximum(0, StrToNum(LCDAnswerStrCopy)), 100) 'Make AAA equal the input (min0, max100)    LCDAnswerString = ""     'reset LCDAnswerString back to Null Endif Outside this script, the manually created string object LCDAnswerStrCopy needs to be bound to LCDAnswerString, this can be achieved directly (change the binding type to COV) or via another script (use Print LCDAnswerString to LCDAnswerStringCopy) Note v4.0 export, script text attached and install guide attached

Issue An error message is displayed when trying to download all objects to a SpaceLogic controller. The error message says:   Offline '/SiteServer' Communication   Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Premium (AS-P) Automation Server Bundled (AS-B) Multi-purpose or Room-purpose (MP/RP) controller Cause This error can occur when the controller is an instance of a Custom Type (CT), but the CT only exists in the type library of the Enterprise Server, and not in the Automation Server hosting the controller. A BMS Server can only access it's own type library. See WebHelp article Custom Types for more information. Resolution Log in to the Automation Server where the MP/RP controller is hosted, and import the custom type to type library.

Issue In a multi-version system, will the database schema in the PostgreSQL database be compatible with EBO servers with lower versions? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Timescale Database Cause In a multi-version system the database schema in the PostgreSQL database needs be compatible with all servers in the system. Resolution The DB schema is backward compatible. The same schema can be used for the complete system and it can be upgraded to the latest version compatible with the top-level server. Compression is done on the PostrgreSQL/TimescaleDB side and since it’s not configured in EBO, the compression will work for EBO servers with lower versions. Compression needs at least schema version 9 for EBO2023 or schema version 13 for EBO2024 and TimescaleDB version 2.0 or higher, refer to: Compression for TimescaleDB

Issue This condition will arise after successfully installing and running Project Configuration Tool for some time. PCT 1.x can no longer initialize the virtual host adapter as a result of the adapter being deleted or removed. The errors may be a result of but not limited to: Introducing a new VPN software package to your PC/Laptop. Manually removing or modifying the Virtual Box Host Only - Network Adapter. Malware or Antivirus platforms that have removed or disabled the adapter. Example: PCT Version - 1.1.2.57 Local mode was set up on a physical laptop and used to offline engineer a project. The job was completed and PCT was not used again for roughly a month. A new project was sold and required PCT for offline engineering. The laptop was booted up and PCT failed to open. The user was presented with the following errors: "Get System State Command: 'Could not connect' " "Get predefined properties command: 'Could not connect' " "GetDashboardErrors Command: 'Could not connect' " "Get System Memory info Command: 'Could not connect' " Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only) Project Configuration Tool 1.x Cause PCT 1.x can no longer initialize the virtual host adapter as a result of the Vbox adapter being deleted or removed. Resolution Reinstall PCT 1.x on top of your current installation. Your projects will not be modified in the process. Locate the installer. Run the installer, it will ask you to remove the previous version. Press ok. Progress will show as uninstalling. PCT will prompt for installation. Click Next. Select default installation paths. Click Next. Select desired PCT mode. Click next. Ready to Install selected mode. Click Next. PCT software installed. Click Finish. Now PCT will set up the Virtual Host Adapter. Press Ok. Status bar. Compted setup dialog. Click Ok. Run PCT. If successful you will see the template sets getting installed via the top right of the window. Open a project and test an AS/AS-P. If the above steps do not work, here are a few more to try:   Restart the machine after the PCT software finishes re-installing Right-click and select “Run as Administrator” Uninstall PCT software and Oracle VirtualBox and re-install once more   If PCT 1.x still will not work, please open a support case with your local Product Support Group.

Issue After 9 straight failed Workstation login attempts the SmartX Controller will be locked out. See Workstation lockout message below.   After 3 failed attempts to add an SmartX Controller to the device administrator the SSH connection will be locked out for the amount of time set in Workstation.    Product Line EcoStruxure Building Operation Environment Building Operation Device Administrator Building Operation Workstation Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Automation Server Putty Cause In order to protect the EcoStruxure system from potential security threats, there have been login lockouts put into place. Both scenarios of lockouts are only temporary. Resolution Locked out of SmartStruxure Workstation Once there has been 9 consecutive Workstation login attempt failures for a single user, that user will be locked out of Workstation for 1 minute.  Locked out of an Automation Server in Device Administrator Once there have been 3 consecutive SSH Automation Server login failures through Device Administrator (Adding an Automation Server into Device Administrator via IP address), the Automation Server will be locked out for a default of 15 minutes.   The SSH Console Lockout time is configurable and can be changed in the Security Manager section in Workstation.   

Issue EBO server (ES/AS/Edge) Trace.log shows COV publisher errors. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server - Standard Cause A BACnet device is misconfigured and trying to perform COV subscription that produces an error. Resolution Review EBO server Trace.log EXAMPLE:  2023-12-28 13:54:05.124 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:54:07.354 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:55:05.173 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:55:07.420 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:02.921 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:56:05.213 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:56:07.673 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:56:09.862 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:57:02.932 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:57:05.247 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:57:07.719 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:57:09.874 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f 2023-12-28 13:58:02.945 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f 2023-12-28 13:58:05.288 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 201> failed. Status: 0x8001001f 2023-12-28 13:58:07.767 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f 2023-12-28 13:58:09.889 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 205> failed. Status: 0x8001001f​ Lookup the BACnet Error Code: Decoding BACnet Errors - Schneider Electric Community (se.com) EXAMPLE:  0x8001001f is unknown object, so a device is trying to subscribe to an object (Object Type + Object ID) that does not exist. NOTE: There could be other error codes not used in this example that are reported. Enable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Information to Trace. Wait for time to pass so Trace.log can collect more records. Review EBO server Trace.log to find the new line before the error, identifying the controller with the misconfiguration. Example: MSTP device (MAC 3) on local MSTP network is misconfigured for unconfirmed COV to BV 202  2023-12-28 14:11:08.439 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 3 process 1: <binary-value, 202>, lifetime 18000s, unconfirmed 2023-12-28 14:11:08.441 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <binary-value, 202> failed. Status: 0x8001001f​ Example: IP Device (MAC 192.168.198.136:47808) is misconfigured for confirmed COV to AV 204  2023-12-28 14:07:03.073 [T] [2817683712] nsp.pin.BACnet.Oms.COV SubscribeCOV from local network, MAC 192.168.198.136:47808 process 1: <analog-value, 204>, lifetime 18000s, confirmed 2023-12-28 14:07:03.075 [E] [2817683712] nsp.pin.BACnet.Oms.COV COVPublisher: Subscribing to <analog-value, 204> failed. Status: 0x8001001f​ Disable trace by navigating to ~/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.BACnet/nsp.pin.BACnet.Oms/nsp.pin.BACnet.Oms.COV and change from Trace to Information. Inspect the listed BACnet devices and correct the misconfiguration.

Issue EBO system was in sync with Building Advisor Portal and is now not. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Automation Server Cause System ID changed and no longer matches in Building Advisor Portal. Resolution Check EBO Server Trace Log for nsp.pin.Cloud records and there should be one that shows "SystemId". Here is an example: 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterface Sending notification {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterfaceReal edgeAgent_sendMessage: {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} (retCode = 0) In Building Advisor Portal, check the BMS System Identifier to ensure it is the same and update as needed. In this case, d057cfba-9fc0-11e4-a62a-3417ebbed129 needed to be updated to 4ba3db45-0235-7146-981a-c81dc08e39bf

  Issue Erratic communication problems encountered during system migration from legacy products to AS-P controllers due to mismatched duplex settings. Product Line EcoStruxure Building Operation. Environment SpaceLogic AS-P SpaceLogic AS-B Cause Legacy controllers or existing devices supporting only Half-Duplex are incompatible with AS-P/AS-B controllers, which support Full Duplex 10/100BASE-TX communications. Resolution To address this issue, follow these steps: Install a managed switch: Introduce a managed switch between the devices to enable effective communication. Configure port settings: Utilize the features of the managed switch to configure each port according to the required duplex mode, either Half-Duplex or Full-Duplex. By implementing a managed switch, you can ensure compatibility between Half Duplex and Full Duplex devices, resolving communication problems and facilitating a smooth migration process.

  Issue How are Modbus 64-bit registers calculated in the Modbus limitations on an RP-C? Can both RS485 ports be used for Modbus on an RP-C? Product Line EcoStruxure Building Operation Environment SpaceLogic RP Controller series RP-C Modbus Cause EBO version 2023 introduced 64-bit register support in RP controllers. EBO Webhelp states that an RP-C has a maximum limit of 250 Modbus registers. It is unclear if a 64-bit register is counted as four 16-bit registers or just one register on the Modbus maximum count. The RP-C controller has two RS-485 ports, and it is unclear if both ports can be utilized for Modbus simultaneously. Resolution A 64-bit Modbus register is counted as one register in the Modbus maximum register count. The RP-C controller has two configurable RS-485 ports that can be used for: Sensor bus Room bus Modbus network As per EBO webhelp, the controller can host two networks, but only one network of each network type.

  Issue How can the WorkStation "Remember me on this computer" option be enabled or disabled? Remember me option is available; user can turn on or turn off remember me: Remember me option is enabled      Remember me option is unavailable; user can't turn on remember me: Remember me option is not enabled   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The availability of the "Remember me on this computer" option is determined by the security setting "Instruct clients to allow autocomplete of credentials." If this setting is unchecked, the server will disable the autocomplete feature for username and password fields on the login page, which also affects the availability of the "Remember me" option in WorkStation. Resolution For EBO versions 3.0 and higher: Remember me for WorkStation logins can be disabled on the server by navigating to Control Panel->Security settings. For EBO version 4.0 (EBO 2022) and higher: The availability of the "Remember me" option is determined by the "Instruct clients to allow autocomplete of credentials." setting. If the checkbox is checked, users can use the "Remember me" option. If the checkbox is unchecked, users will not be able to use the "Remember me" option. In EBO version 6.0 (EBO 2024) and higher, this option is unchecked by default for new installations. For upgrades, the setting chosen before the upgrade will be retained. For EBO version 3.x:  The availability of the "Remember me" option is determined by the "Allow Remember me." setting. If the checkbox is checked, users can use the "Remember me" option. If the checkbox is unchecked, users will not be able to use the "Remember me" option.

Issue Search widget graphics can't find graphic pages created under child servers.    Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause Currently, in EBO 2023, the dynamic search widget will only find graphic pages created on the server the user is logged into on WebStation. The dashboard search widget is not related to the native EBO search object and cannot search child servers. Resolution EBO 2024 (V6) or higher: From 6.0.1 it is possible to include TGML widgets from sub servers (all servers must have EBO version 6.0.1). Note that this functionality is only supported when you use HTTPS as the protocol between the servers, which is the default protocol in 6.0.1.   EBO 2023 (V5) or lower: If graphic pages are located under child servers, they need to be added to the dashboard manually.  Refer to: Adding a Graphic to a Dashboard

Issue The Insight Sensor and Multi Sensor Ambient Light Sensor require calibration before they can be effectively used. Product Line EcoStruxure Building Operation. Environment Insight Sensor. Multi Sensor Cause When setting up a new Insight Sensor or Multi Sensor device, the default settings for Gain and offset may result in inaccurate readings. Calibration is necessary to ensure accurate data collection based on the specific installation area. Resolution To perform the calibration, the following two tasks need to be carried out manually: Calibrate the Light Sensor: Conduct the calibration process in an environment without any daylight for optimal results. Set the light to 100%. Measure the lux level at the reference point using a lux meter. Adjust the gain settings on the sensor to match the measured lux level. Linearize the Feedback Signal: In some cases, lights may not provide a linear feedback (lux level) as the output increases. To compensate for this non-linearity, the signal from the controller is linearized before being sent to the output. During the optimization phase, the controller incrementally increases the output in 10% steps, measuring the adjacent lux levels for each step. The maximum lux supplement is calculated by subtracting the lux level at 100% output from the lux level at 0% output. After the optimization phase, breakpoints are determined and verified by re-running the test. If the results fall within the maximum difference limit compared to a linear signal, the calibration test is considered valid. Remember, performing the calibration process without any daylight present will yield the best results.