Let me preface this by pointing out my understanding of how this should work... When a exposure sequence of flats (with various filters) is initiated, the flat panel illumination will be set to the preset brightness level for the filter currently in use and the panel turned on before the exposures commence. With a desired ADU level set, test exposures will be made to determine the correct exposure, then the required number of flat frames taken. These steps are repeated until all the flats for the various filters are made.  (Not sure whether to expect the flat panel to be turned off between each filter and then back on after the brightness is set or just left on until the entire sequence is finished...)

I am building a flats panel using LEDs controlled by an Arduino using the Alnitak Generic Commands (Rev 44). It is just an illumination panel without a cover, a "Flat-Man" emulation. The Arduino program (based upon several previous designs published on the internet) appears to respond appropriately to the indi_flipflat driver when operated manually via the Main Control tab of the "Flip Man" tab in the Indi Control Panel window.  On/Off and brightness changes happen as expected. Filter brightness presets are reflected correctly in the log file.When a test exposure sequence is run (w/ CCD, filter wheel and telescope simulators along with the infi_flipflat driver) the debug files indicate filter changes initiate the appropriate brightness changes (according to the presets). Polling (1000ms setting) occurs with the appropriate responses being returned and the exposures are made after initial test exposures to achieve the selected ADU setting (set in the Calibration tab of the Capture Module). BUT the light panel is never turned on or off during the sequence.I

have attached an edited copy of the debug logfile. I have added some notes to it and cut out a lot of non-relevant entries.

Let me preface this by pointing out my understanding of how this should work... When a exposure sequence of flats (with various filters) is initiated, the flat panel illumination will be set to the preset brightness level for the filter currently in use and the panel turned on before the exposures commence. With a desired ADU level set, test exposures will be made to determine the correct exposure, then the required number of flat frames taken. These steps are repeated until all the flats for the various filters are made.  (Not sure whether to expect the flat panel to be turned off between each filter and then back on after the brightness is set or just left on until the entire sequence is finished...)

I am building a flats panel using LEDs controlled by an Arduino using the Alnitak Generic Commands (Rev 44). It is just an illumination panel without a cover, a "Flat-Man" emulation. The Arduino program (based upon several previous designs published on the internet) appears to respond appropriately to the indi_flipflat driver when operated manually via the Main Control tab of the "Flip Man" tab in the Indi Control Panel window.  On/Off and brightness changes happen as expected. Filter brightness presets are reflected correctly in the log file.When a test exposure sequence is run (w/ CCD, filter wheel and telescope simulators along with the infi_flipflat driver) the debug files indicate filter changes initiate the appropriate brightness changes (according to the presets). Polling (1000ms setting) occurs with the appropriate responses being returned and the exposures are made after initial test exposures to achieve the selected ADU setting (set in the Calibration tab of the Capture Module). BUT the light panel is never turned on or off during the sequence.

I have attached an edited copy of the debug log file. I have added some notes to it and cut out a lot of non-relevant entries.

What am I missing here? 
 

File Attachment:

File Name: Logcaptureforflipflatoperationtest_2021-09-18.txt
File Size: 38 KB


Read More...

Let me preface this by pointing out my understanding of how this should work... When a exposure sequence of flats (with various filters) is initiated, the flat panel illumination will be set to the preset brightness level for the filter currently in use and the panel turned on before the exposures commence. With a desired ADU level set, test exposures will be made to determine the correct exposure, then the required number of flat frames taken. These steps are repeated until all the flats for the various filters are made.  (Not sure whether to expect the flat panel to be turned off between each filter and then back on after the brightness is set or just left on until the entire sequence is finished...)

I am building a flats panel using LEDs controlled by an Arduino using the Alnitak Generic Commands (Rev 44). It is just an illumination panel without a cover, a "Flat-Man" emulation. The Arduino program (based upon several previous designs published on the internet) appears to respond appropriately to the indi_flipflat driver when operated manually via the Main Control tab of the "Flip Man" tab in the Indi Control Panel window.  On/Off and brightness changes happen as expected. Filter brightness presets are reflected correctly in the log file.

When a test exposure sequence is run (w/ CCD, filter wheel and telescope simulators along with the infi_flipflat driver) the debug files indicate filter changes initiate the appropriate brightness changes (according to the presets). Polling (1000ms setting) occurs with the appropriate responses being returned and the exposures are made after initial test exposures to achieve the selected ADU setting (set in the Calibration tab of the Capture Module). BUT the light panel is never turned on or off during the sequence.

I have attached an edited copy of the debug logfile. I have added some notes to it and cut out a lot of non-relevant entries.

What am I missing here 

File Attachment:

File Name: Logcaptureforflipflatoperationtest.txt
File Size: 38 KB
 

File Attachment:

File Name: Logcaptureforflipflatoperationtest.txt
File Size: 38 KB
?

 

