[TRNSYS-users] Undefined adjacent wall error

[hotline via TRNSYS-users]

Dear Issmail,

My guess would be that you tried to define adjacent surfaces.
This is only possible if two surfaces that are being matched have the same area and exactly the same coordinates.

Please let me know, if this was not helpful to you and send me your .idf file then…

Best
Jakob

_________________________________________________________________________________________________

Jakob Merk
TRNSYS Software Team

Transsolar Energietechnik GmbH
Curiestraße 2
70563 Stuttgart
Fax:        +49 711 67976-11
Email:    hotline at transsolar.com<mailto:hotline at transsolar.com>
Web:      www.trnsys.de<http://www.trnsys.de/>



Von: TRNSYS-users [mailto:trnsys-users-bounces at lists.onebuilding.org] Im Auftrag von Issmail OUHALLOU via TRNSYS-users
Gesendet: 22 February 2017 11:18
An: Jeremy Osborne via TRNSYS-users <trnsys-users at lists.onebuilding.org>
Betreff: [TRNSYS-users] Undefined adjacent wall error

Dear users,

When I import my IDF file into TRNBuild (Trnsys17/Trnsys3d), I got some errors, such as undefined adjacent wall, that I cannot fix later. The problem is when I check the 3D-model everething is OK! Otherwise, I cannot find the undefined wall.

First, how to find out the right surface/wall in question? Second, in 3D-model where exactly to read the declared surface number in error message (Surf-No)?

[cid:image002.png at 01D28CFE.2F716C70]

Can anyone help please?
Thanks in advance.

Best regards,
Ismail.

​



[https://mailtrack.io/trace/mail/e7ed17aa908e9242ad6866e0b8b5d77506aa08ad.png?u=633613]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20170222/8a5c0a4e/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 55387 bytes
Desc: image002.png
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20170222/8a5c0a4e/attachment-0003.png>