CAPE-OPEN

The forum is back up and running! Therefore at this point we are happy to report the release of COCO 3.8 Since 3.7, the following improvements were made: A new energy measure unit, to convert energy stream values to information streams Allowing sub-selection of feeds and products in COCO Flowsheeet ...

Once you created the COM object you should be able to use all the same functions. There is no external stop function. This would also not be possible as Solve does not return control until it is done - it would have to be done from another thread, and the COFE object is apartment threaded (can only ...

... down side is that apparently Excel can only contain 32000 or so characters in a cell: https://techcommunity.microsoft.com/t5/ ... /m-p/66355 - for larger strings you need to find a different way, e.g. split it up over multiple cells.

I am not sure whether this can be done. As the flowsheet is embedded as OLE object, Excel decides whether it should be saved or not. I suppose that if you edit the flowsheet after the solution was imposed, Excel will assume the OLE object was changed and it will be saved. But I do not see an easy wa...

The MeasureUnit help explains what the MeasureUnit does: https://www.cocosimulator.org/index_help.php?page=COUS/measureunit.htm I do not think there is one single definition that fits all purposes. If you need the ideal gas volume, I suggest you use the approach you sketched with the information cal...

Before the mixer: the values match to the 4th digit (corresponding with the accuracy of the gas constant you put in the information calculator) if you switch the vapor phase thermo to Ideal Gas. But in the document as attached, the vapor phase is set to Peng Robinson. After the mixer: If you bring s...

You can embed a COFE flowsheet directly in an Excel sheet (use the Excel template to get started). Then you can simply hide the sheet on which the COFE control is I suppose. Note that the template uses VBA macros, this may be a disadvantage. It is meant to demo automation. You can access automation ...

I did not get notified of this message and missed it. My apologies. Is the question still relevant?

There is currently no such protection. I am also not sure what you would be looking for - just a way to prevent the user from opening the GUI and making modifications? That would be rather easy to circumvent, because the COCO .fsd file is just a zip file with an xml inside, which can be manipulated....

The message "something is wrong" is very vague. Default.cota is a pre-installed package, or did you export that from a working simulation?