Building Automation Knowledge Base

Issue Unsure whether a certificate is in the required PEM file format and what fields it includes to ensure the correct file is installed on the correct server. Sample of certificate -----BEGIN CERTIFICATE----- MIIF+TCCBOGgAwIBAgIRAOUXUXsbB/LpS0VTQsz/HFcwDQYJKoZIhvcNAQELBQAw gY8xCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAO BgNVBAcTB1NhbGZvcmQxGDAWBgNVBAoTD1NlY3RpZ28gTGltaXRlZDE3MDUGA1UE AxMuU2VjdGlnbyBSU0EgRG9tYWluIFZhbGlkYXRpb24gU2VjdXJlIFNlcnZlciBD QTAeFw0xOTAxMTcwMDAwMDBaFw0xOTA0MTcyMzU5NTlaMFAxITAfBgNVBAsTGERv bWFpbiBDb250cm9sIFZhbGlkYXRlZDERMA8GA1UECxMIRnJlZSBTU0wxGDAWBgNV BAMTD3dlYi1zZWN1cml0eS5jejCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC ggEBAMNC5twUz78YyvW9Y+avpBZLZjGFLZbNZN3tukWL/1wuwLUrhuCju1IDXWnJ a7vu4IFA/m/fgD68Y+I6BEF/tdw94TGc/X0n+Q326ZB3ff8e5+GF2o2oXQCUEX60 wGv17zIx8jCYZtaP9rWekUzWmkNPagImboWeYSLWkt7GvdJCU7VY8kpKm7Y/JF/P Qs4Z5+d4HMsfknJ+PofI7Ve3wT0aPE4aiQ3+MWryxcnZYzH7xNpeB7UbkfFIeDki 4X1vkVFM2Do07IkY9dO8d0UNI3lDDJDpxCCW4kVOl8yQTRtmyPZmtXk5uoyFcCEh KP5/T2gxNr9KNzIornE0F7LZfpMCAwEAAaOCAowwggKIMB8GA1UdIwQYMBaAFI2M XsRUrYrhd+mb+ZsF4bgBjWHhMB0GA1UdDgQWBBSHdiVoz7sMpYkdFsQWYHoMcJZU IzAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAdBgNVHSUEFjAUBggrBgEF BQcDAQYIKwYBBQUHAwIwSQYDVR0gBEIwQDA0BgsrBgEEAbIxAQICBzAlMCMGCCsG AQUFBwIBFhdodHRwczovL3NlY3RpZ28uY29tL0NQUzAIBgZngQwBAgEwgYQGCCsG AQUFBwEBBHgwdjBPBggrBgEFBQcwAoZDaHR0cDovL2NydC5zZWN0aWdvLmNvbS9T ZWN0aWdvUlNBRG9tYWluVmFsaWRhdGlvblNlY3VyZVNlcnZlckNBLmNydDAjBggr BgEFBQcwAYYXaHR0cDovL29jc3Auc2VjdGlnby5jb20wLwYDVR0RBCgwJoIPd2Vi LXNlY3VyaXR5LmN6ghN3d3cud2ViLXNlY3VyaXR5LmN6MIIBBAYKKwYBBAHWeQIE AgSB9QSB8gDwAHYAu9nfvB+KcbWTlCOXqpJ7RzhXlQqrUugakJZkNo4e0YUAAAFo Ww+ePQAABAMARzBFAiEAtZoULgmDyEppYK9nmDWNRjRGcE+BBo/DLaaoaYWg7C8C IH+0UCda6Txcl05inAsMpzlePELyZ3hawgEdmMugK3bXAHYAdH7agzGtMxCRIZzO JU9CcMK//V5CIAjGNzV55hB7zFYAAAFoWw+eiwAABAMARzBFAiEAmdEbql+1pWWf HmpkY34JziCOQzaDlFVtUFen+blgIWwCIBVnwDD3vnwSsrO2T5Clo5Pjqa+xxU7O trLo/ZRGkICBMA0GCSqGSIb3DQEBCwUAA4IBAQAzOM9lS3RSU7rLy8T3BfixHvua ErZ+YOHCHpYhlCeSuFZ66jVHueYWvgfF8A+enRdMM0k0z0PC9enREnumNDq3msCf WYhSLd5lDXiEddg2GCrXkwhOFfOiG0tywS5CD+hLsTq1LQkWDQg7EKlIb6ddhaZO IYEQ9xwE7aehynQEvAjv3UyevMYfvw7glY+MW5bkMfsxPndDD1gDbnYt8kyenjcv odjnkvTw4ngnCy1gF9mVWkgQsE1j34FER1bVtR/FlspI0FB+ogV4Qhso1N23DwtF VDKxH8p+ddYh1LX4b6Oy3dZqzt4HOcunPKsFv36ABpeTs8FPOjgQueTWfHQ4 -----END CERTIFICATE----- Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Building Operation Edge Server Cause A third party provides the certificate files and can have names different from the server installed on and in different formats. Resolution Open the file with a text editor (as seen above in the Issue section). PEM files can include a header or footer that could help identify the certificate. The example above does not. The body has a beginning and ending to describe its contents. —–BEGIN CERTIFICATE REQUEST—– and —–END CERTIFICATE REQUEST—– show a CSR in PEM format. —–BEGIN RSA PRIVATE KEY—– and —–END RSA PRIVATE KEY—– show a private key in PEM format. —–BEGIN CERTIFICATE—– and —–END CERTIFICATE—– show a certificate file in PEM format. The format would look like this if the PEM file included the SSL certificate chain. —–BEGIN CERTIFICATE—– //end-user —–END CERTIFICATE—– —–BEGIN CERTIFICATE—– //intermediate —–END CERTIFICATE—– —–BEGIN CERTIFICATE—– //root —–END CERTIFICATE—– NOTE: There must be a blank line after the END is defined. Ensure there is only one certificate in the file to examine. You may have to copy the file multiple times, open each one, and retain only one per file. Open Command Prompt and find a copy of OpenSSL installed on the machine. OpenSSL installed with EBO Use the following command, where server.pem is the file and file type you are inspecting. openssl.exe x509 -in server.pem -text -noout​ Example output from sample above.  Certificate: Data: Version: 3 (0x2) Serial Number: e5:17:51:7b:1b:07:f2:e9:4b:45:53:42:cc:ff:1c:57 Signature Algorithm: sha256WithRSAEncryption Issuer: C = GB, ST = Greater Manchester, L = Salford, O = Sectigo Limited, CN = Sectigo RSA Domain Validation Secure Server CA Validity Not Before: Jan 17 00:00:00 2019 GMT Not After : Apr 17 23:59:59 2019 GMT Subject: OU = Domain Control Validated, OU = Free SSL, CN = web-security.cz Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) Modulus: 00:c3:42:e6:dc:14:cf:bf:18:ca:f5:bd:63:e6:af: a4:16:4b:66:31:85:2d:96:cd:64:dd:ed:ba:45:8b: ff:5c:2e:c0:b5:2b:86:e0:a3:bb:52:03:5d:69:c9: 6b:bb:ee:e0:81:40:fe:6f:df:80:3e:bc:63:e2:3a: 04:41:7f:b5:dc:3d:e1:31:9c:fd:7d:27:f9:0d:f6: e9:90:77:7d:ff:1e:e7:e1:85:da:8d:a8:5d:00:94: 11:7e:b4:c0:6b:f5:ef:32:31:f2:30:98:66:d6:8f: f6:b5:9e:91:4c:d6:9a:43:4f:6a:02:26:6e:85:9e: 61:22:d6:92:de:c6:bd:d2:42:53:b5:58:f2:4a:4a: 9b:b6:3f:24:5f:cf:42:ce:19:e7:e7:78:1c:cb:1f: 92:72:7e:3e:87:c8:ed:57:b7:c1:3d:1a:3c:4e:1a: 89:0d:fe:31:6a:f2:c5:c9:d9:63:31:fb:c4:da:5e: 07:b5:1b:91:f1:48:78:39:22:e1:7d:6f:91:51:4c: d8:3a:34:ec:89:18:f5:d3:bc:77:45:0d:23:79:43: 0c:90:e9:c4:20:96:e2:45:4e:97:cc:90:4d:1b:66: c8:f6:66:b5:79:39:ba:8c:85:70:21:21:28:fe:7f: 4f:68:31:36:bf:4a:37:32:28:ae:71:34:17:b2:d9: 7e:93 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1 X509v3 Subject Key Identifier: 87:76:25:68:CF:BB:0C:A5:89:1D:16:C4:16:60:7A:0C:70:96:54:23 X509v3 Key Usage: critical Digital Signature, Key Encipherment X509v3 Basic Constraints: critical CA:FALSE X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7 CPS: https://sectigo.com/CPS Policy: 2.23.140.1.2.1 Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt OCSP - URI:http://ocsp.sectigo.com X509v3 Subject Alternative Name: DNS:web-security.cz, DNS:www.web-security.cz CT Precertificate SCTs: Signed Certificate Timestamp: Version : v1 (0x0) Log ID : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47: 38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85 Timestamp : Jan 17 09:06:16.765 2019 GMT Extensions: none Signature : ecdsa-with-SHA256 30:45:02:21:00:B5:9A:14:2E:09:83:C8:4A:69:60:AF: 67:98:35:8D:46:34:46:70:4F:81:06:8F:C3:2D:A6:A8: 69:85:A0:EC:2F:02:20:7F:B4:50:27:5A:E9:3C:5C:97: 4E:62:9C:0B:0C:A7:39:5E:3C:42:F2:67:78:5A:C2:01: 1D:98:CB:A0:2B:76:D7 Signed Certificate Timestamp: Version : v1 (0x0) Log ID : 74:7E:DA:83:31:AD:33:10:91:21:9C:CE:25:4F:42:70: C2:BF:FD:5E:42:20:08:C6:37:35:79:E6:10:7B:CC:56 Timestamp : Jan 17 09:06:16.843 2019 GMT Extensions: none Signature : ecdsa-with-SHA256 30:45:02:21:00:99:D1:1B:AA:5F:B5:A5:65:9F:1E:6A: 64:63:7E:09:CE:20:8E:43:36:83:94:55:6D:50:57:A7: F9:B9:60:21:6C:02:20:15:67:C0:30:F7:BE:7C:12:B2: B3:B6:4F:90:A5:A3:93:E3:A9:AF:B1:C5:4E:CE:B6:B2: E8:FD:94:46:90:80:81 Signature Algorithm: sha256WithRSAEncryption 33:38:cf:65:4b:74:52:53:ba:cb:cb:c4:f7:05:f8:b1:1e:fb: 9a:12:b6:7e:60:e1:c2:1e:96:21:94:27:92:b8:56:7a:ea:35: 47:b9:e6:16:be:07:c5:f0:0f:9e:9d:17:4c:33:49:34:cf:43: c2:f5:e9:d1:12:7b:a6:34:3a:b7:9a:c0:9f:59:88:52:2d:de: 65:0d:78:84:75:d8:36:18:2a:d7:93:08:4e:15:f3:a2:1b:4b: 72:c1:2e:42:0f:e8:4b:b1:3a:b5:2d:09:16:0d:08:3b:10:a9: 48:6f:a7:5d:85:a6:4e:21:81:10:f7:1c:04:ed:a7:a1:ca:74: 04:bc:08:ef:dd:4c:9e:bc:c6:1f:bf:0e:e0:95:8f:8c:5b:96: e4:31:fb:31:3e:77:43:0f:58:03:6e:76:2d:f2:4c:9e:9e:37: 2f:a1:d8:e7:92:f4:f0:e2:78:27:0b:2d:60:17:d9:95:5a:48: 10:b0:4d:63:df:81:44:47:56:d5:b5:1f:c5:96:ca:48:d0:50: 7e:a2:05:78:42:1b:28:d4:dd:b7:0f:0b:45:54:32:b1:1f:ca: 7e:75:d6:21:d4:b5:f8:6f:a3:b2:dd:d6:6a:ce:de:07:39:cb: a7:3c:ab:05:bf:7e:80:06:97:93:b3:c1:4f:3a:38:10:b9:e4: d6:7c:74:38 ​ Notable fields include, Issuer: CN = : This is the issuer's common name (CN), Sectigo RSA Domain Validation Secure Server CA, which is the name on the certificate that signed it. If it is the same as a Subject: CN =, then it is, in most cases, Self-Signed. CA Certificates are self-signed and added to a client system in a trust store to be trusted. Validity: Not After: This is the expiration date Subject: CN = : This is the server on which it should be installed common name (CN), in this case, web-security.cz Subject Alternative Name: This Subject Alternative Name (SAN) field can specify alternate server names, like local DNS or IP address. If this server is being used to server content from multiple domains and/or subdomains, all will be listed here. In this sample, two DNS names are listed: web-security-cz and www.web-security.cz. Compare the Common Name (CN) or Subject Alternative Name (SAN) to the address or IP address used to access the server; if it is not one of the included names, then certificate validation will fail. Reference this article to check validity: Verify certificates with OpenSSL

