Help with Logix 5000 motion camming / jerkiness

NO,NO,NO!!!!!
Ethernet encoders should not be used for any demanding motion control. This application seems to be like a flying shear where one actuator must accelerate to match the speed of a master actuator/encoder. The master encoder should have very fine resolution and be deterministic. Ethernet is not deterministic nor does this encoder seem to have enough encoder counts per revolution. This makes it difficult to computer an accurate master speed. The master speed must be accurate because it is used as the target speed for the slave axis. If the master speed is not accurate then it is impossible to use the derivative gain on the slave axis. It is also impossible to compute a good feed forward for the slave or acceleration feed forward.

After a few days I finally figured out that the feed forwards in the axis setup were at 100%
The velocity feed forward should be about 100% on Rockwell motion controllers. I know, remember I wrote the code for the HYD02 and M02AS. The problem is what I described above. The master velocity is for the velocity feed forward for the slave. If the master velocity resolution is as coarse as shown above then the slave velocity feed forward will be just as coarse.
 
The resolution on the encoder is terrible. Crank it to 4x quadrature if not using it already.
One should always be mindful of how many counts they get per cycle. If there are 100 counts +/- 1 that is not a big problem whereas 2 counts +/- 1 is a 50% change. Even so, how much jitter will be caused by the Ethernet?

I always tell our customers to push our encoder inputs to the limit. We can easily handle 8 million counts or more. That means if the same time is 1 millisecond there are 8000 counts per millisecond on the average. The sampling should result in 8000 counts +/- 1 which is pretty good.

However, all this can be ruined if the master encoder is connected to feed chain driven by a sprocket. Sprockets to not pull a consistent rate so they will also cause sample jitter.
 
All evidence (and Peter) point to the encoder. Depending on your application, you might be able to fudge it, but a sinusoidal encoder would fix it right.
 

Similar Topics

Hi all, Has anyone found a quick way to patch in the functionality of the Windows help files in Windows 10 so it can be utilized in Logix 5000?
Replies
0
Views
595
Hello Everyone, I have tried to access the help function from my RSLogix 5000 but everytime I select a function block on the PLC rung and press...
Replies
3
Views
1,222
I’m working with indirect addressing and trying to make an HMI where each Rectangle Object has a tag of “A[0-127]” with a correlating Push Button...
Replies
15
Views
4,142
I have been tasked to upgrade some SquareD PLCs at our plant. I have done several of these upgrades without any issues. However, I have now met my...
Replies
4
Views
2,407
Hi There, When i did FRD instruction in SLC 500 its working, when i try to simulate in RSLogix 5000 same way as i did in SLC 500 which is not...
Replies
14
Views
2,651
Back
Top Bottom