@Jasem: if I remember well it already happened. is there something I should change in the configuration of the driver?
@Jean-Louis: where is your Talon6 observatory based?
If you need assistance in configuring the driver don't hesitate to ask.
the parameters are coded in the WeatherWatcher driver so you cannot customize in the way you need.
But it should not be difficult to abstract the name of the parameters reading them from the driver configuration or an external file.
I've quickly checked in the source code, the parent classes of the driver doesn't make use of any of the parameter names in WW (e.g. 'wind' or 'temperature') so changing them dynamically should not harm the rest of the environment.
About the 'light'/ 'wind' hack: be aware that some of these parameters (marked as critical) are used to trigger actions like shutting down the observatory if the parameter is in a danger range. As far as i know these are: temp, wind, rain and weather forecast. I would not recommend but in case I would rather use 'wind gust' as fake parameter.
not exactly a Dome but a Roll Off Roof. Domes and Roofs share the same base class but Roofs have only Park / Unpark (i.e. open / close) features.
If this is enough for a test, happy to help.
I've a Pegasus Power Box v2 too if you need additional tests.
Where MW4 can be downloaded? And can it be installed alongside MW3?
But since this topic was started I didn't have the chance to test it.
the only setting I ever changed are the coordinates in site management tab. The driver worked fine for me since the beginning and never had an issue.
Chose to have 'mount updates ekos' with the only reason that the model is built inside the mount and I didn't want any external input affecting that.
But first of all download MountWizzard3 by Micheal (who usually reads this forum), it's a great software that will help you in polar alignment and building a model for your mount . Since you have a mount that allows for autoguiding I wouldn' t spend a minute trying to guide.
thank you for sharing your experience. And I understand that given the constraint you have this is an optimal solution.
Luckily I will leave the camera soon under a Bortle 2/3 sky and do not have issue guiding more than 5 min.
When you say that CN recommends "mean ADU should be 800 - 1100 ADUs above the dark ADUs" you mean a sky background area of your light frame not the dark frame mean ADU, right? else you are not taking in account light pollution.
El Corazon wrote: I am imaging under Bortle 8/9 conditions and for those conditions gain 240, offset 40 and exposure times of 8s for L, 20s for R, G, B, 120s for Ha, 60s for O3, 120s (gain 270!) for S2 seem to work best for me.
above gain 200 the read noise doesn't decrease any further while the full well capacity and thus dynamic range are dropping linearly. I do not see the advantage* of going at such high gains given the fact that moreover you are forced to do shorter frames that in the overall integration increase the read noise.
For my first tries (Bortle 8/9) I'm settling at 75/12 for LRGB and 200/50 for SHO adjust time according to saturation.
(*) Unless you are using lucky imaging or want better guiding.