https://forge.codesys.com/forge/talk/Engineering/thread/b9b1c4d20b/2020-02-27T13:56:37.553000ZRecent posts to CANOpen Remote Device eds file (in CoDeSys V3.5 Patch 4)2020-02-27T13:56:37.553000Z2020-02-27T13:56:37.553000Ztimvhhttps://forge.codesys.com/u/timvh/https://forge.codesys.com8cd10e589d0ee30e49d9f27d0215dc8020817aff

<div class="markdown_content"><p>Thanks for the info.</p></div>

2020-02-27T13:56:36.880000Z2020-02-27T13:56:36.880000Zchabhttps://forge.codesys.com/u/chab/https://forge.codesys.come77f3dac7ff9e6b3f4b52dc771c7bcc02e80a3a4

<div class="markdown_content"><p>The unique identification changed.<br/> The ID is compiled from sections in the eds file.<br/> In V3.4: FileInfo and DeviceInfo-sections. And the actual eds filename.<br/> In V3.5: FileInfo and DeviceInfo-sections. And the Identity section <span>[1018]</span>.</p></div>

2020-02-27T13:56:36.659000Z2020-02-27T13:56:36.659000Zchabhttps://forge.codesys.com/u/chab/https://forge.codesys.com4452c3f0f13cff13f2506b39de7ee68cd97ae8cd

<div class="markdown_content"><p>Recently I updated to CoDeSys V3.5 Patch 4 (from V3.4).<br/> And I noticed that some of the eds files for Remote Device are not imported.<br/> For a Vendor, only one eds file is loaded. Any other eds files, for that Vendor, are skipped.</p> <p>Did anyone experience similar behaviour?</p> <p>The steps are Tools; Device Repository; Install; *.eds<br/> The result would be under Tools; Device Repository; Fieldbusses; CANopen; Remote Device.</p> <p>Regards.</p></div>