question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: The output of a Multiply block is in the default units, not in the ones from its input. Why?
|
Solution: The input/output variables of a Multiply block use the <control_signal> variable type, which is a generic type with no units of measurement specified; the units of the variables will depend on the units of the connected model. If there is no connection, there will be no units.
In the attached V7.1. file B2 calculates an apparently erroneous pressure, but B1 calculates the correct value, as its outlet stream is connected to a pressure variable.
This behavior is common to all control models that have input/output variables of <control_signal> type, such as Sum.
Keywords: Multiply, Sum, units
References: None
|
Problem Statement: What causes the Server error in '/AtControlCharts' Application- Run time error for Adaptive Modeling error message when trying to view Adaptive Modeling results?
|
Solution: In Aspen Production Control Web Server, at times the below error message appears when trying to view in the Adaptive modeling case results.
One of the most probable reason for this problem is a system clock mismatch between Aspen Watch server and Aspen DMCplus Online server and the Aspen Production Control Web Server. If this is the case, the problem can be resolved by synchronizing the system clocks on these servers such that the time difference is not greater than 5 minutes.
Keywords: Server error in '/AtControlCharts' Application
Run time error
Aspen Watch
Adaptive modelling
References: None
|
Problem Statement: Models which have been user customized in Aspen Dynamics 10.1 and contain OCX forms, e.g. the PID model, will still be pointing to the 10.1 definition of the OCX form when loaded in 10.2. As a result you may find that you cannot open the OCX form for the model instance in the flowsheet. You will get an error of the following type, the prog-id name varying depending on the control at fault:
The control with a prog-id of AMPID10_1.FacePlate couldn't be loaded. The OCX containing the control probably isn't located correctly.
Check the registry entry for AMPID10_1.FacePlate and make sure the OCX file is placed where the registry indicates it should be.
|
Solution: Go to the customized model definition in the Simulation Explorer and look for the OCX form definition in the Contents of the explorer. Usually you will find the OCX form itself of a certain type, e.g. the Faceplate form of PID will be of type FP and then you will see listed FP itself of type Form Definition.
Select the form definition and then click on it with right mouse button. Choose Edit.
In the Select Control window scroll down to the control you want to update. The name will be exactly the same as the old name in the error message, except for the suffix which will be 10_2 rather than 10_1. Click on the control to highlight it and then click the Select button.
You can now open the form in the flowsheet again.
Keywords:
References: None
|
Problem Statement: Is it possible to manually specify the scan time for a controller being collected on AspenWatch?
|
Solution: The AspenWatch collection for a controller is performed at the same frequency as the controller execution. However, it is not necessary that the AspenWatch collection time and the controller execution time are synchronized. The AspenWatch collection time is internally estimated based on when the user turn on the collection.
It is possible to manually adjust the collection time for a controller and have AspenWatch perform its collection at a particular desired time; Ex.: always 10 seconds past the minute for a one minute controller. The procedure listed below describes how this can be achieved-
1. Start the collection for a controller on AW and ensure that the collection status is Success and note down the ID number for this collection from AspenWatch Maker.
2. Open IP21 Administrator and navigate to InfoPlus.21 | <AWNodeName> | Definition Records | QueryDef | CxxT (where xx represents the AW ID number of the collection. Ex.: a collection with ID 4 on AWMaker would be C04T).
3. Expand the CxxT node and select #SCHEDULE_TIMES.
You should see one entry for the Schedule Time in the right hand panel. Edit the SCHEDULE_TIME column in here to match the schedule time (future time) you desire and hit the Enter/Return key. The changes will not be accepted if you do not hit the Enter key after making the changes. Be sure to enter a schedule time value that is in the future as otherwise the collection will not be conducted properly.
Keywords: AspenWatch
Collection Time
References: None
|
Problem Statement: You have just installed AspenWatch, and because it is a new site, or for some other reason, you do not know the ultimate size and number of controllers, nor the number of Misc or PID tags that will be collected by AspenWatch. Under these circumstances, the spreadsheet is not particularly helpful in determining the size and number of your AspenWatch History filesets. How to you approach this in such a way that what you do now is very likely to be compatible with the situation as your site grows.
|
Solution: is being written, this situation hasn't been evaluated with regard to it's impact on AspenWatch. Performance will still be a consideration. So, thisSolution should be considered applicable to versions up through AspenONE 2006.
Keywords: None
References: None
|
Problem Statement: What is AV in the streams and how is it calculated ?
What is SLIP in the streams and how is it calculated ?
|
Solution: Av is defined as the availability of a stream.
For a flow driven simulation, instead of specifying the flowrate F, the required flowrate FR is specified.
The two variables are related by:
F = Av*FR;
If Av is equal to 1, F is simply equal to FR.
For feed streams, Av is fixed to 1.
For the case of a liquid stream from a vessel (e.g. Flash2 block), Av is related to the liquid level.
As the liquid level becomes too low, Av is ramped down to 0. This means that regardless of the value of FR, the actual flowrate F is zero, which prevents trying to remove more liquid from a vessel that is nearly empty.
Slip = Velocity of vapour phase/Velocity of Liquid phase (the relative velocity of the liquid and vapour phases).
Slip is used in port MaterialPortR as well as in the ports inherited from it (ie MaterialPortRP, MaterialPortRPRev) and it is usually set to 1 except for some systems (pressure relief: expansion and contraction through a pipe) and it is given by:
Slip = Velocity of vapour phase/Velocity of Liquid phase
in case of Vapour-Liquid or Vapour-Liquid-Liquid.
In some models (e.g. pressure relief), SLIP ratio (represented as SLIP in AD) is quite important. For more details, please, have a look at the
Keywords: Availability, Av, Slip, Relative velocity
References: Manual, Chapter 10.
|
Problem Statement: Why Aspen Watch reports show ERROR: Record not found for REPORT NAME: <ReportName>?
|
Solution: Starting V7.3 CP2 using an ADSA name different to that of the Watch server name is allowed; however, the best-practice is to use the same name, i.e. if your Aspen Watch server name is AWSRV, the Data Source should be named AWSRC.
In case the Data Source is changed, the report configuration file (XML) needs to be updated.
The detailed steps to do this are:
1. Run Aspen Watch Maker
2. Choose Tools, Report Management
3. Double-click a report in the list.
4. Click Save in the Report Configuration dialog.
5. Repeat this for each report in the list.
Verify that the XML (C:\ProgramData\AspenTech\SQLplus\public Windows 2008 / 2012) has the new Data Source references, open it with NotePad and check the contents.
Do the same with the XML in the Web (PCWS) server. If they are different check the moveit log file (C:\ProgramData\AspenTech\APC\Performance Monitor\Data Windows 2008 / 2012). The port 12352 is used in the transfer process. WCF is involved, the time difference between both servers has to be less than five (5) minutes. A workaround is copy manually from the Watch server to the Web server the XML files (Windows 2008 / 2012 C:\ProgramData\AspenTech\SQLplus\public).
============================================================================
If the Report has a plot, the message shown is Error - Unknown data source: [Name].
Keywords: Watch, Web, PWCS, Report
References: None
|
Problem Statement: Aspen Watch maker gets a DBWrite Error if the Watch server is V8.4 or higher while Aspen DMC is a lower version like V7.2. The issue occurs because the lower version ccf is missing key internal validation parameters which were added in newer versions.
|
Solution: The structure of the CCF file has changed over the years, with new parameters being added to the CCF and some obsolete parameters being deleted. This introduces a compatibility issue between the CCF file from V7.2 (or earlier) and V7.3CP4 (or later). This could result in DBWrite Error / iGetLong_f ANTROP failed - Validation Error because the v7.2 ccf might be missing some key parameters; the most likely parameter being STAUTOPAIR.
ANTROP is a bridge parameter in watch server which helps smooth function of v8.4 watch. ANTROP fails to produce good values if any of the internal validation parameters in the ccf are missing. For instance in a v7.2 ccf, the STAUTOPAIR parameter is missing. STAUTOPAIR was added as a parameter only in V7.3CP4.
The steps listed below would help fix the above problem if it is caused by the missing STAUTOPAIR parameter–
1. Open the CCF in V7.2 Build and confirm that the STAUTOPAIR parameter does not exist under the General section.
2. Add this parameter as a user defined variable in the ccf with a value of zero, (0) and the keyword LOCAL.
3. Load the CCF online on the DMC server.
4. Please use CimIO T-API (from AW to DMC server) to check the value for STAUTOPAIR. The syntax for T-API is
           M DMCAPPLICATIONNAME STAUTOPAIR VALUE
       Check to see if T-API returns GOOD status with a value of 0.
