Custom Query (122 matches)
Results (16 - 18 of 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #55 | fixed | PPM not queried on error returned | michaelhalloran | michelpons |
| Description |
The scenario is based on the one described for ticket #34 and is obtained when there is no PPDS license available. There is a complete process model developed in Aspen Hysys and making use of PPDS. Because the license is not there the PPM returns an error code 0x80040501 and this is logged in the log file. Aspen Hysys does not seem to pursue any further the matter. However I don't see any attempt from COLTT to query the error handling interfaces that should be present on the PPM object. I wonder why. |
|||
| #58 | fixed | Handling of long list of methods in Viewer | michaelhalloran | michelpons |
| Description |
In the attached log file, both a UO and a PPM are logged. The list of methods in the method list is very long and goes further down than the screen in which it is displayed, resulting in some methods not being reached for filtering/defiltering. Could the list be displayed in multiple columns or maybe in multiple pages, ten or fifteen methods per page and a page numbering permitting to go from one page of method list to another. |
|||
| #59 | worksforme | OATS in Aspen Plus | michaelhalloran | michelpons |
| Description |
Without COLTT enabled on OATS Thermo System, a Property Package logged through OATS can't be imported in Aspen Plus: the Property Package is not listed as available. With COLTT enabled on OATS Thermo System, the Property Package under OATS appears as importable in Aspen Plus and a simple scenario involving this PP can be played in Aspen Plus. OATS is at 2.1.0.2, Aspen Plus is at 7.1 and COLTT is Aug 1, 2010 build. Attached are the log files obtained from COLTT and OATS. Enabling COLTT on OATS should not change OATS behaviour. At the same time this scenario shows that out of proc applications may now be logged with COLTT. |
|||