Hi there,
I have the ATIK414EX mono, however, it seems to be a similar confusion as with your ATIK 460EX.
According to ATIK website technical specification (see screenshot):
Horizontal Resolution: 1391 pixels
Vertical Resolution: 1039 pixels
however, in the
AtikSeries4Manual.pdfAtikSeries4Manual.pdf
it is listed with resolution: 1392x1040.
I tested the ATIK414EX with ATIK's windows capture software Artemis and in windows it captured with: 1391x1039.
Same behavior also with latest INDI and INDIGO driver, so I guess 1391x1039 is the correct. Though I have no idea why such an odd resolution. Looks like
one row and column is left out.
For your ATIK 460EX it is the same confusion on ATIK website. According to website tech spec it is:
Horizontal Resolution: 2749 pixels
Vertical Resolution: 2199 pixels
However, in PDF manual it is 2750x2200.
So I guess the correct resolution suppose to be 2749x2199.
Cheers
Thomas
Read More...
The ASI120MM (USB2) and also the ASI130MM (USB2) is well known for making trouble under Linux. I own the 130MM and can only use the camera in 8 bit mode. In 16 bit it is very unreliable and just makes trouble.
If you search here in forum for "120mm" you will find all the trouble reports. Also the reports are reported in ZWO forum.
What works though is the 120MM-S USB3 version.
Read More...
To make sure you USB GPS device always has symbolic name e.g.
/dev/ttyGPS/usr/lib/udev/rules.d/99-indi_gps_gpsd.rulesSUBSYSTEM=="tty", ATTRS{idVendor}=="1546", ATTRS{product}=="*u-blox*", SYMLINK+="ttyGPS", MODE="0666"[ 296.751463] usb 1-1.2: new full-speed USB device number 6 using ehci-pci
[ 296.860921] usb 1-1.2: New USB device found, idVendor=1546, idProduct=01a8, bcdDevice= 3.01
[ 296.860923] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 296.860925] usb 1-1.2: Product: u-blox GNSS receiver
[ 296.860926] usb 1-1.2: Manufacturer: u-blox AG - www.u-blox.com
[ 296.881337] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
[ 296.881897] usbcore: registered new interface driver cdc_acm
[ 296.881898] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
indi@x230:~>ll /dev/ttyGPS
lrwxrwxrwx 1 root root 7 Sep 6 15:21 /dev/ttyGPS -> ttyACM0So your GPS device name persistently be
/dev/ttyGPSProbably it would be a good idea to submit this rule also upstream to GITHUB.
Cheers
Thomas
Read More...
The Ultimate Powerbox v2 has a slightly different and extended command language (see attached document), so the Ultimate Powerbox v1 INDI driver needs to be updated/extended.
Read More...
Hello Gina,
I solved the image locally with command (and catalog):
solve-field -D /tmp --no-plots \
--overwrite \
--downsample 2 \
--tweak-order 2 \
--scale-units degwidth \
--scale-low 0.1 \
--scale-high 180.0 Light_020.png
Reading input file 1 of 1: "Light_020.png"...
Read file stdin: 1999 x 1512 pixels x 1 color(s); maxval 255
Using 8-bit output
Extracting sources...
Downsampling by 2...
simplexy: found 1386 sources.
Solving...
Reading file "/tmp/Light_020.axy"...
log-odds ratio 173.91 (3.37336e+75), 43 match, 1 conflict, 149 distractors, 62 index.
RA,Dec = (306.427,37.2838), pixel scale 64.3222 arcsec/pix.
Hit/miss: Hit/miss: +--+--+--+-++--++-+++-++++---+++----+----+---+++---++-------+--+--------++--+++-----------c---+-----
Field 1: solved with index index-4117.fits.
Field 1 solved: writing to file /tmp/Light_020.solved to indicate this.
Field: Light_020.png
Field center: (RA,Dec) = (306.430876, 37.289469) deg.
Field center: (RA H:M:S, Dec D:M:S) = (20:25:43.410, +37:17:22.089).
Field size: 34.87 x 26.695 degrees
Field rotation angle: up is 88.9147 degrees E of N
Field parity: neg
Creating new FITS file "/tmp/Light_020.new"...Catalog (Tycho-2 index files)
add_path /data/astrometry/4100>ll /data/astrometry/4100/
total 347312
-rw-r--r-- 1 tstibor tstibor 58 Nov 8 2018 cfg
-rw-r--r-- 1 tstibor tstibor 164995200 Nov 8 2018 index-4107.fits
-rw-r--r-- 1 tstibor tstibor 94550400 Nov 8 2018 index-4108.fits
-rw-r--r-- 1 tstibor tstibor 49772160 Nov 8 2018 index-4109.fits
-rw-r--r-- 1 tstibor tstibor 24871680 Nov 8 2018 index-4110.fits
-rw-r--r-- 1 tstibor tstibor 10206720 Nov 8 2018 index-4111.fits
-rw-r--r-- 1 tstibor tstibor 5296320 Nov 8 2018 index-4112.fits
-rw-r--r-- 1 tstibor tstibor 2733120 Nov 8 2018 index-4113.fits
-rw-r--r-- 1 tstibor tstibor 1382400 Nov 8 2018 index-4114.fits
-rw-r--r-- 1 tstibor tstibor 740160 Nov 8 2018 index-4115.fits
-rw-r--r-- 1 tstibor tstibor 408960 Nov 8 2018 index-4116.fits
-rw-r--r-- 1 tstibor tstibor 247680 Nov 8 2018 index-4117.fits
-rw-r--r-- 1 tstibor tstibor 187200 Nov 8 2018 index-4118.fits
-rw-r--r-- 1 tstibor tstibor 144000 Nov 8 2018 index-4119.fits
-rw-r--r-- 1 tstibor tstibor 38278 Nov 8 2018 log
-rw-r--r-- 1 tstibor tstibor 4853 Nov 8 2018 log10
-rw-r--r-- 1 tstibor tstibor 6699 Nov 8 2018 log7
-rw-r--r-- 1 tstibor tstibor 6634 Nov 8 2018 log8
-rw-r--r-- 1 tstibor tstibor 6376 Nov 8 2018 log9
-rw-r--r-- 1 tstibor tstibor 1054 Nov 8 2018 READMERead More...
Han, try:
www.indigo-astronomy.org/downloads.html
It is fully compatible with INDI and works perfectly with Raspian (and CCDCiel, PHD, ...)
You can even download the ready Raspbian Image:
www.indigo-astronomy.org/indigo-sky.html
Read More...
Of course kstars can be compiled on Raspbian. Raspbian is nothing more or less than a Debian Buster running on ARM.
Just type:
>sudo apt-get build-dep kstarsThen, checkout from e.g. github kstars, go into checkout kstars directory and run:
>mkdir build && cd build && cmake .. && make -j4INDIGO is not an INDI client but an INDI/GO server, and it brings by design also an integrated webserver to adjust INDI/GO properties
as every INDI client is providing it. Moreover, recently several so called agents were added which allow to guide, etc...
I personally run INDIGO on RPI3: Kstars to polar align, and CCDCiel + PHD2 to image.
Read More...
One does not have to concentrate here on anything, but rather use logical reasoning:
>apt-get build-dep
E: Must specify at least one package to check builddeps forDoes exist on Debian Buster (Raspbian) an eq-mod INDI package?
Answer no, so obviously "build-dep" works on shipped Debian packages only.
Please visit libindidriver1 and other
packages to see the dependencies,e.g.:
search libindi
One can observe that e.g. libgphoto2-dev is not in the dependency,
because Debian maintainer are building the packages in a different way. However,
e.g. libindi-plugins has dependency list:
dep: libc6 (>= 2.17) [arm64, ppc64el]
GNU C Library: Shared libraries
also a virtual package provided by libc6-udeb
dep: libc6 (>= 2.4) [not arm64, ppc64el]
dep: libcfitsio7 (>= 3.450~)
shared library for I/O with FITS format data files
dep: libgcc1 (>= 1:3.0) [not armel]
GCC support library
dep: libgcc1 (>= 1:3.5) [armel]
dep: libindidriver1 (>= 1.7.5+dfsg)
Instrument-Neutral Device Interface library -- driver library
dep: libjpeg62-turbo (>= 1.3.1)
libjpeg-turbo JPEG runtime library
dep: libnova-0.16-0
celestial mechanics, astrometry and astrodynamics library
dep: libogg0 (>= 1.0rc3)
Ogg bitstream library
dep: libstdc++6 (>= 5.2)
GNU Standard C++ Library v3
dep: libtheora0 (>= 1.0)
Theora Video Compression Codec
dep: libusb-1.0-0 (>= 2:1.0.8)
userspace USB programming library
dep: zlib1g (>= 1:1.1.4)
compression library - runtime So in other words, when you
>sudo apt-get build-dep libindi-pluginsThis will install all the required dependencies to build that package.
Read More...
There is no need to check by hand which dependencies need to be installed. Just type:
sudo apt-get build-dep libindi-data libindi-dev libindi-plugins libindialignmentdriver1and it will install are the required/depended packages for compiling these packages from source.
So for instance when I want to compile VIM editor my self I would do:
>sudo apt-get build-dep vim
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
cscope docbook-dsssl docbook-utils liblua5.2-dev libosp5 libostyle1c2 libperl-dev libtool-bin lua5.2 openjade opensp pdf2svg tcl-dev tcl8.6-dev texlive-formats-extra
0 upgraded, 15 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.8 MB of archives.
After this operation, 56.4 MB of additional disk space will be used.
Do you want to continue? [Y/n]Read More...
Building Debian packages for Buster from master is unfortunately not that simple, also when you:
apt source libindi*Probably it is indeed much simpler to compile from master, or checkout a certain tag version and compile. I use the following simple
bash script
indibuild.sh#!/bin/bash
declare -a INDI_DRIVERS=( indi-gphoto libatik indi-atik indi-asi indi-eqmod indi-gpsd )
MAIN_PATH=$(pwd)
INSTALL_PREFIX=/usr
# Cleanup build directories.
rm -rf ${MAIN_PATH}/build
# Create build directories.
mkdir -p ${MAIN_PATH}/build/libindi
for i in "${INDI_DRIVERS[@]}"
do
mkdir -p ${MAIN_PATH}/build/3rdparty/${i}
done
# Build libindi.
cd ${MAIN_PATH}/build/libindi
cmake -DCMAKE_INSTALL_PREFIX=${INSTALL_PREFIX} ../../libindi && make -j4 && sudo make install
# Build desired indi drivers.
for i in "${INDI_DRIVERS[@]}"
do
cd ${MAIN_PATH}/build/3rdparty/${i}
cmake -DCMAKE_INSTALL_PREFIX=${INSTALL_PREFIX} ${MAIN_PATH}/3rdparty/${i} && make -j4 && sudo make install
doneRead More...