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.

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 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.