Dirk replied to the topic 'solver minimum FOV' in the forum. 2 months ago

Hello Dirk,
Have you installed the catalog files for the small FOV values. In the options section for the solver you can check and download if required.


Regards
Dirk

Read More...

Dirk replied to the topic 'Guiding problem using EKOS' in the forum. 5 months ago

Hello Ralf,
You write you are using an ST4 cable. What are you using in the guiding tab under via: the camera or the mount, for ST4 you would need the camera...


Regards

Dirk

Read More...

Hello,
Please note , that park position and home position on the cem25p are not the same.

I never managed to understand how parking works with the cem25p, but when I click on park in Ekos, it skews to a position that is very well suited for taking flats.

Read More...

I have seen this from time to as well... .
Regards

Dirk

Read More...

Dirk replied to the topic 'ASI183MM PRO Offset' in the forum. 8 months ago

Hi,
Yesterday, I managed to take a few subs between the clouds, and I can confirm, the OFFSET header is there.

Regards

Dirk

Read More...

Dirk replied to the topic 'ASI183MM PRO Offset' in the forum. 8 months ago

Hi wolfi,
Here is what IFound:
One shortcoming of the FITS standard is that the 16-bit number format is signed, producing a range of -32768 to +32767. The range of data from many cameras is 0 to 65535. To overcome this problem, MaxIm DL subtracts 32768 from each pixel prior to saving. The FITS standard requires that the BZERO and BSCALE keywords be used when the value in the array is not the physical value; MaxIm DL sets BZERO to 32768 and BSCALE to 1. Other applications that interpret these keywords correctly should automatically add 32768 to the image pixels, resulting in a correct image display. This default behavior can be overridden using the File menu Settings command.

But I agree, with bzero = offset and bscale =inverse gain you could even produce fits files containing the number of electrons per pixel....

Regards

Dirk

Read More...

Dirk replied to the topic 'ASI183MM PRO Offset' in the forum. 8 months ago

I understood this value is for the conversion of signed int to unsigned int

Regards
Dirk

Read More...

Dirk replied to the topic 'ASI183MM PRO Offset' in the forum. 8 months ago

Hello Jasem,
for gain I found to more or less standard keywords, which are GAIN or EGAIN, both measured in e-/ADU, for offset I could not find anything commonly used. In ccdciel, Patrick Chevalley decided to add following headers to fits files for Indi controlled cameras:

+ if gain>0 then Ffits.Header.Add('GAIN',gain,'Video gain');
+ if gamma>0 then Ffits.Header.Add('GAMMA',gamma,'Video gamma');
+ if offset>0 then Ffits.Header.Add('OFFSET',offset,'Video offset,brightness');

( sourceforge.net/p/ccdciel/code/602/ )

which was the only useful reference I could find...


Regards

Dirk

Read More...

Dirk replied to the topic 'Comet naming, C/2017...' in the forum. 8 months ago

My fault.
We were talking Kstars and I was looking indilib....

Read More...

Dirk replied to the topic 'Comet naming, C/2017...' in the forum. 8 months ago

Did you push it to master, I do not find it on GitHub....

Read More...

Dirk replied to the topic 'Teamviewer: commercial use detected' in the forum. 8 months ago

Hi,
Although I’m am not a huge fan of Microsoft products, I must say that the Remote Desktop protocol is very good regarding responsiveness and performance.
I installed xrdp on my raspberry and I am quite happy with the performance.

Regards
Dirk

Read More...

Dirk replied to the topic 'ASI183MM PRO Offset' in the forum. 8 months ago

Hello,
I agree that it would be nice to have the offset value in the FITS Header.
EKO, and most other astrophotography tools have two ways to handle image data, 1 or 2 Byte per file, thus 8 or 16 bit. I doubt, that the fits format would even allow 12 bit files. 8, 16 and I think even 32 used more or less widely.
While the camera delivers 12 bit values, the remaining 4 bits are filled with zeros, effectively multiplying the value with 16. So you will have values in the range of 0 to 65535 instead of 0 to 4095 but all you values are multiples of 16.

So in short, I you do not want to use 8 bit, chose 16 and you will receive what you camera delivers.

Regards

Dirk.

Read More...