Building Automation Knowledge Base

Issue Does the Enterprise Server license have a 'node count' like the server license in Niagara R2? Environment SmartStruxure Niagara R2 Cause Comparing the order processes between I/A Niagara R2 and SmartStruxure Resolution The Enterprise Server has an open license.  There is no 'node count' built into it as is the case with Niagara R2. Keep in mind that version 1.3 of SmartStruxure supports a maximum of 32 AS controllers (for optimum system performance).

Issue An owner customer has purchased a non-expiring copy of WorkPlace Tech.  It is installed on a 64-bit Windows 7 computer within the XP 'mode' virtual machine.  Can it be copied to other Windows 7 computers and work or does the WorkPlace Tech license prevent it from working? Environment Windows 7 WorkPlace Tech 5 Cause Loss of potential sales Resolution WorkPlace Tech licensing is not designed to identify a virtual 'hard drive' from an actual hard drive.  As a result, an installed copy of WorkPlace Tech will work in the virtual machine no matter how many Windows 7 computers into which it is installed.

Issue Several Viconics LON thermostats are installed on a job.  Only one won't communicate properly.  What do the different conditions of the Status LED indicate? Environment Viconics all LON thermostats Cause One of many installed is not communicating properly Resolution Different possibilities with the Status LED behavior for the LON thermostat

Issue Linkage kits to be used with Satchwell ALE (s) , ALi, ALX (s), ALM (s) on Schneider Electric Venta V and VG Valve bodies Environment Linkage Kits Cause Linkage kits to be used with Satchwell ALE (s) , ALi, ALX (s), ALM (s) on Schneider Electric Venta V and VG Valve bodies. Resolution Use the L8TV linkage kit part no. 914-1080-000 on V type valve bodies e.g. V211, V211T, V311, V311T, V231, V241, V212, V222, V232, V292, V341 Use the L9TVG linkage kit part no. 914-108-000 on VG type valve bodies e.g. VGS211F, VG221F, VG311F

Issue After copying sections of logic from one application to another the pointers from that logic won't connect to other objects and therefore show up as red lines. Environment WorkPlace Tech Cause Copying sections of logic from an older application has been known to cause this. Resolution To recover the application remove all objects and reference tags that exhibit the connection issue, compile the application and then re-create the deleted logic by pulling objects from the Shapes window.

Issue How do you convert MicroNet 2000 controller filenames generated by the MicroNet Controller Interface "Get Multiple" function to integrator and controller addresses? Environment MN-2000, MN-CI, MicroNet Controller Interface Cause The "Get Multiple" function is used to upload application programs from multiple MicroNet controllers under one MicroNet Integrator or a series of MicroNet Integrators.  The application programs are stored as files with the integrator and controller addresses appended to the name. Resolution When uploading files from multiple MicroNet VAV Controllers, the CI creates unique filenames for each uploaded application file by appending the integrator number and device number to the prefix entered in the Enter File Prefix window. The integrator number and device number are appended in hex format. The file shown in the illustration above was uploaded from MicroNet controller 11 under MicroNet integrator 6.

Issue WebStation connection is unreliable when using a 4G (cellular) connection Auto logoff times are not obeyed  Product Line EcoStruxure Building Operation Environment Building Operation WebStation 3.x Broadband Cellular Networks Cause WebStation creates a subscription with the Building Operation server, so it will attempt to connect every 10 seconds.  If this connection is removed/interrupted/ or no longer required for a period of 60 seconds, WebStation will force itself to log out.  This setting is currently fixed and cannot be adjusted.    Currently, there have been instances where this connectivity issue is seen when using, as shown below, a device with a broadband cellular connection attempting to connect to a Building Operation server that also connected to the same/similar cellular network this is the most common scenario where this issue is seen. Resolution It is recommended not to use these cellular network connections to permanently display Building Operation Server information, especially from mobile devices connecting to the cellular network.  This type of connection should be used sparingly and for quick access to view/check information as necessary.  Connection loss can be expected if you move away from the webpage for more than 60 seconds.  Any lengthy connections to the Building Operation Server are recommended to use a more permanent network connection.     Issues have not been seen when using broadband Internet or a similar connection as shown below to a remote cellular Building Operation Server.  This meaning that the EcoStruxure Building Operation system has remote Internet access via a broadband cellular connection. To troubleshoot this further, capture a HAR file using the details provided here How to collect a network trace | Microsoft Docs and reproduce the issue while this debugging window is open within your browser.  Note: This capture must be done at the source; that is where WebStation is running.  This may not be easy to do using a mobile device.   Send this saved HAR file and the Internet browser version and EBO version used along with connection types to your local support channel. 

