Today I noticed that, in Type56 all outputs after NType 961 will not be saved into the B17 file, and the values are also incorrect. In the Type56 manual:
| NTYPE 961 | B4_QSOLAIR | BAL 4: convective energy gain of zone due transmitted solar radiation through external windows which is transformed immediately into a con. heat flow to internal air | [kJ/hr] |
It is really strange. If I remove the NType 961 out of the outputs definition, the outputs list will work again.
see:
http://www.ibpsa.us/simbuild2012/Papers/SB12_TS04a_3_Delcroix.pdf
http://www.ibpsa.org/proceedings/BS2013/p_1192.pdf
PyBPS is a parametric simulation manager for building performance simulation projects. I hope it will be helpful in the development of Grasshopper plugin
https://github.com/dtavan/PyBPS
This error shows up at the first place when I give the insulation layer a big thickness.
I wrote an E-Mail to transsolar support, and the trick is the Timebase setting in Output of Type 56, which is mentioned in the manual page 5-24.
more was discussed in the paper and presentation of Benoit Delcroix etc.
https://www.mail-archive.com/trnsys-users@engr.wisc.edu/msg01821.html
There are a few known workarounds when Type56 is not able to calculate transfer functions. I believe they have been discussed in the past but here are the ones I know:
– Sometimes the problem occurs for highly insulated walls that are not particularly thick or heavy. In that case replacing some insulation layers with mass-less layers can do the trick. Usually the thermal mass of the insulation layer can be neglected so this is my preferred approach.
– Split the wall in two (or more) parts. You should split the wall as you describe (e.g. half of the thickness in each wall for a uniform wall) but then add a fictitious zone between the two parts of the wall. You basically use that fictitious zone as an infinitely small and infinitely conductive air layer. You should set a very small volume and infinite convection coefficients in the fictitious zone. I think it is best to handle windows separately from the wall if you adopt that approach (windows do not need to be part of a wall in Type56).
– Increase the time base. This is obviously not a great idea if you also have much lighter walls in the building, but if you are simulating a castle with 3-m thick walls all over I guess that would be acceptable.
In any case I would setup a test model with standard walls that are OK, apply the workaround (e.g. add the fictitious zone) and check that the results are the same. Then you can replace the walls with the one that causes the problem.
I hope this helps,
Michaël Kummert
ESRU, University of Strathclyde
TRNsIDF.EXE
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
*********************************************************** * TRNsIDF.EXE - translater from IDF created by Trnsys3d to B17 *********************************************************** This program sorts and renumbers the IDF file and writes a B17 file based on the geomtric information of the IDF file and the template B17 file. In addition, an template DCK file can be generated. CALL: TRNSIDF.EXE %1 %2 %3 %4 %5 %1 absolute path\filename.idf %2 absoluter path\NewFileTemplate.d17 %3 /dck create a template DCK %4 /nonum (optional: no renumeration of surfaces) %5 /N (optional: BatchJob Modus) Note: if no path is defined, the directory of TRNSIDF.EXE is assumed. |
the basic is desribed in TRNSYS 17 Manual Volumen 1 Getting Started in 1.8. Creating a new component. The problem is, the tutorial was created for a long time, something changed since the Visual Studio .NET 2003 is not availble. When Visual Studio 2003 was used, the TRNSYS Studio compiles the DLL file directly and save them to the UserLib folder. Now, without Visual Studio 2003, you get a notification, and get two file exported. One .cpp file(C++ source file) and one .dsp(project description for Visual Studio). If you have new generation Visual Studio installed, then open the .dsp file with it, then a new .vcxproj file will be created as project desription file for the new Visual Studio – I use Visual Studio Express 2012. Then build the DLL is quite easy. If TRNSYS.h is not found, copy it form “Trnsys17\Compilers\Cpp-Mvs2003\Include”.
actually I wanna do it with MingW and Code::Blocks, somehow I cannot get it working, I will try later. The .dsp file has some configurations for the compiler and Code::Blocks cannot read it properly, I think. If someone knows how it works, please let me know.
|
1 2 3 4 5 6 7 |
The following three TYPE 56 standard files are generated automatically every time the BUI file is saved: <ul> <li>a file containing all information about the building excluding the wall construction (*.BLD) and</li> <li>another file that contains the ASHRAE transfer functions for the walls (*.TRN).</li> <li>In addition, an information file (*.INF) is generated as log file which needs to be checked for error messages. The information file contains the processed BUI file followed by the values of wall transfer function coefficients, the overall heat transfer conductance U and the related Uvalue. This information may be useful for the user in verifying the wall description data. Next, the list of inputs required for the Type 56 is printed. These will most commonly be outputs of other components in the TRNSYS simulation. Also, the information file (*.INF) provides a list of outputs of Type 56 as selected by the user. These outputs may be inputs to other components. Finally, a brief table with all of the wall types and their U-values is printed to the information file.</li> </ul> The *.BLD and *.TRN files are used by TYPE 56 during the simulation process. The generated files get the name as the opened *.BUI file and are located in the same directory. If an error occurs, no files are generated. A window displays for detailed information on the error. |
It looks like if I want to use the Heat Tansfer Coefficient based on the results from OpenFoam, I need modify the .inf file somehow. The Heat Transfer Coefficient depends on the Wall Surface Temperatue and the Air Temperature close to the wall. Usually, the convective heat transfer coefficient of wall is set per wall type either as userdefined or as internal calculation. During the internal calculation, the AirNode temperature is used, which will be replaced by OpenFoam in the Coupling. So, I think we should choose it as userdefined. Under userdefined dialog, we can see 3 options: Constant Value, Input, Schedule. Input should be the right choice, which means the convective heat transfer coefficient of each wall are defined as input for Type56. We can calculate them and save data in an external file. Because of the variation of the Air Temperature in CFD, the Heat Transfer Coefficient could also be variable. That means, for each surface of the geometry, a wall type should be defined according to the air temperature. 
|
1 2 3 |
from 05-MultizoneBuilding.pdf page 5-121 Type 56 also offers the possibility to define a certain energy flux to a certain wall surface. |
I searched whole day without success, the workflow is to use the heat flux value from OpenFoam for surface energy balance calculation instead of the process of internal calculation with airnode temperature. If Fluent is used, maybe Type 101 is just right for this, but OpenFoam is the tool available to me. I must find another solution to make this happen. I don’t really understand the setting of Wall Gain , is this just means Convective Heat Flux?
