Building Automation Knowledge Base

Issue User keeps getting re-prompted for login for each station even though using virtual domain. Each station file has been edited to include the cookieDomain slot.  Also, each station’s “hosts” file has mapped every station’s IP address in the virtual domain to their hostnames. Everything seems to be configured correctly. Environment Niagara R2 Cause Host (station) names contained underscores. The hostname cannot contain underscores. Resolution The station must be renamed without underscores. Change the hostname to match the new station name.

Issue Unable to open graphics that are on a shared network drive Product Line INet, Continuum, Access Expert, Security Expert Environment Windows 10 Chrome Windows IE Cause A registry setting is overridden or needs to be reset that was not previously not there. Resolution This is a Microsoft Issue. Here is a link that describes the resolution: https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command

Issue Created new bCX and can't see any of the system objects like system variables Environment CyberStation bCX4040 ACX57xx Cause CyberStation failed to fully create the new controller object in the database.   Resolution Delete the newly created controller from the ContinuumExplorer. Restart CyberStation. Create the controller again.

Issue Editing Multi-Stage control objects. Environment Sigma Control Multi-Stage Multi Stage Cause Multi-Stage control objects cause the controller to lock up when edited. Resolution The exact cause of this issue has not been located, but here are two suggestions. Download the complete object file periodically when editing these objects. If contingency logging is enabled on the multi-stage control object, it should be disabled before working on that object.

Issue How to upgrade an Automation Server if Port 80 is closed and the Automation Server is placed behind a NAT router. Getting error message when upgrading: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Cause The problem is that the certificate are generated with the IP address off the Automation Server, and not the NAT Router IP. Resolution The Device Administrator has the option to add SAN's (Subject Alternative Name) and not just the address of the server. So add both the LAN and the WAN addresses in the SAN field when you generate the certificate and transfer to the server.

Issue In LonMaker, how do I get rid of multiple message tags within a base unit virtual function block? Environment Vista Site Cause In LonMaker, how do I get rid of multiple message tags within a base unit virtual function block? Resolution Right click on the VFB and select to delete NVs & MTs. All unconnected message tags will then be deleted.

Issue Only one of the readers on a 7920 DPU works Environment 7920 DPU Cause If you have defined one door in the DPU 7920, and the door’s Exit Reader parameter is set to anything other than "NO," then the second reader port automatically becomes the exit reader. Resolution If you have defined two doors in a DPU 7920, neither door can have an Exit Reader defined.

Issue After creating an output point on an XPD02 attached to a BCX the output is not working.  The CPU light of the XPD02 stays solid ON. Environment XPD02 BCX Expansion Modules Cause The expansion module was connected to the BCX while powered. Resolution Reload the BCX.

Issue When using PSI 4.1 in direct connect mode, the baud rate is modified and saved but it will not communicate at the new rate. Environment PSI 4.1 Cause A baud rate change in PSI direct connect mode does not take affect until the PSI program is closed and restarted. Resolution Closed the PSI program and restart the program for the new baud rate to take effect.

Issue TreeTech 3.1 is installed on a Windows 7-32 bit computer.  After receiving the unlock code and entering it, a pop-up error window appears stating "Cannot Access Registry". Environment TreeTech 3.1 Windows 7-32 bit Cause The Windows user account was not configured for a password. Resolution Modify the Windows user account to ensure it has administrative rights and that it has a non-blank password.

Issue After Sigma transition into EBO, upon alarm and alarm clear there is no requirement to acknowledge the alarm. In the Sigma Interface, the object alarm 'Type of Acknowledgement is set to 'No' and cannot be changed. Product Line Ecostruxure Building Operation, Satchwell Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Alarm Priorities are incorrectly set in Sigma Alarm Manager. Resolution During the Data Import into EBO, the settings of the Sigma Alarm Manager is checked and the alarm acknowledgement type is set to a specific type. If no alarm priorities are set for acknowledgement in Sigma, then this is repeated in EBO.    To change to 'Single' so that alarms and alarm clears are able to be acknowledged, in Sigma: Open the Alarm Manager and go to the menu options: Configure > Acknowledgement Groups   Redistribute the alarm priorities into the the different acknowledgement groups as per the site requirement. The image below shows the default view on a new install of Sigma.   Redo the Data Import, the 'Type of Acknowledgement' is now seen to be set to 'Single'. However, If it is now showing 'Extended', then the KB article Type of Acknowledgement set to 'Extended' on Sigma Interface object alarm will explain how to change this.

Issue Upgrading an end customer copy of WorkPlace Tech from version 5.8.1 to 5.8.2. Is there a charge for it? Environment WorkPlace Tech Cause Cost estimating for end customer's system upgrade Resolution There is no charge when upgrading WorkPlace Tech from 5.8.x to 5.8.y. Charges apply when upgrading WorkPlace Tech 5.7.x to 5.8.x.  

