question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: How do I find the mass or molar flow for a component on each tray in the column? | Solution: In Aspen HYSYS you can obtain a graphical display or tabular data for the components in the tray sections. This is available under Column Performance / Plots.
You first click Plots and then View Graph or View Table.
In both forms (Graph or Table), there is a button at the bottom left corner named Properties. This will give options for the components to display, flow basis and phase.
Keywords: Column, Performance
References: None |
Problem Statement: Is it possible to create a table in the flowsheet reporting properties reported in the Stream Analysis tools such as Envelope, Critical Properties, Cold Properties, etc.? | Solution: You can create a custom table to report any property of any stream in your simulation. To do this use the Data Tables option located in the Customize tab in the Ribbon.
Create a new table clicking on the Add button. When you look for your Stream Analysis variables, you can filter the search selecting the Analysis radio button located in the Navigator Scope Section. As Object, the Analysis will be shown, e.g., Envelope. Then select the variable(s) you want to report.
Finally, to locate the table on the flowsheet just select the Place on Flowsheet button and choose the Show as Table option.
Keywords: stream analysis, table, customize, flowsheet
References: None |
Problem Statement: How to delete the labels for the objects in the flowsheet. | Solution: If you would want to hide the labels for certain streams or unit operations on the flowsheet. You can select the concerned objects and then right click to select- Format Label- Hide Label as shown in the figure below.
Keywords: Format Label, Hide Label, formatting flowsheet
References: None |
Problem Statement: What do Higher and Lower dead bands mean in a Digital Control Point operation? | Solution: Higher and Lower Dead Bands allow you to specify the upper and lower deviation respectively of the threshold value.
The set point is accompanied with an adjustable differential gap or dead band value, this value allows small deviations to occur in the PV value without triggering changes to the OP state.
The following is an example of how the bands operate. Assume you have a Digital Point operation with the following parameters:
Parameter
Value
Threshold
100
Higher dead band
45
Lower dead band
20
OP is on when
PV>= Threshold
The following situations illustrates when the OP is turned on or off:
· Initial state: If PV value starts at 70 and OP is off, the OP stays off until the PV value rises above or equal to 145, than OP is turned on. Threshold + Higher dead band: 100 + 45 = 145.
· Intermediate state: If PV value rises and falls above value 80 and OP state is already on, then OP remains on. Threshold – Lower dead band: 100 - 20 = 80.
· If PV value falls below or equal value 80, OP is turned off.
Keywords: Digital Control Point, controller, dead band, threshold
References: None |
Problem Statement: What is the default location of preference file? | Solution: The preference file is stored in C:\Users\username\AppData\Roaming\AspenTech
There is a file specific to each version and it is of format Aspen HYSYS Vxx.PRF
Keywords: preferences, file location
References: None |
Problem Statement: The status of the Hyprotech SQP Optimizer indicates ‘violated constraints’, as shown below:
However, the current value of the process constraints functions is above the minimum specified in the Derivative Analysis tab. | Solution: One of the reasons why this message can appear is because the user defined their constraints (in the Constraints/Objective Function page of the Derivative utility) as inequalities of the type
Minimum < Current Value < Empty
As a workaround, the user should specify a maximum value for the process constraints, even if only a lower bound is required. If unsure, the user can choose a relatively large number for the maximum. This will be addressed in a future release.
Keywords: Optimizer, Constraint, Violated, SQP, Derivative
References: None |
Problem Statement: How do users export the component's composition from the spreadsheet to a stream? | Solution: First of all, users have to input the composition data into spreadsheet and make them exportable. This means the data in the spreadsheet should be a calculated data. Usually, user can make another column and have the exactly same data by using formula.
Secondly, users have to export each number onto the target stream. Remember all the composition in the stream should have a mapped number in spreadsheet.
Thirdly, after users export all the number from spreadsheet to the stream, users have to ignore the spreadsheet and unignore the spreadsheet to trigger the action.
Keywords: Export composition, Spreadsheet, Stream component
References: None |
Problem Statement: How do I add a new color scheme? | Solution: If there is a necessity to add a new color scheme for your flowsheet. You can follow the steps shown below.
1. As shown in the figure below go to the Flowsheet/Modify Tab and from the Conditional Formatting drop down select <Add New>.
          Â
2. Once you select the <Add New>, Select Query Variable window will show up to select Variable.
(In this example, Methane Mole Fraction is considered as the criteria).
3. After selecting the variable that will be considered as the criteria for color scheme. Conditional Formatting window will show up to specify the range.
You can also select the number segments you want to divide the color range (Maximum is 7 segments). If you prefer you click on Auto-Set Ranges and the program will set the range.
(In this example, Auto-Set Ranges is selected)
4. After setting up the range, you can view your flowsheet now with legend (make sure the ‘Display Legend’ is checked).
          Â
