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

Reported by michelpons, 14 years ago.

Size of the MSI file for COLTT 1.08.3 (Build Oct 27, 2009) is 22,178 Kbytes while it was only 4,646 Kbytes for the MSI of COLTT 1.07. Refactoring was not supposed to give way to such an increase in code size. So why such an increase?

Reported by michelpons, 14 years ago.

I used COLTT 1.08.3 Build Oct 27, 2009 on a combination of PMC-PME that was used to document a defect in 2008 where it was impossible to get a log with COLTT 1.06. Logging is now possible with COLTT latest version.

The calculation does not run properly in PRO/II. This may be related to the fact that it is PRO/II 8.2 that is used here. I get an error message from PRO/II saying:

2 error(s), 0 warning(s), and 0 message(s) detected:

* error * Unit 1, 'co1' - the cape-open data file 'c:
docume~1
michel~1
locals~1
temp
ssi82
unconnected_co1.Dat' was not found. * error * Unit 1, 'co1' - not all material ports are connected.

The COLTT log file (proii_103109_232827.log) is showing that disconnect calls on ports are raising exceptions:

Port <Outlet> : Return from get_portType - Succeeded Port <Inlet 1> : Call to Disconnect Port <Inlet 1> : Error returned from Disconnect - 0x80040501 Port <Inlet 2> : Call to Disconnect Port <Inlet 2> : Error returned from Disconnect - 0x80040501 Port <Outlet> : Call to Disconnect Port <Outlet> : Error returned from Disconnect - 0x80040501

PRO/II seems to choose not to investigate further the exception since no attempt seems to be made to get information on the error. However I am puzzled by the fact that COLTT does not try either. I thought that, whatever the PME behaviour regarding error handling, COLTT logger was supposed to call ECapeUser and so on in order to get at least a better description of the error. It does not seem to happen there so the log is not sufficiently informative.