The slit is not centered...
252P_cap.jpg

Read More...

About new feature in Ekos, in could be interesting to
1) give some "pixel instructions" to autoguidage :
can tell to Ekos : put the star here, at coordinates X; Y
(I'm doing spectrocopy... so putting a star in a 23µm slit manually is an pain... if it can be done automagically... it's better )

2) add some measuring feature to fitsviewer, in order to see if parts of image are burned.
(important to big stars on astrophotography, and a little more in spectroscopy, where "burned pictures" means "no picture"

Read More...

Hi guys,

I'm doing spectroscopy with Ekos for a month now.

I need some improvments to do thing well and control better my exposition time
First : in fits viewer (in single frame or in ekos), when I use fits viewer, histogram tool... I found a Bug
I found that "MAX" displayed in stat is not 'pixel' max value but 'scale' max value. (scale that can be changed in histogram view)
So, this is not STATS... NB : it's the same for MIN value : it's the minimum of visualisation, not minimum Value.
(I get a eye on code... And it seems code call "DATAMAX/DATAMIN" fits keywords...

Specification of FITS standard says :
KEYWORD: DATAMAX
REFERENCE: FITS Standard
STATUS: reserved
HDU: image
VALUE: real
COMMENT: maximum data value
DEFINITION: The value field shall always contain a floating point
number, regardless of the value of BITPIX. This number shall give the
maximum valid physical value represented by the array, exclusive of any
special values.

SO... I don't think we can use it to store visualisation things as it represents the dynamic of picture.
-> let's create a SPECIAL KSTARS keyword, no ? (Something like : VISUMAX et VISUMIN...)

So, by consequence, statistics about MIN and MAX... are... fake (sorry for my poor english here...). It needs a calculation somewhere (at load ?)

In my use, I need to know which part of spectrum is overexposed. Statistics helps... but it could exist noisy/dark pixels that give a false sensation of overexposition... So I need something like:
-> A button that makes blink all pixels equals or higher ( ?) than the cam's deep or a human entry should be a solution (the better for me, as in DSLR) (first seconds of this video www.youtube.com/watch?v=tOh-ZWc3UNo )

-> Or a selection, then a right click to give stats (real one ) of this crop can be usable too.

Thanks guy.

JB

Read More...

I've just burn img 16.04 on a RPI 3... then I've applied your script...
All is working as I can see. Great job.
The only thing I had to do is setup ssh On.
Next week I will make some tries with real devices.

Read More...

Hi guys,
Atik drivers are built on 32/.64 PC family computer
32 bit arm

As 64 bits is now the standard, on PC as in ARM world, does ATik wil provide 64 bits drivers on this archtecture ?

Thanks a lot,

JB

Read More...

Note really sure

I wil take a look

Read More...

OK... have to rearrange atik xml :
<?xml version="1.0" encoding="UTF-8"?>
<driversList>

<devGroup group="CCDs">
<device label="ATIK CCD">
<driver name="ATIK CCD">indi_atik_ccd</driver>
<version>0.25</version>
</device>
</devGroup>

<devGroup group="Filter Wheels">
<device label="ATIK Wheel">
<driver name="ATIK Wheel">indi_atik_wheel</driver>
<version>0.25</version>
</device>
</devGroup>
</driversList>

Read More...

Hi all

on a updated 16.10 on x86 :
I've followed this github.com/knro/indiwebmanager

And I have some issues :
stro@serveur-astro:~$ /usr/bin/python /home/astro/indiwebmanager/servermanager/drivermanager.py
/usr/share/indi/indi_qsi.xml
/usr/share/indi/indi_nexstarevo.xml
/usr/share/indi/indi_aagcloudwatcher.xml
/usr/share/indi/indi_qhy.xml
/usr/share/indi/indi_dsi.xml
/usr/share/indi/indi_miccd.xml
/usr/share/indi/indi_sbig.xml
/usr/share/indi/indi_asi.xml
/usr/share/indi/drivers.xml
/usr/share/indi/indi_sx.xml
/usr/share/indi/indi_fli.xml
/usr/share/indi/indi_maxdomeii.xml
/usr/share/indi/indi_eqmod.xml
/usr/share/indi/indi_apogee.xml
/usr/share/indi/indi_gpsd.xml
/usr/share/indi/indi_gphoto.xml
/usr/share/indi/indi_fishcamp.xml
/usr/share/indi/indi_ffmv.xml
/usr/share/indi/indi_duino.xml
/usr/share/indi/indi_atik.xml
Parsing XML file: /usr/share/indi/indi_qsi.xml
Parsing XML file: /usr/share/indi/indi_nexstarevo.xml
Parsing XML file: /usr/share/indi/indi_aagcloudwatcher.xml
Parsing XML file: /usr/share/indi/indi_qhy.xml
Parsing XML file: /usr/share/indi/indi_dsi.xml
Parsing XML file: /usr/share/indi/indi_miccd.xml
Parsing XML file: /usr/share/indi/indi_sbig.xml
Parsing XML file: /usr/share/indi/indi_asi.xml
Parsing XML file: /usr/share/indi/drivers.xml
Parsing XML file: /usr/share/indi/indi_sx.xml
Parsing XML file: /usr/share/indi/indi_fli.xml
Parsing XML file: /usr/share/indi/indi_maxdomeii.xml
Parsing XML file: /usr/share/indi/indi_eqmod.xml
Parsing XML file: /usr/share/indi/indi_apogee.xml
Parsing XML file: /usr/share/indi/indi_gpsd.xml
Parsing XML file: /usr/share/indi/indi_gphoto.xml
Parsing XML file: /usr/share/indi/indi_fishcamp.xml
Parsing XML file: /usr/share/indi/indi_ffmv.xml
Parsing XML file: /usr/share/indi/indi_duino.xml
Parsing XML file: /usr/share/indi/indi_atik.xml
Traceback (most recent call last):
File "/home/astro/indiwebmanager/servermanager/drivermanager.py", line 5, in <module>
from parsedrivers import driversList, findDriverByLabel, DeviceDriver
File "/home/astro/indiwebmanager/servermanager/parsedrivers.py", line 33, in <module>
tree = ET.parse(file)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 656, in parse
parser.feed(data)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1653, in feed
self._raiseerror(v)
File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1517, in _raiseerror
raise err


Any ideas ?

Read More...

Issue I have is I need to focus mannually guider. And to do this, I need a stable reading... or I have lots of issues. when some picture are taken, driver segfault, I need to relaunch indiserver... so it's a pain.

I want a stable guider

NB : for titan : my twos titans have issues under all linuxes I've tried, over all hub USB I've tried (it happens...)

Read More...

Hi guys !!

i have a Titan that doesn't work here and a QHY 5...that makes somes trouble sometimes (we are QHY5 owner to have this issue as I see on forum)

Is there a really good cheap cam that can autoguide "plug and play" with indi ?

happy new year !

Read More...

Hi

could you explain a little bit more :
1) why you did not use kstars-bleeding from jasem ppa ?
2) how you compile cfitsio in 32 bit ? (I'm really not a multiarch guru) (I've still compil it in 64 bits
3) about using cfitsio 32, you call setenv, then start indiserver ? (or it is on the same line)

