<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									TRNSYS Forum - Recent Topics				            </title>
            <link>https://trnsys.org/community/</link>
            <description>TRNSYS Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Mon, 09 Nov 2026 02:11:07 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>ground reflected radiation with type 67</title>
                        <link>https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/ground-reflected-radiation-with-type-67/</link>
                        <pubDate>Fri, 23 Oct 2026 17:55:31 +0000</pubDate>
                        <description><![CDATA[Hello 
I am wandering how to treat ground radiation with type 67. In the example given, the type 71 does not use ground radiation but if I use type 1346, should I estimate the total radiati...]]></description>
                        <content:encoded><![CDATA[<p>Hello </p>
<p>I am wandering how to treat ground radiation with type 67. In the example given, the type 71 does not use ground radiation but if I use type 1346, should I estimate the total radiation as : </p>
<p>I_total_shaded = I_beam_shaded + I_sky_diff_shaded  + I_ground_not_shaded </p>
<p>and connect I_beam_shaded to input beam radiation of the collector, I_sky_diff_shaded to input sky diff radiation and I_ground_not_shaded to input  ground radiation or is it better to: </p>
<p>- connect the total diffuse radiation ( sky+ground) to input diffuse radiation of type 67 and connect I_diff_shade to sky diff radiation of the collector and put 0 as input ground radiation of the collector ? </p>
<p>&nbsp;</p>
<p>Thanck you very much </p>
<p>Louis </p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>louis.lamarche@etsmtl.ca</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/ground-reflected-radiation-with-type-67/</guid>
                    </item>
				                    <item>
                        <title>New Release: ExtAMeDAS Plugin v1.0.0</title>
                        <link>https://trnsys.org/community/announce_forum/new-release-extamedas-plugin-v1-0-0/</link>
                        <pubDate>Tue, 20 Oct 2026 05:39:31 +0000</pubDate>
                        <description><![CDATA[Hello everyone,
I would like to announce the release of the ExtAMeDAS Plugin v1.0.0 for the TRNSYS Type99-AMeDAS component. The plugin lets you select a station of the Expanded AMeDAS Weath...]]></description>
                        <content:encoded><![CDATA[<p>Hello everyone,</p>
<p>I would like to announce the release of the ExtAMeDAS Plugin v1.0.0 for the TRNSYS Type99-AMeDAS component. The plugin lets you select a station of the Expanded AMeDAS Weather Data (EA weather data, Japan) on a map, and creates a weather data file (.99) that Type99 can read.</p>
<p>Until now, this plugin was provided only to a limited group of users. For this release, its features and user interface have been reviewed, and it is now publicly available.</p>
<p><b>Key updates in this release:</b></p>
<ul>
<li>
<p><b>.wea2 format support:</b> The plugin now supports the .wea2 format of the EA weather data, including the 2020 standard year and the 2086 future edition. The 1995, 2000 and 2010 editions can be used in either .wea or .wea2.</p>
</li>
<li>
<p><b>Standalone execution:</b> The plugin has been rebuilt with a Windows 11-style user interface. It no longer requires a .NET Runtime installation, and it starts faster.</p>
</li>
<li>
<p><b>Map and station search:</b> The map now uses GSI Tiles (Geospatial Information Authority of Japan). You can search for stations by English name, Japanese name, kana reading or station number.</p>
</li>
<li>
<p><b>Charts and heating period:</b> The annual data, passive climatic chart and daily average charts have been rebuilt. The heating period (daily mean temperature of 15 °C or lower) is shaded, and the legend shows its simulation hours. Chart images can be saved as PNG or SVG.</p>
</li>
<li>
<p><b>Two-year .99 option:</b> With a time step shorter than 1 hour, Type99 can stop at hour 8,760 when a simulation goes past the end of the year. Selecting 2 years in Preferences avoids this.</p>
</li>
<li>
<p><b>English user interface:</b> The plugin, the manual and the installer are shown in English on Windows with a non-Japanese display language.</p>
</li>
</ul>
<p><b>Note on the weather data:</b> The EA weather data is not included in the plugin. Please purchase it separately. The station information file on the EA media must be placed in the same folder as the standard year file.</p>
<p>You can find the download link and the full release notes on the GitHub repository here: <a href="https://github.com/TRNSYSJP/ExtAMeDAS/releases" target="_blank" rel="nofollow noopener">TRNSYSJP/ExtAMeDAS Releases</a></p>
<p>For more details, you can also check out our blog post about this release: <a href="https://www.kankyoukei.com/2026/10/trnsys-type99-amedas-plugin-release.html" target="_blank" rel="nofollow noopener">ExtAMeDAS Plugin Release</a></p>
<p>Best regards,</p>
<h3>日本語版</h3>
<p>拡張アメダス気象データ プラグイン（ExtAMeDAS）v1.0.0　公開のお知らせ</p>
<p>TRNSYSユーザーの皆様</p>
<p>TRNSYS の Type99-AMeDAS コンポーネント向けプラグイン「ExtAMeDAS v1.0.0」を公開いたしましたのでお知らせします。拡張アメダス気象データ（拡張AMeDAS、EA気象データ）の地点を地図で選び、Type99 で読める気象データ（.99）を作るプラグインです。</p>
<p>これまでは一部の方に限定して公開していましたが、機能と画面（UI）を見直して公開することにしました。</p>
<p><b>主なアップデート内容:</b></p>
<ul>
<li>
<p><b>.wea2 形式に対応:</b> 拡張アメダスの .wea2 形式に対応し、2020年版標準年と 2086年将来版を追加しました。1995年版・2000年版・2010年版は、.wea と .wea2 のどちらでもご利用いただけます。</p>
</li>
<li>
<p><b>.NET環境が不要に:</b> Windows 11 風の画面で作り直しました。.NET ランタイムの事前インストールは不要で、起動も速くなりました。</p>
</li>
<li>
<p><b>地図と地点の検索:</b> 地図を国土地理院の地理院タイルに変更しました。地点名・ヨミガナ・英語表記・地点番号で地点を検索できます。</p>
</li>
<li>
<p><b>チャートと暖房期間:</b> 年間データ、パッシブ気候図、日平均年間データのチャートを作り直しました。暖房期間（日平均気温が 15 ℃以下の期間）を背景に塗り、凡例にシミュレーションの時刻を表示します。チャートの画像は PNG・SVG で保存できます。</p>
</li>
<li>
<p><b>2 年分の .99:</b> タイムステップが 1 時間より短く、年をまたいで計算すると、Type99 が 8,760 時で止まることがあります。基本設定で 2 年分を選ぶと避けられます。</p>
</li>
<li>
<p><b>英語の画面:</b> Windows の表示言語が日本語以外の場合は、プラグイン・マニュアル・インストーラーを英語で表示します。</p>
</li>
</ul>
<p><b>気象データに関する注意:</b> 拡張アメダス気象データはプラグインに含まれていません。別途ご購入ください。媒体にある地点情報のファイルは、標準年のファイルと同じフォルダに置いてください。</p>
<p>詳細なリリースノートおよびダウンロードにつきましては、以下のGitHubリポジトリをご確認ください。 <a href="https://github.com/TRNSYSJP/ExtAMeDAS/releases" target="_blank" rel="nofollow noopener">TRNSYSJP/ExtAMeDAS のリリースページ</a></p>
<p>また、本リリースに関する概要は以下のブログ記事でも紹介しています。あわせてご覧ください。 <a href="https://www.kankyoukei.com/2026/10/trnsys-type99-amedas-plugin-release.html" target="_blank" rel="nofollow noopener">TRNSYS拡張アメダスPlugin 1.0.0を公開しました</a></p>
<p>よろしくお願いいたします。</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>YuichiYasuda</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/announce_forum/new-release-extamedas-plugin-v1-0-0/</guid>
                    </item>
				                    <item>
                        <title>New Release: Weather Data Map Plugin v1.0.0</title>
                        <link>https://trnsys.org/community/announce_forum/new-release-weather-data-map-plugin-v1-0-0/</link>
                        <pubDate>Mon, 19 Oct 2026 07:30:19 +0000</pubDate>
                        <description><![CDATA[Hello everyone,
I would like to announce the release of the Weather Data Map Plugin v1.0.0 for TRNSYS weather data readers (Type15-x, Type99).
This version has been completely rebuilt from...]]></description>
                        <content:encoded><![CDATA[<p data-path-to-node="4">Hello everyone,</p>
<p data-path-to-node="5">I would like to announce the release of the Weather Data Map Plugin v1.0.0 for TRNSYS weather data readers (Type15-x, Type99).</p>
<p data-path-to-node="6">This version has been completely rebuilt from scratch. It features a modernized Windows 11-style user interface and introduces several functional improvements to make selecting weather data easier.</p>
<p data-path-to-node="7"><b data-path-to-node="7" data-index-in-node="0">Key updates in this release:</b></p>
<ul data-path-to-node="8">
<li>
<p data-path-to-node="8,0,0"><b data-path-to-node="8,0,0" data-index-in-node="0">Standalone execution:</b> The plugin no longer requires .NET Runtime or Framework installations. It works simply by running the installer.</p>
</li>
<li>
<p data-path-to-node="8,1,0"><b data-path-to-node="8,1,0" data-index-in-node="0">Location search &amp; auto-focus:</b> You can now search for locations by name, state, country code, or file name. The map will also automatically center on your currently selected location upon launch.</p>
</li>
<li>
<p data-path-to-node="8,2,0"><b data-path-to-node="8,2,0" data-index-in-node="0">UI and map improvements:</b> A toggleable minimap and a new button to easily copy location details have been added. You can also customize your weather data folders via the new Preferences menu.</p>
</li>
<li>
<p data-path-to-node="8,3,0"><b data-path-to-node="8,3,0" data-index-in-node="0">Comma decimal support:</b> Fixed an issue to correctly read latitude and longitude on Windows systems using a comma as a decimal separator (e.g., German Windows).</p>
</li>
</ul>
<p data-path-to-node="9"><b data-path-to-node="9" data-index-in-node="0">Note on component location:</b> Please note that the plugin components have been moved to <i data-path-to-node="9" data-index-in-node="86">Quattro -&gt; Weather Data Reading and Processing</i> in the Simulation Studio Direct Access Toolbar. The installer will automatically clean up the old components.</p>
<p data-path-to-node="10">You can find the download link and the full release notes on the GitHub repository here: <a class="ng-star-inserted" href="https://github.com/TRNSYSJP/WeatherDataMap/releases" target="_blank" rel="noopener" data-hveid="0" data-ved="0CAAQ_4QMahgKEwj96cKWxMWXAxUAAAAAHQAAAAAQogE">TRNSYSJP/WeatherDataMap Releases</a></p>
<p data-path-to-node="11">For more details, you can also check out our blog post about this release: <a class="ng-star-inserted" href="https://www.kankyoukei.com/2026/10/weather-data-map-plugin-release.html" target="_blank" rel="noopener" data-hveid="0" data-ved="0CAAQ_4QMahgKEwj96cKWxMWXAxUAAAAAHQAAAAAQywE">Weather Data Map Plugin Release</a></p>
<p data-path-to-node="11">Best regards,</p>
<h3 data-path-to-node="13">日本語版</h3>
<p data-path-to-node="14">Weather Data Map Plugin v1.0.0　リリースのお知らせ</p>
<p data-path-to-node="15">TRNSYSユーザーの皆様</p>
<p data-path-to-node="16">気象データリーダー（Type15-x、Type99）向けプラグイン「Weather Data Map Plugin v1.0.0」をリリースいたしましたのでお知らせします。</p>
<p data-path-to-node="17">本バージョンではプログラムを一から再構築しており、Windows 11風の新しいUIの採用や、気象データ選択をよりスムーズに行うための機能追加を含むメジャーアップデートとなっています。</p>
<p data-path-to-node="18"><b data-path-to-node="18" data-index-in-node="0">主なアップデート内容:</b></p>
<ul data-path-to-node="19">
<li>
<p data-path-to-node="19,0,0"><b data-path-to-node="19,0,0" data-index-in-node="0">.NET環境が不要に:</b> プログラムがスタンドアロン化されました。.NET等の事前インストールは不要で、インストーラーを実行するだけでご利用いただけます。</p>
</li>
<li>
<p data-path-to-node="19,1,0"><b data-path-to-node="19,1,0" data-index-in-node="0">地点検索と自動フォーカス:</b> 地点名、州、国コード、ファイル名での検索機能を追加しました。また、起動時には選択中の地点が自動でマップの中央に表示されます。</p>
</li>
<li>
<p data-path-to-node="19,2,0"><b data-path-to-node="19,2,0" data-index-in-node="0">UIとマップ操作の改善:</b> ミニマップ機能や、地点情報を一括でコピーできるボタンを追加しました。また、基本設定（Preferences）から各気象データフォルダの参照先をカスタマイズできるようになっています。</p>
</li>
<li>
<p data-path-to-node="19,3,0"><b data-path-to-node="19,3,0" data-index-in-node="0">小数点（カンマ）への対応:</b> ドイツ語版Windowsなど、小数点の区切りにカンマを使用する環境でも緯度・経度が正しく読み取れるように修正しました。</p>
</li>
</ul>
<p data-path-to-node="20"><b data-path-to-node="20" data-index-in-node="0">コンポーネントの配置場所に関する注意:</b> Simulation Studio上のコンポーネント配置場所が <i data-path-to-node="20" data-index-in-node="52"><strong>Quattro</strong> -&gt; Weather Data Reading and Processing</i> に変更されました（旧バージョンのコンポーネントはインストーラーが自動で削除します）。</p>
<p data-path-to-node="21">詳細なリリースノートおよびダウンロードにつきましては、以下のGitHubリポジトリをご確認ください。 <a class="ng-star-inserted" href="https://github.com/TRNSYSJP/WeatherDataMap/releases" target="_blank" rel="noopener" data-hveid="0" data-ved="0CAAQ_4QMahgKEwj96cKWxMWXAxUAAAAAHQAAAAAQowE">TRNSYSJP/WeatherDataMap のリリースページ</a></p>
<p data-path-to-node="22">また、本リリースに関する概要は以下のブログ記事でも紹介しています。あわせてご覧ください。 <a class="ng-star-inserted" href="https://www.kankyoukei.com/2026/10/weather-data-map-plugin-release.html" target="_blank" rel="noopener" data-hveid="0" data-ved="0CAAQ_4QMahgKEwj96cKWxMWXAxUAAAAAHQAAAAAQzQE">Weather Data Map Plugin Release</a></p>
<p data-path-to-node="22">よろしくお願いいたします。</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>YuichiYasuda</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/announce_forum/new-release-weather-data-map-plugin-v1-0-0/</guid>
                    </item>
				                    <item>
                        <title>Type2625 JSON Printer 2.0 - a component that writes TRNSYS 18 results to JSON or CSV</title>
                        <link>https://trnsys.org/community/announce_forum/type2625-json-printer-2-0-a-component-that-writes-trnsys-18-results-to-json-or-csv/</link>
                        <pubDate>Sat, 17 Oct 2026 07:31:09 +0000</pubDate>
                        <description><![CDATA[I have released Type2625 JSON Printer 2.0 (2.0.0).Type2625 is a printer component that writes TRNSYS simulation results to a file in JSON or CSV format.- In JSON format, results are written ...]]></description>
                        <content:encoded><![CDATA[<p>I have released Type2625 JSON Printer 2.0 (2.0.0).<br /><br />Type2625 is a printer component that writes TRNSYS simulation results to a file in JSON or CSV format.<br />- In JSON format, results are written as an object keyed by time, so they can be read directly with Python (pandas) and other tools.<br />- Time can be written as simulation time  or as a date and time (e.g. 1995-01-01T00:15:00.000).<br />- Values can be written in exponential or decimal notation.<br />- A dedicated plug-in sets the output format and the names of the inputs to be printed, and shows an example of the output.<br />- It is used in much the same way as Type25 (Printer).<br /><br />What's new in 2.0<br />- The settings plug-in has been rebuilt with a Windows 11 style (Fluent) design. The window can now be resized, and the Inputs page is a simple list of name fields.<br />- .NET Framework and the Microsoft Visual C++ Redistributable are no longer required.<br />- New installer. If version 1.0.4 or earlier is installed, it is uninstalled automatically.<br />- The manual (English and Japanese) is now in HTML and can be opened from Help (F1) in the plug-in or from the last page of the installer.<br />- New component icons.<br />- The output itself is unchanged from 1.0.4.<br /><br />Requirements<br />- TRNSYS 18 (64-bit)<br />- Windows 10 / 11 (64-bit)<br /><br />The installer is not code-signed, so Windows SmartScreen may show a warning when you run it. In that case, click "More info" and then "Run anyway".<br />After installation, the components appear under Quattro &gt; Output &gt; JSON Printer in the Direct Access Toolbar of Simulation Studio.<br />On a first installation, please add a line "2625" to Exe\Descrips.dat in the TRNSYS 18 folder (see section 2.2 of the manual). This is not necessary if you already added it for a previous version.<br /><br />Download and details:<br />https://www.kankyoukei.com/en/2025/04/type2625-json-printer-2.html<br /><br />Comments and bug reports are welcome on the blog.<br /><br />---<br /><br />Type2625 JSON Printer 2.0（2.0.0）をリリースしました。<br /><br />Type2625 は、TRNSYS のシミュレーションの結果を、JSON 形式または CSV 形式のファイルに出力するコンポーネントです。<br />・JSON 形式では、時刻をキーにしたオブジェクトを出力します。Python（pandas）などで、そのまま読み込めます。<br />・時刻は、シミュレーションの時間  または日付時刻（例: 1995-01-01T00:15:00.000）で出力できます。<br />・数値は、指数表記と小数表記から選べます。<br />・専用のプラグインで、出力の形式と出力する Input の名前を設定し、出力例を確認できます。<br />・使い方は Type25（Printer）とほぼ同じです。<br /><br />■ 2.0 の主な変更点<br />・設定用のプラグインを、Windows 11 のデザイン（Fluent Design）で作り直しました。ウィンドウの大きさを変えられるようになり、Inputs の画面は名前を入力する欄の一覧になりました。<br />・.NET Framework と Microsoft Visual C++ 再頒布可能パッケージが不要になりました。<br />・インストーラーを新しくしました。1.0.4 以前がインストールされている場合は、自動でアンインストールします。<br />・マニュアル（日本語・英語）を HTML にしました。プラグインの Help（F1 キー）や、インストーラーの最後のページから開けます。<br />・コンポーネントのアイコンを変更しました。<br />・出力の内容は 1.0.4 から変わっていません。<br /><br />■ 動作環境<br />・TRNSYS 18（64bit）<br />・Windows 10 / 11（64bit）<br /><br />インストーラーはコード署名していないため、実行するときに Windows SmartScreen の警告が表示されることがあります。その場合は「詳細情報」をクリックしてから「実行」をクリックしてください。<br />インストールすると、Simulation Studio の Direct Access Toolbar の Quattro &gt; Output &gt; JSON Printer に追加されます。<br />初めてインストールする場合は、TRNSYS 18 のフォルダの Exe\Descrips.dat に「2625」の行を追加してください（マニュアルの 2.2 を参照）。以前のバージョンで追加済みの場合は不要です。<br /><br />■ ダウンロードと詳細<br />https://www.kankyoukei.com/2021/10/type2625-json-printer.html<br /><br />ご意見や不具合のご報告は、ブログのコメントでお寄せください。</p>
<div id="wpfa-490" class="wpforo-attached-file"><a class="wpforo-default-attachment" href="//trnsys.org/wp-content/uploads/wpforo/default_attachments/1792222490-2026-10-17_16h33_03.png" target="_blank" title="2026-10-17_16h33_03.png"><i class="fas fa-paperclip"></i>&nbsp;2026-10-17_16h33_03.png</a></div>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>YuichiYasuda</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/announce_forum/type2625-json-printer-2-0-a-component-that-writes-trnsys-18-results-to-json-or-csv/</guid>
                    </item>
				                    <item>
                        <title>Type99 tracking mode 3</title>
                        <link>https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/type99-tracking-mode-3/</link>
                        <pubDate>Fri, 16 Oct 2026 11:56:11 +0000</pubDate>
                        <description><![CDATA[Hi all,
I’m modelling a parabolic trough collector field with Type99 (TRNSYS 18), tracking mode 3, horizontal N-S axis (slope 0, azimuth 0). I want to create a didital twin and confirm meas...]]></description>
                        <content:encoded><![CDATA[<p dir="ltr">Hi all,</p>
<p dir="ltr">I’m modelling a parabolic trough collector field with Type99 (TRNSYS 18), tracking mode 3, horizontal N-S axis (slope 0, azimuth 0). I want to create a didital twin and confirm meassured data with  the simulation. <br />The incidence angle was way off. The surface slope output stays near 90 deg all day and never goes back to 0. Changing the axis azimuth makes no difference at all. Maybe there is an error with "GetTiltedRadiation" because i think it interprets the the <span data-teams="true">tilt of the collector surface as axis of my collector row. So in the first time step when the sun is raising my collector faces almos 90° east. So far thats correct, but in the next time step my axis of the collector becomes 90° which means that from now on the collector is rotating around a pole instead of the north sout axis. Also I tried type 109, which works fine but its an outdated type and has a known bug when the slope is 0. Next step is trying type 16 plus type 9.<br /><br />best regards<br />Alex </span></p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>alexunder</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/type99-tracking-mode-3/</guid>
                    </item>
				                    <item>
                        <title>French User meeting 2026</title>
                        <link>https://trnsys.org/community/announce_forum/french-user-meeting-2026/</link>
                        <pubDate>Thu, 01 Oct 2026 13:56:45 +0000</pubDate>
                        <description><![CDATA[Save the date - retenez la date ! Journée TRNSYS France : 26/11/2026 par viso
Stand by for more information.]]></description>
                        <content:encoded><![CDATA[<p><span>Save the date - retenez la date ! Journée TRNSYS France : 26/11/2026 par viso</span></p>
<p>Stand by for more information. </p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>Werner Keilholz</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/announce_forum/french-user-meeting-2026/</guid>
                    </item>
				                    <item>
                        <title>How to Create a Valid Performance Data File for Type 107 at Low Hot-Water Temperatures?</title>
                        <link>https://trnsys.org/community/standard-forum/how-to-create-a-valid-performance-data-file-for-type-107-at-low-hot-water-temperatures/</link>
                        <pubDate>Tue, 01 Sep 2026 08:00:10 +0000</pubDate>
                        <description><![CDATA[Hello everyone,I am currently developing a TRNSYS model of a solar-assisted cooling system that integrates a single-effect absorption chiller, solar thermal collectors.For the absorption chi...]]></description>
                        <content:encoded><![CDATA[<p>Hello everyone,<br /><br />I am currently developing a TRNSYS model of a solar-assisted cooling system that integrates a single-effect absorption chiller, solar thermal collectors.<br /><br />For the absorption chiller, I am using Type 107. However, I have encountered an important issue regarding the default performance data file.<br /><br />The default Type 107 data file in my TRNSYS installation uses the following inlet hot-water temperatures:<br /><br />108.89, 111.67, 113.89, 115.00, and 116.11 °C.<br /><br />My system, however, is designed to operate a low-temperature single-effect absorption chiller with a hot-water inlet temperature around 85–95 °C.<br /><br />Therefore, using the default Type 107 performance file would place the chiller outside the temperature range of the original performance map.<br /><br />I understand that simply replacing the hot-water temperature values in the default data file, for example changing them to 75, 80, 85, 90, and 95 °C, while keeping the original capacity and energy-input fractions unchanged, would not represent a physically valid chiller model.<br /><br />I also found the following TESS/Yazaki data file:<br /><br />Yazaki20-50ton(OneStage)S3.dat<br /><br />which provides the relationship between inlet hot-water temperature and fraction of nominal cooling capacity:<br /><br />76.67 °C → 0.00<br />79.44 °C → 0.25<br />82.22 °C → 0.47<br />85.00 °C → 0.63<br />87.78 °C → 0.82<br />90.56 °C → 0.97<br />93.33 °C → 1.06<br />96.11 °C → 1.13<br />98.89 °C → 1.22<br /><br />This information is very useful for defining the effect of hot-water inlet temperature on cooling capacity. However, it appears to be insufficient for constructing the complete Type 107 performance data file.<br /><br />As I understand it, the Type 107 data file also accounts for:<br /><br />fraction of design load,<br />chilled-water setpoint,<br />entering cooling-water temperature,<br />inlet hot-water temperature,<br /><br />and requires both:<br /><br />capacity fraction, and<br />design energy input fraction.<br /><br />The main difficulty is that publicly available manufacturer catalogues for low-temperature single-effect absorption chillers usually provide only nominal operating conditions or a limited number of correction curves. Complete multidimensional performance data are rarely available.<br /><br />My required nominal cooling capacity is approximately 113 kW (about 32 TR), and the intended hot-water operating range is approximately 80–95 °C.<br /><br />I would therefore appreciate guidance from experienced TRNSYS users or developers on the following questions:<br /><br />What is the recommended method for creating a new Type 107 performance data file for a low-temperature hot-water-driven absorption chiller?<br />Are there existing Type 107 or TESS data files for single-effect absorption chillers operating in approximately the 75–95 °C range?<br />Does anyone have the corresponding Yazaki S1 and S2 data files associated with Yazaki20-50ton(OneStage)S3.dat?<br />If only the hot-water capacity correction curve is available from the manufacturer, is it acceptable to combine this manufacturer-specific relationship with normalized part-load, chilled-water-temperature, and cooling-water-temperature relationships from another validated absorption-chiller dataset?<br />How should the Design Energy Input Fraction be determined when the manufacturer provides cooling-capacity correction factors but does not provide detailed heat-input or COP data for all operating conditions?<br />Would another TRNSYS/TESS absorption-chiller component be more appropriate than Type 107 for modeling a solar-driven single-effect chiller operating around 85–95 °C?<br />If manufacturer selection software can provide several off-design operating points, would it be acceptable to use those data to construct the multidimensional performance map required by Type 107?<br /><br />My main objective is to avoid arbitrary extrapolation and to build a performance file that is physically meaningful and defensible for academic research.<br /><br />Any recommendations, example data files, documentation, or previous experience with this issue would be greatly appreciated.<br /><br />Thank you very much for your help.</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>MPM</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/standard-forum/how-to-create-a-valid-performance-data-file-for-type-107-at-low-hot-water-temperatures/</guid>
                    </item>
				                    <item>
                        <title>Pleiades Modeleur -&gt; TRNBuild : A simpler way to create TRNSYS building models</title>
                        <link>https://trnsys.org/community/modeling-buildings-in-trnsys-trnsys3d-trnbuild-type-56/pleiades-modeleur-trnbuild-a-simpler-way-to-create-trnsys-building-models/</link>
                        <pubDate>Tue, 11 Aug 2026 12:16:53 +0000</pubDate>
                        <description><![CDATA[Hello everyone &#x1f642; ,
I would like to share a tool that may be interesting for TRNSYS users who need to create detailed multi-zone building models.
IZUBA, the French distributor and s...]]></description>
                        <content:encoded><![CDATA[<p class="isSelectedEnd"><span>Hello everyone &#x1f642; ,</span></p>
<p class="isSelectedEnd"><span>I would like to share a tool that may be interesting for TRNSYS users who need to create detailed multi-zone building models.</span></p>
<p class="isSelectedEnd"><strong><span>IZUBA, the French distributor and support team for TRNSYS, has developed a gateway between Pleiades Modeleur and TRNBuild.</span></strong></p>
<p>This can be particularly useful for users working with multi-zone buildings. In Pleiades Modeleur, zones can be created with a single click, and the contacts between adjacent zones are automatically detected. There is no need to manually define the connections between zones, which can significantly simplify the modeling process and reduce the risk of errors &#x1f60e; .</p>
<p><span>Another advantage is the easy definition of </span><strong><span>solar shading </span></strong>and<strong><span> surrounding obstacles</span></strong><span>. The building environment can be imported directly into Pleiades Modeleur, making it much easier to model neighboring buildings that  affect solar gains . And also the p</span><span>ossibility to define and export different schedules, such as occupancy, ventilation, heating and cooling.</span></p>
<p class="isSelectedEnd"><span>Documentation and examples:</span></p>
<p class="isSelectedEnd"><span>TRNSYS FAQ:</span><br /><a href="https://pleiades-doc.com/v4/fr/index.php/FAQ_TrnSys"><span>https://pleiades-doc.com/v4/fr/index.php/FAQ_TrnSys</span></a></p>
<p class="isSelectedEnd"><span>Pleiades modeler → TRNBuild documentation:</span><br /><a href="https://pleiades-doc.com/v4/fr/index.php/Exporter_vers_Editeur_(Modeleur)?toc-id=404#Export_TRNSYS_.28Version_Alpha.29"><span>https://pleiades-doc.com/v4/fr/index.php/Exporter_vers_Editeur_(Modeleur)?toc-id=404#Export_TRNSYS_.28Version_Alpha.29</span></a><span></span></p>
<div id="wpfa-487" class="wpforo-attached-file"><a class="wpforo-default-attachment" title="Pleiades-modeler-to-TRNBUILD.png" href="//trnsys.org/wp-content/uploads/wpforo/default_attachments/1786450613-Pleiades-modeler-to-TRNBUILD.png" target="_blank" rel="noopener"><i class="fas fa-paperclip"></i> Pleiades-modeler-to-TRNBUILD.png</a></div>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>Mohamed TABERNOUST</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/modeling-buildings-in-trnsys-trnsys3d-trnbuild-type-56/pleiades-modeleur-trnbuild-a-simpler-way-to-create-trnsys-building-models/</guid>
                    </item>
				                    <item>
                        <title>Can TRNSYS be repurposed for predicting the energy impact of speculative megastructures (e.g., Dyson spheres) on Earth’s climate? Кто где смотрит русские сериалы онлайн в хорошем качестве?</title>
                        <link>https://trnsys.org/community/admin-forum/can-trnsys-be-repurposed-for-predicting-the-energy-impact-of-speculative-megastructures-e-g-dyson-spheres-on-earths-climate-%d0%ba%d1%82%d0%be-%d0%b3%d0%b4%d0%b5-%d1%81%d0%bc%d0%be%d1%82/</link>
                        <pubDate>Tue, 04 Aug 2026 14:41:54 +0000</pubDate>
                        <description><![CDATA[I’m curious whether the modular nature of TRNSYS allows us to model absurdly large, non‑physical constructs and assess their hypothetical thermal footprints. Would such a “science‑fiction” e...]]></description>
                        <content:encoded><![CDATA[I’m curious whether the modular nature of TRNSYS allows us to model absurdly large, non‑physical constructs and assess their hypothetical thermal footprints. Would such a “science‑fiction” exercise be a legitimate use of the software, or does it cross the line into misuse?]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>Rosserial_Laf</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/admin-forum/can-trnsys-be-repurposed-for-predicting-the-energy-impact-of-speculative-megastructures-e-g-dyson-spheres-on-earths-climate-%d0%ba%d1%82%d0%be-%d0%b3%d0%b4%d0%b5-%d1%81%d0%bc%d0%be%d1%82/</guid>
                    </item>
				                    <item>
                        <title>Open position as a professor for simulation of thermal systems</title>
                        <link>https://trnsys.org/community/announce_forum/open-position-as-a-professor-for-simulation-of-thermal-systems/</link>
                        <pubDate>Tue, 28 Jul 2026 16:01:42 +0000</pubDate>
                        <description><![CDATA[Dear friends of the TRNSYS community,
If, in addition to your passion for thermal simulation, you also have a enthusiasm for teaching (though in German) and hold a PhD, then a position as a...]]></description>
                        <content:encoded><![CDATA[<p>Dear friends of the TRNSYS community,</p>
<p>If, in addition to your passion for thermal simulation, you also have a enthusiasm for teaching (though in German) and hold a PhD, then a position as a professor at the Technical University of Applied Sciences Cologne (TH Köln) with a focus on thermal simulation might be of interest to you.</p>
<p><a href="https://www.linkedin.com/feed/update/urn:li:share:7480219408578207744/">https://www.linkedin.com/feed/update/urn:li:share:7480219408578207744/</a></p>
<p><a href="https://karriere.th-koeln.de/job/view/1566/professur-fuer-thermische-energ">https://karriere.th-koeln.de/job/view/1566/professur-fuer-thermische-energ</a></p>
<p>If you are interested, don't hesitate, to contact me.</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>Klaus Lambers</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/announce_forum/open-position-as-a-professor-for-simulation-of-thermal-systems/</guid>
                    </item>
							        </channel>
        </rss>
		
<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced (Requested URI contains query) 

Served from: trnsys.org @ 2026-11-09 02:11:07 by W3 Total Cache
-->