Installing and Running OLI Engine for UniSim Design (Trial Copy)

Revision as of 17:36, 23 January 2020 by Jberthold (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Why download the OLI Engine in UniSim Design?

A common question arises from UniSim Design users is "Why do I have to download software from OLI Systems, Inc. if it is already available to me from the UniSim Design installation package?"

This is a good question. The answer is easy to understand. OLI continually updates both its databases with new data and updated data as well as continually updates the numerical engine. The version of the OLI Engine in UniSim Design you received from original installation package could be superseded by a more recent build from OLI. For example, version 9.2.1 of the OLI Engine for UniSim design available for UniSim Design R440. This was the version OLI shipped to Honeywell when UniSim Design R440 was being created for release. More recently OLI released version 9.2.3 which contained updated and new data sets not available in the original 9.2.1. If you needed this new data you would have to download the updated software directly from OLI Systems.

Downloading the OLI Engine in UniSim Design

Go to our Downloads page at

Use your Softkey serial number provided to you by OLI Systems Inc and find OLI Engine listed.

Unisim 20.jpg

Save the file:


Run the file:


Installing the OLI Engine

Click Next on the Setup Wizard:


Select the I accept the terms radio button and click Next:


Input your serial number in the Customer Information section:


Choose the 'Typical Install:


Begin Installation:


You will see the following progress window:


Please check your start bar for the software requesting permission to allow you to make changes to your machine, click OK.

Once the progress bar completes, you will be taken to this next section, click Finish


You will exit from the installation process now

Generating the footprint for the softkey

Go to Start->All Programs->OLI Systems-> OLI Engine 9.2 in UniSim-> Tools-> Security Settings and Test


Open Security:


You will see the following Error message:


Go to the Protection Key Tools Tab:


Click the Collect Information button. This will scan your computer and compose a list of objects and then encode them in a binary format. OLI can use this file but cannot read this file. Under no circumstances will OLI Systems, Inc. share this information without your express/written consent.

After you click Collect Information, it launch a familiar save dialog. save the c2v file in preferred location, for this example, we are saving it in Documents.


Send this file to OLI Systems Inc.

Applying the OLI Softkey ( Applying the OLI v2c file)

You will receive a file from OLI Systems with the name of the softkey with the extension OLIv2c (vendor-to-client). In our example this file name would be: PSXXXXX.OLIv2c.


Once you receive that you can locate the file that was supplied by OLI Systems. Highlight it and select Open.


This message means that the key was installed correctly


Close the Security Settings and Test window at this point.

Once you reopen OLI Software, you will see the following screen , which indicates successful installation:


OLI Engine for UniSim R440

After installing the software your start menu changes slightly.

It is advised that you uninstall the previous versions of OLI Engines associated with UniSim in order to be consistent with the new version.

You can find the OLI Engine under OLI Systems folder:

Unisim 15.jpg

Notice that there is no version number of UniSim associated with this new entry.

Click the new entry OLI Engine 9.2 for UniSim.

Select the Tools folder

Select the tool OLI Engine Config Tool.

Unisim 15 1.jpg

If you receive a message about allowing this program to make changes to your computer, please accept Yes/OK

The OLI Alliance software Config Tool window will pop up as follows:

Unisim 16 1.jpg

This window shows you the installed UniSim programs. As you can see from the example we have version R430 and R440 installed. The program has automatically installed each with the current version of the OLI Engine (for this example that is 9.2.1). The build date of the OLI Engine is also displayed which for this example is 04-December-2014.

Linking the OLI Engine to UniSim

Link a Single Version

You can link a particular version of the software. Highlight a version, for our example we will choose UniSim R440.

Click in the Link button to link OLI Engine 9.2 to UniSim R440

Unisim 21.jpg

Once you click on the link button and select the version, your new UniSim build should be linked to the OLI Engine install you just performed:

Unisim 22.jpg

Check for Updated configuration file

Clicking this link will poll the OLI Download Web Site for a new version of a configuration file. At some point in the future, Honeywell Technologies will release a new version of UniSim (or change its name). At that time this configuration tool will be easily updated by downloading a small file.

Unisim 23.jpg

If this is what you want, then you are done and you can click the Close button.

Only show detected or installed products

This check box is used when a non-standard UniSim installation has occurred. OLI may not be able to directly detect the software or an installation script is being written and UniSim was not available. In this case we can link the OLI Engine to a non-existent product for later installation.


Uncheck the Only show detected or installed products box.


As you can see, there are versions of UniSim that are not installed when this picture was taken.

OLI interface inside of UniSim

Create a new case, in the Basis Environment click Add on the Fluid Pkgs tab

Click Add

Unisim 24.jpg

Scroll down to find OLI Electrolyte package;

Unisim 26.jpg

Add OLI and click component list view:

Unisim 25.jpg

Find the OLI Library Component and select between AQ or MSE framework and add your selected components.

Unisim 27.jpg

Now you know that OLI is working within UniSim.

Please contact OLI if you had any further questions.