Not connected, but found using: Scan for Devices
The problem is looking for a bug somewhere in CoDeSys in that, when the slave returns, the cyclic data exchange resumes, but the diagnostics do not update and the node continues to resulting off-line. it is not a problem with the PB master, but with its 3S/CoDeSys management. CoDeSys 3.5.19.20 runtime. Any ideas on how to fix it? Thank you.
The problem is looking for a bug somewhere in CoDeSys in that, when the slave returns, the cyclic data exchange resumes, but the diagnostics do not update and the node continues to resulting off-line. it is not a problem with the PB master, but with its 3S/CoDeSys management. CoDeSys 3.5.19.20 runtime. Any ideas on how to fix it? Thank you.
WHEREAS, I have already searched various posts and forums, where mostly there are few references and mostly geared toward integration in TwinCAT. I am looking for how to properly configure the EL6731 board as a DP master, (where I have its 3S license), with CoDeSys 3.5.19.x. I have three types of slaves, all integrated with their GSD descriptors. In the tab for the various slaves, I don't see options related to node restart on 'station return'. On the card manual, I read that for each slave I should...
How are the servo drives controlled? EtherCAT, step/dir pulses, other? CANOpen, 1 Mb/s, bus load 35%, cycle time 2ms. Another thought is that - if it's step/dir pulse based control - the pulses from the PLC to the drive are getting missed/lost at high frequencies? If that's the case then there would be multiple troubleshooting steps/corrections that could be investigated. Here, it seems to me that we are getting completely off track with the observed problem. You could try to create a simplified...
How are the servo drives controlled? EtherCAT, step/dir pulses, other? CANOpen, 1 Mb/s, bus load 35%, cycle time 2ms. Another thought is that - if it's step/dir pulse based control - the pulses from the PLC to the drive are getting missed/lost at high frequencies? If that's the case then there would be multiple troubleshooting steps/corrections that could be investigated. Here, it seems to me that we are getting completely off track with the observed problem. You could try to create a simplified...
Here is the archive of the simulation project: https://drive.google.com/file/d/1n74Qy-1yLPpI2OK4FaZO5q50y2uTa0Wr/view?usp=drive_link
No errors in any condition. The function terminate correctly with the 'done' bit. Now I leave the machine and I don't know when I will be there again. The assumption you made I had considered. The operational limits of the axis are all fit for purpose, and this function should operate virtually without even noticing the motion limits. In fact in practice with the axis at low speed the function corrects any numerical value of the position in the range 0 ... 360° without any problem whatsoever in a...