Issue Attempting to start or stop a Programmable Function fails and one of the following errors is shown. The programmable function have reported connectivity issues and may not have started correctly. Please ensure all required controllers are online and try again. The programmable function have reported connectivity issues and may not have stopped correctly. Please ensure all required controllers are online and try again. Programmable Function error Product Line Security Expert Environment Security Expert Client Cause The Programmable Function is not enabled to support manual starting or stopping. Resolution On the Programmable Functions General tab, enable the Support Manual Commands option. Support Manual Commands This enables the operator to manually control the function from within the Security Expert software, for example, by right-clicking on the function and setting the value.

Issue Receive API error codes while trying to connect my API to BDP. Product Line EcoStruxture Building Data Platform Environment Building Data Platform Cause Receive the following Error codes: 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 500 Internal Server Error Resolution 400 Bad Request The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing) 401 Unauthorized Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response 403 Forbidden The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server 404 Not Found The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web 500 Internal Server Error The server has encountered a situation it does not know how to handle   Successful responses 200 OK The request succeeded. The result meaning of "success" depends on the HTTP method: GET: The resource has been fetched and transmitted in the message body HEAD: The representation headers are included in the response without any message body PUT or POST: The resource describing the result of the action is transmitted in the message body TRACE: The message body contains the request message as received by the server 201 Created The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests. 202 Accepted The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.

Issue After transitioning SP-AC1, hardware does not respond to manual commands. SX Client shows a valid read and shows the lock has been activated but the hardware does not change state (locked or unlocked) Product Line EcoStruxure Security Expert Environment Security Expert Cause The reader module type configuration did not transfer during the transition In Continuum, IOU modules (in Listview) show ProgramID value is empty/blank when it should have firmware version and module type Resolution In Security Expert, go to Programming|Outputs|General Tab Select irresponsive Module Change Address Module Type from <None> to <Reader(RD)> Save changes Test card read or manual lock

Issue When a TGML graphic is opened from Webstation and the user right clicks on a value in the graphic to open properties, it can take up to 20 seconds before the properties dialog is displayed. During the 20 seconds the working area is just grey. Product Line EcoStruxure Building Operation Environment Building Operation Webstation 2.0.4 and earlier versions Cause This problem only occurs when the signals in the graphic resides in a TAC Xenta; The problem has not been observed with Modbus or BACnet signals, and is only present in Webstation, not in Workstation. Resolution This issue is fixed in EBO 3.0. There is also a hotfix for version 2.0.4. It is labelled 2.0.4.5801. Contact you local technical support organisation if you need the hotfix.

Issue Getting error message when selecting Character set file for the TAC  Xenta Operator Panel (OP).     Product Line EcoStruxure Building Operation, TAC Vista, Xenta OP Environment TAC Xenta OP EcoStruxure Building Operation Microsoft Windows 10 Cause Microsoft Windows 10 does no longer allows the software to change files in all directories. Resolution Manually open up the directory C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation 3.2\WorkStation\CharSet.lib Select the Charset you want to use, depending on the language, and copy the file. Remove the extension, so that the file is named Charset, without any extension. Manually open up the directory C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\WorkStation\Function Block Editor Paste the copied file here.

Issue In LonMaker, an incorrect number of targets were selected when creating a connection resulting in NS Connections #1 lcaErrConninvalidTargetcount error. Environment LonMaker Vista Cause In LonMaker, an incorrect number of targets were selected when creating a connection. Resolution You must specify at lease one and no more than 25 targets when adding members. To add more members, you must invoke the Connect method multiple times.

Issue After a PIN Duress Event at a door, the Duress Trouble Input stays "ON" and is unable to reset or restore the trouble input until a Valid Access Event occurs at the door. Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause Attempting to restore Duress Trouble Input remotely after an accidental PIN Duress Entry by Card Users Resolution This is the intended design and function of the PIN Duress Trouble Input. It is considered an extremely-high priority issue and must be restored by a specific physical action. Remotely restoring (via Keypad in another location) would defeat the purpose of the PIN Duress Trouble Input. This is intentional to prevent a real duress event from going unnoticed.

Issue The setpoint values are displayed briefly and then change to 621.X on the Proview display? Environment All LON proview installations. Cause This occurs when the setpoints are being written into network variable inputs (nvi).  The nvi's default to using the receive heartbeat and will fallback to default after the timeout occurs.  Proview does not perform a send heartbeat function as the connection is an nv update and not an actual binding. The receive heartbeat mechanism in the MNL controllers cause the nvi values to fallback to NA upon heartbeat timeout. Resolution The heartbeat can be disabled for the setpoint nvi, however nvi values are stored in RAM (not EEPROM) and will return to default upon a controller power cycle.  The best solution is to use network configuration inputs (nci) for setpoint displays on the Proview.  These do not have the heartbeat issue and the values are maintained in EEPROM so they are not lost following a controller power cycle.