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.
I’ve been having problems recently with the images download by ekos from my sv305. The files appear and logging doesn’t appear to indicate any problems however while the files are the right size they seem to have null (I’m sort of assuming this as the statistics say min/max as being 0) data image.
I’ve tried shutdown/power down/boot and altering the indi driver settings but with no luck. I’ve swapped the usb connections around (all but a usb memory stick was off a powered usb hub now that is as well)
Now AstroDMx seems to be able to use the camera (yes I’ve done a shutdown etc between just in case).
Finally at my wits end late last night I was trying AstroDMx and tried auto gain rather than auto exposure (which was very noisy) and everything became clear with the stars showing nicely. Switched over to ekos and suddenly that was working fine. Even after yet another power cycle.
Anyone hit something similar?
Is Astrodmx somehow changing some state in the sv305 which survives power cycles? Or has some problem been introduced in the last few days as things were working fine previously?
I'm working on the temperature control on the SV405CC, and I have a question.
The SVBony SDK controls for camera cooling are somewhat different from the INDI default controls.
SVBony provides :
- Powering the cooler ON/OFF
- Setting the cooler power (0 - 100%)
- Reading the current temperature
- Setting the target temperature
INDI provides :
- Setting the target temperature
- Setting the cooling/warming ramp
- Setting the temperature hysteresis
What should I do ?
- Try to wrap all the SVBony controls onto the INDI controls, and only them ?
- Try to mix the INDI Controls and the SVBony SDK, with extra controls ?
- Provide only the SVBony controls, as a proprietary panel, without the INDI default controls ?
Please notice that I don't have the camera yet (waiting for delivery), so, I'm note able to see how the SDK controls really act.