Issue Can the user set the 'Number of States' and the 'State Text' in a multi state object? Product Line EcoStruxure Building Operation Environment BACnet b3 controllers Multi-state values Cause The b3 firmware does not allow the Number of States or State Text to be modified This is Function as designed. Resolution Continuum DOES NOT allow changes to the default number of states and state labels. The 'Number of States' field is read only. An attempt to change any of the label will result in the following error: An error code was returned from a BACnet operation, but the reason could not be determined. The same is seen in EBO if any attempt is made to edit the State Text, see below

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

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 Importing certificates into EBO may require OpenSSL to perform the tasks. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Device Administrator Building Operation Automation Server Cause OpenSSL needs to be used to manipulate certificates so they are in the correct format for importing into EBO Servers. Resolution OpenSSL is installed with Enterprise Server, Enterprise Central, and Device Administrator, so use the following path to resolve your installation. In this example, EBO 2022 is installed on the C Drive, so a change in the path may be necessary for your installation. In EBO 2023, OpenSSL was upgraded to 3.x version (3.0.8 dated 7 Feb 2023). Enterprise Server Location: C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\bin\openssl.exe Device Administrator Location: C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 4.0\Device Administrator\OpenSSL\openssl.exe One can use the command openssl version to see the version installed. In this example with EBO 2022 OpenSSL version 1.1.1l (Letter L) dated 24 Aug 2021 is installed.   Enterprise Server  Device Administrator  Use Copy Path to use openssl.exe in the current directory In Windows Explorer, find openssl.exe Hold SHIFT, Right-Click on openssl.exe, and select Copy Path Paste into the command prompt, and you will see double quotes since the path can contain spaces. Continue to type your command and reference files by name in the current directory. 

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.    

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 In some cases, the event and trend databases can grow really big, although not all the space in the files is used. Therefore, one needs a way to verify that vacuuming the database will help. Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Definitions are documented here: https://www.sqlite.org/pragma.html  PRAGMA schema.freelist_count; Returns the number of unused pages in the database file. PRAGMA schema.page_count; Returns the total number of pages in the database file. PRAGMA schema.page_size; Returns the page size in bytes (B), which must be a power of two between 512 and 65536. Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: SELECT (SELECT freelist_count FROM pragma_freelist_count()) AS FreeList_Count, (SELECT page_count FROM pragma_page_count()) AS Page_Count, ((SELECT page_count FROM pragma_page_count()) - (SELECT freelist_count FROM pragma_freelist_count())) AS Used_Page_Count, ROUND(CAST((CAST((SELECT freelist_count FROM pragma_freelist_count()) AS REAL) / CAST((SELECT page_count FROM pragma_page_count()) AS REAL)) * 100 AS NUMERIC),2) AS Percent_Free, (SELECT page_size FROM pragma_page_size()) AS Page_Size_B, ROUND(CAST(((SELECT freelist_count FROM pragma_freelist_count()) * (SELECT page_size FROM pragma_page_size())) / (1024.0 * 1024.0) AS NUMERIC),3) AS Estimated_Space_MB; Click the blue play button above the Query tab.  Review the Percent_Free and Estimated_Space_MB, which will be returned at a minimum, to decide if you want to perform the 'vacuum' command. The vacuum process is slow, as it was designed to operate in the background. Shrink the SQLite event and trend databases. If the Percent_Free is above 80, this is the better option: Shrink the SQLite event and trends databases (Option 2) by creating a new file.

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 In some cases, the event and trend database can grow really big, although not all the space in the files is used. In extreme cases, there is more free space than used space and it is quicker to create a separate file. Product Line EcoStruxure Building Operation Environment SQlite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: VACUUM main INTO 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 6.0\Enterprise Server\db\Historical\event2.db'; Update the path to match your installation. One can SHIFT-RIGHT-CLICK the event.db or trend.db and select Copy as Path, then select everything inside the single quotes and paste. The paste will include double quotes, so delete those and leave the single quotes Update the database name to ensure it is unique. Click the blue play button above the Query tab. Depending on the size and amount of free space, this can take seconds to days to complete. One can monitor the progress in Windows Explorer by seeing the Size and Date Modified field update. Append .old to the end of the original file and rename the new file, event.db or trend.db, so it replaces the original. Start the Enterprise Server or Enterprise Central.

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 Modicon Switch Ordering options and how to configure the Ethernet Switch for RSTP for EBO Product Line EcoStruxure Building Operation Environment Modicon RSTP Switch (Not Connexium) Building Operation Automation Server Premium MPX and/or RPX Controllers Ethernet Switch Configurator Cause Schneider Electric Industry Offers an RSTP enabled Ethernet Switch that can be used with EBO instead of 3rd party Switches Resolution The following video will illustrate the following steps for Ordering and installing the Modicon Ethernet Switch with EBO The Modicon Connexium Ethernet Switch has been replaced by the updated Modicon Switch Modicon Switch Part Numbers and Email address for ordering Connect and use the SE Ethernet Switch Configurator executable for Switch configuration Set the Time and use the Syslog for troubleshooting Configure EBO and the controllers (MPX/RPX) for RSTP Test the Modicon Switch, EBO, and the MPX/RPX controllers for RSTP     Related Links: Modicon Switch Part Numbers and Ordering Information - (see attached Part Number slide) MCSESM Switch Installation Manual MCSESM Switch Configuration Manual Ethernet Switch Configurator Software - look for  SchneiderElectricEthernetSwitchConfigurator2303_Windows_x86.zip Other Modicon Switch documents RSTP Troubleshooting Community Thread TGML Graphic Setup Video (Training Department)

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 How to trigger different alarms with different alarm texts depending on the value of a single variable Product Line EcoStruxure Building Operation Environment Building Operation Workstation Alarms Cause There is a requirement to trigger different alarms based on the value of a single variable.  As an example, a variable coming from an APC Symmetra UPS will report various alarm states as a number from 1 to 7 in the same variable, and it is required to differentiate the alarm text on each value. Value Status Alarm text 1 unknown Module is in Unknown state from UPS 2 not installed Module not installed in UPS 3 Off OK Module not installed in UPS 4 On OK Module not okay in UPS 5 Off Fail Module off fail in UPS 6 On Fail Module on fail in UPS 7 Lost Communication Module lost comm. in UPS Resolution Here are two examples on how to do it Example 1: 7 different alarms with different alarm texts monitoring the same point Example 2: 1 alarm monitoring a point, and a script dynamically changing the alarm text     From version 1.9 upwards Alarm Decoration is available and could also be used in various ways to achieve the same result.  Similar to example 1 a decoration could be created for each state.  For example for state 3, create a decoration that filters on the active alarm (1) and when the value at change is three (2) override the alarm text message (3) with the relevant text (4). The decorations have the added benefit they can be applied to multiple point alarms.  

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.