Hello Guys!
I read this thread with interest, and thought, maybe my problem fits here...
After fullmoon phase and lots of heavy thunderstorms, yesterday was a night to get my setup out for a night. I wanted to try how guiding with guiding cam and KStars is working. So far i was satisfied with the results at first. So i set up the system to capture 50 lights with 5 minutes exposure time, guiding and dithering. I kept checking the system for the first 5 pictures and all seemed to work well.
So i went to bed and set the alarm clock to 0400.
Then i saw, that the system stopped making pictures after the 12th picture.
When trying to find out why that is so, the only thing that was "wrong" was the work, the guiding module made.
Too bad i did only check the ccd in the log so there is nothing of interrest there...
So what happened ist at first, the "info box" of the guiding module did like PICTURE DONE - DITHERING - DITHERING COMPLETE - PICTURE and so on.
At one point, it did no dithering anymore, and so there came no TAKE PICTURE command anymore.
so it seems that the module taking photos was just waiting for the guiding module to dither, which not happened anymore...
There is also no error message at all.
I have to say additionally, that there were some situations where the guide star was lost and found again, what worked quite well
Now, it was no drama this night, because of different problems anyway. (guiding not working as good as with the mgen, lines instead of points in all four corners...)
I thought OK, lets use the last dark hour for darks, so i first took some flats, and the set up for the darks.
AND THERE A OLD WELL KNOWN PROBLEM OCCURED!
When i took the first darkframe i waited, to see if it works allright and when the picture came in, it was NO DARK!
It was the picture that was taken BEFORE, the last Flatframe.
I thought that this problem, where the system 'forgets" to count pictures taken with the cam, was fixed allready?
So the question is, can that have something to do with the system stopping taking pictures?
Or is the fault somewhere else?
Attached the log though it will not help much.
And a burning question for a Linux-Noob: I did not update for a while, so i am on 2.9.4 still...
What was there to do to get the update?
Only the "sudo get update"?
I am a bit careful with updating now, since the last time i updatet, the whole system was not working well anymore...
Thanks for your kind help
cheers Niki