Read More...

David Swinnard replied to the topic 'Very unstable Raspberry Pi' in the forum. 2 weeks ago

Just a quick note... I to found when I went to powered hub (USB 3, 12V) pretty much all my connectivity issues with the Pi cleared up. Except one. If I had my imaging camera (Fuji X-T3 at the time, USB 3) and my guide camera (ZWO 120mm mono, USB 2) plugged into the hub only one worked. Trial and error lead me to leave the guide camera plugged into one of the Pi's USB ports. The imaging camera and all othe USB devices remain plugged into the hub.

Read More...

Updated Astroberry with Kstars & Indi... all the expected FITS header entries are now present.

Read More...

Thanks for the quick reply Juergen.  Good to know about the Indi version update for this driver.  I'm on Astroberry and will check for updates. (I thought I was updated, but possibly not.

Cheers!

Read More...

Thanks Juergen.  Well that certainly is a more complete list of things in the header than I'm seeing.  What version of Kstars are you running?  What Indi version?

Makes me wonder why the colour and monochrome cameras are reporting differently...

Any 268 monochrome users out there who could check?  (I will be cross posting to CN now)
 

Read More...

Have any of you users of the QHY268M camera found the "read mode" entry in the FITS header?  Thinking my processing program might not be showing me all the header entries, I tried a number of other programs as well.  I am unable to locate the entry Jasem mentioned in his response.

Read More...

Hi Jasem, I assumed there likely was, but I do not see it (using PixInsight FITSHeader). What am I missing here?

 



Read More...

I recently received and started using a QHY268M camera. During my initial experimentation with it (while awaiting clear night skies) I found I was often referring to the FITS header to note the temperature, gain and offset values of a particular exposure.  Along the way I could not find a header entry for the "mode" setting.

This camera can use one of four modes, each offering different characteristics.  The mode is set in the Main Control tab for the camera's driver.

