×

INDI Library v1.9.0 Released (23 Apr 2021)

Major INDI Library release v1.9.0 bring significant internal changes championed by @pawel-soja to modernize core INDI Library drivers and clients. New drivers for DeepSkyDad Flat Panel & Pegasus devices plus further improvements to PCM8 drivers.

ASI294 problem with INDI driver

  • Posts: 177
  • Thank you received: 47
Hi All

I started a new thread because I am now a step further.
I cannot take good Darks using the Indi driver via Ekos. They show no randomness and do not display the amp glow. We noticed a checkerboard pattern, this doesn't look random, all the "lanes" have the same value, and the black pixels exactly half of that.
Maybe its a setting (I am using the defaults) but I cannot get it right.

So I decided to install APT and use ASCOM to connect. The Darks I get via APT are exactly as I would expect. I can clearly see the amp glow and star burst pattern.

Any idea's why the INDI driver behaves so differently from the Ascom?

The image on the left is from Indi, the one on the right from a different capture program.
WO ZS 61
Esprit 100
Skyliner 200p
Edgehd 8 with Celestron OAG
Stellarmate on RPi 4
iOptron GEM45
294 mc pro
224 planetary cam
174 guide cam
Powerbox Ultimate
Sesto Senso focusser
Arduino focusser
QHY5II-Mono guide camera
EOS6D - not modified

The following user(s) said Thank You: Craig
Last edit: 1 year 7 months ago by Rishi Garrod.
1 year 7 months ago #45323
Attachments:

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

  • Posts: 358
  • Thank you received: 131
Are you using the same offset value? I noticed that my ASI178MC has a dark current compensation "feature" that over compensates for dark current and the default offset value was too low and clips to black and was helped by raising offset. This seems common for Sony sensors (at least IMX178 and IMX183 seem to have it) so it might affect 294 as well. It's easy to notice if very short bias frames have higher mean ADU values than longer darks. I had discussion with ZWO about this at bbs.astronomy-imaging-camera.com/viewtopic.php?f=29&t=8426
Remote observatory running Ubuntu 20.10 x64 with ScopeDome 2M, Skywatcher EQ8, TS 8" RC, Atik 383L+, ASI178MC, ASI120MM-S, SX Lodestar X2, SX USB wheel with OAG, ZWO EAF, Gemini SnapCap, USB_DewPoint, KomaHub
1 year 7 months ago #45326

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

  • Posts: 177
  • Thank you received: 47
I have been using the default (for Indi) offset value of 8 for all my frames.
I am also using the unity level of gain (120).
I am not using any bias frames but Flat Darks. My flats are 4 seconds to avoid short exposures.

The Indi driver does have some settings I don't completely understand.
Default the Format is set to 8 bits with RGB, 16 bit and Luma as options. If I set it to 16 bit my darks immediately look much better. I would have expected 16 bit to be the default unless I was trying to get a high FPS?
WO ZS 61
Esprit 100
Skyliner 200p
Edgehd 8 with Celestron OAG
Stellarmate on RPi 4
iOptron GEM45
294 mc pro
224 planetary cam
174 guide cam
Powerbox Ultimate
Sesto Senso focusser
Arduino focusser
QHY5II-Mono guide camera
EOS6D - not modified

1 year 7 months ago #45327

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

  • Posts: 177
  • Thank you received: 47
As usual it turned out to be user error.

Out of the box the driver has the format set to 8 bit (which is I assume to improve the frame rate for lucky imaging).
Once I set it to 16 bit my darks looked normal.
WO ZS 61
Esprit 100
Skyliner 200p
Edgehd 8 with Celestron OAG
Stellarmate on RPi 4
iOptron GEM45
294 mc pro
224 planetary cam
174 guide cam
Powerbox Ultimate
Sesto Senso focusser
Arduino focusser
QHY5II-Mono guide camera
EOS6D - not modified

1 year 7 months ago #45335

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

  • Posts: 177
  • Thank you received: 47
As usual it turned out to be user error.

Out of the box the driver has the format set to 8 bit (which is I assume to improve the frame rate for lucky imaging).
Once I set it to 16 bit my darks looked normal.
WO ZS 61
Esprit 100
Skyliner 200p
Edgehd 8 with Celestron OAG
Stellarmate on RPi 4
iOptron GEM45
294 mc pro
224 planetary cam
174 guide cam
Powerbox Ultimate
Sesto Senso focusser
Arduino focusser
QHY5II-Mono guide camera
EOS6D - not modified

1 year 7 months ago #45336

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

  • Posts: 1114
  • Thank you received: 181
Also, it looks like you had not set the FITS viewer to debayer the image. Only the Red channel is shown then, that's why you are missing 3/4 of the pixels. Did you check the actual saved FITS file in PixInsight or FITS liberator?
Atlas Pro AZ-EQ, ASI1600MM-Pro, ASI120MM-S, ES102ED, WO-Z61, Nikon D3300, ASI-EFW, ZWO LRGB,Ha,O3,S2 filter set
1 year 7 months ago #45362

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

  • Posts: 177
  • Thank you received: 47
I have been viewing the images from within PI. They were not yet debayered.
I though PI displayed images as gray scale until they are debayered?

Is that the tram line effect I am seeing? Only the red pixels.
WO ZS 61
Esprit 100
Skyliner 200p
Edgehd 8 with Celestron OAG
Stellarmate on RPi 4
iOptron GEM45
294 mc pro
224 planetary cam
174 guide cam
Powerbox Ultimate
Sesto Senso focusser
Arduino focusser
QHY5II-Mono guide camera
EOS6D - not modified

1 year 7 months ago #45367

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

Time to create page: 0.676 seconds