Building Automation Knowledge Base

Issue If the AS is configured to get the time from an NTP server the customer need to know how often the AS will ask the NTP server for the time.    Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Central  EcoStruxure Building Operation Enterprise Server EcoStruxure Building Operation Automation Server (AS/ASB/ASP) Cause In version 1.4, the AS asked the NTP server 1 time per minute. Starting in version 1.5, this was changed so the AS is using the standard solution for the NPT protocol. Resolution When using the standard solution in the NTP protocol as the AS does starting in version 1.5, it depends on how much the AS drifts from the NTP server. The faster the AS drifts, the more frequently the time is updated.   For more information regarding Network Time, please see WebHelp article 6370 and corresponding articles. 

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 When Vista Server is started the startup process just hangs. Product Line TAC Vista Environment Vista Server 5.x Cause There can be several causes for this issue. A common issue with this situation is the Vista database has been restored from site without the Lonworks NL220 or LonMaker database. When the Vista server is opened it is unable to contact the Lonworks database and repeated attempts cause the server to hang. Resolution It is possible to prevent the Vista server communications as well as other parts of the Vista server communication. Reference TAC Vista dll Manager to download a tool from the Community that will allow you to disable DLL files and find the cause of the issue. If you are seeing the scenario as stated in the above cause, you would disable Option "10: Network communication" and "11: Field bus communication" in this tool then select the Update button   You must remember to enable the options once you have finished with the site database. If you forget to do this the Vista server will not function correctly when you want to run a live database.

Issue Controllers are online but events are not being logged. No live event updates are showing in the All Events Status Page or being logged to the SecurityExpertEvents database. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause Below is a list of the current causes that may contribute to the issues described: The Event Server settings are not configured correctly. The Firewall is blocking required communications ports. The default Save Events action has been removed. The All Events event filter has an Event Type or Record Filter attached to it which is filtering out events. Resolution For Cause 1 Confirm that the Download Server, Event Server, and Controllers are configured correctly. Check all of the items in this Troubleshoot Security Expert Controllers showing offline article. For Cause 2 Check that any Firewalls are disabled or setup to allow all required ports through. See SX-SRVR Networking Guide for Administrators for further details. Also, confirm that any Anti Virus software is also not blocking required ports or Security Expert applications. For Cause 3 In Security Expert go to Events > Actions and confirm that there is a Save Events action configured for the Site. The action will look like what is shown below and can be manually created if it is not present. Figure 1 - Save Events Action For Cause 4 Ensure that the Status Page view being used is able to see those events and is not filtered in any way. Under Events > Event Filters check that the All Events Event Filter is not filtered and it is set to show all events and records. By default, this is not filtered and not able to be changed. On the Event Types tab ensure "Include All Event Types" is selected. Figure 2 - Event Filter Event Types On the Records tab ensure there is no record filter attached. Figure 3 - Event Filter - Records Then check that the All Events event report is using the All Events filter for All Record Groups.  Figure 5 - Event Reports All Events Note that a fix for the database is available.  Please contact your local support to verify and provide a fix for this issue.

Issue The SP-C Controller was deleted and recreated with the Controller wizard to create default objects. The Controller had previously been online and downloads were successful. After being recreated with the wizard, downloads are failing with a failed loading dat file error message seen in the Controllers Download Diagnostics Window. Failed to load DAT file. Path = 'C:\ProgramData\Schneider Electric\SecurityExpert\Download\13.dat' , Error code = 80070002 Product Line EcoStruxure Security Expert Environment Security Expert Client SP-C Cause The Controller still had configuration settings from the previous setup that were causing a conflict. Resolution Clear the Controller by factory defaulting it, then reconfigure. For instructions on how to default a controller, refer to the Hardware Configuration section Defaulting a Controller in the SP-C Installation Manual - System Controller.

