https://forge.codesys.com/forge/talk/Engineering/thread/d137e9d58f/2020-02-27T13:57:25.529000ZRecent posts to EtherCAT Motor Drive seems was affected by Modbus TCP2020-02-27T13:57:25.529000Z2020-02-27T13:57:25.529000Zlistenyanghttps://forge.codesys.com/u/listenyang/https://forge.codesys.comacf99f60b0149e6f2c0c3383f9d5ce89b0c85169

<div class="markdown_content"><blockquote> <p><strong>Edwin Schwellinger hat geschrieben:</strong><br/> yes that's the problem, you need to change your application in that way<br/> that you only reference the modbus io's in the modbus Task, and the ethercat io's in the ethercat Task.<br/> Thats the solution. The Task deployment tap give you the Feedback after compile / generate code it is updated. <br/> These red and blue cross show you in which task you are using the specified input/output.<br/> If you change that our problems should be solved.<br/> cu</p> </blockquote> <p>hi, Edwin<br/> Seems the problem has been solved, thanks your useful tips. </p></div>

2020-02-27T13:57:25.300000Z2020-02-27T13:57:25.300000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com807be3b7fa1ada87a0875793a137a4e404a7258d

<div class="markdown_content"><p>yes that's the problem, you need to change your application in that way<br/> that you only reference the modbus io's in the modbus Task, and the ethercat io's in the ethercat Task.<br/> Thats the solution. The Task deployment tap give you the Feedback after compile / generate code it is updated. <br/> These red and blue cross show you in which task you are using the specified input/output.<br/> If you change that our problems should be solved.</p> <p>cu</p></div>

2020-02-27T13:57:25.070000Z2020-02-27T13:57:25.070000Zlistenyanghttps://forge.codesys.com/u/listenyang/https://forge.codesys.com314e0b4a474e1c671f24611bed0af6eb6f56a57b

<div class="markdown_content"><blockquote> <p><strong>Edwin Schwellinger hat geschrieben:</strong><br/> hi,<br/> please add the screenshot from the Task deployment<br/> there you should see if the IO's are used in the right Task.<br/> cu</p> </blockquote> <p>hi, Edwin<br/> Thanks your fast reply.<br/> maybe you are right, i didn't find any IO specify into Modbus in task_deployment, i am just define IO to the address(like:var1 AT %QX167.0:BOOL; all the IO signals work fine), not fill into the Modbus IO mapping list. funny that they are all belong to Main_task, is it problem?<br/> other thing is, EtherCAT IO is:ID0~ID39, QD0~QD39, but in deployment all is 0. how come?</p> <p>thanks a lot...</p> <p><img alt="IMG: tasks deployment.JPG" rel="nofollow" src="https://forum.codesys.com//download/file.php?id=470"/></p></div>

2020-02-27T13:57:24.328000Z2020-02-27T13:57:24.328000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.combfd3f6582b187769833a90adc7d2ec3182a316e3

<div class="markdown_content"><p>hi,</p> <p>please add the screenshot from the Task deployment</p> <p>there you should see if the IO's are used in the right Task.</p> <p>cu</p> <p><img alt="IMG: taskdeployment.png" rel="nofollow" src="https://forum.codesys.com//download/file.php?id=469"/></p></div>

2020-02-27T13:57:24.105000Z2020-02-27T13:57:24.105000Zlistenyanghttps://forge.codesys.com/u/listenyang/https://forge.codesys.com53a11db1ac0b43cfb87a3e5a6ae111e120fc85fa

<div class="markdown_content"><blockquote> <p><strong>Edwin Schwellinger hat geschrieben:</strong><br/> Hi,<br/> please check taskdeployment tap in the plc device,<br/> you need to split all I/O's according to their task.<br/> Ethercat IO need to be updatet in the Ethercat Task context and modbus IO's need to be updated in the modbus task context.<br/> Set the IO update task in the plc setting to Ethercat<br/> and in the modbus master you need to specify the modbus task as update task for the modbus io's<br/> Then it will work.<br/> cu</p> </blockquote> <p>hi, Edwin<br/> thanks your reply.<br/> I had check IO updating by corresponding task, pls refer to attached picture. I had test it, it was not working as expecting.<br/> do I need any extra setting?</p> <p>thanks a lot...</p> <p><img alt="IMG: tasks specify.JPG" rel="nofollow" src="https://forum.codesys.com//download/file.php?id=468"/></p></div>

2020-02-27T13:57:23.889000Z2020-02-27T13:57:23.889000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.comcede5b15253a3402534228a60fbeb1a23d7bbaff

<div class="markdown_content"><p>Hi,</p> <p>please check taskdeployment tap in the plc device,<br/> you need to split all I/O's according to their task.<br/> Ethercat IO need to be updatet in the Ethercat Task context and modbus IO's need to be updated in the modbus task context.<br/> Set the IO update task in the plc setting to Ethercat<br/> and in the modbus master you need to specify the modbus task as update task for the modbus io's<br/> Then it will work.<br/> cu</p></div>

2020-02-27T13:57:23.682000Z2020-02-27T13:57:23.682000Zlistenyanghttps://forge.codesys.com/u/listenyang/https://forge.codesys.com7476e12b8a79c13d3036e571ca2b402e824efe27

<div class="markdown_content"><p>hello, all</p> <p>I am facing a problem in v3.5, there is a motor driver connect via EtherCAT slave, and one remote plc via Modbus TCP Slave.<br/> the EtherCAT is for driving the motor, and Modbus TCP is only I/O exchanging with CoDeSys v3.5.<br/> problem is:<br/> The motor was not running smoothly enough(rotating fastly or reversely suddenly), it seems motor was lost some pulses/step sometimes, if I delete the Modbus TCP slave, motor was runing perfectly, EtherCAT seems was affected by Modbus TCP, when I changed Modbus TCP polling cycle time, motor running better.</p> <p>can any one gives any tips? I really need some help from you guys now. </p> <p>thanks a lot.</p></div>