Thanks Bill (widelto). I can see what you’re doing.
I'd question the way the event task is instigated though, as the tasks are called from somewhere in continuous task so are influenced by scan time maybe up to 2-3mS? Obviously not an issue for you as you are at 90m/min with +/- 1mm.
I wondering if there is a better / continuously monitored way to initiate motion tasks. There are lots of options predominantly associated with motion control features (see attached screen dump)
Basic help states: For more detailed information on planning specific types of event tasks, see Identifying and Managing Tasks, or refer to Chapter 2 in your Logix Controllers Common Procedures Manual (publication 1756-PM001).
So more reading.
Thanks again Bill.
69FIREBIRD:
Sorry for my late answer, my events are triggered (event instruction only).
My approach is like this:
First of all, the dieset must start always from the same place.
In my case I always cut at the same place.
I use MAW(1) to watch where to start the dieset, for instance, If my pipe is 6 meter long and my cut is at 600 mm from home, I must start my dieset at 5400 mm this distance is measure thru the MAW.
When the dieset is started, I use a MAG to sync dieset with pipe, you can use profiles or use fixed accel, when dieset is moving use another MAW(2) to get distance where cut is going to take place.
When you get distance to cut on the dieset then I set my first event task, make the cut and them set next event task to go to home, disarm MAW(1), then move dieset back as fast as possible using a MAM, use a profile to stop always at the same time.
The everything starts once again.
