<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to CANbus issue</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/146d3d6c7d/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Runtime/thread/146d3d6c7d/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Runtime/thread/146d3d6c7d/</id><updated>2023-09-14T10:31:23.904000Z</updated><subtitle>Recent posts to CANbus issue</subtitle><entry><title>CANbus issue</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/146d3d6c7d/?limit=25#7f25" rel="alternate"/><published>2023-09-14T10:31:23.904000Z</published><updated>2023-09-14T10:31:23.904000Z</updated><author><name>TimvH</name><uri>https://forge.codesys.com/u/timvh/</uri></author><id>https://forge.codesys.com48527b3b62b8254798f5e1a11819c8a37bcfa473</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;On a PC with the Control Win, this is probably related to the fact that the CAN drivers are not loaded.&lt;/p&gt;
&lt;p&gt;Go to the folder where your Control Win Configuration file is:&lt;br/&gt;
- E.g. C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E1FA7ABE&lt;br/&gt;
- Open the CODESYSControl.cfg&lt;br/&gt;
- Remove the semi-colon in front of the CAN driver you want to use (section ComponentManager).&lt;br/&gt;
- Set the component ID to the next number in the list (e.g. Component.8)&lt;br/&gt;
- Save this file and restart the Control Win.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CANbus issue</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/146d3d6c7d/?limit=25#4b8a" rel="alternate"/><published>2023-09-14T06:41:39.027000Z</published><updated>2023-09-14T06:41:39.027000Z</updated><author><name>transmin01</name><uri>https://forge.codesys.com/u/transmin01/</uri></author><id>https://forge.codesys.com6674f57996cd4b9697e611989ec416521622aa6a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Update: This initial issue was when using a Linux target PLC. Since then I have created a Win10 target PC and the Codesys software reported an issue associated with the device version (see attached).&lt;/p&gt;
&lt;p&gt;I am assuming this is an incompatibility with the xml file from the manufacturer and the firmware version on the module and I am chasing this up with Beckhoff.&lt;/p&gt;
&lt;p&gt;Question is, why would this not report with a Linux target?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CANbus issue</title><link href="https://forge.codesys.com/forge/talk/Runtime/thread/146d3d6c7d/?limit=25#cf78" rel="alternate"/><published>2023-09-13T03:08:04.539000Z</published><updated>2023-09-13T03:08:04.539000Z</updated><author><name>transmin01</name><uri>https://forge.codesys.com/u/transmin01/</uri></author><id>https://forge.codesys.com830f9435288ab8555250901c201d67920e7c2c50</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
   I have been trying to get a CANbus device working with Codesys 3.5SP19 patch1 via a Beckhoff EL671 gateway without success. I have the CANOpen_Manager and CANopen device configured but this will not run. Is there any code required to kickstart the CANbus comms into action?&lt;/p&gt;
&lt;p&gt;Regards Trevor&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>