[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TRNSYS-users] Error with glazing data from Window



Dear Antoine,

 

yes, you are right. The problem is the really high Tvis/Tsol ratio.

Unfortunately, it doesn’t print the correct error message. The strange error message results from a wrong format used
for writing an error message.

 

This problem is fixed in Trnsys 18 by using new standard files for LBNL window program (see section 4.1.3. Glazing library of http://www.trnsys.de/download/en/T18Updates.pdf).

 

If you like to use this high selective glazing I suggest to update to Trnsys 18.

 

Best regards,

 

Marion

 

-----------------------------------------------------------------------------------------------------------------------------------------------------------

Dipl.-Ing. Marion Hiller 
TRANSSOLAR Energietechnik GmbH 
Stuttgart - Munich - New York - Paris  

t: +49.711.67976.0   f: +49.711.67976.11

www.transsolar.com/   

KlimaEngineering - Technologien für energieeffizientes Bauen und Nutzerkomfort in Gebäuden 
Transsolar Energietechnik GmbH, Curiestrasse 2, 70563 Stuttgart

Amtsgericht Stuttgart - HRB 23347 / Steuernummer: 99073/00911 / USt-IdNr.: DE 152272639
Geschäftsführer: Matthias Schuler, Thomas Auer, Stefan Holst, Dieter Schnelle 

 

 

Von: TRNSYS-users [mailto:trnsys-users-bounces@lists.onebuilding.org] Im Auftrag von Antoine Gautier via TRNSYS-users
Gesendet: Mittwoch, 30. August 2017 18:28
An: 'TRNSYS users mailing list at OneBuilding.org' <trnsys-users@lists.onebuilding.org>
Betreff: [TRNSYS-users] Error with glazing data from Window

 

Dear users

 

I get the error message in attachment when I try to simulate a single pane glazing system with Type56 from a Window 7.5 export.

The DOE-2 file report that I use in b17 is also attached.

I have tried with other kinds of single pane glazing with no problem.

It seems as if the kind of glass leading to the error has a high Tvis/Tsol ratio cf. area in purple in the extract of IGDB plotted in the HTML file.

What is this issue about? Is there a workaround?

 

Best regards

--

Antoine Gautier

Solamen

+33 6 58 24 02 60

antoine.gautier@solamen.fr