A quick test with my prototype light panel seems to be working as expected now. (using Oct 01 nightly build.) Now to finish the LP build.

Many thanks for this Jasem.

Read More...

I have tried the new nightly build and found it does in fact properly save the "correct" ADU flat frame exposures.

Flat panel brightness is still only set just once during the setup of the driver (to value for filter slot 1) and is not changed during a sequence where each filter calls for a different brightness setting.

Is the flat panel supposed to be turned off between different filter sequences?  It turned on at the start of the sequence for a filter, but not off at the end, resulting in a flat panel that stays on until manually switched off.

Thanks for these swift updates!

Read More...

Jasem, I have some more information. Using a Kubuntu install with Kstars 3.5.6 beta Build: 2021-09-28T22:15:36Z. I get different operational results from the 3.5.5 trial in the first post.

As you can see from the attached (edited for length) log in each of the LRGB flat frame sequences (of 5 exposures with a 1 second starting exposure) I get the first (1 sec) exposure saved, then a couple of "test" frames to determine the ADU value (set 28000 as target) which are NOT saved, then the 4 remaining "correct" exposures are saved. So for each 5 frame flat sequence I get one frame with the starting exposure and four "correct" exposure frames saved.

In version 3.5.5 all the saved frames were of the "correct" exposure.Additionally, the exposure light is still not being turned on or off. The lamp responds to manual control from Indi as before.

Note: in the log file attached I only included the L exposure sequence and not the RGB ones as they were identical.

 

File Attachment:

File Name: Flattest3.5.6of9-28capt11-44-31.txt
File Size: 33 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.

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. 1 month 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...