Hi Paul, I hope this will help you:
1) You cannot use different filter setting for taking lights and flats. This will result in a different "light profile", for example the UHC filter will cut some part of the light spectrum and resulting flat cannot be used for calibration of lights, that are taken without such filter.
2) Taking sky flats in Ekos is really easy. You just sset target ADU with some +- variance and the software will do all work automatically. You just need to take exposures during dawn or dusk, on the opposite site where is sun. And the sky needs to be clear, without clouds. You can start with exposures 10 - 20 minutes after sun is under horizont. If exposures are short, you will skip and wait few more minutes and repeat this steps until you get exposures in range you want, e.g.: 1-3 seconds. Once ADU are not in the specified range, ekos will automatically calculate new exposure time. And this will repeat until you get enough exposures. I am taking 12-20 exposures.
I hope I wrote it understandable
Hi Paul, here are some practical experience notes:
1) I am using GAIN 120 and OFFSET 8, so the default values. I don't see any benefit in using higher OFFSET.
2) I am taking sky-flats, with typical exposure time 1-2 seconds. These sky-flats I calibrate with darks with same exposure time. I am also using flat tool in Ekos, my setting is 32000 +- 2000 ADU (histogram peak is in the middle).
3) I have set the white balance to 50 for both colors.
4) About the temperature, if |i understand it correctly, you want to maintain the temperature as low as possible? If yes, this not a good approach, as you need to have the same temperature for all you lights and their darks; flats and their darks respectively. I am using -10°C as target temperature for all my exposures and it is working well.
Hi Jasem, I like this idea.Here are some thoughts:
The Ekos icon has been gone after I have removed those three folders. I am sure it was there before this step.
Thank you Rob, so for me it means that it is possible to implement this function. Camera with its own mechanical shutter will benefit from this function. But for cameras without mechanical shutter (and most popular cameras don't have it) it will be needed to have specialized device, that will play role of a mechanical shutter in the optical path. This is a product, that is not on the market now, or at least I don't know if it exist.
Ok, I have deleted those 3 folders and the icon for Ekos in KStars is gone Now I am trying to build most recent version.
I would like to have this feature once the sky will be full of artificial satellites.
Motivation: Megaconstellations like Starlink will soon complicate our hobby. It is already complicating it now, but we still can get rid of the satellite traces during stacking. But once there will be 10k+ satellites, it will be really challenging for the rejection algorithms and HW.
Possible solution: A constantly running process, that will automatically shut mechanical shutter of the camera, before a satellite enters Field of view and opens it again when the satellite leaves the FoV. For this to work, a part of the imaging rig must be a scope/camera that has wider FoV. It can be guiding scope/camera or a separate scope/camera setup. This scope/camera will point to the same location as the main imaging scope/camera. Image acquisition speed needs to be quite fast, e.g. 1-10 fps. Every frame will be analyzed in real time and if there is a trace from incomming satellite, it will calculate in which time the satellite will cross (enters and leaves) the FoV of the main imaging scope/camera. During this time, the shutter will be closed and no satellite's trace will be recorded.
Another possible way, how to know, when a satellite will cross the FoV is to have some updated list of possitions of the satellites. I know that this exist, but can not remember the name right now. For this option you don't need wide field scope/camera, but you need online connection to the internet (or at least possibility to download the most recent "satellite list" and then use it offline) is needed.
Yes Eric, I am using this script: github.com/rlancaste/AstroPi3/blob/maste...upAstroRaspbianPi.sh
Can you please help me identify which folder can be removed after successfull install of INDI and KStars?
Simple question: Is there a safe way how to clean "build" folder after the build is successful and installed? I am not a Linux guru, so sorry for this maybe simple question.
It looks like a serious scientific instrument. I also like his products, I am using AF3.
I don't know if it will help, but you can try to change the SEP Profile. These options are there:
You mean the dropdown list of all temperature sensors? That will be great
Well, I didn't started development of the driver, I am not even a developer. So this could be the way, how to make it easier, just to modify existing Arduino code to provide the data which existing driver needs. Thanks for this info.