Reported by michaelhalloran, 15 years ago.

I am logging a CAPE-OPEN VB6 UO in ProSim Plus 3.0.2.18. The Validate method is faced with a CalcEquilibrium that does not work, at least it is what I presume. When running the Validate without COLTT (1.07 and 1.08.02 have strictly the same behavior), I get an error message as in Screenshots_woCOLTT.doc, it says “la valeur de la propriété est inconnue”, something like the property value is unknown. With COLTT enabled on the UO, I get an error message as in Screenshots_withCOLTT.doc : “La méthode ~ de l’objet ~ a échoué” which may be translated as “the method of object ~ has failed”.

ProSim SA has told me that CalcEquilibrium is supposed to give an ECapeUnknown error code. The error is prompted by a GetProp made by the thermo server on the MO while the MO is not yet prepared to receive such calls since the MO is calculated once the UO represented the process feed has been calculated. The ECapeUnknown error code is consistent with the message displayed without COLTT “the value of the property is unknown”. So the point may be to investigate if and why ECapeUnknown does not appear as the error code displayed by CapeEquilibrium.

The message displayed by ProSIm Plus without COLTT is not that explicit for sure but it seems wrong to me for COLTT to somehow change the message displayed.

Reported by michaelhalloran, 15 years ago.

The scenario involves mostly a TP flash with accompanying property calculations. In the log file I have:

PropertyPackage <Anonymous> : Call to CalcEquilibrium requesting a TP flash:

MaterialObject <Anonymous> : Call to GetNumComponents

MaterialObject GetNumComponents returns 2

MaterialObject <Anonymous> : Return from GetNumComponents - No Error

To finally end with:

MaterialObject <Anonymous> : Call to SetProp :

Property Phase--- Basis--- Calc---- New value

volume Liquid mole Mixture 0.000022776

MaterialObject <Anonymous> : Return from SetProp - No Error

PropertyPackage Flashtype: TP

PropertyPackage Properties: enthalpy, volume

PropertyPackage <Anonymous> : Return from CalcEquilibrium - No Error

My point is that the lines:

PropertyPackage Flashtype: TP

PropertyPackage Properties: enthalpy, volume

Appear way too long after stating that a CalcEquilibrium is called. I would prefer, for the readibility of the log to have:

PropertyPackage <Anonymous> : Call to CalcEquilibrium requesting a TP flash:

PropertyPackage Flashtype: TP

PropertyPackage Properties: enthalpy, volume

And then

MaterialObject <Anonymous> : Call to GetNumComponents

MaterialObject GetNumComponents returns 2

MaterialObject <Anonymous> : Return from GetNumComponents - No Error

I have logged this issue as COLTT 09-020.

Reported by michaelhalloran, 15 years ago.

This morning I had a remote session organized with Andy Johns of TUV NEL Ltd about a test of their PPDS Thermo server implementing Thermo 1.1 in Aspen Hysys v7.1.

During a run based on a case provided by one of TUV NEL clients (ABB I guess), I observed error messages sent by PPDS to Aspen Hysys about stream composition appearing as null. PPDS is equipped with its own logging facility but it is far from complete: the SetPresentPhases is not logged for example. So I moved to COLTT.

With COLTT 1.07 I was able to give evidence to Andy that PPDS was at fault while setting present phases for both vapor and liquid when the phase fraction for liquid was something like 10 to the minus 16 and while the liquid phase composition was set by PPDS to zero for all compounds. Then Aspen Hysys had the right to request the calculation of liquid phase properties that PPDS was unable to provide since it raises an exception when finding that the composition was null in the MO.

That proves that COLTT is working well.

The only problem I got was that Aspen Hysys is crashing when exiting (see ScreenshotsCOLTTv107.doc). No big deal except it means the PPDS license is not released.

So I moved to COLTT v1.08.02 with the hope of having it doing better on that. Well it is a complete failure: Aspen Hysys simply crashes when opening the case.

I will send you the logs obtained with 1.07 (hysys_090409_115121_v107.log) and 1.08.02 (hysys_090409_114804_v10802.log) as accompanying material in a zipped archive. The issue is numbered 09-021.