I manually focus with electronic motors using a B-mask. Normally I get very clean, text book like shapes--angled side spikes and a center spike that is centered to achieve focus. However, take a look at the attached image of my recent B-mask shape. You'll note the spikes are bent--or angled close to the star--almost segmented. Further out, the spikes are long and straight like they are supposed to be. Using the spikes close to the star makes focusing very difficult, as the base of the central spike is to the right, and the top of the central spike is to the left. And the side spikes are angled close to the star as well. Does anybody know what the problem is? I immediately thought of collimation, but the C11Edge holds collimation extremely well, and last week all was well. the scope is permanently mounted on concrete fittings and it remains perfectly level and PA does not change (much). I find it a bit perplexing that collimation would shift with the scope on the mount (mostly not being used as the weather is very poor.
I collected 500 20 sec lum subs to add to my RGB of NGC 5907, and I was amazed how good it came out--it certainly does not look like there is a collimation issue--stars are round and the details in the galaxy very nice for my sky. I attached a copy of an unprocessed screen stretch of the 494 20 sec sub stack. If collimation is off, it can't be by much.
The question is--can a very slight miscollimation cause the B-mask image to look as it does? If that is the case--it appears it is super sensitive and makes a premium method for checking collimation without having to actually get into checking collimation the old fashion way. Besides, it might be that visually collimation errors would be less noticeable than the b-mask for very small miscollimations.
But is it a collimation issue?
The other strange thing is Sub Frame Selector reports the FWHM value of this stack to be sub 1 arcsec (0.90 I think), which MUST be wrong. I checked the settings and they are correct. I expected SFS to report a FWHM of around 2.5


I collected 500 20 sec lum subs to add to my RGB of NGC 5907, and I was amazed how good it came out--it certainly does not look like there is a collimation issue--stars are round and the details in the galaxy very nice for my sky. I attached a copy of an unprocessed screen stretch of the 494 20 sec sub stack. If collimation is off, it can't be by much.
The question is--can a very slight miscollimation cause the B-mask image to look as it does? If that is the case--it appears it is super sensitive and makes a premium method for checking collimation without having to actually get into checking collimation the old fashion way. Besides, it might be that visually collimation errors would be less noticeable than the b-mask for very small miscollimations.
But is it a collimation issue?
The other strange thing is Sub Frame Selector reports the FWHM value of this stack to be sub 1 arcsec (0.90 I think), which MUST be wrong. I checked the settings and they are correct. I expected SFS to report a FWHM of around 2.5


