Jump to content

Featured Articles

Check out the latest featured articles.

File Library

Check out the latest downloads available in the File Library.

New Article

Product Viscosity vs. Shear

Featured File

Vertical Tank Selection

New Blog Entry

Low Flow in Pipes- posted in Ankur's blog


Warning Popup Treatment, Hysys-Matlab Communication Activex

hysys matlab communication

2 replies to this topic
Share this topic:
| More

#1 jjurm007


    Brand New Member

  • Members
  • 2 posts

Posted 06 July 2018 - 03:02 AM

Hello, everyone. Nice to meet you all!


Today I have signed up for this community by chance searching to solve a problem I have confronted.


The problem is "I can't find out how to remove the warning popups for a infeasible design in a reflux distillation column run".


Both by automation through MATLAB activeX handle approach, and HYSYS program settings.


In either ways I want to

1. avoid popups arising


2. handle the situation by a)knowing popup is on and B) sendKeys through to close popups by actxserver("WScript.Shell")


3. just not make up popups by HYSYS settings.


4. approach HYSYS.Backdoor through activeX handle(to search the whole hierarchy to find the object related to warnings or status)


Currently, the popup shows up when I run the column by


because I'm trying to make a feasibility matrix for the distillation column.


Thank you in advance.

Replies will help me a lot.

#2 jjurm007


    Brand New Member

  • Members
  • 2 posts

Posted 06 July 2018 - 03:24 AM

I forgot to add some points.


1. It didn't work when I ticked off the error display options as below.

2. Or when I used "ChangePreferencesToMinimizePopupWindows(hysys,1)"

Attached Files

#3 marchem


    Gold Member

  • Members
  • 152 posts

Posted 06 July 2018 - 08:26 AM

from your description I would guess you wish to call the column object (in Aspen) from some Matlab code, for example as part of some optimization procedure,

do not forget that simulators run as independent processes, they have their own exception handling and so on... if you stop error reporting you may lose control on exception handling with possible numerical errors (which can stop optimizer etc.) so, before to stop error reporting make sure the simulator has the ability to recover automatically from all this kind kind of problems...

for similar applications (running procedures from Matlab, Mathcad etc.) I prefer thermodynamic libraries (I have Prode Properties) but at cheresources forums you can find posts discussing both solutions....

Similar Topics