Page 2 of 2

Re: Cannot use the Excel Unit Operation

PostPosted: 25 February 2014, 10:11
by jasper
I am afraid I am not sure how to help you here, as this is clearly an Excel issue and not a COFE issue.

Re: Cannot use the Excel Unit Operation

PostPosted: 25 February 2014, 10:32
by jasper
As a side remark, Excel is not always as stable while executing either. The Scilab and Matlab unit operations have much fewer stability issues (as Scilab and Matlab themselves run much stabler). For this reason I personally prefer setting up custom models in Scilab or Matlab over Excel.

Re: Cannot use the Excel Unit Operation

PostPosted: 25 February 2014, 10:38
by arvind.prasad
Then, I will try to lean Scilab and learn to write models in Scilab. I guess you must have surely uploaded some tutorials in scilab. I'll go through them.

Re: Cannot use the Excel Unit Operation

PostPosted: 25 February 2014, 11:45
by jasper
Please note that I just uploaded version 1.0.0.22, which fixes an important issue. Please make sure to use this version rather than 1.0.0.21

A function reference is included in the help file, here are some examples:

http://cocosimulator.org/downcs.php?dl= ... 8p3484.fsd

http://cocosimulator.org/down.php?dl=Sa ... p_COCO.pdf
http://cocosimulator.org/down.php?dl=Wa ... Scilab.fsd
http://cocosimulator.org/down.php?dl=Wa ... abatic.fsd

Re: Cannot use the Excel Unit Operation

PostPosted: 25 February 2014, 23:13
by rhsrxs
I also prefer using Scilab. This website has some great engineering examples in Scilab - http://www.scilab.in/Completed_Books.

Also, attached is an example for quick calculation of pressure drop in a pipe for gas flow. Scilab tutorials are easily located using google search.

Re: Cannot use the Excel Unit Operation

PostPosted: 26 February 2014, 08:18
by jasper
Nice example. This example is still explicit in its calculations and does not require a solver. The strength of units like the Excel unit, Matlab unit and Scilab unit is that you can use the solvers that are available with Excel, Matlab and Scilab.

Note that the first setProduct in this example seems redundant.