Reported by michelpons, 8 years ago.

I have a PME returning 0x8004051a to a CalcsinglePhaseProp call: PropertyPackage <WaterEthanol> : Call to CalcSinglePhaseProp

CalcSinglePhaseProp takes input Arguments:

Property Phase POH Liquid

MaterialObject <1> : Call to GetPresentPhases

GetPresentPhases returns:

Phase Status Liquid CAPE_ATEQUILIBRIUM

MaterialObject <1> : Return from GetPresentPhases - Succeeded MaterialObject <1> : Call to GetTPFraction

GetTPFraction takes Input Argument:

The Phase: Liquid

GetTPFraction returns:

Phase Temperature Pressure Composition

Liquid 298.15 101325 0.9

0.1

MaterialObject <1> : Return from GetTPFraction - Succeeded COLTT <WaterEthanol> : Windows error code returned is: 0x8004051a - not known COLTT <WaterEthanol> : No error information available, call to GetErrorInfo returned: 0x1 PropertyPackage <WaterEthanol> : Error returned from CalcSinglePhaseProp - 0x8004051a PropertyPackage <WaterEthanol> : Call to get_description PropertyPackage <WaterEthanol> : Description: pO v CALUPP failed to calculate properties that may be caused by missing parameters or other reasons, please see history file. PropertyPackage <WaterEthanol> : Return from get_description – Succeeded

This is read by COLTT as a Windows error and not as a CAPE-OPEN error. It should be read as a CAPE-OPEN error.

Reported by michelpons, 12 years ago.

I am using Aspen Hysys 7.3 CP2 and a specially developed PPM based on the thermo examples distributed by CO-LaN. The PPM is returning an empty list of constant properties (return on GetConstPropList call) and then Aspen Hysys calls GetCompoundConstant. This apparently raises an error.

COLTT 2.1 build June 5, 2012 says the followinh: PropertyPackage <Anonymous> : Call to GetCompoundConstant

GetCompoundConstant takes Input Arguments:

Error - compIds argument should be of type VT_ARRAY|VT_BOOL not VT_ARRAY|VT_BSTR

GetCompoundConstant returns:

Property Compounds ValueReturned

Warning - propvals argument is empty

PropertyPackage <Anonymous> : Return from GetCompoundConstant - Succeeded

I think the compIds argument should not be a boolean. So may be the message has to be reversed (I don't know what Aspen Hysys is using though). Installer for the PPM as well as instructions to install and use will be delivered through other communication means.

COLTT version 2.0 did not mention an error, i.e. no test was apparently made.

Reported by michelpons, 12 years ago.

In the attached log filen within Calculate I know that the UO gets temperature, pressure, partial mass flowrates from the MO connected to the inlet Port and then sets the same properties on the MO connected to the outlet Port before flashing the MO on the outlet Port. But all SetProp/GetProp calls are mentioned as being made on an anonymous MO. Without the source code of the UO, it would be impossible to know on what the UO acts. Even if the MOs are not named by the PME, which is a pity, could COLTT discriminate between anonymous MOs and mention an Anonymous_1, Anonymous_2 so that one could better follow the sequence?