[TRNSYS-users] TRNSYS3D error

[Yuichi Yasuda]

I have copied the email correspondence related to this question to the 
TRNSYS USERS FORUM.

https://trnsys.org/community/modeling-buildings-in-trnsys-trnsys3d-trnbuild-type-56/trnsys-3d-error/#post-28

Yuichi

On 2023/04/06 14:51, Yuichi Yasuda via TRNSYS-users wrote:
> All surfaces are given names.
> When a surface is created in TRNSYS3D, it is automatically given an 
> alphanumeric name, for example A0737D.
>
> In contrast, TRNBuild identifies all surfaces by number. Therefore, 
> when the IDF is imported into TRNBuild, it is assigned a surface 
> number instead of the name.
>
> Thereafter, when exporting from TRNBuild to an IDF, the surface number 
> will be used as the name.
>
> In your case, it seems that TRNBuild did not export the surface (210) 
> to the IDF correctly.
> Or the surface may be so small that it is not visible.
>
> If you are having difficulty finding the surface, I recommend that you 
> delete and recreate the zone to which the surface belongs.
>
> Yuichi
>
>
> On 2023/04/05 12:55, H via TRNSYS-users wrote:
>>
>> Dear Yuichi and all
>>
>> Thanks for your reply. Howerver, it still cannot find the surface 210 
>> as shown in the following picture. I think the reason is the area of 
>> the 210 surface is 0 as  shown in the following picture. What is the 
>> rule of surface numbers  by TRNBuild to the IDF file? This can help 
>> me find the wrong surface(210). The error occured because the area of 
>> the 210 surface is 0.
>>
>>
>>
>>
>> At 2023-04-05 08:37:09, "Yuichi Yasuda via TRNSYS-users" 
>> <trnsys-users at lists.onebuilding.org> wrote:
>>
>>     Surface numbers are assigned by TRNBuild.
>>     In other words, you cannot find the surface by the number because
>>     it does not exist in TRNSYS3D.
>>
>>     Try the following steps.
>>
>>     1. First of all, export the IDF file from TRNBuild. This will
>>     export the surface numbers assigned by TRNBuild to the IDF file.
>>     2. Then open the IDF file in TRNSYS3D.
>>     3. In the Surface Search dialog, enter the Surface number in the
>>     Name field. In your case, enter 210.
>>     4. Click on the Search Entire Model button.
>>
>>     Now only the surface will be shown.
>>
>>     I hope this works.
>>
>>     Yuichi
>>
>>     On 2023/04/03 15:54, H via TRNSYS-users wrote:
>>>
>>>     Hello, everyone,
>>>
>>>      There is an error when I export the model of TRNSYS3D to the
>>>     TRNSYS , as shown in following picture. How can I find the 210
>>>     surface in sketchup? How can I solve this problem?
>>>
>>>     Best regards,
>>>
>>>
>>>
>>>     _______________________________________________
>>>     TRNSYS-users mailing list
>>>     TRNSYS-users at lists.onebuilding.org
>>>     http://lists.onebuilding.org/listinfo.cgi/trnsys-users-onebuilding.org
>>     -- 
>>
>>
>>
>> _______________________________________________
>> TRNSYS-users mailing list
>> TRNSYS-users at lists.onebuilding.org
>> http://lists.onebuilding.org/listinfo.cgi/trnsys-users-onebuilding.org
> -- 
>
> 安田　雄市 Yuichi Yasuda
> 株式会社クアトロ quattro corporate design co.,ltd
> http://qcd.co.jp/
> Tel：070-8407-3774（直通）
> Tel: 03-5768-6744（代表） Fax:03-5768-6745
> mail: yasuda at qcd.co.jp
>
>
> _______________________________________________
> TRNSYS-users mailing list
> TRNSYS-users at lists.onebuilding.org
> http://lists.onebuilding.org/listinfo.cgi/trnsys-users-onebuilding.org
-- 

安田　雄市 Yuichi Yasuda
株式会社クアトロ quattro corporate design co.,ltd
http://qcd.co.jp/
Tel：070-8407-3774（直通）
Tel: 03-5768-6744（代表） Fax:03-5768-6745
mail: yasuda at qcd.co.jp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20230413/215aff94/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2023-04-05_114212.png
Type: image/png
Size: 92511 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20230413/215aff94/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 71eb9cd58e6d34c1f051d9ef8253c93b_s_func=mbox:getComposeData
Type: image/png
Size: 3272 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20230413/215aff94/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: e20a67172ce0cdaed4d2c37c3a120d1d_s_func=mbox:getComposeData
Type: image/png
Size: 63603 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20230413/215aff94/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Re0EMsqOasE0hwGH.png
Type: image/png
Size: 372998 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20230413/215aff94/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 35b4b0976700fb68f3f5444c2cbcd9b.png
Type: image/png
Size: 3272 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20230413/215aff94/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6141b5282c944830a23957fe5458e4f.png
Type: image/png
Size: 63603 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20230413/215aff94/attachment-0011.png>