Reported by michelpons, 14 years ago.

The scenario is based on the one described for ticket #34 and is obtained when there is no PPDS license available. There is a complete process model developed in Aspen Hysys and making use of PPDS. Because the license is not there the PPM returns an error code 0x80040501 and this is logged in the log file. Aspen Hysys does not seem to pursue any further the matter. However I don't see any attempt from COLTT to query the error handling interfaces that should be present on the PPM object. I wonder why.

Reported by michelpons, 15 years ago.

I am using as PME-PMC combination UniSim Design (PME) and Simulis Thermodynamics (PMC). In the log obtained with COLTT 1.08.03 enabled on the Simulis Thermodynamics Thermo System, I find the following: PropertyPackage <Anonymous> : GetComponentList returns :

Name CAS No Formula TBP MW Nitrogen 7727-37-9 N2 77.3565 28.0134 Argon 7440-37-1 Ar 80.3011 39.948 Oxygen 7782-44-7 O2 90.1792 31.9988

PropertyPackage <Anonymous> : Return from GetComponentList - Succeeded

It is a pattern that mentions \"Succeeded\" on the line corresponding to the return from a method.

But I find also:

PropertyPackage <Anonymous> : Call to GetComponentConstant requesting these constants :

molecularWeight

MaterialObject <Anonymous> : Call to get_ComponentIds

get_ComponentIds returns : 7727-37-9 7440-37-1 7782-44-7

MaterialObject <Anonymous> : Return from get_ComponentIds - Succeeded PropertyPackage <Anonymous> : GetComponentConstant returns

Compounds molecularWeight 7727-37-9 28.013400 7440-37-1 39.948000 7782-44-7 31.998800

The \"succeeded\" is not mentioned then.

Reported by michelpons, 11 years ago.

I am using ProSim Plus 3.3.13.0 together with Aspen Properties v8.0. It is a simple flash but on a mixture containing ions. I am enabling COLTT on Aspen Properties Thermo System and I am running the flowsheet made of a single unit operation, a TP flash. When the box is ticked about error interfaces automatically called when errors are raised, ProSim Plus crashes. When I am simply enabling COLTT and no other options, the run goes to its end nicely. I am using COLTT 2.1 Build 280. My guess is that the description of the last error is a bit too long for COLTT to handle it, but it is just a guess.