Quantcast
Channel: Recent Topics - INDI Forum
Viewing all 14088 articles
Browse latest View live

Starlight Xpress MX drivers included in SX? - by: Barker

$
0
0
Hi INDI team, I hope this is the correct forum and place to bring up an issue.

I'm not a Linux expert but have sucessfully started migration of my astro systems from Windows to Ubuntu using Kstars and INDI.

I managed to get Skysensor 2000 and Canon 20d 'hooked-up' and responding using 'local' but have not succeded with my old MX5C camera that i hope to eventually use for autoguiding but initially for plantary work.

I acknowledge that normally Kstars forum should be used but I think the issue is not there since the Device Manager recognises my devices and works with all except MX5C and I think it maybe related to its USB HID or driver.

Is the MX series included in the INDI_SX driver?

With my basic terminal I used lsusb and dmesg to see that the MX5 doesn't appear in the lsusb but it does in the dmesg (20d is fine) like this:-
usb 2-2: new high-speed USB device number 7 using ehci_hcd

Kstars device manager shows status as red led and output below:-
2013-01-06T10:39:26: Client 0: new arrival from 127.0.0.1:52378 - welcome!
2013-01-06T10:39:26: Driver indi_sx_ccd: <- sxList 0
2013-01-06T10:39:26: Driver indi_sx_ccd: <- ISGetProperties
2013-01-06T10:39:26: Driver indi_sx_ccd: -> ISGetProperties((null))
2013-01-06T10:39:26: Driver indi_sx_ccd: <- ISGetProperties

I don't have the experience to start messing with udev and permissions, is there something I can do or is the driver not supporting MX devices?

Thanks in advance
Andrew

command line client for indiserver + indi_sx_ccd - by: hotblack43

$
0
0
Hello,
I want to use indiserver and the indi_sx_ccd driver to operate my SXV-H9 camera from the command line. I can start indiserver with indi_sx_ccd and then use the getINDI and setINDI commands from the xephem tools (I believe they originate there) and talk to the camera. It appears to answer. When I ask for what I think is an exposure with the command
./setINDI "SX CCD SXVR-H9.CCD_EXPOSURE.CCD_EXPOSURE_VALUE=0.9"
a lot of communication between camera and driver (I think) goes on - but where dopes the image go?

Can anyone tell me if I am doing the right thing, trying to use getINDI and setINDI with indi_sx_ccd in order to build a command line client?

Any ideas for already existing command line client software that uses indiserver on Linux?

If you know 'fswebcam' ffor ordinaru webcams you know the sort of program I am looking for.

Thanks for any help!

How to add a property to a standard driver? - by: vinvin

$
0
0
Hi, I'm developing a telescope driver for the MCMTII mount, documented here, code of the current INDI driver is here.
I'm using the standard Telescope driver. I'd like to add a "allow flip" property for German mounts. The tutorials and documentation on the website seem to refer to the versions of libindi in which there were not already the standard drivers, or at least don't seem to inherit from the standard classes (INDI::Telescope for me). The code that manages all properties seems quite complicated, is it possible to only have some simple code to manage a non-default property? Are there examples somewhere?
Thanks!

indiprop - by: aevers

$
0
0
I wrote a generic INDI properties browser. Source and information is available at indiprop.googlecode.com.

Enjoy!

SXVR-H5, H674 and H694 support in SX Driver - by: polakovic

$
0
0
To whom it may concern - SXVR-H5, H674 and H694 (both Mono and Color) are now recognised by SX Driver (r926 or later)...

SXVR-H694 on OSX is successfully tested, feedback for other platforms and/or cameras is welcome :-)

Peter

Arduino DSC driver - by: sbortolussi

$
0
0
Hello to all,
I wonder if I can ask some directions for the following diy project:
I would like to add DSC to my equatorial mount and to connect them to an indi client (XEphem).
I have 1024 p/r encoders + arduino uno. Now I missing the indi driver. What is the best way to proceed? Starting from an existing telescope driver (LX200?) and modify it? Is there a indi driver to manage only the encoders? I am not a programmer, I can write some basic code, so I would prefer to find a basic driver skeleton to modify.
Kind regards
Stefano