Issue When SigUpgrade is run at Release 4.08, a DeviceCnf.rec file that was created at Release 4.04  (as opposed to being the result from a SigUpgrade from Release 4.03) fails to upgrade to 4.08 correctly, and leaves the file unchanged in the 4.04 format. Product Line Satchwell Sigma Environment Sigma Cause Occasionally, at Release 4.04 when a new DeviceCnf.rec file is created it is tagged "Version 0" instead of the correct "Version 1" Resolution The DeviceCnf.rec file can be still be upgraded to Release 4.08 but by completing an intermediate upgrade from Release 4.04 by any one of following releases: Sigma Release Build Number Release 4.05 3.42.34 Release 4.05 SP1 3.42.43 Release 4.05 SP2 3.42.48 Release 4.05 SEB 3.43.18 Release 4.06 3.44.14 Release 4.06 SP1 3.44.16 Release 4.06 SP1 3.44.18 Release 4.07 3 45 48 Release 4.07 SP1 3 45 51 Release 4.07 SP2 3 45 58   Then finally upgrade again to Release 4.08.57 before continuing with the upgrade..

Issue Clicking a graphic page link fails to open any graphic page, but when opening the path using the System Tree of the server that contains the graphic page, successfully allows the link to open the graphic page. When opening the same page using WebStation, the graphic pages all open successfully. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation 1.9.x or below. Cause Typically having 'dead links' or unresolved binds in any graphic page is the reason for the issue. WorkStation pre-loads all objects of the references to the graphics. This call (CSP GetObjects) fails since (at least) one path of the objects points to a server that does not exist. Unfortunately the protocol can't return the objects that do exist and WorkStation then marks all these objects as non-existent and fails to open the respective binding. This operation cannot be corrected in this version of WorkStation and requires an upgrade to 2.x or above to correct this. Resolution Two options are available Correct/remove all link bindings that are shown with unresolved references to invalid server paths. Example showing an Unresolved Binding Upgrading to Building Operation 2.0 or higher will also resolve this issue.

Issue There is a performance issue affecting the Infinet bus under an AS-P. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Premium Cause Product Support has requested a Trace log with increased reporting for use in troubleshooting the Infinet bus.  Resolution 1. Under the System Tree in Workstation, expand the Modules folder.        2. In the Module folder, under the Trace folder expand the Loggers folder.   3. Under Loggers, navigate to the following modules. nsp.pin.BACnet.Continuum nsp.BACnet.Continuum (EBO versions 2.0 and below only). 4.  Right click on each module to expose the module Properties and increase the reporting level to Trace.     5. Just below the Loggers folder, right click on the Trace Settings folder.   6. In the context menu under Trace Settings, select Get trace log.     The Trace log will appear as a text file in a text editor.  Save the log to an appropriate folder.   Be sure to return the reporting level on all modules to Information once you are finished gathering the logs.   Leaving the reporting level at Trace will fill up the Trace logs with Infinet log entries leaving very little room for anything else. 

Issue When a Modbus device comes back online after being offline a message is sent from the Building Operation Server to the Modbus device which looks similar to: WriteData TX on /dev/tac_comporta: 01 2B 0E 01 00 70 77 ReadData RX on /dev/tac_comporta: 01 AB 01 9E F0 This message can cause the Modbus device to restart or stop responding, is it possible to disable it? Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 1.5.xand above Modbus Device Socomec Power Meters Crompton Integra 1221 Power Meter Cause A feature was added in release 1.5 that is intended to read the device's identification (0x2B). It works by polling this function code (FC). If the Building Operation server does not get a valid reply to this message, it assumes it is not supported by the device and will not request this again. This is usually not a problem but some Modbus devices, such as those listed in the Environment above, are unable to handle this message and will stop communicating with the AS or ES. Resolution In Building Operation 2.0.4 and above the option to enable or disable the device identification request (Function code 2B) has been introduced, allowing the poll interval (and online detection) to be set. Some devices will stop responding to poll requests if the device identification is enabled. Once disabled the AS or ES and the device may need to be restarted to enable normal polling without any device identification request being sent and stopping the normal responses from the device.   In previous versions this message cannot be disabled, however, if device polling is disabled the device identification request won't be requested, which can be used as a work-around. To turn off the device polling: Open Properties Set "Poll interval" to "Inhibit" The trade-off with this workaround is that the online detection for the device is turned off, so the device will never go offline in Building Operation. In some instances, the third-party Modbus device will need to be restarted to allow communication to resume.

Issue When reviewing events from Doors or Users, the below error is shown. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state. Error - The communication object Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Client Workstations SP-C Controllers. Cause Firewall and/or Port settings are incorrectly configured. Certain ports must be opened to enable communication between the server, client workstations, and controllers. Resolution Check the Firewall to ensure that all required ports are open between the Security Expert Server, Security Expert Client Workstations and the SP-C Controllers. Refer to the IP Networking Ports section in the SX-SRVR Security Expert - Networking Guide for Administrators - Reference Guide for details on required ports.

