So.. it is a lovely clear night, with cool temperatures, and I had some mosquito repellent.
It occurred to me... maybe the problem with the rotator was just the number of steps that it had taken... it was showing some 18,000. It's a rotator, right, so, it could show a million, it just keeps goin' round and round. So I ran it down to zero, and set up to try my sequence again. This time I spent some time to get the scope aligned, (not polar aligned, which I just can't do here in my back yard because the trees block my view of the celestial horizon), just a regular two star alignment with a calibration star or two, maybe.
I had high hopes that setting the rotator's steps back down to a low number would fix the issue I'd been having. Alas, it did not. On the bright side, however, I think I have all the logs that a developer could want.
The SGP Log shows the proper error at, for example:
https://drive.google.com/open?id=0B8WLV-uvuJEObHI3WWdvUEp5NzQ
[9/10/2016 9:11:39 PM] [DEBUG] [Telescope Thread] ASCOM Rotator: Error in Move(abs) : MoveAbsolute set - '-134298.2' is an invalid value. The valid range is: 0 to 360. (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException: MoveAbsolute set - '-134298.2' is an invalid value. The valid range is: 0 to 360.
<<
The MoonLite Log shows no error that I noticed after a breif inspection, but I'm not an ASCOM Developer...
https://drive.google.com/open?id=0B8WLV-uvuJEONDdKdVItTmF2Q2s
I hope this helps.
Clear Skies,
Karl