[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 173: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/feed.php on line 174: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
CAPE-OPEN Discussions about use and implementation of the CAPE-OPEN standard 2018-04-14T10:44:40+00:00 http://www.cape-open-forum.org/feed.php?f=5&t=516 2018-04-14T10:44:40+00:00 2018-04-14T10:44:40+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=2061#p2061 <![CDATA[Re: Problem(s) with COCO 3.2]]>
4) add a check box to the energy-mixer (and -splitter) dialog to suppress exposing the temperature limits on the products. If you check this box, your case will work.

As this must be done in Edit mode, there should not be problems with updating the stream. Nevertheless, as energy and information streams are updated upon first connection, I expect there to be cases in which the stream must be disconnected and reconnected.

Let me know if this gives any trouble - the updates are available via CUP.

Also, for the next issue you find, can you start a new topic? This one is getting somewhat lengthy and includes various different issues.

Statistics: Posted by jasper — 14 April 2018, 10:44


]]>
2018-04-14T08:37:30+00:00 2018-04-14T08:37:30+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=2060#p2060 <![CDATA[Re: Problem(s) with COCO 3.2]]>
COFE does not like this as it likes all attributes of the stream to be specified - so it is COFE that raises the error. In case items on a stream remain unspecfied, COFE will be unable to solve recycles in case the stream happens to be a cut stream.

There a number of possible solutions to the issue

1) COFE is modified to just to take into account the work on a stream, and ignore the other data, while solving. This may have as a side effect that the other data (e.g. temperature limits) are not actually converged upon solution, or
2) the energy mixer is modified to put some dummy temperature limits on the product (e.g. [0 K - 1e6 K], or [0 K - 0 K]) when the data are missing (in case of which the feed data is not likely to be originating from a thermal source - in your case it is not). This has the disadvantage that these dummy limits may be taken by the downstream unit as actual limits, or
3) the energy mixer is modified to no longer expose the limits in case they are not present on other of the source streams - this has the disadvantage of added complexity to the unit's logic and changing data on the product stream as a result of connecting / disconnecting a source stream, which may not be taken into account by the downstream unit

I am inclined to go with solution (1) - do you see any issues with this?

Statistics: Posted by jasper — 14 April 2018, 08:37


]]>
2018-04-13T18:26:06+00:00 2018-04-13T18:26:06+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=2056#p2056 <![CDATA[Problem(s) with COCO 3.2 {010}]]>
Version: COFE 3.2.0.21
High and Low Temperatures are not provided by Energy Streams connected to Units so the Energy Mixer Unit will not solve. The lower loop solves because one of the inlet Energy Streams has its High and Low Temperatures specified. I have emailed an fsd file for your review. I hope this can be fixed.

Note: Please back up the emailed fsd file before attempting to solve it because it cannot be reset.

Energy Mixer Problem (Forum 18Apr 13).png

Statistics: Posted by nrgeng — 13 April 2018, 18:26


]]>
2017-09-25T21:37:37+00:00 2017-09-25T21:37:37+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1920#p1920 <![CDATA[Re: Problem(s) with COCO 3.2]]> Statistics: Posted by jasper — 25 September 2017, 21:37


]]>
2017-09-25T12:30:47+00:00 2017-09-25T12:30:47+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1919#p1919 <![CDATA[Problem(s) with COCO 3.2 {009a}]]>
Thanks for your response to this problem. I am using COFE version 3.2.0.16.

In the upper simulation from Posting 009's fsd, if you exchange the positions of the valve and the flow constraint, COFE reports the flowsheet as solved. The lower simulation with its error has been left unchanged and has gone unreported. Any ideas? Thanks.

Statistics: Posted by nrgeng — 25 September 2017, 12:30


]]>
2017-09-24T20:01:25+00:00 2017-09-24T20:01:25+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1916#p1916 <![CDATA[Re: Problem(s) with COCO 3.2]]> Statistics: Posted by jasper — 24 September 2017, 20:01


]]>
2017-09-24T19:59:58+00:00 2017-09-24T19:59:58+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1915#p1915 <![CDATA[Re: Problem(s) with COCO 3.2]]>
The error is now properly indicated and is unrelated to the controller. The error is that flow constraints must be inside a closed recycle or on the start of a feed stream as the first unit. The reason for this is that if the flow constraint is not in a recycle but not the first unit in the stream, it must control its feed stream, which is also controlled by the upstream unit.

The controller is not the source of the trouble. The source of the trouble is the invalid flow constraint in one of the two feed streams, which has an upstream valve unit. But, you also delivered the same flowsheet without the controller, and concluded that it solved. It did not. It looked solved, as the same error in the flowsheet analysis did not get reported to the solver, but without the recycle the unit that showed the problem immediately got marked solved and the solver process finished. If you look at your case where the controllers is removed closely, you will see that it is not actually solved; the mass balance around the flow constraint is not satisfied.

Please find an update that fixes the error reporting issue, and now both samples will, correctly, not solve, and moreover indicate the cause. You can easily fix the setup by placing the flow constraint upstream of the valve.

