Reported by michelpons, 13 years ago.

When a call to the Item method on a Parameter Collection occurs the Viewer displays: Parameter Collection <C01> : Call to Item

Parameter Collection Item takes input argument: 1 Item returns : 1 : 0x129247d8

While for an Item method call on a Port Collection, the Viewer displays:

Port Collection <C01> : Call to Item

Item returns : FEED 1 : Ox12922440

So the input argument is missing in the Port Collection display. This has some importance when the Item method call fails. One does not know for the Port Collection which item has been called.

Reported by michelpons, 13 years ago.

I am re-testing TRAC Ticket #16 with COLTT 1.08.05 Build July 17, 2011. The issue I have is that COLTT does not seem to recognize the CAPE-OPEN Property Package used as a CAPE-OPEN component. The COLTT log mentions that the component does not support the CO interfaces COLTT is able to log.

The component may be installed using the MSI found at: ​http://www.colan.org/Members-temp/index5_dateien/ThermoPack11-1_02.msi

The scenario is in Hysys but I wonder if this is in anyway related to the PME used because everything seems to go on correctly with Aspen Hysys: selecting the PP, selecting the flash, etc... I have attached the short log file obtained.

Reported by michelpons, 13 years ago.

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.