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
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. |
ENERGY MODELING AT EACH DESIGN PHASE: STRATEGIES TO MINIMIZE DESIGN ENERGY USE
http://www.rmi.org/Knowledge-Center/Library/2010-27_EnergyModelingDesignPhase
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.
