Thank you very much for posting the complete logs. They are very helpful. OK we have two separate problems going here:

Issue 1:
This log 20210225@232224.log shows the problem that I suspect is related to the filter wheel not being able to complete it's filter switch, and which we are working hopefully with Diffraction. That taking the filter wheel offline eliminates the lockup trying to take images. Apparently it has no problem selecting the G filter (used for the pointing exposure)

23:22:54 Doing auto-center...
23:22:54 (taking 30 sec. exposure, G filter, binning = 4)
[...]
23:23:05 Plate-solve pointing image.
23:23:05 1251 image stars found
23:23:06 1730 catalog stars found
23:23:07 Solved! 211 stars matched.
23:23:07 Average residual is 1.12 arcsec.
23:23:07 Pointing error is 0.217 arcmin @ angle 338.56
23:23:07 True focal length is 2563.6 mm.

but then switching from G to L it can't complete the exposure. Note that the filter switch happens when the exposure is started within MaxIm:

23:23:08 Switching from G to L filter for imaging
23:23:13 (taking 600 sec. exposure, L filter, binning = 1)
23:23:13 (using 8 MHz readout mode)
23:23:13 (starting [RBI] + exposure)
23:24:28 **Imaging error: **Exposure failed after being successfully started

Issue 2:
The log 20210225@011710.log which shows the out-of-range plate scale issue:

01:17:43 **Script Error (Tracking has been stopped)**
01:17:44 Source: PinPoint.Plate
01:17:44 Message: The value is out of range.: ArcsecPerPixelHoriz

Earlier in the log I note that, at least at the time this run was done, the plate scale was logged as zero!!!

01:17:22 Calculated unbinned plate scales (arcsec/pix): H = 0.00 V = 0.00
01:17:22 Calculated field of view (arcmin): H = 0.0 V = 0.0

This is really strange. In ACP, it is prohibited to enter a zero focal length (see screen shot below). PinPoint, when given a plate scale of zero, will report an "out of range" error for obvious reasons. Note that in the log 20210225@232224.log the plate scale is logged correctly

23:22:33 Calculated unbinned plate scales (arcsec/pix): H = 0.72 V = 0.72
23:22:33 Calculated field of view (arcmin): H = 49.4 V = 49.4

The plate scale is calculated from the Focal Length in ACP's Telescope settings, combined with the physical pixel size (in microns) that I read from the camera (via MaxIm). I'm betting that you have the Focal Length properly entered in ACP. This leaves only one possibility: In the run that failed for out of range, the camera reported 0 x 0 for the pixel size. I can't explain it any other way. Let's keep our eye on this. If needed I can add some logging to AcquireSupport to create a "smoking gun" on the pixel sizes coming from the camera. Also please be certain that you have the latest factory recommended drivers for the camera when used with MaxIm.

Snap1.jpg