Building Automation Knowledge Base

Issue Seeing 0x00001427 Bad RTC chip errors in controller error log along with controller warm start errors. Controller error log contains entries similar to below.    01/01/1989 00:01:10.33 0x00001427       0x04070400       0x02028922       0x00000001       0x0000000                 HardwareErr__ Bad RTC chip 04/16/2011 09:47:24.93 0x00030000       0x00216500       0x00105c62       0x00000000       0x00000000                Warm start 01/01/1989 00:00:00.94 0x00001427       0x00201900       0x0011edba      0x00000001       0x00000000                 HardwareErr__ Bad RTC chip Environment Continuum Controllers Cause The error is a time related error but may not indicate that there is a physical problem with the controllers Real Time Clock (RTC). This can be due to an issue occuring on startup of a controller where there may be requests for time from COV updates. If that request comes in prior to the RTC clock coming up, it can post this error. The COV code will post this error and then try again later.  Resolution If this error occurs after a restart of the controller then this is more than likely a benign error and can be ignored. However, if it occurs when the controller hasn’t just restarted then it could be an actual fault with the RTC chip and may need to be returned for repair.

Issue Browsing between different records in the Security Expert Client is slow. It takes a longer than normal amount of time to see records update. Product Line EcoStruxure Security Expert Environment Security Expert Client Cause There are a large number of unacknowledged alarms being stored in the SecurityExpertEvents database. When the Security Expert Client starts up it will process all of these unacknowledged alarms which can impact browsing the database. Resolution To resolve the immediate problem: 1. Reduce the size of the SecurityExpertEvents database by reducing the overall number of events that will be stored. Setting up automatic event purging and backup helps keep this in check. Under Global | Global Settings | General change the Purge Events older than from the default setting of "Never" to another value from the drop down menu. To backup these events before being purged, ensure the Generate Differential Events Backup option is checked. This is the default setting. 2. If there are more alarms to be acknowledged than can be done manually then contact Product Support mentioning this Knowledge Base Article. Remote access to the site and SQL Server will be required.   To minimize this from happening again: 1. Reduce the amount of events that are setup as alarms. Remove any alarms that are setup for All Events and review any configured alarms to ensure those events are required to be generating alarms. Double check all Inputs and Trouble Inputs to see if they have the Log to Event Buffer option enabled. Not all inputs will require this for normal operation and in some cases having this enabled can result in a large number of unwanted events being logged. This, in addition to an alarm setup to monitor the All Events event filter, is a recipe for disaster resulting in a large number of alarms being generated in a short amount of time. 2. Ensure that a large number of unacknowledged alarms are not allowed to build up over time. Alarms are not able to automatically acknowledged and will stay in the active alarms list until an operator acknowledges them. Operators need to acknowledge alarms on a regular basis. Note that it is possible to batch acknowledge blocks of alarms at one time in the Security Expert Client by doing a multiple selection then right-click acknowledge alarm. Note: If your system has already built up a large number of unacknowledged alarms and you want to quickly acknowledge them all at once to get back to a manageable starting point, then please raise a Support Case with your local Customer Care Centre and Product Support can assist in doing this with a 'one time' SQL Query direct to the Security Expert Database.

Issue The connection to the MQTT broker is not working and the MQTT client in the ES is offline following an upgrade from EBO 2022 to EBO 2023. The following error message can be seen in the ES trace.log: nsp.csc.mqtt.MqttNetwork Connection failed: TCP/TLS connect failure  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central MQTT integration Cause The reason for the connection issue is that the client certificate that is used is (self-signed) signed using SHA1. Since OpenSSL 3.0 this is forbidden at the default security level (which EBO is using) due to it having less then 80 security bits. See text in picture below taken from https://www.openssl.org/docs/man3.0/man3/SSL_CTX_set_security_level.html The default level is 1 and that is the setting EBO is using. Resolution Change the client certificate to one not using signing signature MD5 or SHA1. The certificate signature can be checked using the following OpenSSL command: openssl x509 -in cert.pem -noout -text Below is an example of how to use OpenSSL to check the certificate signing signature on the client certificate:

Issue I/A Series Micronet LON controllers (MNL) SNVTs list Product Line TAC IA Series Environment I/A Series Micronet LON (MNL) controllers Cause The SNVTs available in an I/A Series MNL controller are not listed on the datasheets.  Resolution The SNVTs list for various MNL controllers' LonMark profiles can be found in the WorkPlace Tech 4.0 Engineering Guide appendix B. 

Issue Outside sensor not working on a DC1100 or DC1400 Environment DC1100 DC1400 Cause Outside sensor not working on a DC1100 or DC1400 All wiring and terminations have been checked but the outside air sensor is not working. Resolution On the DC1100 and DC1400, the outside air sensor can be shared between a maximum of 3 controllers. The switch on the rear must be in the up position on one of the controllers. If there is only one controller fitted, the switch on the rear must be in the up position.

Issue In Niagara G3, a BACnet proxy point was initially added to the database as Read only; how can it be change to a BACnet Writable proxy point? Environment Niagara G3 all versions Cause BACnet proxy point type (read only. writable, etc.) is selected when the proxy point is first added to the database. The BACnet Proxy Point was initially discovered and added to the database as Read Only Proxy Point. Resolution Unfortunately, once the BACnet Proxy Point is added to the database its Type value can not be changed. The Proxy Point will have to be deleted, rediscovered and re-added to the database. This time when adding the Proxy Point to the database, make sure to select writable for Type.

Issue Previously purchased WorkPlace Tech software is being moved from one computer to another. What proof of purchase is required for the software so that the purchase of a new copy is not required? How can they prove that they purchased the original copy if the original purchase order and invoice or license request form with unlock code cannot be located? Product Line TAC IA Series Environment WorkPlace Tech 5.x.x NOTE: Old installation must be of same major release (release 5) as the new copy being installed. If the old system has release 4 of the WorkPlace Tech software, the new computer will need to be running Windows XP and the release 4 version of the WorkPlace Tech software will have to be installed on the new computer. Cause Software needs to be migrated to a different computer. This could be due to an upgrade in hardware. Resolution The preferred proof of purchase is a copy of the license request form that shows the customer information, license requested, license unlock code, and the original sales order number. Depending on when or how the license for the existing copy of the WorkPlace Tech Tool software was ordered, this document may have been received by fax or email. If this information is available, a copy can be emailed along with the new license request form (requesting the same product license as the original) to IASeries.license@schneider-electric.com. Note that in some cases the new product code may vary slightly from the original. For example, the original license may have been for WP-TECH-52 and the new one for WP-TECH-58 or WP-TECH-50 -- these licenses are all equivalent. The WIB licensing team will verify the submitted information and if complete/correct, generate the new license unlock code. If the old computer is still functional, the License Diagnostic program can be used to generate a proof of purchase for the software installed on the computer. Use the following procedure to locate the proper version of the program and to generate the license diagnostic text file. NOTE: If the old computer has WorkPlace Tech release 4.0.0, skip step 2 in the following procedure. Open the Windows Explorer (My Computer icon) Search for the file "WPTLDiag.exe" in the Program Files folder of the C:\ drive (or drive where the program files have been installed). If found, skip to step 4, below. Search for the file "WIBSLicenseDiag.exe" in the Program Files folder of the C:\ drive (or the drive where the program files have been installed). Right-Click on the file found in step 2 or 3 and select "Open". This will cause the license diagnostic program to run. When the program opens its display, select Save from under the File menu and save the "WIB License Diagnostic.txt" file. On the new computer run the "Purchase WorkPlace Tech Software" or "Purchase WIBs Software" from the icon on the desktop and fill out the Field Office & Shipping information sections using the information for your office. The "End Customer Information" must match the information from the old system. In the Package List, the same product should be selected as was licensed on the old system. In some cases, the part number may be slightly different, for example, the old system may have been licensed for WP-TECH-53U and on the new system, the product code may be WP-TECH-50U. These license product codes are equivalent. Add the selected package part number to the order list, click the [Accept Order] button and output the order form to a file. Click the [Done] button to exit the purchase screen and click [Done] to exit the Purchase program. Email the saved license diagnostic form and the saved order form to Product Support Services for verification. Product Support Services will verify the information and if correct, forward the information to IASeries.license@schneider-electric.com for processing. They will email the unlock code back to the requesting office. Follow the normal procedures to install the unlock code.

Issue Vista Server can read values on a LON device, but when this same device is used in an Xbuilder project for a Xenta Server no values can be read. Product Line TAC Vista Environment FT-10 LON Network Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause The XIF file of the LON Device does not conform to LonMark standards for self documentation. Vista Server can recover from this and assumes all SNVTs are from the default function block, but XBuilder cannot. On the third line of each variable declaration is the self documentation: 1: VAR nvo01Value 2 0 0 0 2: 0 1 63 1 0 1 0 1 0 1 0 0 0 3: "@1|2 The correct format is to show the functional block number and the member number separated by either a | or # character. Improperly formatted self documentation include the following: "nvo01Value - Does not define the function block or member number. "@_1|_1 - Uses _1 which is not a valid number. "&3.4@0,20000-MP580 - Uses a - (dash) which is not valid It can also be because SNVTs from devices are bound directly to Menta programs in a Xenta 7XX. If the procedure below doesn't solve the issue, refer to Graphic values not updating in a network that includes a Xenta 7XX. Resolution The XIF file must be edited to correct the self documentation. Right click on the controller in Vista Workstation and open the properties window. On the XIF file tab find the file name of the XIF file. Open this file from the $thisfil directory in the Vista database folder. Modify the XIF by manually correcting these invalid lines of self documentation. It is recommended to use the default function block (0) and start with member index 50 to ensure no overlap. Increment the member number for each SNVT. "@0|50 "@0|51 .... Once the XIF file has been updated save it under a new name in the $thisfil directory. In the device properties browse to the new XIF file. Log out of workstation. Log in to workstation. Insert the LON network into Xbuilder. Generate the project and send to the device.

Issue In Function Block Editor, it is possible to define units for function blocks, and these units can only be set to basic units. There is no way to add a metric prefix to the unit. For example W or Wh can be used, but it is not possible to define kW, MW or kWh, MWh. Unit configuration in Function Block Editor v. 1.8 Product Line EcoStruxure Building Operation Environment Building Operation Workstation version 1.8 or earlier Cause Metric prefixes are not implemented for function blocks in Building Operation version 1.8 or earlier. Resolution Upgrade EcoStruxure Building Operation to version 1.9 or later. When editing a function block In Function Block Editor click Select unit and choose unit and Prefix. Function block with prefix in v. 3.0

