Excellent video Shane. I've done quite a bit with MAOC's, but one issue with speed compensation I've not been able to overcome. For Position-Position, Latch/Unlatch, it appears the speed compensation calculates an internal position offset that's added to the Latch/Unlatch positions. That works great unless your latch/unlatch are on the CAM boundaries. If in your example, you have a latch at position 0, and add speed comp to the latch (leading edge), any value that's subtracted from the 0 position puts it outside the boundary of the CAM. In my testing, Ive found the MAOC then completely ignores this particular output for that range. So if you have for example latch/unlatch of 0 and .5, and your leading edge speed comp is calculated based on time/velocity to .1, the output won't fire at -.1 and ignores it altogether. I was hoping speed comp would wrap around. Do you know any workaround for this behavior?
@@ShaneWelcher Okay, understood. In this case I'm testing with a purely virtual axis. But it does the same with a physical axis. CUP set to 2ms. In your example, with a latch set at 0, does any latch speed compensation applied still fire that output? It doesn't for me. The routine is motion exception, running about 180 useconds. The speed of the axis is 160 units/sec.
Join Us & Learn More:
allen-bradley-plc-training.teachable.com
Excellent video Shane. I've done quite a bit with MAOC's, but one issue with speed compensation I've not been able to overcome. For Position-Position, Latch/Unlatch, it appears the speed compensation calculates an internal position offset that's added to the Latch/Unlatch positions. That works great unless your latch/unlatch are on the CAM boundaries. If in your example, you have a latch at position 0, and add speed comp to the latch (leading edge), any value that's subtracted from the 0 position puts it outside the boundary of the CAM. In my testing, Ive found the MAOC then completely ignores this particular output for that range. So if you have for example latch/unlatch of 0 and .5, and your leading edge speed comp is calculated based on time/velocity to .1, the output won't fire at -.1 and ignores it altogether. I was hoping speed comp would wrap around. Do you know any workaround for this behavior?
Honestly I would have to look at the machine design and the program to verify the way your setup is because of multiple reasons.
One being timing
@@ShaneWelcher Okay, understood. In this case I'm testing with a purely virtual axis. But it does the same with a physical axis. CUP set to 2ms. In your example, with a latch set at 0, does any latch speed compensation applied still fire that output? It doesn't for me. The routine is motion exception, running about 180 useconds. The speed of the axis is 160 units/sec.
@@robertmee2
The problem you are seeing is most likely caused by it being a virtual axis which creates timing issues.
I used a real would servo
i m was not hard ware plc and servo . I can learning servo course.
Of course, Every day is an opportunity to learn.