Issue What is the maximum number of trend logs in a SmartX IP Controller? What is the maximum number of trend log records in a SmartX IP Controller? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Cause SmartX IP controller free object system memory is shared between objects and data in your application. There are no specific limits on the number of objects and/or trend logs that you can create. Several factors impact memory consumption: Every object added consumes a fixed amount of memory Memory is shared between objects and data. Adjustments to description fields or trend log buffer sizes will also impact the amount of memory consumed. Different controllers have different amounts of memory to start from. RPC controllers have roughly half of the memory of an MPC. Changes to EBO 3.X will also change the memory consumption, so upgrading your system may skew the memory consumption larger than it was in previous versions. Resolution After adding trend logs to the device consult the Free object system memory entry in the device report since this will help determine how much free memory is available. Trend log buffers are pre-allocated on creation of the trend object. The other place to find how much free memory the device have is in the device property page. This value can be put in a watch window, trended, or even bound to a low-limit alarm.     If the amount of free memory drops below 50 Kbytes, that is critically low available memory. A better target is to try to preserve 50% of available memory. Based on empirical testing, estimates of memory available inside a blank controller are: MP-C: 1890 Kbytes MP-V: 1780 Kbytes RP-C: 1115 Kbytes It is important to not overload the controller because the remaining memory can also be used for COV subscriptions (the last line in the table above). If there is no memory available, then opening a graphic which creates COV subscriptions could overrun memory or operate very slowly

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 When you attempt to save a Menta application in Workstation you will get an "Invalid Data" Error. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Menta Editor Cause Some public variable in the Menta application has had Initial bindings added that conflict with the EBO bindings. Resolution Remove the Initial bindings from the variables in the Menta application and use EBO bindings. To find these Initial bindings follow these steps, Edit the Menta device with the issue From the File Menu "export" the Menta application to a known location on the PC and save it as a MTA file. Browse to this MTA file you exported and open this file with the Menta Editor From the File menu select "Save as" option. Give the file a name and in the Save as Type select FDB (*.AUT) Using Note Pad++ edit the AUT file you just created. Search the AUT file for the label "InitialBindings" [see Figure1 below] Make a note of the objects with Initial bindings so the initial bindings can be deleted from the Menta file. In Workstation edit the Menta device and remove the initial bindings from the objects found in step 7 and change the name of the object noting the original name down. Save the Menta application to the server. In Workstation edit the same Menta device and rename the object back to the noted name in step 8. Save the Menta application.

Issue Instructions are needed to configure the new SMTP configuration. Product Line Andover Continuum Environment Continuum Non-Microsoft Exchange/Outlook SMTP Email Cause Configuration for the SMTP Configuration for email alarming in Continuum 2.00 through 2.03 Resolution In Cyberstation 2.0 and above, you no longer need Microsoft Outlook and Exchange to send email alarm notifications. Other SMTP servers can be used on the network and other email clients can be used also to send email alarm notifications directly to an intended recipient. Note: Public SMTP servers such as Gmail SMTP and Yahoo SMTP do not currently work with this solution as they require SSL or certain unsupported port combinations. The connections these servers establish cause connection issues within the SMTP application. Private SMTP (In-house) servers can be set up and used.   Steps to Configure SMTP Email Alarming   Open and Event Notification Navigate to the Actions Tab Select which events to receive email alarms Select the Delivery Tab Click the Add Recipient button to open the recipient configuration Browse for the recipient Cyberstation by click the ellipsis Select the recipient Cyberstation Select the SMTP Configuration button in the Recipient Configuration window Fill in the Server Configuration fields in the SMTP Configuration window Specify the SMTP Server address, port and login information Fill in the Email Configuration Specify the sender's email address - this is the email address the email will be sent from and it is also the email address that failed emails will be sent to    Type in a Subject line if needed or the default Continuum email subject line will be used Alarm Option Settings - Fill in the RetryCount and Retry Time fields  Retry Count - once you pass this value the email is dropped. The maximum Retry Count is 10  Retry Time -  field is in minutes. The maximum is 1440 minutes (24 hours) Adding an email address to the recipient list Click the Display Master List to open the SMTP Master Email Configuration Dialog Place a check in the check box to add an email address from the existing Master List to the Event Notification's recipient list and then click OK Adding or deleting email addresses from the Master Email list Open the SMTPMasterEmail Event Notification in the templates folder In the opened SMTPMasterEmail Event Notification click the Display Master List button Click the Add Recipient or Delete Recipient button depending on what is needed After selecting Add Recipient supply the email address in the recipient field and click Add Recipient After selecting Delete Recipient, select the address to highlight it and then click the Delete Recipient button. Multiple Selection is supported To deliver email notifications to the added email address, select the check box next to it Testing to ensure email address recipients receive emails Select the address you wish to test and click the Test Selected button Successful email to SMTP Server test will display a pop-up Failed email to SMTP server test will display a pop-up to the Sender's email address Final address configuration Recipients Configuration Options Place a checkmark next to the option needed Ex. Primary or Backup  SMTP Email A checkmark next to Repeat. Repeat will function as if it were an Outlook email alarm and send until the alarm is acknowledged. Known issues: In order for BACnet controllers to use the new SMTP feature, the following hotfix from the following link is needed.  CyberStation v2.00 (Only) SMTP Emailing & BACnet Alarms - Hotfix 2.03 contains the hotfix listed above   For additional information, see the Cyberstation Help, search for SMTP.