5. Update the controller collection on the AW server and start collection.
Other newly added parameters which could pose similar problems include:
clpman
cmov
shpman
ssmana
umvcm
umvlp
lstrbi
stmvdurc
stmvstatus
stmvmove
stmvsize
csiind
stcsicl
Keywords: STAUTOPAIR
AspenWatch
ANTROP
References: None
|
Problem Statement: How do you model fire in Aspen Plus Dynamics (APD)?
|
Solution: Fire calculation is supported in several Unit operations block in Aspen Plus Dynamics such as Flash2, Flash3, Mixer and CSTR blocks. Each blocks are associated with required Fire Configure form. For example, to activate fire calculation in Flash2 model, one may need to go to Form || Configure || Vessel and click on check box Perform Fire Calculation
Aspen Plus dynamics supports following Fire standard: 1) API-521 2) API-2000 3) NFPA-30. Depending on different Fire standards, model support feature(s) like Elevation , design Pressure and environmental factors etc.
Insulation and Drainage Credit can be included in any Fire standard.
Keywords: API-521, Insulation Credit
References: None
|
Problem Statement: Why does the RGibbs model in Aspen Dynamics get an error when components are removed from the component list?
|
Solution: The Rgibbs model in Aspen Dynamics actually calls the Aspen Plus model's routines. One side effect of this is that the component list cannot be changed when using the RGibbs model in Aspen Dynamcis. This is becuase the interface including the number of components is set up in the .appdf file that is generated by Aspen Plus.
Keywords:
References: None
|
Problem Statement: How to move libraries and reports from one machine to another
|
Solution: For KPI Library, the user can copy the file from one machine to another.
This file is located under \Aspen Watch\Template\FormulaLibrary.cfg. It
contains all KPI items as built and custom added.
As for the custom report, we don't have a tool to do this transfer
automatically in version 2006.5. But a savvy IP.21 user can manually do
this: all report definitions are stored in AW_ReportDef and
AW_RPTSectionDef. You can download these definitions and upload them to
another AW Server.
Version 7.1 does provide an option in the Maker / Report Management /
Custom Reports to import and export reports. This copies the report
definition file to a text file which can be moved from one machine to
the next.
Keywords:
References: None
|
Problem Statement: AspenWatch can store and monitor PID loops. This
|
Solution: deals with a possible problem in this mechanism.
PID loops must be associated with a specific DCS because the PID behavior is different from one vendors DCS to another's. These differences are addressed in an SQL procedure and a Configuration file for each vendor that is addressed. As thisSolution is written, the latest version of the software is AspenONE 2004.2. With 2004.2, there are currently the SQL procedures and Configuration files for Foxboro, Honeywell, Honeywell OPC, Mod 300, Centum and Delta V. with the following paired files:
AW_PIDC_FOXAPI.CFG
AWP_PIDC_FOXAPI.SQL
AW_PIDC_TDC300.CFG
AWP_PIDC_TDC300.SQL
AW_PIDC_TDC300_OPC.CFG
AWP_PIDC_TDC300_OPC.SQL
AW_PIDC_MOD300.CFG
AWP_PIDC_MOD300.SQL
AW_PIDC_CENTUM.CFG
AWP_PIDC_CENTUM.SQL
AW_PIDC_DELTAV.CFG
AWP_PIDC_DELTAV.SQL
Prior versions, of course have fewer pre-configured files for DCSs. For clients who have a DCS that is not represented in the distributed configurations, there are three empty files, with only the bare bones structure for the SQL and configuration files that must be filled in by the user, according to the algorithms and structures of their particular DCS. These are called CUSTOM1, CUSTOM2, and CUSTOM3, and have the paired files:
AW_PIDC_CUSTOM1.CFG
AWP_PIDC_CUSTOM1.SQL
AW_PIDC_CUSTOM2.CFG
AWP_PIDC_CUSTOM2.SQL
AW_PIDC_CUSTOM3.CFG
AWP_PIDC_CUSTOM3.SQL
It has been known to happen, that a client would make modifications to one or more of the SQL and/or CFG files, and then find that their PID configuration would no longer work.
This is because ALL the files involved with PID configuration are checked for syntax as a group, and a syntax error in any of the files, whether they are used or not, will cause ALL of them to fail.
Solution
TheSolution is in this excerpt from an e-mail from the AspenWatch developer:
If you make changes to any of the AWP_PIDC_CUSTOMx.SQL procedures, you must make sure that it does not have any errors in the SQLplus syntax. If ANY of these procedures have an error (even if it is not referenced by your PID records), the entire PID configuration process will fail.
To test for SQLplus errors, open the .SQL file you may have edited in the SQLplus client program and press F9 to compile/execute the procedure. If any errors are present in the syntax, then it will tell you. You can also test the code against an existing PID loop by adding a call to it at the bottom of the procedure (just after the last End -- End of procedure statement in the file).
For example:
AWP_PIDC_CUSTOM1('FC2001')
This will execute the SQL procedure's logic on the specified PID record name. You can use the debugger feature (new in SQLplus 2004) to debug your procedure as well. To start the debugger, make sure you added the statement mentioned above (with the correct AW_PIDDef record name) and press F8 (step into) two times. Then use the View-> Variables Window menu option to show the procedure's local variable values as you step through the code. You need to click on the Procedure TAB at the bottom of the window to see anything. Keep pressing F8 to step through the procedure one line at a time.
If you find any errors, correct them and use the Record->Save As menu option and remove any trailing .SQL part of the record name before saving it. (you should be prompted to overwrite if you have the name correct - choose Yes).
Finally, double-check any changes you made to the .CFG file(s) to see that you did not introduce a space or other character. All fields must be TAB-delimited in the .CFG files.
Keywords:
References: None
|
Problem Statement: How to take equipment thermal inertia into account in dynamic simulation?
|
Solution: This is best done in Aspen Plus, before you export the simulation to Aspen Dynamics, in the forms Dynamic HT Equipment. There you can specify the mass and heat capacity of the drum, column stages, and sump. Note that the drum should include the condenser, and the sump should include the reboiler.
It is also possible to change the specification in Aspen Dynamics, although this is a bit more complicated. You need to correctly change the parameter that controls the option of thermal inertia, enter the mass and cp and make sure the initial conditions are set to preserve the starting point. A script is the easiest way to achieve this.
The attached script can be used as a start. You need to edit the name of the block B2 to the name of your actual RADFRAC block. You need also to specify the correct mass and cp for the drum, the stage (note that this is the mass for one stage, while in Aspen Plus dynamic input form, this is the mass for all stages) and reboiler.
We change the initial conditions to specify the initial temperature instead of the initial internal energy (or initial pressure or initial vapor flow) so that the starting point remains unchanged despite the addition of the thermal inertia.
To use this script:
first run the simulation in initialization run mode
copy and edit the script, in the simulation explorer, Flowsheet, click on Add Script
invoke the script (right mouse click on the script, select Invoke Script)
run the simulation in initialization run mode
Your simulation is now ready. If you need to switch off the thermal inertia or change the mass, you can simply update the script and re-run it.
Keywords:
References: None
|
Problem Statement: How do I create a Custom Table?
|
Solution: To create a Custom Table:
1. Click New form button and give a title. New Form can also be accessed from Tools menu.
2. Open the form that contains the variables to be copied. Select the variable name, drag the variable and drop it into the table created.
You can also create a list of variables to be copied using variable find tool (from Tools menu).
Note that you cannot drag a stream variable marked with the < or > character.
Keywords: Custom table, form
References: None
|
Problem Statement: AW collection for a controller deployed through APC Builder stays at Initial and never creates a data collection.
|
Solution: When an APC controller is first deployed with AspenWatch option, it is automatically added to the AspenWatch Maker list. When that controller is started collecting data in AspenWatch, a script in the background is ran to build the rest of the records associated with the controller.
If, for some unknown reason the script is interrupted, the test record defined under AW_STTRGDef does not match the name of the test group defined in the controller. This mismatch results in AW collection to fail for this controller, with status on AWMaker showing Initial and never changing toSuccess. The problem can be confirmed by checking the RepositoryErrors.log file located in C:\ProgramData\AspenTech\APC\Performance Monitor\ folder.
To resolve the problem, locate the test group record in IP.21 Administrator and manually change the name of the record to match the name of the test group in the controller. Restart the data collection in AspenWatch Maker and the controller's status should change to Success and AspenWatch should collect data for the controller.
Keywords: Aspen Watch
APC controller
References: None
|
Problem Statement: How to store Aspen online controllers prediction history using Aspen Watch?
|
Solution: The procedure to store the prediction error(s) is using Aspen Watch, through Aspen Production Control Web Server.
1. Make sure that the controller is configured in Aspen Watch for data collection.
2. In PCWS, go to the History tab -> Plot list (left hand pane) -> Add tags
This will show up the tag selector window.
3. From available variables, the CV(s) should be selected for which prediction needs to be stored.
4. Click on “show attributes”
5. Select the attributes from “available attributes/KPI” section. Ex. ACPRER, AVPRER. Click on “Select tags”
Similarly, other prediction attributes like PRDMDLD (model prediction), PREDER (Prediction error) etc. can also be added to the attributes list,
6. Click OK to go back to plot list page.
7. Select the tags for which historization needs to be done, and click “export”
The history data will be stored in a zip file, as shown in the screenshot, at the location - C:\inetpub\wwwroot\AspenTech\ACOView\Export
Keywords: Prediction history
PRDMDLD
Aspen Watch
References: None
|
Problem Statement: Securing an IP21 Database associated with Aspen Watch may cause not licensed status in AspenWatch Maker
|
Solution: AspenWatch (AW) IP.21 database is installed without any default security permission. It is possible to add permission to the database to make it more secure. Here is an example of an IP.21 data base with some form of security configuration.
Once the database is secured, the AW Maker status for all controllers after the database may become Not Licensed, This is because the service that starts the Aspen APC Performance Monitor Data Service would have lost access to the database. The default startup account for that service is Local System which does not have access to the database.
To resolve the problem, change the account used to start the Aspen APC Performance Monitor Data Service to an user with the appropriate permissions, in the example above that would be a user that belongs to the ACOWebAdmin group. Restarting the Performance Monitor Data service after this change should allow AspenWatch access to the database and change the AW Maker status to Success.
Keywords: Secure Database
Not licensed
AspenWatch Maker
References: None
|
Problem Statement: How to model a fire in a reactor tank
|
Solution: To model a fire in a reactor tank:
1. Before starting the dynamic run, right-click the RCSTR block.
2. On the menu that appears, click Forms | Configure.
3. Activate the fire modeling equations by selecting the Perform Fire Calculations check box on the Vessel tab (Configure | Vessel).
4. Click Configure | Fire to enter the fire calculations as shown below.
Input Variables/Parameters
Values
Description
Fire Standard
API-521 (default)
API-2000
NFPA-30
API-521 Fire Standard
API-2000 Fire Standard
NFPA-30 Fire Standard
Elevation
Used by API-521 only: Tank elevation above source of flame
Environmental Factor
0 < EnvFactor < 1
(Default is 1)
All fire standards: environmental factor. Used for insulated vessels only; otherwise, it defaults to 1.
Design Pressure
Only used for non refrigerated tanks and for calculated fire wet area above 2800 ft²
Used by NFPA-30 and API-2000 only: Tank design pressure for fire relief calculations
5. Select any other tank specifications and credits as required in the form.
Keywords: Fire, reactor, RCSTR
References: None
|
Problem Statement: Calculator block and other Flowsheeting Options results are not transferred from Aspen Plus to Aspen Plus Dynamics. What should should be done?
|
Solution: During export to Aspen Plus Dynamics, results of Calculator blocks and other Flowsheeting Options are not available unless there is a result variable in the stream, corresponding to the input variable that is being calculated. Therefore, before exporting to Aspen Plus Dynamics, you should ensure that the results of all Calculator blocks are transferred to the Aspen Plus input forms. This is also applicable to other Flowsheeting Options such as Design Specs and Model Analysis Tools such as Optimization and Data Fit in Aspen Plus.
For stream variables and most block variables, the way to do this is to use the Aspen Plus reconcile facility. Where Input Reconciliation is not available you must manually copy the results and paste them into the input forms.
To reconcile a stream,
1. Right-click on a stream in Aspen Plus and select “Reconcile�
           Â
