question
stringlengths 19
6.88k
| answer
stringlengths 38
33.3k
|
|---|---|
Problem Statement: No user - whether or not an administrator - can login to Aspen Collaborative Forecasting (CF).
Getting the following error: | Solution: The user that had this error had Swedish as the language set in the Control Panel.
Officially, CF does not support Swedish language.
The CF create_schema or cf_republish will not work in this case.
TheSolution is then to switch language in the Control Panel | Regional and Language Options to a supported localized language, for example to US English.
CF is also localized in Chinese and Japanese.
Keywords: Collaborative Forecasting
Server Error
Unexpected condition
Fulfilling your request
Please notify the administrator
Language
International
References: None |
Problem Statement: Can I tell if any of the variables in a stream are imported into / exported from a spreadsheet? | Solution: If any of the variables in a stream is an imported variable in a spreadsheet then the Logical Ops table on the Attachments tab ... Unit Ops page of the stream window will show the spreadsheet name and cell reference. (This table also shows the connections to any other logical ops. E.g. Sets, Adjusts ...)
If any of the variables in the stream is exported from a spreadsheet then if you hover over the variable value the yellow tool tip will indicate which spreadsheet and cell reference is setting the value.
Keywords: Spreadsheet, Import, Export, Attachments, Logical Ops
References: None |
Problem Statement: How can I change the number of columns displayed in the Workbook? It is difficult to compare certain stream variables as Hysys wraps the columns depending the size of the workbook window. | Solution: Uncheck the Horizontal Matrix checkbox at the bottom of the workbook window. This will transpose the columns and turn off the column wrapping.
Keywords: Workbook, columns, wrapping
References: None |
Problem Statement: What are the Dynamic Specs? | Solution: These are specs that need to be defined for the pressure solver to work. They are mainly pressure and/or flow specs on boundary streams. Other specs are also needed in most unit operations, but these differ based on the type of operation. For example a compressor needs two dynamic specs (similar to the steady state degrees of freedom), these can be efficiency and pressure rise, or Compressor curves and speed, etc..
Many combinations of Dynamic specs can be used and work, the decision on which to use is case specific and depends on what the model is intended for.
Keywords: Pressure, Flow, Specs
References: None |
Problem Statement: Can I access the Optimiser via Automation? | Solution: The Optimiser does not yet have an object in the HYSYS Object Hierachy so can't be accessed via normal OLE Automation methods. However it can be accessed via a 'Backdoor' variable method.
The attached Excel file contains a VBA macro that will link to the currently open HYSYS case, it allows the Optimiser parameters to be set and the Optimiser to be started and its progress monitored.
The code contained in this file is also attached below.
NB Backdoor methods are only recommended when there is no other alternative, the internal HYSYS monikers may not remain constant between versions so care should be exercised when upgrading.
'Note: HYSYS Type library must be referenced under Tools ...
Keywords: None
References: s
'Require explicit variable declaration
Option Explicit
'API Function Declarations
Private Declare Sub Sleep Lib kernel32 (ByVal dwMilliseconds As Long)
Public Sub AccessOptimiser()
'
'Description: Demonstrates how to access the Optimiser via back door variable methods
'
' NB Backdoor methods are only recommended when there is no other alternative, the internal
' HYSYS monikers may not remain constant between versions
' so care should be exercised when upgrading
'
' Modified from code from MGreaves Incident #411554/H16067
'
'Declare Variables |
Problem Statement: From time to time I find that my Dynamic Specs appear to be lost or changed without notice. What is happening? | Solution: By default the dynamic assistant is set to make any appropriate modifications to the dynamic specs of your model.
Based on a thorough understanding of the behaviour of the user's system, the user may decide that these changes might not be desired, so it is recommended for Advanced user to turn this option OFF. You can do that by going to the Preferences Window (from the Tools menu), Simulation Tab, Assistant Page, then uncheck the top option Set Dynamic Stream Specs in the Background.
Keywords:
References: None |
Problem Statement: After splitting out a business unit in Aspen Demand Manager (DM) and Collaborative Forecasting (CF) and creating two new business units the OVERRIDE_REQUEST_ID table in CF reset itself back to the original starting sequence number causing duplicate number to appear in the DM's OVERRID, OVERINF and OVERRID2 tables. This in turn causes the two systems to become out of synch resulting in incorrect data. | Solution: When splitting out a business unit in Aspen DM and CF to form two or more new business units ensure that the pre-split CF data base (DB) history and DM history is removed in the new business units.
DM override number sequencing starts at 1000 while CF DB number sequencing starts at 1. Once the CF DB sequencing reaches 1000 and you still have DM history from the pre-split you will start to have duplicate override numbers and DM will not know what to do with the duplicate sequence numbers resulting in erroneous data.
Keywords: Collaborative Demand Management
References: None |
Problem Statement: Automation example - Check the solved status of streams and operations within a case | Solution: The status message being shown by streams / operations, along with the severity of the message (Required, Optional, Warning, ...) can be accessed via a Backdoor method. Backdoor methods allow access to features not yet wrapped for access by normal OLE methods.
The attached Excel file includes some example code that illustrates this (in the ReportStatusMessages function). Additionally it includes some extra code that provides more detailed status reporting of unconverged streams, Adjusts and Recycles (in the IsCaseConverged function)
Saved with a HYSYS 3.2 Type Library reference. For troubleshooting advice on common HYSYS / OLE Automation errors see KnowledgebaseSolution #112361.
Note
The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use of these examples. We invite any feedback through the normal support channel at [email protected].
Keywords: Status Level, Status Text, Backdoor
References: None |
Problem Statement: Depending of specific setting on machine, Aspen Process Explorer can show the message Could not create Legend. Is AtLegend.ocx registered? while:
· Trying to add create or load a Trend.
· Trying to use the AtLegend.ocx as part of custom application.
· Trying to use other Process Explorer libraries or references (for example TrendChart.ocx) in custom applications.
This | Solution: provides possible way to resolve this issue which can be also useful for other Process Explorer components showing a similar behaviour. Please refer toSolution 116703 and 121716 to look for the list of component that could have a similar issue.
Solution
1. Try to use the legend control not as a standalone component but as part of a trend control (load a reference to TrendChart.ocx). The legend control can be used as standalone control by setting LegendRatio property of the the trend control to 100.
2. Try manually register AtLegend.ocx using RegSvr32 “C:\Program Files (x86)\Common Files\AspenTech Shared\Apex\AtLegen.ocx” (refer toSolution 121716)
3. Try replacing the AtLegend.ocx file from a machine which is working (usually, if Aspen Process Explorer works properly then the AtLegend.ocx control should work properly too).
4. Try disabling DEP (Data Execution Prevention), using the command bcdedit.exe /set nx AlwaysOff on a cmd window
5. Apply latest patch for current Aspen Process Explorer version
6. Try repairing the installation of Aspen Process Explorer.
7. Try uninstalling Aspen Process Explorer, clean registry and reinstall it.
Keywords: Process Explorer
AtLegend.ocx
References: None |
Problem Statement: Can wildcards be used to specify a sub-batch name in a web service query?
Star (*) only seems to works for characteristics and not for sub-batches:
<CharacteristicSpecifiers>
<CharacteristicSpecifier name = LOT instance = 1>
<SubbatchSpecifier name = RdEDistribution instance=1>
<SubbatchSpecifier name = * instance=0/> | Solution: You need to enable wildcarding.
The implicit assumption of wildcarding was an early implementation, if the user specified the characteristic as *.
We then expanded it to use % and other database syntax, even within the name, like start* or start%.
This required the indication that the user wanted to use wildcards so that the request was not ambiguous.
The attribute useLikeComparison in the AdvancedQuery settings needs to be set to TRUE.
-1 is the value for VARIANT_TRUE and the data type used is VARIANT_BOOL, an automation type.
To find the exact syntax we advise that you do the following:
1. create a basic report which specifies the data query using the GUI controls on the web page
2. after making sure the data comes back as expected, save that basic report as something identifiable, like for example QUERYTEST
3. go to the Batch.21 server and under Aspentech\Batch.21\Data\Reports\... you will find the saved basic report .xml file which contains the properly formed XML for the query you wish to perform
The correct format to use is like the following:
<BatchQuery mostRecentBatches = 10>
<BatchDataSpecifiers>
<CharacteristicSpecifiers>
<CharacteristicSpecifier name = LOT instance = 1 orderNumber = 0>
<AdvancedQuery
isSubbatchRequest = 0
useLikeComparison = -1
returnChildSubbatches = 0
returnChildCharacteristics = 0/>
</CharacteristicSpecifier>
<CharacteristicSpecifier name = PRODUCTION instance = 1 orderNumber = 1>
<AdvancedQuery
..........
Keywords: WILDCARD
WILD CARD
SUBBATCH, SUBBATCHES
SUB BATCH, BATCHES
QUERY, QUERIES
ASTERISK
PERCENT
References: None |
Problem Statement: What does the message Invalid tag in formula mean when plotting stored a shared on-demand calculation. | Solution: This means there is an invalid tag being used in the formula. To solve it, simply correct the tag name in the formula.
Also, please note that for previous versions (V7.2, V7.3, V8.0) the error message was different and as follows:
Error Number -4016
Keywords: Calc data
calc record
References: None |
Problem Statement: Dynamic (& Steady State) Isentropic Flash User Variable | Solution: In the attached HYSYS 3.0.1 case the mixer operation has a User Variable (Steady State and Dynamic) that calculates the stream temperature if it were flashed isentropically to the pressure specified in the Flash Pressure user variable.
To see this in operation in Steady State Mode:
Force the mixer to recalculate (e.g. by ignoring and un-ignoring it or by changing the conditions in the feed stream)
Go to the Design ... User Variables page of the mixer (Ensure the green tick button is pressed)
To see this in operation in Dynamics:
Switch to Dynamics mode
Start the Integrator
Go to the Design ... User Variables page of the mixer (Ensure the green tick button is pressed)
If it doesn't already exist a new user variable called Flash Pressure is created in the mixer - by default this is set to 1 atmosphere. Adjusting this value sets the pressure in the flash.
In steady state the user variable is only calculated when the mixer solves, in dynamics the code runs every time the mixer performs a composition step, by default the Execution Rate settings (Options page on Simulation ... Integrator menu option) mean this is once every 10 time steps. In steady state it is possible to make the user variable recalculate whenever the Flash Pressure value is changed, by opening up the Flash Pressure user variable and checking the Trigger Solve checkbox on the Attributes tab.
The user variable is attached to a mixer since stream user variables do not run in dynamics mode, whereas operation user variables do. Similar code could be attached to any other operation, or if necessary a dummy mixer could be added to a case.
Within the code, the first mixer feed stream is duplicated into a Fluid object which is then flashed to a different pressure isentropically. The temperature of the resultant fluid is then reported. This code is contained in a sub procedure which is called by both the PostExecute() [Steady State] and DynCompositionPreStep() [Dynamic] user variable events.
The example case also includes a user variable on the streams that does the same calculation. This works in steady state only.
Also attached is an huv file that will allow these user variables to be imported into any other case. (SeeSolution #109210 for details on how to import the huv file)
See alsoSolution #109861 which contains a similar user variable to calculate the temperature after a flash to a specified vapour fraction.
Note
The Knowledge Base examples are provided for academic purposes only and as such are not subject to the quality and support procedures of officially released AspenTech products. Users are strongly encouraged to check performance and results carefully and, by downloading, agree to assume all risk related to the use of these examples. We invite any feedback through the normal support channel at [email protected].
Keywords: Dynamic User Variable, Isentropic Flash, PostExecute(), DynCompositionPreStep()
References: None |
Problem Statement: Psychrometric charts are widely used to calculate the properties of air-vapor mixtures. Quite often, we are asked if Hysys calculations match the Psychrometric Charts, especially enthalpy. Hysys and Psychrometric Charts enthalpies cannot be directly compared because they use different basis. This | Solution: shows how Hysys enthalpies can be converted to the basis used in the Psychrometric Charts. An excellent agreement is found when the converted enthalpies are compared.Solution
The enthalpy of formation at 25 degrees Celsius for each pure component is used as the reference state in Hysys on the enthalpy calculations. Usually, the Psychrometric Charts use liquid water at 0 degrees Celsius and dry air at 0 degrees Celsius as the reference state.
Given a stream (1) containing water and air (O2 and N2) in Hysys, its enthalpy can be converted to the chart reference state using the procedure:
Add a dummy stream (1-basis-air) and define the temperature, pressure and air composition at 0 degrees Celsius, 1 atm and 100%, respectively. If you decide to use O2 and N2 instead of air, specify the mole fractions as 0.21 and 0.79, respectively.
Add another dummy stream (1-basis-water) and define the temperature, pressure and water composition at 0 degrees Celsius, 1 atm and 100%, respectively.
Add an energy stream (Q-1).
Add a balance operation. In the connection pages select streams 1-basis-air, 1-basis-water and Q-1 as inlet streams and 1 as outlet stream.
Define the balance operation as Mole and Heat.
Hysys will calculate the flows of streams 1-basis-air and 1-basis-water and also the Heat flow of stream Q-1. This Heat flow represents the total enthalpy difference between stream 1 and the chart reference state - in other words, it is the total enthalpy of stream 1 using the chart reference state. Dividing this Heat flow by the mass of dry air, it is possible to calculate the specific enthalpy of that stream as units of energy per mass of dry air (kJ/kg of dry air, for instance).
See the attached example. Stream 1 is at 1 atm and 80 degrees Celsius. Its moisture content is 60 g/kg Dry Air. Using that procedure, Q-1 Energy flow resulted in 2.404e4 kJ/h. Since there is 100 kg of Dry Air in that stream, the calculated enthalpy is 240.4 kJ/kg Dry Air. Using the Psychrometric Chart (see attached), the obtained value is 241 kJ/ kg Dry Air.
Keywords: Air, Water, Psychrometric Chart, Enthalpy, Basis,
References: , Thermodynamics |
Problem Statement: What is the meaning of the PV Work Term Contribution used by Aspen HYSYS? | Solution: The PV work term contribution is a coefficient that allows the user to tune the energy balance equation to reflect the actual behaviour. An isoenthalpic process should have a value of zero and an isoentropic 100. In simple terms, during a depressurisation, it can be thought as the work the vessel does to expel the material that is leaving the vessel.
Refer to the attached PDF document, for an example of how the PV term is placed within the energy balance in a depressurisation example.
.PDF Files
Printable documentation is published in Adobe Portable Document Format (.pdf). You must use the Adobe Acrobat Reader to view these read-only product-specific documents.
To view a .pdf document in your browser, select a document link. To print a .pdf document, select the print icon in the Adobe toolbar after the document loads in your browser. To download a document to your local drive:
From Internet Explorer, right-click on the document link and select Save Target As.
From Firefox, right-click on the document link and select Save Link As.
Adobe Acrobat Reader is the free viewing companion to Adobe Acrobat and allows you to navigate and print Portable Document Format (PDF) files in a Microsoft Windows, Mac OS or UNIX environment. If you do not have Adobe Acrobat Reader version 4.0 or higher installed on your computer, visit the Adobe web site at http://www.adobe.com and download the latest version of the free reader.
If you have an older version of Acrobat Reader, you must first uninstall it with the Adobe Acrobat uninstaller available from the Start menu.
Keywords: Depressuring, PV Work term., Dynamic Depressuring Utility,
References: None |
Problem Statement: What is the HETP and how is it calculated in the Tray Sizing Utility? | Solution: HETP is the Height Equivalent to a Theoretical Plate. It is defined as the height of the packed column divided by the number of theoretical/ideal stages.
How do I get this number for my packed column using the Tray Sizing Utility?
Rating Mode: When you are trying to rate an existing packed column, calculate the number of theoretical (ideal) stages using the HYSYS column (all tray efficiencies will be equal to 1) and then divide the height of the actual column by the number of theoretical stages. This will give you the real HETP. You do not really need to use the Tray Sizing Utility to do an HETP calculation for an existing column.
Design Mode: When you are designing a column and have calculated the theoretical/ideal number of stages for your column using HYSYS, the HETP is a parameter that should generally be specified by the user. The best number for the HETP is the one provided by the packing manufacturer. HYSYS will calculate an HETP value for the selected packing using empirical correlations (see attached document); however, the user is allowed to override it. You can see the name of the correlation used by HYSYS to calculate the HETP on the Performance tab--> Results page --> Packed radio button of the Tray Sizing Utility view.
Keywords: HETP, packed column, theoretical stages, Tray Sizing Utility
References: None |
Problem Statement: I get Windows Installer Error 1406 when installing the application. What do I do? | Solution: Error 1406 results from a problem with the Windows Installer Service, a Microsoft Windows feature involved with program installation. The best wyay to solve this problem is to download version 2.0 of the Windows Installer Service.
For Windows 95 & 98 machines, go to: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=CEBBACD8-C094-4255-B702-DE3BB768148F
For Windows NT 4 & 2000 machines, go to: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4B6140F9-2D36-4977-8FA1-6F8A0F5DCA8F
Click on the *.exe file you downloaded from the Microsoft website to run it. After the Windows Installer Service installation is complete, try re-installing Ground Loop Design.
Usually this problem occurs during the installation of the Sentinel System Driver. Just click on Ignore when this message comes up and the installation will re-start itself. You may have to click on Ignore a second time if the message comes up again. The installation should then proceed to completion.
For more information about this error, please refer to the following website: http://support.installshield.com/error_central/
Keywords: Error 1406; installation error 1406; installation error; windows install error;
References: None |
Problem Statement: Aspen Collaborative Forecasting (CF) offline loading may take a long time if the file is large and possibly could return with a Weblogic Server Error. | Solution: The default transaction timeout in Weblogic server is 30 seconds. This may be changed to 90 seconds as a recommendation.
1. Login to Weblogic Admin tool:
http://<yourHost>:<yourPort>/console
Login/password as what you saved them to be when you created the domain. (This has nothing to do with CF and is configured when you installed Weblogic.)
2. In the Admin page, on the left navigation panel, click: Services ->JTA, and the transaction timeout is shown as follows:
Change the value in seconds and Apply. This setting is saved permanently.
Keywords: Weblogic 8, 9, 10
Transaction Timeout
Collaborative Forecasting (CF)
Java Transaction API (JTA)
References: None |
Problem Statement: Any roles that are set up manually in Aspen Collaborative Forecasting (CF) get deleted from CF by the next publish/republish from Aspen Demand Manager (DM). | Solution: This is indeed working as designed. In the 2006.1 release, any roles that are set up manually in CF and are not set up in DM get deleted from CF by the next publish/republish from DM.
This is a different behavior from previous versions. Previously roles could be manually set up in CF and they would persist after a publish/republish even if they were not setup in DM.
Therefore, theSolution is to make sure that CF roles are also added in DM. In fact each repub shall synchronize roles configured in DM and those in CF. Any role created in CFAdmin but absent from DM will be wiped out upon repub.
This synchronization was not controlled in previous version (e.g. 2006) as it is now controlled in 2006.1. Any role created in CFAdmin must exist in DM. If you need a new role, first define it in DM, then create it in CFAdmin. It will persist upon repub.
Keywords: REPUBLISH
PUBLISH
ROLES
DISAPPEAR
DELETED
References: None |
Problem Statement: How can I use my favorite Workbook setting for all of my simulation cases? | Solution: Once you have setup the Workbook the way you want for one simulation case file, you don't have to do it again for other cases. All you need to do is to save this setup and use it repeatedly for other cases. Here is the procedure to follow:
Open the case file with your favorite Workbook setting. Let's call it case A.
Make sure the Workbook view is active. If not, press Ctrl-W to Open/View it.
From the top menu bar, select Workbook and then Export.
Provide a name for the .wrk file and save it.
Open the case file where you want to use the same Workbook setting. Let' call it case B.
Again, make sure the Workbook view is active. If not, press Ctrl-W to Open/View it.
From the top menu bar, select Workbook and then Import. It will bring the same Workbook format you have in case A into case B.
Keywords:
References: None |
Problem Statement: When trying to install CFweb for the first time on a new Weblogic server, and when running the publish command, I receive this error: | Solution: This error is caused by an attribute in DM being configured improperly. You must reconfiguring the Collaborative Demand Manager (DM) attribute set to resolve this problem.
Keywords: None
References: None |
Problem Statement: What is the difference between 1-sided and 2-sided gradient calculations? | Solution: For gradient calculations, one-sided refers to the use of forward differencing (involving perturbation on one side of the gradient) and two-sided refers to the use of central differences (involving perturbation to both sides of the operating point to compute the gradient).
For practical purposes, two-sided gradient calculations will require an additional flowsheet pass.
Keywords: optimization, gradient calculations, 1-sided, 2-sided
References: None |
Problem Statement: When trying to log onto Aspen Collaborative Forecasting (CF) website you receive a white screen instead of the CF home page. | Solution: Either the Oracle or Weblogic server is down.
Attempt to access the CF database; if you cannot access it, restart the Oracle DB instance.
Check to see if you can access and log on to http://localhost:7001/cfadmin; if not, stop and re-start the Weblogic server.
From the desktop: My Computer>Manage>Services and Applications>Service>beascv AspenCF_AspenCFServer
Keywords: Blank screen
logon failure
log on
References: None |
Problem Statement: How do I model variable volumes in HYSYS dynamics? | Solution: Although the vessel volumes in HYSYS dynamics are typically fixed values, it is possible to model variable volume systems. The key to modeling a variable volume system is to be able to calculate the vessel volume as a function of an independent variable.
In the attached model an equation in a HYSYS spreadsheet is used to calculate the vessel volume as a function of the vessel pressure. The resulting vessel volume is passed through a transfer function block with a 5 second lag to smooth out any unexpected bumps which may occur.
In addition to calculating the vessel volume based on pressure, the spreadsheet is also used to limit the volume that is passed to the transfer function. This is done to ensure that the calculated volumes remain within a realistic range.
Note the equation used in the spreadsheet for relating vessel volume to pressure in the attached case is for illustration purposes only.
Keywords: dynamics, separator, volume, variable
References: None |
Problem Statement: The customer uses Collaborative Demand Management (CDM) and has a number of DM models for its Business Units (BUs). There is a problem getting one of the DM models to publish to CF.
A message displays saying that ...a unique constraint has been violated.
There does not appear to be any duplicate data in what is being published. | Solution: There are some assumptions in Collaborative Forecasting (CF) that any CDM production needs to follow:
1. All attributes are categorized into base attributes and common attributes.
2. Values (codes) from all base attributes make up base keys.
3. Those keys need to be distinct across all business units (BUs) in CF database. In another words, there can not be shared base keys among different BUs.
Example:
For this republish, there are nine base keys in one of the BUs that are identical to those in another BU that caused the error and failure. To correct this problem, it is possible to assign more attributes to the base type. To make changes in base attribute assignment so that the updates entered in DM are updated in CF, do the following:
Evaluate the current base attributes versus all attributes and decide what other attributes need to be added as base attributes.
After making the adjustment, ensure that the rule (there cannot be any shared base keys among different BUs) will not be violated across the instance in the future. This needs to be done in all the models.
Cleanse both fact data and header tables and republish each model to CF
Keywords: Collaborative Demand Management
Publishing
Attributes
References: None |
Problem Statement: Does the energy balance in the Reactor include the Heat of Reaction? | Solution: Yes. The steady-state Reactor energy balance is defined as
Duty = Hvapour + Hliquid - Hfeed, where
Duty = The heating (+) or cooling (-) by the optional energy stream attached to the Reactor
Hvapour = Heat flow of the vapour product stream
Hliquid = Heat flow of the liquid product stream
Hfeed = Heat flow of the feed stream(s)
Because the enthalpy basis used by HYSYS is equal to the ideal gas enthalpy of formation at 25 C and 1 atm, the Heat of Reaction is amalgamated into any product/reactant enthalpy difference. Therefore the Heat of Reaction is reflected in an elevated product temperature for exothermic reaction, while the enthalpy balance is maintained in the Reactor itself.
Keywords: reactor energy, heat of reaction, energy, reactor, enthalpy, reaction,
References: None |
Problem Statement: Why is the pressure in my vessel different from those in the attached streams? | Solution: This situation is likely to arise when Static head contributions are enabled.
In HYSYS Dynamics the pressure of a stream is taken at the point where it comes from, not where it is going to. The pressure of the vessel contents is the pressure of the vapour product stream. The pressure of the vessel feed stream is taken at the product nozzle of whichever operation is upstream, so if this nozzle is at a different height to the vessel vapour product nozzle, then the pressure will be different. The liquid product stream pressure will be higher than the vapour product / vessel pressure since it includes the hydrostatic pressure gain due to the contents of the vessel.
To see this effect in HYSYS: load the attached case (''DifferenceInPressuresDueToNozzleHeights.HSC'' saved in HYSYS 3.1). Here the vessel feed stream leaves the product nozzle from a valve at ground level. The vessel vapour product nozzle is at 10m and the liquid product nozzle 6m above the ground. Hence the vessel pressure (and also vessel vapour product pressure) is slightly lower than the feed stream pressure due to the hydrostatic pressure loss for the low density two phase mixture. However the liquid product pressure is higher than both because of the hydrostatic pressure gain due to the liquid in the vessel.
In practice the vessel pressure actually lags behind the vapour product stream pressure by one time step and the static head contributions are lagged by several time steps, so during a transient the values will never match exactly.
Keywords: Vessel pressure, stream pressure, static head contributions
References: None |
Problem Statement: Can I bring an open case to the front within HYSYS using OLE Automation? | Solution: In the HYSYS interface if a case is open but not showing, it can be activated (brought to the front) by using the Load Workspace option on the Window menu. It is also possible to activate the case through OLE Automation.
The Excel VBA code below illustrates a function that will activate (i.e. bring to the front within HYSYS) a particular case.
To use the code open up HYSYS with any case, paste the code into the VBA editor in Excel, make a reference to the HYSYS type library (Tools ...
Keywords: None
References: s menu option in the VBA editor), change the case name and path as appropriate and run the procedure.
Public Sub CaseToFrontContainer()
BringCaseToFront C:\Program Files\Hyprotech\HYSYS 3.2\Samples\G-1.hsc
End Sub
Private Function BringCaseToFront(ByVal strCaseName As String) As Boolean
'
'Description: Links to the currently active HYSYS instance and brings the specified case to the front
' Returns True if the case was found and activated, False if not
'
'Declare Variables |
Problem Statement: Can Aspen HYSYS calculate the Methane Number of a stream? | Solution: Aspen HYSYS has no built in feature to calculate the Methane Number of a stream. The user should use a spreadsheet to calculate the methane number from an appropriate equation. If you want to calculate this number for many streams in a simulation, we would recommend programming a user variable for it (seeSolution ID 111460 for some training on how to program a user variable).
You can find an equation to calculate the Methane Number at the following internet address:
http://www.arb.ca.gov/regact/cng-lpg/appd.PDF
However, you might want to do a search of your own to determine what equations would be best to calculate the methane number for your streams.
Keywords:
References: None |
Problem Statement: After applying Aspen Batch.21 2006.5 Cumulative Patch #1 or Aspen Production Record Manager V7.1 Cumulative Patch 5 the Extractor logs errors like this:
Debug : IAtXConnection InitializeParameters: Failed to populate Configuration collection. Error using SQL:
SELECT SourceServerName, SourceDBName, SourceDBType, ConfigName, B21Area, DataSource, Status, StartTime, EndTime, CurrentProcessTime, NextProcessTime, TimeSynchronized, QueryInterval, QueryOffset, RetryCount, ProcessingInterval, Debug, State, BundleSize, DataWait, NullsOrder FROM ExtractorServerConfigAssign
Invalid column name 'DataWait'.|-2147217900->-2147217900 | Solution: 1. Stop the Aspen Extractor Service in Windows Services.
2. Run these two scripts:
upgrade v.1.4.13 to v1.4.14
upgrade v1.4.14 to v1.4.15
These are found in Program Files\AspenTech\Batch.21\Server\Setup\Extractor folder.
Note: The scripts will expect the default DB name AspenExtractor. So if your DB name is different, edit them accordingly.
Keywords: Batch.21
Aspen Production Record Manager
extractor
NullsOrder
References: None |
Problem Statement: This knowledge base article provides an example Aspen SQLplus script which shows how to use the Aspen Batch.21 Application Programming Interface (API) to compute statistic values for a batch. | Solution: In order for the Aspen Batch.21 API to function correctly you must first add a reference to the 'Aspen Batch.21 Application Interface' in the Aspen SQLplus Query Writer. This is done through the View |
Keywords: None
References: s menu. You will also need to change the data source, batch area and tag name in the script to match values in your environment.
local datasource,batchqry, batch, i, j int;
local StatisticSpecifier, StatisticValuesList, StatisticValues, Description, StatisticValue;
local batchdata, requestedstatistic;
datasource = createobject('AspenTech.Batch21.BatchDataSources');
batchqry = datasource('YourDataSource').areas('YourArea').BatchQuery;
batchqry.timerange.start = '23-OCT-2007 09:00';
batchqry.timerange.end = '23-OCT-2007 15:00';
batch = batchqry.get;
write 'Number of Batches: ' || batch.count;
write ' ';
for i = 1 to batch.count do
begin
write 'Batch ID: ' || batch(i).id;
statisticspecifier = batch(i).attributevaluequery.statisticspecifiers.add('YourTagName');
StatisticSpecifier.StartTimeCharacteristic.Name = 'start time';
StatisticSpecifier.EndTimeCharacteristic.Name = 'end time';
batchdata = batch(i).attributevaluequery.getdata;
statisticvalueslist = batchdata.statistics;
statisticvalues = statisticvalueslist(1);
write 'error: ' || statisticvalues.error;
if statisticvalues.error = '' then
i = statisticvalueslist.count;
statisticvalue = statisticvalues(1);
write 'Batch Average: ' ||round(statisticvalue.average,4);
write 'Maximum: ' ||statisticvalue.maximum;
write 'Std Dev: ' ||statisticvalue.standarddeviation;
write 'Minimum: ' ||statisticvalue.minimum;
write 'First: ' ||statisticvalue.first;
write 'Last: ' ||statisticvalue.last;
write ' ';
end;
end;
end; |
Problem Statement: When switching the Sampling Type between Actual and Best Fit for your Ip_AnalogDef or Ip_DiscreteDef tag you notice that there is a trend line drawn for the Best Fit plot that extends beyond the tag's oldest time stamp that you have just set using XOLDESTOK. This is even more obvious if you insert two rows in the legend for the tag but set one to use Actual Sampling Type and the other to use Best Fit Sampling Type. The Actual line stops at the tag's oldest time stamp but the Best Fit line extends beyond it. | Solution: What you are seeing is data that is sourced from the Best Fit (BF) repeat area. The repeat area itself was added to Aspen Standard records in patch 7.3.0.3. This data would have built up if you had enabled the Best Fit archiving for the tag. When you used XOLDESTOK to move the tag's oldest time stamp forward, you applied the time stamp date to the IP_TREND_VALUE (like you have done for years) but you did not do the same for the IP_BF_TREND_VALUE. You can confirm this by running the following statements in SQLplus (change ATCAI tag name for your own tag name):
WRITE 'IP_TREND_VALUE: '||XOLDESTOK('ATCAI 1 IP_TREND_VALUE');
WRITE 'IP_BF_TREND_VALUE: '||XOLDESTOK('ATCAI 1 IP_BF_TREND_VALUE');
You will see a divergence between the two time stamps, in particular you will note that the best fit time stamp comes before the trend time stamp.
To quickly synchronize the two end points, run the following statements in SQLplus (again change tag name first):
LOCAL tagname;
LOCAL ts;
tagname = 'XXXX';
ts = XOLDESTOK(tagname||' 1 IP_TREND_VALUE');
IF ts>XOLDESTOK(tagname||' 1 IP_BF_TREND_VALUE') THEN
--move BF oldest time stamp forward, no need to move it backward
XOLDESTOK(tagname||' 1 IP_BF_TREND_VALUE', ts);
END
Keywords: XOLDESTOK
plot Best Fit trend
wrong
old data points
References: None |
Problem Statement: This Knowledge Base article provides steps to resolve the following Aspen Batch Add-in error Compile error in hidden module: frmGetHandles when trying to launch the Find Batch Handles dialog box. | Solution: For Version 2006.5, a new Batch.21 cumulative Patch has been released (as of July 2009) that should resolve the issue:
126726: Aspen Batch.21 2006.5 Patch #2 (Engineering Release) - July 2009
Since the fix has not been released yet for other Batch.21 versions, the troubleshooting steps below may still be useful:
The above error message appears after the user has applied Microsoft Security Advisory: Update Rollup for ActiveX Kill Bits (please see MicroSoft KB article http://support.microsoft.com/kb/960715 for more details).
To resolve the issue, please download the latest cumulative update rollup for the Visual Basic 6.0 Service Pack 6 Runtime Extended Files available from MicroSoft KB 957924.
http://support.microsoft.com/kb/957924
NOTE (for experienced uses only): If for some reason you are not able to install the above mentioned update rollup for Visual Basic 6.0, you can temporarily disable the Update Rollup for ActiveX Kill Bits by following the steps below:
1. Search your Windows registry for this entry:
{6262d3a0-531b-11cf-91f6-c2863c385e30}
2. Change the value of the Compatibility Flags to 0 (zero).
3. Open MicroSoft Excel and test the Aspen Production Record Manager Add-in - it should work now.
There are two other possible work arounds. If the Microsoft patch is added, the error occurs, and the Version 2006.5 patch cannot be applied immediately:
1. The following files need to be registered again, and the file versions provided should be matched or later.
mscomct2.ocx 6.1.98.16
mscomctl.OCX 6.1.98.16
MSFlxGrd.OCX 6.1.98.14
ComDlg32.OCX
comctl32.ocx
FM20.DLL
2. All files with extension .exd need to be deleted on the OS installed disk.
(If the error still persists, it is necessary to then update to the latest available 2006.5 patch.)
The last work-around, applicable only for a Version 2006.5 system, is to run the V7.1 Add-In (that version of the Add-In will not work with Version 2006 or earlier.) Replace the existing .xla and .xlam files with the V7.1 versions, and reopen Excel. Because V7.1 uses run-time licensing though, it will be necessary to point the clients to a license server running V7.1 licenses. If you do not do that, the Add-In will still work, but there will be license error messages that the users have to dismiss each time they use the tool.
Keywords: Compile error in hidden module: frmGetHandles;
Compile;
Hidden;
Handle;
Add-in;
addin;
Excel add-in;
Process Explorer
References: None |
Problem Statement: When working with the Aspen Process Explorer Excel Add-Ins, you may see the following error when building a formula:
#ERROR: 1004
Unable to set the FormulaArray property of the Range class | Solution: This is not a problem with AspenTech software. This is a known issue with Microsoft Excel.
Please review the following knowledge article on Microsoft's Support website:
http://support.microsoft.com/default.aspx?scid=kb;en-us;213181
The error is produced when the formula being generated is longer than 255 characters.
Keywords: ATGetTrend
array
References: None |
Problem Statement: A BCU trigger fails when processing a characteristic (type Alias value) taking its value from a tag whose binary values (0/1) are formatted (using ip_value_format) by a two-value selector record.
The following type of error is displayed in the BCU log:
trigger TriggerName : Encountered errors while sending the XML data to Batch.21 : B21SVR-50132: Invalid value for characteristic
Source of error: <Subbatch xmlns=Aspentech.Batch21 name=batchname instance=auto><Characteristic name=CharacteristcName instance=next><Value>VALUE0</Value><Timestamp isUTC=1>2008-07-01T07:15:21</Timestamp></Characteristic></Subbatch>
Is this kind of tag supported for the processing of characteristics? Or does the user have to change the IP_VALUE_FORMAT?
Notes:
Example of select record:
Value Description
0 VALUE0
1 VALUE1
? The data type of the characteristic (CharacteristcName in the example) is Numeric, while the value of the tags is string (discrete values.)
? If you change the possible values of your tags to 0 and 1 instead of enumeration values, it works. | Solution: In fact you get error Invalid value for characteristic when the data type of the value cannot be converted to the data type of the characteristic. The value is of type Text, so the characteristic should also be of type Text.
TheSolution to avoid the error is to uncheck the Retrieve values as text string flag in the BCU. That way you can send either numeric or string data back to the batch.
Keywords: ALIAS, ALIASES
TEXT
STRINGS
NUMERIC
CHARACTERISTICS
References: None |
Problem Statement: How do I display or plot a rolling average for a tag? | Solution: To display or plot a rolling average, use an ad-hoc calculation with the AspenCalc function MovingAverage in place of a tag name. MovingAverage has two arguments: Tagname and AverageInterval expressed in hh:mm:ss format.
For example, entering
=MovingAverage({ATCAI},00:15:00)
into the legend of an Aspen Process Explorer, Aspen IP.21 Process Browser, or aspenONE Process Explorer plot plots the 15 minute rolling average for the tag ATCAI.
To display a rolling average in a graphic, enter the calculation directly into a Tag Name field for an object.
Keywords: Moving average
Rolling average
Ad-hoc
Ad-hoc calculation
References: None |
Problem Statement: Visual Basic code that works in version 2.5.1 does not work in version 5.0.1. Is there an example available that shows how to insert data in the database in version 5.0? | Solution: The reason why the visual basic code created in version 2.5.1 does not work in version 5.0.1 is because the at_tag control was retired after version 2.5.1. It was replaced with a more flexible architecture that enables Process Data to talk to many different types of data sources and not just InfoPlus.21.
The example below provides a starting point for users trying to get their version 2.5.1 Visual Basic code to work in a version 5.0.1 (or higher) environment.
Dim updateSucceeded As String
Dim UpdateErrorCode As String
Dim sServerName As String
Dim g_pd As New AtProcessData.DataSources
Dim myDS As AtProcessData.DataSource
Dim myTag As AtProcessData.Tag
Dim myAttr As AtProcessData.Attribute
Dim absTime As New AtTime.AbsoluteTime
Dim g_updateTime As New AtTime.AbsoluteTime
Dim g_updateTimeUTC As Date
g_updateTime.Precision = 3
g_updateTime.Parse Now()
g_updateTimeUTC = g_updateTime.ValueUTC
sServerName = tzvetcoffc2
On Error GoTo ReportError
Set myDS = g_pd.Item(sServerName)
Set myTag = myDS.Tags.Add(sTagName)
myTag.WriteAttribute VAL, g_updateTimeUTC, True, sCodeSelect, 0, 0
updateSucceeded = CStr(myDS.ErrorCode)
UpdateErrorCode = myDS.ErrorString
MsgBox updateSucceeded
MsgBox UpdateErrorCode
ReportError:
MsgBox Err.Description
myDS.Tags.RemoveAll
Keywords: visual basic
References: None |
Problem Statement: How do I specify a Workspace on my network as the default Workspace for all users who install Aspen Process Explorer? | Solution: The default Workspace for any user is specified in the Windows Registry entry HKEY_CURRENT_USER | Software | AspenTech | Aspen Process Explorer | Settings under the key DefaultWorkSpace. Once the key is filled out, the entire hive can be exported onto various users' machines so they begin with a specific default workspace.
Keywords: Specify default workspace
References: None |
Problem Statement: Why do I receive the error The method GetBatch failed for object |AtBatchDataSources? | Solution: This is known usability issue, the Batch handle field is not intended as the target for Drag and Drop from the Batch Query Tool.
The text is composed with headers and data and delimited with tabs, so if you Drag and Drop from the Batch Query Tool into an Excel spreadsheet you will then see columns of data shown because Excel can handle the tab delimiter, however the textbox cannot.
Format example:
BATCH NO<tab>START TIME<tab>END TIME<tab>BATCH HANDLE<tab>8585<tab>8/3/2012 8:00:00<tab>8/3/2012 9:00:00<tab>datasource.6532
The target for the Batch Query Tool is the spreadsheet not the batch handle field.
Keywords: BQT
BATCH QUERY TOOL
EXCEL
ADDIN
AtBatchDataSources
References: None |
Problem Statement: Certain characteristics do not display results in the Query Tool. For example a new characteristic called Product is made:
And an instance of the characteristic is added to a batch:
However when including this characteristic in a query, the value is not shown:
Why do certain characteristics not display in the Query Tool? | Solution: Certain words are reserved for internal use by the APRM Genealogy product, and so cannot be used generally by APRM developers, even if you are not specifically using Genealogy features. The reserved words are as follows:
Depth
Equipment
Location
Product
Quantity
Status
Transfer Type
Keywords: empty
null
blank
References: Type
Unit Of Measure
Movement Start
Movement End
Product Type
Product SubType
Description
Reference Batch ID
Keep in mind that on a localized system, those same terms, in the localized language will also have the same behavior. |
Problem Statement: After activating Compliance on new Batch area batch data is not accessible using Batch Detail Display or Query Tool. | Solution: When compliance mode is activated in Aspen Production Record Manager Aspen Security permissions must be set down to the Batch Definition level.
1. In the Aspen Production Record manager Administrator Expand the area that compliance was activated for.
2. Under the area right click on Batch Definition and select properties.
3. Select the security tab and add the appropriate role permissions.
For details on setting security in Aspen Production Record Manager refer to knowledge base article 123384: How to Configure Batch.21 Security
Keywords: local security
afw
Batch
Compliance
References: None |
Problem Statement: After applying ER DT120103 to the system, hotlinks in graphics may stop working properly. When a hotlink is clicked, it may report an error:
Aspen Process Graphics Editor
Cannot find this file.
Please verify that the correct path and file name are given.
Whether you press OK or not, PE will open another instance of itself and actually load the apx file.
No matter what path is specified (a hard coded path, or a relative path, this error persists and the file is opened in another window. | Solution: This error occurs because the information in one or more of the Use DDE settings in the windows file type associations has become corrupted.
Process Explorer attempts to fix such errors automatically at startup by registering all its file types. But in some cases for unknown reasons it may become necessary to fix this problem manually. To do so (Windows 2000):
Double-click My Computer.
On the Tools menu, click Folder Options.
Click the File Types tab.
Click on the File Types column header to sort by file type.
Locate all the Aspen Process Explorer extensions.
The current file extensions are: APX, ATGCS, ATGRAPHIC, ATPLOT, MVA, ATVBA, APWS, ATWORKSPACE.
Select one of the extensions, and examine it as follows:
Click the Advanced button. There should be one action, the open action. Select it.
Click the Edit... button.
Verify the Application used to perform action: text box contains the correct path to ProcessExplorer.
This should be in the short filename format. For example, C:\PROGRA~1\ASPENT~1\APEx\Pe\PROCES~2.EXE %1
If the Use DDE checkbox is unchecked, check it by clicking it.
Verify the DDE Message: text box contains the following: [open(%1)]
The Application: and Topic: text fields will be filled automatically upon closing this dialog.
Select OK, OK, and Close to close out the dialogs and save changes.
Repeat step 6 for all extensions as necessary.
Keywords: hot link
hotlink
References: None |
Problem Statement: When creating a Batch Calculation, the default variable to return the result of the calcuation is ReturnValue. If not explicitly added to the calculation syntax, the error shown in the | Solution: To configure a Batch Calculation correctly, explicitly begin the statement with the variable ReturnValue, and then bind it appropriately:
Keywords: section below is written to the Batch log file, and the calculation fails. The Properties of a simple calculation where ReturnValue has not been used correctly may look something like this:
References: None |
Problem Statement: Application error when launching Batch.21 Web Service:
QueryInterface for interface AspenTech.Globalization.IAtLocalization failed. | Solution: Users must have 'Read & Execute', 'List Folder Contents', and 'Read' NTFS permissions to the following directories:
\Program Files\Common Files\AspenTech Shared\Apex (this one has AtLocalization.dll in it)
\Program Files\Common Files\AspenTech Shared
\Program Files\Common Files
\Program Files
Keywords: Application error
Batch.21 Web service
References: None |
Problem Statement: Running an open-ended query for all batches through the Aspen Production Record Manager (APRM) Query Tool or using the APRM Application Programming Interface (API) to retrieve all batches in this manner
BatchList batchList = bq.Get();
returns the following error:
Server reported error : B21BSC-50079: No query parameters specified. Verify data source/area information and resubmit query. | Solution: The APRM Cumulative Patch (CP) #8 for Version 2004.2 introduced a new feature by which an open-ended query for all batches in the system is no longer allowed. This logic was altered to stop clients from unintentionally executing a query that would return all batches, and therefore take a very long time to complete.
It is still possible to query all batches in the system if you supply a very high batch number for an ending dummy batch. For example, use the value 2147483647 for the highest dummy batch number. This is the maximum value of a long int, which is the datatype of the batch ID.
Keywords: Full
Batch.21
References: None |
Problem Statement: How do you resolve the error message Invalid occurrence number when plotting a custom tag in Aspen Process Explorer? | Solution: When plotting a non-custom definition record, the error message that displays when IP_ARCHIVING is turned off is Invalid value in field IP_ARCHIVING.
However, with custom definition records, the error message that is displayed is Invalid occurrence number. To correct this problem, turn archiving on for the record and verify the error message goes away.
Keywords: IP_ARCHIVING
custom definition records
plot
References: None |
Problem Statement: This Knowledge Base article shows how to show the detail display for a specific batch handle from Visual Basic. | Solution: Below is a sample VB code that shows how to activate the detail display from Visual Basic. The batch handle in this example is Batch21 v7.1.1405.
There are three steps:
1. Create the object
2. Set the batch handle: SetBatch
3. Show the detail display: Show
NOTE: NOTHING is a check to make sure we created the batch detail display object.
Public batchDetailDisplay As Object
Private Sub Command1_Click()
If (batchDetailDisplay Is Nothing) Then
Set batchDetailDisplay = CreateObject(BatchDetailDisplay.Application)
End If
If (batchDetailDisplay Is Nothing) Then
Exit Sub
End If
batchDetailDisplay.SetBatch Batch21 v7.1.1405
batchDetailDisplay.Show
End Sub
Keywords: None
References: None |
Problem Statement: What does a locked batch signify in Aspen Production Record Manager? Is there still some way to edit the batch? | Solution: Once a given batch is locked, no changes can be made by anyone. Characteristics cannot be added, deleted or modified no matter what permissions the user has in the system. The only action that can be taken is that someone with the Lock privilege can unlock the batch. Of course in a compliant system (i.e. one where Aspen Audit & Compliance tracks all auditable activity) both locking and unlocking the batch create audit trail entries.
Keywords: read-only
permanent
permission
References: None |
Problem Statement: Why am I getting the Error B21BCN-54037 when opening a Journal file?
This means the specified event journal file is partially completed and is no longer in the journal_directory, or is
inaccessible. | Solution: To resolve this issue determine why the <filename> file is missing and
restore it. A missing file may be due to:
• Manual deletion of the file.
• The file may reside on a remote server that is currently
inaccessible.
• Access to a file is no longer available due to a change in directory permissions.
Keywords: Batch.21
APRM
Aspen Production Record Manager
OpenBatch
EVT
Mem
B21BCN-54037
References: None |
Problem Statement: A Trend plot added to an Aspen Production Record Manager web-based advanced report does not display the trend line when the report is generated. Also the Batch21Services log will include the following message “Failed to add tag data request to data manager: E_IINVALIDARG”.
If the Aspen InfoPlus.21 Task Service and the Aspen Production Record Manager Services are started with different accounts the method call to read tag data from IP21 may fail because the user information is not passed from the Web to Aspen Production Record Manager to Aspen InfoPlus.21. | Solution: Add the following entry into the registry [below] to force the direct connect method to read tag data from Aspen InfoPlus.21.
· Export the registry as a backup.
· Go to [HKEY_CLASSES_ROOT\CLSID\{710B32A1-7277-11D1-932C-00805F0F1C84}
· Add a key “ProcessList” if it does not already exist
· Add a String Value under the key ProcessList called “ProcessName# [where # is “1” if it’s the first Process name or the next consecutive number if 1 or more already exists]
· Populate the value of “ProcessName#” with Batch21Services.exe
NOTE:
Be very careful when modifying the registry. There may already be values in the process list.
The algorithm is to put ProcessName# where # starts at 1 and increases by one. The code looks for ProcessName1, then ProcessName2, etc.
EXAMPLE, adding ProcessName2
Keywords:
References: None |
Problem Statement: Can I test my APRM connection and run test SQL queries? | Solution: Starting from v8.8, Aspentech has implemented a new ODBC test utility that can be found in 32 bit and 64 bit format:
C:\Program Files\AspenTech\Batch.21\Client\APRM_ODBC_TestApp.exe -- 64 bit client
C:\Program Files (x86)\AspenTech\Batch.21\Client\APRM_ODBC_TestApp.exe -- 32 bit client
Once you select the desired connection method (ADSA, ODBC DSN or Connection String) click on Open Connection to start testing.
Here's a screen capture of the results:
Keywords: APRM_ODBC_TestApp.exe
Test APRM Connection
References: None |
Problem Statement: Why does the BCU service go to 100% after restarting machine? After restarting the BCU server the 'Aspen Production Record Manager BCU service' goes to 100% in the Windows Task Manager. This can cause performance issues with the APRM and BCU servers and clients. | Solution: This issue is caused when there are units in the BCU server administrator that are disabled. These units may have pointed to another data source that either does not exist or is not reachable. This causes connection errors and the BCU will try and re connect. The re connection time varies on scheduled time in the Unit. This will create multiple reconnection errors in the BCU server log located in c:\ProgramData\AspenTech\DiagnosticLogs\ProductionRecordManager\
To resolve this issue you will need to remove the reference to the old server in the BCU unit/trigger or completely remove the unit/trigger. If you delete units then ensure that you restart the APRM and BCU services to refresh the cache.
Keywords: BCU
CPU
100%
References: None |
Problem Statement: After upgrading a pre-v8.4 Aspen Production Record Manager (APRM) system you cannot find any of the Server Tools because the menu option would appear to have not been installed. | Solution: In v8.4 the management of the APRM services is handled within the Aspen Production Record Manager (Batch) Administrator. You will find them under the Local Services node in the console tree.
The APRM Administrator Help file has a new section Using the Local Services Node introducing the function of this new node.
It has been noted that there may be some references in the documentation to the location of the now obsolete external APRM Server Tools. These references will be corrected in due course.
Keywords: Missing
Not found
Not installed
BcuServerManager.exe
AtXServiceOptions.exe
References: None |
Problem Statement: No AM/PM parameter is shown in the timeline when the time setting is in 12 hour format. There should always be either an AM or PM suffix. | Solution: This problem is not specific to Process Explorer, but is instead a system setting. This setting is under Control Panel -> Regional and Language Options -> Customize... (button on the Regional Options tab) -> Time tab. Normally, most people use one of the four options in the pull down menu for Time format. But this field may also be edited, and deleting the tt for AM/PM will removed this suffix. Therefore, be sure to select either the standard h:mm:ss tt or hh:mm:ss tt (for a leading zero) format.
Keywords: am
pm
timezone
ante meridiem
post meridiem
References: None |
Problem Statement: This knowledge base article provides an example Aspen SQLplus query which uses the Aspen Production Record Manager Application Programming Interface (API) to do the following:
Where ever a value of 1250 exists for a BATCH COST instance, use this instance number(s) to return the value of BATCH VALUE. The query then sums up all of the BATCH VALUEs that are returned. | Solution: Important:
1. Items shown in bold should be changed to match your environment.
2. This query was written using the Aspen Production Record Manager demo. However, additional instances (2 and 3) of BATCH COST and BATCH VALUE were manually created using the Detail Display.
3. Since this query uses the Aspen Production Record Manager API, you need to add a reference to the Aspen Production Record Manager (Batch.21) Application Interface through the View |
Keywords: None
References: s menu in the Aspen SQLplus Query Writer in order for this query to execute.
Query:
local data_sources, batch, myarea, myquery, batchlist, i, k int;
local StartTime timestamp, EndTime timestamp;
-- you will likely need to change the data type of required_val to char
local required_val, sum_val real;
required_val = 1250;
sum_val = 0;
data_sources = createobject('AspenTech.Batch21.BatchDataSources');
write 'DATA SOURCE NO: ' || data_sources('YourDataSource').Areas.Count;
myarea = data_sources('YourDataSource').areas('YourArea');
MyQuery = MyArea.BatchQuery;
-- Clear the query.
MyQuery.Clear;
-- start by specifying that we only want to query batch number 400
Myquery.CharacteristicConditions.Add('BATCH NO', 1, atEqual, '400');
batchlist = MyQuery.get;
for I=1 to batchlist.count do
begin
write 'BATCH NO: ' || batchlist(i).characteristics.item('BATCH NO');
write 'START TIME: ' || batchlist(i).characteristics.item('Start Time');
write 'Batch Cost: ' || batchlist(i).characteristics.item('BATCH COST');
write 'Batch Cost: ' || batchlist(i).characteristics.item('BATCH COST',2);
write 'Batch Cost: ' || batchlist(i).characteristics.item('BATCH COST',3);
-- find the highest instance of the batch cost characteristic by specifying -2 as the instance number
write 'Number of instances of Batch Cost: ' || batchlist(i).characteristics.item('BATCH COST',-2).instance;
-- loop through the instances
for k = 1 to batchlist(i).characteristics.item('BATCH COST',-2).instance do
-- check if the instance value equals the required value. if the values are equal write the instance number to the screen
if batchlist(i).characteristics.item('BATCH COST',k) = required_val then
write 'Instance of BATCH COST with required characteristic value: ' || batchlist(i).characteristics.item('BATCH COST',k).instance;
-- now return the list of BATCH VALUEs for the instances that meet the required criteria
write 'Value of BATCH VALUE for this instance:' || batchlist(i).characteristics.item('BATCH VALUE',k);
sum_val = sum_val + batchlist(i).characteristics.item('BATCH VALUE',k);
end
end -- end the for loop
write 'The sum of all of the values with the required characteristic value is: ' || sum_val;
exception
write 'No BATCH NO';
end
end
batchlist = null;
batch = null;
Query Output:
DATA SOURCE NO: 1
BATCH NO: 400
START TIME: 10/1/2007 5:55:44 AM
Batch Cost: 1250
Batch Cost: 1250
Batch Cost: 3000
Number of instances of Batch Cost: 3
Instance of BATCH COST with required characteristic value: 1
Value of BATCH VALUE for this instance:1900
Instance of BATCH COST with required characteristic value: 2
Value of BATCH VALUE for this instance:1900
The sum of all of the values with the required characteristic value is: 3800 |
Problem Statement: When a calculation is executed and an input parameter is a tag, then the current value of the tag is used. However, if you want the data to be obtained at a specific time, you can associate the time with another characteristic or the time of trigger and use an Aspen Calc formula to get the tag data. Using the UTC formulas is preferred since the timestamps from APRM are in UTC. | Solution: Example: Obtaining tag data based on time of characteristic.
ReturnValue = UtcTagHistory( InputTag1, InputTime1, 1)
InputTag1 = Tag in IP21
InputTime1 = Bind to characteristic. Use the [Trigger] instance to get the characteristic that matches the instance of the characteristic trigger. (Start Time[Trigger])
An alternative is to use the time of the trigger characteristic.
InputTime1 = myTrigger.TimeStamp
ReturnValue = UtcTagHistory( InputTag1, InputTime1, 1)
InputTag1 = Tag in IP21
InputTime1 = Get the timestamp value from the myTrigger parameter
myTrigger = Bind to trigger characteristic. Use the [Trigger] instance to get the characteristic that matches the instance of the characteristic trigger. (My Trigger[Trigger], where “My Trigger” is the trigger characteristic)
Keywords: Getting tag data at the time of the trigger
References: None |
Problem Statement: This Knowledge Base article provides a description of a new feature in the Aspen Process Explorer Excel Process Data Add-In on the Properties/Format tabs of all functions, called Values As String. | Solution: This new feature is enabled by default. When this feature is selected, the Add-In will return all values formatted by a selector record to the worksheet as strings. Clear this checkbox to return raw values.
Note: Clear this checkbox to view data using localized (non-US English) formats.
Keywords: None
References: None |
Problem Statement: Process Graphics Editor can open xml files. When users try to import xml files from other applications, the file will not open. | Solution: In order for Process Graphics Editor to be able to open xml files, the files must conform to the PEGraphic.dtd structure.
You will need to make the XML files conform to the PEGraphic.dtd specification. Only then you can convert the XML files to .atgraphic so Process Graphics Editor and Process Explorer can use them.
Keywords: Process Graphic Editor
xml file
import
References: None |
Problem Statement: When referencing a cell holding a timestamp as part of the Characteristic condition, the following error appears: | Solution: This error has been reported on Aspen Production Record Manager (formerly Batch.21) Version 2006.5. However it is not reproducible on a fully patched 2006.5 system. It is also not reproducible on later versions.
Keywords: #ERROR: -2147352571: B21BAI-60258: Invalid data type for characteristic: Start_Time
References: None |
Problem Statement: This Knowledge Base article provides steps to resolve the following error message:
Command executed but returned error 1
which may be encountered when a BCU trigger runs an SQLplus query via iq.exe at the Command line. | Solution: FIRST - one should check if the script would execute without errors if iq.exe process is invoked directly from the Command line.
If that doesn't work then the problem is most likely related to the query itself, such as a typo in the reference to the script name or the path to the query location.
Another reason for this error message may be due to a known MS SQL problem documented inSolution # 121581 ( Connection is busy with results for another hstmt ).
If one also receives the above error message when running the script in the SQLplus Query Writer, then the way to overcome it is to uncheck the box next to Wait for command to complete before continuing for the particular command(s) that's failing. This is done in the BCU Administrator as seen on the screen capture below.
Keywords: Connection is busy with results for another hstmt
References: None |
Problem Statement: The Value field for one or more tags displays the error: Invalid History Request | Solution: Ensure that the tag is associated with an existing Map record that is correctly configured.
1. From the Process Explorer legend, determine the Map record for the problem tag.
2. Verify that the Map record exists in the InfoPlus.21 database.
3. If it exists, check the value of the MAP_DefinitionRecord field. Verify that its value is the name of the definition record for the problem tag. For example, If tag ATCAI is defined by IP_AnalogDef, verify that the MAP_DefinitionRecord field in map record IP_AnalogMap has a value of IP_AnalogDef
4. If any changes are made to the Map record, Process Explorer must be closed and reopened.
Note that a simple reboot of the client machine was also known to have corrected this error in one instance.
Keywords:
References: None |
Problem Statement: By default the Aspen Batch.21 Lightweight Adapter (LWA) uses the reliable method to publish data to the Aspen Enterprise Connect Infobus. This knowledge base article provides an example adapter configuration file which allows items published from Aspen Batch.21 to use the certified transport feature. | Solution: Please download the attached AdapterConfig.xml file. The AdapterInstance value needs to be changed to the correct AdapterInstance used in your environment.
Keywords: bus
PublishItem
References: None |
Problem Statement: When trying to write to Setcim with a Process Graphic, you get this error:
You are not authorized to enter data on:
Server: < server name > | Solution: There is a required registry entry on each client machine that will enable writes to Setcim. Go to: <drive>:\Program Files\AspenTech\ProcessData\etc and double click on CsdsHistoryDA.reg. You should now be able to write to Setcim with a graphic.
Keywords: write
authorized
csdshistoryda.reg
References: None |
Problem Statement: Can Aspen Process Graphics Editor play sound (wav)? | Solution: The Process Graphics editor is not able to use sounds directly. The only way to work around this is to load use Vb (Visual basic) In Process Explorer which could monitor a tag or record.
Keywords: Graphics Editor
Sound
Wav
Process Explorer
VB
References: None |
Problem Statement: When starting Aspen Process Explorer (APEx), the following error comes up in a dialog box: | Solution: This error is caused by a conflict with the ZoneAlarm (Personal Firewall, Integrity) product from Zone Labs. Since this is a third-party product, AspenTech does not provide information about it. However, disabling or changing the settings for this product will remove the error.
To change the settings, inside of ZoneAlarm, change the application portserve.exe to ALLOW ALLOW ASK ASK.
Keywords: Cannot register service
ERROR
WinRPC
RPC
Unable to receive
Winsock
sub-error
Connection reset by the remote side
References: None |
Problem Statement: The following trigger behavior is desired:
Transition trigger with the option to use a specific previous value of a tag (defined in the trigger.)
E.g. A trigger with a transition condition of a tag X=1. Only fire the trigger if the previous value of x was 2. If the previous value was another value, trigger will not fire.
Having access to the previous value could help determine for example whether a batch is ended because of an error condition or the batch is ended under normal conditions. That is just one example. There could be many use cases.
CQ00440579 has been logged to investigate the possibility of adding this functionality directly into the BCU. However what work-arounds exist to get similar functionality now? | Solution: Here are two possible work-arounds:
Use the TimeShift function from Aspen Calc.
1. Make sure your tag of interest writes its value to InfoPlus.21 on a regular basis (for example, every minute.)
2. Lets assume the tag holding your value is Tagx. Create an On Demand Calculation using IP_CalcDef named TagxPreviousValue like =TimeShift(Tagx,-01:05) (In case you are not familiar with IP_Calcdef records, they let you create named and stored Ad-Hoc calculations you can then use elsewhere, like in Process Explorer or in your BCU configuration.) Your parameter of -1:05 should always be able to then pick up the previous value, if you write it every minute (if your trigger should only fire very infrequently, you could make this a longer period, obviously, all that matters is your Timeshift parameter is large enough that you know you will be looking at the last recorded value.)
3. Now build your trigger according to the logic Tagx = 1 AND TagxPreviousValue = 2
That trigger will ONLY fire if the current value is 1 and it was previously 2. (You could also make your IP_Calcdef formula =Timeshift(Tagx,-01:05)=2 and then in your BCU it would evaluate as TRUE or FALSE, so BCU logic Tagx = 1 AND TagxPreviousValue.
Use SQLplus
Write an SQLplus script which looks up the previous value of a tag (script would be triggered to run whenever Tagx equals 1.)
BothSolutions are dependent on certain factors -- to use the suggested Aspen Calc scenario requires the data be regularly written. It would be important in this case to make sure the unit where theSolution is used does not have any tags set to Extrapolate, so that in a Store and Forward scenario (i.e. InfoPlus.21 is offline) the unit would not be able to progress. For the SQLplus scenario, you have to rely on the immediate responsiveness of the script (i.e. you don't want to risk that Tagx has yet another update between the time the trigger fires and the value is read back so action can be taken. Perhaps putting the Querydef record on its own external task would help make performance more predictable.
Keywords: None
References: None |
Problem Statement: Getting the error Batch21 webservice resultstatus: An area with the specified 'name' attribute was not found when using XML with APRM webservice. | Solution: The user configured in IIS does not have the correct permission on a Windows 2008 Server.
In IIS under 'Default Website' check the permissions under Batch21ws by clicking Batch21ws and 'Edit Permission'. Change the IIS_USR, or if using another account name grant 'Full Control' then press 'Apply' then 'OK'.
This should allow access for the user using the Webservice to use XML files.
Keywords: APRM
webservice
XML
References: None |
Problem Statement: The Tag Browser works, but after dragging and dropping a tag on Aspen Process Explorer, the following error comes up in a dialog box:
An action cannot be completed because a component (Aspen Process Explorer - [Document1]) is not responding. Choose Switch To to activate the component and correct the problem
<Switch To...> <Retry> <Cancel> | Solution: At the Command Prompt run NSLOOKUP and check that it works on both the client (usually works on the client because the Tag Browser works) and the server (this is the most likely direction that does not work). If there is not a two-way communication between client and server, work with your local network team to resolve the problem. Once NSLOOKUP works in both directions (from the client to the server and from the server to the client), the problem will be solved.
Keywords: nslookup
installation
configuration
References: None |
Problem Statement: Sometimes after installation of Process Explorer, when trying to add the Process Data Add-In into Microsoft Excel the following error occurs:
Class Not Registered
Looking for object with CLSID:{AC9F2F90-E877-11CE-9F68-00AA00574A4F} | Solution: PossibleSolutions are to reinstall Process Explorer, or to try re-adding the add-in. However the problem may be resolved by re-registering the following DLL:
regsvr32 C:\WINNT\system32\fm20.dll
After executing the above command successfully (where WINNT may be 'Windows' depending on your Windows installation path) try closing Excel, reopening it, and adding add-in again.
Keywords: addin
add-ins
register
References: None |
Problem Statement: When using the Aspen Process Explorer - Tag Browser and saving a search as a favorite, where is the associated favorites file saved? | Solution: The Tag Browser favorites are stored in the following file.
..\Program Files\Common Files\AspenTech Shared\Apex\UserName\Favorite.fav
Keywords: favorite
tag browser
References: None |
Problem Statement: This knowledge base article describes the typical causes of the following error message:
B21BSC-60181: Failed to create Batch server component(s) for data source XXXX. Verify that the Batch.21 server is properly installed on XXXX.
where XXXX is the name of the Aspen Batch.21 server. | Solution: This error usually has the following causes:
1) The Data Source is not configured properly in Aspen Data Source Architecture (ADSA).
a) If you are using user data sources on each client machine, ensure that the data source configuration on the problematic machines matches the data source configuration on the working machine. In particular, ensure that the correct Aspen Batch.21 server name (XXXX in the example above) is specified.
b) Ensure that there are no network connectivity issues between the client machines and the Aspen Batch.21 server.
c) Ensure that the nodename of the server as specified in the ADSA configuration resolves to the correct IP address on your network. This can be accomplished through the DOS commands Ping and Nslookup.
2) The BCU Data Source is not started (in the BCU Server Manager). Since not having the BCU Data Source started would affect all users, if some client machines do not receive this error then this is likely not the cause.
Keywords: Configuration
Connectivity
References: None |
Problem Statement: This knowledge base article describes troubleshooting steps to take to resolve the following error:
bcustart: starting BCU as data source XXXX
bcustart: BCU Start() failed (80004005: B21BCU-55013: Unable to create the process data sources collection.) | Solution: 1. Re-register AtProcessData.dll through the following commands using Regsvr32.exe
Regsvr32 /u AtProcessData.dll
Regsvr32 AtProcessData.dll
2. If re-registering AtProcessData.dll does not resolve the problem then
- Run the repair option for Aspen Process Data, ADSA, Aspen Process Explorer and Aspen Batch.21 from the aspenONE installation media
- Reapply the cumulative patches for the products mentioned above
- Uninstall then re-install Aspen Batch.21 (making sure to not install Aspen Batch.21 through a terminal services session)
If the suggestions listed above do not resolve the problem then the following tests will provide a better idea of where the problem lies.
- In the BCU Server Manager ensure that the BCU data source is listed correctly and the account used to start the BCU service is a domain account with local administrative privileges on the Aspen Batch.21 server.
- In the ADSA Client Config tool press the Test button. Are any errors returned?
- Check the Aspen Batch.21 component listed in the ADSA configuration. Ensure that all parameters are correct for the OLE DB connection to the BCU data source. When you go through the OLE DB configuration press the test button to ensure that the connection to the database is successful.
- The BCU Server Manager has a Logging tab which allows the user to enable additional logging options. Enable all of the flags then attempt to start the BCU again. The log files generated from this action should contain additional information about the error. If you have trouble interpreting the log files contact the AspenTech support group for further assistance.
Keywords: None
References: None |
Problem Statement: This Knowledge Base article provides a code sample showing how to create a BCU trigger in VB.NET . The code can be found in the Aspen Production Record Manager Interface Help files. | Solution: Dim servers As New AtBatch21BcuApplicationInterface.BcuDataSources
Dim units As AtBatch21BcuApplicationInterface.InstalledUnits
Dim newunit As New AtBatch21BcuApplicationInterface.Unit
Dim newtrigger As New AtBatch21BcuApplicationInterface.Trigger
Dim newconditionterm As
AtBatch21BcuApplicationInterface.ConditionTerm
Dim newcondition As AtBatch21BcuApplicationInterface.Condition
Dim newaction As AtBatch21BcuApplicationInterface.Actions
Dim newcharacteristic As
AtBatch21BcuApplicationInterface.Characteristic
Dim errorlog As New Object
newtrigger = newunit.Triggers.Add(newtrigger)
newtrigger.ConditionProcessing.Type =
AtBatch21BcuApplicationInterface.AtBcuTriggerTypeEnum.atTriggerTypeTransition
newconditionterm =
newtrigger.ConditionProcessing.Conditions.Item(1)
newcondition = newconditionterm.Item(1)
newcondition.Operand1.Source =
AtBatch21BcuApplicationInterface.AtBcuValueSourceEnum.atValueSourceTagValue
newcondition.Operand1.Tag.Name = BCW_4411
newcondition.Operand1.Tag.Map = IP_DiscreteMap
newcondition.Operand1.Tag.ExtrapolateToCurrentTime = True
newcondition.Operand2.Source =
AtBatch21BcuApplicationInterface.AtBcuValueSourceEnum.atValueSourceConstant
newcondition.Operand2.Constant = 1
newcondition.Operator =
AtBatch21BcuApplicationInterface.AtBcuConditionOperatorEnum.atOperatorEq
newtrigger.Actions.Characteristics.Add(Status)
newcharacteristic = newtrigger.Actions.Characteristics.Item(1)
newcharacteristic.DisplayName = Status
newcharacteristic.Value.Source =
AtBatch21BcuApplicationInterface.AtBcuCharacteristicValueSourceEnum.atCharacteristicValueSourceConstant
newcharacteristic.Name = Status
newcharacteristic.Value.Constant = 1
units = servers.Item(IWAB).Areas.Item(Ineos).InstalledUnits
newunit.DisplayName = 45V14
newunit.Designator1.CharacteristicName = Jaar
newunit.Designator2.CharacteristicName = Week
newunit.Designator3.CharacteristicName = Batchnummer
newunit.Designator4.CharacteristicName = Unit
newunit.Designator1.Value.Tag.Name = DESJ_V14
newunit.Designator2.Value.Tag.Name = DESW_V14
newunit.Designator3.Value.Tag.Name = DESBN_V14
newunit.Designator4.Value.Tag.Name = DESBN_V14
units.Install(newunit, errorlog)
Keywords: Trigger
VB
BCU
References: None |
Problem Statement: After a new install of Aspen Process Explorer, the user is prompted to register the application. Will Aspen Process Explorer function properly if the user does not register the application? | Solution: While we do recommend that all users properly register their AspenTech software, the software will continue to function without problems. By not properly registering the software, you may however be prompted to acknowledge and cancel the registration prompt each time you login to open and use the Process Explorer application.
Keywords: new software
register
References: None |
Problem Statement: V7.1 adds a new Bulk Load feature for Aspen Production Record Manager. However this feature is also available in Version 2006.5 running Cumulative Patch 1 or later. Is there a step-by-step example explaining how to use this feature to add characteristics? | Solution: 1. Do an Export operation in the Production Record Manager Administrator tool to create an XML file containing all the information of the Batch area you want to work with. This will be the starting point for the Specification Template spreadsheet.
2. Make a copy of the Batch21SpecificationTemplate.xlt Excel document, saving it to a working directory. The original is under C:\Program Files\Aspentech\Batch.21\Client. Open the spreadsheet, and under the Aspen menu, invoke the Import XML command and browse to and choose the file you just created (if you don't already have an Aspen menu choice, then use the Tools, Add-Ins menu choices to add AtBatch.xla.)
A successfully imported file:
Note that on the various tabs along the bottom of the spreadsheet your Batch area information is present.
3. In the case of Aspen's Batch Demo area, there are 39 characteristics at various batch levels. In this example, we add 10 more example top level characteristics, starting with Line 40:
4. Adding the new characteristics to the Batch area is a two-step process. First, use the menu choices Aspen, Batch, Configuration, Production Record Manager, Generate Hierarchy to create a new XML file with the new Characteristics. Examining that file shows the new characteristics in XML format:
5. Now, from within the target Batch Administrator Area, import the new XML file:
then expand the area to view the results:
Keywords: Bulk Load
Bulkload
Characteristics
References: None |
Problem Statement: Data Fields in Process Graphics Editor will not show multiple rows of data that may be generated by a QueryDef, only the first row can be displayed and this typically would be the column header. | Solution: First, modify the QueryDef so that the column headers are not displayed. You can do this by using the COLUMN_HEADER option:
Example:
Use SQLplus to create a QueryDef record called MyQuery with the following SQL Statement
SET MAX_ROWS 3;
SET COLUMN_HEADERS FALSE;
SELECT NAME FROM IP_ANALOGDEF WHERE NAME LIKE 'AT%' ORDER BY 1;
For this example, it is necessary to go into IP.21 Administrator and change the #OUTPUT_LINES field on the MyQuery record to 3 before continuing.
Then, in Process Graphics Editor, you will have to create a Data Field control for each expected output row, and place them one under the other to make them appear as one contiguous block. For each Data Field control you must set the occurrence number according to the row from the query OUTPUT_LINES you wish to display.
Example:
Use Process Graphics Editor to create a Data Field control with the following Data Source properties:
· Tag Name: MyQuery 1 OUTPUT_LINE
· Attribute: VAL
· Map: QUERYDEF
The number 1 in the Tag Name above indicates the occurrence number. Copy and paste this Data Field control twice, position them below the first and change the Tag Name in each case to reference the appropriate occurrence number.
By positioning the data fields closer together you can make it appear that you are displaying one block of output data. ThisSolution can also be applied to IP.21 Browser Graphic Studio, the results of which can be viewed in Internet Explorer.
Keywords: Multiple rows
Multiple Occurrences
Data Field
QueryDef
OUTPUT_LINE
References: None |
Problem Statement: Users who have created custom formulas on the Calc server are unable to make use of it as an ad-hoc calculation in APE on the client PC. The error Invalid Tag may appear. However, using built-in formulas in the ad-hoc calculation is successful (eg. =abs(tag1)). | Solution: In order to use formulas with ad-hoc calculations, Aspen Calc must first be installed on the client system. When you install Calc on the client the built-in formulas are also installed. But in order to use custom formulas created on the server, you have to copy the library that contains the custom formulas onto the client PC. These formulas would then be available on the client PC.
Keywords: custom formula
ad-hoc
References: None |
Problem Statement: The Aspen Excel Process Data COM addin was installed, but longer appears in the Microsoft Excel ribbon. | Solution: If the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\14.0*\User Settings\AspenExcelAddin** exists, then this indicates that the user has opened Excel on the machine before.
When Process Explorer is first installed, all Excel addin registry entries are created under HKEY_LOCAL_MACHINE. When a user opens Excel for the first time, the registry entries under HKEY_LOCAL_MACHINE are copied over to HKEY_CURRENT_USER. The Count string shown in the screen capture means that the registry keys for the addins have already been copied from HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER.
To initiate the registry key copy from HKEY_LOCAL_MACHINE to HKEY_CURRENT_USER, delete any of the following folders:
AspenAPRMConfigExcelAddin
AspenAPRMExcelAddin
AspenExcelAddinPD
AspenExcelAddinIP21Config
The next time the user opens Excel, it will perform the registry copy again, and the folder that was previously deleted will be recreated.
*NOTE:
For machines with Excel 2010, use registry key 14.0
For machines with Excel 2007, use registry key 12.0
**NOTE:
For APRM Configuration addin, use registry key AspenAPRMConfigExcelAddin
For APRM Process Data addin, use registry key AspenAPRMExcelAddin
For Aspen Process Data addin, use registry key AspenExcelAddinPD
For Aspen Configuration InfoPlus.21 addin, use registry key AspenExcelAddinIP21Config
Keywords: Excel addin
COM addin
Process Data
APRM addin
regedit
References: None |
Problem Statement: After upgrading, the Aspen Production Record Manager Add-In no longer works. Opening Microsoft Excel causes an error:
compile error in hidden module b21menus
When the Aspen Production Record Manager Add-In is added into Microsoft Excel, the following error is seen:
cannot find project or library
When the OK button is clicked, a dialog then asks for a password for accessing the Aspen Production Record Manager Add-In. | Solution: Under these circumstances, there will likely be several instances of AtBatch.xla or AtBatch.xlam file on the system in various locations.
The most recent version of these file may exist in the directory: <drive>:\Program Files\AspenTech\Batch.21\Client.
This won't match the version located in: <drive>:\Program Files\Microsoft Office\OfficeXX\Library.
To get things working, copy the latest version of the AtBatch.xla and AtBatch.xlam files and place them into the <drive>:\Program Files\Microsoft Office\OfficeXX\Library folder.
Next, open Microsoft Excel and in the Add-Ins dialog window, unselect the option for Aspen Batch.21 Add-In and then close Microsoft Excel. Next, reopen Microsoft Excel. From there go to the Add-Ins dialog window, click the Browse... button and navigate to the AtBatch.xla or AtBatch.xlam file residing in the <drive>:\Program Files\Microsoft Office\OfficeXX\Library folder.
The Aspen Production Record Manager Add-In should now be ready for use.
Keywords: b21menus
compile error
hidden module
References: None |
Problem Statement: How do I change the Aspen Process Explorer menu ribbon to the Windows Classic view? | Solution: Aspen Process Explorer provides the ability to use the classic main menu bar or the Ribbon. The Ribbon is available in Process Explorer V7.3 and later. You can switch between the two as desired.
In Aspen Process Explorer click on the Process Explorer Options icon
and click on the Classic Menus button to change to the Windows Classic
This will change to the classic main menu.
You can change back to use the Ribbon Main menu bar by going to the Tools -> Options menu and click on the 'Switch to Ribbon Control Bar' button.
Keywords: ribbon, menu, classic
References: None |
Problem Statement: There are a number of known issues with the V7.3 Excel Process Data Addin which require changes be made post install. Each error message is documented in this | Solution: with appropriate fix.
Solution
There are two main issues which arise with the v7.3 Excel Process Data Addin, these are:
1. Connection to IP.21 shared memory
2. Authentication issues
Please refer to the individual knowledge base articles attached to thisSolution and apply the appropriate fix.
Keywords: Excel Addin
Process Data
Failed: A Call to SSPI Failed
Invalid Datasource
Error: Server Unavailable ( NotResponding ) Error ( Error Number -1002 )
FAILED: The server has rejected the client credentials
#NAME?
References: None |
Problem Statement: During the installation, I get a Windows Installer error: Internal Error 2753. How do I get rid of this error and proceed with the installation? | Solution: Try turning off Norton AntiVirus.
Check in your C:\>temp directory for a setup.exe file. If one exists, delete it.
When selecting to Install HYSYS (or any product), make sure you select at least some subcomponents to install, if not all the subcomponents.
Keywords: Installer Error, 2753, Internal Error
References: None |
Problem Statement: Heat Transfer Fluids (Thermal Fluids, Hot Oils, Diathermic Oils) for Process Heating and Cooling are present among Hysys database components. Nevertheless, due to its commercial names, are difficult to look for and to finally find them as a consequence of many of them being a mixture rather than a single component. | Solution: Make use of the Formula filter when browsing the components database. Due to their mixture nature, Hysys database shows <Unknown> as formula for the heat transfer fluids. Selecting the Formula radio button and just beginning to type <U in the Match window will make Hysys to show the database components of unknown formula.
Keywords: Heat Transfer Fluids, Refrigerants, Thermal Fluids, Hot Oils, Diathermic Oils
References: None |
Problem Statement: Collaborative Forecasting server is returning an unexpected condition when trying to log in. The following error is being seen by all users:
Server Error
The Collaborative Forecasting server encountered an unexpected condition which prevented it from fulfilling your request.
Please notify the administrator.
NOTE: If the password has expired, then publishing to CF from the Demand Manager will also be failing. | Solution: The database password (Oracle/CF) has expired and needed to be reset. To resolve this, first the database administrator will need to reset the Oracle password. Once this is complete, the file cf\cf_integ\rc\jdbc.ini will also need to be updated with the changed password.
Keywords: database
pass word
expiration
down
References: None |
Problem Statement: Is Aspen Collaborative Forecasting supported in a virtual environment? | Solution: The following table illustrates Aspen Collaborative Forecasting (listed as Aspen Chemical Supply Chain) and the supported virtualization technologies.
Virtualization Technology
Aspen Chemical Supply Chain
VMware ESX Server
Yes
Microsoft Hyper-V
Yes
Citrix Presentation Server
Yes
Microsoft Terminal Server
Yes
Microsoft Application Virtualization
No
Keywords: None
References: None |
Problem Statement: For a liquid stream of liquid and aqueous phases present at standard conditions, HYSYS calculates the Actual Volume Flow of the overall stream when the stream temperature and pressure is set to the standard conditions. The value does not match the Liq Vol Flow @ Std Cond of the overall stream. Why? | Solution: All calculations for volumetric stream flows are based on density. For a liquid stream, the actual volume flow is calculated based on the actual liquid density while the Liq Vol Flow @ Std Cond is based on the Liq Mass Density @ Std Cond.
HYSYS uses the internal methods of the chosen property package to calculate the actual liquid density at the stream temperature and pressure. Most of the property packages use the COSTALD model for liquid density calculations. However, some of the equation-of-state packages (i.e., Peng Robinson, SRK, Sour PR and Sour SRK) allow you to choose either COSTALD or the equation of state. For standard liquid density, the traditional HYSYS thermo always uses COSTALD, regardless of the property package you have chosen. However, if you use COMThermo in HYSYS 3.0.1 or above, you have choices of liquid density models. The selected model will be used for both actual and standard liquid density calculations.
Obviously, if different models are used for the actual and standard liquid densities, the actual and standard densities and volume flows will not match for individual phases and the overall stream.
However, even when the same model is used for the actual and standard liquid densities, the actual and standard liquid densities and volume flows of the overall stream still differ while these properties of each phase are equal.
This is because the actual and standard liquid densities of the overall stream are calculated in a different way. The actual and standard liquid densities of each phase are calculated by the density model with the composition of each phase. Since the stream temperature and pressure are set to the standard conditions, the actual liquid density of each phase is calculated to be equal to the standard liquid density. The actual liquid density of the overall stream is calculated as a weighted average of the individual phases. However, the standard liquid density of the overall stream is calculated by the density model using the bulk composition of the stream. Therefore, it differs from the actual liquid density of the overall stream. In consequence, the actual volume flow of the overall stream does not match the standard liquid volume flow.
Contrary to the actual volume flow, the standard liquid volume flow of the overall stream is just a theoretical value for a multiple phase stream. It does not change with stream conditions, so long as the stream's overall composition does not change. It does not equal to the sum of the standard liquid volume flows of individual phases. You should use the actual volume flow at standard conditions as the measure of a multiple phase stream.
Keywords: volume flow, liquid density, Actual Volume Flow, Liq Vol Flow @ Std Cond
References: None |
Problem Statement: When attempting to modify the ProcessExplorer.rc files, the error message:
'Cannot change standard MFC resources!'
may be returned if any change is made to the project. Note: The ProcessExplorer.rc files will compile successfully if no change is made to them. | Solution: --------
The following lines must be temporarily removed or commented out of the ProcessExplorer.rc and Pgraph.rc resource files:
#include ..\..\..\Extern\microsoft\Vc\mfc\include\l.esp\afxres.rc // Standard components
#include ..\..\..\Extern\microsoft\Vc\mfc\include\l.esp\afxprint.rc // printing/print preview resources
#include ..\..\..\Extern\microsoft\Vc\mfc\include\l.esp\afxolecl.rc // OLE container resources
#include ..\..\..\Extern\microsoft\Vc\mfc\include\l.esp\afxolesv.rc // OLE server resources
#undef __AFXPRINT_RC__
#undef __AFXRES_RC__
#undef __AFXOLECL_RC__
#undef __AFXOLESV_RC__
Note that the relative path for the include directives will change with each language setting. These include files provide support for standard MFC resources, such as File and Print dialogs. When translating to non-provided languages (such as Russian) these resources must also be translated (they are already translated for Spanish, German, etc.) These files are included in the localization kit to provide a template for your custom translation. These include directives can be removed for resource editing and then replaced manually.
Keywords:
References: None |
Problem Statement: When using the Aspen Process Explorer tool the Aspen Excel Add-Ins are installed to all accounts, however, you have to enable this for each user account in the system. | Solution: Enable/disable a certain Add-In in Excel is a user setting. Different users can enable and disable the Add-In based on their individual needs. An enabled Add-In is loaded when the Excel is started and this takes time to load. When the user has too many Add-Ins enabled, he will experience a length delay on starting Excel.
Therefore, the user needs to enable/disable Add-In based on need.
Keywords: Add-in Excel enable
References: None |
Problem Statement: How do I display a trend plot without a legend or scrollbar inside a VBForm? | Solution: In order to remove a plot's legend and scrollbar, right click on the plot inside the VBForm to display the properties form:
Then change the field LegendRation to 0.
This causes to plot to appear within the VBForm with neither a legend nor scrollbar.
Keywords: Legend
VBForm
KPI plots
References: None |
Problem Statement: Using Aspen SQLplus iq.exe command line program to run a simple command from Aspen BCU Administrator will need to create a sql file. If there is a stored procedure in IP.21, is there any way to run it without creating a sql file? | Solution: Use Aspen SQLplus sqlplusx command line program. This program allows the running of SQL query on a computer without IP.21 installed.
For example, a Stored Procedure call list_trend_values which accept 2 parameter, a record and a timestamp is created in the IP.21 database. The following is added to the BCU command.
C:\Progra~1\Aspentech\InfoPlus.21\db21\code\sqlplusx.exe /h=testmachine list_trend_values('ATCAI', CURRENT_TIMESTAMP - 500)
Keywords: BCU Administrator
BCU Script
BCU command
Stored Procedure
ProcedureDef
sqlplusx
References: None |
Problem Statement: Why is the IBP/FBP (obtained from TBP/D86/D1160(atm)) not matching with the bubble/dew point of my oil? | Solution: The IBP that you see in the Oil Environment under the Blend View --> Property Plot (or in the BP Curves utility) will be different than the bubble point at atmospheric pressure (in the simulation).
This is a common misconception. Let us say you have distillation data from 3 different lab analysis techniques; TBP, D86, and D1160(atm). For the same sample, all three will have a different 0% point (IBP). None would match the bubble point of the stream/oil/sample at atmospheric pressure. Likewise for the 100% point (FBP), none would match the DewPoint of the stream at atmospheric pressure.
This is because of the difference in experimental techniques. TBP is about the equivalent of passing the sample through 15 to 100 theoretical stages at a reflux ratio of 5 or greater. D86 and D1160 tests are reasonably rapid batch laboratory distillations involving the equivalent of approximately one equilibrium stage and no reflux except for that caused by heat losses (Perry's Chemical Engineering Handbook, page 13-86 - 13-88). None are the equivalent of a single stage atmospheric flash. Note the IBP rises as we move from TBP to D86 to Single Stage Separation. This is expected because the separation is becoming more and more smeared as the apparatus goes from super fractionation to single stage separation i.e. with TBP we are pulling off almost a pure component at the IBP, whereas with a flash it is a whole mixture of components. The D86 and D1160(atm) techniques lie somewhere in between.
Keywords: IBP, FBP, TBP, D86, D 1160 (atm), bubble point, dew point, distillation
References: None |
Problem Statement: BCU Administrator fails to load, error is:
Failed to retrieve batch area. B21BAI-60174: Specified area is not defined | Solution: There are several possible causes of this error:
1. Verify that all the characteristics specified for the Designator structure exist. If a designator-related characteristic has somehow been deleted, this error will occur.
2. Verify that no security has been applied to the areas table. Run a query like:
select * from areas
and check the contents of the acl fields. If they are anything other than NULL, and security has NOT been applied as part of the desired configuration, then update these fields to NULL. (Check the Area properties in the Product Record Manager tool to verify whether or not security is applied.)
3. If this error persists on a system where Security has been defined, try removing and re-adding security.
If the error persists, please contact Aspentech Support for further troubleshooting advice.
Keywords: None
References: None |
Problem Statement: For writing equations to the pressure flow solver in dynamic mode extensions, people feel they can not use pressure and flow balance equations because Hysys does not give you a chance to update the equation coefficients and constants. So they always use general equations as a workaround. However, general equations should only be used when your equations are non linear, otherwise they could slow the simulation down slightly. More information on how to properly write the P-F equations in a Dynamic Extension is given here. | Solution: For flow and pressure balance equations, you can initially set the coefficients and constant values in the extension when the equations are constructed. After that it will not periodically ask you to change them but you can change the coefficients and constants when you want to. For example, you may choose to do so in the PreProcessStates method.
The Hysys dynamic extension interface exports method for this, specifically:
UpdatePressureBalanceEquationCoef (eqn number, variable number / constant for last, coef or constant) UpdateFlowBalanceEquationCoef
You need to call these methods via the HYSYS DynUnitOpContainer (not implement them).
If you had an equation P = const then you would use something like this:
mobjDynContainer.UpdatePressureBalanceEquationCoef 0, 0, 1.0 mobjDynContainer.UpdatePressureBalanceEquationCoef 0, 0, 101.0
The general equations can of course also be used but are more expensive as HYSYS calls you to update the derivatives each and every iteration of every step. Hence if the coefficients and constants do not change all the time, you are better off using the pressure or flow balance equations as described above.
Keywords: Pressure Flow Solver
Dynamics
Dynamic Extension Unit Operation
Programmability/Extensibility
References: None |
Problem Statement: How can I use HYSYS OLE to efficiently create case studies? | Solution: The use of OLE functionality can greatly increase the speed with which case studies can be created within HYSYS. By utilizing nested FOR loops, multiple states can be easily and efficiently defined, thereby reducing the effort required to develop related process models.
In the attached Excel spreadsheet, VB code is used to modify the stream names in a given case. The algorithm searches the collection of material streams in the active case to find a match for each name in the associated stream table. If a match is made, then the stream is assigned a corresponding tag number as dictated by the second column in the table. If no match is made, no re-naming occurs and the search continues with the next name in the table. A routine to do the reverse (change the active simulation case from tag numbers back to stream names) has also been added.
Note that if there are more stream names in the table than there are in the simulation case, you will have to change the range of the FOR loops (as this is currently set to the number of material streams in the active case). For demonstration purposes, the stream table has been designed for use with the G-2.hsc sample case that is shipped with HYSYS, however this can easily be modified to suit your specific needs.
Keywords: streams, OLE, VB, automation, Excel
References: None |
Problem Statement: Does the pipe segment automatically account for the pressure drop between segments of different diameters? | Solution: Currently: No
You must manually add a swage or a fitting with an appropriate k value to account for these losses.
Keywords: Pipe Segment, Reducer, Expander, Swage, Segments of different diameter
References: None |
Problem Statement: During process troubleshooting there is often a need to view multiple trend plot files for the same time period. Usually what happens is that the timeframe of interest is identified when viewing a single plot. Then, subsequent plots of potential interest are opened. However, the time frames of all opened plot files are set to the most recently opened plot, which is dependent on what was last saved on those plots. The result is that each time a new file is opened, the timeframes of all the opened plot files must be reset to the timeframe of interest.
Is there a way around this problem? | Solution: This issue was addressed in version 2004 of Aspen Process Explorer.
Open up Proces Explorer
Go to: Tools | Options | General
On the General tab, you have two options:
If you want APEx to display the time of the saved plot, select the flag titled: Always apply document times when opened.
If you want APEx to display the time of the legend, do not select that flag.
Keywords: trend plot
time span
References: None |
Problem Statement: How do I display values from an Aspen InfoPlus.21 record's repeat area in Aspen Process Graphics Editor? This example will demonstrate how to display value from OUTPUT_LINE of an OCCURRENCE for tags from QueryDef record in the Aspen Process Graphic Editor using Data Field object. | Solution: 1. Open Aspen Process Graphic Editor by going to Start => All Programs => AspenTech => Aspen Manufacturing Suite => Process Explorer => Process Graphics Editor.
2. Click on the Data Field button (the object with number 5 and a yellow pencil) and draw it on the grid.
3. Right click on the Data Field object or double click on the Data Field to get to the Data Field Properties dialog box.
4. Select the Data Source tab
5. For the Tag Name, enter something like atcai_value 3 output_line where
atcai_value is a Aspen InfoPlus.21 QueryDef record,
3 is the occurrence number,
and output_line is the repeat area's field name.
Note: After you fill in the Tag Name field and move to the next field like Attribute, it then automatically fills in the Attribute field with VAL and Map field with QueryDef.
6. Select a valid data source for this tag to retrieve data from.
7. Save the graphic and exit Aspen Process Graphics Editor.
8. Open the saved .atgraphic file in Aspen Process Explorer to view the 3rd occurrence of the repeat area field
'OUTPUT_LINE'.
Keywords: OUTPUT_LINE
graphic
References: None |
Problem Statement: The list of security roles is empty in Aspen Batch.21 Administrator. The same problem exists for all areas defined.
Right click on an area
Select the Security tab
When clicking on the Add... key, the Select Aspen Role window shows an empty list of roles
Note: Roles have been correctly entered and the Batch.21 application has been added in the AFW Security Manager. | Solution: This can happen if you change the security server URL in the AFW Tools (Client Registry Entries tab / URL line) but forget to restart the Batch.21 and the security services. Don't forget to restart the services to fix this problem.
Keywords: Security
Roles
Empty
References: None |
Problem Statement: On some machines Microsoft Excel can take several minutes to start with the Aspen Process Data Add-ins installed, showing in the splash screen:
· Loading Add-Ins (1 of x) Aspen Production Record Manager...,
· Loading Add-Ins (2 of x) Aspen Production Record Manager Configuration...,
· Loading Add-Ins (3 of x) Aspen InfoPlus.21 Configuration..., etc
Up to a minute's delay for each add-in during which time the system doesn't show any significant CPU activity. | Solution: The reason why some machines appear slower than others can be explained by a machine configurable security option that controls whether a check for publisher's certificate revocation is made. With this option activated Excel will wait until it eventually times out on machines with no internet access.
Deactivate this option on your machine and see if it has an impact on the start up time of Microsoft Excel:
· Open Internet Options,
· Select Advanced tab,
· Look for Security section within the Settings list,
· Uncheck the “Check for publisher’s certificate revocation”
You should also be aware that such certificate revocation checks have a time-out period which is controlled by Windows security policy. Please refer to technical forum groups regarding this subject for the latest information for your particular version of Windows.
Keywords: Microsoft Office
ribbon-based COM add-in
extremely slow
very slow
waiting
loading
startup
group security policy
certificate path validation setting
References: None |
Problem Statement: What do the Source column icons in the Production Record Manager Detail Display tool mean? | Solution: In V7.1 and earlier, the Source column in the Detail Display tool was only shown by default if the Batch Area had 21 CFR 11 Compliance turned on. In V7.2 and later all Aspen Production Record Manager (APRM) systems display the Source column in the Detail Display. There are eight possible sources for an APRM characteristic. In the Detail Display only the icon is shown in the Source column, so thisSolution gives further information about those sources:
Icon
Notes on Characteristic Origin
Aspen Batch Extractor
Characteristic origin is optional Aspen Batch Extractor Component, part of the APRM product since Version 2006.
Aspen Production Execution Manager
Characteristic origin is XML submitted from Aspen Production Execution Manager containing source=ebrs key in XML header.
Aspen Production Record Manager
Characteristic origin is from within APRM - an example would be a Calculated Characteristic where the output from a formula creates a new characteristic instance
Aspen Production Record Manager BCU feed app
Characteristic origin is from the Unit scripts written in the APRM BCU component
Aspen global services app
Characteristic origin is from a custom application written against the APRM API where atSourceServices has been set.
Customer Custom Application
Characteristic origin is from a custom application written against the APRM API where atSourceCustomApplication has been set.
Manual
Characteristic origin is (1) manual input, for example, adding a characteristic using the Detail Display tool, or (2) a custom program which has not set the atSource to Services or CustomApplication.
Open Batch Connect
Characteristic origin is the Aspen Open Batch Connect component.
For custom programs written to submit data via the APRM API, there are two valid sources that may be specified, atSourceServices or atSourceCustomApplication. If not specified, characteristics created via the custom program will show as Manual in the Detail Display. There is no qualitative difference between designating a program source as atSourceServices or atSourceCustomApplication. It is meant as a way to easily distinguish characteristics created via in-house programming from characteristics created via applications written by Aspen's Global Services team.
This list of sources is fixed (additional source choices and icons cannot be added or deleted from the system.)
Keywords: Batch.21
BDD
Source attribute
References: None |
Problem Statement: After 64 hours, data for the RDBMS tags can begin to display as *** (stars/asterisks) instead of the actual values contained in the RDBMS database tables. This only occurs for RDBMS data. | Solution: The Process Explorer installation manual (v.6.0 and later) describes the database table structure of the RDBMS tables. This manual documents all of the required and optional fields in the RDBMS database tables. One of the optional fields is called 'ScanLast'. ScanLast tells Process Data how far back into history to look for data.
If no value is specified for ScanLast, or if the ScanLast field does not exist in the RDBMS tables, then the default value of 64 hours will be used. Process Data will look for data in the RDBMS tables as far back as the ScanLast parameter states. All data with timestamps older than:
Current Timestamp - ScanLast
will appear as *** in Process Explorer.
Keywords: stars
asterisks
star
asterisk
References: None |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.