This problem has just shown up. When ACP calls for an autofocus, the subframe in focusmax is set at x = -16, y = -16, w = 1, h = 1. And, of course, no stars show up, so focus fails. How do I fix this?
Printable View
This problem has just shown up. When ACP calls for an autofocus, the subframe in focusmax is set at x = -16, y = -16, w = 1, h = 1. And, of course, no stars show up, so focus fails. How do I fix this?
which version of FM do you have, I think ACP just calls the focus method in FM and that is it
I have version 3.7.0.72. It has been working up until tonight. Then it started with this odd behavior.
hmm, not sure, I am using ver 4 so don't have 3 anymore to look at but another observatory does
I assume the subframe is not set it Maxim DL
Richard,
So the problem could be in FocusMax, ACP or MaxIm. Dean mentioned Maxim - look at the Expose tab on the Camera Control window. There is a "subframe" section - The checkbox can be checked or not, but make sure you click on the "expand" icon to ensure the camera CCD is not otherwise restricted.
In FocusMax, on the Setup tab, set the frame width to something like 100, then go to Open/Options, and in the Focus section, uncheck Enable auto subframe width.
See what happens now. if there's still a problem I would suspect some glitch in ACP.
Hi Dick, that is what I was thinking. ACP calls the AutoFocus method and I am not sure if AutoFocus is inside ACP or the object.AutoFocus when the object is the connection to FM. But yes since it just started I suspect a subframe setting is the cause Thanks for the FocusMax check, 4 does not have this or I have not seen it yet
Dick, can you email me at sharpless281@gmail.com, I have a script question
I'll go along with the others and only add that that subframe setting is really bizarre. ACP doesn't fiddle with the subframe in MaxIm during a run unless there is a #subframe directive in the plan, and in that case it sets it, takes the image(s) then restores it to fullframe. It also restores to fullframe at the beginning of a run, so I'm guessing this is happening in FocusMax.
I have been able to get it working again by rebooting the PC. If I shut down FocusMax and then restart it without rebooting, the problem returns. I will try Dick Berg's suggestion tonight.
I just looked at my setup and it was already set exactly as Dick Berg had suggested.
I'll post again if it happens again.