I ran last night on the same target VdB152. Here are the results.
20180914@031507.log - Looks like you killed the run during the autofocus after it figured out the rotator offset

03:16:15 Imager sky position angle is 242.8 deg.
03:16:15 Rotator mech. position angle is 154.8 deg.
03:16:15 Within max error tolerance, no re-slew needed.
03:16:15 PA error of 165.2 deg. detected. Correcting...
03:16:15 Start rotate to PA 48.0 deg (raw rotator angle 320.0)
03:16:15 (wait for rotator)
03:18:20 (rotation complete)
...
03:19:36 20:19:36 ** Starting Near Focus **
03:19:45 20:19:45 Pos., HFD, MeanFocus, X, Y, Flux, Pixel, Count
03:19:45 20:19:45 66527, 04.51, 66240, 2922, 1301, 250, 1014, 1
03:19:52 **Script Error**
03:19:53 Source: ACP
03:19:53 Message: The script was aborted.
03:19:53 Location: line 1433 column 25.

20180914@032015.log - Guiding problems but the rotator is behaving, assuming you requested 48 degrees #posang 48 in your Plan.

03:26:07 Imager sky position angle is 47.9 deg.
03:26:07 Rotator mech. position angle is 320.0 deg.

However

03:26:08 Switching from L to H filter for imaging
03:26:09 (take guider image at initial interval 5 sec)
03:26:24 (guide star SNR=very high X=266 Y=398)
03:26:24 (first exposure estimate 3 sec)
03:26:29 (guide star SNR=very high X=266 Y=398)
03:26:29 (final exposure for guiding 3 sec)
03:26:34 (guide star SNR=very high X=266 Y=398)
03:26:35 PA=48 (off-axis guider @ 45.4 deg)
03:26:35 Guide angle is 93.3 deg.
03:28:28 **Guider unexpectedly stopped while waiting for measurement

This says you had a very bright guide star in the guider. Why it would not start guiding ????? You mentioned that the guider went off the side? This says that guiding never even got started, it could not even measure the deviation (guide error). I will continue to analyze your other logs.

20180914@033356.log - Another kill during AutoFocus

03:35:19 20:35:18 Moving to: 65045
03:35:31 20:35:31 Pos., HFD, X, Y, Flux, Pixel, Count
03:35:31 **Script Error**
03:35:31 20:35:31 65045, 04.87, 1248, 2381, 75, 1035, 1
03:35:32 Source: ACP
03:35:32 Message: The script was aborted.
03:35:32 Location: line 1433 column 25.
03:35:32 20:35:32 Moving to: 62373
03:35:32 20:35:32 Stopping operation: FocusMax is being terminated

20180914@033552.log - The guider started successfully but it looks like it is not guiding with the correct polarity or calibration.

03:40:53 (take guider image at initial interval 5 sec)
03:41:08 (guide star SNR=very high X=268 Y=398)
03:41:08 (first exposure estimate 3 sec)
03:41:14 (guide star SNR=very high X=268 Y=398)
03:41:14 (final exposure for guiding 3 sec)
03:41:19 (guide star SNR=very high X=269 Y=398)
03:41:19 PA=48 (off-axis guider @ 45.4 deg)
03:41:19 Guide angle is 93.2 deg.
03:41:23 (autoguiding at 3.00 sec.)
...
03:41:23 (guided dither - moving guide star dx=0.8 dy=0.9 guider pixels
03:41:34 (ex=1.17 ey=0.28)
03:41:34 (guider error n/a or too high, try #1)
03:41:46 (ex=1.94 ey=0.41)
03:41:46 (guider error n/a or too high, try #2)
03:41:57 (ex=2.94 ey=1.73)
03:41:57 (guider error n/a or too high, try #3)
03:42:09 (ex=3.38 ey=4.37)
03:42:09 (guider error n/a or too high, try #4)
... killed at this point for guide star drift-off

6. Those subs turned out to be rotated from the original FOV from the earlier runs before the change was made in the Gemini setup. The stack from last night is angled about 45 degrees from what I set up in the script and from the image I sent you yesterday. there still appears to be an issue with the rotator I don't understand.
The logs indicate that the "script" (observing plan for VdB152 H3) has #posang 45 in it? That's the PA that ACP is rotating to anyway, and it is happy now!! Would you please check? Post the script/plan here as an attachment.


I am in the process of releasing a field test Scheduler, something I've been trying to do all week, and I really really want to get it done today. So depending on my time I may call you to look at your guider settings. Since you had it working before with ACP and since you are guiding OK in MaxIm a lot has to be right. But if you calibrated separately at some random PA in MaxIm then tried to run ACP that will always fail. You must calibrate using the CalibrateGuider script with the camera at 0PA and a bright star in the guider. That's the only way the scales and angles will be right. Recall that ACP, once calibrated, can guide all sky, all rotations, without re-calibrating. The easy way to get a star in the guider at 0PA is described here: