The reason there isn't much information there for SLC/MicroLogix is that controlling the speed or the stop/start control of a drive using anything but cyclic I/O connections from a ControlLogix or CompactLogix family controller is not a recommended method.
To my continuing frustration, though, a lot of people want to do it. And a lot of those folks are novice users of the MicroLogix or PowerFlex or of messaging logic.
I am personally reluctant to provide advice on the topic. I once wrote a very good PowerFlex 700 and SLC-5/05 control routine for a customer who had already installed the hardware and had used SLC-5/05 instead of ControlLogix, against my direct advice. As a condition of fixing his program, I made him promise not to build another one like it, because it was likely to have problems when the system was expanded in the future.
The program worked so well they made it their standard architecture. And yes, they have exactly the problems I predicted, but now they have them in sites all over the country.
Let's skip to the end and I can describe some of the things that go wrong:
1. The next design uses more drives and the logic isn't corrected to handle the message queue correctly, resulting in "hung up" messages and drive timeouts.
2. The wrong timer settings are put into the timer logic, resulting in heavy loads on the controller's network port and a slowdown of the HMI traffic, resulting in apparent degradation of the HMI performance, which folks proceed to waste a lot of time attempting to troubleshoot from the HMI side.
3. The control system gets connected to an enterprise network with multiple RSLinx/RSWho browsing sessions open on engineering workstations, which use up all the unused CIP connections for the controller. When a drive powers down, an RSLinx session grabs the last remaining CIP connection and when the drive powers back up, it can't connect over Ethernet to the MicroLogix.
None of those would happen with a ControlLogix, because they are built to do cyclic I/O connections as part of the Ethernet firmware, and all the connection establishment, timing, and management is done by the Ethernet module, not by the user logic.
TL;DR I am a grumpy old man.