Keywords: Colour Scheme, Conditional Formatting, Material Stream Colour
References: None |
Problem Statement: Is there a way to display fraction digits in a user variable? | Solution: Yes, it is possible to modify the decimal points displayed in a User Variable.
1. Go to the User variable you want to modify and open the window where you edit the code. You’ll see the Units cell. By default is Index, but change it to User.
2. Open the Simulation Options window by going to File tab | Options. Select the Units of Measure option. At the bottom you’ll see the Variable Formats section. Look for the User variable
3. Double click on the User variable; The window Format Editor appears. Select the Fixed Decimal Point option and define the number of decimal digits you want to display.
Click on OK, and now you should see the number of the User Variable in the format you just defined.
Keywords: User variable, Units of measure, Variable Format.
References: None |
Problem Statement: How to add case study results to a flowsheet. | Solution: The steps to place your case study results on Flowsheet.
1. Go to a Case Study. Select the results (each row separately) and right click. Click Send to / Select Data tables / Create New.
2. You can continue this for all the different rows.
3. Then go to the Navigation Panel on the left- Go to Data Tables Folder.
4. The Created Data Tables will be there. Modify the name for your data tables.
Â
5. Go to each Data Table and select Place on Flowsheet.
Keywords: Case Study Results, Data Table
References: None |
Problem Statement: How to create a template for model summary? | Solution: If you wanted to create a template for reporting via Model Summary you can select manage templates option from the drop down menu for template.
Then select new to create a new template.
Choose the required variables to be included and then click ok.
It will be saved as new template. Please give a name to the template created.
You can also export it and save it as .sgtxml file so that you can import this template for other simulations.
Once the template is created it will be now available as one of the options.
.
These steps can be followed in Aspen Plus.
Keywords: Model summary, template, Summary Grid Template Files (.sgtxml)
References: None |
Problem Statement: Why doesn't the Air Cooler solve when Air Inlet and Product Temperatures are specified, but the Air Flow is not specified?
What parameters are required to solve Air Cooler exchanger models? | Solution: In Aspen HYSYS, the Air Coolers are simple exchanger models. When the Air Flow rate and the Air Outlet Temperature are not specified, Aspen HYSYS will not solve as there are multiple solutions associated with this combination. Air Coolers use a simple heat balance calculation to solve where the heat load on the tube side is known and must be equal to the heat load of the air side (assuming no heat loss). In order to get to the target heat load, any number of combinations of temperatures and air flow rates can be obtained. Therefore, when Air Flow rate and Air Outlet Temperature are not specified, there will be a degree of freedom missing and lead to the Air Cooler not being solved.
Keywords: Air Cooler, Air Inlet and Outlet Temperatures
References: None |
Problem Statement: Why does the UA value not remain constant when we click the "Transfer UA to End Point" in Rigorous Shell & Tube tab? | Solution: That is because the Log Mean Temperature Differences (LMTD) values shown in the performance tab are calculated differently for a simple end model compared to simple weighted model and EDR Rigorous models.
The LMTD is corrected for weighted models and Exchanger Design and Rating (EDR) rigorous model and not corrected for simple end point models. When converting from EDR to Simple End Point, HYSYS wants to make sure the resulting process conditions are similar, so it modifies the UA to account for the fact that LMTD is not corrected in the simple end point model.
The accuracy of the results wont be affected as the final outlet temperature will be the same as calculated by EDR.
Keywords: Transfer UA to End Point, LMTD, UA
References: None |
Problem Statement: How do I customize the Fly by window in Aspen HYSYS? | Solution: When a user hovers over the stream in Aspen HYSYS this displays the values of the variables specified in the Fly by setup. The default variables are Temperature, Pressure and Molar Flow. The default variable can be changed in the “File | Options” in Aspen HYSYS. Select “Simulation” in the “Options” page and move to the Tool tips section as shown below.
Now click on “Specify Fly by”. This will open a window where you can select the variables wish to display for the material stream and energy stream.
Keywords: Fly by, Variables
References: None |
Problem Statement: How do I export data to Microsoft Excel using the Hypotheticals Manager? | Solution: In version 8.6 and 8.8, you can select desired data and use Copy-Paste functionality ( Ctrl C+Ctrl V). Another way of doing this, using "print Datasheet" functionality. Below is how you can do it:
1) Open Hypothetical manager and right-click to select “Print Datasheet�
2) Uncheck all but “hypotheticals� and check “Text to file� and “Delimited� box under available data blocks window. Click Preview.
3) Click “print to file� to save it in *txt format
4) The file can then be opened using Excel. Ensure that you specify 'All Files (*.*)' or 'Text Files (*.txt)' in order to see this file when opening from Excel.
5) You don’t need to change anything in the wizard, just press “next�. In Page 2, make sure the delimiter is “comma� and then Finish.
Keywords:
References: None |
Problem Statement: How to configure the Auto Upload Tool V8.8 with the Collection Server option | Solution: This knowledge base article provides the configuration procedure for the Auto-Upload Tool V8.8 (AUT) with the Collection Server option. The Collection Server option can be used when a firewall does not permit a user to configure the Auto-Upload Tool with HTTPS, EMAIL or SFTP option.
Please follow Solution Article 143599 if you want to configure the Auto-Upload Tool V8.8 (AUT) with HTTPS, EMAIL or SFTP option
To configure the Auto-Upload Tool V8.8 (AUT) with the Collection Server option, the user will need to configure the AUT on the License Server to upload the Usage logs to a Shared Drive, then on a Client machine, the user will need to configure the AUT to collect the logs from the Shared Drive and send it to AspenTech automatically.
v To configure AUT on the license server, please follow the below steps:
1. Go to Start > All Programs > AspenTech > Aspen SLM and run the aspenONE SLM License Manager tool
2. In the aspenONE SLM License Manager, click the Configure Usage Logs button to open the AUT.
3. At the Welcome screen, provide a Admin Email Address and a Company Email Domain to receive a confirmation email once AspenTech has received the usage log.
4. Select Use Custom Settings and click Continue.
5. Custom Configuration (Step 1 of 2) setting:
· SLM System Name will automatically populate by reading your license file.
· Frequency needs to be select, AspenTech recommends a Weekly upload
· Privacy Level setting:
a) None: this is the default option
b) Medium: User information will be converted into unidentifiable unique names.
(Examples: User name “John” will be converted to “x3y4ss”. Machine name “TestPC1” will be converted to “g74sr2”. IP Address “123.123.123.123” will be converted to “es4.rts.p3t.au2”.)
c) High: User information will be converted into masked names. This option will require you to use the same mapping file if you have two or more SLM Servers.
(Examples: User name “John” will be converted to “user1”. Machine name “TestPC1” will be converted to “machine1”. IP Address “123.123.123.123” will be converted to “ip1.ip2.ip3.ip4”.)
· UserMap File location needs to be the default as shown in the wizard.
· Archive Folder location needs to be the default as shown in the wizard.
6. Custom Configuration (Step 2 of 2) settings:
· Select Upload Method as To Collection Server
· Client Mode should be Network Share
· Shared Folder Location: Type the shared folder location where you want to collect all the Usage logs (ZIP files). Share folder location should start with \\ (two back slash).
· User Name: Username along with the domain should be specified.
· Password for the given username should be specified.
· Click Continue button.
7. Click TEST Upload to verify the Shared Folder is accessible with the given credentials.
8. Once a successful message is received, please click the Finish button
v To Configure a Client machine to Collect logs from the Shared Drive and send them to AspenTech, please follow below steps:
1. Go to Start > All Programs > AspenTech > Aspen SLM and run the aspenONE SLM License Manager tool
2. In the aspenONE SLM License Manager, click the Configure Usage Logs button to open the AUT.
3. At the Welcome screen, provide a Admin Email Address and a Company Email Domain to receive a confirmation email once AspenTech has received the usage log.
4. Select Use Custom Settings and click Continue.
5. Custom Configuration (Step 1 of 2) setting:
· SLM SYSTEM Name will be automatically populated by reading your license file.
· Frequency needs to be select, AspenTech recommends a Weekly upload
· Privacy Level setting:
· None: this is the default option
· Medium: User information will be converted into unidentifiable unique names.
(Examples: User name “John” will be converted to “x3y4ss”. Machine name “TestPC1” will be converted to “g74sr2”. IP Address “123.123.123.123” will be converted to “es4.rts.p3t.au2”.)
· High: User information will be converted into masked names. This option will require you to use the same mapping file if you have two or more SLM Servers.
(Examples: User name “John” will be converted to “user1”. Machine name “TestPC1” will be converted to “machine1”. IP Address “123.123.123.123” will be converted to “ip1.ip2.ip3.ip4”.)
· UserMap File location needs to be the default as shown in the wizard.
· Archive Folder location needs to be the default as shown in the wizard.
6. Custom Configuration (Step 2 of 2) settings:
The user has 3 options to send the Usage logs to AspenTech, HTTPS or EMAIL or SFTP. The user can choose any of these options.
I. Upload Method: HTTPS (Recommended)
· Check the box Use this machine as collation server.
· Server Mode: Network Share
· Shared Folder Location: Map the share drive folder on the client machine and then browse to the shared drive location.
· Click Continue.
II. Upload Method: EMAIL
· SMTP Server Name: Type the SMTP server name
· Email: Type Admin Email Address
· Domain/Username: Type User name with Domain
· Password: Click Change and type password for specified User name.
· Check the box Use this machine as collation server
· Server Mode: Network Share
· Shared Folder Location: Map the share drive folder on the client machine and then browse to the shared drive location.
· Click Continue
III. Upload Method: SFTP
· Please email [email protected] to request for the SFTP encryption key.
· Once you have received the key, save it on the client machine.
· Select the Browse button to point ACC key received from Customer Care Team.
· Check the box Use this machine as collation server
· Server Mode: Network Share
· Shared Folder Location: Map the share drive folder on the client machine and then browse to the shared drive location.
· Click Continue
7. Click TEST Upload to verify the Shared Folder is accessible with the given credentials.
Once a successful message is received, please click the Finish button
Keywords: AUT
Auto Upload Tool
Usage log
Collection Server
Upload
ALC
Usage Report
References: None |
Problem Statement: How can I remove an old server from the server list in the SLM License Profiler? | Solution: This solution will provide you with instructions on how to remove an old license server from the License Server drop down list in the SLM License Profiler.
To remove the old license server, follow these steps:
1) Open the Windows Registry by clicking Start Menu > Run and type regedit.exe. Click OK.
2) Navigate to the following folder: [HKEY_CURRENT_USER\Software\ASPENTECH\SLM\SLM LICENSE PROFILER\HISTORY\SERVERS]
3) Right-click the server that you wish to delete and select Delete from the context menu.
4) Close the Windows Registry.
Keywords: SLM, License Profiler, License Server
References: None |
Problem Statement: How do I ensure that SLM logging is enabled and working properly? | Solution: This knowledge base article provides a checklist that can be used to ensure that SLM logging is enabled and working for both Auto-Upload Tool (AUT) submission and manual submission methods.
Auto-Upload Tool (AUT) submission is the recommended and best method for submitting usage logs. The latest AUT can be installed from KB article 144316.
Auto-Upload Tool (AUT) Submission
1) Is my environment variable set correctly?
· Follow the folder path in the environment variable (LServOpts).
1. Login to SLM license server using Administrator account.
2. Right click on the "My Computer" icon and select "Properties".
3. Click on "Advanced" tab. Choose the "Environment Variables" button.
4. Under the bottom box called "System Variables", look for LServOpts and double click on the LServOpts variable name to locate the path where the logs are being generated.
· If the LServOpts environment variable has not been set correctly or created at all, please do the following:
1. Check the C:\Windows\System32 folder for a file called “lservsta”. If found, please manually send this file by following the directions under “How do I manually send the usage logs?” and proceed to create a new environment variable with the following information:
Name: LServOpts
Value: –l "C:\Program Files(x86)\AspenTech\SLMServerLogs\lserv.log" -z 2m -lfe 2
(if you are using a 32-bit machine, the value will be –l "C:\Program Files\AspenTech\SLMServerLogs\lserv.log" -z 2m -lfe 2)
2. Go to Start, then Run; type in “services.msc”, then click OK; find the service called “Sentinel RMS License Manager” and restart the service to enable the logging.
3. Check the location designated by the environment variable that was just created to see if logs files are now being generated.
2) Is my AUT configured properly to send the usage logs automatically?
· On the Schedule tab in the ALC Configuration Tool, verify that your license’s System Name is automatically displayed in the Server Name box. The System Name will be automatically read from your license file. The AUT will not upload the log files if the System Name is not detected. If the Server Name box is empty then your license file likely cannot be located on the SLM server. Please see KB article 135098 to fix this issue.
· For HTTPS* option, ensure the following requirements are met:
If you have installed V8 or later of the Auto-Upload Tool (AUT) you do not need to perform any extra configuration after installation. Usage log files will automatically upload every 30 days using a secured, 128-bit HTTPS connection.
*HTTPS is the recommended AUT protocol for submitting logs. However, if your company cannot use the secured HTTPS, you may select to use secure FTP or email to send the log files.
· For SFTP option, ensure the following requirements are met:
1. Submit an incident with AspenTech Support to request an SFTP key (also known as a Public/Private Encryption key). It will be generated within 2 business days.
2. Verify that your company’s firewall has TCP/IP Port 22 open, so AUT can access AspenTech’s SFTP server.
3. On the SFTP tab, verify that the SFTP Server is set correctly to: alcftp.aspentech.com
· For email option, ensure the following requirements are met:
1. In the SMTP box, type in your SMTP address.
2. Verify that your company’s firewall has TCP/IP Port 25 open, so AUT can send the email to AspenTech.
3. In the Your Email configuration section, enter the following:
a. Email Box (use this format: [email protected])
b. User name (use this format: MyDomain\MyUserId)
c. Password (user’s password for the email box)
3) Are the ports required for AUT submission open in my firewall?
The Auto-Upload Tool enables automatic upload of software usage logs to AspenTech using one of the following protocols and required ports:
Log Transmission Protocol
Required Open Port
HTTPS
443
Secure FTP (SFTP)
22
Email
25 (or SMTP server specific port)
In order for the AUT to work with one of the selected protocols, please ensure that your company’s network allows traffic on the corresponding port.
Manual Submission
1) Is the usage log Windows Environment Variable set correctly?
· Follow the folder path in the Environment Variable (LServOpts).
1. Login to SLM license server using an Administrator account.
2. Right click on the "My Computer" icon and select "Properties".
3. Click on "Advanced" tab. Choose the "Environment Variables" button.
4. Under the bottom box called "System Variables", look for LServOpts and double click on the LServOpts variable name to locate the path where the logs are being generated.
· If the LServOpts environment variable has not been set correctly or created at all, please do the following:
1. Check the C:\Windows\System32 folder for a file called “lservsta”. If found, please manually send this file by following the directions under “How do I manually send the usage logs?” and proceed to create a new environment variable with the following information:
Name: LServOpts
Value: –l "C:\Program Files(x86)\AspenTech\SLMServerLogs\lserv.log" -z 2m -lfe 2
(if you are using a 32-bit machine, the value will be –l "C:\Program Files\AspenTech\SLMServerLogs\lserv.log" -z 2m -lfe 2)
2. Go to Start, Run, type in “services.msc”, click OK, find the service called “Sentinel RMS License Manager” and restart the service to enable the logging.
3. Check the location designated by the environment variable that was just created to see if logs files are now being generated.
2) How do I manually send the usage logs?
· Please email the usage logs to [email protected] along with a copy of the appropriate AspenTech license file.
Note: The mailbox limit is 10 MB. If your log files are bigger than 10 MB, please break up the files into multiple emails with smaller attachments, or send an email to Customer Care asking them how they would like you to send them the files.
Keywords: Auto-Upload Tool
Usage Logs
Logging
SLM
Environment variable
LservOpts
References: None |
Problem Statement: When we run loads.exe and then click on add, we get the following error: "unable to add the sentinel RMS license manager service to the system service registry. Is the service already installed? Error (431)".
How do we resolve this? | Solution: 1. Use the?? "Remove" option when running loads.exe found in C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT.
2. Run loads.exe again and use the "Add" option. The sentinel RMS license Manager Service should be installed.
Keywords: Restart sentinel RMS license Manager Service, Error 431
References: None |
Problem Statement: What is the difference between SLM Version and Sentinel Version? | Solution: Sentinel Version – This refers to the version of the software development kit (SDK) used with the version of SLM Tools installed.
SLM Version – This refers to the version of the licensing DLL file (STRGXI2.DLL). This DLL file is stored in the following directory.
· 32bit OS: C:\Program Files\Common Files\AspenTech Shared\
· 64bit OS: C:\Program Files (x86)\Common Files\AspenTech Shared\
Keywords: sentinel version, slm version, what's the difference between slm and sentinel version?, slm tools
References: None |
Problem Statement: | Solution:
Keywords:
References: None |
Problem Statement: Can I restrict a client machine from opening more than one instance of an AspenTech product? | Solution: Currently, the License Manager does not have the functionality to limit or restrict the number of product instances that can be opened on a client machine.
Please note that each instance of the product that is open will consume tokens, if using a token license.
Keywords: Restrict
Share Limit
Reserve
Open Sessions
Multiple Applications
References: None |
Problem Statement: How do I check the current MTU size on the network? | Solution: AspenTech's network license server requires to have port 5093 on TCP and UDP open and the MTU set to 1500 (V8.8 and higher) or 7512 (V8.7 and below) for it to work as designed.
To verify your current MTU, run the following command from an elevated command prompt (run as administrator).
Type the following in the Command Prompt: netsh interface ipv4 show subinterfaces
it will retrieve the network information like this:
Keywords: MTU size, MTU
References: None |
Problem Statement: How to create a plot over time that shows the duration of time spent at specific token levels (not just peaks) from the Max Daily Token Usage Report data?
*The Max Daily Token Usage Report spreadsheet is one of the usage reports provided to customers through the AspenTech support website.
*If you do not know how to access the Max Daily Token Usage Report, please see KB article 145209 for instructions on how to access and download the usage reports from the AspenTech Support Website. | Solution: This knowledge base article explains how to use the raw data from the Max Daily Token Usage Report to create a plot over time that shows how long was spent at certain token usage levels (not just peaks). This will provide more insight into token usage behavior of the software users.
1) Add a column titled "Duration" to right of the "DateTime (UTC)" column on the Raw Data tab of the daily usage report.
2) In the first cell under the added Duration column (should be cell B2), type in "=H3-H2" and press Enter. This will subtract the timestamp at time A2 from the next consecutive timestamp at time A3 to give you the seconds that were spent at that token usage level in cell K2.
3) After clicking on cell B2, double-click on the black box on the bottom right corner of the cell to have all of the cells in the column filled the formula's calculation.
4) Click and drag across the column header letters to highlight columns A through K.
5) Click on the Insert tab from the top bar and then PivotTable. Click OK and the PivotTable will be created in a new tab of your spreadsheet.
6) From the PivotTable Field List, click and drag the following fields to the appropriate areas: "DateTime (UTC)" to under Row Labels, "Duration" to Values, "Total Tokens (Log)" to Values.
7) Click on the down-arrow next to Duration under Values and then Value Field Settings from the pop-up menu. Click on Sum and then OK.
8) Click on the down-arrow next to Total Tokens (Log) under Values and then Value Field Settings from the pop-up menu. Click on Max and then OK.
9) On the top bar under PivotTable Tools, click on Options and then PivotChart. This will create graph plot based on the data in the PivotTable.
10) Click on the gray drop-down arrow on the top right of the Row Labels column of the PivotTable to select which dates you like to only have show in the table and graph. Using the Date Filters from the drop-down menu is the easiest way to configure the date range that you would like to view.
Keywords: Daily usage report
token usage
token duration
token levels
usage analysis
References: None |
Problem Statement: How can I check my license expiration date with the SLM License Profiler? | Solution: To use the SLM License Profiler to check the expiration dates of the licenses:
1. Start the SLM License Profiler by clicking Start | Programs | Aspen Tech | Common Utilities | SLM License Profiler. The SLM License Profiler dialog box is displayed.
2. Select either a license server or a local license file.
· To select a license server, select a server name from the License Server dropdown list or type the name of the server in the License Server box. You may click the Refresh Server Listing button at any time to refresh the list of license servers configured on the local computer. This is useful in the event that the SLM Configuration Wizard was used to change the configuration of one of the servers on the local computer.
· To select a local license file, select Local License File in the License Server dropdown list. The License File field is enabled.
3. If you selected a license server in step 2, go to step 4.
· If you selected Local License File in step 2, type the full path and filename of the license file in the License File box or browse for a license file.
4. Click Load Information to query the license server or license file for the System Name, Company and Locking Info information.
5. Click View Licenses to display all available license information that was found on the license server or in the license file.
6. Check the expiration date in the “Expiry Date” column. The date will in the format DD/MM/YYYY. In the example below, the expiration date is 12-July-2016
Note: if you don’t have the SLM License Profiler installed, please follow the instructions in in KB 141145.
Keywords: SLM
SLM License Profiler
License
Expiration Date
References: None |
Problem Statement: After installing a license server, attempting to load License Information in SLM License Profiler will throw an error message similar to this:
"Could not find License Server "(Server IP)" or profile information for "(Server IP)". Error 18: The license for this product or feature could not be found. Be sure you are pointing to the correct license file or the license server is configured properly." | Solution: Even though the license file is copied to the correct folder you need to remove the .SLF extension off the name of the file.
1. Open Windows Explorer and browse to the usual location where the network license should be saved:
C:\Program Files (x86)\Common Files\SafeNet Sentinel\Sentinel RMS License Manager\WinNT
2. Use the Organize button and select Folders and Search options | View tab and then uncheck "Hide extensions for known file types". Click OK.
Now all files will be displayed with their full name regardless if they are a known file type or not. Look for the license file named LSERVRC.SLF and rename it to remove the .SLF extension.
Restart the Sentinel RMS License Manager service for the changes to take effect and try loading the license again using the SLM License Profiler.
Keywords: LSERVRC
Sentinel RMS License Manager
Error 18
References: None |
Problem Statement: What Engineering products use which license keys? | Solution: Attached (Product Names vs License Keys.xlsx) is a list of the license keys that are used by the Aspen Engineering Suite (AES) and the associated Aspen products that will consume them.
Keywords: license keys
Aspen Engineering Suite
AES products
References: None |
Problem Statement: Are there any examples for Aspen Batch Distillation? | Solution: After installation of Aspen Batch Distillation application user can able to find examples in below path
C:\Program Files\AspenTech\Aspen Batch Distillation V7.X\Examples
Corresponding documentation reference user can see either in documentation DVD under Aspen Batch Distillation folder under help file which is attached
OR
Open Aspen Batch Distillation application then go to help then click on Aspen Batch Distillation Contents then expand Aspen Batch Distillation Example Simulations
Keywords: Examples, Tutorials, Help file etc;
References: None |
Problem Statement: Cannot add a steam stream in Petroleum Refining's petroleum distillation column. | Solution: In sample case “Petroleum Column” appears some steam inlet streams.
There is no way to add steam streams to the petroleum column any more. This is due to the way the architecture of the model has changed.
When RefSYS was originally created, the petroleum column was based on the HYSYS column with an option for a short cut model. Therefore, we had to support things like steam streams and reboiler duties.
Around V7.2 or V7.3, the petroleum column was changed to use the SCD from PIMS and there was no longer an option to use the rigorous column as the petroleum column, so there was no longer a need to specify steam or energy streams to the petroleum column.
For existing cases, we kept the streams, but for new cases they are not created and we do not have a way to create them.
The example case Petroleum Column.hsc was originally built before the change, so that is why it still shows steam streams.
Keywords: Steam stream, refsys, petroleum distillation column
References: None |
Problem Statement: What is the D2887 option inside the FCC reactor environment? | Solution: The D2887 option in FCC is implemented according to the API method. Users can't change it and when users select "Internal feed", it will always use the API conversion and transform it to TBP values. When users used the external feed, there are two options. If the API option is selected, the distillation data of external feed will be converted by the API method and then transformed to TBP values. If the TBP mass option is selected, the distillation data of the external feed will be directly used as TBP
Keywords: D2887, FCC
References: None |
Problem Statement: Where do I enter Light Ends data in Petroleum Assays? | Solution: In Aspen HYSYS V8.0, 8.2 and 8.3, Macro Cut Table of Petroleum Assays includes a particular section for Light Ends in Set Up tab (see below)
Since Aspen HYSYS V8.4 Macro Cut Table in Petroleum Assays was replaced by Aspen Assay Management. In this new interface, light ends information should be included in the Pure Component tab of the Input Assay window. In this tab click on the cell labelled Click to Add Cut to be able to enter this information.
Â
Keywords: Light Ends, Petroleum Assays
References: None |
Problem Statement: How do I find the Coversion of Hydrocracker products and how is the conversion calculated? | Solution: The hydrocracker product yields are available under the Results page as shown in the screenshot below.
The conversion is calculated as follows:
Conversion weight % = 100 x (light products + distillates) / feed mass flow rate
Conversion volume % = 100 x (light products + distillates) / feed volume flow rate
Note that adding all the the product yields (light products + distillates) may not match the conversion exactly. The small differences in the conversion balance is due to the internal tolerances for recycles in the hydrocracker model.
Keywords: Hydrocracker, Product Yields, Conversion
References: None |
Problem Statement: Why is the pseudo component representing the FBP of the assay reported as 700+ and not the values entered in the assay manager?
The assay has been imported into the Assay Manager and characterized normally. The crude standard cuts in the assay are given up to 1050 0C, but the Hypos generated cover the full spectrum only up to 700 0C. | Solution: The problem lies with the components list that has been used. The Hypos available in the component list do not go over the boiling point of 700 0C. Therefore the generated hypos are restricted to this boiling point.
The default component list that has been added should be replaced with the petroleumcomp1_extended components list (see screen shot) and then higher boiling point hypos available in this component list can become accessible. The petroleum extended can be accessed by clicking the import tab in the components form.
Keywords: ,
petroleumcomp1_extended, assay, hypos
References: None |
Problem Statement: How to access the specified heat of reaction in Aspen Batch Modeler for use in Aspen Simulation Workbook. | Solution: If you want to access specified heat of reaction variable in Aspen Batch Modeler for use in ASW , please do the following steps.
Step 1: Open c:\program files (x86)\aspentech\AMSystem v8.8\bin\OnSaveBatchsepScript.vb  using Notepad.
Step 2:Â Change
InvokeLibraryScript "BatchSep", "DeleteCustomRxnModels"
  to