Thanks for all

Read More...

Hi

this is a veru good job ! I have exactly the same devices but... I needed to reinstall in 32 bit in order to use Atik things. (So I've install a odrobian not supported by "odroid" so each update is a pain.)

Could you explain here or somewhere how you install all this ?

WHat about "indiseparate server", could you explain this please ?

Read More...

Hi guys... I have an issue in compiling qhy driver :
odroid@odroid32:~/indi-git/3rdparty/indi-qhy$ cd ../libqhy/
odroid@odroid32:~/indi-git/3rdparty/libqhy$ cmake -DCMAKE_INSTALL_PREFIX=/usr
running cp /home/odroid/indi-git/3rdparty/libqhy/libqhy_armv8.bin /home/odroid/indi-git/3rdparty/libqhy/libqhy.so.0.1.8 2>&1
-- Configuring done
-- Generating done
-- Build files have been written to: /home/odroid/indi-git/3rdparty/libqhy
odroid@odroid32:~/indi-git/3rdparty/libqhy$ make
odroid@odroid32:~/indi-git/3rdparty/libqhy$ sudo make install
Install the project...
-- Install configuration: ""
-- Up-to-date: /usr/include/libqhy/qhyccd.h
-- Up-to-date: /usr/include/libqhy/qhyccdcamdef.h
-- Up-to-date: /usr/include/libqhy/qhyccderr.h
-- Up-to-date: /usr/include/libqhy/qhyccdstruct.h
-- Up-to-date: /usr/include/libqhy/log4z.h
-- Installing: /usr/lib/libqhy.so.0.1.8
-- Up-to-date: /lib/udev/rules.d/85-qhy.rules
-- Up-to-date: /lib/firmware/qhy/QHY290.img
-- Up-to-date: /lib/firmware/qhy/QHY10.HEX
-- Up-to-date: /lib/firmware/qhy/POLEMASTER.HEX
-- Up-to-date: /lib/firmware/qhy/QHY8PRO.HEX
-- Up-to-date: /lib/firmware/qhy/QHY29.HEX
-- Up-to-date: /lib/firmware/qhy/IMG0H.HEX
-- Up-to-date: /lib/firmware/qhy/QHY6.HEX
-- Up-to-date: /lib/firmware/qhy/QHY5II.HEX
-- Up-to-date: /lib/firmware/qhy/QHY28.HEX
-- Up-to-date: /lib/firmware/qhy/QHY8M.HEX
-- Up-to-date: /lib/firmware/qhy/QHY8L.HEX
-- Up-to-date: /lib/firmware/qhy/QHY5III224.img
-- Up-to-date: /lib/firmware/qhy/QHY163.img
-- Up-to-date: /lib/firmware/qhy/QHY16200A.HEX
-- Up-to-date: /lib/firmware/qhy/QHY15.HEX
-- Up-to-date: /lib/firmware/qhy/QHY2.HEX
-- Up-to-date: /lib/firmware/qhy/QHY224.img
-- Up-to-date: /lib/firmware/qhy/QHY5III290.img
-- Up-to-date: /lib/firmware/qhy/IC16200A.HEX
-- Up-to-date: /lib/firmware/qhy/QHY183.img
-- Up-to-date: /lib/firmware/qhy/miniCam5.HEX
-- Up-to-date: /lib/firmware/qhy/QHY23.HEX
-- Up-to-date: /lib/firmware/qhy/IMG2P.HEX
-- Up-to-date: /lib/firmware/qhy/QHY11.HEX
-- Up-to-date: /lib/firmware/qhy/IC8300.HEX
-- Up-to-date: /lib/firmware/qhy/QHY27.HEX
-- Up-to-date: /lib/firmware/qhy/QHY160002AD.HEX
-- Up-to-date: /lib/firmware/qhy/IMG50.HEX
-- Up-to-date: /lib/firmware/qhy/QHY21.HEX
-- Up-to-date: /lib/firmware/qhy/IMG2S.HEX
-- Up-to-date: /lib/firmware/qhy/QHY8.HEX
-- Up-to-date: /lib/firmware/qhy/QHY814A.HEX
-- Up-to-date: /lib/firmware/qhy/QHY5.HEX
-- Up-to-date: /lib/firmware/qhy/IC90A.HEX
-- Up-to-date: /lib/firmware/qhy/QHY12.HEX
-- Up-to-date: /lib/firmware/qhy/QHY20.HEX
-- Up-to-date: /lib/firmware/qhy/QHY16000.HEX
-- Up-to-date: /lib/firmware/qhy/QHY695A.HEX
-- Up-to-date: /lib/firmware/qhy/QHY2E.HEX
-- Up-to-date: /lib/firmware/qhy/QHY5III185.img
-- Up-to-date: /lib/firmware/qhy/QHY7.HEX
-- Up-to-date: /lib/firmware/qhy/QHY5III178.img
-- Up-to-date: /lib/firmware/qhy/IC16803.HEX
-- Up-to-date: /lib/firmware/qhy/QHY90A.HEX
-- Up-to-date: /lib/firmware/qhy/QHY16.HEX
-- Up-to-date: /lib/firmware/qhy/QHY5III174.img
-- Up-to-date: /lib/firmware/qhy/QHY174.img
-- Up-to-date: /lib/firmware/qhy/QHY22.HEX
-- Up-to-date: /lib/firmware/qhy/QHY9S.HEX
-- Up-to-date: /lib/firmware/qhy/QHY2PRO.HEX
-- Up-to-date: /lib/firmware/qhy/QHY5LOADER.HEX
-- Up-to-date: /lib/firmware/qhy/QHY178.img
running /usr/bin/cmake -E create_symlink /usr/lib/libqhy.so.0.1.8 /usr/lib/libqhy.so.0 2>&1
running /usr/bin/cmake -E create_symlink /usr/lib/libqhy.so.0 /usr/lib/libqhy.so 2>&1
odroid@odroid32:~/indi-git/3rdparty/libqhy$ cd ../indi-qhy/
odroid@odroid32:~/indi-git/3rdparty/indi-qhy$ cmake -DCMAKE_INSTALL_PREFIX=/usr
-- Found CFITSIO: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found INDI: /usr/lib/arm-linux-gnueabihf/libindi.so
-- Found libqhy: /usr/lib/libqhy.so
-- Found libusb-1.0:
-- - Includes: /usr/include/libusb-1.0
-- - Libraries: /usr/lib/arm-linux-gnueabihf/libusb-1.0.so
-- Configuring done
-- Generating done
-- Build files have been written to: /home/odroid/indi-git/3rdparty/indi-qhy
odroid@odroid32:~/indi-git/3rdparty/indi-qhy$ make
Linking CXX executable indi_qhy_ccd
/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../libqhy.so: file not recognized: Format de fichier non reconnu
collect2: error: ld returned 1 exit status
CMakeFiles/indi_qhy_ccd.dir/build.make:89: recipe for target 'indi_qhy_ccd' failed
make[2]: *** [indi_qhy_ccd] Error 1
CMakeFiles/Makefile2:60: recipe for target 'CMakeFiles/indi_qhy_ccd.dir/all' failed
make[1]: *** [CMakeFiles/indi_qhy_ccd.dir/all] Error 2
Makefile:117: recipe for target 'all' failed
make: *** [all] Error 2
odroid@odroid32:~/indi-git/3rdparty/indi-qhy$ sudo make install
Linking CXX executable indi_qhy_ccd
/usr/lib/gcc/arm-linux-gnueabihf/4.9/../../../libqhy.so: file not recognized: Format de fichier non reconnu
collect2: error: ld returned 1 exit status
CMakeFiles/indi_qhy_ccd.dir/build.make:89: recipe for target 'indi_qhy_ccd' failed
make[2]: *** [indi_qhy_ccd] Error 1
CMakeFiles/Makefile2:60: recipe for target 'CMakeFiles/indi_qhy_ccd.dir/all' failed
make[1]: *** [CMakeFiles/indi_qhy_ccd.dir/all] Error 2
Makefile:117: recipe for target 'all' failed
make: *** [all] Error 2
odroid@odroid32:~/indi-git/3rdparty/indi-qhy$

Does anyone an idea ?

JB

Read More...

E: Impossible de récupérer ppa.launchpad.net/mutlaqja/ppa/ubuntu/po...ntu16.04.1_amd64.deb 404 Not Found

E: Impossible de récupérer certaines archives, peut-être devrez-vous lancer apt-get update ou essayer avec --fix-missing ?

Read More...

this one (just pushed.)
github.com/djibb/indi/tree/master/3rdparty/indi-shelyak

Read More...