Thomas Stibor's profile

Hello Daniel,

the INDI Gphoto driver uses the libgphoto2 library to communicate with the DSLR.
Setting the camera's SD card is basically the same as e.g. using the command line tool and setting:

gphoto2 --set-config capturetarget=1

That is, the RAW or JPEG image is not leaving the camera via any USB out, but is directly stored on the camera's SD card (when inserted) when taking an image or movie.
So saving the image in FITS is not possible when setting the target to SD. To save the image in FITS format, the RAW camera image first has to be read out from the camera
via USB (e.g. on Rpi or any PC) and then converted to FITS format. Once converted to FITS format the FIT headers are set.

Cheers
Thomas

Read More...

Hmm that is strange. I just booted by RPi and checked the version and installed it without any problems:

[indi@indiberry ~]$ lsb_release -a && apt info libev-dev && sudo apt install -y libev-dev
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 10 (buster)
Release:	10
Codename:	buster
Package: libev-dev
Version: 1:4.25-1
Priority: optional
Section: libdevel
Source: libev
Maintainer: Boyuan Yang <byang@debian.org>
Installed-Size: 214 kB
Depends: libev4 (= 1:4.25-1)
Homepage: http://software.schmorp.de/pkg/libev.html
Download-Size: 125 kB
APT-Sources: http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
Description: static library, header files, and docs for libev
 Static library, header files, and documentation for libev.
 .
 libev provides a full-featured and high-performance event loop that is
 loosely modelled after libevent. It includes relative timers, absolute
 timers with customized rescheduling, synchronous signals, process status
 change events, event watchers dealing with the event loop itself, file
 watchers, and even limited support for fork events. It uses a priority
 queue to manage timers and uses arrays as fundamental data structure. It
 has no artificial limitations on the number of watchers waiting for the
 same event.
 .
 libev supports select, poll, epoll, kqueue, and inotify.

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libev4
The following NEW packages will be installed:
  libev-dev libev4
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 160 kB of archives.
After this operation, 292 kB of additional disk space will be used.
Get:1 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian buster/main armhf libev4 armhf 1:4.25-1 [34.5 kB]
Get:2 http://mirror.de.leaseweb.net/raspbian/raspbian buster/main armhf libev-dev armhf 1:4.25-1 [125 kB]
Fetched 160 kB in 0s (357 kB/s)
Selecting previously unselected package libev4:armhf.
(Reading database ... 289593 files and directories currently installed.)
Preparing to unpack .../libev4_1%3a4.25-1_armhf.deb ...
Unpacking libev4:armhf (1:4.25-1) ...
Selecting previously unselected package libev-dev.
Preparing to unpack .../libev-dev_1%3a4.25-1_armhf.deb ...
Unpacking libev-dev (1:4.25-1) ...
Setting up libev4:armhf (1:4.25-1) ...
Setting up libev-dev (1:4.25-1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10+rpt2+rpi1) ...
[indi@indiberry ~]$

So probably the most simplest solution is to download that directly from one of the Debian mirror and install the package by hand:
packages.debian.org/buster/libev-dev
packages.debian.org/buster/armhf/libev-dev/filelist

So e.g.

wget http://ftp.cz.debian.org/debian/pool/main/libe/libev/libev-dev_4.25-1_armhf.deb && sudo dpkg --install ./libev-dev_4.25-1_armhf.deb

It looks like JPL changed the query syntax. The problem seems to be: "epoch.mjd" and "per.y". According to the JPL website the parameters are "epoch_mjd" and "per_y".

Read More...

Hello Bill,

the two GSC Ubuntu DEB packages (e.g. version 22.04) can be downloaded from here:
gsc Global Star Catalog
and
gsc-data Global Star Catalog

By inspecting the content of the Debian package (here version 20.04.1) one can see:

$ dpkg -c ./gsc_1.3_ubuntu20.04.1_amd64.deb 
drwxr-xr-x root/root         0 2019-10-30 08:55 ./
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/bin/
-rwxr-xr-x root/root     27368 2019-10-30 08:55 ./usr/bin/decode
-rwxr-xr-x root/root     38984 2019-10-30 08:55 ./usr/bin/gsc
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/share/
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/share/doc/
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/share/doc/gsc/
-rw-r--r-- root/root       277 2019-10-30 08:55 ./usr/share/doc/gsc/changelog.gz
-rw-r--r-- root/root      1733 2019-10-30 08:55 ./usr/share/doc/gsc/copyright

and