2. Select the variables to reconcile.
Keywords: Results transfer, Design specification, Calculator
References: None
|
Problem Statement: How to get daily and monthly aggregate AspenWatch data with different starting time than the default starting time.
|
Solution: Daily aggregate AspenWatch data are being calculated at midnight for the previous 24 hours.
Monthly aggregate AspenWatch data are being calculated at midnight of the first date of the month for the previous months.
If a different starting time is desired, there are three options.
1) Use the PCWS web interface and generate reports using Hourly averages with 24 hours at the duration and the end time desired.
2) Using AspenWatch Maker to schedule the custom reports. Chose 1-Day as the option and set the End time to the desired time. The report will produce a daily average with the desired time range.
3) Generate the custom reports using SQLplus. Define an AspenWatch report via Maker, then use the AW_CUSTOM_DATA SQL procedure to generate the reports in different format (XML, HTML, CSV)
AW_CUSTOM_DATA(REPORTNAME CHAR(24), ENDTIMESTR CHAR(24) = '',
HISTTYPE CHAR(8) = '', DELTA INTEGER = 1, OUTPUTTYPE CHAR(4)='CSV')
where,
REPORTNAME is your Aspen Watch report name.
ENDTIMESTR is the report end time (DD-MON-YYYY HH:MI:SS)
HISTTYPE is the data aggregate type (HOURLY, DAILY, MONTHLY)
DELTA is the number of those aggregates to include (e.g. 1 day vs. 5 days)
OUTPUTTYPE is the format you want the data in (HTML, CSV or XML)
Examples:
AW_CUSTOM_DATA('Daily Performance Report','24-JAN-2008 00:00:00','DAILY',1,'XML');
AW_CUSTOM_DATA('My Shift Report','24-JAN-2008 17:00:00','HOURLY',8,'HTML');
Keywords: AspenWatch KPI
Averages
Aggregrates
References: None
|
Problem Statement: Why does Aspen Watch need multiple TSK_IQx configured?
|
Solution: For a regular IP.21, it is recommended to have only one TSK_IQ according to KB 143860. While this advice may hold true for many IP.21 installations, Aspen Watch installations are better optimized with multiple IQ tasks. Aspen Watch run various additional queries and processes and is typically accessing historical data in relatively large chunks. It is therefore designed to spread this load across various IQ tasks instead of a single one. Spreading the load is necessary to gain better performance.
Multiple IQ tasks allow slower queries to execute independently of other fast ones.
Keywords: Aspen Watch
TSK_IQ
References: None
|
Problem Statement: I have defined a Heater model in Aspen Plus where I have chosen as Heat Transfer option LMTD for exporting to Aspen Dynamics.
When I look at the values in aspen Dynamics, I notice that the LMTD calculation does not match my hand calculation of the log mean temperature difference for the inlet and outlet temepratures given in teh block.
|
Solution: Heater assumes a perfectly mixed process side and for the process stream the temperature is made equal to the outlet temperature. As a result you do get a different value from what you were expecting if you were using the inlet process temperature in the LMTD calculation.
The heater block has no dynamic features up to this version. The decision on using the perfect mixing assumption comes from the fact that LMTD will actually only be making more sense and its usage more accurate in a heatX model, rather than the simplified Heater model, which has no dynamic features.
We will review this assumption if and when we decide to include dynamic features in Heater. In the mean time we suggest the use of HeatX for this case instead.
Keywords:
References: None
|
Problem Statement: Aspen Watch (AW) historizes and makes available all the entries that are associated with controller variables by default. The user is able to define specific entries that may be meaningful to him in his installation, but are really specific to only his installation. What can be done to make the values from these user defined entries available for viewing and manipulation?
|
Solution: There is a file named UserEntryTags.txt that is automatically created by Aspen Watch Maker when you load a controller. It contains information appropriate for creating miscellaneous tags corresponding to all the tags that are not recognized as normal entries for the variables. i.e. user defined entries.
The intent is that you utilize this file as an input file for AW Maker to import Miscellaneous tags to manipulate these values however you find necessary.
Obviously, the naming conventions of these files is automatically generated, but it is consistent with the other variables associated with the controller. The user should review this file before using it to ascertain whether or not the naming convention will satisfy his needs
With the 2006.5 release, manipulation of Misc and PID tags has been facilitated. they can be incorporated into KPIs and can be utilized in custom reports.
Keywords: None
References: None
|
Problem Statement: Why is IIS needed on the Aspen Watch server?
|
Solution: The Aspen Watch server requires IIS because it now uses SQLPlus Reports which requires access to the SQLPlus Reports web site.
Keywords: watch, aspen, reports, iis, internet, information, manager, 2006.5
References: None
|
Problem Statement: AspenWatch Inspector did not get installed with 2006.5
|
Solution: Inspector functionality is now found on the Productin Control Web Server, provided that is also upgraded to 2006.5.
The Inspector page for DMCplus Controllers displays a table of numerical data for all controller applications or for all variables within an application. You can choose to view the data as Raw Data, Hourly Statistics, Daily Statistics, or Monthly Statistics.
By default, the Inspector page displays the most recent data, but you can choose to retrieve historical data that is stored in the Aspen Watch database. Also, links are provided for viewing plots of variable histories and summaries of steady-state analyses.
To access the Inspector page for DMCplus Controllers:
1 From the (History tab) NavBar click any of the following:
DMCplus Controllers
-or-
Within the section for DMCplus Controllers, expand the list of options that are available under the desired CONTROLLER_NAME, and then click Overview, Independents, or Dependents.
2 From the menu bar, click Inspector. The Inspector page is displayed.
If, from the NavBar, you clicked DMCplus Controllers or Overview, the Inspector page displays data that is applicable to all DMCplus Controllers applications. Each row of the table is dedicated to a single application.
If, from the NavBar, you clicked Independents or Dependents, the Inspector page displays data that is applicable to a specific DMCplus Controllers application. Each row of the table is dedicated to a single variable in the application.
To use the Inspector page:
1 From the drop-down list (located in the top left corner), select the desired type of time range:
Raw Data (default) Provides data that consists of snapshot values (without any averaging of values obtained during a span of time).
Hourly Statistics, Daily Statistics, or Monthly Statistics Provides averaged results of data samples that were obtained during the specified range of time. (See Note below.)
Note: The options for Hourly Statistics, Daily Statistics, or Monthly Statistics are available only when the Inspector page is displaying variable-specific data for one DMCplus Controllers application.
2 Select either the From current time option (which is the default) or the Time ending at option.
3 If you selected the Time ending at option, then also enter the ending date and time:
Click the day-month-year box. A calendar is displayed. Use the calendar to select the desired date. (By default, the date is the current date.)
Enter values in the hour: minute: second: boxes to specify the desired time of day. (By default, all zeroes are in these boxes.)
4 To facilitate saving data to a file (for long term record-keeping or for sending a report by e-mail attachment), select the New Window check box.
5 Click Refresh to obtain the data that meets the criteria you specified.
6 To obtain more information about table column headings, pause the mouse pointer over each column heading. A ToolTip displays an unabbreviated description.
7 To display the Detail Plot window for plotting a trend line of a variable history, click the <variable name> link in a table cell under the NAME column.
8 To view a Steady-State Analysis summary, click the ssa link in a table cell under the NAME column.
Keywords: watch, inspector, pcws, process explorer, installation
References: None
|
Problem Statement: Does Aspen Plus Dynamics solve the transition from 2-phase relief to liquid only relief?
|
Solution: Aspen Plus Dynamics does not support the transition from 2-phase relief to liquid only relief.
Keywords: Aspen Plus Dynamics, 2-phase, relief
References: None
|
Problem Statement: What is the benefit of removing unused components in Aspen Plus Dynamics and how to do it?
|
Solution: The calculation of the properties of unused components (with mole fraction of 0) can lead to convergence problems. Also removing unused components will make the Dynamics file size smaller and, hence improves run time.
Unused components can be removed either from Aspen Plus or Aspen Plus Dynamics.
In Aspen Plus: Please use Dynamic Configuration > Dynamic Options form
In Aspen Plus Dynamics: Please use the Arrow tabs
Key Words
Components, Convergence, Dynamics
Keywords: None
References: None
|
Problem Statement: How do I model a pipe with varying diameter along the length?
|
Solution: To model a pipe with varying diameter along the length, you need to right click on the model and click configure.Check pipe diameter varies along the length option from Dimension tab. The Model probably will be under-specified by one variable. You may need to go to the all variables table and change the spec for pipe outlet inner diameter to be fixed.
Keywords: Diameter, fixed
References: None
|
Problem Statement: With a new installation of AspenWatch, Inspector fails with message Failed to create empty document. Aspen Process Explorer may also fail with an attime error.
|
Solution: Under some circumstances ATtime.dll might not get registered properly. When this happens, re-registering the ATtime.dll will fix the problem.
One way to re-register:
Open a DOS window and CD to the directory containing the .dll (you can do a search to find it if you don't know where it is)
Then type:
regsvr32 -u ATtime.dll -- to unregister the .dll. It may be be registered but incorrectly. It may not be registered.
Then type:
regsvr32 ATtime.dll -- to re-register the .dll
? Alternatively, you can simply open a DOS window and supply the full path to the .dll in the command.
Keywords: Aspen, watch attime
References: None
|
Problem Statement: Is it possible to use Aspen Custom Modeler to modify and add to my Aspen Dynamics simulation?
You may want to do this in order to:
Edit and extend an existing Aspen Dynamics model, stream, variable type...
Add your own custom models to Aspen Dynamics simulations
|
Solution: You can run Aspen Custom Modeler and Aspen Dynamics in the same window at the same time, if you have a license for both products.
To use Aspen Custom Modeler and Aspen Dynamics at the same time, you need to do the following:
Open either Aspen Custom Modeler or Aspen Dynamics.
Select the Tools drop-down menu and choose Settings...
Click on the Custom Modeling tab.
Ensure the box next to Aspen Dynamics is checked - this adds the Custom Modeling folder to the All Items pane of the Simulation Explorer.
To edit an Aspen Dynamics model you need to do the following:
Open Aspen Dynamics.
Expand the Dynamics library, click on the folder containing the model you want to copy.
Select the model and either press CTRL-C, click with the right mouse button and choose Copy, or choose the Edit pull down menu and select Copy.
Expand the Custom Modeling library and click on the Models folder.
Either press CTRL-V, or choose the Edit pull down menu and select Paste.
Now you can edit the Aspen Dynamics model just like you would your own custom model
The steps are the same if you wish to modify stream, parameter, port, procedure or variable types.
Note that if you want to modify an Aspen Dynamics model that is already being used on the flowsheet then you need to:
Copy the model from the library as explained above.
Save and reload the file otherwise the existing blocks will still using the version from the library, not the modified version
Note that if you want to modify a submodel (such as the stage model in a Radfrac column) you need to copy first the submodel, then the Radfrac model. The order is important, otherwise you will get an error when reloading the simulation.
It is the user's responsibility to update the model when a new version of Aspen Dynamics is released. The customised model will not inherit any changes in the newer Aspen Dynamics model.
Keywords: edit
model
dynamics
custom modeler
References: None
|
Problem Statement: Try to add a controller, and it says Controller already loaded.
This is frequently because of an unsuccessful attempt to update a controller, and the user has decided to simply delete and re-add the controller... accepting the fact that doing this will cause history to this point to be lost.
This problem is considerably less likely to occur in AspenONE versions of AspenWatch, and indeed as conditions that cause this have been found and repaired, it is less likely with each passing version, but some obscure condition might cause this behavior in spite of all efforts.
It is usually an indication that some records have not been deleted after an attempt to remove a controller from the AspenWatch database.
|
Solution: If the version of AspenWatch is AMS 6.0.1, there are some updated queries that deal with problems parsing gain multipliers inSolution 114194.
If your version of AspenWatch is from an AspenONE release, do not useSolution 114194. Newer versions of these queries are in all AspenONE versions.
If your version of AspenWatch is AMS 6.0.1, then make sure thisSolution is applied before resorting to utilizing queries created from the templates below.
Now, assuming that either you are on an AspenONE version of AspenWatch, or you have applied the patch (114194) to an AMS 6 version of AspenWatch, and AWMaker is still failing to add the controller, we proceed with efforts to manually remove any records that remain after trying to remove a controller.
Please note again that removing and re-adding a controller will effectively throw away the history that has been accumulated to this point. If this has not already been done (i.e. you have only tried to update unsuccessfully), and losing history is not satisfactory, then the best course of action might be to note and document as much about the behavior as you can, then send the .ccf and .mdl file to support to have them try to duplicate the behavior, and perhaps have the developer device a patched version for the particular failure your .ccf and .mdl file are suffering.
First, this query will tell you how many records from the old controller are still in the database after you have tried to remove it.
QUERY 1
select name from all_records where name like 'c0n%';
where the n is the ID number of the controller you are having trouble with.
The controller ID is roughly the 8th column in AWMaker.
The above SQLplus query will help you detect which records are left behind. Either delete them by hand if there are just a few, or if there are too many, use the SQL query below as a template, follow the instructions and delete them with the query.
Important: Do not assume these queries can be run as they are without modification and caution. They were not created by a developer, and are very primitive. They will almost certainly require some configuration to your current situation.
Always backup a snapshot file of your database
QUERY 2
WARNING!! This will delete ALL records associated with a controller in an Aspen Watch database where the controller is failing to load.
NOTE:
FIRST: you must attempt to delete the controller with Maker
NEXT: run this query to clean up remaining records (if any)
FINALLY: Modify this variable to refer to the correct controller index prefix
local cid char(16);
NOTE:
that the following executable line will cause all the records in the database associated with the controller with index = 1. If this is not the correct index, use the information in QUERY 1 to determine the correct index and modify the following line:
cid ='c01%';
update aw_depdef set aw_archiving_1 = 'off', aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
update aw_depaggdef set aw_archiving_1 = 'off', aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
update aw_depcalcdef set aw_archiving_1 = 'off' where name like cid;
update aw_inddef set aw_archiving_1 = 'off', aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
update aw_indaggdef set aw_archiving_1 = 'off', aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
update aw_indcalcdef set aw_archiving_1 = 'off' where name like cid;
update aw_subdef set aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
update aw_subaggdef set aw_archiving_1 = 'off', aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
update aw_ctlcalcdef set aw_archiving_1 = 'off' where name like cid;
update aw_etcvdef set aw_archiving_1 = 'off', aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
update aw_etmvdef set aw_archiving_1 = 'off', aw_archiving_2 = 'off', aw_archiving_3 = 'off' where name like cid;
NOTE:
that error messages in the output might not necessarily be bad.
-- If your controller has no records of this type, or if the records
-- were successfully deleted by AW Maker, you will get a message to that
-- effect. the same holds true for the following group of queries:
delete from ScheduledActDef where name like cid;
delete from aw_caldef where name like cid;
delete from aw_folderdef where name like cid;
delete from aw_depdef where name like cid;
delete from aw_depaggdef where name like cid;
delete from aw_depcalcdef where name like cid;
delete from aw_inddef where name like cid;
delete from aw_indaggdef where name like cid;
delete from aw_indcalcdef where name like cid;
delete from aw_subdef where name like cid;
delete from aw_subaggdef where name like cid;
delete from aw_ctlcalcdef where name like cid;
delete from aw_etcvdef where name like cid;
delete from aw_etmvdef where name like cid;
delete from querydef where name like cid;
write '***** Remaining records with prefix: ' || cid || ' *****';
select name, definition from all_records where name like cid
Once the zombie records have been removed, you should be able to add the controller the controller to the AspenWatch database successfully.
Keywords: None
References: None
|
Problem Statement: When launching AspenWatch Inspector, after connecting to the database, there is a message no data available - failed to open %SETCIMLINKS%. An attempt was made to open AMS 6.x database, and the AWEvents probably caused confusion.
|
Solution: There may be a number of causes for this message, one of those being when there is a mismatch between the snapshot version and the version of the running AspenWatch application. A snapshot from an AMS 6x version of AspenWatch, loaded into an AspenONE version of the product for instance will cause such a message.
When Inspector tries to do system message queries, or tag message queries, it tries to get information out of the AWEvents database. In the AMS 6 version, the AWEvents database was an MS Access database. Because of the fragile nature of the MS Access database when used for this application, the AWEvents database was moved to an IP.21 history repository. As a consequence of this, the %SETCIMLINKS% file will exist for an AMS6 system but not for an AspenONE system.
The version of the database can be determined by opening IP.21 Administrator and looking at the record AW_BASE_FOLDER, which is defined by AW_FOLDERDef. In AW_BASE_FOLDER, the AW_DESCRIPTION field contains a version string reflecting the version of the snapshot/database.
Keywords: None
References: None
|
Problem Statement: Is it possible to split a control signal to model the output of a PID controller that actuates two valves?
|
Solution: You can use the SplitRange model from the Dynamics / ControlModels library for Aspen Dynamics. Alternatively, the same model is available in Aspen Custom Modeler under the Modeler / Models library.
The SplitRange model allows you to take an input control signal over a specified range and create two output control signals. The example file attached shows an input to the SplitRange model that varies between 0 and 100. 10% of the signal is passed to one output, with the range of 0 to 10. The remaining 90% of the signal is passed to the other outlet, in the range from 0 to 90.
Keywords: control
pid
controlsignal
signal
split
splitrange
References: None
|
Problem Statement: Aspen Watch uses the standard Cim-IO client program for InfoPlus.21 (cimio_c_client.exe) to retrieve Miscellaneous and PID tag data. There are four of these clients configured by default when Aspen Watch is installed. Each of these clients are associated with one and only one logical device (IODEV1, IODEV2, etc.), and thus can only communicate with one data source. If there are more than four sources of data, you must configure additional clients to be able to communicate with them.
|
Solution: Create additional Cim-IO Clients for Misc and PID tags.
In Aspen Watch, there are four Cim-IO clients that are created by default with the installation of Aspen Watch. These are standard Cim-IO clients for IP.21, but with specific names: TSK_M_IODEV1 through TSK_M_IODEV4.
Every TSK_M_IODEVx task is mapped to a dedicated set of records in the IP.21 database and a corresponding IODEVx logical device entry in the cimio_logical_devices.def file. This means that if you have more than four sources for your data, or for some reason need to use multiple dlgp's, you will need more than four logical devices, and hence more than four Cim-IO clients. You can configure more following the instructions below.
Assumptions are that the user has some familiarity with InfoPlus.21, IP.21 Manager, IP.21 Administrator and Cim-IO.
Guidelines:
The Cim-IO clients have External tasks named TSK_M_IODEV1 through TSK_M_IODEV4 in the task manager. Additional external tasks must be made for any additional clients created. They should be named TSK_M_IODEVx, where x is an increment from the number of the last Cim-IO client external task and external task record that currently exists. If you run out of numbers (0-9), you can also use letters (A-Z), but only one character is allowed.
The Cim-IO clients have various other entries that are required, in terms of record names, logical device names, etc. and the convention is that these names will correspond to the IODEVx that is in the external task and external task record.
In the following explanation, we will assume we are creating IODEVx, where x corresponds to the current number being used.
1. Create a Defined Tasks entry in IP.21 Manager.
Double click on one of the existing client tasks, e.g. TSK_M_IODEV4
In the NEW TASK DEFINITION box, and the Task name (TSK_XXXX) field, change the name to TSK_M_IODEVx, (where x is the appropriate number), then click ADD. The executable is the same for all the Cim-IO client tasks (%CIMIOCODE%\cimio_c_client,exe), and the .out and .err file will be automatically filled in by the IP.21 Manager.
You can create all the External Task entries you intend to create at this point before moving on to the next step.
2. Create the external task records using IP.21 Administrator
Each External task requires an External Task Record in the IP.21 database:
In IP.21 Administrator, drill down to Building blocks, then to External Tasks. Find one of the existing external task records (named TSK_M_IODEVn, where n is any of 1 through 4). Right click on it, and select Duplicate TSK_M_IODEVn. Select the name that corresponds to the new IO device you are making. You will also have to click on the Root Folder name in the dialog before you can save the new record. The External Task record should have exactly the same name as the External task defined in IP.21 Manager. In the resulting record, you will need to change the IO_DEVICE field to reflect the new name (i.e. IODEVx, where x is the number of the new Cim-IO client you are creating).
As with the previous step, you can create all the entries you intend to create at this point. Each of these records will need to be created before you can complete the configuration of the next records.
3. Create the IO device records in IP.21 Administrator
The easiest way to do this is to drill down, in IP.21 Administrator to the CIM-IO section (not I/O, but the CIM-IO that is at the same level as Definition Records, and Building Blocks). Under CIM-IO, you should see the IODeviceRecDef records that already exist, IODEV1 to IODEV4 in addition to any other ones you may have created.
Right click on one of the IODEVn records and select Duplicate. Enter the name for the record you are going to create (IODEVx, where x is the appropriate number.)
After creating the IO Device record, you will need to make it Unusable - right click on the record in the left hand pane (scope pane) and select Make Unusable. Once the record is unusable, you will be able to change the IO_MAIN_TSK field. This will be the External task record name you have created for this Cim-IO Client, then make the record Usable by right clicking and this time selecting Make Usable.
4. Create additional IO-Groups.
Once again, in IP.21 Administrator, drill down to Definition Records, then IOGroupsDef and select IO-Groups. Increment the repeat area count field, #_OF_SELECTIONS by the number of IO devices you are adding. Highlight the #_OF_SELECTIONS repeat area in the scope pane, and fill in the blank occurrences you have just created. SELECT_DESCRIPTION should have the same name as the IO device record. IO_GROUP_PROCESSING should be set to ON and IO_GROUP_PERMISSION should be set to Read Only for each occurrence.
5. Create appropriate entries in the cimio_logical_devices.def file.
Entries in the cimio_logical_devoces.def file are of the form:
Logical device host name dlgp service name
IODEV5 <host> <service name>
Logical device is normally an arbitrary name, however in this case, it must be of the form IODEV<number> and best practices would probably conclude that <number> should increase consecutively.
host name is of course, the name of the host from which the data will be retrieved. It will normally be an interface to the DCS, such as an App node, or a PC which is running the DCS supplied software.
dlgp service name is a name in the services file, that is associated with a port number which coincides with the port number assigned to the server process on the host.
If you have already configured your original four IO devices in the cimio_logical_devices.def file, then you probably have a fair understanding of the linkage and can configure the additional entries in the file for the new clients you have created. If you experience problems, contact AspenTech support.
6. Final steps
Once all the external tasks, supporting records and logical devices are configured, use IP.21 Manager to start each of the new TSK_M_IODEVx tasks. Review the .OUT and .ERR files to make sure they all start without error.
NOTE: If you modify a Logical Device definition in the cimio_logical_devices.def file, you must re-start the corresponding TSK_M_IODEVx task before it will see the change.
Keywords: PID tags, clients, Misc tags
References: None
|
Problem Statement: How to apply a sine disturbance?
|
Solution: You have several options to do this:
tasks
flowsheet constraint
custom model
Task
You can use the SRAMP function to specify a sine-shape ramp.
Task move_B1 runs when time >= 0
base as realparameter;
ampli as realparameter;
period as realparameter;
base : 1;
ampli : 0.2;
period : 1;
sramp(blocks(B1).input_, base + ampli, period/2);
sramp(blocks(B1).input_, base - ampli, period/2);
restart after 0;
End
The advantage is that you can activate/deactivate the tasks and it does not require changing the specifications of the variables. The disadvantage is that you cannot change the parameters when the simulation is running.
Flowsheet constraints
In the simulation explorer, in flowsheet, flowsheet constraints, type the following code:
CONSTRAINTS
// Flowsheet variables and equations...
base as realvariable (fixed, 1);
ampli as realvariable (fixed, 0.2);
period as time_ (fixed, 1);
blocks(B2).input_ = base + ampli*sin(2*3.14159*time/period);
END
You can change the values in the flowsheet constraints. Note that you need to free the manipulated variable.
Custom model
Activate the custom modeling option and create a new model.
Model Disturbance
Output_ as output realvariable;
base as realvariable (fixed, useuomof:Output_);
ampli as realvariable (fixed, UseUOMof:ScaleOf: Output_);
period as time_ (fixed);
Output_ = base + ampli*sin(2*3.14159*time/period);
End
The advantage of the custom model is that you can create easily as many blocks as required, use the controlsignal stream type to connect to the variable to manipulate and have units of measurements for the base and the amplitude variables.
See the attached example. Note that the task does not give exactly the same sine curve, because the first ramp ramps from the current value of the variable, not from the base value.
Keywords:
References: None
|
Problem Statement: A condenser is modelled using HeatX. Phase specific heat transfer coefficients are used in a simulation and get as results an overall heat transfer coefficient U=408 W/m2/K. However, when the file is exported to Dynamic, the value of U changes to 385 W/m2/K.. A similar problem is observed when using rigorous geometry. Why?
|
Solution: What is happening is that in Aspen Plus you use the rigorous calculation mode, which gives you multiple heat transfer coefficients calculated for each zone. In this specific case, we have two zones, e.g. down to dew point of hot side for desuperheating, then condensation of hot side. The average heat transfer coefficient reported is simply the average on area basis (e.g. sum ( areai Ui) / sum (areai) where areai is the area of zone i, Ui the heat transfer coefficient of zone i.
Because the model in Aspen Dynamics is more simple, it has only one zone. It assumes an overall heat transfer coefficient. This overall heat transfer coefficient is calculated from the overall log mean temperature difference, the calculated overall heat duty, and the area, so that the initial heat duty calculated will match Aspen Plus. This may be a bit confusing, but this is a consequence of the assumptions in Aspen Dynamics HeatX model, which has only one zone.
See the attached bkp file (export as flow driven to Aspen Dynamics) and see the spreadsheet with a cross check calculation of the values reported.
Keywords:
References: None
|
Problem Statement: Known Issue: Install Database Configuration utility can fail to complete with a CRDBSETC: Error in CreateDBSharedMemoryObjects error message if Aspen Transition Manager processes are running.
Description: The Install Database Configuration (IDC) procedure of Aspen Watch Performance Monitor can fail to execute to completion if a related program attempts to re-start IP.21 when it detects that IP.21 is not running. The one such program that can cause this problem is the Aspen Transition Manager Server service (and related ATM_IP21.exe process). The ATM_IP21.exe program is launched by the Aspen Transition Manager Server service to maintain a connection to the IP.21 database for ATM applications. If it detects that IP.21 has stopped unexpectedly, it attempts to auto-restart IP.21. This is a problem when running IDC because IDC performs multiple stop/starts of certain IP.21 processes. IDC needs exclusive access to IP.21 tasks during the procedure to properly upgrade and configure the Aspen Watch database. If the ATM_IP21.exe process is running during this process, IDC cannot reliably detect when IP.21 has stopped or started (because ATM_IP21.exe is auto-restarting IP.21 without any knowledge of the IDC process).
|
Solution: Before running IDC, look in Windows Task Manager for any processes that begin with ATM_. If you see any, then use the Services control panel to stop the Aspen Transition Manager Server service (if the service is not running, start it first, then stop it). Verify that all the ATM_ processes are stopped in task manager (these include: ATM_Service.exe, ATM_Admin.exe, ATM_Exec.exe and ATM_IP21.exe). If any of these processes remain, then manually end the process using Task Manager.
Now you should be able to run Install Database Configuration without error. Once the procedure is complete, you can restart the Aspen Transition Manager Server service if desired.
Note: Aspen Transition Manager Service is not required by Aspen Watch Performance Monitor and it is not common to have both products installed on the same InfoPlus.21 server.
Keywords: Install Database Configuration Utility
Aspen Watch
DBCLOCK Error
References: None
|
Problem Statement: I need to change the dimensions of a mixer block. However, I don't want to go back to Aspen Plus and have to re-export the file to Aspen Dynamics. I would prefer to make the change directly in Aspen Dynamics. How can I do that?
|
Solution: In some cases, the only option is unfortunately to go back to Aspen Plus and re-export the file to Aspen Dynamics. In version 2006 we have improved the file import capability in Aspen Dynamics, which hopefully should address some issues with the workflow.
In some specific cases, the change can be implemented directly in Aspen Dynamics.
- restart the simulation
- set the run mode to initialization and run the simulation
- create a kept result (just in case something goes wrong during the next steps)
- open the AllVariables table of the mixer block
- change the internal energy E spec from Initial to Free
- change the holdup Mc from Initial to Free
- if you have a system with only one component:
- change the temperature from Free to Initial
- change the pressure from Free to Initial
- if you have more than one component, change for all but one component, the mole fraction Z from Free to Initial
- you can then change the length and the diameter of the block
- do an intitialization run
Note that if you have a level controller connected to the mixer, you may have to reconfigure it.
Note also that this procedure may not be used if the mixer contains a liquid-vapor system with a single component.
The idea behind this procedure is to use the equation oriented reSolution procedure of Aspen Dynamics, and swap the initial specifications (which specify the initial conditions of the dynamic model, i.e. the data at time 0). Typically you want to maintain the initial temperature and pressure, as well as the initial overall composition. The steps outlined above simply implement that idea.
Keywords:
References: None
|
Problem Statement: I am using the Process Data Excel Addin and selecting the SQL+ function, I have selected to use the SQLplus Entry and Entered query as shown:
|
Solution: This is a know problem and is discussed in KB134687 also. The problem is that the use of a datasource with a name which is also a valid Excel cell reference will force the Addin to look in cell MAN5 for the name of the datasource.
To avoid this issue, please put quotes around the datasource name, in this instance MAN5.
Keywords: No Data Received
Process Data Addin
References: None
|
Problem Statement: Is it possible to use the AspenTech Excel Addins for either Aspen ProcessData or Aspen Batch.21 with Excel v2007 ?
|
Solution: For all versions up to and including v2006, if selected during installation, AspenTech distributes an Aspen Batch.21 and an Aspen Process Data *.XLA file. These are the files that are loaded into Excel to enable the AspenTech Excel Add-ins for those products.
Excel-2007 requires a new modified *.XLA file for either Aspen Batch or Aspen Process Data - actually they are *.XLAM files. It also requires new or modified dll(s).
These new or modified files and dll(s) are only available with the first of our versions that supports Excel2007 which is our version 2006.5
Therefore, the only way we can support the use of Excel 2007 with the AspenTech Add-Ins (Batch and/or ProcessData) would be via an upgrade of at least the A/T Client software to v2006.5
Meaning that we do not support Excel 2007 for use with our Add-ins for any client version earlier than 2006.5
Keywords:
References: None
|
Problem Statement: DMCplus Context server fails without error messages. No obvious problems, such as mis-matched configuration files (see
|
Solution: 115467)Solution
Pending discovery of the cause, the work around for this issue is to set the recovery options for the DMCplus Context Service to Restart the Service for the First failure:, Second failure:, and Subsequent failures:
This work around has proved successful for several clients.
It is possible, that extenuating circumstances could prevent this from being a workable option for your application. If you decide to implement this work around, it is recommended that you contact support to log the incident. Logging the incident enables you to be notified in the event a patch has been made available or, with your cooperation, an executable might be provided that can be used in conjunction with the Microsoft debugger to help diagnose the problem on your system.
Keywords: Context server
Crash
References: None
|
Problem Statement: AspenWatch PID Record Name drop down box only allows one to select from among the first ~100 loops that have been added to the database.
|
Solution: Open Aspen PID Watch
Tools - > Options -> Configuration Options --- AW PIDDef Record Search - Maximum Tags option
The default is set to 100 tags, this can be modified as needed.
Keywords: PID Watch, tags, list, drop, down
References: None
|
Problem Statement: There is no log left in TSK_AW.out and TSK_AW.err file when TSK_Aw crashed with application error.
|
Solution: Use debug diag as command line parameters for TSK_AW task.
And, as an option, setting debug diag verbose (without the quotes) on the command line for TSK_AW task will provide lots of information and it may tell where things are failing.
AWCollect Debug file configuration sample
1. Start InfoPlus.21 Administrator and double click TSK_AW task in Defined Task list and definition of the task will be shown. Write debug diag into Command line parameters and push update button.
2. Scan on the controller which is monitored by TSK_AW in Watch Maker.
Following is example of the debug output.
** AWCollect version 8.0.0 [01-SEP-2005] started Wed Dec 09 17:10:41 2009
Cim-IO Application Id for this instance is : AWCollect_680
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:08:15==
Checking Cim-IO device. Current: New: IODMCP
Connecting to device: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:08:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:10:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612006150
27, 27
New Time, Old Time : 612006150, 612004950
27, 27
Wed Dec 09 17:10:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:10:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:10:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:11:14.3, 674.299988, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:11:14.3, 2925.699951, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:11:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 4 (0.1 sec)
Activating DMCWatch calculations...
EXTASKCHK: actid = 5658
actft = 0
costail = 1
err = 0
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:10:15==
Checking Cim-IO device. Current: IODMCP New: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:10:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:11:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612006750
27, 27
New Time, Old Time : 612006750, 612006150
27, 27
Wed Dec 09 17:11:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:11:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:11:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:12:14.0, 734.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:12:14.0, 2866.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:12:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 1 (0.1 sec)
Activating DMCWatch calculations...
EXTASKCHK: actid = 5658
actft = 0
costail = 1
err = 0
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:11:15==
Checking Cim-IO device. Current: IODMCP New: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:11:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:12:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612007350
27, 27
New Time, Old Time : 612007350, 612006750
27, 27
Wed Dec 09 17:12:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:12:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:12:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:13:14.1, 794.099976, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:13:14.1, 2805.899902, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:13:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 1 (0.1 sec)
Activating DMCWatch calculations...
EXTASKCHK: actid = 5658
actft = 0
costail = 1
err = 0
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:12:15==
Checking Cim-IO device. Current: IODMCP New: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:12:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:13:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612007950
27, 27
New Time, Old Time : 612007950, 612007350
27, 27
Wed Dec 09 17:13:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:13:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:13:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:14:14.0, 854.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:14:14.0, 2746.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:14:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 1 (0.1 sec)
Activating DMCWatch calculations...
EXTASKCHK: actid = 5658
actft = 0
costail = 1
err = 0
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:13:15==
Checking Cim-IO device. Current: IODMCP New: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:13:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:14:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612008550
27, 27
New Time, Old Time : 612008550, 612007950
27, 27
Wed Dec 09 17:14:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:14:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:14:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:15:14.0, 914.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:15:14.0, 2686.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:15:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 1 (0.1 sec)
Activating DMCWatch calculations...
EXTASKCHK: actid = 5658
actft = 0
costail = 1
err = 0
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:14:15==
Checking Cim-IO device. Current: IODMCP New: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:14:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:15:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612009150
27, 27
New Time, Old Time : 612009150, 612008550
27, 27
Wed Dec 09 17:15:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:15:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:15:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:16:14.1, 974.099976, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:16:14.1, 2625.899902, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:16:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 1 (0.1 sec)
Activating DMCWatch calculations...
EXTASKCHK: actid = 5658
actft = 0
costail = 1
err = 0
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:15:15==
Checking Cim-IO device. Current: IODMCP New: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:15:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:16:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612009750
27, 27
New Time, Old Time : 612009750, 612009150
27, 27
Wed Dec 09 17:16:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:16:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:16:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:17:14.1, 1034.099976, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:17:14.1, 2565.899902, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:17:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 1 (0.1 sec)
Activating DMCWatch calculations...
EXTASKCHK: actid = 5658
actft = 0
costail = 1
err = 0
EXTASKCHK: actid = 0
actft = 0
costail = 0
err = 0
EXTASKCHK: actid = 5658
actft = 1078198272
costail = 0
err = 0
recid : 5658
last runtime : ==09-Dec-2009 17:16:15==
Checking Cim-IO device. Current: IODMCP New: IODMCP
dbLastLoad, lastLoad, needReload: 1260343019, 1260343019 0
Wed Dec 09 17:16:15 2009
NO_IND, NO_DEP, NO_SUB: 9,8,0, ErrCode: 0, ListID: 5658
Checking Cim-IO device. Current: IODMCP New: IODMCP
Wed Dec 09 17:17:15 2009
Back from Get_CTL_RunTime()
HR_Upd_Time Read: 611974950, 27
Hourly Update flag: 0
HR_Upd_Time, Time_rec: 611974950, 612010350
27, 27
New Time, Old Time : 612010350, 612009750
27, 27
Wed Dec 09 17:17:15 2009
Before allocating Cim-IO Structures
Wed Dec 09 17:17:15 2009
After allocating Cim-IO structures. Calling Get_CTL_Data...
Checking Cim-IO device. Current: IODMCP New: IODMCP
In Get_CTL_Data: ino, notag : 1523, 1429
List ID: 5658, Timeout_used: 400
Wed Dec 09 17:17:15 2009
Back from Get_CTL_Data.
MDLNAM(DB) : ==C2HDR.Rev00.mdl==
MDLNAM(CTX): ==C2HDR.Rev00.mdl==
MDLNAM(USE) : ====
IdxFlg, timestr, tsec, ctlint: 2, 09-DEC-09 17:18:14.0, 1094.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
IdxFlg, timestr, tsec, ctlint: 1, 09-DEC-09 17:18:14.0, 2506.000000, 60.000000
UpdHr, UpdDay, UpdMon : 0, 0, 0
Put_Cntr_Agg - AggHr, AggDay, AggMon : 0, 0, 0
** Freeing Data Collection structures **
Back from Store_CTL_Data: recid 5658, CTLName: C2HDR IOstatus: 0 initial_flg: 1
Wed Dec 09 17:18:14 2009
CTLName: C2HDR IODevice: IODMCP E_Time: 1 (0.1 sec)
Activating DMCWatch calculations...
Keywords: awcollect.exe
TSK_AW0?
application error
References: None
|
Problem Statement: Aspen Watch model verification may hung-up by submitting several cases in succession. And, its status keeps to be Request or Running. This status would not be changed even after the machine reboot.
|
Solution: Work around procedure is as follows.
1. When you see that the status for your model verification task is not updating (e.g. it stays in Running status). Use Task manager on the Aspen Watch Server machine and kill any SIMDriver.exe processes.
2. Use Aspen InfoPlus.21 Administrator and navigate to the AW_MDLSIMDef record that matches you application (there is one for each Aspen DMCplus controller in the database: <APPNAME>_SIM). Change the AW_RECORD_STATUS = Idle
Now a new Model verification for your controller can be submitted.
Keywords: Model Verification
Simdriver.exe
References: None
|
Problem Statement: What are snapshots in the dynamic model? How do we maintain and use them in simualtions?
|
Solution: Snapshots for the current simulation structure are recorded as the Current Snapshots for the simulation. To access these snapshots:
In the All Items pane of the Simulation Explorer, click Simulation and then in the Contents pane, click the camera icon. Tools---> Snapshots Pull down menu
By default, the current snapshots are saved in ASCII format when you save your simulation as a language text file. The user can verify if this option is turned on, by going to Tools-->Settings->Snapshots-->include snapshots in ASCII save.
When you change the simulation structure, the current snapshots are converted into a single binary format snapshot archive (.snp file) below the working directory of your installation. The directory is automatically given the same name as the simulation input file. To see the snapshot files you have accumulated:
In the All Items pane of the Explorer, expand the Simulation node and then click Results Archive. Go to Tools-->Use/Select Results from the Pull-down form at the top of the Window.
By default, the only snapshots stored are the for the Initial Specification and Dynamic Initialization. It can also be saved when you change the problem (flowsheet structure) (e.g. add a controller)- Archived snapshots - If you accept YES when prompted
The user can activate scheduled or manual snapshots by going to Tools-->Snapshots and in the Snapshot management window, selecting Take Regular snapshots at Interval of .. or Take snapshot now with Description. It is always good practice to assign meaningful names to snapshots instead of SNP001, etc. The user can rename the archived snapshots by clicking on the Results Archive in the Simulations explorer and then selecting the archive (Snpxxx) in the contents pane. Click on the Right Mouse Button to select rename to assign a (descriptive) name.
If you want to rewind to a particular Current shapshot you can either use the Rewind (<<) button in the Toolbar or go to Tools->Snapshot and click on the appropriate snapshot. It is important to note that if you rewind past (to a time before) a snapshot in time, the current snapshot will be lost.
Also, It is important that you rewind to a point where the Converged status is Yes.
Aspen Dynamics creates a folder under the working directory (e.g. C:\My Simulations) with the same name as the problem and stores the snapshot in this folder.
To Initialize a problem with an archived snapshot,
1. Go to Results Archive in the simulations explorer pane and double click on the particular snapshot (SNP---) in the contents pane. A Use window pops up. Select the appropriate description and with the Fixed Free and Initial checked in both copy from and Copy to click on Copy button. You can view the changes in the values by clicking on View changes.
2. Tools/Use/Select Results/Browse (browse allows you to pick literally ANY .snp file on the PC or even anywhere on then network
If you move the files from one computer to another, make sure to include the snapshot (.snp) files around make sure to create appropriate folder in the other machine and move the files to the corresponding location.
If you delete the .snp file by accident you will lose the archived snapshot.
Keywords: Snapshots,Toolbar
References: None
|
Problem Statement: App folder, CCF and MDL were removed and now the AspenWatch controller cannot be deleted from maker.
|
Solution: On the AspenWatch machine, recreate the folder for the controller and populate with CCF and MDL file.
Open Aspen Watch Maker and identify the controller that cannot be deleted, and notice it's ID from the ID column.
Open Infoplus21 Administrator, expand the machine name and navigate down to and open the Definition Records
Move down to AW_CTLAGGDEF and double click to display records on right side of display.
The Cxx_AGG record that matches the ID should be missing.
For instance, if the AspenWatch controller has an ID of 01, confirm C01_AGG is missing.
Then select / highlight an existing Cxx_AGG record and right click and select Duplicate Cxx_AGG
Rename the duplicated record to the missing Cxx_AGG, for our example, C01_AGG and select / highlight the RootFolder and click okay.
Open the record and edit AW_LABEL to the controller name.
Edit AW_LOCAL_CTL_NAME to the controller name as well.
(You must hit enter to same each change as it is made)
Return to Aspen Watch Maker and delete the controller.
When you return to the IP21 Administrator, you should find the new co1_agg has been removed.
Keywords:
References: None
|
Problem Statement: How to modify the global limit of state variables in Aspen Plus Dynamics?
|
Solution: One can specify Lower limit of temperature under Aspen Plus SIM_OPTIONS for global LOWER/UPPER limits of temperature (in the Aspen Plus user interface, Setup | Simulation Options | Flash Convergence). This enhancement helps to be more consistent, and Aspen Plus Dynamics users are no longer need to modify and T_min, if the range pre-specified in Aspen Plus could cover the operation temperature range.
In Aspen Plus dynamics, default values of state variables can be found under Explorer || Simulation || Globals || Dynamic Options. One can modify the number as per requirement of model dynamics.
Note: The global parameters of the state variables such as temperature and pressure to limit them lower and upper bounds are considered while running in dynamics particularly at extreme situations(e.g; vessel drying with constant duty heat options).
Keywords: T_max, T_min, Flash
References: None
|
Problem Statement: Guidelines for sizing the event historian.
|
Solution: First, one must realize that the number of events that will be generated will vary greatly depending on circumstances. In general, use of the spreadsheet that helps calculate tsk_dhis, and then infer a 1:10 ratio for the aggregate historian is *fairly* reliable. There will be variation, but within manageable limits.
Not so the historian for events. We have seen instances where an unforeseen configuration or circumstance has caused thousands of events to be generated every cycle. This is abnormal, but should be considered as a possibility.
The best place to start is with the default, installed configuration, i.e. 3 repositories of ~40MB each unless your installation is very large, in which case it might be a good idea to follow the recommendations for aggregate history (i.e.1:10 ratio with the main historian) but realize that has no mathematical basis, other than the fact that it will be influenced by the number of points in your controllers.
Normally, the 40 MB filesets would be able to last for several months, assuming there is not a number of abnormally active controllers that generate a great deal of events. The reason to say they would be able to handle several months, is because as installed, the timespan is set to 30 days, which means it will shift on time constraint when it might be expected to be only a fraction full.
The timespan can be set in the IP.21 Administrator by right clicking on the AW_EVTH repository, choosing properties and then the global tab. The maximum fileset size can also be set here. The timespan can be set to a maximum of 730 days.
After the 2006 release, the Install Database Configuration? (IDC) step will set the timespan to a minimum of 90 days. (note that if the timespan has been set to greater than 90 days, it will not be reduced by IDC.) This will cause the filesets to shift after 90 days if they haven't yet been filled. If the timespan is set to 730 days, then it is unlikely (though not impossible) that a fileset would be shifted before it was filled to the specified capacity. As with any other IP.21 repository, the user can determine which behavior suits his site and needs, if he understands the behavior.
Once the timespan and maximum size of the filesets have been set, the progress should be monitored (e.g. using IP.21 Administrator to look at the characteristics of the filesets) to see if the number of events being generated over any given amount of time is as expected, or greater, or less.
If it seems it will fill up before it reaches the specified timespan, and there is a desire to shift at a timespan, then increase the fileset size (increasing to greater than 1 GB is not a good idea for any History21 fileset because of underlying OS problems with handling very large files) If it seems that the timespan will be reached before fileset reaches capacity, and you wish to shift on capacity, then increase the timespan.
Once the basic parameters for the system has been established, monitor the repositories, and keep in mind that at any given time, you may briefly encounter an abnormally large number of event activities, and you may want to over-estimate the need in the hopes of containing a (temporary) increase in Event activity.
The user should be able to see from the above discussion that a firm recommendation for the size of the event historian, analogous to the recommendations for tsk_dhis and tsk_aggh, cannot be given with any confidence, but hopefully the above discussion will allow the user to approach the task in a rational manner.
Also, keep in mind how long Event information will be kept. This will also be important in determining the size, timespan and number of filesets for the event historian.
Please contact technical support with your comments, questions, or suggestions.
Keywords: Event History
References: None
|
Problem Statement: How do I diagnose dynamic model with respect to the model equations and variables?
|
Solution: User should be able to analyze the sensitivity of the model equations to the value of any of the variables in the equation. By analyzing sensitivity of the equations, one may be able to find particular model residual or equations that may be hard to satisfy during convergence. To do this, you need to go to Tools || solver Options || Diagnostics and check the box of Equation Sensitivity Check.
During the run, each time the derivatives of the equations with respect to the variables being solved are computed, a check is made and a warning is issued for any derivatives where:
Absolute derivative value is greater than Equation Sensitivity tolerance
Keywords: Sensitivity, Diagnostics
References: None
|
Problem Statement: When the RTE Service is restarted for Aspen APC Controllers being monitored in Aspen Watch Performance monitor, the ONSTS handling reverts to the default even after changing ONSTS for several calculations and saving them. How do I retain the ONSTS handling changes that were made?
|
Solution: The UPDATE action for your controller is being triggered on the Aspen Watch side when a restart of the RTE Service occurs. This is by design in case the controller configuration changed while the RTE Service was unavailable. The standard list of KPIs (and their settings - including ONSTS Handling) that get applied during the UPDATE come from the formulalibrary_base.cfg file in the <drive>\Aspen Watch\Templates folder. This template file needs to be updated so it uses your preferences rather than reverting back to the default during an UPDATE.
following is the procedure to update the base formula library:
1. Make a copy of the FormulaLibrary_base.cfg file and rename it to FormaulaLibrary.cfg
(if there is already a FormulaLibrary.cfg, then rename it to something else so you can use that name).
2. Access one of the KPIs in Maker that you wish to modify.
3. Make the change to the ONSTS Handling option.
4. Choose the Save to Library button. This will modify the FormulaLibrary.cfg file with your change(s).
5. Copy the FormulaLibrary.cfg file to FormulaLibrary_base.cfg
Next time an UPDATE event occurs, the settings for your KPIs should be populated as expected from the updated FormulaLibrary_base.cfg file.
Keywords: ONSTS handling
RTE Service
References: None
|
Problem Statement: Aspen Watch Performance Monitor - all versions
|
Solution: The directory structure on the Aspen Watch machine should match the Aspen DMCplus server with no subdirectories between the App folder and the controller folders. If the directory structure does not imitate what is on the Aspen DMCplus server do the following:
Stop the collection in AspenWatch Maker.
Go to the IP21Administrator to redefine the path, this is done in the Definition Records / AW_CTLDEF
The new directory structure is established on the AspenWatch machine under the APP folder and the controller folders contain the latest CCF and MDL files.
Start the controller collection in AspenWatch Maker.
Keywords: None
References: None
|
Problem Statement: In a non-feed stream, the variable vf is not active. How can I find the vapor fraction of these streams?
|
Solution: In A+ Dynamics, streams are not flashed and therefore vapor fraction (vf) is not available for non-feed streams. However, in most cases, the vapor fraction of a product stream can be found from the upstream block (model/unit op), i.e., the block that the source of the stream is attached to.
Keywords: vapor fraction, stream. vf
References: None
|
Problem Statement: How do I determine the record name associated with a recid and translate the error code?
In AspenWatch Maker, the status of a collection is reading DB_Write error.
Inspecting the .out file for the TSK_AWxx associated with the collection, the following message is observed:
Write to DB (IND Group 3) unsucessful. recid:5447, numok:28, err:-15
|
Solution: In order to determine the record name associated with Recid 5447, open SQLplus and execute the following query:
select name from all_records where recid=5447 (This provides the record name for record id 5447)
If you want to get the definition along with the name, execute the following:
select name,definition from all_records where recid=5447
To translate the error code, -15, visit the Infoplus21/include directory and refer to the setcim.h file. The error codes are translated there. In this case -15 is Invalid field type.
Keywords:
References: None
|
Problem Statement: How is controller input calculated for direct and reverse action?
|
Solution: The controller input is calculated depending on the specified controller action. If the action is set as Direct, input is calculated as SP - PV. When we manually increase the set point, the input will be increase, resulting in a higher output value. If the action is Reverse, input is calculated as PV-SP. When we manually increase the set point, the input will decrease, resulting in a lower output value.
Keywords: controller input, error.
References: None
|
Problem Statement: Sometimes, the output does not appear to be a result of simple division or multiplication operation. How do Divide and Multiply block calculate the output?
|
Solution: The answer is that the simple division or multiplication operation is sandwiched by unit conversions. Internally, Aspen Plus Dynamics uses Metric units, and the division in Divide or multiplication in Multiply unit is always performed in Metric units. Before the division or multiplication, the inputs are converted to values in internal units. After the division or multiplication, the result is converted to value in user selected units as output.
If the two inputs and output are dimensionless or in Metric units, the output can be related to inputs according to the operation, division or multiplication. If a different unit profile is selected, the output is often not related to the inputs in a simple manner, as unit conversions are part of the calculations in these cases.
Keywords: Divide, Multiply
References: None
|
Problem Statement: The AW_FORMAT field of the AW_MSCDef record defaults to F10. 4. This makes many of the numbers on Process Explorer trends have too many significant figures. I would like an automated method for changing AW_FORMAT to another value (e.g., F 6. 1).
|
Solution: The AW_FORMAT field was defined during the record creation time. The following SQL statement can easily change ALL the AW_MSCDef defined record to use F6.1 as AW_FORMAT.
UPDATE AW_MSCDef
SET AW_FORMAT = 'F6.1';
After you run this sql, all the AW_MSCDef defined records will all use F6.1 to present the value.
Keywords:
References: None
|
Problem Statement: How can you troubleshoot SQL queries used in AspenWatch?
|
Solution: A lot of ApsenWatch feature,s utilitize SQL queries to accomplish their objectives. Sometimes due to an error in configurations or bugs in the query, the query may not run.
To see the error in the query, go to the query in Infoplus.21, examine the status and output.
-Go to Start>All Programs>AspenTech>Aspen Manufacturing Suite>Apsen Infoplus.21>Infoplus.21 Administrator
-Find the query with the error under Querydef
-If you have error, it would show in the STATUS and ERROR_TYPE
-The default value for #OUTPUT_LINES is zero, change it to 10 or 20 then the debug message would be available for examination.
-The default value for #OUTPUT_LINES is zero, change it to 10 or 20 then the debug message would be available for examination.
Keywords: AspenWatch SQL queries
References: None
|
Problem Statement: Why can I not see free variables for input control stream connections?
|
Solution: When controlled streams are brought into flowsheet, each streams and blocks are highlighted with multiple ports. You are able to control which ports to show for available connections. Normally, you would see only fixed variables are available for control stream connections. There is a button called Only Fixed variables will be available when connecting an input control stream you should be able to uncheck the option in order to view fixed as well as free variables for connecting input control stream. This is sometimes important settings when you want to control any intermediate block or stream parameters but their variables are not normally available for input connections as they are free. To check this option, Please go to Tools || Settings || Control Stream Connections:
Keywords: fixed, control stream
References: None
|
Problem Statement: When using drag and drop from Tag Browser (from both Aspen Process Explorer and Excel Add-in), the following error message is presented:
Run Time error '-2147467259' (80004005) Method '~' of object '~' failed
|
Solution: The first time a user launches Aspen Process Explorer and opens the Aspen Tag Browser, the system automatically creates some entries in the HKEY_CURRENT_USER registry section under the following tree:
HKEY_CURRENT_USER\Software\AspenTech\Aspen Tag Browser\Options.
This is where the Aspen Tag Browser stores its settings.
The Aspen Tag Browser creates two new keys (if they do not exist) named CDDAvaContents and CDDSelContents for the available and selected options for the drag and drop feature of the Aspen Tag Browser. Make sure that these keys are set to:
SERVER(S)MAP(M) for the CDDAvaContents
TAG(T)SERVER(S)MAP(M) for CDDSelContents.
Keywords: Method '+' of object'+' failed
Tag Browser
References: None
|
Problem Statement: Can Aspen Plus Dynamics handle vapor phase polymer components?
|
Solution: Vapor phase polymer components are not supported in Aspen Plus Dynamics. Aspen Flash calculations treats polymers as non-volatile components. If Aspen Plus simulation flashes even trace amount of polymer appearing in the vapor stream of flash operations (Flash2, Flash3), the dynamic simulation will be under specified, and the run button will not be available. This occurs because the vapor stream attributes in the vapor stream, the simulation becomes under specified.
To solve the problem, the vapor pressure parameters need to be adjusted in Aspen Plus or the Polymer_in_Stream value needs to be changed from Yes to No, in the vapor stream (S2) connected to flash block.
To change the Polymer_in_Stream value, please select Vapor Stream (S2) > Polymer Inputs > Polymer_in_Stream > No
Key Words
Polymer, Vapor Phase, Flash
Keywords: None
References: None
|
Problem Statement: 1. Is there a VB program example with code for adding tags and scooters, and deleting tags and changing timespan using VB?
2. Is there a recommended way of saving a tag list from a VB Form?
|
Solution: Answer # 1:
An example is installed with Process Explorer. It is called TrendForm.apx and is located in the
<install drive>:\Program Files\Aspentech\APEx\Samples\ProcessExplorer\VBForm directory.
Answer # 2:
The above example form does not allow saving the tags in the form and have them reloaded with the next start. The code sample below uses the Container Control which makes the area like Process Explorer and allows the user to save and reload the form with the tag list.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Private Sub CommandButton1_Click()
' Container1.LoadXML (d:\delete files\sample.xml)
test1 = Container1.ShowOpen(d:\delete files\sample.xml)
Container1.Load (test1)
Container1.TimeLineVisible = False
End Sub
Private Sub CommandButton2_Click()
test1 = Container1.ShowSave(d:\delete files\)
Container1.Save
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Keywords: add
delete
VB
VBA
time
span
References: None
|
Problem Statement: What is the maximum number of tags that Process Explorer can display in a trend plot?
|
Solution: While there is no hard coded upper limit, the maximum number of tags that can appear in a trend plot depends on these factors:
Speed of your client or data source
Amount of memory on your client system
Type of data presentation
Amount of data returned from your database
Overall size of your database
Data source/client configuration
Keywords: Maximum number of points
Maximum number of tags
Points
Tags
Display
Plots
References: None
|
Problem Statement: If you have exhausted the options in KBs 107955 and 110698 to resolve problems like Connection Failure is Fatal, IP.21 is not currently running, NAN or ****** displayed in the tag Value field in the Process Explorer Legend,
you can use the information in this KB article to help you confirm if Aspen Process Explorer client is able to successfully connect to an Aspen InfoPlus.21 server.
|
Solution: An Aspen Process Explorer clients use TCP to communicate with Aspen InfoPlus.21 through a Remote Procedure Call (RPC) server named TSK_APEX_SERVER.
The error messages described above could mean that the Aspen Process Explorer client is unable to communicate with the task TSK_APEX_SERVER in the InfoPlus.21 system.
There may be multiple reasons for this. For example, the client application is attempting to access the database across a firewall and may encounter a problem if the firewall blocks access.
To determine if the Aspen Process Explorer clients are able to communicate with the TSK_APEX_SERVER in the InfoPlus.21 system, use the Windows netstat command with arguments to confirm that a communication link is established between the client and server programs.
The output of the command shows in the first column a lists all of the TCP and UDP connections on the machine running Netstat. The second column is the machine's local IP address and port number, while the third is the remote or foreign address and port number. The fourth column is called State, which is the state that the connection, or potential connection, is in. 'LISTENING' shows a classic open port listening for inbound connections. 'ESTABLISHED' means there's an actual connection between your machine and the remote IP and port that is able to exchange traffic. The final column is the owning Process ID associated with each connection.
In the InfoPlus.21 system open the IP.21 Manager program and select the TSK_APEX_SERVER in the list of Running tasks to find the its Process ID.
                   Â
Open a CMD window in the Aspen InfoPlus.21 system and execute the following command using the Process ID argument:
                         netstat -aon | find 46824
The output of the command shows a TCP port connection with a LISTENING status:
this is the typical output when there are no clients connected to the TSK_APEX_SERVER RPC server, the TSK_APEX_SERVER is in a LISTENING state waiting for clients connections.
When a client connects, the output of the command will show a second line with the connection information to the client:
the client, (IP 10.32.160.162) is connecting to the InfoPlus.21 system, (IP 10.32.160.176) and the connection status is ESTABLISHED.
If there was no such ESTABLISHED connection line in the output that would indicate that there's a problem establishing the connection, possibly because a firewall or other device is blocking the connection.
To allow for communications across firewalls, Aspen InfoPlus.21 includes an option to assign a specific port number for each RPC server tasks. If the firewall permits two-way communication through the specified ports, clients will be able to connect to the server. See KB 104056 for further information on how to setup the TSK_APEX_SERVER to use a specific port that is opened in the firewall.
Keywords: Connection failure is fatal
Connection failure
fatal
firewall
References: None
|
Problem Statement: There are several applications whose presence conflicts with the functionality of the Aspen Tag Browser when installed on the same machine. Some of them are: Crystal Info, Hummingbird, and a few older DOS applications. A common symptom of the conflict is that the Tag Browser Server icons are missing and the error message 'no server connected' is displayed on the status screen. The
|
Solution: to this problem is described in AspenTech Knowledge Base Article # 107949. However, on some rare occasions theSolution won't work. In those cases, the only way to troubleshoot the problem, other than reinstalling Process Explorer (which often doesn't work either), is to replace, one by one, the dll's responsible for the proper operation of the Tag Browser.
A list of the dll's responsible for the proper operation of the Tag Browser is provided below.
Solution
DLL NAME:
VERSION: (It depends on the version of your aspenONE software)
ADVAPI32.DLL
AtTagBrowserPE.DLL
AtTagBrowserSQLplus.DLL
GDI32.DLL
KERNEL32.DLL
MFC42.DLL
MSVBVM60.DLL
MSVCRT.DLL
NTDLL.DLL
OLE32.DLL
OLEAUT32.DLL
RPCRT4.DLL
TagBrowser_en.DLL
USER32.DLL
VERSION.DLL
OLEDB32.DLL
Keywords:
References: None
|
Problem Statement: Have you ever wondered when looking at 'something' in Aspen Process Explorer that involved manipulating the raw historical values stored in the database, whether the math calculations were performed on the client where Aspen Process Explorer (or Web Server running Aspen Web.21) is running, or on the server where Aspen InfoPlus.21 or Setcim might be running?
This 'something' could include:
Looking at a Trend Plot in which you have chosen to look at Aggregates such as Averages or Standard Deviations.
Looking at an Excel Spread sheet in which you have chosen to look at Aggregates such as Averages or Standard Deviations.
Looking at a 'Q' plot that is displaying a 'Q' record.
Looking at a 'Q' plot that is displaying an 'adhoc' record.
Using the new feature introduced in V5 to do ad-hoc calculations.
Using the new RDBMS feature introduced in V5 to read data directly from a Relational Database.
|
Solution: Most calculations, especially when choosing one of the 'Types' from 'Tools => Options => Sampling' in Process Explorer, are performed on the Server side. That is, they are performed on the machine where the AspenTech Database is running, and the newly calculated values are sent for plotting by Aspen Process Explorer.
There are a few exceptions where the calculations are performed on the Client box running Aspen Process Explorer (or Web Server running Aspen Web.21). They are:-
'Q' plot that is displaying an 'adhoc' record. Here the subgroups are formed and the other calculations are executed on the Client side.
Ad-hoc calculations are executed on the client side
The Process Data for RDBMS also goes directly from the client to the RDBMS database.
Keywords: None
References: None
|
Problem Statement: What-if simulation use current values feature does not report steady state target which match the online controller steady state target for some controllers with ramp variables. Please note that these are values generated by the simulation even before performing a what-if calculation. The values could be off for What-if simulation for a controller which has active constraint variables limited due to a ROC DWN or ROC UP status.
|
Solution: What-if simulation (WIS) is not an exact duplicate of the behavior seen in online controller and the purpose of what-if simulation is to perform simulation and to get a quick understanding of the response of applications for limit adjustments. The following explanation on working mechanism provides information about why there is a difference between the values for steady state target of WIS and online controllers.
Working mechanism -
WIS uses a special handle to approximate the unknown open loop CV predictions which is internally within Aspen watch referred to as AW_PSSDEP. When WIS runs, the DEP value for a CV is replaced by PSSDEP. PSSDEP (Approximation of CV open loop predictions) contains information about MV moves whose impact will show on the CVs and thereby provides a SS target result for WIS which is identical to Online Controller target values.
Comparison of results between WIS and Online controller
1) The SS Target calculation results for WIS and Online controller could be different when the WIS runs for Active constrained MVs which are constrained by the SSSTEP in up or down direction, which means MANACT = 4 or 5 (ROC UP or ROC DN). This is because the initial conditions for the online controller is different from the initial condition for WIS and therefore the approximation used by WIS could lead to slightly different result compared to Online controller.
2) However under situations where the Active constrained MVs are constrained due to limits then the steady state target results might look quite similar.
3) The other caveat is the SSDEP for Ramp variables in WIS may not match the values shown in online controller because WIS is using an approximation of open loop CV predictions.
Keywords: What-if Simulation.
.CCF file.
Ramp variables
References: None
|
Problem Statement: I have created a model in Aspen Custom Modeler. How can I use this model in Aspen Plus Dynamics?
|
Solution: Go to Start Menu -> AspenTech -> Process Modeling (V8.4) -> Aspen Plus Dynamics. Open a dynamic file and check Tool -> Custom modeling
Open the ACM file where we have built the model.
Now you can drag and drop model to the flowsheet. Please make sure you are using right component list.
Keywords: Model, dynamic
References: None
|
Problem Statement: Why Aspen Process Explorer keys are no longer distributed with AspenWatch Server/Desktop or RTOWatch?
|
Solution: The Aspen Process Explorer key was originally included with these products to facilitate plotting within the Aspen Watch Inspector desktop tool. With the migration of the Aspen Watch Inspector functionality to the Aspen Production Control Web Server in V2006.5, the need for a Aspen Process Explorer license was superseded. The Aspen Production Control Web Server uses an embedded Aspen Process Explorer plot control that does not require the Aspen Process Explorer license. Aspen Process Explorer is still available to both perpetual Aspen InfoPlus.21 customers and to token customers.
Keywords: Process Explorer, AspenWatch, RTOWatch
References: None
|
Problem Statement: Unable to find the counters inVariable Binding
|
Solution: In 2006.5, changes were made regarding how the counter value is calculated. Here are steps to configure a KPI with counter:
1. On Custom Calculation Configuration page, select Summation as Calc Type from the pulldown list;
2. Then select a Var Group (MVs, CVs, FFs,etc);
3. On Variable Binding page, select Variable/Tags as Scope;
4. If you want to summarize all the values for a specific type of variables, choose DEP.* or IND.* from the variable list and then select an attribute (such as DEPSTA, etc).
To see an example, you can look at 03PCTMVON by double-clicking it on Custom Calculation Configuration page.
Keywords: kpi, counter, aspenwatch
References: None
|
Problem Statement: Aspen Watch Model
|
Solution: To test to see what model file is found in the context, you can use Cim-IO Test API to fetch the MDLNAM entry for the controller (see below).
If the name in the context shows the old name, try re-starting the DMCplus Context Service and also the dmcp_viewsrv on the DMCPlus machine. Perhaps the context the Cim-IO server is mapping to is an old one. Corrections have been made to some locking issues in Manage and the viewsrv in 2006.5 and later.
Keywords: None
References: not updating
**
There is a problem with model updating and wrong reference.
When a controller was added to AW Maker, after a few cycles, the status on Maker shows Success. However, on IP.21 the AW_CL task for this controller was stopped. The output file states error loading DMCplus model file. The name of the model file referred in the output file was not the current DMCplus model file.
On the IP.21 definition record, it also has a value of a ghost DMCplus model file.
Starting and stopping IP.2, deleting the controller from Aspen Watch Maker and adding it back and manually copying the ccf and model from the DMCplus server to the Aspen Watch server did not help
|
Problem Statement: Not able to see custom tags when using Matrikon OPC client after upgrade to v7.3
|
Solution:
Keywords:
References: None
|
Problem Statement: How does Aspen Watch Maker calculates the threshold for a new baseline case?
|
Solution: Starting with V7.1 when you generate a new Baseline Case, the calculated threshold is = MAX(0.5, 3*Sigma Deviation).
If you review your results you will see a lot of 0.5 values for the threshold, however you can manually change this values:
1. On Aspen Watch Maker go to Tools / Baseline Management select your case and click review. You can edit the values here or you can copy and paste them to excel for further treatment.
2. On the PCWS go to the History tab, select the desire KPI and click on Threshold. If you have enough privileges you will be able to change it.
Please keep in mind that a Threshold determines how far away the KPI value can be from the reference value before it is deemed as an indicator of good or poor performance.
The following Threshold types are available, as appropriate for the physical meaning of the KPI:
Type
Criterion
Poor
Acceptable
Good
Alarm - High - Actual
(Value – Baseline)
> Threshold
> 1/2 Threshold
< 1/2 Threshold
Alarm - Low - Actual
(Baseline – Value)
> Threshold
> 1/2 Threshold
< 1/2 Threshold
Alarm - High - Percent
(Value – Baseline) / Baseline
> Threshold
> 1/2 Threshold
< 1/2 Threshold
Alarm - Low - Percent
(Baseline – Value) / Baseline
> Threshold
> 1/2 Threshold
< 1/2 Threshold
Alarm - Deviation - Actual
Abs(Value – Baseline)
> Threshold
> 1/2 Threshold
< 1/2 Threshold
Alarm - Deviation - Percent
Abs((Baseline – Value) / Baseline)
> Threshold
> 1/2 Threshold
< 1/2 Threshold
Event
True or False
True
-
False
Constraint
True or False
True
-
False
Keywords: Aspen Watch Maker
Baseline
Threshold
KPI
References: None
|
Problem Statement: When trying to configure a Miscellaneous tag in Aspenwatch Maker, V7.3 w/updates and he configures an IOGETDEF, it tells him to go back and configure as a IOLONGGETDEF. When he configures as an IOLONGGETDEF, it tells him to reconfigure as an IOGETDEF.
|
Solution: Because of the architecture we have in place for IO Get records, we have to prevent mismatch between IOGetDef and IOLongTagGetDef records being accessed by the same IO-Group tag (IODEV1, IODEV2, etc.). We did not begin enforcing this rule until recently.
If you've been using the IOLongTagGetDef records before this rule began being enforced, it may be that the offending IOGetDef records is: D-IOGet
This record is a required template record that is used by the database. It does not affect Aspen Watch record processing and can be safely ignored. This record is probably using IODEV1 in its IO_GROUP field. This is what is causing the problem. Our check for IOGet record type association is not filtering out this template record during the check.
To work around this problem, temporarily assign the D-IOGet record's IO_GROUP field to some other unused IODEVn group.
Keywords:
References: None
|
Problem Statement: Heating Value Sensor to show Gross heating value and net heating values
|
Solution: Steam sensor now allows user to calculate the gross and net heating values. To activate, right click on a material stream, select Forms|ConfigureSensor and then select Low Heating Value from available properties view to right side. See attached example for the QVALGRS and QVALNET values associated with SSensor(1) section. You need to scroll stream PRO's all variables form to the end to see them.
Keywords: Heating value, sensor
References: None
|
Problem Statement: Aspen Dynamics does not map Aspen Plus design specifications, Fortran blocks, optimization blocks, sensitivity blocks or balance blocks to the dynamic simulation. This is because a dynamic simulation is always a rating mode calculation, not a design calculation, so these design specifications and blocks may not be relevant.
However, you can enforce the constraints implemented by these blocks by adding a controller to the dynamic simulation. Some Aspen Plus models enable you to vary a parameter using a design specification, or a Fortran, optimization or sensitivity block.
For example, in RadFrac, you can vary the feed stage location. When you vary a structural parameter, the steady-state results are calculated using the value of the parameter after it has been varied. However it is the value of the parameter that you specified on the input form that is used in the Dynamic simulation. This inconsistency may result in the initialization of the dynamic simulation failing.
|
Solution: To avoid the initialisation failure or an initialisation to a different condition where the system will not be at steady state, you should use Reconciliation in Aspen Plus, then remove or hide any design specifications and model analysis blocks that vary a structural parameter, run the steady-state simulation, and then export the dynamic simulation.
To reconcile a block or stream in Aspen Plus you can click on it with the right mouse button, then choose Reconcile...
For more details on using Reconciliation and on what is supported in Aspen Plus please look at the followingSolutions:
For Streams: 102354
For Blocks: 108012
Keywords:
References: None
|
Problem Statement: AspenWatch 2006.5 w/CP1
How to configure additional IODEVs beyond the default 4
|
Solution: Download and refer to the attached IODeviceConfig.doc
Keywords: Watch, IODEV, configure, new
References: None
|
Problem Statement: Each Aspen Watch has 3 external task TSK_PID[n] (n=1~3). But, what they do are not documented.
|
Solution: TSK_PID[n] external task handles the performance and history aggregation calculation for PID tags.
The Task ID of Tag Maintenance Tool Input file determines which TSK_PID[n] external task handles the performance and history aggregation calculation for PID Tags.
Keywords: TSK_PID[n]
PID
Task ID
Tag Maintenance Tool Input file
References: None
|
Problem Statement: How are sump and tray modeled in steady state and dynamic model?
|
Solution: Sump is the bottom of the column to which the bottom product and boil up stream are connected. It is similar to a vessel with liquid and vapor phase in equilibrium. Tray is where upward vapor flow, downward liquid flow and optional feed meet.
In a steady state model, only the equilibrium relationship between vapor and liquid is modeled. The sump and tray have the same model.
In a dynamic model, tray hydraulics is part of the tray model to determine the column pressure profile, while the sump is essentially modeled as a vessel. A level control is often attached to sump. A temperature control is sometimes optionally attached to a tray.
Keywords: Tray, sump
References: None
|
Problem Statement: Aspen Watch Disc Size Calculation spreadsheet included in aspenONE 2006.5 Documentation DVD is not correct. It says that AW_AGGH total size is 1/4 the size of TSK_DHIS. As a matter of fact AW_AGGH consumes as much disk space as TSK_DHIS.
|
Solution: Use Aspen Watch Disc Size Calculation spreadsheet included in aspen ONE 7.1 Document DVD.
Keywords: AW_AGGH
TSK_DHIS
Aspen Watch Disc Size Calculation spreadsheet
WatchDiskSizeCalcs.xls
References: None
|
Problem Statement: how do you include cumulative total flow over the dynamic run in the stream report?
|
Solution: One can report total cumulative flow in a particular stream to estimate total fluid transferred through feed or product line over the period of dynamic run. To do this, please follow the following procedure:
1) Right Click on any stream and configure sensor
2) Check to calculate phase Properties
3) on the additional properties table, move the cumulative flow on to the right side
The configured stream should show total and component cumulative mass, molar and volume flow in the stream.
Keywords: Configure sensor, Fluid, Cumulative flow
References: None
|
Problem Statement: Task TSK_IQ# (#=1,2,...) does not start and the following error is encountered when starting up an InfoPlus.21 database after a shutdown.
Error creating event object, error code=183
|
Solution: TSK_IQ4 is executing 2 query records, namely, AW_RunCVAnalysis and AW_CVASched. Both query records are calling on the executable called PerformAnalysis.exe program.
This issue normally will be resolved by simply rebooting the entire machine. However, this is not necessary. It can be resolve by performing as follow:
1. Launch Windows Task Manager.
2. Select Details tab in Windows Task Manager.
3. Search for the executable called PerformAnalysis.exe.
4. Select the PerformAnalysis.exe.
5. Click on the End Task button.
6. Start TSK_IQ4 in Aspen InfoPlus.21 Manager.
Keywords: Aspen InfoPlus.21 Database
Aspen Watch Performance Monitor
TSK_IQ
References: None
|
Problem Statement: Sometimes, a user selected STEP-GROWTH type of reaction to model polymer system. After exporting from Aspen Plus and opening the model in Aspen Plus Dynamics, the reaction data cannot be found.
|
Solution: Users cannot access the reaction parameters for STEP-GROWTH type reactions in Aspen Plus Dynamics, because Aspen Plus Dynamics is calculating STEP-GROWTH type reactions through a procedure call to Aspen Plus via the appdf file.
If you want to change the kinetic parameters, you have to go back to Aspen Plus, change the parameters and re-generate the .APPDF file. In Aspen Plus Dynamics, a model is made of a .DYNF file and a .APPDF file. The APPDF file contains all the physical property parameters and the kinetic parameters for the reactions.
Keywords: step-growth
References: None
|
Problem Statement: How do I minimize the token / license consumption, when Aspen DMCplus Controller is started?
By default, a DMCplus CCF as AspenWatch and SmartStep enabled. When the DMCplus application is started, it will check out the appropriate tokens / licenses for all three products.
There may also be a configuration for activating Adaptive Modeling.
If AspenWatch or SmartStep is not being used, these should be modified in the CCF, as well as for Adaptive Modeling.
|
Solution: There are 3 entries for DMCplus optional module license request.
           AWENB : Aspen Watch Performance Monitor
           AMENB : Adaptive Modeling
           SMSTENB: SmarStep