Issue There is a problem after upgrading the SystemDB to N4.10. Product Line TAC IA Series Environment I/A Jace 8000 N4.10 I/A Enterprise Server N4.10 Cause In Niagara 4.10, we upgraded SystemDB from Orient v2 to v3, and as a result of that change, any customers that are utilizing SystemDB on their Supervisor stations will need to re-index accordingly upon upgrading to 4.10. Resolution In Niagara 4.10, the SystemDB has been upgraded from Orient v2 to v3.  Because of this change, customers that are utilizing SystemDB on their Supervisor stations will need to re-index upon upgrade to 4.10.  Please note, re-indexing can take a considerable time upon upgrade, and the DB will not have accurate information when queried until the index upgrade is complete. After upgrading to 4.10, invoke the actions that force system indexing.  Be aware that re-indexing can take some time, and that the DB won’t have accurate information when queried until the index is complete. The following image shows how to invoke execute on the Local System Indexer: If the Station has a DB configured to contain information about points on other stations, the Niagara Network System Indexer should be used, rather than the Local System Indexer.  Additional details regarding indexer actions can be found in the Niagara System Database and System Indexing Guide.

Issue Adding Web.Client to an existing site that has Continuum installed with the CFR compliance option. Environment Continuum with CFR Compliance Cause Can't find any part numbers for Web.Client with CFR compliance or an option to add it. Resolution We do not have an option for Web.Client with CFR. One of the requirements for CFR is the inclusion of operator text when performing certain actions; there is no way to prompt for, or supply, this operator text when using a Web.Client browser client.

Issue All Custom Types in an AS-P suddenly disappeared and it is not possible to create any new Custom Types. When trying to create a Custom Type it results in an invalid Custom Type object:   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause For an unknown reason, the Configuration database has become corrupt. Resolution Workaround 1: Do an upgrade of the AS-P to the same version which should fix this issue.   Workaround 2: Restore a backup taken before this issue appeared.

Issue For integration purposes, it is important to clarify exactly what Andover Continuum X-Driver protocols have a prescribed upgrade path and remain supported in EcoStruxure Building Operation (EBO) Product Line Andover Continuum, EcoStruxure Building Operation Environment Andover Continuum Building Operation Enterprise Server Building Operation Automation Server Premium Cause As more and more systems Transition from Andover Continuum to EBO, customers need to know how existing Continuum X-Drivers can be supported and upgraded to maintain data connectivity in their new EcoStruxure Building Operation architecture. Resolution Product Announcement PA-00789 available on EcoExpert Exchange details all those X-Drivers which are supported going forward into EBO

Issue A MN-Sx sensor is installed more than 200 feet away (the maximum specified) from a MNL controller. The dynamic temperature value drops in and out at the controller.  Is there a repeater that can be installed to improve communications? Environment MNL MN-Sx Cause Cable run extends beyond the specified 200 feet. Resolution There is no repeater available that can be used for the MN-Sx cable run.

Issue ACX781's are still installed on some older sites but the cabinet keys cannot be found. Can these be replaced? Environment ACX781 Cabinet Enclosure Cause No one has the cabinet key and it needs to be replaced. Resolution The ACX781 controller has been discontinued since 2007. The stock on the cabinet lock/key assembly has been depleted since then and there are no replacements available.

Issue Is it possible to include the Comments field from Extended Logs into Report Server Reports? Product Line EcoStruxure Building Operation Environment Building Operation Reports Server Cause Regardless of the new Reporting Features in EcoStruxure Building operation (EBO) 3.2, users of existing systems up to and including EBO 3.1 are asking if it is possible to include the Comments field in Extended Logs within the Enterprise Sever to enhance the data in RS Reports? Resolution Extended Log Comments within the ES are not available to Report Server reports today and given the move to new Reporting Features now available in EBO 3.2 it is unlikely that an Enhancement Request for such a feature would be implemented quickly. Therefore, the suggestion here would be to migrate the Extended Logs to External Storage via TimeScaleDB where all the Extended Log data (including the comments) can be freely manipulated by 3rd party Reporting Products.