$ dpkg -c ./gsc-data_1.3_ubuntu20.04.1_all.deb | head -n 25
drwxr-xr-x root/root         0 2019-10-30 08:55 ./
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/share/
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/share/GSC/
drwxr-xr-x root/root         0 2019-10-30 08:55 ./usr/share/GSC/N0000/
-rw-r--r-- root/root     31404 2019-10-30 08:55 ./usr/share/GSC/N0000/0001.GSC
-rw-r--r-- root/root     38640 2019-10-30 08:55 ./usr/share/GSC/N0000/0002.GSC
-rw-r--r-- root/root     31044 2019-10-30 08:55 ./usr/share/GSC/N0000/0003.GSC
-rw-r--r-- root/root     37356 2019-10-30 08:55 ./usr/share/GSC/N0000/0004.GSC
-rw-r--r-- root/root     35296 2019-10-30 08:55 ./usr/share/GSC/N0000/0005.GSC
-rw-r--r-- root/root     33436 2019-10-30 08:55 ./usr/share/GSC/N0000/0006.GSC
-rw-r--r-- root/root     31740 2019-10-30 08:55 ./usr/share/GSC/N0000/0007.GSC
-rw-r--r-- root/root     28248 2019-10-30 08:55 ./usr/share/GSC/N0000/0008.GSC
-rw-r--r-- root/root     30504 2019-10-30 08:55 ./usr/share/GSC/N0000/0009.GSC
-rw-r--r-- root/root     40092 2019-10-30 08:55 ./usr/share/GSC/N0000/0010.GSC
-rw-r--r-- root/root     26088 2019-10-30 08:55 ./usr/share/GSC/N0000/0011.GSC
-rw-r--r-- root/root     33784 2019-10-30 08:55 ./usr/share/GSC/N0000/0012.GSC
-rw-r--r-- root/root     36988 2019-10-30 08:55 ./usr/share/GSC/N0000/0013.GSC
-rw-r--r-- root/root     28360 2019-10-30 08:55 ./usr/share/GSC/N0000/0014.GSC
-rw-r--r-- root/root     31576 2019-10-30 08:55 ./usr/share/GSC/N0000/0015.GSC
-rw-r--r-- root/root     29664 2019-10-30 08:55 ./usr/share/GSC/N0000/0016.GSC
-rw-r--r-- root/root     29964 2019-10-30 08:55 ./usr/share/GSC/N0000/0017.GSC
-rw-r--r-- root/root     26832 2019-10-30 08:55 ./usr/share/GSC/N0000/0018.GSC
-rw-r--r-- root/root     30888 2019-10-30 08:55 ./usr/share/GSC/N0000/0019.GSC
-rw-r--r-- root/root     35608 2019-10-30 08:55 ./usr/share/GSC/N0000/0020.GSC

For installing that on Gentoo probably the most simple ansatz is to checkout it out from git and compile & install it.

$ git clone https://git.launchpad.net/gsc
Cloning into 'gsc'...
remote: Enumerating objects: 9636, done.
remote: Counting objects: 100% (9636/9636), done.
remote: Compressing objects: 100% (9603/9603), done.
remote: Total 9636 (delta 5), reused 9623 (delta 4)
Receiving objects: 100% (9636/9636), 234.35 MiB | 3.95 MiB/s, done.
Resolving deltas: 100% (5/5), done.
Updating files: 100% (9628/9628), done.

Cheers
Thomas

Read More...

Another option besides chrony etc... is to use e.g. the following python script which fetches the time/date from GPS and set it
simply with a "sudo date" command.

#!/usr/bin/python

import os
import sys
import time
from gps import *

print 'Set System Clock to GPS UTC time'

try:
gpsd = gps(mode=WATCH_ENABLE)
except:
print 'ERROR: No GPS Present, time not set!!'
sys.exit()

while True:
#wait until the next GPSD time tick
gpsd.next()
if gpsd.utc != None and gpsd.utc != '':
#gpsd.utc is formatted like"2015-04-01T17:32:04.000Z"
#convert it to a form the date -u command will accept: "20140401 17:32:04"
#use python slice notation [start:end] (where end desired end char + 1)
# gpsd.utc[0:4] is "2015"
# gpsd.utc[5:7] is "04"
# gpsd.utc[8:10] is "01"
gpsutc = gpsd.utc[0:4] + gpsd.utc[5:7] + gpsd.utc[8:10] + ' ' + gpsd.utc[11:19]
os.system('sudo date -u --set="%s"' % gpsutc)
sys.exit()

Read More...

Well, you could also try to modify in file CMakeLists.txt the entry:

find_package(INDI 1.9.1)

to

find_package(INDI 1.8.9)

or some prior version and see whether it works as expected.

Read More...