×

INDI Library v1.9.9 Released (30 Nov 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Can EKOS add focuser temp to captured filename?

  • Posts: 12
  • Thank you received: 0
Probably not the right forum, if someone knows a better place to ask please let me know.

I use a DSLR and as a result, temperature is important for calibration frames.

It seems that EKOS allows me to add a number of variables to the captured filename but the temperature setting seems to come from the temp setting for the cooled camera.

I'd like to use the sensor from the focuser instead.

Is this possible?
4 months 21 hours ago #85147

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

  • Posts: 203
  • Thank you received: 45
What device you have set in focus tab as temperature source? Maybe you need to set focuser as temperature source there?
4 months 17 hours ago #85149

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

  • Posts: 970
  • Thank you received: 128
If you have a focuser, the temperature should be in the FITS header:
FOCUSPOS=                27710 / Focus position in steps
FOCUSTEM=            1.743E+01 / Focuser temperature in degrees C
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
4 months 15 hours ago #85151

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

  • Posts: 12
  • Thank you received: 0
Thanks, that is helpful as an alternative. Now I just need an extended "ls" command for Linux that can display and sort by the FITS headers :)
4 months 8 hours ago #85170

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

  • Posts: 12
  • Thank you received: 0
Ahah. Looks like fitsgetext can pull out individual headers from fits files from the command line. This means I can write a script to rename the files to include the sensor temp.
4 months 8 hours ago #85171

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

  • Posts: 970
  • Thank you received: 128
Haha, I had already wanted to write a reply refering to shell admins morning calisthenics :D
I didn't even know fitsgetext, though it seems only to work on extensions... What you look for might be fitshdr from the wcslib-tools package? Or fitsheader from astropy.
I usually use dd to print FITS headers....
fits () 
{ 
    coun=$2;
    if [ .$coun = . ]; then
        coun=36;
    fi;
    dd if="$1" ibs=80 cbs=80 conv=unblock count=$coun 2> /dev/null
}
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
4 months 7 hours ago #85172

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

  • Posts: 12
  • Thank you received: 0
Thanks, I found that gnuastro (linux package) includes the astfits utility that does the trick.
I also found that EKOS in my setup is putting the focuser temperature in the value called CCD-TEMP when using a DSLR. (There is no FOCUSTEM FITS header in my images).

Here is how I'm pulling CCD-TEMP from the fits headers in a random fits file. Note that for some reason, even though the value is an integer, a "." is placed at the end of the decimal value. So I use sed to remove a trailing ".".
I guess EKOS truncates or rounds up the focuser temp when putting it into CCD-TEMP.

astfits file.fits -h0 | grep CCD-TEMP| awk '{print $2}'|sed s/.$//`
Last edit: 4 months 6 hours ago by Brian Hayward.
4 months 6 hours ago #85174

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

  • Posts: 970
  • Thank you received: 128
Ha! What about this one?
woodstock:EKOS% astfits -h0 Test.fits |grep FOCUSTEM
FOCUSTEM=                16.54 / Focuser temperature in degrees C               
 
woodstock:EKOS% exiftool '-filename<%f_${FOCUSTEM;}.%e' Test.fits 
    1 image files updated
woodstock:EKOS% ls Test*fits
Test_16.54.fits
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
4 months 3 hours ago #85176

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

  • Posts: 12
  • Thank you received: 0
Hey, nice tip - thanks. I haven't used exiftool before.

No FOCUSTEM in my images:
$ astfits -h0 Test*.fits |grep FOCUSTEM
$

Since I don't have a cooled camera, it seems to just set the CCD-TEMP instead:
$ astfits -h0 Test*.fits |grep CCD-TEMP
CCD-TEMP= 22. / CCD Temperature (Celsius)

I bet it's a bug in EKOS that results in CCD-TEMP being "22." instead of "22.3" or similar.
The UI displays the full value in all areas (Focuser tab and Capture tab). But 100% of my images have a FITS header CCD-TEMP that ends in a ".".

Of course, with the dot at the end, the filename ends up being:
$ exiftool '-filename<%f_${CCD-TEMP;}.%e' Test.fits
1 image files updated
$ ls Test*
Test_22..fits

Now I need to find the proper forum to report the above bug.
4 months 3 hours ago #85178

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

  • Posts: 970
  • Thank you received: 128
The FOCUSTEM was just for the test. You can use any of the header entries for that :)
as for the dot - it might well be that it's the accuracy of the number, and the dot just indicates it's a float value. For the renaming - if all of them have the dot at the end, just leave it out in the command line:
exiftool '-filename<%f_${CCD-TEMP;}%e' Test.fits
or use 0.%e to get 20.0.fits....
Guess the EKOS forum is the right one to ask.
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
4 months 3 hours ago #85180

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

Time to create page: 0.970 seconds