<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Dynamic Memory with Control RTE V3 64</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/</id><updated>2020-02-27T15:17:26.226000Z</updated><subtitle>Recent posts to Dynamic Memory with Control RTE V3 64</subtitle><entry><title>Dynamic Memory with Control RTE V3 64</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/?limit=25#86b4" rel="alternate"/><published>2020-02-27T15:17:26.226000Z</published><updated>2020-02-27T15:17:26.226000Z</updated><author><name>jerry.sorrells</name><uri>https://forge.codesys.com/u/jerry-sorrells/</uri></author><id>https://forge.codesys.come483d9805b311885d6f7cbcc0f44c8c573394edb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thank you, Marcel.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Dynamic Memory with Control RTE V3 64</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/?limit=25#2d0c" rel="alternate"/><published>2020-02-27T15:17:24.409000Z</published><updated>2020-02-27T15:17:24.409000Z</updated><author><name>mprestel</name><uri>https://forge.codesys.com/u/mprestel/</uri></author><id>https://forge.codesys.comcc9e46f91c6a0f74ca77326c4b65143974d49ac6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;in SP10 the dataserver was replayed by the new data sources manager.&lt;br/&gt;
Here is the release note&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Zitat:&lt;/strong&gt;&lt;br/&gt;
With CODESYS Version V3.5 SP10 the DataServer will be replaced by the new Data Sources Manager. Projects with DataServer can be used furthermore when the compiler version and the visualization profile is not updated. When the compiler version and the visualization profile is updated to V3.5 SP10 then the DataServer must be converted to the new Data Sources Manager. A command is provided in the context menu when the DataServer is selected. &lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Best regards,&lt;br/&gt;
Marcel&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Dynamic Memory with Control RTE V3 64</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/?limit=25#c148" rel="alternate"/><published>2020-02-27T15:17:23.777000Z</published><updated>2020-02-27T15:17:23.777000Z</updated><author><name>jerry.sorrells</name><uri>https://forge.codesys.com/u/jerry-sorrells/</uri></author><id>https://forge.codesys.com912d17f818f4301a0412a382b133c095d55bb63a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, Edwin. Thank you for your reply. The only reason we're still at 3.5.9 is the DataServer. We plan to update and quit using the DataServer, but we're looking for an intermediary step. Do you happen to know the most updated version of Codesys that still supports the DataServer?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Dynamic Memory with Control RTE V3 64</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/?limit=25#f7c4" rel="alternate"/><published>2020-02-27T15:17:23.121000Z</published><updated>2020-02-27T15:17:23.121000Z</updated><author><name>eschwellinger</name><uri>https://forge.codesys.com/u/eschwellinger/</uri></author><id>https://forge.codesys.comc329e448523ae87760833803f789ce529df5721e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;hm Codesys Memory Manager, 3.4.2.0 - hm this is preatty old, could you check if the project need to be updated&lt;br/&gt;
I would expect to have this lib at least in 3.5.12.0&lt;br/&gt;
( so update projcet compiler/ visu profile and device descriptions to current version is maybe needed)&lt;/p&gt;
&lt;p&gt;BR&lt;br/&gt;
Edwin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Dynamic Memory with Control RTE V3 64</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/7cfdba04a8/?limit=25#df08" rel="alternate"/><published>2020-02-27T15:17:21.294000Z</published><updated>2020-02-27T15:17:21.294000Z</updated><author><name>jerry.sorrells</name><uri>https://forge.codesys.com/u/jerry-sorrells/</uri></author><id>https://forge.codesys.com9ab2e9ce452cd40ed60049819ef875ec090cad27</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We are converting a project from a 32-bit controller running Codesys to Control RTE V3 64 (version 3.5.9.10) . The project uses dynamic memory allocation. When Application-&amp;gt;Properties-&amp;gt;Application build options-&amp;gt;"Use dynamic memory allocation" is selected, the library CDS_MemMan (Codesys Memory Manager, 3.4.2.0) is implicitly added to the Library Manager. After the library is added, building the application results in multiple errors for type conversions between DWORDs (32-bit) and POINTERs (64-bit) and all of the errors are associated with the CDS_MemMan library. When dynamic memory allocation is disabled, the errors go away, but of course we can no longer use dynamic memory in the application.&lt;/p&gt;
&lt;p&gt;&lt;img alt="IMG: Screen Shot 2019" rel="nofollow" src="https://forum.codesys.com//download/file.php?id=5082"/&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>