AXFOLLOW

[Evilbeard]

Ok, I'm making a system for tracking on the edge of a web of film. I have an ultrasonic sensor that gives me the direction I need to go. I have two axes. One for a carriage near the sensor, and one for the end of the machine. When the program determines that we need to move in a direction, I have it using AXVEL with instantaneous acceleration/deceleration. If I attempt to clone that axis for the end of the machine axis by using AXFOLLOW, it uses the default accel/decel parameters that are setup in the AXCONFIG for the second axis. The first axis accelerates and decelerates instantaneously, while the follower axis accel/decels with the standard trapezoid.

Is there a way to make this work, or do I simply have to have two AXVEL instructions (one for each axis) that operate simultaneously?

Basically, I need the axes to be identical (always in the same position) as the machine runs, so that the punches/attachements are in the proper position of the web, and that the finished product accumulates properly on the end of the machine.

[BobO]

Following infinite accel/decel is probably never going to work well, so yeah, I'd probably just use a second AXVEL. You do run the risk of them getting off by small numbers of counts, which is what AXFOLLOW is designed to prevent, but if you do everything to both axes on the same scan, they ought to be the same.

[Evilbeard]

Following infinite accel/decel is probably never going to work well, so yeah, I'd probably just use a second AXVEL. You do run the risk of them getting off by small numbers of counts, which is what AXFOLLOW is designed to prevent, but if you do everything to both axes on the same scan, they ought to be the same.

I'm not working with a precise enough operation to have a few counts cause problems, though over an extended period of time, I suppose this could be an issue if the gap continues to grow.

[BobO]

Following infinite accel/decel is probably never going to work well, so yeah, I'd probably just use a second AXVEL. You do run the risk of them getting off by small numbers of counts, which is what AXFOLLOW is designed to prevent, but if you do everything to both axes on the same scan, they ought to be the same.

Shouldn't be cumulative.