<?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 Posts				            </title>
            <link>https://trnsys.org/community/</link>
            <description>TRNSYS Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sat, 21 Nov 2026 10:35:22 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Temperature distribution in rock around storage</title>
                        <link>https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/temperature-distribution-in-rock-around-storage/#post-1447</link>
                        <pubDate>Wed, 18 Nov 2026 15:17:56 +0000</pubDate>
                        <description><![CDATA[Good Morning.
I work on the Pit Thermal Energy Storage (PTES) model with TESS library. What I would like to know if it is possible to have the temperature distribution in the rock/soil arou...]]></description>
                        <content:encoded><![CDATA[<p>Good Morning.</p>
<p>I work on the Pit Thermal Energy Storage (PTES) model with TESS library. What I would like to know if it is possible to have the temperature distribution in the rock/soil around the storage (on the perimeter area and under the storage, I think in 2D view)?</p>
<p>Please look at:</p>
<p>https://www.iea-dhc.org/fileadmin/documents/Annex_XII/2020.03.09_Report_Task_C_IEA_DHC_Annex_XII_Project_03.pdf </p>
<p>Figures from 23 to 26. I would like to get something like that.</p>
<p>I use Type1536_NoHX_v2a with Ground Coupling Type1301_v2a. You can look at my screenshots model.png (sorry for the mess, but these are my beginnings). Do I need some more components or what? In both aforementioned components, there is no output connected to this matter. </p>
<p>Could anyone help me?</p>
<p>Thank you for your time.</p>
<p>Karol</p>
<div id="wpfa-493" class="wpforo-attached-file"><a class="wpforo-default-attachment" href="//trnsys.org/wp-content/uploads/wpforo/default_attachments/1795015076-model.png" target="_blank" title="model.png"><i class="fas fa-paperclip"></i>&nbsp;model.png</a></div>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>karol_p</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/temperature-distribution-in-rock-around-storage/#post-1447</guid>
                    </item>
				                    <item>
                        <title>Answer to: Do you knwo how to solve an issue arising with multiple instances of a TYPE in the same simulation ?</title>
                        <link>https://trnsys.org/community/standard-forum/do-you-knwo-how-to-solve-an-issue-arising-with-multiple-instances-of-a-type-in-the-same-simulation/#post-1446</link>
                        <pubDate>Wed, 18 Nov 2026 09:40:17 +0000</pubDate>
                        <description><![CDATA[Hello John@JohnSteinbergs thank you for your comment.Your comment regarding the coding issue of variable storage is consistent with the answers I have by now. I found a 2007 thread in what s...]]></description>
                        <content:encoded><![CDATA[<p>Hello John<br /><br />@JohnSteinbergs thank you for your comment.<br /><br />Your comment regarding the coding issue of variable storage is consistent with the answers I have by now. I found a 2007 thread in what seems to be a Trnsys obselete forum where someone was having the same problem. So you mentioned the temperature variable that is not being properly stored, which makes sense.<br /><br /><br />I reached out to the TYPE developers and they recognized the issue some time ago, maybe in the next version it will be fixed. However, they also gave me a solution to overcome this problem easily. In addition, I was developing my own solution to this problem. I will list them here aiming to help others in the future.<br /><br /><br />Solution #1: The easiest way to fix this problem and was recommended by the type developers. Since the tank storage can hold up to three different PCM modules, use different modules to include PCM information. For example, in my case study there are two tanks, one for the heating season and another for the cooling season. When setting the data, I include the hot tank PCM in module 1, and for the cold tank the PCM goes in module 2. I had the PCMs using the module 1 of each corresponding tank. This definitely solved the problem, as the problematic variable is stored in different locations for each PCM module. However, it may be more complicated if more than three tanks are intended to be used.<br /><br /><br />Solution #2: As suggested by John Steinbergs in the comment above and by David here Re:  Problems using several types in a project. This seems to be an effective way to solve the problem, but needs a bit of skills with recompiling. As you have said, the fortran files will be needed, and hopefully one can reach out to the developer.<br /><br /><br />Solution #3: prior to the TYPE840 developers answered my email, I was creating my own way to overcome the problem by implementing binary variables. In this regard, I have a one tank only with the parameters set as variable name, which allowed to call the parameters through the calculator. Each parameter will be called whenever the season signal is on. As I have two main season signals, one for winter and another for summer, that would be another way to overcome the issue.<br /><br />Thank you again for the comment and hope that these conversations here can help others in the future.<br /><br />Kind regards<br /><br />Humberto</p>
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>HumbertoSantos</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/standard-forum/do-you-knwo-how-to-solve-an-issue-arising-with-multiple-instances-of-a-type-in-the-same-simulation/#post-1446</guid>
                    </item>
				                    <item>
                        <title>Answer to: Do you knwo how to solve an issue arising with multiple instances of a TYPE in the same simulation ?</title>
                        <link>https://trnsys.org/community/standard-forum/do-you-knwo-how-to-solve-an-issue-arising-with-multiple-instances-of-a-type-in-the-same-simulation/#post-1445</link>
                        <pubDate>Tue, 17 Nov 2026 23:27:45 +0000</pubDate>
                        <description><![CDATA[@humbertosantos thank you for the detailed post! Your independent testing of the circuits and identification that the issue only arises when two tanks are present indicates the issue is like...]]></description>
                        <content:encoded><![CDATA[<p><span>@humbertosantos</span> thank you for the detailed post! Your independent testing of the circuits and identification that the issue only arises when two tanks are present indicates the issue is likely in the source code. My guess is that the temperature of the PCM is not being properly stored for calculations in the next time step. This would then lead to the two tanks (of the same TYPE) using temperatures interchangeably and producing unexplainable results.</p>
<p>The simplest fix if you have the source code and are familiar with recompiling types is to make a copy of Type 840 called Type 1840, replacing all "Type840" text in the source code with "Type1840" and recompiling it in the MyType project of TRNSYS18\Compilers\TRNSYS\TRNSYS.sln. You will also need to modify the Type 840 proforma to make a Type 1840 proforma. This will ensure that the two tanks do not share any variables since they will be treated as a different TYPE.</p>
<p>If you do not have the source code, you will need to reach out to the authors of the model to see if they can provide the source code or create and compile a Type 1840 for you. Alternatively, they may be able to identify the root issue and provide an updated Type 840 that works with multiple instances.</p>
<p>Finally, if the first two options are not possible then I would suggest you reach out to your distributor as they should be able to assist in recompiling the source code and troubleshooting.</p>
<p>&nbsp;</p>
<p>cheers,</p>
<p>John</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>JohnSteinbergs</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/standard-forum/do-you-knwo-how-to-solve-an-issue-arising-with-multiple-instances-of-a-type-in-the-same-simulation/#post-1445</guid>
                    </item>
				                    <item>
                        <title>Do you knwo how to solve an issue arising with multiple instances of a TYPE in the same simulation ?</title>
                        <link>https://trnsys.org/community/standard-forum/do-you-knwo-how-to-solve-an-issue-arising-with-multiple-instances-of-a-type-in-the-same-simulation/#post-1443</link>
                        <pubDate>Mon, 16 Nov 2026 02:41:46 +0000</pubDate>
                        <description><![CDATA[Hello everyone,
I am modeling a building heating and cooling system in TRNSYS 18 coupled with a heat pump and two separate Phase Change Material (PCM) thermal energy storage tanks simulated...]]></description>
                        <content:encoded><![CDATA[<p dir="ltr" data-path-to-node="1"><span>Hello everyone,</span></p>
<p dir="ltr" data-path-to-node="2"><span>I am modeling a building heating and cooling system in TRNSYS 18 coupled with a heat pump and two separate Phase Change Material (PCM) thermal energy storage tanks simulated using </span><b data-path-to-node="2" data-index-in-node="180">Type 840</b><span> (Heinz &amp; Moser model):</span></p>
<ul dir="ltr" data-path-to-node="3">
<li>
<p dir="ltr" data-path-to-node="3,0,0"><b data-path-to-node="3,0,0" data-index-in-node="0">Heating PCM tank (Type 840 – Unit 1):</b><span> Filled with encapsulated cylinders of Crodatherm 37 (operating range:</span><span> 35–45 °C),</span><span> reading external heating/cooling enthalpy tables via Logical Units 30 and 33.</span></p>
</li>
<li>
<p dir="ltr" data-path-to-node="3,1,0"><b data-path-to-node="3,1,0" data-index-in-node="0">Cooling PCM tank (Type 840 – Unit 2):</b><span> Filled with encapsulated cylinders of Crodatherm 9.</span><span>5 (operating range:</span><span> 5–12 °C),</span><span> reading separate external enthalpy tables via different Logical Units.</span></p>
</li>
</ul>
<p>I developed equations to control the operation of a heat pump, using a storage tank containing phase-change material (PCM) for the winter and a separate tank—also containing PCM—for the summer; both were modeled using the TYPE 840 component.<br /><br />However, I noticed inconsistencies in the results regarding the PCM melting process—specifically, the energy released deviated from expectations, which in turn affected the final simulation results.<br /><br />After spending a considerable amount of time investigating the potential causes, I discovered that when each circuit was run independently—whether for heating or cooling—the simulation results matched my expectations. I then removed one of the tanks (TYPE 840) from the simulation file (deck file) and confirmed that the issue stemmed precisely from the presence of two such tanks.<br /><br />Could someone provide guidance on how to resolve this? While I could run the simulations separately, it would be significantly more time-consuming; therefore, if a solution exists, I would prefer to try that first. Thank you in advance for any comments or suggestions. I do appreciate it.</p>
<p>&nbsp;</p>
<p>Regards</p>
<p>Humberto </p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>HumbertoSantos</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/standard-forum/do-you-knwo-how-to-solve-an-issue-arising-with-multiple-instances-of-a-type-in-the-same-simulation/#post-1443</guid>
                    </item>
				                    <item>
                        <title>Answer to: cpvt</title>
                        <link>https://trnsys.org/community/standard-forum/cpvt/#post-1442</link>
                        <pubDate>Tue, 10 Nov 2026 08:34:21 +0000</pubDate>
                        <description><![CDATA[Hi Ibrahim,
If your question is about how to set up a new component, the easyest way is to us the function 
File/New … New Component.
Fill in the Proforma, save it to \TRNSYS18\Studio\Pro...]]></description>
                        <content:encoded><![CDATA[<p>Hi Ibrahim,</p>
<p>If your question is about how to set up a new component, the easyest way is to us the function </p>
<p>File/New … New Component.</p>
<p>Fill in the Proforma, save it to \TRNSYS18\Studio\Proformas and use</p>
<p>File/Export as</p>
<p>To produce a C++ or FORTAN code template. This is described in \TRNSYS18\Documentation\02-SimulationStudio.pdf for the code generation and in 07-ProgrammersGuide.pdf for compiling the new type.</p>
<p>If your question is about how to model the cpvt collector, you will find some useful articles <a href="https://www.google.com/search?q=creating+a+custom+TRNSYS+CPVT+component+type+that+uses+triple-junction+photovoltaic+cells&amp;rlz=1C1GCPS_enFR1199FR1199&amp;oq=creating+a+custom+TRNSYS+CPVT+component+type+that+uses+triple-junction+photovoltaic+cells" target="_blank" rel="noopener">on the net</a>.<br /><br /><br /></p>
<p>&nbsp;</p>
<p>This one looks promising :</p>
<p>https://www.academia.edu/91093920/Concentrated_photovoltaic_thermal_CPVT_solar_collector_systems_Part_II_Implemented_systems_performance_assessment_and_future_directions</p>
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>Werner Keilholz</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/standard-forum/cpvt/#post-1442</guid>
                    </item>
				                    <item>
                        <title>cpvt</title>
                        <link>https://trnsys.org/community/standard-forum/cpvt/#post-1439</link>
                        <pubDate>Mon, 09 Nov 2026 14:29:43 +0000</pubDate>
                        <description><![CDATA[Hello, everyone. Please, I need help creating a custom TRNSYS CPVT component type that uses triple-junction photovoltaic cells.]]></description>
                        <content:encoded><![CDATA[<p>Hello, everyone. Please, I need help creating a custom TRNSYS CPVT component type that uses triple-junction photovoltaic cells.</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>Ibrahim</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/standard-forum/cpvt/#post-1439</guid>
                    </item>
				                    <item>
                        <title>Answer to: 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/#post-1437</link>
                        <pubDate>Wed, 28 Oct 2026 17:52:17 +0000</pubDate>
                        <description><![CDATA[@louis-lamarcheetsmtl-ca
Louis, I think the first option is the one that I would use. 
As a side note (and my apologies if you are already aware of this) Type67 applies a mask to the diffu...]]></description>
                        <content:encoded><![CDATA[<p><span>@louis-lamarcheetsmtl-ca</span></p>
<p>Louis, I think the first option is the one that I would use. </p>
<p>As a side note (and my apologies if you are already aware of this) Type67 applies a mask to the diffuse radiation but assumes an isotropic sky. It does not take into account the added diffuse radiation from horizon brightening or from circumsolar diffuse. Technically the shading factor that it computes is most appropriately applied when you have selected the isotropic sky model in your weather data reading component. However, I typically use one of the Perez sky radiation models instead. I think that the underprediction of diffuse solar that comes from the isotropic sky model plus the shading factor means that the impacts of shading are overestimated.</p>
<p>~ david</p>
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>DavidBradley</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/ground-reflected-radiation-with-type-67/#post-1437</guid>
                    </item>
				                    <item>
                        <title>Answer to: Type99 tracking mode 3</title>
                        <link>https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/type99-tracking-mode-3/#post-1436</link>
                        <pubDate>Wed, 28 Oct 2026 17:37:06 +0000</pubDate>
                        <description><![CDATA[@alexunder
sorry for the late reply. Did you by chance try this with Type15? Or perhaps the weather file you are working with is not one of the ones that can directly be read by Type15. In ...]]></description>
                        <content:encoded><![CDATA[<p><span>@alexunder</span></p>
<p>sorry for the late reply. Did you by chance try this with Type15? Or perhaps the weather file you are working with is not one of the ones that can directly be read by Type15. In any case, please get in touch with your distributor and send them the project you are working with so that they can see what is going on. I would be a little surprised if getTiltedRadiation() were at fault because there are other components that rely on the same subroutine.</p>
<p>~ david</p>
<p>&nbsp;</p>]]></content:encoded>
						                            <category domain="https://trnsys.org/community/"></category>                        <dc:creator>DavidBradley</dc:creator>
                        <guid isPermaLink="true">https://trnsys.org/community/component-libraries-tess-libraries-transsolar-components-user-written-components/type99-tracking-mode-3/#post-1436</guid>
                    </item>
				                    <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/#post-1434</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/#post-1434</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/#post-1433</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/#post-1433</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-21 10:35:22 by W3 Total Cache
-->