There is option for controlling the histogram at Settings menu -> Configure KStars -> FITS -> non linear histogram

Hi Jarno,
I tested different settings in the KStars FITS menu. I got different results. What I can see, the X-axis is still nonlinear and expressed as a 8-bit 0 to 255 levels. Above I have the raw CR2 file as a CFA format. Both X and Y are linear. I think I can use the KStars FITS histograph for a rough selection and the relation between the colors are no problems, the last check I do in Windows with some more advanced tool. It's a progress.

 

/Lars

Maybe you already know, but if you need to establish exposure time to reach target ADU, you can use the "Calibrate" button that enables when you choose "Flat" for image type in capture tab.Then Ekos will automatically find correct exposure before taking your flat sequence.

Hope this helps.



 

@Jarno

Much better now when I changed the paameters yo told me about. But there is something wrong, the histogram doesn't update with new photos, I have to close down the histogram and FITS viewer and take a new photo to see the update.

@Matteo

Interesting, I will test that function later on

/Lars

Lars post=78811 userid=3671
-  but the Astroberry version of VNC could not transfer files.

/Lars

Just for the record, the VNC server in Astroberry does transfer files. Click on the black VNC button in the Taskbar, and select the file transfer option from the menu list. I used this for a long period, but these days I prefer using the Samba server option by creating a network drive in Windows File Explorer which gives me simpler and consistently faster transfer connections.

Strange, when I ggoled on this subject one year ago I got the impression that it was very difficult. Now I ahve at least two solutions, WinSCP works very well, but I will test Astroberry VNC later.

Thanks for all information !

/Lars

I noticed that something has changed with the histogram view several months ago.
I started to largely ignore the histogram and just mouse over the fits image viewer to see what the intensities are.
That's with 16bit astro camera.

Last couple of days I've been playing with a DSLR (Nikon D5500) as an imaging camera for the first time in more that a year.
Both histogram and fits viewer are totally inconsistent and wrong now (was OK a year ago I believe).
Especially when the format is set to Native (NEF in my case).
When the format is set to FITS things get better but still are a bit strange.

I'm not sure if I understand, do you mean you get a histogram with Fits data, 1-65550 ? My histogram is always 0-255, Canon 6D raw, CR2 files.

How to setup Fits/Histogram to that ?

See screendump:

 

/Lars

Sorry, I was confused and didn't understand what's going on...
Yes, for both FITS and NATIVE the histogram is not linear and 0-255.
With NATIVE both histogram and fits viewer are wrong
With FITS, histogram is wrong but the fits viewer shows correct intensities (14bit in my case. 0-16384).

Okay, then I understand better.

I save my Canon files as Native, but temporarly they must be in fits format. So what I see in the Fitsviewer is converted native files because Fitsviewer can only display fits files, or ?

/Lars

With the caveat that I'm using StellarMate, not Astroberry, I certainly never see a 256-bit histogram. In the camera tab on the INDI Control Panel, is there an option for 8-bit vs. 16-bit images? For a long time my Pi kept defaulting to 8-bit and my images suffered terribly because of that! Dunno how the CR2 and FITS work together but the FITS off my ASI183, a 14-bit camera, are always 16-bit.

With a dedicated astro-camera there's no problem with histogram/fits viewer.
With a DSLR there is a problem.
When it is set to NATIVE (at least in my case with D5500 and NEF format), the histogram is 8-bit and stretched all the way and is the same for say 1 sec and 10 sec exposure. Fits viewer also shows wrong intensities I believe.
When it is set to FITS things do get better. Fits viewer shows right intensities but the histogram sometimes is wrong. Sometimes it is OK.