libindi-0.9.6 fails to compile - by: ptitjack

$
0
0
Hello,

I am working under Gentoo Linux and i can't compile libindi-0.9.6 from sources.
I followed the INSTALL instructions in /usr/local/share :
1) # tar xzvf libindi.tar.gz
2) # mkdir libindi_build
3) # cd libindi_build
4) # cmake -DCMAKE_INSTALL_PREFIX=/usr . ../libindi-0.9.6
5) # make install

It stops at the 89% step with the error :
Linking CXX executable tutorial_dome
libindidriver.so.0.9.6: undefined reference to `uncompress'
collect2: ld a retourné 1 code d'état d'exécution
make[2]: *** [tutorial_dome] Erreur 1
make[1]: *** [CMakeFiles/tutorial_dome.dir/all] Erreur 2
make: *** [all] Erreur 2

Can you help me ?

Thanks in advance,

Cheers,

--
Jacques

Arduino DSC driver - by: sbortolussi

$
0
0
Hello to all,
I wonder if I can ask some directions for the following diy project:
I would like to add DSC to my equatorial mount and to connect them to an indi client (XEphem).
I have 1024 p/r encoders + arduino uno. Now I missing the indi driver. What is the best way to proceed? Starting from an existing telescope driver (LX200?) and modify it? Is there a indi driver to manage only the encoders? I am not a programmer, I can write some basic code, so I would prefer to find a basic driver skeleton to modify.
Kind regards
Stefano

Astro-Physics GTO Driver - by: orly_andico

$
0
0
Hi all,

I may have hallucinated this, but I seem to recall that there was an AP GTO (CP2) driver for INDI.

Technically, this mount can be supported by the LX200 protocol.

Also, does the current LX200 driver support PulseGuide commands? and can lin_guider leverage INDI?

Meade DSI family support - by: orly_andico

$
0
0
hi all,

is there any reason why Meade DSI CCD's are not supported? as far as I can see the libdsi project on SourceForge provides this...

HOWTO: Building latest libindi & Ekos - by: knro

$
0
0
  • Ubuntu/Mint/Debian

  • Packages are already available for Ubuntu/Mint:



    If you have Ubuntu 13.10 or higher (or Mint 16 or higher), you can install kstars-bleeding which will install KStars, Ekos, libindi, and all 3rd party drivers.


    For Debian/Raspberry PI or older Ubuntu/Mint releases:


NOTE: If you want to just build libindi, you can omit as those are necessary for building KStars/Ekos.

  • OpenSUSE


  • Fedora/Redhat/Scientific Linux


  • Mageia/Mandriva


  • Manjaro/ArchLinux



  • Now that all the prerequisites are installed, you are ready to build libindi & KStars:

    CCD driver problems - by: beyond

    $
    0
    0
    I have been using PHD guiding with Microsoft webcam and gphoto2 with Nikon DSLR but am not able to get either working with INDI.
    The webcam works with mplayer tv://. With INDI the FITS viewer shows a few lines at the top of image and a shaded bar through middle. Same static image for video stream. Format selection issue?
    The DSLR works with gphoto2 --capture-image-and-download. With INDI the only apparent action is the Ekos log shows "Failed to set binning." with no shutter release from DSLR. The DSLR details are being populated in the status tab of the INDI control panel
    I have tried indi-full apt packages on fresh kubuntu 13.10. I was not able to install kstars-bleeding as apt-get reports an unmet dependency with libqjson, but I have tried the Ekos VM image with same result.
    I have also tried a few INDI device settings options but not seeing any changes.
    Any suggestions to debug where the problem is?
    Thanks, Mark

    Ekos & INDI on Rasbperry PI - by: knro

    $
    0
    0
    Today is the first day I didn't have to use my laptop to control my gear, I replaced it with Rasbperry PI! I purchased the PI along with USB WiFi dongle, and now it's sitting on the roof connected to all my equipment (QSI CCD, HEQ Mount, SX Lodestar, and MoonLite focuser). All the equipment are connected to a powered USB hub which also powers the PI. After installing libindi and all the drivers necessary for my gear, I simply SSHed into the PI and ran INDI server on the default port 7624.



    Then I configured Ekos for remote connection and viola I'm connected and now guiding and capturing images of M78! It's very seamless experience as if all the controls are local, but I'm doing it from the comfort of a warm living room!

    Anyone else tried INDI with Rasbperry PI?

    calibrating moonlite focuser with INDI - by: milosz

    $
    0
    0
    Hi,

    I'm trying to get my moonlite hi-res stepper driver to work with INDI. I managed to connect over serial port and move the drawtube in both directions. The problem is, I've no idea where the absolute '0' position should be? The moonlite INDI page says the drawtube should be fully retracted before powering the controller. Does that mean absolute 0 means the shortest possible drawtube (drawtube fully inside the OTA)? In my case the absolute position decreases when the drawtube is extending. That would mean absolute 0 is when the drawtube is fully extended. I'm lost. Any help is appreciated.

    Cheers,
    milosz

    QHY5 INDI driver - by: milosz

    $
    0
    0
    Hi,

    I tried guiding with QHY5 today and had some trouble connecting to the camera. When the camera is freshly connected to USB INDI driver can't connect to it. After I ran qhy_ccd_test INDI driver was able to connect to the camera, but only if indiserver was run as root. Interestingly USB VID/PID changed after running qhy_ccd_test (I suppose camera does some kind of re-enumeration). I didn't notice such behavior when using QHY5 under Windows (VID?PID change). I guess running indiserver as a root isn't the best idea. Is there anything I can do to sole this problem?

    Cheers,
    milosz

    DMK41 AU02.AS : How to configure it with INDI ? - by: bilbo-le-hobbit

    $
    0
    0
    Hello, two years proud owner of a DMK41 camera AU02.AS, one thing I miss: I've never been able to make it work under Linux. I yet have to go through a Windows virtualization, while the rest of my astronomical equipment is well recognized and operational with the INDI protocol under linux.
    But yesterday I found a topic on the Imaging Source forum explaining a method for the camera to be recognized via v4l2. I reproduced the same method without frankly understand, but it works! I can now open guvcview and connect the DMK, the video is displayed!
    Nice! I can try with Kstars ... The camera is well recognized with v4l2, but the picture is completely buggy

    I've taken the same image with guvcview and kstars

    What is wrong with the settings?

    First impression on Kstars+EKOS+INDI - by: milosz

    $
    0
    0
    Hi All,

    Sorry for the lengthy post but I couldn't resist. I was so impressed with Kstars and Ekos I had to write about it :)

    First of all many thanks for the great job you’ve done with Kstars and Ekos. I didn’t expect it to work so well. I managed to get all my devices working during the first session and almost got to serious imaging. There were some small problems on the way though.

    Kstars crashes a lot when zooming and pointing map to found targets. However it might be “fixed” by Jasem here:
    lists.kde.org/?l=kstars-devel&m=138807351307331&w=2
    Just tried that and similar fix applied also to asteroidscomponent.cpp solves the zoom problem.

    Ekos is a modal window. On my small screen it almost completely covers the kstars map. When I try to minimize the ekos window, kstars also gets minimized, so I can’t use the map. That is pretty annoying :(

    It happened a few times that I closed INDI configuration panel and I wasn’t able to reopen it from Ekos. I’m not really sure when it happens. Also when closing Ekos and Kstars, indiserver is not stopped automatically. One needs to remember about that or subsequent attempt to run INDI in ekos will fail (to connect to devices).

    Guiding didn’t work for me. I wasn’t able to go through calibration. The error message I got was that the mount didn’t go back to the initial position in DEC axis. I remember I had pretty big backlash in DEC axis. PHD was able to cope with that. That is a pity that ekos can’t (so I have to finally fix it). Anyway, there is one question I didn’t find answer for when reading the: do I need to align the guider with the mount? I mean that the edges of the image are aligned with star motion when moving mount in RA/DEC.

    After attempting to guide and calibrate the guider, EQMOD stopped working. I wasn’t able to slew the scope to new target. Restarting INDI usually helped, but it happened once that neither restarting INDI nor restarting kstars helped. I even tried disconnecting EQDIR. Only laptop restart helped resolving the problem.

    Plate solving worked well. However there is one annoying feature. Every time I start EQMOD I have to fill in the scope and guider aperture and focal length. I wasn’t able to save these values between restarts.

    Autofocus didn’t work at first but the camera was totally out of focus. After coarse manual focus I used auto-focus and it worked pretty well (didn’t try to cross check with mask though).

    CCD (capture) module wasn’t used a lot. I only took preview pictures because of the missing guiding. There was one annoying bit though. I had 2 cameras defined: main and guide. Every time I started ekos, guide cam appeared in the CCD module and Align module. This was tricky as plate solving didn’t work at first. Only after a moment I realized that I was using guide cam instead of main cam for Align.

    To sum up, I was very happy to go that far during first full session. I wasn't able to image under Linux before because of lack of Atik drivers. Now the drivers are there and kstars with ekos seem to be pretty good for astrophotography. There are some problems, but not that major.

    Cheers,
    milosz

    Nikon D7000 - by: slippo74

    $
    0
    0
    Hi there,

    First: I really want to thank you for this amazing piece of software. It's incredibly well made and I'm 100% sure it will bring my astrophotography experience to next level.

    I'm experiencing some issue while I'm trying to use my Nikon D7000 as primary CCD in Ekos.
    The camera appears to be working fine via Gphoto2 module and it seems that Ekos recognise it as "Online" when I connect it.
    However if I try to use the Preview or Capture and Solve functions, it doesn't go anywhere (just keep saying Capturing...).
    If I execute "gphoto2 --capture-image-and-download" I'm indeed able to get a picture from the camera.
    I know there is another post opened for similar issue but I would appreciate if you guys can help me with some direction.

    Thanks in advance

    Cris

    Suggestions for improvements - by: bilbo-le-hobbit

    $
    0
    0
    The weather is still bad here, I keep my tests in my living room ... I have a suggestion: In the EKOS panel, ccd tab, there is a window displaying the sequences queue. Once programmed sequence such LRVB Dark, I wish I could copy and duplicate this sequence in a loop (LRVBD,LRVBD,LRVBD...) . Would it be possible to add copy / paste to the sequences queue?
    On my Starlight Xpress filter wheel, I would like to display the name of each filter used, not its number. It would be nice to rename ourselves each slot used. Is this possible?

    ATIK driver does not work on Gentoo Linux - by: ptitjack

    $
    0
    0
    Hello,

    I am trying to get Atik driver working on Gentoo Linux and libindi-0.9.6.
    - I get the latest libindi-0.9.6 via svn
    svn checkout svn://svn.code.sf.net/p/indi/code/trunk/libindi libindi
    - make and make install without any problem
    - As i don't work on Ubuntu, i get the deb package and extract the tar.gz.
    - I copy indi_atik_ccd to /usr/bin
    - While launching indiserver by
    $indiserver indi_atik_ccd, i get a lot of lines :
    error while loading shared libraries: libnova-0.14.so.0: cannot open shared object file: No such file or directory
    - So i upgraded libnova from 0.12.3 to 0.14.0 but, now i get :
    error while loading shared libraries: libnova-0.12.so.3: cannot open shared object file: No such file or directory

    I really don't understand what's going on... :(

    Have you any idea ?

    Thanks very much

    --
    Jacques
    Viewing all 14088 articles
    Browse latest View live


    <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>