Reported by michelpons, 14 years ago.

De: Michael Halloran [michaeljhalloran@…] Envoyé: Saturday, April 25, 2009 7:40 PM À: Michel Pons Cc: Ahsan Akhtar Objet: Re: Simulis Thermodynamics in Aspen Hysys 2004 Michel,

You'll notice that the calls which use anonymous as the name are all on the ICapeUtilities Interface which is a separate logger in 1.08 after the refactoring. The problem is that this logger hasn't been told that the name of the unit has changed.

Ahsan, there needs to be a mechanism to pass the name of the owning PMC to all aggregated loggers when the name is changed. It should be similar to SetLoggedComponent but it only needs to pass name. It needs to be called from put_PMCName. Could you investigate?

Regards Michael =========================================================== De: Michel Pons [technologyofficer@…] Envoyé: Wednesday, April 15, 2009 10:28 AM À: 'Ahsan Akhtar' Cc: 'michaeljhalloran@…' Objet: FW: Simulis Thermodynamics in Aspen Hysys 2004

Pièces jointes: hysys_041009_170955.log

Ahsan,

I was not able to pinpoint which of the « old » issues this was related to. So please consider this as issue 09-007 till one knows better.

Best regards

Michel =============================================================== De: Michel Pons [technologyofficer@…] Envoyé: Friday, April 10, 2009 5:54 PM À: 'Michael Halloran' Cc: 'Ahsan Akhtar' Objet: RE: Simulis Thermodynamics in Aspen Hysys 2004

Pièces jointes: hysys_041009_170955.log

Michael,

Please find attached a log of a MatLabUO in Aspen Hysys v7.1 as logged with COLTT v1.08.02.

I don’t see a difference between having MatLabUO logged and not logged. I get the same kind of errors displayed by Aspen Hysys.

Still I am a bit bewildered by the fact that once Aspen Hysys has put CO-100 as component name,

Unit <Anonymous> : Call to put_ComponentName Unit put_ComponentName puts: CO-100 Unit <CO-100> : Return from put_ComponentName - No Error

I still get now and then <Anonymous> to be used as name for the UO:

Unit <Anonymous> : Call to get_parameters

Unit <Anonymous> : Return from get_parameters - No Error

Unit <Anonymous> : Call to Edit Unit <Anonymous> : Return from Edit - No Error

Amidst numerous entries using <CO-100> as the Unit name. I think this is an old issue though.

Best regards

Michel

Reported by michelpons, 15 years ago.

De: Michel Pons [technologyofficer@…] Envoyé: Sunday, April 26, 2009 10:26 PM À: 'Michael Halloran' Cc: 'Ahsan Akhtar' Objet: RE: GLCC UO In Aspen Hysys v7.1

Pièces jointes: COLTT09_011_Screenshots.doc

Michael,

Please find attached a Word file with screenshots obtained with the scenario of COLTT issue 09-011. I ignore the assertion failed error and then Aspen Hysys crashes.

Best regards

Michel ======================================================= De: Michael Halloran [michaeljhalloran@…] Envoyé: Saturday, April 25, 2009 11:35 PM À: Michel Pons Cc: Ahsan Akhtar Objet: Re: GLCC UO In Aspen Hysys v7.1 Michael,

Can you add information about the assertion? When you get an assertion do you try to ignore it and continue the run?

I don't understand the logs here. The 1.07 log should show the calls to get_ComponentName in the same places as the 1.08 log. The 1.07 logger is logging them and they must have been called or the name shown in the log wouldn't have changed to Check for the 1st parameter. So that looks like a 1.07 problem to me; the 1.08 log is what I would expect.

Regards Michael ========================================================== De: Michel Pons [technologyofficer@…] Envoyé: Thursday, April 23, 2009 10:15 PM À: 'Ahsan Akhtar' Cc: 'Michael Halloran' Objet: GLCC UO In Aspen Hysys v7.1

Pièces jointes: hysys_042309_215826v107.log; hysys_042309_215412v1082.log

Ahsan,

I have ran a combination involving a CAPE-OPEN UO using Thermo 1.0 and Aspen Hysys v7.1. The UO comes from TOTAL and has been made with the Visual Basic Wizard.

The scenario starts from an Unconnected case file that displays three streams, one to be used as inlet and two as outlets to the UO. I use “Add Operation” then Extensions the CAPE-OPEN 1.0 and select GLCC UO. Then I accept this choice. Things are differing from then on with/wothout COLTT and between COLTT versions.

Without COLTT enabled on the GLCC UO, I get message boxes from Aspen Hysys of the type “Error in ExposeCOParstoHysys(13)”. This has been documented to Aspentech Support and is in the process of being solved. Several of these message boxes have to be Okeyed before arriving at the point where connections between ports and material streams can be made. I stop the scenario here.

With COLTT v1.07 enabled on the GLCC UO, I get first the same error message as above and then I have a message box repeated quite a number of times “ActiveXtender Error setting cell color (SetFontCellColor).

With COLTT v1.08.02 (after changing the COLoggersST.dll file) I get, after accepting the UO, a debug assertion failed message and then Aspen Hysys crashes.

I have joined to this message the two log files obtained. I am surprised that the two logs do not show exactly the same sequence.

COLTT v1.07

Parameter Collection <Unnamed> : Call to Item requesting Item 1 Parameter Collection Item returns : 0x569a84 Parameter Collection <Unnamed> : Return from Item - No Error Parameter <Check> : Call to get_Specification

get_specification returns: 0x56e97c

Parameter <Check> : Return from get_Specification - No Error

COLTT v1.08.02 ParameterCollection <Anonymous> : Call to Item requesting Item 1 ParameterCollection Item returns : 0x5698ec ParameterCollection <Anonymous> : Return from Item - No Error Parameter <Anonymous> : Call to ICapeIdentification.get_ComponentName Parameter <Anonymous> : Return from ICapeIdentification.get_ComponentName - No Error Parameter <Check> : Call to get_Specification

get_specification returns: 0x56ccfc

Parameter <Check> : Return from get_Specification - No Error

I have logged this issue as 09-011 in the meantime.

Best regards

Michel

Reported by michelpons, 14 years ago.

De: Michel Pons [technologyofficer@…] Envoyé: Thursday, June 18, 2009 11:11 AM À: 'Ahsan Akhtar' Cc: 'michaeljhalloran@…' Objet: SimSci UO in PRO/II

Pièces jointes: MyScreenCopies.doc

Hi,

In the attached Word document I have documented a scenario that leads to a crash in PRO/II when either COLTT 1.07 or 1.08.02 is enabled on a UO. I think that the crash is related to the fact that the UO is 0.93 compliant. Could there be a way to avoid such a crash which does not look good?

I have listed this issue as 09-012.

Best regards

Michel