Custom Query (122 matches)
Results (28 - 30 of 122)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#88 | worksforme | COLTT does not recognize UO as supporting CAPE-OPEN interfaces | michaelhalloran | michelpons |
Description |
I am using the case described in Ticket 03. I am using COLTT build dated July 17, 2011. This build incorporates a test about presence of Microsoft .Net 3.5 on the machine at installation. Since ProSim Plus does not need .Net 3.5 I installed .NET 3.5 SP1 and the necessary updates (except KB2518864 which did not succeed). The scenario calls for starting ProSim Plus with a case file that contains only four streams, one being the inlet. I insert the UO in the flowsheet and I connect its ports (one inlet, three outlets) to streams in the flowsheet. I define the UO parameters using the Edit function. Connection of ports, edition work fine from a ProSim Plus point of view with or without COLTT enabled on the UO. When asking for the UO to validate itself I get the kind of error message that is mentioned in Ticket 03. Now with COLTT build July 17, 2011, I get a very short log file saying that the UO is not supporting CO interfaces that COLTT may logged. I uninstalled COLTT July 17, 2011 and I installed the 1.08.04 version available from SourceForge. That time I get a rather complete log file that shows COLTT is able to log what happens between the PME and the PMC. Stating that the UO is not supporting the CO interfaces seems a little bit strange then. |
|||
#113 | fixed | COLTT entry remaining in Viewer after filtering COLTT entries | Michael Halloran | michelpons |
Description |
The line \"COLTT Property Package Final Release...\" remains in Viewer even after filtering all COLTT entries. The issue has been documented using PRO/II 9.1 and the VB6 PP example Thermo System together with the native PRO/II flash but should be present in other configurations. |
|||
#139 | Not Reproducible | COLTT log file created for a case with failed initialisation of Aspen Properties won't load into the Viewer | michaelhalloran | michaelhalloran |
Description |
This one is a mistake caused by using the Viewer when the log file was still being written to. |