Hello Everyone!
I have a program that has to be very efficient for cycle time so the majority of my moves are Joint CNT100.
At a couple points in my program the CNT motion option on a move command, before the following lines that execute I/O, seems to be allowing the I/O commands to fire much to soon, in one of the cases before the motion is hardly even started it seems. This is obviously bad when you want I/O based actions to occur near to certain positions or at certain times. How can I get around this?
I am aware that a CNT motion option looks ahead at the next point to make more efficient moves/ paths but I had no idea, or have any idea why you would want it too, also execute other types of commands as well in advance. It seems to me that CNT motion option is not actually looking at positions for better efficiency but is rather just an (for lack of better terms) time modifier that just decrease the amount of time dedicated to the move its attached to and moves on to the next line after that amount of time elapses.
Also I have tried just adding a wait command after the Move command and before the I/O which does work but doesn't provide an easily predictable point at which the I/O will execute.
Thanks!