'InvokeLibraryScript "BatchSep", "DeleteCustomRxnModels"
Step 3: Open the batch modeler file ,run the simulation, reinitialize, save and close.
Step 4: Find the DHRxnRef variable using variable find and create a table .
Step 5: Copy and paste the DHRxnRef variable from the table on the Organizer
Keywords: ASW , Heat of Reaction
References: None |
Problem Statement: How to collect fractions for each receiver during batch distillation simulation | Solution: You can refer to the example file in this solution to develop your own process. Here are the key steps for adding receivers and finding the results.
1. Add Receivers: Four (4) receivers are present in the attached simulation. Three of them work as Liquid receivers and one of them works as Vapor Receiver. In the screenshot below, 1 and 2 refers to receiver ID but not number of receivers.
2. Operating Steps: You have to add three separate steps, if you want to replace the receivers every 1 hour for 3 times. You can give the receiver name for each steps and Reflux distillate flow rate.
3. End condition: In each operating step, remember to give an end condition.
4. Key results: You can go to Holdup Summary Results and review fractions for each receiver.
Keywords: multiple receiver, collect material, Batch Modeler, fractions
References: None |
Problem Statement: Even though Aspen Batch Modeler V8.8 is installed, the Batch Modeler file opens in V8.4. Right-clicking and opening with the modeler V8.8 also doesn't open the file in V8.8.
The same problem applies to all the modeler products (ACM, Aspen Plus Dynamics etc.) | Solution: Please follow the steps below to set the version to V8.8
1. Go to computer’s start menu.
2. Right-click on Set Version- Aspen Modeler V8.8 under Aspen Tech/ Process Modeling V8.8
3. Click "Run as administrator"
4. A window pops up. Click "Yes" in the following window.
You will receive a message that the current version has been set to V 8.8, as shown below.
Keywords: Batch modeler, version issues, set version
References: None |
Problem Statement: There are several methods that can be used to calculate the values of RON and MON for a material stream defined completely from a component list, as a function of the individual component properties. This solution describes how to generate these values, and how to report them when the field for RON (or MON) appears as <empty> in the Properties menu. This issue also pertains to petroleum assays which have pure components from the databank included in its definition.
Related Knowledge Base solutions ID: 131735, 109286 and 109289. | Solution: To report the values of RON using different blending methods, first access the values of this property for the mixture/assay components. Open the component list shown in the panel for the defined fluid package in the Properties environment (click in ‘Edit Properties’ as shown below).
In the new window that appears, select the property from the list (e.g. RON (Clear)).
Now, define user properties (open ‘User Properties’ in the ‘Properties’ environment). Here, choose the basis on which the blending is done, and copy the values from the previous table (where all the RONs for pure components are listed). Then, duplicate this variable, changing only the blending method. You can create 3 variables, for example
RON Mass
RON Molar
RON Volume
Then in the simulation environment, these can be viewed in the stream menu, in the ‘Attachments’ tab, under ‘Analysis’. Create new user variable and view the results by double clicking in ‘User Property-1’ (change the basis in which composition is shown for the stream if values for the properties do not appear).
For this example, the results are as follows:
Comparing these values with the one shown in the stream ‘Properties’ tab, we can see that the latter value is calculated based on the a blending rule which uses the liquid volumetric fractions as basis.
Notes and tips:
(a) Example screenshots generated with octane_example.hsc file given in Solution ID 131735.
(b) In some simulations without a defined petroleum assay (stream entirely defined from component list), when opening the list of properties in the fluid package, a number of properties (including RON and MON) do not show up. To work around this, please create a fictitious petroleum assay (the details are irrelevant as it is not going to be used, it can be e.g. imported from library). Open the list of properties again, and all missing properties (related with petroleum properties) should now appear.
(c) If the values for RON and MON in the stream property table are missing, this is probably due to the lack of RON and MON data for the pure components constituting the mixture. To solve this, access the property list from the fluid package, check the table for components with no available value, and enter the missing data. The value of RON (or MON) for the mixture can now be calculated for different stream compositions.
(d) This information may be particularly relevant for streams containing branched hydrocarbons, as the values reported by other calculation methods (e.g. using ‘Cold Property’ utilities) are not found to be as accurate (see e.g. Solution ID 131735 and 109286).
Keywords: RON, MON, properties, blending methods, user properties
References: None |
Problem Statement: What happens when the Valve Hysteresis is enabled and disabled? | Solution: For a relief valve, when "Valve Hysteresis" is enabled there are addition set points for closing the valve considered other than the Set pressure and Full Open pressure (provided under Design-> Parameters page for a Relief valve).
The ‘Closing Pressure’ is the pressure at which valve will begin to close form the initial position after it has been open for depressuring and once the pressure reaches the "Seating Pressure" the valve is fully closed from its initial open position.
If "Valve Hysteresis" is disabled: Then the Closing Pressure = Full Open Pressure and Reseating Pressure = Set Pressure.
Keywords: Relief Valve, Dynamics, Valve Hysteresis, Closing Pressure, Reseating Pressure
References: None |
Problem Statement: What is Disable/Enable Auto Linking supposed to do, with Aspen Petroleum Schedular? | Solution: A new feature of Auto-Linking of events has been added with CP2 in V8.8
This feature means that dragging an event bar close to the end of another event bar located on the left hand side automatically links the dragged event to the left event if the distance between the event edges becomes small enough.
This feature can be enabled or disabled in two ways.
1. Enable or disable auto-linking via the Setting Dialog (page Event Default):
a. If auto-linking is disabled, dragging an event bar close to the end of another event bar should not link events. During the dragging, the gap rectangle should not be drawn.
b. If option �Enable Auto-Linking� is checked auto-linking should work as before.
2. Via the main-toolbar button.
This button enables or disables the auto-linking without opening the Setting dialog.
Keywords: AUTO-LINK, NEW FEATURE, TOOLBAR, LINK
References: None |
Problem Statement: What is preventing Aspen Process Sequencer from displaying properly in Aspen Process Control Web Server (PCWS) when using Internet Explorer 11 (IE11) or Google Chrome? | Solution: Aspen Process Sequencer does not support Chrome, however it does support IE11. To use Aspen Process Sequencer with IE11, the user would need to set the document mode in IE to IE5 Quirks. From IE browser, hit F12 to bring up the Developer Tools. Then select document mode and click on IE5 Quirks.
The Aspen Process Sequencer screen will display properly on restarting the IE Browser after the change.
Keywords: Aspen Process Sequencer, PCWS
References: None |
Problem Statement: What is the external_db.m2r_cfg file used for? | Solution: When connecting to an external database, a typical method is declaring the connection, and supplying the connection parameters directly in the Aspen Production Execution Manager ("APEM") code, using the DB_SHARED_CONNECTION function. However a different approach that has several advantages is declaring database connections in the external_db.m2r_cfg. This centralizes the connection information and avoids the risk of embedding information which can potentially change (for example the username and password used for accessing the external db) in your code.
How does external_db.m2r_cfg work?
When any execution starts, APEM function libraries are loaded. They look at the DEFAULT_CONNECTIONS parameter of external_db.m2r_cfg. If that number is greater than 0, then APEM sets up the specified number of connections to the defined databases. This allows any DB_XXX() function to be called (like DB_SHARED_CONNECTION, DB_CHECK, etc.) See the APEM Design
Keywords: None
References: Guide for more information.
Here is the generic info from an entry to connect to an Aspen InfoPlus.21 database. In an external config file where this is the only connection set up, DEFAULT_CONNECTIONS is set to 1:
# Information for Oracle default connection using
# class111 driver.
DB_NAME_1 = oracle_classe111
DB_DESC_1 = connection using classes111
# Type. It must be defined before.
DB_TYPE_1 = ORACLE
DB_URL_1 = jdbc:oracle:thin:@m2rnt_server:1526:aebrs
DB_DRIVER_1 = oracle.jdbc.driver.OracleDriver
DB_USER_1 = aebrs40
DB_PASSWORD_1 = aebrs40
And here is that same entry edited for connection to InfoPlus.21:
# Information for IP.21 Connection
# AspenTech SQLPlus driver
DB_NAME_1 = MyIP21
DB_DESC_1 = connection to InfoPlus.21
# Type. It must be defined before.
DB_TYPE_1 = IP21
DB_URL_1 = jdbc:odbc:MyIP21
DB_DRIVER_1 = sun.jdbc.odbc.JdbcOdbcDriver
DB_USER_1 = Administrator
DB_PASSWORD_1 = Aspen100
Here is a line-by-line explanation:
DB_NAME_1 -- The name used in APEM code to reference this connection. For sake of clarity the name MyIP21 is used to match a previously defined ODBC connection on the system of the same name (this DSN was created using the Aspen SQLPlus driver.)
DB_DESC_1 is your description
DB_TYPE_1 is IP21. However because no "type" properties are defined for Aspen InfoPlus.21 this adds no further connection characteristics to the connection. Observe that at the top of the file there are many parameters that end with either _MSSQL or _ORACLE. For a connection where type is set to ORACLE or MSSQL, these defined characteristics will be used. For example, if I wanted a DATE_FUNC_BEGIN characteristic defined specifically for my IP21 connection, I would add DATE_FUNC_BEGIN_IP21 to match the DB_TYPE_1 parameter of Aspen InfoPlus.21.
DB_URL_1 is jdbc:odbc:MyIP21 -- this is telling the Java environment that the specific Windows ODBC connection we are using is called MyIP21.
DB_DRIVER_1 references in the necessary Java JDBC/ODBC bridge to be used for the connection.
Lastly with DB_USER_1 and DB_PASSWORD_1, you supply the user and password to be used for authenticating the connection.
Obviously, it is less than desirable to embed usernames and passwords in a clear text file, so we recommend directory security to hide the contents of the cfg_source directory from unauthorized users. (Workstation MOC installations do not need access to the server cfg_source directory.) One of the planned enhancements for APEM is to move connection information like this into the ADSA, where it can be stored in an encrypted format.
As a last tip on working with external_db.m2r_cfg, if you have several connections defined, it allows the opportunity to start coding more generic BPs that retrieve the connections available in their environment using functions like GET_CONNECTIONS OR GET_CONFIG. Best practice recommendation is to use GET_CONNECTIONS. GET_CONFIG executes the logic "for DB_NAME_1 what is my connection name?", "for DB_NAME_2 what is my connection name?" (etc.) And then of course the problem may be that DB_NAME_3 is expected to be Database X at one plant (LIMS, A&C, etc.), but DB_NAME_3 is something else at another plant, and the addition of a new entry in the middle throws everything off -- a big headache. GET_CONNECTIONS is more flexible because it pulls back an array of connections, but just the names (i.e. the values on the right side of the DB_NAME_1.) So instead of using GET_CONFIG, use GET_CONNECTIONS -- this pulls back an array based on the values on the RIGHT side of the "=" sign, so you just get back the names. If you enforce a consistent naming scheme for different types of DB connections, combined with GET_CONNECTIONS, you could then base some of your programming logic on the array of defined names.
IMPORTANT NOTE: The above example using InfoPlus.21 is valid, and works fine for MOC clients where an SQLplus ODBC driver is already installed locally, and no InfoPlus.21 database security is being used. However there is a different connection method that can be used to bypass a locally installed driver and that is also necessary when InfoPlus.21 has security applied. See Article 125488 for details. |
Problem Statement: Java is using “.” as wildcard,
When using the function MATCH to find a string in an array and PACK to select the corresponding element(s) from another array, the character '.' acts like a wildcard.
How to return only 'third' in the following example? How can I exclude '.' as wildcard?
MESSAGE(PACK({"first","second","third","fourth"}, MATCH({"abc","a,c","a.c","a c"},"a.c"))) | Solution: Java is using . as wildcard, and it can be excluded by a backslash.
For example "\a.c" as in the example above
Keywords: Java
Apem
MATCH
PACK
aEBRS
References: None |
Problem Statement: How do I change Regional settings for MOC?
Regional settings (Locale) are mapped on the Windows settings by default.
This default can be overridden by using the OVERRIDE_LOCALE setting in the
flags.m2r_cfg file based on ISO standards. Also, regional settings have an
impact on the language in which the application is displayed. | Solution: You can Override the Windows Regional settings by user the MOC flag OVERRIDE_LOCALE.
The Locale (language/country settings affects number separator, date formats,) definition.
If Locale defined Windows Regional Settings are overridden.
Valid values are, for example: en, en_US.
If language/country is not valid, en_US is
taken (though, labelled with given name).
To change this navigate to the location of your MOC configuration files.
By default this will be c:\Program Files (x86)\AspenTech\AeBRS\cfg_source.
1. Open the flags.m2r_cfg file with 'Notepad' in windows.
2. Search for the Key OVERRIDE_LOCALE =
3. Open the file Attached to this incident to look for the list of Country Codes and time zones allowed by Java.
These codes can be ISO-639 up to ISO-639.2 depending on the java version you are using. You can also use ISO-3166
4. Change flag ie. 'OVERRIDE_LOCALE = en' or 'OVERRIDE_LOCALE = en_US'
5. Save this file and close notepad
6. In the same folder you will see the file 'Codify_all.cmd'. Double click on this file and it will update the configuration.
Keywords: AeBRS
APEM
Timezone
Override
Override_locale
References: None |
Problem Statement: How do I change the Tomcat logging properties? Tomcat generates many logs and cant take up space or you may want to enable additional logging to troubleshoot an issue. | Solution: To change the Tomcat logging you will need to navigate to the Tomcat folder using windows explorer.
Typically the Tomcat folder is located in c:\Program Files(x86)\Common Files\AspenTech Shared\Tomcat7.x.xx\bin
Double click on the file Tomcat7w.exe
You can change the 'Level' to enable more logging or less logging.
Error = Capture runtime errors or unexpected conditions
Info = Information Message , related to Server Activity
Warning = Warning messages
Debug = Shows all messages
Error selection should produce less logs where debug will produce more logs.
Keywords: Apache, APEM, Infoplus.21, Web21
References: None |
Problem Statement: Is there any easy way to customize the Stream Summary? | Solution: Currently, the stream table format (TFF) file needs to be modified to create a customized stream summary. It is not that easy to get the TFF file to create the desired format; hence, many customers have requested an easier graphical way of customization.
Finally, in version 2006, the Stream Summary form will be re-designed to be much easier to customize.
Some new features include:
Properties will be selected from list rather than from previously created prop-sets.
Rows can be moved up or down or deleted.
Multiple units of measure will be able to be selected.
KeyWords
customize stream report
Keywords: None
References: None |
Problem Statement: This Knowledge Base article provides troubleshooting steps to resolve the following issues with aspenONE Process Explorer:
· Process Explorer thumbnails images not visible in Search Results
· Published Tags are not visible within Search Results
· Tag Type-ahead not working for aspenONE Simulation Flow Diagrams
· Search results do not appear and page continuously loads
· AtWebplotsConfig.xml error box appears when searching for tags
· Page appears blank after selecting APE icon from aspenONE home page
· Unable to see plots in APE
· Blank screen appears when attempting to scan tags and loading icon in browser tab does not appear
· Tag search type ahead not working
· Graphic Thumbnails not appearing in search | Solution: Please download and review the following attachment:
A1PE_Troubleshooting_Guide4.pdf
Keywords: a1PE
References: None |
Problem Statement: Is it possible to get stream results in terms of Dry Basis (without moisture) in Aspen Plus? | Solution: Dry basis is the expression used for calculations in which the presence of water is ignored. In Aspen Plus, all calculations are done on a wet basis by default. We can check this dry basis option in order to avoid manual calculations. To activate the dry basis option, go to Results Summary | Stream (Custom) | Right click on Default, select Add New, then in Edit View if you go to Calculations Option tab you will find Water Basis option by default it is wet basis.
By selecting the properties from the left you can change the water basis to dry, wet, or both.
Keywords: Dry Basis, Stream (Custom), Results Summary
References: None |
Problem Statement: How to package Aspen Engineering Products for a silent installation while connecting to remote a Aspen Properties Database. | Solution: Many customer environments do not allow installing any databases on a local user machine. These particular customers may maintain a central SQL Server to host their databases. This solution article provides instructions for creating a silent install package for installing Aspen Properties Database locally on a user machine and connect it to a remote Central SQL Server APED database.
To host an Aspen Properties database on a SQL Server, please follow KB Solution: 145154
Build a Config.aem file to be used within package.
· A clean machine needs to be setup to build a Config.aem file, which would be used on all users machine.
· Download and run the attached UseRemoteSQLKey.reg registry file.
· Please follow Aspen Engineering V8.8 Quick Install Guide to install Engineering products on a clean machine.
· Configure the clean machine to register a remote Aspen Properties Database:
· Go to Start | All Programs | AspenTech | Process Modeling V8.8 | Aspen Properties | Aspen Properties Database Manager. Click OK on the warning message and the Aspen Properties Database Manager will open.
§ In the Aspen Properties Database Manager, on the left side, right-click on Aspen Physical Properties Databases and select Register Database
§ At the Register Properties Database Wizard, fill in the following information:
1. Uncheck Use LocalDB
2. Server Name: <SQL Server Service Path>
(Note: The default is .\SQLEXPRESS. The “.\” means “this computer”. If connecting to another computer, put the computer’s name first, followed by the SQL Server Service name. Example: Server1\SQLEXPRESS)
3. Authentication Mode: Select SQL Authentication.
(Note: The below login credentials are the default for APED database which would need to be created on Central SQL Server if not available after restoring the Database)
4. Login Name: apeduser (v7.0-7.3) or apeduser2 (v8.x)
5. Password: Aprop100 (v7.0-7.3) or Aproperty88# (v8.x)
6. Database: Select the Database listed in the list of Database Example: APEOSv8.x, APV8x, NISTV8x and FACTV8x.
7. Click Ok
8. Repeat step 1 – 7 for all APEOSv8.x, APV8x, NISTV8x and FACTV8x databases.
9. Exit Aspen Properties Database Manager.
10. Config.aem file will get updated with the registered database(s).
· Go to C:\ProgramData\AspenTech\APED V8.8 and copy Config.aem file to be used within the package.
Build a Silent Installation with all Aspen Engineering Products:
· A clean machine needs to be used for preparing a silent installation package.
· Download and run the attached registry file: UseRemoteSQLKey.reg.
· Please follow KB Solution Article: 138560 to record Aspen Engineering installation.
· Verify all the required MST, XML and Batch files are created.
Deploy the package using any deployment software:
If you are using Microsoft SCCM, please follow the SCCM Best Practise guide KB Solution Article: 142957 to deploy the package.
· The package needs to be rolled out in the following sequence:
o Roll out UseRemoteSQLKey.reg registry file
o Roll out Aspen Engineering Batch files which installs all the products
o Roll out Config.aem file which was created.
Keywords: Centralize
Central
Aspen Properties Database
APED
Share
Remote Connection
Database
Register
SCCM
Silent
Config.aem
unattended
References: None |
Problem Statement: How to control the tank level using a logical expression driven by a Spreadsheet operation | Solution: The spreadsheet operation is able to handle If-Then-Else statements that can be easily used to manipulate several operations in Aspen HYSYS Dynamics such as valves, based on user specified conditions.
The attached file is an example of how to maintain a tank (V-100) level managing the liquid outlet with valve VLV-102. This valve open or close based on the tank level as described below:
- When tank level is below 1%, the valve will close
- When tank level is higher than 5%, the valve will open
Please see SPRDSHT-1 in which these parameters have been set in cells B3 and B5.
Notice that cell B2 contains the current level tank while cells B4, B6 and B7 indicated the desired valve opening according to the tank level. The logic expression is on cell B9.
Hint: If you want to know more about other logical expressions that can be used in the spreadsheet, please click on the Function Help button of this operation.
Run the Dynamics case. You will see the warning "The dynamics assistant identified items which need attention. Would you like to solve there in steady state first and not switch to dynamics?" Please say "No".
There is a strip chart already created so you can see the current behavior.
Try increasing the flow in the feed stream and look at the strip chart.
Keywords: Dynamics, Tank Level, Valve Opening, Spreadsheet, Logical
References: None |
Problem Statement: This solution is the guideline on how to achieve data transfer from Thermal to Mechanical. | Solution: This is Japanese Solution.Please see the attachment.
Keywords: JP-
References: None |
Problem Statement: How do I know if I am using the latest version of Aspen Assay Converter? | Solution: The Aspen Assay Converter version is independent from the Aspen HYSYS version.
The Aspen Assay Converter file version can be checked by following the steps below.
1. Go to the folder: C:\Program Files (x86)\AspenTech\Assay Converter
2. Locate the file AFAMAssayConverter.exe
3. Right click and enter in the Properties.
4. Open the Details tab and see the file version.
The first version of Aspen Assay Converter was released in 11th February 2014. Click HERE to download
The file version associated with this release is 1.0.0.0
A patch was released on 14th November 2014 to fix the CQ00539572 - Unexpected Vapor Phase for the heavy cuts at 15 C. This fix has been included in the Hysys Cumulative Patches.
The file version associated with this release is 2.0.0.2
The latest patch was released on July 2016 to fix property management issues. This is available in AspenONE exchange in Aspen HYSYS.
The file version associated with this release is 2.8.1.3
Keywords: assay converter, version, patch
References: None |
Problem Statement: How to solve: "The required version of Visual Studio for exporting models was not found - compilation aborted." | Solution: Visual Studio provides the compiler and linker for ACM to export models into Aspen Plus or Aspen HYSYS. The official supported version of Visual Studio can be found in the ACM documentation under Compatibility Notes. Although the compatibility is version specific, if a different release of Visual Studio is installed in your machine, there is a simple way to try to compile and export your model by modifying the system environment variables . Please do the following:
1. Go to Start > right click on computer and select properties or go to Control Panel > System and Security > System
2. Click on Advanced system settings and then click on Environment variables
3. Under system variables you should see a variable that defines the path for Visual Studio components called VSxxxOMNTOOLS, where xxx is the number of the version installed in your machine, for example for VS 2008 the variable will be VS90COMNTOOLS. In this path there is a batch file called vsvars32.bat that sets the environment variables required to make use of Visual Studio capabilities such as compiler and linker. ACM will look for this environment variable (for the supported version only) in the exporting process. The table below shows the compatibility and variable name for each version of ACM:
ACM VS Enviroment Variable name
V8.0 2008 VS90COMNTOOLS
V8.4 2008 VS90COMNTOOLS
V8.8 2013 VS120COMNTOOLS
4. Create a new user variable with the name of the specific version of Visual Studio supported for the version of ACM installed in your machine
5. Copy the value of the existing VSXXXCOMNTOOLS variable into the value of the one just created.
6. Click OK to the dialog forms.
Now ACM should be able to export your model. Please note that from V9 on, ACM already includes all the require components to export the model, therefore no third party program installation is required any more.
Keywords: ACM, model export, compiler, Visual Studio
References: None |
Problem Statement: How to fix a crashing problem when the TEMA sheet is intended to be printed in Aspen Shell and Tube Exchanger V8.8? | Solution: The root cause of the issue is related to Windows 7 with .NET Framework 4.6.
The .NET Framework 4.6 provided by the Microsoft Security Update does not have the method System.Printing.PrintQueue.GetDpiX needed in System.Printing.dll.
There are two options to solve the problem:
Revert the security update
Update to .NET Framework 4.6.1
For reference: Please take a look to Microsoft Windows Update MS16-035
https://support.microsoft.com/en-us/kb/3136000
Keywords: TEMA, Print, Crash, Windows 7, KernelBase, .NET Framework 4.6
References: None |
Problem Statement: How to connect a workstation to use the Aspen Properties Enterprise Database (APED) on another computer. | Solution: There are times when customers want to have their Aspen Engineering software use the APED database that is located on another computer. This could be that they do not want to install Microsoft SQL Server xxxx Express onto their individual computer. The instructions will give the information to configure this setup.
How do you configure SQL Express for remote access of physical properties in APED?
http://support.aspentech.com/webteamasp/KB.asp?ID=125084
After you have completed the steps on the remote computer, you will need to register the three APED databases (APV8x, FACTV8x and NISTV8x). To do this you will need to use the Aspen Properties Database Manager utility located at Start | All Programs | Astpentech | Process Modeling V8.x | Aspen Properties | Aspen Properties Database Manager.
Before we register the remote databases, please verify that the property databases are not installed locally, if they are, using the database manager, select the database and right click and select the Delete Database Registration, do this for each database, this is needed because you can't register more than 1 copy of each database, this includes the remote ones.
Databases must be registered before they can be used by programs on your computer, such as Aspen Plus or Aspen HYSYS. Right-click Aspen Physical Properties Databases under console root and select Register Database...see screenshot attached.
1. Database Type - Only SQL Server is supported.
2. Server - If your administrator has set up a database server to be shared over the network, select the name of the server from the list. To connect to SQL Server Express, you must add "\SQLEXPRESS" after the computer name.
3. Login Name -apeduser2.
4. Password - Aproperty88#.
5. Database - Specify the name to be used for the new database. Keep the name short, using a maximum of 8 characters.
Keywords: APED
remote computer
References: None |
Problem Statement: Table MIP (Mixed Integer Programming) is attached to a MultiPeriod (PPIMS) model. When you run the model, you get the following error:
"MIP model has no integer variables"
What is the reason for this error and how can it be solved? | Solution: In table PERIODS, there is an optional column called "MIP". It allows a user to define for which periods you want to use MIP. For example, in the table shown below, Mixed Integer Programming will be used only for periods 1 and 2, but not for period 3.
If column MIP is present in Table PERIODS, but there are NO entries for any period, and Table MIP is attached to the model, PIMS will generate the error "MIP model has no integer variables".
To make the model work, remove the "MIP" column or put entries into the MIP column in Table PERIODS for the periods you are going to run. It is probably a good idea to remove that column altogether to avoid getting this problem in the future. The resulting Table PERIODS looks as follows:
Keywords: MIP
Mixed Integer Programming
PPIMS
MultiPeriod PIMS
PERIODS
References: None |
Problem Statement: In the PIMS iteration log, the following message can appear: DISTRIBUTION XYZ TO ABC VALUE 1.35 EXCEEDS 1.00.
In what situations (i.e. what instances of the message) should some action be taken by the modeler? | Solution: As with many questions about PIMS, the answer is "it depends".
This message can appear when Table PCALC is used. The issue is that when Distribution Coefficients are >>> 1, then the error of the pool quality is being magnified, or multiplied, by that coefficient. This can make models unstable because the error is overcompensated for.
As for the question "how big is too big" there is no precise answer. Typically Distribution Coefficients that are < 2 don't cause major issues.
Structures that can cause this commonly involve recursion structure that turns qualities into column activities for control. In such scenarios, we suggest this is remodeled using Table PROCLIM rather than Table CAPS to control the qualities.
Structure where a column is fixed at 1.0 and contains a -999 for quality transfer can also cause distribution coefficients > 1. For such structure, the users may want to fix the column closer to the activity of the pool collector column that is creating the 999 quality and then adjust other coefficients accordingly. This can help to reduce the magnification of the Error Distributions in this case.
Keywords: Error Distribution
Table PCALC
References: None |
Problem Statement: Modeling Ammonia Flooded Evaporators with Aspen Shell & Tube Exchanger | Solution: OBJECTIVE
The example file will enable you to setup an Ammonia Flooded Evaporator rating case in the Shell & Tube Module of the EDR program and help analyze results.
PROCESS DESCRIPTION
Model a Methanol-Water mixture cooling process on the tube side vaporizing Ammonia on the shell side. Enable rating/checking mode to evaluate performance in a defined geometry.
GENERAL GUIDELINE
Set process data and pressure drop constraints. Enter process stream composition for both shell and tube sides. Select Aspen Properties package for both sides and choose NRTL method for Methanol-Water mixture & REFPROF method for Ammonia.
Set calculation method to rating / checking mode and input all parameters as shown in the example. Run the program.
RESULTS SUMMARY
OPTIMIZATION PATH: Offers a quick design check to confirm surface area ratio and pressure drop ratio. Confirms design status.
TEMA SHEET: Performance, design and construction details can be found in the section.
THERMAL & HYDRAULIC SUMMARY: Confirms process cooling on the tube side and vaporization of Ammonia on the shell side. Heat load matches between shell and tube sides. Pressure drop conditions are met as well. Distribution of pressure drop across various sections of geometry helps determine what to adjust to minimize pressure drop.
CALCULATION DETAILS: Performance along shell and tube side are located in separate sections. Each section details performance along the length of the heat exchanger and values for vapor fraction, film coefficients, heat flux, heat load, etc. can be depicted on a plot for easier understanding.
DESIGN CONSIDERATION: A flooded evaporator BXM design with a shell side cross-flow design feature has been illustrated. A square pitch pattern helps achieve lower pressure drop and provides vapor lanes for the vapor to escape the bundle. Adequate baffle supports have been employed to mitigate vibration and resonance issues. Mean metal temperatures on shell and tube sides are fairly close to each other and hence an expansion joint may not be necessary. The relatively high tube side pressure drop may require thicker than typical pass partition plates.
Keywords: EDR, Ammonia Flooded Evaporator, Design, Simulation
References: None |
Problem Statement: Aspen PIMS V8.8 is taking more than 10 minutes to launch | Solution: This article will outline the instruction to reduce Aspen Products launch latency.
Aspen Applications will check for licenses during launch depending on the License server and bucket configuration in SLM Configuration Wizard.
Configure the client machine to priorities license server and bucket:
Follow KB:21970 to configure the user machine to priorities license server and bucket depending on your product use.
Download and apply attached registry:
Download and extract SLM.zip
Double click to install SLM.reg
This registry will update user machine with following SLM configuration.
Disable Broadcasts
Disable searching licenses in all available buckets
Ignore local licenses on user machine
Disable License Expiration reminder
If above steps does not reduce product launch latency issue, then please follow below steps:
Upgrade the SLM Server to V10 (SLM 8.6.1) and above version
Go to Products Patches on our eSupport website and download latest version of SLM Server software for upgrade.
Install SLM Tools V10 on each users machine
Go to Products Patches on our eSupport website and download latest version of SLM Tools software.
Follow KB:22161 to roll our SLM Tools latest version on all the users machine.
Note: SLM Tools can be upgraded on a user machine where the application is lower version, for example: SLM Tools V10 can be installed on machine using Aspen PIMS V8.8.
Keywords: Latency
product launch
slow launch
References: None |
Problem Statement: How to configure a client machine to use a network license for V8.X and older | Solution: Here are the instructions -
Go to Start | Programs | AspenTech | Common Utilities | Configuration Wizard.
Select `Yes? radio button to answer `Will you be connecting to an SLM server over the network.? Click Next.
Enter or highlight the license server name that you want to use. Review bucket information listed in bottom box and update if necessary. Click Next.
In Configure Advanced Settings, select `Yes? to the question. Click Next.
Ignore the box about Project Tracking. Click Next.
Check the box for `Enable Broadcasting? if you need to connect to multiple license servers/files or uncheck if not. Click Next.
In For Licensing Type, check all of the boxes and then click the `Auto Configure/Optimize License Type Settings? button.
You want the system to return `Unified Licensing? and if it does not and throws an error message contact AspenTech support at 1-888-996-7100. Click the Next button.
Click Next.
At this time your computer?s registry is being updated so you might see some DOS command windows appear and disappear showing you what is being registered. Be sure you see the message `No errors encountered while updating the registry.? Click Finish.
Keywords:
References: None |
Problem Statement: In Aspen Petroleum Scheduler,
How to resolve the error "Unable to open database file(MS Access Database)" on launching Demo model which results in crashing of APS.
The Root cause for the problem is :
1. Either The machines does not have MS Access driver installed
[or]
2. The default connection for MS Access database is nor created. | Solution: Please try the below solution :
Solution 01: ( Create a default MS Access connection )
a) Open ODBC Administrator . Go to User DSN
b) Verify that a data source named “MS Access Database” exists.
c) If it does not exist, then please create a new connection, with the same name, same driver, by click on “Add”
Solution 02: ( If we cannot find MS Access default connection or driver is unavailable in the ODBC administrator)
In case you cannot locate the MS Access driver in the ODBC window , then we need to install ODBC driver.
Below is the procedure to install MS Access ODBC Driver.
1. Download the 32-bit version of the Microsoft Access Database Engine 2010 re-distributable from the following location:
https://www.microsoft.com/en-us/download/details.aspx?id=13255
Download AccessDatabaseEngine.exe.
2. Once downloaded, install AccessDatabaseEngine.exe by opening a Command prompt, with admin privileges, and then typing:
AccessDatabaseEngine /passive.
After installation, you will be able to open any .mdb file without any issues.
KeyWords
APS, Crash, Demo model, Database, unable to open, MS Access
Keywords: None
References: None |
Problem Statement: When you run more than one case in PIMS V8.8 while connected through the Cisco VPN client, you may occasionally receive a "Failed to Validate | Solution: ID in PrSolutionID table. Please run the model again and generate the results."
Solution
This is a possible issue in PIMS V8.8, and can happen in certain cases when connected to the Cisco VPN client. To work around this issue, you'll need to commute the PIMS licenses using the license commuting tool (please refer to the kb article: https://esupport.aspentech.com/S_Article?id=000082386 ). After successfully commuting the licenses, disconnect from the Cisco VPN and you should be able to run multiple cases in PIMS as normal.
Please also refer to the KB articles below for additional troubleshooting steps:
https://esupport.aspentech.com/S_Article?id=000058477
https://esupport.aspentech.com/S_Article?id=000063385
https://esupport.aspentech.com/S_Article?id=000070114
Keywords: None
References: None |
Problem Statement: When trying to open a project in IQ Power tools the following error shows: Project Load Failure. | Solution: This error usually shows after moving the project folder to a different location. The full path for the project directory is directly stored in the project file.
Below image shows the error:
Locate the *.proj file and open it with notepad. The 4th line shows the current location expected by the project:
Edit the *.proj file with note pad so it reflects the current path. Then open the project file, this time it should be successful.
Keywords: IQPowerTools
Aspen Process Statistical Analyzer
Apollo
References: None |
Problem Statement: Sharepoint 2013 security does not allow custom master pages to be uploaded directly to the Share Point Master Page List. If you do, you will see an error message like: "Code blocks are not allowed in this file"
This solution provides workaround on how to update the Aspen Master Page for a Sharepoint 2013 site. | Solution: Aspen Master pages are located at:
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\FEATURES\CUINavigationBar\aspendefault.master
And
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\FEATURES\RBVCompatibleView\aspendefaultCompatible.master
By default Aspen Sites are using aspendefault.master as master page. When the “Aspen RBV Compatible View” is activated, the sites will be using aspendefaultCompatible.master as master page.
Before making any change on the Master page, do a backup copy of it. To be able to modify the current page Launch “Sharepoint 2013 Management Shell” and run the following command:
Disable-SPFeature CUINavigationBar -Url:http://<Your Server>:<port>/<your Site> -Confirm:$False
Having running this command you’re now able to open the web page and modify the settings you need. Having done all changes, save the page and run the next command:
Enable-SPFeature CUINavigationBar -Url:http://<Your Server>:<port>/<your Site>
Reload the Site and test if changes work properly.
Keywords: aspendefault.master
aspendefaultCompatible.master
"Code blocks are not allowed in this file"
References: None |
Problem Statement: This solution describes how to add command line arguments to Aspen Cim-IO Store and Forward processes when the interface device was configured using the I/O wizard. | Solution: Note, if you are using V9.0+ of the Aspen Cim-IO Interface Manager, do not continue here, instead refer to knowledge base article 146539-2: How do I use Cim-IO Interface Manager to set additional parameters for the S&F processes?
When configuring a Cim-IO device using the I/O Configuration Wizard, a text based CSD file for the device is created in the AspenTech\Cim-IO\Management folder on the Cim-IO interface system.
You must edit this file to configure the arguments on the processes. The method described below attempts to make use of the I/O Configuration Wizard to help reduce the possibility to introducing a syntax error but with experience you can make all the changes directly to the CSD file itself.
1. See article 105498-2: What are the Aspen Cim-IO Store & Forward startup command line arguments ?
2. Stop the device using the InfoPlus.21 Administrator. Stop the Cim-IO server tasks (TSK_M.., TSK_A.., TSK_U..) in InfoPlus.21 Manager.
3. Open the Properties of the device and go to the Processes tab
4. With "Enable Store & Forward" checkbox ticked examine how a normal set of scanner, store, and forward processes are defined by clicking on each in turn and clicking on the Properties button.
5. Open the Windows\System32\drivers\etc\services file in notepad and comment out (prefix with #) the three appropriate lines: <tcpservice>_ST, <tcpservice>_SC, <tcpservice>_FW
Save the services file.
6. Back in the Wizard, untick the “Enable Store & Forward” checkbox and click OK. This will remove the processes that would have automatically been created initially (note, this would have also deleted the associated services from the services file if it had found them - we commented them out so this should not happen).
7. Open the Properties | Processes Tab again.
8. Click the Add button to add back each of the Scanner, Store, and Forward processes.
For each one, add the arguments in the Arguments edit box, leaving a blank space after the DLGP service name. You can copy and paste from the text below:
a. Name: Store process
Service Name: <tcpservice>_ST
Executable: %CIMIOROOTQ%\Code\Cimio_sf_store.exe
Arguments (see documentation for usage but always put the DLGP service name first): <tcpservice> followed by arguments
b. Name: Scanner process
Service Name: <tcpservice>_SC
Executable: %CIMIOROOTQ%\Code\Cimio_sf_scanner.exe
c. Name: Forward process
Service Name: <tcpservice>_FW
Executable: %CIMIOROOTQ%\Code\Cimio_sf_forward.exe
9. Click OK.
10. Stop the CIM-IO Manager service.
11. Open and edit the appropriate CSD file so that the 4th line is StoreForward (not NoStoreForward). Save the file.
12. Reopen the services file and uncomment the 3 lines: <tcpservice>_ST, <tcpservice>_SC, <tcpservice>_FW
Check the services file to make sure it is correct - it should look the same as it did at the beginning. Save the services file.
13. Restart the CIM-IO Manager service. Restart the device. Restart the Cim-IO server tasks (TSK_M.., TSK_A.., TSK_U..)
14. Check that the arguments are applied correctly by looking through the CIMIO_MSG.LOG file.
WARNING: After following this procedure, to reconfigure the device you can only make changes directly to the CSD file itself (the CIM-IO Manager service must be stopped to allow this). If you attempt to make any changes to the configuration of the device using the I/O Configuration Wizard all the argument settings you made on the processes will be lost.
It is acknowledged that it is very difficult to change and maintain such settings using the tools provided before V9.0 of the Aspen Cim-IO Interface Manager. For this reason it is recommended that you upgrade to Cim-IO V9+ should you want to add command line arguments to Aspen Cim-IO Store and Forward processes.
Keywords: cimio
store and forward
notaginfo
msgs
device
timeout
cimio_sf_store
cimio_sf_scanner
cimio_sf_forward
References: None |
Problem Statement: After following solution 14172 and registering both 32-bit a 64-bit Aspen SQLplus ODBC Drivers, you might get the following error: The setup routines for the AspenTech SQLplus ODBC driver could not be loaded due to system error code 193. | Solution: To start troubleshooting, please verify that libc21.dll exists in C:\Program Files\Common Files\AspenTech Shared. If not, running the repair installation is necessary.
If libc21.dll is in the aforementioned path, add it to the environment variable PATH. To do so:
1. Go to the start button, right click on Computer and select Properties.
2. On the Control Panel Home, Select Advance System Settings.
3. Go to the Advance Tab and Click on Environment Variables.
4. On system Variables, select Path and click EDIT.
5. Copy the variable value in a Notepad, and add the AspenTech Shared path.
6. Copy the text back into the Variable Value field and Click OK.
Keywords: Environment variables, ODBC, 64-bit, driver, path, SQLplus
References: None |
Problem Statement: Can I model Screw Compressor in Aspen HYSYS? | Solution: The Screw Compressor is a new compressor model introduced as a part of the Compressor Unit operation in HYSYS V9.
Prior to V9, there is no unit operation in Aspen HYSYS that can directly model a rotary screw compressor or any other type of screw compressor. However, there are couple of work-arounds that have been applied in the past, although all are approximate rather than rigorous.
In most of the cases oil-injected screw compressor is used. For an oil-injected screw compressor, both gas and oil enter the compressor (the oil acts as a sealing agent and coolant). Regarding the presence of two phases in the Compressor, Aspen HYSYS will generate a warning although the calculations will normally be performed. The temperature increase across a screw compressor is not as high as for a conventional centrifugal compressor; the compression is closer to isothermal. The calculations performed by the Aspen HYSYS Compressor are as follows:
Ideal flash / Isentropic condition: Aspen HYSYS uses the inlet entropy and the specified outlet variable (pressure, temperature, etc.) to calculate the rest of the "ideal" outlet conditions. flash for calculating the ideal conditions
Adiabatic or polytropic condition: Apply efficiency to obtain actual conditions. Eefficiency = (work required ideal / work required actual).
So even by using an efficiency of 100%, what is being calculated is always the isentropic compression which will give a higher outlet temperature than operating close to isothermal compression conditions. For example, a P-V diagram of the two different paths followed during the compression will show the isothermal curve goes right to the isentropic one. The work Aspen HYSYS predicts will also be less due to thermodynamic reasons (the area under the P-V diagram curve will be smaller because the final state will be different, higher final volume for the same final pressure in the case of isentropic compression). Therefore, isothermal compression as such cannot be calculated by any Aspen HYSYS operation.
One rough approximation to the isothermal compression is to build a series of compressor-cooler groupings to reach the final state at an almost isothermal condition, however in this case the work consumed by all operations will be higher than the real isothermal compression work.
Another option would be to map the performance data from the vendor into curves (in the format used by the default Compressor) and represent the screw compressor with a centrifugal compressor.
Alternatively if, from vendor data, you know the outlet conditions you expect to achieve you can use a heater operation to represent the compressor, leave duty and delta P empty, then specify the outlet conditions and Aspen HYSYS will calculate the pressure rise and the required duty.
Keywords: Screw compressor, screw
References: None |
Problem Statement: What is the reason for History plots to show NaN in HPT on PCWS even though there is a value shown in process explorer plot and in . | Solution: Check to see if ADSA connection handshake between the PCWS and Aspen watch is successful by performing a test connection on the ADSA client config tool (Please right click + run as admin while opening ADSA client config tool).
Also check to see if Aspen public data sources have been added correctly while the user data sources is blank for the ADSA client config tool by navigating to the configuration section of ADSA client config tool.
If the ADSA configuration is correct then verify in IIS Manager, if ISAPI & CGI Restrictions includes ATPROCESSDATAREST.dll in the components. It is possible that due to error in the installation, this component is missing in the ISAPI and CGI restrictions.
This can be added as follows (Confirm if it is ok to lose connection to PCWS for a small time interval while executing the following steps)
1) Open IIS Manager and double click to on ISAPI & CGI restrictions to open.
2) Click on "Add..." button on extreme right section under the Actions pane.
3) Click on the browse button next to ISAPI or CGI path and add the path C:\inetpub\wwwroot\AspenTech\Web21\ProcessData\AtProcessDataRest.dll.
4) Add description as - AtProcessDataRESTWeb21
5) Select the checkbox to allow extension path to execute.
This could help get the history plots to show data. Please contact AspenTech Support for any additional configuration or questions in any of the steps mentioned in this article.
Keywords: High Performance Trends
Value is NaN
References: None |
Problem Statement: When clicking on the Export to KGTower in the Tray Sizing utility, I receive a message in the trace window that says that KG-Tower is not installed in my machine even though I do have it installed. | Solution: The version of KG-Tower installed might not be compatible with the Aspen HYSYS version, and so the installation check in the registry is mistaken.
However, the .kgt file is still generated in the directory and can be opened and used in KG-Tower directly.
Keywords: Column analysis, Tray, Packing, Sizing, Rating
References: None |
Problem Statement: Why does the print of the API sheet occupy 25% of the page? | Solution: There was a defect in Aspen Exchanger Design and Rating V8.8 and ealier where the print out is small when you right click and select print. This has been fixed in V9.
The workaround in V8.8 is to use the option from File / Print and select the APIsheet. This should give the right size.
Keywords: Print, small, API sheet
References: None |
Problem Statement: Equations and Example Benchmark Calculations for Two Phase Orifice Sizing and Vapor Noiise and Reaction Forces using Aspen HYSYS | Solution: The attached PDF contains a validation with hand calculations for two phase orifice sizing and vapor noise and reaction forces inside the Safety Analysis Environment. This gives two forms of the Leung Omega Methods as implemented in the Safety Analysis Environment.
1. For cases that are saturated or two-phase at relief conditions, upstream of the relief valve.
2. For cases that are subcooled liquid upstream of the relief valve, with flashing occurring across the valve, producing a two-phase stream at the valve outlet.
This document contains:
1. Non-Subcooled Omega Method
a. Equations
b. Example with Critical Flow
c. Example with Supercritical Flow
2. Subcooled Omega Method
a. Equations
b. Example with Low Subcooling, critical flow
c. Example with Low Subcooling, subcritical flow
d. Example with High Subcooling
3. Direct Integration Method
a. Equations
b. Example
4. Noise
a. Equations
b. Example
5. Reaction Forces
a. Equations
b. Example
Keywords: PSV, PRD, Relief Sizing, Orifice Sizing, validation, whitepaper
References: None |
Problem Statement: How to access the Dynamic Depressuring Utility via VBA? | Solution: The following code can be used to gain access to the Dynamic Depressuring Utilities in the simulation file. From that point, the user can execute specific methods to all utilities or further select which of the utilities should be read or manipulated.
Dim hyDepressUtil As CDynDepressuring
Dim utilVar As Variant
For Each utilVar In hyCase.UtilityObjects
If utilVar.TypeName = "dynamicsdepressuring" Then
Set hyDepressUtil = utilVar
'perform actions on the depressuring utility
End If
Next utilVar
Keywords: Dynamic Depressuring Utility, VBA, automation
References: None |
Problem Statement: How do I configure Citrix Server and Client? | Solution: Please refer to attached configuration document which shows step by step direction about Prerequisite, Installation & configuration of Citrix Licensing server, Installation & Configuration of Citrix server and Client.
Keywords: None
References: None |
Problem Statement: How is the Aspen Properties Excel Calculator used? | Solution: The Aspen Properties Excel calculator provides rigorous physical properties as Excel built-in functions. These functions are easy-to-use, can be integrated in spreadsheet calculations, and provide full access to all the property methods and models available in Aspen Properties. You can use these functions to calculate physical properties of pure components and mixtures, as well as to perform phase equilibrium calculations.
To use the Aspen Properties Excel Calculator:
1. Add the Aspen Properties Excel Calculator to Excel menu:
A. Open Microsoft Excel.
B. Go to the Tools menu and select Add-ins. The Add-ins dialog box appears.
C. Click on the Browse button, go to the \Aspen Properties\Engine\xeq directory where the Aspen Properties calculation engine was installed (e.g., C:\Program Files\AspenTech\Aspen Properties\Engine\xeq), select the "Aspen Properties.xla" file.
A new menu item "Aspen Properties" will appear on the main menu bar of Microsoft Excel. (If you installed Aspen Properties with the Lite Client option, in step (C), you need to locate the Aspen Properties.xla file in the \Engine\xeq directory on the file server. You must respond No, when asked whether or not to copy the Excel Add-In file to your local drive.)
2. Run the examples delivered with installation. These example files (with extension aprbkp) are stored in \Aspen Properties\GUI\xmp\ directory. Let us take "drex1.aprbkp" for the exercise.
A. Copy drex1.aprbkp to a new directory C:\temp\..
B. In Excel, place your prompt at Cell A1, go to Aspen Properties\Select Properties Package, select Aspen Properties. Browse to C:\temp directory and open drex1.aprbkp. The path and file name will display in Cell A1.
C. Move to Cell A2, from Aspen Properties click "Select Components". Select H2O and click OK. H2O displays in Cell A2.
D. Move to Cell B2, from Aspen Properties click "Select Properties". Select VaporPressure and click OK. VaporPressure displays in Cell B2.
E. Move to Cell C2, from Aspen Properties click "Select Property Methods". Select STEAM-TA and click OK. Steam-TA displays in Cell C2.
F. Move to Cell A3, click the "Paste Function" button "fx" on the menu bar. Under Function Category click Aspen Properties, under Function Name click VaporPressure. Click OK, an input window pops up. Enter A2 at ComponentList and 373 at Temperature (water at 373 K). Click OK. The calculated pressure of "100605.3297" in N/m^2 displays in Cell A3.
For multiple components and multiple properties, a table can be arranged by the user. The above procedures can also be followed to open an Cape-Open property packages.
For more information see the Aspen Properties User Guide, Chapter 21, Aspen Properties Excel Calculator.
KeyWords
Aspen Properties
Excel calculator
calculator
Cape-Open.
Keywords: None
References: None |
Problem Statement: In versions previous to 8.0, the method to change the fluid package was to select portions of the model, then with all the equipment highlighted, right mouse click and select "Change Fluid Package". Where is this located in versions higher than V8.0? | Solution: The "Change Fluid Package" button is not supported since V8.0.
The new feature used for this task is the "Fluid Package Association" button, which is located in the Home menu.
For more information, please refer to Solution ID: 142291 How to change the fluid package of a single or multiple components in Aspen HYSYS V8.0
In previous versions to V8.8, however, when users specify a fluid package manually in any equipment or stream, the "Fluid Package Association" was not able to switch to the new fluid package. This was by design. The solution was to change the fluid package manually equipment by equipment.
This has been fixed in V8.8, the ' Fluid Package Association' button now allows for a quick change of all equipment to a new fluid package.
Keywords: Change Fluid Package, Fluid Package Association, fluid package
References: None |
Problem Statement: AspenHysys.exe v8.8 crashes and the windows error log indicates error with KERNELBASE.dll | Solution: Open the software with another user account, if this works, the corrupted user profile must be recreated by the system administrator.
If it still doesn't work, repair the system files of the computer, you can use this Microsoft solution as a guide: https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files
Keywords: None
References: None |
Problem Statement: In v 8.8 and V9 the valve manufacturer and ANSI-ISA valve type can not be selected. While in 8.6 and prior versions this selection was available. Why? | Solution: In pre V8.8 versions, the valve sizing/method options seemed to be miscategorized. There are basically two sizing methods:
Fisher Universal
ANSI/ISA
In the Pre-V8.8 versions, with each of the above selections you also had another menu for selecting valve manufacturers as a sub-selection. This was wrong. These selections should not be a subcategory of the above two options. They are separate models with separate equations. Also, ANSI/ISA uses its own unique equation, making the valve manufacturer menu essentially obsolete
Keywords: : ANSI-ISA, valve manufacturer methods
References: None |
Problem Statement: What options do I have to edit the Custom Stream Report in Aspen Plus V8.8? | Solution: To begin customizing your report, go to Results Summary | Streams (Custom):
or
The “Default” summary will appear after clicking this section, this report will show all the information relevant to all the streams and all the properties that have been added to a property set, including multiple units for each variable. This Default report is the basis to create one or more custom reports.
Right click on the Default tab and select “Add new”
Enter a name for the new sheet. Click OK.
Right click the newly created Sheet tab and select Edit View:
The Stream Summary Edit View will appear, this menu will allow you to do the following:
Control the streams to be displayed on the report and re order them.
Manipulate the properties to be displayed in the report. You can show, hide or reorder these values. These properties will be read from a default list and the Property Sets that have been added to the simulation. New property sets can be added from this form.
Change each property’s label, format (significant digits), units (multiple units available), etc.
Edit properties qualifiers, control the components, phase, basis, etc. at which each property should be reported.
Keywords: Stream Report, Customize, Properties, Table, Summary
References: None |
Problem Statement: How do I prevent the error, "Error Loading Documentation Builder", in Aspen HYSYS V8.4, during a documentation builder for the PSV module?
PSV Plus Error: Error Loading Documentation Builder | Solution: Microsoft Access is a prerequisite for this application.
Install Microsoft Access, then retry loading the documentation builder.
Keywords: PSV Plus
Microsoft Access
Documentation builder
HYSYS
V8.4
References: None |
Problem Statement: How do I prevent the error, "Error Loading Documentation Builder", in Aspen HYSYS V8.4, during a documentation builder for the PSV module?
PSV Plus Error: Error Loading Documentation Builder | Solution: Microsoft Access is a prerequisite for this application.
Install Microsoft Access, then retry loading the documentation builder.
Keywords: PSV Plus
Microsoft Access
Documentation builder
HYSYS
V8.4
References: None |
Problem Statement: What are some tips for migrating from Aspen HYSYS V7.3 to Aspen HYSYS V8.x? | Solution: Below are some quick Tips for pre-V8 users, when they are migrating:
1. Basis Manager is "Properties" Environment now and can be accessed from environment selection on left Hand side (LHS).
2. "Utilities" are under "Stream analysis" under "Home" tab in ribbon bar.
3. Object palette is "model palette" and can be accessed from "View"/"Flowsheet/Modify" tab on ribbon bar.
The text/Annotation box is under the "Format" tab.
4. Logical operations can be added by pressing F12 Key or from model palette
5. The preferences are set under "FIle=>options" now.
6. Utilities related to equipments are under "Equipment Design" under "Home" tab in ribbon bar
7. PFD modification tools are under "Flowsheet/Modify" tab.
8. Case study, workbook, Reports, Optimizer and Flowsheet summary are under "Home" tab in ribbon bar.
9. The correlation manager can be accessed by pressing the small square in "Simulation" section on "Home" tab.
10. The version, build and licensing information of the product can be checked from "File=>About" now.
Keywords:
References: None |
Problem Statement: What are the new refinery reactor models available in Aspen HYSYS Petroleum Refining V8.8? | Solution: Three new naphtha hydrotreater models - Naphtha Hydrotreater, CatGas Hydrotreater SHU, and CatGas Hydrotreater HDS- are introduced in Aspen HYSYS Petroleum Refining.
The Naphtha Hydrotreater is used to pretreat feeds going to the reformer or isomerization unit. The main purpose is to remove sulfur; however, it also removes most of the olefins and nitrogen species.
The CatGas Hydrotreater SHU and CatGas Hydrotreater HDS are used to treat the naphtha coming from an FCC. The purpose is to remove sulfur and minimize olefin loss to prevent the loss of octane.
The CatGas Hydrotreater SHU runs at a much lower temperature and hydrogen concentration than the HDS and is primarily used to saturate diolefins while also converting some light sulfides to heavier sulfides. Typically, only the heavy naphtha from the SHU goes to the CatGas Hydrotreater HDS, because typically the light naphtha has very little sulfur and also high olefin concentration.
Keywords: Naphtha Hydrotreater, CatGas Hydrotreater SHU, CatGas Hydrotreater HDS
References: None |
Problem Statement: How to display windows side by side in Aspen HYSYS V8. | Solution: To display window side by side, below is the method:
· First hover the cursor over the window's tab and right click to check it is "Dockable".
· Place mouse on the top bar and drag the window, a four-point compass activates as shown below - drop the window onto one of the four points to determine how HYSYS will split the workspace to display them side by side or as upper and lower panes. Drop the tab into the center square to restore it to the original row of tabs. You can save different layouts of windows and switch between them; these saved layouts (and the current layout) are saved with the simulation.
The window arranged:
Keywords: UI, display
References: None |
Problem Statement: How to specify when PPM, PPB or "trace" will be used for component fractions in stream results? What does "trace" mean for component flowrates or fractions? | Solution: It is possible to specify that PPM, PPB or "trace" to be used for values in the Stream Results or in the Custom Stream Results.
Stream Results
The units used for component fractions in Stream Results can be specified in Table Format Files (.TFFs), which are located under C:\Program Files\AspenTech\Aspen Plus xxxx\GUI\Xeq. For example, using the following input in a .TFF file:
prop massfrac prop-label="Mass Frac" ppm=1e-3 ppb=1e-6 &
trace=1e-9 trace-label="trace" zero-label=" "
PPM is used when mass fraction is in the range of 10-3~10-6, PPB is used for the range of 10-6~10-9, and "trace" is used for the fractions less than 10-9. The existing .TFF files in the above folder already have such specifications. Users can modify these ranges or create their own .TFF files. Users can choose which .TFF file to use from the Format drop down menu in Result Summary | Streams | Material sheet.
Custom Stream Results
Fractions in the Custom Stream Summary can also use PPM, PPB or "trace" (see attached file).
The following steps can be used to specify when PPM, PPB or "trace" are used:
1. First go to Results Summary | Custom Stream Summary.
2. Add a new sheet (say Sheet 1) by right-clicking on the Default sheet and then "Add".
3. Right-click on Sheet 1 then "Edit view" to access the Stream Summary Edit View Wizard.
4. The display options tab in the wizard can be used to specify the options for component flows and fractions as show in the screen shot below.
Trace is the value below which the Custom Stream Summary points the Trace label string instead of a value.
The field for PPM (or PPB) can be used to set the threshold, below which the letters PPM (or PPB) will appear after the affect numbers.
Keywords: TFFs, Component fractions, Custom stream summary
References: None |
Problem Statement: How do I change pipe roughness for all pipes in Aspen HYSYS? | Solution: In this example, it shows how to find all pipe segment using pipe typename ("pipeseg"). Backdoor variables are used to obtain all fitting types in each pipe.
FittingTypes = hyPipebd.BackDoorVariable("FittingType.500.[]:Name.0").Variable.Values
Roughness of pipe can be changed by ":Length.552.[]".
Keywords: Excel, Macro, Pipe Segment.
References: None |
Problem Statement: Where can I find the demonstration files for the Safety Analysis Webinar hosted in July 2015? | Solution: Attached to this knowledge base article you will find the demonstration files from the July 2015 Safety Webinar, "Reduce the Time and CAPEX of Pressure Relief Analysis Projects using an Integrated Process Safety Solution" so you can follow along with the recording.
Keywords: webinar files, PSV, Safety Analysis
References: None |
Problem Statement: We use tiered pricing for purchases and sales in our Aspen PIMS model, but we want to control the order in which they are sold. For purchases, by default, less expensive tiers are purchased before more expensive tiers. For sales, the default behavior is the opposite: higher-priced tiers are sold before lower-priced tiers. How can we force the system to buy or sell the tiers in a different order? | Solution: Tiered pricing uses Table ALTTAGS to define aliases for purchases and sales. In order to define different prices for a given material or utility, different tags must be used in Tables BUY, SELL, UTILBUY or UTILSEL.
The default ordering of buying or selling these tiers is determined by economics. Because the Aspen PIMS model is maximizing profit, the optimizer prefers buying less expensive feedstocks and selling more valuable products. This is known as convex tiered pricing.
Introduced with the 2006 release (version 16) of Aspen PIMS, we introduced a column called PRIORITY in Tables BUY, SELL, UTILBUY or UTILSEL. The PRIORITY column is used to force a certain order of purchase or sales of the tiers. A lower number in this column indicates a higher priority, e.g., the highest priority is number 1. This can be used to implement non-convex tiered pricing.
We will demonstrate the use of the PRIORITY column with an example based on the standard VOLSAMP sample model. This example uses tiered pricing for diesel fuel. The figure below shows Table ALTTAGS which sets up tag DSX as an alias for diesel fuel (DSL).
We will first show convex tiered pricing for diesel. The following figure shows Table SELL without the PRIORITY column. Please note that tier DSL sells at a higher price than the alias DSX.
The resulting material sale is shown below. Please note that the model sells DSL exclusively.
We will next show the use of the PRIORITY column. The figure below shows Table SELL with the priority column. Note that the prices and bounds of DSL and DSX are the same as above, but DSX has a priority of 1 and DSL has a priority of 2.
The resulting material sale is shown below. Please note that the lower-priced DSX is purchased up to its limit of 10,000 barrels per day, while the higher-priced DSL is under its limit of 25,000 barrels per day. This demonstrates non-convex tiered pricing.
Keywords: None
References: None |
Problem Statement: Troubleshooting the Documentation Builder in the Safety Analysis Environment | Solution: The Documentation Builder is a tool in the Safety Analysis Environment of Aspen Plus and Aspen HYSYS which allows you to generate reports for you relief device analysis. The tool uses Microsoft Access to generate the reports. Microsoft Access, however, can have some odd interactions depending on your computer settings. Here at AspenTech, we have aggregated some common issues and how to navigate them.
“I tried to click the Documentation Builder button on the ribbon, and got the error shown below. However, I checked the task manager (no running instances of MSACCESS.EXE), and even restarted my computer. The documentation builder still would not load.”
To use the Documentation Builder, you need to have either MSAccess Runtime installed (free) or the full version of Microsoft Access.
You can download MSAccess Runtime here: http://www.microsoft.com/en-us/download/details.aspx?id=10910 .
Please note that if you are using AspenTech software using virtualization, then the virtual machine must have MSAccess Runtime or full Microsoft Access installed.
Once you have installed MSAccess Runtime, restart your computer, and launching the Documentation Builder again. If this does not work, please submit a support incident.
“I just upgraded to Windows 8, and the Documentation Builder won’t open. When I try, I get a message to insert my Smart Card.”
The Documentation Builder does not seem to open on Windows 8 machines, and it consistently displays the message that you see. We are trying to contact Microsoft to resolve the issue; the problem was traced to their program, not AspenTech’s. However, we know what an inconvenience this can be, so we currently have a support ticket with Microsoft to try to resolve the issue. Note that the issue only appears with MSAccess Runtime installed, not the full version of Microsoft Access.
“I am using Windows 7. When I try to launch the Documentation Builder, my computer asks me to connect a Smart Card. I don’t have a Smart Card.”
The SmartCard service can get automatically started depending on what third-party programs you have installed. You can follow the steps outlined in the following document to get around the problem. http://computerstepbystep.com/smart_card_service.html
"A potential security concern has been identified. Warning: The digital signature has expired"
When attempting to access the Documentation Builder, if you see an error that says that the digital signature has expired (see above), you do not have the most recent update of the Safety Analysis environment installed. Please install the latest cumulative patch to fix this issue.
“The View button in Access datasheets can't be opened.“
MS Access will fail to show reports if a printer is not set up. You don’t have to install a real printer—you can use a virtual printer such as a PDF writer if there is no access to a real printer.
Keywords: Troubleshooting Documentation Builder, Safety Analysis Environment, Aspen HYSYS, Aspen Plus, PSV, MS Access
References: None |
Problem Statement: What causes the "Error creating DMCplus Context" error when simulating controllers in APC Builder? | Solution: The message "Error creating DMCplus Context" indicates that the simulation engine is unable to resolve the current controller configuration. The issue is caused in situations where the controller model does not have any curves associated to some of the variable i.e. these row or column associated with the variable would be blank when viewing the model.
There are two possible resolutions to this problem-
1. Add dummy zero curves to these variables. The user could add a model with zero or near zero gain (Ex. 1e-6) to these variables before simulating the controller. This option is particularly useful in situations where the user would prefer to keep the variable in the controller and update the associated curves at a later instance.
2. Another option would be to completely remove these variables from the controller structure by right-clicking on the model then select Edit | Variables. Select the variable to remove and hit the Delete button to remove variable from the controller. This would be the preferable option in situation where the engineer has decided to discard the variable being remove from the APC structure.
Keywords: APC Builder
DMCplus Context
References: None |
Problem Statement: When running many cases (more than 80) in big models, especially for PPIMS, MPIMS or XPIMS, it can happen that Aspen PIMS crashes. One possible cause of the crash is that the maximum size of the Results.mdb is reached. The Results.mdb, as any Microsoft Access database, has a 2 gigabyte file size limit set by Microsoft. The same maximum size limit also applies to MSDE, the single client SQL Server application.
When the Results.mdb hits this limit, or maybe a little before, the system crashes because it cannot write to the database.
Starting with PIMS 2004.1 (16) the use of the Results.mdb is mandatory, because it is used to generate all of the reports. | Solution: One possible solution to avoid the crash is to review the size of the Results.mdb for one case. A good approximation is that the total size of the database will be the database size created for one case, times the number of cases. If that goes close to the 2 GB limit, you need to run fewer cases at a givne time, then move the Results.mdb to another folder and continue the run with the remaining cases.
The file Results.mdb can be moved to any directories other than the model folders. The purpose is that Aspen PIMS can continue write to a fresh Results.mdb database.
Keywords: Results.mdb
Reports
Cases
References: None |
Problem Statement: The Recursion structure for transferred streams in multi-plant model are generated by PIMS during global matrix generation. There is no PGUESS nor PDIST available in global model.
If I look into the matrix of global model, the initial error distributions are all 0.01 for transferred streams.
How does PIMS generate initial Error Distributions for Transferred streams? | Solution: PIMS refers M2M (Initial Model-To-Model Error Distribution Factor) option in Advanced tab of Recursion Settings.
The default is 0.01.
Keywords: MPIMS
XPIMS
Recursion Settings
References: None |
Problem Statement: Why doesn't the excel sheet open from my model tree on double clicking? Some users randomly see this issue. | Solution: Excel performance can be erratic if there are "orphan" Excel processes open. First, make sure that all excel instances are closed. To do this, open task manager by pressing Ctrl+Alt+Del or right click on the taskbar and select "task manager". In the processes tab, check for any "EXCEL.exe" entries. If you find any, right click on the instance and select "End Process"
Close PIMS and see if this resolves the issue. If there were no such orphan Excel.exe processes and the issue persists, then try one or more of the tips below. One of these may resolve the issue.
Method 1: Excel DDE Settings (Make sure this setting is always followed)
It could be fixed by unchecking “Ignore other applications using DDE” in Excel Settings.
i. Close PIMS and all instances of excel
ii. Open MS Excel
iii. Go to file-> options. This opens up Excel options.
iv. In the Advanced tab under the General section, make sure that the “Ignore other applications that use Dynamic Data Exchange (DDE)” is unchecked.
Once unchecking, close all instances of excel again and restart PIMS.
Method 2: Disabling Report Writer Add-Ins
If Aspen Report Writer is enabled as an Excel add-in, sometimes you cannot open an Excel file directly from the Model Tree in Aspen PIMS.
i. Go to Tools | Program Options | Spreadsheet and select the "Do Not Load Installed Add-Ins When Launching Excel" option.
ii. If you try to open an Excel file directly from the Model Tree it should open.
Method 3: Manually disable add-ins in excel
If the above two doesn't solve the issue, we could try disabling all add-ins in excel, as it has been seen that some of the add-ins interfere with PIMS functionality.
i. Open Excel. Go to File-> options-> add-ins
ii. In the following menu, select manage excel add-ins and click on Go
iii. Disable all add-ins from the dialog box as shown below.
iv. Close all instances of excel and restart PIMS to test it again.
Keywords: Excel, PIMS Model tree, Add-Ins
References: None |
Problem Statement: Activated Dynamics allows you to convert your existing steady state compressor model into a dynamic model with no additional inputs. Apply pre-made templates, emergency scenarios, and results to obtain a full dynamic model without the need to input additional specifications. | Solution: Aspen HYSYS V8.8 now offers Activated Dynamics for one, two, or three stage compressor configurations. A dynamic compressor flowsheet is created from the steady-state model with minimal input using pre-made templates for frequently analyzed emergency scenarios. Users with minimal to extensive dynamic experience can take advantage of this functionality, enabling them to:
· Dynamically model a compressors through the aid of pre-made templates or user generated custom templates
· Leverage pre-made scenarios: Shutdown, Emergency Shutdown, Total Power Loss, and Discharge Valve Failure
· Visualize compressor behavior more easily with pre-configured stripcharts and a variety of results forms
·  Improve the modeling of compressor operation near the surge region with options for non-dimensional and quasi-dimensionless curve
Activated Dynamics results with two-stage template.
To use this feature follow the steps outlined below.
On the Home Tab of the ribbon, click on the Compressor Surge button to launch a new form. On this form you can select how many compressor stages you have, and which template you would like to use. There are pre-made templates available and there is also an option to utilize custom templates. To learn more about the custom templates, please see item 141554. After selecting the stages and template, click on Enter Flowsheet to be brought into a dynamic subflowsheet.
All of the specifications entered in the compressor on the main flowsheet will be brought into the dynamic subflowsheet. A number of different unit operations will be added and configured so the model is ready to run dynamically. Upon entering the dynamic subflowsheet, the Input Summary form will appear. On this form you will be able to view all of the equipment sizing calculated by HYSYS and change them if you wish to do so. The normal HYSYS number convention holds true on this form with blue italicized values being defaults, blue bold values being user set inputs, and black values being calculated.
After reviewing the inputs, an emergency scenario can be selected and the case can be run. For single stage models there are four scenarios available. These scenarios are discharge valve failure, controlled shutdown, total power loss, and emergency shutdown. For multi-stage systems all of the above scenarios are available except for total power loss.
After clicking on run, a number of results forms will appear where you can view the output of the simulation. After observing the results and viewing potential issues, the case can be brought back to its starting point using the Rewind button. This button will bring the case back to the conditions prior to starting the run as well as reset the integrator. Changes can be made and a new scenario can be selected if you wish to do so.
Keywords: HYSYS Dynamics, Dynamics, Compressor, Activated Dynamics, Templates, Emergency Scenarios, Safety, Compressor Surge, Custom Templates
References: None |
Problem Statement: How to manipulate the Controller mode using the Event Scheduler? | Solution: You can use the Event Scheduler to manipulate the mode of the controllers that you have in your Dynamics simulation in an automated process.
If you want more details of how to use the Event Scheduler, please see Solution ID 135823.
In the Event Scheduler, you can define an Action in an Event and set the Type to “Set Controller Mode”.
You will see the current mode of your controller displayed and then decide what's the action you want to perform by selecting a New Mode.
In the attached sample case, two different actions have been created. The first one allows you to change the current position of one of the valves. The second one is turning off the controller of a different valve so this controller will stop manipulating the control valve.
The Event Scheduler's scheme in sample file is as follows:
To see the changes:
1. Open attached case.
2. Start the Event Scheduler.
3. Run the Simulation.
The most simple way to monitor the changes in the controllers is looking at the Face Plates.
You can also track the results using the strip charts. These are showing flow and pressure profile of the model.
Hint: Right click on the strip charts of the attached case and select "AutoScale All Axes" in order to adjust the view of the plots. The strip charts need to be adjusted once the Event Scheduler is initialized.
Keywords: Event Scheduler, controller On/Off, controller mode
References: None |
Problem Statement: This knowledge base article describes how to configure a client computer to use a Network License for V8.8 and below | Solution: This Knowledge Base article walks you through configuring SLM Clients (i.e AspenTech applications) by using the SLM Configuration Wizard. The SLM Configuration Wizard is used to configure the SLM application on all computers connecting to an SLM server on a network or running SLM locally.
To configure a client for Network Licensing follow these steps:
To start the SLM Configuration Wizard:
? On the Windows desktop, click the Start menu; then click Programs | AspenTech | Common Files |SLM Configuration Wizard.
? On the first screen, for question `Will you be connecting to an SLM server over the network?? select:
? YES to connect to a SLM Server (Network License)
? On the Servers screens:
Note: the order of the License Buckets can also be configured within each SLM Server
? On the 'Configure Advanced Settings' screen, select 'Yes' and then 'Next'.
? On the 'Licensing Type' screen:
? On the last screen, click on 'Finish'.
Now the SLM client is configured. Next time you start an AspenTech application, the new settings will come into effect.
Keywords: Network License
SLM configuration Wizard
Bucket
License Server
SLM Server
References: None |
Problem Statement: This knowledge base article describes which version of the SLM client tools is required to properly log the fractional token usage. | Solution: The products will run with SLM V8 but these older versions of SLM would not handle fractional tokens (1 token for more than 1 MV or user). For fractional tokens to be logged each client PC must have the version of the STRGXI2.dll file that is at Build 2014.0.1.351 or higher if running aspenONE V8.x, or Build 2010.0.1.341 if using aspenONE V7.3.
If there are any aspenONE V8.x pre-2014.0.1.351 or aspenONE V7.3 pre-2010.0.1.341 clients connecting to the SLM server, the tokens are not counted for on a fractional basis. To assist in troubleshooting, you can use the SLM server log files to identify the SLM client version number of all connecting clients.
You may upgrade your SLM V8.x or V7.3 client using the aspenONE SLM File Updater located here:
https://esupport.aspentech.com/apex/S_SoftwareDeliveryDetail?id=a0e0B00000BbrcQQAR
Keywords: Tokens
Global share
Aspen Process Explorer
Aspen IP.21 Process Browser (Web.21)
References: None |
Problem Statement: How do AspenONE versions correlate with Aspen PIMS versions? | Solution: Here are how the AspenONE release versions correlate with Aspen PIMS versions. Note that anytime the Aspen PIMS version changes, a new license key is required.
AspenONE Aspen PIMS
Version Version
v2004 150000
v2004.1 160000
v2006 170000
v2006.5 to v7.x 180000
v8.x 190000
v9 - v11 190000
Keywords: PIMS
Internal version
References: None |
Problem Statement: How to move records from one folder to another folder using Aspen SQLplus | Solution: SET EXPAND_REPEAT=1;
FOR SELECT record_name AS moveit FROM sourcefolder WHERE record_name LIKE ''xxx'' DO
INSERT INTO destinationfolder(record_name) VALUES (moveit);
DELETE FROM sourcefolder WHERE record_name LIKE moveit;
END;
-- The "SET EXPAND_REPEAT=1" command prevents overwriting of existing occurrences by the "INSERT INTO" -- The "SELECT" statement selects the records, based upon their name. In this case ''xxx'' is moved. -- The "INSERT INTO" commands inserts the record into the destination folder -- The "DELETE" command deletes the record from the source folder
-- The "END" statement closes the FOR loop.
KeyWords:
move
record
folder
SQL+
Keywords: None
References: None |
Problem Statement: What is the procedure to configure controller(s) for data collection in Aspen Watch Maker? | Solution: The procedure is different for controllers deployed through the legacy ACO base platform (using CCF & MDL or MDL3 file) and the new RTE platform (DMC3 Builder).
ACO base platform (CCF + MDL/3)
1. Before proceeding to add a controller to Aspen Watch, please make sure that the controller is loaded and running on the online server.
2. Copy the CCF and MDL file from the APC Online server and paste it in C:\ProgramData\AspenTech\APC\Performance Monitor\app\<controller_name> folder located in the AW Server.
3. Start Aspen Watch Maker by going to Start | Programs | AspenTech | Aspen Manufacturing Suite | APC Performance Monitor | Aspen Watch Maker from the Windows start menu
4. In AW Maker, you can add controller(s) by click on Actions | Add
5. Click on the Browse button next to CCF Path and File Name, navigate to C:\ProgramData\AspenTech\APC\Performance Monitor\app\<controller_name> and select the .ccf file. Once the .ccf file is entered, controller name will be added by default.
6. Select any of the available collection tasks (TSK_AW0n).
7. Select the appropriate IODMCP as the Cimio logical device name.
8. Select any of the available KPI Libraries. Users may create their own custom KPI libraries to use with controller. Click OK to configure the controller and then again to start data collection.
9. A new row will be visible in AW Maker for the new controller just configure in AW. Wait until Maker indicates a Run status of Success (initially goes to Not Licensed and then to Success after couple of cycles).
10. It is also recommended to set the Auto-Update attribute from Actions drop-down menu.
RTE Platform (DMC3 Builder)
1. The controller must be deployed online first from DMC3 Builder tool. Once it is deployed, it needs to be started from DMC3 Builder tool. Wait for few minutes for the controller to run 1 cycle.
2. Open AW Maker and switch to the APC Applications option to see the new controller automatically listed in here.
3. The user will now select the controller and start data collection as illustrated in the screenshots above.
Keywords: Aspen Watch Maker
Configure Data Collection
References: None |
Problem Statement: This knowledge base article describes how to check the version of the Software License Manager (SLM) client software. | Solution: This Knowledge Base article shows how to check the version of the SLM Client dynamic-link library core component, which is (STRGXI2.dll) Sometimes it may be necessary, for troubleshooting purposes, to determine if a particular .dll file is the correct version.
1. Locate the STRGXI.dll file, which may be located in the following locations:
V7.3 and older versions:
<root>:\ Program Files\Common Files\Hyprotech\Shared directory. 32bit computer
<root>:\ Program Files(x86)\Common Files\Hyprotech\Shared directory. 64bit computer
V8.0 - V10.1
<root>:\ Program Files\Common Files\AspenTech Shared directory. 32bit computer
<root>:\ Program Files\Common Files(x86)\AspenTech Shared directory. 64bit computer
2. Right-click on the .dll file.
3. Select Properties in the context menu.
4. Click on the Version Tab. In the example below the version is 2010.0.0.287.
Keywords: dll, strgxi2.dll, version
References: None |
Problem Statement: Problem with the Aspen Properties databases not being restored when opening Aspen Plus for the first time after installing on Windows 7 or 8 for multiple users as is common at Universities. | Solution: Although LocalDB by default is delivered and installed on Windows 7 or 8 or 10 it should not be used under this situation.
Customers can switch from LocalDB to SQL Server on Windows 7 or 8 or 10 using the following steps:
1. Install SQL Server 2008 Express R2 SP3 or later version as a pre-requisite. Create the security login as "apeduser2/Aproperty88#". Set "Windows and SQL Server authentication mode" with the SQL Server installed.
2. Edit the .reg file attached. Change the APED version number to the current version.
Version MM VERSION APED Prefix New PURE databank
V10.0 36.0 36.0 APV100 PURE36
V9.0 35.0 35.0 APV90 PURE35
V8.8 34.0 34.0 APV88 PURE32
V8.6 32.0 32.0 APV86 PURE32
V8.4 30.0 30.0 APV84 PURE30
V8.2 28.0 28.0 APV82 PURE28
V8.0 27.0 27.0 APV80 PURE27
V7.3.2 26.0 26.0 APV732 PURE26
3. Run the .reg file.
4. Install aspenONE.
5. Right after the installation, launch "Database Tester" (run as administrator) and click "Start". This will launch "Aspen Properties Database Configuration" dialog. Then uncheck "LocalDB" from the dialog. This will switch from LocalDB to the SQL Server installed. Click "OK" to restore databases with the SQL Server installed, instead of LocalDB.
The steps above need to be done only once on each Windows 7 or 8 or 10 machine. Any account logon will use the same databases.
Keywords: None
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.