If these entries are 0 (NO), no additional token license is consumed.Â
If these entries are 1 (YES). licenses for the optional modules are consumed. Â
Licenses / tokens are consumed when the DMCplus controller is running. Loading controllers would not consume these resources. When an application is stopped, the tokens / licenses are released.Â
Keywords: AWENB, AMENB, SMSTENB, TOKEN, LOAD, START
References: None
|
Problem Statement: Can Aspen Watch Performance Monitor V7.2 collect Aspen Nonlinear Controller information?
|
Solution: Yes, Aspen Watch V7.2 can collect Aspen Nonlinear Controller information if it is imported into the Advanced Process Controller environment and run as an Advanced Process Controller application.
Keywords: None
References: None
|
Problem Statement: How do I prevent Miscellaneous Tags from showing Data Unavailable status?
|
Solution: 1. Go to Aspen Watch / Tools Menu / Tag Maintenance / Miscellaneous Tab, check the failing tags and theirs IO Device associated (IODEVxx)
2. Go to IP21 Administrator InfoPlus.21 / Node-Computer Name / CIM-IO / IODEVxx / Get transfers / AW_G0000SSSSDU / IO_#TAGS, make sure that the IO_DATA_PROCESSING is ON for the failing tags.
Note: Whata??s AW_G0000SSSSDU? The Aspen PID Watch Performance Monitor Help explains:
AW_G0000SSSSDU
IoGetDef record for collection of Miscellaneous Tag information, where SSSS is the collection interval in seconds, D is the Cim-IO device number, and U is the Cim-IO device unit number.
AW_P0000SSSSDU
IoGetDef record for collection of PID Tag information, where SSSS is the collection interval in seconds, D is the Cim-IO device number, and U is the Cim-IO device unit number. Typically, there will be four IoGetDef records created for collection of the PID loop information.
For example, if the default scan periods were accepted on PID loop Import and Cim-IO Device 3, Unit 1 used for IO communications; the following IoGetDef records would be created:
SLOW AW_P0000360031A A A A A 60 minute data collection
MEDIUM AW_P0000006031A 60 second data collection
CONFIG AW_P0004806431A A scanned only at configuration time
Note that the default Fast scan rate is initially set to the Normal scanning interval at PID record configuration time.
AW_X0000SSSSDU
A separate IoGetDef record is created only for collection of the FAST scanning configuration parameters, where SSSS is the collection interval in seconds, D is the Cim-IO device number, and U is the Cim-IO device unit number.
When the Fast scan interval is modified (changed from the Normal scan interval default) and FAST scan mode is enabled, an AW_X IoGetDef record is created and contains only the PID loop FAST process measurement, setpoint, and controller output parameters.
These same parameters are collected in the AW_P IoGetDef record when in NORMAL scan mode, and disabled during FAST scanning.
When the FAST scan mode is disabled for a specific PID loop, the AW_X IoGetDef entries are removed and then re-enabled in the AW_P IoGetDef record.
In the previous IP21 Administrator screenshot example, the Get Transfers are:
A? Miscellaneous Tags: AW_G01P00030D1U1
A? PID Tags: AW_P01P000006011, AW_P01P000360011, AW_P01P060480011 and AW_X01P000001511
3. Ita??s also recommended just keep the current Miscellaneous Tags in the Aspen Watch Maker. If there are several of them, you can export them through AW / Tools / Tag Maintenance / Miscellaneous Tags and analyze which ones are still collecting in your system.
In the Aspen Watch Help you can find additional information of how to Delete Miscellaneous or PID Tags (there are two ways: Delete Tags Manually or Delete a Group of Tags Using an Input File)
Keywords: Aspen Watch, Miscellaneous Tags, PID, Export
References: None
|
Problem Statement: How to change the format type for custom reports?
By default the reports generated in Aspen Watch are in HTML format and saved in C:\ProgramData\AspenTech\SQLplus\output directory.
However you can use the AW_CUSTOM_DATA SQLplus procedure to generate the reports in HTML, CSV or XML format.
|
Solution: Once you define an Aspen Watch report (via Maker), you can call the AW_CUSTOM_DATA SQLplus procedure (examples below...) and request the data in the format you need (HTML, CSV or XML).
AW_CUSTOM_DATA(REPORTNAME CHAR(24), ENDTIMESTR CHAR(24) = '',
HISTTYPE CHAR(8) = '', DELTA INTEGER = 1, OUTPUTTYPE CHAR(4)='CSV')
where,
REPORTNAME is your Aspen Watch report name.
ENDTIMESTR is the report end time (DD-MON-YYYY HH:MI:SS)
HISTTYPE is the data aggregate type (HOURLY, DAILY, MONTHLY)
DELTA is the number of those aggregates to include (e.g. 1 day vs. 5 days)
OUTPUTTYPE is the format you want the data in (HTML, CSV or XML)
Example:
SET OUTPUT=?C:\TEST2.XML?;
AW_CUSTOM_DATA(`Democol Test?,'05-FEB-2013 10:00:00',' HOURLY ',1,'XML');
SET OUTPUT DEFAULT;
Keywords: Aspen Watch Maker
Custom Report
Aspen SQLplus
References: None
|
Problem Statement: I installed Aspen Plus V7.3.2. While working with Aspen Plus Dynamics, I am facing the following issue while transferring to Dynamics: the dynamic file is created but while opening it can not load the properties file.
It seems it is because of the following reason
1) The dynamic file created from Aspen Plus V7.3.2 is of version 7.3
2) But the properties files created is of version V7.3.2
Hence the conflict: Aspen Plus dynamics of V7.3 is supposed to use properties file of version V7.3.2 which is not compatible. How do you fix this conflict?
|
Solution: There is a utility program installed when A+ V7.3.2 is installed that controls what version of Aspen Properties is used for V7.3 Aspen Plus Dynamics (APD) or any Aspen Custom Modeler (ACM) based product. The utility program is accessed from the Start menu in the Process Modeling V7.3 folder for APD, ACM, etc in the same place as the icon to start the program. The utility is called ?Aspen Properties Version Selector?.
Go to Start | AspenTech | Process Modeling V7.3 | Aspen Plus Dynamics | Aspen Properties Version Selector
You only need to use this once - the setting is saved.
Keywords: None
References: None
|
Problem Statement: Aspen Watch database that contains Smart Step controller cannot be upgraded to ver. 2006.5 without damaging the database snapshot. Not all the records are not migrated. And, the associated history cannot be shown.
|
Solution: Remove SmartStep controller from database using Watch Maker. And, upgrade database snapshot followingSolution 112062 (How to upgrade Watch database snapshot using InfoPlus.21 Database Upgrade Wizard?). And, followSolution 117762 (Procedure to move Aspen Watch data between computers while upgrading to a newer version.) to migrate history data.
Aspen DMCPlus and Aspen SmartStep are integrated into a single software platform with aspenONE 2006.5. And, Aspen Watch database does not contain the definition records for SmartStep controller any more. And, database upgrade aborts when it tries to upgrade SmartStep records.
History for SmartStep is not so important and it should be removed from the database snapshot before the database upgrade.
Aspen Watch Install Database Configuration does database upgrade also. Its database upgrade aborts if the database is upgraded using Typical mode of InfoPlus.21 manager -Upgrade Database function.
NOTE:
There has been one report where the InstallDBConfig.bat failed to start IP.21 after moving the empty SNP to InfoPlus21.snp. The subsequent reload had no live database so the script failed. Adding a pause statement to the bat file and manually starting IP21, and the script continued. The script failed at the end to start IP21 so this needed a similar manual start.
Also, if you notice failures on the configuration of the misc tags during run of InstallDBConfig.bat, you may consider exporting the misc and PID tags before upgrade and importing them later. At that point, all tags seemed OK.
Keywords: InfoPlus21 Manager
Upgrade Dataabse
Install Database Configuration
References: None
|
Problem Statement:
|
Solution: ?The method of instantaneous properties to calculate MWD is not valid when you have significant chain transfer to polymer . This is why we have the distribution tracking feature turned off for the LDPE example. When the calculated PDI values reported on the curves are not in agreement, it usually means there is a side reaction which is not considered by the method of instantaneous properties.
?The method of instantaneous properties assumes that polymer molecules grow and deactivate quickly as the growing center terminates or moves to another molecule of monomer, solvent, or chain transfer agent. The method assumes that the polymer molecules are conserved once they are formed. These assumptions limit the method of instantaneous properties to addition polymerization (ionic polymerization and step-growth condensation reactions are specifically excluded because these reaction schemes are reversible).
Further, the assumption that polymer molecules are conserved once they are formed can be invalid in the presence of certain side reactions, including random (thermal) scission, which destroys polymer molecules, and chain transfer to polymer, which causes inactive polymer molecules to become active again, leading to long-chain branch formation and significantly increasing the weight-average molecular weight and PDI. The molecular weight distribution charts display the MWW and PDI calculated by the method of moments and the method of instantaneous properties. If the predicted values for the PDI are not in reasonable agreement with each other, it is most likely due to these types of side reactions.
Keywords:
References: None
|
Problem Statement: How to incorporate the effects of liquid static head on the outlet pressure of any model with a liquid holdup.
|
Solution: Effects of liquid static head can be applied to liquid hold-up models such as Decanter, Flash2, Flash3, Mixer, PetroFrac, RadFrac and RCSTR. These models allow for not only the effects of static but also the effects of height difference between the outlet of the model and the inlet of the downstream block.
To incorporate these features, please set LiquidHead to “Yes� in Configure form of each block.
Key Words
Dynamic Simulation, Static Head, Outlet Pressure.
Keywords: None
References: None
|
Problem Statement: Collection Status is Old RunTime: Waiting History page shows -9999 for all values.
|
Solution: The Aspen InfoPlus.21 database Time Format has been changed from DD-MMM-YY to DD/MM/YY (the snapshot carries along all the time format options).
Aspen Watch relies on the timestamp being the default format. When the time format is anything other than
DD-MMM-YY, the collection status in Maker will show Old Runtime: waiting.
To change the time format to its default setting, do the following:
1. Open Aspen InfoPlus.21 Administrator.
2. Right-click on your server name and select Properties.
3. Click the Time Parameters tab.
4. Be sure the DD-MMM-YY button is depressed (selected) and then click Apply. There is no need to restart IP.21.
You will not see this problem when the out-of-the-box setting in Aspen InfoPlus.21is used.
Once this fix is verified, we should create aSolution in the Knowledgebase for this. In fact, we need to add this to the list of possible reasons for the Old Runtime: Waiting message.
There are a couple additional items we need to do to make sure all your systems are back to normal and the disk doesn't fill up.
1. On the DMC machines, set DebugLevel = 0 in the \Program Files\AspenTech\Aim-IO\io\dmcp\cimiodmcp.cfg file.
2. On the Aspen Watch machines, make sure TSK_AWNN has no command line parameters defined (remove the debug diag verbose parameters and click the UPDATE button). Do this for all your TSK_AWNN tasks. Once you do this, you may want to stop IP.21, delete all the .OUT and .ERR files in case some are big and restart.
Keywords: watch, pcws, update, thistm, history
References: None
|
Problem Statement: TSK_MSC[n] are added to Aspen Watch 2006.5. But, no documentation explains what they do.
|
Solution: TSK_MSC[n] external task handles the performance and history aggregation calculation for miscellaneous tags.
The Task ID of Tag Maintenance tool Input file is ignored and only TSK_MSC1 is assigned to each miscellaneous tag.
Keywords: TSK_MSC[n]
Task ID
References: None
|
Problem Statement: Event log in Aspen Watch Performance Monitor does not track all operator changes
|
Solution: When Aspen Watch sees the frequent re-occurrence of an event, it creates an event exception rule automatically and stops logging events for that condition. This is a housekeeping measure to prevent excessive logging of the same event over and over. You can check for this by opening IP.21 Administrator and navigating to the AW_ExceptionsDef record called AWEventExceptions. The exceptions are listed in the AW_NUM_EXCEPTIONS repeat area.
To remove the exception, simply clear all the fields for that occurrence (set them all blank for that row with the exception of AW_SOURCE and AW_TYPE which can be set to Any). Removing all of these exceptions is not a big issue, since they will be re-created automatically when the AWEventMaintain query runs the next time (it is the query that does the checking for duplicate events over the most recent 24 hour period). This query runs at 01:00 every morning.
NOTE: You can increase the maximum number of duplicate events allowed per day by editing the QueryDef record called AWEventMaintain. In the QUERY_LINES, edit the line that says:
AW_CleanAWEvents(20);
And change the argument (20) to something larger. For example the following line sets it to create an exception if 65 or more duplicate events occur in a 24 hour period:
AW_CleanAWEvents(65);
Keywords: None
References: None
|
Problem Statement: Install Data Base Configuration tool hangs, does not complete
|
Solution: Rename the current InstallDBConfig.bat in C:\Program Files\AspenTech\Aspen Watch\etc\cfg
Move the InstallDBConfig.bat contained with thisSolution to C:\Program Files\AspenTech\Aspen Watch\etc\cfg
Run new InstallDBConfig.bat.
Keywords: update, IP21, database, IDBC, aspenwatch, upgrade
References: None
|
Problem Statement: Why is there no effect to the change in polymer reaction parameters in Aspen Plus Dynamics?
|
Solution: Free Radical and ZN kinetics in Aspen Plus Dynamics (APD) can be run in 'open' (equation) mode and in 'closed' mode. The closed mode uses the reaction model 'as is' from the APPDF file. If you are using the closed form models, you will not be able to see the effect of changing any kinetic parameters in APD. If you want to see the effect, you need to run in open mode. To set in open mode, go to explorer || Flowsheet|| Dynamic Options and change GlobalPolMethod from procedure to equation.
Keywords: Reaction, Dynamic
References: None
|
Problem Statement: Which Aspen Plus Dynamics models can be used to simulate reverse flow?
|
Solution: These following models can be used to support reverse flow:
Heat Exchangers: Heaters, HeatX and MHeatX
Manipulators: Mult
Mixers/Splitters: FSplit and Mixer
Pressure Changers: Pipe and Valve
Pressure Relief: Bursting Disk, Expansion, Orifice, PSV, TValve, DeltaP
Reactors: RCSTR
Separators: Decanter, Flash2 (Dynamic mode only), Flash3 (Dynamic mode only)
Streams: MaterialStream
Key Words
Reverse Flow, Dynamic model
Keywords: None
References: None
|
Problem Statement: In 2006.5, we made changes on how the counter value is calculated, how to configure a KPI with counter.
|
Solution: Here are steps to configure a KPI with counter:
1. On Custom Calculation Configuration page, select Summation as Calc Type from the pulldown list;
2. Then select a Var Group (MVs, CVs, FFs,etc);
3. On Variable Binding page, select Variable/Tags as Scope;
4. If you want to summarize all the values for a specific type of variables, choose DEP.* or IND.* from the variable list and then select an attribute (such as DEPSTA, etc).
To see an example, you can look at 03PCTMVON by double-clicking it on Custom Calculation Configuration page.
Keywords: KPI, counter, custom, watch
References: None
|
Problem Statement: How to add/remove generation of controllers while exporting from Aspen Plus to Aspen Plus Dynamics?
|
Solution: By defaults, Aspen Plus generates Pressure and Level controllers for unit operations before it is exported to Dynamics. You can uncheck the options for controllers in Dynamics > Controllers form
You can also manually delete the controllers in Aspen Plus Dynamics.
Key Words
Controllers, Level, Pressure
Keywords: None
References: None
|
Problem Statement: How do I create a CAD file from an Aspen Plus Dynamics flowsheet?
|
Solution: Aspen Plus Dynamics supports the creation of .DXF ( Data Exchange Format) file. This data format was developed by Autodesk and used for CAD (computer-aided design) vector image files, such as AutoCAD documents; similar to the .DWX format.
The DXF format is an ASCII (text) based file. It was developed as a universal format so that AutoCAD documents could be opened more easily with other programs. One can generate DXF file from Aspen Plus Dynamics which can be opened and edited with other 3D modeling applications.
To Generate .DXF file in Aspen Plus dynamics, Go to Menu bar|| Flowsheet || Generate .DXF
Keywords: AutoCAD, ASCII
References: None
|
Problem Statement: What is the workflow to link Aspen Plus Dynamics with OPC (OLE (object linking and embedding) for Process Control) server via On-Line Link (OLL)?Â
|
Solution: A representative Aspen Plus Dynamics model need to be developed of the process configuration. OPC server needs to store the variable values from process plant as Tag Variables.
The workflow to establish link between Aspen Plus Dynamics and OPC Server is described in the attached document. An example file is also provided to follow the instructions.
Key Words
Aspen Plus Dynamics, On Line Link, OPC Sever, Tag
Keywords: None
References: None
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.