Issue Attempting to commission a controller in an LNS environment results in the following error: Cannot communicate with the device. (Subsystem:  NS, #26) Environment LonMaker, NL220 Cause An NS, #26 error indicates a complete failure to communicate.  Most often this will be the result of physical layer problems.  In some situations it maybe due to a failed controller. Resolution Check the obvious physical layer connections: Is the cable plugged into the laptop to connect to FT-10?  Is the router between the computer and device being commissioned online and communicating?  Are the wires terminated properly at the controller?  Is the controller powered? Are there end of line terminators fitted? Inspect the controller: Are the LEDs blinking as designed? Are you able to receive a service pin from the device? Does an MOT or NXE need to be reloaded to the device? Typical troubleshooting techniques will usually resolve an NS, #26 error once it is understood to be a complete lack of communication at the physical layer.

Issue Some things to look for when you get ID 0 errors when doing a Save to Database Product Line Andover Continuum Environment Continuum Database Cause There are several causes such as date and time settings, scan variables, IP addresses, etc. Some troubleshooting steps are listed below based on different possible causes. Resolution Confirm that the date has been set in the controller. Edit the scan system variable and put a description in the description field. Doing this will update the LastChanged attribute of the Scan system variable. Verify that an IP address has been configured in the controller. If you are saving a remote site back that is earlier than revision 1.52 you need to set an IP address in the remote controller. Verify that the CX controller is at least revision 1.5 Verify that the controller is not reset. In some rare cases we saw that you would have a problem if you created the CX controller while offline editing. The correction in this case was to go offline edit, delete the CX in Cyberstation, go online, recreate the CX and then do the save to database. If the controller you are saving back has to go through a firewall and the firewall has blocked the access to the other IP addresses of the other controllers this controller knows about. Port numbers 33487, 33440, and 33456 are blocked in a router. Specifically port number 33456 is used for the save to database functionality. Make sure Firewall programs are not blocking the network connections. Disable any firewall programs before doing a “Send to DB”. Create a debug file (Acc_Dump_Debug.txt). See the Infinity-to-Continuum Upgrade document. Look in the debug file and see where it failed and act accordingly. 

Issue Is it possible to just install the IA Commissioning Tool (WPCT) or IA Flow Balance Tool without having to install WorkPlace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech I/A Series WorkPlace Tech Commissioning Tool I/A Series WorkPlace Tech Flow Balance Tool Cause  WorkplaceTech is not required on the PC but the operator needs to use the WPCT and or Flow Balancing Tool. Resolution It is possible to install the WPCT and/or the IA Flow Balancing software without having to install WorkPlace Tech.  At the time of the WorkPlace Tech installation, there are three options to select from: WorkPlace Tech Flow Balance Tool Workplace Tech Commissioning Tool WorkPlace Tech 5.x. WorkPlace Tech Flow Balancing Tool is preselected.  It cannot be deselected – it must be installed.  You can choose to install the WorkPlace Commissioning Tool by selecting it. If WorkPlace Tech is not needed then do not select the box next to it. WorkPlace Tech will not be installed during the installation process.

Issue After TAC Vista Server is started, logging into TAC Vista Workstation, an error "Ensure that Vista Server is started" occurs. Product Line TAC Vista Environment TAC Vista Server TAC Vista Workstation TAC Vista Webstation Cause This issue is due to the DCOM permissions that Vista Server relies on and they must be manually changed. Resolution Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET contains a DCOM Utility that can automatically set the proper permissions to clear the issue. To manually alter DCOM parameters: Locate the DCOM config in Component Service > Computers > My Computer Right-click TACOS and selected Properties Select Security tab Click the Edit in Launch and Activation Permissions. Add the appropriate groups or user names of computer and Allow them permissions. After finishing the above procedures, the issue should be solved. Error: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. also discusses this issue.

Issue Satchwell CZU Mk3 Zonemaster Controller requires replacement. Product Line Field Devices Environment Stand alone Fan Coil Unit Temperature Controller. Satchwell CZU Mk 3 Zonemaster Controller. CZU 3201 CZU 3202 CZU 3203 Cause Obsolescence of Satchwell CZU Mk3 Zonemaster Controller. Resolution Replacement of Satchwell CZU Mk 3 Zonemaster Controller with S-E Satchwell CZU Mk 4 Zonemaster Controller. The CZU 4201 may be used to replace the following CZU Mk 3 Controllers :- CZU 3201, CZU 3202, CZU 3203 N. B. CZU 3201 Controllers provided an additional -9 to +9 V d.c. output enabling connection to peripherals such as the Satchwell NSU 1401 Night Set-back Override Unit, TSU 1402 Two Step Auxiliary Unit and SSU 1403 Signal Selector Unit. CZU 3202 and CZU 3203 Controllers provided an additional -0.5 to +9 or -9 to +0.5 V d.c. output enabling connection to the Satchwell NSU 1401 Night Set-back Override Unit. Additional outputs are not provided on the CZU 4201 Controller and in those applications where these are required then it will be necessary to consider an alternative Controller to the CZU 4201. Details of the CZU 4201 may be viewed  here. A remote Satchwell Adjustable Room Temperature Sensor such as the DRT 3451, or a remote Satchwell Duct Temperature Sensor from the DDU range of Sensors may have been installed and connected to the Controller. Any existing remote Satchwell Temperature Sensor may be retained for connection to the CZU 4201. Should the remote Satchwell Adjustable Room Temperature Sensor require replacement then this may be replaced by an S E STR 612 Adjustable Room Temperature Sensor. Details of the STR 612 may be viewed here. Should the remote Satchwell Duct Temperature Sensor require replacement then this may be replaced by an S E STD 670 Duct Temperature Sensor. Details of the STD 670 may be viewed here.

Issue When trying to distribute personnel to Netcontrollers, about half of them fail with the message: Error text undefined (TBD) 0x00002001 under the Last Error column in the Access Distribution View. Environment CyberStation Access Control Cause Access distributions are failing with the same error message in the access distribution view. Resolution Make sure that there are no access controllers that are offline. If there are, and they cannot be brought back online right away, such as during a site renovation, set them to "Out of Service" until they are able to communicate. If they are no longer to be used then delete them - as CyberStation may be trying to distribute to them. This same error message came up on a different project. It was noted that the personnel that failed to distribute (with this error) had schedules attached to their assigned areas, and the schedules reside in the controller that gives the error. The problem was resolved by reloading all the access controllers one-by-one.   Make sure if there are remote area schedules that network issues are not blocking the controller receiving the personnel distribution from getting to the remote controller that own the area schedule point. You can test this by creating test points in each controller and using a program to import the point, in some cases you will see that the program will give the same 0x00002001 error on compilation which indicates network issues. Work with IT to find out what is blocking comm between the two controllers.

Issue DPU Offline shows up when the Door Configuration is selected from the Summary Controller. Product Line TAC INET Environment All versions of I/NET Cause The Resident I/O Points for those doors are either non existent in the save file, offline or have lost communications to the controller. Resolution Verify that the DPUs are Online and communicating to the Controller by clicking connect Controller/MCU Configuration and verify that the addresses are blue and communicating Select Resident I/O Points and verify that the 08 and 09 points does exist for the respective points If not add and then update the database Select Summary/Door Configuration/ and verify that the doors are now in blue rather than red indicating that they are online. Temporary Individuals have the DPU RES check box, which means the information is stored in the DPU (such as a SCU) until the battery runs out.

Issue Unable to import component Library into Graphics Editor. Double Clicking Archive Results in: Graphics Editor - Unexpected Error A problem occurred in this application Object reference not set to an instance of an object. Right-Clicking in the Component Library White Space shows the "Import" option grayed out. Product Line EcoStruxure Building Operation Environment TGML Graphics Editor Cause The Default Libraries Location is no Longer accessible. This could be caused by a network drive being offline, an external drive being ejected or a user permissions being changed. Resolution Open the TGML Graphics Editor Right Click in the Component Library Space Click on "Libraries" Notice that no Location is bolded as this would indicate the default location Set a Location as default. Close the Libraries editor and import component libraries as desired.

Issue Trying to run a Script program from a Graphic but getting error Read Only Property. The control in the Graphic has been bound to a VALUE object, in the Script program an output variable (ManualChange in the code below) is bound to the same VALUE object. The program is supposed to toggle the value of 'theOutput' when triggered by setting 'ManualChange' from the Graphic, this works in versions prior to 1.4. Numeric Output theOutput, ManualChange LEAD_CHANGE:   ManualChange = Off Goto WaitForManualCHG WaitForManualCHG:   If ManualChange = On then   if theOutput = on then theOutput = off else theOutput = on   Goto LEAD_CHANGE endif Product Line EcoStruxure Building Operation Environment WorkStation Automation Server - AS Enterprise Server - ES Cause Starting in version 1.4, SmartStruxure does not allow more than one write reference to the same VALUE, once a write reference is defined for a value or other references to the same value are READ ONLY. (See Reference Guide and References beginning with 1.4.x) Resolution Change the ManualChange variable in the Script to a PUBLIC and then from the Graphic bind directly to it. Numeric Output theOutput Numeric public ManualChange LEAD_CHANGE: ManualChange = Off Goto WaitForManualCHG WaitForManualCHG: If ManualChange = On then if theOutput = on then theOutput = off else theOutput = on Goto LEAD_CHANGE endif   See screen shot below of the binding in the Graphic

Issue Cannot commission an IC3 LON controller in LonMaker. It has become applicationless and the red service LED is flashing or is permanently lit.  Product Line Satchwell Sigma Environment Satchwell Sigma Controller IC3 IC LON FTT-10 NodeUtil Cause The Echelon chip has become 'locked' and requires resetting.  This can be caused by corrupted controller files, very high LON traffic (> 50% Bandwidth), or the controller has started from "start-up mode" or cold start.   Resolution The Echelon chip can be reset using NodeUtil.exe  .  This is a DOS-based program that can be loaded onto a laptop with an FTT-10 Echelon adaptor. A clean working set of controller files will be downloaded to the device. In the case of a flashing red LED - Download 'clean' files to the controller Start NodeUtil on the laptop and plug LON cable into the controller Reset controller (via onboard reset button) Activate the plug-in LON card service pin and the Neuron Id should appear on the laptop. Note: If further controller resets and service pin activations fail to generate the service pin echo then discard the plug-in card and replace with a new one. From the NodeUtil menu select 'R' and enter the Node Id number Confirm the reset of 3150 Node The service LED should stop flashing and the controller should now be 'Configured' that is not 'applicationless' In the red LED is permanently lit - Download 'clean' files to the controller, the Echelon chip will become locked again. Repeat the reset procedure using NodeUtil.exe, this will allow the controller to work, but the plug-in card will need to be replaced. Example of NodeUtil process; NODEUTIL> (H)elp with commands A -- (A)dd node to list. D -- Set the (D)omain of the network interface. E -- (E)xit this application and return to DOS. F -- (F)ind nodes in the current domain. G -- (G)o to node menu............. H -- (H)elp with commands. L -- Display node (L)ist. M -- Change node (M)ode or state. O -- Redirect (O)utput to a file. P -- Send a service (P)in message. R -- (R)eboot 3150 node. S -- Report node (S)tatus and statistics. T -- (T)ransceiver parameters. V -- Control (V)erbose modes. W -- (W)ink a node. Z -- Shell out to DOS. NODEUTIL> Received an ID message from node 2. Program ID is ICLON1a NODEUTIL> Received an ID message from node 2. NODEUTIL> (R)eboot 3150 node Enter node id for reboot (0-2) [2] :2 *** Neuron 3150: Rebooting will reset comm. params, node state on-chip EEPROM variables and buffer configuration Are you sure you really want to do this? (Y/[N]): Successfully rebooted node NODEUTIL> A second solution has been provided by a customer and could be considered if the above suggestions does not provide a solution. Alternative reset procedure provided by a customer is as follows: - 1. Removed the IC LON from both the LON and the Sigma network. 2. I used SCDU tool to re-node the ICLON to a random IP address, which I believe cleared the database and the files etc. 3. I removed the power form the ICLON and then removed the LON daughterboard card from the ICLON mainboard. 4. Re-instated power and re-installed the LON daughterboard card. 5. Connected with NODE Utility as per the product data-sheet below. And cleared the LON comms buffers as the suggested method. 6. Checked that the red constant service light ceased from the constant illumination. And witnessed that the Green LON heartbeat LED was operational. 7. Re-Node the ICLON to the original IP and check operation. * The Sigma IC-LON plug-in card can be purchased using the part number S-LON. The S-LON has been discontinued as of 29th December 2017 and it is now in the service period (limited quantities available for purchase). Refer to PA-00528 for details.

Issue Explanation and detail required for Client Access License (CAL). Product Line Andover Continuum, EcoStruxure Building Operation, TAC INET Environment Windows  SQL Server Cause Information on Client Access License (CAL). Resolution Server licensing and Client Access Licenses (CALs) for the MS Server or MS SQL can become complex. It may be worthwhile to research further through Microsoft resources. SQL Server 2008 is available under three licensing models: Server plus device client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each client device. Server plus user client access license (CAL). Requires a license for the computer running the Microsoft server product, as well as CALs for each user. Processor license. Requires a single license for each CPU in the operating system environment running SQL Server. This license includes unlimited client device access. SQL Standard will normally come with 5 CALs. If more than 5 connections exist, then ore SQL CALs need to be purchased. See Microsoft Volume Licensing for more information. Note: MS Server CALs are separate and are also required. EcoStruxure Building Operation does not check CAL Client Access Licensing. EcoStruxure Building Operation Reports Server can be run using Microsoft SQL Express.