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

[TRNSYS-users] NBDM import - bug and fix

To: trnsys-users@cae.wisc.edu
Subject: [TRNSYS-users] NBDM import - bug and fix
From: pseudomino@gmx.com
Date: Wed, 01 Jun 2011 13:23:59 +0000
List-archive: <http://mailman.cae.wisc.edu/pipermail/trnsys-users>
List-help: <mailto:trnsys-users-request@cae.wisc.edu?subject=help>
List-id: "TRNSYS users mailing list at the Solar Energy Lab, UW-Madison" <trnsys-users.cae.wisc.edu>
List-post: <mailto:trnsys-users@cae.wisc.edu>
List-subscribe: <https://mailman.cae.wisc.edu/listinfo/trnsys-users>, <mailto:trnsys-users-request@cae.wisc.edu?subject=subscribe>
List-unsubscribe: <https://mailman.cae.wisc.edu/options/trnsys-users>, <mailto:trnsys-users-request@cae.wisc.edu?subject=unsubscribe>

Hi,

Maybe you already know that, but when importing a NBDM file beginning with "<?xml version="1.0" encoding="iso-8859-1" ?>"
TRNSYS (I use v. 17) is unable to import and crash.

A simple workaround is to remove this line (which is only used to a get a nice looking display of the tree structure of the file in a browser or text editor).

But maybe this should be fixed in a next TRNSYS release ?

Regards,

Damien

Follow-Ups:
- Re: [TRNSYS-users] NBDM import - bug and fix
  - From: "keilholz, werner" <werner.keilholz@cstb.fr>

Prev by Date: [TRNSYS-users] " forrtl.error.(63) output conversion error unit 6 file ....lst"
Next by Date: Re: [TRNSYS-users] obsolete input for Type551
Previous by thread: [TRNSYS-users] " forrtl.error.(63) output conversion error unit 6 file ....lst"
Next by thread: Re: [TRNSYS-users] NBDM import - bug and fix
Index(es):
- Date
- Thread