Thread Content
WARNING WHILE GENERATING RESULTS FOR UNIT OPERATIONS BLOCK: “B26” (MODEL: “HEATX”) The calculated feed temperature for the hot side (4.4648428D+02) is inconsistent with its inlet stream value (4.4387647D+02). Probable cause: loose flash tolerance, or an upstream block with different phase specifications or property methods. The calculated value will be used in calculations. How can this issue be resolved?
This error is caused by a mismatch between the feed temperature on the hot side and the value of its input stream in the HeatX module. The steps to solve this problem are as follows: 1. Check the parameter settings in the heat pump system, especially those related to the flashing process. It may be due to an overly tight error tolerance setting during the flashing process. You can try increasing the error tolerance to see if that can solve the problem. 2. Check the parameter settings of other unit operation blocks in the system to ensure they are consistent with those in the HeatX module. If other unit operation blocks use different phase state specifications or property methods, it may lead to inconsistencies between the hot-side feed temperature and the values of the input streams. Try to standardize the parameter settings for all relevant unit operation blocks. 3. Check the data in the input stream to ensure its accuracy. The inconsistency may be caused by an incorrect temperature value in the input stream. You can carefully check the attribute data of the input stream to ensure it is consistent with the hot-side feed temperature. 4. If the above methods do not solve the problem, it is recommended that you contact experts or developers in the relevant field for assistance and technical support. They may be able to analyze the problem more specifically and provide solutions. .
Thank you for your reply. However, this is a cyclic structure; in other words, the heat flux values that are inputted are calculated by Aspen itself. The material properties should be fine – it’s probably a matter of tolerances. How can this be fixed?
If your heat flux values are calculated by Aspen itself and involve a flashing process, then you can try adjusting the relevant tolerance settings to resolve the issue. Here are some possible solutions: 1 Check the parameter settings for the flashing process in the HeatX module, especially those related to the flashing tolerance. You can try increasing the value of the flashing tolerance, for example by expanding the tolerance range for the flashing temperature or pressure, so that the system can tolerate greater errors. 2 Check the other unit operation blocks involved in the flashing process within the iterative structure, to ensure that their flashing tolerance settings are consistent with those of the HeatX module. If other unit operation blocks use different flash tolerance settings, it may lead to inconsistencies in the heat flow rates. Standardize the flash tolerance settings for all relevant unit operation blocks. 3 If the above methods do not solve the problem, you can try to re-establish the loop structure to ensure consistency in data transfer and flashing processes between various unit operation blocks. 4 If the problem persists, it is recommended that you contact Aspen Plus’ technical support team, as they will be able to provide more specific assistance and solutions. They can help you identify the root causes of problems and provide corresponding solutions by analyzing your models and data. .
The flow stocks don’t have initial values assigned; calculations are first performed until the values of the two flow stocks are equal, after which they are combined. V14 now supports loop modules :)
Thank you for your reply; after changing the valid phase state in the previous module, there will be no issues thereafter :)