Aspen Hysys, and other process simulation software, is an essential tool when we talk about chemical process engineering and plant design. The software has many features and the chemical process engineer can save a lot of time if well used. Below I list 5 features I really like and that can let your life easier.
One of the big issues when sharing aspen hysys files is to match version between users. Even between the same companies I already faced hysys problem because design departments around the world had a different version of aspen hysys. It can happen a lot when a just new version of the software is released. In any case, it is possible to open process simulation developed in V10 or V11 in older versions of aspen hysys. To do that, you just need to save your newest version as .XML. See the procedure below:
To open the file, in an older version of Aspen Hysys, go to File, select Open, Open Case and look for the folder where the .XML file is available, chance file type to HYSYS XML Cases or list All Files. Select the .XML and confirm.
The standard flowsheet colour background in the lastest version of Aspen Hysys is white. Too much brightness and white colour associated with long hours in front of computer leads to eye dryness. Besides that, hysys original version from Hyprotech had green background flowsheet, the same as in the Unisim Design (Honeywell product). The fact is that Aspen Hysys and Unisim Design has the same origin.
To set flowsheet colour go to File tab, select Options and look for Resources Options. a list with Colours and Font Options will be available. Once finished, it is possible to save as Save Preference Set. Everytime you open a new process simulation Hysys will load the new setting conditions.
Once you load a process simulation file using the Open file option, hysys override the current process simulation and there is no windows to return to the previous process simulation. This can be a issue if you need to return to previous process simulation and you do not know how to do that. In my earlier days I used to open many process simulation files in order to be able to shift between them.
However, there is a very easy way to shift loaded files inside Aspen Hysys. you just need to go to File tab and select Active Folder. This way, you will be able to shift between loaded process simulation inside the same hysys window.
Who uses Aspen Hysys for a long time, or any other process simulation software, knows that in some level your process simulation will stop working. This can be very frustanting if lose a lot of work and sets.
HYSYS automatically saves documents for recovery in case the program stops responding or you lose power. When the AutoRecover feature is turned on, the changes you make to a document are saved in a recovery file based on the AutoRecover save interval. For example, if you set Auto Recover to save every 5 minutes, you will recover more information than if you set it to save every 10 minutes. With AutoRecover turned on, if HYSYS hangs (stops responding) while you have cases open, and you have to reboot, HYSYS automatically opens the recovery files when you start HYSYS again. The information in the recovery files reflects the last time AutoRecover saved the cases. AutoRecover is not a replacement for regularly saving your documents; the recovery file is deleted when you save or close the document.
As per standard, Aspen Hysys auto save process simulation each 15 minutes. To adjust the time for auto save click in the File tab, go to Options and in the Simulation go to Auto-recovery Settings. See in the picture below.
Aspen Hysys use a set of colours code to let easier to the user understand what is happening in the process simulation. For instance, to default conditions red means missing information, yellow warning, dark blue normal and light blue not solved.
However it is possible to set a scheme of color to identify variable behaviour. If you go to Flowsheet/Modidy tab, at the right site you will find Conditional Formatting option where Default Colour Scheme is selected.
In this section you can check Display Legend, access Editor and select pre set colour scheme available in Aspen Hysys (HYSIM Colour scheme, P/F colour spec, Temperature, CO2 Freeze Out, Hydrate Formation and Free Mercury). Besides that it is possible to add new sets to the process simulation.
Become an expert in Aspen Hysys enrolling my INPROCESS BOOSTER ASPEN HYSYS training program. It is the fastest and easiest way to learn Aspen Hysys step by step and improve your skills to expert level.
What I gather from the report is that Aspen Plus is looking for a specific version (or a newer one). Which version is that? That probably depends on the version of Aspen Plus that you are using, about which we have no information.
This is a message internal to the Intel library. libifport wants the same version of libifcore to be loaded, and they are not here. Some third-party applications carry along their own versions of the Intel DLLs rather than use the redistributable installer, and this can cause problems.
What version of A+ are you using? If you're not using the latest version of A+, then it may now know about the current version of Intel Fortran -- you should check the AspenTech site for updated versions of the aspcomp.bat file, so that Aspen links into the correct version of the compiler. (We're still using v12 of the AspenOne suite for compatibility with other operations -- as a consequence the installed version of aspcomp did not have the correct name or path for the current Intel Fortran).
Your problem appears to be during installation and not in using Fortran through A+. AspenPlus does not require the user to have Intel OneAPI or a Fortran compiler installed. However, AspenPlus does appear to unpack a number of libifcore*.dll (* = rtd,mmd,mdd etc.) and place them in C:\Windows\System32 and C:\Windows\SysWOW64 folders. When OneAPI is installed, the same files are installed in the OneAPI folders under Program Files (x86). The AspenPlus files have a date of 2017 or 2019, whereas the OneAPI files on my computer have a date of 2021. I have never had this error crop up in AspenPlus during installation although multiple versions of the files do exist. If you cannot get help from A+ customer support, perhaps best doing a clean install once again.
Hello avinshs, While installing AspenPlus V12.1, I am getting these errors "The code execution could not procees because svml_dispmd.dll was not found. Reinstalling the program may fix this problem","The code execution could not procees because libifcoremd.dll was not found. Reinstalling the program may fix this problem", I tried clean installing aspen v12.1 multiple times, still facing same error. So please can you provide me these two dll files (svml_dispmd.dll,libifcoremd.dll) which are of 2017 or 2019(installed by aspen). I don't want OneAPI's libifcoremd.dll and svml_dispmd.dll files, I want the files provided by AspenPlus. It seems i have to place them manually in C:\Windows\System32 before starting installation!
@Hemang_Vadgama You do not have to manually place any files such as libifcoremd.dll or svml_dispmd.dll - AspenPlus does the full install in one step for all the selected packages. If libifcoremd.dll is not available, it will be installed for you.
2. Make sure that the upgraded Sentinel License Manager (SLM V12.2) is correctly installed first and the licenses are recognized. Sometimes the errors are due to SLM. Aspen V12+ will not install with the older SLM in place.
You also need to add your oneAPI installation dir to your PATH before installing the product that depends on Intel Fortran. Please, consult with the installation guide of Aspen Plus to learn more about prerequisites.
While @Alina_S_Intel is correct that the DLLs can be found there, and those are used when running within Visual Studio or a command line build environment, they are not used when running outside those environments. Instead, the DLLs installed under Program Files(X86)\Common Files\Intel are used. These are supplied by the redistributables installer and added to PATH. It is not correct to add the oneAPI installation directories to the system PATH variable.
@Hemang_Vadgama , do NOT place those DLLs in the Windows System32 folder! Doing so will break other programs. I suggest installing the latest oneAPI runtime DLLs - this should be compatible with older code. If Aspen is copying those DLLs into a Windows folder, it is horribly broken.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
ChemWanderer: You are welcome. Yes, for this scenario it is very important to collect the requirements of the Aspen Plus software, Intel processors are able to support different applications, but to be sure we need to check the requirements of the tool itself. Aspen Plus software, like most other software, continues to evolve and new versions are released frequently. This online course covers Aspen Plus version 11, the latest version at the time of recording this video. Please note that this online course covers the basic features of Aspen Plus that do not change from version to version. The course explains how to use Aspen Plus on computers that use the Windows operating system. We assume that Aspen Plus is installed on your computer and that you have a basic knowledge of how to use the computer. If you`re new to Aspen Plus and have little or no experience in chemical engineering simulation, then you`ve come to the right place. Equation-oriented Aspen Plus models and ACM simulations can get quite large. For large simulations with more than 100,000 variables, we recommend that users get a separate desktop, each with a 64-bit Windows system with 8 GB or more of RAM and a fast processor. More than 2 cores are not an advantage for Aspen Plus or Aspen Custom Modeler on a single user computer. Using a 64-bit operating system means that our products can access 4 GB of RAM instead of 2 or 3 GB on a 32-bit computer, which is useful for very large simulations.
c80f0f1006