Custom Query (122 matches)


Show under each result:

Results (52 - 54 of 122)

Ticket Resolution Summary Owner Reporter
#182 fixed Can't disabled COLTT on UO Michael Halloran michelpons

Reported by michelpons, 9 years ago.


With a UO supplied to me, once COLTT is enabled on it, even if I untick the \"Enable\" box, after closing the controller, reopening it lets see the UO with COLTT enabled once more. Something must be wrong in the way the registry access works. The DLL with its registration exe will be supplied. The only way I have found to go around the issue is to open the registry (regedit), to search for the UO name (Tester Helper), to suppress the entry in the registry for it, and then to register the UO again. If something goes wrong when disabling COLTT on a UO, the end-user should be told about it. If there is a way to easily circumvent the issue, it should be arranged for.

#184 fixed Logging CompIds for SetProp of scalar mixture property Michael Halloran michelpons

Reported by michelpons, 9 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.

#185 duplicate Three log files created for one run Michael Halloran michelpons

Reported by michelpons, 9 years ago.


Usually, whatever the number of PMCs on which logging is enabled, there is a single log file created per PME run. I have a scenario that leads to three different logs created for a single PME run. The scenario is using Aspen Hysys 8.4 CP1 with Hotfix dated February 2014. Prior to running Aspen Hysys, an XFlow file has been created using the XFlowSaver UO. The attached Stream01 file is containing the saved material stream. The point here is to save a material stream created in one PME, here COFE, and to automaticalmy load this material stream in another PME. I enable COLTT on both the TEA Thermo System and on the XFlowLodaer UO. In Aspen Hysys I start with a new case. First I define a Fluid Package as a CAPE-OPEN 1.0 Property Package which is the n-depropanizer PP from TEA Thermo System. Then I insert the XFlowLoader UO in Aspen Hysys (while in hold mode) and one Material Stream. I connect this Material Stream to the outlet Port of the XFlowLoader UO. I edit the XFlowLoader and I point to the attached Stream01 file so that it may be loaded as needed. After editing, I make the flowsheet active. Then the XFlowLoader is calculated, meaning that the contents of the Stream01 file are loaded in the UO which then sets its properties in the Aspen Hysys Material Stream. I then exit Aspen Hysys without saving the case. I obtain the three attached logs. There should be only one log file.

Note: See TracQuery for help on using queries.