Would it be possible to have the "mode" value reported in the FITS header along with the gain and offset values?  (If it's there and I missed it please point it out to me.)

Read More...

Riccardo, I had a chance to try the FITS save again...same results as last time.  It just transfers GGGG files that are grey only. I tried a few different configurations (FITS options, Capture module options, Indi Fuji_ccd settings) and always ended up with either a failure or a grey FITS file.  Saving the images took quite a while, on the order of two minutes (conversion from RAW time, I guess)  Way too slow to be useful.  I shoot with the Fuji set to save compressed RAF files (~26MB) to save space as my processing program will successfully handle the compressed files.
I will stick with using RAF files for now.

Read More...

I'm not sure I have any new insights, but I did want to flag an issue that's plaguing me. I started a quick response to Riccardo yesterday but decided to compose offline and include some log file information within the response.

I am still plugging away using my F-T3 and having some small successes. MOST of the time I get the results I'm hoping for - in terms of the camera behaving as defined in the Capture Module settings (ISO, exp. time, number of shots, etc.).  In each session  though something seems to go wrong, usually the exposure times get jumbled.

For example, on a clear night last week I had set up three exposure sequences: 2 x 1 sec., 20 x 120 sec. and another 20 x 120 seconds. The ISO sets correctly but (like every time), the first  exposure fails (I've learned to keep them short so I'm not wasting too much time). Usually the second attempt succeeds and thing progress as expected. But, not always. Frequently I get the "Could not wait for event" error message and then some attempts at exposures that are NOT in the sequence currently being exposed. These random exposures have always matched the current guide camera exposure setting. 

Here is a snippet of the the indi_fuji_ccd log from that session (with my annotations):

WARNING    1338.554369 sec    : All images and folders shall be deleted from the camera SD card after capture if capture target is set to SD Card.  ***** actually images are ALWAYS saved, regardless of this setting
INFO    2120.716599 sec    : Starting 1 seconds exposure.
ERROR    2121.845897 sec    : Error downloading image from camera: Directory not found    ***** to my knowledge the directory is properly defined in Ekos and Indi
ERROR    2121.846011 sec    : Failed to expose.
INFO    2121.913572 sec    : Starting 2 seconds exposure.        ***** wrong time, should be 1 second (this is the guide CCD exposure time)
INFO    2135.504177 sec    : Starting 1 seconds exposure.        ***** 2nd attempt - nothing…
INFO    2148.198707 sec    : Starting 2 seconds exposure.        ***** again, the wrong time reported (but corresponds the guide exposure time though ??)
INFO    2161.949513 sec    : Starting 1 seconds exposure.        ***** 3rd attempt - successful
INFO    2164.608158 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_1_secs_2021-06-03T23-18-16_001.raf
INFO    2173.711968 sec    : Starting 1 seconds exposure.        ***** second exposure of 1 sec. sequence started and saved
INFO    2176.331714 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_1_secs_2021-06-03T23-18-28_002.raf

    ***** start of first 120 second sequence - all looks good.

INFO    2186.458305 sec    : Starting 120 seconds exposure.
INFO    2311.656320 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-20-43_053.raf
INFO    2321.761852 sec    : Starting 120 seconds exposure.
INFO    2446.911192 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-22-59_054.raf
     ***** omitted lines here *****
INFO    4127.636040 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-50-59_066.raf
INFO    4138.788107 sec    : Starting 120 seconds exposure.
INFO    4264.340503 sec    : Image saved to /home/astroberry/Pictures/Light/NGC_7000_Light_120_secs_2021-06-03T23-53-16_067.raf
INFO    4276.546513 sec    : Starting 120 seconds exposure.

    *****( Now things go wrong… after 15 correct exposures of 120 seconds, there are still 5 more to go:

ERROR    4396.466260 sec    : Error downloading image from camera: File not found
ERROR    4396.466368 sec    : Failed to expose.                      ***** until the download attempt everything appears to be working - not until the exposure is over is it noticeable
INFO    4396.508905 sec    : Starting 2.5 seconds exposure.    ***** once again, this is the guide camera exposure time
WARNING    4396.567961 sec    : Could not wait for event.       ***** don’t have any idea what event this refers to…
WARNING    4396.569318 sec    : Could not wait for event.
WARNING    4396.570312 sec    : Could not wait for event.
WARNING    4396.571333 sec    : Could not wait for event.
WARNING    4396.572407 sec    : Could not wait for event.
WARNING    4396.573457 sec    : Could not wait for event.
WARNING    4396.574483 sec    : Could not wait for event.
WARNING    4396.575529 sec    : Could not wait for event.
WARNING    4396.576570 sec    : Could not wait for event.
WARNING    4396.577570 sec    : Could not wait for event.
INFO    4396.577623 sec    : Starting 120 seconds exposure.    ***** an attempt to start the correct exposure - less than 0.1 seconds after the “event” issue
ERROR    4516.486066 sec    : Error downloading image from camera: File not found    ***** after the exposure, the same failure sequence occurs
ERROR    4516.486216 sec    : Failed to expose.
INFO    4516.510096 sec    : Starting 2.5 seconds exposure.    ***** again, an attempt at an exposure that corresponds to the guide camera setting…
WARNING    4516.557539 sec    : Could not wait for event.
WARNING    4516.559214 sec    : Could not wait for event.
WARNING    4516.560762 sec    : Could not wait for event.
WARNING    4516.562386 sec    : Could not wait for event.
WARNING    4516.564513 sec    : Could not wait for event.
WARNING    4516.566101 sec    : Could not wait for event.
WARNING    4516.567698 sec    : Could not wait for event.
WARNING    4516.569300 sec    : Could not wait for event.
WARNING    4516.570865 sec    : Could not wait for event.
WARNING    4516.572513 sec    : Could not wait for event.
INFO    4516.572630 sec    : Starting 120 seconds exposure.    ***** another  attempt to start the correct exposure - less than 0.1 seconds after the “event” issue

    ***** and so on until I noticed the Fuji’s back screen NOT showing an exposure countdown, just the normal live view. I finally aborted the sequence and “reset” the entire system including power cycling the Pi and the Fuji camera, restarting Kstars and reacquiring the target. Each of these failures happens after the (2 minute) exposure is supposed to have occurred.

This is typical of my observing sessions so far.  I have to keep periodic watch on the Fuji’s screen to see if an exposure are actually happening when Ekos indicates one is.

I am really curious to know why the Capture Module is attempting to make exposures that are numerically equivalent to the guide camera when an issue occurs with the Fuji download. Each time I see this, the random exposure is that currently being used by the guide camera.  Some cross-talk happening for some reason?  (the Indi guide CCD log file shows nothing unusual…)

UPDATE:  Last night is was unexpectedly clear so I hastily set up my rig to gather more data on NGC7000.  As I had too move the tripod, polar alignment took longer than usual (I do like the new display triangle).  Unlike every other session, this one came off without a hitch - in terms of the exposure sequences (after?the "first exposure attempt failure" event). I captured 30, two minute exposures without an issue.  I then changed objects to try another few exposures before heading to bed.  Upon looking out the window to see the mount was moving properly, I noticed I had left the Bahtinov mask on the telescope (the fancy WO one that came with my GT-71).  I have just over an hour of images with a beautiful collection of Bahtinov diffraction patterns.  Rats.


 

Read More...

Hi Riccardo, I have not been able to solve this yet. I'm not sure where the issue is... Ekos, Indi, gphoto or...?

I literally just had an idea but I've yet to try it. (I've been composing my response to your question in the Fuji thread...)

I will be sure to update if I have any sort of success.

Read More...