question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: How to model a distillation column in Hysys
|
Solution: Tips to model a distillation column in Hysys
1. Use the column input expert which guides you through the installation of a column. The input expert is available for standard column templates:
· Absorber
· Liquid-Liquid Extractor
· Reboiled Absorber
· Refluxed Absorber
· Distillation
· Three Phase Distillation
2. The Input Expert contains a series of input pages. Supply the required information before advancing to the next page. When you have worked through all the pages, you will have supplied the basic information required to build the column.
3. Reboiler Pre-configurations:
· Reboiler Once-through: this configuration is available when using the kettle reboiler. The liquid coming from the stage above the reboiler passes through the reboiler once and is returned to the bottom of the column as a mixture of liquid (which goes into the sump, to be drawn as bottom product) and vapor (which goes up to the stage above).
· Reboiler Circulation without baffle: the liquid coming from the stage above the reboiler enters the sump, from which the bottoms and the reboiler feed are both drawn (with same composition). The reboiler product is returned above the sump. Vapor may also be produced when the hot liquid return from the reboiler contacts the liquid in the sump.
· Reboiler Circulation with baffle: The sump is divided into two sections with different compositions. The liquid from above the reboiler enters one section, from which the reboiler feed is drawn. The reboiler liquid product enters the other section, from which the bottoms stream is drawn. Excess reboiler liquid return (above the flow rate of the bottoms stream) overflows into the first section. Vapor from the first section (along with that from the reboiler product) passes up to the stage above.
· Reboiler Circulation with auxiliary baffle: The sump is divided into three sections by a main baffle and an auxiliary baffle. Liquid from the tray above enters the section from which the reboiler feed is drawn. Reboiler return enters above the middle section, overflowing over the main baffle into the section from which the bottoms stream is drawn. Liquid can flow under the auxiliary baffle into or out of the middle section, depending on flow rates. The composition of the middle section is the same as one of the other two sections, depending on the direction of flow. In this configuration, the sump is modeled as two stages, representing the different compositions of the reboiler feed and the bottoms stream.
4. Once all information has been entered via the input expert, user must make sure the number of degree of freedom must be 0. This can be viewed from the Design tab, monitor page. The number degree of freedom determines the number of active specifications required. General guideline:
· Absorber: 0 degree of freedom
- This means active specification is not required
· Liquid-Liquid Extractor: 0 degree of freedom
- This means active specification is not required
· Reboiled Absorber: 1 degree of freedom
- 1 active specification required
· Refluxed Absorber: 1 or 2 degree of freedom
- Total and full reflux require 1 active specification
- Partial condenser requires 2 active specifications
· Distillation: 2 or 3 degree of freedoms
- Total and full reflux require 2 active specifications
- Partial condenser requires 3 active specifications
· Three Phase Distillation: 3 or 4 degree of freedom
- Total and full reflux require 3 active specifications
- Partial condenser requires 4 active specifications
5. Input active specifications must be distributed along the column to achieve column convergence.
Keywords: Distillation column, getting started guide
References: None
|
Problem Statement: You want to remove an Exception Type from Aspen Collaborative Forecasting (CF) Exceptions Tab.
|
Solution: To remove an Exception Type from CF you must first remove it from Aspen Collaborative Demand Manager (DM). In DM navigate to Exception Notification>Define. Highlight the Exception Type you wish to delete. Select Remove. Republish to CF. Open CF and navigate to the Exception Tab. The Exception Type is gone.
Keywords: Exception report
Delete CF report
References: None
|
Problem Statement: Is there a way to lock my HYSYS PFD so that other users can only run the case, but not add or delete operations and streams?
|
Solution: With HYSYS v3.4 and up there is a new tab under the Simulation --> Main Properties menu that can be used to accomplish this.
To lock the flowsheet, simply go to the Simulation menu, select Main Properties, go to the Lock tab, and then enter a password. Once the flowsheet is locked users cannot create or delete objects, or change connectivity. The lock will remain in effect if the case is converted to a template.
Sub-flowsheets located in the main PFD need to be locked individually.
To unlock a locked flowsheet, return to the Lock tab and type in the password. Please be aware that if you forget the password you will not be able to unlock the flowsheet; note also that the password is case sensitive.
Keywords: PFD, flowsheet, lock, password
References: None
|
Problem Statement: Why am I unable to change feed/product locations in my tower?
|
Solution: Structural changes to the column flowsheet (such as changing the feed or product locations) cannot be made while the solver is HOLDING. A message indicating Topological changes cannot be made whilst the solver is in hold mode should appear if changes are attempted while the solver is HOLDING (depending upon your session preferences, this message will appear either in the trace window or as a pop-up dialog box). In order to resolve this problem, activate the solver prior to making the desired changes.
Keywords: error, solver, change, stage, tray, feed, product, location
References: None
|
Problem Statement: What options do I have to modify the appearance of objects in a PFD?
|
Solution: To make a PFD selection look different, you can do the following things:
- Right click on the selection and select Format Label | Change Font (or Change Color) to modify the labels for that selection.
- Activate the PFD Size Mode (select PFD | Select Mode | Size from the main menu) and modify the size of any object in the PFD using the re-sizing arrows.
- Right click on a stream object and select Draw Thick Streamline to increase the thickness of the connecting streamline (right click on the stream object and select Draw Normal Streamline to return to the original appearance).
- Right click on a unit operation object and select Draw Wire Frame to show a wire frame drawing of the PFD icon (right click on the unit operation object and select Draw 3D to return to the original appearance). You can also access various PFD icons for each unit operation by right clicking on the object and selecting Change Icon from the ensuing menu.
- Convert the selection into a subflowsheet and apply a different color scheme in it. To learn more color scheme please visitSolution document # 108771.
Keywords: PFD, color, colour, draw, thick streamline, scheme, wire, frame, font, size
References: None
|
Problem Statement: Does the Aspen HYSYS pipe segment calculate the sonic velocity?
|
Solution: No, HYSYS does not provide the sonic velocity value.
In the Pipe Segment, the 'Check Choked Flow' option can be enabled (Pipe Segment Property View, Design tab, Calculation page). Using this feature, HYSYS checks for choked flow. The flow across the Pipe Segment can be increased until the warning 'Flow is choked', corresponding to sonic velocity, is seen in the Trace Window.Solution 110043 provides more information on this topic.
Alternatively, the Mach Number Unit Operation Extension (Solution 110068) can also be used for any given Pipe Segment or Stream in HYSYS.
Keywords: sonic, velocity, critical, choked, flow, pipe, segment, mach, number.
References: None
|
Problem Statement: You are currently using the Oracle version 10.2.0.4 for your Aspen Collaborative Forecasting (CF) environment. You need to upgrade the current version 10.2.0.4 to 10.2.0.5 since you would be facing a non-compliance issues. Is this version of Oracle supported?
|
Solution: As per the attached Installation guide, as long as you are on Oracle 10.2.x, this will be supported. Aspen CF V7.3 is not supported on Oracle 11g or higher.
Keywords: Oracle 10.2.x, upgrade
References: None
|
Problem Statement: The equivalent length over pipe segment swage is calculated as zero
|
Solution: Aspen HYSYS does not give an equivalent length for swage. It just provides an angle for the pipe segment so the equivalent length is zero.
To model a reducer or enlarger with calculated equivalent length use the User Defined option and provide VH and FT factors.
Keywords: Swage, Equivalent length, Pipe segment
References: None
|
Problem Statement: Aspen Collaborative Demand Manager (CDM) is often used along with Aspen Collaborative Forecasting (CF), to allow users who do not have access to CDM to enter overrides using the CF web interface. These overrides would require the approval of the CDM user, before being entered to the model and the data. CF application allows users to enter overrides at different pre-configured override levels. This
|
Solution: explains how to configure these override levels.
Solution
The following steps guides you through this process:
1. Backup your CDM case file for just-in-case reasons
2. Backup your CF Database for just-in-case reasons. Usually, these backups are done by the Database Administrator of your group.
3. Open the CDM Case file
4. Hit F3 on your keyboard
5. Type in: CFOCLC. Except for the first 2 entries OCL and ATTTYPE, the rest of the attributes have been configured to appear in CF and can be used for overrides.
6. Hit F3 and type in: CFOCLR
7. Scroll down and add 2 new entries and fill in the Code column with sequential numbers
8. For example, if you want to add a new override level of Location-End Customer-Marketing Material and if you already have 98 other entries in CFOCLR, you would fill the entries as:
Code
Description
99
Loc-EndCust-MarMat
100
Loc-EndCust-MarMat
9. Close this window and choose Yes when asked whether to Apply changes
10. Hit F3 and type in: CFOCL. This table shows the current override levels available for usage. If there is an override level already available that you are interested to use, go to step: 14.
11. Scroll to the end, you would find the two empty rows that you just added. For the Location-End Customer-Marketing Material override level, fill these rows as:
OCL
ATTTYPE
ATT3
ATT18
ATT17
ATT9
ATT10
ATT2
ATT24
ATT1
ATT11
ATT5
ATT8
PRO
REP
ATT4
ATT7
ATT6
LOC
ATT5B
ATT19
CLASS
FABLE
CUST
Loc-EndCust-MarMat
CONTENT
N
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
N
Y
N
N
N
N
Y
Loc-EndCust-MarMat
FILTER
N
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
N
Y
N
N
N
N
Y
*You are free to choose the appropriate attributes as filters. In order to see descriptions in the column headers instead of Code, you can right click on the CFOCL table and choose Table Attributes; there should be a Decode under Colset - choose Description in this drop-down menu instead of Code.
12. Close this window and choose Yes when asked whether to Apply changes
13. Now, go to Run Action | Collaborative Forecasting | Publish / Re-Publish option depending on where you are in your forecasting cycle
14. Open Internet Explorer
15. Login to the CF Admin page
16. Choose the Roles tab
17. Check the Roles you want to make this override levels available to. Click on the Edit button.
18. In the Override Levels section, you would find the new override at the bottom. Press the Ctrl key and select the new override level in the list box and click Apply button.
19. Open CF (as one of the roles which you added the new override to) and check whether the changes have been applied. Also, check the data and confirm that everything is correct.
Keywords: None
References: None
|
Problem Statement: I get Windows Installer Error 1605 during the installation of my application. What do I do?
|
Solution: When this error occurs, it prevents a setup from being removed from the system. First, you must remove the setup from the machine, and then you need to change the value of the REINSTALLMODE property.
Go to Installer folder found in the Windows directory. For example, on WinNT/2000 machines this location is C:\WinNT\Installer.
Find the cached .msi file for the setup that was just installed. This .msi file is renamed by Microsoft with a random name, such as a1b23.msi; therefore, an additional step must to be taken to locate the specific package. You can determine which .msi belongs to your setup by right-clicking the .msi and going to the Summary tab and verifying the Subject and Author field. Once the MSI file is found, delete and rerun the setup.
You must now change the value of REINSTALLMODE. The REINSTALLMODE property can be set a few different ways. It can be set in the Property Manager, in InstallScript, by a Custom Action, or in Setup.ini. Determine the method you are using to set the REINSTALLMODE property and follow the appropriate steps below to change its value.
Property Manager
Open the Property Manager view of the InstallShield Development Environment (IDE).
Find REINSTALLMODE and set its value to a value, such as amus, omus, vam, etc. It cannot be set to a single-file code option letter. The default value of REINSTALLMODE is omus.
Custom Action
Open to the Custom Actions view of the IDE.
Search through the custom actions available, clicking each one. If the custom action is of type Set a Property, the Property Name property should say REINSTALLMODE and the Property Value property is a sequence of options codes. The Property Value property should be changed in this case to a value, such as amus, omus, vam, etc. It cannot be set to a single-file code option letter.
InstallScript
Go to the InstallScript section of the IDE.
In the script editor, type CTRL+F and do a search for REINSTALLMODE.
If a value is found, it will probably be a parameter being passed to a MSIfunction called MsiSetProperty. Change the value being passed to this function so the REINSTALLMODE property will be set to a New code option such as amus, omus, vam, etc. It just cannot be set to a single-file code option letter.
Setup.ini
If you are using a uncompressed release, the setup.ini will be found in your release folder. The release folder can easily be opened by going to Tools > Open Release Folder in the IDE.
Open the setup.ini in Notepad and check the [STARTUP] section. There will be a line CmdLine = . If REINSTALLMODE is listed to the right, change its value to a New code option, such as amus, omus, vam, etc. It cannot be set to a single-file code option letter
Note: If you are using a compressed release in which the setup.ini is embedded into a setup.exe, see InstallShield Knowledge Base article Q107253 HOWTO: Modifying a Setup.ini That Is Embedded in Setup.exe or Update.exe.
For more information regarding this error, please refer to the following website: http://support.installshield.com/error_central/
Keywords: Windows Installer Error 1605; Error 1605; Installation Error
References: None
|
Problem Statement: There is no button or menu option to cancel/undo a data or graphical entry in HYSYS.
|
Solution: Save frequently and rebuild manually.
Keywords: Undo, Cancel, Delete, Button, Option, Menu, Tool, Command, Short-cut, Key, Ctrl.
References: None
|
Problem Statement: Can I access Compressor results (including head factor and exponents) via Automation?
|
Solution: Currently the Compressor object (CompressOp in the HYSYS type library) does not have properties for all the results that are available in the interface. However these properties can be accessed via Backdoor variables. In this method the internal monikers (pointers to the information) are used to access the variables.
The attached Excel example includes code to retrieve all the results that are available in the interface.
NB Backdoor methods are only recommended when there is no other alternative, the internal HYSYS monikers may not remain constant between versions so care should be exercised when upgrading. The code was tested with HYSYS 3.2.
Saved with a HYSYS 3.2 Type Library reference - For troubleshooting advice on common HYSYS / OLE Automation errors see KnowledgebaseSolution #112361.
Note
The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use these examples. We invite any feedback through the normal support channel at [email protected].
Keywords: Compressor, polytropic head factor, polytropic exponent, isentropic exponent
References: None
|
Problem Statement: How to define new components in FeedFuel block in Aspen Utilities Planner V8.0?
|
Solution: User can add new components to the Fuel component list so they can be used to define the fuel composition.
To add new components,
1. Display Explorer in Aspen Utilities Planner V8.0
2. Double click Configure Properties to bring up Build Component List - Fuel form
3. Once Aspen properties V8.0 is launched, navigate to Components>Specifications form to add new components.
4. Click Methods>Parameters>Binary Interaction form so the parameters are updated and the status is changed to Input Changed.
5. Run Aspen Properties to complete calculation
6. Exit Aspen Properties. Click Yes when prompted to Save changes to PropsPlus.aprbkp file.
7. Click OK button to dismiss Physical Properties Configuration dialog.
8. Double click Fuel component list to add the newly defined components to the list. Click OK button to dismiss the dialog.
9. Add a FeedFuel block to the flowsheet and double click on the block. Noticed that the newly defined components should appears in the list.
Keywords: component,feedfuel
References: None
|
Problem Statement: How do I specify the relative humidity for a stream in Aspen HYSYS?
|
Solution: Presently, relative humidity is not specified in Aspen HYSYS. However, please review the attached workaround.
The attached Aspen HYSYS simulation does the calculation. Basically, our standard saturate method is used, adding water to a gas stream until a small amount is knocked out. The relative humidity is input in the spreadsheet and the excess water is removed using a component splitter.
Alternatively, you can use the saturate extension (Solution ID#110073). This one operation will replace all of the operations in the attached case. With this operation, you can set the relative humidity of the outlet stream directly.
Keywords: Relative Humidity
References: None
|
Problem Statement: The Workbook is configured such that the stream compositions are displayed, but the compositions disappear when the Include Sub-Flowsheets button is clicked.
|
Solution: The composition of all streams will only be displayed if all sub-flowsheets in the case use the same Fluid Package. The fluid packages for sub-flowsheets are set in the Basis Environment on the Simulation Basis Manager\Fluid Pkgs tab.
Keywords: workbook, subflowsheet, sub-flowsheet, compositions
References: None
|
Problem Statement: How may I use Excel VBA to automate a series of runs of my HYSYS model and retrieve results for each run?
|
Solution: The attached HYSYS 3.1 case is a simple model of a compressor with curves enabled. The attached spreadsheet allows the user to enter a series of feed temperatures, pressures and flows. These are then sent to the HYSYS model and, for each set of input data, a set of results is extracted from HYSYS and reported on the spreadsheet.
For troubleshooting advice on common HYSYS / OLE Automation errors seeSolution #112361.
Note
The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use these examples. We invite any feedback through the normal support channel at [email protected].
Keywords: Automate Batch runs
References: None
|
Problem Statement: Automation example - Access to PIPESYS extension
|
Solution: The attached Excel spreadsheet illustrates how to obtain details of the piping geometry and results from the PIPESYS extension.
Saved with a HYSYS 3.2 Type Library reference - For troubleshooting advice on common HYSYS / OLE Automation errors see KnowledgebaseSolution #112361.
Note
The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use these examples. We invite any feedback through the normal support channel at [email protected].
Keywords: PIPESYS, Backdoor
References: None
|
Problem Statement: Access HYSYS PFD via Automation, Creates a sketch copy of the HYSYS PFD in Excel
|
Solution: The attached Excel spreadsheet includes VBA code that creates a sketch copy of the current HYSYS PFD on the Excel spreadsheet. This illustrates access to the various PFD objects within HYSYS.
For an introduction to accessing PFD objects via Automation seeSolution ID # 112354.
For details of some common errors that can occur when linking Excel to HYSYS via VBA, and how to resolve them seeSolution ID # 112361.
Note: This Automation application has been created by AspenTech as an example of what can be achieved through the object architecture of HYSYS. This application is provided for academic purposes only and as such is not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading and using, agree to assume all risk related to the use of this example. We invite any feedback through the normal support channel at [email protected].
Keywords: Automation, PFD, PFDItems, PFDItem
References: None
|
Problem Statement: Why can't I find the input page where nozzle elevation parameters are entered?
|
Solution: For HYSYS 2.4.1. & HYSYS 3.0.1
Go to Simulation --> Main Properties --> Licenses page --> Activate HYSYS Plant+ option
For HYSYS 3.1 and later
Go to Simulation --> Main Properties --> Licenses page --> Activate HYSYS Fidelity option
Keywords: Fidelity, Elevation, Nozzle
References: None
|
Problem Statement: Can I install and run the Collaborative Forecasting Web application on IBM WebSphere Application Server?
|
Solution: IBM WebSphere Application Server is not supported at all at this time.
Collaborative Forecasting Web Application only can be installed and run with the BEA Weblogic Server.
Keywords: IBM
Websphere
Application Server
References: None
|
Problem Statement: Aspen Collaborative Forecasting (CF) Trigger is not compiling after upgrading to V7.1.
|
Solution: The CF Trigger functionality is not being used in V71.
If you receive an error message that is similar to this, CREATE OR REPLACE TRIGGER cf_instance_parameters_id_gen, you can ignore it during your upgrade; it will not impact V7.1.
The CF_instance_parameters.sql table script has been updated in V7.2 eliminating this error.
Keywords: CF_TRIGGER
Compile
CF_Instance_parameters_ID_GEN
Collaborative Forecasting
References: None
|
Problem Statement: Why I am getting a temperature rise in a pipe?
I have a pipe that is loosing heat to the surroundings. Yet I observe a temperature rise. How is it possible?
|
Solution: Temperature can fall or rise in a pipe depending on pressure drop. Temperature rise can take place due to Joule-Thompson effect. To test whether the pipe segment or pipesys pipe is predicting a temperature rise correctly or not you can use a valve, connect a copied stream (copy from pipe's inlet) and put the same pressure drop as in the pipe(s). If you observe a temperature rise across the valve you can be sure that the temperature rise in the pipe is normal. If you have heat loss from the pipe, you will observe a higher temperature rise in the valve.
Keywords: Pipe, pipesys, temperature rise, temperature, rise
References: None
|
Problem Statement: Where can I find the freezing point for a stream?
|
Solution: Unfortunately, Aspen HYSYS is not a solid-liquid equilibrium simulator and therefore it cannot predict the freezing point of any substance. Freezing point calculations require pure component properties such as melting points and solid heat capacities which are not included in our database. It is only prepared to perform vapor-liquid, liquid-liquid or three phase equilibria. The only exceptions to this are the prediction of solid hydrate formation in natural gas and CO2 solids formation which are done via the Hydrate Formation and CO2 Freeze Out utilities, respectively.
Keywords: freezing point, solids, VLE, LLE, SLE, VLLE
References: None
|
Problem Statement: Why does my Automation code fail when I try to manipulate PFD items or read the extent of the PFD?
|
Solution: This is likely to be because the PFD window in HYSYS is not open.
Any code that tries to manipulate HYSYS PFD items, e.g.:
[PfdItem Object].XPosition = [PfdItem Object].XPosition + 100
or
[PfdItem Object].Hidden = True
will fail if the HYSYS PFD window is not open. Here [PfdItem Object] represents a valid object for an item on the PFD. Additionally the Extent property of the PFD is Empty if the PFD is not open, so attempting to read any values from it will also give an error.
The way around this is to use a backdoor message method to ensure the PFD is open. Backdoor methods are only recommended when there is no other alternative; the internal HYSYS monikers may not remain constant between versions so care should be exercised when upgrading. The code here has been tested with HYSYS 3.0.1, 3.1 and 3.2.
The following Excel VBA code tests to see whether the PFD is already open (by checking whether it's Extent property contains any data) and then opens it with a backdoor method if required.
Sub CheckPFDIsOpen()
'HYSYS Type Library reference required
Dim hyApp As HYSYS.Application
Dim hyFlowSht As HYSYS.Flowsheet
Dim hyCase As HYSYS.SimulationCase
Dim hyPfd As HYSYS.PFD
Dim hyBD As HYSYS.BackDoor 'Must be declared as type Backdoor, Object won't do
Dim varPFDExtent As Variant
'Link to objects
Set hyApp = GetObject(, HYSYS.Application)
Set hyCase = hyApp.ActiveDocument
Set hyFlowSht = hyCase.Flowsheet
Set hyPfd = hyFlowSht.PFDs.ActivePFD
'Get size of HYSYS PFD
varPFDExtent = hyPfd.Extent
'If the PFD window is not open in HYSYS then varPFDExtent is Empty
If TypeName(varPFDExtent) = Empty Then
'Use a backdoor workaround to open the PFD
Set hyBD = hyFlowSht
hyBD.SendBackDoorMessage CreatePFDAndView
End If
End Sub
For an introduction to accessing PFD objects via Automation seeSolution ID # 112354. For an Excel example file that creates a sketch copy of the current HYSYS PFD on the Excel spreadsheet seeSolution ID# 112355.
Keywords: Automation, PFD, PFDItem, Extent, Backdoor
References: None
|
Problem Statement: Where can I find the DM and Aspen Collaborative Forecasting logs to submit to Aspen Support?
|
Solution: By default, The DM log files located at the following folder C:\CF\cf_integ\dm\log and CF log files located at the following bellow folder C:\bea\user_projects\domains\AspenCF\logs
Keywords: None
References: None
|
Problem Statement: HYSYS extensions are built from a compiled COM dll and an Extension Definition File (EDF). If you have developed your HYSYS extension as a .NET object you will need to add COM Interoperability to your .NET assembly dll file in order for the extension to be registered and work properly.
|
Solution: There are several ways to add COM interoperability to your .NET assemblies depending on the development tools you have available. Below are listed the most common ways for the most common development tools.
Adding COM interoperability to .NET assemblies from Microsoft Visual Studio (all versions)
Open your HYSYS extensionSolution in MS Visual Studio.
Right-Click your extension project in theSolution explorer and select project properties.
In the project property pages set to 'true' the following build switch value:
Configuration Properties | Build | Register for COM Interop
Adding COM interoperability to .NET assemblies from the command prompt (regasm.exe)
There is a command prompt tool which comes with the .NET Framework SDK that will allow COM clients to create .NET classes from your assembly.
The tool is regasm.exe and it's located in one of the following directories depending on the .NET Framework version you have installed:
C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
To register your .NET dll as a COM server, type this command:
regasm.exe myNETextension.dll
More usage information about this tool can be found in the following MSDN link:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpgrfassemblyregistrationtoolregasmexe.asp
Keywords: .NET, COM, assembly, register, extension, regasm.exe
References: None
|
Problem Statement: How can I check that Aspen HYSYS is representing my Crude Assay well enough?
|
Solution: Aspen HYSYS does all calculations on a TBP basis in the Oil Manager. Aspen HYSYS Oil Manager uses an algorithm to convert any input assay data (D86/D1160/D2887) to TBP data.Go through the following procedure to compare crude assay given by you and that calculated by Aspen HYSYS:
1. Specify an oil assay of any type such as D86/D1160/D2887.
2. Cut this assay using the options given on page Simulation Basis Manager|Oil Manager|Enter Oil Environment|Cut/Blend|View|Data|Cut Option Selection. There are three options: (a) Auto Cut (b) User Ranges (c) User points. Note that option (b) works with respect to TBP temperature range.
3. Go to Simulation Basis Manager|Oil Manager|Enter Oil Environment|Cut/Blend|View Composite plot. The composite plot will show the oil assay curve information given by you and calculated by Aspen HYSYS. This will give you a graphical representation of the deviation in these two.
4. If you see a major deviation, it may be reduced by changing options at Simulation Basis Manager|Oil Manager|Enter Oil Environment|Assay|View|Calculation Defaults. For further details on Calculation Options, please refer to Knowledge baseSolution #109360.
For more information on the Oil Manager, please refer to the Simulation Basis Manager manual (Chapter 4, page 202) at Knowledge baseSolution #117413.
Keywords: ASTM, D86, D1160, D2887, TBP, Composite Plot, Crude Assay
References: None
|
Problem Statement: Can I set both pressure and flow specifications for a feed stream in Dynamics?
|
Solution: Technically both pressure and flow specs can be activated on a feed stream, although this is likely to cause the model to be over specified. Usually for a feed stream connected to a valve (or other resistance operation like a heater or cooler) then a pressure spec is used; otherwise a flow spec would be used.
One way to specify both the flow and pressure of a feed stream connected to a valve is to disable the pressure flow relationship of the valve (On the Dynamics ... Specs page). In general this method isn''t recommended, since with both flow and pressure fixed then the flow is no longer driven by a pressure gradient so if, for example, a downstream valve is closed you can get unrealistically high pressures as flow will still be forced into the closed valve. If this method is used it is recommended to add some form of protection to the model to help avoid situations where the constant flow may cause problems (e.g. using a spreadsheet to reduce the flow specification or having a bypass valve to throw away material).
A better approach is often to have a feed stream with a pressure spec and then a fairly large valve (which may not exist in the plant and is sized to give minimal pressure drop) and a controller to give the desired flow into the system. The pressure spec on the feed stream will give you the constant pressure and the valve and flow controller will allow you to set the flow going into the system. In this scenario if you close off actual downstream valves, the flow entering the system will be stopped (because of pressure gradients) without having to resort to spreadsheets or bypass valves.
Keywords: Boundary Stream Specs, Specifications, Pressure, Flow, Valve
References: None
|
Problem Statement: I would like to run Aspen Collaborative Forecasting on a 64 bit server. However, Aspen Collaborative Forecasting is a 32 bit application. What is the memory limitation for doing so?
|
Solution: Memory Limits for Windows Releases
This topic describes memory limits for supported Windows releases:
Memory and Address Space Limits
Physical Memory Limits: Windows 7
Physical Memory Limits: Windows Server 2008 R2
Physical Memory Limits: Windows Server 2008
Physical Memory Limits: Windows Vista
Physical Memory Limits: Windows Home Server
Physical Memory Limits: Windows Server 2003 R2
Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)
Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)
Physical Memory Limits: Windows Server 2003
Physical Memory Limits: Windows XP
Physical Memory Limits: Windows 2000
Physical Memory Limits: Windows Embedded
How graphics cards and other devices affect memory limits
Related Topics
Limits on memory and address space vary by platform, operating system, and by whether the IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.
4-gigabyte tuning (4GT), also known as application memory tuning, or the /3GB switch, is a technology (only applicable to 32 bit systems) that alters the amount of virtual address space available to user mode applications. Enabling this technology reduces the overall size of the system virtual address space and therefore system resource maximums. For more information, see What is 4GT.
Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.
Memory and Address Space Limits
The following table specifies the limits on memory and address space for supported releases of Windows. Unless otherwise noted, the limits in this table apply to all supported releases.
Memory type Limit in on X86 Limit in 64-bit Windows
User-mode virtual address space for each 32-bit process
2 GB
Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default)
4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
User-mode virtual address space for each 64-bit process
Not applicable
With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default):
x64: 8 TB
Intel IPF: 7 TB
2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
Kernel-mode virtual address space
2 GB
From 1 GB to a maximum of 2 GB with 4GT
8 TB
Paged pool
Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value.
Windows Vista and above: Limited only by kernel mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value.
Windows Home Server and Windows Server 2003: 530 MB
Windows XP: 490 MB
Windows 2000: 350 MB
128 GB
Windows Server 2003 and Windows XP: Up to 128 GB depending on configuration and RAM.
Windows 2000: Not applicable
Nonpaged pool
Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory.
Windows Vista: Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value.
Windows Home Server, Windows Server 2003, and Windows XP/2000: 256 MB, or 128 MB with 4GT.
75% of RAM up to a maximum of 128 GB
Windows Vista: 40% of RAM up to a maximum of 128 GB.
Windows Server 2003 and Windows XP: Up to 128 GB depending on configuration and RAM.
Windows 2000: Not applicable
System cache virtual address space (physical size limited only by physical memory)
Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.
Windows Vista: Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value.
Windows Home Server, Windows Server 2003, and Windows XP/2000: 860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.
Always 1 TB regardless of physical RAM
Windows Server 2003 and Windows XP: Up to 1 TB depending on configuration and RAM.
Windows 2000: Not applicable
Physical Memory Limits: Windows 7
The following table specifies the limits on physical memory for Windows 7.
Version Limit on X86 Limit on X64
Windows 7 Ultimate
4 GB
192 GB
Windows 7 Enterprise
4 GB
192 GB
Windows 7 Professional
4 GB
192 GB
Windows 7 Home Premium
4 GB
16 GB
Windows 7 Home Basic
4 GB
8 GB
Windows 7 Starter
2 GB
2 GB
Physical Memory Limits: Windows Server 2008 R2
The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.
Version Limit on X64 Limit on IA64
Windows Server 2008 R2 Datacenter
2 TB
Windows Server 2008 R2 Enterprise
2 TB
Windows Server 2008 R2 for Itanium-Based Systems
2 TB
Windows Server 2008 R2 Foundation
8 GB
Windows Server 2008 R2 Standard
32 GB
Windows HPC Server 2008 R2
128 GB
Windows Web Server 2008 R2
32 GB
Physical Memory Limits: Windows Server 2008
The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.
Version Limit on X86 Limit on X64 Limit on IA64
Windows Server 2008 Datacenter
64 GB
1 TB
Windows Server 2008 Enterprise
64 GB
1 TB
Windows Server 2008 HPC Edition
128 GB
Windows Server 2008 Standard
4 GB
32 GB
Windows Server 2008 for Itanium-Based Systems
2 TB
Windows Small Business Server 2008
4 GB
32 GB
Windows Web Server 2008
4 GB
32 GB
Physical Memory Limits: Windows Vista
The following table specifies the limits on physical memory for Windows Vista.
Version Limit on X86 Limit on X64
Windows Vista Ultimate
4 GB
128 GB
Windows Vista Enterprise
4 GB
128 GB
Windows Vista Business
4 GB
128 GB
Windows Vista Home Premium
4 GB
16 GB
Windows Vista Home Basic
4 GB
8 GB
Windows Vista Starter
1 GB
Physical Memory Limits: Windows Home Server
Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.
Physical Memory Limits: Windows Server 2003 R2
The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version Limit on X86 Limit on X64
Windows Server 2003 R2 Datacenter Edition
64 GB
(16 GB with 4GT)
1 TB
Windows Server 2003 R2 Enterprise Edition
64 GB
(16 GB with 4GT)
1 TB
Windows Server 2003 R2 Standard Edition
4 GB
32 GB
Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)
The following table specifies the limits on physical memory for Windows Server 2003 with SP2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version Limit on X86 Limit on X64 Limit on IA64
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition
64 GB
(16 GB with 4GT)
1 TB
2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition
64 GB
1 TB
2 TB
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition
4 GB
32 GB
Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)
The following table specifies the limits on physical memory for Windows Server 2003 with SP1. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version Limit on X86 Limit on X64 Limit on IA64
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition
64 GB
(16 GB with 4GT)
X64 1 TB
1 TB
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition
64 GB
(16 GB with 4GT)
X64 1 TB
1 TB
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition
4 GB
32 GB
Physical Memory Limits: Windows Server 2003
The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.
Version Limit on X86 Limit on IA64
Windows Server 2003, Datacenter Edition
64 GB
(16 GB with 4GT)
512 GB
Windows Server 2003, Enterprise Edition
64 GB
(16 GB with 4GT)
512 GB
Windows Server 2003, Standard Edition
4 GB
Windows Server 2003, Web Edition
2 GB
Windows Small Business Server 2003
4 GB
Windows Compute Cluster Server 2003
32 GB
Windows Storage Server 2003, Enterprise Edition
8 GB
Windows Storage Server 2003
4 GB
Physical Memory Limits: Windows XP
The following table specifies the limits on physical memory for Windows XP.
Version Limit on X86 Limit on X64 Limit on IA64
Windows XP
4 GB
128 GB
128 GB (not supported)
Windows XP Starter Edition
512 MB
Physical Memory Limits: Windows 2000
The following table specifies the limits on physical memory for Windows 2000.
Version Limit on X86
Windows 2000 Professional
4 GB
Windows 2000 Server
4 GB
Windows 2000 Advanced Server
8 GB
Windows 2000 Datacenter Server
32 GB
Physical Memory Limits: Windows Embedded
The following table specifies the limits on physical memory for Windows Embedded.
Version Limit on X86 Limit on X64
Windows XP Embedded
4 GB
Windows Embedded Standard 2009
4 GB
Windows Embedded Standard 7
4 GB
192 GB
How graphics cards and other devices affect memory limits
Devices have to map their memory below 4 GB for compatibility with non-PAE-aware Windows releases. Therefore, if the system has 4GB of RAM, some of it is either disabled or is remapped above 4GB by the BIOS. If the memory is remapped, X64 Windows can use this memory. X86 client versions of Windows don?t support physical memory above the 4GB mark, so they can?t access these remapped regions. Any X64 Windows or X86 Server release can.
X86 client versions with PAE enabled do have a usable 37-bit (128 GB) physical address space. The limit that these versions impose is the highest permitted physical RAM address, not the size of the IO space. That means PAE-aware drivers can actually use physical space above 4 GB if they want. For example, drivers could map the ?lost? memory regions located above 4 GB and expose this memory as a RAM disk.
Keywords: None
References: None
|
Problem Statement: What is the Ref. Temperature in an Energy Stream?
|
Solution: The Ref. Temperature in an Energy Stream is not used by HYSYS and will always show <empty>. This field was intended for use with some functionality which was not implemented.
Keywords: Energy Stream, reference temperature, ref.
References: None
|
Problem Statement: How can I obtain elements of a RealFlexVariable as RealVariables? (Examples: Setting Tee splits, Column Stage Pressures)
|
Solution: Normally it is only required to be able to set all the elements in a RealFlexVariable. E.g. when setting the component compositions in a stream. This is achieved by using the SetValues method and is covered in more detail inSolution #108949.
Occasionally it is necessary to set only certain values within an array of values. For example: when setting Tee Splits or column stage pressures.
This can be accomplished by using the Variables property of the RealFlexVariable class to obtain a variant array of RealVariable objects for each of the elements within the RealFlexVariable, and then setting a value into one of these objects.
This is illustrated in the VBA code below. This code links to a Tee and sets one of the split fractions. To use the code open up HYSYS with any suitable case (the attached case 'EgToUseToSetTeeSplits.hsc' (saved in HYSYS 3.0.1) will work), paste the code into the VBA editor in Excel, make a reference to the HYSYS type library (Tools ...
Keywords: None
References: s menu option in the VBA editor) and run the procedure.
Sub SetTeeSplits()
'Description: Example of obtaining a RealVariable object for an element within a RealFlexVarible
'Declare Variables
|
Problem Statement: Is it possible to generate an input summary using Aspen HYSYS?
|
Solution: New in Aspen HYSYS 2006.5, an Input Summary was added to the HYSYS Flowsheet Summary form (i.e. select Flowsheet | Flowsheet Summary | Input Summary from the HYSYS main menu). Alternatively, the Input Summary can be generated by selecting Simulation | View XML from the main menu, and then activating the Input Summary button.
The Input Summary form provides a break down of all the user supplied values in the HYSYS flowsheet (i.e. this summary does not include any unit operation default values or values calculated by HYSYS when solving the flowsheet).
Keywords: input, summary, file, XML, flowsheet
References: None
|
Problem Statement: After changing the password for the IIS service account user, Upload of overrides are failing in Aspen Collaborative Forecasting (CF). How is this corrected?
|
Solution: You should review the IIS log files first. Most likely you will see multiple 401 error messages in the logs, IIS log file clearly indicates that domain\\user name, password combination in proxy.properties file not valid (Error 401 means unauthorized login failed). You then need to perform the following actions to make Offline Override functionality to work in CF.
In proxy.properties file client needs to re-fill the following entries:
PROXY_PW=valid password
PROXY_LOGIN= domain\\user name (Make sure that you are using proper domain name followed by two backward slashes and user name)
ENC=N
After making the above change client needs to stop IIS and re-start IIS first and stop and re-start Weblogic as next in sequence.
Note: user should be an administrator and have sufficient privileges with domain account; once user performs Offline Overrides after the above changes; next sub-sequent logins; user information would be validated against caching.
Keywords: None
References: None
|
Problem Statement: Is the Tacite pressure drop correlation still available in Aspen HYSYS? I can no longer find in among the list of pressure drop correlations in the pipe segment.
|
Solution: As of Aspen HYSYS 2006, the Tacite Hydrodynamic Module is no longer available in the pipe segment operation. When loading older cases that contain this correlation, the following error message may appear:
After acknowledging the above warning, the simulation case will load without further incident, but will use the Beggs and Brill correlation in place of the Tacite Hydrodynamic Module.
Note that when loading cases that contain more than one instance of the Tacite pressure drop correlation, a separate warning message will appear for each. In these situations, it may be preferable to activate the Send further recall error messages to the trace window checkbox (shown above) in order to avoid acknowledging each error individually.
Keywords: wax, deposition, pipe, segment, ProFES
References: None
|
Problem Statement: Server Error when the Create Override functionality is filtered by Legal entity and Business unit in the Collaborative Forecasting
|
Solution: Reason for the error, Collaborative Forecasting offline loading may take a long time if the file is large or data volume is high. The default transaction timeout in Weblogic server is 30 seconds and it is recommended to change this to 90 seconds or more.
To do this please follow the below Procedure
1. Login to Weblogic Administration tool:
http://<yourHost>:<yourPort>/console
Login/password is as what you saved when you created the domain. This has nothing to do with CF.
2. In the admin page, on the left navigation panel, click: services ->JTA, and the transaction timeout is shown as follows:
Change the value in seconds and Apply. This setting is saved persistently, after that you need to restart the Collaborative Forecasting web application using Windows service.
Keywords: Server Error
Transaction timeout
JTA
Create override
Collaborative Forecasting
Weblogic
References: None
|
Problem Statement: Data Chart failing to display when user clicks Display Chart(s) icon.
|
Solution: Make sure you select the check box in the Chart column before you select the Display Chart(s) icon.
Failure to select the check box will result in an error.
Keywords: Collaborative Forecasting
Chart
References: None
|
Problem Statement: This knowledge base article describes the steps to install bridge libraries into SCM.
|
Solution: 1. Open the case into which you will install the Bridge Libraries.
2. From the Navigation Pane, click Modeling | Tools | Library Manager.
3. In the SCM Ribbon, do one of the following:
Under the Home tab, click Properties or
Under Data tab, click Properties.
The Properties Panel opens.
Note: Review which Libraries are already linked, as this will let you know which Bridge Libraries to install.
4. Install the Bridge Library corresponding to the SCM Application.
For example, install DMB_VX-Y into Demand Manager.
5. In File Explorer, locate the file and paste its file path, including the file name, into the Properties
Panel’s Add/Upgrade Libraries section.
6. Click Add/Upgrade.
7. In the Properties Panel’s Library Status section, click the newly added library in the Linked Library
list to select it. A single available feature should appear in the list below the Linked Library list.
8. Select that feature, and then click Re/Install.
9. Install the Shared Library Bridge (SHB_VX-Y.CAS).
Each feature corresponds to a library. For example, the General Methods Feature corresponds with
the General Methods Library.
10. In the Properties Panel, do the following:
Select the features that correspond with the libraries noted in step 4.
Check the version number of the feature.
If any selected feature has a version number in which the final six digits are all 0 (ex. X.Y.000.000),
deselect that feature.
Because no fixes have been made against that feature, it isn’t necessary to install it.
Note: An error message will appear at the end of your installation if you try to install these features.
However, because nothing is being installed from these features, you can ignore the error message.
11. Click Re/Install to reinstall the selected features.
Keywords: None
References: None
|
Problem Statement: This knowledge base article gives an overview of Macros in SCM.
|
Solution: What is a Macro?
A macro in SCM is a user defined procedure that contains a set of instructions to perform a particular task. It comprises of a series of commands. Any SCM command can be executed from a macro, however there are certain SCM commands that can be used only in macros.
How to write a Macro:
1. Create a new set.
2. Type the desired commands in a sequence. Enter each command on a separate line.
The Description of the macro definition set should contain the commands to be executed.
3. The code of the macro definition set can contain optional labels as below:
DO
GOTO
EOF
ON ERROR
4. Save the set.
Note: Use only upper case letters in a Macro and write one macro per set. It is also recommended that you use letter M when you name a Macro set.
How to run a Macro:
A Macro can be run from the command line,
Syntax:
<macroname
How are Macros executed?
Aspen SCM executes the commands in a Macro sequentially until the END command is reached. Macros are very useful when you want to perform repetitive tasks and execute commands in a sequential manner. However since SCM interprets each line of a macro every time it is being run, processing certain large and complex loops can be slow.
Keywords: None
References: None
|
Problem Statement: The following
|
Solution: explains how to change the language of a case file in Aspen SCM.
Solution
Starting V8.4, a new application - Aspen SCM Utilities, would be installed along with Aspen SCM.
The first step to change the language of the case file is to change the language of SCM through the SCM Utilities:
1. Open Aspen SCM Utilities from the start menu under the Aspen Supply Chain Suite section
2. Once Aspen SCM Utilities is opened, choose “Select SCM Language”
3. This would open a window asking you to choose the required SCM Language. Once you choose the language, click on Run.
4. Allow commands to run, inside the Utilities window
The second step is to change the language of the case file:
1. Open Aspen SCM from the start menu under the Aspen Supply Chain Suite section. Notice that SCM uses the language selected in the previous step.
2. Go to File | Open and choose the required case file to open
3. Choose File | Case Language and choose the required language from the drop down
These two steps would change the language completely on the SCM and SCM Applications side.
Keywords: None
References: None
|
Problem Statement: How does the COSTALD liquid density model in Aspen HYSYS account for the effect of pressure?
|
Solution: In previous versions, the Chueh-Prausnitz model was used to account for the effect of pressure when calculating liquid density using the COSTALD equation. New in Aspen HYSYS 2006.5, the Tait equation was added as an option on the Parameters pagetab of the Fluid Package form, as in the figure below:
Keywords: COSTALD, liquid, density, calculation, pressure, Tait, Chueh-Prausnitz
References: None
|
Problem Statement: A swage fitting added as the last segment in a Pipe Segment Unit Operation will be automatically identified as an exit swage by Aspen HYSYS. The exit swage does not appear to have an impact on the overall pipe pressure drop (i.e. if it is removed, the same exit pressure is obtained).
|
Solution: The swage calculation in Aspen HYSYS accounts for pressure changes due both to acceleration (recoverable losses) and friction (non-recoverable losses). The pressure change across a swage is given by [ref. 1, section 5.2.3]:
Pin - Pout = K*0.5*rho*vel^2 + 0.5*rho*vel^2 - 0.5*rho_in*vel_in^2 (1)
where:
K the fitting factor (loss coefficient)
rho mass density
vel velocity
Pin, Pout pressure (into and out of swage)
Here Aspen HYSYS uses the convention that the loss coefficient is based on the outlet velocity head, although eqn (1) can be recast to use a loss coefficient based on the inlet velocity head (the two forms are interchangeable and, for incompressible flow, will give identical results).
Note that, if there is a diameter change in the direction of flow, the acceleration losses associated with changes in velocity head can lead to an increased pressure drop in the case of a contraction or a pressure rise in the case of an expansion. For expansions, the pressure rise is caused because velocity head is recovered as pressure head as the fluid decelerates (often termed static pressure recovery).
The loss coefficients, K, are normally calculated as functions of the upstream and downstream pipe diameters. However, there are two special cases:
1. A swage fitting identified as entrance will be assigned a K value of 0.5
2. A swage fitting identified as an exit will be assigned a K value of 1.0.
The basic assumption is that an inlet swage is treated as a sudden contraction from infinite diameter (hence zero velocity) and similarly an outlet swage is treated as a sudden expansion to infinite diameter (hence again zero velocity). Using this assumption, the K=0.5 and K=1.0 values can be derived from the loss coefficient equations [see, for example, ref.2].
For an exit swage where K=1.0, it is expected that there will be no overall pressure change. This is because the frictional (non-recoverable) loss is 1 velocity head and this is exactly balanced by the 1 velocity head that is recovered due to the deceleration of the fluid. So the net effect on the pressure drop is zero. Note that because the expansion for the outlet is assumed to be to infinite diameter and zero velocity, the loss coefficient calculation must be based on the inlet velocity head (not the outlet as shown in eqn 1) because the outlet velocity head is zero.
It is important to note that the equations for swage fittings are based on the assumption of fully developed flow. This means that for very short pipe segments either side of the swage, HYSYS will tend to over-predict the pressure change. We typically suggest checking that upstream and downstream segments have a length equal or greater than 5 times their diameters, to allow fully-developed flow to be established. For shorter lengths, users are advised to treat the HYSYS results with caution.
Keywords: swage, fitting, exit, pressure, drop, impact, segment, flow, K value, Crane, reducer, expander
References: s
1. Aspen HYSYS Operations Guide Manual.
2. Technical Paper 410M. Flow of Fluids Through Valves, Fittings and Pipe. Crane Co. 1999.
|
Problem Statement: There might be situations when you have to edit multiple cells in a table – you might be wanting to use the same value for all these cells or multiply/divide a factor to all these cells or add/subtract a value from all these cells. This
|
Solution: explains the easiest workflow to perform this process in all Configured Applications of Aspen Supply Chain Management.
Solution
For example, there is a screen in the Collaborative Demand Manager called the Forecast Review. This screen has a table which is used for viewing the current forecast values and to extensively override these values with new ones. In this table, users often have multiple number of cells to edit.
As soon as you select a cell, the numbers in that box would get selected and the application would be in the editing mode. If you hit the “Enter” key in your keyboard, you would exit the editing mode and you would be able to select the cell as a whole.
Editing Mode
Non-Editing Mode
Once you are in the non-editing mode, you would be able to select multiple cells, either through the “Ctrl” + Left mouse click (if you want to select cells randomly across the table) or through Shift and arrow keys (if you want to select cells in a series).
Ctrl + Left Mouse Click
Shift + Arrow Keys
*Please note that if you use Ctrl + Left Mouse Click for selecting cells, the initially selected cell upon which “Enter” key was used will be ignored. Only the cells upon which the Mouse is clicked will be selected.
After making the required selections, right click anywhere inside the table and choose the “Bulk Edit” option:
This would open up a little utility which has options to add/subtract a value to all the selected cells or multiply/divide a factor to all the selected cells or assign a value (by choosing the “=” symbol) to all the selected cells.
Once you choose the required Operation and type the required Value and click Apply, the new number would get populated on all the selected cells. For example, choosing the Operation as * and Value as 2.00 would change the table to:
After modifying this table, “Apply Changes” button needs to be selected from the “Home” tab in the Ribbon or from the right-click menu or by hitting the “F8” key in your keyboard, to submit the overrides.
Keywords: Bulk-Edit
PS
CDM
SP
References: None
|
Problem Statement: Which packing correlation should I use: Robbins or SLE? (Tray Sizing Utility)
|
Solution: In Tray Sizing Utility, there are two Packing Correlations, Robbins and SLE.
Robbins correlation, found in Chemical Engineering Progress Journal - May 1991, is only valid at liquid loading factors up to 20,000 and the program flags L is out of range warning message once the loading factor exceeds 20,000. Note: there is a bug in User's Guide HYSYS manual- page 8-78 as it states that the correlation is valid only at liquid loading < 20,000 Ib/hr ft2 (as opposed to liquid loading FACTOR). This is a mistake in the manual only, not in the code, and has already been logged in our Defect Control System to be corrected in the future.
SLE (Sherwood - Leva - Eckert) correlation is not valid when the pressure drop per length is either < 0.05kPa/m or > 1.5kPa/m and the program flags Pressure drop is out of range warning message when the pressure drop exceeds the limit. This equation can be found in any Column sizing or design book.
Robbins is the default correlation because it tends to predict pressure drop and hold up better, especially for newer packings. However, as mentioned it is constrained to conditions where a liquid loading factor is calculated as less than < 20,000. Outside this range use SLE so long as you are within SLE's range of validity.
Keywords:
References: None
|
Problem Statement: What is Marginal Utility Cost and how is it calculated?
|
Solution: The Marginal Utility Cost (MUC) is the incremental cost incurred by a plant for generating one additional unit of that utility. Correct calculation of the MUC is important for optimal operation of the plant heat/power systems and also for evaluating retrofit options. An example of calculating the MUC for a steam header is given below.
Example: A high pressure steam header runs 580 psia saturated steam. The MUC of this steam header is calculated by:
1. Go to Optimization, Edit Optimization Settings and check the ‘Calculate marginal utility costs’ box.
2. Double-click on the high pressure steam header in the flowsheet to open its Summary Table. Set the ‘IncludeMarginalCost’ field to ‘True’.
3. Run the optimization. The MUC of generating one additional unit of high pressure steam can be viewed in Summary Table.
Keywords: Marginal utility cost, steam header
References: None
|
Problem Statement: When loading Aspen Utilities Planner I get an error message Please install one of the following system compatible versions for: OOMF
|
Solution: OOMF is not part of Aspen Utilities Planner installation.
To have OOMF installed, you need to
· OOMF V8.4 - install Energy Analyzer V8.4 from the V8.4 DVD
· OOMF V8.6 – install PM(A+) from the V8.7 DVD
Also check inside the registry if you have the correct registry information.
· HKEY_LOCAL_MACHINE --> SOFTWARE --> WOW6432Node --> AspenTech --> 30.0 --> OOMF.
Make sure the value says 32.0 not 32
Keywords: aspen utilities planner, OOMF error, unable to run utilities planner
References: None
|
Problem Statement: I am using AutoPlant; however, it is quite tedious to transfer all the data into HYSYS. Does HYSYS interface with AutoPlant?
|
Solution: Unfortunately, HYSYS does not interface with AutoPlant.
If AutoPlant is an ActiveX compliant environment, however, you may be able to use a client such as MS Excel to access functions and variables in AutoPlant (functioning as an ActiveX server). Since HYSYS can also function as an ActiveX server, one could use MS Excel as an intermediary to transfer information from one application to another.
At this time, we do not have any examples, but the HYSYS to Excel side is fairly well documented on our support website (someSolutions are cross-referenced above). For more information on the capabilities of AutoPlant, you would have to contact Bentley (www.Bentley.com).
Keywords: Bentley
Excel
AutoPlant
HYSYS
References: None
|
Problem Statement: I am trying to create a report in HYSYS. I want to display liquid and vapor phase transport properties (for example, Molecular Weight, Viscosity) within the report. How may I do this?
|
Solution: In HYSYS v3.x and above, the column phase transport properties are displayed on the Performance Tab/Plot Page. From the field entitled Tray by Tray Properties, select Transport Properties and then click on the View Table button. At the bottom of the table is a Properties button. Press this button to edit the default (lt. liquid) transport properties information.
Keywords: phase
transport
properties
molecular weight
viscosity
surface tension
performance
References: None
|
Problem Statement: How is the settle out calculation performed in the Dynamic Depressuring Utility?
|
Solution: The Depressuring Utility in HYSYS works by defining a fluid of known composition and conditions and performing a depressuring calculation for a defined time period using defined heat flux and valve parameters.
The initial fluid composition is taken from the reference inlet stream(s) specified on the Design\Connections page of the depressuring utility. Up to four inlet streams can be specified and, if multiple streams are specified, the depressuring utility performs a settle out calculation to find the overall initial fluid composition and conditions.
The settle out conditions are calculated by performing a constant enthalpy, constant volume flash based on the conditions of the specified inlet streams and the volumes of each of the stream phases specified on the Design\Connections page. The attached Aspen HYSYS 2004 example case shows how this settle out calculation is performed by using HYSYS unit operations and a spreadsheet to carry out the same calculation. The details are as follows:
Spreadsheet Settle Out Calcs contains the individual inlet stream vessel and liquid volumes. These match the inputs on the Design\Connections page of Dynamic Depressuring Utility Depressuring - Dynamics - 1.
The three Adjust unit operations on the left hand side of the PFD adjust the total molar flow of each inlet stream until the actual volume flow over 1 hour of that stream is equal to specified vessel volume for that inlet.
Each feed is then flashed to separate the vapour and liquid parts.
The flow rates of the liquid streams from each flash are then defined using Adjust unit operations such that their actual volume flow over 1 hour is equal to the specified liquid volume for that inlet. Dummy tees are used in the setting of these flows.
The flow rates of the vapour streams from each flash are similarly defined using Adjust unit operations such that their actual volume flow over 1 hour is equal to the difference between the specified vessel volume and specified liquid volume for that inlet. Again dummy tees are used in the setting of these flows.
The streams from steps 5 and 6 are combined in a mixer.
A valve is then used to perform a constant composition, constant enthalpy flash.
The valve exit pressure is defined by an Adjust. This does the settle out calculation on the basis of constant volume, such that the actual volume flow over 1 hour is equal to the sum of the specified vessel volumes of the inlet streams.
This is the same calculation as is performed inside the depressuring utility:
The settle out stream pressure is used to define the initial operating pressure of the depressuring utility (Design\Operating Conditions page).
The actual volume flow of liquid over 1 hour of the settle out stream is used to define the initial liquid volume in the depressuring utility (Design\Connections page).
The settle out stream enthalpy is used to define the initial enthalpy (and hence temperature) in the depressuring utility.
The above approach can be used to define the settle out conditions of any number of streams.
Keywords: Settle, out, depressuring
References: None
|
Problem Statement: What version of OLGAS is being used in HYSYS?
|
Solution: OLGAS 2000 is incorporated into HYSYS v3.1 and up. HYSYS versions previous to 3.1 used the OLGAS v1.1 correlation.
Keywords: OLGAS, HYSYS, Pipe, Correlations
References: None
|
Problem Statement: Why can I not enter my D86 assay in mass percent?
|
Solution: Aspen HYSYS accepts TBP and Chromatographic analyses in any one of the three standard bases; however, due to the form of the API Data Book conversion curves, EFV, ASTM D86 and ASTM D1160 distillations must be supplied on a liquid volume basis and ASTM D2887 distillations must be entered on a mass basis.
Keywords: assay, enter, basis, bases, D86, EFV, ASTM, D1160, TBP, D2887, chromatographic
References: None
|
Problem Statement: When do the Data Sets in the Update Log on the home page of Collaborative Forecasting update and what triggers their update?
|
Solution: The All Sets Published columns update when the create_schema.cmd is executed or when the database (Converting CF database from prior version to current version) is upgraded.
The Data Sets Re-Published columns updates after:
1. Published is selected from the Publish Collab Forecast screen.
2. Re-publish is selected and then intra_repub u1 (here u1 means business unit one u1,u2,u3...un) is executed from the command line.
3. After you accept or reject an override in DM then Re-publish on Process CF Override screens, this column also updates.
The Selected Records Refreshed columns update when the create_schema.cmd is executed or when the database (Converting CF database from prior version to current version) is upgraded.
Keywords: Collaborative Forecasting
Main Screen
References: None
|
Problem Statement: How does HYSYS calculate pump and compressor duty?
|
Solution: The pump and compressor duty is calculated in HYSYS using the following equations:
Pump Duty:
Duty = Flow * Power
If outlet pressure is greater than inlet pressure, Power is calculated as:
Power = (Pout - Pin) / LiquidDensity / (Eff / 100);
Otherwise (meaning if the outlet pressure is smaller than the inlet pressure), power is calculated as:
Power = ((Pout - Pin) / LiquidDensity) * (Eff / 100);
Where LiquidDensity is inlet liquid density (if inlet liquid density is not known, then outlet liquid density is used).
Compressor Duty:
Duty = flow * (Hout - Hin)
Where Hin is the Feed Enthalpy.
If Adiabatic efficiency is specified, then Hout is calculated as
Hout = IsentropicEnthalpyChange / Adiabatic Efficiency
If polytropic efficiency is specified, then Hout is calculated as:
Hout = IsentropicEnthalpyChange / Adiabatic Efficiency (where Adiabatic Efficiency is first calculated using the polytropic efficiency)
More information can be found in the Rotating Equipment section of the HYSYS Operations Guide.
Keywords: Pump duty, compressor duty, adiabatic efficiency, polytropic efficiency, power, pump, compressor
References: None
|
Problem Statement: How do I enter ASTM D5307 simulated distillation data in Aspen HYSYS?
|
Solution: The generation of the ASTM D5307 distillation curve data is the same as for the ASTM D2887 method (both are based upon retention times and peak areas). Therefore, the ASTM D5307 data can be entered in Aspen HYSYS as ASTM D2887.
The only difference between the two assays is that the D2887 is used for light crudes and it is a one pass method, while the D5307 is used for heavier crudes and it is a two pass method.
Brief description of the method used to obtain a simulated distillation curve generated from chromatographic data:
A crude sample is passed through the gas chromatographer (GC) and retention times are recorded.
These retention times are then compared with the retention times from pure components, which are known.
Based upon the area of the peaks given by the GC, it is possible to calculate how much of the pure components are contained in the crude sample.
As each pure component has a known boiling point, a resulting boiling point curve can be reported on a weight percent basis.
Keywords: ASTM, ASTM D5307, ASTM D2887, Oil Manager
References: None
|
Problem Statement: What is the definition of True Vapor Pressure and Reid Vapor Pressure?
|
Solution: Definition:
True vapor pressure (TVP) is the pressure of the vapor in equilibrium with the liquid at 100 F. It is equal to the bubble point pressure at 100 F.
After the sample is flashed at 1 atm and 33 F, and the resulting liquid product is mixed with air at a volume ratio of 1 : 4 (liquid : air). The pressure of the system at constant volume and 100 F is reported as Reid vapor pressure (RVP). RVP is a measure of the vapor-locking potential of the material. A stabilized gasoline should have an RVP between 10 and 12 psia.
Comparison:
Reid vapor pressure is different from true vapor pressure in value caused by the vaporization of small amount of sample and the presence of water vapor and air in the test chamber. Usually the two properties differ by a factor of 1.05 to 1.10.
Conversion methods between RVP and TVP are provided in reference [3].
Keywords: TVP, RVP, true vapor pressure, Reid vapor pressure.
References: s:
1) ASTM D2889 - 95(2005)e1 Standard Test Method for Calculation of True Vapor Pressures of Petroleum Distillate Fuels.
2) ASTM D323 - 06 Standard Test Method for Vapor Pressure of Petroleum Products (Reid Method).
3) US Environmental Protection Agency (EPA) publication AP-42, Compilation of Air Pollutant missions. Chapter 7, Section 1.
|
Problem Statement: When the user tries to open and run a model in Aspen Utilities Planner (AUP) installed from Aspen ONE DVD-ROM V8.7, the user may experience some issues since the OOMF is not included within the Aspen Utilities Planner’s installation files.
|
Solution: OOMF is not necessarily used or required by AUP, however in order for it be to installed correctly, the user should install the following programs from the correct AspenONE DVD-ROM version:
1) OOMF V8.4 - Install Energy Analyzer V8.4 from the V8.4 DVD.
2) OOMF V8.6 - Install PM(A+) from the V8.7 DVD.
Keywords: OOMF, AspenONE DVD-ROM V8.7, Energy Analyzer, PM(A+).
References: None
|
Problem Statement: By default, the stream Fly-by on HYSYS PFD only shows the stream name, temperature, pressure and molar flow. Can I add more properties?
|
Solution: Yes, this can be done by changing options under Tools --> Preferences --> Simulation --> Tool Tips. Check the Show PFD Fly By check box, then select either the SteadyState or Dynamic radio button, depending on which mode you are currently in.
To modify the fly-by properties of material stream, highlight Material Stream, then in the right hand side column check the checkboxes of the stream properties that you want to display in the Material Stream Fly-by.
To modify the fly-by content of unit operations, expand the Unit Operation tree on the same Tool Tips view, highlight a unit operation and select the appropriate checkboxes from the right hand side column for the parameters that you want to display in the unit operation fly-by .
Once the modifications are done, you can choose to Save Preference Set or just return to the flowsheet. The PFD fly-bys should now display the properties you selected. If the modification does not take place once returning to the flowsheet environment, exit the program and re-launch HYSYS.
Keywords: Stream, material stream, PFD, Fly by,
References: None
|
Problem Statement: Gas heats up when expanded across an adiabatic valve - why? Shouldn't it cool down?
|
Solution: Whether a gas heats up or cools down when expanded across an adiabatic (constant enthalpy) valve depends on the sign of the Joule-Thomson (J-T) coefficient (a positive J-T coefficient means cooling occurs and a negative J-T coefficient means heating occurs) and the sign of the J-T coefficient depends on the conditions (T and P). As shown in Figure 1 in the attached Word document, it is positive inside the shaded area and negative outside; the boundary at a given pressure is the Inversion Temperature. Reduction of pressure under adiabatic conditions moves the system along constant enthalpy curves (isenthalps). The inversion temperature occurs when the isenthalps change the sign of their slopes from negative to positive.
A gas typically has two inversion temperatures (upper inversion temperature and lower inversion temperature) at a given pressure (see Figure 2 in the attached Word document). For a perfect gas, the J-T coefficient is zero.
Keywords: Joule-Thomson, Inversion temperature, Gas temperature, Adiabatic , Valve, Thomson
References: None
|
Problem Statement: My simulation is quite large and I am having trouble finding a stream. Is there an easy way to find the stream and make changes?
|
Solution: There are two methods.
1. The Simulation Navigator will allow you to view and make changes to each stream, vessel, etc. without having to do a manual search. This tool is found under Flowsheet|Simulation Navigator.
2. The Select Objects feature, found in the PFD menu, allows you to select the stream on the PFD without physically clicking on the stream. When the stream is selected it is surrounded by a flashing white box. Once the stream is selected you can press the Home key on the keyboard to center the PFD on the stream allowing you to open the stream's property view. (Note the PFD window must be the active window in order to see the PFD menu.)
Keywords: flowsheet
data
zoom
manual
search
References: None
|
Problem Statement: I am modelling a gas-gas exchanger with the heat exchanger model. With either the end point or weighted model, the reported U value on the dynamics tab of the exchanger is about 110 to 140 Btu/hr/ft2/°R where as one would normally expect an U value in the order 10 - 20 Btu/hr/ft2/°R for a gas to gas heat exchange application.
|
Solution: With the endpoint and weighted mode calculation, the heat exchanger block calculates the UA value for the exchanger from
Q = UA x LMTD
In other words, the UA is calculated by dividing LMTD into Q. Since the heat changer has default geometry values, the exchanger area is calculated from the geometry and hence the U value displayed on the dynamics tab of the exchanger is equal to the UA result divided by the calculated area.
It is important to realize that the U values for these modes are not calculated from the shell and tube side film coefficients and therefor quite likely will not match the expected overall U value for the type of application e.g. gas-gas, gas-boiling liquid etc.
Keywords: heat transfer coefficient
References: None
|
Problem Statement: How can I make the Report/Datasheet/Specsheet header show only the file name not the full path?
|
Solution: HYSYS uses a number of configuration files to control what gets printed for each type of report datasheet. These files are all contained in the \Support subdirectory of the HYSYS installation (along with various other support files), and have the extension rdf (report definition file). There is one for each operation / stream type. These are all just plain text files, however the format is not really intended for user modification. The file that controls the header and footer is called headfoot.rdf.
Attached to thisSolution are modified versions of the headfoot.rdf file for various HYSYS versions (named appropriately e.g. HYSYS 32 headfoot.rdf) that make the report display just the file name instead of the full path. To use any of these files:
Close any open instances of HYSYS
Locate the headfoot.rdf file in the \Support subdirectory of your HYSYS installation - rename it (e.g. to something like headfoot.oldrdf)
Download the appropriate headfoot.rdf file from thisSolution - Be sure to get the file corresponding to the version you are using!
Rename the file to headfoot.rdf and put it into the \Support subdirectory
Start HYSYS - any reports will now use the modified header
For interest and in case you need to modify the headfoot.rdf file of a newer HYSYS version the only change made was as follows:
Change the section (only change is line starting Moniker)
TextField CaseName
Size 45 1
Label Left Case Name:
Align Left
LabelWidth 8
Moniker DocumentObject.0:FullFileName.100
end
to
TextField CaseName
Size 45 1
Label Left Case Name:
Align Left
LabelWidth 8
Moniker DocumentObject.0:CaseFileName.300
end
N.B. The headfoot.rdf file is usually set to read only so its file attributes will need to be changed to allow modifications to be made.
Keywords: Headfoot.rdf, Report Definition file, file name, file path
References: None
|
Problem Statement: The stream cutter unit operation can be installed and converged when using the OLI property package, but it cannot be used to switch between the OLI property package and any other property package.
|
Solution: This is a limitation of the OLI package, it does not currently support the stream cutter operation functionality. Until this functionality is added, you must use a subflowsheet approach, where the subflowsheet has a different simulation basis than the main environment, which is OLI.
Keywords: stream cutter, OLI
References: None
|
Problem Statement: In the Design tab / Connections menu of the Depressuring-Dynamics utility the user has the option to input some metal mass in contact with the vapour and some metal mass in contact with the liquid as Correction Factors. How are they used in the Depressuring calculations?
|
Solution: The contribution of the metal wall to the heat losses is only taken into account if Detailed is selected as Heat Loss Model on the Heat Flux page (Design tab). The metal mass that is going to absorb part of the heat being transferred is calculated assuming cylindrical shape for the vessel with flat ends (times the thickness, times the density). If the vessel is known to have some additional metal parts that need to be taken into account (like valves or other attached fittings) or if it is necessary to account for non-flat vessel ends (i.e. semispherical) the Correction Factors can then be used.
Keywords: Correction Factors, Metal Mass, Detailed Model
References: None
|
Problem Statement: SYLTHERM 800 is not included in the HYSYS pure compound database.
|
Solution: SYLTHERM 800 heat transfer fluid is a highly stable, long-lasting silicone fluid designed for high temperature liquid phase operation. It exhibits low potential for fouling and can often remain in service for 10 years or more.
As a relatively new heat transfer fluid, SYLTHERM 800 is not available in the HYSYS pure compound database. The fluid package provided with thisSolution allows users to import a readily available SYLTHERM 800 fluid created as a hypothetical component. You can simply import it into a HYSYS file from the Fluid Package view in the Basis Environment, as indicated in the attached image file. The information used in defining this component was taken from DOW Product Information sheet published in Nov.2001.
Keywords: SYLTHERM 800, heat transfer fluid, thermal fluid, hypothetical, component
References: None
|
Problem Statement: </u></b>
How can I add third party tray vendor (e.g. Sulzer) information in the Tray Sizing utility?
<b><u>
|
Solution: </u></b>
Unfortunately this is not possible. HYSYS only supports the following tray vendor information: Koch, Glitsch and Nutter.
<b><u>KeyWords</u></b>
Tray Sizing, Tray Vendor
Keywords: None
References: None
|
Problem Statement: When loading an Utilities Planner file V8.0 through Excel it is will occasionally show the following error message:
Aspen Properties: Unable to generate definition file. Aborting command,
and then followed by :
Filed to establish connection. Do you want to retry?
If you click Yes, Excel will load the file successfully or sometimes show the error:
“MS Excel: Unable to connect with OLE”.
How can I avoid these errors?
|
Solution: In V8.0, the Aspen Properties file is embedded in the Utilities Planner (.auf) file. So when an Aspen Utilities simulation is loaded, it calls Aspen Properties via OLE automation in the background to generate the appdf. If the machine is slow, this can time out and you will see the error shown. This effect can be magnified under Excel because Excel in turn calls Aspen Utilities via OLE automation.
To avoid this issue the user can modify the .auf file to use aspenutilities.appdf instead of generating it every time. The steps to do this are as follows:
1. Clean out any AM_* sub-folders under the folder containing the *.auf file
2. Load the *.auf file in Aspen Utilities.
3. On the explorer window, go to Component Lists and select Configure Properties from the lower pane
4. In the Physical Properties Configuration dialog, select Use Properties definition file and AspenUtilities.appdf from the C:\ProgramData\AspenTech\Aspen Utilities Planner V8.0 directory (or other directory which contain the properties file which you want to use)
5. Press OK to close the dialog and close the simulation.
6. Open AMSystem V8.0\bin\OnPostOpenUtilitiesDocumentScript.vb in notepad
7. Comment out the line : Application.Simulation.RaiseUserEvent(LoadProperties)
by putting a single quote ' before the line and then saving this.
Load the simulation file through Excel again and you will observe that the file will load faster and without errors.
Keywords: Utilities Planner, Excel, definition file.
References: None
|
Problem Statement: What is Use Spreadsheet operating mode (Design --> Heat Flux --> Heat flux parameters) and how can I use it to model the heat flux to the vessel being depressurized?
|
Solution: The Use Spreadsheet option refers to the duty spreadsheet of the dynamic depressuring utility. This spreadsheet can be accessed by clicking the View Spreadsheet button on the Design --> Heat Flux page if the operating mode selected is Use Spreadsheet or by going inside the dynamic depressuring utility flowsheet while using any other operating mode. This option allows the user to edit the duty spreadsheet without the values in the spreadsheet getting overwritten when the utility runs. This feature also allows more advanced users to use their own equation for modeling the heat flux to the vessel. For example, heat flux to the vessel can be modeled using a combination of different operating modes, the standard/default equations being used by the spreadsheet can be modified or additional equations can be added to the existing ones. An example Hysys 3.1 case using Use Spreadsheet operating mode is attached. Please note that an additional equation (Test Duty, Cell B14) had been added to the spreadsheet and the equation for ACTUAL DUTY (Cell B15) has been modified to include the contribution from the additional equation.
IMPORTANT: Please note that the coefficient/parameters and the Test Duty equation (cell B14) specified on the duty spreadsheet of the attached example Hysys case are arbitrary.
Keywords: dynamic depressuring, Use Spreadsheet, Duty Spreadsheet
References: None
|
Problem Statement: How can I take a side draw from a tray and set out to a stage below? For a better understanding of the procedure, this
|
Solution: document presents an example on how to take all the liquid from tray 6 and set out to the tray 7 in an Atmospheric Crude Tower.Solution Add a new specification into the Column. You must select the Column Liquid Flow spec. In the Stage option you will select the tray you want to take the side draw. As Spec Value a very low value would be defined. In the Column Environment go to the Column editor and select the Side Draws page located in the Design tab. Select the Liquid option. Create a new stream with the tray number corresponding to the side draw. The go to the Connections page and add the new stream already created associated with the set out tray. Return to the Main Subflowsheet and be sure the degrees of freedom in the Column are equal to zero. Set the active specs. Finally run the column.
Keywords: column, tower, tray, specification, liquid
References: None
|
Problem Statement: How do I resize Stream / Unit operation tables on the PFD?
|
Solution: It is not possible to use the drag option to enlarge or reduce the size of PFD tables. The workaround is to resize the fonts on the table which will subsequently resize the table.
The work flow is as follows:
Highlight the table to be resized--> On the Ribbon tab click on Format --> Click on Edit --> Then select the font size required.
Keywords: PFD, Stream, Unit operation, Table size
References: None
|
Problem Statement: What are the new features added in Aspen Utilities Planer V7.3
|
Solution: Several new features are added to Aspen Utilities Planner V7.3 to improve the user experience.
1. Support hierarchical flowsheeting environment - Aspen Utilities Planner now supports ACM hierarchical block in the optimization. User could add any layer of hierarchies in the flowsheet in modeling complex utilities system.
2. Embed data editor in Excel - three worksheets namely Demand, Availability and Energy Cost Summary are created automatically. These worksheets enable user to directly edit the demand and equipment constraint as well as the tariff information inside Excel. This also facilitates the data exchange between Aspen Utilities Planner and other programs such as Aspen PIMS.
3. Calculate the marginal cost for the constraints - The marginal costs are calculated and displayed side by side with the optimumSolution for the active constraint. This enable user to easily see the economic impact of the constraint on the total energy cost.
For more details look at the attach document
Keywords: Demand, Availability, Energy
References: None
|
Problem Statement: Is there a quick way of hiding multiple objects on the PFD or all the objects of one type?
|
Solution: This can be done by first selecting multiple objects on the PFD using the 'Select Objects ...' function and then hiding them.
Right click on the PFD, choose 'Select Objects ...' On the list that appears select all the objects you want to hide. You can use the usual Windows selection keys, e.g. Shift and click to select a group, or Ctrl and click to make multiple selections. To select all the operations of one type use the 'Setup Custom' button to create a filter and then select all the objects in the list.
'OK' the Select Objects window, then right click on one of the highlighted objects on the PFD and choose 'Hide'. This will hide all the objects that are selected.
To unhide objects right click on the PFD background and choose 'Reveal Hidden Objects ...'
Keywords: Hide, Reveal, Multiple
References: None
|
Problem Statement: I added some user properties in the basis/oil environment. How do I see them in the stream property view for all the streams?
|
Solution: If you are interested in seeing your user properties in the stream property view for all the streams, please follow the steps below:
From Tools menu, select Correlations.
On the Correlation Manager view, under Available Correlations property box, click on the plus sign beside Clone correlations group.
Select the user property you want to see in the stream property view and click on the green tick button (under the Toolbar for Correlation Controls (Global)).
Repeat step 3 for other user properties.
Close the Correlation Manager view.
Now you can see your user properties for all the streams on the stream property view (Worksheet --> Properties).
Keywords: user property, streams, correlations
References: None
|
Problem Statement: Does PIPESYS predict the temperature profile close to the pipe wall - not the bulk temperature?
|
Solution: PIPESYS predicts the bulk temperature profile, not the temperature profile across the pipe diameter. You would need a 2D or 3D finite element program to calculate the temperature close to the pipe wall.
Keywords:
References: None
|
Problem Statement: In Aspen HYSYS Dynamics, are column-trays Theoretical or Actual?
|
Solution: HYSYS trays in dynamics are actual 100% efficient trays. In other words, when it comes to thermodynamics the trays act as theoretical trays, and when it comes to hydraulics the trays act as actual trays. To make them truly actual trays, you need to specify the efficiency, which then becomes a flash efficiency (i.e. how much of the vapour feeding the tray participates in the flash).
Keywords: Dynamics, Dynamic, Column, Tray,Trays, Efficiency, Efficiencies, Actual, Theoretical
References: None
|
Problem Statement: I get the error Error 0: Cannot find a security key on the serial port of this computer but my key is there. What is wrong?
|
Solution: For HYSYS 2.2.2 and earlier:
This error message is telling you that HYSYS is having problems seeing the key because:
It's not attached to the computer properly. Check your cables or gender changers. We have seen many instances where the cable connecting the key to the computer was faulty.
There is a problem with the serial port of the computer. Check that another device such as a serial mouse works using the port in question. The HYSYS key can be on either com port, it will look at both ports. If there is something wrong with your port, your IT people will have to help you.
The key is no longer working. Take the key to different computer start up HYSYS and load a case. If unsuccessful, we'll need to send you a new key. Contact [email protected] with your key number, and shipping address.
The computer is too fast. HYSYS 2.4 has a new security system that is both software and hardware based and should correct the problem of keys not being found due to fast chips. We'll need to send you a new SLM key that fits on the parallel port. This problem may occur with Pentium IV computers.
This message will come up for a standalone HYSYS version. The errors for network versions are different. Please see the Get Started manual on your HYSYS CD for more information.
Keywords: serial, standalone, install
References: None
|
Problem Statement: Can Multiple Aspen Utilities Models be run on a single Aspen OnLine Server?
|
Solution: Yes, multiple Aspen Utilities models be run on a single Aspen OnLine server.
Aspen Utilities configuration items regarding the location of the Profile, Tariff, Interface, and Demand Databases, as well as the location of the Optimization Model file, are configured at an application/PC level.
As such, if a user wants to run multiple Aspen Utilities Models on a single PC, he has to reconfigure these application settings for each model to point to the database and Optimization files specific to the Utilities Model the user wants to run. In other words, normally there can be only one Aspen Utilities model which uses database run on single Aspen OnLine platform. By following the steps below, user can configure multiple Aspen Utilities models to run on one Aspen Online platform.
Open first model file in Aspen Utilities 12.1
Click Flowsheet folder in the simulation pane
Click Add Script and give name PreOpt
Copy the following lines to the script
' Read and Write to and from the Registry.
Dim strInterfaceValue, strProfileValue,strTariffValue,strDemandValue,strModelValue strModelValue = D:\AspenTech\Aspen Utilities 12.1
strInterfaceValue = D:\AspenTech\Aspen Utilities 12.1\BP Lavera\Interface.mdb strProfileValue = D:\AspenTech\Aspen Utilities 12.1\BP Lavera\ProfileData.mdb
strTariffValue = D:\AspenTech\Aspen Utilities 12.1\BP Lavera\TariffData.mdb
strDemandValue = D:\AspenTech\Aspen Utilities 12.1\BP Lavera\DemandData.mdb
Dim objShell 'This establishes the variable Shell that will become the WScript.Shell object. Set objShell = CreateObject(WScript.Shell) 'Establish the WScript.Shell object: Shell
Const Reg_InterfaceKey = HKEY_CURRENT_USER\Software\AspenTech\Aspen Utilities\12.1\Databases\Interface 'Set constant as the registry path to the desired interface database key.
Const Reg_ProfileKey = HKEY_CURRENT_USER\Software\AspenTech\Aspen Utilities\12.1\Databases\ProfileData 'Set constant as the registry path to the desired interface database key.
Const Reg_TariffKey = HKEY_CURRENT_USER\Software\AspenTech\Aspen Utilities\12.1\Databases\TariffData 'Set constant as the registry path to the desired interface database key.
Const Reg_DemandKey = HKEY_CURRENT_USER\Software\AspenTech\Aspen Utilities\12.1\Databases\DemandData 'Set constant as the registry path to the desired interface database key.
Const Reg_ModelKey = HKEY_CURRENT_USER\Software\AspenTech\Aspen Utilities\12.1\Dash\ModFilePath 'Set constant as the registry path to the optimization model file path key.
' Write current path to registry key and read it to become constant for script. objShell.RegWrite (Reg_InterfaceKey), strInterfaceValue, REG_SZ ' objShell.RegWrite (Reg_ProfileKey), strProfileValue, REG_SZ ' objShell.RegWrite (Reg_TariffKey), strTariffValue, REG_SZ ' objShell.RegWrite (Reg_DemandKey), strDemandValue, REG_SZ ' objShell.RegWrite (Reg_ModelKey),strModelValue , REG_SZ '
'strReadValue = objShell.RegRead(Reg_TestKey)
'MsgBox strTestValue
Set objShell = nothing
Change the string value of strInterfaceValue, strProfileValue,strTariffValue, strDemandValue,strModelValue to the desired location.
Double click on the script to test. Message Script Completed should pop up.
Close the script and Save the model file
Exit AU
Follow the same step for the second model.
The PreOpt script will be called automatically before the optimization run and therefore the database and model settings will be altered accordingly.
The above step and script can be applied to multiple version of Aspen Utilities. Simply substitute the version number from 12.1 to appropriate version number. For example, subsititute 12.1 with 13.1 if you are using Aspen Utilities version 2004.
Keywords: Aspen Utilities
Aspen OnLine
multiple
References: None
|
Problem Statement: How Temperature Correction Factor is calculated in Gas Turbine?
|
Solution: Here are some of the general equations used.
PowerTCorrection = (TAirin ? RefTemp) * K1Power + K2Power
ExhaustFlowTCorrection = (TAirin ? RefTemp) * K1ExhaustFlow + K2 ExhaustFlow
HeatConsTCorrection = (TAirin ? RefTemp) * K1HeatCons + K2HeatCons
dExhaustTempTCorrection = (TAirin ? RefTemp) * K1 ExhaustTemp + K2 ExhaustTemp
The correction formula are:
PowerOut(?PowerOut1?).Power = Power_Curve * PowerTCorrection *PerFact * HumidityCorrection + PerformanceCorrection + PowerAugmentation
FFuel = Fuel_Curve * HeatConsTCorrection;
FAirout = ExhaustFlow_Curve * ExhaustFlowTCorrection + SteamIn(?SteamIn1?).F
TAirout = ExhaustTemp_Curve + dExhaustTempTCorrection
Note:
Gas turbine model, GTG performance depends on the ambient temperature and humidity. The performance curves entered (i.e. Heat Cons vs. Power, Exhaust Temp vs. Power, and Exhaust Flow vs. Power) are typically based on a specific temperature tested by the equipment vendor such as at 60 F. User need to correct those performance based on the current ambient temperature and humidity.
Keywords: GTG, Exhaust flow
References: None
|
Problem Statement: Why actual liquid flow value in table or workbook showing empty in case of two liquid phase streams?
|
Solution: If you import/add variable actual liquid flow in spreadsheet, show table view or in workbook it will show empty in case of stream with two liquid phases even though it shows value in property view of the stream. Since, there is a two liquid phase formation, actual liquid flow data is linked to phase actual liquid flow..mixed liquid phase. Therefore, to import/add actual liquid flow correctly, you have to choose phase liquid flow..mixed liquid phase option.
Keywords: import, actual liquid flow, two liquid phase, stream
References: None
|
Problem Statement: How do I create a Surge Controller in Aspen HYSYS?
|
Solution: The Surge Controller in Aspen HYSYS is a special type of unit operation and must be added by clicking the Create Surge Controller button on the Dynamics\Specs page of the associated compressor.
If the compressor associated with the surge controller is subsequently deleted, the surge controller is automatically deleted as well.
Important Note
If a Surge Controller is added from the Flowsheet\Add Operation menu (or its F12 shortcut), or from the Create Unit Op button on the Workbook, then it will not function.
Keywords: surge controller, compressor, anti-surge
References: None
|
Problem Statement: When a duty stream is attached to a separator in dynamics how is the duty split between the phases?
|
Solution: There are several options which depend on the settings in the separator.
If there is no heat loss, the energy stream is fed directly into the separator equilibrium flash and is not applied to any bypass material which exists if effciencies are being used (i.e. efficiencies less than 100%). The bypass phases are then mixed with the equilibrium flash result phases.
If simple heat loss is being used with the vessel then the duty is split between the equilibrium and bypass phases such that they move towards the same temperature.
If detalied heat loss is being used then there is a duty value applied to each phase and that value is split between the bypass and the equilibrium flash phases.
Keywords: Duty, Separator, Dynamics, Phase
References: None
|
Problem Statement: When defining the ambient temperature for a buried pipe, what should I enter?
|
Solution: For buried pipes, you should enter the ambient temperature as the ground temperature at surface level.
Keywords: ambient, temperature, pipe segment
References: None
|
Problem Statement: Why does the PID Controller report the PV up to 7% outside the PV range?
|
Solution: For example in the attached case the controller range is set to 0 to 100 bar, the PV is reported as 107 bar, and the pressure in the stream (the source for the PV) is 110 bar.
This is intentional, to allow the user to see small PV overshoots just outside of the PV range. However, internally the controller algorithm only sees the PV varying within the PV range. So for example a 2% change in PV from 102% to 104% of the range will not affect the controller output.
Keywords: PID Controller, PV range
References: None
|
Problem Statement: What are the equations behind Dynamic column hydraulic calculations?
|
Solution: When running a distillation column in Dynamics, several parameters are displayed on the Performance / Hydraulics page of the tray section (in the Column Environment). Here below is explained how all those fundamental variables are calculated.
Bulk Liq Volume is calculated by multiplying the area of the tray section by Liquid Height on Tray; and Liquid Height on Tray minus Height over weir is equal to Weir Height.
Liquid Height on Tray is for the whole tray itself and has nothing to do with the liquid height in the downcomer. This way the Height over weir is the height of the layer of liquid that is overflowing from one tray to the tray below, and is related to the liquid flow and the weir length. If you think that the liquid height you get is too high, you should verify the weir length you are using which should be the total weir length. You may get an unreasonable height of liquid on tray because of a weir length that is too small.
DC Volume: the default value of the downcomer volume is calculated based on DC Volume = 0.05 (m) - Diam (m)^2 - PI / 4
Currently Downcomer Volume, Active Area and number of flow paths are not used in the Column Hydraulics calculations. As we can deduce from the above, what is done is that the volume of liquid and the total area are used to compute the height of liquid. Then using the total weir length, the height of liquid over the weir is calculated and that determines the liquid flow by using the Francis weir equation.
The basic weir equation is Fweir = 1.839 - Lweir - density - h^1.5 (units of the constant, m^0.5/s).
Part of the development plan for future releases is to make the hydraulics calculations more sophisticated.
Summarizing, what is shown in the Hydraulics page of the tray section is as follows:
1 - Dry hole DP: according to the following equation:
flow = k - SQRT(density - DryHoleDP)
2 - Static Head:
P = g - (rhoL - liqHontray + rhoV - (traySpace-liqonTray))
3 - Height over weir: comes from the Francis equation for the standard suppressed rectangular weir: Q = 3.33 - L - h^3/2 in Field units
4 - Liquid Height on Tray = Height over weir + Weir Height
Keywords: Column, tray section, hydraulics.
References: None
|
Problem Statement: What does L, H, V, phases stand for in the properties table utility?
|
Solution: L - indicates a light liquid (hydrocarbon rich) phase
H - indicates a heavy liquid (heavier hydrocarbon or aqueous) phase
V - indicates a vapour phase
Keywords: hydrocarbon, properties, utility, table
References: None
|
Problem Statement: How can I force an extension to resolve using code outside the extension?
|
Solution: There are a number of ways to accomplish this
Ignore and Unignore the extension via code
There is no defined object type for an extension operation. However if you obtain an object for your extension using the Object variable type and then set up a watch on this operation you'll see it has a number of properties. One of these is IsIgnored, by setting this to True and then False you can force a recalculate.
Sub ReCalcExtn()
'Example VBA code to force an extension to solve by ignoring and unignoring it
Dim hyApp As HYSYS.Application
Dim hyCase As HYSYS.SimulationCase
Dim hyExtnObject As Object
Set hyApp = GetObject(, HYSYS.Application)
Set hyCase = hyApp.ActiveDocument
Set hyExtnObject = hyCase.Flowsheet.Operations.Item(op-100)
hyExtnObject.IsIgnored = True
hyExtnObject.IsIgnored = False
End Sub
Change the value of an extension variable that is itself set to trigger a solve in the extension
This is more elegant (although a little more involved), since it does not make the extension show as temporarily ignored.
This is illustrated by the RVP sample extension. (In KnowledgebaseSolution #110059, http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=110059)
The user variable that accompanies the extension (to automate the ignoring/unignoring of the boiling point curves utilities required in the API 5B1.1 method) needs to trigger a resolve of the extension. It does this using the following lines of code:
Dim RVPOp As Object 'Object reference for the RVP Extension
Dim ReCalcRV As HYSYS.RealVariable 'RVP Extension variable that when changed forces a recalculate
'... Intermediate lines - establish RVPOp as an object for the RVP extension
Set ReCalcRV= RVPOp.GetUserVariable(ReCalcAPI5B11).Variable
ReCalcRV.Value=ReCalcRV.Value+1
The GetUserVariable method is the way to access extension variables from outside the extension (See KnowledgebaseSolution #109139, http://support.aspentech.com/webteamcgi/SolutionDisplay_view.cgi?key=109139)
Here ReCalcAPI5B11 is the 'Tag' (or moniker) of a variable set up in the RVP edf file that has its Triggers Solve checkbox checked. This variable need not be linked to any of the widgets on the extension interface. Hence by incrementing this variable the extension will resolve.
Keywords: Extension, Solve, GetUserVariable, Isignored, Triggers Solve
References: None
|
Problem Statement: Even if the units in HYSYS are set to Field units, the specified frequency (number of fins per unit length) will be considered in HYSYS as fin/m (NOT fin/in).
To verify this, switch between Field and SI units and look at the frequency at each time. It will not change.
|
Solution: The frequency on HTFS-ACOL/ Extended Surface page and HTFS - MUSE/ Fins page always has to be specified as fin/m even though the units are set to Field in HYSYS.
Keywords: Frequency
Fin
ACOL
HTFS
HYSYS
Extended
Surfaces
MUSE
Link
Units
Field
SI
References: None
|
Problem Statement: Aspen Utilities Planner generates error message Unhandled exception…. What does this mean and how can this be avoided?
|
Solution: This error message is generated when an unsupported character such as slash or a space is used in a block name. In this case the Aspen Custom Modeler (ACM) replaces the block name internally with Blocks (“….”). Such as a name UITILEXP.MIP/XYXSOLV is replaced by UTILEXP.BLOCKS(“MIP/XYZSOLV”) which has more than 25 characters. The current database design limits the number of characters allowed in the EquipmentID column to a maximum of 25 characters.
How to fix this error - Remove the unsupported characters in the block name to eliminate the above error.
Keywords: Unhandled exception
References: None
|
Problem Statement: How do I configure the new OLGA link extension and add OLGA Link, specify connections, set up the OLGA server, expose variables, and perform other additional steps?
|
Solution: The document attached will cover all of the steps required for setting up and configuring the new OLGA Link extension. You will learn how to add an OLGA Link, specify connections, set up the OLGA server, expose variables, and perform other additional steps.
Keywords: Dynamic simulation, dynamics, transient, HYSYS, HYSYS Dynamics, hydraulics, OLGA, extension, upstream, upstream dynamics
References: None
|
Problem Statement: Normally you can register extensions in HYSYS from Tools | Preferences | Extensions tab. However, if the extension name includes an underscore, it may cause a corruption in the information which is saved about the extension in the registry either because the extension's name is broken or because the information is added under an additional subkey - Addins.
HKEY_CLASSES_ROOT\Software\Hyprotech\HYSYS\1.1\Extensions\Addins
In either case, no error will show up during the extension registration but HYSYS will not be able to access the extension at runtime.
If you are developing the extension you can correct the problem by using a PROGID name which includes no underscores and re-compile the extension but in some cases you may receive the compiled extension files from a third party provider and you do not have access to the code.
|
Solution: If you are unable to modify the PROGID name, then it is possible to successfully install the extension using the regextn.exe file with the steps outlined below.
1. Save the extension files to a sub-older under:
C:\Program Files\AspenTech\Aspen HYSYS V7.1\Extensions
2. Save the regextn.exe to the same location.
3. Launch a command session and navigate to the mentioned folder.
4. Register the extension using the command
regextn.exe myExtension.DLL
Where myExtension.DLL should be replaced with the actual name of the extension you want to register.
Keywords: HYSYS Extension, Registration
References: None
|
Problem Statement: Dynamic Extensions - a possible alternative to User Variables for speed critical applications
|
Solution: It is possible to use User Variables in Aspen HYSYS Dynamics mode, either by adding DynPressureFlowPreStep() or DynCompositionPreStep() events to fire the code every pressure or composition step, or using a VariableChanged() event procedure to respond to changes in the value entered into the User Variable.
In Dynamics mode, Aspen HYSYS will call the code very frequently, since the User Variable code is interpreted each time it is run, it can negatively affect the speed of the model.
Aspen HYSYS Unit Operation Extensions can be coded to run in both Steady State and Dynamics modes. Since the code in an Extension is compiled, it can often be more efficient, and hence faster, than a User Variable. The development time for a Dynamic Extension compared to a User Variable is slightly longer, since more Extension infrastructure code is necessary. Additionally, some work is needed to develop a simple interface and a Visual Basic compiler is required. The majority of the code in a User Variable that does the actual calculations can be reused with relatively minor changes.
ThisSolution introduces the basics of Aspen HYSYS Steady State and Dynamic Extensions in sufficient detail so that a simple example User Variable can be converted into a simple Dynamic Extension. It is assumed that the reader is familiar with working with User Variables and understands the basics of Extension creation (i.e. creation of an edf file to define the interface, and a Visual Basic project to contain the code). Full details of creation of Steady State and Dynamic Extensions are given in the AspenTech training courses EC1015 (Developing Extensions For Aspen HYSYS) and EC1014 (Developing Dynamic Extension Unit Operations For Aspen HYSYS). Notes and examples for these courses can be downloaded from the Training section of the AspenTech website. Additionally, details of the creation of Steady State Extensions can be found in the Aspen HYSYS Customisation Guide manual. The Sample Macros and Extensions \ Unit Operation Extensions section of the Aspen HYSYS Knowledgebase at support.aspentech.com contains several example Extensions.
Procedures required in Extensions
Every Aspen HYSYS Steady State Unit Operation Extension requires the following procedures:
Initialize(), Runs each time the Extension is added to the flowsheet, or a case containing the Extension is recalled. Commonly used to link the variables defined in the Extension definition file to variables within the Visual Basic code. The Initialize() procedure MUST return the current Aspen HYSYS version number (there is a specially defined constant that makes this easy)
Execute(), Runs each time the Aspen HYSYS solver attempts to solve the Extension
Additionally there are several optional procedures
VariableChanged(), Fired whenever values of the Extensions variables changed. Often used to respond to the user changing values in the interface. This procedure works in both Steady State and Dynamics mode.
StatusQuery()
VariableChanging(), ...
In order for an Extension to work in Dynamics mode it MUST also implement the following procedures:
DynInitialize(), The Dynamic equivalent of Initialize()
InitializeSystem(), Runs each time the Integrator starts
NumberOfFlowEquations()
NumberOfPressBalEquations()
NumberOfFlowBalEquations()
NumberOfGeneralEquations(), Tells the pressure flow solver how many equations the Extension contributes. For simple Extensions this can be zero in all cases.
PreProcessStates(), Called at each step of the integration just before Pressure Flow Solver starts to solve the set of equations.
PostProcessStates(), As above except runs just after the Pressure Flow Solver solves the set of equations
StepEnergyExplicitly(), Called each time the solver does an energy calculation step
StepCompositionExplicitly(), Called each time the solver does a composition calculation step
There are several other optional procedures for Dynamic Extensions.
The Energy and Composition procedures run, by default, every 2 and 10 Integrator time steps. This can be changed on the Integrator control panel (Simulation ? Integrator menu option)
In order to make code execute whilst the dynamic solver is running it is simply a matter of placing the code within the appropriate procedure (PreProcessStates, PostProcessStates, StepEnergyExplicitly or StepCompositionExplicitly).
Syntax Differences
The VB syntax used in Extensions and User Variables is exactly the same. The main differences in the code lie in the objects used to gain access to the Aspen HYSYS object hierarchy and the variables used to display values on the interface.
For User Variables the objects ActiveObject and ActiveCase return Automation objects for the parent object that the User Variable is attached to (object type depends on the parent object), and the case (An object of type SimulationCase). For Extensions the main way into the Aspen HYSYS object hierarchy is via the Container object (of type ExtnUnitOperationContainer) that is passed to the Initialize() procedure. This allows access to the case, the flowsheet and to variables defined within the Extension interface.
User Variables have another object: ActiveVariableWrapper, which via the Variable property allows access to a RealVariable for the User Variable. This can be used to write results or read user entered values. It is possible to access the values of other User Variables on the same object (e.g. to write extra results or provide extra parameters) via the GetUserVariable() method of ActiveObject. For Extensions it is first necessary to define variables in the edf file, these can then be accessed via the FindVariable method of the Extension Container object.
Code Reuse
Consequently a lot of the code that actually does calculations can be used without any changes. Apart from introducing the extra infrastructure required for an Extension (e.g. Initialize(), DynInitialize(), ?), the other changes that must be made are in the sections where access is made into the object hierarchy and when values are read from / written to the interface.
Steps required to convert a User Variable to a Dynamic Extension
There are several steps required to create a Dynamic Extension that duplicates a User Variable:
Using the Extension View Editor, design a simple Extension interface to allow information to be entered and results to be displayed. Create variables to hold these values.
Create a VB dll project that implements the necessary procedures to call the modified User Variable code and to interact with the interface.
Modify the VB code from the User Variable to interact with the variables defined in the edf and referenced in the Initialize procedure.
Call the converted User Variable code from one of the Dynamic procedures.
Compile the Extension dll and register it in Aspen HYSYS.
Example
The simple example attached to thisSolution includes a User Variable ('Input') that takes the value entered, multiplies it by ten and writes this value into another User Variable ('Output'). The User Variable is attached to the spreadsheet 'SPRDSHT-UVs'. The code that does the calculation and interacts with the User Variable values is in a separate procedure ('TheCode') which can be called from either VariableChanged(), DynPressureFlowPreStep() or DynCompositionPreStep(). Another spreadsheet ('SPRDSHT-IO UV') is used to drive the User Variable. This imports the flow rate from a stream in the model and exports it to the User Variable. A transfer function is set to oscillate the stream flow so that the User Variable can be seen to be working.
The functionality of the User Variable is also implemented in a Dynamic Extension. This has a simple interface with two defined variables 'InputVar' and 'OutputVar' accessed via a matrix widget. The accompanying VB code has an Initialize() procedure that references these two variables and links them to two VB variables: 'hyInputVar' and 'hyOutputVar'. As in the User Variable there is a procedure 'CalculateValues' that does the calculation. This is called by Execute() and PostProcessStates() in the compiled code, but this can easily be modified.
There is another spreadsheet 'SPRDSHT-IO Extn' that does the same job as 'SPRDSHT-IO UV' except exporting to the Extension variable.
As well as the Extension source code the compiled dll is also attached. All the attached files should be extracted to a convenient directory and then the dll should be registered on the Extensions tab of the Preferences window in Aspen HYSYS (Tools ? Preferences menu option).
Speed Increases Possible
By ignoring the Extension and the IO spreadsheets it is possible to see how the integration speed (Real time factor) is affected. In a test by the author comparing the Dynamic Extension with the code being called in the PostProcessStates() procedure and the User Variable with the code being called in the DynPressureFlowPreStep() procedure, the Extension was found to be 1.5 times faster.
For User Variables with more code the speed increase would be expected to be larger, as the advantage of running compiled code vs. interpreting it becomes larger. Speed increases of 4 to 5 times have been seen in such circumstances. If the same User Variable is used multiple times in a large Dynamic model this speed gain would be multiplied.
Conclusion
Whether the additional effort to develop a Dynamic Extension can be justified obviously depends on the effect of the User Variable on the model speed. For complex or frequently used User Variables, transitioning to a Dynamic Extension is an option worth considering.
Note
The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use of these examples. We invite any feedback through the normal support channel at [email protected].
Keywords: User Variables, Dynamic Extensions
References: None
|
Problem Statement: When the “All variables” table for any type of blocks or streams is openend, the Value and Spec Attributes (columns) are missing. How can I fix this issue?
|
Solution: When some columns are not shown in the table it can be because the value was not selected to be displayed in the default specification when opening Aspen Utilities Planner or other ACM family products.
Firstly one has to check if the variables are selected. To do that, right click on the open table and select Properties (or a shortcut Alt+Enter), then the Edit Properties Table will be opened. In this table, check if the appropriate attributes are selected in the right side column, as show in the screenshot below:
If the value is not selected, then move it from the Available Attributes to Selected Attributes Column and click OK.
If you notice that the Attribute is selected, but is not visible in the Table, then open another ACM family product – it can be Aspen Custom Modeler or Aspen Adsorption, and check if the same issue was noticed. If the same problem is present in other products, do the following steps:
1. Open the registry editor (regedit.exe in a Windows search programs and files)
2. Go to HKEY_CURRENT_USER| Software| AspenTech| QuickTable| <version_number_for_example:30.0>| AttributeColWidths and check in the Data column if the value for missing attributes are 0, like in the screenshot below:
3. Right click on the Name (Lower in this example), and select Modify
4. Enter a Decimal number, for example 800, and click OK
5. Close registry and restart Aspen Utilities Planner – the issue should be fixed.
Note that modification of the registry is not recommended, that is why it is important to make sure that this is exactly the issue which is described above, before making any changes.
Keywords: missing attributes, missing columns,
References: None
|
Problem Statement: As there is no facility in HYSYS to get the list of all the components (associated with a fluid package in a given case) and their properties, how do I get the components (list) and their properties from HYSYS?
|
Solution: The attached Excel macro prints all the components (associated with the first fluid package of the selected case) and their properties (Critical Pressure (kPa), Critical Temperature (C) and Accentricity) to the excel sheet. Other properties can be included in the list by editing (adding a line) the code in module Module1. Component list (and their properties) associated with other fluid packages (other than the first one) can also be obtained by editing the code a little bit.
Steps to follow:
Open the attached Excel file and click on the RUN THIS MACRO button.
File Open property view appears. Select the file name and click OK.
The components (list) and their properties are printed on the Excel sheet (Sheet1).
To enter Microsoft Visual Basic environment, press ALT + F11. Edit/modify the code in module Module1.
Keywords: Component list, properties, OLE
References: None
|
Problem Statement: When I try to import variables from the PIPESYS unit operation extension into the Aspen HYSYS Spreadsheet, the nomenclature is very confusing. Which are the variables that can be imported from PIPESYS to the Spreadsheet in Aspen HYSYS?
|
Solution: Since PIPESYS is a third party extension, when the Aspen PIPESYS unit operation is selected in the Spreadsheet in Aspen HYSYS, there are just a few variables that are enabled to be imported from the available variable list.
From these variables, the ones that are truly accessible are those used in the summary section of the output report.
The summary section variables are:
1. g_SumUpstreamPress
2. g_SumUpstreamTemp
3. g_SumDownstreamPress
4. g_SumDownstreamTemp
5. g_SumPressLoss
6. g_SumFrictionLoss
7. g_SumHydrostaticLoss
8. g_SumKineticLoss
9. g_SumFacilityLoss
10. g_SumAvgPressGrad
11. g_SumTotalLiqHoldup
12. g_SumTotalLinePack
13. g_SumPipeVolume
14. g_SumHeatLoss
If other variables than the above are imported you may need to check if the value is being updated once the calculations change. If it is not, you can refresh a report including this variable in order to update it.
Keywords: PIPESYS, variables, spreadsheet, extension
References: None
|
Problem Statement: How Gas Turbine Air temperature and Humidity correction are calculated in Aspen Utilities?
|
Solution: The HumidityCorrection is calculated using the following equation :
HumidityCorrection = Humidity*K1Humidity + k2Humidity ;
where K1Humidity and K2Humidity are constants
The Air Temperature correction is calculated as :
PowerTCorrection = (TAirin-Tref)*K1Power + k2Power;
where K1Power and K2Power are constants
These correction factors are used to calculate the actual power from the power computed from the performance curves :
Power_A = Power_C * PerFact * PowerTCorrection * HumidityCorrection + PowerAugmentation + PerformanceCorrection;
where Power_A is the actual power and Power_C corresponds to the value on the performance curves.
Keywords: Humidity, Gas Turbine, Air Temperature
References: None
|
Problem Statement: Can HYSYS calculate interfacial tension between two liquids?
|
Solution: HYSYS does not calculate the interfacial tension between two liquid phases. HYSYS does not do this because there is not, to our knowledge, a good scientific (or even engineering) understanding of this phenomenon. If you have data or a correlation for some specific system, it would be easy to implement that as a user property (see Simulation Basis Manager manual for more details regarding User Properties). If you have no data, using the difference between the surface tension in the first phase and the surface tension in the second phase as an approximation is probably the best you can do.
Keywords: interfacial tension
References: None
|
Problem Statement: Can I check if a column has converged using Automation?
|
Solution: Yes, the ColumnFlowsheet object has a boolean property (CfsConverged) which can be checked to see if the column has converged. The code example below illustrates this.
To use the code below open up HYSYS with any case that contains a column, paste the code into the VBA editor in Excel, set the code to reference the column name, make a reference to the HYSYS type library (Tools ...
Keywords: None
References: s menu option in the VBA editor) and run the procedure.
Public Sub IsColConvergedExample()
'
'Description: Demonstration of using CfsConverged property of the ColumnFlowsheet object
'
'Declare Variables
|
Problem Statement: How do I model a gas turbine in HYSYS?
|
Solution: The attached HYSYS case demonstrates how to model a gas turbine in HYSYS.
In the attached model, the combustion process is simulated using a Gibbs equilibrium reactor. The air-fuel ratio (mass flow of stream Air divided by the mass flow of stream Combustibles) is adjusted to fix the turbine feed temperature at 1100 C.
If desired, the Gibbs reactor can be replaced by a conversion reactor if sufficient data is available for the combustion reactions.
PS - For some reason the case crashes in HYSYS 3.4 (build 6035) while opening. Works fine in HYSYS 2004.
Note
The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use of these examples. We invite any feedback through the normal support channel at [email protected].
Keywords: gas turbine, Gibbs reactor
References: None
|
Problem Statement: Is therminol included in HYSYS component library?
|
Solution: The heat transfer fluids known as therminols can be found as THEOLs, e.g. THEOL-55, THEOL-75 in HYSYS component library.
Keywords: Therminol, Theols, heat transfer fluids
References: None
|
Problem Statement: What version of Aspen Plus is required with Aspen Utilities Planner 2004.2?
|
Solution: Aspen Utilities Planner 2004.2 will only work with Aspen Plus 2004.1.
Aspen Plus 2004.1 is found on the aspenONE 2004 update 1 and aspenONE 2004 update 2 media.
Keywords: compatible update
References: None
|
Problem Statement: What is the minimum amount of information required to characterize an oil in Aspen HYSYS?
|
Solution: The only information you need to provide is a distillation curve (TBP, ASTM D86, ASTM D1160, ASTM D2887, or EFV). If you do not have any distillation data then Aspen HYSYS requires two out of these three properties: Molecular Weight, Standard Density or Watson UOP K. From these properties Aspen HYSYS will calculate an average TBP distillation curve.
Of course the more information you provide to Aspen HYSYS the more accurate your model will be.
For more information on characterizing oils, please refer to the Aspen HYSYS Simulation Basis Manual.
Keywords: minimum, oil, characterize, characterise
References: None
|
Problem Statement: What is the temperature approach option in the equilibrium reaction, and how can it be used to modify the effluent composition from an equilibrium reactor?
|
Solution: The temperature approach option in the equilibrium reaction allows the user to adjust the equilibrium constant of a reaction by offsetting the temperature at which it is calculated. The approach value is an empirical adjustment that is used to modify the extent of reaction at equilibrium when the value of the equilibrium constant is not well established.
Using the temperature approach option offsets the effective temperature used to calculate the equilibrium constant depending on whether the reaction is endothermic or exothermic:
ln Keq = -DG/R(T - DeltaT) if the reaction is endothermic.
ln Keq = -DG/R(T + DeltaT) if the reaction is exothermic.
For a given reaction, a temperature increase will favor the reaction direction that absorbs heat (i.e. the endothermic pathway). In HYSYS, it is possible to identify if a reaction is endothermic by viewing its reaction heat. If the reaction heat is positive, the reaction is endothermic, if it's negative, the reaction is exothermic. Note that an endothermic reaction will become exothermic if you reverse the direction of the reaction.
In the following example:
CH4 + H2O <=====> 3CO + H2
The forward reaction (CH4 + H2O to produce 3CO + H2) is endothermic, hence the reverse reaction (3CO + H2 to produce CH4 + H2O) is exothermic. In HYSYS, if a positive DeltaT is specified as the temperature approach for this reaction, the CH4 composition in the product stream will increase. This is because the reverse reaction (producing CH4 + H2O) is being favored since the equilibrium temperature is effectively being decreased to T - DeltaT.
Keywords: DeltaT, equilibrium, reaction, approach, approach temperature
References: None
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.