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.
yes the camera was probably a bit out of focus as it was at a setting for a couple of weeks ago. It could also have been down to the misty clouds or the moon as usually the snr is in the hundreds.
The sv106 with its helical focuser seems rather difficult to focus. I’ve tried using astrodmx as it gives quite rapid feedback. Do you have any suggestions about what could help?
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.
Rookie mistake
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 don't use this feature. In my mind, it's the wrong way to go. The settings should be stored in the client software, not at low level, or you may experience
the issue you just discovered.
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.
First implement and release the INDI control, then implement the SVBONY control. Or vice versa. Why not implement it in whichever way can be released sooner?
I too am waiting for SV405CC to ship, and SVBONY tells me it will ship at the end of this month.
Hopefully the SV405CC will arrive in your hands soon.
are you saying the settings are stored in the camera and retained through power cycles?
That sounds a rather pointless and error prone thing for them to decide to do. Would have thought it would be cheaper/easier and thus more profitable to leave it to a client to set.
Is there some form of reset to defaults call that could be made when the indi driver is initialised otherwise people are just going to keep hitting what seems like random errors?
INDI has CoolerSP (Cooler ON / OFF) control. You can also add your own property for setting the cooler power. I presume there is "automatic" mode when the power is set automatically, and another where it is manual. You can also add another switch for that.
<< Is there some form of reset to defaults call that could be made when the indi driver is initialised otherwise people are just going to keep hitting what seems like random errors? >>
I don't know yet. I have to explore the APIs deeper.