As an aside, note that your measured variable is always equal to your controlled variable. Not sure if this was an actual example, but you can simply eliminate your controller and measure unit, and simply stick the ‘setpoint’ directly into the controlled stream.

Statistics: Posted by jasper — 24 September 2017, 19:59


]]>
2017-09-24T02:01:51+00:00 2017-09-24T02:01:51+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1914#p1914 <![CDATA[Problem(s) with COCO 3.2 {009}]]>
I am sending an fsd for your review. I am using COFE version 3.2.0.15.

This problem is probably connected to Postings 007 and 008. The flowsheet solves without Controller FC but not with Controller FC. Any ideas? Thanks.

Statistics: Posted by nrgeng — 24 September 2017, 02:01


]]>
2017-07-17T07:01:21+00:00 2017-07-17T07:01:21+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1874#p1874 <![CDATA[Re: Problem(s) with COCO 3.2]]>
RSP?

Restarting re-initializes the guess from a subset of specifications already in the flowsheet. This may lead to a better state than the flowsheet was in - particularly in case the solution was trying to go into a region where one or more units or streams could not be calculated.

I will be happy to analyze the reported issues further with more information on the flowsheet - at least the connectivity.

Statistics: Posted by jasper — 17 July 2017, 07:01


]]>
2017-07-13T20:50:18+00:00 2017-07-13T20:50:18+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1872#p1872 <![CDATA[Problem(s) with COCO 3.2 {008}]]>
I will not be sending an fsd file but want to inform you of the odd behavior of the solver included with COFE version 3.2.0.14.

I just inserted a Controller Unit into the flowsheet. The Controller Unit would not register the SP from the RSP port. The Controller Unit was deleted and a new Controller Unit was inserted. The controller registered the SP in the Unit Edit dialog so the flowsheet, which solved previously, solved.
Then:
1) Changed SP from 125 to 120
2) Partition 2 showed residual gradually decreasing
3) Stopped and aborted simulation
4) Restarted, and the simulation solved almost instantaneously
5) After that, the SP can be increased or decreased with almost instantaneous results
6) What happened? Was the Controller Unit at fault?

This problem seems similar to Item 1 of posting {007}, I hope this information will help when evaluating future reported problems.

Statistics: Posted by nrgeng — 13 July 2017, 20:50


]]>
2017-04-30T11:53:07+00:00 2017-04-30T11:53:07+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1824#p1824 <![CDATA[Re: Problem(s) with COCO 3.2]]>
Not sure of whether this was introduced by your artificial example, but in your example case for the second controller, the measured value at solution must always be equal to the controlled value. Hence, you can, in this case, eliminate the controller, directly control the feed rate from the other controller and eliminate the measure unit.

2) not clear on what you mean. What exactly does not update? Can you send me a screen shot?

Statistics: Posted by jasper — 30 April 2017, 11:53


]]>
2017-04-29T14:37:38+00:00 2017-04-29T14:37:38+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1823#p1823 <![CDATA[Problem(s) with COCO 3.2 {007}]]> Updated to COFE 3.2.0.11

Within two different flowsheets, the same two problems occur. A portion of one flowsheet exhibiting one problem has been emailed as an fsd.
Problems:
1) Cascade controls do not function properly. The secondary loop does not receive/accept RSP signal from primary loop controlled variable.

Intermittent
2) Document Explorer does not update displayed data. This problem occurs in the flowsheet but not in this portion of this flowsheet. (More about this in another Forum posting)

The RSP Information stream between primary and secondary controllers in a cascade loop is not resetting the secondary controller SP, but the RSP input of the secondary controller does change the SP without the primary controller connected. Can this be corrected?

Additional information regarding another flowsheet with the same problem:
Able to manually operate simulation with MV in the range of 48 to 52. When a controller is inserted, and set to MV of 50, it winds the MV to zero and all successive iterations are with the same residual shown. The solver seems to be "stuck." Any idea why? Have others reported any similar problems? I have observed this phenomenon in two different simulations. Has the solver been changed recently? I am now unable to use the Controller Unit in COFE 3.2.0.11 for other than simple loops. Help! Any suggestions?

Statistics: Posted by nrgeng — 29 April 2017, 14:37


]]>
2017-03-27T08:35:34+00:00 2017-03-27T08:35:34+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1770#p1770 <![CDATA[Re: Problem(s) with COCO 3.2]]> Statistics: Posted by jasper — 27 March 2017, 08:35


]]>
2017-03-24T10:45:26+00:00 2017-03-24T10:45:26+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1769#p1769 <![CDATA[Re: Problem(s) with COCO 3.2]]> Statistics: Posted by jasper — 24 March 2017, 10:45


]]>
2017-03-23T19:10:54+00:00 2017-03-23T19:10:54+00:00 http://www.cape-open-forum.org/viewtopic.php?t=516&p=1768#p1768 <![CDATA[Problem(s) with COCO 3.2 {006g}]]> Statistics: Posted by nrgeng — 23 March 2017, 19:10


]]>