Custom Query (122 matches)
Results (40 - 42 of 122)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#42 | fixed | Change of error message when UO logged | Michael Halloran | michelpons |
Description |
I am using a UO made at University of Trieste (Trieste HX). The source/installation is provided as attachment. A number of tests had been made with this UO in the past in ProSimPlus, PRO/II or UniSim Design. I think I have a problem getting the UO properly registered. The RegUnit.bat does not work or rather it is RegUnitAsm.exe that seems to fail (folder bin). However, I double-clicked on the RegistrationInfo.reg file and the registry was updated. The HeatExchanger UO appears in COLTT Controller as well as in the list of UOs available to the PME, here ProSimPlus. When the UO is not logged, when trying to instantiate the UO in ProSimPlus I get the following error message: ProSimPlus - Sans nom.pmp3 Le module spécifié est introuvable. OK I would translate that as \"the specified module can't be found\". Now, when I enable COLTT on the HeatExchanger UO, I get as error message for the same step: ProSimPlus - Sans nom.pmp3 Access violation at address 774D1404 in module 'ole32.dll'. Read of address 00000000. OK while the log file contains:
ClassFactory : Loading HeatExchanger implemented by mscoree.dll ClassFactory : Failed to load mscoree.dll For sure, the UO is not properly installed. However is it right to have a different error message with COLTT enabled on the UO and with the UO on its own? |
|||
#150 | fixed | Check if names of duplicated MOs are retrieved | Michael Halloran | michelpons |
Description |
I am opening up in Aspen Plus v7.3.2 a case file that makes use of Aspen Plus embedded thermo and of the VB6 Mixer Splitter example used as a splitter. I run the case and analyze the log file obtained with COLTT 2.1 Build 246. Within the Calculate call, there is a call to Duplicate the MO named as 1: MaterialObject <1> : Call to Duplicate MaterialObject Duplicate returns clone: 013A43B0 MaterialObject <1> : Return from Duplicate - Succeeded Once this is done I presume that most subsequent CalcProp and CalcEquilibrium calls are made on the duplicated MO. However the following is logged: MaterialObject <1> : Call to CalcProp requesting:
MaterialObject <1> : Return from CalcProp - Succeeded I wonder if COLTT has really updated the name of the MO, or if the duplicated MO has the same component_Name as the original MO. I can't see any call to get_componentName on the ICapeIdentification interface carried by the duplicated MO. Would be necessary to know what is going on. If the duplicated MO is given the same name as the original MO by the PME, it may induce some recommendation to developers to avoid that situation. |
|||
#26 | fixed | Copyright notice | ahsanakhtar | michelpons |
Description |
In the \"About\" window of COLTT controller, the copyright mentions 2005-2008 while it should be 2005-2009. I don't know how much it matters though. The same copyright appears in the \"Components\" view of COLTT controller and should be also updated(i.e. 2008 to 2009). |