Issue Implementing a pre-entry access card anti-passback using Plain English program Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause The anti-passback implementation in Continuum engages when the credential holder enters the area as detected by the door switch/contact. (if no door switch is configured, then the credential holder is considered to have entered the area immediately after access has been granted by the system) When doors are located in close proximity to each other, as is the case with a bank of turnstiles, for example, the built-in anti-passback scheme is easily defeated as a cardholder is able to unlock multiple nearby turnstiles before triggering the door contact and engaging the built-in anti-passback functionality. Resolution The simplest solution to the issue described above is to configure the door objects WITHOUT a door switch/contact, this, however, is not always possible depending on on-site requirements. A second solution is to take control of the doors using Plain English. The solution presented here is for a bank of three turnstiles, (A, B, and C), it uses a PE program per turnstile. The solution can easily be adapted for a bank of less or more turnstiles. NOTE: The PE programming here is provided as a sample, for guideline purposes only, the programs are not intended as a complete solution, significant modifications may be required for site deployment. Program code for door/turnstile A 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' |_____X______X______X______ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the 'initialization line which specifies which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileB, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_B, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_B, theLastCrdTime_C Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_A theTurnstileB = Turnstile_B theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_A_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileA_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM '------------------------------------------------------------------------------------------ Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile B 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of the following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_C '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_B theTurnstileA = Turnstile_A theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_B_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_B_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileB_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_B_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile C   'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileB 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_B, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_B '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_C theTurnstileA = Turnstile_A theTurnstileB = Turnstile_B 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_C_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_C_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum thisAlarmPoint = TurnstileC_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_C_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING        

Issue In Access Expert's 'View All Hardware' window, the status of controllers does not update. For example, controllers say 'Online' even though they are actually 'Offline' and vice versa. Live Monitoring window does not show disconnect/online events. Seq log shows error: Failed to Publish event.Moniker:MonikerItem {"Namespace":"MercuryServiceEvents","Nickname":"mercury:15-12-1"} Product Line Access Expert Environment Access Expert Premise Software Cause Enterprise Administrator group, under root, is missing permissions for Mercury service. Resolution Log into the Root instance, edit the Enterprise Administrator group, in the "Event Types" tab, make sure permission is granted to the Mercury Service and Mercury Commands

Issue What are the rules for inheritance in TGML? Environment TGML editor Cause In order to create TGML components that function as designed,  it is important to understand the TGML rules for inheritance Resolution Attribute inheritance means that a child element inherits (gets) the attribute value from an ancestor element if the attribute value is undefined (omitted) and if the attribute has been specified for an ancestor (any of the parents). In the example below, Rectangle will inherit the Fill value from the component.

Issue When emailing an alarm from the ENC the timestamp is always the time the alarm occurred; even when the Alarm email is due to an acknowledgement or return to normal. Environment G3, ENC's, JACE's Cause The default "body" property of the EmailRecipient contains only the %timestamp% which represents when the alarm occurred. Resolution Additional parameters can be added to the EmailRecipient "body" property to provide the "return to normal" and "acknowledged" timestamps. The return alarm timestamp can be added with %normalTime%. The acknowledged timestamp can be added with %ackTime%.  

Issue Troubleshooting Heat Meter installations (also Cooling or Flow meter) Environment Heat cooling or flow meter installation Kamstrup Cause Troubleshooting Heat Meter installations (also Cooling or Flow meter) when there is a problem with the values being measured Resolution To aid Product Support please supply the following information 1. Sketch of the installation, including physical details of pipe size, lengths and bend details plus any local valves etc. 2. Schematic sketch showing positions of Boilers/Chillers, Pumps, meters and sensors. 3. Photo of the installation if possible 4. Details of the media, maximum/minimum temperature, nominal flow and system pressure 5. What BMS is connected to the meter? Running NOTE Were no flow or little flow is seen, there may be air within the system, even if the "Air in System" info is not given on the meter.

Issue The Enterprise Network Server is licensed for 3 subordinates but when trying to add one it faults with the message "exceeded device limit of three"? Environment G3 Enterprise Network Sever Cause If stations had been added to the Niagara Network in the Enterprise Network Server and then deleted the subordinate count in the license does not reset. Resolution Restart the station and the subordinate count in the license will be reset to the correct number and allow the addition of more stations if the limit has not been reached.