Issue How to display a binary on/off value for fan the following hardware outputs for a Xenta 102-AX graphic page: Fan command Heat 1 command Heat 2 command Damper open Damper close Environment Xenta 102-AX StruxureWare Building Operation TGML Graphics Cause Universal Outputs 1, 2, and 3 on a Xenta 102-AX are controlled via percent based values. Through hystereses, they will turn on and off. Without knowing the previous status of the output, values between 1% and 99% will be unclear as to the present value of the output. Note: due to this SNVT being of a user-defined type, TAC Vista Workstation is unable to display these values. This solution can only be applied to a SmartStruxure Solution. Resolution Navigate to the Xenta 102-AX object in Building Operation Drill down to Node Object [0] > nvoRawHwValues > Universal Outputs Current Value Use the following signals for a true/false status of each command: Damper Drive Down State Damper Drive Up State Universal Output1 state (fan) Universal Output2 state (heat 1) Universal Output3 state (heat 2)

Issue What is the unit load of SE8300 that will help me to count how many SE8300 controllers that can be added on AS ComA and ComB Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SER8300 room controller SE8300 room controller Automation Server Cause Documentation does not state the unit load of the SE8000 range Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SE8000 range use the ADM4850A transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/8 UL load. In addition the 100K local bias resistors have been eliminated and therefore the 1/8 UL of the transceiver would be the total UL presented to the bus by the SE8000.   Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus ADM 4850A0 0.125 Yes None None 0.125 Yes** ** Unlike the normally recommended interconnection of the communication common/reference (ground) terminal on all bus devices such as documented in the generic application note for the isolated RS485 bus interfaces, the Viconics bus should be operated with the communications REF (reference) terminal open on each SE8000 and not connected to the bus shield wire, or to any other circuit. Based on the above the total number of devices can be calculated as 32/0.125 = 256 The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore an Automation Server is limited to 127 devices per com port (254 total per AS) so this should effectively be the limiting factor.   Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue The value of an exported Infinet point is not updated in some or all of the subscribing controllers. Product Line EcoStruxure Building Operation, Andover Continuum Environment Building Operation Automation Server Continuum i2 Controller Cause The subscribing controller is offline or inaccessible when the IE update is broadcast. Resolution The main disadvantage with the Continuum Import/Export (IE) system is that, in certain cases, it is possible that the updated value may not reach one or more of the subscribers due to various reasons such as network or controller down problems, excessive traffic on the network, etc. This is not of big concern when the point is of an analog type that changes frequently such as a temperature input since the point will update again when the temperature changes in a matter of seconds or minutes at the most.  For binary values though, a missing update is a big concern. Consider an occupancy schedule point that turns ON at 08:00 and off at 17:00.  If a subscriber misses the 08:00 update the zones under control by the subscriber will be unoccupied the entire day. The Point’s Refresh Attribute. Continuum points have a ‘Refresh’ attribute that is used to force the IE system to send a new updated value, setting the refresh attribute to true forces the Infinity controller to export the point’s value regardless of whether it has changed or not. It is IMPERATIVE that a PE program periodically refreshes binary points that are exported in Infinity controllers such as i2 devices. In the schedule example described above, a program* can be added to the Infinet controller that hosts the exported point.  This program should be triggered by the minute system variable and coded as follows: *make sure the program is of the type Infinet Script Program This will ensure that any subscribers to the schedule OCC flag won’t go more than a minute with a stale value of the point. Refreshing points that reside under the Infinet interface of the Automation Server (EBO 3.1 and greater) If the point to be refreshed resides under the Infinet interface of the AS-P then there are some differences in the way the refresh is accomplished. The program will be of the type Script Program. The point will have a REFRESH property, you bind to the refresh property in the Script Program instead of the point's value. The most important difference is that while in the i2 device the export takes places when you set the value of the refresh property to true, in the Automation Server the export takes place when the value of the refresh flag is toggled, regardless of the value (true or false) Below is an example of a Script Program refreshing some value objects that reside at the Automation Server under the Infinet interface The statement DigValue1 = (DigValue1 = false) is just a very efficient way to toggle the value of the refresh property, it is equivalent to saying.... If DigValue1 = false then set it to true and if DigValue1 = true then set it to false. Things to consider when refreshing exported points. Do not refresh points at a fast rate as this will cause unnecessary traffic on the Infinet field bus, refresh rates of one minute or more are strongly recommended. For the same reason, when refreshing many points, the operation should be staggered to avoid flooding the Infinet bus with an avalanche of IE traffic at the same instant.

