This issue, examples of which periodically come up on various forums, is a tough one to understand, and does create tension between application developers (like me) and their users (like you). This particular one is going on here, on the MaxIm forum, and the LX200GPS forum. In order to address this in a generic way, I wrote an essay which hopefully explains the issue, and why application developers just can't be paying attention to (or altering) timing of their calls to the standard driver functions to avoid bugs in the driver and or the device (mount) hardware.
It's posted as a Frequently Asked Question on the ASCOM site now. If you feel it can be clarified/improved, please feel free to post back here and I'll do my best to make it clearer:
Why Can't You Just Add Logic to Your Program to Compensate For My Device's Problem?