I'm using a color cmos so I'm not really concerned about the gain issue you mentioned.
Anyway, having a different gain setting per sequence wouldn't increase time to take calibration frames too much? that could be automated of course but storage / download time would increase.
Thanks, I read the thread (well ,not all 188 posts...), argumentations are solid but the data presented are mainly empirical. There's another useful thread on CN that discuss the theory behind the calculations:
El Corazon wrote: Here is another informative (and at times spirited) discussion on the same topic. That one also addresses the effect of gain.
Do you have an excel file with simulations of suggested exposure times to share? I would like to compare to mine
'Preliminary steps' are unpark, focus, calibrate, cool camera and guide?
When taking a flat, focus of course should be skipped and calibration as well. But you say that you can untick those parameters in the configuration. I thought that those parameters were session level parameters (valid for all sequences ) and not sequence level parameters that you can customize for each sequence.
I meant bandwidth, sorry. But the point was that for 'no filter' I would not assume 300nm bandwidth but a greater value as the SQM meter collects light on a wider range as far as i know.
I wanted to check if my noise calculation were correct so adapted my own spreadsheet to match the data presented in the first video.
Results are very similar, the only difference being the wavelength at which SQM is measured: reading the SQM documentation is should be about 500nm but to match the data in the video 300nm is to be used (well these data are not in the video but the video references to tools.sharpcap.co.uk/ ). Anyone have the same difference?
Too bad that the video ended before gain was taken into account. I have many doubts how to treat it.
hi, good to hear that everything is working fine.
I only tried shutdown when sequence was running using the scheduler. That's where it is useful to me.
Anyway it is quite easy to test: just lower any of the critical threshold to a Danger / Red level even if it doesn't make sense. E.g. if ambient temp is 10 degrees set the upper OK to a lower value, say 5 deg. Light will be immediately red and shutdown will be triggered.
Remember that only critical parameters are used for shutdown or other operations inside Ekos. So forecast, cloud or other parameters are for your visualization only; and you already have the SOLO display for that.
Only wind, temp and rain are set on my configuration.
I wrote an help file for this Weather Watcher driver (at least what I get of it), hopefully Jasem will add it to documentation. Even though i think we are the only 2 using it...
Think you have to restart both the drivers and kstars.
weather watcher is meant to work on different weather providers so keywords that the driver reads have to match exactly.
In you SOLO the parameters are:
cwinfo=Serial: 1319, FW: 5.6
cwinfo=Serial: 1319, FW: 5.6
So, in 'options' you should enter 'rain' instead of 'precip' and 'temp' instead of 'temperature'. Wind is ok.