Reverse import of the EXCEL file exported from ASPEN into the ASPEN reduction model
Thread Content
This post was last edited by Urban Wildman on 2011-8-20 at 20:17. I am using the ACOL module in ASPEN ONE V7.1 EDR; I conducted a simulation calculation for an air cooler, and after the calculation was completed, I exported all the results to an Excel file. This Excel file can be synchronized with the data in ASPEN ACOL (changes made in ASPEN can be updated in the Excel file, but I haven’t tried updating it in the reverse direction, so I’m not sure if that will work). Since it is used both at home and in the office, with files being copied back and forth, the ASPEN model files were lost. Is it possible to reverse-import the data from the saved EXCEL files into ASPEN in order to restore the original calculation model? I first open ASPEN EDR and create an empty ACOL model, then open the previously saved EXCEL file mentioned earlier; it prompts me that the model in the EXCEL file is different from the new model and asks whether to update it ； If I agree to update, the original data in EXCEL is replaced by the empty ACOL model data. This gives me a glimmer of hope for restoring the calculation model; please ask the experts for help.
So far, reverse engineering has not been successful; attempting to create files with the same name using ACOL also did not lead to a successful reverse update. The only option is to re-enter the data manually based on the values in the Excel sheet. However, it turns out that the effective average temperature difference always differs from the previously calculated values. I’m not sure which other parameters may not be set identically to those originally used (there are too many input parameters :( )
Isn’t ACOL used here?
Why doesn’t version 7.2 have EDR? I want the Aspen and HTRI interfaces; it’s really troublesome not to have a database in HTRI
I think the feature that comes closest to what you’re describing is the Aspen Simulation Workbook; it allows for data exchange between Excel and Aspen files, enabling the background Aspen model to be invoked for calculations as soon as the data in Excel is modified, with the results then being returned to Excel. Now the model file is missing, and that’s really tricky
It’s not possible to export it back from Excel; since the original file is gone, it has to be recreated.