Issue Description of the Parameters used in the 102-AX Plug-In Product Line EcoStruxure Building Operation, TAC Vista Environment LonMaker NL220 HTML 102-AX Plug-In Cause This may aid in finding the SNVT associated with each Plug-In field. Resolution nviBoxFlow nvoActualValue nviAplicMode nviOccCmd nviEmergCmd nvoLocalLatch   INPUT OBJECTS nvoUnvInput1 nvoEmergCmd nvoAuxTemp1 nvoUnvInput2 nvoLocalOccLatch nvoUnvInput3 nvoCO2ensor nvoAuxTemp2 nvoUnvInput4 nvoSetPtOffset VAV STATUS nvoOccpncyStatus nvoUnitStatusMode nviTerminalLoad nvoSpaceTemp nvoEffectSetPt nvoBoxFlow nvoFlowControlPt nvoAirPressure nvoHighSpaceTemp nvoLowStaticPress nvoLowStaticPress nvoOAirFlowRatio NETWORK BOUND INPUTS nviApplicMode nviOccCmd nviEmergCmd nviAirFlowReset nviCO2 nviDuctInTemp nviOutsideTemp nviRelStPt nviUnvOutput1 nviUnvOutput2 nviUnvOutput3    UCPTcooling Band SCPTsetPnts.unoccupied_cool SCPTsetPnts.Standby_cool SCPTsetPnts.occupied_cool UCPTheatingBand SCPTsetPnts.unoccupied_heat SCPTsetPnts.Standby_heat SCPTsetPnts.occupied_heat UCPTovrdDuration SCPTmaxRange UCPTresponseRate nviSetPoint nciVAVSelctnCntl.oP.ESS (UCPTvavSelection UCPTnormalPeriod.minute UCPTnormalOpen Airflow Setpoint SCPTminFlow SCPTmaxFlow SCPTminFlowStby UCPTunocAirFlow SCPTminFlowHeat UCPTminFlowWU UCPTmaxFlowWU UCPTfanOnFlow UCPTfanOffFlow Airflow Reset nviAirFlowReset UCPTco2LoReset UCPTco2HiReset Outside Air Requirement UCPToccOAReqd UCPTunocOAReqd nvoOAirRatio Airflow Setting SCPTgain UCPToffsetPress UCPTpressCutOff UCPTairFlowCoeff UCPTloStatPrior  

Issue The error "Failed to Invoke the Security Expert Suprema Component" is seen when attempting to register/enroll a user's biometric credential at a Security Expert Client Only machine.   Figure 1 - Suprema scan error   When doing a registration/enrollment from the Security Expert Server this error is not seen and the registration is successful. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Reader Cause The Suprema.dll has not been properly registered on the local machine. Resolution First check in C:\Program Files (x86)\Schneider Electric\Security Expert folder and confirm that the three files Suprema.dll, BS_SDK.dll, and BS_SDK_V2.dll are all present. If they are not you will need to copy them over from a working installation of Security Expert Server Installation.   Now run the below commands via an Administrator authenticated command prompt session: For 64-bit machines cd C:\Windows\SysWOW64 regsvr32.exe “C:\Program Files (x86)\Schneider Electric\Security Expert\Suprema.dll” For 32-bit machines regsvr32.exe “C:\Program Files\Schneider Electric\Security Expert\Suprema.dll” You should get a pop-up saying the .dll was registered successfully. Close and re-open the Security Expert client and re-test enrolling a user's fingerprint.

Issue After installing a self-signed certificate via Internet explorer as detail in article  SSL Certificates - Security Certificate Risk warning logging in to WorkStation or WebStation using HTTPS  There is still a warning in Chrome and Firefox that the site is "Not secure" This warning is not seen in the earlier versions of Internet Explorer but from version 11 it is also seen in Internet Explorer. Product Line EcoStruxure Building Operation Environment WebStation Cause Different browsers have different policies to Self-signed Certificates and display a different warning, but still use HTTPS. These policies may change over time, but it is not something that can be controlled Without a neutral and recognized third party—such as a certificate authority—verifying certificate ownership, a certificate is meaningless. To better understand, when doing something like creating an HTTPS connection you have the following chain: A client web browser making the request to the server. The remote web server sending data back to the client. And an HTTPS certificate authorized by a neutral 3rd party that vouches that the server is who it is and the encryption is valid because of that. A self-signed certificate is inherently untrusted because anyone can generate a self-signed certificate. Anyone including an entity that deliberately pretends to be something/someone they aren’t. With a self-signed certificate there is simply no trusted third party that has the basic human procedures set to simply state, “Okay, this domain has a certificate we issued them and thus you can trust them. We say they are in fact the domain the claim to be and not an imposter.” And since anyone in the world can create a self-signed certificate on their own, it’s usage has inherent trust issues. What makes a certificate valid has very little to do with deep technology or encryption techniques but what makes it valid is a process centered around a neutral—and recognized—third party validating a usage procedure and browser makers adhering to respect of those procedures. At the end of the day, an encryption key pair is an utterly meaningless pile of bits and bytes without the enforcement of the processes and procedures that surround them. Resolution Internet Explorer - No warning Chrome - "Not Secure" shown Firefox - Initially a "Your connection is not secure" warning is seen "10.158.7xx.xxx:xxx uses an invalid security certificate. The certificate is not trusted because it is self-signed. Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT" Add Exception, allows access as below   The best way to permanently remove the warning is to pay for a certificate from a certificate authority. See this forum post on how to get generate and add a certificate from a certificate authority

Issue On a cold start, the i2 or b3 controller does not retain the configuration stored in flash memory. The controller error log shows a 0x000014fb error.   12     E      01/01/1989 00:02:10.00     0x000014fb     0x0928ab00     0x019085a6    0x1442000c Product Line Andover Continuum Environment Continuum b3 Controller Continuum i2 Controller Cause i2 and b3 controllers must compile the controller configuration prior to backing the configuration up to flash memory.  An invalid configuration will prevent the compilation process from completing, thus preventing the backup process from succeeding.     The most common causes of OMS Backup failures are Plain English programs that contain errors. Input or Outputs that are configured without a channel number.   Resolution Correct any configuration errors.  Initiate a backup of the controller configuration to flash memory. Verify that the backup has been successful.  There should be no 0x000014fb  errors in the controller error log. 

Issue How to register a BACnet device as a Foreign Device with ES/AS Product Line EcoStruxure Building Operation Environment ES AS WS BACnet Cause Documentation Resolution Before a device can register with ES/AS, the ES/AS has to be configured to assume the BBMD role by creating the BBMD under the IP Network of the BACnet interface. You can then examine the BDT00001 entry for the IP address and port your foreign devices will use to register. Configure the device to register as a foreign device with the ES/AS, in this example we have configured a bCX4040 using its configuration web page. (Note, in order to configure a bCX as a foreing device you must first disable the BBMD option in the bCX) If the device registration was successful, the device's IP address will appear in the foreign device table (FDT) of the ES/AS