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.

Reported by michaelhalloran, 15 years ago.

I am starting with a case file of UniSim Design R390 where one inlet stream is defined and three outlet streams are drawn. The scenario is to select a VB6 CAPE-OPEN UO (made by TOTAL) and insert it in the flowsheet, connect it, edit it and run it.

With COLTT 1.07, I get to the same point as without COLTT 1.07 enabled on the VB UO. The case can’t be run because the UO can’t be validated since the mixture molecularweight property is missing from the UniSim Design UO. You will find the file Screenshots_v107.doc showing the point I can reach and unisimdesign_082609_212727_v107.log as the log file obtained.

With COLTT 1.08.02 I can’t get so far. The UO does not load in UniSim Design when logged. You will find attached Screenshots_v10802.doc showing what happens as error message and unisimdesign_082709_075015_v10802.log as the log file obtained.

When I say attached, I will post the files as an archive on yousendit.com to ensure you can get access to these.

I am numbering this issue as COLTT09-018. I don’t know if the latest modifications committed by SHMA on COLTT will lead to a different behaviour. There is a need to know.

Reported by michelpons, 15 years ago.

A defect had been raised a while ago with SimSci-Esscor about the fact that InitNew was not called by PRO/II on a a new CAPE-OPEN UO being inserted in a flowsheet. According to SimSci-Esscor secondary support, the bug LFPE#25122 (InitNew not called) got fixed and working fine. However the log I can make of a COUSCOUS UO in PRO/II 8.3 does not show InitNew being called (see proii_090909_194007.log). SimSci-Esscor thinks that COLLT is not reporting InitNew call when the persistence type is IPersistPropertyBag.

They have tested the behavior with their internal CAPE-OPEN test units (COSESPersistB100.dll, COSESPersistC100.dll and COSESPersistD100.dll in zipped archive). The COLTT log file (proiid_PKM.log) shows that InitNew is called for persistence types IPersistStreamInit and IPersistStorage (they made their run with COLTT 1.07). However, the COLTT log file does not show the call to InitNew when the persistence type is IPersistPropertyBag. SimSci-Esscor has debugged the code and noticed that InitNew is called for IPersistPropertyBag also. So there is a good chance that COLTT has not implemented IPersistPropertyBag and that leads to an improper report on InitNew being called.