question
stringlengths
19
6.88k
answer
stringlengths
38
33.3k
Problem Statement: How do I model a piping network where the pipes themselves are known and the source and destination pressures are fixed, but flows are unknown?
Solution: The user must supply initial guesses for flowrates and vary them with design specifications. Solving the design specifications can be difficult, because the variables all interact and because if a flow is set too high, the pipe blocks will have trouble. (Once critical flow is encountered, the downstream pressure becomes indeterminate.) In the attached example, the flows of three feed streams are varied to produce the final downstream pressure, given a network of 2- to 6-inch piping. The feed streams are pure water at its bubble point (steam condensate), so all the pipes have flashing two-phase flow. Convergence tips: First build and run the model without any design specifications. Add design specs one at a time, then run the flowsheet with each new spec. Since the pressures have to be equal where two streams meet, one simple set of design specs will vary a feed stream flow such that the pressure where it mixes with the main flow is equal to the pressure of the other stream. DS-1 and DS-2 in the example file are of this type. For an overall design spec, vary one of the feeds such that the final pressure is equal to the known final pressure. This is used in DS-3. When the specs begin to interact, force the specifications to be converged simultaneously on the Convergence/Conv Options/Defaults form's Sequencing sheet. Stream reconciliation was used to provide inputs that are close to the converged solution so that the flowsheet can more easily be run after changing input specifications. Even with this input, big changes may require reconverging one spec at a time. Note that this problem is much easier to solve with an equation-oriented simulator such as Aspen Dynamics. Exporting this file as a pressure- driven simulation and running it in Aspen Dynamics is a more straightforward solution. KeyWords: Keywords: None References: None
Problem Statement: How can I retrieve Aspen Plus Error Messages with Visual Basic?
Solution: Aspen Plus error messages are stored in a folder called PER_ERROR below the objects which they reference. For example, the messages for the overall simulation are stored as a PER_ERROR collection under Results Summary/Run Status. The PER_ERROR message collection for convergence blocks can be found under the Output section of the actual convergence block. The attached example contains a general subroutine (CheckForErrors) that will retrieve these messages. In this example, the error messages are retrieved from a convergence block that was assigned to converge a design specification. This example was written for Aspen Plus 10.1 and Excel97. Define a local object variable for CheckForErrors. The messages for this object will be retrieved if this object has a status equal to error. Dim lo_ErrFolder As IHNode Define a local collection describing where the error messages are located. The route to the PER_ERROR object is slightly different for different objects. Dim lc_ErrMessF As IHNodeCol Define string variables to hold status and error messages Dim ls_Error As String Dim ls_Message As String Set local object to Convergence Block of interest Set lo_ErrFolder = go_Simulation.Tree.Data.Convergence.Convergence.Elements("C-1") Set local collection defining location of error messages Set lc_ErrMessF = lo_ErrFolder.Output.PER_ERROR.Elements Call routine to gather error messages from object Call CheckForErrors(lo_ErrFolder, lc_ErrMessF, _ ls_Error, _ ls_Message) Display error status and messages in Excel. Messages will be written to Excel Text box named Errors. Range("Status").Value = ls_Error Errors.Text = ls_Message KeyWords VB, VBA, error Keywords: None References: None
Problem Statement: What is the EB-Scripts option under Flowsheeting Options in the Aspen Plus 10.1 data browser?
Solution: EB (Equation-based) scripts is meant for users to enter scripts/commands for RT-Opt models. It was added for the RT-Opt 10.0 GUI and should have been removed from the Aspen Plus 10.1 GUI. It is not to be used for Aspen Plus simulations. It will be available in Aspen Plus 11.1 to be used for the dual-execution mode (sequential modular and equation based) models. Fixed in Version EB-Scripts option removed in the Aspen Plus 10.2 User Interface Scripts for Equation Oriented solution available in Aspen Plus 11.1 KeyWords EB-Scripts Keywords: None References: None
Problem Statement: Simulation is under specified by 1 when you switch from local to rigorous properties. This occurs with a RADFRAC column in the flowsheet.
Solution: The column has subcooled reflux and liquid distillate and the equation to calculate the liquid mass density at the subcooled conditions is missing from the rigorous properties section of the property sub-model. Workaround: Add the missing equation in the Flowsheet Constraints section of the problem To do this: In the Simulation Explorer, select the Flowsheet icon. In the "Contents of Flowsheet" pane, right clickon the Flowsheet object icon and select Edit. In the text editor, under the Constraints section, add the equation to calculate the liquid mass density: BLOCKS("BLOCKNAME").stage(1).pliqsub(1).Rhom = BLOCKS("BLOCKNAME").stage(1).pliqsub (1).Rho*BLOCKS("BLOCKNAME").stage(1).pliqsub(1).MW; Notes: You must include the semi-colon at the end of the equation The text is not case-sensitive and can include lower and upper-case text The block names must be enclosed in quotes. Compile the Flowsheet Constraints section by doing the following: Right clicking in the Editor window Select Build/Compile Save and Exit from the text editor The problem should now be square. If you switch back to local properties you will have to edit the Flowsheet constraints section and remove or comment this equation out. Fixed in Release: 10.2 and later Keywords: None References: None
Problem Statement: How is the melting point of a polymer calculated in Aspen Plus? Is possible to modify it?
Solution: The Metal Transition Temperature (TM) of a polymer is calculated with the Van Krevelen Melt Transition Temperature Correlation (model TM0DVK). Tm,A = Melt transition temperature for segment type A nk = Number of occurrences of functional group k in the segment from the segment database or user-specified segment structure Ym,k = Melt transition temperature of functional group k, from van Krevelen database Mk = Molecular weight of functional group k Tm = Melt transition temperature of the polymer Nseg = Number of segment types in the copolymer XA = Mole segment fraction of segment type A in the copolymer MA = Molecular weight of segment type A Ym,k values for functional groups are given in Van Krevelen Functional Groups. You can edit the TMVK parameter to modify the calculated Melt Transition Temperature (TM) Note that "Treat polymers below the polymer melting point as solids" should be checked on the Properties Components | Polymers | Characterization | Options sheet. See example file attached. In the example Polypropylene (PP) has a TMVK of 135C specified as shown above. The feed stream at 60C is a solid and the product stream at 136C is a liquid. Keywords: Melting Point, Melting Transition Temperature, Polymer, Van Krevelen, TM. References: None
Problem Statement: New in Economic Suite V10.1 - MS Office 64 bit is supported
Solution: The V10.1 Economic Suite (Aspen Capital Cost Estimator, Aspen In-Plant Cost Estimator, Aspen Process Economic Analyzer, Activated Economics) now supports MS Office 64 bit applications. Before V10.1 only MS Office 32 bit applications were supported. Starting with V10.1 both MS Office 32 bit and 64 bit applications are supported. Keywords: MS Office 64 bit, 64 bit, 32 bit, Excel, Excel 64 bit, Excel 32 bit, Word, Word 64 bit, Word 32 bit References: None
Problem Statement: Starting in version V7.1 of Aspen InfoPlus.21, 32 Bit; it is possible for Administrators to specify the type of license that is going to be used by a particular database. How to select the License Key Type in Aspen InfoPlus.21? There are four types: Standard - Embedded - Backup - Development. NOTE: These options are not available for 64-Bit InfoPlus 21
Solution: In order to configure the proper Aspen InfoPlus.21 license type, follow these simple steps: 1. Shut down the database from the InfoPlus.21 Manager 2. From the Administrator tool, right-click on the database name and select "Set License Key Type" 3. Select the appropriate license type and click OK. For information on license types, see KB 128914 4. Start the database 5. Optionally, you can verify that InfoPlus.21 is checking out the correct license by using the WLMAdmin tool: Keywords: Token Tokens Hot Backup SLM License Scheme Selector Selection Aspen Watch AspenWatch IP.21 References: None
Problem Statement: Which switches are available for the AtRunUnattended.exe to perform silent installation
Solution: AspenTech provides a way to automatically deploy AspenTech software to multiple computers to ensure a consistent configuration of the software on all target computers. The aspenONE Installer provides a means to record user inputs using the built-in record option. The output of this recording can then be used to perform an unattended install using the atrununattended.exe tool. The following is the Syntax to use AtRunUnattended.exe: Syntax: "\\myserver\myshare\AtRunUnattended.exe" "[\\myserver\myshare\]MyInstall.xml" [/I | /S] [/noreboot | /forcereboot] [/L] [logfile="C:\Logs\silent.log"] [altsource="\\myserver2\myshare2"] /m Switch Description /I Interactive Install : This will show a small installation progress pop up window without any buttons /S Silent install: This will not show any progress of installation on the user screen, it’s a Default option /noreboot Do not reboot even if reboot was required by the installed products /forcereboot Reboot always when used this parameter /L Creates Windows Installer verbose log files under %temp% logfile Fully qualified log file name. Log file is created under %temp% with file name ATRunAttended *.log altsource Alternative install media location. Use \altsource=. to start the search from AtRunUnattended.exe folder /m Generate .mif file for SMS client computers /removeall Uninstalls all AspenTech products Note: .xml file path is optional if the XML file is in the same directory as AtRunUnattended.exe Keywords: AtRunUnattended, Silent, Unattended, Installation, Switch References: None
Problem Statement: Why am I not able to locate my current usage reports on the AspenTech Support Center website?
Solution: Access is granted to usage reports based on individual server name and system name combination. If the server name or license system name has changed since the last time you accessed the reports, you will need to send a email request to [email protected] and include the new server or system name. For instructions on locating your system name see knowledge based What is a license System Name and how can I quickly find it? Keywords: : token usage, reports, token reports, usage reports, usage logs, monthly report, daily report References: None
Problem Statement: How to use the SLM Test tool
Solution: 1. As of Aspen ONE V9, the executable should be at this location: C:\Program Files (x86) \Common Files\AspenTech Shared\SLM Client Tools If not, obtain and copy the executable (SLMTest.exe) to a location on the hard drive. 2. Ensure the server is set up via the SLM Configuration Wizard and pointing to the correct location. The example screenshot below shows the Configuration Wizard pointing to the local machine: localhost This varies according to the name of the license server in question. 3. Start the executable. You may then enter in the license name of the license you would like checked out into the SLM Test Tool. Ensure that hold is checked and edit the units according to your parameters. You should see the screen below once you click “Start Test” and the tool has been run: 4. Enter the following keys a. SLM_AspenPlus b. SLM_HYSYS_Process c. SLM_AcolPlus d. SLM_TascPlus Example, Aspen Plus consumes 18 tokens. If the unit is 1 then only 18 tokens will be consumed from the server. If you put 2 then 36 tokens will be consumed. If trying to consume 3,000 tokens… a. SLM_AspenPlus - 18 tokens X 100 = 1880 b. SLM_HYSYS_Process - 14 tokens X 80 = 1120 Total = 3000 (user can use similar example to check-out all tokens and scale at the same time) 4. Finally access the aspenONE SLM License Manager to confirm that the token has indeed been checked out. The below example has been done on the server itself (hence the localhost under License Server). This can be done on any machine with the SLM Configuration Wizard installed as long as the correct license server is being pointed to: Above, the “Licenses in Use” column has been clicked to organize from most to least to assist in locating the appropriate license. Keywords: SLM test test tool References: None
Problem Statement: When attempt to connect to the Aspen.Infoplus21_DA.1 of a 64-bit InfoPlus.21 server, the below error message is encountered.
Solution: This issue can be ensuring that the OPC Core Components Redistributable(x64).msi found in <USB drive>:\aspenONE_V10_MSC_T\aspenonemscdvd\core\OPCCore_x64 is installed. To verify whether it is installed, check whether the folder C:\Program Files\Common Files\OPC Foundation\Bin can be found and that the following files are in it. opcbc_ps.dll OpcCategoryManager.exe OpcCmdPs.dll opccomn_ps.dll OpcDxPs.dll opchda_ps.dll opcproxy.dll opcsec_ps.dll opc_aeps.dll If the files exist, re-register the DLL files using the OPCCoreReg.txt in this knowledge based article by performing the following steps after downloaded it. Rename the file to be called OPCCoreReg.bat. Launch a command prompt using Run as administrator. Browse to location of the file using CD command. For example, if the file is found in C:\Temp, issue below command. cd C:\Temp Execute the batch file by entering OPCCoreReg. Keywords: Matrikon OPC Explorer COM/OPC error 0x80004005 on CoCreateInstance() Error string: Unspecified error Additional: Could not connect to server 'Aspen.Infoplus21_DA.1' References: None
Problem Statement: Unable to find selection for OPC HDA when trying to configure OPC HDA as a data source in Aspen Mtell System Manager.
Solution: In order to configure OPC HDA as a data source for use in Mtell, the following steps need to be performed. Launch Honeywell PHD Sensor Adapter Configuration. Enter the server name of the machine which has OPC HDA server installed in textbox beside Server Name in Server Configuration tab. Enter the OPC HDA server programmatic identifier in textbox beside ProgID. Enter a user name and password which has DCOM permission to the OPC server. Click on Test button to check for successful connection to the OPC HDA server. Click on Save button to save the configuration. After performing the above configuration, on the machine installed with Mtell, perform as below to check that able to browse for the tags in the OPC HDA server. Launch Internet Explorer. Browse to below URL replacing Mtell_machine withe the hostname of machine installed with Mtell. http://Mtell_machine/AspenTech/AspenMtell/Adapter/HoneywellPhd/api/sensor After confirming able to see the tags in the OPC HDA server, perform the following steps to add the data source. Launch Aspen Mtell System Manager. Click on Configuration tab. Select Sensor Data Sources in the Settings. Click Add Data Source. Enter a name in text box in Define Data Source dialog box. Click on OK button. Select the following: Source - Plant Historian Historian - Honeywell PHD Click on Save button to save the configuration. Click on Map Sensors button to launch Assets Map dialog window. Click on Refresh button. If no error, a list of tags/sensors will be displayed as shown in screenshot below. Below is an example screenshot connecting to Matrikon OPC Simulation server through OPC HDA. Note: If the Mtell setup is on a separate machine from the OPC HDA server, DCOM permission will need to be configured on the OPC HDA server including ports need to be opened in firewall. Following knowledge based articles can be referred to. DCOM considerations when OPC Server is remote to Aspen Cim-IO for OPC interface DCOM consideration when using a firewall Keywords: References: None
Problem Statement: After entering the server name and ProgID of OPC HDA server in Honeywell PHD Sensor Adapter Configuration, when testing for connection, below error message is encountered.
Solution: This error is due to the machine installed with Mtell does not have OPC Core Components Redistributable (x64) installed.\ A copy of OPC Core Components Redistributable (x64).msi can be found in <USB drive>:\aspenONE_V10.1_APM\aspenoneapms\core\OPCCore_x64 folder in the USB media. Keywords: Connection Failed Unable to case COM object of type 'System.__ComObject' to interface type 'OpcRcw.Comn.IOPCServerList2'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{9DD0B56C-AD9E-43EE-8305-487F3188BF7A}' failed due to the following error: The specified module could not be found. (Exception from HRESULT: 0x8007007E References: None
Problem Statement: After configuring the adapter to OSIsoft PI for the Plant Historina, when attempting to get data using Quick SPC, error message such as below is encountered. An error has occurred.","ExceptionMessage":"Method not found: 'Double OSIsoft.AF.Asset.AFValue.ValueAsDouble()
Solution: The Mtell server need to be installed with the PI AF client. Perform the following steps to check on the version of AF SDK installed. Launch PI System Explorer. Click on Help | About PI System Explorer.... Look for the line which mentioned AF SDK version. As per OSIsoft documentation on OSIsoft.AF.Asset.AFValue.ValueAsDouble(), the version of AF SDK which supports this specific method are 2.7.5, 2.8, 2.8.5, 2.9, 2.9.5 and 2.10. If the AF SDK mentioned in the About PI System Explorer does not match any of the mentioned version, the PI AF client will need to be upgraded to PI AF 2015 R2. Keywords: None References: None
Problem Statement: "Error: The remote server returned an error: (401) Unauthorized" when launching Aspen Mtell System Manager Detailed error when browsing http://localhost:80/AspenTech/AspenMtell/InteropServer/MIMOSA/ Error message 401.3: You do not have permission to view this directory or page using the credentials you supplied (access denied due to Access Control Lists). Ask the Web server's administrator to give you access to 'C:\inetpub\wwwroot\AspenTech\AspenMtell\InteropServer\MIMOSA'. Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3282.0
Solution: This article outlines the instruction to address IIS Error message 401.3: You do not have permission to view this directory or page using the credentials you supplied (access denied due to Access Control Lists). Ask the Web server's administrator to give you access to 'C:\inetpub\wwwroot\AspenTech\AspenMtell\InteropServer\MIMOSA'. Enable Anonymous Authentication: 1. Click Start and type inetmgr to launch Internet Information Services (IIS) Manager 2. Expand Sites and select Default Web Site 3. Double click Authentication 4. Right click Anonymous Authentication and select Enable Identify the account used for Anonymous Authentication: 1. Click Start and type inetmgr to launch Internet Information Services (IIS) Manager 2. Expand Sites and select Default Web Site 3. Double click Authentication 4. Right click Anonymous Authentication and select Edit 5. It should be using IUSR user for Anonymous Authentication Give full permission to IUSR account: 1. Go to C:\inetpub\wwwroot\ 2. Right click AspenTech folder and select Properties 3. Click Edit button in Security tab 4. Click Add IUSR account 5. Give full control allow permission to IUSR account 6. Click Apply and Ok Restart IIS to apply this changes: 1. launch CMD as Adminisrtator 2. Type: IIS Reset Keywords: IIS error 401 Unauthorized MIS Web Service References: None
Problem Statement: When launching Mtell View, the below error message is encountered. Server Error in '/AspenTech/AspenMtell/MtellView' Application. Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
Solution: The error message is due to HTTP Activation not enabled for the .NET Framework. This can be resolved by performing as follow. Launch Server Manager. Click on Next button for "Before You Begin" screen. Click on Next button for "Select installation type" screen leaving selection as "Role-based or feature-based installation". Click on Next button for "Select destination server" screen. Click on Next button for "Select server roles" screen. Tick the checkbox beside HTTP Activation under .NET Framework 3.5 Features. Tick the checkbox beisde HTTP Activation under .NET Framework 4.5 Features | WCF Services. Before is a sample screenshot which shows HTTP Activation is installed. Keywords: None References: None
Problem Statement: When launching aspenONE Credentials, below error message is displayed.
Solution: /Workaround The Tomcat version might have been upgraded by following knowledge based article "Upgrading Tomcat to address Common Vulnerabilities and Exposures (CVE)". However, the previous version of Tomcat folder was left in the directory and instead of copying the conf, webapps and appdata directories, the folders are moved to the newer version of Tomcat folder. The issue can be resolved by performing either of the following actions. Delete the old version Tomcat folder. Rename the old version Tomcat folder by appending "Old_" in front. E.g. Old_Tomcat7.0.56. Keywords: Tomcat users file 'C:\Program Files (x86)\Common Files\AspenTech Shared\Tomcat7.0.56\conf\tomcat-users.xml' does not exist! LDAP users file 'C:\Program Files (x86)\Common Files\AspenTech Shared\Tomcat7.0.56\appdata\solr\collection1\conf\AspenSearchSolrSecurity.xml' does not exist! Tomcat7.0.37 Tomcat7.0.50 Tomcat7.0.56 Tomcat8.0.36 References: None
Problem Statement: When issuing SQL query in SQLplus Web Service page, no data is returned even though the same SQL query is working in Aspen SQLplus using the same Windows account as shown in screenshot below from a V8.8 setup without patches applied. In other version such as V10, Access Denied is returned even though the user has the permission to read from the record and the same SQL query is working in Aspen SQLplus as shown in screenshot below.
Solution: Aspen InfoPlus.21 is having database security implemented. Although the user had been assigned to a role with permission to read the record as determined in Aspen SQLplus, however, it is due to the authentication settings for SQLplus Web Service in Internet Information Services (IIS) Manager. This issue can be resolved by performing as follow: Launch Internet Information Services (IIS) Manager. Select SQLplusWebService under Default Web Site. Double-click on Authentication found under IIS in the middle pane in Internet Information Services (IIS) Manager. Disable Anonymous Authentication. KeyWords: ERROR [HYO92] Invalid attribute/option identifier ERROR [HY000] Error reading definition record (ID = 5) fixed fields: Access Denied Keywords: None References: None
Problem Statement: What are the advantage and disadvantage of deploying and hosting a single vs. multiple license servers?
Solution: Number of SLM Server(s) Advantage Disadvantage Single SLM Server · Lower maintenance costs. · Can host both ENG and MSC Tokens (in separate buckets) · Single log file for Token report generation. · Simpler SLM client/server configuration and license file install. · Greatest License efficiency (Tokens/Licenses are shared among a larger pool of users.) · "Follow the sun" type of license sharing · Single point of failure. · Performance may decrease when hosting a large number of users. · Requires fast, reliable network. Multiple SLM Servers · Better server performance since the number of users per server will be reduced. · Can host both ENG and MSC Tokens (in separate buckets). · Less risk as outage of one server will not impact the users of the second server. · Better for managing different business units at different locations, or separating ENG and MSC users. · Each site or business unit controls its own token/license pool. · Can be a work around for slow network at selected sites. · Higher maintenance costs. · Increased management responsibility needed for client/server machines configurations. · Network issues restricting SLM network access (e.g. PCNs). Keywords: Single license server, Multiple license servers, SLM Server, deployment, hosting, license, and installation References: None
Problem Statement: How to configure AFW Security for SQLplus
Solution: 1. Open “AFW Security Manager” as an administrator 2. On the left panel highlight “Roles” à right click 3. Set the name of the “New Role” (create always a role for the Administrator) àOK(Description is optional) 4. Highlight the role à right click à Properties 5. Select "Members" tab à Add à Advanced 6. A new window will appear, Select "Find Now" à choose the name of the user you want to give or restrict access à OK 7. Apply à OK 8. Highlight “Applications” à Right click à All tasks à Import Application 9. Follow the next tab to find the .XML for SQL à C:\Program Files\AspenTech\InfoPlus.21\db21\sql à select the .XML à Open 10. Now it will appear on your left panel as SQLplus à right click on "Servers" à New à Securable Object 11. On “Name” write the name of the IP.21 Server 12. Highlight “MES” à right click à Properties 13. First choose the role “Admin” à check all the boxes so “Admin” can have complete access à Apply 14. Then choose the “user” that won’t have access to SQLplus à check only the boxes you want the user to have access à apply 15. Exit AFW Security Manager 16. Open Services 17. Highlight “AFW Security Client Service” à Restart 18. If you run SQLplus with the user that has no access it will appear the next window. For additional information, please find the articles below: How does Aspen SQLplus verify AFW security? How does Aspen InfoPlus.21 verify Aspen Framework (AFW) security? Keywords: None References: None
Problem Statement: After installing Aspen HYSYS, the Ejector/Eductor extension is not shown in the Aspen HYSYS Pallete. It is not listed under Customize / Register Extension / Registered Extensions and it doesn't appear in the installation folder C:\Program Files (x86)\AspenTech\Aspen HYSYS V10.0\Extensions
Solution: The Ejector extension was developed as a collaboration between AspenTech and Transvac Systems as a means of illustrating how liquid-liquid ejectors could be modelled in Aspen HYSYS using known correlations and data at that time (2009) from Transvac Systems. This Automation application was created as an example of what can be achieved through the object architecture of Aspen HYSYS. This application was provided for academic purposes only and as such, it was not subject to the quality and support procedures of officially released AspenTech products. In 2014, Transvac explicitly stated that these correlations / data had been revised and they no longer wished for AspenTech to use 'out-of-date' data in modelling such systems as it is not well representing the performance of liquid/liquid ejectors. AspenTech removed this feature from the Aspen HYSYS installation for future versions (as of V8.8) but has kept the legacy tool for modelling steam and gas-gas ejectors (available from the Support website) if users wish to still use it (understanding that it was still an academic illustration). 110065-2 Steam Ejector Extension Unit Op https://esupport.aspentech.com/S_Article?ID=110065 130321-2 Steam ejector extension unit operation for Aspen HYSYS with Aspen Properties https://esupport.aspentech.com/S_Article?id=000030569 For modelling liquid ejectors, AspenTech recommends the extension "Jet pump" from Caltec. This is found in AspenONE Exchange accessible within Aspen HYSYS. Fixed in Version 227049: An enhancement request is being considered to add a native HYSYS unit operation in a future version. Keywords: ejector, extension, Transvac References: None
Problem Statement: In some occasions, HYSYS may calculate and transfer to EDR a Vapor Fraction outside of the expected range from 0 to 1: This will generate an error within EDR and will prevent the model to run. Workaround The reason for this behavior is, in most cases, due to a flash calculation problem. There are two things that could potentially fix this problem: Adjust the temperature range at which properties are being calculated (usually you will need to reduce the range) Change the EOS
Solution: Method from “Cubic EOS Analytical Method” to “Numerical Method”, under Properties Environment | Fluid Packages | Set Up In the future, in case HYSYS calculates a vapor fraction outside the expected range, the values will be capped at the corresponding boundary before being transferred to EDR. Fixed in version VSTS 313336: Fixed in a future release Keywords: Message 1122, Message 1802, vapor fraction, HYSYS, EDR References: None
Problem Statement: Why am I getting input error 1802 when rigorously sizing a Heat Exchanger in Aspen Plus?
Solution: When trying to size a Rigorous Heat Exchanger in Aspen Plus, the following messages in the EDR Browser might pop up: Input Error 1802: P18: Specific enthalpies for stream 1 do not increase with temperautre, (or only increase by an implausibly small amount). Stream data set number 1, at quality 0. Even after Aspen Plus has completed normally, the rigorous sizing will not complete due to the aforementioned message. The reason why this happens is due to the bubble and/or dew points being calculated by Aspen Plus for every model, even for supercritical, which does not have any physical sense. Enhancements are already reported so that Aspen Plus has an option of specifying temperature range when EDR is integrated. In V11, enhancements were made so that EDR gets better and more accurate results for such models. If not possible or no V11 version available, the workaround is: Open EDR as standalone program Go to File | Import and import the heat exchanger from the A+ simulation Review the Property Data and make sure there are not supercritical temperatures there, as well as the specific enthalpy values increasing as temperature values increase. Once the Heat X Design has been achieved, go back to A+ and specify a Shell & Tube exchanger, only this time Size interactively instead and select the obtained .edr file from the previous steps. Keywords: 1802, edr, plus, supercritical References: None
Problem Statement: Is there any downside to using the IoLongTagGetDef transfer records, or IoLLTagGetDef transfer records in place of IoGetDef transfer records?
Solution: The long and LL transfer records add additional bytes to the Standard CimIO message. Long transfers add an extra 40 bytes per tag and LL records add 216 bytes per tag. This generally is not a concern and there is no other downside to using Long, or LL transfers for all gets and puts. Additional details about the Cim-IO message size can be found in the Aspen Cim-IO User’s Guide in the section “Analyzing Performance and Resource Requirements” KeyWords: message store & forward IoGetDef IoGetHistDef IoLongTagGetDef IoLLTagGetDef IoUnsolDef IoLongTagUnsDef IoLLTagUnsDef IoPutDef IoLongTagPutDef IoLLTagPutDef IoPutOnCosDef IoLongTagPOCDef IoLLTagPOCDef Keywords: None References: None
Problem Statement: How to enable .NET Framework 3.5.1 within Windows
Solution: This solution provides instructions for installing .NET Framework 3.5.1 for Windows 8/8.1, Windows 10, Windows Server 2012 R2, and Windows Server 2008 R2. Windows 8/8.1 · Microsoft .NET Framework 3.5 SP1 (3.5.1) in Windows is an optional "Windows Feature" on Windows 8/8.1. To install it, press the "Windows logo key +R" key combination to bring up a run box, then type "appwiz.cpl" and press enter. · This will open the Program and Features part of Control Panel, on the left hand side click on the "Turn Windows features on or off" link. · Next, click on the Plus symbol (+) next to Microsoft .NET Framework 3.5 check box to expand the list. · Click on both Windows Communication Foundation HTTP Activation and Windows Communication Non-HTTP Activation. · Click the OK button to complete the installation of Microsoft .NET Framework 3.5 SP1 (3.5.1) on Windows 8/8.1. Windows 10 · Microsoft .NET Framework 3.5 SP1 (3.5.1) in Windows is an optional "Windows Feature" on Windows 10. To install it, press the "Windows logo key +R" key combination to bring up a run box, then type "appwiz.cpl" and press enter. · This will open the Program and Features part of Control Panel, on the left hand side click on the "Turn Windows features on or off" link. · · Next, click on the Plus symbol (+) next to Microsoft .NET Framework 3.5 check box to expand the list. · Click on both Windows Communication Foundation HTTP Activation and Windows Communication Non-HTTP Activation. · Click the OK button to complete the installation of Microsoft .NET Framework 3.5 SP1 (3.5.1) / 4.5 on Windows 10. Windows Server 2012 R2 · Microsoft .NET Framework 3.5 SP1 (3.5.1) in Windows is an optional "Windows Feature" on Windows Server 2012 R2. To install it, press the "Windows logo key +R" key combination to bring up a run box, then type "appwiz.cpl" and press enter. · This will open the Program and Features part of Control Panel, on the left hand side click on the "Turn Windows features on or off" link. · This will open the Add Roles and Features Wizard part of Server Manager, click Next button. With the default settings, click Next button on "Installation Type", "Server Selection", and "Server Roles" pages. · On the "Features" page, click on the Arrow symbol (►) next to Microsoft .NET Framework 3.5 check box to expand the list. · Check .NET Framework 3.5, HTTP Activation, and Non-HTTP Activation and click Next. Click the Install button on the Confirmation screen. Windows Server 2008 R2 · Microsoft .NET Framework 3.5 SP1 (3.5.1) in Windows is an optional "Windows Feature" on Windows Server 2008 R2. To install it, press the "Windows logo key +R" key combination to bring up a run box, then type "appwiz.cpl" and press enter. · This will open the Program and Features part of Control Panel, on the left hand side click on the "Turn Windows features on or off" link. · This will open Server Manager. Click Features in the left navigation pane and then click the "Add Features" link. · Next, click on the Plus symbol (+) next to Microsoft .NET Framework 3.5.1 Features check box to expand the list. · Next, check ".NET Framework 3.5.1" and "WCF Activation" (includes HTTP Activation and Non-HTTP Activation). Click the Install button to install the features. Keywords: .NET Framework 3.5.1 Aspen Engineering Suite Aspen Manufacturing and Supply Chain Suite AES Install MSC Install aspenONE References: None
Problem Statement: Why can’t I generate Detail Unit Rate Estimating (DURE) reports from Aspen Capital Cost Estimator?
Solution: In order to enable the generation of DURE reports, ACCE performs a check of the available Excel version on the user’s computer, if there is any problem with Excel installation, this can effectively stop ACCE from detecting it and as a result, the option to create these reports becomes grayed out. If facing this issue, the user should first make sure that the current version of Excel installed on their machine is compatible with the version of ACCE currently in use. After this has been verified, the user should proceed to repair the installation of MS Office in order to fix the Excel registry, whish should allow ACCE to correctly detect the installation of Excel and enable the DURE reports. Keywords: Gray, DURE, Disabled, Excel, Run, Report, Detailed References: None
Problem Statement: How to use an Ad-Hoc calculation to calculate the maximum value for multiple tags.
Solution: The Aspen Calc max function allows for 2 tags Max(T1,T2). If the max for additional tags is required the base function can be combined using the following syntax. 2 tags =max(tag1,tag2) 4 tags =max((max(tag1,tag2)),(max(tag3,tag4))) 6 tags =max((max((max(tag1,tag2)),(max(tag3,tag4)))),(max(tag5,tag6))) 8 tags =max((max((max(tag1,tag2)),(max(tag3,tag4)))),(max((max(tag5,tag6)),(max(tag7,tag8))))) KeyWords: max ad hoc aspencalc Keywords: None References: None
Problem Statement: Why is the Description field is grayed out in the Aspen Tag Browser?
Solution: Searching tags by the description field uses Aspen SQLPlus which must be installed on the desktop system and added to the ADSA datasource. Open the ADSA Client Config tool and verify the datasource has the Aspen SQLPlus service component added. Also, check that Aspen SQLPlus is installed on the desktop system. KeyWords: descroption sqlplus Keywords: None References: None
Problem Statement: By default, commuting Aspen Capital Cost Estimator (ACCE) licenses will commute an 8 token license key that is not necessary to run the product.
Solution: Make sure to have this patch installed on the computer that uses ACCE (note: if you are not using the scheduling features of the ACCE, you can go to the next step): V9: https://esupport.aspentech.com/apex/S_SoftwareDeliveryDetail?id=a0e0B00000DjWEzQAN V9.1: https://esupport.aspentech.com/apex/S_SoftwareDeliveryDetail?id=a0e0B00000DjYYeQAN V10.1: https://esupport.aspentech.com/apex/S_SoftwareDeliveryDetail?id=a0e0B00000DjWF4QAN V10: https://esupport.aspentech.com/apex/S_SoftwareDeliveryDetail?id=a0e0B00000DjV1mQAF To properly commute the ACCE licenses open the aspenONE SLM license manager from your start menu: When the aspenONE SLM license manager opens, click on the Commute option: Expand the license server you have configured, select the correct bucket (1) and then select the Aspen Capital Cost Estimator license (2): Expand the Aspen Capital Cost Estimator option (1) and deselect the SLM_Econ_IPS option (2), then proceed to indicate the amount of days you are going to commute the licenses (3), and then proceed to click Commute to finish the process (4): Once the process finishes, you’ll be able to see the commuted licenses and the details of the request. Keywords: None References: None
Problem Statement: What is Aspentech's recommendation for organizing Aspen CimIO transfer records?
Solution: When multiple PLC’s are connected to a Aspen CimIO Interface, Aspentech recommends organizing the transfer records by PLC. This configuration may improve the overall stability of the system and make get record maintenance easier. For example; if one PLC is offline the associated transfer record(s) can be turned off temporarily. KeyWords: Plc Initial Wait for async Keywords: None References: None
Problem Statement: Can I change the cost of bulk materials in Aspen Capital Cost Estimator (ACCE) without indexing the Codes of Accounts (COAs)?
Solution: Yes. The user has the option of entering bulks as quoted items, with user-specified prices. Alternatively, the user also has the option of adjusting bulk prices at the component level using the Options | Mat'l / Man-hours % Adj. & Vessel Tracing form. Keywords: economics, estimate, piping, electrical, instrumentation, insulation, civil, steel, paint References: None
Problem Statement: The Customized Set of Units (Set1, Set2, Set3) are not being correctly used on the Code Calculation report.
Solution: Internally, the program uses one of (3) sets of units: US Customary, SI or Metric. This is a requirement so all the formulas in the Code Calculation section are congruent (units will match). For example, for Pressure, there will always be lb/in2, N/mm2 and kgf/mm2, or psi, MPa and Kgf/mm2. For customized Set of Units, you should always follow these rules: Use Set1 to change US Use Set3 to change SI Use Set2 to change Metric For this example, if the user wants to use MPa on the Code Calculation Report, the user should select Set2. The CC report will appear as N/mm2 (MPa) Keywords: Units of Measure, Units Set, Code Calculation, Set1, Set2, Set3. References: None
Problem Statement: Attached is an example of a User Property Set to calculate the total Gibbs free energy of a stream
Solution: Attached is an example of a User Property Set to calculate the total Gibbs free energy of a stream. A Fortran compiler is needed to compile and run this example. C C C Purpose: This routine is an example of a user-defined property C that can be used within an ASPEN PLUS property set. C C Product C Release: Release 10 of ASPEN PLUS C C Supporting C Files: TESTGFE.INP C C Usage C Notes: The name of this subroutine must be declared on the C Properties.Advanced.User Property form. C The name that is assigned to the object used to store C this property becomes the name for the user property. C This name is assigned before the User-Property form is C entered. The user property must also be specified in a C property set to be included in a stream report. C C Refs: Chapter 7 of the User Models Keywords: None References: Manual. C
Problem Statement: Are the Setting Plans and Tubesheet Layouts displayed for non-TEMA type exchangers?
Solution: Both the Multitube Hairpin (M-type shell) and the Double Pipe (D-type shell) type exchangers are non TEMA type shells and thus are NOT supported for Setting Plans. As for the Tubesheet Layouts, only the layout for the M-type exchanger is displayed on EDR Shell & Tube Thermal. If you try to change the model from thermal to Shell & Tube Mechanical, the model runs with the Warning: "Warning 797: Teams does not design multi-tube hairpin or double pipe. Shell type changed to E". Keywords: 797, multitube, exchanger, EDR, Warning References: None
Problem Statement: If you have been given a SQL Server database file (filename.bak) and need to restore the database.
Solution: Please use below example script (modify where necessary): USE master; GO ALTER DATABASE MTell_Test SET SINGLE_USER WITH ROLLBACK IMMEDIATE; RESTORE DATABASE MTell_Test FROM DISK = 'C:\DB_backup\MtellSuite.bak' WITH REPLACE; ALTER DATABASE MTell_Test SET MULTI_USER; Keywords: None References: None
Problem Statement: What needs to be considered when performing upgrade or maintenance work on SLM License Server?
Solution: The process to follow: 1 – Local I.T. to perform full back up of physical SLM License Server or take snapshot of server if it is a virtual server 2 – Work to be done out of hours 3 – If applying a Microsoft patch or Fix to the SLM License server 4 – Not all Microsoft Patches have been tested by AspenTech so we recommend having a full back up of server prior to Microsoft patch or fix being applied 5 – Make sure you have full admin access to apply the patch or fix 6 – If the server is physical server – do you have remote ILO access if RDP fails? 7 – If the Server is a virtual server – do you have access to VMware console or HYPER-V Console? 8 - Apply the patch or fix required to the SLM server and reboot the server 9 – Have a client system on the side to test and verify license key access – for example can I open HYSYS and get valid license key from the SLM server after patch or fix applied? 10 – Check the following after patch / fix applied: A – Is the SLM server reachable via network access? B – Can I open the License Profiler on a client system and still see the licenses? C – What is speed of ping response to SLM License server from client system – it needs to be below 300ms with no losses D – Check that you can do nslookup to SLM server by ip-address and server name and get back the correct responses E – If I have an Aspen InfoPlus.21 (IP.21) product installation in the organisation – open the IP.21 manager and am I allowed to stop it – Permission needed from Management. Before making any changes to the SLM server. Here you might see the IP.21 server go into a license denied status if service not stopped first in the IP.21 Manager 11 – When applying patch / fix do not take too long to complete the work. 12 – If you take too long other systems will go into grace period, if this occurs those systems with a grace period will need a reboot to get a clean valid license or key 13 – When in grace period you should not attempt to add new tags or records into the IP.21 system, until the SLM server is back and the IP.21 system is showing licenses granted status 14 – When you are applying patch or fix – you should not try and commute licenses for offline usage. If you need to commute licenses for client offline access – this should be done prior to patch or fix being applied to the SLM server. If you commute licenses during this outage may cause the SLM License server to become un-synchronised for licenses in the SLM Pool Keywords: None References: None
Problem Statement: Why are the temperature ranges I specify when importing an exchanger to EDR not working?
Solution: When importing a heat exchanger from an Aspen Plus simulation to Aspen EDR, the following window shows up: Said window displays a table with editable values, so you can try and re-specify Lower and Upper Temperatures on each Pressure set, after which you can click on Import. Once the heat exchanger has been imported, review the ranges for Cold/Hot Stream Properties found under Input | Property Data | Hot (or Cold) Stream Properties. See how they are not respected from the Lower/Upper limits defined (image attached for better view): The actual low and upper limits will be calculated again. This behaviour is by design. Lower and upper limit is display only on the Import window The above table represents the range of temperatures for property curve. In future versions, an enhancement will be added to adjust said table with a hot/cold side factor when decided, to go beyond the dew point to vapor phase. Note including vapor or not will not affect the EDR simulation. Keywords: EDR, import, range, temperature References: None
Problem Statement: Why is there a “Stage 0” in a vacuum column?
Solution: In vacuum columns, the 1_Main Tower section shows specs for Stage 0 . The pressure specification shown for this so called "Stage 0" is the Vacuum Overhead Product Pressure (which is indeed, vapor). Going inside the Column Environment may be more insightful. Stage 0 is merely representing the Prod P pressure, since there is not actual pressure drop in Stage 1. Note Product P is the same as the reported 1-Main Tower Stage 0 pressure on previous screenshot. Since this is a vacuum column, gauge pressure will be negative (below atmospheric pressure). In a distillation column, the pressure rises as the stages increase (bottom pressure is higher than overhead pressure). Hence, in negative values, the bottoms pressure increases (becomes "more positive"). Keywords: vacuum, HYSYS, stage, column References: None
Problem Statement: Why is EDR not giving tube velocities and displaying Error 5 when running?
Solution: The following error may be encountered when running a Shell & Tube exchanger in EDR: This occurs because EDR cannot detect overlapping tube passes and it can obtain a tube layout exchanger design with this characteristic: The algorithm will be changed so that it kept better track of how many rows it had set so that it wouldn't try to overlap them. This better algorithm will come up with a much more reasonable layout. As for now, we can use the 'match pass details' option to force EDR to come up with the same layout, manually modifying the numbers of rows for the various passes. Seeing the following example, we can detect we have 8 tube passes and the default Tube layout option (New (optimum) layout). First off, switch the Tube layout option to 'Match, pass details': Based on the Error 5 and the Tube Layout displayed on the Setting Plan results, we know there’s an overlap of tube passes. In the Exchanger Geometry | Bundle Layout | Pass Details tab, you'll note that typically the numbers for the tube rows/columns/etc for pass region 8 start at zero, which disables the 8th pass for the tubes and overlaps the tube in some other pass. You can try to reduce the number of rows in other pass regions, so that pass 8 has some tubes in it. Any required change on the Bundle Layout Pass Details will have to be done manually: This corrects the error and the layout is correctly retrieved: Keywords: overlap, tube, passes, bundle, layout References: None
Problem Statement: Is there a web version of the Aspen Golden Batch Profile Monitoring Plot?
Solution: Yes, there is a web version of the Aspen Golden Batch Profile Monitoring Plot. You can use aspenONE Process Explorer (A1PE) to create such a plot. Open A1PE, navigate to Process Explorer, click the + button and select the Golden Profile on the Event Plots tab. Keywords: None References: None
Problem Statement: What does Warning 1917 mean on Exchanger Design and Rating?
Solution: The message (on EDR) Results Warning 1917 states: "In a reflux condenser the condensing range was 32.09F. Your input or calculated temperature-enthalpy relationship may not be valid with this condensing range and counter-current vapor-liquid flow." This message basically says that the accuracy of the EDR calculation for a (non-equilibrium) reflux condensation might not be high enough. Reflux condensation is a non-equilibrium condensation. Equilibrium condensation states both liquid and vapor are at the same temperature, and EDR assumes this thermal equilibrium for any Design. For the non-equilibrium (reflux condensation) case, EDR makes some assumptions to come up with a good approximation for the fact that the bulk liquid condensate is not in thermal equilibrium with the bulk (condensing) vapor. The deviation of the non-equilibrium condensate liquid from the equilibrium condensate liquid will become significant when the condensing temperature range (temperature range in which the condensation takes place) is higher than 32 F, and that is the limit where EDR issues a warning message. Warning 1917 may just be a description of the phenomenon taking place. There is a possible alternative to overcome or decrease said range. If the overall expected heat load somehow decreases, the model might be able to get a condensation with a lower temperature range. Please note that decreasing the Heat Load may also have some undesired behavior, such as the outlet temperature not being met. Keywords: reflux, condensation, non-equilibrium, range References: None
Problem Statement: How to include testing hours in ACCE N option
Solution: The attached document explais changes in N-Option for painting costs and coats of painting per component and pipe, instrument and electrical testing for areas. Keywords: N-Option, Paint, AIPCE, ACCE References: None
Problem Statement: Sorry, Error Adding Aspen Calc server ‘SERVERNAME’ This error occurs when using a web browser on the same computer where the Aspen Calc web application is running (in the Microsoft Internet Information Service (IIS), and Enhanced Protection is enabled for the internet zone where the Aspen Calc web application is running. Since it is on the same computer, this will likely be the Local Internet zone.
Solution: This error occurs because when using web browsers like Microsoft Internet Explorer, they are not allowed to invoke operations in IIS (on the same computer) that involve writing to objects like files or registry keys. This is part of the Enhanced Protection feature added to IE a while back. Apparently, actions initiated by IE will cause server-side writes to fail. Recommended: 1. Don’t use the web browser on the same computer where the Aspen Calc web server (IIS) resides. Alternatives: 2. Disable enhanced protection for the appropriate zone in the web browser. This change is specific to each user account that might use the web browser. Please be sure you understand the security implications of disabling enhanced protection. 3. Use the IIS configuration tool to change the application settings of the Aspen Calc web application to connect as a specific user. So instead of using “pass-though” credentials, specify a user account that has been granted DCOM access to all the other computers where Aspen Calc Calculation Scheduler services reside that will be managed using the web application. Of course this solution may not be desirable since it runs all server-side operations under the one user account. This means that Aspen Calc security will not be acting on the user account that launched the web browser. KeyWords: Process Browser Web21 Keywords: None References: None
Problem Statement: What does Warning 1336 mean in EDR?
Solution: When working with a Shell & Tube model in Exchanger Design and Rating, an Operation Warning 1336 may show up. "Operation Warning 1336: The optimum design to minimize surface area (or capital cost) results in a tight baffle pitch with a low crossflow fraction. Consider trying alternative designs with a larger baffle pitch resulting in a slightly higher capital but lowered operating costs" Said warning states the current calculated optimal design (to minimize surface area or capital cost) results in a tight baffle pitch, which may result in a low crossflow fraction. When doing a Design run, EDR will always try to retrieve the “optimal design” based on the unit which provides the lowest surface area or the lowest capital cost. The Warning 1336 provides further insights on said Design, stating that, even if the retrieved design is the one with the lowest surface area (or lowest capital cost), there might be other designs which can provide a lower operating cost. This lower operating cost can be achieved by increasing the baffle pitch (baffle spacing), slightly increasing the Capital Cost, but decreasing considerably the Operating costs of the unit. You can decrease the baffle pitch in the EDR Console by changing the “Specify some sizes for Design” option to Yes: This warning is merely descriptive. If you are sure of the current Design and want the Geometry Limits and Specifications as they are, you can work with said simulation with no problems. Keywords: 1336, Baffle, Pitch, EDR, Warning References: None
Problem Statement: How to add a new craft in the construction workforce project basis
Solution: Under Construction Workforce | Wage Rates display the Craft Wage Rates. Review the Craft code list and pick a number to avoid repeating the same code for the new craft. For example, craft code 55 doesn’t exist in the list below so let’s use that number. Move to Craft Names and include the new code (i.e. 55) and the new Craft name. Click on Apply. In the Crew Mixes, define the amount of labor for the new craft as a percentage of one of the existing craft codes. Below it is shown how the craft code 60 is defined of the new craft 55. This will be the 50 percent of craft code 60. Click on Apply Lastly, define the wage rate and productivity for the new craft in the craft wage rate/productivity from, otherwise, define an overall productivity and wage rate for all crafts Keywords: Construction Workforce, Craft Names, Wage Rates, Craft Code. References: None
Problem Statement: Sorry, Aspen Calc server ‘SERVERNAME’ is not available This error occurs when the web application fails to make a successful DCOM connection to a Calculation Scheduler either locally or remotely. This is typically due to insufficient DCOM access permissions on the computer where the Calculation Scheduler service is running. Following the recommendations in Aspen Calc Web Application Configuration below will allow the connection.
Solution: Aspen Calc Web Application Configuration Aspen Calc’s web application allows users to connect to the Calculation Scheduler service on computers throughout a network. Once connected, users can manage the Calculation Scheduler using a web user interface instead of having to install the Aspen Calc thick client application. However, since it is a web application, some configuration steps must be completed to enable seamless connections to the Calculation Scheduler services across the network. The Aspen Calc web application connects to external Calculation Schedulers by using Microsoft’s Distributed Component Model (DCOM). This communication mechanism requires the opening TCP/IP ports, as well as, proper configuration of DCOM settings. Additional complexity exists when trying to pass user authentication credentials from a client-side web browser to the Aspen Calc web application, and finally to the target Calculation Scheduler. All three applications could be on three different computers. Properly Configure DCOM Security Changes must be made to the DCOM security settings on each Aspen Calc server. The changes below result in the tightest (most minimal) configuration. It does not alter the overall default system permissions, nor the permission of any other COM component other than the Aspen Calculation Engine. 1. Log onto each server computer where the Aspen Calc Scheduler service is running that you wish to access from a remote Aspen Calc Web application server. 2. Configure DCOM settings by launching Component Services from the Server Manager (or Control Panel, Administrative Tools). 3. Expand to the My Computer node and select the Properties option. 4. From the Default Properties tab, ensure that DCOM is enabled. 5. From the COM Security tab, add an entry for ANONYMOUS USER, and DISTRIBUTED COM USERS to the Access Permission Security Limits. 6. From the COM Security tab, add an entry for ANONYMOUS USER, DISTRIBUTED COM USERS to the Launch and Activation Permission Security Limits. There is no need to change either of the default permissions. Note: Setting permission limits does not grant or deny access to COM components, but instead it sets the limits when permissions are later set. For example, if you set limits for ANONYMOUS LOGON to allow local access but not remote access, then later if you try to grant remote access permission on a specific COM component, it will not be honored. This is because it is limited by the global limits. This is why remote access is added as an allowed limit here; so that later we can grant this to the specific Aspen Calculation Engine COM component. 7. Add the AspenCalc users to the Distributed COM Users group. 8. Now the DCOM security settings must be configured for the Aspen Calc Scheduler Service itself. So, select the DCOM Config node, then select the AspenTech Calculator Engine component. Right-click and select Properties. 9. Select the Security tab and enable the Customize option. Then, click the Edit button and add ANONYMOUS LOGON, and DISTRIBUTED COM USERS. 10. Grant Allow Remote Activation permission for ANONYMOUS LOGON, and DISTRIBUTED COM USERS. AspenCalc folder permissions On the Aspen Calc and Web Server, add the Everyone group to the Security on …\AspenTech\Aspen Calc folder and allow Read & Execute, List permissions KeyWords: Web21 Process Browser Keywords: None References: None
Problem Statement: Why do I see the Input Warning 1869: “The specified or implied heat load is above the maximum plausible value. It has been scaled by x.xx, to give this value as a first estimate for the Simulation calculation”? How do I prevent it?
Solution: When working on Simulation mode, you have to specify the exchanger geometry and process information defining a first estimate of the duty. However, if the specified/estimated heat load for either the hot/cold streams is above the largest possible heat load based on your inlet conditions, Aspen EDR will escalate the initial duty and use that new value as a first estimate for the calculations. To remove this warning, you should carefully check if your specified or implied outlet temperatures are indeed feasible. Keywords: Warning 1869, Heat Load, First estimate. References: None
Problem Statement: On the HTFS Resonance Analysis table, when tubes report a Turbulent Buffeting ratio (Ft/Fn) between 0.8 to 1.2, they are marked with an asterisk, as possible vibration problem. However, no Turbulent buffeting amplitude is reported. What is the reason for this?
Solution: When the natural frequency is high (i.e. grater than 88Hz) it yields zero amplitude according to the TEMA method calculation for Turbulent buffeting amplitude. When using the HTFS method, Aspen EDR does not report the zero amplitude value as it is not physical. In the same way, the Resonance Analysis only report the highest turbulent amplitude for a particular tube. For additional information, refer to the articles below: How can I interpret the Resonance Vibration results given by the HTFS method in Aspen Shell & Tube Exchanger? What is Turbulent Buffeting, and how can it be minimized? How is the turbulent buffeting frequency calculated? Keywords: Vibration Analysis, Resonance Analysis, HTFS, Turbulent Buffeting, Frequency ratio. References: None
Problem Statement: When opening the MOC (Manufacturing Operations Control) you may get the message "Server watchdog Condition Detected" in the MOC Client?
Solution: This message will appear by default every 60 seconds if the Apache tomcat server is not running or cannot be reached. To resolve this issue check the following: Check the server to ensure that the Apache Tomcat service is running. On the server check the flags.m2r.cfg for the port number and ensure this is open on the Client windows firewall router etc.. Typically this port is 8080. Default location is C:\Program Files\Aspentech\AeBRS\cfg_source\path.m2r_cfg C:\Program Files\Aspentech\AeBRS\cfg_source\ The java version you are using has been updated. Restore to supported version in installation documentation. If the problem is associated with an existing workstation: Close and reopen the MOC. Log in and as soon as the MOC comes up, go into the orders module and cancel the order. Note: Do not try to open the order or it will get locked up again. For Configuration of the Server watchdog please refer to New Aspen eBRS Feature: The Watchdog Keywords: Server Watchdog Watchdog MOC Aebrs References: None
Problem Statement: What does the “Note 866: Designer elected to apply ASME VIII Div 1 UCS-68(c) MDMT temperature reduction” means?
Solution: Minimum Design Metal Temperatures (MDMT) are set based upon the lowest operating temperature the pressure vessel will encounter. Material specifications, impacting testing, and PWHT should be selected that will meet the MDMT requirements per the applicable design construction code. The Note 866 means you have selected the option to apply the ASME VIII Div 1 UCS-68(c) MDMT temperature reduction (Input | Materials | Main Materials | Normalized/Clad Materials) The program will examine each component separately and calculate its minimum design metal temperature, the outcome can be checked from Results | Code Calculations | MAWP/MDMT/Test Pressures. Note: By changing material specifications or testing the component, you can lower the minimum design metal temperature to a desired value. However, the ASME Code has many rules on this subject (such as those presented in UG-20(f)) so it is recommended to use additional judgment and experience when deciding on the minimum design metal temperature for a vessel. Keywords: Note 866, MDMT, UCS-68(c), Temperature Reduction. References: None
Problem Statement: How PIMS AO calculates Nonlinear Ratio
Solution: PIMS AO uses nonlinearity ratio to represent the accuracy of the predicted change in the equation. If the equation is linear, the nonlinearity ratio will be 1.0, otherwise it indicates how nonlinear it is. A negative nonlinearity ratio indicates movement of variable value in the opposite direction. And a large negative value indicates a discontinuity or bad derivatives. Nonlinearity ratio is calculated for each equation in the model as below: Nonlinearity Ratio (NLR)= Approximated value / Exact value For example, assume f(x) = x2 is linearized at x = 1 Write the Taylor series expansion (1st order) f(x)|xo=1 ≈ f(xo) + (x – xo) * f’(xo) = 2x – 1 When x = 1, NLR = 2*1-1/12 =1 When x =2, NLR = 2*2-1/22 =0.75 When x=-1, NLR = (2*(-1)-1)/(-1)2 =-3 Keywords: None References: None
Problem Statement: How can I determine which license keys are being used by an aspenONE V8.x application?
Solution: In versions prior to V8.0, this was displayed by selecting Help from the toolbar and then select About. In V8.0 and higher, this functionality is accomplished by selected to File, About, and then Licensing Information. After clicking the License Information button, a display will show the license key(s) currently checked out, along with the expiration, and the license server being used. Note: Some aspenONE products may only check particular license keys depending on the model/case configuration. Keywords: license key licensing information File | About References: None
Problem Statement: Is there a way to change the nozzle locations for a Shell and Tube exchanger?
Solution: You can set the locations for the nozzles in the EDR model. Just go to Exchanger Geometry | Nozzles | Nozzle Orientation and choose from the dropdown options for either Shell or Tube Side Nozzles. Just be aware the nozzle orientation may not be acceptable by EDR. If you select a non-acceptable location nozzle, the program will show error messages related to the nozzle location. Keywords: nozzle, orientation, location, shell, tube, exchanger References: None
Problem Statement: How to report Flooding Velocity for knockback condensers in EDR?
Solution: Currently, the program provides messages if the inlet velocity is close to the flooding velocity based on the following criteria: Warning message if inlet velocity exceeds flooding velocity Warning message if inlet velocity is 80% of the flooding velocity Advisory message if inlet velocity is 50% of the flooding velocity No message is displayed if inlet velocity is below 50% of the flooding velocity In a future version, both inlet velocity and flooding velocity will be reported for all knockback condenser cases. Keywords: Flooding velocity, knockback condenser, advisory 1334 References: None
Problem Statement: How to model a Plate Fin Kettle exchanger in Aspen Exchanger Design and Rating?
Solution: The program Aspen Plate Fin Exchanger allows modelling these types of exchangers. The only calculation mode available is Stream by Stream simulation which uses the common wall temperature assumption. Other calculation modes such as Layer by Layer simulation, Rating and Design are not available for these types of exchanger. In the plate fin kettle example attached, a cross-flow plate-fin exchanger is used instead of a tube bundle. The parting sheets are vertical. The cold stream has vertical fins open at the top and bottom to permit boiling in up-flow, and return of un-vaporized liquid to the pool in which the exchanger is immersed. The hot (condensing) stream flows horizontally. The exchanger is defined as being horizontal, with the condensing stream inlet at end A. The condensing stream has distributors. To specify the exchanger, in Input | Problem Definition | Application Options, select Plate-fin Kettle as exchanger type. In the Process Options tab, the boiling stream has its “Stream type” set to “Thermosiphon” and the “Flow direction” set to “Crossflow”. The rest of the specifications of the exchanger can be set up in the Input | Exchanger Geometry. Keywords: Plate Fin Kettle, Thermosiphon, crossflow. References: None
Problem Statement: Where are the logs for Aspen Cloud Connect?
Solution: The logs for Aspen Cloud Connect are located in folder C:\Program Files\AspenTech\Aspen Connect\ ToolKit logs: C:\Program Files\AspenTech\Aspen Connect\Toolkit\Logs DataCollector logs: C:\Program Files\AspenTech\Aspen Connect\Cloud Connect\DataCollector\Logs DataSender logs: C:\Program Files\AspenTech\Aspen Connect\Cloud Connect\DataSender\Logs KeyWords: Aspen Cloud Connect Cloud Keywords: None References: None
Problem Statement: What inputs affect the pricing of a flow meter? I have made quite a few changes to my piping rates, viscosity, and density, line/loop specs etc. but the flow meter price stays the same.
Solution: Flow instruments are added at a unit cost and are independent of the piping rates, viscosity, and density, line/loop specs etc. You can view and modify the unit prices using the Aspen Capital Cost Estimator tool using the Unit Rate estimating feature. Attached is a screenshot showing the unit price for the flow instrument. You can find more information on how to use Unit Rate Estimating in the following KB solutions: 000041271 - Using Detailed Unit Rate Estimating 000020753 - Jump Start - Detailed Unit Rate Estimating using Aspen Capital Cost Estimator Keywords: Flow Instruments, Unit Rate Estimating References: None
Problem Statement: I am getting an ERROR message when I run my scenario estimate. What does ERROR> 'PC - 4' CABLE TYPE TO OPERATOR CENTER IS INCORRECT mean and how do I fix it?
Solution: The PC-4 ERROR to refers an ERROR in the Process Control section of the Project Basis. The origin of the problem is the Control Center definintion. If M is the option selected in the Cable type to Operator Center field, while DDCTL (Digital) is the specified Control Center type, this ERROR will occur. The M option for the Cable type to Operator Center field only applies to Analog Control Center types (this is shown in the description field when the cursor is placed on Cable type to Operator Center field, ‘M’ option. Accessng Run| Scan for Errors from the program user interface Menu bar will also display the scenario error list in the Report Editor window. . Keywords: HIWAY, Cable type to Operator Center, Process Control, ERROR PC-4, References: None
Problem Statement: Why do I see the “Input Warning 1061: Based on the inlet and outlet conditions the cold stream is a liquid, but two-phase properties have been specified. The program may apply subcooled boiling calculations”?
Solution: Suppose the cold stream outlet temperature is just below the bubble point (so really the cold stream is single-phase liquid). It is quite possible that at some point along the tube, the local wall temperature may be above the bubble point, that may cause the fluid to locally boil, but later may re-condensate when mixed with the rest of the fluid. If only single-phase properties are input then only a single-phase calculation can be performed. However, if two phase properties have been entered (such as using B-JAC / COMThermo / Aspen Properties), then it would be possible to perform a boiling calculation at the tube wall. This could lead to a higher heat transfer coefficients and increased frictional pressure losses than a true single-phase calculation. This concept when the wall temperature in a liquid below its bubble point is high enough to generate vapor bubbles, even if the outlet temperature (mixed mean) is below the bubble point, is called Subcooled Boiling. Subcooled calculations can be turned off by selecting ‘Not Allowed For’ for the Subcooled boiling accounted for in option on the Input | Program Options | Method/Correlations | Vaporization tab. Note: The default to carry out the Subcooled Boiling calculations and allow for any increase in HT coefficients and frictional pressure losses. There is a similar concept with condensation, when the bulk temperature of a stream is above the dew point, but the local wall temperature is below the dew point, called Wet Wall Desuperheating (WWD). Further details are explained on the article Why do I see the Input Warning 1060: "Based on the inlet and outlet conditions the hot stream is a gas, but two-phase properties have been specified". The program may apply wet-wall desuperheating calculations? Keywords: Warning 1061, Subcooled Boiling, Vaporization. References: None
Problem Statement: The attached document describes how to set Property Table values using EDR’s Automation (COM) interface. This document also provides some related information that is useful when using EDR’s COM interface from Visual Basic or VBA in Microsoft Excel. Also see the section “The Aspen EDR .NET Automation Server” in the EDR Help (in Supplementary Programs and Databases) for more information.
Solution: This guide covers: How to identify variables How to Keywords: EDR, VBA, COM Interface, Properties, Variables, Automation. References: the EDR COM interface EDR COM interface Setting Properties
Problem Statement: When estimating the cost of a project that includes a HDPE High Density Polyethylene fusion bonded plant bulk pipe an error message saying SDR NOT AVAILABLE is thrown. Why is this happening?
Solution: The reason for the error message is due to the standard pipe availability recognized by Aspen Economic Evaluation for pipe diameter and SDR number. For example, if a HDPE pipe with an SDR of 7 is defined with a 30 inch inner diameter (ID) pipe you will, the following message: ERROR> 'PIP- 88' REQUESTED PRESSURE/SDR NOT AVAILABLE AT THIS DIAMETER. MAX. SDR OF 9.0 ,MAX. PRESSURE OF 200.0 PSIG AVAILABLE Or similarly if the SDR of a 32.5 inch ID pipe with an SDR of 3 were evaluated the message that Aspen Economic Evaluation will send would be: >WARN > 'PIP- 88' REQUESTED PRESSURE/SDR NOT AVAILABLE AT THIS DIAMETER. SDR OF 26.0 WILL BE USED HDPE Pipe availability table shows the SDR available for different pipe ID and is provided in this below: Pipe diameter (inch) SDR (Standard Dimensional Ratio) 7 9 11 13.5 15.5 17 21 26 32.5 2 Y Y Y Y Y Y N N N 3 Y Y Y Y Y Y Y Y N 4 Y Y Y Y Y Y Y Y N 5 Y Y Y Y Y Y Y Y Y 6 Y Y Y Y Y Y Y Y Y 8 Y Y Y Y Y Y Y Y Y 10 Y Y Y Y Y Y Y Y Y 12 Y Y Y Y Y Y Y Y Y 14 Y Y Y Y Y Y Y Y Y 16 Y Y Y Y Y Y Y Y Y 18 Y Y Y Y Y Y Y Y Y 20 Y Y Y Y Y Y Y Y Y 22 N Y Y Y Y Y Y Y Y 24 N Y Y Y Y Y Y Y Y 28 N Y Y Y Y Y Y Y Y 30 N Y Y Y Y Y Y Y Y 32 N N Y Y Y Y Y Y Y 36 N N N N Y Y Y Y Y 42 N N N N N Y Y Y Y 48 N N N N N Y Y Y Y 52 N N N N N N N Y Y 54 N N N N N Y Y Y Y This table is also available as an attachment to this article. If the pipe ID is defined to an available SDR, the project should evaluate without any issues relating to SDR, ID pipe availability.. Keywords: Standard diameter ratio, HDPE bulk pipe, SDR, pipe availability References: None
Problem Statement: What does "Operation Warning 1920: Flame height is too large for the firebox" means, and how do I prevent it?
Solution: The flame length is used to determine the heat release pattern within the firebox. You can either specify a value, or leave it blank, to let the program determine a typical value given the fuel and burners specified. As the Operational Warning states, the flame height is too large for the Firebox; in Aspen Fired Heater, the height of the flame should not exceed two-thirds the height of the firebox and adequate lateral clearance must be provided between the edge of the flame and the front face of the tubes. To avoid this operational issue, we recommend the following: If you input the flame length value, you should check the firebox geometry (Heater Geometry | Firebox | Layout | Firebox dimensions) Note: Typically, the firebox height is 2.5 times the width of a cabin firebox, or 2.5 times the diameter of a cylindrical firebox. With much lower values, there is a risk of the flame being so high as to overheat the roof. With much higher values, the heating at the top of the firebox may be much less than elsewhere. If you are using the program model for flame length, you should check that you have set appropriate values for the Firebox input items: Type of burner (Heater Geometry | Firebox | Layout | Burner details) Type of fuel (Program Options | Thermal Analysis | Firebox Zones) Additional information on flame lengths is given in HTFS Handbook Sheet RD3, available via the HTFS Research Network. Keywords: Warning 1920, Flame Height, Flame Length, API 560, burner, fuel. References: None
Problem Statement: Why if I use EDR inside HYSYS to size a heat exchanger, the resulting heat exchanger has different geometry than the one I would get if I use EDR independently and import the properties from HYSYS?
Solution: These differences are probably caused by properties used during the design process, and are usually observed when there are two liquid phases present in at least one of the streams. When EDR is used standalone and a HYSYS file is imported (containing two liquid phases in one of the streams), both liquid phases are combined into one, so average properties are calculated for the overall phase. However, when EDR is used inside Aspen HYSYS, both liquid streams are imported as they are, as well as their properties, so no combination occurs. Using average properties when two liquid phases are present could lead to inaccurate results, so it is recommended to use the import capability in EDR standalone with caution. You can always create the heat exchanger in EDR connected to HYSYS and then export it to EDR standalone if further modifications must be made. Keywords: EDR, HYSYS, results, differences, two liquid phases, properties, activated, standalone References: None
Problem Statement: Security Alert: Information about Meltdown and Spectre fixes and AspenTech software
Solution: AspenTech is aware of recently disclosed research regarding side-channel analysis of speculative execution on modern computer processors. Several different vulnerabilities have been identified, which have been named Meltdown and Spectre by the researchers and are tracked as CVE-2017-5715, CVE-2017-5753, and CVE-2017-5754 in the National Vulnerability Database (https://nvd.nist.gov). AspenTech is evaluating the impact of these vulnerabilities on our products, and this knowledge base article will be kept in place and updated as new information is available. The situation is very dynamic, with different hardware and operating system vendors releasing patches rapidly. We are in the process of evaluating the potential impact of these patches on AspenTech software and have found: Microsoft patches released in early January introduced a DCOM issue that caused problems with some Aspen MSC software. The follow-up Microsoft patches corrected this issue. No currently known issues (including performance issues) with latest Microsoft patches available as of 18-Jan-2018. We recommend that customers follow appropriate procedures to test and validate any patches issued by hardware and software vendors to address the Spectre and Meltdown vulnerabilities before applying to any production systems. Keywords: CVE-2017-5753 CVE-2017-5715 CVE-2017-5754 Meltdown Spectre Vulnerability Security References: None
Problem Statement: What does "Operation Warning 1918: Stack exit temperature is below the dew-point" mean, and how do I prevent it?
Solution: On gas fired heaters, the dew point of the flue gas is around 330 K (57°C) and the condensate is water made slightly acidic by dissolved CO2 and NOx. With sulfur-laden fuels a more serious problem arises in that dilute sulfuric acid is formed. The presence of this acid not only increases corrosion but raises the dew point considerably, perhaps to as high as 415 K (142°C) when burning 3.5% sulfur fuel oil. It is important that not only must the stack gases exceed this dew point but also all the metal surfaces in contact with them. In practice, this gives a minimum exit temperature of around 380 K (107°C) for gas firing, 450 K (177°C) for high-sulfur fuel oil firing. On heaters where a very high efficiency, and therefore a low exhaust temperature, is sought, care must be taken with regard to the dew point of the flue gases, particularly if high-sulfur fuels are in use. For example, to avoid very cold surfaces at the cold end of the heater, coils handling fluids which are very cold at the inlet are often arranged wholly or partially co-current with the gas. This topic is more fully discussed in the following HTFS Handbook Sheets, available via the HTFS Research Network: RP14: NOx Reduction Techniques: a Critical Review RP15: SO2 Reduction Techniques: a Critical Review RP16: CO2 Reduction Techniques: a Critical Review Keywords: Warning 1918, Stack exit temperature, Dew Point, Exhaust gas. References: None
Problem Statement: How can Aspen Plus Data Fit data be retrieved via Visual Basic COM?
Solution: An example, written in Visual Basic for Applications (VBA) in Excel97, on how to access data within an Aspen Plus Data Fit data set is attached. The Visual Basic code in this example can also be used in standalone Visual Basic projects. The data is triple indexed. The first index is traditional. The second index is the name of the variable. The third index indicates whether the variable was declared as a DataFit Input or Result. The InputResult string variable holds that designation. Also, since Value is a Visual Basic built-in property, it must be enclosed within Elements to explictly refer to the Aspen Plus VALUE folder. The subroutine that retrieves the data is in this example is called GetDataFitVars. A key loop from this routine follows: ' Define pointer to folder containing data Set DSCol = DS.Elements("VALUE").Elements NLines = DSCol.RowCount(0) For I = 0 To NVar - 1 ' Find out whether variable is an Input or Result type InputResult = DSCol.Label(2, I) Range("Grid").Offset(2, I).Value = InputResult For N = 1 To NLines ' Print each variable ' Data is indexed by row number (N-1 -> Nlines - 1), ' Variable Name (Var(I), I=0 -> NVar - 1), ' "INPUT" or "RESULT" (InputResult) Range("Grid").Offset(N + 2, I).Value = _ DS.Elements("VALUE").Elements(N - 1, Var(I), InputResult).Value Next N Next I ' Retire pointer Set DSCol = Nothing For example to accessing the first two variables in a sample data-fit data-set: Node.FindNode("Model Analysis Tools\Data-Fit\Data-Set\SET-1\Input\VALUE\(#1,FPHEN, INPUT)").Value = 141999 Node.FindNode("Model Analysis Tools\Data-Fit\Data-Set\SET-1\Input\VALUE\(#1,TPHEN, INPUT)").Value = 219 KeyWords automation VBA Keywords: None References: None
Problem Statement: Example of a User Property Set to calculate the solids concentration in a slurry based on g/L or wt. % Both Aspen Plus 9 and 10 Fortran routines are attached.
Solution: C--THIS FILE HAS BEEN CONVERTED BY AP9TO10---- C Purpose: This routine is an example of a user-defined property C that can be used within an ASPEN PLUS property set. c C Product C Release: Release 10 of ASPEN PLUS C C Supporting C Files: TESTSOL.INP C C Usage C Notes: The name of this subroutine must be declared on the C Properties.Advanced.User_Property form. C The name that is assigned to the object used C to store this property becomes the name for the user property. C This name is assigned before the User-Property form is C entered. The user property must also be specified in a C property set to be included in a stream report. C C Refs: Chapter 7 of the User Models Keywords: None References: Manual. C C
Problem Statement: In the Aspen Cim-IO Interface world, an ''Unsolicited'' request means that you would like the value sent : from the Aspen Cim-IO Server, to the CIM-IO Client (InfoPlus.21 Server), ONLY when the value has changed (or changed by a certain amount). In this case, what is the reason, meaning and impact of the IO_FREQUENCY field in an IoUnsolDef transfer record?
Solution: If you look in the Aspen Cim-IO User''s Guide for the description of IO_FREQUENCY for an IoUnsolDef record, you will see a lengthy explanation of the impact of using positive or negative numbers in that field. The first thing to realize is that every Cim-IO Interface is unique and their capabilities depend on the type of process equipment they each interact with. Due to this interaction, it''s important to look at the specific Interface User''s manual for detailed explanations and/or restrictions. For example, the Aspen Cim-IO for Bailey SemAPI Interface, along with Bailey''s API, supports true Unsolicited requests. However, it is possible to get different results when using different values in the IO_FREQUENCY field. With this interface, the IO_FREQUENCY field is used as a time-based filter (or deadband) so that you could remove small ''chatter'', or if it''s decided that you do not want values sent more frequently than (say) 15 seconds. This is fully explained in both the User''s Guide for this interface as well as in Knowledge Base solution 115080. Another example is with the popular Aspen Cim-IO for OPC Interface. Unlike Bailey SemAPI, OPC servers do not truly support unsolicited requests. However Aspen''s interface does. With a Positive value for IO_FREQUENCY, the OPC Server will be polled at that frequency and automatically filter out identical values. With a Negative value for IO_FREQUENCY, it is the Aspen scanner process (cimio_sf_scanner.exe) that polls at the specified frequency. In this case a ''Deadband'' needs to be provided to perform the filtering. Knowledge Base article 105251 discusses this further. Although both interfaces perform in totally different ways for Unsolicited requests, you can see that IO_FREQUENCY can be thought of as a filter in both cases. Finally, a few customers have requested the ability to get true Unsolicited AND get a value at a fixed time interval such as once per hour. In general that is not possible with a single IoUnsolDef record. One workaround would be to also create a scheduled IoGetDef record pointing between the same DCS address and InfoPlus.21 database. With the Aspen Cim-IO for Fisher Chip interface only, it has been discovered that just activating the IoUnsolDef Get records will cause a value to be sent from the Server to the Client, even if the value has not changed. Therefore if you want a value to be sent, for example, once per hour, whether the value has changed or not, you could create a ScheduledActDef record, add all the IoUnsolDef record names to the ScheduledActDef record, then re-schedule it once per hour (or whatever period you require). One interface that does provide this ability automatically is the above mentioned Aspen Cim-IO for Bailey SemAPI Interface. Should you have any questions on specific Interfaces, unsolicited related or not, please contact your local AspenTech Technical Support Group. KeyWords Keywords: None References: None
Problem Statement: How to limit the maximum number of Tokens can be commuted from SLM License Server
Solution: A user can commute any number of tokens from a SLM License Server using the SLMCommute tool. This article will help you to add a token percentage cap on the SLM Server so that all the tokens will not be used by commuting users. 1. Login to the SLM License Server 2. Open the Environment Variables from the Advance System Settings: a. Right click My Computer and select properties. b. Click Advance System Settings. c. In the Advance Tab, click Environment Variables. 3. In the System Variables section, look for the LServOpts variable and double click to modify it. 4. Modify the Variable value and append -com value (Percentage 0 to 100) at the end of the line. Example: -l "C:\Program Files (x86)\AspenTech\SLMServerLogs\lserv.log" -z 5m -lfe 2 -com 10 Note: -com 10 means 10% of the total tokens on the SLM License Server will be allowed for commuting. Please do not modify anything before the "–com" variable, as this setting is for generating Usage logs. 5. If you wish to block commuting tokens completely on the SLM License server, then set the Variable value as -com 0 for 0% of the total tokens available on the SLM License server. Example: -l "C:\Program Files (x86)\AspenTech\SLMServerLogs\lserv.log" -z 5m -lfe 2 -com 0 6. Restart the Sentinel RMS License Manager Service for the changes to take effect Keywords: SLM Commute SLM Tool Limit Commuting Token Reduce Disable Commuting References: None
Problem Statement: What are all the different worksheet with EIU Template and its purpose?
Solution: The different worksheets specify Settings, crude tank volume & properties, crude receipt events info, component run down info. & assay info. Additionally, specifying for each sheet please refer below: Worksheet names associated with data you are importing, must match the following: Worksheet Name Description Settings Mandatory for all workbooks CrudeInventory Only used by APS Contains crude tank volumes and properties CrudeEvents Only used by APS Contains crude receipts ProcessInventory Contains all component and finished product volumes and properties ProductEvents Contains all product/component receipts or shipments Component Rundowns (Mapped in the Settings worksheet) Only used by MBO Each component will have a separate worksheet for the rundown. Component worksheets will be mapped to MBO codes on the Settings worksheet under the #Component Rundowns section. Assays (Mapped in Settings worksheet) Only used by APS Each assay worksheet needs to be mapped to an APS crude unit under the #Assays section on the Settings worksheet. PriceSet (Mapped in Settings worksheet) Each price set worksheet needs to be mapped to price set name. under the #Price Set section on the Settings worksheet. In addition, if you are importing assays (APS only), the following mapping worksheets must also be included: Mapping Worksheet Name Description PIMS_ASSAY_XREF Maps PIMS crude towers to Petroleum Scheduler crude towers PIMS_CRUDE_XREF Maps PIMS crude codes to Petroleum Scheduler crude codes PIMS_PROP_XREF Maps PIMS crude properties to Petroleum Scheduler crude properties PIMS_STRM_XREF Maps of PIMS crude streams to Petroleum Scheduler crude streams WholeCrudeProps Maps PIMS to Petroleum Scheduler entire crude codes and values. KeyWords APS, Excel work book, EIU, template, worksheet Keywords: None References: None
Problem Statement: What type of pressure Aspen Exchanger Design & Rating (EDR) uses?
Solution: All the pressures in Aspen EDR are absolute, unless it is specified otherwise. This is to maintain consistency with the literature references, in where is well accepted that all pressure is absolute, unless it is specified as gauge/relative. Note: the specified design pressures used in the mechanical design calculations are always in gauge pressure, which is one atmosphere less than the equivalent absolute pressure. Keywords: Pressure, Absolute, Gauge, Relative. References: None
Problem Statement: Why do I see the Input Warning 1862: "In absence of adequate information to determine heat loads, it has been assumed that stream 1 condenses completely (…)”? How do I prevent it?
Solution: When working on Simulation mode, you have to specify the exchanger geometry and process information defining a first estimate of the duty. However, if the program does not have enough information to estimate this initial duty (for example, if you only defined the inlet conditions and flow rates of the hot and cold streams, but not the outlet conditions), Aspen EDR will assume the hot stream condenses completely and use that as first estimate. Then the program calculates the stream actual outlet conditions and hence the actual duty. If you would like to remove such warning message, you only need to explicitly supply in the process data input, enough values to estimate this first duty on one of the process streams. Keywords: Warning 1862, Heat Load, Condenses Completely. References: None
Problem Statement: This article explains what the messages "The timestamp in one of the cache.dat files does not match that of the snapshot." and "Performing history synchronization." found in TSK_DBCLOCK.OUT mean.
Solution: Aspen InfoPlus.21 points are records that store history. A point has one or more history repeat areas. History repeat areas hold the most recent historical values for points. For example, a record defined by IP_AnalogDef has a history repeat area named IP_#_OF_TREND_VALUES which contains the most recent compressed trend values for the record. History synchronization occurs when Aspen InfoPlus.21 verifies the contents of history repeat areas against the most recent recordings stored in history file sets. File sets are searched from newest to oldest. History synchronization can be time consuming if there are many points in the database, or if the database contains many points that have not been recently updated, forcing a search of many file sets. When Aspen InfoPlus.21 stops, the database sets timestamp markers in the headers of the database snapshot and the cache.dat files associated with each history repository. When starting Aspen InfoPlus.21, TSK_DBCLOCK compares the timestamp markers. If they are the same, TSK_DBCLOCK bypasses history synchronization, speeding the time it takes to start Aspen InfoPlus.21. If TSK_DBCLOCK performs history synchronization, allow it to finish. Restarting TSK_DBCLOCK forces history synchronization to start again. Keywords: TSK_DBCLOCK cache.dat history synchronization References: None
Problem Statement: How do I add a new sensor to an existing Equipment Set?
Solution: To add a new sensor role to an existing equipment set please follow the steps below. 1. Log into Aspen Mtell Agent Builder and click on the Machine Learning tab 2. Highlight the equipment set you would like to add a new sensor role to and click on the Sensor Roles tab 3. Click on the Add.. button 4. On the Define Sensor Role screen enter the Sensor Role Name of the new sensor and enter a Description. If additional information like the Category, Measurement or Outlier Values is available it can be added 5. Click OK 6. Click on the Sensor Mappings tab and find the newly added sensor role, it should appear without a tag 7. Right-click in the empty tag field and select Edit 8. On the Select Sensor Mapping for Sensor Role screen click on the … button 9. On the Select Sensor screen type in the tag for the new sensor role in the Filter field and click Refresh. You can also type part of the tag name and click Refresh to pull up a list of similarly named tags. 10. When the tag is populated select it and click OK. 11. Back on the Select Sensor Mapping for Sensor Role screen, enter any additional information like Valid Range or Data Lookback, if required, and then click on Re-import and Retrain button. The new tag will be saved, data will be imported, and any associated agents will be re-trained Keywords: Adding sensor roles Adding new sensor roles References: None
Problem Statement: After creating a new KPI, the calculated values and the display on the right side of the Plot Area do not appear
Solution: If the KPI doesn’t bring any data but the tag is collecting information correctly, open InfoPlus.21 Administrator and look for the KPI created. On the fix area look for the IP_CONFIG_STATUS it must be on OK. If is empty this means that the TSK_KPI has not been created or is not running. If it’s not running you will need to double click on it and Run Task, if it has not been created you will need to create it with the KPI Wizard or directly in the InfoPlus.21 Administrator. The executable for this task is kpi_task.exe and it is located con C:\Program Files\AspenTech\InfoPlus.21\db21\code\kpi_task.exe Keywords: KPI IP_CONFIG_STATUS Aspen Process Explorer kpi_task.exe References: None
Problem Statement: Why should I avoid to use COA300, 400 and X00s for accountings?
Solution: ACCE uses these COA as heading or title for sub-COA, so some of reports cannot report the cost rightly. We don't recommend to use these COA for specific accumulation costs. Keyword COA, ACCE, Account Keywords: None References: None
Problem Statement: What is the error message "Analysis failed. The correlation matrix is not a Positive Definite matrix." during the risk analysis?
Solution: ACCE uses the Monte-Carlo method which requires Positive definite matrix. If user correlation matrix does not satisfy positive definite, ACCE will give you an error message as above. About the definition of positive definite matrix, please see the below link. https://en.wikipedia.org/wiki/Definiteness_of_a_matrix Attached excel file can be used to check if user correlation satisfies positive matrix, please check the B8 Cell. If it is negative, it means that your correlation does not satisfy the positive definite matrix. Keywords: Risk Analysis, Positive definite, correlation References: None
Problem Statement: How can I delete many tags at once?
Solution: Note: Before executing the query attached to this solution, save a copy of the database to a snapshot that can be used to restore the database in case the query yields unexpected results. Attached to this solution is a query named DeleteTags.txt. Copy the contents of the text file into the Aspen SQLplus Query Writer. This query deletes tags listed in deletetags.txt. This file must be in the InfoPlus.21 Group200 folder. The query assumes the tags to be deleted are defined either by IP_AnalogDef or IP_DiscreteDef. Before deleting a tag, the query tries to delete all references to the tag. If the tag is being scanned from the process, the query turns off the transfer record, deletes the occurrence from the transfer record, and turns on the transfer record after deleting all the tags in the list. This query does not delete any references to the tags in queries, plots, graphics, or AspenCalc calculations. It is the responsibility of the user to delete or modify references external to the Aspen InfoPlus.21 database. Key Words delete tags bulk mass-delete mass delete Keywords: None References: None
Problem Statement: How can I convert UNIX Epoch Time (i.e. number of seconds since 01-JAN-1970) to Aspen InfoPlus.21 format?
Solution: Attached to this solution is a file named UnixEpochTimeToIP21Time.txt. Copy the contents of this file to the Aspen SQLplus query writer and save the query as a record defined by ProcedureDef named UnixEpochTimeToIP21Time. UnixEpochTimeToIP21Time has one calling parameter: UnixEpochTime - Integer UNIX Epoch Time (i.e. number of seconds since 01-JAN-1970) The function returns the equivalent Aspen InfoPlus.21 timestamp. The earliest value for UnixEpochTime that may by passed to the function is 315640800 (02-JAN-1980). Keywords: unix epoch References: None
Problem Statement: How do I clone pure components in Aspen HYSYS?
Solution: Pure components in the HYSYS library can be cloned and the the properties can be modified. For example cloning of pure water can be done to represent salt water in the process. Follow the steps given below to clone a library component: 1. Open the HYSYS case and Enter the properties page 2. Display the components in the component list as shown below and then click on Convert. 4. This will show the list of pure components in left column and hypo components under the hypo components 5. Now select the pure component in the list and then click Convert to Hypo(s) 6. The properties for the cloned components can be modified as required. Keywords: Cloning Pure Components, Hypothetical Components References: None
Problem Statement: How can I display an integer value in Aspen InfoPlus.21 as binary?
Solution: Use the message display format code "UB 32" to display an integer value as binary. Key Words Binary UB32 UB 32 Keywords: None References: None
Problem Statement: How to improve the publishing speed for a large SQL database in APS by cleaning up the publishing tables?
Solution: In V11, there is a new CONFIG keyword that users can set in order to potentially increase the publishing performance. The keyword is SQLSERVER_DELETE_RESULT_TBL_W_TMPTBL. This can be set to Y in table CONFIG. SQLSERVER_DELETE_RESULT_TBL_W_TMPTBL keyword has been added to improve publishing speed when working with SQL where a large number of records are involved. This keyword is used to improve SQL performance when publishing when number of records to delete and re-write are extremely large. For the SQL Database, you must have db_ddladmin rights or the ALTER table rights for the following tables to utilize the keyword. If you do not have these rights, the keyword should be set to N. This keyword affects the following published APS Tables: Tables\No. Records _ZTANKS _ZSTRMS _ZPARAMS _TANKS _PARAMS _STRMS _CRDRUNS By enabling this keyword, it ensures the temp table to copy data to be retained, truncate the existing table and then copy data back to the results table, thus improving the speed of deletion; speed only improves if the data to be deleted is at least 30% of the total data in the table Hence this keyword can be utilized to make improvement in publishing performance when you already have a large number of records existing in the publishing table, and the process of deletion of records in your database is taking a very long time. Keywords: None References: None
Problem Statement: Encountered "Win32 error 1314" message when starting up the Aspen CIM-IO Manager service. Here is the sample error logged in the CIMIO_MSG.LOG file: Logged by CIMIOManager on node xxxx: Win32 error 1314 logging on as xxxx for server xxxx Logged by CIMIOManager on node xxxx: CIMIO_MGMT_SERVER_LOGON, Error logging on as another user WNT Error=1314 A required privilege is not held by the client.
Solution: In order to resolve this issue, the local security policies need to be updated. Specifically, the account used to start CIM-IO Manager need to be added to the Local Policies for: Act as part of the operating system Log on as a batch job Log on as a Service Replace a process level token Go into Control Panel -> Admin Tools -> Local Security Policy, and add the account used to start CIM-IO Manager to the Local Policies => User Rights Assignment in each of above mentioned policies. To add the account to these policies, you would need to click on each of the policies above and go to its Properties area to add the account. For example, right click on Act as part of the operating system => Properties => click on Add Users or Groups => enter domain\user name in the 'Enter the object names to select' field and click OK. Once done, click OK again. Keywords: Error 1069: The service did not start due to a logon failure. References: None
Problem Statement: Having built a report on the Aspen SQLplus reporting website, you set the report format to Excel and test it interactively. Excel file is seen to be created successfully. You find when switching it to be automated, NO Excel file is generated when the report is activated by the trigger event. If you switch the report format back to HTML, a file IS generated when the report is activated by the trigger event. When activated, the automated report causes a signal to be sent to TSK_SQLR external task. The program associated with TSK_SQLR (\AspenTech\InfoPlus.21\db21\code\SQLplusReportScheduler.exe) is clearly running otherwise you would not have seen a file generated when the format was switched back to HTML. Interestingly, (assuming Excel report format is selected again) automated Excel reports will be generated if you stop the TSK_SQLR external task in Aspen InfoPlus.21 Manager but instead run the program in a command prompt window, ie. 1. In Aspen InfoPlus.21 Manager, locate the TSK_SQLR task listed in Running Tasks list 2. Copy the executable path into Windows clipboard (we'll paste it later) 3. Stop the TSK_SQLR task 4. In services.msc, find Aspen InfoPlus.21 Task Service. Note the user account used to run this service 5. Open command prompt window but do so with "Run as different User" and specify the credentials of the account that runs the Aspen InfoPlus.21 Task Service (see item 4) 6. Change Directory to the folder you have copied into clipboard, eg. default would be: CD C:\Program Files\AspenTech\InfoPlus.21\db21\code 7. At the prompt, type the following 2 lines, Set SETCIM_PROCESS_NAME=TSK_SQLR SQLplusReportScheduler.exe This will run the process but it won't return control back to you within the window. Now see what happens with the automated Excel report processing; trigger a new automated Excel report. Expected result: an Excel file ends up in the output file. You can close the command prompt window, start TSK_SQLR task in Aspen InfoPlus.21 Manager and proceed to the solution for a procedure to follow to fix automated Excel reports.
Solution: Non-interactive use of server side office automation can be made to work but certain folders are expected to exist. You need to make some changes to the Aspen InfoPlus.21 server / web server. 1. Use Windows Explorer to create two folders: (replace SysWOW64 with System32 depending on your use of x86 or x64 bit Excel edition) C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache C:\Windows\SysWOW64\config\systemprofile\Desktop 2. Run iisreset.exe from command line (Run as Administrator) 3. Then test the automated report with the Excel format Note, there are numerous discussions regarding this solution to be found across the internet. Keywords: SQLplus Web Report RunReport(): Failed to run the automated report: Incorrect function. RunReport(): Failed to convert to Excel format: The device is not ready. References: None
Problem Statement: In ACCE, how can I know how many piles there are for the building?
Solution: For buildings added, based on its rule, selection of foundation type for building will not affect its cost, this is for information only, so ACCE will not calculate the pile quantities. But user can control pile specification in Area level civil specs form. And then, adding number of piles manually for the building in Building | Options | Civil bulk items. Be sure, the building should be located in above defined Area. Keywords: ACCE, Building, Pile References: None
Problem Statement: Table Settings "FIXBAL" is not working correctly when define in case file and cause reporting problem in Full
Solution: . This is a known issue in PIMS AO and occurring in PIMS V10 CP4. Description: User might want to set FIXBAL in Table Settings for certain case in case file. For this example, define in Case 8. Run the case in AO and check on xmps000008.Xlp file. Row Type shown as LE instead of EQ. We can also notice that solution files Stream Disposition Summary (SDSUM) and Stream Disposition Map (SDMAP) are not generated and also not reported in full solution report. Process Feeds and Process Yields also disappeared from Process Submodel Summary in full solution report. Solution: To turn on FIXBAL at Model Settings>General before running the case. It will solve the FIXBAL issue. 2. To put keyword GENERATE at the case file. It will solve the SDSUM, SDMAP and reporting issue. This issue has been fixed in V11 and going to be fixed in V10 next patch release. Keywords: None References: None
Problem Statement: Which property method should I use, when modeling Sour Water systems in Aspen HYSYS V11.0?
Solution: Aspen HYSYS V11 features a new Sour Water property package, which models the removal of H2S, NH3, and other contaminants from water. Advantages of using Sour Water Property Package are: Rigorous rate-based distillation Enables the modeling of both reaction kinetics & mass transfer Auto-generated Reaction Chemistries Integration with Column Analysis Several useful examples of the sour water stripping process are provided in the Aspen HYSYS | Samples | Sour Water Stripping folder and these can serve as templates for all supported processes. The “Sour PR” or “Sour SRK” is the recommended property package for sour water stripping processes in V10 or prior. Check the KB Artcile below for more details. https://esupport.aspentech.com/S_Article?id=000029080 Keywords: Sour Water, Property Packages References: None
Problem Statement: I notice that my strip chart does not display all the data that should have been stored. Why is this?
Solution: There are three main reasons why the strip chart would not be displaying data that you believe should have been recorded: 1. You have elapsed the maximum number of points available for the logger, i.e. the logger is now 'forgetting' the oldest points. To solve this increase the number of logger points and/or reduce the frequency at which data is being recorded. This is possibly the most common cause. 2. The variable could not be calculated (i.e. it was <empty>) prior to that point. This can occur if the (calculated) variable is not applicable or beyond the numerical range during those points in the simulation run. A value that returns <empty> is not plotted by the strip chart. 3. The variable was only added to the historian at a later point Only from the point that the variable is added to the historian, will it be begin to record data. As such, the program would not have been made 'aware' that such a variable should be recorded. Keywords: strip chart, missing trend, data logger References: None
Problem Statement: License Commuting Troubleshooting Guide
Solution: This article contains a list of KB to help you troubleshoot SLM Commute issues: Getting Error 77 while commuting a license How do I prevent SLM Error 84 when commuting a license? Are administrative privileges required to setup commuting on a client machine? What information should be provided to AspenTech to get Commute or Time fix? (error 75 or 26) Unable to commute a license, error "This is the same machine" What is the purpose of "no-net" on the list of configured SLM Servers in the SLM Configuration Wizard? How do I setup SLM Role-based Commuting? How to limit the maximum number of Tokens can be commuted from SLM License Server Can commuting be disabled on a client machine? Keywords: None References: None
Problem Statement: This knowledge base article describes how to limit the number of days for which a license can be commuted by an end user. The SLM Commute tool can commute the license keys for a maximum of 30 days, but the 30 day limit can be reduced.
Solution: 1. To launch Windows Registry Editor, open Windows start menu and type "regedit" into the search box, and then click the result "regedit" NOTE: To make edits in the registry, you will need Administrative privileges. 2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Aspentech\SLM\Configuration 3. Right click on the the other side of the window pane and create a new String Value called AEAMAXCOMMUTERDAYS 4. Double click and change the value to the number of days you need to limit the commuting and click OK Keywords: SLM Commute, Registry, SLM Tool, SLM, Limit References: None
Problem Statement: How do I configure CIMIOOPCPUTLISTFREQUENCYINSECS for Aspen Cim-IO for OPC when using Aspen DMCplus controllers?
Solution: 1. Shutdown Aspen InfoPlus.21, Aspen DMCplus, or any other Aspen or third-party applications that use Cim-IO. Stop Aspen Cim-IO Manager and Aspen Cim-IO for OPC Interface services. Stop any other third-party services that use Aspen Cim-IO. Stop all Cim-IO processes (e.g. AsyncDlgp) if still running. 2. Decide whether to create or not the registry key and the fictitious scan frequency value that will enable the new behavior for new PUT groups. The following table summarizes all the installation cases in a computer running CIM-IO for OPC, suggesting whether to enable or not the new behavior: CIM-IO OPC-DA Instances DELTA-V Server Other OPC Servers PUT Enable PUT Intensive Frequency Option 1 Yes N/A No No Yes Yes N/A Yes No No Yes No Many Yes Yes No No Yes Yes N/A Yes No No Yes No 3. Create Windows registry key that enables new behavior In order to enable the special behavior that specifies a frequency other than zero for PUT groups, use REGEDIT to create the following Windows registry value of type REG_DWORD: 32bit operating system: HKEY_LOCAL_MACHINE\Software\Aspentech\CIM-IO to OPC Interface\CIMIOOPCPUTLISTFREQUENCYINSECS 64bit operating system: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Aspentech\CIM-IO to OPC Interface\CIMIOOPCPUTLISTFREQUENCYINSECS as shown in the figure below. 4. Enter the desired scan frequency value in seconds. Keep in mind that to make effective a new value for the frequency, the CIM-IO for OPC Interface must be restarted. 5. Reverse the steps in the Pre-configuration section: Start service CIM-IO for OPC Interface, if used Start service Aspen Cim-IO Manager Start any other third-party services shutdown because they use Cim-IO Start InfoPlus.21, Aspen DMCplus or any other Aspen or third-party applications shutdown because they use Cim-IO. [Include instructions as to how to verify the installation of the patch.] 6. Confirm that the new behavior has or not been adopted Open CIMIO_MSG.LOG to see whether the new registry value was either read and implemented or not. Also, if the CIM-IO diagnostic Application Specific option OPCLOG is specified, the diagnostic file will show the frequency specified when adding a new PUT group. In CIMIO_MSG.LOG: Key value defined 25-APR-2019 18:27:44.357, Logged by IP21OPC on node W2K8TIOV731: Detected initial value in CIM-IO to OPC Interface\CIMIOOPCPUTLISTFREQUENCYINSECS, ListID = 1503, transnum = 1132812434, of 30 secs Key value not defined RegQueryValue failed for CIM-IO to OPC Interface\CIMIOOPCPUTLISTFREQUENCYINSECS, ListID = 1503, transnum = 1129816512, assumed 0 secs, [The system cannot find the file specified. ] In CIM-IO_DIAG.LOG: OPCLOG Diagnostic <** 25-APR-2019 19:52:10.362, OPCLOG Diagnostic 10032 by IP21OPC on node W2K8TIOV731: **> >>>OPC AddGroup 1137854439 Completed In 75812(ms). HR = 0x0. Name: W2K8TIOV730_TSK_M_IP21OPC_200_1503, Active: 0, Freq: 30000 Revised Rate: 30000. Keywords: DMCplus PUT WRITE Cim-IO for OPC References: None
Problem Statement: Joule-Thomson-Coefficient-Calculator-with-ACM
Solution: ACM exported model to Aspen Plus to be used for JT coefficient calculation. . User need to install .ATMLZ file to operate the calculation. JT coefficient will be calculated as per the inlet stream information. These files are compatible with V11. Original code in ACM Model JTCOEFF Inlet as input molefractionport; outlet as output molefractionport; Inlet.F=outlet.F; Inlet.Z=outlet.Z; Inlet.T=outlet.T; Inlet.P=outlet.P; Inlet.H=outlet.H; Inlet.V=outlet.V; dx as realvariable(fixed,0.1); T([1:3]) as temperature(inlet.T-10); P([1:3]) as pressure(inlet.P); Z(componentlist) as molefraction; H as enth_mol; JT([1:2]) as realvariable; z=inlet.z; H=inlet.H; For i in [1:3] Do P(i)=Inlet.P+(i-2)*dx; Call (H) = pEnth_Mol(T(i), P(i), Z); Endfor For i in [1:2] Do JT(i)=(T(i+1)-T(i))/(P(i+1)-P(i)); endfor JTCoefficient as realvariable; JTCoefficient=sigma(JT)/2; End Aspen Plus Test Result Keywords: JT, Joule-Thomson, ACM, References: None
Problem Statement: How do I install a license dongle?
Solution: Before connecting the dongle to the USB port, you will need to install the dongle drivers so Windows will detect the dongle. You can either download the dongle driver through the View Attachments link below or install it from the aspenONE media. To install the dongle drivers, follow these steps: 1) You will need to obtain an aspenONE media (Engineering, Manufacturing or APM). 2) Run setup.exe. 3) Click the Install and configure SLM (Software License Manager) software icon from Welcome screen. and then Accept the terms of the agreement to proceed. 4) Expand SLM Tools and check the Dongle Driver checkbox and click Next (make sure to uncheck the SLM License server if this is a standalone license). 5) Proceed through the installer and install the dongle drivers. 6) Once the installation is finished, plug the dongle into the USB port and Windows should automatically detect it. 7) To confirm that the dongle is working, run the SLM Configuration Wizard and click the Config button. If you see Sentinel Hardlock at the top of the Locking Information screen, then the dongle is working. Keywords: SLM Dongle Driver Safenet Sentinel References: None
Problem Statement: Starting Aspen InfoPlus.21 results in loss of recent trend data after applying V11.0 CP1 ("Aspen MES V11 CP1 (V11.0.1) Cumulative Patches - November 2019"). This problem only occurs after applying V11.0 CP1. When historical recordings are made, values are first written to the history repeat area of a tag. From there, the historical recording moves to the memory-resident event queue for the repository. The queue is a FIFO queue containing values for all tags for the repository that need to be written to a file set. The repository’s archiver process sorts the contents of the queue into cache buckets. When the cache bucket fills, the archiver task empties the cache bucket to a file set. A point may be plotted when it is either in a cache bucket or in a file set. When Aspen InfoPlus.21 stops, TSK_H21T saves the contents of the cache buckets for each repository to a file named cache.dat located in the root folder of each repository. When Aspen InfoPlus.21 starts, TSK_DBCLOCK should restore the cache buckets for each repository from cache.dat. This does not happen in v11.0.1, and, as a result, all recordings that were in cache buckets but not yet written to a file set are lost.
Solution: After installing "Aspen MES V11 CP1 (V11.0.1) Cumulative Patches - November 2019 ", you must install "Aspen_InfoPlus21_V11.0.1_ECR_00519220 for InfoPlus.21 V11.0.1 servers (32 or 64 bit)." Key Words Keywords: None References: None
Problem Statement: Why are the ASTM D86 results empty for a gas stream?
Solution: The results of D86 are empty if most compositions in this stream are light end components. In such a case, D86 curve is not applicable to characterize this stream. The D86 curve is converted from TBP curve by API 3A11 method. Users can search this method via API manual. You need the TBP curve in the valid range. In the algorithm, it required 50% TBP >=0 F. Otherwise, it is out of the range of the conversion. For a stream including only a finite set of individual small molecules, distillation curve is not recommended to evaluate the stream properties. Key words ASTM D86, Gas Stream Keywords: None References: None
Problem Statement: A and V frames are usually used for condensing duties where good condensate drainage is obtained. However, they can be used for single-phase cooling where plot area is at a premium.
Solution: When modeling an A or V frame, the following steps need to be followed: - Select the Rating/Checking or the Design calculation mode (Input\Problem Definition\Application Options) - On the Exchanger Geometry|Geometry Summary form for the Exchanger frame type, select 'A or V frame' - Next, in the Fan configuration select the following options according to the frame that wants to be modeled. a) A Frame - Select 'Forced draught' b) V Frame - Select 'Induced draught' - In Exchanger Geometry\Unit Geometry\Unit Geometry tab, enter the Angle of outside flow. This is used to determine the direction of the X-side flow: A value of 0° is vertically upwards, 90° is horizontal and 180° is vertically downwards. A conventional air-cooled heat exchanger usually has the air flowing vertically upwards, and a default value of 0°. A ducted air-conditioning unit will often have air flowing through the coil in the horizontal direction; and the angle is 90°. To define an A-Frame Condenser with an angle of 45° to the horizontal, then set this item to 45°. Then set the Bundle Relative Direction to +90° if you require the tube side flow in the first pass to be upwards or -90° if you require the tube side flow in the first pass to be downwards. Keywords: A and V frame, Air Cooled Exchanger References: None
Problem Statement: Upon installation of Aspen IP.21 Process Browser (formerly Web.21), SUN Java is also installed. After this, systems may get the version of Java updated, and may experience problems when using Aspen InfoPlus.21 Process Browser. How to recover from this?
Solution: Customers have reported various degrees of success when using newer versions of Java in their system, but the recommendation is to always use the one supplied with the product, as this is the only one it was tested on. In all cases, the product installation guide and release notes should always be consulted before an app that relies on a particular version of Java is installed. Unless older versions of Aspen applications are being used, all newer versions are tested with the latest version of Java available at the time the software application was released. Please note that it is also recommended to disable automatic Java updates from Windows | Control Panel | Java application. Keywords: Java Runtime Environment JRE Requirement Java Development Kit JDK References: None
Problem Statement: The functionality of graphics created in the Aspen IP.21 Browser Graphic Studio can be extended through the use of Java Script. Scripting is performed as a result of events, such as the onClick or onEnter event for a button or data field. As long as the syntax rules of Java Script are followed, users can execute scripting added to the Actions tab of any dynamic object in a graphic, as well as scripts associated with the onLoad and onUnload events of an entire graphic. It is possible to add approximately 15,000 characters of scripting in the Actions tab of each object. As such, it may be cumbersome to troubleshoot scripting errors. This solution is intended to share some of the resources available for evaluating and correcting problems related to the Java Script within a graphic.
Solution: JAVA SCRIPT EVALUATION PAGE: A Java Script evaluation page is available in each Aspen Graphic Studio installation. In the C:\Program Files (x86)\AspenTech\Web21GraphicStudio\Tools directory, there is a file called JSEval.htm. If you open this file in Internet Explorer, it offers a window from which you can type (or paste) Java Script and evaluate it for syntax errors. This can be extremely helpful as Java Script syntax is both case-sensitive and somewhat difficult to debug! USING MICROSOFT DEVELOPER TOOLS: The Microsoft DevTools help web developers build and test their websites. To open the DevTools in your browser, press the "F12" key. For example, the Microsoft IE and Edge DevTools include: An Elements panel to edit HTML and CSS, inspect accessibility properties, view event listeners, and set DOM mutation breakpoints A Console to view and filter log messages, inspect JavaScript objects and DOM nodes, and run JavaScript in the context of the selected window or frame A Debugger to step through code, set watches and breakpoints, live edit your code, and inspect your web storage and cookie caches A Network panel to monitor and inspect requests and responses from the network and browser cache A Performance panel to profile the time and system resources required by your site A Memory panel to measure your use of memory resources and compare heap snapshots at different states of code execution An Emulation panel to test your site with different browser profiles, screen resolutions, and GPS location coordinates For more information please visit the following website: https://docs.microsoft.com/en-us/microsoft-edge/devtools-guide Pressing the "F12" key opens a window that prints details about the loading of java applets. If you open a Graphic Studio graphic, you will see debugging information in the console window. Note: To interpret the debug information available through the console, may require the assistance of the support consultants or development team. The easiest way to share this information would be to save the trace output into a file and send this output file to Support. EXAMPLES OF SCRIPTING PROVIDED WITH THE GRAPHIC STUDIO: Examples of scripting in Graphic Studio graphics are available in the Aspen Demo Project, which is installed with the Graphic Studio ( C:\Program Files (x86)\AspenTech\Web21GraphicStudio\Samples ). If you open the AspenDemo.prx file and navigate to the DemoScripts graphic, several scripting samples are available in the Actions tabs of the various objects. REFERENCES: There are many references and examples for Java Script available on the internet. Suggested sites include: JScript user's guide: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/js56jsconjscriptusersguide.asp KeyWords lang=jscript java applet model class file diagnostic Keywords: None References: None
Problem Statement: Animation is a set of graphical states that define how the appearance of an object changes, depending on specified conditions. Aspen IP.21 Browser Graphic Studio allows custom animation schemes to be saved and reused within a project. This Knowledge Base article answers the following question: Where are custom animation schemes saved?
Solution: The schemes are saved in the project file (.prx) located in the C:\Users\<username>\Documents\Web21Graphics directory. Keywords: References: None
Problem Statement: Which System, User, and Application Configuration Files should be Saved, Backed Up, and/or Transferred when Upgrading to the aspenONE V11.0 Release on MES Web Servers on which aspenONE Process Explorer is installed.
Solution: The KB Article content documented below is intended to help you identify the important A1PE (aspenONE Process Explorer) Web Server Installation and/or Application and User Specific Files that need to be Saved and Backed Up during Upgrades, and/or Transferred to the New Server / Client Machines when Migrating to New Hardware during Upgrades, especially for those files located in the AspenTech Installation, Program Files, or User Specific Profile folder locations. In addition to referencing this KB Article for your V11.0 Upgrades, then it is also Highly advised that you Download and Review the Content provided in the V11.0 Product Installation, User, and Configuration Guides, which are posted and made available for Download from AspenTech’s Support Website. And when Reviewing those Product Documents pay close attention to the Chapters and Sections focused on Upgrades including Migrations of the Software from Old to New Machines, as well as any Steps that should be executed and completed Prior to an Upgrade. Important Files to Save, Backup, and/or Transfer when Upgrading A1PE (aspenONE Web-Based Process Explorer) Web Servers: Keywords: None References: None