Custom Query (122 matches)
Results (28 - 30 of 122)
Ticket |
---|
#42 |
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? |
#43 |
Description |
I am using a UO built by IFP within COFE 1.15. The UO is a 3-phase separator. When the UO is not logged, the calculation goes to its end but COFE displays warnings about properties not set. So I enabled COLTT on the UO and reran the case. With COLTT enabled on the UO, I can drop the UO in the flowsheet, I can connect the inlet port and the three outlet ports to streams, but COFE aborts when I double-click on the icon representing the UO. The Edit method of the UO is not implemented and normally the generic UO interface from COFE should have appeared so that I may give values to the UO parameters. The attached COLTT log shows that the logging stops in get_Reports. I attach also the COFE document from where I start. The installer for the UO is too large to be attached and will be delivered through a file server. |
#46 |
Description |
I am using the GLCC UO in PRO/II 8.3 Patch 1. It relates to a case raised with SimSci-Esscor Support. I have a scenario that calls fro dropping the GLCC UO on the PRO/II flowsheet, to connect inlet and outlet ports, to edit the UO in order to choose the location for its output file, then to calculate the process model made of this UO. Examining the log made with COLTT, I see that get_Values calls on the integer parameters of the UO are at first looking good. Then, after the Edit call, the get_Values calls for integer parameters return a message \"An Invalid Argument\". What is not clear is who is sending this message and then what it means exactly. The only argument of such a call is the returned value. There is no error raised and no means for the call to pass a message. So my educated guess is that COLTT is posting the message but on what grounds. Plus, if it is indeed COLTT which is posting the message, it should be made obvious. Here, as it is posted, one may think that get_Value returns this message. Would it be possible to get more info on what is going on? |