×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Cannot take Flats with ZWO camera

  • Posts: 79
  • Thank you received: 13
Ok, video followed same steps I did. I will try with latest version.
I installed Stellarmate for RPI3+, what is the best way of updating to latest version of KSTARS?
Software updater ran a few days ago did not update it.
5 years 5 months ago #30380

Please Log in or Create an account to join the conversation.

Try this:
The following user(s) said Thank You: Max Dobres
5 years 5 months ago #30390

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 11
I too had a similar issue but since updating to nightly build and updating as mentioned in this post all is ok.
Skywatcher 190MN - EQ6 Pro (with Belt Mod) - ASI1600MM-Cooled - ASI EFW7 - ASI120MM - WO f4 Guide Scope - Rigel nStep - KStars/Ekos - KDE - PixInsight
The following user(s) said Thank You: Jasem Mutlaq
5 years 5 months ago #30394

Please Log in or Create an account to join the conversation.

  • Posts: 79
  • Thank you received: 13
Still not quite working: (Logs attached, seems to be 3 of them)
OK so updated as instructed and Kstars is showing as version 3 Build: 2018-10-13T19:26:36Z
Attached my ASI 178MC and set calibration as ADU = 5000, Tolerance = 300 as in video.
Ran with initial exposure of 1 second count of 5. Using an LCD light frame as the target
It started iterating and seemed to get stuck with a max ADU of 255 eventually suggesting a 2000 exposure. (Reading from the bottom up on this list)

2018-10-15T18:02:38 Capturing 1.000-second image...
2018-10-15T18:02:27 CCD capture aborted
2018-10-15T18:02:21 Capturing 2,000.000-second image...
2018-10-15T18:02:21 Current ADU is 255 Next exposure is 2,000.000 seconds.
2018-10-15T17:59:06 Capturing 193.192-second image...
2018-10-15T17:59:06 Current ADU is 255 Next exposure is 193.192 seconds.
2018-10-15T17:59:02 Capturing 1.953-second image...
2018-10-15T17:59:02 Current ADU is 255 Next exposure is 1.953 seconds.
2018-10-15T17:58:58 Capturing 1.562-second image...
2018-10-15T17:58:58 Current ADU is 255 Next exposure is 1.562 seconds.
2018-10-15T17:58:55 Capturing 1.250-second image...
2018-10-15T17:58:55 Current ADU is 255 Next exposure is 1.250 seconds.
2018-10-15T17:58:52 Capturing 1.000-second image...
2018-10-15T17:58:52 Job requires 1.000-second images, has 0/5 frames captured and will be processed.

Tried a few more variations of starting point, same result.

Inspection by trial and error suggested a real exposure of somewhere in the region of .001 required, certainly less than 1 second.
Tried again with initial exposure very short. Same thing, iterates and eventually hits ADU 255 ceiling.

Tried setting ADU to 150 (ie less than 255) with tolerance 10 and it completed test iterations and captured Flats (Obviously wrongly exposed)

Regards
Max
5 years 5 months ago #30432
Attachments:

Please Log in or Create an account to join the conversation.

That's because you're taking 8-bit images! For this to work, take 16bit images. In INDI Control Panel --> ZWO --> Controls --> 16bit
The following user(s) said Thank You: Max Dobres
5 years 5 months ago #30434

Please Log in or Create an account to join the conversation.

  • Posts: 79
  • Thank you received: 13
Ok changed to 16 bit (Didn't know the setting was there)

Now works if I start with low starting exposure: .001 secs, builds up to target , but if I start with 1 sec exposure it bounces off to 2000 seconds after getting ADU = 65479 several times.
But this works great now I know where to start.
Thanks.
5 years 5 months ago #30440
Attachments:

Please Log in or Create an account to join the conversation.

I'll add a warning if I detect 8bit images. The log actually behaves fine, it goes down to 0.001 seconds after a few iterations. However, for some reason, the image is either not received or not analyzed. I think I'll add one more case when it is near saturation (like what happened here) so that it takes immediate step to reduce the exposure time instead of the iterative approach. Thanks for the logs!
5 years 5 months ago #30448

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 11
Just a quick suggestion; don't have your light source too bright. Keep it nice and low and the exposures will be long enough for the camera to adjust to the desired ADU.
Skywatcher 190MN - EQ6 Pro (with Belt Mod) - ASI1600MM-Cooled - ASI EFW7 - ASI120MM - WO f4 Guide Scope - Rigel nStep - KStars/Ekos - KDE - PixInsight
5 years 5 months ago #30454

Please Log in or Create an account to join the conversation.

  • Posts: 535
  • Thank you received: 109
A good suggestion as the ASI1600 sensor, for one, seems to operate differently with exposures longer than .2 than it does with faster exposures. There is a graph that shows this somewhere. For this reason, I always do flats with an exposure > .2s and adjust the brightness down to make that possible.
5 years 5 months ago #30464

Please Log in or Create an account to join the conversation.

  • Posts: 106
  • Thank you received: 11
Interesting. My Luminous flats were successfully taken at 0.011 sec with basically indoor ambient light. When below that time the image generated included horizontal lines.
Skywatcher 190MN - EQ6 Pro (with Belt Mod) - ASI1600MM-Cooled - ASI EFW7 - ASI120MM - WO f4 Guide Scope - Rigel nStep - KStars/Ekos - KDE - PixInsight
5 years 5 months ago #30471

Please Log in or Create an account to join the conversation.

I just pushed few changes to improve the algorithm in GIT, so check the next nightly.
The following user(s) said Thank You: Max Dobres
5 years 5 months ago #30472

Please Log in or Create an account to join the conversation.

  • Posts: 79
  • Thank you received: 13
So based on your previous instructions Will:

sudo apt-get update
sudo apt-get install indi-full kstars-bleeding

Get me the most recent build?
5 years 5 months ago #30486

Please Log in or Create an account to join the conversation.

Time to create page: 0.446 seconds