https://forge.codesys.com/forge/talk/Engineering/thread/96b5493b31/2022-08-22T20:10:37.469000ZRecent posts to Is there a bug in the CANopen Manager ?2022-08-22T20:10:37.469000Z2022-08-22T20:10:37.469000ZDavidBohttps://forge.codesys.com/u/davidbo/https://forge.codesys.com2003d99d35b362e82eecb74ab274056e6e400ea6

<div class="markdown_content"><p>I can report that all my PDO was device specific asynchrony it means in my case that when ever a variable in the PDO changed value the PDO was sent. For one device it was acceptable but for 2-3 devices the bus got saturated and the behavior of CODESYS became unpredictable. When I changed the PDO to cyclic the problem disappeared.</p></div>

2022-07-18T11:39:03.348000Z2022-07-18T11:39:03.348000ZDavidBohttps://forge.codesys.com/u/davidbo/https://forge.codesys.comd582eb703bb49f4a4a5823ab65497aa476ed25c1

<div class="markdown_content"><p>I have a problem with receiving heat beats from 2 slave nodes, and I am beginning to believe that the CANopen Manager has a problem with receiving heat beats either by doing some access violation or overwrite data not yet read. My system is this:</p> <p><strong>CODESYS Control For Raspberry Pi MC SL</strong><br/> Version 4.4.0.0</p> <p>Version: 3.5.17.0<br/> Description: CANopen Manager<br/> Configuration version: 3.5.1.0</p> <p>Baud rate 250kbit/s<br/> MainTask Interval 100ms</p> <p><strong>SYNC</strong><br/> Cycle period 100ms, Window length 20ms<br/> For each node I have 4 Rx PDO and 4 Tx PDO. Heart beat every 400ms</p> <p>First I thought that all PDOs always where transmitted and received at every SYNC period. That does not seem to be the case. with<br/> ip -details -statistics link show can0<br/> I can see that TX: bytes aren't changing but the number of packets does. Why? Is that because the values of my TX PDOs haven't change? Can anyone confirm that?</p> <p>Ok my problem is this:<br/> My two nodes works well for 1 hour. Then I get missing heart beats from both of them.</p> <p>I was curious about what error frames I might receive from the nodes when the fault occurred, so I ran<br/> candump -e -x -ta -a -l any,0~0,#FFFFFFFF</p> <p>but as soon I did that there was no problems. It works for hours and it is still running.<br/> However, I cannot have logging enabled in my application for ever. Any suggestions for a work around.</p></div>