Reported by michelpons, 10 years ago.

It appears that COLTT does not log the CompIds argument in a SetProp for a scalar mixture property. It should.

I have encountered an issue with this argument with the following scenario: Take Aspen Properties HDA PP under OATS. Open COFE and select the OATS/ HDA Aspen Properties PP. In the COFE view “Flowsheet configuration”, where you will see “Aspen Properties 28.0/HDA” listed, click on “Material types”. There untick the boxes on the left of Hydrogen, methane and diphenyl. That way the Material Objects defined by COFE will carry only benzene and toluene as compounds. Close the Flowsheet configuration view. Go to Flowsheet/Calculator. As property select enthalpy. As phase select Vapor. As temperature enter 500 K. As pressure enter 100000 Pa. For the mole fraction of C6H6 enter 0.5 (the diphenyl mole fraction will be set to 0.5 automatically).

While you are entering these pieces of information, error messages will appear in the bottom part of the COFE screen. This is OK. COFE attempts to make the calculation requested even before all the necessary pieces of information have been provided. However take notice of the last error message: “Failed to calculate property enthalpy for phase vapor (calType mixture): CalcProp failed: The following errors showed on calling AspenCalcProp[]: Failed to ICapeThermoMaterialObject > SetProp[].

COLTT does not report that compIds contains \"C6H6\" and \"TOLUENE\" while it should be UNDEFINED for a scalar mixture property. In order to pinpoint sucn an error with COLTT, COLTT should display the CompIds even for that kind of property.

Reported by michelpons, 14 years ago.

I set up a scenario in Aspen Plus 7.2 where I reload a saved case where a COUSCOUS splitter is configured with three outlets. All ports are connected to streams. During the reload of the case, the call to Disconnect on each of the UO Port fails: \"Error returned from Disconnect - 0x80040501\". I don't see COLTT attempting to call the error handling interfaces on the Port. My understanding is that a Port should implement the error handling interfaces and so could be queried for further information. I attach the log file obtained.

Reported by michelpons, 13 years ago.

I am using A+ v7.1 and a FORTRAN UO Mixer. While the run goes rather well (the UO is not found in mass balance by A+ though) with COLTT (May 30, 2011 build) enabled on the FORTRAN UO Mixer, the log file obtained does not load properly in the Viewer.