Thank you for showing your INDI panel. Are you sure that that is what the 12 bit stretch-option is doing?
I believe the darker appearance of your guiding images might be due to a difference in stretching, that is affecting the apparent brightness of the image.
If I press the toggle stretch button in the guding module of Ekos the images get much darke, the background is basically black, and only the brighter stars are seen as pinpoints of light. This is different from the mangled images I have been talking about. They too do have the blacker background, but as one can see on my previously posted screenshot from within Ekos, most of the stars remain visible. But, instead of being pinpoints of white, they are big fat white blobs. just as big as can be seen in the other screenshot, although devoid of any radial gradient to the whiteness.
I do not know whether this at all matters for my guiding. I have not been able to notice any dips in guiding precision occuring when the images look like that. Though, overall, I do have pretty poor guiding performance with my recently acquired EQ6-R( about 1.5 arcseconds with lots of horrible spikes at irregular intervals and in directions). I do believe this is due to mechanical issues, and has nothing to do with the svbony camera, I simply am curious as to why the occasional image has that freaky appearance.
was just having a quick look through the sv305 and notice in the disconnect routine the camera mutex lock is commented out. Is this correct. I also noticed there’s a TODO in the abortexposure routine, is something missing here? I’ve had a couple of times where trying to stop exposures seems to result in problems though I’m not sure that was the sv305 camera or sony. Hmm the abort property is also commented out earlier so I (not having read the docs ) probably means the routines not used.
Last edit: 5 months 2 weeks ago by Nigel Dunmore. Reason: property commented out in code
<< in the disconnect routine the camera mutex lock is commented out >>
It has been done by purpose : If something goes wrong, and the mutex stay locked, we should be able to stop de camera.
But you're right, the "unlock" line should be commented as well.
<< I also noticed there’s a TODO in the abortexposure routine >>
The previous SVBony SDK provided an abort method, but it disappeared in the new one.
I tried a couple different solutions (stopping the camera, disconnecting, etc.), but nothing worked.
So, I disabled the "CCD_CAN_ABORT", leaving the code in, and waiting for a miracle to happen
During last nights messing around - not really clear due to high level cloud, nearly full moon and the usual light pollution- I thought I would take a set of images using my guide scope (an sv106) with the sv305 and see what happens over different exposure times. Basically I’m a beginner trying to get a handle on what happens when.
This was unguided ( I did try having it guiding but for some reason I couldn’t image and guide with the same camera doh ) and poorly polar aligned.
The images showed stars quite happily at 1 sec, 10, 20 and 30 but at 40 they seemed to become blurry and above that up to at least 3 minutes the images seemed to be blank.
When guiding with a color camera, I usually use bin 2x2, to avoid debayer artifacts.
The SV305 sensor (imx290) has a pretty small pitch (2.9um). Unless you image at very long focal length, I think you will get better results, with better SNR.
ok can ignore my question about the disappearing stars. Basically it appears that the sky was so bright that after 40 seconds the image was becoming over-exposed. At least that seems to be what I’m seeing in fits liberator. Next time I will check the histogram as I could see things move to the right as the exposure time increased until things basically dropped off the end.