https://forge.codesys.com/forge/talk/Engineering/thread/7bb669969b/2022-02-09T13:01:41.816000ZRecent posts to CanOpen Manager - Timeout till _3SCOS.DEVICE_STATE.OPERATIONAL2022-02-09T13:01:41.816000Z2022-02-09T13:01:41.816000Zneapolitaner1https://forge.codesys.com/u/neapolitaner1/https://forge.codesys.com3ed9fb6b5e77594830eea50fbb60c07a2bb3bca3

<div class="markdown_content"><p>hi,</p> <p>finally i found the issue ... on my CAN-bus there are several CanOpen and J1939 devices. To keep the busload as low as possible i set the CanOpen PDO's to different interval-times. Therefore every few minutes/hours (depending on the chosen timings) all PDO's need to get handled at the same time.</p> <p>This "spike" in bus-load and especially cpu-load required way too much processing-time and exceeded the cycletime of the CPU.</p> <p>means: i've chosen 10ms as minimum CPU taskcycle<br/> during "spike": the CPU taskcycle-time took up to 14ms and probably messed up the internal timing/statemachine of the CanOpenManager</p> <p>solution: i've set the CPU-taskcycle-time to 20ms and since that modification everthing is fine!</p> <p>br,<br/> Andy</p></div>

2022-02-09T11:10:14.018000Z2022-02-09T11:10:14.018000Zjenslindruohttps://forge.codesys.com/u/jenslindruo/https://forge.codesys.comcf06e2ac28ecede426cdc52405aed3dc5a7f9a79

<div class="markdown_content"><p>Hi neapolitaner<br/> Did you ever find a solution to this problem? I am currently facing a similar situation.</p></div>

2022-02-09T11:10:10.932000Z2022-02-09T11:10:10.932000Zjenslindruohttps://forge.codesys.com/u/jenslindruo/https://forge.codesys.com2773c1e89b0bd717e487dfeb8e95e8eeb3674e68

<div class="markdown_content"><p>Hi neapolitaner<br/> Did you ever find a solution to this problem? I am currently facing a similar situation.</p></div>

2022-02-09T11:10:09.695000Z2022-02-09T11:10:09.695000Zjenslindruohttps://forge.codesys.com/u/jenslindruo/https://forge.codesys.comb83d0a6ff2c8549da001baa4c460926e1a279051

<div class="markdown_content"><p>Hi neapolitaner<br/> Did you ever find a solution to this problem? I am currently facing a similar situation.</p></div>

2022-02-09T11:10:08.828000Z2022-02-09T11:10:08.828000Zjenslindruohttps://forge.codesys.com/u/jenslindruo/https://forge.codesys.coma3db5b4e43e0307d278faf468f10df1284c3f0ea

<div class="markdown_content"><p>Hi neapolitaner<br/> Did you ever find a solution to this problem? I am currently facing a similar situation.</p></div>

2020-07-22T14:57:35.247000Z2020-07-22T14:57:35.247000Zneapolitanerhttps://forge.codesys.com/u/neapolitaner/https://forge.codesys.com8525e8edac2680595dcb233e4a9229438837d85b

<div class="markdown_content"><p>i'm using 3.5/SP10 .. i have to stick to that version because the ecu-supplier (TTControl) only supports that version</p> <p>"without a reason, the manager certainly doesn't" -&gt; :) i guess so, but i can't really reproduce the issue and depending on my can-traces i can't really naildown any bus-errors or similar.</p> <p>my master is producing a heartbeat with 500ms -&gt; upon simulated buserrors the CanOpenManager sends the ResetNode within less than 1sec (gess 1,5*500ms)</p> <p>-&gt; so IMHO increasing the errorthreshold/hb-timeout up to 3sec would probably fix my sporadic buserrors(missing node-hb)?!</p> <p>a restart of the can-nodes is very 'bad' in our application therefore i'm looking for a more forgiving behaviour of the CanOpenManager</p></div>

2020-07-22T14:38:48.973000Z2020-07-22T14:38:48.973000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com1cb6d34bd4305292efd3f6494a0252b5bdfcb294

<div class="markdown_content"><p>Hi,<br/> which plc in which version are you using?<br/> Could you enable CANOPEN_DEBUG as compiler define ( not needed =&gt;3.5SP16<br/> Then attach the plclogger - maybe the can trace too.</p> <p>"Unfortunately the Manager sends a ResetNode to all of my devices without any reason"<br/> without a reason, the manager certainly doesn't<br/> There will be a heartbeat error probably?!</p> <p>BR<br/> Edwin</p></div>

2020-07-22T12:52:01.754000Z2020-07-22T12:52:01.754000Zneapolitanerhttps://forge.codesys.com/u/neapolitaner/https://forge.codesys.come99e6887ff4c48685a2ccd72b9fca24d473f8d03

<div class="markdown_content"><p>i'm using the CanOpenManager to communicate with my devices (5pcs). Unfortunately the Manager sends a ResetNode to all of my devices without any reason. The time between the ResetNode-cmd is very random -&gt; could be a few minutes to few hours!!?!<br/> I've made lot's of canbus-traces, can see the ResetNode-cmd by the Manager but can't find any reason for the reset-cmd ...</p> <p>-&gt; so my last guess is that there is a intermittet failure on the bus and the manager sends the reset within less than one second!?!</p> <p>-&gt; is it possible to modify the timeout of the CanOpenManager that the ResetNode is sent only after a few seconds</p> <p>br,<br/> Andy</p></div>