I used to create the MDF database manually in Visual Studio, now I want to try create the database programmatically inside the program.
The first useful article I found was from microsoft, but without success. There were 2 issues here:
1. the server name – in the example, they use “server = localhost”, it should be changed to “server = .\\SQLEXPRESS”
2. “create file encountered operating system error 5(access is denied.)” – the possible solution may be this
more info: http://msdn.microsoft.com/en-us/library/ms254504(v=vs.110).aspx
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.
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,
ESRU, University of Strathclyde